Related
edit and tldr
ok so i recieved the phone from htc with a bootloop out of the box
instead of sending it back i was a numpty and decided to sort it myself and unlocked it to flash a rom
i accidentially deleted all the data
managed to get my winsows 8 laptop working today and got drivers working smoothly to the point i was able to sideload a rom so the phone finally had life from being a brick
my issue is no matter what rom i load it boots to splash screen, hangs at a black screen with the status bar at the top and battery and time then reboots and repeats.
i want help to get my phone back to life and stable with a workable rom and no bootlooping
i dont know what the issue is
i dont have s off
rumrunner wont work
i cannot boot into phone to allow debugging or disable fast boot
please help
device info
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
i will offer a small sum for who ever gets me a working phone. small exchange for a paperweight !
Deleted. Op edited post to include cash reward. Dont want to look like im helping to receive money.
hi there, thank you for the reply, i have done steps 1, id already done that but ive done it again and installed the sdk into a folder in c drive for ease. the only problem is that when i click on fastboot in xp it comes up with a cmd windows a lot of writing comes down and then it just closes :/
ive already voided the warranty as ive somehow managed to unlock the bootloader and ive flashed cmw now what i need to do is somehow get s off and sideload a rom
another issue i have is that because i cant use fastboot the way youve said, ive downloaded an all in one tool from this forum, when i click a process it dosent do anything for me, but what it does so, is open a cmd window in which im able to type in fast boot commands i did the getvar all command and here is what you requested
'C:\Documents' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
C:\Documents and Settings\fresh\Desktop\one\data>
Deleted
garyfl said:
ok so i think this is going to be a little long winded
basically, i got a htc one given to me by htc,
Click to expand...
Click to collapse
Why don't you think they would give you a new working one?... :s (this is just a rhetorical question)
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
the ruu you have linked indicates i need s off, which i am having trouble doing, could you guide me ? i am thinking when i have fixed my windows 8 laptop tommorow this is going to be a smoother process. it also says i need hboot 1.44 and have to flash this
garyfl said:
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
Click to expand...
Click to collapse
If you don't solve it before I get a lil bit of time, I can try for tonight but can't promise it as it's still hectic here at work, I'll log in remotely and have a look at things if you want, and try to help you get it sorted.
In the meantime, you can take a picture of the hboot or fastboot screen that you get to with power + vol down and post it, and that will help you get the information from us for more information on the phone.
Also post a shot of the correspondence from HTC with your personal information removed/redacted/left out and that will also help us help you.
DO NOT ATTEMPT S - OFF with the knowledge and hardware that you're working with, you first need to use adb and fastboot some and be familiar with it before even going there. I'm not saying not ever, I'm saying not until you've resolved this and the phone's running good.
Deleted
when i run rumrunner with my version 2.24.401.1 it just says run again and read. so obviously failing. i did everything before i typed fastboot devices and got my device code, then getvar ver to get my number and downloaded appropriately but rum runner dosent work. so no s off. i give up.
sorry didnt read your reply, well it didnt initialise so no s off anyway
garyfl said:
sorry didnt read your reply, well it didnt initialise so no s off anyway
Click to expand...
Click to collapse
Take a picture of the hboot screen and post it for us
im sorry i cant take a pic atm no cameras, what i can do is write eveything out as it looks in detail for you
***tampered*** <--- in dark grey
***unlocked*** <--- in pink
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OPENdsp-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013, 00.54:00.14313
FASTBOOT USB <--- in red
then its just the vol up and down with selecable bootloader, reboot, reboot bootloader, power down at the bottom. i have rooted many phones in the past, desire hd, one x, galaxy note, galaxy s4, its just the trouble i am facing i think is using xp
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
garyfl said:
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
Click to expand...
Click to collapse
flash twrp/cwm recovery to your one
open the sideload feature of the customer recovery on your phone and connect to your computer usb
download this and put the downloaded file together with your adb and fastboot folder
then adb sideload or adb push the dowloaded guru reset to your One
once it is done, you can install the guru reset zip using the custom recovery install option
right just to update i have some semi good news and fell im getting somewhere
got my windows 8 laptop up and running today and installed all drivers and adp corrdctly, this accounts for the intel usb 3 mod too. adb and fastboot were recognising the device.
ive succesfully got out of brick mode and managed to get a rom to sideload to the deviice, the rom being viper rom in question, installed successfully, only issue is i have a wierd bootlooping issue where it does actually boot to lockscreen but when i pull lockscreen up with my finger it shows htc splash screen.
having ago with android revolution now.
wondering if i have to flash a boot.img or something
can anyone advise ?
ive spent countless days on this
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
garyfl said:
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
Click to expand...
Click to collapse
the guru ruu.zip for 2.24.401.1 is sideloading now
guys, the guru stock installed but now im back to the very beginning of the way i recoieved my phone. bootloops to the black screen with bar at top with date and battery, then after a while restarts, please someone help me
I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.
XDA Dev said:
I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.
Click to expand...
Click to collapse
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!
SaHiLzZ said:
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!
Click to expand...
Click to collapse
Haha, thanks, I guess nearly 3 years of lurking on these forums taught me something about posting.
I was using a Windows Vista SP2 PC to try this. I've just tried it on my Mac running Windows 7 SP1 with bootcamp, the RUU file (which still checks out with the correct MD5 hash) starts the installshield wizard normally, but as soon as I accept the terms and conditions, the program closes and nothing opens again. I checked on task manager, the process closes shortly after accepting the terms. I tried restarting and looking up for a solution but I couldn't find anything that worked.
Is Vista really the only reason it's stuck at checking headers? I know Vista is rather despised by a lot of people, but by 2014 it did get better. I'd rather use that machine because on my Mac running Windows 7 the RUU could not start up because I've made the Windows partition too small. (It has around 3gb free now whereas the vista machine has more than 150).
Sorry for the double post, but it's probably my last one on this thread.
Even if my boot loader was re-locked, I tried running the firewater program to get s-off, and it worked. (As a bonus it re-unlocked my boot loader without wiping the phone, but I re-locked it again to get the ruu working).
Then I tried downgrading to hboot 1.44, but for some reason it kept giving an error like "failed: remote 42 custom id check fail." I decided to try the sense 5.0 ruu anyway (on my vista PC), and it worked! The phone now says "relocked" but tampered is gone of course, and I have hboot 1.44, android 4.1 and htc sense 5.0, but still s-off.
The first update popped up (and it's not android 4.4 with sense 6, it's something in between) so I'm going to update until no more updates are available. Then I'm going to re-unlock the boot loader because I want to root my phone, and then set up all my stuff. When a new update comes out, I can just flash the original recovery, apply the update and then re-flash twrp to root again.
Thank you for the suggestion to install the older ruu. I'm still stumped on why the newer one didn't work (it would have caused much less hassle), but whatever. At least my phone is much cleaner now. It feels good to have it like this again, I'm not against custom roms but I like the stock software too.
I'm using my iPhone to write this, but trust me, my htc is in full working order now.
Until next problem I can't solve myself
Sent from my iPhone using Tapatalk
Thanks for updating back. Don't S-ON.
SaHiLzZ said:
Thanks for updating back. Don't S-ON.
Click to expand...
Click to collapse
Yeah, I'm not going to. I've updated to android 4.3 now and I'm still downloading updates--it updated hboot to 1.55 but I still have s-off, so I believe it stays s-off if I don't run the command to (I guess irreversibly) go back to s-on, which I don't even know. (I didn't do s-off before because I didn't care about the extra privileges and was afraid of bricking my phone, but now that I have it I don't mind so I'm keeping it).
Sent from my iPhone using Tapatalk
I got a message about the OTA update so downloaded it and went to install, on the reboot I got the bootloader appearing which says
****TAMPERED***
****LOCKED****
****Security Warning****
I have never bothered to root the phone or anything as its one I use for my business so didn't want to take any risks with it! HTC were absolutely useless when I asked them about this (no surprises there)
so how do i get the update to install on my phone?
the_r_sole said:
I got a message about the OTA update so downloaded it and went to install, on the reboot I got the bootloader appearing which says
****TAMPERED***
****LOCKED****
****Security Warning****
I have never bothered to root the phone or anything as its one I use for my business so didn't want to take any risks with it! HTC were absolutely useless when I asked them about this (no surprises there)
so how do i get the update to install on my phone?
Click to expand...
Click to collapse
can you post the output of ''fastboot getvar all'' except imei and serialno
i can try!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3835mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
well, now it's getting really annoying, I guess the update tried to install and somehow fooled google play into thinking it had, that updated itself and now I get errors every minute to say google play services has stopped and then after about 4 the phone reboots - it's really handy having a premium device for work that I can't use
so decided i would try and follow the guide to set back to stock - first thing to do is to get s-off - tried the firewater thing but the phone won't stay on long enough to get through the instructions!!
What a piece of …
I am going to attempt to get a new handset from my network as this kind of rubbish shouldn't happen to a handset that i've never tried to alter!
Can you download the RUU for your phone, boot into bootloader then flash it?
Sent from my HTC One using Tapatalk
well, no!
I am now looking at the white screen "h&c quietly brilliant" and have been for some time - won't get past that screen now not sure what happened on one of the restarts to make that happen but assuming it's just going to get worse until it goes in the bin
can i flash the RUU with S-On?
I have so much hate for my phone right now, the one reason I have never touched the software on this one is because I need it for work, and it's the only one that's gone t*** up!
the_r_sole said:
can i flash the RUU with S-On?
I have so much hate for my phone right now, the one reason I have never touched the software on this one is because I need it for work, and it's the only one that's gone t*** up!
Click to expand...
Click to collapse
One of the main reasons I root and install custom recovery and s-off is to insure I have backups and the ability to flash any RUU. Their is no Nandroid with a stock phone.
So, can anyone help with this?
Phone can only get to bootloader and freezes at white screen if I try to start it...
the_r_sole said:
So, can anyone help with this?
Phone can only get to bootloader and freezes at white screen if I try to start it...
Click to expand...
Click to collapse
well, I got somewhere! went to htcdev to unlock the bootloader, once I did that it rebooted properly so apart from losing all my text messages and having to set up my emails it's all good!
have done some more reading and it seems like 1.56 hboot can't get s-off so I am in the ludicrous situation of not being able to get a completely stock phone to be a completely stock phone and get the OTA updates!!
the_r_sole said:
have done some more reading and it seems like 1.56 hboot can't get s-off so I am in the ludicrous situation of not being able to get a completely stock phone to be a completely stock phone and get the OTA updates!!
Click to expand...
Click to collapse
you can s-off using firewater for hboot 1.56, sometime it works, sometime it don't.
you can still have ota updates if you restore the missing files for ota and you flash back the stock recovery.
or some custom roms are always up-to-date and not much different from a stock rom look (i.e ARHD)
you can always send the phone to fonefunshop.com and have it s-off'ed via a java card. then you'll be able to do a full ruu
Yeah, tried firewater a few times and it gave me the error saying that it will never work!
Went for ARHD which works fine, so will just stick with it for a while anyway
Cherrs
Ok so I think I might have f*cked up a bit. Today I was playing around with my phone, trying to get te "knockoff" feature working. I found this, rather old, instruction to do it and followed everything.
Everything went fine. I got my phone unlocked, installed TWRP recovery and SuperSU. But then I tried doing the last step and flashed the kernel. Thats when it started going wrong. All of a sudden I couldn't get out of the recovery mode. I tried a couple of things and somehow, by messing up, I am now at a point it seems like I have erased pretty much everything and can't do anything. I can still go into the fast boot mode. I can also still go to the recovery mode and then I can add files to my phone through Android File Transfer. I can still flash things from my laptop to my phone or install them through the recovery but it seems like everything is empty and I somehow managed to delete everything.
When in recovery I try the reboot option, it says that i have no OS installed and asks me to instal SuperSU but doing so doesn't change anything.
Can anyone please help me? I looked for hours on the internet already but nothing seems to work. At this point I just want my phone to be working again. Do note I am using a Mac so I can't use any windows programs to do anything.
Try to use a ruu.
How do I do that? And where do I find that?
Can't post a link cause I'm on my phone but in the General section, it says HTC M7 RUU collection. Read carefully because you can mess up your phone even more if you select the wrong one. Good luck :thumbup:
Sent from my HTC One using XDA Free mobile app
You can find latest here:
http://forum.xda-developers.com/showpost.php?p=59275081&postcount=1
Which one would be the correct RUU? Cause I cant seem to find one that fits my phone I think. The number for mine starts with 7.11. Ill look for the correct one this afternoon cause I have it but there seems to be none that matches it.
UPDATE:
Here is all the data from the Getvar:
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.18.111.2
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: T-MOB101
battery-status: good
battery-voltage: 4311mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b30b07eb
hbootpreupdate: 11
gencheckpt: 0
Which ruu should I use? I just want my phone back working, preferably just the normal version of android.
And do I flash the RUU through Terminal to my phone or do I need to put it on my phone and install it through recovery?
Sorry to be late,
Hard working today, answer in your Mp
So... Sorry if the title is a little misleading, but here goes... Android 5.0.2 and Maximus 50.0.0, no custom kernels or any mods... I gave the phone to a friend and he basically did a factory reset (even tho he really didnt need to...) and it deleted all the apps and stuff, but there was some files under Other in Storage that didnt get deleted, so he had the bright idea to get into recovery (twrp) and do a full wipe (internal, data, system, etc...). So when the phone booted, it gave a SystemUI force close and an Package Access (or something similar) force close too, and there arent any folders at all when you open an app such as androzip or file explorer... Also, when you connect the phone to the pc, it recognizes the phone but theres no "Phone" after I open Computer > HTC One (it used to display a folder with the image of a storage device, like a pendrive, named Phone and under it, it said how much storage space was available... You know, like any other phone, I'm just mentioning it to be as clear and specific as possible). So, being as there is nothing there to open to access all the folders (that also dont exist cause they were deleted), I have no way to copy the rom and flash it again... I tried to sideload it through twrp, nothing... I tried to manually create folders, nothing... I tried the latest RUU and the one that came just before it, nothing on either, they eventually just give an error... So, I'm pretty much stuck with the phone giving systemui and package acces force closes and unable to transfer anything to it... Any thoughts on how to get it back to normal??
Luisit0 said:
So... Sorry if the title is a little misleading, but here goes... Android 5.0.2 and Maximus 50.0.0, no custom kernels or any mods... I gave the phone to a friend and he basically did a factory reset (even tho he really didnt need to...) and it deleted all the apps and stuff, but there was some files under Other in Storage that didnt get deleted, so he had the bright idea to get into recovery (twrp) and do a full wipe (internal, data, system, etc...). So when the phone booted, it gave a SystemUI force close and an Package Access (or something similar) force close too, and there arent any folders at all when you open an app such as androzip or file explorer...
Click to expand...
Click to collapse
It doesn't make sense already.... How can a phone boot in the OS and have a SystemUI force close after wiping the system partition? There is no more system installed on the phone after wiping /system....The phone shouldn't be able to boot at all....Maybe he didn't correctly explained you what he did...
Also, when you connect the phone to the pc, it recognizes the phone but theres no "Phone" after I open Computer > HTC One (it used to display a folder with the image of a storage device, like a pendrive, named Phone and under it, it said how much storage space was available...
Click to expand...
Click to collapse
Only if the phone is correctly(completely) booted in the OS or booted in a custom recovery with MTP support (like newer twrp versions)
I have no way to copy the rom and flash it again... I tried to sideload it through twrp, nothing...
Click to expand...
Click to collapse
Need more precision here:
What happened exactly when trying to sideload?
What rom (name + version)?
What is your adb version (you can find the adb version by typing "adb version" in the command window)?
What is your twrp version?
Also need to know your "fastboot getvar all" (don't post your imei/sn)
I tried the latest RUU and the one that came just before it
Click to expand...
Click to collapse
What versions exactly? Ruu.zip or Ruu.exe?
nothing on either, they eventually just give an error...
Click to expand...
Click to collapse
Need to know what the error was or I can't tell you whats wrong
Any thoughts on how to get it back to normal??
Click to expand...
Click to collapse
Yep, but I need you to answer my questions first :good:
alray said:
It doesn't make sense already.... How can a phone boot in the OS and have a SystemUI force close after wiping the system partition? There is no more system installed on the phone after wiping /system....The phone shouldn't be able to boot at all....Maybe he didn't correctly explained you what he did...
Only if the phone is correctly(completely) booted in the OS or booted in a custom recovery with MTP support (like newer twrp versions)
Need more precision here:
What happened exactly when trying to sideload?
What rom (name + version)?
What is your adb version (you can find the adb version by typing "adb version" in the command window)?
What is your twrp version?
Also need to know your "fastboot getvar all" (don't post your imei/sn)
What versions exactly? Ruu.zip or Ruu.exe?
Need to know what the error was or I can't tell you whats wrong
Yep, but I need you to answer my questions first :good:
Click to expand...
Click to collapse
Sorry he didnt wipe system in recovery, I accidentally included it... He wiped data, caches and internal data. The phone does boot up and everything, but like I said, it gives me a systemui force close as soon as it boots into the home screen, the statusbar is gone aswell as the background, recent apps etc. so systemui is in fact not working, and a few seconds later comes up the package access force close. And as far as sideloading, when i tried to sideload the maximushd 50.0.0 rom it gave me an error saying "error: device not found". I was trying to copy over the same rom it had installed, maximushd 50.0.0 android 5.0.2. My adb version is 1.0.31 and my recovery is twrp 2.7.1.1. The RUU versions I tried where the ones from the RUU thread, the two latest cingular (at&t) ones. The first one was RUU M7 UL K44 SENSE55 MR Cingular US 4.18.502.7 R10 Radio 4T.24.3218.09 10.26.1718.01L Release 356565 Signed 2 (AT&T), but that one stayed at 5% and never continued on. Then I tried the earlier one, RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2, but that one stuck at 3% "Sending" and eventually gave an error saying Error [155] Unknown Error, The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again, and it gave me the option to try and recover but even after recovering it just did the same thing... Finally, here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Sorry I didnt give out some of these basic details before, its been a while since I post anything XD so, any thoughts? I appreciate it btw!
Luisit0 said:
Sorry he didnt wipe system in recovery, I accidentally included it... He wiped data, caches and internal data. The phone does boot up and everything, but like I said, it gives me a systemui force close as soon as it boots into the home screen, the statusbar is gone aswell as the background, recent apps etc. so systemui is in fact not working, and a few seconds later comes up the package access force close. And as far as sideloading, when i tried to sideload the maximushd 50.0.0 rom it gave me an error saying "error: device not found". I was trying to copy over the same rom it had installed, maximushd 50.0.0 android 5.0.2. My adb version is 1.0.31 and my recovery is twrp 2.7.1.1. The RUU versions I tried where the ones from the RUU thread, the two latest cingular (at&t) ones. The first one was RUU M7 UL K44 SENSE55 MR Cingular US 4.18.502.7 R10 Radio 4T.24.3218.09 10.26.1718.01L Release 356565 Signed 2 (AT&T), but that one stayed at 5% and never continued on. Then I tried the earlier one, RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2, but that one stuck at 3% "Sending" and eventually gave an error saying Error [155] Unknown Error, The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again, and it gave me the option to try and recover but even after recovering it just did the same thing... Finally, here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Sorry I didnt give out some of these basic details before, its been a while since I post anything XD so, any thoughts? I appreciate it btw!
Click to expand...
Click to collapse
Ok, no problem.
Imo what you should do is to flash the latest dev edition ruu not at&t. If you flash the at&t ruu, you'll get the at&t bloatware that comes with it and you'll only be able to install ota update if connected to the a&t network. The dev edition is pretty much the same exact thing except you don't need to be connected to at&t for updates and that it doesn't come with carriers bloatware.
Your phone is on hboot 1.60 which makes me believe it was running the unofficial 7.17.401.1 firmware leaked by LlabToFeR? The ruu you did tried (3.xx.502.x and 4.xx.502.x failed because you need to use a ruu.zip if downgrading (or downgrade the hboot version before using an old ruu.exe).
Since your phone is S-OFF this should be really easy to fix.
Run the 7.17.1540.35 Dev edition RUU posted in this thread :http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
then you should receive one ota update to 7.17.1540.51 which is the update pushed yesterday.
alray said:
Ok, no problem.
Imo what you should do is to flash the latest dev edition ruu not at&t. If you flash the at&t ruu, you'll get the at&t bloatware that comes with it and you'll only be able to install ota update if connected to the a&t network. The dev edition is pretty much the same exact thing except you don't need to be connected to at&t for updates and that it doesn't come with carriers bloatware.
Your phone is on hboot 1.60 which makes me believe it was running the unofficial 7.17.401.1 firmware leaked by LlabToFeR? The ruu you did tried (3.xx.502.x and 4.xx.502.x failed because you need to use a ruu.zip if downgrading (or downgrade the hboot version before using an old ruu.exe).
Since your phone is S-OFF this should be really easy to fix.
Run the 7.17.1540.35 Dev edition RUU posted in this thread :http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
then you should receive one ota update to 7.17.1540.51 which is the update pushed yesterday.
Click to expand...
Click to collapse
I see. I was attempting to use the at&t ruu simply because the phone is an at&t one, but also cause I hadnt seen that thread. Thanks for pointing it out! Also, yes it was the firmware from LlabToFeR the one I flashed, if I do recall correctly. As for the .exe, I had forgot about the difference between it and .zip, its been quite a while since I messed around with the M7. I used to flash the hell out of it before lol. Thanks so much for your time and help, I'm downloading the 7.17.1540.35 ruu now. Hope all goes well! I'll let u know :good:
Luisit0 said:
I see. I was attempting to use the at&t ruu simply because the phone is an at&t one, but also cause I hadnt seen that thread. Thanks for pointing it out! Also, yes it was the firmware from LlabToFeR the one I flashed, if I do recall correctly. As for the .exe, I had forgot about the difference between it and .zip, its been quite a while since I messed around with the M7. I used to flash the hell out of it before lol. Thanks so much for your time and help, I'm downloading the 7.17.1540.35 ruu now. Hope all goes well! I'll let u know :good:
Click to expand...
Click to collapse
Hi I'm having the same problem in my HTC One too. Did the above method solve the problem?