Database Develop

[SOLVED] my incredible S stuck at HTC Logo After OTA Update

Hello, i Have HTC Incredible S.
my phone was S-Off with EhabFG RUU, after 2.3.5, 3.0 Sence officially released i decided to get back to original RUU.
i installed 2.1 RUU and then i performed steps here:
http://forum.xda-developers.com/showthread.php?t=1359555
to get back my S-ON to get update, after that i request OTA and installed 2.3.5 RUU successfully, after rebooting my phone now is stuck on HTC Logo and i can't do anything.
can anyone help me what can i do to get my phone back?
my bootloader still alive, but when i tried to install any official Rom but i'm receiving error said this RUU is older than i have.
Please Help.
Regards

hamza_aj said:
Hello, i Have HTC Incredible S.
my phone was S-Off with EhabFG RUU, after 2.3.5, 3.0 Sence officially released i decided to get back to original RUU.
i installed 2.1 RUU and then i performed steps here:
http://forum.xda-developers.com/showthread.php?t=1359555
to get back my S-ON to get update, after that i request OTA and installed 2.3.5 RUU successfully, after rebooting my phone now is stuck on HTC Logo and i can't do anything.
can anyone help me what can i do to get my phone back?
my bootloader still alive, but when i tried to install any official Rom but i'm receiving error said this RUU is older than i have.
Please Help.
Regards
Click to expand...
Click to collapse
You need to go into Fastboot mode and enter the command:
Fastboot getvar main_version and post your results. Also a shot of what your current HBOOT screen looks like.

tpbklake said:
You need to go into Fastboot mode and enter the command:
Fastboot getvar main_version and post your results. Also a shot of what your current HBOOT screen looks like.
Click to expand...
Click to collapse
thank you for fast respons.
my HBOOT Screen:
===
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3822.10.08.28_M
eMMC-boot
Apr 1 2011,18:34:39
===
and i don't know why i get error for the command you give, i get this result:
===
C:\Android>Fastboot getvar main_version
getvar:main_version FAILED (remote: unknown command)
finished. total time: 0.001s
===
Thank again

hamza_aj said:
thank you for fast respons.
my HBOOT Screen:
===
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3822.10.08.28_M
eMMC-boot
Apr 1 2011,18:34:39
===
and i don't know why i get error for the command you give, i get this result:
===
C:\Android>Fastboot getvar main_version
getvar:main_version FAILED (remote: unknown command)
finished. total time: 0.001s
===
Thank again
Click to expand...
Click to collapse
Ok try Fastboot getvar all and post the results.

tpbklake said:
Ok try Fastboot getvar all and post the results.
Click to expand...
Click to collapse
this is the result:
===
C:\Android>Fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.13.0000
INFOversion-baseband: 3822.10.08.28_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.09.415.2
INFOserialno: HT16ATD00221
INFOimei: 355301049745212
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 3876mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.021s
===
Sincerely

hamza_aj said:
this is the result:
===
C:\Android>Fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.13.0000
INFOversion-baseband: 3822.10.08.28_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.09.415.2
INFOserialno: HT16ATD00221
INFOimei: 355301049745212
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 3876mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.021s
===
Sincerely
Click to expand...
Click to collapse
Ok the line version-main shows that you have 3.09.415.2 which is what the OTA Attempted to install. In order to flash an older RUU, you need to change this value using the main_version program to something like 1.00.0000. Search this forum for downgrading hboot and you should find instructions on how to do that.

tpbklake said:
Ok the line version-main shows that you have 3.09.415.2 which is what the OTA Attempted to install. In order to flash an older RUU, you need to change this value using the main_version program to something like 1.00.0000. Search this forum for downgrading hboot and you should find instructions on how to do that.
Click to expand...
Click to collapse
OK, thank you i'll search for it, and if you found the link please posted here.
Thanks

hamza_aj said:
OK, thank you i'll search for it, and if you found the link please posted here.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20024110&postcount=10
This link shows you exactly what you need to do. The original post of this thread should have the file to download that contains the main_ version app.

tpbklake said:
http://forum.xda-developers.com/showpost.php?p=20024110&postcount=10
This link shows you exactly what you need to do. The original post of this thread should have the file to download that contains the main_ version app.
Click to expand...
Click to collapse
thank you very much i will apply this steps now.
Best Regards

hamza_aj said:
thank you very much i will apply this steps now.
Best Regards
Click to expand...
Click to collapse
Hello, back again with no luck.
i see this steps for a device starting normally but my device freezing on HTC Logo so i can't do many steps here.
also, i tried to open downgrade toolkit, and the result still as the same.
can anyone help?
Regards

hamza_aj said:
Hello, back again with no luck.
i see this steps for a device starting normally but my device freezing on HTC Logo so i can't do many steps here.
also, i tried to open downgrade toolkit, and the result still as the same.
can anyone help?
Regards
Click to expand...
Click to collapse
OK, so inside the downgrade toolkit zip file you should find both zergRush and misc_version images, right?
Here are the steps you need to try using adb after you copy the zergRush and misc_version images to the same directory where you have adb.exe and fastboot.exe:
adb shell rm -r /data/local/tmp/*
adb push zergRush /data/local/tmp/zergRush
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/zergRush
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 1.00.000.0'
Once you have done that then you can try flashing the RUU for your region.

Possible to s-off again and reflash boot.img from official RUU?
Not familiar with these issues as I find it hard to fathom why one would want to go official after trying so hard to go custom.
Edit: @tpbklake I don't want to step in on your support, but are you sure your code is correct? It's pushing zergrush and misc_version into their own folders within tmp but executing from tmp? Misc_version needs superuser permissions.

Nonverbose said:
Possible to s-off again and reflash boot.img from official RUU?
Not familiar with these issues as I find it hard to fathom why one would want to go official after trying so hard to go custom.
Click to expand...
Click to collapse
I completely agree, but the fact is some of these noobs see an OTA pop up and immediately think they need to flash it and end up in these situations without even reading and researching. Then they come help looking for help...

tpbklake said:
I completely agree, but the fact is some of these noobs see an OTA pop up and immediately think they need to flash it and end up in these situations without even reading and researching. Then they come help looking for help...
Click to expand...
Click to collapse
Lol yeah I noticed, but I also noticed that you're almost always the first and usually only one helping them out.
While I think your hard work and tireless efforts are commendable, spoon feeding noobs will just make them that much more dependant on you next time, and the time after that,etc..
From what I have seen of your activity on this forum, your thanks meter should be well in excess of your posts. /2c
Happy new year

Nonverbose said:
Lol yeah I noticed, but I also noticed that you're almost always the first and usually only one helping them out.
While I think your hard work and tireless efforts are commendable, spoon feeding noobs will just make them that much more dependant on you next time, and the time after that,etc..
From what I have seen of your activity on this forum, your thanks meter should be well in excess of your posts. /2c
Happy new year
Click to expand...
Click to collapse
I try to help, but I like to take the approach together them to search and find things on their own. I try to not post step by step, especially when someone else has done it.
It is like baking a cake. You can give them a recipe, but if they don't know how to turn on an oven, run a mixer or know the measurement abbrev. then that recipe is not of much value now is it?

tpbklake said:
OK, so inside the downgrade toolkit zip file you should find both zergRush and misc_version images, right?
Here are the steps you need to try using adb after you copy the zergRush and misc_version images to the same directory where you have adb.exe and fastboot.exe:
adb shell rm -r /data/local/tmp/*
adb push zergRush /data/local/tmp/zergRush
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/zergRush
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 1.00.000.0'
Once you have done that then you can try flashing the RUU for your region.
Click to expand...
Click to collapse
thank you very much for your kind replay.
i tried to do this steps but i'm receiving this:
===
C:\Android>adb shell rm -r /data/local/tmp/*
adb server is out of date. killing...
* daemon started successfully *
error: device not found
===
i don't know if should i attache my device to fastboot or HBOOT USB but i tried both.
i attached my device and accessed to: HBOOT USB and i see: HBOOT USB PLUG
and i take fast boot and i can see: FASTBOOT USB.
why i'm receiving device not found?
sorry for a lot questions and thanks again for help.
Regards

hamza_aj said:
thank you very much for your kind replay.
i tried to do this steps but i'm receiving this:
===
C:\Android>adb shell rm -r /data/local/tmp/*
adb server is out of date. killing...
* daemon started successfully *
error: device not found
===
i don't know if should i attache my device to fastboot or HBOOT USB but i tried both.
i attached my device and accessed to: HBOOT USB and i see: HBOOT USB PLUG
and i take fast boot and i can see: FASTBOOT USB.
why i'm receiving device not found?
sorry for a lot questions and thanks again for help.
Regards
Click to expand...
Click to collapse
You need to have the phone booted normally when you are typing the adb commands.

tpbklake said:
You need to have the phone booted normally when you are typing the adb commands.
Click to expand...
Click to collapse
thank you, but as i told you from the biganning my phone is not starting normally. it just start and stuck on HTC Logo.
can i do something in my case?
thanks

Try flashing a custom rom

hamza_aj said:
thank you, but as i told you from the biganning my phone is not starting normally. it just start and stuck on HTC Logo.
can i do something in my case?
thanks
Click to expand...
Click to collapse
OK, do you still have the OTA file that you attempted to flash? It is probably still on your microSD card in one of the directories somewhere.
If you open that OTA.zip file, there should be a file inside called firmware.zip (or firmware.img can't remember which one it is). If you extract that file and then copy it to your microSD car and rename it PG32IMG.zip (or PG32IMG.img if it is firmware.img) and then reboot into HBOOT mode, it will attempt to install this and if it is successful you should be good to go.

Messed up HTC One

Hi all,
I am Marc and i'm new here on the forum..(and in installing custom roms). so i tried cyanogenmod for a couple of days , but then i decided to go back to stock rom. And somehow,i messed up at that moment. I now have a HTC One wich will only boot in bootloader mode,nothing else.
If i set the Phone to fastboot mode, i don't see it in windows..if it's in recovery mode i see the Phone in windows,but it is unaccessable...so i can't copy a new rom to the Phone and reinstall it with twrp recovery.(that is on the Phone)
HTC One is a international version. Here is the getvar info..
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__E11
battery-status: good
battery-voltage: 4291mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Confused as i was i formatted the system in recovery mode and now it looks like there's no partition anymore..
I'm desperate...can somebody help me?

marc1201 said:
Hi all,
I am Marc and i'm new here on the forum..(and in installing custom roms). so i tried cyanogenmod for a couple of days , but then i decided to go back to stock rom. And somehow,i messed up at that moment. I now have a HTC One wich will only boot in bootloader mode,nothing else.
If i set the Phone to fastboot mode, i don't see it in windows..if it's in recovery mode i see the Phone in windows,but it is unaccessable...so i can't copy a new rom to the Phone and reinstall it with twrp recovery.(that is on the Phone)
HTC One is a international version. Here is the getvar info..
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__E11
battery-status: good
battery-voltage: 4291mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Confused as i was i formatted the system in recovery mode and now it looks like there's no partition anymore..
I'm desperate...can somebody help me?
Click to expand...
Click to collapse
you must be using Windows 8.1
get yourself Windows 7 or Ubuntu
Sent from my One using Tapatalk

kamilmirza said:
you must be using Windows 8.1
get yourself Windows 7 or Ubuntu
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I am using windows 7 pro

marc1201 said:
I am using windows 7 pro
Click to expand...
Click to collapse
in custom recovery use:
adb push <name of rom>.zip /data/media/0/
or
adb sideload <name of rom>.zip
to get a ROM onto your phone and install it.

nkk71 said:
in custom recovery use:
adb push <name of rom>.zip /data/media/0/
or
adb sideload <name of rom>.zip
to get a ROM onto your phone and install it.
Click to expand...
Click to collapse
When i use adb push i got the following:
C:\Users\Marc\Downloads\HTCOneRoot>adb push firmware 3.62.401.1.zip/data/media/0
/
error: closed
So it says error: closed
When i use adb sideload it says:
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\Marc\Downloads\HTCOneRoot>
I don't know anymore...I'm really new in these things
Marc

marc1201 said:
When i use adb push i got the following:
C:\Users\Marc\Downloads\HTCOneRoot>adb push firmware 3.62.401.1.zip/data/media/0
I don't know anymore...I'm really new in these things
Marc
Click to expand...
Click to collapse
1- Why are you pushing a firmware?? you need to push a ROM
2- adb push <name of rom without spaces>.zip /data/media/0/ , you typed:
adb push firmware<space should not be here>3.62.401.1.zip<missing space>/data/media/0

nkk71 said:
1- Why are you pushing a firmware?? you need to push a ROM
2- adb push <name of rom without spaces>.zip /data/media/0/ , you typed:
adb push firmware<space should not be here>3.62.401.1.zip<missing space>/data/media/0
Click to expand...
Click to collapse
@ nkk71, isn't that the same?(rom or firmware) The file i downloaded is named firmware 3.62.401.1,wich should be the 4.3 rom with sense 5.5...
I guess i better left it Original..:crying:
Edit: when i do it like you said i still got the same error:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
C:\Users\Marc\Downloads\HTCOneRoot>

marc1201 said:
isn't that the same?(rom or firmware) The file i downloaded is named firmware 3.62.401.1,wich should be the 4.3 rom with sense 5.5...
I guess i better left it Original..:crying:
Click to expand...
Click to collapse
NO, it is certainly not the same.
I think you should take a break (before you do something you'll really regret), and do some reading (no offense intended).... we were all where you are now, but start searching and reading.

nkk71 said:
NO, it is certainly not the same.
I think you should take a break (before you do something you'll really regret), and do some reading (no offense intended).... we were all where you are now, but start searching and reading.
Click to expand...
Click to collapse
I think i should do that yes.. I have another file called M7-3.4.10-g6ac477c This is the rom i think.(m7 is given in the file name)
But still got errors...:crying::crying::crying:
I think i just going to send it to HTC...No warranty then,but probably less cost then buying a new one
Another question..do i need to have S-OFF?? It's still on S-ON...

marc1201 said:
I think i should do that yes.. I have another file called M7-3.4.10-g6ac477c This is the rom i think.(m7 is given in the file name)
But still got errors...:crying::crying::crying:
I think i just going to send it to HTC...No warranty then,but probably less cost then buying a new one
Another question..do i need to have S-OFF?? It's still on S-ON...
Click to expand...
Click to collapse
While in fastboot USB, use the command "fastboot erase cache", and then push the ROM, not the firmware..... do what nkk71 wrote and you should be alright! Do not send the phone to HTC, you will get no refund or repair done

I am able to erase the cache but pushing the rom will not work here.. then somehowe the device is not recognized
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.066s
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
List of devices attached
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
List of devices attached
FA35RW907658 recovery
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
cannot stat 'm7-3.4.10-g6ac477c.zip': No such file or directory
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
error: device not found

marc1201 said:
I am able to erase the cache but pushing the rom will not work here.. then somehowe the device is not recognized
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.066s
C:\Users\Marc\Downloads\HTCOneRoot>adb push m7-3.4.10-g6ac477c.zip /data/media/0
/
error: device not found
error: device not found
Click to expand...
Click to collapse
you need to be in custom recovery for adb to work
bootloader => only fastboot commands
custom recovery => only adb commands
booted ROM with USB debugging enabled => only adb commands
I don't know where you got that file from (or if it is even a ROM, looks more like a kernel to me), but check my signature and use Clyde's index thread for a list of ROMs.
I'm on ARHD: http://forum.xda-developers.com/showthread.php?t=2183023
Recommended recovery (especially for 4.4 ROMs) is TWRP at the moment:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
make sure to check MD5 to know it's not a corrupt download, that site doesnt work with download managers.
in bootloader:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery
adb devices -> confirm it shows up
adb push Android_Revolution_HD-One_51.0.zip /data/media/0/ <- this will take about 5 mins, and will not show any progress until it's finished
in recovery select "install" and choose the ROM, go through the installation (and select wipe!!)
I hope that's clear

nkk71 said:
you need to be in custom recovery for adb to work
bootloader => only fastboot commands
custom recovery => only adb commands
booted ROM with USB debugging enabled => only adb commands
I don't know where you got that file from (or if it is even a ROM, looks more like a kernel to me), but check my signature and use Clyde's index thread for a list of ROMs.
I'm on ARHD: http://forum.xda-developers.com/showthread.php?t=2183023
Recommended recovery (especially for 4.4 ROMs) is TWRP at the moment:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
make sure to check MD5 to know it's not a corrupt download, that site doesnt work with download managers.
in bootloader:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery
adb devices -> confirm it shows up
adb push Android_Revolution_HD-One_51.0.zip /data/media/0/ <- this will take about 5 mins, and will not show any progress until it's finished
in recovery select "install" and choose the ROM, go through the installation (and select wipe!!)
I hope that's clear
Click to expand...
Click to collapse
nkk71,that's pretty clear,downloaded the Android_Revolution_HD-One_31.6.zip and followed all the steps you mentioned..But the Phone still won't cooperate.. I got a protocol failure..What is this?
C:\Users\Marc\Downloads\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6
.3.3-m7.img
< waiting for device >
sending 'recovery' (9184 KB)...
OKAY [ 1.165s]
writing 'recovery'...
OKAY [ 0.716s]
finished. total time: 1.884s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.058s]
finished. total time: 0.059s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA35xxxxx sideload
C:\Users\Marc\Downloads\HTCOneRoot>adb push Android_Revolution_HD-One_31.6.zip /
data/media/0/
protocol failure
C:\Users\Marc\Downloads\HTCOneRoot>
At a second try i got this..:
C:\Users\Marc\Downloads\HTCOneRoot>adb push Android_Revolution_HD-One_31.6.zip /
data/media/0/
failed to copy 'Android_Revolution_HD-One_31.6.zip' to '/data/media/0/': Is a di
rectory
What does the sideload after the FA35XXX number? I tought it had to be FA35XXX Device...?

If device is in sideload then do adb sideload romname.zip
sent from my mobile device

marc1201 said:
nkk71,that's pretty clear,downloaded the Android_Revolution_HD-One_31.6.zip and followed all the steps you mentioned..But the Phone still won't cooperate.. I got a protocol failure..What is this?
C:\Users\Marc\Downloads\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6
.3.3-m7.img
< waiting for device >
sending 'recovery' (9184 KB)...
OKAY [ 1.165s]
writing 'recovery'...
OKAY [ 0.716s]
finished. total time: 1.884s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.058s]
finished. total time: 0.059s
C:\Users\Marc\Downloads\HTCOneRoot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
C:\Users\Marc\Downloads\HTCOneRoot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA35RW907658 sideload
C:\Users\Marc\Downloads\HTCOneRoot>adb push Android_Revolution_HD-One_31.6.zip /
data/media/0/
protocol failure
C:\Users\Marc\Downloads\HTCOneRoot>
Click to expand...
Click to collapse
you have to download a ROM. look here. http://forum.xda-developers.com/showthread.php?t=2183023 Download that rom and then do the above command.Just make sure you type in the correct name of the file in your command window. Firmware is not the same as a ROM. a ROM is a custom version of the operating system i.e. Android in this case. There are many ROMS to choose from. What you are attempting is not correct. This is why you must read.read .read and read BEFORE you attemp anything on a very expensive device. OK? Capeesh? Alright.

@ SaHiLzZ , sideload did the trick
Running the revolution HD-One 3.61 rom now...so back online hehe. Just pity that it isn't a stock rom...I rather had the Phone back in Original state..but that's a thing for later
Is there anyone out here who can help me find the Original stock rom...?
But for now, i am very happy that it runs again and i want to say a very big thank you to all that helped me !! THANK YOU !
Marc

marc1201 said:
@ SaHiLzZ , sideload did the trick
Running the revolution HD-One 3.61 rom now...so back online hehe. Just pity that it isn't a stock rom...I rather had the Phone back in Original state..but that's a thing for later
Is there anyone out here who can help me find the Original stock rom...?
But for now, i am very happy that it runs again and i want to say a very big thank you to all that helped me !! THANK YOU !
Marc
Click to expand...
Click to collapse
Why would you want to go back to stock ROM? ARHD is completely stock, just rooted and with improvements:
This is improved version of stock ROM - no visual changes!
Click to expand...
Click to collapse

nkk71 said:
Why would you want to go back to stock ROM? ARHD is completely stock, just rooted and with improvements:
Click to expand...
Click to collapse
Nkk71,this phone is only about 5 months old and i'm thinking about selling it. So to avoid warranty issues for the new owner and beeing able to update(via HTC) i want the phone back to original state.
Thus..again the question, who can help me with a stock rom?
Thanks again,
Marc

marc1201 said:
Nkk71,this phone is only about 5 months old and i'm thinking about selling it. So to avoid warranty issues for the new owner and beeing able to update(via HTC) i want the phone back to original state.
Thus..again the question, who can help me with a stock rom?
Thanks again,
Marc
Click to expand...
Click to collapse
modelid: PN0710000
cidnum: HTC__E11
Click to expand...
Click to collapse
if you want to sell it and/or return to 100% stock, you can follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
RUU.ZIP method, using this ruu.zip: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/

nkk71 said:
if you want to sell it and/or return to 100% stock, you can follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
RUU.ZIP method, using this ruu.zip: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
Click to expand...
Click to collapse
I am going to read your guide from a to z to be sure i don't brick it again.
Thanks once more for the help, i really appreciate it !

Ok I need help getting back to stock asap!!!

Hi, please can someone help me getting back to stock. I have tried using guides but I am just stumped.
My phone is a UK model unlocked to any network, I have messed around with it a lot and think I have messed up the radios or something as I am only getting Edge connectivity even though all my friends are getting HSPA on the same network, something is just not right!
C:\Users\Nath\Desktop\Fastboot>Fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.20.3263.16
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: SH3BRW902127
INFOimei: xxxxxxxxxxxxxxxxxxxx
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 3754mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-4dab9d12
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.051s

Soff first. Then you can flash an older RUU..

SaHiLzZ said:
Soff first. Then you can flash an older RUU..
Click to expand...
Click to collapse
Can't get S-OFF have tried and tried, think it's cos my H-BOOT is 1.56

When I try sideloading this is what I get
C:\Users\Nath\Desktop\Fastboot>adb sideload 4.19.401.11.zip
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.

Rumrunner result
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
yES
Type 'Yes' or 'No'
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this w
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (35/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit

simmo0020 said:
Can't get S-OFF have tried and tried, think it's cos my H-BOOT is 1.56
Click to expand...
Click to collapse
There are some known problems with HBoot 1.56 in regards to SOFF.. try Firewater that is known to work
However, me being a noob am not allowed to post external links.. But the link is in this thread.. do let me know if it works..
http://forum.xda-developers.com/showthread.php?t=2633276

shabzbd said:
There are some known problems with HBoot 1.56 in regards to SOFF.. try Firewater that is known to work
However, me being a noob am not allowed to post external links.. But the link is in this thread.. do let me know if it works..
http://forum.xda-developers.com/showthread.php?t=2633276
Click to expand...
Click to collapse
Tried this and just get the whelp this sucks message

Try ADB push instead of sideload, download the 401 gurureset rom, ive used it loads of times, adb push it to your sdcard, then flash it in twrp recovery, select to wipe data and also select stock radio and stock recovery when given the option, once its finished and set up you will be completely stock and get OTA's
adb push (romname).zip /sdcard/ (from within recovery main page)
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Stock ROM version for these types:
modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016

Seanie280672 said:
Try ADB push instead of sideload, download the 401 gurureset rom, ive used it loads of times, adb push it to your sdcard, then flash it in twrp recovery, select to wipe data and also select stock radio and stock recovery when given the option, once its finished and set up you will be completely stock and get OTA's
adb push (romname).zip /sdcard/ (from within recovery main page)
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Stock ROM version for these types:
modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
Click to expand...
Click to collapse
Just keep getting this
C:\Users\Nath\Desktop\htc one>adb push rom.zip /sdcard
cannot stat 'rom.zip': No such file or directory

simmo0020 said:
Just keep getting this
C:\Users\Nath\Desktop\htc one>adb push rom.zip /sdcard
cannot stat 'rom.zip': No such file or directory
Click to expand...
Click to collapse
you do have fastboot and adb on your computer right ?
you must place the rom.zip file in the same folder as adb and fastboot and then open a command window there, when you type the file name of the zip, it must be exactly the same as the zip file itself, capital letters, lower case etc.
you are also missing another forward slash from the end of your command /sdcard/

Are you root at the moment? This is what i found.. from another thread.. check out this post..
http://forum.xda-developers.com/showpost.php?p=52431720&postcount=10

Seanie280672 said:
you do have fastboot and adb on your computer right ?
you must place the rom.zip file in the same folder as adb and fastboot and then open a command window there, when you type the file name of the zip, it must be exactly the same as the zip file itself, capital letters, lower case etc.
you are also missing another forward slash from the end of your command /sdcard/
Click to expand...
Click to collapse
Ok so a little progress made, I managed to flash the guru reset stock ROM but I still only have EDGE.
Also I notice I am missing a main version. cpId and microp??
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.21.3263.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: SH3BRW902127
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 3813mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-4dab9d12
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.047s

those were missing from your other output too, but nothing to worry about, mine is missing too, do you get OTA's now ? whith each OTA you should get a radio update too.
when you flashed the guru reset, did you select to install stock recovery and stock radio, did you also select to wipe data ?

Seanie280672 said:
those were missing from your other output too, but nothing to worry about, mine is missing too, do you get OTA's now ? whith each OTA you should get a radio update too.
when you flashed the guru reset, did you select to install stock recovery and stock radio, did you also select to wipe data ?
Click to expand...
Click to collapse
Yeah OTA's are available, is it worth updating?

yes definitely give it a try, download over wifi only not mobile network.
---------- Post added at 01:20 PM ---------- Previous post was at 01:18 PM ----------
Also I forgot to mention, check your APN setting regarding your mobile data being edge only, they could be wrong.

Seanie280672 said:
those were missing from your other output too, but nothing to worry about, mine is missing too, do you get OTA's now ? whith each OTA you should get a radio update too.
when you flashed the guru reset, did you select to install stock recovery and stock radio, did you also select to wipe data ?
Click to expand...
Click to collapse
Yeah I did.
I'm downloading the system update now.
This whole EDGE issue has me super confused.
When I go in to the city I am getting LTE no worries but near where I live I am only getting EDGE even though others around me are getting HSPA, so I know the phone is capable of it so it surely can't be a hardware issue?

simmo0020 said:
Yeah I did.
I'm downloading the system update now.
This whole EDGE issue has me super confused.
When I go in to the city I am getting LTE no worries but near where I live I am only getting EDGE even though others around me are getting HSPA, so I know the phone is capable of it so it surely can't be a hardware issue?
Click to expand...
Click to collapse
Others ? same phone same network ?

simmo0020 said:
When I try sideloading this is what I get
C:\Users\Nath\Desktop\Fastboot>adb sideload 4.19.401.11.zip
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
Click to expand...
Click to collapse
Just FYI, if you want to adb sideload in the future:
You need at least ADB version 1.0.29 to use sideload, yours is outdated, (1.0.26) and the "adb sideload" command was not implemented yet in this version. Most up-to-date version of ADB is 1.0.31

Seanie280672 said:
those were missing from your other output too, but nothing to worry about, mine is missing too, do you get OTA's now ? whith each OTA you should get a radio update too.
when you flashed the guru reset, did you select to install stock recovery and stock radio, did you also select to wipe data ?
Click to expand...
Click to collapse
Seanie280672 said:
Others ? same phone same network ?
Click to expand...
Click to collapse
Different phones same network but here is the weird bit, the only network I seem to be able to use a sim card on effectively out here is Rogers, any others I can't get signal with.
My friends are using a variety of phones on different networks and all have HSPA, Rogers, Telus and Virgin, anytime I try to use a Telus or Virgin sim around here I get nothing, at least with Rogers I get EDGE, in town I had HSPA with Telus and LTE with Rogers.

Still struggling with Data even after going back to sock, in fact really struggling for a signal completely.
Please help!

I messed up pretty bad....

Hey guys I just tried to root my phone and after a few failed attempts I tried to return it to its original condition. Now I have no OS, when powering up it goes on to the HTC logo then nothing. I can access the bootloader and TWRP but that is all.
I have a HTC One M7 running on 4.4.3 with a Vodafone UK contract, any ideas on how to fix this?

rossrfc95 said:
Hey guys I just tried to root my phone and after a few failed attempts I tried to return it to its original condition. Now I have no OS, when powering up it goes on to the HTC logo then nothing. I can access the bootloader and TWRP but that is all.
I have a HTC One M7 running on 4.4.3 with a Vodafone UK contract, any ideas on how to fix this?
Click to expand...
Click to collapse
Sounds like you just need to push a Rom to the phone, please can you connect fastboot usb in the bootloader, then in the fastboot command line type
Code:
fastboot getvar all
And post the out put here, please edit out your serial no. And imei no. Before posting.
Also please confirm which version of twrp you have currently.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Sounds like you just need to push a Rom to the phone, please can you connect fastboot usb in the bootloader, then in the fastboot command line type
Code:
fastboot getvar all
And post the out put here, please edit out your serial no. And imei no. Before posting.
Also please confirm which version of twrp you have currently.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(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: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3766mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Also it wont let me into TWRP now. but it was the latest version.

rossrfc95 said:
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(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: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3766mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Also it wont let me into TWRP now. but it was the latest version.
Click to expand...
Click to collapse
Have you relocked the bootloader? Custom recovery won't boot with a relocked bootloader.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Have you relocked the bootloader? Custom recovery won't boot with a relocked bootloader.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Bootloader is still unlocked

rossrfc95 said:
Bootloader is still unlocked
Click to expand...
Click to collapse
What happens when you try to boot twrp? Have you tried
Code:
fastboot erase cache
It's probably better to flash 2.6.3.3 for now anyway so flash 2.6.3.3 then fastboot erase cache and try boot into twrp.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
What happens when you try to boot twrp? Have you tried
Code:
fastboot erase cache
It's probably better to flash 2.6.3.3 for now anyway so flash 2.6.3.3 then fastboot erase cache and try boot into twrp.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Code:
C:\Users\Ross\Desktop\OneDrivers_Fastboo
ecovery-twrp-2.6.3.3-m7.img
target reported max download size of 151
sending 'recovery' (9184 KB)...
OKAY [ 1.192s]
writing 'recovery'...
OKAY [ 0.855s]
finished. total time: 2.055s
C:\Users\Ross\Desktop\OneDrivers_Fastboo
******** Did you mean to fastboot format
erasing 'cache'...
OKAY [ 0.391s]
finished. total time: 0.393s
I can boot into TWRP now.

rossrfc95 said:
Code:
C:\Users\Ross\Desktop\OneDrivers_Fastboo
ecovery-twrp-2.6.3.3-m7.img
target reported max download size of 151
sending 'recovery' (9184 KB)...
OKAY [ 1.192s]
writing 'recovery'...
OKAY [ 0.855s]
finished. total time: 2.055s
C:\Users\Ross\Desktop\OneDrivers_Fastboo
******** Did you mean to fastboot format
erasing 'cache'...
OKAY [ 0.391s]
finished. total time: 0.393s
I can boot into TWRP now.
Click to expand...
Click to collapse
Ok download this Rom. http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
Rename the file to rom.zip and put it in your fastboot folder.
Boot the phone to twrp (just on the twrp home screen is fine) connect usb and in the command terminal type
Code:
adb devices
To check adb is working.
Code:
adb push rom.zip /sdcard
the command window will appear unresponsive until the push completes. Once it done Install the Rom with TWRP.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Ok download this Rom.
Rename the file to rom.zip and put it in your fastboot folder.
Boot the phone to twrp (just on the twrp home screen is fine) connect usb and in the command terminal type
Code:
adb devices
To check adb is working.
Code:
adb push rom.zip /sdcard
the command window will appear unresponsive until the push completes. Once it done Install the Rom with TWRP.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
after I went into the bootloader i just plugged my htc back into my computer and now my computer wont recognize the device, I have tried a different wire.

rossrfc95 said:
after I went into the bootloader i just plugged my htc back into my computer and now my computer wont recognize the device, I have tried a different wire.
Click to expand...
Click to collapse
See Q2 in this faq post to get your drivers working again. http://forum.xda-developers.com/showthread.php?p=52135024
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

got it connected now, results...
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>adb devices
List of devices attached
FA381W901618 recovery
Code:
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>adb push rom.zip /sdcard
cannot stat 'rom.zip': No such file or directory
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>

Solved
U need a ROOTed phone and a cable with USB acces,and then u put a room into usb and u mount USB from ur Phone and from there u install the Room u put it on USB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

BeniHtc said:
U need a ROOTed phone and a cable with USB acces,and then u put a room into usb and u mount USB from ur Phone and from there u install the Room u put it on USB
View attachment 2968014
Click to expand...
Click to collapse
cant i just put one from my computer to my phone?

rossrfc95 said:
cant i just put one from my computer to my phone?
Click to expand...
Click to collapse
Ok so adb is working now, just push the Rom as instructed in my previous post
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 07:11 AM ---------- Previous post was at 06:55 AM ----------
rossrfc95 said:
got it connected now, results...
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>adb devices
List of devices attached
FA381W901618 recovery
Code:
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>adb push rom.zip /sdcard
cannot stat 'rom.zip': No such file or directory
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>
Click to expand...
Click to collapse
Sorry missed this post. Adb is unable to see the file, either it's in the wrong folder or the file name is different to what you typed.
If your sure the file is in the correct folder. And renamed rom.zip.
You have to be careful renaming with file extensions on Windows, it's possible you have a double .zip extension.
Windows appends (automatically adds) file extensions so your rom.zip could be called rom.zip.zip.
Try
Code:
adb push rom.zip.zip /sdcard
or try Removing the .zip from the Rom.zip file name so the name displays only Rom then use the original push command
Code:
adb push rom.zip /sdcard
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Sorry missed this post. Adb is unable to see the file, either it's in the wrong folder or the file name is different to what you typed.
If your sure the file is in the correct folder. And renamed rom.zip.
You have to be careful renaming with file extensions on Windows, it's possible you have a double .zip extension.
Windows appends (automatically adds) file extensions so your rom.zip could be called rom.zip.zip.
Try
Code:
adb push rom.zip.zip /sdcard
or try Removing the .zip from the Rom.zip file name so the name displays only Rom then use the original push command
Code:
adb push rom.zip /sdcard
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Tried that, the only thing thats done anything for me was
Code:
adb push rom.zip /sdcard /rom.zip
Results-
Code:
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot> adb push rom.zip /sdcard /ro
m.zip
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\Ross\Desktop\OneDrivers_Fastboot\Fastboot>

got it working after playing around for a little while today, thanks for your help Danny201281.

Need help with my m7 (my phone is acting weird)

I flashed ARHD 93 on my M7. Everything was successful. Until I noticed my Virtual SD disappeared. It was their since 20gb was still being occupied, but was showing empty on my computer and the file explorer on my M7 . However I couldn't access it. I was not able to take any pictures, save pictures, or download music. I would get error message saying "unable to save file to sd due to insufficient file permission"
Since than I wiped my SD/internal memory and wiped everything else and than Adb sideload ARHD 93. This made it worse.
Now not only the previous problem still exist. Now I have a black background, My notification bar disappeared. My home button no longer functions. My virtual SD is gone. I can't transfer files over. My Computer gives me an error when I try. I have dont have a lock screen. I keep getting this pop up saying "Unfortunately, System UI has stopped." and my phone is extremely slow. Please help.
I even regret upgrading my rom now. Cause this all started from upgrading from ARHD 92 to 93.
PLEASE HELP, someone!

zainkool said:
I flashed ARHD 93 on my M7. Everything was successful. Until I noticed my Virtual SD disappeared. It was their since 20gb was still being occupied, but was showing empty on my computer and the file explorer on my M7 . However I couldn't access it. I was not able to take any pictures, save pictures, or download music. I would get error message saying "unable to save file to sd due to insufficient file permission"
Since than I wiped my SD/internal memory and wiped everything else and than Adb sideload ARHD 93. This made it worse.
Now not only the previous problem still exist. Now I have a black background, My notification bar disappeared. My home button no longer functions. My virtual SD is gone. I can't transfer files over. My Computer gives me an error when I try. I have dont have a lock screen. I keep getting this pop up saying "Unfortunately, System UI has stopped." and my phone is extremely slow. Please help.
I even regret upgrading my rom now. Cause this all started from upgrading from ARHD 92 to 93.
PLEASE HELP, someone!
Click to expand...
Click to collapse
What is your version-main number? Post the output of "fastboot getvar all" (hide your imei and serialno)
the sdcard access issue can normally be solved with the restorecon command:
Code:
adb shell
su
restorecon -FR /data/media/0
exit
adb reboot

alray said:
What is your version-main number? Post the output of "fastboot getvar all" (hide your imei and serialno)
the sdcard access issue can normally be solved with the restorecon command:
Code:
adb shell
su
restorecon -FR /data/media/0
exit
adb reboot
Click to expand...
Click to collapse
I'm at work at the moment. I'll post it when i get home, since my home computer has adb drivers installed, unless their is another way to get the info your asking?

alray said:
What is your version-main number? Post the output of "fastboot getvar all" (hide your imei and serialno)
the sdcard access issue can normally be solved with the restorecon command:
Code:
adb shell
su
restorecon -FR /data/media/0
exit
adb reboot
Click to expand...
Click to collapse
The fastboot getvar all command isn't working for me. But i can provide this info from the bootloader screen.
I do have have t mobile m7.
M7_UL PVT SHIP S-On RH
HBOOT-1.56.0000
Radio-4A.24.3263.09
OpenDsP-V.32.120.274.0909
OS-
eMMC-boot 2048MB
Does this help or am I missing something?

zainkool said:
I flashed ARHD 93 on my M7. Everything was successful. Until I noticed my Virtual SD disappeared. It was their since 20gb was still being occupied, but was showing empty on my computer and the file explorer on my M7 . However I couldn't access it. I was not able to take any pictures, save pictures, or download music. I would get error message saying "unable to save file to sd due to insufficient file permission"
Since than I wiped my SD/internal memory and wiped everything else and than Adb sideload ARHD 93. This made it worse.
Now not only the previous problem still exist. Now I have a black background, My notification bar disappeared. My home button no longer functions. My virtual SD is gone. I can't transfer files over. My Computer gives me an error when I try. I have dont have a lock screen. I keep getting this pop up saying "Unfortunately, System UI has stopped." and my phone is extremely slow. Please help.
I even regret upgrading my rom now. Cause this all started from upgrading from ARHD 92 to 93.
PLEASE HELP, someone!
Click to expand...
Click to collapse
Maybe try to change file system of data in recovery and return to stock file system. In TWRP : WIPE-Advanced Wipe- check Data- Repair or Change File System- Change File System- for example to EXT2 - at the finish change to EXT4.

zainkool said:
The fastboot getvar all command isn't working for me. But i can provide this info from the bootloader screen.
I do have have t mobile m7.
M7_UL PVT SHIP S-On RH
HBOOT-1.56.0000
Radio-4A.24.3263.09
OpenDsP-V.32.120.274.0909
OS-
eMMC-boot 2048MB
Does this help or am I missing something?
Click to expand...
Click to collapse
Fix your fastboot problem, you will need fastboot connectivity eventually. These info doesn't really help, the only thing I can tell you, based on your hboot version, is that you are running an old firmware on your phone and that could be an issue with arhd 93. Did the restorecon commands worked or not?

alray said:
Fix your fastboot problem, you will need fastboot connectivity eventually. These info doesn't really help, the only thing I can tell you, based on your hboot version, is that you are running an old firmware on your phone and that could be an issue with arhd 93. Did the restorecon commands worked or not?
Click to expand...
Click to collapse
Restore con didnt work. I did get getvar all to work
This is my result.
C:\android-sdk\platform-tools>adb devices
List of devices attached
FA39JW904307 recovery
C:\android-sdk\platform-tools>adb shell
~ # ←[6nsu
/sbin/sh: su: not found
~ # ←[6nrestpr←[←[←[←[J
/sbin/sh: res: not found
~ # ←[6nexit
C:\android-sdk\platform-tools>adb shell
~ # ←[6nsu
/sbin/sh: su: not found
~ # ←[6nrestorecon -FR /data/media/0
unknown option -- F
usage: restorecon [-nrRv] pathname...
~ # ←[6nexit
C:\android-sdk\platform-tools>adb reboot bootloader
C:\android-sdk\platform-tools>fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(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
all: Done!
finished. total time: 0.094s

alray said:
Fix your fastboot problem, you will need fastboot connectivity eventually. These info doesn't really help, the only thing I can tell you, based on your hboot version, is that you are running an old firmware on your phone and that could be an issue with arhd 93. Did the restorecon commands worked or not?
Click to expand...
Click to collapse
I flashed a new firmware and now my phone is bricked. I cant flash a new recovery or I may be doing it wrong
This is what I flashed. This is what I flashed.
http://forum.xda-developers.com/showthread.php?t=2355814
Quote:
OTA 4.19.531.10 - T-Mobile USA
Quote:
modelid: PN0713000
cidnum: T-MOB010
Download:
tmo_fw_4.19.531.10
Quote:
Whats included:
Quote:
boot.img
Hboot
radio.img (4A.24.3263.09_10.38r.1157.04L)
rcdata.img
recovery.img
rpm.img
sbl1-1.img
sbl1-2.img
sbl1-3.img
sbl2.img
sbl3.img
tp_HMX852XD.img
tz.img

zainkool said:
I flashed a new firmware and now my phone is bricked. I cant flash a new recovery or I may be doing it wrong
This is what I flashed. This is what I flashed.
http://forum.xda-developers.com/showthread.php?t=2355814
Quote:
OTA 4.19.531.10 - T-Mobile USA
Quote:
modelid: PN0713000
cidnum: T-MOB010
Download:
tmo_fw_4.19.531.10
Quote:
Whats included:
Quote:
boot.img
Hboot
radio.img (4A.24.3263.09_10.38r.1157.04L)
rcdata.img
recovery.img
rpm.img
sbl1-1.img
sbl1-2.img
sbl1-3.img
sbl2.img
sbl3.img
tp_HMX852XD.img
tz.img
Click to expand...
Click to collapse
I guess you didn't read that big red warning....
IF YOU ARE S-ON LEAVE NOW! This thread is intended for S-Off users that need to return to stock. It is not a general update/upgrade thread. Do not attempt to flash while S-On! Thanks for Understanding.
Click to expand...
Click to collapse
Now try to flash the 6.10.331.9 RUU to unbrick your phone, then take all the ota update until you are running the latest version, unlock bootloader, flash twrp and finally flash arhd.
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/

alray said:
I guess you didn't read that big red warning....
Now try to flash the 6.10.331.9 RUU to unbrick your phone, then take all the ota update until you are running the latest version, unlock bootloader, flash twrp and finally flash arhd.
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
Click to expand...
Click to collapse
I got it to work. After the flash. I unlocked my bootloader, flashed a recovery, and than ARHD 93 Rom. It normal now. I used the official OTA firmware, not the custom one that requires S-off. I also gave you something for your troubles.
What is the lastest firmware out BTW? I had a hard time to find it.
Thanks a lot man. Really appreciate all the help.

zainkool said:
I got it to work. After the flash. I unlocked my bootloader, flashed a recovery, and than ARHD 93 Rom. It normal now.
Thanks a lot man. Really appreciate all the help.
Click to expand...
Click to collapse
I used the official OTA firmware, not the custom one that requires S-off. I also gave you something for your troubles.