The basic problem I have is that the software won't apply to my phone correctly.
Software number: 1.02.605.6. Should show 2.01.605.11
Any help would be awesome.
Here is more information that I think could be useful. Please request any additional information or clarification.
I delocked, then I ran the new RUU, then unlocked it back up. I got to the point of basically having everything stock, and it showed the new 2.01.605.11 software number, but obviously I wanted everything back, so I flashed my nand backup using amon ra. I must have missed something because I'm basically back to the same spot I used to be which was that the update would randomly shut my phone down and end on this error "E:Error in /cache/fumo/OTAPkg.zip" in the recovery screen and i'd have to battery pull to make things restart..
I'm not sure if it's different now, but my baseband version shows:
0.95.00.1118r, 0.95.00.1223r
i know the first one is the new baseband. I do not have the 5 signal bars though, although I did when everything was stock for a minute before i started messing with things again.
ON the bootloader screen it shows hboot v2.11
So I think i'm really close just missing something. Is it not cool to just flash my old recovery file that i made before starting this stuff? Did I include too much information when I created it(check too many boxes).. I'm not even sure how to ask this question to be honest.
When I try to do the update itself at this point, it will download and start to apply, and then give me the same error like this one.
'E:Error in /cache/fumo/OTAPkg.zip'
Since doing everything I currently cannot use wifi, it shows "error" in the settings menu which I know is similiar to other errors people have gotten.
I would greatly appreciate any help and explanation!
Have you tried relocking your phone and doing a factory reset via the bootloader? The OTA will pop up once factory reset. This is how to applied the OTA with ease, hope this helps!
I actually did a factory reset before any of this. I should have included that in the OP. Honestly I think it was still locked when I factory reset, but I know it worked in some form because I no longer had amon-ra recovery. I'm like right on the verge of understanding all this kernal stuff on another level but obviously not there yet since I can't figure this OTA out.
So you were rooted debloated but otherwise stock, and you just relocked *which means its still rooted right?* and then factory reset, then the update will apply.. then you unlock it again.. and then you can flash back to your debloated nand backup?
Maybe i'm not understanding flash and recover.. can i not use those interchangeably?
Could my problem be that I did the factory reset before locking it back up? I thought with some methods factory reset wasn't necessary (RUU resets things regardless)..
I believe I relocked, did a factory reset, then once stock rom loaded up I downloaded and installed update. After installing the OTA was when I unlocked again, thats odd I believe once re-locked you lose root access and doing a factory reset will grant you stock unrooted rom. Try deleting the OTA zip from the sd card and redownload. The wifi not working means you had a kernel installed, reinstall stock kernel from NilsP thread and make sure to use Scott's flash tool to flash the boot.img from the kernel. You can get the boot.img from kernel in the PH98IMG.zip which resides in the kernel folder.
You might as well run the RUU for 2.01.605.11. It is the update and will probably fix everything for you. It will get you back to stock, you will just have to unlock the phone after you run the RUU and then reinstall Amon Ra to get root back.
thurst0n said:
I delocked, then I ran the new RUU
Click to expand...
Click to collapse
I've already run the new RUU.
And then you did a restore of a nandroid. Your mainver is now updated and your are trying to run an older mainver, probably why you are having so many issues. Rerun the RUU and act like it is a brand new phone that you just picked up. if you want to run a rom, install from scratch.
richii0207 said:
I believe I relocked, did a factory reset, then once stock rom loaded up I downloaded and installed update. After installing the OTA was when I unlocked again, thats odd I believe once re-locked you lose root access and doing a factory reset will grant you stock unrooted rom. Try deleting the OTA zip from the sd card and redownload. The wifi not working means you had a kernel installed, reinstall stock kernel from NilsP thread and make sure to use Scott's flash tool to flash the boot.img from the kernel. You can get the boot.img from kernel in the PH98IMG.zip which resides in the kernel folder.
Click to expand...
Click to collapse
Ok Im going to sort of "Start over soon" if I can't finnegal a way here shortly.
But I swear it showed 'relocked' in bootloader, and i was still rooted. Relocking it forces everything back to stock, but it sitll shows the updated radio, and hboot2.11
I really don't think I ever flashed a kernal unless you count amon-ra as being a kernal. Again i'm new to this and some of the terminology confuses, me so explanation to the steps helps too.
EmerikL said:
And then you did a restore of a nandroid. Your mainver is now updated and your are trying to run an older mainver, probably why you are having so many issues. Rerun the RUU and act like it is a brand new phone that you just picked up. if you want to run a rom, install from scratch.
Click to expand...
Click to collapse
Ok so basically you're saying I can't have my cake and eat it too? I will have to reset my phone up with apps and settings etc.. I don't use a ROM, I just froze and uninstalled many many things, and installed other things etc..
Is the 'E:Error in /cache/fumo/OTAPkg.zip' caused by the mainver discrepency?
I was trying to prevent starting from scratch, but I suppose backing up from my nandroid is essentially flashing a rom.. right?
Would it possible to achieve my old setup using TI as opposed to amon-ra recovery?
thurst0n said:
Ok so basically you're saying I can't have my cake and eat it too? I will have to reset my phone up with apps and settings etc.. I don't use a ROM, I just froze and uninstalled many many things, and installed other things etc..
Is the 'E:Error in /cache/fumo/OTAPkg.zip' caused by the mainver discrepency?
I was trying to prevent starting from scratch, but I suppose backing up from my nandroid is essentially flashing a rom.. right?
Would it possible to achieve my old setup using TI as opposed to amon-ra recovery?
Click to expand...
Click to collapse
I restored a nand I made before the OTA after I accepted the OTA so it can be done. I wasn't having any issues, certainly not the one you are having. My software says 1.02.605.6 since flashing the older ROM but I still show the new radios listed in baseband, and I'm not getting that error. My mainver is at 2.x. You can check what mainver your phone is on in fastboot using the following command:
fastboot getvar all
But that error is not really a mainver error, at least not like the ones that have been happening. That file you mentioned the error about is the OTA update and your phone seems to be trying to run it or something. I think what is happening is that you are restoring your nand cache and there's a trace of the OTA in there so your phone wants to run the OTA. I would bet that if you delete the OTAPkg.zip file you'll be fine. Either it's there and your phone is trying to run it or your phone thinks it's there and it's not. You might want to look in settings and see what it says about having an update.
Also, wipe your cache and dalvik cache in recovery and see if that fixes it. Especially if that OTA file isn't there, then it must be something else in your cache that wants to run the update.
If that doesn't work, then RUU again and then try restoring your nand without the cache checked. Or if you made a nand right after the RUU restore that. If you didn't, make one after you get RUU and rooted in case you need to revert back. I'm kicking myself cuz I was so excited to get my phone back how I wanted it I forgot to make one myself after I RUU'd today and of course I didn't realize it until right after I confirmed I wanted to flash the custom ROM.
feralicious said:
I restored a nand I made before the OTA after I accepted the OTA so it can be done. I wasn't having any issues, certainly not the one you are having. My software says 1.02.605.6 since flashing the older ROM but I still show the new radios listed in baseband, and I'm not getting that error. My mainver is at 2.x. You can check what mainver your phone is on in fastboot using the following command:
fastboot getvar all
But that error is not really a mainver error, at least not like the ones that have been happening. That file you mentioned the error about is the OTA update and your phone seems to be trying to run it or something. I think what is happening is that you are restoring your nand cache and there's a trace of the OTA in there so your phone wants to run the OTA. I would bet that if you delete the OTAPkg.zip file you'll be fine. Either it's there and your phone is trying to run it or your phone thinks it's there and it's not. You might want to look in settings and see what it says about having an update.
Also, wipe your cache and dalvik cache in recovery and see if that fixes it. Especially if that OTA file isn't there, then it must be something else in your cache that wants to run the update.
If that doesn't work, then RUU again and then try restoring your nand without the cache checked. Or if you made a nand right after the RUU restore that. If you didn't, make one after you get RUU and rooted in case you need to revert back. I'm kicking myself cuz I was so excited to get my phone back how I wanted it I forgot to make one myself after I RUU'd today and of course I didn't realize it until right after I confirmed I wanted to flash the custom ROM.
Click to expand...
Click to collapse
Getvar All shows this
Code:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.11.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.01.605.11
(bootloader) serialno: 000000
(bootloader) imei: 000000000
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bc948b45
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I need to go to work now, but I appreciate everyones help in this! I must be looking in the wrong spot or it's not there, cuse the OTApkg.zip i cannot find at the moment, i swear i've downloaded it like 20 times over the past 2 weeks haha
feralicious said:
I restored a nand I made before the OTA after I accepted the OTA so it can be done.
Click to expand...
Click to collapse
Same here.
thurst0n said:
Getvar All shows this
Code:
< waiting for device >
(bootloader) version-bootloader: 2.11.0000
(bootloader) version-main: 2.01.605.11
I need to go to work now, but I appreciate everyones help in this! I must be looking in the wrong spot or it's not there, cuse the OTApkg.zip i cannot find at the moment, i swear i've downloaded it like 20 times over the past 2 weeks haha
Click to expand...
Click to collapse
First of all, I would edit your post and delete your serial number and imei as I believe that is sensitive info.
So you are updated based on what you posted, did you check your baseband in settings? That will confirm your radio update. I would try wiping your cache and dalvik cache in recovery. I do think there's some trace of that update and your phone is trying to update but that file isn't there so it errors out.
After you wipe power down, pull battery and then reboot. Hopefully that fixes it.
Then go into settings and see if it shows any updates available for you.
Sent from my ADR6425LVW using Tapatalk
Related
Sorry for long post but I've tried to provide a sufficient level of detail. If the answer is in another thread let me know. I've read quite a few of them now!
I've had my flyer for a short time and was loving it until I tried to mod it.
I installed CWM and Superuser root and had it "S-Off". I tried to flash the Leedroid HC rom. It seemed to be dead on re-boot just the HTC screen. I did a restore from CWM and got Gingerbread back. Some apps like default browser did not work though.
Now I had a mostly working system I followed the O'brian (think' that correct name) including using official HTC unlocker as was in instructions. Tried to use another HC rom and the ARU wizard. I got an error 155 and an RUU failure msg on device. Not sure what to do know. I have download this file "Best RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed". Nothing much happens when I run it other than seeing the install screen, then it exits. I really need some help to get back to some kind of working system.
Been through thread "[GUIDE][Flyer+View]Gingerbread S-
OFF/Recovery/Permaroot"
Can't follow post 17 to get S-Off as device will not boot into android!
From CWM Backup, the external SD card I used seem to have got corrupted. This could have been root of problems
data.img - file error
cache.img - file error
nandroid.md5 - file error
Boot.img, recovery.img and system.img files seem ok...
Got this msg from "revolutionary.exe" when tried to get -"S-Off" again.
Found your device: /sbin/sh: getprop: not found (/sbin/sh: getprop: not-/sbin/sh
: getprop: not, Android: /sbin/sh: getprop: not, ROM version: /sbin/sh
Your device: /sbin/sh: getprop: not, with HBOOT /sbin/sh: getprop: not is
not supported at this time.
Here are my device details:
INFOversion: 0.5
INFOversion-bootloader: 1.11.0011
INFOversion-baseband: 3822.10.08.07_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 2.23.405.4
INFOserialno: HT15WT403213
INFOimei: xxxxxxxxxxxxxxxx
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__054
INFObattery-status: good
INFObattery-voltage: 4143mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: f0e1145e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
I have hboot 1.11.0011 with CWM and access via ADB
Your help appreciated, at end of my tether!
allot to take in but best I could tell you were on gingerbread and maybe tried to flash Lee Droid HC version so that would not work. So then you followed an old thread to update to HC using Paul Obrien's method whcih requires HTC Dev unlock of the boot loader. At this point in time you can not flash any roms via recovery and your system will not boot into android.
Please confirm if I am following what happened to you and if while in your hboot screen it says Unlock up top.
Thanks for replying.
In summary that's correct.
If I hold down the vol-down button I get the screen that says:
"*** UNLOCKED ***"
"flyer PVT SHIP S-ON RL
HBOOT-1.11.0011
Micro P-0950
Radio 3822.10.08.07_M
eMMc-Boot
I still have USB access to it via fastboot I think
ok so here we go
no hc rom will just directly flash and boot because you can not overwrite the boot.img via recovery with HTC dev unlock. If you wanted to flash say Leedroid you would have to pull the boot.img from the rom package then fastboot flash it first then back to recovery and flash the rom. This is a hacky way to do it and to be honest every time you flashed a rom you would have to do the same. Here is what I suggest:
follow this thread here to downgrade
http://forum.xda-developers.com/showthread.php?t=1307759
you may likely be able to skip the misc version part. Hopefully you are aware of what your stock ruu is. If you tried running it before and it failed it was because you did not relock the boot loader prior to trying as is described in the thread I linked
Once, hopefully, you are back on GB, I would run this method to get to HC
http://forum.xda-developers.com/showthread.php?t=1358758
now, if you flashed a hc rom on your device and it will not boot, just as mentioned flash the boot.img via fastboot from the rom and it should boot. This is if you are looking for the easy fix, and assuming I understand everythign you have done to this point
I have downloaded this file to use as my stock RUU
"RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_relea
se_204108_signed.exe".
I will go through steps 1 to 8 of the thread and the rest if I can. I am not sure about step 8, it says boot to android. Are you saving if I managed to get that far I will have some kind of working system back before I proceed further?
I will have a go now and let you know how I get get long.
Cheers!
as I stated you may not need to do the misc version part. and you do not need to flash recovery and su if you already have both
I followed the steps and apllied the HTC unlocker again, then flashed the recover.img with no error messages and put the Super User zip on my external SD card. I used the CWM install from zip option, seemed to proceed, no errors reported. When I re-booted the tablet I just have an empty black screen and nothing else. Should I proceed with the RUU or stop and try something else?? If I turn it off it immediately comes back on again to blank screen. The only way to keep it turned off is to use the power down option on hboot menu.
you were unlocked
you already had recovery
you already had super user
you did not have to repeat any of these steps
if you can get into hboot then follow the instructions to revert assuming you have the three things mentioned above. You can likely skip the misc-version step. If you get a message while flashing the ruu that states older version you will have to do the misc-version step which since you can not boot into android can be done in recovery as adb will see your device in recovery
I do not really think you are in too bad of a way right now, but without meaning to offend you, you scare me with not paying attention to what is being said. One concern I have is to make sure you have enough battery life left. If you hit less than 30% you will not be able to run the RUU. If you are confident that you have that much continue. If not power down through fastboot and charge for a couple of hours.
Please read, read, read, and do nothing unless you are atleast 50% confident that you understand
Hi
I really appreciate the help you are giving me. The only did all the steps just in case as I am paranoid about missing something important. I do think I have enough battery so I will see if I can use the RUU I downloaded
Thanks
I am now running the RUU, it says "updating rom image". It is showing a black screen with the letters HTC in white in the middle. I hope this works.
Thanks for your help.
Comment has been edited, sorry for silly question, answered in thread you mentioned
that is normal
My god, I am so relieved. To tired to be estatic. It's taken me 24 hours and only two hours sleeps to get back to Stock! You save my bacon Mcord! The battery after flashing was nearly 100%. Thankfully I kept it charging even though it was bricked in an attempt to increase the rescue time I had. The only downside is I missed a ski class I'd paid for and having to pay the "Filefactory" company for a subscription so I could reliably download the RUU.
I've learnt the hard way for sure. Anybody else reading this don't assume that just reading the instructions is enough. My SD Card had corrupt backup recovery files on it. How often do we double-check the integrity of our backups? the SD card may have also mean that the rom loaded onto it was corrupt as well. I should have checked the MD5 of all the files.
Thanks again!! I think I'll pause a bit before Honeycomb and def backup!
happy your back up and running. your problem was just not fully understanding the differences between GB and HC and S off and HTC Dev unlock. the thread I linked you is the one to use going forward if moving to HC and looking to run custom roms. As I mentioned before read, read, read.
What if in addition adb don't work ?
Hello,
I tried to downgrade, but the adb command don't work : device not found response...
So I connot follow the process explained http://forum.xda-developers.com/showthread.php?t=1307759
Second the CWN is broken too... Is that a problem ?
Thanks
It has come to a lot of peoples furious attention that there is an issue with the latest RUU from HTC. I firsthand had to deal with it an it is documented in this thread http://forum.xda-developers.com/showthread.php?t=2074643 in which i attempted to restore my htcdev unlocked phone back to stock.
THE ISSUE
The problem is the ruu is updating hboot and seemingly nothing else. Radios, recovery, rom, etc all have remained the same after running the ruu. Attempts at re running the ruu do nothing and various ways of flashing/applying the ruu are ineffective. This creates a stable but malfunctioning phone with mismatched hboot, radios, rom, and seems unable to take you back to fully stock.
Pre-RUU:
s-on
hboot: 1.19
radio: 1.05.11.0606
rom: stock rooted jb with superuser
Post-RUU: (after multiple flashings/applications)
hboot: 2.09
radio: 1.05.11.0606
rom: stock rooted jb with superuser (i'm assuming that this should have been completely stock instead its the same rom i had previous to ruu application)
In the mean time, I've been running the latest stock jb rom and its stable enough for a functioning phone but things like cellular data (streaming music from google music doesn't work or sending sexy pics to the ladies on snap chat) and lte is completely absent. If you experience the same issue post in here with what happened, solutions, fixes, etc.
GOING BACK TO STOCK
If you need to get back to stock or semi bricked your phone use the ruu for your current software not the latest (for example if your hboot is 1.19 use the ruu with hboot 1.19 not the jb ruu with 2.09 hboot)
For now it seems the best thing to do is aware htc of the problem, wait for a new ota update/ruu fix, and/or wait for new s-off method for 2.09,
tankerevo has been working on various attempts/fixes and i've forwarded this thread along with some other information to htc.
RESPONSE FROM HTC
Dear rollerpig,
Thank you for contacting the HTC Technical Support Center in regards to your issue suggestion.
We are glad to know there are customers like you committed with our brand to improve our service and customer satisfaction. We understand there could be a lot of users and fans waiting for a fix on this RUU. We think it is amazing to have a good support in our users to enhance our products and releases. Right now we will share this concern with the Develop Team to look forward on a solution. We expect this issue will be fixed as soon as possible.
Rollerpig, we want to thank you once again for working with us, and for caring about our brand.
If you require further assistance in the near future please contact us through http://www.htc.com/us/support/email-support or call us at +1-866-449-8358 from 6AM to 1AM EST, 7 days a week.
Have a nice day,
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Julian
HTC
Want to see what others are saying? Have a question to ask other HTC fans?
Become a fan of HTC facebook.com/htc
Follow us on Twitter twitter.com/htc
Subscribe to our YouTube Channel youtube.com/htc
Explore our development resources developer.htc.com
Please visit us at htc.com if you have any questions or need further assistance.
Click to expand...
Click to collapse
THE FIX
Here's a possible fix complements of user Fuses. I have not tried this yet because i'm on vacation but it looks very promising and most likely works. http://forum.xda-developers.com/showthread.php?t=2097150
Fix
- Download JB OTA firmware from http://unlimited.io/jewel.htm
- Download fastboot executable (google)
- Put all files in one directory
- Reboot phone into fastboot mode
- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock
- Enter commands
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
NOTE:
If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.
After this flash stock RUU again.
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily.
Click to expand...
Click to collapse
Obviously, depending on the firmware version you are frozen at there will likely be variance in stability and function between ROMs and other users with the issue stuck at a different firmware version.
For me the last ICS stock ROM is working the best including LTE. But WiFi, Cell, and Data do restart rather incessantly.
MeanBean 2.0 works alright considering... But LTE doesn't work at all and the radios get very weak signals to the point that I start to enter roaming often.
It might help to post before and after info of the radio versions, hboot, pri, all that stuff so if someone were to have used the RUU and it worked they can compare what the old stuff is to the new stuff.
does gps work well on the ics stock?
sickied for a little while until issue is resolved
Papa Smurf151 said:
sickied for a little while until issue is resolved
Click to expand...
Click to collapse
good deal... And also , Thanks OP for the heads up
I've got my lte back, but had to nandroid back to superlte. I went to ##3282# and set profile to 1, and changed scan timer to 2 and max timer 30. It has been the longest I've had constant lte in a month.
Sent from my EVO using Tapatalk 2
Mine was hosed too. If I ran the 2.13 RUU, it said you have a 2.13 image, would you like to update it to 2.13. If I ran the 3.15 RUU, it would say you have a 3.15 image on your phone, would you like to update it to 3.15?
Needless to say, none of that worked. I even tried the P75 image of JB direct from Sprint through recovery. No workie. I gave up and took it to Sprint. Explained that after RUU just aint going to work and this phone is stuck in ICS/JB hybrid limbo.
Sprint replaced the phone and I am now good to go. If you want to wait for a hack fix, then wait. Otherwise, you can try getting Sprint to replace it with a new one.
So back to my original question, can someone post what the 3.15.651.16 official numbers should be.
PRI, Radio, All those magical numbers were talking about..
Id like to check mine and see. I do remember downloading the RUU and installing it..
IAmSixNine said:
So back to my original question, can someone post what the 3.15.651.16 official numbers should be.
PRI, Radio, All those magical numbers were talking about..
Id like to check mine and see. I do remember downloading the RUU and installing it..
Click to expand...
Click to collapse
PRI - 2.87_003
Baseband - 1.12.11.1119
bigdaddy619 said:
PRI - 2.87_003
Baseband - 1.12.11.1119
Click to expand...
Click to collapse
OK those numbers match my device so i guess im OK..
The file i used to upgrade was downloaded 12/24/2012
RUU_JEWEL_CL_BJ_45_S_SPRINT_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe
This is the RUU i used on mine because i was impatient and didnt want to wait for the OTA to hit my phone.
From what i can tell it did the upgrade just fine.
IAmSixNine said:
The file i used to upgrade was downloaded 12/24/2012
RUU_JEWEL_CL_BJ_45_S_SPRINT_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe
This is the RUU i used on mine because i was impatient and didnt want to wait for the OTA to hit my phone.
From what i can tell it did the upgrade just fine.
Click to expand...
Click to collapse
IAmSixNine, could you give us a bit more detail on your setup. OS (windows etc), where you downloaded the RUU, and what software version were you running before you upgraded.
Windows 7 home, i was on the latest stock, unlocked device prior to that update coming out.
Where did i DL it at, http://www.htcruu.com/?dir=Jewel
Try this one, please report on that thread if fix works for you also
http://forum.xda-developers.com/showthread.php?t=2097150
I installed the 3.15 RUU from CM10 to try to bring my phone back to stock.
The RUU took, but now my phone is incredibly slow, freezes, screen goes unresponsive, camera wont work...All kinds of issues]
I even reapplied the same RUU from the stock 3.15 ROM.
Are my issues symptoms of this problem outlined in this thread?
Possibly. What's you baseband version?
If its less than 1.12 then yes.
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Also if it is less then fllow fuses thread link above.
update baseband
is there a way to update the baseband version mine is less then 1.12, I am s-off and am running the latest meanrom because meanbean was super unstable for me.
do I need to download the latest ruu to update it, then flash it with the latest meanbean?
frey482 said:
is there a way to update the baseband version mine is less then 1.12, I am s-off and am running the latest meanrom because meanbean was super unstable for me.
do I need to download the latest ruu to update it, then flash it with the latest meanbean?
Click to expand...
Click to collapse
Here is the full firmware minus hboot-recovery-kernel
http://d-h.st/4Y0
MD5 2a9b2c8f6a969fe0163df5738e8f4b5
Rename it PJ75IMG and place it on your ext sdcard/boot into bootloader/ it should ask you if you want to update follow the on screen instructions once you are rebooted remove the file from your sdcard if you don't you will be asked to update every time you enter bootloader
I rooted my phone this morning, and attempted to install cm10. the screen became inop. so I tried a recovery and it put it into boot loop. I have relocked the phone and tried some RUUs but all come back with bootloader, or signature errors, I have tried this method as well to no avail all i end up getting is this:
C:\Users\Downloads>fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 27.926s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 106.089s
Boot Screen:
*tampered
*relocked
s on
hboot 2.09
radio 1.12.11.1210
opendsp-v31.1.45.0815
eMMC-boot
Any help would be appreciated
I was trying to root my HTC One Mini and I bricked it.
I was following the tutorial on AndroidRootCentral and things were going well until I needed to install the SuperSU zip file. I couldn't find the file. My file structure as shown through TWRP was nothing like the file structure as seen though HTC Sync Manager. I tried rebooting the phone and placing the SuperSU zip in many locations. I'm not exactly sure what when wrong.
I probably screwed myself even further when I tried various things to get the phone to reset. Nothing I've read seems to work and I've been reading things and trying to get it to work since Friday. I've tried relocking the phone and then using an AT&T (my carrier) RUU. None of the RUUs I've found for AT&T work. All come back with a message about something being too long (I could look this up if you really need to know).
So ... help!
Is there a way to basically format and start over?
chilort said:
I was trying to root my HTC One Mini and I bricked it.
I was following the tutorial on AndroidRootCentral and things were going well until I needed to install the SuperSU zip file. I couldn't find the file. My file structure as shown through TWRP was nothing like the file structure as seen though HTC Sync Manager. I tried rebooting the phone and placing the SuperSU zip in many locations. I'm not exactly sure what when wrong.
I probably screwed myself even further when I tried various things to get the phone to reset. Nothing I've read seems to work and I've been reading things and trying to get it to work since Friday. I've tried relocking the phone and then using an AT&T (my carrier) RUU. None of the RUUs I've found for AT&T work. All come back with a message about something being too long (I could look this up if you really need to know).
So ... help!
Is there a way to basically format and start over?
Click to expand...
Click to collapse
More specifics please. What version of the firmware were you on? What RUUs have you found / tried to run? Please provide the exact error to further expedite the process. Also, if you have fastboot set up, boot to the bootloader and run:
fastboot getvar all
and post the results.
es0tericcha0s said:
More specifics please. What version of the firmware were you on? What RUUs have you found / tried to run? Please provide the exact error to further expedite the process. Also, if you have fastboot set up, boot to the bootloader and run:
fastboot getvar all
and post the results.
Click to expand...
Click to collapse
I'm going to bring some of this to you in pieces so I may edit this post for more info to answer your questions (I have a toddler running around and it is dinner time).
I do not know my firmware version. Under relocked my phone says:
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.29.40g.00.19
OpenDSP-v19.2.0268.0927
OS-4.13.502.3
eMMC-boot 1024MB
Jul 11 2014,20:49:19.0
I cannot hotlink but the one in this thread (http://forum.xda-developers.com/showthread.php?t=2777778) is one of the RUUs I tried. I tried others but in my haste to try to get this thing running again I didn't exactly take good records.
After running getvar all
version: 0.5
version-bootloader: 2.22.0000
version-baseband: 1.29.40g.00.19
version-cpld: None
version-microp: None
version-main: 4.13.502.3
version-misc: PVT SHIP S-ON
serialno: HT385WA00294
imei: 356482050078674
meid:
product: m4_ul
platform: HBOOT-8930
modelid: PO5822000
cidnum: CWS__001
battery-status: good
battery-voltage: 4314mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e1af350
hbootpreupdate: 11
gencheckpt: 0
Edit:
Okay, when trying the RUUs I get Error 155: Unknown error.
My PC is a an old Core 2 Duo and crashed a few times just trying to load the RUU. The RUU then asks to go through a recovery mode. It shows a picture with four exclamation points in the corners of the screen on the phone. My phone does not have the exclamation points. I've tried the recovery process a few times and it doesn't do anything.
The error about something being too long was when I was trying to load a .zip using fastboot from my Mac.
Seems like you're in a bit of a pickle then... There aren't any current RUUs for your phone. The one that you linked to would not be able to work unless you are S-Off because S-On will not let you downgrade. That version is 4.2.2 and it appears that you have accepted the OTA which means you will not be able to just run that RUU and get back to normal. Now, that doesn't mean there aren't any options, but probably at this point, it might be easiest just to install a custom rom since you still have TWRP. Just have to remember to pull the boot.img out of the rom zip and use fast boot to install or you will bootloop. If you really want to be back on bone stock, you would need to jump through some hoops. Basic outline is as follows:
Put rom on phone.
Boot to TWRP
Wipe and install rom
Boot to bootloader and flash boot.img
Once back up and running you'd need to S-Off (I believe Rumrunner for 4.2.2, but you'll need to double check that)
Once S-Off is achieved, then you would need to relock the bootloader and then you should be able to run the RUU and accepts the OTA(s) to get up to date and stock / non rooted
Unless this is for warranty issues, I'd just use a custom rom. I'm certain there is one that is completely stock or just stock + root if that is all you want / need.
es0tericcha0s said:
Seems like you're in a bit of a pickle then... There aren't any current RUUs for your phone. The one that you linked to would not be able to work unless you are S-Off because S-On will not let you downgrade. That version is 4.2.2 and it appears that you have accepted the OTA which means you will not be able to just run that RUU and get back to normal. Now, that doesn't mean there aren't any options, but probably at this point, it might be easiest just to install a custom rom since you still have TWRP. Just have to remember to pull the boot.img out of the rom zip and use fast boot to install or you will bootloop. If you really want to be back on bone stock, you would need to jump through some hoops. Basic outline is as follows:
Put rom on phone.
Boot to TWRP
Wipe and install rom
Boot to bootloader and flash boot.img
Once back up and running you'd need to S-Off (I believe Rumrunner for 4.2.2, but you'll need to double check that)
Once S-Off is achieved, then you would need to relock the bootloader and then you should be able to run the RUU and accepts the OTA(s) to get up to date and stock / non rooted
Unless this is for warranty issues, I'd just use a custom rom. I'm certain there is one that is completely stock or just stock + root if that is all you want / need.
Click to expand...
Click to collapse
Thank you for the help! I am not at all opposed to a custom rom (I thought going backward might be easier than forward). But that goes beyond what I've read so far. I know I could Google it, but would appreciate any links, pointers, or other primers.
Stock + root is what I was trying to achieve.
Here's a version of stock rooted rom from the international version (no AT&T bloatware - yay!):
http://forum.xda-developers.com/showpost.php?p=51779967&postcount=294
You need either the odexed or deodexed version from this post since you are on hboot 2.22. Odexed is fine if you aren't planning on trying to theme anything though there really isn't that much difference between them. Odexed used to be preferred for smoothness but with phones as powerful as they are now, you would be very hard pressed to tell them apart. Basically you just need to make sure you are on the right recovery, flash the rom, then use the boot.img to flash via the bootloader and you should be good to go.
Because you do not have an SD card slot, you will need to use adb while in recovery to push the rom zip from the computer to the phone. Like so:
adb push rom.zip /sdcard/ (replace rom.zip with the name of the rom you downloaded - Hint: you can name it whateveryouwant.zip to make it easier).
If you need adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Just make sure you have the right drivers and ^ and the rom zip in that folder ^ and use the Command Prompt (make sure you change directories to the adb/fastboot folder) to enter the commands.
es0tericcha0s said:
Here's a version of stock rooted rom from the international version (no AT&T bloatware - yay!):
http://forum.xda-developers.com/showpost.php?p=51779967&postcount=294
You need either the odexed or deodexed version from this post since you are on hboot 2.22. Odexed is fine if you aren't planning on trying to theme anything though there really isn't that much difference between them. Odexed used to be preferred for smoothness but with phones as powerful as they are now, you would be very hard pressed to tell them apart. Basically you just need to make sure you are on the right recovery, flash the rom, then use the boot.img to flash via the bootloader and you should be good to go.
Because you do not have an SD card slot, you will need to use adb while in recovery to push the rom zip from the computer to the phone. Like so:
adb push rom.zip /sdcard/ (replace rom.zip with the name of the rom you downloaded - Hint: you can name it whateveryouwant.zip to make it easier).
If you need adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Just make sure you have the right drivers and ^ and the rom zip in that folder ^ and use the Command Prompt (make sure you change directories to the adb/fastboot folder) to enter the commands.
Click to expand...
Click to collapse
The version of TWRP on my phone is 2.6.0.0. This is not version listed in the link you posted. They list 2.7.0.5. Will this be problematic?
I went ahead and gave it a try. I loaded TWRP and went into the adb sideload feature. The screen for sideload listed the following:
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Running boot script ...
Finished running boot script.
E: TWFunc::Copy_Log -- Can't open destination log
E: Unable to mount '/cache'
Starting ADB sideload feature ...
I saved the rom as rom.zip to make things easier as suggested. In my terminal window I typed the command as listed (ADP and the rom are in the same folder). In the terminal window I received:
error: closed
error: closed
You will definitely need the newer TWRP before it will work. But you don't use adb sideload. As long as the PC recognizes the phone correctly, then you just need to open the Command Prompt, change directories to the folder where adb and rom.zip are store and then copy and paste the command into it and hit enter. It should start to send. It will take awhile and there is no timer so just go grab a sandwich or drink or something and be patient.
You can use this video for reference:
https://www.youtube.com/watch?v=Hn4E3fKX7WM
It's a different device, but the same exact steps. He does state that he puts the name of the rom after /sdcard/ in the command, but it's not necessary. Won't make a difference for this.
Okay. That was somewhat helpful. I couldn't find TWRP 2.7.0.5, but I did get 2.7.1.1 and I got it loaded.
I've tried the adb command. It sits there for a long time, then the phone reboots into TWRP. I get no messages back in the terminal window and nothing is loaded into the /sdcard directory (or anywhere else as far as I can tell).
Edit: wait. Formatted it and am going to try again.
Edit 2: loading rom!!!
Don't forget to fastboot the boot.img or it won't boot. If it is still stuck in a bootloop after the rom and boot.img are installed, then reboot to recovery and perform another factory reset. Should work. If not, then you might need the other TWRP. The link for it is right on the same post as the rom. Not sure how you missed it...
es0tericcha0s said:
Don't forget to fastboot the boot.img or it won't boot. If it is still stuck in a bootloop after the rom and boot.img are installed, then reboot to recovery and perform another factory reset. Should work. If not, then you might need the other TWRP. The link for it is right on the same post as the rom. Not sure how you missed it...
Click to expand...
Click to collapse
I missed it because I didn't read carefully and am doing this in bits and spurts.
The good news is that I have a running phone again. Thank you so much for the help!:good:
chilort said:
I missed it because I didn't read carefully and am doing this in bits and spurts.
The good news is that I have a running phone again. Thank you so much for the help!:good:
Click to expand...
Click to collapse
:good::highfive::victory:
es0tericcha0s said:
:good::highfive::victory:
Click to expand...
Click to collapse
Thank you again for walking me through this. It is nice to have my HTC back. My slow, piece of junk work phone can now go back to running BOINC.
No problem. It's how I give back to the community.
Hello there.
I have been trying at this for a while now but simply cannot figure out how to get around this issue. I have successfully rooted my M8 but now I am trying to install OTA updates. I looked up a guide on how to do this and came to this video:
Everything was going swimmingly until about minute 7 in the video where the step is to and go ahead with the OTA updates. When my phone restarts to install the updates the progress bar loads to about 1/5 and then stops for a few moments before giving me the triangle red exclamation mark icon.
How do I get around this? I'm fairly certain I have the right stock recovery. All I want to do is install the OTA updates without losing any of my current apps/settings. If an easier process is to unroot my phone and leave it that way then so be it.
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Any help pointing me in the right direction would be swell. I apologize in advance for the tall order. Thanks.
blinkdagger said:
Hello there.
I have been trying at this for a while now but simply cannot figure out how to get around this issue. I have successfully rooted my M8 but now I am trying to install OTA updates. I looked up a guide on how to do this and came to this video:
Everything was going swimmingly until about minute 7 in the video where the step is to and go ahead with the OTA updates. When my phone restarts to install the updates the progress bar loads to about 1/5 and then stops for a few moments before giving me the triangle red exclamation mark icon.
How do I get around this? I'm fairly certain I have the right stock recovery. All I want to do is install the OTA updates without losing any of my current apps/settings. If an easier process is to unroot my phone and leave it that way then so be it.
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Any help pointing me in the right direction would be swell. I apologize in advance for the tall order. Thanks.
Click to expand...
Click to collapse
If I remember correctly, you can't be rooted doing official ota updates. Finish updates, then root
BR7fan said:
If I remember correctly, you can't be rooted doing official ota updates.
Click to expand...
Click to collapse
Ok, do you think it's worthwhile to manually do the updates?
blinkdagger said:
Ok, do you think it's worthwhile to manually do the updates?
Click to expand...
Click to collapse
Yeah I found them to be those guys get the latest up very quick. Make sure your s-off
BR7fan said:
Yeah I found them to be those guys get the latest up very quick. Make sure your s-off
Click to expand...
Click to collapse
Ok thanks a lot. I will try to manually install the updates.
BR7fan said:
If I remember correctly, you can't be rooted doing official ota updates. Finish updates, then root
Click to expand...
Click to collapse
You would be remembering incorrectly. Root has no impact itself on whether an OTA will install. As long as no system files have been altered by the user (using root permissions), and stock recovery is installed. Root and unlocked bootloader are both okay. Although you will most likely lose root after the update.
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
blinkdagger said:
Phone INFO:
CID: T-MOB010
version 4.4.4
HTC sense v. 6.0
software #: 3.32.531.2
SDK API level: 6.25
Click to expand...
Click to collapse
Is your phone the T-Mob version, or an AT&T version converted to T-Mob? Because this is the AT&T version specific forum section.
Another option to update would be to just run the T-Mobile Lollipop RUU. Relock the bootloader if you are s-on. Biggest downside, is that RUU will wipe the phone; and keeping user data may be your reason for seeking the OTA route.
redpoint73 said:
You would be remembering incorrectly. Root has no impact itself on whether an OTA will install. As long as no system files have been altered by the user (using root permissions), and stock recovery is installed. Root and unlocked bootloader are both okay. Although you will most likely lose root after the update.
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
Is your phone the T-Mob version, or an AT&T version converted to T-Mob? Because this is the AT&T version specific forum section.
Another option to update would be to just run the T-Mobile Lollipop RUU. Relock the bootloader if you are s-on. Biggest downside, is that RUU will wipe the phone; and keeping user data may be your reason for seeking the OTA route.
Click to expand...
Click to collapse
I think I may have posted in the wrong forum. My phone is simply the T-Mobile version as far as I know. I think I may have changed some system files around. Do you know of a way to reset them to default that way I can proceed with the OTA updates? I do want to keep all the apps and user settings. My plan was to re root the phone after the OTA updates were done. Thanks for your help.
blinkdagger said:
I think I may have posted in the wrong forum. My phone is simply the T-Mobile version as far as I know.
Click to expand...
Click to collapse
T-Mobile has its own section, so yes this is the wrong forum section. But I'll try to help anyway, as your issues aren't that carrier specific.
blinkdagger said:
I think I may have changed some system files around. Do you know of a way to reset them to default that way I can proceed with the OTA updates?
Click to expand...
Click to collapse
Few different options.
1) Just restore the nandroid backup you made before messing with system files. And you did this, like you should before making any such mods, RIGHT? Well if not:
2) You can manually change them all back. Probably the most tedious method, especially since you don't seem sure of what you changed.
3) Find the right stock nandroid and flash it. Find corresponding stock recovery, and flash it.
4) Relock the bootloader and RUU to stock, and since you can just RUU to the current OS version, no need to OTA. After that, just unlock the bootloader again via HTCDev.com (of if you want to avoid that, sunshine) in preparation for installing custom recovery (and root) again. Yes, RUU will wipe that phone, but that brings us to the next point:
blinkdagger said:
I do want to keep all the apps and user settings. My plan was to re root the phone after the OTA updates were done. .
Click to expand...
Click to collapse
You are rooted, so back up your apps and app data with Titanium Backup (or similar root app). Then you can just restore all the apps and app data after you RUU. You should be backing them up anyway. Saying you want to keep your app data; then not having them backed up is a contradiction. If you data is important to you, back it up. And that advice goes for whether you decide to RUU or not.
Backing up setting with Titanium across ROM versions is not recommended. But unless you have a really large amount of settings customizations, it usually doesn't take that much time to set these up again manually, anyway (as long as your apps and app data are already restorable).
Option 4 above is what I would consider. Its really up to you whether options 3 or 4 are best for you. But the reason I like RUU, even though it has the extra steps of relocking/unlocking the bootloader, and backing up your data; what it saves you is from finding the right stock nandroid and stock recovery, and putting them to the correct location on the phone to then Restore with TWRP. And these steps are ones with potential for mistakes that can make them exhaust a lot more time than you would think. RUU is a complete factory image, so everything is sure to play well together, no guesswork or potential for mistakes.
redpoint73 said:
T-Mobile has its own section, so yes this is the wrong forum section. But I'll try to help anyway, as your issues aren't that carrier specific.
Few different options.
1) Just restore the nandroid backup you made before messing with system files. And you did this, like you should before making any such mods, RIGHT? Well if not:
2) You can manually change them all back. Probably the most tedious method, especially since you don't seem sure of what you changed.
3) Find the right stock nandroid and flash it. Find corresponding stock recovery, and flash it.
4) Relock the bootloader and RUU to stock, and since you can just RUU to the current OS version, no need to OTA. After that, just unlock the bootloader again via HTCDev.com (of if you want to avoid that, sunshine) in preparation for installing custom recovery (and root) again. Yes, RUU will wipe that phone, but that brings us to the next point:
You are rooted, so back up your apps and app data with Titanium Backup (or similar root app). Then you can just restore all the apps and app data after you RUU. You should be backing them up anyway. Saying you want to keep your app data; then not having them backed up is a contradiction. If you data is important to you, back it up. And that advice goes for whether you decide to RUU or not.
Backing up setting with Titanium across ROM versions is not recommended. But unless you have a really large amount of settings customizations, it usually doesn't take that much time to set these up again manually, anyway (as long as your apps and app data are already restorable).
Option 4 above is what I would consider. Its really up to you whether options 3 or 4 are best for you. But the reason I like RUU, even though it has the extra steps of relocking/unlocking the bootloader, and backing up your data; what it saves you is from finding the right stock nandroid and stock recovery, and putting them to the correct location on the phone to then Restore with TWRP. And these steps are ones with potential for mistakes that can make them exhaust a lot more time than you would think. RUU is a complete factory image, so everything is sure to play well together, no guesswork or potential for mistakes.
Click to expand...
Click to collapse
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
blinkdagger said:
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
Click to expand...
Click to collapse
Yes. As of this date, Sunshine is the only way to gain S-Off for the M8. Firewater is discontinued.
blinkdagger said:
Hey thanks for all the help. I have decided to use Option 4 but I have discovered that my phone is still S-ON. I found this thread which seems to be able to provide me with the right RUU file.
http://forum.xda-developers.com/showthread.php?t=2754063
The only issue is that at the top of the thread it says that these RUUs are meant for S-OFF users. After searching a bit I learned that supposedly http://theroot.ninja/ is the only way to change my phone from S-ON to S-OFF. I just don't want to pay 25 bucks if I don't have to. Is this the only way?
Click to expand...
Click to collapse
The s-off statement in the thread you linked was specific to firmware packages. S-off is required to flash a firmware.zip, not an RUU. Those are 2 very different things.
RUU will run fine with s-on, as long as you relock the bootloader; and also you can only run an RUU that is equal or greater than the software version you rooted (looks like Android 4.4.4). So what you want is a T-Mobiel RUU for either Android 4.4.4 (software 3.xx) than OTA to Android 5.0; or RUU right to Android 5.0 (software 4.xx).
redpoint73 said:
The s-off statement in the thread you linked was specific to firmware packages. S-off is required to flash a firmware.zip, not an RUU. Those are 2 very different things.
RUU will run fine with s-on, as long as you relock the bootloader; and also you can only run an RUU that is equal or greater than the software version you rooted (looks like Android 4.4.4). So what you want is a T-Mobiel RUU for either Android 4.4.4 (software 3.xx) than OTA to Android 5.0; or RUU right to Android 5.0 (software 4.xx).
Click to expand...
Click to collapse
Hey I know it has been a while but I just got around to taking care of this. I want to use an RUU to reset everything like you mentioned. The trouble I am now having is with the re-locking procedure.
I am trying to to relock the bootloader using the "fastboot oem lock" command. When I enter the command I get this message.
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.194s
I have done this about 5 times now and the lock status remains "UNLOCKED". Thank you for all your help thus far. I will continue to try to search for a solution.
Hi guys,
I can't install OTA update. It says that my phone may be running a modified version of its system software. So can someone help me please.
Here is the info:
INFOversion: 0.5
INFOversion-bootloader: 3.16.0.000
INFOversion-baseband: 1.15.2133156
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.54.401.5
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: HT45WWM07657
INFOimei: ****************
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul_ca
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B12000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: ab0efa49
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.047s
You need to restore the stock ROM for the phone's original CID/MID in order to install an OTA.
Based on your main version number (with "401" in it) you are running a stock or custom ROM based on the Euro ROM.
My CID is 11111111. I think, my phone is an at&t variant "ul_ca". So, if I install the stock rom at&t, it will be sim-locked? Anyway, I can't install a custom recovery on my phone .
rvaaness said:
My CID is 11111111. I think, my phone is an at&t variant "ul_ca".
Click to expand...
Click to collapse
I take back what I said earlier. SuperCID should be okay.
Stock ROM won't relock the SIM.
You need to re-install the stock ROM to OTA. But you might find it easier to just RUU (which will also update your phone to the latest version) rather than searching around for the right stock ROM; as long as you don't mind your data being wiped (which the RUU will do).
rvaaness said:
Anyway, I can't install a custom recovery on my phone .
Click to expand...
Click to collapse
Is your bootloader unlocked?
Fastboot/adb connectivity?
The bootloader is unlocked. But I can't access to recovery. Trying to install different custom recovery, and the phone stuck on it.
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
The bootloader is unlocked. But I can't access to recovery. Trying to install different custom recovery, and the phone stuck on it.
Click to expand...
Click to collapse
Fastboot erase cache, the try installing recovery again. Use current version TWRP (version 2.8)
Fastboot erase cache. And try to install to twrp.
Always recovery boot stuck.
Sent from my HTC One_M8 using XDA Free mobile app
Try running the Lollipop RUU to update the phone.
As long as you don't mind your data being wiped (RUU will wipe your data), the RUU is a better/cleaner install anyway.
I have read somewhere that we must change the cid matching with the RUU. So, I will lose the superCID, right?
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
I have read somewhere that we must change the cid matching with the RUU. So, I will lose the superCID, right?
Click to expand...
Click to collapse
SuperCID is fine. SuperCID by definition passes any CID check. Its only if you are on another carrier's CID, that you need to change it (to match what the RUU is looking for).
Hello,
I was very afraid to do the update by RUU because I had already brick my htc one m8. But finally, I done it. Everything was working but at the step 5/7, my computer said that the fastboot stop working. BUT I rebooted my phone and the ROM at&t works until now. Is it normal? Or must I re-install the RUU? Thank you for your reply.
rvaaness said:
I was very afraid to do the update by RUU because I had already brick my htc one m8. But finally, I done it. Everything was working but at the step 5/7, my computer said that the fastboot stop working. BUT I rebooted my phone and the ROM at&t works until now. Is it normal? Or must I re-install the RUU? Thank you for your reply.
Click to expand...
Click to collapse
Since it seems the RUU didn't run to completion, I'd run it again. Its not uncommon for this to happen.
If you check the hboot number, main version, etc. I have a feeling these have not changed, and that the steps executed successfully involved just pushing the files to the phone (and not actually installing them). But that is just a guess, as I don't know off had what step is what.
Ok. I understand now. But... Now, when I am checking the software update, there is no upadate available however my android version is 4.4.2.
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
Ok. I understand now. But... Now, when I am checking the software update, there is no upadate available however my android version is 4.4.2.
Click to expand...
Click to collapse
You typically won't get OTA updates on the AT&T version M8 unless you are connected to the AT&T network. This is a AT&T specific requirement (other versions will update fine regardless of carrier).
Did you get the original OTA (Post #1) over the network; or did you put the file on the phone yourself manually?
In any case, you can RUU to update all the way up to the latest version Android 5.0, no need to mess with OTAs at all.
I received the OTA by network, and can't put it on my phone manually as I said I can't access to a custom recovery.
I fear to use RUU, in case all steps will be not finished, and I think that maybe last time it was just a chance. Am I wrong?
Sent from my HTC One_M8 using XDA Free mobile app
rvaaness said:
I fear to use RUU, in case all steps will be not finished, and I think that maybe last time it was just a chance. Am I wrong?
Click to expand...
Click to collapse
I already mentioned, that the RUU not running fully the first time is fairly common.
Anything has a small chance to brick the phone (so be aware of the risks and consequences). But this is the official RUU meant for your device. Its one of the safest things around.
Ok. Thank you. But now, I have another problem. A big problem!
My phone was fallen, the screen is not broken, but the phone doesn't turn on. When I plug the charger, the LED is red and there is a picture of charging empty battery. Already try:
1- Push the Power + Volume Up
2- Push the Power + Volume Down
3- Push the Power + Volume Up + Volume Down during 1-2 minutes
Everything is not working. The LED just turn to green and after the same screen battery charging.
Do you think that it is the motherboard? Thank you for the reply.
rvaaness said:
My phone was fallen, the screen is not broken, but the phone doesn't turn on. When I plug the charger, the LED is red and there is a picture of charging empty battery. Already try:
1- Push the Power + Volume Up
2- Push the Power + Volume Down
3- Push the Power + Volume Up + Volume Down during 1-2 minutes
Everything is not working. The LED just turn to green and after the same screen battery charging.
Do you think that it is the motherboard? Thank you for the reply.
Click to expand...
Click to collapse
Try holding combo 1 for a minute or so.
Also, try combo 1 and 2 with and without the charger plugged.
Combo 3 is not a valid combo on this phone, that I am aware. No point in trying it.
Mobo? Maybe. Can be any number of things since you dropped it.