I have SuperCID and rooted. What am I doing wrong?
C:\androidSDK\sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\androidSDK\sdk\platform-tools>fastboot getvar cid
< waiting for device >
cid: 11111111
finished. total time: 0.002s
C:\androidSDK\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.082s]
finished. total time: 0.082s
C:\androidSDK\sdk\platform-tools>fastboot flash zip PJ8312000-OneX.zip
sending 'zip' (36064 KB)...
OKAY [ 2.859s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.992s
C:\androidSDK\sdk\platform-tools>fastboot oem boot
< waiting for device >
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F50C4
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD0B
(bootloader) TAG:hero panel = 0x4940047
(bootloader) TAG:engineerid = 0x2
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is O2___102
(bootloader) setting->cid:2___102
(bootloader) serial number: HT26KW307917
(bootloader) commandline from head: console=ttyHSL0,115200,n8 androidboot
(bootloader) .hardware=qcom
(bootloader) command line length =790
(bootloader) active commandline: poweron_status=1 reset_status=0 board_el
(bootloader) ite.disable_uart3=0 diag.enabled=0 board_elite.debug_uart=0
(bootloader) userdata_sel=0 androidboot.emmc=true androidboot.pagesize=20
(bootloader) 48 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.sf=1 td.td=1 td
(bootloader) .ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=69
(bootloader) 4 imc_online_log=0 androidboot.efuse_info=FFSL androidboot.
(bootloader) baseband=1.27a.32.45.28 androidboot.cid=O2___102 androidboot
(bootloader) .devicerev=0 androidboot.batt_poweron=good_battery androidbo
(bootloader) ot.carrier=O2-DE and
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=fat
(bootloader) aARM_Partion[A].name=extra
(bootloader) aARM_Partion.name=reserve
(bootloader) aARM_Partion[C].name=radio
(bootloader) aARM_Partion[D].name=adsp
(bootloader) aARM_Partion[E].name=dsps
(bootloader) aARM_Partion[F].name=wcnss
(bootloader) aARM_Partion[10].name=radio_config
(bootloader) aARM_Partion[11].name=modem_st1
(bootloader) aARM_Partion[12].name=modem_st2
(bootloader) aARM_Partion[13].name=reserve
(bootloader) partition number=20
(bootloader) Valid partition num=20
(bootloader) setting_get_bootmode() = 9
(bootloader) ram size = 0
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90005000 (phy 90005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
(bootloader) Start Verify: 3
(bootloader) jump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:11787 msec
FAILED (status read failed (Too many links))
finished. total time: 6.224s
C:\androidSDK\sdk\platform-tools>adb push soffbin3 /data/local/tmp/
579 KB/s (4751 bytes in 0.008s)
C:\androidSDK\sdk\platform-tools>adb shell chmod 744 /data/local/tmp/soffbin3
C:\androidSDK\sdk\platform-tools>adb shell su -c "/data/local/tmp/soffbin3"
C:\androidSDK\sdk\platform-tools>adb reboot bootloader
C:\androidSDK\sdk\platform-tools>
Click to expand...
Click to collapse
It all looks like it's going through fine, some people have reported it taking a few tries for it to stick though.
Sent from my Evita
timmaaa said:
It all looks like it's going through fine, some people have reported it taking a few tries for it to stick though.
Sent from my Evita
Click to expand...
Click to collapse
I tried again. Now I'm getting "99 unknown fail"
What I did was to unplug at the black HTC screen after I got the error 99 and power off and started over. That was the only way I could update the firmware.
Sent from my HTC One XL using XDA Premium 4 mobile app
nickfury27 said:
I tried again. Now I'm getting "99 unknown fail"
Click to expand...
Click to collapse
When you get error 99, simulate a battery pull and start again.
Sent from my Evita
nickfury27 said:
I tried again. Now I'm getting "99 unknown fail"
Click to expand...
Click to collapse
When it originally failed did you flash again after it said failed flush image again immediately?
Sent from my HTC One XL using xda app-developers app
nickfury27 said:
I tried again. Now I'm getting "99 unknown fail"
Click to expand...
Click to collapse
I actually got that many times doing it on mine. when that came up i RUUd and tried again. got the first error then pushed it again and got it.
I think this is what happened to me. Read somewhere to wipe the cache a few times. Finally, finally it worked. Maybe for you too.
Sent from my One X using xda app-developers app
I've tried it a million times and I still can't get S-off. What am I suppose to do??
Are your subsequent attempts giving you error 92 or error 99 when flashing the zip?
Sent from my Evita
timmaaa said:
Are your subsequent attempts giving you error 92 or error 99 when flashing the zip?
Sent from my Evita
Click to expand...
Click to collapse
First it gives error 92. And every attempt after that gives error 99. I have to simulate a battery pull to get 92 again.
You've definitely extracted the soffbin zip into your fastboot folder? What ROM are you running while attempting it?
Sent from my Evita
timmaaa said:
You've definitely extracted the soffbin zip into your fastboot folder? What ROM are you running while attempting it?
Sent from my Evita
Click to expand...
Click to collapse
Yes, I extracted soffbin. And I'm using Cyanoges Mod 10.2 Nightly.
You have given root access to adb in developer options?
You could try flashing a Sense ROM purely for this exercise, some people have claimed it works better on Sense. But for the record, I've gotten s-off on two devices, one on Sense and the other on aosp.
Sent from my Evita
timmaaa said:
You have given root access to adb in developer options?
You could try flashing a Sense ROM purely for this exercise, some people have claimed it works better on Sense. But for the record, I've gotten s-off on two devices, one on Sense and the other on aosp.
Sent from my Evita
Click to expand...
Click to collapse
Holy **** it worked! I've given root access to adb and that did it. I've been going crazy over this for a week. Thank you!
Glad to see you got it done.
Sent from my Evita
nickfury27 said:
Holy **** it worked! I've given root access to adb and that did it. I've been going crazy over this for a week. Thank you!
Click to expand...
Click to collapse
Can you write here for me how you did it in detail, please?
Amanbekov said:
Can you write here for me how you did it in detail, please?
Click to expand...
Click to collapse
Here is a detailed guide on how to get S-off. >>> http://forum.xda-developers.com/showthread.php?t=2155071
My problem was that I didn't enable the root access for ADB at developer options so at the last step I didn't grant root access. After enabling root access for ADB it asked for root rights at the last step and that did it.
nickfury27 said:
Here is a detailed guide on how to get S-off. >>> http://forum.xda-developers.com/showthread.php?t=2155071
My problem was that I didn't enable the root access for ADB at developer options so at the last step I didn't grant root access. After enabling root access for ADB it asked for root rights at the last step and that did it.
Click to expand...
Click to collapse
Many thanks to you, my friend! Unfortunately, I was bricked my AT&T HTC One X before I did all of that things and it can't load to Android, but it can load only in bootloader and in TWRP recovery, so I can't to do anything else with my brick =)) So, thank you very mach again and I'm sorry for my English! =)
That's not a brick if you can get to bootloader and recovery. Just flash a ROM.
Sent from my Evita
Related
I give up. I have a AT&T HTC ONE X and im rooted unlocked bootloader and superCID 111111111 and I tried to get S-Off but i get a file not found error. I want to change my cid back to the original att cid so i can run a 3.18 ruu. I heard running a 3.18 ruu with s-ON and superCID will Hard Brick your phone. How can i go back to normal before I tampered anything.
----TAMPERED----
----UNLOCKED----
HBOOT 2.14
Version 3.18
S-ON
CID 1111111
Which part of the s-off process gives you the file not found error?
Sent from my Evita
The very end where you put in the chmod command for soffbin3 it says can't chmod file or directory doesn't exsist. But when I use es file explorer to look in /Data/local/tmp the soffbin3 file is there
Sent from my HTC One X using xda app-developers app
BloatedDuck404 said:
The very end where you put in the chmod command for soffbin3 it says can't chmod file or directory doesn't exsist. But when I use es file explorer to look in /Data/local/tmp the soffbin3 file is there
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Soffbin has to go in your fastboot/adb folder. That's why it's not found
Sent from my HTC One XL using xda premium
BloatedDuck404 said:
The very end where you put in the chmod command for soffbin3 it says can't chmod file or directory doesn't exsist. But when I use es file explorer to look in /Data/local/tmp the soffbin3 file is there
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Did you extract the zip before putting it into the adb folder?
Sent from my Evita
wrong folder??? I just copied and paste the commands into command prompt. Ill try moving the zip
******EDIT*******There is not fastboot adb folder on the phone.----- Oh the computer. No I did not unzip. Ill try to unzip
You didn't follow the instructions properly then. Read it carefully, and follow the instructions precisely.
Sent from my Evita
BloatedDuck404 said:
wrong folder??? I just copied and paste the commands into command prompt. Ill try moving the zip
******EDIT*******There is not fastboot adb folder on the phone.----- Oh the computer. No I did not unzip. Ill try to unzip
Click to expand...
Click to collapse
Feel like an idiot but now Operation is not permitted.
Can you copy and paste the lines from the command prompt in here? It'll give us a better idea of what's going on.
Sent from my Evita
---------- Post added at 12:00 AM ---------- Previous post was at 12:00 AM ----------
Also, do you have adb debugging enabled in developer options?
Sent from my Evita
http://forum.xda-developers.com/showthread.php?p=33189590
This should help you.
Sent from my HTC One X using xda premium
BTW now error 99 if I retry from scratch
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.093s]
finished. total time: 0.097s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip PJ8312000-One
X.zip
sending 'zip' (36064 KB)...
OKAY [ 2.590s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.858s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem boot
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F50C4
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD04
(bootloader) TAG:hero panel = 0x4940047
(bootloader) TAG:engineerid = 0x1
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is CWS__001
(bootloader) setting->cid::CWS__001
(bootloader) serial number: HT2ACW300425
(bootloader) command line length =719
(bootloader) active commandline: reset_status=0 board_elite.disable_uart3
(bootloader) =0 diag.enabled=0 board_elite.debug_uart=0 userdata_sel=0 an
(bootloader) droidboot.emmc=true androidboot.pagesize=2048 skuid=0 ddt=20
(bootloader) ats=0 androidboot.lb=1 td.sf=1 td.td=1 td.ofs=328 td.prd=1
(bootloader) td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=694 imc_online_log=
(bootloader) 0 androidboot.efuse_info=FFSL androidboot.baseband=0.24p.32
(bootloader) .09.06 androidboot.cid=CWS__001 androidboot.devicerev=3 andr
(bootloader) oidboot.batt_poweron=good_battery androidboot.carrier=ATT an
(bootloader) droidboot.mid=PJ8310
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=fat
(bootloader) aARM_Partion[A].name=extra
(bootloader) aARM_Partion.name=reserve
(bootloader) aARM_Partion[C].name=radio
(bootloader) aARM_Partion[D].name=adsp
(bootloader) aARM_Partion[E].name=dsps
(bootloader) aARM_Partion[F].name=wcnss
(bootloader) aARM_Partion[10].name=radio_config
(bootloader) aARM_Partion[11].name=modem_st1
(bootloader) aARM_Partion[12].name=modem_st2
(bootloader) aARM_Partion[13].name=reserve
(bootloader) partition number=20
(bootloader) Valid partition num=20
(bootloader) setting_get_bootmode() = 9
(bootloader) ram size = 0
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90005000 (phy 90005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
(bootloader) Start Verify: 3
(bootloader) jump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:635526 msec
FAILED (status read failed (Too many links))
finished. total time: 6.420s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell chmod 744 /data/local/
tmp/soffbin3
Unable to chmod /data/local/tmp/soffbin3: Operation not permitted
Have a look on page 17 (I think) of the s-off thread, there is a fix for the error 99 problem posted by Chongodroid.
Sent from my Evita
kool im downloading viperXL 3.2.7 and ill follow his steps. Htc is so confusing but I love there devices. So risky. I cant thank you enough for taking time out of your day to help me
It's no problem at all. Let us know how it all goes.
Sent from my Evita
No go but I flashed a rom and got over my fear to do that. You know I got error 92 like it was suppose to do but since I did not unzip I couldnt proceed. BUT when I unzipped it and started over I got error 99. I want s-off so I can get rid of that red text (I see now that I flashed a rom),tampered, if I ever need to ruu withe superCID since im on 3.18 and ya know s-off stuff. But I guess my phone doesn't what to s-off. This is my first HTC android phone and Its been a scary ride. Thanks for your help anyway it was greatly appreciated. If ya got anymore suggestions ill try em. I stay with viper rom ATM.
Did you let viper boot after flashing? Or did you boot to the bootloader after flashing?
Sent from my Evita
No I rebooted to the bootloader. Didn't even let viper boot at all.
Sent from my HTC One X using xda app-developers app
And you still got error 99? Another trick to try after getting error 99 is to simulate a battery pull and start again.
To simulate a battery pull on this phone, hold power and volume down keys at the same time, the cap lights will start flashing, when the screen goes blank you can let go of the power key but keep holding volume down until it boots into the bootloader. Then start the s-off process again.
Sent from my Evita
OMFG YOU ARE THE BOMB IT WORKED!!!! Thanks for your help thanks soooooo much.
Awesome :thumbup:
Glad I could help
Sent from my Evita
Hi guys....I'm just wondering if you guys know where I can find good htc one xl driver.....seem like my laptop sometime recognized the usb connection and automatic install the driver and sometime not......especially when I tried to do S-OFF.....right before entering 3 soffbin3 command after Android boot to OS......I always got error device not found after......usb debugging is checked before and unchecked after boot to Android OS.....and I read somewhere on thread that Android 4.2.2 for security purpose htc uncheck USB debugging after boot .....and then I went back to Android 4.0.3 sense 4 and same result....and I'm thinking is the driver might not installed properly......so any link and idea would appreciated......btw using window 7
C:\Android\android-sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android\android-sdk\platform-tools>fastoot oem readcid
'fastoot' is not recognized as an internal or external command,
operable program or batch file.
C:\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.006s]
finished. total time: 0.007s
C:\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.064s]
finished. total time: 0.065s
C:\Android\android-sdk\platform-tools>fastboot flash zip PJ8312000-OneX.zip
sending 'zip' (36064 KB)...
OKAY [ 2.744s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.841s
C:\Android\android-sdk\platform-tools>fastboot oem boot
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F6C9C
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD04
(bootloader) TAG:hero panel = 0x940047
(bootloader) TAG:engineerid = 0x1
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT24DWXXXXXX
(bootloader) command line length =688
(bootloader) active commandline: poweron_status=32 reset_status=0 board_e
(bootloader) lite.disable_uart3=0 diag.enabled=0 board_elite.debug_uart=0
(bootloader) userdata_sel=0 androidboot.emmc=true androidboot.pagesize=2
(bootloader) 048 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.sf=1 t
(bootloader) d.ofs=328 td.prd=1 td.dly=0 td.tmo=300 imc_online_log=0 and
(bootloader) roidboot.efuse_info=FFSL androidboot.baseband=0.18c.32.09.01
(bootloader) androidboot.cid=11111111 androidboot.devicerev=3 androidboo
(bootloader) t.batt_poweron=good_battery androidboot.carrier=ALL androidb
(bootloader) oot.mid=PJ8310000 androidboot.keycaps=qwerty androidboot.dq=
(bootloader) FAIL androidboot.mode=normal androidboot.serialno=HTXXXXXX
(bootloader) 93 androidboot.bootloader=1.09.0000 androidboot.nledhw=0 zyg
(bootloader) ote_oneshot=off kmemleak=off rpm_debug.enable=0
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=fat
(bootloader) aARM_Partion[A].name=extra
(bootloader) aARM_Partion.name=radio
(bootloader) aARM_Partion[C].name=adsp
(bootloader) aARM_Partion[D].name=dsps
(bootloader) aARM_Partion[E].name=wcnss
(bootloader) aARM_Partion[F].name=radio_config
(bootloader) aARM_Partion[10].name=modem_st1
(bootloader) aARM_Partion[11].name=modem_st2
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90006000 (phy 90006000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
(bootloader) jump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:11377 msec
FAILED (status read failed (Too many links))
finished. total time: 6.387s
C:\Android\android-sdk\platform-tools>adb push soffbin3 /data/local/tmp/
error: device not found
C:\Android\android-sdk\platform-tools>adb push soffbin3 /data/local/tmp/
error: device not found
Swyped From BlueICESense_JBE
The best way to get the latest drivers is to download the latest HTC Sync Manager from the HTC One XL page at HTC.com
Sent from my Evita
timmaaa said:
The best way to get the latest drivers is to download the latest HTC Sync Manager from the HTC One XL page at HTC.com
Sent from my Evita
Click to expand...
Click to collapse
I did that....And updated my htc driver installer from version 3 to version 4 or something.....do I need to keep htc sync manager or uninstall it after that?
Swyped From BlueICESense_JBE
Uninstall Sync Manger but leave drivers installed.
Sent from my Evita
timmaaa said:
Uninstall Sync Manger but leave drivers installed.
Sent from my Evita
Click to expand...
Click to collapse
I did that......same result.....error device not found......I just dunno what else to do.........btw.....I'm fine without S-OFF for now.... since I'm still on older hboot 1.09 and don't have reboot, wifi or signal what so ever on Android 4.2.2 sense 5 base ROM...... but would be awesome with S-OFF to complete mod.......
Swyped From BlueICESense_JBE
Use a different computer
Sent from my VENOMized HoxL
area51avenger said:
Use a different computer
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Did that too....using my wife laptop...my son laptop.....
Swyped From BlueICESense_JBE
Maybe it's a case of needing to download the latest Android SDK to ensure your adb is fully up to date. Or it could be as simple as using the rear usb port on your pc as opposed to the front usb port (may sound silly but it's worked for many people).
Sent from my Evita
timmaaa said:
Maybe it's a case of needing to download the latest Android SDK to ensure your adb is fully up to date. Or it could be as simple as using the rear usb port on your pc as opposed to the front usb port (may sound silly but it's worked for many people).
Sent from my Evita
Click to expand...
Click to collapse
Felt like something easy fix......like u said but I just dunno what else to do and I don't have PC......and i tried all four usb port from my laptop.....might have to use my brother PC but I dunno if he have all the Android sdk tool etc.....but I will try to update adb version via sdk manager tonight......:thumbup: Do you think twrp 2.6.3.0 have to do with it? But it work just fine for me flashing ROM, restoring back up...back and forth sense 4 and sense 5 Rom.....
Swyped From BlueICESense_JBE
I don't think the version of TWRP you're running matters, it doesn't come into the s-off process at all.
Sent from my Evita
timmaaa said:
I don't think the version of TWRP you're running matters, it doesn't come into the s-off process at all.
Sent from my Evita
Click to expand...
Click to collapse
Seem to me like.....somewhere inside there a script that somehow killed USB debugging .....after reboot
Swyped From BlueICESense_JBE
You need to check usb debugging in developer settings after the phone boots as I've instructed before, are you doing that?
Sent from my Evita
timmaaa said:
You need to check usb debugging in developer settings after the phone boots as I've instructed before, are you doing that?
Sent from my Evita
Click to expand...
Click to collapse
Yes and keep unchecked everytime after I got failed 92.....before pushing soffbin3 command.....and I did check it again and everytime.....that's y make me think somehow or sometime during booting to Android after failed 92 .....there is a script or command in my phone to uncheck USB debugging......but I doubt it ......just some thought
Swyped From BlueICESense_JBE
I don't that's the case, even if it did disable it on boot you can enable it once the phone boots.
Sent from my Evita
timmaaa said:
I don't that's the case, even if it did disable it on boot you can enable it once the phone boots.
Sent from my Evita
Click to expand...
Click to collapse
I did check it again after booted up.....and then when i enter first command adb push soffbin3 /data/local/tmp/ ........it said error....device not found and then i forced the phone coz im stuck on black htc screen using power button combo....sometime brought me back to bootloader.....and i started with second command from the beginning again .......fastboot oem rebootRUU but when the phone booted up to OS.....i used first command adb reboot bootloader but after that always same error device not found.....
Maybe you need to try another ROM.
Sent from my Evita
Solved.....s-off now
timmaaa said:
Maybe you need to try another ROM.
Sent from my Evita
Click to expand...
Click to collapse
SOLVED.....awesome....i figured it out.....:
1. Make sure to use android ICS ROM base coz JELLY BEAN base rom has a security feature that killed usb debugging during or after booting.
2. Check your android ADB version make sure 1.0.31 from cmd prompt navigate to your adb folder by pressing shift+right click and open cdm
3. Make sure u have all the htc driver install by installing htc sync manager ...it will update your htc driver installer and make sure to uninstall htc sync manager after that....just leave htc driver installer on your computer.
AWESOME....VERY APPRECIATED TIME AND HELP U GUYS GIVEN
Myrder said:
With the new 4.2.2 Android version ADB has a security feature that has to be authenticated on the users screen before the phone can be accessed.
You also need to check your ADB version: 1.0.29 or 1.0.31?
1.0.29 - Will not see your device/gives a "device offline" output.
1.0.31 - Will give a prompt on your device asking for authentication. This is the one you want.
To check your ADB version, nav to your ADB folder in cmd prompt and type "adb version" no quotes.
If it gives you 1.0.29, you need to update using your SDK manager.
To do this you need to nav to your /tools folder in your SDK folder. Here you will type "android" no quotes. Then follow the upgrade process.
Click to expand...
Click to collapse
Hmm, that's interesting. I've gotten s-off on two devices while on Jellybean. But at least you finally got it working.
Sent from my Evita
timmaaa said:
Hmm, that's interesting. I've gotten s-off on two devices while on Jellybean. But at least you finally got it working.
Sent from my Evita
Click to expand...
Click to collapse
Weird huh.....but like people said every phone is different...that's just what i did to my phone incase this might be useful for other xda member.....Just do alot of reading....and u might cross path with other people problem........READ....READ....AND READ.....:good: BTW TIM.....very appreciated for ur time.....i'm all out thanks....for today....more come to u tomorrow and other that help me.....
Myrder said:
With the new 4.2.2 Android version ADB has a security feature that has to be authenticated on the users screen before the phone can be accessed.
You also need to check your ADB version: 1.0.29 or 1.0.31?
1.0.29 - Will not see your device/gives a "device offline" output.
1.0.31 - Will give a prompt on your device asking for authentication. This is the one you want.
To check your ADB version, nav to your ADB folder in cmd prompt and type "adb version" no quotes.
If it gives you 1.0.29, you need to update using your SDK manager.
To do this you need to nav to your /tools folder in your SDK folder. Here you will type "android" no quotes. Then follow the upgrade process.
Click to expand...
Click to collapse
No problems mate, I'm just glad it finally worked for you.
Sent from my Evita
I am new to this HTC version of rooting and installing custom recovery on phones. I previously did this to my Galaxy S3 and it all worked fine. I wanted to make sure i am following the correct instructions to root and be able to install cyanogenmod on my one x. I currently have the android version 4.0.4. Please let me know if all the links i have are correct. Really appreciate the help guys!!
1. Root the HTC one X
[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit link
2. Install SuperCID
[TOOL] OneClick SuperCID for Unlocking Bootloader link
3. S-OFF
[S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA link
4. Install TWRP http://forum.xda-developers.com/showthread.php?t=1677447
5. Follow the ROM installation procedure
Thanks...
hari04415 said:
I am new to this HTC version of rooting and installing custom recovery on phones. I previously did this to my Galaxy S3 and it all worked fine. I wanted to make sure i am following the correct instructions to root and be able to install cyanogenmod on my one x. I currently have the android version 4.0.4. Please let me know if all the links i have are correct. Really appreciate the help guys!!
1. Root the HTC one X
[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit link
2. Install SuperCID
[TOOL] OneClick SuperCID for Unlocking Bootloader link
3. S-OFF
[S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA link
4. Install TWRP http://forum.xda-developers.com/showthread.php?t=1677447
5. Follow the ROM installation procedure
Thanks...
Click to expand...
Click to collapse
Good steps but after s-off you should run the 3.18 ruu. Then flash twrp and your choosen rom.
DvineLord said:
Good steps but after s-off you should run the 3.18 ruu. Then flash twrp and your choosen rom.
Click to expand...
Click to collapse
Could you tell me how to install 3.18 RUU...any link would be much appreciated..thanks
Just download the 3.18 RUU, connect your phone to the PC in fastboot mode and run the RUU exe program. Just make sure you don't have HTC Sync Manager installed, make sure no other programs are running, and make sure screen saver/hibernation is turned off. You must have s-off before you run the RUU though.
Sent from my Evita
Thanks i will try it now!
Would I have to relock the boot loader before running the ruu? Fastboot OEM lock??
Sent from my HTC One XL using XDA Premium 4 mobile app
No, as long as you get s-off first you don't need to relock the bootloader.
Sent from my Evita
timmaaa said:
No, as long as you get s-off first you don't need to relock the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
timmaaa, I am using a mac and i am in processing of finishing root method from the step 1 i posted earlier. I got the unlock_code.bin from htcdev but not sure what to do now. Do i go to terminal and use the fastboot from there or do i have to use the super CID link to unlock the bootloader?
You just need to follow the instructions at the htcdev, it's outlined pretty specifically.
Sent from my Evita
timmaaa said:
You just need to follow the instructions at the htcdev, it's outlined pretty specifically.
Sent from my Evita
Click to expand...
Click to collapse
I followed the step 1 correctly. Now in bootloader it says unlocked but when i try to run SuperCID it doesnt work. Tried both on mac and windows.
The 2.20 root exploit should give you SuperCID in order to unlock the bootloader. What does it say when you give the following command?
Code:
fastboot oem readcid
Sent from my Evita
timmaaa said:
The 2.20 root exploit should give you SuperCID in order to unlock the bootloader. What does it say when you give the following command?
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
it says 1111111
I have installed the SuperSU and repeated the procedure. This time around i was able to finish the procedure but i still have S-ON. Please help me get the S-OFF
Here is my cmd prompt
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
HT28SW301846 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip PJ8312000-One
X.zip
sending 'zip' (36064 KB)...
OKAY [ 2.652s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.753s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem boot
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F9E3C
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD04
(bootloader) TAG:hero panel = 0x4940047
(bootloader) TAG:engineerid = 0x1
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is CWS__001
(bootloader) setting->cid::CWS__001
(bootloader) serial number: HT28SW301846
(bootloader) commandline from head: console=ttyHSL0,115200,n8
(bootloader) command line length =699
(bootloader) active commandline: reset_status=0 board_elite.disable_uart3
(bootloader) =0 diag.enabled=0 board_elite.debug_uart=0 userdata_sel=0 an
(bootloader) droidboot.emmc=true androidboot.pagesize=2048 skuid=0 ddt=20
(bootloader) ats=0 androidboot.lb=1 td.td=1 td.sf=1 td.ofs=328 td.prd=1
(bootloader) td.dly=0 td.tmo=300 imc_online_log=0 androidboot.efuse_inf
(bootloader) o=FFSL androidboot.baseband=0.19as.32.09.11_2 androidboot.ci
(bootloader) d=CWS__001 androidboot.devicerev=3 androidboot.batt_poweron=
(bootloader) good_battery androidboot.carrier=ATT androidboot.mid=PJ83100
(bootloader) 00 androidboot.keyca
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=fat
(bootloader) aARM_Partion[A].name=extra
(bootloader) aARM_Partion.name=radio
(bootloader) aARM_Partion[C].name=adsp
(bootloader) aARM_Partion[D].name=dsps
(bootloader) aARM_Partion[E].name=wcnss
(bootloader) aARM_Partion[F].name=radio_config
(bootloader) aARM_Partion[10].name=modem_st1
(bootloader) aARM_Partion[11].name=modem_st2
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90005000 (phy 90005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
(bootloader) jump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:15253 msec
FAILED (status read failed (Too many links))
finished. total time: 7.362s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push soffbin3 /data/local/tm
p/
356 KB/s (4751 bytes in 0.012s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell chmod 744 /data/local/
tmp/soffbin3
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell su -c "/data/local/tmp
/soffbin3"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>
You need to stop posting the same thing in multiple places, duplicating posts is against the rules. I've answered you in the other thread.
Sent from my Evita
Hello, I actually have a T-Mobile version of the HTC One m8 but that community seems dead and I haven't been able to find help to my problem. I am kind of getting desperate so I will tell you what I know. I have done my best to search for solutions and I feel as though I have exhausted almost every possible work around so that is why I look to you guys for help.
***Software status: Modified ***
***UNLOCKED***
MS_UL PVT SHIP S-ON
RADIO-1.22.213311491.08G
version-bootloader: 3.19.0.0000
version-main: (blank)
product: m8_ul
modelide: 0P6B13000
cidnum: T-MOB010
The issue is that the phone is in a boot loop status with an unresponsive operating system. Essentially, I cannot successfully maneuver around the file system and adjust/change settings because it is laggy/slow/unresponsive. Someone suggested to me that I flash an RUU but all attempts have failed. I cannot "re-lock" my bootloader either. When I try to do so I get the following error:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.232s
I could care less about loss of data (in fact I have everything backed up) but I just want my phone to work again either rooted/unrooted, locked/unlocked, or otherwise. Any willingness to help would be reciprocated with immense gratitude. Thank you for the time and consideration.
Pretty sure I can help you. Send me a pm I'll help u.
Look here:::> http://forum.xda-developers.com/showthread.php?t=3078889
Sent from my One M8 using XDA Premium 4 mobile app
My power button quit working, I'm within the 1 year warranty period, and I need to go back to stock after I get my replacement.
Before I call VZW, since I'm rooted and using nV ROM, and I know they ask about the Software, does anyone have a screen shot of the Stock Software screen, Kit Kat unless LP has been pushed?
Thanks!
Sent from my HTC6525LVW using XDA Premium 4 mobile app
EvoNotion said:
My power button quit working, I'm within the 1 year warranty period, and I need to go back to stock after I get my replacement.
Before I call VZW, since I'm rooted and using nV ROM, and I know they ask about the Software, does anyone have a screen shot of the Stock Software screen, Kit Kat unless LP has been pushed?
Thanks!
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
They can see more information than you can tell them. Best bet is to be stock during that call.
Thanks for that input.
So, since the new phone arrived, I've been trying to restore my old phone to stock, S-OF, Unroot and Locked boot loader, etc.
I'm able to ADB into fastboot, however for whatever reason I cannot load the 06BIMG.zip(not at my computer)
Fastboot simply reboots immediately when I adb reboot boatloader.
Is there another way to get a stock image on the phone, remove the red text at boot up, s-off, lock boot loader with stock recovery and unroot?
Everything I've tried seems to be hinged on that fastboot rebooting issue.
Thanks
Sent from my HTC6525LVW using XDA Premium 4 mobile app
EvoNotion said:
Thanks for that input.
So, since the new phone arrived, I've been trying to restore my old phone to stock, S-OF, Unroot and Locked boot loader, etc.
I'm able to ADB into fastboot, however for whatever reason I cannot load the 06BIMG.zip(not at my computer)
Fastboot simply reboots immediately when I adb reboot boatloader.
Is there another way to get a stock image on the phone, remove the red text at boot up, s-off, lock boot loader with stock recovery and unroot?
Everything I've tried seems to be hinged on that fastboot rebooting issue.
Thanks
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
0P6BIMG.zip ?
I typed it from my phone whilst I was enjoying the evening outside. Just the only numbers in my head.
I'm downloading your RUU exe right now Dottat. Didn't realize you're local by an hour to me.
thanks!
dottat said:
0P6BIMG.zip ?
Click to expand...
Click to collapse
So I downloaded your EXE, and I get a failure in regard that it reboots to the HTC logo and the phone reboots immediately, causing the program to fail.
Error 155: unknown error
This is the same problem i was having when trying to do the fastboot push of the RUU I had downloaded previously.
Image version is 1.54.401.10
What ever can i do?
EvoNotion said:
So I downloaded your EXE, and I get a failure in regard that it reboots to the HTC logo and the phone reboots immediately, causing the program to fail.
This is the same problem i was having when trying to do the fastboot push of the RUU I had downloaded previously.
Image version is 1.54.401.10
What ever can i do?
Click to expand...
Click to collapse
Try flashing official stock vzw firmware via SD card. Are your mid and cid stock?
401 isn't vzw firmware BTW
dottat said:
0P6BIMG.zip ?
Click to expand...
Click to collapse
dottat said:
Try flashing official stock vzw firmware via SD card. Are your mid and cid stock?
401 isn't vzw firmware BTW
Click to expand...
Click to collapse
I just remember last year downloading and installing the nV Rom which was 4.4.2. and updating the radios.
I've tried the 0p6bimg.zip method in fastboot, but it fails as well. Maybe I'm doing it wrong, but it's in the root of the SD card.
EvoNotion said:
I just remember last year downloading and installing the nV Rom which was 4.4.2. and updating the radios.
I've tried the 0p6bimg.zip method in fastboot, but it fails as well. Maybe I'm doing it wrong, but it's in the root of the SD card.
Click to expand...
Click to collapse
I can do a team viewer session with you this weekend to take a look with you if you want
dottat said:
I can do a team viewer session with you this weekend to take a look with you if you want
Click to expand...
Click to collapse
That would be tits man. I'll be in Dover tomorrow night if you want to check it out live....LMK
EvoNotion said:
That would be tits man. I'll be in Dover tomorrow night if you want to check it out live....LMK
Click to expand...
Click to collapse
Depends on what time...lol. I work in Lancaster during the week a lot.
dottat said:
Depends on what time...lol. I work in Lancaster during the week a lot.
Click to expand...
Click to collapse
You tell me, I'll probably get out of work around 3pm and head down to York. I have to pick up tools from a friend that's borrowing them for work around 5/530, so whenever.
Since the PWR buttons not working, I'm not able to select HBOOT at the bootloader screen, and the commands I was using to get the HTC black screen fail to push. However, I just renamed your ZIP file and will try again and report back
EvoNotion said:
You tell me, I'll probably get out of work around 3pm and head down to York. I have to pick up tools from a friend that's borrowing them for work around 5/530, so whenever.
Since the PWR buttons not working, I'm not able to select HBOOT at the bootloader screen, and the commands I was using to get the HTC black screen fail to push. However, I just renamed your ZIP file and will try again and report back
Click to expand...
Click to collapse
BTW...from a booted ROM the command adb reboot oem-78
Will land you in ruu mode.
dottat said:
BTW...from a booted ROM the command adb reboot oem-78
Will land you in ruu mode.
Click to expand...
Click to collapse
well now, learn something new everyday. Got me to the HTC screen, and then it rebooted though.
EvoNotion said:
well now, learn something new everyday. Got me to the HTC screen, and then it rebooted though.
Click to expand...
Click to collapse
Can you adb reboot-bootloader and get a fastboot getvar all.
X out your imei and sn
dottat said:
Can you adb reboot-bootloader and get a fastboot getvar all.
X out your imei and sn
Click to expand...
Click to collapse
C:\Users\Abraham\Documents>adb kill-server
C:\Users\Abraham\Documents>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Abraham\Documents>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.027s]
finished. total time: 0.037s
C:\Users\Abraham\Documents>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1726320 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 8.723s
C:\Users\Abraham\Documents>adb reboot bootloader
C:\Users\Abraham\Documents>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 99000429333087
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.141s
C:\Users\Abraham\Documents>
EvoNotion said:
C:\Users\Abraham\Documents>adb kill-server
C:\Users\Abraham\Documents>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Abraham\Documents>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.027s]
finished. total time: 0.037s
C:\Users\Abraham\Documents>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1726320 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 8.723s
C:\Users\Abraham\Documents>adb reboot bootloader
C:\Users\Abraham\Documents>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 99000429333087
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.141s
C:\Users\Abraham\Documents>
Click to expand...
Click to collapse
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898
dottat said:
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898
Click to expand...
Click to collapse
Should I rename it to something?
EvoNotion said:
Should I rename it to something?
Click to expand...
Click to collapse
Should not need to
dottat said:
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898
Click to expand...
Click to collapse
Got half way through and now I'm at the four exclamation marks on the corners