Database Develop

One touch on cupcake 1.5 failed

hey guys, i tryed the one clik meth od here:
http://theunlockr.com/2009/08/22/how...-in-one-click/
after everything, when i get to step 12 and reboot my phone (holding home and power) my phone just freezes with the rogers logo up (i need to remove battery to get back).
What can I try next to root my phone? should i first restore my back up image that i made with the program before I do anything else?
I need some help as i really need to root this phone for 2 reasons
1)apps on sd
2)Rogers locked out the touchscreen keyboard

http://forum.xda-developers.com/showthread.php?t=563679
Follow this, if you want CM keep going all the way through, if you want someone else's ROM then flash that instead of CM's.

hey, ok so my latest update is that i got myself to SPL 1.33.2005
i was able to boot into everything that was needed (power + camera) (power + home)
I am now at this step:
http://forum.xda-developers.com/showpost.php?p=4848777&postcount=506
Look at where he posts his info he has:
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.20.17
I have:
DREAM PVT 32B SHIP S-OFF
does it matter that mine says S-OFF

Hold your horses! That isn't the link I gave you to follow... You are in dangerous territory right now... what all have you done, exactly? Flashing that SPL can and will brick your phone if not done right.

I was using the link you gave me, close to the top it says to follow the linked guide for rogers phones as they are done differently(my phone is rogers)
that link leads you to:
http://forum.xda-developers.com/showthread.php?t=558301
once done that it says to go to:
http://forum.xda-developers.com/showpost.php?p=4848777&postcount=506 (never mind i should not use this as his spl is different as well, not the spl gotten from the previous link)
OR
http://forum.xda-developers.com/showthread.php?t=544654
this first one is a relply of the second link (supposedly easyer)
LAST EDIT:
So, should i continue following
http://forum.xda-developers.com/showthread.php?t=544654

Ok, carry on! As long as your reasd twice and do once you should be ok. And don't worry about the 'on' vs 'off', the big concern is what board do you have, and you have the 32b PVT, which is the one you need. I believe that 'on' 'off' is in regards to carrier lock.

like i edited, the first link guy does not have the SPL that I now have, i will be following the final link
http://forum.xda-developers.com/showthread.php?t=544654
When it says:
"once you are at SPL 1.33.2005 (AND ONLY THEN)
download this (it is hyperlinked)
(md5: 4a58a5702fdf899547011888d9cc066f .. sha1: 99e38e4f8798e952e67421a42e7b053ea70957b7)
extract both images wherever you'd like."
does it mean extract whereever on the sd?

I would assume extract and place on the root of the SD card based off the fact you will be doing all this from fastboot, aka the phone itself.

alright so i did that stuff, now when i boot the phone hangs at the rogers logo, what should i try.

did make a nandorid back up in the recovery menu a little while ago, how an i use it to go back? or is there another option to do something?
I can still boot into the recovery menu and camera+ power menu

Can you get into recovery? First boots take a long time as well, how long has it been hung up? But it sounds like you don't have a ROM on the device currently.

I can get into recovery, It was hung for like 4-5 minutes before i reset it. I dont think i did the fastboot stuf right, I pressed send inorder to fastboot, it said fastboot and i started typing the stuff on the link (you cannot see anything i was just typing) i then rebooted to recovery and Alt+s applyed the update (cynogen).
it is hung at the rogers screen. Can you try and translate the link
http://forum.xda-developers.com/showthread.php?t=544654
a bit better and i can try the fast boot part again?
In the guide it says press back arrow to get inot fast boot but on my screen there is only one option for fastboot and it is the send button.

I tryed to use the update.zip file again but this time it said that it could not mount and that the directory does not exist.

It sounds like you did do the fastboot right, actually, since if you didn't it would boot up fully...
I would try this, dl this rom and put it on the root of your sd card, then boot into recovery mode and select "flash any .zip update" or whatever the exact wording is, then select the file named "dwang-v1.15" and follow the onscreen prompts. It is also probably a good idea to get your phone on a charger sometime soon, wouldn't be surprised if the battery is getting close to dead since when in fast boot and recovery and during boot up itself battery drain is pretty quick.
I truly think you did the fastboot stuff right, since when done you should have the SPL and radio, recovery, but no ROM and need to boot into recovery and flash the new ROM.
Forgot to give the link to the ROM, it is dwang's, my personal favorite and a good starting point to work from:
http://forum.xda-developers.com/showthread.php?t=567023

the option is apply update.zip so i should probably change the file name to that. Ill give it a go.

its still hanging on the rogers icon, weird. Perhaps i should use the nandoid backup? if you agree that that is the best option how would i do that?
another note, when i tryed to flash the rom you gave me it did not let me, game a an error about mounting and cannot find a file, I then put the recovery images back onto the sd card and the operation worked this time, it was unpackin na extracting and everything. Now it is still hung.

I would probably just nandroid at this point, yes

can ou guide me on how to do that?

Hmmmmmmm, do this for me as well, boot into boot loader (camera+power) and tell me what it says on the screen.

DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA21000)
CPLD-4
RADIO-3.22.20.17
Apr 20 2009, 15:30:43
HBOOT
<SEND> Fastboot Mode

[Q] To start anew!

So I've been using CM 6.0 for a while now, and recently my phone has begun getting worse and worse. It's now down to only lasting about 8 hours, and stops sending text messages several times every day (requiring a power down, and turn off). Not to mention when I power off my phone, it turns right back on again.
As you can tell it's been quite frustrating. I think my real problems began a few months ago when my phone wouldnt turn on. It was fully charged and everything but it wouldnt get past the "Rogers" boot screen (this is on a Rogers HTC Dream). Luckily I was able to boot into recovery and flash CM 6.1.0. It was a messy flash, as it didn't wipe anything but it did get my phone working. So my phones just been getting progressively ****tier since then. And now i can't even get into the recovery mode, or install Clockwork Mod.
So basically what I'm asking here is if anyone can point me in the direction of a guide to FULLY wipe my phone, and update my SPL/Drivers/Radio/Recovery Image/etc to the latest/most stable, and to do a clean install of CM 6(or 7).
Thanks.

I think this will work for you to get all of that but the cm6/7. Although i assume you know where to find that at.
http://forum.xda-developers.com/showthread.php?t=831139

Thanks for the response, I will do my best to follow this guide.
First small problem I ran into though.
My SPL:
-Which is the newest/best SPL to work with?
-and how do I check which one I have? If i remember correctly it needs to be checked through the recovery console, which I dont have access too :S
Help?
Thanks.

Can u get into fastboot? That's where u get your info
Sent from my HTC Magic using XDA App

johnson8cyl said:
Can u get into fastboot? That's where u get your info
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Yes, here is what I see:
=========================
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA21000)
CPLD-4
RADIO-3.22.26.17
Apr 20 2009, 15:30:43
=========================
//(^In green text). Then I see:
=========================
HBOOT
<SEND> FastBoot Mode
=========================
//And then if I click the <SEND> button, I see
=========================
FASTBOOT
<CAMERA STEP2> HBoot Mode
<BACK> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
=========================
//So yeah, that's the info I have. As I said I can't get into my Recovery. My goal is to update my phone to the latest and greatest, and do a full clean wipe and a fresh install of CM6/CM7. So what files should I be updating to return my phone to fixable state?

Well you see Send-fastboot. You can get into fastboot. That is bootloader mode. Now you can download the recovery of your choice and go on to flashing a rom.
This will give you step by step on how to get the newest recovery radio/spl all through fastboot mode. Then you can flash your rom in the recovery you just flashed. http://forum.xda-developers.com/showthread.php?t=831139

[Q] Full reboot loop?

Hi,
My One M7 is stuck in a sort of boot loop. I've had boot loops on other phones when flashing etc. but this is different to any I've had before. My phone is rooted with unlocked bootloader but it is still running stock 4.3. I've never flashed a ROM on this phone. As stated, I've had boot loops on other phones where it tries to boot but doesn't fully boot before it restarts and I assume that's the same with a HTC One. The problem I have is when the phone has fully booted, it then restarts itself after around 10 seconds. It is as if the power button is stuck so it turns itself of then on again endlessly. I can fully press the power button and feel the little click so I assume it isn't stuck. I can't think of any reason it would be doing this. I assume it will just keep looping until it is out of battery.
Any help is appreciated, thanks,
Oli.
PS. I can get into recovery fine.

perceptic said:
Hi,
My One M7 is stuck in a sort of boot loop. I've had boot loops on other phones when flashing etc. but this is different to any I've had before. My phone is rooted with unlocked bootloader but it is still running stock 4.3. I've never flashed a ROM on this phone. As stated, I've had boot loops on other phones where it tries to boot but doesn't fully boot before it restarts and I assume that's the same with a HTC One. The problem I have is when the phone has fully booted, it then restarts itself after around 10 seconds. It is as if the power button is stuck so it turns itself of then on again endlessly. I can fully press the power button and feel the little click so I assume it isn't stuck. I can't think of any reason it would be doing this. I assume it will just keep looping until it is out of battery.
Any help is appreciated, thanks,
Oli.
PS. I can get into recovery fine.
Click to expand...
Click to collapse
I am having the same problem. Please keep this forum up to date because I would like a solution as well.
I would like to try a fcatory reset. But first I would like to find a way to back up all the files on my phone.
If anyone has an idea on how to back up all the stuff on my phone before i reset it, please let me know.

Bump!

I'm not sure if my issue is the same. But I have a very very similar one!
I am running stock kitkat, unlocked, rooted. Have been for a few months now without issue.
Yesterday my phone died, so i charged it while it was off (thought it might charge faster) for a couple hours. I figured it should be close to full but noticed it was only 20% charged. So when I turned it on, i get all the way booted, and can use the launcher for maybe 20-40 seconds before it reboots.
i do get a small amount of time to play on the phone each loop. ive noticed that im not getting or sending any sms (says 4 bars and 4g, but nothing going through).
i can also get into cwm recovery and fastboot so i have some options there.
what are my options? id like to not have to lose everything (i have titanium backups.....but they're on the sd card so a wipe would delete my backups)

I am in the same situation.
Unlocked and rooted
Stock HTC One Sense - no ROMs flashed
CWM Recovery
Kitkat 4.4.2
Sense 5.5
hboot 1.56
software number 4.18.502.7
kernel 3.4 10-ge12f77e
CID CW__001
AT&T
This all started for me back when I tried to restore a CWM nandroid backup. I was able to restore the backup but afterwards, the reboot loop started. If I factory reset the phone from recovery and cleared the cache and davlink I was able to reconfigure my phone and get it back up and running but if I reboot the phone, the reboot loop starts over again.
I can't even return it to stock since I can't S-Off using firewater or rumrunner or anything else in order to run RUU. So basically I am stuck with a phone that I have to reconfigure if I reboot it which causes the reboot loop to start.
Any help would be greatly appreciated!

perceptic said:
Hi,
My One M7 is stuck in a sort of boot loop. I've had boot loops on other phones when flashing etc. but this is different to any I've had before. My phone is rooted with unlocked bootloader but it is still running stock 4.3. I've never flashed a ROM on this phone. As stated, I've had boot loops on other phones where it tries to boot but doesn't fully boot before it restarts and I assume that's the same with a HTC One. The problem I have is when the phone has fully booted, it then restarts itself after around 10 seconds. It is as if the power button is stuck so it turns itself of then on again endlessly. I can fully press the power button and feel the little click so I assume it isn't stuck. I can't think of any reason it would be doing this. I assume it will just keep looping until it is out of battery.
Any help is appreciated, thanks,
Oli.
PS. I can get into recovery fine.
Click to expand...
Click to collapse
Try powering off from the bootloader or hold power + volume up till the phone shuts off. have you installed anything that would have maybe caused it ?
you could try and flash the stock recovery back to the phone and do a factory reset and then flash TWRP 2.6.3.3 and see how that goes
ibarazi said:
I am having the same problem. Please keep this forum up to date because I would like a solution as well.
I would like to try a fcatory reset. But first I would like to find a way to back up all the files on my phone.
If anyone has an idea on how to back up all the stuff on my phone before i reset it, please let me know.
Click to expand...
Click to collapse
read above ..no 2 phones are the same... I need more info like you version of recovery / rom / updates installed / android version / fastboot getvar all / bootloader screen shot
VM0824 said:
I'm not sure if my issue is the same. But I have a very very similar one!
I am running stock kitkat, unlocked, rooted. Have been for a few months now without issue.
Yesterday my phone died, so i charged it while it was off (thought it might charge faster) for a couple hours. I figured it should be close to full but noticed it was only 20% charged. So when I turned it on, i get all the way booted, and can use the launcher for maybe 20-40 seconds before it reboots.
i do get a small amount of time to play on the phone each loop. ive noticed that im not getting or sending any sms (says 4 bars and 4g, but nothing going through).
i can also get into cwm recovery and fastboot so i have some options there.
what are my options? id like to not have to lose everything (i have titanium backups.....but they're on the sd card so a wipe would delete my backups)
Click to expand...
Click to collapse
read above and list the same things I ask them
Houtex2k said:
I am in the same situation.
Unlocked and rooted
Stock HTC One Sense - no ROMs flashed
CWM Recovery
Kitkat 4.4.2
Sense 5.5
hboot 1.56
software number 4.18.502.7
kernel 3.4 10-ge12f77e
CID CW__001
AT&T
This all started for me back when I tried to restore a CWM nandroid backup. I was able to restore the backup but afterwards, the reboot loop started. If I factory reset the phone from recovery and cleared the cache and davlink I was able to reconfigure my phone and get it back up and running but if I reboot the phone, the reboot loop starts over again.
I can't even return it to stock since I can't S-Off using firewater or rumrunner or anything else in order to run RUU. So basically I am stuck with a phone that I have to reconfigure if I reboot it which causes the reboot loop to start.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
same here .. read above and list all the things I ask above
you can also try my guru reset posted here >> http://forum.xda-developers.com/showthread.php?t=2775650

Well my One just fixed itself . I was JUST about to do a factory reset and, when my phone turned itself on, I heard loads of buzzing. Well, turned out it was all my notifications and as VM0824 said, signal wasn't working. I waited a couple of minutes then sighed hugely in relief haha.
Good luck to everyone else in sorting the problem out :good:
Oli.

Android 4.4.2
HTC Sense 5.5
Software number 4.18.502.7
HTC SDK API Level 5.68
Kernel 3.4.10-ge12f77e
I used cwm to factory reset. It seems to work fine now. BUT, if I restore all system and user app + data from titanium backup, then the issues comes back.
So I did another factory reset, and this time only installed missing app+data. It will take me some time to get my stuff back the way it was, but its working.
Now I have a new symptom though, apparently I have space issues???
1. Using Lucky Patcher, I ran into an issue trying to patch titanium backup. As it was doing the step involving creating the .odex, it told me it could not create the .odex or something like that. As if there was no room. I deleted some stuff from my SD card (even though it indicated 18gb free space in the data manager) and it worked.
2. I installed dropbox as my first thing since the reset since I store some apps there. I have an old version of swype (the new ones have been laggy) that I tried to install and it says "storage full or unavailable" when I click it in Dropbox.
Now the data manager indicates i have more than 18gb left....yet i cant find room for swype? I wonder if my storage is going bad? i imagine if there's write contention or i lost access to certain storage, that could cause a crash and reboot (hence the boot loop).
so how do i diagnose if there is an issue with my storage?

VM0824 said:
Android 4.4.2
HTC Sense 5.5
Software number 4.18.502.7
HTC SDK API Level 5.68
Kernel 3.4.10-ge12f77e
so how do i diagnose if there is an issue with my storage?
Click to expand...
Click to collapse
so your using a patched version of titanium and your trying to restore your data with it? Dude pay for the app if it's that useful to you... piracy is not acceptable here, look for help elseware.

Info from Recovery and Fastboot Getvar all
**** TAMPERED ****
**** ULOCKED ****
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3218.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014,09:32:41.0
C:\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT**********
(bootloader) imei: *************
(bootloader) meid :************
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3915mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
recovery-clockwork-touch-6.0.4.8-m7
Now that I've done the fastboot getvar all command and rebooted the phone I am stuck in a reboot loop and will have to factory reset and start over. Any help would be appreciated and thanks for your time.

i have the same problem with my one , first in android 4.3 starting auto-restart and then after a flashing 4.4.2(4.19.401.9) the signal is out of range and imei and base band are unkonwn
i update to 4.19.401.11 and didn't change after all
i really confused , please help me , my hboot is 1.56 and i didn't s-off or unlock yet

I did a factory reset and it seemed to fix the problem with one hitch. you can never let the phone die.
i have had this running for a few weeks now and as long as i make sure the battery doesnt die, then the phone wont start boot looping. last night it died -_-
i couldnt even get a light to come on and had to use a trick from another post about holding power + volume + bright light on sensor to even get it to charge. but now that its charging and I turned it on, boot loop again.
i guess ill do another factory reset and be more careful to never let the battery die......until im eligible for an upgrade lol.

cyanogenmod keeps crashing / restarting

I have the AT&T HTC Vivid and am trying to install cyanogenmod on it and it keeps restarting when cyanogenmod loads
I have tried the regular tutorial as well as:
http://forum.xda-developers.com/showthread.php?p=20795908
I have the HTC unlock, s-on.
I tried both clockwork recovery and wcxrecovery
I was able to flash cyanogenmod 'cm-10-20131006-NIGHTLY-holiday.zip'
Installed in recovery, and then flashed the boot.img in fastboot (tried alternating the order)
cleared cache / factory reset / dalvik cache
Still it will only get to the first screen then restarts. First boot will get it to language selection and then as soon as a selection is made, it restarts.
I have searched a lot, but most of the results are for the problem of the recovery stuck when starting (which I fixed with the unlock), or with it never getting past boot screen.
Thanks for any help you can offer.

Cleared the data again including /system and it will get to the home screen, but if I try to do anything it freezes and reboots, and now is bootlooping, and no longer gets to the home screen.

georgecoffey said:
Cleared the data again including /system and it will get to the home screen, but if I try to do anything it freezes and reboots, and now is bootlooping, and no longer gets to the home screen.
Click to expand...
Click to collapse
Sounds like you need to do an RUU from gingerbread to ICS...
If you're on vodaphone... You'll prolly need to s-off... So you can use supercid and then use another carriers ICS RUU so you have the newer hboot...
Sent from my Vivid 4G using Tapatalk

Hi, I have the same problem but I have the bootloader as it should be (i think)
=JuopunutBear=
HOLIDAY PVT SHIP S-OFF RL
HBOOT-1.85.2525
eMMC-boot
I tryied so many ROMs that i don't know what else to do...
Can any one help me????? Please...

godzec said:
Hi, I have the same problem but I have the bootloader as it should be (i think)
=JuopunutBear=
HOLIDAY PVT SHIP S-OFF RL
HBOOT-1.85.2525
eMMC-boot
I tryied so many ROMs that i don't know what else to do...
Can any one help me????? Please...
Click to expand...
Click to collapse
Recovery version?

Soft bricked?

Hey guys, I think I've soft bricked my device all the way to hell and back.
So I was running Nocturnals GPE ROM and something screwed up and I was left with no service for the whole day. I came home to find that it was an issue which happened on the latest version of the ROM where if you flash anything it screws with the radio (even though I'm pretty sure I didn't flash anything in between my sending a text before getting in my car and getting out, but... whatever). So I went home and tried flashing all different radios- 1180, 0155 (or whatever it is) on TWRP 2.6, 2.7, and 2.8. No dice- same thing every time (no baseband, phone basically knows nothing about itself except its serial number). I then tried flashing ViperOne after wiping the phone (which TWRP didn't even do, I still had my SD Card items, but it said it did it so I trusted it). That booted up to an HTC Logo and a status bar with still no service. So I did a factory reset and wiped again, flashed the GPE ROM (because it actually booted to a usable interface) and went to bed, figuring I'd deal with it tomorrow afternoon and deal with another day without service and school wifi restrictions.
So I came home today and tried to flash an RUU. I'm now on 0904 radios with no recovery and nothing to boot into. Booting normally or rebooting through fastboot gets me into a bootloop with just an HTC Screen. Flashing a recovery via fastboot will say it flashed, but trying to get into recovery will again bootloop it, but this time, on the first loop of the bootloop, it will have the "Entering recovery..." message at the top. I then tried to flash clockwork to try to install anything, and to my surprise, it booted! I then did a full wipe to try to install a new ROM, but then after wiping and rebooting to try to push something via fastboot, I could not get into clockwork again.
At this point I tried to use the RUU.exe for the phone. After freezing my computer and taking 10 minutes to load, it said there was an error and that the phone wasn't connected. I'm assuming this is because I was in the bootloader, not in an OS. So I've now been sitting here trying to get anything to flash and boot, but I keep getting bootlooped.
I'm now just sitting in the bootloader trying to think of a solution, but I'm out of ideas. Anyone got anything?
Bootloader looks as follows:
*** UNLOCKED ***
M7_WLS PVT SIP S-OFF RH
CID-SPCS_001
HBOOT-1.57.0000
RADIO-1.01.20.0904_2
OpenDSP-v31.120.274.0617
OS-1.11.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42.0
I'm probably going to take it to Sprint tomorrow and see if they can do anything, and if not, let me place a hold on a Nexus 6 since it's going to be less money on contract allegedly. But until then, I'm hoping I can get this figured out.
Thanks for any help you guys can provide!
EDIT: I got TWRP to run on the phone! I guess it must have been a bad download that I was using or something. Now downloading stock and I'm going to Xposed the balls out of it to make it near stock, since I want to have as close to GPE as possible.
EDIT 2: So I got into TWRP- The adb sideload didn't work. Actually- it worked once, but once it got to 100%, it said the file was corrupt then deleted it. So I went back into TWRP and after several tries, could not get it to work again. So I go to try my OTG cable. I tried flashing a completely stock ROM and it got almost all the way, then said "could not find /data, could not find /system, could not find /cache, could not find internal memory". This makes me believe that the phone has literally no other files on it other than TWRP. So I tried to find some way to get those files, and that managed to lead me to flash the boot.img for the phone. Now it booted up and has been stuck at the HTC boot screen with the "powered by Android" logo at the bottom and the red text. I've held down volume down + power for 5 minutes and it did nothing; the lights just kept flashing. I'm going to take it to Sprint tomorrow and say I was trying to get it back to stock and the RUU screwed it up. Sprint is supposedly pretty cool about mods and rooting, so hopefully they can help me out.

Bseagull said:
Hey guys, I think I've soft bricked my device all the way to hell and back.
So I was running Nocturnals GPE ROM and something screwed up and I was left with no service for the whole day. I came home to find that it was an issue which happened on the latest version of the ROM where if you flash anything it screws with the radio (even though I'm pretty sure I didn't flash anything in between my sending a text before getting in my car and getting out, but... whatever). So I went home and tried flashing all different radios- 1180, 0155 (or whatever it is) on TWRP 2.6, 2.7, and 2.8. No dice- same thing every time (no baseband, phone basically knows nothing about itself except its serial number). I then tried flashing ViperOne after wiping the phone (which TWRP didn't even do, I still had my SD Card items, but it said it did it so I trusted it). That booted up to an HTC Logo and a status bar with still no service. So I did a factory reset and wiped again, flashed the GPE ROM (because it actually booted to a usable interface) and went to bed, figuring I'd deal with it tomorrow afternoon and deal with another day without service and school wifi restrictions.
So I came home today and tried to flash an RUU. I'm now on 0904 radios with no recovery and nothing to boot into. Booting normally or rebooting through fastboot gets me into a bootloop with just an HTC Screen. Flashing a recovery via fastboot will say it flashed, but trying to get into recovery will again bootloop it, but this time, on the first loop of the bootloop, it will have the "Entering recovery..." message at the top. I then tried to flash clockwork to try to install anything, and to my surprise, it booted! I then did a full wipe to try to install a new ROM, but then after wiping and rebooting to try to push something via fastboot, I could not get into clockwork again.
At this point I tried to use the RUU.exe for the phone. After freezing my computer and taking 10 minutes to load, it said there was an error and that the phone wasn't connected. I'm assuming this is because I was in the bootloader, not in an OS. So I've now been sitting here trying to get anything to flash and boot, but I keep getting bootlooped.
I'm now just sitting in the bootloader trying to think of a solution, but I'm out of ideas. Anyone got anything?
Bootloader looks as follows:
*** UNLOCKED ***
M7_WLS PVT SIP S-OFF RH
CID-SPCS_001
HBOOT-1.57.0000
RADIO-1.01.20.0904_2
OpenDSP-v31.120.274.0617
OS-1.11.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42.0
I'm probably going to take it to Sprint tomorrow and see if they can do anything, and if not, let me place a hold on a Nexus 6 since it's going to be less money on contract allegedly. But until then, I'm hoping I can get this figured out.
Thanks for any help you guys can provide!
EDIT: I got TWRP to run on the phone! I guess it must have been a bad download that I was using or something. Now downloading stock and I'm going to Xposed the balls out of it to make it near stock, since I want to have as close to GPE as possible.
EDIT 2: So I got into TWRP- The adb sideload didn't work. Actually- it worked once, but once it got to 100%, it said the file was corrupt then deleted it. So I went back into TWRP and after several tries, could not get it to work again. So I go to try my OTG cable. I tried flashing a completely stock ROM and it got almost all the way, then said "could not find /data, could not find /system, could not find /cache, could not find internal memory". This makes me believe that the phone has literally no other files on it other than TWRP. So I tried to find some way to get those files, and that managed to lead me to flash the boot.img for the phone. Now it booted up and has been stuck at the HTC boot screen with the "powered by Android" logo at the bottom and the red text. I've held down volume down + power for 5 minutes and it did nothing; the lights just kept flashing. I'm going to take it to Sprint tomorrow and say I was trying to get it back to stock and the RUU screwed it up. Sprint is supposedly pretty cool about mods and rooting, so hopefully they can help me out.
Click to expand...
Click to collapse
Try the command fastboot erase cache then reboot into twrp and reflash rom
Sent from my HTCONE using Tapatalk

thicklizard said:
Try the command fastboot erase cache then reboot into twrp and reflash rom
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Oh man, I can't tell you how many times I did that. I also ended up flashing a stock ROM. Then, it would boot, but after booting, be stuck on an uninteractive HTC logo screen. In order to do anything, I had to unplug it to get the critical better warning, then click more info, allowing me into the settings app. That really got me no information, so I ended up just giving up and trying to get it back to as close to stock as possible. I was able to get rid of the tampered notification and the red warning text, but I couldn't get the Superuser to work, so I had to live with it not being fully locked and settle for it saying "relocked". The I went back to S-ON, factory reset, then brought it back to Sprint.
They said it was water damage.
***** please.
However, that meant I could take to to geek squad with that excuse because we have their insurance plan (which covers water damage!) and they didn't even bother checking. So now I'm using my old Galaxy Epic 4G running 2.3.6 until a new phone ships in.
The worst part of it all is that my dbrands aren't sticky anymore, so I'll have to use the phone naked until February when I get a Nexus 6. I bonded with those dBrands for over a year. They were the life of my phone!
At least I'll get a new set of headphones, which I conveniently broke the same day I lost service.