[Q] OS system deleted? - One (M7) Q&A, Help & Troubleshooting

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

Related

Wiped OS

First and foremost I would like to apologize for my inability to find my own solution when there are literally a ton of threads like this out there. The answer to my problem is probably staring in my face, I just haven't seen it yet.
I was running the latest Beanstalk build for my Sprint HTC One when I started getting force closes randomly. I decided to return it back to stock, only to find I inadvertently wiped everything.
I have spent the past week pouring over posts, googling things and have hit a brick wall.
I've tried flashing Ruu and it will installed all the way to what looks like 95% and stalls. A reboot only gets me sitting at the HTC white logo screen.
My PC is running windows 8.1 I have access to Fastboot, but ADB doesn't recognize my PC. I've tried installing Ubuntu, but cannot select it at the load screen (sigh).
Side load isn't working either.
I have an older version of Clockworkmod installed on it, but can't do anything with it being that nothing will mount.
S is on also.
HBOOT 1.55.00005
OS 3.05.651.6
version: 0.5
version-bootloader: 1
version-baseband: 1.0
version-cpld: None
version-microp: None
version-main: 3.05.65
version-misc: PVT SHI
serialno:
imei:
meid:
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4305
partition-layout: Gen
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader:
hbootpreupdate: 11
gencheckpt: 0
If someone could help me out with this, I would greatly appreciate it.
Use the RUU found here the first link
http://forum.xda-developers.com/showthread.php?t=2576995
BD619 said:
Use the RUU found here the first link
http://forum.xda-developers.com/showthread.php?t=2576995
Click to expand...
Click to collapse
Downloaded, rebooted RUU and ran installer. The next thing I know I'm not only getting RUU dialog boxes I'm getting ARUWizard dialog boxes prompting me to "click here" to go to the next dialog box, preventing me from interacting with the RUU.
I've never seen this before.
HarveyStyles said:
Downloaded, rebooted RUU and ran installer. The next thing I know I'm not only getting RUU dialog boxes I'm getting ARUWizard dialog boxes prompting me to "click here" to go to the next dialog box, preventing me from interacting with the RUU.
I've never seen this before.
Click to expand...
Click to collapse
Start the RUU from your PC while booted to bootloader,check the boxes click next until it's ready to start and let it do it's thing.
Thank you soo much, it worked like a charm. I guess I was trying the wrong version or something because it wouldn't completely flash before.
Sent from my HTCONE using XDA Premium 4 mobile app
In case anyone else was having this problem, I ran into the dialog box popups during the RUU for ATT Lollipop RUU. I actually had to resort to using an old Kit Kat RUU that I had saved to my computer. Worked like a charm.

[Q] Boots into OS then reboots with com.htc.htc dialer isnt responding

Would it be possible to give me some advice on whats wrong with my HTC ONE. Every time I install a ROM after a few minutes I get "com.htc.htc dialer isnt responding", a few minutes later the device reboots itself. Ive tried locking and unlocking the bootloader, running RUUs (Which when I do i just get the taskbar at the top of the screen nothing else), flashing the latest firmware, and different Kernels, I have completely run out of ideas. any ideas how I can get it working? Ive been trying to fix it since Friday (Up till 4am and all day yesterday, searched for answers all over the place and I just cant fins a solution)
I bought it off ebay and the guy before tried to root it, I thought I could fix it (teaches me for trying to save some money), when I got it it had been rooted and had HBoot 1.55 and ive downgraded it to 1.44, locked and unlocked the bootloader. Kernel is ElementalX-m7-13.5.1 and Radio is Radio_4A.23.3263.28_10.38r.1157.04L and im trying to install the Elegancia_ONE_1.0.0_2 ROM
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 1.29.401.12
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4326mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
Your help would be really appreciated.
langers1 said:
Would it be possible to give me some advice on whats wrong with my HTC ONE. Every time I install a ROM after a few minutes I get "com.htc.htc dialer isnt responding", a few minutes later the device reboots itself. Ive tried locking and unlocking the bootloader, running RUUs (Which when I do i just get the taskbar at the top of the screen nothing else), flashing the latest firmware, and different Kernels, I have completely run out of ideas. any ideas how I can get it working? Ive been trying to fix it since Friday (Up till 4am and all day yesterday, searched for answers all over the place and I just cant fins a solution)
I bought it off ebay and the guy before tried to root it, I thought I could fix it (teaches me for trying to save some money), when I got it it had been rooted and had HBoot 1.55 and ive downgraded it to 1.44, locked and unlocked the bootloader. Kernel is ElementalX-m7-13.5.1 and Radio is Radio_4A.23.3263.28_10.38r.1157.04L and im trying to install the Elegancia_ONE_1.0.0_2 ROM
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.19.3263.13
version-main: 1.29.401.12
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
Your help would be really appreciated.
Click to expand...
Click to collapse
In any booted ROM, if you go to "Settings -> About -> Software information -> More" does baseband show up correctly?
and "Settings -> About -> Phone identity" shows correct IMEI, IMSI?
nkk71 said:
In any booted ROM, if you go to "Settings -> About -> Software information -> More" does baseband show up correctly?
and "Settings -> About -> Phone identity" shows correct IMEI, IMSI?
Click to expand...
Click to collapse
Hi Nkk71
It is saying:
Baseband version - unknown
IMEI - Unknown
IMWI SV - Unknown
Imsi - unavailable
langers1 said:
Hi Nkk71
It is saying:
Baseband version - unknown
IMEI - Unknown
IMWI SV - Unknown
Imsi - unavailable
Click to expand...
Click to collapse
Sorry to be the bearer of bad news , but it's a hardware problem, not fixable via any software method.
nkk71 said:
Sorry to be the bearer of bad news , but it's a hardware problem, not fixable via any software method.
Click to expand...
Click to collapse
Ah poo, thats £180 down the drain . Bet the person on ebay knew the problem to and just passed it onto me.
langers1 said:
Ah poo, thats £180 down the drain . Bet the person on ebay knew the problem to and just passed it onto me.
Click to expand...
Click to collapse
there were two or three similar cases on the Q&A a few weeks ago (dont have the links handy), but nothing worked, tried very hard (even manually flashing the modem partitions), but it was all a no go. the hardware needed to be fixed
langers1 said:
Would it be possible to give me some advice on whats wrong with my HTC ONE. Every time I install a ROM after a few minutes I get "com.htc.htc dialer isnt responding", a few minutes later the device reboots itself. Ive tried locking and unlocking the bootloader, running RUUs (Which when I do i just get the taskbar at the top of the screen nothing else), flashing the latest firmware, and different Kernels, I have completely run out of ideas. any ideas how I can get it working? Ive been trying to fix it since Friday (Up till 4am and all day yesterday, searched for answers all over the place and I just cant fins a solution)
I bought it off ebay and the guy before tried to root it, I thought I could fix it (teaches me for trying to save some money), when I got it it had been rooted and had HBoot 1.55 and ive downgraded it to 1.44, locked and unlocked the bootloader. Kernel is ElementalX-m7-13.5.1 and Radio is Radio_4A.23.3263.28_10.38r.1157.04L and im trying to install the Elegancia_ONE_1.0.0_2 ROM
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 1.29.401.12
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4326mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
Your help would be really appreciated.
Click to expand...
Click to collapse
I am having same issue, happened right after using my phone on a roadtrip for hours, think I overheated it.
It wasn't rooted before, but I figured I would try and fix it myself.
Tried a bunch of different ROMs, and reflashed the firmware, never works okay for more than couple days.
Should have left it stock, and warrantied it out.
MajorDraco said:
I am having same issue, happened right after using my phone on a roadtrip for hours, think I overheated it.
It wasn't rooted before, but I figured I would try and fix it myself.
Tried a bunch of different ROMs, and reflashed the firmware, never works okay for more than couple days.
Should have left it stock, and warrantied it out.
Click to expand...
Click to collapse
try a full ruu.zip or ruu.exe, it has revived some phones, but if the same error creeps up again, then i guess it's a hardware problem.

[Q] no ruu for my phone... And I've lost my baseband and network and IMEI and and and

Wow, let me start by saying I love this site. I've been lurking for years and the info and guides available have helped me root some 10 devices. I've really done it to myself this time, though. I have the m7_wls, but I'm not a sprint customer. My CID is ACG__001 and I go through a little local phone shop.
I rooted this phone like the day after I got it with no issues with HTCdev unlock and S-on. I wasn't really planning on doing the whole S-off thing, but then I flashed an elemental X kernel and fried my carrier and network and baseband information. I don't know where it went. I don't know how to get it back.
Oh, and I restored back to stock Rooted just to try to fix it. That's why I took a backup after all, so I could break my phone with no fear of permanent damage, but lo! The baseband and all that info is still gone and now the phone just reboots every three minutes after it tells me that the dialer isn't responding.
Great. So I managed to get the rebooting thing to quit by flashing a cm11 nightly, but now I'm still left with a phone that isn't a phone. Yay! Anyway, I was thinking I may be able to snag a matching radio out of any old RUU, but now neither Firewater nor rumrunner work. Oh, and sunshine? It's not compatible with cyanogenmod.
Let me paste up my wife's getvar all here right quick We have the same phone, got them a week and a half apart, so they're basically identical so you can see what it SHOULD look like:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 1.01.20.0904_2
version-cpld: None
version-microp: None
version-main: 4.08.510.7
version-misc: PVT SHIP S-ON
serialno: FA4A9S900374
imei: xxxxx
meid: xxxxx
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: ACG__001
battery-status: good
battery-voltage: 3865mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-660ef031
hbootpreupdate: 11
gencheckpt: 0
So, what I'm wondering, is if there's a way to use ADB to pull her ENTIRE phone off of her phone and then push it to mine to get me up and running? Obviously the imei and meid are different, but yeah...
Oh, my name's Andrew, by the way.
Updat
Here's an update, though if anyone wants to verify:
I was poking around in the system/firmware/modems folder and I have nothing in it. Is there supposed to be something in it? My old GS2 doesn't even have this folder. Is it a symlink to the radio partition?
Also, I found that there is a way to actually format corrupted partitions via adb and pushing a mkfs.ext4 file to the phone somewhere... I had to do that to my data partition at one point. I also found that there is a way to pull the partition data into an image file. Do these pulled images still have HTC's signatures on them or is that just a separate thing inside the RUU?
Any news about this cid ACG__001 ?
i also own an ACG__001 , i dont know from which company is
conquesoextra said:
i also own an ACG__001 , i dont know from which company is
Click to expand...
Click to collapse
ACG__001 is most likely C-Spire Wireless (a US cdma carrier). ACG stands for "Associated Carrier Group", C-spire being a member of that group hence why the ACG__001 cid. A ruu is already available in the lollipop collection thread (general section) for that cid.
https://www.cspire.com/
http://www.associatedcarriergroup.com/

[Q] Cannot install any ROM's at all, but can access bootloader.

Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.
Loafmanuk said:
Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.
Click to expand...
Click to collapse
ok first of all, you need to use TWRP latest for Lollipop custom roms, 2.6.3.3 is too old, use 2.8.6.0, also, expect problems with Lollipop roms whilst your still on KitKat firmware (hboot 1.57), you really need to be on Lollipop firmware to use Lollipop custom roms.
People using the latest Lollipop custom roms on KK firmware are reporting no wifi, Bluetooth issues etc.
can you post your fastboot getvar all please without imei and serial number please.
Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.
BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.
Loafmanuk said:
Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.
Click to expand...
Click to collapse
yup shows me a lot of info: 6.16.61.8 this shows me your on Orange UK network, although its now T-Mo & Orange together as EE, sorry but they've not released the Lollipop update yet for the 61's which is the 3rd set of numbers pulled from that long number above, this also confirms your on orange UK ORANG001 and so does this: PN0710000 kind of......... long story
m7_ul this tells me you have the LTE version of the M7
4275mV battery info = good
4T.28.3218.04 radio version
1.57.0000 hboot version
(bootloader) security: on (bootloader) build-mode: SHIP PVT SHIP S-ON basically your s-on
it would show your imei number and serial number too, but you want to keep those 2 numbers to yourself.
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Loafmanuk said:
BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.
Click to expand...
Click to collapse
plug your phone into the computer whilst its booted into recovery main screen only, the internal storage of your phone should open on your computer, copy the rom.zip to your internal storge, unplug and flash it.
I'm pretty sure 2.8.6.0 supports usb otg, you may have to select it as a storage option first as it defaults to internal storage, cant quite remember as I'm on an M8 now.
edit: yes it does, select install and then at the top change from internal storage to usb otg.
I've re installed TWRP 2.8.6.0 and finally got it to see the USB stick (reformatted it). But when I try and install it seems to be going ahead, but after a minute or to I get the TeamWin splash screen flash up as though recovery is booting and it returns to the main menu. Oddly, the LED on the memory stick is still flashing!?!
I'll try installing from the phones internal memory like you suggested and hopefully that will work. Thank you so much for this, I'll update in a while.
Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.
Loafmanuk said:
Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.
Click to expand...
Click to collapse
you are very welcome, I just use my USB OTG for backup's and restores, never tried flashing a rom from it.

****ed up, need help

Hey guys, I'm relatively new to this and my english is pretty bad so sorry in advance but I've tried to fix this for a few hours now and I've only made the situation worse for myself
I found my "old" HTC One M7 a couple of days back so I thought it would be a good idea to root it and play around with xposed framework and some cool modules I heard about. So I managed to unlock the bootloader, flash CWM Recovery and root my phone. No problems so far.
Now, yesterday I wanted to remove xposed framework from my phone so I thought I could just recover from the backup I made in CWM Recovery before I installed the framework. Turns out that was not the greatest of ideas and my phone got stuck on the boot screen.
I didnt think of it like such a big deal and I tried to factory reset and wipe the phone to maybe get it working again. Turns out that was not the greatest idea either and now I cant go into recovery, I can't flash a new recovery and my computer wont recognizes my phone at all (Except for fastboot)
I've installed and uninstalled all drivers I could possibly think of and find and I still cant find a solution to my problem. I tried to flash a RUU but that didnt work either. I can barely do anything with my phone anymore and I can't think of anything else I havent tried. Please help
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.19.401.30
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4129mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
My bootloader shows the Tempered , Relocked and Security Warning flags
deleted
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
vilan22 said:
Hey guys, I'm relatively new to this and my english is pretty bad so sorry in advance but I've tried to fix this for a few hours now and I've only made the situation worse for myself
I found my "old" HTC One M7 a couple of days back so I thought it would be a good idea to root it and play around with xposed framework and some cool modules I heard about. So I managed to unlock the bootloader, flash CWM Recovery and root my phone. No problems so far.
Now, yesterday I wanted to remove xposed framework from my phone so I thought I could just recover from the backup I made in CWM Recovery before I installed the framework. Turns out that was not the greatest of ideas and my phone got stuck on the boot screen.
I didnt think of it like such a big deal and I tried to factory reset and wipe the phone to maybe get it working again. Turns out that was not the greatest idea either and now I cant go into recovery, I can't flash a new recovery and my computer wont recognizes my phone at all (Except for fastboot)
I've installed and uninstalled all drivers I could possibly think of and find and I still cant find a solution to my problem. I tried to flash a RUU but that didnt work either. I can barely do anything with my phone anymore and I can't think of anything else I havent tried. Please help
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.19.401.30
version-misc: PVT SHIP S-ON
serialno: SH36EW905338
imei: 357864055623936
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4129mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
My bootloader shows the Tempered , Relocked and Security Warning flags
Click to expand...
Click to collapse
You need to flash firmware again, search on arhd's website they have all the firmwares and after that ruu will work, I don't remember step by step process but you can always search on google. For RUU to work you need to flash firmware first, its mandatory.
RUU contains the firmware, so there is no need to flash anything except the actual RUU. You problem is relocked bootloader and custom recovery. First thing you need to do is unlock your bootloader again. Then we can talk about other steps to get your phone working again
donkeykong1 said:
RUU contains the firmware, so there is no need to flash anything except the actual RUU. You problem is relocked bootloader and custom recovery. First thing you need to do is unlock your bootloader again. Then we can talk about other steps to get your phone working again
Click to expand...
Click to collapse
Alright, I unlocked the bootloader again. What now?
vilan22 said:
Alright, I unlocked the bootloader again. What now?
Click to expand...
Click to collapse
Now download TWRP recovery and flash it via fastboot
donkeykong1 said:
Now download TWRP recovery and flash it via fastboot
Click to expand...
Click to collapse
Done and working!
vilan22 said:
Done and working!
Click to expand...
Click to collapse
Great! Now, download ARHD ROM, and tranfer the zip to your phone using MTP option in recovery
While you wait, you might want to edit your "fastboot getvar all" and remove your IMEI and serial no [emoji6]
donkeykong1 said:
Great! Now, download ARHD ROM, and tranfer the zip to your phone using MTP option in recovery
While you wait, you might want to edit your "fastboot getvar all" and remove your IMEI and serial no [emoji6]
Click to expand...
Click to collapse
Alright, do I flash the ROM now?
vilan22 said:
Alright, do I flash the ROM now?
Click to expand...
Click to collapse
Yep! Flash away [emoji4]
donkeykong1 said:
Yep! Flash away [emoji4]
Click to expand...
Click to collapse
Flashed successfully and it seems to be working just fine Thanks for the help! Learned alot from this
vilan22 said:
Flashed successfully and it seems to be working just fine Thanks for the help! Learned alot from this
Click to expand...
Click to collapse
Great! Enjoy your phone, and feel free to ask if you need anything [emoji4]

Categories

Resources