i need help to install nougat on my htc one a9
-Now i run actually in cyanogenmod 14.1
- when i try to update manually my phone, with 2PQ9IMG_HIA_AER[email protected]61209_60.00_F_release_500842_combined_signed_2.zip
i have an error : could not find meta-inf/com/google/android/update-binary in the zip file
I need help, please
Sorry for my translation thank you
first flash firmware
amirinda said:
first flash firmware
Click to expand...
Click to collapse
ok first a need to flash the firmware
i have a htc one A9 hiaeuhl, with S-ON
can you give me a link to download appriopriate firmware for my phone
thobama said:
ok first a need to flash the firmware
i have a htc one A9 hiaeuhl, with S-ON
can you give me a link to download appriopriate firmware for my phone
Click to expand...
Click to collapse
Try https://www.androidfilehost.com/?fid=745425885120707133
thobama said:
could not find meta-inf/com/google/android/update-binary in the zip file
Click to expand...
Click to collapse
RUU are not flashed using TWRP, flash using fastboot
alray said:
RUU are not flashed using TWRP, flash using fastboot
Click to expand...
Click to collapse
i try this procedure:
- adb reboot bootloader
- in bootloader mode i choose the "download mode"
-adb sideload firmware2.16.401.3.zip
loading: 'firmware2.16.401.3.zip'adb server version (31) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
thobama said:
i try this procedure:
- adb reboot bootloader
- in bootloader mode i choose the "download mode"
-adb sideload firmware2.16.401.3.zip
loading: 'firmware2.16.401.3.zip'adb server version (31) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
Click to expand...
Click to collapse
Flash using fastboot, not twrp neither adb, fastboot.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
or use the sd card method
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
First of all, he should not flash 2.16.401.3.
Didusieq said:
First of all, he should not flash 2.16.401.3.
Click to expand...
Click to collapse
Even if I agree with you, it doesn't really matter if he flash the 2.16 or the 2.17 firmware before flashing the 2.17.401.2 RUU. As long as the HOSD is updated with the new decryption key which is the same in both 2.16 or 2.17 the phone will accept the 2.17.401.2 RUU
But there are two different Firmware files. I would install newer one.
alray said:
Flash using fastboot, not twrp neither adb, fastboot.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
or use the sd card method
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Click to expand...
Click to collapse
when i try : fastboot oem rebootRUU
< waiting for any device >
so i when i used the second method with SD card
7 RU_CID_Fail cid android-info mismatched
Didusieq said:
But there are two different Firmware files. I would install newer one.
Click to expand...
Click to collapse
Yes I agree with that,just saying there will by no difference in the end result since the 2.17 ruu will flash the 2.17 firmware over the 2.16. As long as he update his firmware to 2.xx he will be fine to flash the 2.17 ruu.
---------- Post added at 02:38 AM ---------- Previous post was at 02:38 AM ----------
thobama said:
when i try : fastboot oem rebootRUU
< waiting for any device >
so i when i used the second method with SD card
7 RU_CID_Fail cid android-info mismatched
Click to expand...
Click to collapse
What is your cid?
alray said:
Yes I agree with that,just saying there will by no difference in the end result since the 2.17 ruu will flash the 2.17 firmware over the 2.16. As long as he update his firmware to 2.xx he will be fine to flash the 2.17 ruu.
---------- Post added at 02:38 AM ---------- Previous post was at 02:38 AM ----------
What is your cid?
Click to expand...
Click to collapse
CID htc___247
thobama said:
CID htc___247
Click to expand...
Click to collapse
Can you see "HTC__247" listed under the 2.17.401.2 ruu?
https://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344#post63640734
Have you read the FAQ at post 2 ?
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
This ruu is not compatible with your phone, unless you make it S-OFF and change the CID.
alray said:
Can you see "HTC__247" listed under the 2.17.401.2 ruu?
https://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344#post63640734
Have you read the FAQ at post 2 ?
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
This ruu is not compatible with your phone, unless you make it S-OFF and change the CID.
Click to expand...
Click to collapse
i understand now
can you help me do this? i try sunshine apk but i didnt work
thobama said:
i understand now
can you help me do this? i try sunshine apk but i didnt work
Click to expand...
Click to collapse
Sunshine work best on stock rom. Go back to your stock rom (there is MM ruu for Bouygues in the collection) and try sunshine again. Or even simpler, go back to your stock rom and check if there is an ota update for Nougat.
alray said:
Sunshine work best on stock rom. Go back to your stock rom (there is MM ruu for Bouygues in the collection) and try sunshine again. Or even simpler, go back to your stock rom and check if there is an ota update for Nougat.
Click to expand...
Click to collapse
thanks a lot for your help
amigo instalaste
tengo el modelo htc__322 de claro y me salen los mismos errores
wilson230997 said:
tengo el modelo htc__322 de claro y me salen los mismos errores
Click to expand...
Click to collapse
Please post in English (see forum rules)
I'm not sure what error you are referring to exactly. If you're talking about the error discussed at post #1, it's simple, you can't flash a RUU using a custom recovery, it must be flashed using fastboot (read last page discussion).
If you're referring to the error discussed at post #11, you're trying to flash a RUU version not compatible with your phone. HTC__322 is the A9_UL and will only accept x.xx.600.x ruu version. See the ruu collection threads post #2 for more info.
thobama said:
when i try : fastboot oem rebootRUU
< waiting for any device >
so i when i used the second method with SD card
7 RU_CID_Fail cid android-info mismatched
Click to expand...
Click to collapse
Dude, have you really taken time to fully read the instructions? It is all there, just read it! RTFM!!!
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Related
Hello
I have a problem with installing another rom.
My phone: htc sensations xe
Hboot 1.29
current rom MIUI
if I try to install any frimware it says "parsing...pg58img" and then noting anymore (dont know if thats good or not)
i have 4ext recovery :good:
i do wipe and install a rom p.e. CM9
it always hangs on the bootloop
Pleaassssssss help me :laugh::laugh::laugh::laugh::laugh::crying: :crying: :crying::crying:
gunelturk said:
Hello
I have a problem with installing another rom.
My phone: htc sensations xe
Hboot 1.29
current rom MIUI
if I try to install any frimware it says "parsing...pg58img" and then noting anymore (dont know if thats good or not)
i have 4ext recovery :good:
i do wipe and install a rom p.e. CM9
it always hangs on the bootloop
Pleaassssssss help me :laugh::laugh::laugh::laugh::laugh::crying: :crying: :crying::crying:
Click to expand...
Click to collapse
Okay first off...smaller fonts are your friend.
Second, are you s-on still?
What current firmware version do you have?
Try to enable 4ext Smart Flash.
If it won't work flash latest firmware package and check if you are S-On or S-Off.
ema0185 said:
Try to enable 4ext Smart Flash.
If it won't work flash latest firmware package and check if you are S-On or S-Off.
Click to expand...
Click to collapse
also i have the same problem with hboot 1.180000 UNLOCKED with htcdev and s-on (recovery cwm)..how can i do?please help us!!
:crying:
marchetto said:
also i have the same problem with hboot 1.180000 UNLOCKED with htcdev and s-on (recovery cwm)..how can i do?please help us!!
:crying:
Click to expand...
Click to collapse
You need to upgrade your firmware to 3.32 or the latest 3.33 BUT you first need to S-OFF your phone.
In Sensation Android Development there are guides that will help you doing this.
marchetto said:
also i have the same problem with hboot 1.180000 UNLOCKED with htcdev and s-on (recovery cwm)..how can i do?please help us!!
:crying:
Click to expand...
Click to collapse
you should have used revolutionary.io to S-OFF your device
there wan't no reason to unlock your bootloader with your hboot version
see here http://revolutionary.io/
and after that you have to upgrade your fw version in order to install ics or jb rom
rzr86 said:
you should have used revolutionary.io to S-OFF your device
there wan't no reason to unlock your bootloader with your hboot version
see here http://revolutionary.io/
and after that you have to upgrade your fw version in order to install ics or jb rom
Click to expand...
Click to collapse
thanks..but how can i use revolutionary.io if i'm in bootloop?
---------- Post added at 01:14 PM ---------- Previous post was at 12:53 PM ----------
ema0185 said:
You need to upgrade your firmware to 3.32 or the latest 3.33 BUT you first need to S-OFF your phone.
In Sensation Android Development there are guides that will help you doing this.
Click to expand...
Click to collapse
thanks :fingers-crossed:
but how can i S-OFF my phone? i'm in bootloop..
Reinstall the original RUU
ema0185 said:
Reinstall the original RUU
Click to expand...
Click to collapse
i've tried but i don't know what is mine!!
all of original RUU make me error..
marchetto said:
i've tried but i don't know what is mine!!
all of original RUU make me error..
Click to expand...
Click to collapse
fastboot getvar cid
tell me the output of that command - you need the fastboot files on your computer, then put the phone into bootloader and connect to pc. Open up cmd and cd to where you put the files, eg. "cd C:\fastboot" press enter then run the command
ooooh now i seeit my phone is s-onn ( i thought it was s-off)
i thought it was only possible if i had original RUU
thanks veryy much i will try it now
Jonny said:
fastboot getvar cid
tell me the output of that command - you need the fastboot files on your computer, then put the phone into bootloader and connect to pc. Open up cmd and cd to where you put the files, eg. "cd C:\fastboot" press enter then run the command
Click to expand...
Click to collapse
cid:T-MOB010
thanks a lot for your help..:good:
Hi Guys,
Good day!
Have received a system update notification on my One SV and downloaded the file:
OTA_K2_UL_JB422_SENSE50_MR_hTC_Asia_WWE_3.12.707.2-2.14.707.5_release_3445776pznn0vdk5c0jhzu
However, my phone is rooted, with CWM Recovery v6.0.3.2.
Please help on how will I able to install the update.
Thanks!
My bootloader info:
TAMPERED
UNLOCKED
K2_UL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40a.00.07
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 7 2013, 22:41:40:-1
You must restore your stock recovery. Also the boot.img and system partition (System apps) must be stock and nothing deleted!
old.splatterhand said:
You must restore your stock recovery. Also the boot.img and system partition (System apps) must be stock and nothing deleted!
Click to expand...
Click to collapse
Thanks for the reply!
Can you please teach me how to restore everything?
I have read your guide but I think it will not be applicable(?) in my case since my phone is Asia WWE and there is no available RUU for K2_UL.
Thanks!
I think, the best for you is, read and follow this thread.
@russellvone did a good job in building things for asian phones
old.splatterhand said:
I think, the best for you is, read and follow this thread.
@russellvone did a good job in building things for asian phones
Click to expand...
Click to collapse
Thanks again for the reply.
During downgrade of hboot, I have received the ff. error:
Model ID incorrect! Update Fail!
When I run the command on Terminal Emulator, I got 2 model IDs:
PL8010000, PL8015000
Please help.
Thanks!
The hboot downgrade is only for european phones. There is no RUU for your asia model. You have another radio.img.
old.splatterhand said:
The hboot downgrade is only for european phones. There is no RUU for your asia model. You have another radio.img.
Click to expand...
Click to collapse
That's sad news..
I think the problem is that my hboot cannot be downgraded, since the RUU issue can be solved using @russellvone 's method.
Anyway, thanks a lot!
You can update with a special firmware.zip. You need to backup your radio.img first, and replace it with the one inside the firmware.zip. Then you need to edit the model id in the android-info.txt of firmware.zip.
This must be flashed and then you can restore a european backup/rom.
Maybe @renanski still has his radio.img and can share it with us. He has also asia k2ul.
I've got a copy if needed @old.splatterhand @palamanTM
russellvone said:
I've got a copy if needed @old.splatterhand @palamanTM
Click to expand...
Click to collapse
K2ul Asia radio.img? Share it with us
And also already a firmware.zip for it?
old.splatterhand said:
K2ul Asia radio.img? Share it with us
And also already a firmware.zip for it?
Click to expand...
Click to collapse
uploading now
---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------
K2_UL_Asia_Radio.img_PL80IMG.zip
@old.splatterhand
Thanks, @russellvone for this!
Have replaced the android-info.txt in the original PL80IMG.zip file and tried again to downgrade the hboot.
But I got "CID Incorrect!" error.
after moonshine S-OFF, my phone's info is now:
K2_UL PVT SHIP S-OFF RL
CID-HTC_044
HBOOT-2.00.4444
RADIO-1.15.40a.00.07
OpenDSP-v9.2.0268.1214
eMMC-boot
Thanks again for the assistance!
You need to get Supercid first. Use this fastboot cmd:
fastboot oem writecid 11111111
Click to expand...
Click to collapse
old.splatterhand said:
You need to get Supercid first. Use this fastboot cmd:
Click to expand...
Click to collapse
Thanks! My hboot was successfully downgraded!
But when I run the RUU, I'm getting an "MODEL ID ERROR."
I tried to extract the rom from temp files (as instructed by @russellvone in the other thread) but I am always getting a corrupted zip.
There was another method mentioned in that thread, using an extractor, but unfortunately, I have no linux pc to run the program.
Maybe @wilson3q or any of you guys can share the rom file.
And please enumerate again the correct procedure in flashing, as I was not able to get it clearly on the other thread.
Please help.
Thanks again.
palamanTM said:
Thanks! My hboot was successfully downgraded!
But when I run the RUU, I'm getting an "MODEL ID ERROR."
I tried to extract the rom from temp files (as instructed by @russellvone in the other thread) but I am always getting a corrupted zip.
There was another method mentioned in that thread, using an extractor, but unfortunately, I have no linux pc to run the program.
Maybe @wilson3q or any of you guys can share the rom file.
And please enumerate again the correct procedure in flashing, as I was not able to get it clearly on the other thread.
Please help.
Thanks again.
Click to expand...
Click to collapse
This way is only for a model with existing RUU!
Lets try another way:
Download this firmware.zip: http://d-h.st/69V
Make sure, the android-info.txt is correct for your model id. Replace the radio.img inside, with the one from russel, the rename the firmware.zip to PL80IMG.zip and put it on your sdcard. Boot into bootloader, confirm to flash. After that, install twrp recovery and flash my stock odexed rom.
old.splatterhand said:
This way is only for a model with existing RUU!
Lets try another way:
Download this firmware.zip: http://d-h.st/69V
Make sure, the android-info.txt is correct for your model id. Replace the radio.img inside, with the one from russel, the rename the firmware.zip to PL80IMG.zip and put it on your sdcard. Boot into bootloader, confirm to flash. After that, install twrp recovery and flash my stock odexed rom.
Click to expand...
Click to collapse
I was hoping I can get my phone back to stock to receive the "official" update.
But since there is still no RUU available, I'll go with your stock odexed rom.
Thanks a lot for the assistance, @old.splatterhand and @russellvone! my phone is now 4.2.2!
old.splatterhand said:
This way is only for a model with existing RUU!
Lets try another way:
Download this firmware.zip: http://d-h.st/69V
Make sure, the android-info.txt is correct for your model id. Replace the radio.img inside, with the one from russel, the rename the firmware.zip to PL80IMG.zip and put it on your sdcard. Boot into bootloader, confirm to flash. After that, install twrp recovery and flash my stock odexed rom.
Click to expand...
Click to collapse
What if I flash the firmware.zip inside the OTA file for 4.2.2 and flash your 4.2.2 stock odexed ROM,will it work?
Fysiks said:
What if I flash the firmware.zip inside the OTA file for 4.2.2 and flash your 4.2.2 stock odexed ROM,will it work?
Click to expand...
Click to collapse
Yes, if for your K2 variant.
Sent from my C525c using Tapatalk
Modding.MyMind said:
Yes, if for your K2 variant.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Am I required to flash the boot.img inside the ROM?
Fysiks said:
Am I required to flash the boot.img inside the ROM?
Click to expand...
Click to collapse
If you are S-On, then:
flash Rom via custom recovery after you have conducted a factory reset wipe from within your custom recovery, to include the system partition which can be found in the advance options if using TWRP.
Then, wipe dalvik cache and cache after it finishes
Then, reboot your bootloader, and via fastboot, flash the boot.img which would require you to extract it from the Rom and placing it where your proper adb/fastboot files are on your PC. Use this command:
Code:
fastboot flash boot boot.img
If you are S-Off, then just flash the Rom via custom recovery as explained above. You will not need to flash the boot.img via fastboot. Just wipe dalvik cache and cache after it finishes, and reboot your device.
I'm trying to update a phone I haven't used for a while with a newer ROM, but I'm not able to get in to recovery to do it. It's already rooted with an old ViperOne ROM on and I thought it already had CWM on., but Flashify is telling me it has the stock recovery. I've tried installing CWM and TWRP via Flashify and Fastboot and they've completed without any errors, but I'm never able to get in to it and it boots as normal. I can't even get in to the stock recovery that's supposedly there.
Does anyone have any idea what the problem might be?
Thanks.
Well try this.
Download Rom Manager
It wil flash the CWM by itself and then reboot into the Recovery. Notice what happens.
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
If Helped Click Thanks...
I've tried that too, still just reboots as normal.
Then it might be a Dead Recovery. Well which device are you using. And maybe Flashing your Device back to stock which would flash back the stock recovery.
Hope This Works ..!
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
Tell me wgich device are you using.
HTC One S S4 running Android 4.0.4 ICS
mrkwtrs said:
HTC One S S4 running Android 4.0.4 ICS
Click to expand...
Click to collapse
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all
LS.xD said:
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all
Click to expand...
Click to collapse
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?
mrkwtrs said:
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?
Click to expand...
Click to collapse
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before
LS.xD said:
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before
Click to expand...
Click to collapse
Just seen an O2 UK RUU further down the list so I'll try that.
mrkwtrs said:
Just seen an O2 UK RUU further down the list so I'll try that.
Click to expand...
Click to collapse
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.
LS.xD said:
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.
Click to expand...
Click to collapse
Think I'm all sorted. Thanks for your help! :good:
Today I tried back from CyanogenMod 12 to stock rom in HTC ONE S.
One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101
During this procedure: https://translate.google.pl/translat...OMu&edit-text=
In this 6. point "6. Turn the phone back - no, it's not over yet, but the worst is behind us. We run suitable for our model and already RUU.exe normally carry out the procedure ROM Upgrade Utility - Using the instructions of the installer. ". I used RUU from this link https://drive.google.com/folderview?id=0B1IYElPvrGZrdGR6SXIwYjgxd1U&usp=sharing#list
Installer (RUU) show me error [140]: error bootloader version.
After I close installer phone was reboot and I see only bootloader - On the top I see TAMPERED RELOCKED Security Warning)
I can not run Android now
Could you help me? Please
Update> I unlock it using fastboot flash unlocktoken Unlock_code.bin, but what is next?
noiserobert said:
Today I tried back from CyanogenMod 12 to stock rom in HTC ONE S.
One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101
During this procedure: https://translate.google.pl/translat...OMu&edit-text=
In this 6. point "6. Turn the phone back - no, it's not over yet, but the worst is behind us. We run suitable for our model and already RUU.exe normally carry out the procedure ROM Upgrade Utility - Using the instructions of the installer. ". I used RUU from this link https://drive.google.com/folderview?id=0B1IYElPvrGZrdGR6SXIwYjgxd1U&usp=sharing#list
Installer (RUU) show me error [140]: error bootloader version.
After I close installer phone was reboot and I see only bootloader - On the top I see TAMPERED RELOCKED Security Warning)
I can not run Android now
Could you help me? Please
Update> I unlock it using fastboot flash unlocktoken Unlock_code.bin, but what is next?
Click to expand...
Click to collapse
to use a RUU your bootloader need be relocked
---------- Post added at 06:28 PM ---------- Previous post was at 06:26 PM ----------
You can try rumrunner to S-OFF and after that try with Ruu
JavierG123 said:
You can try rumrunner to S-OFF and after that try with Ruu
Click to expand...
Click to collapse
I tried it but it not work. I think because it work only with stock rom
How back t stock rom with s-on?
noiserobert said:
I tried it but it not work. I think because it work only with stock rom
How back t stock rom with s-on?
Click to expand...
Click to collapse
Flash the proper RUU for your CID, you don't need S-Off for that.
Sent from nowhere over the air...
@thanks Rapier
I describe as I did it in detaliled:
1. Run fastboot oem readcid and fastboot getvar version-main and receive inforamtion Cid T-MOB101 3.16.111.11
2. Downlaod proper (??) RUU RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09es.50.02.07_2_10.09d.50.04L_ver2_release_287723_signed.exe . Is it proper for my device One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101?
3. Run fastboot oem lock
4. Run fastboot erase cache
5. Run RUU (from 1 point)
6. RUU inform me that will be install oddest (something like 2.38.111.xx - I dont remember all number) version then is on my ONE S (3.16.111.11), I accept it
7. RUU reboots my phone, and HTC starts and on blac background was logo htc
8. After few minutes RUU installer show me error [140]: error bootloader version.
9. I accept RUU and it close and my phone reboot to bootloader On the top I see TAMPERED RELOCKED Security Warning)
Where is wrong ?
Plese help me
I resolve it
1. Install a Viper 2.20
2. Use rumrunner.us to set your phone S-OFF
noiserobert said:
I resolve it
1. Install a Viper 2.20
2. Use rumrunner.us to set your phone S-OFF
Click to expand...
Click to collapse
And the RUU works?
I do not RUU because I did S-Off and it was fantastic
I go to Maximums HD (based on stock rom)
noiserobert said:
I do not RUU because I did S-Off and it was fantastic
I go to Maximums HD (based on stock rom)
Click to expand...
Click to collapse
but... for install Maximums HD you don't need S-OFF....
JavierG123 said:
but... for install Maximums HD you don't need S-OFF....
Click to expand...
Click to collapse
Of course you MUST have S-OFF to install Maxiums HD. Please read about it!
noiserobert said:
Of course you MUST have S-OFF to install Maxiums HD. Please read about it!
Click to expand...
Click to collapse
i'm sorry men. my bad
No problem
Only one problem is that not support beatsaudio
noiserobert said:
No problem
Only one problem is that not support beatsaudio
Click to expand...
Click to collapse
in android development or other section like that here in the forum... exist a flasheable zip to get on any device beats audio and other features...
I am wrong, this rom support BA! It is fantastic!
Hi,
I am looking for firmware for A9 EU version 1.56.401.70. I would like to downgrade form Nougat to 6.0.1.
Thanks.
Didusieq said:
Hi,
I am looking for firmware for A9 EU version 1.56.401.70. I would like to downgrade form Nougat to 6.0.1.
Thanks.
Click to expand...
Click to collapse
You can decrypt the 1.56.401.70 RUU to extract the firmware from it
https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928
Yes, I have the output. Folder with files. How to create Firmware then? I am S-on so I need official one.
Didusieq said:
Yes, I have the output. Folder with files. How to create Firmware then? I am S-on do I need official one.
Click to expand...
Click to collapse
I don't think it will work on S-ON since it's now decrypted. Zip all files from the firmware folder together and name the file "firmware.zip". (do not zip the folder, only the content - you don't want the folder in your zip)
Yes, it wont work.
Anyone know how to extract firmware 1.56?
jureca said:
Anyone know how to extract firmware 1.56?
Click to expand...
Click to collapse
Thats exactly what we was talking here, read previous posts (#2 and 4)?
Didusieq said:
Yes, I have the output. Folder with files. How to create Firmware then? I am S-on so I need official one.
Click to expand...
Click to collapse
You can not downgrade firmware from Nougat to Marshmallow if you are S-On.. you need to S-Off to do that..
Even having the signed firmware?
Dr.Anshuman said:
You can not downgrade firmware from Nougat to Marshmallow if you are S-On.. you need to S-Off to do that..
Click to expand...
Click to collapse
Didusieq said:
Even having the signed firmware?
Click to expand...
Click to collapse
That's not 100% true. When S-ON you can't downgrade simply by flashing an older ruu but there is trick to do it. You have to manually change (downgrade) the version-main value in the /misc partition so the older RUU or Firmware can flash (version-main check will pass). All you need is either a rooted rom or at least a custom recovery.
For example, if you have a rooted rom:
Code:
adb shell
su
echo -ne "1.56.401.70\x00\x00" | of=/dev/block/mmcblk0p28 bs=1 seek=2208
exit
exit
Or from twrp terminal simply use
echo -ne "1.56.401.70\x00\x00" | of=/dev/block/mmcblk0p28 bs=1 seek=2208
Click to expand...
Click to collapse
since twrp terminal is already a rooted shell (already at the # prompt)
Then reboot in download mode and see you version main is now 1.56.401.70 instead of 2.16.401.3
Is 2.16.401.3 using the same bootloader version as 1.56.401.70? Is yes i'm really positive that this method should work. On older htc devices (i.e using hboot instead of aboot) this method worked fine only if downgrading to a version-main using the same hboot version. Not sure if the same limitation apply on devices using aboot like the A9 but worth a try. But this method definitively worked for A9 when going from 1.56.something to 1.10.something.
This is well known method, I even made a TWRP aroma tool for that purpose for the One M7:
https://forum.xda-developers.com/showpost.php?p=59436794&postcount=2
Also explained in the A9 ruu thread at post #2 (FAQ #6)
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Well, but I need to be rooted, right?
Didusieq said:
Well, but I need to be rooted, right?
Click to expand...
Click to collapse
It can be done from TWRP recovery even if you're phone is not rooted (so an unlocked BL at least)
Or it can be done from the OS but requires ROOT.
Last time I tried to flash recovery, Ive bricked the phone. :/ Had to reflash RUU.
@Didusieq Btw that will not solve your initial problem. You need a signed firmware.zip (1.56.401.70 or older) to be flashed before the 1.56.401.70 ruu because of the signature change implemented in 2.xx.xxx.x. The only 1.56.401.70 signed firmware.zip I can find is the one from the 1.27.401.5 --> 1.56.401.70 ota update. Firmware.zip from ota update are not including every firmware img (partial firmware update only) and because of that , it's never advised to use these firmware.zip to downgrade since you'll only be downgrading a few firmware img, not all (this could cause incompatibilities and in the worst case, brick your phone ). This is something you could try if you have agree with the risks.
Btw can you confirm your actual bootloader version on 2.16.401.3 ?
---------- Post added at 04:05 PM ---------- Previous post was at 04:05 PM ----------
Didusieq said:
Last time I tried to flash recovery, Ive bricked the phone. :/ Had to reflash RUU.
Click to expand...
Click to collapse
Strange, this should be something relatively easy...
---------- Post added at 04:09 PM ---------- Previous post was at 04:05 PM ----------
Otherwise, Sunshine S-OFF is the fastest and safest way to downgrade. Or you'll have to wait for that 2.17.401.2 ruu Graham Wheeler was talking about on twitter.
Thats why I am thinking if it is worth risking. They should provide with the RUU shortly.BTW. Which one is the BL version? :/
Didusieq said:
Thats why I am thinking if it is worth risking. They should provide with the RUU shortly.BTW. Which one is the BL version? :/
Click to expand...
Click to collapse
version-bootloader from the gatvar or you should be able to get it with "fastboot getvar version-bootloader"
version-bootloader: 1.0.0.0000
Didusieq said:
version-bootloader: 1.0.0.0000
Click to expand...
Click to collapse
so looks like it's the same version of 1.56.401.70 so the version-main downgrade trick should work. Only thing missing is a signed firmware.zip from 1.56.401.70 or older (or the courage to flash the signed firmware.zip from the 1.56.701.70 ota )
I am not so brave. .401. is my region so I should have this one.
Hi, i have "downgrade" with: echo -ne "1.56.401.70\x00" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208 - its fine. I have now in download mode 1.56.401.70, but not me flash Marschmallow RUU (12 RU_ZIP_ERROR). I need firmware 1.56.401.70 - does anyone have? (does not me decrypt from RUU)
THANKS