Problem solved, thanks to craven667 (http://forum.xda-developers.com/showthread.php?t=1542555)
Also I would like to thank malybru, for trying to push me to the right directions. Thanks guys, I really appreciate your help.
Hello, I have no idea whats going on now in my phone, I have HTC Sensation, before I used Android Revolution HD 6.6.x but then I was curious to try CM9, so I just downloaded ROM, performed basic wipe steps, and flashed ROM, everything was fine, but later I decided to go back to ARHD, so this time I downloaded version 6.6.2 XE and Firmware package 3.32.401.x, what I did was, flashed firmwware package, then super wipe, then flashed ARHD, but after reboot I'm on HTC logo bootloop, tried to flash many times, even tried to flash CM9 again, but got the same problem. My bootloader looks like this:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
I also tried few different things from searching forum, but none worked for me so far.
What would be the best solution to get back on Stock or Any other ROMs ?
Thanks.
w0ferz said:
Hello, I have no idea whats going on now in my phone, I have HTC Sensation, before I used Android Revolution HD 6.6.x but then I was curious to try CM9, so I just downloaded ROM, performed basic wipe steps, and flashed ROM, everything was fine, but later I decided to go back to ARHD, so this time I downloaded version 6.6.2 XE and Firmware package 3.32.401.x, what I did was, flashed firmwware package, then super wipe, then flashed ARHD, but after reboot I'm on HTC logo bootloop, tried to flash many times, even tried to flash CM9 again, but got the same problem. My bootloader looks like this:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
I also tried few different things from searching forum, but none worked for me so far.
What would be the best solution to get back on Stock or Any other ROMs ?
Thanks.
Click to expand...
Click to collapse
Hi,
I would download the firmware and ARHD ROM again,check the md5,and re-install.
Probably a bad download.
I tried many times, also I tried different roms (even gingerbread) and still nothing, stuck on HTC logo bootloop, I just have no idea what to do.
P.S Can its be something "fast boot" related ?
Because when its boots up, after plain HTC logo shows up "Quietly Brilliant" for less then a second, and that's it, starts the same loop again.
w0ferz said:
I tried many times, also I tried different roms (even gingerbread) and still nothing, stuck on HTC logo bootloop, I just have no idea what to do.
P.S Can its be something "fast boot" related ?
Because when its boots up, after plain HTC logo shows up "Quietly Brilliant" for less then a second, and that's it, starts the same loop again.
Click to expand...
Click to collapse
Hi,
Gingerbread will not work unless you downgrade the firmware to 1.17 (HERE)
Have you not got a nandroid you could restore?
I did downgrade (did everything as its should be done) but anyway I'm getting bootloop...
I keep trying again and again, but without any success. I'm familiar with flashing custom firmwares, etc. (its my third phone over a year) and never got such problems.. I still have a hope to fix it somehow.
But thanks anyway, I really appreciate your help.
Hi everyone.
I am aware that this problem might have been already solved, but i kept searching those three days about a similar thread or solution on the forum but there was none.
I own a vodafone Htc one S bought days earlier, i did the update from the update menu in the controle panel, but i wanted to see what custom roms were like, so i went throught unlocking bootloader, installing CWM and then flashed some roms posted on the forum, but none of them had the otptions the stock were having (the sound options when ringin and some other stuffs the stock one had), so i decided to take a look a the TrickDroid rom, wich seemed to be perfect for me, assuming it had all the stock options+tweaks to add or remove them, and more ram optimised thank the stock one , so i went trought the process, flashed the boot.img that came with, but got stuck on the htc screen with no other possibility than to flash another Rom, then i came up knowing that to be able to use the TrickDroid rom, i had to be already on the official one, so this is were my problem starts :
I have done all the steps to flash stock rom, assuming relocking bootloader, flashing original recovery and boot, then downloaded the RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.7z Rom, when the installing starts, it keeps giving me the 131 error, client ID.
I looked everywhere for a similar thread or solution, but nothing that could help me.
I checked my boot loader and its giving :
****TAMPERED****
****RELOCKED****
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-1.08es.50.02.21
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
So figured out that i need an RUU that comes with radio 1.08es, but the problem is i checked those 3 days for it, but werent able to find any.
I am stuck with a paranoid rom wich is much less good (for me) than the stock one (but indeed lighter with no operator stuff, but i learned how to get rid of the stock operator apps).
I just wanna go back to the official rom, with sense, or, at least, a custom rom wich have the same capabilities of the stock one, without bugging.
Thanks in advance.
EDIT:Resolved .
2 fixes :
A custom rom that is stock : http://forum.xda-developers.com/showthread.php?t=1970131
Debrand device : http://forum.xda-developers.com/showthread.php?t=1674202.
Hello, thanks for your time to read in advance.
Background
I've had my first smartphone (HTC Desire HD) for about 3 year and decided it was getting old and slow even though it had Cyanogemod 7.2 successfully loaded on it. So recently I bought a new one online for about $150 from China. Looks identical, weighs the same however there are very small details that still make me doubt its authenticity. I'm 90% sure its legit even though the IMEI is fine. I ran the new one through the same process (AAHK) I did with the old one to install Cyanogenmod.
The HBOOT details:
ACE PVT ENG S-OFF RL
HBOOT - 0.85.2425
MICROP - 0438
RADIO - 26.03.02.26_M
eMMC - boot
Apr 12 2011,00:55:45
NO ROM LOADED
NO RECOVERY IMAGE (TeamWin originally)
The problem
Right now, this phone may be bricked (completely dead?), I am hoping its not. I have no ROM loaded on it so I cannot enable USB Debugging and now there is no recovery image either. When I am in HBOOT menu, I select the recovery option, phone does a reboot and shows this:
http://imgur.com/YsCGTSQ
What I did to break it
Initially I had CM 11 loaded and after a while it started to show errors. So I decided to go back and install CM 7.2 the more stable option.
Once I did this, the CM 7.2 ROM now somehow in the process of being loaded copied all the additional apps I had installed on the CM 11 ROM with it. Now I had CM 7.2 with apps that I should have manually had to install.
I tried several times to clear the cache and Dalvik cache through the TeamWin recovery. Then tried to reload CM 7.2. Same problem.
I then ran phone through AAHK (http://forum.xda-developers.com/showthread.php?t=2367322) again which I believe fried my phone. Or I could have also done a factory reset then ran the AAHK. Not exactly sure, it was a while ago when I was doing then.
What can I do to fix the phone?
Anyone with the time and patience please help. If you need any clarifications ask away.
TIA
ant-onov
Hope you all can help me. I am having issues getting GPS to work on my phone. I am rooted and S-OFF. I will give you everything that I have done thus far to fix the issue with no luck. This (to the best of my knowledge) all started after the move to 4.4.3
First I tried to use FasterFix with no luck.
Next I fount this thread here which messed with the gps.conf and gps.conf_default in system/etc with no luck
Next I put a stock image back on my SD Card (0P6BIMG.zip) and let the bootloader load it and reset to stock 4.4.2, took the OTA to 4.4.3 and still could not get GPS to work (I do not know if GPS worked before taking the OTA as I didnt move locations).
I am running this ROM (have not updated to the current update dated 10/23/2014).
Here is what my Bootloader is telling me:
Code:
M8_WLV PVT SHIP S-OFF
CID-VZW__01
HBOOT-3.18.0.0000
RADIO-1.09.20.0702
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 7 2014, 20:26:27.0
Please let me know if you need any more information and thanks!
-Nick
Same
I am having the same problem. Did you find a solution yet?
Also having the same issue. Running bone stock 4.4.4. Factory reset and it's taking sooooo long to get GPS lock. GPS Test sees 22 right now. I have had the app open for maybe 20 minutes and it still can't get a lock.
It seems like I've fixed my update issue, so I wanted to post this for other people's benefit.
As described here: http://forum.xda-developers.com/verizon-htc-one-m8/help/update-issues-cyanogenmod-t3127489
I had an issue updating to newer versions of CyanogenMod and gapps. My phone radio (the LTE indicator) would not work. It kept acting like it was endlessly searching for a signal or stopping and starting. After Googling and re-Googling and re-Googling with every different combination of relevant search terms I could think of, I found a thread that suggested upgrading the radio version.
I found a link for newer firmware here: http://forum.xda-developers.com/showthread.php?t=2723159
I downloaded that file, renamed it to OP6BIMG.zip, put it in the root of my external SD card, rebooted into HBOOT, and the phone automatically detected the file, and prompted me to update.
Here are my versions before the update:
M8_WLV PVT SHIP S-OFF
HBOOT-3.19.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.0.0-00542-M8974.0311
OS-4.17.605.5
eMMC-boot 2048MB
Feb 3 2015,21:50:28.0
Here are my versions after the update:
M8_WLV PVT SHIP S-OFF
HBOOT-3.19.0.0000
RADIO-1.12.20.1211
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-4.17.605.5
eMMC-boot 2048MB
Feb 3 2015,21:50:28.0
Then I did a factory reset, flashed the new CyanogenMod, rebooted to let that do it's thing, went back to recovery mode and installed the new gapps.
Looks like everything is fine now.