Related
hi guys...
This was my previous thread..
http://forum.xda-developers.com/showthread.php?t=1463743
Now downloaded the RUU..
RUU_Saga_hTC_Asia_India_1.47.720.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199605_signed_4..
hwen i run the RUU boot loader says security error but RUU says error 155.. here are the shots...
now please guide me to restore it to orignal state? i have SDK tools and Fastboot...
please help me
Try to reboot phone to fastboot mode and then run RUU. That should fix it.
i tried in fastboot mode but still error 155 occurs....i dun knw why im not able to restore the origial backed up image also..here are the contents of my backed up image....
After installing WP7 of MIUI based on..im not able to restore backed up one...but i can restore CM7.1.............
Please guide me .....
When i was going to return to stock rom, I first tried to flash a 1.47-RUU without success. I am not sure why, but the 2.10-RUU worked for me (but that is no choice for you, as I don't see for Asia it in the List of Shiped ROM Collection).
I have been coming from a 6.xxx HBOOT called engHBOOToverARX.img, you will find a link somewhere in the discontinued Tutorial here. If your phone was unbranded, you will find the original tutorial in the quotes. Basically I flashed this engHBOOT in fastboot (resulting in 6.xxx-HBOOT), than I run the RUU.
Thanks for the suggestion...
i ll try with 2.10-RUU AND LET U KNOW..
im my phone platfor info it says my product is HTC_SAGA and my brand is HTC_EUROPE what does this means?
Means shipped indian ruu RUU_Saga_hTC_Asia_India_1.47.720.1_Radio_20.28I.30 .085AU_3805.06.02.03_M_release_199605_signed_4 doent work for me?
this is what i have got after i do "fastboot flash zip rom.zip which was extracted from the above said RUU i.e RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed...
Now what?
please guide me
Which bootloader version are you currently stuck with? Are you able to access recovery etc?
fastboot getvar all - paste the results from that command here.
fastboot rebootRUU - try running the RUU again when you're in this mode.
I have a workaround, but it's not very good so i didn't post before, but you seem pretty desperate. Flash a pre-rooted stock rom via recovery(there's a thread in development section). Then, run gingerbreak to unroot. Try to find a rom from your region. If not, use the latest one. You won't get any updates.
Sent from my iPod touch using Tapatalk
hboot 2.00.002......YES IM ABLE TO ACCESS CWM RECOVERY AT ANY TIME AND RESTORE ONLY CUSTOM ROM BUT NOT ORIGNAL BACK UP DONE FOR THE FIRST TIME AFTER UNLOCK.....
suprisingly after installing CM7.1 i could restore the original back up but now im not able to...
ok i ll do what u said and give u feedback
my phone platfor info it says my product is HTC_SAGA and my brand is HTC_EUROPE what does this means?
You flashed a european rom, no problem. You want to sell it? Say you bought it from spain xD
Sent from my iPod touch using Tapatalk
fastboot getvar all ....................
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.405.6
(bootloader) serialno: MB129TJ00690
(bootloader) imei: 355067047867643
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3795mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt:0
all done!
when i did fastboot rebootRUU
C:\android>fastboot rebootRUU
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
and i had RUU but error 155
what if i want to use it for myself with internet pass through as a must option...????
i have both...RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed ...and
RUU_Saga_hTC_Asia_India_1.47.720.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199605_signed_4
why im not able to go back to the orignal sense UI 2.5/3????
Because that would be downgrading...........
Try this - http://forum.xda-developers.com/showthread.php?t=1399331
Use the 1.47 RUU this time.
C:\android>adb push zergRush /data/local/tmp
push: zergRush/zergRush -> /data/local/tmp/zergRush
1 file pushed. 0 files skipped.
195 KB/s (23060 bytes in 0.115s)
C:\android>adb push misc_version /data/local/tmp
push: misc_version/misc_version -> /data/local/tmp/misc_version
1 file pushed. 0 files skipped.
520 KB/s (589849 bytes in 1.107s)
C:\android>adb shell chmod 777 /data/local/tmp/zergRush
C:\android>adb shell chmod 777 /data/local/tmp/misc_version
C:\android>adb shell
# cd /data/local/tmp/
cd /data/local/tmp/
# ./zergRush
./zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000161e0
[*] Sending 149 zerglings ...
[+] Overseer found a path ! 0x000161e0
[*] Sending 149 zerglings ...
[-] Zerglings did not leave interesting stuff
# adb shell /data/local/tmp/misc_version -s 1.27.405.6
adb shell /data/local/tmp/misc_version -s 1.27.405.6
adb: not found
# /data/local/tmp/misc_version -s 1.27.405.6
/data/local/tmp/misc_version -s 1.27.405.6
--set_version set. VERSION will be changed to: 1.27.405.6
Patching and backing up partition 17...
#
after this i ran 1.47 RUU but error 155 persists....at update signature it failed
i restored back to CM7.1 now agian.......
please guide me......................
im not able to downgrade to 0.98 .im not to s-off........not able restore to original back up ..............
RUUs don't work on official HBOOT (the latest ones anyway) unlocked. Didn't for me anyway. Relock again by typing "fastboot oem lock"
If you get Carrier ID error, use a goldcard.
hi every one
i was trying to match the RIL/basebande versions
i tried to flash some radio files and i dont know what it happend (i really forget what i did exactlly)
sudenlly i pressed the hard reset in the hboot (yes i remember i did this)
after that i tried to reflash a radio file via fastboot
i notices that in my hboot it's writen like this
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
now when i try to flash PG58IMG (radio) it says fail-PU
i thaught that i'm still s-on because that pink LOCKED which written above (even it's written s-off under it !!!!!!!!)
okay i was able to change between hboot version by just flashing the hboot zip file and that's all so i tried to do that like i was
now when i try to flash the hboot (PG58IMG) it says alsi fail-PU
and now i'm stuck into this screen
here is my getvar resault if some one could help me
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 9.99.999.999
(bootloader) serialno: (removed by me because it's not important)
(bootloader) imei: (removed by me because it's not important)
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.509s
specter16 said:
hi every one
i was trying to match the RIL/basebande versions
i tried to flash some radio files and i dont know what it happend (i really forget what i did exactlly)
sudenlly i pressed the hard reset in the hboot (yes i remember i did this)
after that i tried to reflash a radio file via fastboot
i notices that in my hboot it's writen like this
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
now when i try to flash PG58IMG (radio) it says fail-PU
i thaught that i'm still s-on because that pink LOCKED which written above (even it's written s-off under it !!!!!!!!)
okay i was able to change between hboot version by just flashing the hboot zip file and that's all so i tried to do that like i was
now when i try to flash the hboot (PG58IMG) it says alsi fail-PU
and now i'm stuck into this screen
here is my getvar resault if some one could help me
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 9.99.999.999
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.509s
Click to expand...
Click to collapse
As long as you have access to the boot loader and/or fastboot, you're not bricked. You can technically flash Universal firmware and a recovery to get around this but you might want to flash an RUU as it'll boot you into a ROM and give you a working setup to play with.
Since you're S-OFF download and flash an RUU via fastboot, upgrade or downgrade; it makes very little difference as it will put you in a position to flash a recovery and or universal firmware.
A note on RIL/Basebands, 3.32 and 3.33 have no adverse effects of using a non matching RIL baseband so long as your WiFi and mobile network works, you should be good.
P.S: remove your SN & IMEI from your post
Sent from my HTC
DennisBold said:
As long as you have access to the boot loader and/or fastboot, you're not bricked. You can technically flash Universal firmware and a recovery to get around this but you might want to flash an RUU as it'll boot you into a ROM and give you a working setup to play with.
Since you're S-OFF download and flash an RUU via fastboot, upgrade or downgrade; it makes very little difference as it will put you in a position to flash a recovery and or universal firmware.
A note on RIL/Basebands, 3.32 and 3.33 have no adverse effects of using a non matching RIL baseband so long as your WiFi and mobile network works, you should be good.
P.S: remove your SN & IMEI from your post
Sent from my HTC
Click to expand...
Click to collapse
i tried an RUU and it says error 171 usb connection error !
i'm in fastboot and i can see my device connected using the fastboot devices commande
by the way this problem happed while i'm trying to get my wifi working
any way now i'm trying to get my device booting
specter16 said:
i tried an RUU and it says error 171 usb connection error !
i'm in fastboot and i can see my device connected using the fastboot devices commande
by the way this problem happed while i'm trying to get my wifi working
any way now i'm trying to get my device booting
Click to expand...
Click to collapse
I skimmed over your other thread, and you probably should have tried a kernel with BCM drivers if you haven't already.
Try with a different (and known to work) USB.
Also, make sure HTC Sync is closed and that you run the RUU as administrator.
Sent from my HTC
DennisBold said:
I skimmed over your other thread, and you probably should have tried a kernel with BCM drivers if you haven't already.
Try with a different (and known to work) USB.
Also, make sure HTC Sync is closed and that you run the RUU as administrator.
Sent from my HTC
Click to expand...
Click to collapse
i tried Sultan kernel with BCM driver and it didn't work (wifi turning on................................)
any way this is not my current prb now
one other thing
when i try this commande fastboot oem rebootRUU
here is what it says
Code:
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.235s]
finished. total time: 0.257s
and RUU is still not working
specter16 said:
i tried Sultan kernel with BCM driver and it didn't work (wifi turning on................................)
any way this is not my current prb now
one other thing
when i try this commande fastboot oem rebootRUU
here is what it says
Code:
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.235s]
finished. total time: 0.257s
and RUU is still not working
Click to expand...
Click to collapse
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
DennisBold said:
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
Click to expand...
Click to collapse
okay i'll try
please stay connected, i really need you
specter16 said:
okay i'll try
please stay connected, i really need you
Click to expand...
Click to collapse
Sure. If the fastboot commands work I've got something you can try.
Sent from my HTC
DennisBold said:
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
Click to expand...
Click to collapse
not working !!!
fastboot erase recovery gives me this
Code:
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s
specter16 said:
not working !!!
fastboot erase recovery gives me this
Code:
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s
Click to expand...
Click to collapse
You are S-OFF?
Try:
fastboot oem unlock
Else move the universal firmware file into the folder with fastboot and type:
fastboot flash zip <zip name>.zip
Sent from my HTC
DennisBold said:
You are S-OFF?
Try:
fastboot oem unlock
Else move the universal firmware file into the folder with fastboot and type:
fastboot flash zip <zip name>.zip
Sent from my HTC
Click to expand...
Click to collapse
not working
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
specter16 said:
not working
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
Sorry, always getting commands mixed up.
Try:
fastboot update PG58IMG.zip
Sent from my HTC
DennisBold said:
Sorry, always getting commands mixed up.
Try:
fastboot update PG58IMG.zip
Sent from my HTC
Click to expand...
Click to collapse
archive does not contain 'boot.img'
error: update package missing boot.img
are you sure that i'm s-off my friend ??? because it's written in the hboot above with pink
*** LOCKED ***
but under this line it's written S-OFF with green
specter16 said:
archive does not contain 'boot.img'
error: update package missing boot.img
are you sure that i'm s-off my friend ??? because it's written in the hboot above with pink
*** LOCKED ***
but under this line it's written S-OFF with green
Click to expand...
Click to collapse
You're S-OFF, however your bootloader is locked. Meaning commands are locked, S-OFF disables security allowing you to flash things without being signed by HTC.
Could you try this:
fastboot erase cache
fastboot oem rebootRUU (if you get SDcard errors, take out your SDCard and try again)
fastboot flash zip PG58IMG.zip
fastboot reboot-bootloader
Sent from my HTC
DennisBold said:
You're S-OFF, however your bootloader is locked. Meaning commands are locked, S-OFF disables security allowing you to flash things without being signed by HTC.
Could you try this:
fastboot erase cache
fastboot oem rebootRUU (if you get SDcard errors, take out your SDCard and try again)
fastboot flash zip PG58IMG.zip
fastboot reboot-bootloader
Sent from my HTC
Click to expand...
Click to collapse
fastboot erase cache
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.024s
fastboot oem rebootRUU
SD card errors and the device reboot into hboot
specter16 said:
fastboot erase cache
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.024s
fastboot oem rebootRUU
SD card errors and the device reboot into hboot
Click to expand...
Click to collapse
Tried removing your SD-Card? And have you checked the SDCard still works?
Sent from my HTC
DennisBold said:
Tried removing your SD-Card? And have you checked the SDCard still works?
Sent from my HTC
Click to expand...
Click to collapse
nothing is inserted on my phone (SIM / SD)
and my sd card is working fine on my pc
omg what i did :s:s:s
specter16 said:
nothing is inserted on my phone (SIM / SD)
and my sd card is working fine on my pc
omg what i did :s:s:s
Click to expand...
Click to collapse
That's odd. Insert your SDCard after formatting it and placing the PG58IMG.zip on it. Then reboot into bootloader. See if it works, and let me know.
Sent from my HTC
Fail-PU errors generally correspond to firmware corruption
Which is pretty hard to solve
If Op can exactly tell flashing what caused this issue
Maybe we can have a chance
Btw can the phone go to recovery?
Also how did the patched hboot flash went?
Sent from my HTC Sensation 4G using xda premium
DennisBold said:
That's odd. Insert your SDCard after formatting it and placing the PG58IMG.zip on it. Then reboot into bootloader. See if it works, and let me know.
Sent from my HTC
Click to expand...
Click to collapse
- Fail-PU next to the bootloader line
i found this command
Code:
fastboot oem writesecureflag 3
i think this will return me back to s-on
but can i s-off my phone from hboot ??? if i want
or it's useless this command for me ?
In my quest to upgrade the hboot of my HTC One XL (evita), I accidentally used a tool intended for the the HTC One X (JFW Tool), and overwrote my CID to HTC__621. Now I'm stuck in the bootloader. Any help would be much appreciated (especially with the steps, I'm still a bit fuzzy on SuperCID, S-Off, bootloaders, roms and recovery). I think I was previously unlocked, running an unofficial CyanogenMod (because updates stopped coming around), and then I wanted to get on the OTA CM train, but needed to update hboot, which got me in my current situation:
Here's what my bootloader screen says:
Code:
*** TAMPERED ***
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
FASTBOOT (or FASTBOOT USB)
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
And here's what I've tried:
tried setting CID to 11111111
tried flashing recovery (my TWRP recovery is not present anymore)
tried flashing hboot
tried running X-Factor exploits
ran the all-in-one tool to try and exploit and unlock
I cannot seem to get anything to work. Flashing anything generates a remote signature fail id error.
Please help me to get my phone back up again!
Thanks,
Dave
You tried all those things without knowing what you're doing? You must love to live life dangerously!
Your bootloader is locked.
In bootloader, use volume down to scroll to reboot and hit power button to select it. Then read forums on how to unlock bootloader.
Sent from my HTC One X using xda premium
Venomtester said:
In bootloader, use volume down to scroll to reboot and hit power button to select it. Then read forums on how to unlock bootloader.
Click to expand...
Click to collapse
Perfect, that's what I needed (I didn't know bootloaders could become "relocked".
So, I'm now back to where I was before, with a phone I cannot update to the latest CM10, because my hboot is too old (=1.09)
I've tried to follow all the instructions on these forums for updating hboot to 2.14, without any success:
Using Hassoon2000's all-in-one kit for the HTC One X (evita) and also from the command line, I've tried to directly install:
hboot 2.14
OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k (which contains 2.14)
It fails on signature or hangs. I tried this with bootloader locked and unlocked (thanks to Venomtester, I can now do this without difficulty), and from the bootloader, fastboot and htc screens (gold htc logo).
So any hints on how to get hboot 2.14 installed on this device? Failing that, (or perhaps instead of) I could even go back to a factory ROM and settings, if I could get some hints on this.
Thanks again,
Dave
PS: I have a feeling it may be malfunctioning due to that CID change I did. I tried to change CID back using the regular tool, and then used the instructions for hex editing the CID, all without success (adb shell doesn't work)
boulder_dave said:
Perfect, that's what I needed (I didn't know bootloaders could become "relocked".
So, I'm now back to where I was before, with a phone I cannot update to the latest CM10, because my hboot is too old (=1.09)
I've tried to follow all the instructions on these forums for updating hboot to 2.14, without any success:
Using Hassoon2000's all-in-one kit for the HTC One X (evita) and also from the command line, I've tried to directly install:
hboot 2.14
OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k (which contains 2.14)
It fails on signature or hangs. I tried this with bootloader locked and unlocked (thanks to Venomtester, I can now do this without difficulty), and from the bootloader, fastboot and htc screens (gold htc logo).
So any hints on how to get hboot 2.14 installed on this device? Failing that, (or perhaps instead of) I could even go back to a factory ROM and settings, if I could get some hints on this.
Thanks again,
Dave
PS: I have a feeling it may be malfunctioning due to that CID change I did. I tried to change CID back using the regular tool, and then used the instructions for hex editing the CID, all without success (adb shell doesn't work)
Click to expand...
Click to collapse
What is your CID right now still the same?
use fastboot oem readcid to find out if you're not sure.
exad said:
What is your CID right now still the same?
use fastboot oem readcid to find out if you're not sure.
Click to expand...
Click to collapse
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.85.502.3
(bootloader) serialno: HT249W300070
(bootloader) imei: 359691042133556
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
boulder_dave said:
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.85.502.3
(bootloader) serialno: HT249W300070
(bootloader) imei: 359691042133556
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
Click to expand...
Click to collapse
Okie dokie, so, your bootloader is unlocked at this point right?
If so, flash twrp 2.6: fastboot flash recovery recoveryfilename.img
Your CID shouldn't matter for right now, you should at least be able to flash a Rom at this point (obv. not cm10.1 3.4 kernel). Then we can work on SuperCID and S-OFF.
exad said:
Okie dokie, so, your bootloader is unlocked at this point right?
If so, flash twrp 2.6: fastboot flash recovery recoveryfilename.img
Your CID shouldn't matter for right now, you should at least be able to flash a Rom at this point (obv. not cm10.1 3.4 kernel). Then we can work on SuperCID and S-OFF.
Click to expand...
Click to collapse
Thanks for all the help!
2.6 TWRP installed and working. Still running (extremely poorly, all kinds of flakiness: loses cellular data connection constantly) the 10.1 CM I was running before I embarked upon this upgrade.
What should I do next?
Cheers,
Dave
If I'm not wrong, you're gonna need to s-off to get to the newest cm nightlies because of RUU. So first you're gonna need SuperCID. Someone correct me of I'm wrong but I'm gonna say you need to
fastboot oem writecid 11111111
and then head over to the S-Off thread. I wouldn't do this just yet, because I'm not 100% sure, but if someone could confirm that'd be wonderful.
RollTribe said:
If I'm not wrong, you're gonna need to s-off to get to the newest cm nightlies because of RUU. So first you're gonna need SuperCID. Someone correct me of I'm wrong but I'm gonna say you need to
fastboot oem writecid 11111111
and then head over to the S-Off thread. I wouldn't do this just yet, because I'm not 100% sure, but if someone could confirm that'd be wonderful.
Click to expand...
Click to collapse
That command may or may not work.
The good news is, if it doesn't, since you have root and aren't on a 2.14 hboot it's still super easy
If that command doesn't work, boot to the rom you're using, make sure usb debugging is enabled. If you're using CyanogenMod, you'll also have to give ADB root access in developer settings.
Open command prompt in the folder you have ADB and do
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
then you should have superCID and should be able to S-OFF using the sticky in original android dev. section
when you type the su command, it may prompt you on your phone to allow su through adb so keep that in mind.
exad said:
That command may or may not work.
The good news is, if it doesn't, since you have root and aren't on a 2.14 hboot it's still super easy
If that command doesn't work, boot to the rom you're using, make sure usb debugging is enabled. If you're using CyanogenMod, you'll also have to give ADB root access in developer settings.
Open command prompt in the folder you have ADB and do
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
then you should have superCID and should be able to S-OFF using the sticky in original android dev. section
when you type the su command, it may prompt you on your phone to allow su through adb so keep that in mind.
Click to expand...
Click to collapse
Excellent, you guys are the best! So, I have CID = 11111111, S-OFF.
What's the next step to getting back on the CM10 bandwagon? Or updating hboot? Or whatever I need to do next?
Cheers,
Dave
Run your carrier 3.17/3.18 ruu
Then flash twrp then flash cm10.1
Sent from my One X using xda app-developers app
exad said:
Run your carrier 3.17/3.18 ruu
Then flash twrp then flash cm10.1
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Here's how I tried to flash the RUU (failing):
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.945s
This booted me into CM unexpectedly
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>adb reboot-bootloader
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.062s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.835s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.936s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
For some reason, if I didn't reissue the below command, subsequent flashes would fail, even though I was still in the black screen with HTC logo mode
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.060s]
finished. total time: 0.063s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.421s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.514s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.024s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.060s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.132s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.234s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.063s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.144s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.232s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.065s]
finished. total time: 0.070s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>
So I'm not sure what to do next. Flashing RUU doesn't seem to work. bootloader says I'm still S-OFF (whatever that means), now "RELOCKED", CID still 11111111, and hboot still 1.09.
Thanks again for taking me through this,
Dave
All you need to do is run the RUU as was intended. It's an exe file. Plug in your phone and start the program.
Use RUU not OTA, it is easier.
OTA would require stock recovery to complete and much more care with how stock things are.
RollTribe said:
All you need to do is run the RUU as was intended. It's an exe file. Plug in your phone and start the program.
Click to expand...
Click to collapse
Thanks everyone! I'm back on the CM10.1 bandwagon (with OTA updates!) and this HTC One X is working better than ever.
For other folks, here were my mistakes and stumbling blocks:
Don't use utilities intended for the HTC One X (Tegra 3) on the HTC One XL (evita). This is how I accidentally changed my CID. This might seem obvious, but when you're checking around these forums, you can frequently end up in the wrong forum.
ADB commands work when the phone is in its OS.
If the setcid command line doesn't work, use the line from exad.
Don't try and use the RUU flashing procedure (with the OTA .zip file) to flash the firmware, use the .exe file, and just execute it.
I did not (and still don't really) understand the difference and utility of RUUs, S-On/S-Off, unlocking the bootloader, hboot, ROMs, SuperCID, radios, ADB and fastboot commands.
Back to using my now very functional HTC One X (it was on the verge of a tragic high-velocity intentional disassembly).
Cheers,
Dave
boulder_dave said:
[*]I did not (and still don't really) understand the difference and utility of RUUs, S-On/S-Off, unlocking the bootloader, hboot, ROMs, SuperCID, radios, ADB and fastboot commands.
Click to expand...
Click to collapse
There's a link in my signature that I took time to write up just for explaining these.
Fixed
And how will his hboot go to 2.14?
Sent from my HTC One XL using xda app-developers app
---------- Post added at 01:42 AM ---------- Previous post was at 01:39 AM ----------
Cause I'm confused to where you got the exe file from? Thanks
Sent from my HTC One XL using xda app-developers app
ZayedQamer.zq said:
And how will his hboot go to 2.14?
Sent from my HTC One XL using xda app-developers app
---------- Post added at 01:42 AM ---------- Previous post was at 01:39 AM ----------
Cause I'm confused to where you got the exe file from? Thanks
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
by running the RUU :silly: http://forum.xda-developers.com/showthread.php?t=1671237
Hi,
I'm wondering if anybody can help me to find HTC One S RUU for Cincinnati Bell?
Or nandroid backup?
Or if you have boot.img, recovery.img and system.img?
CID = HTC__017
-----------------------------------------
*** LOCKED ***
VLE PVT SHIP S-ON RL
HBOOT - 1.13.0000
RADIO - 1.16.31501S.16_2
OpenDSP-v28.1.0.32.0504
eMMC - boot
Apr 20, 2012, 15:14:18
-------------------------------------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.84.422.6
(bootloader) serialno: FA2XXXX00199
(bootloader) imei: 352XXXXXXXXX254
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: HTC__017
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.082s
Thanks
Fraser34 said:
Hi,
I'm wondering if anybody can help me to find HTC One S RUU for Cincinnati Bell?
Or nandroid backup?
Or if you have boot.img, recovery.img and system.img?
CID = HTC__017
-----------------------------------------
*** LOCKED ***
VLE PVT SHIP S-ON RL
HBOOT - 1.13.0000
RADIO - 1.16.31501S.16_2
OpenDSP-v28.1.0.32.0504
eMMC - boot
Apr 20, 2012, 15:14:18
-------------------------------------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.84.422.6
(bootloader) serialno: FA2XXXX00199
(bootloader) imei: 352XXXXXXXXX254
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: HTC__017
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.082s
Thanks
Click to expand...
Click to collapse
Can't find a matching RUU
BUT
i recently helped another user with a simiar problem.
In case you unlock the bootloader and get S-OFF you can do as followed:
S-OFF your phone --> get super CID --> flash stock recovery --> change CID to e.g unbranded (HTC__001) --> Flash unbranded RUU
LS.xD said:
Can't find a matching RUU
.....
In case you unlock the bootloader and get S-OFF you can do as followed:
S-OFF your phone --> get super CID --> flash stock recovery --> change CID to e.g unbranded (HTC__001) --> Flash unbranded RUU
Click to expand...
Click to collapse
Thanks for reply.
Yes, I've unlocked bootloader.
But my problem is - I have bootloop.
So, I can't load Android on the phone to use adb to S-OFF my phone.
(What I found so far is - you need to have working adb to S-OFF the phone)
Which means I can't change CID to be able to flash any other RUU.
Thanks.
Fraser34 said:
Thanks for reply.
Yes, I've unlocked bootloader.
But my problem is - I have bootloop.
So, I can't load Android on the phone to use adb to S-OFF my phone.
(What I found so far is - you need to have working adb to S-OFF the phone)
Which means I can't change CID to be able to flash any other RUU.
Thanks.
Click to expand...
Click to collapse
Can you enter fastboot mode?
LS.xD said:
Can you enter fastboot mode?
Click to expand...
Click to collapse
Yes, I can.
And:
If I go to "Factory reset" - it goes to bootloop.
If I go to Recovery - it goes to bootloop.
Fraser34 said:
Yes, I can.
And:
If I go to "Factory reset" - it goes to bootloop.
If I go to Recovery - it goes to bootloop.
Click to expand...
Click to collapse
You'll have to flash a working recovery using fastboot. Do you know how to do?
LS.xD said:
You'll have to flash a working recovery using fastboot. Do you know how to do?
Click to expand...
Click to collapse
Yes. I know how to flash a working recovery using fastboot.
What do I do after that?
Is your sdcard working or do you have storage mount error?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Is your sdcard working or do you have storage mount error?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Well, how or when can I see that?
So far I didn't see any errors related to sdcard.
I just want to remind - Android doesn't boot, my PC doesn't see my phone, so, I can't put anything on sdcard.
Thanks
Fraser34 said:
Well, how or when can I see that?
So far I didn't see any errors related to sdcard.
I just want to remind - Android doesn't boot, my PC doesn't see my phone, so, I can't put anything on sdcard.
Thanks
Click to expand...
Click to collapse
Flash latest TWRP using fastboot.
Perform a FULL wipe.
Flash rom via ADB Sideload (TWRP supports this feature)
IMPORTANT: Your bootloader vesrion will only support 4.0x versions. May be JB too. But NO 4.3+. So i'd suggest to flash ICS rom.
You will need to flash the kernel (boot.img) manually using fastboot due to your phone is S-ON!
Just to make sure that I understood you correctly:
LS.xD said:
Flash latest TWRP using fastboot.
Click to expand...
Click to collapse
For example this one - openrecovery-twrp-2.7.0.0-ville.img ?
So, after I install it , if I go to fastboot -> recovery I should see, let's call it, TWRP menu. Is it correct?
And ADB Sideload is one of the menu?
LS.xD said:
Perform a FULL wipe.
Flash rom via ADB Sideload (TWRP supports this feature)
IMPORTANT: Your bootloader vesrion will only support 4.0x versions. May be JB too. But NO 4.3+. So i'd suggest to flash ICS rom.
Click to expand...
Click to collapse
Should I try this ROM, for example:
[ROM] MaximusHD 10.0.0 | JB 4.2.2 | Sense 5.0 | Fast&Stable | OTA Updates | 4.06.401.1 | Online
LS.xD said:
You will need to flash the kernel (boot.img) manually using fastboot due to your phone is S-ON!
Click to expand...
Click to collapse
Where should I get boot.img ?
So far I found RUU for my RADIO - 0.16.31501S.16_2 for T-Mobile (CID = T-MOB010):
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
But my CID = HTC__017
Should I take boot.img from this RUU?
Thanks
Fraser34 said:
Just to make sure that I understood you correctly:
For example this one - openrecovery-twrp-2.7.0.0-ville.img ?
So, after I install it , if I go to fastboot -> recovery I should see, let's call it, TWRP menu. Is it correct?
And ADB Sideload is one of the menu?
Should I try this ROM, for example:
[ROM] MaximusHD 10.0.0 | JB 4.2.2 | Sense 5.0 | Fast&Stable | OTA Updates | 4.06.401.1 | Online
Where should I get boot.img ?
So far I found RUU for my RADIO - 0.16.31501S.16_2 for T-Mobile (CID = T-MOB010):
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
But my CID = HTC__017
Should I take boot.img from this RUU?
Thanks
Click to expand...
Click to collapse
NO!
Maximus HD is for S-OFF only!!!
You have to use the boot.img contained in the rom you flash. Otherwise you will have a brick again.
I'm looking for a compatible Rom for you. Just some patience please.
LS.xD said:
NO!
Maximus HD is for S-OFF only!!!
Click to expand...
Click to collapse
Got it.
LS.xD said:
You have to use the boot.img contained in the rom you flash. Otherwise you will have a brick again.
I'm looking for a compatible Rom for you. Just some patience please.
Click to expand...
Click to collapse
OK. Thanks - waiting for you.
(Actually, I would like to have something close to stock ROM as much as possible.)
Fraser34 said:
Got it.
OK. Thanks - waiting for you.
(Actually, I would like to have something close to stock ROM as much as possible.)
Click to expand...
Click to collapse
Really hard to find a 4.0.3 based rom these days...
Here it is --> Virtuos 1.4 - based on stock 4.0.3
Just to make sure that I understood you correctly:
Quote:
Originally Posted by LS.xD View Post
Flash latest TWRP using fastboot.
For example this one - openrecovery-twrp-2.7.0.0-ville.img ?
So, after I install it , if I go to fastboot -> recovery I should see, let's call it, TWRP menu. Is it correct?
And ADB Sideload is one of the menu?
Yes please use TWRP 2.7. ADB sideload is selectable in the TWRP menu.
Connect it to your computer. Open commandline.
Type "adb sideload ROMNAME.zip" and it will flash the rom immediately to your phone.
LS.xD said:
Really hard to find a 4.0.3 based rom these days...
Here it is --> Virtuos 1.4 - based on stock 4.0.3
Click to expand...
Click to collapse
Great!
I'll try it and let you know.
Thanks a lot!
2. To flash TWRP 2.7
OK.
I'm trying to flash TWRP 2.7:
>fastboot flash recovery openrecovery-twrp-2.7.0.0-ville.img
sending 'recovery' (9046 KB)...
OKAY [ 1.098s]
writing 'recovery'...
OKAY [ 2.164s]
finished. total time: 3.265s
I go to bootloader - please, see pic1 how it looks.
I go to "RECOVERY" from FASTBOOT - HTC logo with text appears, black screen and after that the phone goes to bootloop again. See pic2.
Looks like TWRP was not installed?
Am I doing something wrong?
Thanks.
Fraser34 said:
OK.
I'm trying to flash TWRP 2.7:
>fastboot flash recovery openrecovery-twrp-2.7.0.0-ville.img
sending 'recovery' (9046 KB)...
OKAY [ 1.098s]
writing 'recovery'...
OKAY [ 2.164s]
finished. total time: 3.265s
I go to bootloader - please, see pic1 how it looks.
I go to "RECOVERY" from FASTBOOT - HTC logo with text appears, black screen and after that the phone goes to bootloop again. See pic2.
Looks like TWRP was not installed?
Am I doing something wrong?
Thanks.
Click to expand...
Click to collapse
Have you restarted the bootloader after flashing? Pls immediately rastart the bootloader after installing twrp.
Why you got the bootloop? (What did you change?)
LS.xD said:
Have you restarted the bootloader after flashing? Pls immediately rastart the bootloader after installing twrp.
Why you got the bootloop? (What did you change?)
Click to expand...
Click to collapse
1. I flashed TWRP
2. reboot bootloader
3. FASTBOOT -> RECOVERY. And I got bootloop.
Fraser34 said:
1. I flashed TWRP
2. reboot bootloader
3. FASTBOOT -> RECOVERY. And I got bootloop.
Click to expand...
Click to collapse
Don't panic
If fastboot is bugged, relock bootloader and unlock again. Then flashing will be fine.
May you tell me what caused the bootloop originally? Will help to find a solution.
LS.xD said:
Don't panic
If fastboot is bugged, relock bootloader and unlock again. Then flashing will be fine.
May you tell me what caused the bootloop originally? Will help to find a solution.
Click to expand...
Click to collapse
1.
When I re-lock it it says:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.938s
But re-locks it.
2. Unlock it again - no problem
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.152s
3. re-flash TWRP 2.7:
sending 'recovery' (9046 KB)...
OKAY [ 1.084s]
writing 'recovery'...
OKAY [ 2.172s]
finished. total time: 3.258s
4. reboot bootloader, reboot the phone.
5. FASTBOOT -> RECOVERY - bootloop !!!
2. I bought the phone from eBay in this condition - bootloop.
Thanks
[Solved] HTC Butterfly S-Off, Unlock, Bootloader & TWRP Recovery "Stuck in bootloop."
PLEASE try to HELP or acknowlede!
Please forgive me for contacting you as such but I'm desparate right now.
Dear All,
I'm wound up in a bootloop. Please help at the earliest.
This is my current status and a little history.
1. I was flashed InsertCoin 3.0.6 on my x920d (originally HTC_038) a couple of days ago (and did a TWRP Backup after That),
2. Had unlocked my previous, old custom rom (thru HTCDev), S-Off (thru rumrunner) and
3. rooted by flashing 'UPDATE-SuperSU-v2.02' from recovery after flashing the ROM a couple of days earlier.
4. I had also flashed Kairi's firmware-kk (which is for HTC_061) as I had Super CID 11111111 by "fastboot oem writecid..." method, now I'm not able to do it anymore).
Anyway, there was some problem (wrongly presumed by me) with the htc backup/restore function, so I reflashed the IC3.0.6 rom a couple of times thru recovery(TWRP 2.7 by Kairi). And the device booted perfectly.
Stupidly, I happened to flash '[ROM] FireKatN4 Deodex V5 TW 4.4.4' through Kairi's recovery. Link of the ROM - http://forum.xda-developers.com/note...emely-t2916463.
Thish rom was for Samsung T Mobile Galaxy Note 4 N910T and it did not flashed properly; so I re-flashed IC3.0.6 thru recovery (if required I can perform this again) and it showed successful at the end.
Now since then whenever I reboot it get stuck in bootloop.
Since yesterday I have been trying various steps (repeated several times and not inchronological order):
- Unlocked the bootloader thru HTCDev once again.
- Flashing the firmware-kk thru oemRUU after changing the CID to 11111111 in the 'adroid-info file" of this firmware's zip. (it gave Remote90 error and after repeating fastboot flash zip firmware-kk.zip it flashed.
Although in between it said "signature checking, verified fail - Bypassing" and then continued on its own after that, successful at the end. However on my device the green bar moved only to 90% and remained there.)
- Rebooted into bootloader, tried flashing the same firmware with Error :
"C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 1.975s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.011s"
Now my status is:
Although I'm able to flash recovery img thru fastboot. I can do it from oem rebootRUU.
My Getvar all read as :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 3A.32.306.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.709.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxx
(bootloader) imei: xxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11 - (As per Kairi's original Firmware-kk android-info file it is : 3, the CID is HTC_061)
(bootloader) gencheckpt: 0
all: Done!
Now
1. I,m S-Off, Relocked/Unlocked Bootloader (able to do this thru fastboot).
2. Can boot into bootloader & TWRP Recovery - Kairi's, but cannot boot the phone.
3. After flashed IC3.0.6 thru recover once again. when rebooting, get stuck in bootloop again.
Please try to help me out.
P.S. I have somescreenshots available of several steps, if required.
Hi Capt Vikram.
Try extracting the boot img and flash that. It has got me out of a few bootloops
Clarkie_955i said:
Try extracting the boot img and flash that. It has got me out of a few bootloops
Click to expand...
Click to collapse
Hi Clarkie,
Your help is appreciated.
I flashed the IC3.0.6 rom thru recovery successfull.
rebooted to bootloop.
Then I flashed the boot img from InsertCoin 3.0.6 from fastboot.
No luck Again stuck in bootloop.
Capt Vikram Sandhu said:
Hi Clarkie,
Your help is appreciated.
I flashed the IC3.0.6 rom thru recovery successfull.
rebooted to bootloop.
Then I flashed the boot img from InsertCoin 3.0.6 from fastboot.
No luck Again stuck in bootloop.
Click to expand...
Click to collapse
Did you flash the kk firmware twice? It will fail on the first go so flash again.
Clarkie_955i said:
Did you flash the kk firmware twice? It will fail on the first go so flash again.
Click to expand...
Click to collapse
Yes Clarkie,
I had flashed firmware-kk thru 'fastboot oem rebootRUU', then 'fastboot flash zip fimware-kk.zip'
It gave me th 90 error and I repeated the command and it went successful.
I'll do that again and update you with each step chronologically.
Thanks for your help in my desparate situation.
Here's what I repeated. Step - by -step
1. First of all got the getvar all details:
C:\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 3A.32.306.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.709.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4195mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
QUERY : Should I be concerned regarding
i. (bootloader) platform: HBOOT-8064
ii. (bootloader) hbootpreupdate: 11, because in Kairi's firmware zip the android-info reads
1) CID H_061 (I changed it to 11111111)
2) hbootpreupdate:3 (This I did not change)
2. Relocked the boot loader (after checking if I could unlock it again through the previous code.bin. I did this successfully but without Selecting 'Yes' option at the end of the process on my device)
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (Too many links))
finished. total time: 1.246s
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.136s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.009s]
finished. total time: 0.148s
NOTE: Both the times device booted into bootloop.
3. Flashing Kairi's firmware-kk.zip through RUU
a. Rebooted in RUU
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.053s]
finished. total time: 0.055s
b. Flashed firmware-kk (remember the file CID changed to 11111111
C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 2.007s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 3.490s
C:\Fastboot>
C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 2.016s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-2,0
(bootloader) [RUU]WP,sbl1-2,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,8
(bootloader) [RUU]UZ,radio,13
(bootloader) [RUU]UZ,radio,22
(bootloader) [RUU]UZ,radio,31
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,58
(bootloader) [RUU]UZ,radio,67
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,80
(bootloader) [RUU]UZ,radio,89
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,35
(bootloader) [RUU]WP,radio,71
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 10.628s]
finished. total time: 12.650s
Note: In the device the green bar did not reach the end. And did not reboot.
c. 'fastboot reboot bootloader' - command not recognized
d. 'fastboot reboot' - rebooted into bootloop
e. Manually booted the device into bootloader.
4. Getvar all - Same as previous.
5. Unlocked the bootloader.
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.136s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.149s
Note: The device automatically rebooted into bootloop yet again. Manually rebooted to bootloader it shows *** UNLOCKED ***
6. Re flashed Kairi's TWRP
C:\Fastboot>fastboot flash recovery TWRP-2-7-Kairi.img
target reported max download size of 1514139648 bytes
sending 'recovery' (10572 KB)...
OKAY [ 1.564s]
writing 'recovery'...
OKAY [ 0.977s]
finished. total time: 2.546s
7. Entered Recovery from the device. (To install Kairi's reset kernel) Did not wipe cache/dalvik after installation
Note: - 'adb reboot bootloader' did not work at recovery, thou
C:\Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA34HPN00627 recovery
C:\Fastboot>adb reboot bootloader
8. Entered bootloader thru TWRP options on the device.
9. Flashed boot.img (extracted from InsertCoin 3.0.6 Zip). Did not erase cache after this.
C:\Fastboot>fastboot flash boot boot.img
target reported max download size of 1514139648 bytes
sending 'boot' (6500 KB)...
OKAY [ 0.926s]
writing 'boot'...
OKAY [ 0.747s]
finished. total time: 1.677s
10. Entered recovery to install InsertCoin Rom.
a. Selected - Perform a full wipe in the installer.
b. Deselected all the checkmarks (for HTC + Google)
c. Selected - 'Enable Cache - All times' in the end
d. Install. (Please refer the attached screen shots)
e. Reboot your Device now from the installer. (HOPE TO boot into android. Fingers crossed).
f. Again Bootloop.
g. Rebooted into bootloader
h. Fastboot the boot image once again erased cache after that.
C:\Fastboot>fastboot flash boot boot.img
target reported max download size of 1514139648 bytes
sending 'boot' (6500 KB)...
OKAY [ 0.926s]
writing 'boot'...
OKAY [ 0.745s]
finished. total time: 1.675s
C:\Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.068s]
finished. total time: 0.070s
I. Still in bootloop.
Please help/advice.
Hi Vikram.
This could be the blind leading the blind. But I will help out as much as I can.
I had the same problem with IC boot looping and especially with my nandroid backups. See if you can download a different rom and get that on your sd card and flash that. You can try BOA Butterfly v8.0 that always booted up for me when IC wouldn't. I also found a stock nandroid x920d backup that worked. At least I had my device working until I had the time to sort out IC on my device.
Now a couple of your queries.
My cid 11111111
HBOOT 1.57
The green progress bar never reaches the end it always stays at about 90% and reboot bootloader command should be like this
"adb reboot-bootloader" without the quotes
Sorry Vikram all over the place tonight I just finished work. Hope this helps. Plus the best information I can give you as well is search this site. everything you need is on here with a little searching. Only been doing this since July and I also tried to flash every rom out there only to discover that they all don't work. Got myself out of a few bootloops.
Try what I mentioned above and see how you go with that.
Clarkie_955i said:
Hi Vikram.
This could be the blind leading the blind. But I will help out as much as I can.
I had the same problem with IC boot looping and especially with my nandroid backups. See if you can download a different rom and get that on your sd card and flash that. You can try BOA Butterfly v8.0 that always booted up for me when IC wouldn't. I also found a stock nandroid x920d backup that worked. At least I had my device working until I had the time to sort out IC on my device.
Now a couple of your queries.
My cid 11111111
HBOOT 1.57
The green progress bar never reaches the end it always stays at about 90% and reboot bootloader command should be like this
"adb reboot-bootloader" without the quotes
Sorry Vikram all over the place tonight I just finished work. Hope this helps. Plus the best information I can give you as well is search this site. everything you need is on here with a little searching. Only been doing this since July and I also tried to flash every rom out there only to discover that they all don't work. Got myself out of a few bootloops.
Try what I mentioned above and see how you go with that.
Click to expand...
Click to collapse
Thanks A TON Clarkie,
Your reply is very much appreciated. It seems like a ray of hope in a dark tunnel. Really grateful to you.
Now coming back to the matter at hand -
I had earlier tried to
1. Tried to flash 'NOS_m7_v3.0.0_dlxbu1' thru Recovery, was successful but when tried to boot, got stuck again in bootloop. Then again installed InserCoin.
Note - Maybe I did not perfom a wipe cache & definately did not flash the boot image thru fastboot after flashing the above rom.
Secondly I'm neither able to reboot from bootloader mode into recovery nor vice verca.
Thirdly, I cannot flash any zip from bootloader (but able to flash image files thru bootloader & install zip thru recovery); & no "fastboot reboot recovery" from bootloader mode and no "adb reboot bootloader"
from recovery (same with RUU "fastboot reboot bootloader", though in recovery & fastboot mode "adb/fastboot devices" show my device).
Fourthly, whenever I reboot into system/android I get Two bootscreens - 1. HTC Quietly Brilliant & the device gets disconnected and connected again and the second boot screen is HTC One.
Finally it stays at the HTC One screen for some time and suddenly there is some very slight variation in the brightness of the bootscreen, then the capacitive buttons (Back, Home & Recent app) lightens and it
reboots.
2. Tried to restore from TWRP Backup (when I was successfully running InserCoin for the first time) but again the bootloop. I also have one of NOS_m7_v3.0.0 (When I was S-On), that I've not tried yet as I'm afraid to get
back to S-On and bootloop at the same time..
3. Meanwhile, today a couple of hours ago, I came across this thread - http://forum.xda-developers.com/showthread.php?t=2208833, and
performed an advanced wipe thru recovery (wiping everythingh except external sd card). Wiped Dalvik Cache. TWRP Backup. Rebooted. (For a lovely change) Got stuck at boot screen -HTC Quitely Briliant.
(maybe no OS installed).
4. Manually went into bootloader and then recovery. Installed InsertCoin again. At the end it said no SuperSU. Swiped to install it. Reboot. Got stuck at Bootloop.
Please try to Suggest:
A. When to flash boot.img - before or after installing the rom.
B. Does restoring S-On state backup will effect my S-Off condition.
Thanx In Advance.
1 + 1 = 11
Will Definately try BOA's Rom meanwhile.
HI Clarkie,
Tried the download links at BOA's ROM thread in the forum. Doesen't work.
Can you provide me a link.
Ok Vikram.
From what I have done and read I have always done a factory reset thru recovery before flashing any rom. Also try re flashing TWRP same version. I also got stuck on HTC ONE screen and turned the device of at power button and back on and it booted up fine. I would keep your device at s.off and i flashed the boot img after the rom because the device would not boot. Sorry for the short replies I am not that quick on the keyboard.
Here is the link for boa
http://forum.xda-developers.com/showthread.php?t=2656094
Spare link 4 is still up.
Just keep going on it. It is a process of thinking what worked before and why it not working now.
Keep me posted
Clarkie_955i said:
Ok Vikram.
From what I have done and read I have always done a factory reset thru recovery before flashing any rom. Also try re flashing TWRP same version. I also got stuck on HTC ONE screen and turned the device of at power button and back on and it booted up fine. I would keep your device at s.off and i flashed the boot img after the rom because the device would not boot. Sorry for the short replies I am not that quick on the keyboard.
Here is the link for boa
http://forum.xda-developers.com/showthread.php?t=2656094
Spare link 4 is still up.
Just keep going on it. It is a process of thinking what worked before and why it not working now.
Keep me posted
Click to expand...
Click to collapse
Thanks Clarkie,
I'll give it a shot.
And let you know.
Capt Vikram Sandhu said:
Thanks Clarkie,
I'll give it a shot.
And let you know.
Click to expand...
Click to collapse
Check your commands you need one of these ---- between adb reboot-bootloader. That is what I was trying to say last night. Not sure if you got it.
Cheers
Clarkie_955i said:
Check your commands you need one of these ---- between adb reboot-bootloader. That is what I was trying to say last night. Not sure if you got it.
Cheers
Click to expand...
Click to collapse
Got it Sir,
Thanx.
P.S. Downloading the BOA Rom from the link. Will let you know what happens.
Capt Vikram Sandhu said:
Got it Sir,
Thanx.
P.S. Downloading the BOA Rom from the link. Will let you know what happens.
Click to expand...
Click to collapse
No worries.
Remember if it gets stuck on htc screen power off with power button and restart. See how you go.
Good Luck
Clarkie_955i said:
No worries.
Remember if it gets stuck on htc screen power off with power button and restart. See how you go.
Good Luck
Click to expand...
Click to collapse
Hi Clarkie,
Tried the following:
Installed TWRP 2.6.3
Factory reset from recovery.
Installed BOA V8.0 thru recovery (Couldn't understand the language of aroma installer, but went ahead both the times).
Device Rebooted into bootloop again.
Powered off with only the power button, but then it again restarted into bootloop.
Flashed the boot.img thru fastboot. Reboot. Again bootloop.
Went to Recovery. Wiped everythingh except Micro SDcard
Installed the rom thru recovery install zip
Aroma Installer Finished Screen -> from recovery reboot options went into fastboot. Flashed the boot.img.
Rebooted to System - Back to square 1 in bootloop.
Also during the bootloop pressing down the power button does not power off & restarts the device. But the screen goes off for a few seconds and automatically boots intp the bootloop.
FYI -
I'm using a partitioned sd card. with 1. FAT32, 2. ext4 & 3. Linux SWAP. And thru recovery file manager it showed sd-ext & superuser folders in the root. I'll give it a try on an unpartitioned card.
had successfully, flashed recovery-clockwork-touch-6.0.3.1-dlxub1 before flashing TWRP 2.6.3. But the CWMod recovery shows the following:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I tried adb reboot-bootloader but nothing happens.
Please try to suggest from here.
How can I check (from Bootloader/recovery) if my device is rooted/unrooted.
I mean when the splash screens stays on for more than a few minutes and not in boot loop hit the power button to off then back on. That has worked for me. I am not sure about your partitioned sd card. I just store things on mine.
Have a look at this. http://forum.xda-developers.com/showthread.php?t=2283896
I had the same similar errors a while ago but I cant remember how I fixed it. Well I do. I fixed one error at a time and lots of searching.
Clarkie_955i said:
I mean when the splash screens stays on for more than a few minutes and not in boot loop hit the power button to off then back on. That has worked for me. I am not sure about your partitioned sd card. I just store things on mine.
Have a look at this. http://forum.xda-developers.com/showthread.php?t=2283896
I had the same similar errors a while ago but I cant remember how I fixed it. Well I do. I fixed one error at a time and lots of searching.
Click to expand...
Click to collapse
I have done again the following steps as you said:
1. Started the Device.
2. First Splash screen came up - HTC quietly Briliant.
3. Second Splash Screen came up - HTC One.
4. Waited for one/two seconds and pressed continuosly on the power button.
5. Screen went totally black/maybe powered off.
6. Removed my finger from the Power button in order to press it back to power the device.
7. Before I can press it is back on the first splash screen pops up and the bootloop starts.
8. Even If I do not release the power button after the 5th step it automatically reboots & bootloop starts.
I did try this from the first bootscreen and also after complete power down from bootloader/recovery mode.
Meanwhile I'll search the link you gave.
I think that maybe I'm unrooted now because when i try thru recovery - advance - file manager, I cannot see any file in /system/bin/ (where there should have been a su file there.)
Thanks for your reply . will keep you posted.
Your replies mean a lot to me.
Hi Clarkie,
Re-read all of your posts and guidance.
Motivated by this and the links provided espaicially by you and reply from abhinav.tella I think I'm able to lock on the problem (perhaps).
Right now compiling it and will post with further details.
Kindly try to walk me thru it with your suggestions and guidance.
Thanx in advance.
Bits and Pieces
Hi Clarlie,
Thanks for your time & energy till date. You are kind enough to help out somebody very selflessly on your part. I'm motivated and have inculcated the same.
Anyway, I tried to understand the whole thing piece by piece. Also I have assimilated a few screenshots (I have many others if required.)
The following is only what I did & now think could be the cause.
First of all; I had successfully installed and was running InsertCoin a few days ago. See Step by Sep as per the numbered images attached with this and several within the next few following posts.
1
1. 1. Unlocked, rooted & running InserCoin, (but a Kernel & firmware based on 4.2 custom rom) --- 28-11-14 17-23hrs
1. 2. Achieved S-Off with XUNUS's (http://forum.xda-developers.com/htc-butterfly/help/qa-insertcoin-3-0-6-dlxub1-android-4-4-t2950052)help & updated to TWRP 2.7 Kairi's along with reste-kernel-ub1 again Kairi's, 29-11-14 19-32.
1. 3. bootloader after s-off before revone, 29-11-14 23-09.
1. 4. bootloader after removing TAMPERED thru revone, 30-11-14 00-02
Cont to next to post...
Capt Vikram Sandhu said:
Hi Clarlie,
Thanks for your time & energy till date. You are kind enough to help out somebody very selflessly on your part. I'm motivated and have inculcated the same.
Anyway, I tried to understand the whole thing piece by piece. Also I have assimilated a few screenshots (I have many others if required.)
The following is only what I did & now think could be the cause.
First of all; I had successfully installed and was running InsertCoin a few days ago. See Step by Sep as per the numbered images attached with this and several within the next few following posts.
1
1. 1. Unlocked, rooted & running InserCoin, (but a Kernel & firmware based on 4.2 custom rom) --- 28-11-14 17-23hrs
1. 2. Achieved S-Off with XUNUS's (http://forum.xda-developers.com/htc-butterfly/help/qa-insertcoin-3-0-6-dlxub1-android-4-4-t2950052)help & updated to TWRP 2.7 Kairi's along with reste-kernel-ub1 again Kairi's, 29-11-14 19-32.
1. 3. bootloader after s-off before revone, 29-11-14 23-09.
1. 4. bootloader after removing TAMPERED thru revone, 30-11-14 00-02
Cont to next to post...
Click to expand...
Click to collapse
Ok Vikram.
I found this for you. It is a very good write up with great detail. http://forum.xda-developers.com/showthread.php?t=2630214
Hope this gets you going.
---------- Post added at 07:37 AM ---------- Previous post was at 07:29 AM ----------
Clarkie_955i said:
Ok Vikram.
I found this for you. It is a very good write up with great detail. http://forum.xda-developers.com/showthread.php?t=2630214
Hope this gets you going.
Click to expand...
Click to collapse
You might want to change your cid. Thought you was supercid 11111111