yashsingh1/xdaforums huggingface dataset:
[Moto E4 Guides, News, & Discussion] ozmage:
https://nopaste.xyz/?3a707bb4304ab64f#r7tSsESO2w8UvM52VEASJhzJIanOoBBstqFgGNEt1gE=

adb logcat -b radio

on lineageos

---------- Post added at 01:13 AM ---------- Previous post was at 01:03 AM ----------

that would do nothing either

look

this is from a Russian forum pda somebody already did this :0 we are doomed

{

Thank you.

The first method does not work 100%.

TA was originally unlocked from the sprint by unlocking the boot and inserting an empty partition oem.img (about 16 MB in size).

After the OTA arrived the NCQS26.69-64-8 version of the modem changed to M8920_15000.280.06.58.05E (on the M8920_15000.280.06.58.05R), the

radio module is de-activated and can not be turned on.

If you lower the firmware version to NCQS26.69-64-5 (Baseband-Unknown) and update by air, the modem is returned, but does not work.

The thought crept in that OTA was installed crookedly and to blame oem.img (which was used when untying the sprint).

I requested NCQS26.69-64-5 and through adb sideload installed Blur_Version.26.211.9.sperry_sprint.sprint.en.US.zip when installing there were errors in the oem section and it was not installed until the end.

Filled the image oem.img from the working machine and installation Blur_Version.26.211.9.sperry_sprint.sprint.en.US.zip went without errors, but the radio did not start.

Also tried to flash sections from the working device:

modem.img and fsg.img, fsc.img, ssd.img, dsp.img, devcfg.img which are related to the radio, the result of zero-Baseband or M8920_15000.280.06.58.05E or Unknown.

At me variants have ended, the version of a radio module can not be lowered.

How to make a GSM module?

I also tried unlock via Gcpro Key, which was done repeatedly unlock xt1766, wrote that the release was successful, but the connection never appeared ..}

https://4pda.ru/forum/index.php?showtopic=835660&st=2280
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Here's the truly mysterious thing about your analysis. My device, for example, I can downgrade to NCQS26.69-64-5 with the firmware package, and upon reboot accept and install the NCQS26.69-64-8 OTA, and my radio works perfectly. Not every device owner is experiencing a broken radio. That's why I strongly disagree with the Russian PDA opinion of the bug. Both in theory and in practice, although difficult and risky, any alterations made to a device by an OTA update can be reversed. And, upon reversing the alterations to pre-OTA state, the device configuration will likely reflect the pre-OTA state.

While I am truly pushing Motorola Mobility tech support for a fix, the beurocracy of the matter is that things must follow a standard operating procedure. Tech support and software developers will slowly analyze the bug, reach a determination as to why only some devices, and not others, are affected by the OTA, a bug fix OTA patch will then be compiled, then the roll out of the fix ensues. But I'm certainly not convinced that this bug is irreversible. When OEMs roll out OTAs that create a major bug such as this, those OEMs are fully capable of fixing the bug. I must admit, this is one of the most puzzling OTA bugs I've ever encountered; this is certainly not the first time such an occurrence has transpired, and likely won't be the last. As for myself, I'm not giving up either. If I fail 10 more times in finding a resolution, it will be well worth it knowing I'm giving my best efforts.
[Moto E4 Guides, News, & Discussion] ozmage:
yeah looks like the one of the 4pda forum have a real broken radio not like the 2 of us which the phone work just fine but only on stock have you tried to flash lineageos the radio is off all the time and cant be turn it on check my logcat .
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
I agree with you. Another theory, and something that has been effective in the past -- if I dump all relevant partitions from my device (which is 100% functional) and create a TWRP flashable installer which flashes those partitions to a device with corrupt or buggy firmware, in theory, the broken device must become fully operational. If I compiled such an installer, would you be willing to try it? I will of course take great care that a partition doesn't get flashed with an incorrect image.

Yes, I recreated the LineageOS procedure you spoke of. Twice in fact. Soon as I restored my TWRP backup, all was well. I've read your logcat thoroughly. And it just still does not make sense to me. This is a crazy ass bug for certain.

The logcat is very clear that your device is not reading -- or not recognizing -- your SIM.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
[MENTION=8371146]ozmage[/MENTION], a very interesting entry of your log is the -- Failed to listen on sap_uim_socket1 -- message. Only three things give rise to this: (1) corrupt or missing radio firmware; (2) a corrupt or missing UICC card; or (3) a hardware related malfunction due to the baseband radio itself -- or the SIM socket. It is obviously the 1st scenario -- firmware related.

My point on this is, we have to rule out other possibilities and I think this confirms your issue. If your radio was working fine before the OTA, then after the OTA your radio is broken,it doesn't take Sherlock Holmes to surmise that the OTA was the culprit. But nevertheless, confirmation is always needed when troubleshooting.
[Moto E4 Guides, News, & Discussion] ozmage:
but it is reading the sim on the lineageos configuration at the start says sim detected spain and select the language to spanish it ask me to activate the data Viva which is my carrier and on the apn settings there are my apns but on the phone information menu *#*#4636#*#* the radio its off and i try to turn it on with the switch and do nothing and the logcat shows right away this :

08-16 18:12:49.216 1677 1677 D RILJ : [3761]> RADIO_POWER on [SUB0]

08-16 18:12:49.225 1677 1778 D RilRequest: [3761]< RADIO_POWER error: com.android.internal.telephony.CommandException: MODEM_ERR ret=

08-16 18:12:49.226 1677 1778 D RILJ : Unsol response received for UNSOL_OEM_HOOK_RAW Sending ack to ril.cpp [SUB0]

08-16 18:12:49.226 1677 1778 V RILJ : [UNSL]< UNSOL_OEM_HOOK_RAW 514f454d484f4f4bf2030800040000000050c011 [SUB0]

so you flashed lineageos and your modem works ? or not , but yeah after restore the twrp of 64-8 the radio is on

---------- Post added at 03:04 AM ---------- Previous post was at 03:02 AM ----------

looks the ril is just broken on custom roms not stock RIL works for you on custom roms after 64-8 ota ?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Yes I just flashed LineageOS earlier today in fact. See that -- MODEM_ERR ret -- entry in your log? Another confirmation it's firmware related. There can be no doubt that the issue is from a corrupt partition. But which one remains the mystery. Like I said, I can create an installer with all pertinent partitions. The "ret" is reference to FAC (feature across code). Firmware. The log strongly suggests firmware is failing to power your radio on.

We need to troubleshoot your com.android.internal.telephony system process as well.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Yes, to clarify, both custom and stock ROMs function completely normal after installing the OTA for NCQS26.69-64-8.
[Moto E4 Guides, News, & Discussion] ozmage:
sorry to ask again , lineageos on your phone the radio is on the modem works on it , if yes so the problem relays in my phone , this is just wonderful ..... only me is affected on custom roms , i will test your installer if lineageos works on your device after 64-8 ota yes .

---------- Post added at 03:17 AM ---------- Previous post was at 03:16 AM ----------

ok i see now

---------- Post added at 03:19 AM ---------- Previous post was at 03:17 AM ----------

the package that you uploaded before of 64-8 on google drive its a dump of all your partitions after the ota right ? i will download that first while you compile the installer that you talk about early .
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
No it's not a dump of "all". The SPerry has around 55 total partitions. Of course, some are simply spares put in place by the OEM in the event of future necessity. Others -- such as /cid and /pds -- contain your MEID, IMSI, ESN, IMS configs, etc. I'll dump everything that could possibly have any relevance to this issue, plug them all into my Android Kitchen, and make the installer. I'll do my very best to have it completed by tomorrow afternoon.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
[MENTION=8371146]ozmage[/MENTION], for your reference, this is a complete partition index of the xt1766.

https://drive.google.com/folderview?id=1omDEz6tB2U6Z88mCfubIwcGRoFHt0jMF

There are 54 total. Note that all bootloader partitions also have a dedicated partition for a backup. E.g., /aboot, /abootbak; /sbl1, /sbl1bak; /rpm, /rpmbak, etc. In the meantime, while you await the installer, try to familiarize yourself with as many partitions as possible -- names and relevancy. It'll come in handy down the road.
[Moto E4 Guides, News, & Discussion] ozmage:
if what im going to do dont work flash the 64-8 that you made to fix my ril on custom roms i will wait , thanks so much to clarify me that is my phone with the problem thanks in advance .

---------- Post added at 03:38 AM ---------- Previous post was at 03:36 AM ----------

good thanks
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Anytime [MENTION=8371146]ozmage[/MENTION]. I realize this type of thing is frustrating and you need your device working. Be patient and know I'm doing my best to help -- succeed or fail I'm trying for you.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Also [MENTION=8371146]ozmage[/MENTION], I want you to give this a try. This is the /persist partition and it could he very relevant to this issue. Download the persist.img and try this in fastboot:

fastboot oem fb_mode_set

fastboot flash persist persist.img

fastboot erase carrier

fastboot erase DDR

fastboot erase cache

fastboot oem fb_mode_clear

Then,

fastboot reboot

https://drive.google.com/file/d/16ItVjal46BG36o392dWwGF1wkqQfsbhE/view?usp=drivesdk
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Okay [MENTION=8371146]ozmage[/MENTION], slowly narrowing things down if nothing else. I'll get the partition installer compiled and link it sometime tomorrow afternoon. Appreciate you trying the files. At least that tells us what the problem is not. I just made my full partition dump. At least 33 out of the 54 will be included in the installer.
[Moto E4 Guides, News, & Discussion] sidgallup:
Firmware is destroying radios then, funny how it only affects some people. Mine is Boost branded, ozmage's is Virgin Mob. and your is it Sprint? are they exaactly the same devices and firmwares just put in a different box or are they different in some way?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Not on the Moto E4 SPerry. This data is stored on /pds and /cid. Motorola Mobility is no longer implementing the older hob and dhob configs. Because /tz and /aboot prevent direct flashing via fastboot on a number of partitions, I'll write a script in Edify to flash them with the TWRP installer. I'll exclude the primary bootloader (/rpm), secondary bootloader (sbl1), and trust zone (/tz), all of which have the potential to trip a qFuse and cause a brick. The secondary radio partitions will be included (/ssd, /fsc, /sec, etc.) Since Motorola Mobility has denied all my requests for copies of its carrier manifests (classified information apparently), there are a few partitions for which the purpose remains unknown, but I'll also include those since there's no risk in flashing them.
[Moto E4 Guides, News, & Discussion] ozmage:
So [MENTION=342404]ALI12[/MENTION] just downgraded the boot loader and still have broken radio , i already flashed persist and nothing happen so , im waiting for [MENTION=7383447]MotoJunkie01[/MENTION] make his twrp compilation to flash it later . this is not good ......

[MENTION=342404]ALI12[/MENTION] you downgraded the modem too ? what says on baseband in fastboot mode ? after downgrade the bootloader ?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Ok [MENTION=8371146]ozmage[/MENTION] here is the installer. I would recommend doing a full factory reset after installing it. I have tried it on my own device and works fine for me. However this is at your own risk. It flashes 29 of the key partitions. I did include /tz. To note, these partitions are all taken from Build No. NCQS26.69-64-8.

Link: https://drive.google.com/file/d/1I2DPtmdBeitu45LfUOY-3GJINCOdseF8/view?usp=drivesdk

You need to be running the NCQS26.69-64-8 version of the Android OS when flashing this. Just install via TWRP, do a full factory reset, and reboot. Make a full backup of anything important of course before trying it.

This is based on the theory that I have included key partitions from a fully functioning device. Installing this will put your device in the same configuration as mine firmware wise. With that logic, your device should function normally just as mine does.

As an added bonus, flashing this should debloat your device, since I included my debloated /oem partition in the installer.
[Moto E4 Guides, News, & Discussion] ozmage:
cool thanks downloading now .
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Fingers crossed...
[Moto E4 Guides, News, & Discussion] ozmage:
what version of twrp do you have ?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
The latest [MENTION=6485916]squid2[/MENTION] build: v3.2.3-r1

https://xdaforums.com/devdb/project/?id=22028#downloads
[Moto E4 Guides, News, & Discussion] ozmage:
booting fine after flash im gonna flash lineageos , modem is working fine on stock and everything else

---------- Post added at 05:23 PM ---------- Previous post was at 05:21 PM ----------

looks better debloated jejeje
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
So your radio is working again?
[Moto E4 Guides, News, & Discussion] ozmage:
booting lineagos now fingers crossed X
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
So to clarify, your radio was working again in stock?
[Moto E4 Guides, News, & Discussion] ozmage:
[MENTION=7383447]MotoJunkie01[/MENTION] No Man I Have no Luck its not working at all radio still off on lineageos

---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------

yes always work but not on lineageos
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Then I can tell you what would certainly work. If those same partitions in my installer were all downgraded from NCQS26.69-64-8 to the partitions from NCQS26.69-64-5, you would be fully reverted to pre-OTA. It would have no other choice but to work.

One thing I learned for certain with that installer is that it will force partitions to downgrade that would not otherwise flash with fastboot or RSD Lite.
[Moto E4 Guides, News, & Discussion] ALI12:
Yeah, I already downgraded all bootloader except SBL1 which will brick phone as this cannot be downgraded by fastboot/root/eMMC(via eMMC Repair tools I mean)....

downgrade modem and phone will have unknown baseband.

Even I had another phone fully working and radio OK with BB.07 bootloader (NCQ26.69-56) build.

I just flashed fsg.mbn and NON-HLOS.bin with erasing modemst1/st2 from (NCQS26.69-64-8) and phone's radio stopped working. I saw baseband become from (R) to (E) and radio was off...

[MENTION=8371146]ozmage[/MENTION]: after flashing persist from [MENTION=7383447]MotoJunkie01[/MENTION]'s post.

Try:

fastboot erase modemst1

fastboot erase modemst2

fastboot reboot

and see if phone's IMEI/MEID/ESN/S/N remains untouched?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
You can downgrade sbl1 with Qualcomm's QFIL/QPST using emergency download mode. But it would be inconsequential to this issue. The secondary bootloader should not have any relevance to RIL.
[Moto E4 Guides, News, & Discussion] ozmage:
well there is nothing i can do now , and im not going to brick it so is better if i get rid of it and buy another one ,

im not going to struggle no more but hey if there is a solution that not involves bricking i will try but seems like i have no luck i been doing everything this last few days and im tired of th is phone the thing is not end with a bricked phone that is not good for anybody now i can give it away to a person who only use the phone like a normal person , not a geek who uses root and flash custom roms .
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
It appears that Motorola Mobility is not going to roll out an OTA fix either. Tech support and software development have stated that unless it's a bug affecting the stock configuration, there is nothing to fix. Those guys aren't exactly supportive of custom development. But who knows, the next scheduled incremental OTA could inadvertently fix it.
[Moto E4 Guides, News, & Discussion] ozmage:
this happen to me but others dont even have modemradio on stock , well this means i have some luck

---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------

i will wait for the ota ..... i will keep the phone other month
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
That is true. There are quite a few device owners who have no signal at all running pure stock.
[Moto E4 Guides, News, & Discussion] carlosvinuezap:
[MENTION=7383447]MotoJunkie01[/MENTION] [MENTION=8371146]ozmage[/MENTION]

Do you have information about the failure of service? I am a user who can not use my phone for more than 14 days, and I only have 2 months to buy it ...
[Moto E4 Guides, News, & Discussion] ozmage:
nope im facing a problem too not like yours but you know i cannot use custom roms only stock on lineageos i THE RADIO is off
[Moto E4 Guides, News, & Discussion] carlosvinuezap:
[MENTION=8371146]ozmage[/MENTION] hablas español? soy de venezuela
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Are you having radio failure on stock ROM or only on custom?
[Moto E4 Guides, News, & Discussion] carlosvinuezap:
[MENTION=7383447]MotoJunkie01[/MENTION]

my phone was updated since the last OTA and since then the radio failure is turned off
[Moto E4 Guides, News, & Discussion] sidgallup:
Is there a way to edit - add APNs on lates OTA? im thinking about giving this phone to my uncle since hes older, needs a phone and he doesnt care about custom ROMs, its either that or selling this one on Craigslist for what i paid and get a brand new one which im not going to update this time.
[Moto E4 Guides, News, & Discussion] carlosvinuezap:
[MENTION=7383447]MotoJunkie01[/MENTION]

is there no way to get the official rom NCQS26.69-64-8 to flash the equipment?

when placing the equipment in fastboot the baseband at the end says 5E

I'm asking you should not 5R appear?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
I'm not certain about the misnomer between 5E and 5R. Mysterious indeed. If you want to officially upgrade to NCQS26.69-64-8, flash this partition updater first via TWRP. It will update your bootloader, radio and partition index to the latest build. https://drive.google.com/file/d/1I2DPtmdBeitu45LfUOY-3GJINCOdseF8/view

Then, go to this link and flash the system image only in fastboot mode. https://drive.google.com/file/d/1T7OydBiJ6TY9w6D__yhFc9ioIOYpWCAC/view
[Moto E4 Guides, News, & Discussion] carlosvinuezap:
[MENTION=7383447]MotoJunkie01[/MENTION] do you indicate the commands to update the first step and the second?

Thank you
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
The first step (first link), simply download the zip and store it to your device. Boot into TWRP, select install, and swipe to start installing.

Second step (second link): download the zip package and extract system.img only. Store it on your device. You can also install that in TWRP. Just select install, just like previous step, now select Install Image in bottom right hand of screen, select the system.img and swipe to install.

Go back to TWRP main screen, select WIPE, Format Data, swipe to commence. Now select WIPE and swipe for a factory reset. Reboot system.
[Moto E4 Guides, News, & Discussion] carlosvinuezap:
[MENTION=7383447]MotoJunkie01[/MENTION]

I have not installed twrp on my computer, I do not intend to root
[HTC Excalibur] NRGZ28:
I put the CHome interface on a diet. I always though the panels were too fat.... so I made them thinner. All this was done in the .cpr file in \windows. So I attached it here, if you want to try it to your device. Make sure to backup your original file, in case you want to go back. Enjoy... :D
[HTC Excalibur] superminipoo:
coolio.

can u make the panels different color? when u go down it changes to different color or shape. hehe, something to think about.
[HTC Excalibur] NRGZ28:
Nah I cant. Tried.... :/ I can change the opacity of the panel, but it's not that dramatic lookin :)
[HTC Excalibur] superminipoo:
man u guys r way ahead of me on skinning.
[HTC Excalibur] inspron:
How did you get it to show "Task" at the bottom right on every screen instead of contacts?
[HTC Excalibur] superminipoo:
smart tool kit
[HTC Excalibur] inspron:
mind if I ask which WM6.1 u are using? I have been trying to get my Dash to look like those pictures.

I downloaded Ricky V8 vanilla but it doesn't show "My Programs" like on yours.

I wonder if his V7 is a better bet.
[HTC Excalibur] littleclown:
good idea but now when I change the active baloon every other baloon jump and hide a half on top and bottom - not cool :).

please attach original file :)
[HTC Excalibur] jsp_m:
I have an issue with iconbar and this slim Chome profile - inconbar background has a part of the background picture which is not connected to the rest of the background picture

I gues you have it also, but it is less visible since you have that line-background

Any ideas on how to remedy this?
[HTC Excalibur] Se7eN43:
same here as jsp. the slim bars dont look bad but it shifts the topbar area of the background image to the left. if only i wasnt picky about the topbar being transparent. good find though. thanks
[HTC Excalibur] jsp_m:
I am almost sure that it can easily be resolved by adapting the size specs in Chome cpr file (open in notepad), probably here:

<Image ID="Background" Opacity="1.0" Top="0" Width="320" Height="220"/>
<Layer ID="StaticHomeArea" Visible="False"/>
<ListView ID="HomeNav" Width="320" Height="186" Columns="1" Rows="5" ItemWidth="320" ItemHeight="36">
<Layer ID="Focus" Width="320" Height="84">
<Image ID="Image Default" Width="320" Height="84" ScalingAlgorithm = "TriLinear" Opacity="1.0" />
<ControlSequence ID="Action Sequence" FramesPerSecond="30" Loop="False">
<Image ID="Image" Left="0" Top="0" Width="320" Height="114" ScalingAlgorithm = "TriLinear" Opacity="1.0" />
</ControlSequence>

or in the active homescreen xml

will playaround a bit, if I don't fix it I will rather drop out iconbar than this great feature
[HTC Excalibur] Mikey:
Can you take a SS.

Im thinking if you resize the pic to 320*240 should fix it. I think the pics 320*213
[HTC Excalibur] tmcfarland:
Nice ... perhaps panels could slimmed down even further using 96 DPI?
[HTC Excalibur] NRGZ28:
The panels CAN be slimmed down as much as you want... :)

The way to fix that is to change background issue is to change the second line in the file to this...

<Image ID="Background" Opacity="1.0" Top="-27" Width="320" Height="213"/>
[HTC Excalibur] NRGZ28:
Updated the file in the first post to reflect this change...
[HTC Excalibur] blahzay_blah:
i tried this thin chome ok frst it changed my background all black and then its not even aligned with the panles, it was worth the try but i guess not for me thanx anyway gpd work
[HTC Excalibur] johnnylavah:
very nice! i will try it out tonight
[HTC Excalibur] tdub1025:
I used the updated file and still cant change the BG
[HTC Excalibur] rickwyatt:
NRGZ28 could you fix this for me
[HTC Excalibur] Reeg:
I had the same thing happen. I went back to the normal setting.
[General Questions and Answers] JarekStudio:
Could someone make a custom recovery for me from this stock one, please? My mobile is Huawei Cun-l21, I have ported one twrp, but I had problems with partitions, 0mb storage... It's very important for me.

Stock recovery -> http://www.mediafire.com/file/7w449g7eqhyyeyt/recovery.img/file