I've rooted and flashed custom roms many times during the years on many devices, but this is the first time I've needed to go back to stock and it didn't really go as planned.
The reason is I planned to use my old retired One X as work phone and use my work phone for other purposes and our company is using MobileIron which requires an unrooted phone and also adds several other limitations to the phone (requires a five digit pin, doesn't allow stuff on the lock screen etc.).
I was previously running a Resurrection Remix (Android 5.1) on it with the new layout, but I installed an old Philz recovery, reformatted the sd card, flashed this rom http://forum.xda-developers.com/showthread.php?t=1546970, that was supposed to be completely stock, not rooted, no busybox etc. and then also installed the stock recovery after the rom. After that I was able to take an official OTA update to fix the heartbleed bug (4.18.401.4) and I thought everything was fine.
I then registered and installed MobileIron and also that looked fine and I got a nice green checkbox that all was ok, but when I did the final step to try to connect to the corporate Exchange ActiveSync that failed and I got a mail telling me something like "Critical. Your mobile device has been detected as compromized (jailbreaked or rooted). All access to corporate information has been blocked/removed from the device.".
Does anybody know what MobileIron is looking for and if there is any way to be more stock than I currently am? I don't suppose it will check for an unlocked bootloader? I do have an old RUU lying around "RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed". But it feels wrong to use a RUU to downgrade the phone (if that's even possible on a S-ON phone?), and even if I did would I be able to upgrade to the current version using OTA's in that case? If it matters my CID is HTC__Y13.
Related
Hi,
I've had my DHD for 6 months now, and I love it, but after seeing this thread...
http://forum.xda-developers.com/showthread.php?t=1056329
I've finally decided I want to get rid of the Vodafone crap on my phone. It takes way longer to boot than it should, I have stupid apps on there, and I'm generally sick of seeing the Vodafone symbol every time I boot my phone, especially as I bought the phone from them and am not even contracted to them.
Is there an easy way to rid myself of this Vodafone branded ROM? I know next to nothing about rooting or anything, however.
After seeing the link above, I realised that I'll probably be waiting ages for Vodafone to send the update OTA, and I would really like some Gingerbread around about now. Hopefully the process will speed up my phone.
But, is there anyway I can do this without losing everything on my phone? My messages, apps, settings?
A lot of questions there - thanks in advance.
Hi, you will lose everything you don't backup.
Apps will need to be reinstalled, and settings will be lost.
If your firmware version is greater than 1.3x.xxx.x then you will need to downgrade to 1.32
Follow THIS thread to downgrade.
Once downgraded simply download & run the RUU~.exe file and it will take care of the rest.
How could I backup my apps (and settings) and restore them once updated?
My 'software version' is 1.32.178.5
Looking at the link you provided, it says...
System requirements:
Desire HD with build number 1.72 or higher
My DHD's build number is 1.32.xxx.x... Do I...not have to downgrade? Or what?
Also, since I'm running on an Australian network (Virgin), will I need to incorporate that somehow into the software I put onto the phone or something..?
You can root your phone and use clockwork to remove data/cache to go back to factory settings
as for the virgin thing, just make sure your APNs are correct and you should be fine
So I could root it and use Clockwork and my phone would basically be like a standard Desire HD that I bought new, unbranded in a shop?
yeah but you will also lose all your contacts and messages etc
i think you can use titaniumbackup to save those kind of things .. but done quote me because ive never done this, ive only rooted and cleared then flashed a new rom on
actually look up a stock RUU guide
EDIT: Just Root your phone and flash a custom rom imo
I did it .. never going back
Hmm, okay.
What about if I wanted to put something on my phone like the link I posted up top, the 2.3 'release'?
well click the ROOTED link in my sig
and do all the steps with the exception of the flashing of the MIUI.zip ... just replace it with the custom rom of your choice and bobs your uncle
i advice to back up your apps and anything else you want to keep
Hello,
I would like to create a full stock backup, I do not care for applications or settings, the only thing I want is full non-rooter, current Gingerbread with ability to install possible upcoming OTA updates.
The reason for this is simple, I want to try out different ICS roms just for fun and then go back to original, HTC Sense 2.1 powered rom.
The question is: How do I do that? I know I can handle rooting the device and installing various things but how do I get back?
Thanks!
PS A link with instructions on how to do that would be nice, I tried searching the forums and Google but nothing legit came out.
If you have already rooted your phone and installed a recovery such as ClockworkMod or 4EXT, reboot into recovery and go to the "Backup" menu and make a full backup.
In the event of problems, you can do a full wipe or factory reset, and then go to the same backup/restore menu to restore your backup from the SD card.
But if the phone is Gingerbread (it is) I have to downgrade first, correct? To Froyo 2.2. So Basically that leaves me with a copy of 2.2 while my phone came with Gingerbread in the first place.
It basically shows that I've changed (downgraded) the software, doesn't it?
stranded.eu said:
But if the phone is Gingerbread (it is) I have to downgrade first, correct? To Froyo 2.2. So Basically that leaves me with a copy of 2.2 while my phone came with Gingerbread in the first place.
It basically shows that I've changed (downgraded) the software, doesn't it?
Click to expand...
Click to collapse
If you have ALREADY rooted it, then there is no need to be downgrading back to an exploitable firmware when you've already exploited the phone. If all you're doing is installing a custom rom on an already rooted/unlocked phone then you need only flash the roms via recovery.
You would only have to downgrade the firmware if you for some reason decided to flash the original stock firmware, hboot, etc onto the phone.
But that's least as far as the backups go.
In terms of how to get the phone back to non-root/locked state there's a sticky/wiki for that, though I would find it to be a pain in the butt to have the phone rooted and unlocked and then have to go thru the process of locking it back up only to possibly risk bricking it. The more times you mess with the firmware/radio/hboot the more likely you are to brick it.
Just to make it all clear my phone is kinda new, was never rooted, that's why I'm asking. I still can't believe that HTC doesn't have an app like Xperia has, SEUS to be exact, you can fix any phone with one click. By saying fix I mean install the latest, official rom.
That's too bad there is no other way to root Desire Z.
stranded.eu said:
Just to make it all clear my phone is kinda new, was never rooted, that's why I'm asking. I still can't believe that HTC doesn't have an app like Xperia has, SEUS to be exact, you can fix any phone with one click. By saying fix I mean install the latest, official rom.
Click to expand...
Click to collapse
If never rooted there's not much of a way to make a full backup first (since most backup tools like Titanium Backup requires root).
That's too bad there is no other way to root Desire Z.
Click to expand...
Click to collapse
Well there is the HTCDev unlocker from HTC themselves, but you actually have better luck following something like cyanogenmod's wiki entry.
Something like this works quite well : http://wiki.cyanogenmod.com/wiki/HTC_Vision
You just need to make sure to triple-check all the numbers and messages, someone accidentally skipping 2 or 3 steps multiple times is just asking for problems.
But once rooted (like for my G2 I followed the cyanogenmod steps, and then went another step by upgrading my radio to the latest, I just went with a different rom after being rooted) it's usually best to keep it that way even if you decide to just flash the stock rom (i.e.: still rooted and unlocked, but simply using the original software they provide you, which can be rooted simply by having the su binary and superuser app).
The voiding of warranty usually applies to software, i.e.: you bricked the phone as a result of flashing the wrong hboot. Where as if the screen or eMMC dies, it's a hardware failure and shouldn't be voided simply because the phone was rooted (unless of course they determined you fried your CPU by running the phone at 1.9Ghz constantly).
You could just download a full version of the G2 gingerbread rom from shipped-roms.com and flash that if you ever want/need to go back to stock gingerbread.
-Nipqer
Hi,
Create a small problem for myself.
Started with 1.26.xxx (aussie version on Vodafone).
Unlocked, installed CWM, Rooted and put SuperSU on it.
Then backed up using CWM. (including SuperSU).
Installed ARHD 5.x?? I think.
Try to go back to original but only managed to recover to 1.26.xxx incl SuperSU.
Relocked.
Updated via 1.28.xxx to 1.29.xxx via OTA (including revert to associated boot.img).
Now my damn (insert any number of swearwords) sensor chip is bust.
All associated sensor functions are dead.
(First had to calibrate to get it working, now altogether dead).
Tried even factory reset, but that only goes back to 1.29.xxx Including SuperSU for some reason.
Here is my problem: I want to back to point of purchase an claim statutory warranty (different rules here from manufacturers warranty).
But I am concerned with SuperSU on it they might complain and not touch it.
How do I get back to any pure original Rom (no SuperSU)?
Tried RUU, bit was worn version.
My current ROM states:
Android 4.0.3
Software: 1.29.862.11 (Vodafone Australia I think, I am with VF Australia)
Cheers and Thanks.
PS: Tried googling, but flooded with irrelevant stuff.
This gave me cancer..
Relocking your bootloader then running the correct RUU is your best bet any day.
Uninstalling superuser may leace other relevant apps inside like busybox etc.
on xda for android and mistyping like a boss
walaway said:
This gave me cancer..
Relocking your bootloader then running the correct RUU is your best bet any day.
Uninstalling superuser may leace other relevant apps inside like busybox etc.
on xda for android and mistyping like a boss
Click to expand...
Click to collapse
Hi,
Many thanks for your reply. Looked hard but cant find the correct RUU.
Cheers
Update:
Seem to have fixed it.
1. unlocked again
2. Flashed CWM
3. Installed SuperSU via CWM
4. Removed SuperSU from within itself
5. Installed 1.29.401.11 Recovery
6. Reapplied OEM lock.
See how we go with my warranty claim re sensor chip.
Cheers
[Edit]: resolved by going S-OFF and changing the CID. Still odd this evne happened.
After trying to get XPosed Alpha working on stock Lollipop (apparently it doesn't - crashes com.android.phone, persistnetly) I tried a couple of ROMS / Backups offered here. Amongst them the Beatmod ROM (http://forum.xda-developers.com/desire-eye/development/rom-beatmod-desire-eye-android-5-0-2-t3094559) that comes with (working) XPosed (but breaks ADB and USB PassThru), and the offered flashable Lolloipop ROM offered here: http://forum.xda-developers.com/des...m-htc-desire-eye-europe-2-19-401-1-5-t3089472
Of course I made a nandroid backup of my Stock Lollipop before doing anything (I made the backup rioght after the OTA) - and it worked fine going back from Beatmod to my backup.
Howerver now (I think it started after flashign the Stock ROm I linked above - but I didn't notice it right away) after booting the system UI crashes, so does Dot View - no matter what ROM or Backup I apply. Beatmod is stuck at "Unlocking SIM card", and my recovery shows no active SIM. I THINK I accidentally screwed up the radio in the process - but I'm S-ON so I'm not qutie sure how that can even happen.
I have the unlocked international version of the eye, S-ON. Carrier is T-Moibel Germany.
Any help getting at least back to stock would be appreciated, as it seems there is no RUU available anywhere yet for this version of the phone.
Note: I'm new to debugging these things (by now I always managed to repair things myself), so please tell me what additional info is needed! I'm tech-savyy so no need to break it down in tiny pieces, no worries.
Applying my Backup from before any OTAs (Means KitKat) worked. However now, while the first OTA went through just fine, the one that updates to Lollipop stops with
Code:
Package expects build fingerprint of htc/tmo_de/htc_eyeul:4.4.4/TKU48P/402884.9:user/release-keys or htc/tmo_de/htc_eyeul:5.0.2/LRX22G/504177.2:user/release-keys; this device has htc/htc_europe/htc_eyeul:4.4.4/KTU48P/402884.9:user/release-keys
.
I guess that means it downloaded a branded OTA version, while I'm currently running an unbranded firmware - the question is, why - and why did it work the first time rigfht after I got the phone?
-> Which part did I change while flashing around that doesn't get reset when I apply the backup, and how do I get it back? As I said, I'm S-ON.
It's even worse. I tried manually flashing the firmware from the OTA ZIP and it worked. Then I tried unlokcing the bootloader again - didn't work at first, needed more than one try, but worked.
So, I guess I successfully branded my before unbranded device? How do I go back?
Last update. Issue still not solved. OTAs that I can download won't install anymore (looking for branded device but don't find it, see second post). Backup I made and ROMs downloaded end up with no Signal and crashing SystemUI, and not recognizing the SIM card anymore (My Stock KitKat backup still works fine though. Just Lollipop doesn't). I'm pretty sure the crashes are because of the SIM card issue (broken Radio? But I flasehd the firmware from the OTA that DOES include radio) though.
Why is there no RUU yet!
CID shows T-MOB101 - which would indicate a branded device (that I did not buy - I have to admit though, I didn't check the CID before all this). It downloads a branded OTA. BUt the stock system is HTC_Europe (as it should be) so the OTA doesn't install anymore. The backup form the HTC_Euope Lollipop however doens't recognize the SIM.
Apparently my CID changed. On an S-ON phone. What the ****?
Decided to go back to my S-oFF Sprint htc one m8 from over a year ago.
First thing I did was update my firmware only, no recovery no boot, firmware only. I upgraded firmware to 6.20.651.3 using this link: http://forum.xda-developers.com/showthread.php?t=2729173
I then updated my twrp from 2.8.50 to 3.0.2-0.
after I try any rom, even sprint roms, I can't get passed the hands free activation and prl update screen. It will reboot before the phone boots up. I have tried a few gpe roms and it wont get past the boot screen.
I tried loading up a nandroid i made over a year ago and its a lollipop rom that works, but still wants to go through handsfree activation. I am able to turn it off there, but want to get back to marshmallow and newer roms. I called sprint support and they said it shows as fully activated on their end.
What else should I try? Should i upgrade firmware, recovery and boot?
I hate bumping, but im out of options here. Any advice?
memekmek said:
I hate bumping, but im out of options here. Any advice?
Click to expand...
Click to collapse
I've gone through countless threads like these: http://forum.xda-developers.com/showthread.php?t=2716834
my situation seams to be unique, where my phone will actually reboot right after hands free activation, thus rendering it useless. I've been able to mount the system in twrp and delete the htc service apk, but on the marshmallow roms, i can't get LTE to work.
Im stumped. :crying:
So I've managed to read through threads and turn off hands free activation by:
1. Using wifi at initial setup (this helps get passed the initial hands free activation)
2. Mounting system in twrp, then deleting htcservice apk in twrp (this helps getting past the initial setup if its a problem)
3. freezing vdm client in titanium backup to avoid having the hands free activation keep popping up.
However, even though I made sure to upgrade my firmware in steps I am not sure if i properly have the latest firmware installed correctly. Is there a way to check? I have LTE on 5.0 roms, but cannot get LTE to work on 6.0 roms. Even 3g data toggles on and off on 6.0 roms.
Any help on the LTE and firmware issues would be very much appreciated!
memekmek said:
However, even though I made sure to upgrade my firmware in steps I am not sure if i properly have the latest firmware installed correctly. Is there a way to check? I have LTE on 5.0 roms, but cannot get LTE to work on 6.0 roms. Even 3g data toggles on and off on 6.0 roms.
Click to expand...
Click to collapse
On the bootloader screen, the OS number indicates the firmware version. Alternately, if you do fastboot getvar all, the firmware number is shown as "version-main". So you will want to see 6.20.651.3 there for Marshmallow firmware (6.20.654.3 for HK Edition).
Additionally, if the OS number is red on the bootloader screen, or a 2nd number is shown in parenthesis (usually in red) it means there is an issue with the firmware not properly installed (partially installed).
redpoint73 said:
On the bootloader screen, the OS number indicates the firmware version. Alternately, if you do fastboot getvar all, the firmware number is shown as "version-main". So you will want to see 6.20.651.3 there for Marshmallow firmware (6.20.654.3 for HK Edition).
Additionally, if the OS number is red on the bootloader screen, or a 2nd number is shown in parenthesis (usually in red) it means there is an issue with the firmware not properly installed (partially installed).
Click to expand...
Click to collapse
Then I appear to be stuck as to why data does not work on my 6.0 roms. I am a Sprint user, tested the stock rooted rom from OMJ's thread, tried insert coin rom, viper rom. None of the 6.0 roms have data working properly.
memekmek said:
Then I appear to be stuck as to why data does not work on my 6.0 roms. I am a Sprint user, tested the stock rooted rom from OMJ's thread, tried insert coin rom, viper rom. None of the 6.0 roms have data working properly.
Click to expand...
Click to collapse
Only thing I can think of, is do full RUU (will wipe the phone) instead of just the firmware, and see if that helps.
redpoint73 said:
Only thing I can think of, is do full RUU (will wipe the phone) instead of just the firmware, and see if that helps.
Click to expand...
Click to collapse
Does the bootloader need to be relocked? if not, can i rename the ruu as 0P6BIMG.zip and update through fastbook in the bootloader?
memekmek said:
Does the bootloader need to be relocked? if not, can i rename the ruu as 0P6BIMG.zip and update through fastbook in the bootloader?
Click to expand...
Click to collapse
Since you are s-off, you do not need to relock the bootloader to RUU.
Yes, you can use the SD card method (rename RUU to 0P6BIMG.zip, put on SD card, and reboot into bootloader).
redpoint73 said:
Since you are s-off, you do not need to relock the bootloader to RUU.
Yes, you can use the SD card method (rename RUU to 0P6BIMG.zip, put on SD card, and reboot into bootloader).
Click to expand...
Click to collapse
Welp, did the RUU last night. It changed nothing, and did nothing for me other than making it a pain to reinstall twrp and get my nandroid back up. booo
lte and data is still spotty on 6.0 roms. The only other possible reason i think this could be happening is because i tried to carrier unlock this phone a few months ago, but i downloaded sim card info app, and it all appears to be ok.