Related
Hi guys. Becouse much people in thread [DFT][Updated!#2] HSPL / RSPL for HTC WP7 First Generation do not know, how to downgrade SPL to be able HSPL using, we can resume all known ways here. But, I have no all devices, post confirmations, please. I have got >=1 confirmations from all next mehods, but, use it carefully, it is on your own risc. For any devices no JTAG/XTC method is possible to restore factory state!
1. Two-stage way (worked for any devices only, but for all SPL states including "small" and "big" halfbrick).
Using official update parts.
Description .. in progress.
Links:
http://forum.xda-developers.com/showthread.php?t=1361577,
Google Translated Unbrick Manual.
2. ROMUpdateUtility way (worked for any devices only, for equal brand/region only, not for halfbricked, but PC USB connection is needed only).
EDIT: ATTENTION: DO NOT TRY METHOD NR. 2. It is really, that this method can work only on any device, but more devices may be fullbricked!
Using original ROM parts (Thanks to Ansar).
Description .. in progress.
Links:
Google translated from WMMania.cz
EDIT> Better way seems original SPL downgrading RUU only - see http://forum.xda-developers.com/showthread.php?t=1411904
3. Full GoldCard (worked for all devices, all brand/region, for intacted SPL and "small" halfbrick only, but not for "big" halfbrick). You need Y-Cable (may be simplified - see picture - you nedd 2,5'' external disc usual additional power cable and very chip USB A/F-A/F junction only).
Using original ROM parts.
Description .. in progress.
One way only, which is for Trophy device fully confirmed.
Links:
http://forum.xda-developers.com/showthread.php?t=1359498
4. Simplified "like" GoldCard (worked for any devices, equal brand/region only, for intacted SPL and "small" halfbrick only, but not for "big" halfbrick). You need Y-Cable (may be simplified too), but you do not need second WM/Android/Linux device for CID reading.
Using original ROM parts.
Description .. in progress.
Links:
Google Translated Unbrick Manual.,
http://forum.xda-developers.com/showthread.php?t=1371073
Nice idea all in one thread. If you want, you can use my movie about that.
http://www.youtube.com/watch?v=uctenG08Fj8
Please clear up my mixed head.
I have a O2 Branded Htc 7 Pro. I am stuck on 7720.68
I cant restore any of my premango states and I cant boot to usb host mode anymore. (800b010a or 8018004D or...)
So there is no way to fix my bootloader at the moment right? Official Updates from Zune (HTC Updates or 7740) dont work either. However I have the possibility to use the cab sender togo to 7740, but that is the only cab that works this way.
Help me please what can I do?
After Mango halfbrick
Hi kaemen. Have you tried http://htc7pro.howto.cz/O2ODEHTGoldHTCOEMUpdate2011.cab posting by cab sender? If success, you can downgrade SPL by GoldCard. But, it is for your risc, cca 1% of flashing results fullbrick.
Google translate page http://htc7pro.howto.cz/Unbrick/UnbrickCesky.htm or see all my posts in HSPL XDA thread. Martin
this is seriously bugging me now.
I dont have backup before 7720,
i dont have y cable or anything
spl is at 5.1
now can anyone simplify what needs to be done?
I dont understand why this is so complicated for everyone. I have a HTC Mozart on DFT 7720 and i can easily downgrade by restoring to a stock Pre-Mango ROM. Just plug in the device while holding the volume key to get the multi color screen and then run the RRU Rom .exe and there you go.
Im probably missing something here arnt I?
I get an error 80180048
Too danger
fahdriyami said:
I dont understand why this is so complicated for everyone. I have a HTC Mozart on DFT 7720 and i can easily downgrade by restoring to a stock Pre-Mango ROM. Just plug in the device while holding the volume key to get the multi color screen and then run the RRU Rom .exe and there you go.
Im probably missing something here arnt I?
Click to expand...
Click to collapse
It is not so simply. This method can work, see point 2 from my first post. But, 1. it is not working on halfbricked device, 2. it can fullbrick phone in any combination of RUU-Device-Brand-SPL5.x.
Better way seems original SPL downgrading RUU only - see http://forum.xda-developers.com/showthread.php?t=1411904
the post written by OP is seriously confusing. "any device only"?? what does that even mean? if it were to say "some device" or "certain devices ony" it would have made more sense. right now im just to baffled by the sentences to even try any of the listed solutions.
bevoc said:
the post written by OP is seriously confusing. "any device only"?? what does that even mean? if it were to say "some device" or "certain devices ony" it would have made more sense. right now im just to baffled by the sentences to even try any of the listed solutions.
Click to expand...
Click to collapse
This article is a year old, from the time of the first WP7 generation. Also, several people promised linguistic correction and no one did it. I am not able to write english right myself, this is translated with Google help. But, enough people used it successfully last year. Many recent articles is there now on XDA. I writed here first posts about halfbrick solution possibility without special hardware and about SPL downgrade too. But, they are very old, you can find many recent and better posts here.
Today I spotted this blog item http://blog.htc.com/2012/04/your-phone-your-thoughts-tell-us-what-you-think/ I think we should start post our concerns about not being able to gain a proper unlock.
(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
From this thread : http://forum.xda-developers.com/showpost.php?p=25407373&postcount=19
I have posted the same in Facebook Page and Tweeted it. I think we should be more aggressive.
what about groubal?
Posted anyway :s
"There has been overwhelmingly customer feedback that people want access to open bootloaders on HTC phones. I want you to know that we've listened. Today, I'm confirming we will no longer be locking the bootloaders on our devices. Thanks for your passion, support and patience," Peter Chou, CEO of HTC
Please S-Off your devices as promised, your unlock is not a true unlock and it is still heavily restricted. We can't flash official RUUs in this weak htc-dev unlocked state! Please fulfil your promise!
You have some valid points, but you do realise us tinkerers aren't htc's only customers right? Most businessmen now use smartphones like the one X and they certainly do not fiddle with their phones, nor do they accept that their phone comes with serious security flaws potentially opening their device up to strangers or corporate espionage. This point, however, could be used both for and against this fact. For example, if HTC officially provided S-OFF via htcdev then they could avoid people developing exploits for their device while also causing the device to be factory reset when it is applied. The downside of this is their products could get a reputation for being unstable or whatever (people seeing my device for example, and getting the idea that all one X's are on the verge of exploding)
That doesn't seem to be an issue for Google or Samsung, so I don't think its a really valid point.
Rekoil said:
You have some valid points, but you do realise us tinkerers aren't htc's only customers right? Most businessmen now use smartphones like the one X and they certainly do not fiddle with their phones, nor do they accept that their phone comes with serious security flaws potentially opening their device up to strangers or corporate espionage. This point, however, could be used both for and against this fact. For example, if HTC officially provided S-OFF via htcdev then they could avoid people developing exploits for their device while also causing the device to be factory reset when it is applied. The downside of this is their products could get a reputation for being unstable or whatever (people seeing my device for example, and getting the idea that all one X's are on the verge of exploding)
Click to expand...
Click to collapse
I understand mate .. That's why the S-OFF should be optional. I personally working in a co-operate enviorment most of the them won't go for Android since our enterprise applcation doesn't work well (Like deployment of software apps etc.) most of them prefer Blackberry for Windows based phone. That's why Windows 8 phone comes with secure boot and large scale application deployment with same tools used in Windows so they can convert the remaining BB users to Windows. Android has a long way to get attention from enterprise users. For now think it's an entertainment OS. Sony went a long way in this case they allow complete unlock even help FreeXperiaTeam with development of CM. Sooner or later our devs will find a way to S-OFF why not HTC offer it proactively and creative a good will against devs like Sony did.
S-off on any HTC phone do not I repeat do not open any other security issue ie a business would not leave such possibility open some business develop there own software for phones etc and still do they was doing it with the old pda phones and HTC pda phones with HTC to stop locking there phones allows this option again to a business.
A business wouldn't leave a device open as they would lock them there selfs via encryption etc so people arguing over its opening security holes is an invalid point other devices are open ie Samsung etc so why not HTC all other HTC that have been exploited to allow the same hasn't broken any security regarding networks or the ability to change serials etc as this info is on a write once chip and can not be over written like some other devices in past
The reply from HTC ceo has just made my day it's great news I just hope it true to the word
And believe it or not there loads of corporate business are using android devices to its full existent well here in the uk they are as its such a powerful operating system and not just for entertainment I speak from experience I use my phone for business and use a lot of business apps etc so my phone is not just for entertainment purposes etc
Everyone's concern over security is a fair statement but not valid reason not to unlock and am glad to hear HTC agree now.
Sent from my HTC One X using xda app-developers app
@dryan433: Dude, what are you talking about? Have you ever heard about something called punctuation or capital letters?
Sent from my HTC One X using xda app-developers app
My phone does not show always has a red "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action, even pause makes turning on and off it goes back to that screen, it happened while trying to install RECOVERY, what can I do, I can sign in to bootloader
boaz01 said:
My phone does not show always has a red "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action, even pause makes turning on and off it goes back to that screen, it happened while trying to install RECOVERY, what can I do, I can sign in to bootloader
Click to expand...
Click to collapse
First advice I can give you, is you should post this in your thread for non international(tegra version) thread. They will be able to help you. But it might solve a problem if you just install a new rom. But I highly recommend to go to the at&t hox thread.
I followed this guide and it all worked fine until I got to the when I reboot the phone after installing the file it boots to the screen where it says htc and then does nothing I can still get back to the bootloader but have no idea what to do there, this is my first time trying to root a phone. It won't let me post the url for the guide but it was called htconeroot . com
I personally strongly advise again using those random "root" websites. The info is often outdated (and not organized in a way that would warn you of such). And those websites often just steal methods and files from xda (giving little or not credit), anyway. Can't tell you how many times I've seen folks get stuck by those websites, and come running here for help.
Even if you can't post a link, you at least need to be more specific as to what exact steps you took. I know you're new here, and the best way to ask for help is to provide as many details and specific as possible. Asking for help with a couple poorly typed, run-on sentences is not the best way to get help. It just wastes time as we need to ask you for all the proper info:
Describe each step you did in detail.
Did you use a toolkit, if so which one?
What file did you flash exactly that caused the issue?
What version TWRP?
What version SuperSU?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting). Or at least tell us what OS number it says on the bootloader screen (along with hboot and radio number).
@redpoint73 This is actually a good website. It's run by @zedomax who is a member (although I don't know if he's around much anymore) and he always gives proper credits back to XDA.
To tell the truth, this is what I used to root my M8, as I was unfamiliar with HTC devices (coming from Nexus and Samsung) and had used his tutorials for both previous brands when I was new to rooting.
The best thing about his tutorials is that he has a YouTube video to go along with his printed instructions (and how many time have you seen this asked for?). But I digress.
You are of course correct asking for SU and TWRP versions. That tutorial is over 2 1/2 yrs old. It was made when the M8 first came out.
To @LaggyToast, you need the latest version of SuperSU (sorry, but all I have for a link is a direct download) and the latest version of TWRP.
Follow the same instructions, but use the updated versions so you have something that is compatible with the newer firmware.
xunholyx said:
@redpoint73 This is actually a good website. It's run by @zedomax who is a member (although I don't know if he's around much anymore) and he always gives proper credits back to XDA.
The best thing about his tutorials is that he has a YouTube video to go along with his printed instructions (and how many time have you seen this asked for?). But I digress.
Click to expand...
Click to collapse
I'll take your word for it, that that website is okay. But frankly, there are just too many of those random "root" websites for me or most folks to keep track of. Folk will often just Google for how to root, trusting these websites without knowing if they are legit or not, and wonder why things go south (when they invariably do - especially when the info is outdated). All the proper info is here on XDA. And more importantly, we have an open forum with a great community that will help when folks run into problems (which is something almost all of the random "root" websites lack).
I also don't see YouTube tutorials as necessarily a good thing. Folks keep asking for videos, primarily (although maybe not always) because they are too lazy to properly take the time and effort to read, learn, and understand. All too often, folks use the video as a shortcut to proper learning, and just mimic the video. But unfortunately, a video is never going to contain all the details and nuances of written guides; nor help much when things go wrong.
I can see how videos may be a handy addition, when used properly in conjunction with proper written guides, and the requisite learning, reading and understanding. But videos are too often as an inferior replacement for written guides and proper learning.
Just my personal opinion, of course.
Hi,
My wife HTC m9(UK, Vodaphone, latest stock ROM, No root) was turned off last night to charge.
When booted up it does the below. It does not load into the OS. Every boot loops into the below.
https://drive.google.com/file/d/0B8n21CQX7535cjF4MnZqV2E1dGM/view?usp=sharing
It says the software has been modified?
My wife was very insistent that I never root or change ROMS on her phone.
Does anyone have a fix or is this send off for replacement?
Any advice would be greatly appreciated.
Thanks
Ca1v
ca1v said:
Hi,
My wife HTC m9(UK, Vodaphone, latest stock ROM, No root) was turned off last night to charge.
When booted up it does the below. It does not load into the OS. Every boot loops into the below.
https://drive.google.com/file/d/0B8n21CQX7535cjF4MnZqV2E1dGM/view?usp=sharing
It says the software has been modified?
My wife was very insistent that I never root or change ROMS on her phone.
Does anyone have a fix or is this send off for replacement?
Any advice would be greatly appreciated.
Thanks
Ca1v
Click to expand...
Click to collapse
What happens if you try to boot to Download Mode? I guess you see the black screen that is mentioned in Q7, right? If that's the case there isn't much you can do...
Download mode seems to be working (https://drive.google.com/file/d/0B8n21CQX7535cEFhTlpnajF5anM/view?usp=sharing)
If this is the case, can you point me in the right direction to get resolved?
Many thanks for the help
Flippy498 said:
What happens if you try to boot to Download Mode? I guess you see the black screen that is mentioned in Q7, right? If that's the case there isn't much you can do...
Click to expand...
Click to collapse
Download mode seems to be working (https://drive.google.com/file/d/0B8n...ew?usp=sharing)
If this is the case, can you point me in the right direction to get resolved?
Many thanks for the help
Interesting. Your video in post 1 shows a security warning. That means that the OS got deleted. This is only possible if you unlock the bootloader and delete it manually via TWRP or if the EMMC gets broken. Since the phone's S-ON and its bootloader is locked and not unlocked or relocked I assumed that the latter happened*.
As long as the download mode is working you can restore the system with the help of a RUU. Instructions can be found in the thread I linked in my last post. Be aware that all data on the phone is going to get erased.
* Well, it is possible to get the phone's status back to S-ON and locked with S-OFF but you said you never tinkered with that phone...
Flippy498 said:
Interesting. Your video in post 1 shows a security warning. That means that the OS got deleted. This is only possible if you unlock the bootloader and delete it manually via TWRP or if the EMMC gets broken. Since the phone's S-ON and its bootloader is locked and not unlocked or relocked I assumed that the latter happened*.
As long as the download mode is working you can restore the system with the help of a RUU. Instructions can be found in the thread I linked in my last post. Be aware that all data on the phone is going to get erased.
* Well, it is possible to get the phone's status back to S-ON and locked with S-OFF but you said you never tinkered with that phone...
Click to expand...
Click to collapse
Just thought I'd bring to your attention that apps are now being written that will try to obtain root without you knowing. The reason is that they can steal any information they want and sell it to corporations for as little as 4 pence/6c a record.
It is possible that it is a failed root by an app.
"I'm safe, I only download my apps from google playstore" - nope, you're not.
"I only use signed apps and the checksum is always correct" - nope, checksum can be matched with padding.
"I only use external sources to update genuine apps" - nope, see the Google playstore comment above.
"I have all my security and privacy set to super strict, I have my apps verified by google" - nope, still not secure because alerts are only written when the malicious/bad code is found.
Be warned, my fellow xda'ers. There is a whole new breed of security breach and it is terminal to root as a whole. Apps like kingoroot etc are issuing the wrong type of people with the wrong type of information and they are using it for the wrong purposes.
Google will stuggle to put a lid on these types of apps because they attack the hardware for access to software (a simple memory buffer overflow attack), inject a few lines of code and you're in, permanently. It will eventually result in a total lockdown at the manufacturer and bye bye root access, roms, mods etc, you'll get what you're given.
How do we prevent this?. We don't and we can't. We just have to sit back and watch as the world takes our privacy while bricking our devices one by one just to "try" to earn a poxy 4p.
Beamed in by telepathy.
@shivadow: I'm actually not sure what you're trying to achieve with your post. Malicious apps that can root your device without letting the user know about that exist since several years now. (Click here for a random example from 2011) Smartphones aren't completely safe and they never were. Everyone who's claiming the opposite either doesn't know what he/she is talking about or is simply lying.
To name just a few more android security flaws/exploits that emerged in the past: rageagainstthecage, gingerbreak, heartbleed, stagefright, the master key vulnerability, the futex bug, rootnik...
All of these have more or less been used for manipulating android phones. There is no absolute security. Android is still as secure/insecure as it's always been.
In addition, several OEMs are already trying to prevent their customers from rooting their phones since several years. Samsung's KNOX is a perfect example. (I don't want to discuss whether they're successful. That's a whole different topic.)
But let's get back to the deleted OS of the OP's phone: I've never heard about failed root attempts that erase a complete system partition. Therefore, I highly doubt that a malicious app caused all the trouble. Failed root attempts may cause a bootloop but they don't wipe your phone. Just think about the following: How should the dev of such app gain money if the app deletes OSes? Without OS there is no information you can steel and if you have no information you could sell/abuse/whatsoever you don't gain any money. Oh and not to forget that most apps on the play store already collect more than enough data from your phone they can sell afterwards without having to root it.
I meant failed root could be the cause, if the op didn't then who did?. If no-one modded it then dead nand is the only player..
I agree with every thing else but I don't trust those apps that try to gain root in the background to steal data and I think it's too easy for them to bugger your phone just for the sake of making a few coins. Face it, if I was doing it, once I had what I wanted I wouldn't care about the device. Sod the gracious exit and all that jazz.. No evidence, no conviction.
Maybe I'm being ott but my questions and points are still valid.
This is a proper "who dunnit" because I doubt it died of its own accord.
Knox is for businesses btw. If knox is triggered, which is very easy to do, the business is advised not to buy the device as it "may" have been compromised. But if no company secrets are being held on the device then it's still good to use. Knox protection was counteracted by supersu. In a nutshell, unless you run a company knox is of no concern to the everyday user.
Just thought I'd chuck that in there, I'm versed in the arts of the s3 i9300. I moved from that phone to this m9.
Beamed in by telepathy.