Database Develop

Can someone clear a few things up for me?

I'm pretty new to rooting and flashing. My bionic is my first android or smart phone at all for that matter. A couple weeks ago I rooted and flashed r3blurr3d 1.7 and have been running that pretty happily. I want to flash the new SHIFT3R base and one of the PAX but a couple things have me extremely confused.
According to my phone information I am running system version 5.5.892. I'm reading all these posts about the radio and kernel upgrades and that forever root is needed and such and clearly i'm missing something. Do I need to flash back to stock and do OTA updates before moving forward with SHIFT3R and such? I've been looking for a step by step on what to do to get my phone up to date AND running one of these ROMS but im really freaking confused.
I sound like a huge noob to this and I am. Just looking for some guidance.
EDIT: What I think I understand is I need to flash to go back to stock 5.886, flash 7.893, and proceed from there. Is that correct?

Essem said:
I'm pretty new to rooting and flashing. My bionic is my first android or smart phone at all for that matter. A couple weeks ago I rooted and flashed r3blurr3d 1.7 and have been running that pretty happily. I want to flash the new SHIFT3R base and one of the PAX but a couple things have me extremely confused.
According to my phone information I am running system version 5.5.892. I'm reading all these posts about the radio and kernel upgrades and that forever root is needed and such and clearly i'm missing something. Do I need to flash back to stock and do OTA updates before moving forward with SHIFT3R and such? I've been looking for a step by step on what to do to get my phone up to date AND running one of these ROMS but im really freaking confused.
I sound like a huge noob to this and I am. Just looking for some guidance.
EDIT: What I think I understand is I need to flash to go back to stock 5.886, flash 7.893, and proceed from there. Is that correct?
Click to expand...
Click to collapse
Good questions and its always better to ask first and thought a noob, than to come back here looking for info on how to fix a brick.
Alot of people here have great information. However, take the time to understand root and flashing before you go too much further. Root sounds scary but really isn't. Flashing sounds dangerous but really isn't....if you know what you're doing and not do anything you're unsure of.
take the time to read the FAQ's about rooting and flashing. Understand Recovery. know what Kernel and baseband mean. It won't take long. There's a decent FAQ about How to Root in this sub forum. Over in the DEV forum, there are a couple of threads about how to do this.
You do NOT need a new kernel to flash...though a ROM may come with one or require it.
you should understand Recovery before flashing. This is a MUST.
Make your backups. With Recovery and backups, you almost always have a way home.
And absolutely, no matter how stupid it sounds, ASK THOSE QUESTIONS.
I'm new to Bionic so I can't help you with details about this phone, yet. However, I'm not new to Android and I'm not new to Rooting for Flashing. It sounds like you know enough to get in trouble. So, go back to those FAQ,s and understand the basics now, you won't have problems later.
good luck.

alodar1 said:
Good questions and its always better to ask first and thought a noob, than to come back here looking for info on how to fix a brick.
Alot of people here have great information. However, take the time to understand root and flashing before you go too much further. Root sounds scary but really isn't. Flashing sounds dangerous but really isn't....if you know what you're doing and not do anything you're unsure of.
take the time to read the FAQ's about rooting and flashing. Understand Recovery. know what Kernel and baseband mean. It won't take long. There's a decent FAQ about How to Root in this sub forum. Over in the DEV forum, there are a couple of threads about how to do this.
You do NOT need a new kernel to flash...though a ROM may come with one or require it.
you should understand Recovery before flashing. This is a MUST.
Make your backups. With Recovery and backups, you almost always have a way home.
And absolutely, no matter how stupid it sounds, ASK THOSE QUESTIONS.
I'm new to Bionic so I can't help you with details about this phone, yet. However, I'm not new to Android and I'm not new to Rooting for Flashing. It sounds like you know enough to get in trouble. So, go back to those FAQ,s and understand the basics now, you won't have problems later.
good luck.
Click to expand...
Click to collapse
I figured out my bionic specific question but thanks so much for the advice. When you talk about backups I hear about nandroid backups and thats something I haven't done, is that what everyone does and what I should be doing? If so, what does a nandroid backup do for me and when should I backup?

Essem said:
I figured out my bionic specific question but thanks so much for the advice. When you talk about backups I hear about nandroid backups and thats something I haven't done, is that what everyone does and what I should be doing? If so, what does a nandroid backup do for me and when should I backup?
Click to expand...
Click to collapse
Nandroid backup is done through clockwork recovery (CWR aka CWM).
It backs up your entire system exactly as it is so if you ever mess something up, you can just restore that backup and your phone will come out exactly how it was when you made that backup (system settings, apps, preferences, SMS/MMS, everything)

Essem said:
I figured out my bionic specific question but thanks so much for the advice. When you talk about backups I hear about nandroid backups and thats something I haven't done, is that what everyone does and what I should be doing? If so, what does a nandroid backup do for me and when should I backup?
Click to expand...
Click to collapse
As Tivo explained, its Clockwork Recovery. If you do not have this installed, it should be your next step. With CWR you create the nandoids mentioned before. These are your lifeline in case of a bad flash. You can always go backwards if you have them.
I'm surprised you've rooted and flashed with out having a custom recovery installed. In most root instructions, recovery is almost always mentioned up front.
---------- Post added at 02:13 PM ---------- Previous post was at 02:02 PM ----------
Essem said:
I figured out my bionic specific question but thanks so much for the advice. When you talk about backups I hear about nandroid backups and thats something I haven't done, is that what everyone does and what I should be doing? If so, what does a nandroid backup do for me and when should I backup?
Click to expand...
Click to collapse
alodar1 said:
As Tivo explained, its Clockwork Recovery. If you do not have this installed, it should be your next step. With CWR you create the nandoids mentioned before. These are your lifeline in case of a bad flash. You can always go backwards if you have them.
I'm surprised you've rooted and flashed with out having a custom recovery installed. In most root instructions, recovery is almost always mentioned up front.
Click to expand...
Click to collapse
Here's a link to the Recovery info and how to use the recovery and make the backups

[Q]Any Tutorials for Locking, Unrooting?

I need to put the phone back to "normal" for a warranty replacement. Any tutorials I can follow?
Thanks
I already have a nandroid backup of my old carrier ROM. I want to basically flash and with a stock recovery as well.

G-Bus said:
I need to put the phone back to "normal" for a warranty replacement. Any tutorials I can follow?
Thanks
I already have a nandroid backup of my old carrier ROM. I want to basically flash and with a stock recovery as well.
Click to expand...
Click to collapse
look in the Development section you will see it there.

I remember seeing it a while ago but I can't freeking find it right now... Been going thru it for the past 45 minutes. Care to post a link please? you know when you look for something its right in your face and you cant see it....
I found the all in one tool kit, so I'll try that hopefully it works...

G-Bus said:
I remember seeing it a while ago but I can't freeking find it right now... Been going thru it for the past 45 minutes. Care to post a link please? you know when you look for something its right in your face and you cant see it....
I found the all in one tool kit, so I'll try that hopefully it works...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2183942

HTC One Bricked?

Ok so I recently rooted my HTC One and I think I might've bricked my phone. I tried out the Renovate ROM (I think it was the latest version) and it didn't work somehow, and my phone was stuck in boot, so I went into recovery, and factory reset but I accidently checked the button for system and then my OS was deleted. To fix that, I adb pushed Insert Coin ROM and flashed that, but when I booted my phone, it started up fine, but then after 10 seconds or so, the phone would just freeze and then reboot. I went back into recovery adb pushed the stock Sprint HTC One ROM and flashed that and the same thing is happening, but this time, when the phone turns on, it just shows a black screen with the notification bar at the top, and I can't use it in any way. It also freezes and reboots after like 10 second.
TL: DR
My Sprint HTC One keeps on freezing then rebooting after ten seconds, no matter what ROM I try.
Thanks in advance.

Yea....you understand you cant install gsm htc one roms. Thats what you did. Go download a ruu and run it while your in bootloader as i see adb is working for you
Sent from my HTCONE using xda premium
---------- Post added at 12:09 PM ---------- Previous post was at 11:57 AM ----------
Also no ur not bricked. A hard brick means the phone cant even power on. Its a brick. Unusable.
Sent from my HTCONE using xda premium

HTC_M7 said:
Yea....you understand you cant install gsm htc one roms. Thats what you did. Go download a ruu and run it while your in bootloader as i see adb is working for you
Sent from my HTCONE using xda premium
---------- Post added at 12:09 PM ---------- Previous post was at 11:57 AM ----------
Also no ur not bricked. A hard brick means the phone cant even power on. Its a brick. Unusable.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I believe I have done the same thing as I am very new to this. Is there a link or something to find this ruu? and doesn't it need to be a certain one?
Like my phone is a Sprint HTC One. I am stuck in a boot loop and no matter what ROM I try it just keeps rebooting? Please any help would be greatly appreciated!

Check this thread for the RUU and instructions
http://forum.xda-developers.com/showthread.php?t=2250904

Khilbron said:
Check this thread for the RUU and instructions
http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!

Knixson said:
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin
GSM is the AT&T, T-mobile & international models....Sprint & Verizon are CDMA

O.M.J said:
fastboot flash unlocktoken Unlock_code.bin
GSM is the AT&T, T-mobile & international models....Sprint & Verizon are CDMA
Click to expand...
Click to collapse
Thank you! would I also need to install the open recovery twrp to gain root access as well?

Knixson said:
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Click to expand...
Click to collapse
You need to follow the dev instructions. If I were you though, I wouldn't do anything more until you understand some of the risks involved. A phone is a really, really inconvenient thing to have incapacitated when you're learning how to flash. For one, your device wasn't bricked (completely nonresponsive to input); for another, dev instructions are going to tell you to use fastboot (or a toolkit that runs fastboot for you).
Before you start again, you should learn how to use fastboot at the very least, and if you can, adb install/sideload (although it seems you tried that based on the OP). fastboot is often the only thing working if a flash goes awry.
A ROM is a ROM, no matter what device it's for. GSM/CDMA are separate network technologies that power your phone. In the U.S., Sprint and Verizon are the major CDMA carriers, while AT&T, T-Mobile, and essentially the rest of the world use GSM. The easiest way to tell the difference between the two is to remember if you needed a SIM card to activate the phone or not.
However, GSM and CDMA devices are set up differently on the software (and hardware, in terms of radios) side, and if you flash a ROM built for a GSM phone onto a CDMA equivalent, you'll probably break the device. For all intents and purposes, you should consider GSM phones to be wholly distinct devices. Also make sure you're only flashing ROMs built for Sprint, as there are often differences between Sprint and Verizon phones as well.

Knixson said:
Thank you! would I also need to install the open recovery twrp to gain root access as well?
Click to expand...
Click to collapse
yep...unlock, flash recovery, flash ROM

Rirere said:
You need to follow the dev instructions. If I were you though, I wouldn't do anything more until you understand some of the risks involved. A phone is a really, really inconvenient thing to have incapacitated when you're learning how to flash. For one, your device wasn't bricked (completely nonresponsive to input); for another, dev instructions are going to tell you to use fastboot (or a toolkit that runs fastboot for you).
Before you start again, you should learn how to use fastboot at the very least, and if you can, adb install/sideload (although it seems you tried that based on the OP). fastboot is often the only thing working if a flash goes awry.
A ROM is a ROM, no matter what device it's for. GSM/CDMA are separate network technologies that power your phone. In the U.S., Sprint and Verizon are the major CDMA carriers, while AT&T, T-Mobile, and essentially the rest of the world use GSM. The easiest way to tell the difference between the two is to remember if you needed a SIM card to activate the phone or not.
However, GSM and CDMA devices are set up differently on the software (and hardware, in terms of radios) side, and if you flash a ROM built for a GSM phone onto a CDMA equivalent, you'll probably break the device. For all intents and purposes, you should consider GSM phones to be wholly distinct devices. Also make sure you're only flashing ROMs built for Sprint, as there are often differences between Sprint and Verizon phones as well.
Click to expand...
Click to collapse
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS

Knixson said:
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Click to expand...
Click to collapse
1) If all you are doing is flashing Roms right now you don't need to s-off.
2) You flash the zip.
and I will second the notion that you should do a lot of reading before you do too much. This is an easy process to screw up if you don't know what you are doing and taking your phone out of commission can be a real pain in the ass.
Good Luck!

Knixson said:
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Click to expand...
Click to collapse
We all have to start somewhere. There are some good guides in the forums if you search though that will be a lot more comprehensive than the answers we can give in each individual thread.
1. S-OFF matters if you want to make changes to /system during runtime. For example, if you used a root tool like Titanium Backup to move an app into /system with S-ON, the phone would crash because it detected a security violation (improper programic access to a secured location). S-OFF disables that check. You can still flash ROMs with S-ON though since the protection isn't active to the same extent in recovery, although I think it will block writing to the radio. Don't monkey with it more than you have to though, because it's easy to really screw yourself over with the wrong combination of software (unsigned boot software and S-ON will really brick your phone).
2. Read the thread. Almost all ROMs though are distributed in a flashable .zip, meaning you copy it over to the phone's storage and install through recovery (or use sideload). You shouldn't have to use the .imgs ever, although it's a good trick to know (use fastboot flash <> <>.img) in case something goes wrong. I had to do this recently when my fubared my /system but didn't feel like reflashing the whole ROM, so I extracted system.img from the ROM I used and just pushed that to device.

Rirere said:
We all have to start somewhere. There are some good guides in the forums if you search though that will be a lot more comprehensive than the answers we can give in each individual thread.
1. S-OFF matters if you want to make changes to /system during runtime. For example, if you used a root tool like Titanium Backup to move an app into /system with S-ON, the phone would crash because it detected a security violation (improper programic access to a secured location). S-OFF disables that check. You can still flash ROMs with S-ON though since the protection isn't active to the same extent in recovery, although I think it will block writing to the radio. Don't monkey with it more than you have to though, because it's easy to really screw yourself over with the wrong combination of software (unsigned boot software and S-ON will really brick your phone).
2. Read the thread. Almost all ROMs though are distributed in a flashable .zip, meaning you copy it over to the phone's storage and install through recovery (or use sideload). You shouldn't have to use the .imgs ever, although it's a good trick to know (use fastboot flash <> <>.img) in case something goes wrong. I had to do this recently when my fubared my /system but didn't feel like reflashing the whole ROM, so I extracted system.img from the ROM I used and just pushed that to device.
Click to expand...
Click to collapse
Thank you everyone has been very helpful I am so glad I found this forum I really do appreciate all the info that has been shared with me!
So I will leave with one final question then back to studying, Do you know any really good beginner tutorials or anything to start at?
Thanks again people I have learned a lot just in this conversation

Knixson said:
Thank you everyone has been very helpful I am so glad I found this forum I really do appreciate all the info that has been shared with me!
So I will leave with one final question then back to studying, Do you know any really good beginner tutorials or anything to start at?
Thanks again people I have learned a lot just in this conversation
Click to expand...
Click to collapse
There was a really good one in one of the threads in the development section, but I can't for the life of me remember what ROM had it posted. I'll take another look for it later, but in the meantime I would try reading on XDA's wiki.

Oh I just remembered one more question. I have Viper ROM currently but if I wanted to ad a different one should I wipe the Viper first and install new one or would it install right over top of the Viper? Thanks any help is appreciated. You have been the best!!!

Knixson said:
Oh I just remembered one more question. I have Viper ROM currently but if I wanted to ad a different one should I wipe the Viper first and install new one or would it install right over top of the Viper? Thanks any help is appreciated. You have been the best!!!
Click to expand...
Click to collapse
You can flash over it (which is often called a dirty flash) but you are much better off wiping first. I usually use This tool. Just put it on your sd card and flash it before you flash your new ROM.

I believe this thread will help any and all Sprint HTC One owners if they are having bootloop problems and also answers to frequently asked questions lmao!! Thanks again everyone you ALL have been VERY HELPFUL!!!!

Knixson said:
I believe this thread will help any and all Sprint HTC One owners if they are having bootloop problems and also answers to frequently asked questions lmao!! Thanks again everyone you ALL have been VERY HELPFUL!!!!
Click to expand...
Click to collapse
also do a nandroid before flashing, so you have a fall back

Htc One Stuck In Cwm And Cant Flash A Rom
SO i Rooted my Htc one and now im stuck in Cwm and i cant flash a rom or anything i have tried to sideload a Ruu file onto my phone but that didnt work
SO i tried using the Rom Update Utility and that didnt work either
Im lost and stuck with a Htc One That doesnt work at all i have tried multiple methods but nothing seems to work please help me if you can im 100% new to this whole thing....

jake012 said:
SO i Rooted my Htc one and now im stuck in Cwm and i cant flash a rom or anything i have tried to sideload a Ruu file onto my phone but that didnt work
SO i tried using the Rom Update Utility and that didnt work either
Im lost and stuck with a Htc One That doesnt work at all i have tried multiple methods but nothing seems to work please help me if you can im 100% new to this whole thing....
Click to expand...
Click to collapse
Check PM

[Q] Assistance Please - Returning to Stock

I have read a pile of material now on returning to Stock. I am still confused, and want to turn my One back to stock in order to sell it.
I have a Telus Mobility HTC One
Firmware 1.29.661.17
HBOOT= 1.44
I am rooted
I have S on
Ok, now that this is all out of the way, here is what I want to accomplish:
1. I want to return the HTC one to stock
I learned a valuable lesson. I really should have taken a nandroid backup before jumping into flashing custom roms. My bad. I have never done it. Now I know why.
Can someone please point me in the correct direction?
Things I have done/looked for:
-I have searched for a 1.29.661.17 nandroid backup for TWRP. There was a link for one, it is dead. I have PM'd the original poster in hopes they still have it.
-I have searched for a RUU to download. I haven't had much success, or what I saw confused the heck out of me.
Now, if someone could please assist - What is the correct procedure for me? Can someone point me to the right place, link to go?
I appologize. There are a bundle of posts on returning to stock. I didn't mean to open another one.

bbabiuk said:
Can someone please point me in the correct direction?
Things I have done/looked for:
-I have searched for a 1.29.661.17 nandroid backup for TWRP..
Click to expand...
Click to collapse
Here's a link for 1.29.661.5 TWRP nandroid backup. You should be able to restore this and then take OTA's to get you back to 1.29.661.7 and then 1.29.661.17.
http://www.htc1guru.com/dld/m7-twrp-nandroid-backup-cid-telus001-1-29-661-5-rar

Thank you! So one last question. Do I just flash it like any other ROM in twrp? Or do I have to put it in the twrp backups file then hit restore? Because if that is the case I'm kind of pooched. I downloaded the file and copied to data/twrp/backup. When I go to twrp it doesn't show up.
Sent from my HTC One using XDA Premium 4 mobile app

bbabiuk said:
Thank you! So one last question. Do I just flash it like any other ROM in twrp? Or do I have to put it in the twrp backups file then hit restore? Because if that is the case I'm kind of pooched. I downloaded the file and copied to data/twrp/backup. When I go to twrp it doesn't show up.
Click to expand...
Click to collapse
The file you downloaded is in rar format (kind of like a zip). Get winrar and extract the files it contains (system.ext4.win, etc) and then copy them into the twrp backups folder in same manner as other backups, then use TWRP restore function.

Twrp Backups not showing in recovery

before anyone says anything about using a search function let me say that i have searched every page on this site/google/youtube/ etc for an answer or fix
but anyway, so i screwed up and installed an old firmware update (mistakingly thinking it was new) and ran into a ton of issues, that after an extremely long night, i was able to fix.
i managed to load up the stock rom 4.4.2 that i had when i initially unlocked my device, and was hoping to copy over my twrp back up that i made earlier that day. when i make a twrp back up, i usually copy it to my pc to save phone space, and i tried to copy it back, and i put it in the backup folder, and although i can find it in file manager, i cant recover it. looking at the folder it looks like every other backup ive ever made, i have no idea why it wont show. i got a flasher app "Rashr" and it doesnt recognize it as a recovery folder either. does something need to be different? when i tried the twrp app, it selected all the typical boot img etc things but then says that it has to restart and when it does the twrp recovery still doesnt recognize it.
help ideas?
im still actively working it and if anyone finds anything that'll be wonderful thanks

I was helping you yesterday no?
I think what happened when you flashed a 4.1.2 you changed the file structure.
4.2.x and above handle things differently.
If you look in data/media/0/twrp you should find your backup.
I would still suggest running the latest RUU and starting fresh and it will give you the correct file structure.

BD619 said:
I was helping you yesterday no?
I think what happened when you flashed a 4.1.2 you changed the file structure.
4.2.x and above handle things differently.
If you look in data/media/0/twrp you should find your backup.
I would still suggest running the latest RUU and starting fresh and it will give you the correct file structure.
Click to expand...
Click to collapse
this might help too, don't know

Aldo101t said:
this might help too, don't know
Click to expand...
Click to collapse
Maybe you can elaborate on what this does I've never seen it.

BD619 said:
Maybe you can elaborate on what this does I've never seen it.
Click to expand...
Click to collapse
back when 4.1.2 was live, guys flashed to 4.2, and it messed up the file structure, if they went back to 4.1.2, (if I remember correctly)this would fix the file structure.
---------- Post added at 03:45 PM ---------- Previous post was at 03:40 PM ----------
Aldo101t said:
back when 4.1.2 was live, guys flashed to 4.2, and it messed up the file structure, if they went back to 4.1.2, (if I remember correctly)this would fix the file structure.
Click to expand...
Click to collapse
I thought maybe he could flash back to 4.1.2 then flash this, then back up his sdcard to computer then go on to 4.2. or above delete his sdcard on 4.2 or above then restore it from computer, just my thoughts on it.

Aldo101t said:
back when 4.1.2 was live, guys flashed to 4.2, and it messed up the file structure, if they went back to 4.1.2, (if I remember correctly)this would fix the file structure.
---------- Post added at 03:45 PM ---------- Previous post was at 03:40 PM ----------
I thought maybe he could flash back to 4.1.2 then flash this, then back up his sdcard to computer then go on to 4.2. or above delete his sdcard on 4.2 or above then restore it from computer, just my thoughts on it.
Click to expand...
Click to collapse
He flashed a really old rom and lost his ability to use the touch screen.
Not sure if he will be staying on the older rom.

BD619 said:
He flashed a really old rom and lost his ability to use the touch screen.
Not sure if he will be staying on the older rom.
Click to expand...
Click to collapse
yeah, your probably right, just thought I'd throw it out there.

i managed to use the files i used to root my phone to restore my phone back to a usable state. im not exactly sure if its RUU but my phone is basically back to where it was almost 5 months ago, luckily i had did an htc backup about 3 weeks ago, so i didnt quite lose every thing. its back to 4.4.2. im not exactly sure if my issue is making sense.
i have a back up i made on twrp, i cut and paste it to my desktop. when i put it in my twrp backup folder, its treated as if its not there. i can physically search for it and find it within the folder. is there a certain way that backups are made? i just made a backup of my device today, and it created a seperate FAxxxxxxxxx folder, im gonna try and put it in there to see if it helps any, but at this point im thinking i should give up and admit a lost cause.
my devce works, and thanks BD for all the help you gave!! seriously wouldve gone crazy without it.lol

Enishi44 said:
i managed to use the files i used to root my phone to restore my phone back to a usable state. im not exactly sure if its RUU but my phone is basically back to where it was almost 5 months ago, luckily i had did an htc backup about 3 weeks ago, so i didnt quite lose every thing. its back to 4.4.2. im not exactly sure if my issue is making sense.
i have a back up i made on twrp, i cut and paste it to my desktop. when i put it in my twrp backup folder, its treated as if its not there. i can physically search for it and find it within the folder. is there a certain way that backups are made? i just made a backup of my device today, and it created a seperate FAxxxxxxxxx folder, im gonna try and put it in there to see if it helps any, but at this point im thinking i should give up and admit a lost cause.
my devce works, and thanks BD for all the help you gave!! seriously wouldve gone crazy without it.lol
Click to expand...
Click to collapse
You must have ran the RUU file. Once you run the RUU file and you have to unlock everything using the HTC DEV method then yes, you will loose everything because the RUU file will bring your phone as it was coming out of the store.