Problems updating to 2.29.405.2 - Desire General

Hello all,
I tried to update to 2.29.405.2.
My Desire is rooted with 2.10.405.2 ROM (the original one).
I downloaded the update by manually checking for an update(via Wifi), ran it, and when the mobile rebooted I got this:
{
"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"
}
I clicked the power button and got the recovery menu and beneath that it said:
Code:
ClockworkMod Recovery v.2.5.0.7
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify the whole-file signature
E:signature verification failed
Installation aborted.
What should I do?
PS: This is the first update I am installing..I 'm new to anroid systems.
Thank you for your time!

If you update a rooted ROM there is a good chance you will end up with problems such as boot loop.
Signature verification failed because you are trying to apply an update to a modified ROM. You can turn it off and apply it but it's not recommended as said already.

Then what should I do?

pspuser007 said:
Then what should I do?
Click to expand...
Click to collapse
Update using Gold Card, but first use search button

or...
just get the RUU from shipped roms and run that...

First you would not lose much from not updating to 2.29, the only thing that is worth it is for the new radio, but if you are okay now, I don't think there is any reason to update.
If you want to do it, nevertheless, you should first unroot.
If your original ROM was 2.10.405.2 ,in other words, if you are not branded then you would not need to use a goldcard.

I just read you reply, 3722.
Well, I am thinking about it because of these:
http://forum.xda-developers.com/showpost.php?p=9808553&postcount=15
What should I do?
*Thank you all for the replies!

First tell us whether you are branded.
If you are you couldn't flash 2.10.405.2 version without a goldcard, and you said that you are on that version with root.
So either you have already made a goldcard or you are not branded.

i think 2.10.405.2 is an unbranded WWE rom.
the link to download 2.29.405.2 is below:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
all you need to do is download this and after you've put your phone into fastbootand connected it to your PC , run the .exe.
this will get you to 2.29.405.2 but your phone will be unrooted and wiped so your contacts / apps etc. should be backed up.
you can then root again if needed.
HTH

just confirmation - 2.10.405.2 is unbranded

I am unbranded because I haven't used a goldcard to root my desire.
I 've downloaded the RUU.
Ran it, and when I got the screen that informs me about the progress and at the phone I got a black screen with silver HTC letters.
The RUU progress bar windows closed and gave me a message about checking that the phone is connected to the USB.
I disconnected the USB and saw the fastboot screen with only option RUU.
Plugged the usb cord again, and got the black screen with silver HTC letters.
Nothing happened.
So I closed the RUU.
Now what should I do with the device?
Turn off by removing the battery?

ok, can you put your phone into fastboot while not connected to the PC (back & power). you should see fastboot in a red box.
then connect to the PC, this should now change to fastboot USB.
if this is the case, try running the RUU at this point.
oh, and try not to be too hasty unplugging or taking the battery out

I just ran the RUU again and it's upgrading now.
Will reply, If I get any problems!
Thanks a lot mikep and all the other members that replied!

no problem, it will probs take approx 10 mins.
i hope you've got your contacts/apps backed up?
if you've used titanium, you will have to root again to gain access to them (Unrevoked).
hope it goes well - let us know

It went smoothly
I 've backed up with Titanium.
I have to re-root.
Will do it after I return home (in 3 hours).
Will reply here if anything occurs!
Thanks a lot again!

Happy Days!!!

Everything OK! I rooted & restored the backup.

Good stuff! Make sure you make another nand backup now you're on the newer rom so you have one to fall back to
Sent from my HTC Desire using XDA App

When you say another nand backup?
What is this "nand backup"? :-S (sorry I don't know much)
You mean backing up my whole system+data so that I can restore them if I try a custom ROM that I don't like?

Yep, correct.
Make a backup thru the clockworkmod recovery or thru rom manager.
You will then always be able to get back to the position you're at now.
Hope this makes sense
Sent from my HTC Desire using XDA App

Related

Superuser disabled by default???

So my old g2 broke and I just got a new one. I rooted with the non-adb method. Now I've flashed miui and I'm getting the following error. See photo. I'm unable to use root required stuff and can't get into recovery. I can get into hboot however. Please help!
{
"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"
}
Sent from my HTC Desire Z using XDA App
Do you have the superuser app in your launcher? have you actually opened it and given rights to things?
Well, I've installed superuser, opened it. It has app list, log list, which are both empty and a settings page. I opened the settings page to see if there was something to enable permissions, there wasn't. I've decided to go into hboot, do a factory reset. It took me into recovery and I wiped data/cache/dalvik. I tried installing a new rom, got an error status 1. Did some research, they said to run a scandisk, I did, it didn't change anything. So now I'm trying to root again using the ADB method since I don't have a rom on my phone and it fails to install a new one. So I'm stuck in recovery. ffs. lol. Now I'm having trouble with CMD commands as the guide says to write specific commands, which I write and it says they don't exist. Anyone willing to add me via MSN or yahoo and help me through this? I would GREATLY appreciate it.
I'll elaborate to exactly what I did ---- (My phone came with 2.2 with the option to OTA 2.3.3, I did NOT upgrade to 2.3.3)
Received my phone today in the mail. Loaded it up. Went directly to the non-adb root page here on xda. Downloaded the files, followed the directions exactly. Downloaded clockworkmod, flashed 5.0.2.0 recovery. Downloaded MIUI via clockworkmod. Rebooted my phone into recovery. Wiped data/cache/dalvik. Installed MIUI. Booted into MIUI. Downloaded Titanium backup to recover some files from my old phone(sd card), got that error saying I wasn't rooted. Tried downloading superuser, that didn't fix it. Downloaded busybox, and busybox wouldn't install because it said I wasn't rooted.
Rebooted into recovery, got stuck at white HTC logo screen. Removed battery. Restarted phone into hboot. Clicked factory reset which restarted the phone into recovery. Inside recovery, I wiped data/cache/dalvik again. Tried installing a new rom, got error status 1.
From here, I attempted to root via ADB method. Followed all the steps but HTCsync couldn't connect to my phone. Although it "adb devices" command recognized my phone and most of the adb commands were working (it seemed). I rebooted my phone into recovery after playing on adb for about an hour. I tried reinstalling that new rom and it installed! Well...sort of. Instead of getting an error, it said installed, but it was almost instantaneous. I knew something had fudged up. So I rebooted my phone anyway just to see if it had taken the new rom. It didn't.
I rebooted back into recovery, cleared data/cache/dalvik and reinstalled MIUI successfully. Now I'm in MIUI and it says there's no root. I tried connecting HTCSync via MIUI, it failed. I'm unable to use HTCSync with MIUI? Anyway, now I'm stuck and I have NO idea what to try next. Been at this for a few hours now and can't seem to get anyone to nudge me in the right direction. Thanks for reading.
Does your bootloader screen actually indicate that the phone is S-OFF ? It seems like you didn't complete a full root process and you're stuck half way so to speak.
I thought that's what happened. So what I did was, went ahead and put the stock rom back on my phone. I downloaded the PC10IMG and updated via bootloader. Now I'm back on 2.2. I can't get HTCSync to connect so ADB method is out of the question. Some version information, not sure if it's useful to you, but I still want to root my phone, just don't think that method works for me, not sure why.
Android Version: 2.2
Baseband version: 12.22.60.09bU_26---blah blah
Kernel: 2.6.32.17
Build number 1.19.531.1 CL---blah blah
Is that sufficient info for a pro dev to assist me? I've disabled my firewall aswell as windows defender to see if that would allow me to connect through HTCSync, but that didn't help. So now I have to find a new method of rooting my phone..
Problem solved. Started back from stock and tried the same method again but with different recovery. Viola! Success. Thanks anyway.
Sent from my HTC Vision using Tapatalk

incredible 2 / revone freeze

Hi all, love this forum, much much much to learn from this place
Ok, long story short, rooted dinc 2 from htcdev, following steps from this guy but got no further then that cuz the s-on...
read around and found a few guides to s-off if I had hboot-0.97.0000 ... problem was I had hboot-0.98.0000, so I found XDA.... yeah
I then followed the steps outlined here to drop back to hboot-0.97.0000 even if I had custom roms etc installed (outlined in the (HSO) section on post #2).
Success, downgraded per the tutorial.
So here is what changed:
downgraded to 0.97.0000 from 0.98.0000
radio went from 1.09.01.0312 to 1.09.01.0622
kernel went from 2.6.35.9-g11de853 to kernel 2.6.35.9-g6760582
[email protected] #1 remained un changed
baseband went from 20.32w.30.0813u_1.09.01.0312 to 20.27w.30.0811u_1.09.01.0622
build# went from 6.04.605.07 cl353602 release-keys to 2.18.605.3 cl79787 release-keys
android vs. went from 2.3.4 to 2.3.3
So next I re tried the steps here for s-off, but every time my phone just freezes, locked up tight, no buttons do anything, this happens at step #4. if it sits for like 15 minutes it eventually reboots itself, otherwise removing the battery is the only option.
Am I missing something, I am new to rooting, so it is very possible, lol
ok, so I read and read until I worked out the s-off issue, I am now s-off
{
"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"
}
now my big problem is No Service.
I searched XDA and Google for the resolution and found the answer is supposed to be the radio img, so I found several img's here.
Since my radio prior to all this was 1.09.01.0312, I chose the one labeled 6.01.605.05 OTA: 1.09.01.0312...
I loaded the file onto my sd after renaming it to PG32IMG.zip, rebooted phone, let it update, reboot the phone, then pulled battery, booted into Clockwork so I could remove the PG32IMG.zip file via usb mount. rebooted completely, still No Service.
Current info after completing Revolution/S-off:
hboot-6.133.1002
radio: 1.09.01.0312
kernel: 2.6.35.9-g6760582
[email protected] #1
baseband: 20.32w.30.0813u_1.09.01.0312
build# 2.18.605.3 cl79787 release-keys
android vs. 2.3.3
Any suggestions on where I should go from here, anyone?
Load a rom of your choosing and activate the phone
Ok, so, I assume I can load, say Cyanogen's 7.2.0 zip file onto my sd card, boot hboot, select recovery to get into clockworks menu & then simply install zip rom sd card?
Just not having the best of luck, modding, lol
Downloaded Cyanogenmod 10.1, placed on sd, installed zip via clockwork mod, rebooted and now I am stuck in a boot loop here, at the Cyanogen animated boot screen, learning a lot, really fast, lol
So I tried and tried installing different mods and even completely re following tutorials from the beginning to resolve my issue with "No Service" after installing the Cyanogenmod 10.1, to get the Radio working. No matter what I tried, no success.
I even called a friend in Florida who works high up in management for another provider, who had me log into the phone and dial ##778 and then check some NAM settings. Even doing this didn't resolve my issues.
Just after I hang up the phone with him, I find a post here for Cyanogenmod 10.1 Borked Radios. Will be trying this after I read and read the post to make sure I follow it to a tee so I do not waste another 20 + hrs walking in circles.
Posts:
First post, Second post, Third post... So then I find this post that says Post 2 - Restoring a non-functioning radio
Did a factory restore from within clockwork after clearing Dalvik & system caches, Have installed stock vzw rom from bottom of this page, but am sort of stuck at this point, as I cannot locate a stock Recovery.img to follow the instructions exactly
ok I a confused, the instructions between the two links don't sound right.
and I did find a signed recovery image, it's inside the stock vzw package I linked...... so I am loading it twice?? that's confusing... could really use another person here and not just me in my own head... tho writing this all down could be therapeutic for some I guess
Making a new post for this issue since the title for this post does not reflect the issues currently.
continuing search for answers in this post here entitled more accordingly to the issue

[Q] Force Restart constantly

I recently restored my phone to stock to take advantage of the latest sprint updates. I had been rooted for years and now just dont see a reason for it as my phon performance had dropped of as development stopped on the custom rom i was running.
I used E4gt-EL29-Restore Odin 1.8 to restore. Initially messaging force closed constantly, then after a day or two it now constantly reboots itself. It indicated that I had a SD card malfunction. I tried to reformat it but that failed. now every 10-15 seconds it reboots until the battery dies. I will not stay on long enough for me to connect and run any thing.
Any help is appreciated!
ForayeEvo4g said:
I recently restored my phone to stock to take advantage of the latest sprint updates. I had been rooted for years and now just dont see a reason for it as my phon performance had dropped of as development stopped on the custom rom i was running.
I used E4gt-EL29-Restore Odin 1.8 to restore. Initially messaging force closed constantly, then after a day or two it now constantly reboots itself. It indicated that I had a SD card malfunction. I tried to reformat it but that failed. now every 10-15 seconds it reboots until the battery dies. I will not stay on long enough for me to connect and run any thing.
Any help is appreciated!
Click to expand...
Click to collapse
You may have a bad flash, a bad download of whatever you are trying to install or a bad battery.
I would think it is the battery but I would try reflashing as well. Verify the download md5 checksum is correct if it is offered to verify the file integrity of the download.
tdunham said:
You may have a bad flash, a bad download of whatever you are trying to install or a bad battery.
I would think it is the battery but I would try reflashing as well. Verify the download md5 checksum is correct if it is offered to verify the file integrity of the download.
Click to expand...
Click to collapse
Thanks for the reply. I'm sure its not the battery.
let me explain some more...I was running OneClick Root for EL29, with Caukin's Rom form circa 2011
- I removed root using the same OneCliclk Restore for EL29, and got the latest GB27 OTA from Sprint.
-All apps and settings were unchanged except Messaging would force close. I stopped using it and installed Handcent
-SD Storage Icon says card is corrupted
-Everything worked for a day or two, then it starts to reboot every 20 seconds...except its looks like it only the splash screen reloading back to the lock screen.
Is there a method to interrupt this cycle? the divice is now UNrooted, and will not stay on long enough to Re-Root or initialize USB.
Thanks
ForayeEvo4g said:
Thanks for the reply. I'm sure its not the battery.
let me explain some more...I was running OneClick Root for EL29, with Caukin's Rom form circa 2011
- I removed root using the same OneCliclk Restore for EL29, and got the latest GB27 OTA from Sprint.
-All apps and settings were unchanged except Messaging would force close. I stopped using it and installed Handcent
-SD Storage Icon says card is corrupted
-Everything worked for a day or two, then it starts to reboot every 20 seconds...except its looks like it only the splash screen reloading back to the lock screen.
Is there a method to interrupt this cycle? the divice is now UNrooted, and will not stay on long enough to Re-Root or initialize USB.
Thanks
Click to expand...
Click to collapse
Pull battery, replace battery, hold Power+Volume Down until it goes into Download Mode then you can do another one click Odin
{
"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"
}
Looks like you're going to have to reinstall gb27 manually through your USB. Just use the one click gb27 rooted restore found here http://www.sxtpdevelopers.com/showthread.php?t=166 and you'll be fine, you'll lose all your data though.

Video and/or step by step firmware upgrade instructions available?

So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.
guyverzero said:
So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.
Click to expand...
Click to collapse
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine
clsA said:
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine
Click to expand...
Click to collapse
Would restoring my nandroid after flashing that RUU cause anything to go wrong?
guyverzero said:
Would restoring my nandroid after flashing that RUU cause anything to go wrong?
Click to expand...
Click to collapse
it's always better to start fresh after the RUU
Nope, it's doing the same thing again. This is my GSam from last night.
Now, let me stress that I did everything clean. RUU, did a clean setup, clean venom flash, etc. I didn't restore any settings. I don't know what to do, as the phone is completely normal under 1.32. Oh and I flash 1.32 in the same exact way I do 2.7 as well, there's no difference
{
"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"
}
Sent from my HTC One M9 using Tapatalk

Potentially bricked? Sprint M9 unable to take OTA

Good evening folks. I am in desperate need of expert advice on this subject.
I imagine that other users have encountered this issue, and this thread may be useful in the future to the assistance of others.
I am rooted, and S-off (as of yesterday). Yesterday, I had TWRP 2.8.7 installed, with stock sense (and sprint bloatware), running android 5.0.1, on firmware 2.11.651.19
*** STILL UNSOLVED*** At first, I was prompted to do a system update (1 of 2), in order to prepare my device for android 6.0. Upon download completion of the first update, and when attempting to install, I am brought back to HBOOT, and the update is nowhere in sight, even when rebooted.
This is a constant loop, and always brings me back to HBOOT.
This is what I have been trying to figure out, and it has got me in an enormous mess ***
*** UNLOCKED ***
htc_himawhl PVT-SOFF
CID-SPCS_001
LK-1.0.0.0000
[email protected]
OpenSDP-15.6.1.00522.8994_1026
OS-3.41.651.4
Feb 3 2013,13:49:48(695981)
Let me describe my problem before I get into detail.
It started when I got my M9, I got it from Sprint, and instantly wanted to root it and install Cyanogenmod 13 on it.
To my mistake, I rooted the phone BEFORE I did the OTA update to Android 6.0
As we know, this is a block based system, and this introduces many difficulties.
I had been running TWRP 2.8.7, and stock sense with all my pre-loaded Sprint crap. I was unable to install cyanogenmod 13 or anything.
This led to much frustration, research, and pain as I browsed countless threads on the XDA forums, downloading many items, hoping they would fix my issue.
Now, for my issues.
The HTC RUU for my phone has never worked, and I was constantly met with ERROR 155. I attempted to re-lock the bootloader, but this made no difference.
Often, when I type in adb devices into the command prompt, I am prompted with something like "you are using a different version than the server... Daemon started.. Then devices: and then nothing. This is what I usually get:
{
"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"
}
It is obvious to me that if no device is detected, then no work may be done on the phone.
Other times, the phone will recognize, but it seems as if there is no effect on what I am trying to do.
Last night, I paid sunshine $25 to S-off my phone, hoping that it would help me. While the S-off process was extremely easy with this service, my problems are not remedied.
I saw that to restore my phone to 100% stock, that I must complete a RUU with my device, renamed to 0PJAIMG.img, and move it to the SD card.
When I did this, I was still running Stock sence, and was able to move files to my SD card/External SD card.
I went into the bootloader and the phone recognized that I had a "0PJAIMG.img" file on my phone, but I used the wrong file. I used a 75mb file with the firmware, but not all of the sprint things with sense installed. I assumed that since this was the latest firmware, it would allow me to keep Sense and my files, and allow me to take the OTA update to the latest android version
Here are images with information to the INCORRECT "0PJAIMG.img" (that I had renamed from this screenshot) I installed on my phone using the bootloader.
You can see the CORRECT file at about 2GB, and the incorrect file at 75mb.
For reference, Here is what is included in the 75mb file.
Now, I am unable to connect my phone to adb, as it shows up as in the pictures.
I have no recovery installed, so the Stock HTC (and very basic) recovery is there.
I am continuously prompted to install the INCORRECT 0PJAIMG.img that I placed on my phone, and I have no way to remove it as I know.
When I boot normally, I see the HTC One logo, and then a black screen. The screen is still on, but completely black. There is no way to exit this, other than pressing all buttons for 5+ seconds.
I do have the correct 0PJAIMG.img (2gb file), but I have no way of switching these two files, since I cannot connect.
I cannot install TWRP due to no devices showing up in the ADB interface.
When I plug my phone into my computer, I do get the "connected" noise from windows.
Please let me know if I can be more specific. I am going on a trip soon, and will take whatever lengths to get my phone working again.
I have read all relevant threads that I know of, so please avoid re-directing me to another page unless you think I have perhaps missed something.
My end-goal is to have a fully functional HTC M9 with Cyanogenmod 13 snapshot installed. I am on sprint, so I am unsure if I can even use Cyanogenmod. My alternative preference would be the D-Boyz mod to sense.
UPDATE:
I am able to install TWRP 2.8.7.1, and play with that. It seems that when restoring from my old backups, I have the same firmware and OS.
Only now, my radio is bricked.
I have attempted to re-create this, after many painstaking "optimizing apps" runs.
I am currently in a "android is starting"... process.
I will keep this thread updated with information as I progress. I hypothesize that my radio will still be broken.
I am absolutley at my wit's end with this device. I should have never upgraded from the HTC M8. I miss you baby.
I am tempted to take my phone back to sprint. I paid for the S-Off though, and would like to avoid this if possible.
All I want is android 6.0 and CG13.... I'm sick of being annoyed by the "system update is available" notification constantly.
*** STILL UNSOLVED*** At first, I was prompted to do a system update (1 of 2), in order to prepare my device for android 6.0. Upon download completion of the first update, and when attempting to install, I am brought back to HBOOT, and the update is nowhere in sight, even when rebooted.
This is a constant loop, and always brings me back to HBOOT.
This is what I have been trying to figure out, and it has got me in an enormous mess ***
Solved by flashing the ZIP of the RUU for the latest version, placing it on the base of the Phone storage, and naming it "0PJAIMG.zip"

Categories

Resources