Develop Bugs

[Q] Getting rid of Vodafone AU ROM to 'stock'?

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

[Q] Help needed: Formerly working Nandorid backups no longer work

[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 ****?

Verizon Unlock/Root Survey

I thought I'd put together a basic survey to possibly help others with their Unlocking/rooting questions.
Please only answer if you have successfully completed the steps and have your bootloader unlocked and phone rooted based on information provided by THIS thread. If you don't currently own a Verizon Retail Note 4, respectfully, PLEASE DO NOT post a reply. Thank you.
If you reply, it is assumed that you have completed the process and have successfully turned your Retail Phone into a Developer Phone. If you are still "tinkering" with your phone after the conversion process, feel free to reply and update your reply as needed, to help others.
Before you began:
Your Android Version?
Your build number?
Did you Odin or Flash to get the above Build Number?
What version of KingRoot did you use to Temp Root your phone?
After Converting to Developer Mode/Rooting (Some questions - If Applicable):
SINCE converting, what Android Version/Build Number have you upgraded from/to? Was the upgrade via OTA or Odin?
What confirmed working root apps are you running (other than Root Checker)?
What have you installed onto your phone that requires an unlocked bootloader that are confirmed to be working?
Has this process changed (made better or worse) how your phone reads extended batteries? State which external batteries you have tested, since the root process was made available this week.

Here's my experience.
STARTED WITH:
Your Android Version? 5.0.1
Your build number? BOG5 Safe Upgrade
DOWNGRADED TO (Because I thought I had to which might've been a mistake)
Your Android Version? 4.4.4
Your build number? ANJ5
Flashed via Odin 3.10.7
Results: After starting the HOWTO Guide on converting from Retail to Developer Mode, I got stuck on THIS step, which gave me an error message
Code:
./samsung_unlock_n4-2
Later, I was told that others had reported issues trying to convert from KK. I then took the Safe Upgrade to BP1. Be sure that you are installing the RETAIL version of the ROM, not the Developer Version. You are not there, yet.
Once you are on BP1, download eMMC Brickbug Check from the Play Store. Verify that your CID begins with 15 followed by a bunch of random numbers. Then, follow the steps on the HOWTO Guide on converting your Retail phone to Developer.
After you do this:
Boot to Download Mode (VOLUME DOWN+HOME+POWER) and flash TWRP 2.8.5 recovery via Odin
If you haven't, already, get your MicroSD card, plug it into your computer and load SuperUser and the kernel (see this reply) onto it. Put it back into your phone
Boot to TWRP recovery (VOLUME UP+HOME+POWER)
Install the two files you just loaded
I this point in time, you SHOULD have BPA, Developer Mode AND root.
With that said........
Your Android Version? 5.0.1
Your build number? BP1
Flashed via Odin 3.10.7
What version of KingRoot did you use to Temp Root your phone? KingRoot 4.8.5
Rather than answer my own questions, I'll just state what so far does work that I've tried:
I've installed CM13 via TWRP. I currently do not have root, but that's about to change.

Before you began:
4.4.4
ANJ5
Don't remember
4.8.5
After rooting:
(If applicable) Have you taken an OTA or Flashed via Odin to a more updated build number? If so, what build number?
Upgrade to 5.0.1 N910VVRU2BOG5_StockRestore.tar.md5 using Odin.
Followed directions to unlock Developer mode.
Flashed N910VVRU2BPA1_StockRestore.tar.md5 to get 5.1.1 through Odin.
Reflashed TWRP and rebooted.
copied MultiSystem-Kernel_LP-5.1.1.zip, BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip, and xposed-v75-sdk21-arm-arter97-snapdragon.zip to phone and flashed them through TWRP. Wiped cache and Davlik cache. Rebooted.
(If applicable) What confirmed working root apps are you running (other than Root Checker)?
Titanium Backup, SD Maid, Xposed Framework, TWRP Manager, Call Recorder, BusyBox Free.
(If applicable) What have you installed onto your phone that requires an unlocked bootloader that are confirmed to be working?
You couldn't install TWRP without an unlocked bootloader, so...
(If applicable) Has this process changed (made better or worse) how your phone reads extended batteries? State which external batteries you have tested, since the root process was made available this week.
Haven't tested yet, but I think the MultiSystem-Kernel_LP-5.1.1.zip and screen auto brightness settings are draining battery less. Too soon to tell.

Issues with HTC 10 from AU / KDDI in Japan

Good morning,
I've recently moved to Japan and purchased an HTC 10 from AU / KDDI. The version information is as follows: CID KDDI_801, MID 2PS670000 / htc_pmeuhljapan. This is my first time dealing with a non-US phone. I've unlocked, s-offed, etc and installed CyanogenMod on my US HTC phones. I've managed to S-OFF / Unlock the AU phone. However, I was unable to root without TWRP or backup the stock recovery. So I flashed TWRP onto it, rooted and that whole deal without issue. I've also backed up my System Image / Boot.
This broke my OTA updates (surprise surprise) but I found an update here: http://forum.xda-developers.com/htc-10/help/htc-10-au-japan-ota-zip-file-t3490829/page2 and attempted to flash. I cannot flash the entire zip file, however, my phone will take the firmware file within. This seems to update the firmware from 1.28 to 1.95. However, this breaks the phone's WiFi (WiFi won't see any networks), but seems to re-install stock recovery.
Still, the OTA updates failed. So I reflashed TWRP recovery and restored my backup. WiFi works just fine again. After I restore the backup it says OS-1.95.970.4 in download mode, however, in the OS itself it shows the old build number 1.28.xxxx. Does anyone have an applicable copy of the stock recovery I can throw on there and attempt to get an OTA update? If not, would international ROM's work with this phone or do I need to find Japan specific? I know they have some of their own bands so I'm not sure of compatibility issues. If you need any additional information please let me know. Sorry if any of the questions / circumstances seem ridiculous, again, I've never had to deal with a non-US phone so there's a bit less information available.

i also use htc 10 of Au japan, can you upload an stock or backup of stock of it. my phone cant boot now

is this phone water proof?

minori_aoi said:
is this phone water proof?
Click to expand...
Click to collapse
No

Hi..which twrp did you flash?

Sir how you unlocked this phone. ?
I dont know i try sunshine and the htcdev there is no way to unlocked bootloader it's furstasing.... :crying:
And another way is buy xtc2clip the price is like so so expensive :crying:

August 2018 - SM-N910V downgrade (6.0.1 to 5.1.1) and root attempt

Hello XDA,
I began following the directions at the following post:
https://forum.xda-developers.com/no...bilized-process-to-unlock-bootloader-t3375527
which seemed have a lot of confirmed successes. I downloaded all the linked files with the exception of Attachment 3779589, which is apparently no longer on the site.
I got stuck at the step when, upon attmepting to root with Kingroot, the app said 'Root strategy unavailable.' I'm guessing the problem is that I'm running 6.0.1, and will need to flash back to 5.1.1. I'm slowly downloading PDA N910VVRU2BPA1/CSC N910VVZW2BPA1 from Sammobile as we speak, but in the meantime, I am wondering about the relevance of this set of instructions from almost two and a half years ago. Should I use newer versions of these tools when and where available, or are the versions specified in doctor-cool's post the ideal/necessary ones for this process? Would a newer version of one or more of those tools simplify or shorten the process in some way? Is there a newer, better set of instructions for rooting the SM-N910V?
Many thanks in advance,
-newmy51

newmy51 said:
Hello XDA,
I began following the directions at the following post:
https://forum.xda-developers.com/no...bilized-process-to-unlock-bootloader-t3375527
which seemed have a lot of confirmed successes. I downloaded all the linked files with the exception of Attachment 3779589, which is apparently no longer on the site.
I got stuck at the step when, upon attmepting to root with Kingroot, the app said 'Root strategy unavailable.' I'm guessing the problem is that I'm running 6.0.1, and will need to flash back to 5.1.1. I'm slowly downloading PDA N910VVRU2BPA1/CSC N910VVZW2BPA1 from Sammobile as we speak, but in the meantime, I am wondering about the relevance of this set of instructions from almost two and a half years ago. Should I use newer versions of these tools when and where available, or are the versions specified in doctor-cool's post the ideal/necessary ones for this process? Would a newer version of one or more of those tools simplify or shorten the process in some way? Is there a newer, better set of instructions for rooting the SM-N910V?
Many thanks in advance,
-newmy51
Click to expand...
Click to collapse
Have you gotten it figured out? Just in case you haven't or if there's anyone else wondering, it's okay to start the unlock process with the step that involves the hybrid firmware. Aside from that the process is still pretty much the same.
Other notes....
When starting Kingroot for the first time it always says Root Strategy Unavailable, just go ahead and press the root button.
If you need to download Samsung firmware use the website updato.com. It is much faster to download from (15-20 min).

the instructions are still the same and relevant.
i managed to downgrade my firmware using Odin to that hacked developer version of 5.11
temp root it twice to unlock the bootloader-absolutely need a sim with working data
install twrp,
install a newer bootloader/modem/system files
its a process but it does work . all i wanted was a stock rooted image with twrp so i can make a backup. my device seems to have a failing emmc chip and would halt the process. also it doesnt turn on unless i put in the freezer. i was able to get everything flashed after after putting it in the freezer for an extra long time. the write fail will happen if the unit heats up. but i think once you get it on there, you might be good

kevintm78 said:
Have you gotten it figured out? Just in case you haven't or if there's anyone else wondering, it's okay to start the unlock process with the step that involves the hybrid firmware. Aside from that the process is still pretty much the same.
Other notes....
When starting Kingroot for the first time it always says Root Strategy Unavailable, just go ahead and press the root button.
If you need to download Samsung firmware use the website updato.com. It is much faster to download from (15-20 min).
Click to expand...
Click to collapse
I gave up when I got a "no OS found" warning from TWRP, and neither could I install the Emotion ROM already on internal storage, nor could I sideload anything even after reinstalling Samsung drivers on my PC. Then bought a pre-rooted Note 4 on FleaBay, which proceeded to go boot loopy after a couple days of normal use. I restored from the one backup on the device, only for the problem to reappear. Seller swears he's sold 400+ units and that it's a super stable rom/build etc. etc. Now I'm using a hand-me-down, beater HTC One Max with a broken camera while I consider my next purchase.