Database Info

[Q] Some Rom and ADB questions

Ive managed to htc-dev bootloader unlock and root but when it comes to install roms I have question
Do have to have a certain firmware to install some roms?
Am on kernel 3.4 and Hboot 2.15 tmob 3.1453117710rd
I flashed viper rom with no hitch but when i tried any other rom I end up freezing at the logo screen for the rom,ie freezes at carbon loading screen for carbon, even after I re flash both the rom and the boot,img for it
I am currently s-on
My second question is there any way to trouble shoot adb? I keep trying to push files via adb and keep getting adb cannot find such file or directory, I installed ADB according to this http://forum.xda-developers.com/showthread.php?t=879701
I run the cmd prompt from desktop and commands like adb-reboot work fine
But when i attempt to push i get the cant find file error

what recovery are you using? what version of twrp?
twrp 2.3.3
http://techerrata.com/file/twrp2/ville/openrecovery-twrp-2.3.3.0-ville.img

recovery is twrp 2.1.6
Should I update to the new recovery?

foodiegamer said:
recovery is twrp 2.1.6
Should I update to the new recovery?
Click to expand...
Click to collapse
yes, people have a lot of luck with this version of TWRP

Yea flashing to newest trwp did it for me

Rooting and s-off for vzw m8 on Lollipop

Hey all,
After some browsing on here recently, it looks like a somewhat experimental exploit has been found to gain temporary root access long enough for Sunshine to do its thing. I am planning to use the "Kingroot" method to root and permanently s-off my HTC M8.
It has been some time since I seriously rooted any android phone so I wanted to compile a checklist of the steps I will need to take to fully downgrade my operating system from Lollipop back to Kit Kat once all is said and done. My questions are as follows:
-is it necessary to flash a stock 4.x.x sense rom before flashing a custom 4.x.x build?
- from a stability/performance standpoint what sense kit Kat rom do you find to be the best? I prefer sense for the great widgets and features it provides.
- is flashing a kernel necessary for going from 5.x.x to 4.x.x? I recall doing this to my OG droid several times.
- will flashing new radios be necessary or are the still included in rom builds?
- Is twrp the preferred recovery for the m8 or do alternatives exist which you'd recommend?
Please let me know of any other important steps I will need to take before attempting the downgrade. Thanks in advance.

x25064 said:
Hey all,
After some browsing on here recently, it looks like a somewhat experimental exploit has been found to gain temporary root access long enough for Sunshine to do its thing. I am planning to use the "Kingroot" method to root and permanently s-off my HTC M8.
It has been some time since I seriously rooted any android phone so I wanted to compile a checklist of the steps I will need to take to fully downgrade my operating system from Lollipop back to Kit Kat once all is said and done. My questions are as follows:
-is it necessary to flash a stock 4.x.x sense rom before flashing a custom 4.x.x build?
- from a stability/performance standpoint what sense kit Kat rom do you find to be the best? I prefer sense for the great widgets and features it provides.
- is flashing a kernel necessary for going from 5.x.x to 4.x.x? I recall doing this to my OG droid several times.
- will flashing new radios be necessary or are the still included in rom builds?
- Is twrp the preferred recovery for the m8 or do alternatives exist which you'd recommend?
Please let me know of any other important steps I will need to take before attempting the downgrade. Thanks in advance.
Click to expand...
Click to collapse
Once s-off if you want stock experience, I would flash kk ruu

This should be in Q&A, not development. Maybe @moderator an move it?
x25064 said:
Hey all,
After some browsing on here recently, it looks like a somewhat experimental exploit has been found to gain temporary root access long enough for Sunshine to do its thing. I am planning to use the "Kingroot" method to root and permanently s-off my HTC M8.
It has been some time since I seriously rooted any android phone so I wanted to compile a checklist of the steps I will need to take to fully downgrade my operating system from Lollipop back to Kit Kat once all is said and done. My questions are as follows:
-is it necessary to flash a stock 4.x.x sense rom before flashing a custom 4.x.x build?
Click to expand...
Click to collapse
You mean after being s-off? No
- from a stability/performance standpoint what sense kit Kat rom do you find to be the best? I prefer sense for the great widgets and features it provides.
Click to expand...
Click to collapse
Totally personal preference. I like CleanROM
- is flashing a kernel necessary for going from 5.x.x to 4.x.x? I recall doing this to my OG droid several times.
Click to expand...
Click to collapse
The kernel is part of the rom you flash. You can flash a different kernel after installing a rom. Just gotta make sure it's compatible with the rom
- will flashing new radios be necessary or are the still included in rom builds?
Click to expand...
Click to collapse
On HTC devices you have to distinguish between firmware and rom. The firmware is radios, hboot and such. The rom is seperate. In general you have to have 4.4 firmware to run a KK rom and 5.x firmware to run a LP rom. Although I know of people who flashed the 5.0.1 firmware and then went back to CleanROM 3.x (which is KK) without a problem. YMMV
Is twrp the preferred recovery for the m8 or do alternatives exist which you'd recommend?
Click to expand...
Click to collapse
Everybody seems to be running TWRP
Please let me know of any other important steps I will need to take before attempting the downgrade. Thanks in advance.
Click to expand...
Click to collapse
You cannot downgrade to KK unless you are s-off. Once you are s-off, flash the firmware for the rom you want to run, then flash the rom

Thanks for the info, that is exactly what I need. I finally have some time today to give this a shot so I will report my results.

Looks like I am already running into issues with Kingroot not opening on my phone. It will install, then once selected from my app drawer it just flashes the screen with no result.

I got another version from a download list on XDA heres the progress so far:
- kingroot gains root after 2-3 tries, no big deal
- sunshine installed and given su permission
- sunshine verifies, I pay them, final tests are run and it reboots
- phone fully rebooted, sunshine asks to continue
- I hit home and minimized Sunshine, went back to kingroot, installed - reboot - Sunshine pops up, minimize, kingroot - repeat until root is successful
- maximize Sunshine from apps tray, continue - s-off successfully
- rebooted the phone into the boot menu and verified that the bootloader is unlocked and s-off has been successfully achieved
I do also concur with other postings that the modified flag has been placed when I enter the boot menu.

Also just to clarify - I CAN download RUU 4.4.3, place it on my root SD directory (FAT32), and go into hboot mode and flash accordingly? This won't brick my phone going from 5.0.1 to 4.4.3 as long as the phone is s-off unlocked?

Ok.. I flashed 4.4.3 which worked.. then went into the play store to grab TWRP - tried to install the recovery and it said something went wrong. I chose to reboot the phone into recovery to check if one was already installed (I thought RUU was bone stock..) and now I can't get kitkat to boot up.. it just goes to TWRP or gives me the red exclamation point....... not sure what to do here but I don't think adb will work since it requires drivers I can't install without the phone being fully booted up..
EDIT: Since I still had a recovery and an SD card with the 4.4.3 RUU on it, I just wiped the system and booted up into the hboot to reinstall the RUU again. Phew..
Now I'm just confused as to why TWRP did that to my phone in the first place? I don't want to install it again now because that was such a pain, but I want to get a rom loaded..

TWRP Manager sucks. The partition layout is slightly different between KK and LP and probably TWRP Manager flashed the recovery to the system partition. That's why it booted straight to recovery.
Use fastboot to flash TWRP.

Thanks man, that makes sense. I'll give it a shot tomorrow!

I was able to RUU TWRP no problem with a RUU zip I found on here. Worked like a charm.
I have to say I didn't realize how bad the official lollipop OTA is compared to running a 4.4.3 version of viperrom. It's like night and day and my battery life is excellent now. So glad the kingroot exploit worked!

x25064 said:
I was able to RUU TWRP no problem with a RUU zip I found on here. Worked like a charm.
I have to say I didn't realize how bad the official lollipop OTA is compared to running a 4.4.3 version of viperrom. It's like night and day and my battery life is excellent now. So glad the kingroot exploit worked!
Click to expand...
Click to collapse
Thanks for this whole thread! Your detailed process has given me the confidence to finally do this on mine, can't wait to be back to KK and have a working device again!

Cyanogenmod update fails with error 7

Hello everybody, I hope to find help here.
My phone is the HTC One A9, Europe Version ("hiaeuhl"). Recovery is TWRP 3.0.2-0.
The background story is that I already managed to install Cyanogenmod after downgrading the original ROM to Version 1.10 and unlocked the bootloader with the HTC Unlock tool. I also managed to decrypt the device.
I'd like to update my system regularly, but unfortunately the last running version is the cm-13.0-20160904-NIGHTLY-hiaeuhl.zip from September 4th.
If I try to install the latest versions of Cyanogenmod (for example from September 9th) I always get the error
hiae.veryfy.trustzone() failed to read current TZ version: -2
Updater process ended with ERROR 7
I already tried to remove the lines that check this in the file updater_script inside the ROM's zip, then I could install the update, but afterwards I was stuck in a boot loop.
The error has nothing to do with the encryption, it apears with and without device encryption, and it has nothing to do which system (original or custom) is installed before flashing. It is also indifferent if I try the update via the system's update function or directly in TWRP. It's the fact that the Cyanogenmod version from September 4th is the last working for me. I definetly chose the right one for hiaeuhl, but it seems the developers have added a feature that makey my device incompatible to this ROM.
If there is anything I can do to update my system again, please let me know.

Have the same issue.
We need to update it, but I don't know how
jira.cyanogenmod.org/browse/NIGHTLIES-3351

Here is how I could solve the issue:
- flashing the latest stock firmware (and let it possibly completely update)
- install TWRP via fastboot
- from TWRP a factory reset
- install new version of the Cyanogenmod from TWRP
It worked for me, now I can use my beloved custom Rom

The Same Problem
I have exactly the same Problem, last working CM-Update was the 3rd September

Did you try my solution? With the older CM Rom versions for the HTC A9 you had to downgrade the stock rom, otherwise the CM wouldn't have started after the installation. Now it seems that the stock rom has to be the latest one (for me the 1.56) that you are able to flash the latest CM versions.

I do not have the latest stock Rom, my os is 1.27.161.6, seems actually cm needs 1.57, i am unlocked and s-off

You should probably find the right version for your phone here:
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
You should take the one with the right cid for your phone (which you can find with "fastboot getvar all" in the fastboot mode)

Thanks, i will try it and report

The last build i found for my version is 1.27. this is what i have

Hmmm... then I guess you have to wait until the new version appears in the forum. Seems that you have a device with vodafone branding. Since you already set S-off you also have the possibility to change your cid to one of the existing newer firmwares.

Is there a solution without going back to stock?

I'm not an expert, but I don't think so. It seems that the version number of the stock rom is stored somewhere even after changing the system to Cyanogenmod, and this version has to be the latest one. So unfortunately, as far as I know, you'll have to do the flashing procedure again...

thanks Silberhase, now i am on CM 13 again. Thats what i did: wrote Supdercid, searched a ruu-version for my build, found a 1.56.401.70 version, flashed this, then flashed twrp 3.0.2.0 again, factory reset - without factory reset i was not able to install cm, format data, recovery, latest cm update, flash gapps, restore my other data with titanium, done....

I'm glad to hear it worked for you!

Yes, but next Problem or better i actually do not know what problems will raise. After updating today successfully to last cm build phone is encrypted... TWRP requires password for decryption. Problem all over forums. Today i habe no fun to Format data again and restore all.

That's also what I experienced. Other users reported that the current TWRP version 3.0.2.0 can't handle the encryption of the HTC One A9. And every update will encrypt the device again. As a workaround you can do this:
- copy the downloaded update from /sdcard/cmupdater to the external memory card
- boot to the recovery (when asked for password push the cancel button) and install both the update and the gapps again (without wiping anything) from the memory card.

Its a pity, all worked perfectly. Installed last cm.. Which encrypted phone. Restored my backup. All Working. Updated apps, want backup again.... .... Error opening /system/addon.d (not a directory)..error in generating tarlist......Create tarfork()
Process Ended with error 255

I'm trying to help as much as I can even though I have no experience with all this. I never did a backup
Maybe you find the answer here:
http://forum.xda-developers.com/nexus-6/help/e-createtarfork-process-error255-t3302462
Maybe it helps to mount "system" in TWRP and then delete /system/addon.d. But it seems that this step has to be repeated before every backup.

Any news to this theme? Is Twrp able to handle A9 again in new Version?

The recent version 3.0.2.0 of TWRP is available for the A9 but can't handle it's encryption. It works anyway if you are willing to use some workarounds.

M8 Stuck in initial boot after loading boot.img

Hi,
I've unlocked and s-off'ed my m8 4.4.3 in an attempt to load a custom android 7.1.1 rom (resurrection remix to be exact). I go through all the steps laid out in wccftech.com's tutorial and when I initially install the flash boot of the extracted image (in the same folder as my sdk platform tools) and then reboot, it always gets stuck. I've tried rebooting manually after and then loading into hboot to continue with installing the .zip file in recovery, but it always fails and I think this is the cause. Is there some sort of workaround for this? It's done this on both resurrection and crDroid. I am at a loss.

Half Kitsune said:
Hi,
I've unlocked and s-off'ed my m8 4.4.3 in an attempt to load a custom android 7.1.1 rom (resurrection remix to be exact). I go through all the steps laid out in wccftech.com's tutorial and when I initially install the flash boot of the extracted image (in the same folder as my sdk platform tools) and then reboot, it always gets stuck. I've tried rebooting manually after and then loading into hboot to continue with installing the .zip file in recovery, but it always fails and I think this is the cause. Is there some sort of workaround for this? It's done this on both resurrection and crDroid. I am at a loss.
Click to expand...
Click to collapse
Do you have the latest version of twrp installed?

custom roms keep puttimg me back into fastboot

So long time android user. I have the tmo variant of the Oneplus7 pro with unlocked bootloader via exploit found. Have twrp installed amd stock rom rooted with magisk. I tried installing the Havoc and the Aosip rom followed directions step by step. Havoc booted to the first gteen splash screen then reboots to fastboot. Aosip gets to the settimg up wifi then reboots to fastboot. I made a backup of the stock rom before installing anything and im able to restore it with twrp and root. I looked in the threads but didn't find anything unless i missed it. Also been sitting on telegram waiting on someone to shed some light.

fordstang99 said:
So long time android user. I have the tmo variant of the Oneplus7 pro with unlocked bootloader via exploit found. Have twrp installed amd stock rom rooted with magisk. I tried installing the Havoc and the Aosip rom followed directions step by step. Havoc booted to the first gteen splash screen then reboots to fastboot. Aosip gets to the settimg up wifi then reboots to fastboot. I made a backup of the stock rom before installing anything and im able to restore it with twrp and root. I looked in the threads but didn't find anything unless i missed it. Also been sitting on telegram waiting on someone to shed some light.
Click to expand...
Click to collapse
Trying the canary build

It worked with canary 19.4
Mods please delete if need be