i cant install rom InsertCoin for htc one mini - HTC One Mini

hi brothers
please help me i cant install rom InsertCoin for htc one mini
and All that you have installed the system InsertCoin I find Unchangeable and remains on the old operating system cyanogen mod
And you install more than Recovery on two twarp ,, cmw same problem and nothing has changed
Anyone who has experience please help me...... :crying:

ico5555 said:
hi brothers
please help me i cant install rom InsertCoin for htc one mini
and All that you have installed the system InsertCoin I find Unchangeable and remains on the old operating system cyanogen mod
And you install more than Recovery on two twarp ,, cmw same problem and nothing has changed
Anyone who has experience please help me...... :crying:
Click to expand...
Click to collapse
Assuming that you have:
- Unlocked bootloader from HTCdev.com
- Flashed custom recovery, I prefer TWRP 2.7.1.1
- Flashed AT&T firmware ( HBOOT 2.22, Newest Radio, etc )
- SuperCID
- S-OFF
You should just copy the InsertCoin ROM image file to your SDcard ( preferably in the root folder ) [ /sdcard/ ], boot into Recovery Mode, within TWRP go to Wipe -> Advanced Wipe, select "System, Data, Dalvik Cache, Cache" press wipe.
Then go to "Install" select the InsertCoin ROM file and start the install.

Related

[Q] Switch from 4EXT to CWM ? / Flashing boot.img ? (CM10-alpha)

Hi XDA
My device before the procedure : HTC Desire S, unbranded, Bootloader locked,
HBoot 2.00.0002, S-ON, ICS stock rom via HTC RUU tool
I unlocked the bootloader via htcdev.com.
After hours of reading and testing "everything" I found here on xda (great stuff!!),
I finally managed to have a running CM10-alpha.
(http://forum.xda-developers.com/showthread.php?t=1776256 / Version 2012-09-17)
As I am new to this flashing stuff, I first tried to follow the flashing guide
on the CM-website. Was not workable because "Revolutionary" can not be used on hboot 2...
So I continued with flashing CWM-recovery and after a wipe (factory/reset/cache/dalvik),
I flashed CM10.zip and gapps.zip.
It went through without any errors, unfortunately, the device did not boot afterwards.
I found this guide :
http://forum.xda-developers.com/showthread.php?t=1525100 (CustomROM with 4EXT-recovery)
It indicates flashing "boot.img" (from the CM10 zip-file) as a last step.
Probably the most important step for this HTC device ?!
The Desire S booted CM10 without any further problems and is running since.
(I did not flash GApps.zip, just downloaded Maps and Youtube.)
I have 3 questions :
1. Is it possible to update to a newer version of 4EXT-recovery without losing
the CM10-installation ?
(e.g. 4EXT-Touch : http://forum.xda-developers.com/showthread.php?t=1377745)
2. Is it possible to switch from 4EXT to CWM-recovery without losing
the CM10-installation ? I would like to have CWM because I could then use the ROMManager App.
(e.g. http://forum.xda-developers.com/showthread.php?t=1484753)
3. If I would stick with the current 4EXT-recovery,
do I always have to flash "boot.img" as the last step before booting up the device ?
(e.g. after the next CM10-alpha release)
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Thanks so much !
CM10 is great, so much faster than HTC-stock rom ICS (with Sense 3.6) !!
CU
1) yes
2)yep
3)si
Edit: you only have to flash the boot.img when the kernel changes from cm10 to fallout yes.
Updating cm10 no, if the dev didn't change the kernel.
After a full wipe (in 4ext format everything exept SD-card) you also have to use fastboot. Because that wipes the boot.img
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
FrolicFrog said:
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Changing recovery will not touch anything else on your device. But there were some issues reported with CWM on some ROMs.
I think one of them is a lack of /system/lib partition support, which is important if you go from a ROM that has such to a ROM without one (it will end with two conflicting /system/lib directories and the device will not boot.
Also I am not sure that CWM wipes the .android-secure directory on the SDcard which can cause issues if going from AOSP to Sense ROM
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
pughie said:
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
Click to expand...
Click to collapse
I have used it about an year ago so it is definitely improved. But there was an user with Bluetooth issues after flashing my kernel and changing the recovery solved it. Also 4EXT has a lot of minor but very useful settings over CWM. Anyway the OP can try both and stick with the one he likes more
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Sent from my HTC Desire S
amidabuddha said:
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Click to expand...
Click to collapse
Ah, will check on this one. Thanks !
FrolicFrog said:
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Bug in CM10 Alpha by nk11
Hello XDA,
Sorry if this question is in the wrong thread.
It is regarding the cm10 alpha port by nk111.
I got it working, save one major bug, the speaker does not produce any sound output whatsoever:
This applies to ringtones, alarm tones and music.
The sound is perfectly audible through a pair of earphones.
I followed the steps in the official thread to delete the file /system/lib/hw/audio_policy.msm7x30.so and reboot
but this only aggravates the issue by disabling all audio outputs!!!
I am running clockwork mod v5 with HTC bootlocker unlocked, S-ON.
Any help would be greatly appreciated.
c.m.b said:
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Click to expand...
Click to collapse
I saw the screenshot of kernel version 3, too. And was quite excited
Thanks for the hint with wiping only cache&dalvik.

[Q] HTC ONE S (Stuck a white screen ) HTC logo

Hello Friend,
well i was trying to upgrade my HTC ONE S to Different Rom, i install TWRP there was option to wipe data , without reading the full instruction i wipe each and everything without taking backup, now i am unable to install any Rom Version , i tried so many thing but failed
i used One_S_All-In-One_Kit_v4
1)i tried flash with one s Zip
2)Flash Kernel
3)Flash Factory RUU Zip
everything failed
TWRP show no OS installed .....
i also attached the getvar report to let you know about HTC ONE S
i will be very thank full to you if you help me regarding this matter

[Q] How to root HTC one mini (At&T)?

Can someone help me root my HTC one mini at&t version, it's up to date on the latest firmwire 4.4.2. I tried rooting it before using this tutorial right here htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux
Got as far as installing custom recovery but when I install SuperUser it shuts off constantly, so I had to revert it back. The bootloader shows Unlocked "tampered" and S-On. So could anyone help? I'm using cricket on this phone and hoping to root it so I can switch roms (thinking that'll solve the MMS problem)
AzrielAx said:
Can someone help me root my HTC one mini at&t version, it's up to date on the latest firmwire 4.4.2. I tried rooting it before using this tutorial right here htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux
Got as far as installing custom recovery but when I install SuperUser it shuts off constantly, so I had to revert it back. The bootloader shows Unlocked "tampered" and S-On. So could anyone help? I'm using cricket on this phone and hoping to root it so I can switch roms (thinking that'll solve the MMS problem)
Click to expand...
Click to collapse
You don't need to root it to install a custom ROM. YOU only need to unlock it (through HTC Dev) and install a custom recovery (TWRP). If you reboot to bootloader and post the hboot version you're on, I can point you to the correct files.
jollywhitefoot said:
You don't need to root it to install a custom ROM. YOU only need to unlock it (through HTC Dev) and install a custom recovery (TWRP). If you reboot to bootloader and post the hboot version you're on, I can point you to the correct files.
Click to expand...
Click to collapse
M4_UL PVT Ship S-ON RL
The Hboot version is 2.22.0000
Shows Tampered in black and unlocked in pink
I have team win recovery Project v2.7.1.1 installed just when I tried installing SuperUser on it it kept turning off so I had to restore it from a backup before I installed Superuser
AzrielAx said:
M4_UL PVT Ship S-ON RL
The Hboot version is 2.22.0000
Shows Tampered in black and unlocked in pink
I have team win recovery Project v2.7.1.1 installed just when I tried installing SuperUser on it it kept turning off so I had to restore it from a backup before I installed Superuser
Click to expand...
Click to collapse
So do you want to root your existing ROM or flash a custom one? Most custom ROM's come rooted already.
The best custom sense ROM is Insert Coin. (IMO) You can download it from the Android Development section.
Before you flash:
1) Download Insert Coin rom and copy it to your device
2) Make a backup in twrp and test it (it sounds like you already have a good backup)
3) copy the backup folder to your computer just in case you wipe out your SDCard...in fact, I'd backup everything you don't want to lose, including the backup. Nothing you do should wipe your sdcard, but better safe than sorry.
To flash:
1) Boot to recovery (TWRP)
2) Go to Wipe
3) Go to Advanced Wipe
4) Wipe the following: Davlik Cache, System, Cache & Data (DO NOT WIPE INTERNAL STORAGE-this is your sdcard)
5) Back out the the TWRP homescreen
6) Go to Install
7) Find the Insert Coin rom, select it, and swipe to start the install
8) Follow the onscreen menus for install options (since you already wiped everything, you can select the option to NOT wipe prior to install)
Notes on Insert Coin - if you use handsfree bluetooth calling, you need to download one of the 4.4.2 versions of the ROM (3.0.7 or 3.0.8). I usually use 3.0.7, personally. 3.0.8 had some issues with paid apps not installing properly and 3.0.7 is pretty much bugfree imo. If handsfree bluetooth isn't important, then the latest 4.x.x version will be fine.
I hope this helps you.
jollywhitefoot said:
So do you want to root your existing ROM or flash a custom one? Most custom ROM's come rooted already.
The best custom sense ROM is Insert Coin. (IMO) You can download it from the Android Development section.
Before you flash:
1) Download Insert Coin rom and copy it to your device
2) Make a backup in twrp and test it (it sounds like you already have a good backup)
3) copy the backup folder to your computer just in case you wipe out your SDCard...in fact, I'd backup everything you don't want to lose, including the backup. Nothing you do should wipe your sdcard, but better safe than sorry.
To flash:
1) Boot to recovery (TWRP)
2) Go to Wipe
3) Go to Advanced Wipe
4) Wipe the following: Davlik Cache, System, Cache & Data (DO NOT WIPE INTERNAL STORAGE-this is your sdcard)
5) Back out the the TWRP homescreen
6) Go to Install
7) Find the Insert Coin rom, select it, and swipe to start the install
8) Follow the onscreen menus for install options (since you already wiped everything, you can select the option to NOT wipe prior to install)
Notes on Insert Coin - if you use handsfree bluetooth calling, you need to download one of the 4.4.2 versions of the ROM (3.0.7 or 3.0.8). I usually use 3.0.7, personally. 3.0.8 had some issues with paid apps not installing properly and 3.0.7 is pretty much bugfree imo. If handsfree bluetooth isn't important, then the latest 4.x.x version will be fine.
I hope this helps you.
Click to expand...
Click to collapse
'
It did I successfully installed a custom rom on it thank you!

[Q] HTC pico stuck on htc screen..help needed

Today i updated my recovery from twrp 2.6.3 to twrp 2.8 in order to install cm12 RC4..Rom failed to install so i tried to restore the backup i made..it failed too recover as well..i decided to freshly install cm10.2 as i was using it before all this.after all the wiping .the rom installed without any problem but when i rebooted the phone to system its stuck on htc screen..i have tried installing other roms include stock rom but similar result upon booting..RUU is not available for my radio 1.12.82.08...i dont know what to do now please help asap as i dont have any other cellphone
pico_lover said:
Today i updated my recovery from twrp 2.6.3 to twrp 2.8 in order to install cm12 RC4..Rom failed to install so i tried to restore the backup i made..it failed too recover as well..i decided to freshly install cm10.2 as i was using it before all this.after all the wiping .the rom installed without any problem but when i rebooted the phone to system its stuck on htc screen..i have tried installing other roms include stock rom but similar result upon booting..RUU is not available for my radio 1.12.82.08...i dont know what to do now please help asap as i dont have any other cellphone
Click to expand...
Click to collapse
Please change the recovery to flash other roms, the recovery provided in cm12 OP cannot flash other roms... In order to flash other rom please flash other recovery...
pico_lover said:
Today i updated my recovery from twrp 2.6.3 to twrp 2.8 in order to install cm12 RC4..Rom failed to install so i tried to restore the backup i made..it failed too recover as well..i decided to freshly install cm10.2 as i was using it before all this.after all the wiping .the rom installed without any problem but when i rebooted the phone to system its stuck on htc screen..i have tried installing other roms include stock rom but similar result upon booting..RUU is not available for my radio 1.12.82.08...i dont know what to do now please help asap as i dont have any other cellphone
Click to expand...
Click to collapse
use TWRP 2.7.0.0 FOR cm10.2(i'm using it).for CM11 RC3 and CM11RC4 use modified recovery given in respective post.
don't restore backup of one recovery with other
flash superwipe before flashing any ROM.
http://forum.xda-developers.com/showpost.php?p=48859393&postcount=5

[Q] [HELP] Stuck at HTC Logo and Recovery

So, I haven't been using my pico recently..used it about 6 months ago and it has been unused ever since..
Today, I finally picked it up and tried to install MIUI V4. I updated TWRP to 2.7 and it was updated.. Deleted the previous rom and installed the MIUI zip.. When I restarted even the MIUI bootanimation did not show up, only the HTC Logo showed up, and the phone rebooted into recovery. .
So, is it bricked ? I tried installing CM9 but same problem..Any help will be appreciated
TAOprajjwal said:
So, I haven't been using my pico recently..used it about 6 months ago and it has been unused ever since..
Today, I finally picked it up and tried to install MIUI V4. I updated TWRP to 2.7 and it was updated.. Deleted the previous rom and installed the MIUI zip.. When I restarted even the MIUI bootanimation did not show up, only the HTC Logo showed up, and the phone rebooted into recovery. .
So, is it bricked ? I tried installing CM9 but same problem..Any help will be appreciated
Click to expand...
Click to collapse
did you 'Make a clean install' , when you flash different rom you have to Clean old one
In TWRP 2.7
Go to WIPE > Advanced Wipe > select :dalvik, cache , data ,system > swipe to clean >>>Than flash ur rom bro
XenoMorphv2 said:
did you 'Make a clean install' , when you flash different rom you have to Clean old one
In TWRP 2.7
Go to WIPE > Advanced Wipe > select :dalvik, cache , data ,system > swipe to clean >>>Than flash ur rom bro
Click to expand...
Click to collapse
Yup wiped everything including system and sd-ext partiton
TAOprajjwal said:
Yup wiped everything including system and sd-ext partiton
Click to expand...
Click to collapse
i dont know bro maybe you need to change recovery ? also can try nand recoveryies... again i dont know much but you can try to 'fastboot flash boot boot.img' method...
our forum slowly dies
TAOprajjwal said:
So, I haven't been using my pico recently..used it about 6 months ago and it has been unused ever since..
Today, I finally picked it up and tried to install MIUI V4. I updated TWRP to 2.7 and it was updated.. Deleted the previous rom and installed the MIUI zip.. When I restarted even the MIUI bootanimation did not show up, only the HTC Logo showed up, and the phone rebooted into recovery. .
So, is it bricked ? I tried installing CM9 but same problem..Any help will be appreciated
Click to expand...
Click to collapse
i think may b its a issue with twrp version... try twrp v2.6 or lower... i think it will work for sure...

Categories

Resources