I am looking at getting this phone. Seeing how it is without even simple CWM (How does this happen on XDA?!) I'll go ahead and build a recovery (and maybe a couple ROM's .
Here is what I need:
Latest Recovery Image
Latest System Image
Latest Boot Image
Latest graphics.c
Willing testers are needed as well.
When applicable:
Root your device
Install Flashify
Download Recovery image
Flash via Flashify.
Done. Custom recovery w/o bootloader unlock
I'll be happy to test out. Just let me know what I need to get ya and where to get it.
Kwongger said:
I am looking at getting this phone. Seeing how it is without even simple CWM (How does this happen on XDA?!) I'll go ahead and build a recovery (and maybe a couple ROM's .
Here is what I need:
Latest Recovery Image
Latest System Image
Latest Boot Image
Latest graphics.c
Willing testers are needed as well.
When applicable:
Root your device
Install Flashify
Download Recovery image
Flash via Flashify.
Done. Custom recovery w/o bootloader unlock
Click to expand...
Click to collapse
I knew it was here somewhere. http://forum.xda-developers.com/showthread.php?p=54945442
I don't know much about Flashify, but I didn't think you could flash anything without bootloader unlock/ Loki.
Can you enlighten me?
Does no good w/o unlocked bootloader, hence why there is nothing available thus far for it.
otherwise myself or others would have already done something.
PlayfulGod said:
Does no good w/o unlocked bootloader, hence why there is nothing available thus far for it.
otherwise myself or others would have already done something.
Click to expand...
Click to collapse
Flashify does not need an unlocked bootloader. It works great on my HTC One Max, SHIELD Portable, and SHIELD Tablet w/o bootloader unlock. Unlocking the bootloader is a requirement of the past.
Kwongger said:
Flashify does not need an unlocked bootloader. It works great on my HTC One Max, SHIELD Portable, and SHIELD Tablet w/o bootloader unlock. Unlocking the bootloader is a requirement of the past.
Click to expand...
Click to collapse
No offense, but dont delude yourself.
Without a viable way to backup and restore, one is just asking for trouble flashing things.
And w/o a unlocked bootloader you cannot flash recovery, esp on this device.
Kwongger said:
Flashify does not need an unlocked bootloader. It works great on my HTC One Max, SHIELD Portable, and SHIELD Tablet w/o bootloader unlock. Unlocking the bootloader is a requirement of the past.
Click to expand...
Click to collapse
You are wrong.
Without even addressing the other models, HTC One Max used emmc based write protection. You CANT write to the recovery patition without using the official unlock, or SunShine/Firewater unlocks.
On top of that, even if you managed to write to the partition, say some how you had some exploit that dropped write protection, you still have to unlock it (or s-off, which is an unlock) because if you didnt hboot would fail the validation of the recovery partition.
jcase said:
You are wrong.
Without even addressing the other models, HTC One Max used emmc based write protection. You CANT write to the recovery patition without using the official unlock, or SunShine/Firewater unlocks.
On top of that, even if you managed to write to the partition, say some how you had some exploit that dropped write protection, you still have to unlock it (or s-off, which is an unlock) because if you didnt hboot would fail the validation of the recovery partition.
Click to expand...
Click to collapse
forgot to add the s-off part! Thanks for calling me on that one. I do so much to these damn things that I forget how I've mutilated their software xD
Kwongger said:
forgot to add the s-off part! Thanks for calling me on that one. I do so much to these damn things that I forget how I've mutilated their software xD
Click to expand...
Click to collapse
LG G3 should fail for a similar reason, the signature checks. LG does not have an "s-off/unlock" to disable them. TMobile obviously isn't checking but AT&T is, I believe Verizon and Sprint do as well.
PlayfulGod said:
No offense, but dont delude yourself.
Without a viable way to backup and restore, one is just asking for trouble flashing things.
And w/o a unlocked bootloader you cannot flash recovery, esp on this device.
Click to expand...
Click to collapse
lgg3root.com
Am I hallucinating while this guy flashes TWRP via Flashify? (I wouldn't put it past me xD) Or does T-mo magically have an unlocked bootloader? If the do, I'll be pissed with Sprint/LG haha.
jcase said:
You are wrong.
Without even addressing the other models, HTC One Max used emmc based write protection. You CANT write to the recovery patition without using the official unlock, or SunShine/Firewater unlocks.
On top of that, even if you managed to write to the partition, say some how you had some exploit that dropped write protection, you still have to unlock it (or s-off, which is an unlock) because if you didnt hboot would fail the validation of the recovery partition.
Click to expand...
Click to collapse
PlayfulGod said:
No offense, but dont delude yourself.
Without a viable way to backup and restore, one is just asking for trouble flashing things.
And w/o a unlocked bootloader you cannot flash recovery, esp on this device.
Click to expand...
Click to collapse
To both of you:
People like you are the reason that I've taken a long break from XDA. The drama and attacks are senseless and absurd. I come here with FREE software, and you criticize and correct me on things even when you're wrong. You punks have no fricking idea about what I know or can do, and you're willing to cut your nose off to spite your face. I have a build booting for ATT and Sprint of TWRP... I am just going to keep it private. You fools don't deserve it. XDA is going to hell, and I'm getting off of the crazy train now.
Mods, please close this thread.
Kwongger said:
lgg3root.com
Am I hallucinating while this guy flashes TWRP via Flashify? (I wouldn't put it past me xD) Or does T-mo magically have an unlocked bootloader? If the do, I'll be pissed with Sprint/LG haha.
Click to expand...
Click to collapse
the tmo g3 (d851) comes with a unlocked bootloader.
PlayfulGod said:
the tmo g3 (d851) comes with a unlocked bootloader.
Click to expand...
Click to collapse
Those bastards. Looks like I'm leaving sprint too ;D
Kwongger said:
To both of you:
People like you are the reason that I've taken a long break from XDA. The drama and attacks are senseless and absurd. I come here with FREE software, and you criticize and correct me on things even when you're wrong. You punks have no fricking idea about what I know or can do, and you're willing to cut your nose off to spite your face. I have a build booting for ATT and Sprint of TWRP... I am just going to keep it private. You fools don't deserve it. XDA is going to hell, and I'm getting off of the crazy train now.
Mods, please close this thread.
Click to expand...
Click to collapse
I didn't insult, attack or anything, I provided factual information to you in an area I am knowledgeable. Yet you came on and just called me a p*nk.
I don't need anything from you, I was trying to help you. I too have a custom images booting from emmc (not from fastboot) on AT&T, this is how I know what i needed to make it happen. My track record more than speaks for itself.
Mod here, dont worry I'll take care of it.
DELETE
Didn't get to the end of the thread.
yup
Kwongger said:
lgg3root.com
Click to expand...
Click to collapse
Neat, a site talking about the tools auto, playful, cube and I wrote.
jcase said:
Mod here, dont worry I'll take care of it.
Click to expand...
Click to collapse
Ah, that's why. I understand why you were so rude.
Kwongger said:
To both of you:
People like you are the reason that I've taken a long break from XDA. The drama and attacks are senseless and absurd. I come here with FREE software, and you criticize and correct me on things even when you're wrong. You punks have no fricking idea about what I know or can do, and you're willing to cut your nose off to spite your face. I have a build booting for ATT and Sprint of TWRP... I am just going to keep it private. You fools don't deserve it. XDA is going to hell, and I'm getting off of the crazy train now.
Mods, please close this thread.
Click to expand...
Click to collapse
I'm sorry... did you just call these both "punks" while at the same time talking about drama and attacks? BWahaha - Pot, meet Mr. Kettle.
This whole thing you're trying to do puts everyone who chooses to use this process in danger of fetching up their device... And that's great you have a build booting - go you. But FFS don't go all "I AM THE GREATEST!" here when you're the one ignoring actually good advice from at least one professional in the industry who has done more for the community as a whole than your little piece of work. Please, keep your work to yourself, and just use it yourself without putting everyone else's devices at risk. Oh - and it seems your long break wasn't long enough - maybe consider extending it if it gets you this worked up over very helpful information.
EDIT: Closing at the request of the very stressed out user.
Related
Well at last, HTC has brought us their method to root HTC Evo 3D & Sensation.. Just register to become a member (dev) and begin rooting your Evo3D. I wanted to show you all what to expect.. and of course there are disclaimers so view screen shots for full details. I have not tried this setup so please give feedback, I do have the phone but it's been rooted by other methods.. just giving fellowship & sharing information. Enjoy!
Go to HTCDev.com to get started.. (This will VOID your warranty, root your phone & give you super human strenghts)
Previous rooting gave phone's the same voided warranty especially servicing in carriers service center, same deal. Revolutionary method also voids warranty so now people have choices.. (Former Sprint Service Mgr)
As informed please give useful feedback if you have used this method so we know where we stand with this and in fact "IF" HTC is helping us out.
Thx to Doomstang for input-
Doomstang said:
Well I think I've finally gotten somewhere...Wireless Tether was just successfully granted Superuser permissions.
This was all done without ever having rooted this phone in the past...so I accepted the OTA update, unlocked with HTC Dev's process, got a working recovery going, and then got Superuser installed.
graffixnyc posted the link to the working recovery so I used that: http://www.multiupload.com/AQ9KV7IME9
Click to expand...
Click to collapse
And Graffixnyc-
graffixnyc said:
This was the version of CWM that booted for me. I flashed through fastboot and also did a nandroid restore just fine. This was the version IEF(from alpharev) gave me on irc
http://www.multiupload.com/AQ9KV7IME9
I was able to get into recovery from selecting recovery from the fastboot method and from doing adb reboot recovery. Sorry for not posting earlier I had finals yesterday and went out after to celebrate
http://www.multiupload.com/AQ9KV7IME9
Click to expand...
Click to collapse
Please make sure all items are installed and up to date.
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Continued "disclosure"
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty. Please note that unlocking your bootloader does not mean that you will be able to unlock the SIM lock. Unlocking your SIM lock is at the discretion of your operator/carrier and is not part of the bootloader unlocking scope.
Our devices have been designed with our hardware and software specifications in mind and unlocking the bootloader will change the software and may cause unexpected side effects. It is impossible for HTC to ensure the proper functioning of your device after this. In the worst case scenario, it is possible that your device may be physically damaged due to overheating or the behavior of your device might be altered including, but not limited to, hearing aid compatibility (HAC) and specific absorption rate (SAR) values.
Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable. Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader. HTC bears no responsibility if your device is no longer usable afterwards.
HTC is committed to assisting customers in unlocking bootloaders for HTC devices. However, due to some of our carrier customers concerns, certain models with specific restrictions may not be able to be unlocked. Please refer to our list of supported devices to see if your device is eligible for unlocking the bootloader.
We strongly suggest that you do not unlock the bootloader unless you are confident that you understand the risks involved. This is a technical procedure and the side effects could possibly necessitate repairs to your device not covered under warranty. If you are still interested in unlocking the bootloader, and you understand the consequences both to your device and to your warranty, then you may refer to the following pages where we have provided the unlocking instructions.
If there's an error you will see screen shot below.. with details on what happened.
So maybe I'm confused about what this does ... I went through the process and everything seems to have worked. Bootloader now shows unlocked. I tried to flash a recovery (both clockworkmod and TWRP) and it seems to flash successfully but when I try to run recovery it just reboots the phone after showing the HTC logo for a minute. I was hoping to install the rooted OTA but not sure what to try next...
nabbed said:
No. I'm not confused about the unlock.
I'm worried about a man who makes a guide about unlocking the device he does not have...
Am I wrong to be worried, about a man, who makes a post, about unlocking a device, he does not have?
Has has tested the method?
Click to expand...
Click to collapse
Yooooo. Godzson is a trusted guy and helps many devs in the community. No sense in flamming him when you'll just start pissing off devs here.
Sent from my PG86100 using Tapatalk
Godzson is a trusted member on here. Don't think you have to worry about him. Why would someone take all this time to write up a post with pics and the info just to mess with people? Smh....... Alot of the devs in the 3d community who do roms and themes don't even have the damn 3d. Don't start turning this community into **** by questioning people trying to help.
gthing said:
So maybe I'm confused about what this does ... I went through the process and everything seems to have worked. Bootloader now shows unlocked. I tried to flash a recovery (both clockworkmod and TWRP) and it seems to flash successfully but when I try to run recovery it just reboots the phone after showing the HTC logo for a minute. I was hoping to install the rooted OTA but not sure what to try next...
Click to expand...
Click to collapse
TWRP doesn't work and CWM Is a hit or miss. You should of tried the stock recovery, I think it had one. Wait till a root for the new boot loader I say.
I think the unlocked just gives partial access to the bootloader if I am correct. Your security flag(s-off) is still on.
Sent from my EVO3D(overclocked) via XDA App
Godzson is only posting to what HTC promised, here a unlocker. He is also a trusted member, who provides a substantial amount of information for the community. Please they are also right to say some dev, and do not have this device and do an amazing job developing for it. let's please keep peaceand move forward..
Why waste your time reposting instructions found on htcdev.com? People want to know what happens after you do the method and how it helps put custom software on your phone.
mwalt2 said:
Why waste your time reposting instructions found on htcdev.com? People want to know what happens after you do the method and how it helps put custom software on your phone.
Click to expand...
Click to collapse
Because sometimes people want to see the process without having to DO the process....
Why question it? Just don't read through 2 pages or more of posts if it's offensive to you.
Yo GODZSON, you do know that the little green android guy isn't the only one that's green around here, don't you? LMFAO. Just look at the noobs trying to flame you, and don't even know anything about you, LOL. Yeah, LOL. Like they got room to talk. Keep up the great work buddy.
On a more serious note, does this method actually allow you to root? Cuz I didn't really see anything on HTC's site, or in your post about rooting. Yet the title states rooting with HTC's unlock method. Just a fyi.
Sent from my PG86100 using XDA Premium App
Well sir maybe doing a lil research would benefit the questions. I did assist with 2 threads in Evo3D (screen pics and 3D converting). I placed this for information to the community and for knowledge to those that may want to see what it looks like and have other options of rooting their phone. I do have the device but's its been rooted therefore I havent tried this "Official" method. Would be nice to ask with some manners in XDA you can get suspended, banned, etc for your actions, this is a community to help each other out.
Thanks to all the fellow dev's for the kind words.. to all the noobs with lack of knowledge no worries we're here for you to help out, much love for you.. hey we all started there at one time
Well I think I've finally gotten somewhere...Wireless Tether was just successfully granted Superuser permissions.
This was all done without ever having rooted this phone in the past...so I accepted the OTA update, unlocked with HTC Dev's process, got a working recovery going, and then got Superuser installed.
graffixnyc posted the link to the working recovery so I used that: http://www.multiupload.com/AQ9KV7IME9
this is a joke!
HTC's unlocked bootloader is a joke, it just says "unlocked" but you cannot flash any new recoveries and you get S-ON. Don't try this folks, stay rooted! My 3D is now officially bricked with HTC method, it's not unlocked at all as you can't do anything with it.
zedomax said:
HTC's unlocked bootloader is a joke, it just says "unlocked" but you cannot flash any new recoveries and you get S-ON. Don't try this folks, stay rooted! My 3D is now officially bricked with HTC method, it's not unlocked at all as you can't do anything with it.
Click to expand...
Click to collapse
I'm very sorry to hear yours was bricked but I was able to flash a working recovery (although the first 2 I tried did fail) and gain SU permissions even with S-ON still showing.
thnx
Doomstang said:
I'm very sorry to hear yours was bricked but I was able to flash a working recovery (although the first 2 I tried did fail) and gain SU permissions.
Click to expand...
Click to collapse
Thanks I actually saw your post and trying that now! We will have ROOT!
It does look like things are working for some starting here in one of the other threads.
Great write up
Lol, sorry HTC. We beat you to it.
Sent from my EVO 3D using XDA Premium App
The unlock is terrible, I got it to work on my Dad's phone, but I could only get into clockwork once, TWRP doesn't work, and only a manual flash of clockwork seemed to work, I tried to get in with Rom Manager for him so he could do a backup, and it wouldn't go either, and it didn't want to go back in for me manually either, just boots up.
Oh well, I managed to root it and get a rom installed. So we shall see how everything goes.
It's S-ON still, which is complete crap.
nfollin said:
The unlock is terrible, I got it to work on my Dad's phone, but I could only get into clockwork once, TWRP doesn't work, and only a manual flash of clockwork seemed to work, I tried to get in with Rom Manager for him so he could do a backup, and it wouldn't go either, and it didn't want to go back in for me manually either, just boots up.
Oh well, I managed to root it and get a rom installed. So we shall see how everything goes.
It's S-ON still, which is complete crap.
Click to expand...
Click to collapse
4.0.1.5 failed for me too.
I started with CWM 4.0.1.4.
I clicked update recovery in ROM Manager and it said 4.0.1.5 successfully installed after I granted it SU permissions. Had it reboot into recovery from ROM manager and the phone just restarted...so I manually went to recovery via HBoot and it fails to load and restarts the phone. I guess I'll push that 4.0.1.4 back to it now.
so the bootloader gets unlocked but yet it stays S-on? wtf lol ?
I recently unlocked my phone and rooted, I tried to flash CM7 Beta everything went well except when i rebooted it got stuck at the dual core screen. After trying everything, I decided to flash back to stock since cm7 wouldn't boot. My question is now that I flashed back to stock do I need to re-unlock my device? Does it stay unlocked? Can I just root it and retry CM7 again?
it happens to me too im reading on the forum but i dont think the bootloaders remain unlock cuz when u do the process it say that in the warnings
No one knows?
I read that once you unlocked you are unlocked forever because when you unlock it kills a fuse but you can cover up the 'unlocked' message so the average joe (such as ATT or Best Buy employee) wouldn't know you unlocked for insurance purposes.
I've also read posts though, like you, that state that it does re-lock the bootloader, so I am confused! I dont want to try flashing again though and end up with a hard-brick!
only installing official roms after unlocking will re-lock your phone or brick it. so if you can no longer see 'unlocked' when you turn your phone on then you will need to re-unlock the bootloader.
before installing any custom roms you need to do a backup. after that, do a full wipe/factory reset, wipe cache & wipe dalvik cache. then install your custom rom, reboot, wait anything up to 10 minutes, and voila!
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
Sent from my MB860 using XDA App
konna280 said:
only installing official roms after unlocking will re-lock your phone or brick it. so if you can no longer see 'unlocked' when you turn your phone on then you will need to re-unlock the bootloader.
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Might want to do some reading and research. This has all been discussed previously in a couple of threads with links supporting a hardware unlock. Nobody has provided any proof of a software only unlock as of yet. Would appreciate if you posted where you got your information.
Cheers!
konna280 said:
only installing official roms after unlocking will re-lock your phone or brick it. so if you can no longer see 'unlocked' when you turn your phone on then you will need to re-unlock the bootloader.
before installing any custom roms you need to do a backup. after that, do a full wipe/factory reset, wipe cache & wipe dalvik cache. then install your custom rom, reboot, wait anything up to 10 minutes, and voila!
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+1
Can you provide a link that this is indeed a software lock?...
Sent from my GT-I9000 using xda premium
CaelanT said:
Might want to do some reading and research. This has all been discussed previously in a couple of threads with links supporting a hardware unlock. Nobody has provided any proof of a software only unlock as of yet. Would appreciate if you posted where you got your information.
Cheers!
Click to expand...
Click to collapse
Sorry, when i say software based i mean the use of software (using programs to flash files) to modify hardware. hardware based unlocking would mean having to modify hardware, such as soldering or other means of modifying/replacing components.
konna280 said:
Sorry, when i say software based i mean the use of software (using programs to flash files) to modify hardware. hardware based unlocking would mean having to modify hardware, such as soldering or other means of modifying/replacing components.
Click to expand...
Click to collapse
Soo..
You start a new thread about a topic that already has 17 threads dedicated to it.
You clearly dont understand how the current unlocking process works.
You claim to know of a new sw unlock, but even after being asked a few times will not elaborate or give a link or other info about it.
And your making up your own terms depending on what makes sence to you.
That settles it. You win the lolthread of the day, and were not laughing with you.
let's simplify:
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
This unlocks the bootloader through the use of software, does it not?
http://tinyurl.com/6gwycaq (explains what a bootloader is)
Plus... I didn't start the thread. You might need to do a little reading on that.
I've clearly unlocked, rooted, and installed a new ROM on my atrix (i initially used the gingerbreak app to root it, but decided to change the ROM at a later date, so unlocked it fully)
I don't claim to know of a sw unlock. I merely stated that software is used (RSD lite, drivers etc) to carry out the unlocking procedure.
Oh, by the way, it's "WE'RE not laughing with you" (not very nice ) and "YOU'RE making up your own terms". Little bit of research for you, if you want
konna280 said:
...
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
...
Click to expand...
Click to collapse
I think you're mistaken, it's a hardware lock. There has not been a software only solution shown. Since I have gone through the steps you described, and then re-unlocked my bootloader, the two processes were different (unlocking vs. re-unlocking), meaning that something changed when I unlocked the bootloader.
http://en.wikipedia.org/wiki/Antifuse#Antifuses_in_integrated_circuits
Trust me, this stuff is in all the ICs that you use.
Ok then, i apologize for not doing my research
I just ASS-U-MEd that if it can be re-locked then there is no modification taking place to the hardware itself (such as blown fuses - I'll admit though I only recently heard about eFuse's/Antifuse's as I've never dealt with them before, and therefore didn't know that the Atrix had them)
Thanks for the info.
lockety lock lock lock Lmfao
Im still laughing. No apostraphes needed.
WiredPirate said:
Im still laughing. No apostraphes needed.
Click to expand...
Click to collapse
nvm lol
10char
reunlocking is the same presedure which you did before. just you dont need to do the fastboot unlock oem.i did it and reunlock 2.3.4 telstra
This is my primary concern.
Quote from toastcfh in the one x forum TWRP thread. ......
no, USB mount does not work in recovery. It appears to be locked out in recovery mode. the workarounds to get it working are one of two things.
(1) fastboot boot awesomeRecovery.img (this works because fastboot then boots recovery on the boot/temporary partition. So the you're not actually in recovery mode
(2) Offmode (this works because again you're again not technically in recovery mode. It uses the recovery ramdisk, kernel, and binaries but its still not technically recovery.
On that note I've seen suggestions that it's possibly a recovery issue with cwm and twrp. Unfortunately it doesn't appear to be the case. If it were then in CWM u wouldn't have usb when u fastboot boot the recovery or in offmode (fair assumption since both these options use the same kernel, ramdisk and binaries as recovery?). Can it be fix? Not that i know of. It looks to me like a total radio or bootloader lockout from using USB in recovery. Which means on a radio or bootloader level USB is disabled in recovery mode.
On that note I think we should raise the point to HTC that this locking down of the device does not suite our needs.Key points of fail would be as follows.
(1) Can NOT flash the boot partition from recovery. I've personally contacted HTC on this numerous times and they seem to just not care. Responding with "It's a security issue" and so forth. I would love to know how this is a security issue of any sort. Every other Android device has this ability except HTC devices since they started the HTC unlock ordeal. It's utter fail IMHO and HTC should listen to our needs .
(2) Can NOT flash recovery or boot partitions from system. This issue is NOT a deal breaker and isn't so bad when it comes down to the nitty gritty. But since the issue above exists, flashing with applications like htc dumlock and such were our only options. These work around apps cant be used to flash now because of the lockpout from system and it wouldn't be such an issue if HTC didnt lock us out in recovery from flashing boot.
(3) Can NOT flash P*IMG.zips in hboot/bootloader anymore. For the unlocked device running a custom firmware this is a must. Specially when radio updates and such are needed from the OEM. We seen a big use of this on the Sensation when HTC updated the device from Gingerbread to Ice Cream Sandwich. The update required new hboots, radios, and partitioning to actually use. So in that instead of having to flash a RUU Which didn't exist the only choice was to flash a custom P*IMG.zip that included all the radios and images need to run the builds. At this point we can't update those image/partitions without flashing an RUU. This makes no since and doesn't seem to do anything but make things more difficult on the unlocker to customize and modify their device.
(4) If all the conditions above HAVE to exist. Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
(5) WHAT WAS THE POINT OF HTC UNLOCK? I was to reach out and except us as a community. It was to keep us from having to exploit their firmware and look for holes to gain control of a device we rightfully own. WHAT DID HTC UNLOCK DO? It unlocked the devices at first and with each new revision of the unlock it gets more locked down and harder for us to use it as intended. WHAT DOES THAT LEAD TO? It leads to us hoping someone will take the time out of their life and exploit HTC's firmware so we can have access and control of our devices. I mean, it's bad when u have people poking a device with a paperclip to get a device unlocked to avoid a official unlock.
Bottom line; I'm personally fed up with HTC's unlock. It's absolute crap! It does not serve the purpose it was intended and only makes things harder then they were before. As a devoted HTC customer it has me questioning if my next device will be an HTC. With all the other options that would allow me to spend less time trying to gain proper access to my device and more time actually having fun with it, why choose HTC? Everyone else is shying away for these same issues. Everyone with an HTC unlocked device waits for someone to exploit HTC's firmware and give them a proper unlock. Why not just choose a device without the locked down/unlock instead? IDK but HTC needs to step up and listen to us. Every HTC forum with an HTC Unlock is screaming for these issues to be fixed.
My call to HTC is to fix these issue and/or give us proper documentation on flashing firmware to our devices via custom recoveries. The boot flashing lockout is dumb, pointless, and in NO WAY a security threat AT ALL and is nothing more then a CRAP RESPONSE to something that they sould be working to correct, instead of ignoring. In the end its hurting HTC's relations with developers and is ultimately doing the opposite of what it's original intent.
HTC, PLEASE READ AND LISTEN!!!11ONEone
To everyone else, SPREAD THE WORD!!!ONEone
Click to expand...
Click to collapse
This comes straight from toastcfh himself.
I think that if we all send an email to customer support and follow up something may come of this. Copy what toastchf said into an email send it everyone and then follow up until you get someone who cares. Then tell them about all those people who aren't doing this because they are fed up and switching to Samsung devices.
Sent from my EVO 3D S using XDA
you should edit your post to put his Quote in actual [ QUOTE=toastcfh;25407373]....(quoted post text goes here)...[/QUOTE ] tags(just remove the "space" between the first and last bracket...like I have done so below.
toastcfh said:
no, USB mount does not work in recovery. It appears to be locked out in recovery mode. the workarounds to get it working are one of two things.
(1) fastboot boot awesomeRecovery.img (this works because fastboot then boots recovery on the boot/temporary partition. So the you're not actually in recovery mode
(2) Offmode (this works because again you're again not technically in recovery mode. It uses the recovery ramdisk, kernel, and binaries but its still not technically recovery.
On that note I've seen suggestions that it's possibly a recovery issue with cwm and twrp. Unfortunately it doesn't appear to be the case. If it were then in CWM u wouldn't have usb when u fastboot boot the recovery or in offmode (fair assumption since both these options use the same kernel, ramdisk and binaries as recovery?). Can it be fix? Not that i know of. It looks to me like a total radio or bootloader lockout from using USB in recovery. Which means on a radio or bootloader level USB is disabled in recovery mode.
On that note I think we should raise the point to HTC that this locking down of the device does not suite our needs.Key points of fail would be as follows.
(1) Can NOT flash the boot partition from recovery. I've personally contacted HTC on this numerous times and they seem to just not care. Responding with "It's a security issue" and so forth. I would love to know how this is a security issue of any sort. Every other Android device has this ability except HTC devices since they started the HTC unlock ordeal. It's utter fail IMHO and HTC should listen to our needs .
(2) Can NOT flash recovery or boot partitions from system. This issue is NOT a deal breaker and isn't so bad when it comes down to the nitty gritty. But since the issue above exists, flashing with applications like htc dumlock and such were our only options. These work around apps cant be used to flash now because of the lockpout from system and it wouldn't be such an issue if HTC didnt lock us out in recovery from flashing boot.
(3) Can NOT flash P*IMG.zips in hboot/bootloader anymore. For the unlocked device running a custom firmware this is a must. Specially when radio updates and such are needed from the OEM. We seen a big use of this on the Sensation when HTC updated the device from Gingerbread to Ice Cream Sandwich. The update required new hboots, radios, and partitioning to actually use. So in that instead of having to flash a RUU Which didn't exist the only choice was to flash a custom P*IMG.zip that included all the radios and images need to run the builds. At this point we can't update those image/partitions without flashing an RUU. This makes no since and doesn't seem to do anything but make things more difficult on the unlocker to customize and modify their device.
(4) If all the conditions above HAVE to exist. Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
(5) WHAT WAS THE POINT OF HTC UNLOCK? It was to reach out and accept us as a community. It was to keep us from having to exploit their firmware and look for holes to gain control of a device we rightfully own. WHAT DID HTC UNLOCK DO? It unlocked the devices at first and with each new revision of the unlock it gets more locked down and harder for us to use it as intended. WHAT DOES THAT LEAD TO? It leads to us hoping someone will take the time out of their life and exploit HTC's firmware so we can have access and control of our devices. I mean, it's bad when u have people poking a device with a paperclip to get a device unlocked to avoid a official unlock.
Bottom line; I'm personally fed up with HTC's unlock. It's absolute crap! It does not serve the purpose it was intended and only makes things harder then they were before. As a devoted HTC customer it has me questioning if my next device will be an HTC. With all the other options that would allow me to spend less time trying to gain proper access to my device and more time actually having fun with it, why choose HTC? Everyone else is shying away for these same issues. Everyone with an HTC unlocked device waits for someone to exploit HTC's firmware and give them a proper unlock. Why not just choose a device without the locked down/unlock instead? IDK but HTC needs to step up and listen to us. Every HTC forum with an HTC Unlock is screaming for these issues to be fixed.
My call to HTC is to fix these issue and/or give us proper documentation on flashing firmware to our devices via custom recoveries. The boot flashing lockout is dumb, pointless, and in NO WAY a security threat AT ALL and is nothing more then a CRAP RESPONSE to something that they sould be working to correct, instead of ignoring. In the end its hurting HTC's relations with developers and is ultimately doing the opposite of what it's original intent.
HTC, PLEASE READ AND LISTEN!!!11ONEone
To everyone else, SPREAD THE WORD!!!ONEone
This is the future of HTC unlock and each new device it gets worse. Maybe HTC will listen and address these issues, then again maybe we will just need to find another OEM that supports us and does listen.
Click to expand...
Click to collapse
I read this last night. The man is absolutely correct. I am actually going to write a similar one about Asus with Transformer Prime unlock. Reading his post inspired me. Lol. All his points are extremely valid. It seems that there are manufactures who want to lock people out, makes us wait for them for updates and fight the dev community anyway possible. Then, it seems others are the exact opposite. Other manufacturers would rather the devs here fix it and they don't hear from us. The latter of the two is probably smarter. There are issues with every phone but the ones who are more dev friendly don't catch as much crap for it because at least they are fully open and the devs here can try to fix it.
Sent from my Anthrax infected 3D!
If I've helped you in any way... hit the "Thanks" button.
wait so you "thank" me but dont take the little sec to edit your post and fix it? lol
sgt. slaughter said:
wait so you "thank" me but dont take the little sec to edit your post and fix it? lol
Click to expand...
Click to collapse
Lol s off can be good if you know what your doing . But it can be a curse for those that have no idea . Such as you can screw somethin up .
I think htc isn't bad they just don't want a bunch of folks brickin and frying the CPU on a phone and sending it in sayin it was htc fault .. Tellin em fix it when it was a noobs fault.
Sent from my PG86100 using xda premium
sgt. slaughter said:
wait so you "thank" me but dont take the little sec to edit your post and fix it? lol
Click to expand...
Click to collapse
You're a mod, fix it yourself...
Vdubtx said:
You're a mod, fix it yourself...
Click to expand...
Click to collapse
That's not a mods job. Lol..
Sent from my PG86100 using xda premium
Vdubtx said:
You're a mod, fix it yourself...
Click to expand...
Click to collapse
Not Mod of this forum u dork. lol
sgt. slaughter said:
Not Mod of this forum u dork. lol
Click to expand...
Click to collapse
Lol Where is a donky smiley .
Sent from my PG86100 using xda premium
Sorry if this is posted before or buried in the mountain of threads, but from what i've read so far, does the root method actually give you S-OFF? I don't want to root it if i wont be able to flash roms. Also, when i plugged in my device the driver updated and its 2.0.7.3. Does that mean i dont need to download the drivers?
tampered just means rooted if you want to unlock your bootloader so you can flash custom roms.click on the link below and it has instructions.
http://forum.xda-developers.com/showthread.php?t=1690919
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1690919
There is no S-Off for this phone as of yet, but I don't think we'll need it. Root is different than S-Off.
S-Off is closer to an Unlocked bootloader, which the post I directed to you does. With this method you'll be able to flash roms using TWRP.
wobbies said:
Sorry if this is posted before or buried in the mountain of threads, but from what i've read so far, does the root method actually give you S-OFF? I don't want to root it if i wont be able to flash roms. Also, when i plugged in my device the driver updated and its 2.0.7.3. Does that mean i dont need to download the drivers?
Click to expand...
Click to collapse
Currently there is no S-Off method available for this phone (as of right now). But we've come to find out that we don't need S-Off that much on this phone.
Even with S-On, you can flash roms, mods, tweaks, etc. Hell you can even flash Radios now (which use to be reserved for S-Off).
The current method is HTCDev Unlock. It does mark your bootloader as 'tampered'. But when am I going to actually use a manufacturer warranty or somebody like Sprint is actually going to check the Bootloader. But even that is different from root. You can root, which will give you root access. Then if you want you can unlock the bootloader which will allow you to flash a custom recovery which will allow you to flash Roms, etc.
Edit: I've been ninja'd.
Thank you very much guys
So in order to flash custom ROMs I have to unlock the bootloader (and void the warranty)?
sracercelica said:
So in order to flash custom ROMs I have to unlock the bootloader (and void the warranty)?
Click to expand...
Click to collapse
yes, but you can make it seem as if you never unlocked by ruu'ing. sprint will never know... if it gets that bad, "somebody stole it."
Rydah805 said:
yes, but you can make it seem as if you never unlocked by ruu'ing. sprint will never know... if it gets that bad, "somebody stole it."
Click to expand...
Click to collapse
Well sprint only gives 30 days warranty anyways so I am actually worried about HTC's warranty. I dont have the insurance through Sprint (which I heard is going to increase to 10 bucks a month).
I know that i can pay to sim unlock our desire 610 but surely s-off has been achieved so we can change our CID to sim unlock our device for free??
zubairali00 said:
I know that i can pay to sim unlock our desire 610 but surely s-off has been achieved so we can change our CID to sim unlock our device for free??
Click to expand...
Click to collapse
We....don't have s-off
ninjasinabag said:
We....don't have s-off
Click to expand...
Click to collapse
And no one is working on it?
zubairali00 said:
And no one is working on it?
Click to expand...
Click to collapse
I have the same problem , i buy htc desire 610 vodafone uk , with lock, i root the phone, erase all, install recovery - rom AT&T ,
but only way is buy unlock code service... and pay 26 $ approx :crying:
zubairali00 said:
And no one is working on it?[/QUOTE
There is/was someone in the general board who received and is selling s-off 610s. (No actualperson bought from his sale, so I don't know if he was lying or if it was an error)
ClearD is working on a Rom, so he's probably the only person currently with an idea of how to go about it. Like I said though, he's been working pretty hard on the Rom so he may be reticent to start a new project.
Click to expand...
Click to collapse
Phew. I appreciate the thought, but that is way beyond my level of experience. However, I do have information of someone working on an s-off for our device. It's probably going to be a while until it's finalized, but it will work on a wide range of devices, similar to Sunshine. It will also be a paid app, like Sunshine. But, I'd pay for s-off myself. It's important. Lol
ClearD said:
Phew. I appreciate the thought, but that is way beyond my level of experience. However, I do have information of someone working on an s-off for our device. It's probably going to be a while until it's finalized, but it will work on a wide range of devices, similar to Sunshine. It will also be a paid app, like Sunshine. But, I'd pay for s-off myself. It's important. Lol
Click to expand...
Click to collapse
Can you elaborate a little on that? I know s-off is important but if the bootloader is unlocked and we have a kernel doesn't that mean we can flash unsigned zips already?
Or is it more about using it on other carriers? I have no intention but if I gave this phone to someone, could they take it to say verizon and activate it?
I'm just confused. I guess I don't know the difference between s-off an unlocked bootloader for practical reasons.
Unlocked bootloader lets us flash system, boot, and recovery partitions. That's about it. We can't change the Cid or splash screen or radio image, as those are still security protected. Like the warning screen from the early root method? It's the splash screen. We can remove that once we get s-off. Basically s-off lets you change/flash anything.
Is anyone try "oneclick root" option from MobileGo PC Suite?
On Youtube is posted video(animated presentation)how to root Desire 610 with MobileGo.
On Wondreshare Mobilego Forum is even link to additional root tool: "CC Root" http : //goo.gl/IsyzC
Some with D610 as backup phone maybe wish try, no word about S-OFF, reverse option (from root) is not supported.
P.S.
"oneclick root" option is available in free version of app.
We've already got a root tool... A very simple root tool. That I made. It doesn't s-off.
ClearD said:
We've already got a root tool... A very simple root tool. That I made. It doesn't s-off.
Click to expand...
Click to collapse
Is not bad thing knowing if exist more than one option how to root 610, true is that no any feedback about MobileGo root method on any htc phone.
I would prefer wish to hear from you an answer like: I could try...
Thx
We already have more than one root method. And they're simple. There in fact doesn't need to be more than one, because the bootloader can be unlocked and one is all there will ever need to be, because of this. It's as easy as flashing recovery and flashing root through recovery. That's it. My tool just automates that process. Why use something untested when we already have one that will always work, without fail?
Also this thread is about sim unlocking, not rooting. S-off is not root and we don't have s-off capabilities yet. Back on track.