Related
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
herzbert said:
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
Click to expand...
Click to collapse
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
el_smurfo said:
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
Click to expand...
Click to collapse
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Checked MD5?
torxx said:
Checked MD5?
Click to expand...
Click to collapse
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Same here... But fine now
herzbert said:
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Click to expand...
Click to collapse
Hey there,
I was having the same problems as you messioned. I flashed the boot.img through fastboot myself and some how it then worked Did not have an problems with flashing the boot.img before. But maybe its worth a try.
Of course you need to use fastboot!!
Did not try yet to flash the RUU. There was an update of CM10 yesterday. The heavy battery drain is gone with this update and there is no urgent need to go back to TrickDroid right now.
herzbert said:
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Click to expand...
Click to collapse
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Sent from my HTC VLE_U using Xparent SkyBlue Tapatalk 2
LikeaG2root said:
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Alright, so, what are these special steps? Can you tell? If its not flashing the within recovery and push the boot.img via fastboot to the phone I would be very interested. My previous HBoot version was 1.13. Flashing ROMs was never a big deal. Also not going to CM9 and back to sense based ROMs.
Click to expand...
Click to collapse
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
HighRoIIer said:
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
Click to expand...
Click to collapse
I did also flash the boot.img via fastboot. Why do you say that anyway? Is there another method to flash a boot.img?
you didn't mention wiping System as part of the full wipe--needs done
Partially solved
rugmankc said:
you didn't mention wiping System as part of the full wipe--needs done
Click to expand...
Click to collapse
Right, I did not mention it because system is wiped by TWRP during flashing the ROM. So there was no need to wipe it seperately. But maybe my mistake was not to wipe data and the new "asec" folder messed things up.
I'll never know because yesterday I did a complete wipe including the SDCard. Afterwards I was able to install TrickDroid flawlessly.
Thank you all for your efforts.
I have h-boot 1.14 withe twrp recovery, I backed up my phone with a previous rom i had and my question is would I have to install the image again after i restore the phone or should the phone restore without any problems.
cal4877 said:
I have h-boot 1.14 withe twrp recovery, I backed up my phone with a previous rom i had and my question is would I have to install the image again after i restore the phone or should the phone restore without any problems.
Click to expand...
Click to collapse
Most of the time yes you will have to install the boot .img manually coming from a different base or Rom... But say if you're on viper and your back up is the same base sense Rom you probably wouldn't have to reflash it... But if coming from cm10 or anything else yes
a box of kittens said:
Most of the time yes you will have to install the boot .img manually coming from a different base or Rom... But say if you're on viper and your back up is the same base sense Rom you probably wouldn't have to reflash it... But if coming from cm10 or anything else yes
Click to expand...
Click to collapse
Awesome thanks man, also im currently running nocturnals dirty rom I believe this is a AOKP rom, now if i want to flash another AOKP or any other CM10 base rom wouldnt the image be the same? or the i have to flash another image of the rom aswell?
cal4877 said:
Awesome thanks man, also im currently running nocturnals dirty rom I believe this is a AOKP rom, now if i want to flash another AOKP or any other CM10 base rom wouldnt the image be the same? or the i have to flash another image of the rom aswell?
Click to expand...
Click to collapse
Be safe and flash it
Is it necessary to reflash rom before restore or can you just fastboot flash boot.IMG and just restore backup?
Sent from my One X using xda premium
I believe you have to flash boot. IMG and than restore according to the comments up there
I just wish we had to option to downgrade the software/hboot without going thru all those steps listed, I remeber i had the htc inspire and you will be able to downgrade hboot by choosing a downgraded version of Ruuu files.
cal4877 said:
I just wish we had to option to downgrade the software/hboot without going thru all those steps listed, I remeber i had the htc inspire and you will be able to downgrade hboot by choosing a downgraded version of Ruuu files.
Click to expand...
Click to collapse
Yeah I loved the inspire that's what got me into android... But I got my phone on hboot 1.09 I've never done the downgrade process but I heard it can be pretty simple
Hey guys, just a quick question, must we always flash the firmware zip file first in bootloader before flashing a custom rom?
I ask this because I had already flashed the latest firmware (3.33.401.6) ages ago, I've been using albinoman887's CM 10.2 rom and Carbon Rom without any problems (well actually, I do have battery issues and 2 small minor issues). But today, I decided to check my firmware version using fastboot command
fastboot getvar version-main
Click to expand...
Click to collapse
and I got something like 1.24.401.1.
Well, that's obviously wrong, so I flashed the firmware again and this time it shows the proper version.
So I was just wondering, does doing a full wipe or flashing a new rom affect the firmware at all? Must we flash it everytime prior to flashing a new rom? I don't understand how my firmware was changed even though all I've been doing is switching between JB custom roms.
chaoscreater said:
Hey guys, just a quick question, must we always flash the firmware zip file first in bootloader before flashing a custom rom?
I ask this because I had already flashed the latest firmware (3.33.401.6) ages ago, I've been using albinoman887's CM 10.2 rom and Carbon Rom without any problems (well actually, I do have battery issues and 2 small minor issues). But today, I decided to check my firmware version using fastboot command and I got something like 1.24.401.1.
Well, that's obviously wrong, so I flashed the firmware again and this time it shows the proper version.
So I was just wondering, does doing a full wipe or flashing a new rom affect the firmware at all? Must we flash it everytime prior to flashing a new rom? I don't understand how my firmware was changed even though all I've been doing is switching between JB custom roms.
Click to expand...
Click to collapse
It happened to me too and I still don't know what caused it to change. Maybe it changed after I performed S-Off or maybe it changed after flashing ViperS 3.1.2.
Edit: It is not causing any problem as your actual firmware is same. You can flash any ICS/JB rom with this firmware. No need to flash firmware before flashing ROM.
Sent from my Sensation
MrJukeHardbane said:
It happened to me too and I still don't know what caused it to change. Maybe it changed after I performed S-Off or maybe it changed after flashing ViperS 3.1.2.
Sent from my Sensation
Click to expand...
Click to collapse
Hmm......ok so now do you flash the firmware every time before you flash a new custom rom then?
For me, the 1st time I flashed the 3.33 firmware was when I've had S-OFF first, then I flashed the firmware and then the custom ROM after, in the proper order.
But I still don't know if I need to flash the firmware everytime or not.
chaoscreater said:
Hmm......ok so now do you flash the firmware every time before you flash a new custom rom then?
For me, the 1st time I flashed the 3.33 firmware was when I've had S-OFF first, then I flashed the firmware and then the custom ROM after, in the proper order.
But I still don't know if I need to flash the firmware everytime or not.
Click to expand...
Click to collapse
No. I never flashed firmware as my firmware is already 3.33 and it just shows 1.24.401. I just flash any ICS/JB Rom and it boots perfectly that means I've latest firmware. There's no need to flash firmware even if it shows 1.24.401
Sent from my Sensation
MrJukeHardbane said:
No. I never flashed firmware as my firmware is already 3.33 and it just shows 1.24.401. I just flash any ICS/JB Rom and it boots perfectly that means I've latest firmware. There's no need to flash firmware even if it shows 1.24.401
Sent from my Sensation
Click to expand...
Click to collapse
Well, I'm the exact same with you, I could still flash JB or ICS custom roms even though mine says 1.24.401.
However, I read somewhere that it's not accurate to check under Settings for the firmware version as it could have been edited in build.prop. The safest way to check is to put your phone in fastboot mode and run the CMD command:
fastboot getvar version-main
Click to expand...
Click to collapse
I read that today and decided to check it again to make sure, and my firmware version comes up as 1.24.401. I then decided to flash the 3.33 firmware again, this time after running the same fastboot command, I get the proper firmware version shown as 3.33.xxx.x (can't remember what it was).
So ya, I think something must have went wrong....
Hi, I'm trying to update my HBoot to 2.13 or 2.15 so I can install the nightly CM11 builds. However, I'm not certain on the steps, so am hoping someone can clear things up for me.
This is the guide I've been looking at:
http://forum.xda-developers.com/showthread.php?t=2501542
At the top he says to find the correct RUU, then links to RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe for HTC Europe.
Am I able to just use that one? My original RUU is RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe, but I can't find a JB version of that.
Looking on http://www.androidruu.com/?developer=Ville, I can't see any RUUs for JB with Radio_0.16.315.
I don't want to download and try and use the wrong thing, so could someone just confirm whether I can/can't use the HTC Europe RUU, and if not, if there's anyway I can update the HBoot to run CM11?
Thank you.
zodac01 said:
Hi, I'm trying to update my HBoot to 2.13 or 2.15 so I can install the nightly CM11 builds. However, I'm not certain on the steps, so am hoping someone can clear things up for me.
This is the guide I've been looking at:
http://forum.xda-developers.com/showthread.php?t=2501542
At the top he says to find the correct RUU, then links to RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe for HTC Europe.
Am I able to just use that one? My original RUU is RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe, but I can't find a JB version of that.
Looking on http://www.androidruu.com/?developer=Ville, I can't see any RUUs for JB with Radio_0.16.315.
I don't want to download and try and use the wrong thing, so could someone just confirm whether I can/can't use the HTC Europe RUU, and if not, if there's anyway I can update the HBoot to run CM11?
Thank you.
Click to expand...
Click to collapse
No! As the OP has said in his thread, you have to use the correct RUU that matches your CID. So yeah you cant use the Europe RUU.
And if your bootloader is still locked and you are S-ON, i suggest you try to find an OTA for JB.
Because THERE IS NO RUU for JB. HTC did not release any RUU for JB as they pretty well understood OTA did serve their purpose.
So if you can confirm your existing HBOOT version here, that would be great to those who can help. Else please provide your CID. (You can use CID getter which is downloadable from PlayStore)
ayyu3m said:
No! As the OP has said in his thread, you have to use the correct RUU that matches your CID. So yeah you cant use the Europe RUU.
And if your bootloader is still locked and you are S-ON, i suggest you try to find an OTA for JB.
Because THERE IS NO RUU for JB. HTC did not release any RUU for JB as they pretty well understood OTA did serve their purpose.
So if you can confirm your existing HBOOT version here, that would be great to those who can help. Else please provide your CID. (You can use CID getter which is downloadable from PlayStore)
Click to expand...
Click to collapse
Ha, a nice strong "no". Thank you for that - good thing I came here to check first then.
Ok, first things first, I've tried updating using the OTA, but it doesn't install. I'm using TWRP v2.6. I could get the error code, but I think I read somewhere that you can't (or shouldn't) install OTA with custom bootloaders? I was hoping to use CM if possible anyway, so hopefully shouldn't have to worry about that (unless that's the way to update the HBoot...)
As for the other info, my HBoot is v1.13 and my CID is O2___01.
807 94346552
Anyone with any information?
zodac01 said:
Anyone with any information?
Click to expand...
Click to collapse
Have you tried to S-OFF your device? If you don't want to do that, why can't you run the O2 RUU then use the system update to get to the higher android version? You have to re-lock the bootloader etc.. as detailed in that guide.
rosswhite said:
Have you tried to S-OFF your device? If you don't want to do that, why can't you run the O2 RUU then use the system update to get to the higher android version? You have to re-lock the bootloader etc.. as detailed in that guide.
Click to expand...
Click to collapse
I tried doing that - I installed the O2 RUU, and then tried to install the update, but it wouldn't work in TWRP. So I locked the bootloader (using fastboot oem lock), but trying to install the update just sends me to the stock HTC bootloader, and doesn't install anything. Is there something else I need to do to install the OTA update?
zodac01 said:
I tried doing that - I installed the O2 RUU, and then tried to install the update, but it wouldn't work in TWRP. So I locked the bootloader (using fastboot oem lock), but trying to install the update just sends me to the stock HTC bootloader, and doesn't install anything. Is there something else I need to do to install the OTA update?
Click to expand...
Click to collapse
The O2 RUU should revert the phone completely to stock and put the stock HTC recovery on the phone so TWRP should not even be installed at this point. Just to trying to understand what you are doing: you install the RUU, once it has booted go to Settings>About>Software Updates>Check Now. It will will find an update then choose to install it. Are you saying from here the phone just reboots to the bootloader and doesn't install the update?
rosswhite said:
The O2 RUU should revert the phone completely to stock and put the stock HTC recovery on the phone so TWRP should not even be installed at this point. Just to trying to understand what you are doing: you install the RUU, once it has booted go to Settings>About>Software Updates>Check Now. It will will find an update then choose to install it. Are you saying from here the phone just reboots to the bootloader and doesn't install the update?
Click to expand...
Click to collapse
That was my mistake - I used the RUU, but then installed TWRP right away, and the updates wouldn't work.
Updated to 4.1.1 on stock - going to see if I can get CM installed now.
zodac01 said:
That was my mistake - I used the RUU, but then installed TWRP right away, and the updates wouldn't work.
Updated to 4.1.1 on stock - going to see if I can get CM installed now.
Click to expand...
Click to collapse
Ok, so I managed to get CM 10.2 installed (the latest stable version). I'm having an issue with v11 though.
I downloaded the most recent nightly build and try to install it (after flashing the boot.img), but get the following message:
Code:
Installing '/sdcard/cm-11-20140315-NIGHTLY-ville.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11 <cut off here>
Error flashing zip '/sdcard/cm-11-20140315-NIGHTLY-vil <cut off here>
Updating partition details...
Unlike the last few times I tried updating, where I got a clear error (like bootloader or hboot errors), the log doesn't seem to specify why the update failed.
zodac01 said:
Ok, so I managed to get CM 10.2 installed (the latest stable version). I'm having an issue with v11 though.
I downloaded the most recent nightly build and try to install it (after flashing the boot.img), but get the following message:
Code:
Installing '/sdcard/cm-11-20140315-NIGHTLY-ville.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11 <cut off here>
Error flashing zip '/sdcard/cm-11-20140315-NIGHTLY-vil <cut off here>
Updating partition details...
Unlike the last few times I tried updating, where I got a clear error (like bootloader or hboot errors), the log doesn't seem to specify why the update failed.
Click to expand...
Click to collapse
It might be the recovery, I think CM11 needs a modified version of TWRP 2.6.3.0, its in the OP of the CM11 thread.
http://forum.xda-developers.com/showpost.php?p=47483838&postcount=1
Edit: You should also be able to use TWRP 2.7.0.0 : http://techerrata.com/browse/twrp2/ville
rosswhite said:
It might be the recovery, I think CM11 needs a modified version of TWRP 2.6.3.0, its in the OP of the CM11 thread.
http://forum.xda-developers.com/showpost.php?p=47483838&postcount=1
Edit: You should also be able to use TWRP 2.7.0.0 : http://techerrata.com/browse/twrp2/ville
Click to expand...
Click to collapse
Dammit, it was actually in the OP. I really should have seen that. Sorry for wasting your time - that was the problem. I've got 4.4.2 running nicely now.
Thank you very much for your time and patience.
zodac01 said:
Dammit, it was actually in the OP. I really should have seen that. Sorry for wasting your time - that was the problem. I've got 4.4.2 running nicely now.
Thank you very much for your time and patience.
Click to expand...
Click to collapse
No problem at all, glad you got it sorted.
Hi,
I'm having a similar problem with flashing CM11 nightlies. This is what I have done:
I have been running MaximusHD for a couple of months. Before that I was running CM11 nightlies just fine.
I used this guide (http://forum.xda-developers.com/showthread.php?t=2322755) to successfully downgrade to hboot 2.15. I then ran MIUI for a few days, which worked fine, but I still wanted the AOSP goodness that you get with a CM-based ROM, so I decided to change to the official CM11 nightlies.
I then tried to flash CM11 (and also PA and Vanir, both based on CM11, plus several other versions of the nightlies, which I found on download.cyanogenmod.com) in TWRP 2.7.0.0. Each time failed with the error: "E:Error executing updater binary in zip 'name-of-zip'".
Then I looked at the CM11 OP on XDA (http://forum.xda-developers.com/showthread.php?t=2528113). I read that you must have one of the two "updated recoveries". While I thought that the zips should flash on TWRP 2.7.0.0, I flashed those recoveries via fastboot also. When flashing the same files as above on the modified TWRP 2.3.3.0, I got exactly the same error as I did with 2.7.0.0. When I tried flashing the ROMs on ClockWorkMod, I got a "Status 7" error.
I googled around a bit and found some (old!) posts on various forums that said that there was a recovery called philz-touch that seemed to be working for some people. I downloaded it, flashed it, and got another "status 7" error when I tried to flash any of the zips.
Then I tried using several versions of TWRP (all the ones here http://techerrata.com/browse/twrp2/ville from 2.3.3.0 to 2.7.0.0 to be precise) and tried flashing each of the zips again. Still no luck.
Other things I have tried:
*I re-ran the steps here (http://forum.xda-developers.com/showthread.php?t=2322755) to ensure that it had definitely worked the first time.
*I tried using the hboot 2.15 and 2.13 (both modded and unmodded) that I found here (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266)
*I tried re-downloading the ROM zips that I had been flashing to make sure that none of them had been corrupted in any way.
*I tried flashing the CM10.2 stable ROM that I found on download.cyanogenmod.com. It flashed no problem and booted fine with no fuss.
I feel like I am the only one on the internet who is having these issues even after changing to the updated recoveries! Please excuse my English, it is not my first language! I would really appreciate some help on this, as I have absolutely no idea what to do.
Thank you very much!
c1aran said:
Hi,
I'm having a similar problem with flashing CM11 nightlies. This is what I have done:
I have been running MaximusHD for a couple of months. Before that I was running CM11 nightlies just fine.
I used this guide (http://forum.xda-developers.com/showthread.php?t=2322755) to successfully downgrade to hboot 2.15. I then ran MIUI for a few days, which worked fine, but I still wanted the AOSP goodness that you get with a CM-based ROM, so I decided to change to the official CM11 nightlies.
I then tried to flash CM11 (and also PA and Vanir, both based on CM11, plus several other versions of the nightlies, which I found on download.cyanogenmod.com) in TWRP 2.7.0.0. Each time failed with the error: "E:Error executing updater binary in zip 'name-of-zip'".
Then I looked at the CM11 OP on XDA (http://forum.xda-developers.com/showthread.php?t=2528113). I read that you must have one of the two "updated recoveries". While I thought that the zips should flash on TWRP 2.7.0.0, I flashed those recoveries via fastboot also. When flashing the same files as above on the modified TWRP 2.3.3.0, I got exactly the same error as I did with 2.7.0.0. When I tried flashing the ROMs on ClockWorkMod, I got a "Status 7" error.
I googled around a bit and found some (old!) posts on various forums that said that there was a recovery called philz-touch that seemed to be working for some people. I downloaded it, flashed it, and got another "status 7" error when I tried to flash any of the zips.
Then I tried using several versions of TWRP (all the ones here http://techerrata.com/browse/twrp2/ville from 2.3.3.0 to 2.7.0.0 to be precise) and tried flashing each of the zips again. Still no luck.
Other things I have tried:
*I re-ran the steps here (http://forum.xda-developers.com/showthread.php?t=2322755) to ensure that it had definitely worked the first time.
*I tried using the hboot 2.15 and 2.13 (both modded and unmodded) that I found here (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266)
*I tried re-downloading the ROM zips that I had been flashing to make sure that none of them had been corrupted in any way.
*I tried flashing the CM10.2 stable ROM that I found on download.cyanogenmod.com. It flashed no problem and booted fine with no fuss.
I feel like I am the only one on the internet who is having these issues even after changing to the updated recoveries! Please excuse my English, it is not my first language! I would really appreciate some help on this, as I have absolutely no idea what to do.
Thank you very much!
Click to expand...
Click to collapse
You just got bad luck and probably missed the right recovery. Starting with 1/05 nightly you need a special recovery due to some CM commits. It is an unofficial 2.7.0.8 and you can find it by looking in CM11 official thread in the last pages. It is posted by intervigil a link to CM wiki from where you can download it. You will need this recovery to flash any CM nightly newer than 1/05 and also for any ROM that's based on CM tree and build lately.
The TWRP 2.7.0.0 was fine as long as you flash an older nightly or a ROM that doesn't have those commits yet.
I'm on the phone right now but I'll try to look for a link and give to you if you don't find it
Edit: Here you go...
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
Sent from nowhere over the air...
Rapier said:
You just got bad luck and probably missed the right recovery. Starting with 1/05 nightly you need a special recovery due to some CM commits. It is an unofficial 2.7.0.8 and you can find it by looking in CM11 official thread in the last pages. It is posted by intervigil a link to CM wiki from where you can download it. You will need this recovery to flash any CM nightly newer than 1/05 and also for any ROM that's based on CM tree and build lately.
The TWRP 2.7.0.0 was fine as long as you flash an older nightly or a ROM that doesn't have those commits yet.
I'm on the phone right now but I'll try to look for a link and give to you if you don't find it
Edit: Here you go...
LINK REMOVED
Sent from nowhere over the air...
Click to expand...
Click to collapse
Hi,
I got a bit frustrated last night and must have missed that information in the CM11 thread. I had a look at that link and it has fixed my issues. Thank you very much!
Hey Guys, cause i can't getting S-Off in case of a Secured STOCK-ROM and secured Kernel i need to change it.
I wanna get now
[NIGHTLIES][4.4.2]CyanogenMod 11.0 for AT&T HTC One Mini - m4 - THE NEW ROM
and
[KERNEL] [CM11] [S2W/DT2W] Sweep2Wake/DoubleTap2Wake Kernel for CM11 - THE NEW KERNEL
after that i think i can get my S-off and finally flashing InsertCoin till cm11 is stable.
First Question:
Is that possible to avoid my problem with S-off cause i am changing Rom and Kernel?
Second Question:
When i switch from cm11 nightlies to Insertcoin will i get any problems cause the kernel is only for CM11?
I flashed insertcoin 2.6 without s off, from cyanogenmod without any problems, just make sure that you use the latest version of twrp. There is also 2.7 but I think you need s off for that, and I heard that there are some problems with flashing that version.
Sent from my HTC One mini using XDA Free mobile app
ziedje said:
I flashed insertcoin 2.6 without s off, from cyanogenmod without any problems, just make sure that you use the latest version of twrp. There is also 2.7 but I think you need s off for that, and I heard that there are some problems with flashing that version.
Sent from my HTC One mini using XDA Free mobile app
Click to expand...
Click to collapse
Well...i flashed todax cm and packman without any problems!
But when i am going to flash insert coin i am not getting any happy end...after reboot i am still on the last rom that flashed? Same things have happened to Stock-Rom and now to Pac-man and CM
I am done with inserctoin ;D
aJay2k1 said:
Well...i flashed todax cm and packman without any problems!
But when i am going to flash insert coin i am not getting any happy end...after reboot i am still on the last rom that flashed? Same things have happened to Stock-Rom and now to Pac-man and CM
I am done with inserctoin ;D
Click to expand...
Click to collapse
just flash the firmware again by miniwhooper and itll fix the problem...
htconemini said:
just flash the firmware again by miniwhooper and itll fix the problem...
Click to expand...
Click to collapse
I had an ordeal getting IC on my mini, the main problem was the TWRP 2.7.1.1 dropped my USB connection which then meant I had no access to Sideload or ADB and couldn't send the zip to my phone.
Pre checks that you will need to make sure you have in place;
HBOOT 2.22 - http://forum.xda-developers.com/showthread.php?t=2759131
CID - 11111111 - http://forum.xda-developers.com/showthread.php?t=2789272
S-OFF (I used Rumrunner) - http://forum.xda-developers.com/showthread.php?t=2789272
TWRP - 2.7.1.1 - This version is a must as it uses the new partition layout
If you wipe everything apart from Data it will remove the existing Rom, then install IC 3.0.3
Once it is installed flash the boot.img that is inside the IC 3.0.3 zip and will stop getting boot loop.
Hope this helps