Hello, I'm Daniel,
My problem: I have unlocked my HTC Desire 825's bootloader a few months back, don't ask me why, I didn't know what I was doing. My device is S-ON, not rooted and has its bootloader unlocked. It has TWRP installed and working. When trying to install a new OS (it was my first time trying) I did not backup anything, wiped my system and pretty much every partition on the phone. Now there is nothing that I can boot to. I have attempted to download some 2PUKIMG's for returning my phone to stock but my CID prevented me from installing them as they were not the right ones, if anybody knows where to get the H3G_ROI 2PUKIMG for free I'm all open ears. I do not have a supercid and cannot change it because of S-ON, things like moonshine wont work and I've already tried firewater(basically the old version of moonshine) but I do not have superuser and supersu installation does not work properly. For some reason fastboot does not work with my laptop(I do not think that it is the phone's fault). ADB works just fine when I launch into TWRP. I've looked around at as many places as possible but due to the phone's recent launch just over a year ago I could not find much apart from paid downloads for the 2PUKIMG's I need but I highly doubt that paying for the download will get me to where I want.
What I need is either another tested method to S-OFF my device via ADB/TWRP/Fastboot(if I get it to work) or the 2PUKIMG H3G_ROI. The S-OFF would allow me to install superuser and/or install any 2PUKIMG with the supercid. The 2PUKIMG will(obviously) return the stock ROM to my phone.
Thank you for any replies and/or help and it is very appreciated!
-Daniel
Have you tried http://forum.gsmdevelopers.com/showthread.php?t=24278
---------- Post added at 10:00 AM ---------- Previous post was at 09:54 AM ----------
Also, have you tried side loading while in recovery? Just send the superuser file to phone and install through recovery
Post your getvar result please.
fastboot getvar all
Hi, do not worry
I already had this problem and I ended up solving it,
I made a post on how I solved it
you can find it right here
Good luck, If you have any questions, please do not hesitate
Related
Good ghod what a state I've managed to get myself into: I've been unlocking/re-locking my phone (ROM: OTA ICS, S-On, Unlocked, Rooted) for right at a year now, but, during the recent OTA update push, I managed to get it into a state where it will no longer unlock. My (long, sorry) story follows...
I started receiving the recent OTA push two or three weeks ago. The problem is that I'd renamed the HTClinkifydispacher apk and odex files, and added a couple of things to /system/app/build.prop so the update would fail. Why was this such an immediate problem? Because I use my phone for an alarm clock and would wake up on random days to see it booted to recovery---after having overslept. Grrr.
Being the impulsive guy that I am, rather than just ask here how to stop the f$*kin' update, I found and saved the OTA.zip file to my sdcard, fixed the two problems I was having, re-locked the bootloader, and booted to recovery. Next, I *thought* I picked the OTA zip file to install... but I was wrong.
For at least one reason (I wanted to install a kernel with tun.ko installed so I could use a VPN network connection), I had a copy of SebastianFM's 1.4 overclocked kernel zip on my sdcard and mistakenly picked *it* instead of the OTA zip (hey, the fonts are small in Amon Ra). Well, that install failed, and, when I saw what I'd done, I thought "uh oh," so I rebooted the phone fully to see if I'd done any damage. None was apparent. So I moved on, once again re-booting into recovery and (this time successfully) installing the OTA zip.
Woo-hoo!
I thought I was golden, but I was wrong: Using my original unlock code and an up-to-date copy of the Android SDK on my linux box, I tried to reflash the unlocktoken partition using the fastboot command. My cursor froze/still freezes at something like "[0kb downloaded]..." It's almost like I've lost permission to write to that partition in the bootloader.
After the first sixteen times of trying various re-flashes of the August OTA, I thought "Gee, maybe it's something to do with the firmware," and since doing something is almost always worse than doing nothing (yes, that's what I meant to say), I did the only thing I could do: I flashed the Global Update RUU zip from October that I got off of Android Police's site. It's a great ROM; unfortunately, I still cannot unlock my bootloader.
In anticipation of some possible questions, let me add that
(1) I've factory reset any number of times;
(2) When I did the flashes, I immediately re-flashed a second time to ensure that the flashes took;
(3) When I connect my USB cable, I see "Fastboot USB" light up in the fastboot section of HBOOT.
(4) When I issue any other fastboot command, such as "fastboot devices" or "fastboot get_identifier_token", I get responses from the phone.
(5) Even though I have my original Unlock_code.bin file from HTCdev, I went through the whole unlock process from that site (sent a new identifier token; got the Unlock_code.bin back; tried "fastboot flash unlocktoken Unlock_code.bin") on two other occasions. Interestingly, the identifier_tokens would vary, but any new Unlock_code.bin files have all been identical---if the md5sum hash can be trusted to distinguish them.
Can anyone out there in expert-land help me figure out how to re-unlock my bootloader?! !? Beer can be involved.
Many thanks for your patience and kind consideration...
cheers,
john
Hey All,
So, I'd like to first say thanks to all of you who read and considered throwing in an opinion on how I might move forward with my little problem.
Secondly, I have some followup from HTC, which spawns a followup question. Please read on...
Since my OP, I have been in a back and forth with HTC about what I did to my phone that has left me unable to re-unlock it. Their answer, in a nutshell, was that I'd accepted the update while my phone had a 3rd-party recovery on it. Guilty as charged, I did; Amon Ra 3.15.
More specifically, they wrote: "If any portion of this check fails due to the stock recovery not being present, the update may load but the security sector will not authenticate. This may be blocking the re-unlock."
If you're like me, you'll note that there are a couple of "may"s in those two sentences that have left me wondering if they're just giving me a stock "I really don't know what the hell happened to your phone" answer.
So just to satisfy my curiosity, has anyone else out there ever had a problem flashing OTAs while having a 3rd-party recovery on their phones?
thanks again,
john
There's a couple threads about the recent OTA, one in General and one in this section. People posted about their various experiences, you might find some useful info in those.
I wonder if you can s-off at this point and fix your issue? I don't know if you need to be unlocked to s-off, I know you end up locked, but if not, that would give you the freedom to flash what you want without needing to be "unlocked".
feralicious said:
There's a couple threads about the recent OTA, one in General and one in this section. People posted about their various experiences, you might find some useful info in those.
Click to expand...
Click to collapse
Yes, I've looked through them and had no luck finding anything relevant to my case.
feralicious said:
I wonder if you can s-off at this point and fix your issue? I don't know if you need to be unlocked to s-off, I know you end up locked, but if not, that would give you the freedom to flash what you want without needing to be "unlocked".
Click to expand...
Click to collapse
The phone has to be unlocked to do the s-off thing.
thanks,
john
Update: Problem Solved!
Hey All,
As the post title states, I finally did get this sorted out.
The solution? Borrowing a windows 7 computer, downloading the HTC device drivers, fastboot and adb, and then merely running the 'fastboot flash' thing. Like I'd done a thousand times already on my linux system. Sheesh.
Thanks to all who read or contributed to this thread...
cheers,
john
I have superuser and artas CWM. I am running P769BK. I want to install a new ROM but want to avoid a security error again. Any tips?
I searched here and Google and found nothing. If I need to go to another thread I will.
Sent from my LG-P769 using Tapatalk 4 Beta
thchipmunk said:
I have superuser and artas CWM. I am running P769BK. I want to install a new ROM but want to avoid a security error again. Any tips?
I searched here and Google and found nothing. If I need to go to another thread I will.
Sent from my LG-P769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same here man i had unlocked the bootloader a while back before the JB upgrade was gonna try a Rom so decide to flash recovery and got the Sec error did all reflashed KDZ back on JB rooted and with artas recovery they say once you unlock the bootlader it stays that way, anyways did all the steps again to unlock, but boot normal and i have no way of checking... How can we know or check that the bootloader is unlocked??
Anyone????
If you have unlocked your bootloader, you would know
anyways here are a couple of ways to check, because y'all still want to check
1. Dial the number EVIL#*769# (3845#*769#) this will get you into the hidden menu
note: if you have a P760 change number to 3845#*760# change the last number/digit to whatever your device is
Once in that menu look for the bootloader tab, if it doesn't have it, sorry the kdz you are on doesn't show if it's unlocked or not.
2. Put your phone in the s/w upgrade mode, it should show unlocked bootloader
3. Another way to check is to fastboot and flash a custom recovery for your device BUT first extract your current recovery.img in case you receive a security error. However, I would advice y'all don't fastboot and flash anything unless you really know what y'all are doing. You have been warned!!!
---------- Post added at 12:15 PM ---------- Previous post was at 12:11 PM ----------
elpuertorro said:
Same here man i had unlocked the bootloader a while back before the JB upgrade was gonna try a Rom so decide to flash recovery and got the Sec error did all reflashed KDZ back on JB rooted and with artas recovery they say once you unlock the bootlader it stays that way, anyways did all the steps again to unlock, but boot normal and i have no way of checking... How can we know or check that the bootloader is unlocked??
Anyone????
Click to expand...
Click to collapse
In your case @elpuertorro you have to flash the u-boot.img from a P760 v20B
I uploaded the u-boot here http://forum.xda-developers.com/showpost.php?p=43386521&postcount=14
Another thing, if you did in deed unlock your bootloader, flashing a new kdz will (should not) not replace the u-boot.img. All P769 or LGMS769 will know right away if their bootloader is unlocked because the "LG" letters will be inverted when your boot up the phone (unless you flashed a u-boot.img from a P769).
Thanks! This are my unfortunate results.
I did not see the menu. I did the offline flash of V20_00
Nothing about unlocked bootloader
Yeah... I don't feel confident enough to try this again. Not yet.
Oh well. I'll wait longer until I feel better about what I am trying.
I have the P769BKGO GSM unlocked using Net10. So I think I won't be able to do the adb reboot oem-unlock trick. Other thoughts? Is flashing a different KDZ the only other route?
kuma82 said:
If you have unlocked your bootloader, you would know
anyways here are a couple of ways to check, because y'all still want to check
1. Dial the number EVIL#*769# (3845#*769#) this will get you into the hidden menu
note: if you have a P760 change number to 3845#*760# change the last number/digit to whatever your device is
Once in that menu look for the bootloader tab, if it doesn't have it, sorry the kdz you are on doesn't show if it's unlocked or not.
2. Put your phone in the s/w upgrade mode, it should show unlocked bootloader
3. Another way to check is to fastboot and flash a custom recovery for your device BUT first extract your current recovery.img in case you receive a security error. However, I would advice y'all don't fastboot and flash anything unless you really know what y'all are doing. You have been warned!!!
---------- Post added at 12:15 PM ---------- Previous post was at 12:11 PM ----------
In your case @elpuertorro you have to flash the u-boot.img from a P760 v20B
I uploaded the u-boot here http://forum.xda-developers.com/showpost.php?p=43386521&postcount=14
Another thing, if you did in deed unlock your bootloader, flashing a new kdz will (should not) not replace the u-boot.img. All P769 or LGMS769 will know right away if their bootloader is unlocked because the "LG" letters will be inverted when your boot up the phone (unless you flashed a u-boot.img from a P769).
Click to expand...
Click to collapse
kuma82 said:
If you have unlocked your bootloader, you would know
anyways here are a couple of ways to check, because y'all still want to check
1. Dial the number EVIL#*769# (3845#*769#) this will get you into the hidden menu
note: if you have a P760 change number to 3845#*760# change the last number/digit to whatever your device is
Once in that menu look for the bootloader tab, if it doesn't have it, sorry the kdz you are on doesn't show if it's unlocked or not.
2. Put your phone in the s/w upgrade mode, it should show unlocked bootloader
3. Another way to check is to fastboot and flash a custom recovery for your device BUT first extract your current recovery.img in case you receive a security error. However, I would advice y'all don't fastboot and flash anything unless you really know what y'all are doing. You have been warned!!!
---------- Post added at 12:15 PM ---------- Previous post was at 12:11 PM ----------
In your case @elpuertorro you have to flash the u-boot.img from a P760 v20B
I uploaded the u-boot here http://forum.xda-developers.com/showpost.php?p=43386521&postcount=14
Another thing, if you did in deed unlock your bootloader, flashing a new kdz will (should not) not replace the u-boot.img. All P769 or LGMS769 will know right away if their bootloader is unlocked because the "LG" letters will be inverted when your boot up the phone (unless you flashed a u-boot.img from a P769).
Click to expand...
Click to collapse
Thanks kuma the thing is i did this when i got the phone back in Jan so as you can see by now what ever i did is a bit of a blur, (short time mem loss you know lol) but i did recall doing it and have my folder set up for my phone, but to try to remember what or how and what tut i followed is the problem...but it's cool because i was looking for
V20b and since i could find one yesterday talking to carloswii for a copy asked if V20c would work as he didn't know figured i will try it and report back for the benefit of all....so that's next today
ps Kuma that's great advice but hey @thchipmunk don't be scared man is scary reading all but once you do it like 2 times it's all smooth plus with th KDZ offline method this cel comes back to life in no time so far as they have said you can't brick this phone even if you tried lol. to the rest stick with kuma's advice lol.
I am mostly just scared because it took me forever to get the KDZ to flash again. I kept getting that the USB was not connected to the phone so I wasn't able to ever complete the flash.
I do wonder though, if I would be able to unlock the bootloader. I see the directions say you need to wait 30+ minutes once connected, I assume this is some restriction in place on the actual phone with the SIM. However, I have an ATT SIM that I am using through NET10. Will that matter?
elpuertorro said:
Thanks kuma the thing is i did this when i got the phone back in Jan so as you can see by now what ever i did is a bit of a blur, (short time mem loss you know lol) but i did recall doing it and have my folder set up for my phone, but to try to remember what or how and what tut i followed is the problem...but it's cool because i was looking for
V20b and since i could find one yesterday talking to carloswii for a copy asked if V20c would work as he didn't know figured i will try it and report back for the benefit of all....so that's next today
ps Kuma that's great advice but hey @thchipmunk don't be scared man is scary reading all but once you do it like 2 times it's all smooth plus with th KDZ offline method this cel comes back to life in no time so far as they have said you can't brick this phone even if you tried lol. to the rest stick with kuma's advice lol.
Click to expand...
Click to collapse
thchipmunk said:
I am mostly just scared because it took me forever to get the KDZ to flash again. I kept getting that the USB was not connected to the phone so I wasn't able to ever complete the flash.
I do wonder though, if I would be able to unlock the bootloader. I see the directions say you need to wait 30+ minutes once connected, I assume this is some restriction in place on the actual phone with the SIM. However, I have an ATT SIM that I am using through NET10. Will that matter?
Click to expand...
Click to collapse
Been there , done that lol
By anychance when that happened to you
1 you were connecting the phone on lg software mode? that's what it should be and i'm sure you was
2 if you did, was it giving you errors about installing drivers failed?? that happens to me sometimes so i just restart the pc and then the phone get's recognized.
just remember sometimes we have to hit that skip that pops up when it's searching for drivers on the phone.... worse comes to worse reinstall the drivers for the phone hope this helps you out man.
I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
COrootking4life said:
Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
Click to expand...
Click to collapse
Yes HTC has a RUU (Rom Update Utility) You posted in the AT&T forums so I'm going to assume you need the AT&T RUU
You can download it directly from HTC Here
The RUU requires s-off or Relocked bootloader
you relock it with this command
fastboot oem lock
fastboot reboot-bootloader
I've tried that before the ruh fails BC the phone shows no operating system. I've tried several different ones. The one thing that I see in relation to all the ruu threads all say you should see a os version in the current field and in dont. Unless there's some other order of operations Im not aware of when trying to use them.
Sent from my GT-N7105 using XDA Free mobile app
I've solved this without an RUU. I will post a "SOLVED" thread in the development page.
Sorry for the delay folks
COrootking4life said:
Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
Click to expand...
Click to collapse
Sorry for the sluggish delay, due to some scheduling conflicts and other hurdles came into play but nevertheless Im posting my solved post now. head over to the ATT HTC ONE ANDROID DEVELOPMENT FORUM TO FIND THE POST LABELED "SOLVED"
i have installed the Skydragon GPE edition last year and now when i tried to Completely Format the Rom or the data system etc ..
I cant Install any rom. I tried the RUU didnt work . i dont have the latest TWRP and i cant flash it to adb . i Did all the commands
im so frustated im so Noobish in this .. sorry .. but still i can access to recovery but its old
i was thinking to Buy the otg usb .. then download some rom . But i dont know if its gonna work cause most new roms in htc one m8 att
needs a new TWRP which is i cant do anymore .. Please help me ..
Not enough info:
1) Current hboot and main version number? Do fastboot getvar all, and post the output (delete IMEI and serial numbers before posting, as these are personal info).
2) What RUU (exact file name)?
3) S-on or s-off?
4) If s-on, did you relock the bootloader when running the RUU (this is required)
5) What happened exactly, when you ran the RUU? Any error messages? If so, what were they?
6) What ROMs did you try? What was the result (again, any error messages, and if so what did they say)?
7) What version TWRP?
8) Was your phone updated to Lollipop before you unlocked the bootloader?
---------- Post added at 10:31 AM ---------- Previous post was at 10:27 AM ----------
adr1105 said:
i dont have the latest TWRP and i cant flash it to adb
Click to expand...
Click to collapse
adb requires a working OS, and won't work in the current condition. TWRP is typically flashed via fastboot, not adb, which requires the phone be connected and booted into bootloader-fastboot mode.
Do you have fastboot connectivity (any response to command: fastboot devices)?
Also, this isn't a "hard brick" or any kind of brick, that that matter.. As long as the screen comes on, these phone is recoverable (you just aren't going about it properly). A "hard brick" is a phone that is not recoverable (short of opening it up and JTAG, replace motherboard, etc.).