Related
[Q&A] [ROM] InsertCoin 3.0.6 for DLXUB1 | Android 4.4.2 | HTC Sense 6 | | IC PerApp
Q&A for [ROM] InsertCoin 3.0.6 for DLXUB1 | Android 4.4.2 | HTC Sense 6 | | IC PerApp Theme
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] InsertCoin 3.0.6 for DLXUB1 | Android 4.4.2 | HTC Sense 6 | | IC PerApp Theme. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Stuck on Boot screen while trying to flash [ROM] InsertCoin 3.0.6 for DLXUB1 | Androi
Hi,
I tried to flash the [ROM] InsertCoin 3.0.6 for DLXUB1 | Android 4.4.2 | HTC Sense 6 | | IC PerApp Theme and got stuck on the boot screen.
I have TWRP 2.5 installed, Hboot 1.41.0000 and bootloader unlocked.
I simply went into recovery and installed the zip file.
Please help. It is much needed and appreciated.
Capt Vikram Sandhu said:
Hi,
I tried to flash the [ROM] InsertCoin 3.0.6 for DLXUB1 | Android 4.4.2 | HTC Sense 6 | | IC PerApp Theme and got stuck on the boot screen.
I have TWRP 2.5 installed, Hboot 1.41.0000 and bootloader unlocked.
I simply went into recovery and installed the zip file.
Please help. It is much needed and appreciated.
Click to expand...
Click to collapse
Might be because you did not use this TWRP Made by Kairi.
Thanks a ton sir. The room had been flashed and I'm living it.?
Sent from my HTC Butterfly using XDA Free mobile app
Hi,
How to S-Off my devices now. Its HTC x920d, CID: HTC_038, Rooted and other info as attached thumbnails.
Your advice is needed and much appreciated.
Capt Vikram Sandhu said:
Hi,
How to S-Off my devices now. Its HTC x920d, CID: HTC_038, Rooted and other info as attached thumbnails.
Your advice is needed and much appreciated.
Click to expand...
Click to collapse
I personally used Rumrunner to do my S-OFF. Perhaps did you enable usb debugging in developer options?
xunus said:
I personally used Rumrunner to do my S-OFF. Perhaps did you enable usb debugging in developer options?
Click to expand...
Click to collapse
Dear Xunus,
Yes I had the debugging mode on and fastboot off in the dev. options & power settings respectively. Also I don't have HTC Sync. Set up my ASUS ROG G750JMhttp://www.asus.com/in/Notebooks_Ultrabooks/ASUS_ROG_G750JM/according to this guide - http://forum.xda-developers.com/showthread.php?t=2256359 for device recognition in adb/fastboot mode after completly setting up JDK (& enviorment fully with path setting in system enviornment) and Android SDK as per this link - http://developer.android.com/sdk/index.html
But I'm in a thicker soup now. (in between my query and your reply).
Actually this device was initially my first x920d HTC_038.
On this intial device I was S-on, unlocked, maybe rooted or rooted then unrooted ( bootloader displayed *** TAMPERED *** ***UNLOCKED*** ,S-On, Hboot 1.41.00 - if required i can post the image) & definitely had a custom rom installed on it & TWRP 2.5 (don't remember which custom rom {somewhere around Android JB initial versions & subsequently upgraded to JB 4.2, but was not able to update to 4.3});
Last week I came across InsertCoin Kitkat Roms and tried to upgrade by flashing TWRP 2.8 & then flashing the zip through recovery TWRP 2.8 and got stuck at boot screen. You were kind enough to help me out - http://forum.xda-developers.com/showpost.php?p=56987280&postcount=3
Then I flashed Kairi's Twrp and flashed Insert Coin 3.0.6. Then rooted by flashing 'UPDATE-SuperSU-v2.02.zip'. My device info after this was as - http://forum.xda-developers.com/showpost.php?p=57107853&postcount=5
Then I tried to s-off through rumrunner 0.5.xx following this guide - http://rumrunner.us/instructions/ but it never finished - (attached image). Then I relocked the bootloader by fastboot oem lock command in fastboot mode. It did relock my bootloader, then i retried rumrunner through fastboot, but it came up with this - 'attached image 1'. Nnow I'm stuck with relocked bootloader, rooted device running insert coin 3.0.6, cannot boot into recovery, cannot flash PL99IMG.img/TWRP 2.7 Kairi (attached images). But my fastboot/adb is fully up and the IC rom is running good.
Kindly try to help me if you get some time.
Also I want to contribute (though am not able to contribute financially at the moment) to our forum , but sure can commit/devote minimum 6 to 10 hours a week for any job the forum/members' want or can be understudee to any member. Just bear in mind that I'm a noobie
I hope+wish to contribute+learn simultaneously to+from our forum.
Thanks.
:good:
Capt Vikram Sandhu said:
Dear Xunus,
Yes I had the debugging mode on and fastboot off in the dev. options & power settings respectively. Also I don't have HTC Sync. Set up my ASUS ROG G750JMhttp://www.asus.com/in/Notebooks_Ultrabooks/ASUS_ROG_G750JM/according to this guide - http://forum.xda-developers.com/showthread.php?t=2256359 for device recognition in adb/fastboot mode after completly setting up JDK (& enviorment fully with path setting in system enviornment) and Android SDK as per this link - http://developer.android.com/sdk/index.html
But I'm in a thicker soup now. (in between my query and your reply).
Actually this device was initially my first x920d HTC_038.
On this intial device I was S-on, unlocked, maybe rooted or rooted then unrooted ( bootloader displayed *** TAMPERED *** ***UNLOCKED*** ,S-On, Hboot 1.41.00 - if required i can post the image) & definitely had a custom rom installed on it & TWRP 2.5 (don't remember which custom rom {somewhere around Android JB initial versions & subsequently upgraded to JB 4.2, but was not able to update to 4.3});
Last week I came across InsertCoin Kitkat Roms and tried to upgrade by flashing TWRP 2.8 & then flashing the zip through recovery TWRP 2.8 and got stuck at boot screen. You were kind enough to help me out - http://forum.xda-developers.com/showpost.php?p=56987280&postcount=3
Then I flashed Kairi's Twrp and flashed Insert Coin 3.0.6. Then rooted by flashing 'UPDATE-SuperSU-v2.02.zip'. My device info after this was as - http://forum.xda-developers.com/showpost.php?p=57107853&postcount=5
Then I tried to s-off through rumrunner 0.5.xx following this guide - http://rumrunner.us/instructions/ but it never finished -http://dl-1.va.us.xda-developers.com/3/0/3/7/9/2/7/Rumrunner_Error.png?key=vEm3NkbgFBSwUpCE1I-SYQ&ts=1417206844 . Then I relocked the bootloader by fastboot oem lock command in fastboot mode. It did relock my bootloader, then i retried rumrunner through fastboot, but it came up with this - 'attached image 1'. Nnow I'm stuck with relocked bootloader, rooted device running insert coin 3.0.6, cannot boot into recovery, cannot flash PL99IMG.img/TWRP 2.7 Kairi (attached images). But my fastboot/adb is fully up and the IC rom is running good.
Kindly try to help me if you get some time.
Also I want to contribute (though am not able to contribute financially at the moment) to our forum , but sure can commit/devote minimum 6 to 10 hours a week for any job the forum/members' want or can be understudee to any member. Just bear in mind that I'm a noobie
I hope+wish to contribute+learn simultaneously to+from our forum.
Thanks.
:good:
Click to expand...
Click to collapse
I'm not really a pro on this stuff, just sharing my experience on the Butterfly. Since your current situation is a Relocked bootloader and unfortunately its still S-ON. The only thing you could do was to unlocked your bootloader again via every possible ways. I did see you tried to unlock with the 1st unlock_code.bin. But it gave you error. How about getting a new Unlock_code from HTC? Hopefully it will work this round. Without a unlocked bootloader there's pretty much nothing else you could do.( Caution: unlocking your bootloader again will wipe your data. Recommended to backup your stuffs if you need them)
If you are able to unlock your bootloader, things to do and try out.
1st: Flash Kairi's 270X twrp
2nd: Flash Kairi's reset kernel (Because its a unsecured stock kernel)
3rd: Turn on usb debug, HTC fast boot turn off
4th: Try rumrunner again.
The real developers for x920d left here in xda would be kairi_zeroblade and xXminiWHOOPERxX. Its only them that can make a change to the X920D xda community.
xunus said:
I'm not really a pro on this stuff, just sharing my experience on the Butterfly. Since your current situation is a Relocked bootloader and unfortunately its still S-ON. The only thing you could do was to unlocked your bootloader again via every possible ways. I did see you tried to unlock with the 1st unlock_code.bin. But it gave you error. How about getting a new Unlock_code from HTC? Hopefully it will work this round. Without a unlocked bootloader there's pretty much nothing else you could do.( Caution: unlocking your bootloader again will wipe your data. Recommended to backup your stuffs if you need them)
If you are able to unlock your bootloader, things to do and try out.
1st: Flash Kairi's 270X twrp
2nd: Flash Kairi's reset kernel (Because its a unsecured stock kernel)
3rd: Turn on usb debug, HTC fast boot turn off
4th: Try rumrunner again.
The real developers for x920d left here in xda would be kairi_zeroblade and xXminiWHOOPERxX. Its only them that can make a change to the X920D xda community.
Click to expand...
Click to collapse
Voila
I have just unlocked again through flashing unlock token.
Actually if you see in the image in my previous post I had erronouslt typed "fastboot unlocktocken Unlock_code.bin". It should had been "fastboot unlocktoken Unlock_code.bin".
The device is setting up for the first time as I type.
Thanks XUNUS.
Now should I follow your the steps you mentioned or first of all change my CID HTC_038 to CID: 11111111 by "fastboot oem writecid 11111111" and then continue to your steps.
Also can you provide me the link to kairi's reset kernel?
I cannot do a "fastboot oem writecid 11111111" as I'm S-On.
meanwhile I've successfully flashed Kairi's TWRP and now am searching for his Reset Kernel.
Capt Vikram Sandhu said:
Voila
I have just unlocked again through flashing unlock token.
Actually if you see in the image in my previous post I had erronouslt typed "fastboot unlocktocken Unlock_code.bin". It should had been "fastboot unlocktoken Unlock_code.bin".
The device is setting up for the first time as I type.
Thanks XUNUS.
Now should I follow your the steps you mentioned or first of all change my CID HTC_038 to CID: 11111111 by "fastboot oem writecid 11111111" and then continue to your steps.
Also can you provide me the link to kairi's reset kernel?
I cannot do a "fastboot oem writecid 11111111" as I'm S-On.
meanwhile I've successfully flashed Kairi's TWRP and now am searching for his Reset Kernel.
Click to expand...
Click to collapse
Oh ya i forgot to add that in Here it is
xunus said:
Oh ya i forgot to add that in Here it is
Click to expand...
Click to collapse
Finally --- SUCCESS in S-Off thru rumrunner (attached thumbnail)
What I did was downgraded to [ROM]|8.15.2013|NOS M7 v3.0.0|(Sense 5.0 JB 4.2.2)Butterfly - http://forum.xda-developers.com/showthread.php?t=2193912
and ran rummrunner. VOILA.
Will definitely share the steps with you in my next post.
Thanks for all your support. I owe you, NOS, rumrunner, insertcoin and xda a big 'IOU'.
:good::good:
Capt Vikram Sandhu said:
Finally --- SUCCESS in S-Off thru rumrunner (attached thumbnail)
What I did was downgraded to [ROM]|8.15.2013|NOS M7 v3.0.0|(Sense 5.0 JB 4.2.2)Butterfly - http://forum.xda-developers.com/showthread.php?t=2193912
and ran rummrunner. VOILA.
Will definitely share the steps with you in my next post.
Thanks for all your support. I owe you, NOS, rumrunner, insertcoin and xda a big 'IOU'.
:good::good:
Click to expand...
Click to collapse
Haha enjoy! Don't forget to update your firmware to the latest from HTC official. (I supposed you have Super-CID)
xunus said:
Oh ya i forgot to add that in Here it is
Click to expand...
Click to collapse
Hi Xunus,
I was running InsertCoin 3.0.6 on my x920d HTC_038, unloocked (thru HTCDev), S-Off (thru rumrunner) and rooted by flashing 'UPDATE-SuperSU-v2.02' from recovery after flashing the ROM a couple of days earlier.
I had also flashed Kairi's firmware-kk (which is for HTC_061) as I had Super CID 11111111.
There was some problem with the htc backup/restore function, so I reflashed the rom acouple of times thru recovery(TWRP 2.7 by Kairi).
I happened to flash '[ROM] FireKatN4 Deodex V5 TW 4.4.4' from http://forum.xda-developers.com/note...emely-t2916463. Which did not flashed properly; so I re-flashed IC3.0.6 thru recovery and it showed successful at the end.
Now when I tried to reboot it got stuck in bootloop.
Since yesterday I have been trying various steps:
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 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 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"
Although I'm able to flash recovery img thru fastboot.
My Getvar all read as :
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: 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
(bootloader) gencheckpt: 0
all: Done!
Re flashed IC3.0.6 thru recover once again. when rebooting, get stuck in bootloop again.
PLEASE HELP
P.S. I have some pics also if required.
I am also S-Off, Relocked/Unlocked and not sure about root status.
Please Help
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.
Please share the link to the HTL21 ROM with NFC support...
Please share the link to the HTL21 ROM update with NFC support... Using now Butterfly_Sense6.0_KK4.4.2_Soul16.0
Thank you!
my dlxu x920e japan (i think version) cant get the insertcoin 2.4.0 release to work can you post how you did it
Lollilop update for Butterfly
Is there any possibility of getting Lollilop update via Insertcoin Rom for M7 on Butterfly?
Thanks
No !
jayc007 said:
Is there any possibility of getting Lollilop update via Insertcoin Rom for M7 on Butterfly?
Thanks
Click to expand...
Click to collapse
No ! i dont think so.. I earlier talk with official mentor of IC ROMS. and he told me that development for x920d has been stopped because they dont have a Butterfly now.
lollipop or at least kk 4.4.4 update for htc butterfly
i am running IC 3.0.6 its running ok, but i have some GPU lag in some games that i didnt have issues with when i was running htc stock 4.3 it not a deal breaker everything else works better, but i was hoping IC update this ROM to a newer version like on HTC DNA, at least KK 4.4.4
thanks
thanks for ur sharing.
friend brought me a d820e to look at, says it happens after OTA (sounds weird...)
my analysis as follows:
1. bootloader stays locked after reboot, tried "fastboot oem unlock" several times
2. flashing factory image, custom recoveries, cache, etc... are failed
Code:
sending 'recovery' (9434 KB)...
OKAY [ 0.515s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.696s
.
3. factory reset/date wipe/cache wipe results in:
Code:
Can't mount /cache/etc...
i could try to flash with LG flashtool but i'm not sure which TOT i should use, don't want to brick the device even more.
any other suggestions?
device info:
Code:
tools>fastboot.exe getvar all
(bootloader) max-download-size: 0x40000000
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: M8974A-2.0.50.2.22
(bootloader) version-bootloader: HHZ12d
(bootloader) version-cdma: N/A
(bootloader) variant: hammerhead D820(E) 16GB
android system recovery LRX22C
sh33z0r said:
1. bootloader stays locked after reboot, tried "fastboot oem unlock" several times
Click to expand...
Click to collapse
eMMC is dead.
anything to do or just rma?
sh33z0r said:
anything to do or just rma?
Click to expand...
Click to collapse
If it's still in warranty, RMA. If it isn't, send it to LG and pay for repair (motherboard swap).
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
skinny1439 said:
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) serialno: FA79G0500641
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 358182081003810
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
(bootloader) cid: BS_US001
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
Click to expand...
Click to collapse
Delete your SN and Imei.
Wysłane z mojego HTC U11 przy użyciu Tapatalka
skinny1439 said:
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
Click to expand...
Click to collapse
Skip again the bootloader unlocking procedure via htcdev
HTC U11 & Tapatalk
linar10 said:
Skip again the bootloader unlocking procedure via htcdev
Delete imei and serialno
HTC U11 & Tapatalk
Click to expand...
Click to collapse
Thanks I was able to unlock the bootloader via the htc dev. I just had to redownload the unlock key.
HTC u11 fails to boot.
skinny1439 said:
Thanks I was able to unlock the bootloader via the htc dev. I just had to redownload the unlock key.
Click to expand...
Click to collapse
I have a new problem.
I will start at the beginning. I was running stock htc oreo. I really wanted to install viperu 1.7. I assumed that I needed to reinstall nougat. I attemped to use the htc ruu to roll back. This failed. I booted into twrp and performed a wipe and restore to a known good nougat backup. When I rebooted the device started to boot gets past the htc logo and the shuts off. Thinking that something failed I rebooted into twrp and attempted to reinstall a stock zip. This fails to install. I wiped again and installed viperu 1.7 everything installs properly per the viper install guide. When the phone reboots it starts to install the apps. It finishes but shuts off. I connected it to a charger and booted the phone and attempted to boot but shuts off.
Can someone please tell me what I have done wrong and how to fix it.
thanks in advance.
Without s-off, the older ruu will not work. Probably older rom on newer firmware may not work. Download stock backup 2.xx.xxx.x and restore in twrp and do not forget full wipe before restoring backup
HTC U11 & Tapatalk
linar10 said:
Without s-off, the older ruu will not work. Probably older rom on newer firmware may not work. Download stock backup 2.xx.xxx.x and restore in twrp and do not forget full wipe before restoring backup
HTC U11 & Tapatalk
Click to expand...
Click to collapse
Do you have a stock backup 2.xx.xxx.x or know where I can get one. I looked online but they dont have 2.x on the list.
My phone is 2PZC50000 BS_US001 WHL (Single SIM) US Unlocked.
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
IT works again!!
linar10 said:
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
Click to expand...
Click to collapse
You saved me. I am extremely grateful of your knowledge. I thought I flushed 700 buck down the drain.
Whats the best way to revert back to nougat so I can flash to viperu 1.7. Right now I am on 2.31.617.2 from the backup you sent me to in the link. I do need to root the phone but have not attempted yet. I was planning to root the phone at the same time as installing viperu. Much thanks again.
skinny1439 said:
You saved me. I am extremely grateful of your knowledge. I thought I flushed 700 buck down the drain.
Whats the best way to revert back to nougat so I can flash to viperu 1.7. Right now I am on 2.31.617.2 from the backup you sent me to in the link. I do need to root the phone but have not attempted yet. I was planning to root the phone at the same time as installing viperu. Much thanks again.
Click to expand...
Click to collapse
Can't roll back to 7.1.1 yet. You need to be S-Off and Sunshine isn't fully working on Oreo at this time.
But there is a ViperU Oreo Rom available now. If you want, to just flash it and sick with 8.0.
linar10 said:
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
Click to expand...
Click to collapse
You're the man.
henslo said:
Can't roll back to 7.1.1 yet. You need to be S-Off and Sunshine isn't fully working on Oreo at this time.
But there is a ViperU Oreo Rom available now. If you want, to just flash it and sick with 8.0.
Click to expand...
Click to collapse
Thanks for all your help. I really appreciate it!
skinny1439 said:
Thanks for all your help. I really appreciate it!
Click to expand...
Click to collapse
The viper rom for oreo doesn't really work right yet and they're working on it. I'm using stock with magisk beta 14.5. Substratum works a bit too.
My HTC U11 always stuck in bootloader saying I use an unauthorized software everytime I update to Android Oreo ( official OTA update).
Even if I use RUU to 8.0.
The only thing I can boot my phone is when I use Nougat Rom. Even Costum Rom not helping. It;s very weird that I cannot update to 8.0.
I try leedroid Rom, also same, got back to Bootloader. So I need to reflash the 7.1.1 Rom to enable to boot.
My phone is S-Off with Bootloader Unlocked.
When I try to relock bootloader it will say something like
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ -0.000s]
finished. total time: -0.000s
In the Menu is greyed out saying bootloader already unlock.
Thanks in advance for any help.
sing2x said:
My HTC U11 always stuck in bootloader saying I use an unauthorized software everytime I update to Android Oreo ( official OTA update).
Even if I use RUU to 8.0.
The only thing I can boot my phone is when I use Nougat Rom. Even Costum Rom not helping. It;s very weird that I cannot update to 8.0.
I try leedroid Rom, also same, got back to Bootloader. So I need to reflash the 7.1.1 Rom to enable to boot.
My phone is S-Off with Bootloader Unlocked.
When I try to relock bootloader it will say something like
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ -0.000s]
finished. total time: -0.000s
In the Menu is greyed out saying bootloader already unlock.
Thanks in advance for any help.
Click to expand...
Click to collapse
Am output of a
Code:
fastboot getvar all
might show us some more, to help you with that very problem. Don't forget to delete your IMEI and SN though.
Tell us which RUU you are using that causes this very problem as well.
Sent from my HTC U12+ using XDA Labs
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1562400000
(bootloader) serialno: FA76T1802xxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 990007230168xxx
(bootloader) version-main: 1.28.617.6
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-001791N-1709131257
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
(bootloader) cid: BS_US001
all:
finished. total time: 0.016s
Any RUU, any costum Rom based on Android 8.0 give me error.
Other than that, all 7.1.1 Roms / RUU boots just fine.
It's Sprint Unit , S-Off , and change to BS-US001
return to sprint Rom also no use.
I can receive OTA no problem.
After OTA to 8.0 stuck in Bootloader again saying same error.
sing2x said:
Any RUU, any costum Rom based on Android 8.0 give me error.
Other than that, all 7.1.1 Roms / RUU boots just fine.
It's Sprint Unit , S-Off , and change to BS-US001
return to sprint Rom also no use.
I can receive OTA no problem.
After OTA to 8.0 stuck in Bootloader again saying same error.
Click to expand...
Click to collapse
Well that's it actually. The device only accepts CDMA sprint updates. So it would have to be rebranded and RUU'd back to Sprint to receive updates again. But are you really using an HTC U11? The fastboot command mentions a slot which in general only applies to Treble enabled devices.
Sent from my HTC U12+ using XDA Labs
Ruu back to sprint. Also cannot upgrade to 8.0. Even on OTA update. Yes its U11.
Any help ? it only works with 7.0 Rom. I try almost everything.
Hi,
I’ve been an owner of a Moto G7 Power device for a few months now. As we all know, life is not perfect and I still experience several problems (such as unavailable VoLTE/VoWiFi and no SMS notifications on a locked screen), that were present in LOS17.1 and are still there in 18.1. Since I am not an expert and therefore might had made some mistakes during flashing my phone, I’d like to give it a (last) shot and to try to do a fresh install of LOS – maybe it will help? What would be the best possible way to do that (in order to eliminate any doubts that anything was done wrong during flashing, etc)?
So what I have:
- Moto G7 Power (ocean, X1955-5), now "almost new".
- The device is manufacturer unlocked, all hardware seem to be completely OK.
- LOS18.1 installed (and is pretty much OK except for the problems I mentioned above).
That said, here is what I’d like to ask:
1. Does it make any sense to go back to the stock ROM, thren get all official Android/Motorola updates first and only after that to flash LOS?
2. Which LOS to flash: older 17.1 or the most recent 18.1?
3. Which custom recovery to use: TWRP or the one provided by LOS? Both have the versions specific for my device and seem to be maintained and updated.
4. Is it better to flash the custom recovery or just to load it via fastboot boot recovery.img? I used the latter option before and it seemed to work.
5. Does it matter which version of platform-tools to use? My Linux distro definitely does not have the latest one, though it works.
Thanks for any advice!
Stilbium said:
Hi,
I’ve been an owner of a Moto G7 Power device for a few months now. As we all know, life is not perfect and I still experience several problems (such as unavailable VoLTE/VoWiFi and no SMS notifications on a locked screen), that were present in LOS17.1 and are still there in 18.1. Since I am not an expert and therefore might had made some mistakes during flashing my phone, I’d like to give it a (last) shot and to try to do a fresh install of LOS – maybe it will help? What would be the best possible way to do that (in order to eliminate any doubts that anything was done wrong during flashing, etc)?
So what I have:
- Moto G7 Power (ocean, X1955-5), now "almost new".
- The device is manufacturer unlocked, all hardware seem to be completely OK.
- LOS18.1 installed (and is pretty much OK except for the problems I mentioned above).
That said, here is what I’d like to ask:
1. Does it make any sense to go back to the stock ROM, thren get all official Android/Motorola updates first and only after that to flash LOS?
2. Which LOS to flash: older 17.1 or the most recent 18.1?
3. Which custom recovery to use: TWRP or the one provided by LOS? Both have the versions specific for my device and seem to be maintained and updated.
4. Is it better to flash the custom recovery or just to load it via fastboot boot recovery.img? I used the latter option before and it seemed to work.
5. Does it matter which version of platform-tools to use? My Linux distro definitely does not have the latest one, though it works.
Thanks for any advice!
Click to expand...
Click to collapse
Your problems are more like related to the carrier the device is on, the software channel, radio firmware, and maybe apns included with LOS
sd_shadow said:
Your problems are more like related to the carrier the device is on, the software channel, radio firmware, and maybe apns included with LOS
Click to expand...
Click to collapse
So, in other words, you do not think that anything like this could be screwed up during installation/flashing?
I also have a feeling that it (VoLTE part) is somehow related to the carrier... but what can I do? I tried to make a new apn (based on the carrier's instructions) and it worked exactly the same as that included into LOS (i.e. no VoLTE, IMS is always reported "not registered"). On the other hand, I (as well as a couple of others) did not have these problems on the stock.
The reason why I'd like to try a fresh install is that someone (Moto G7: river, which is very similar; also the same carrier) reported that a) he got VoLTE working by going back to stock and then flashing a new version of LOS17.1 and b) his VoWiFi stopped working (on the same device) after an upgrade to 18.1:
https://gitlab.com/LineageOS/issues/android/-/issues/3269
Stilbium said:
So, in other words, you do not think that anything like this could be screwed up during installation/flashing?
I also have a feeling that it (VoLTE part) is somehow related to the carrier... but what can I do? I tried to make a new apn (based on the carrier's instructions) and it worked exactly the same as that included into LOS (i.e. no VoLTE, IMS is always reported "not registered"). On the other hand, I (as well as a couple of others) did not have these problems on the stock.
The reason why I'd like to try a fresh install is that someone (Moto G7: river, which is very similar; also the same carrier) reported that a) he got VoLTE working by going back to stock and then flashing a new version of LOS17.1 and b) his VoWiFi stopped working (on the same device) after an upgrade to 18.1:
https://gitlab.com/LineageOS/issues/android/-/issues/3269
Click to expand...
Click to collapse
Flashing stock is a possible fix, even likely, if others have reported just that.
Doesn't mean you installed it incorrect.
Custom Roms don't include radio firmware, and sometimes it needs to be reflashed.
If you want you can just flash the stock radio firmware.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
sd_shadow said:
Flashing stock is a possible fix, even likely, if others have reported just that.
Doesn't mean you installed it incorrect.
Custom Roms don't include radio firmware, and sometimes it needs to be reflashed.
If you want you can just flash the stock radio firmware.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
Thanks for a hint! Honestly, I bought this phone with a sole purpose of using a custom ROM without google apps... so I am not going back to stock.
Do I understand it correctly that the code you provided implies that I follow only the part of the instructions on "how to flash a stock ROM back" from here:
https://forum.xda-developers.com/t/...ersions-flash-back-to-stock-firmware.3927138/ ? The sequence of commands is different there - erasing comes after the both flashing commands (I am not an expert, sorry).
One more thing - which stock ROM should I use? I mean, which version - the latest, the closest to the current version of LOS or it does not matter? As far as I can see, the latest stock is for Android 10, and I have LOS18.1 installed.
Stilbium said:
Thanks for a hint! Honestly, I bought this phone with a sole purpose of using a custom ROM without google apps... so I am not going back to stock.
Do I understand it correctly that the code you provided implies that I follow only the part of the instructions on "how to flash a stock ROM back" from here:
https://forum.xda-developers.com/t/...ersions-flash-back-to-stock-firmware.3927138/ ? The sequence of commands is different there - erasing comes after the both flashing commands (I am not an expert, sorry).
One more thing - which stock ROM should I use? I mean, which version - the latest, the closest to the current version of LOS or it does not matter? As far as I can see, the latest stock is for Android 10, and I have LOS18.1 installed.
Click to expand...
Click to collapse
The commands I posted are just the radio parts.
That order sometimes fixes radio issues, that the normal order does not.
There may be a benefit to flashing the newer firmware, rarely is the older firmware better, unless you are flashing an older custom ROM.
sd_shadow said:
The commands I posted are just the radio parts.
That order sometimes fixes radio issues, that the normal order does not.
There may be a benefit to flashing the newer firmware, rarely is the older firmware better, unless you are flashing an older custom ROM.
Click to expand...
Click to collapse
Thanks a lot! Though it did not help... maybe I did something wrong.
So first I looked at getvar:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-16222030b3b-201001
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ....................
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: A37CC9D800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: ....................
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 07-08-2020
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 29 15:45:40 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QPOS30.85-
(bootloader) ro.build.fingerprint[1]: 23-3/dc622c:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_41.00.01.162R OCEAN_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Thu Oct 1 00:21
(bootloader) kernel.version[3]: :27 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_retail-a30e356d6d-201001
(bootloader) rpm.git: MBM-2.1-ocean_retail-20f2cf34-201001
(bootloader) tz.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) devcfg.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) keymaster.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) prov.git: MBM-2.1-ocean_retail-6814a8d41f-201001
(bootloader) aboot.git: MBM-2.1-ocean_retail-16222030b3b-201001
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
(bootloader) pcb-part-no: SP69A6P7PU
all: listed above
finished. total time: 0.014s
and noticed that the current-slot/running-slot is b.
Grabbed the latest retus Moto firmware from lolinet (the same 10/QPOS30.85) and then, as probably expected:
Code:
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modemb' (65428 KB)...
OKAY [ 2.616s]
writing 'modemb'...
(bootloader) Invalid partition name modemb
FAILED (remote failure)
finished. total time: 2.617s
Then:
Code:
$ fastboot flash modem_b NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_b' (65428 KB)...
OKAY [ 2.612s]
writing 'modem_b'...
OKAY [ 1.110s]
finished. total time: 3.722s
$ fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.017s]
finished. total time: 0.017s
$ fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.017s]
finished. total time: 0.018s
$ fastboot flash fsg_b fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_b' (9204 KB)...
OKAY [ 0.368s]
writing 'fsg_b'...
OKAY [ 0.121s]
finished. total time: 0.490s
After reboot everything is exactly the same as before - i.e. the same problems remained, no new ones showed up.
UPD: actually, no - the phone is reachable, it rings, but neither I can hear the other party, nor I am heard by anyone.
Maybe I had to flash both a and b slots?
Since my carrier is T-Mobile (though the phone is retail), would it make any sense to try to flash the radio from the T-mobile ROM? There are two ROMs available - RETUS (which I used) and TMO.
Looks like I'll have to temporarily go back to the stock... my fault anyway, needed to check more carefully what the LOS "official support" actually means
Thank you.
Well, back to stock (RETUS) for a while. IMS status is registered, so I guess VoLTE should work. Will try it and VoWiFi a bit later.
However, the settings in APN are a bit different from what is supplied with LOS - could this be the problem?
I'll try to flash LOS ROM once again, so going back to my initial questions - which recovery would you recommend and should I really flash it or fastboot boot?
Thank you.