problem with one mini

GixxGle

Member
Aug 27, 2011
17
1
0
Steps for installing cm11 to new partition after ota 4.4.2 update:

  1. Flash recovery that supports new partition.
    (TWRP2630-KKOneMine.zip or twrp-2.7.0.5-m4kk.img.zip)
  2. Download the latest nightly from http //download.cyanogenmod.org/?device=m4.
    (cm-11-201404xx-NIGHTLY-m4.zip)
  3. Edit nightly zip file by replacing boot.img and META-INF/com/google/android/updater-script with attached files.
    (boot.img and updater-script(updater-script.zip))
  4. Flash the editied nightly zip file from the recovery.
Ohhhhh lay!, i'll try today.

Thanks in Advances.

----------------------------------

Big Thanks Again kyasu for your recommend.

My HTC One mini Life Again.
 
Last edited:

GixxGle

Member
Aug 27, 2011
17
1
0
Steps for installing cm11 to new partition after ota 4.4.2 update:

  1. Flash recovery that supports new partition.
    (TWRP2630-KKOneMine.zip or twrp-2.7.0.5-m4kk.img.zip)
  2. Download the latest nightly from http //download.cyanogenmod.org/?device=m4.
    (cm-11-201404xx-NIGHTLY-m4.zip)
  3. Edit nightly zip file by replacing boot.img and META-INF/com/google/android/updater-script with attached files.
    (boot.img and updater-script(updater-script.zip))
  4. Flash the editied nightly zip file from the recovery.
Dear kyasu

Your update-script.zip can i apply for OTA update?
(OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_WWE_3.10.707.3-1.32.707.2_R_release_351633.zip)

i success to update hboot 2.22 from cmvienneau (http://forum.xda-developers.com/showthread.php?t=2584810)
If i try what your concern? :confused:
 

kyasu

Senior Member
Sep 23, 2012
488
2,234
123
Tokyo
Dear kyasu

Your update-script.zip can i apply for OTA update?
(OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_WWE_3.10.707.3-1.32.707.2_R_release_351633.zip)

i success to update hboot 2.22 from cmvienneau (http://forum.xda-developers.com/showthread.php?t=2584810)
If i try what your concern? :confused:
My update-script.zip cannot be applied for OTA update.
OTA file you specified contains hboot 2.22.
So if you are using stock rom, you can update by the OTA file and modded hboot 2.22 will be replaced by the stock hboot 2.22 (maybe).
 
  • Like
Reactions: GixxGle

GixxGle

Member
Aug 27, 2011
17
1
0
:good:

My update-script.zip cannot be applied for OTA update.
OTA file you specified contains hboot 2.22.
So if you are using stock rom, you can update by the OTA file and modded hboot 2.22 will be replaced by the stock hboot 2.22 (maybe).
:good::laugh:

Thanks
 

silverbox750

Senior Member
Dec 2, 2010
69
5
0
Boot loop help

Hi there,i used the fuu for stock rom and recovery,i was runnning 4.4.2 hboot 2.21 s off
and after fuu phone was on boot loop so i run the 4.4.2 fuu and phone still in boot loop.
i made a back up via twrp and saved it in my pc,now no backup in the phone and phone
on boot loop.
how can i push the backup to restore via twrp..? if its possibile
or how can i just fixed that bootloop.?
please help..
 

lfe.zaius

Member
Jul 11, 2015
11
0
0
Corrupt emmc

Apologize for reviving an old thread, however this seems to be the correct path to fix my BRICKED M4.

UNLOCKED M4 S-OFF CID 11111111 HBOOT 2.22

fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5822000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4116mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f6d46eca
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Have failed to write new boot and recovery via fastboot. NO recovery image to boot into from fastboot. Unable to get adb running. Posted below terminal logs of various commands. Any help would be appreciated, thanks!

erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.010s

erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.039s

erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.007s
fastboot flash boot boot.img
target reported max download size of 800227328 bytes
sending 'boot' (5994 KB)...
OKAY [ 0.917s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 1.082s

fastboot flash recovery recovery.img
target reported max download size of 800227328 bytes
sending 'recovery' (8576 KB)...
OKAY [ 1.065s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.235s
 
Last edited: