yashsingh1/xdaforums huggingface dataset:
[Optimus V Android Development] speck1234:
It was CWM I was using, not TWRP. Let me know when you do because neither version of TWRP in the Drive link worked on my LS670. Tried both versions and phone reboots when trying to go into recovery. Prior to that I tried flashing both TWRPs using both CWM and Flash Image GUI and it still reboots and refuses to go into recovery. If anyone knows how and where to get a good working bootable OS2SD friendly NON-TLS TWRP for the LS670 I'm all ears, because the issue might be related to TLS and I'm new to all this.

---------- Post added at 02:06 AM ---------- Previous post was at 01:55 AM ----------

I even tried flashing one of the internal builds of CM11 using CWM and it gave me an error with Status 0
[Optimus V Android Development] bigsupersquid:
I'll poke at the zip files now.

if the twrp recovery installer zip's update-binary is too new it might cause flashing errors, but I thought I used an older one intentionally for that.

I do have a vm670 rather than an ls670, they use the same board but the partitioning is a little different. so maybe the recovery partition is a little small on the ls670? but I hadn't heard this issue before. also back when this was active, I did not get any reports of Optimus s having issues with either twrp or TLS

Depending on how in-depth you'd like to go, it can probably be debugged, since you say your ROM is rooted. You'd have to install connectbot unless your CM has terminal. A few terminal commands would get logs and partition information, and you could post that here. Let me know if you want to try those. that'd show why the recovery reboots via a /proc/last_kmsg.

First, post me a flashable zip file that works in your current recovery, preferably a flashable recovery zip itself. I can use that to make one for twrp for you with a compatible update-binary.

The OS2SD ROM is fun to run, it makes the little phone feel bigger, but it is a little glitchy, just because even getting it to run required a lot of patches and build tweaks inherited from the now-defunct and disbanded androidarmv6 team. There's things like the 3.0 kernel is known to eat power while the wifi is turned on due to a sleep issue with the BCM chip. And it's slow to wake from screen off randomly. At one point the alarms failed to go off. but if I remember right, that's fixed. It's been a couple years since I used it myself.

plus there'll be many installable apks which crash due to neon assembly language code being assumed compatible due to kitkat, but it's not. because the *670s are armv6k, not armv7 and don't run neon code. that's the reason for the aforementioned patches and build tweaks.

anyway, let me know if you want to use the terminal for logging and data, and post me a working recovery zip if you can. It's the weekend so I can keep tabs on the thread.

you can't effectively flash any of these roms with cwm. you'd have to change the installer scripts even if it could handle the binaries. the internal and os2sd (ext4 only) ROMS have their installer scripts fixed (to make sure they'll flash the boot.img) and are re-uploaded now. but they'll still only work with the twrp I have posted. cwm uses a different partition map due to the kernel changes. and the new twrp will not correctly flash old ROMs, also because system and userdata are reversed in the partition map.

//edit:

hmmm, the update-binary in the twrp zip file looks like it should work, but cwm may not use the newer edify scripting. it might be fine. flash image gui should work, though, if I remember right. so still might need a last_kmsg after it reboots from recovery.

so it might help if you post a recovery.zip that does work for you. I can modify it for the newer twrp and that'll be simpler to test than having to type in terminal and upload files from sdcard.
[Optimus V Android Development] speck1234:
I was busy on the weekend sorry about that. But thanks for the advice though. I remember having a test TWRP someone made for the LS670 and it worked, but I don't remember where I found it on the internet though. It said something like twrp_ls670_test3.zip and it was on MediaFire but I don't have it downloaded anymore, I accidentally deleted it. Stupid me. My CM7 has a terminal emulator built-in so I'll have a look at the last_kmsg and the logcat. Also I'll dig Google for the TWRP and keep you posted once I get it. I'm on XDA on the mobile browser and I will still need to figure out how to upload files here, if XDA even allows me to.

Edit: Found it. The working recovery is attached.
[Optimus V Android Development] bigsupersquid:
[MENTION=8027143]speck1234[/MENTION]

you can try this recovery.img with flash image gui or this test zip in either flash image gui or the twrp version that does work on your device.

either way, this twrp version can take up to a minute to start all the way up, I think because of the oddball changes in the way the fstab is handled in it.

//edit:

the contents of /proc/last_kmsg after the phone reboots from TWRP could be useful, a logcat is only about your android install and won't have any data about the recovery in it though.
[Optimus V Android Development] speck1234:
bigsupersquid, follow up? I'm waiting for a working OS2SD TWRP for my LS670. Does carrier/color matter because I think it works for some of the people here and I have the purple one from Sprint and partition layout/hardware probably varies between carriers/colors and I can't tell if the uploaded builds on the Google Drive link were incompatible with my variant of the LS670.

Does the LS670 have a fastboot mode where I can manage to flash it via USB at all? I tried getting it into emergency mode(hold vol-, camera button and search), typed "fastboot devices" on my PC's command prompt and it returned nothing. If there's a button combination to go to fastboot mode to flash a recovery I'm all ears because I tried every button combination I could think of and no such luck. Only working button combinations were emergency mode and recovery.

---------- Post added at 02:16 AM ---------- Previous post was at 02:13 AM ----------

Nevermind I'm on the XDA app now and I don't understand why it doesn't always refresh. Sorry I didn't see your new post until now. Mind the last reply I made.
[Optimus V Android Development] speck1234:
Heads-up, 2 questions.

1. Does carrier/color matter because I think it works for some of the people here and I have the purple one from Sprint and partition layout/hardware probably varies between carriers/colors and I can't tell if the uploaded builds on the Google Drive link were incompatible with my variant of the LS670.

And,

2. Does the LS670 have a fastboot mode where I can manage to flash it via USB at all? I tried getting it into emergency mode(hold vol-, camera button and search), typed "fastboot devices" on my PC's command prompt and it returned nothing. If there's a button combination to go to fastboot mode to flash a recovery I'm all ears because I tried every button combination I could think of and no such luck. Only working button combinations were emergency mode and recovery. For this reason I use Flash Image GUI.
[Optimus V Android Development] bigsupersquid:
carrier only matters if you have to mess with baseband ril binaries after the rom is installed.

color doesn't matter.

I've never heard before of an ls670 or vm670 that was not compatible with the rest of them, so something weird is going on in your situation.

fastboot depends on your firmware. zv4 for vm670, I forget on ls670, but if it works, reboot bootloader in su terminal will put it in fastboot.

if the recovery I just posted won't boot on your device after using flash image gui to flash it, I need a /proc/last_kmsg after it reboots to the rom to see why.

there's no reason I know of except download or nand issues that would keep this recovery from running on any thunderc ( Sprint or virgin Mobile Optimus s or v.)
[Optimus V Android Development] speck1234:
So sorry for the duplicate post yesterday. I tried to figure out how to edit or delete it on the XDA app.

Neither recovery you gave me worked; they still reboot. I'll gather the last_kmsg and attach it once I get it.

FYI I'm on stock ZVD with root and stock recovery now because CM7 started freezing at the boot animation and wouldn't go into the TWRP in order to clear dalvik cache and data so I had to use a guide on androidcentral.com to "un-softbrick" it. I still have Flash Image GUI on it. If you want you could port OS2SD stuff from the multi's onto the twrp-ls670-test3.zip I attached. It's TWRP 2.2.x(don't remember last 2 numbers) though so I doubt it would work with that version.

---------- Post added at 07:07 AM ---------- Previous post was at 07:02 AM ----------

Also if I remember correctly, adb reboot bootloader when done on my PC(stock ZVD so don't have terminal app anymore but will install new one shortly) didn't do anything it rebooted to the ROM.

---------- Post added at 07:19 AM ---------- Previous post was at 07:07 AM ----------

It could be a problem with my NAND but I think it could be the kernel that's the issue. I installed CrossBreeder armv6 a while back. is that a custom kernel or some sort of modification? And is a TLS kernel needed for my recovery to not reboot? Because a while back I noticed in the CWM I had on it that the log when installing TWRP 2.7.1.0 said "tested to be only compatible with TLS builds!" so I'm intrigued my LS670 doesn't have it's TLS on due to it rebooting. Google doesn't give me info on where to get a custom kernel with TLS enabled.
[Optimus V Android Development] bigsupersquid:
if cm7 was having issues freezing and getting to recovery, it increases the likelihood of NAND issues. I did read that later Optimus s/v models seemed to sometimes have weaker flash storage.

as far as porting into the older twrp, I'd rather not play at that. it needs certain features from the newer kernel like selinux, and a half-baked recovery could cause additional issues.

TLS is just a software switch in the kernel, it has nothing to do with your hardware. it does change the way some binaries run, they're supposed to be built compatible with TLS to work.

here's info on TLS.

https://www.kernel.org/doc/html/latest/networking/tls.html

your fastboot functionality is locked out in firmware, bummer.

crossbreeder is a tweak but not kernel.

aside from my 3.0 kernel port, the newest one for this device is a 2.3 kernel, and nothing else but mine will have TLS turned on. trying to use a2.3 kernel with KitKat would require a full system rebuild and still probably wouldn't work.

KitKat is going to require TLS without rebuilding it with different flags, or using one of the earliest variants like Skinbark's.

get me that last_kmsg for a better idea what's going on. at this point other than bad NAND flash in the phone, I'm fairly clueless why it won't start up the newer twrp. if the kernel is the problem the log should show why.

I'm guessing not all of twrp successfully flashes due to weak NAND. twrp is really big and required lzma compression to even fit the recovery partition in these older devices.
[Optimus V Android Development] speck1234:
That's strange. Maybe you can build a 'Lite' TWRP for the LS670 models with the weaker NANDs; or someone somewhere might have a non-rebooting CWM that can flash yours or skinbark's CM11 without the status 0 or 7. think mine's one of them. I have flashed the TWRP 2.8.0.0, and when it rebooted I pulled the last_kmsg for you to look at attached. I had to add the .txt extension because it says Error invalid file when I upload raw files.
[Optimus V Android Development] speck1234:
Aside from that I first thought CrossBreeder was a kernel or a modification to it. I had Bobzhome's CM7 which wasn't stable on my LS670. I now run IHOs CM7 for VM670 with MiRaGe kernel on it with the LS670 conversion. It's snappy and I never had an issue. I will stay on the TWRP 2.2.2.1 (the test3 one) until you figure something out.

Both CM7s show the baseband version of LS670ZVD so I wonder if someone can try to crack open the bootloader so Fastboot functionality can be unlocked without needing a flash tool to get a working recovery and OS back.
[Optimus V Android Development] bigsupersquid:
well, drat.

the last_kmsg is from the mirage kernel rather than recovery, it seems like the newer twrp is not able to start at all on your device.

the best I could do for you with the older recoveries would be modifying the internal KitKat rom to flash with the twrp you're using. internal can't handle current play services even, because there's insufficient space on /data.

there's too many modifications to my twrp version needed to flash the os2sd rom to make the os2sd rom easily usable with an older recovery.

at this point I'd almost need your device in hand to debug why it's acting different than any other ls670 reports from back when this was a going thing., unless you get access to a computer with adb and want to play with a lot of long drawn out debug reports.

I can provide a copy of the twrp running on my devices extracted with dd to test, but that's about it.
[Optimus V Android Development] speck1234:
That'd be a great idea. I do have access to adb and fastboot via my Windows command prompt. I however did what you told me to get the last_kmsg but I didn't know that was for the kernel. It did come from /proc, so how do I get the recovery one if TWRP doesn't boot at all? Do I flash it with Flash Image GUI and THEN get the last_kmsg without rebooting? If I understand correctly memory over time degrades, the phone was introduced around 2011-2012 so my NAND might be failing. I might try to get a refurbished or brand new LS670 with a good NAND on eBay or Amazon and see if the recovery reboot problem still persists. You can still modify one of your KitKat roms or build a new one entirely to flash on my TWRP 2.2.2.1 and also modify for other people with a failing-NAND LS670 who are in the same situation as me.
[Optimus V Android Development] speck1234:
Bump. I got Cannibal Open Touch recovery working on it. I still got the same Status 0 as I did with TWRP 2.2.2.1 AND CWM. Bummer. After doing some googling I found it means wrong update-binary. If it were Amend it would be called updater-binary. There's an update-binary(Edify) in the META-INF of my CM7 MiRaGe rom and your CM11 also uses edify. If they are both edify why does it give me the status 0 then? Hmm...

If I copy the update-binary from my CM7 to the META-INF/com/google/android of your CM11 would that work?

---------- Post added at 12:38 PM ---------- Previous post was at 12:18 PM ----------

I went back and re-read your post #115 and thought it was a good idea to do what I just said above, to copy over the CM7's update-binary and change values /data to /system and /system to /data in the CM11's updater-script. BigSuperIdea!(Pun intended) My computer's not with me right now, which I totally forgot to tell you I have one now, but I'm away from home so when I get back I will edit and repack/resign the ROM, cross my fingers and hope it works. If it does I'll share the results and maybe the ROM itself. Mind if I give you credit to put my name on the zip filename so that others know I modified it? I can't find a non-TLS build anywhere so why not?

I can name it cm-11_20141014_EXPERIMENTAL_internal-bigsuperROM_old-update-binary_updater-script-mod-for-Non-TLS-kernels-by-speck1234_thunderc_signed.zip
[Optimus V Android Development] bigsupersquid:
if the ROM runs, it'll be running with TLS enabled, that is just a kernel config setting.

Every single LS670 and VM670 run with the same circuit board (the only difference is they cross-wired the home and menu buttons on the LS670 compared to the VM670,) so there's no reason that TLS is the thing killing functionality. Something is going on with either the recovery flash or the innards of your device.

as far as older recovery goes, switching system and data references in the updater-script and replacing the update-binary will probably allow the internal ROM to flash with an older edify recovery, as long as the zip isn't setting selinux contexts. if it does mess with selinux the ROM still may not boot if flashed with a recovery that can't handle selinux. that was one of the more annoying changes with kitkat.

I'll pull a copy of the twrp running on one of my optimus V's for you to test, to see if the original upload got corrupted over the years. I doubt it'll work either but it's worth a try.

the last_kmsg you got was done correctly, it's just that recovery didn't start far enough to leave even a panic log.

the LS670 has gotten pretty cheap on ebay if you wanted to try an alternate device to see if your current one has issues with flash memory.
[Optimus V Android Development] bigsupersquid:
unfortunately all but one of my vm670s no longer function. I'll have to borrow the one my child is issuing to grab recovery from it.

still, I'm pretty sure the posted image is functional under normal circumstances.
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] warmend:
Hello,

gen 8 9 10 is tablets!!

not smartphones!!

so we need a new part for smartphones on this forum

please!
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] tablet-guy:
There is not much interest for Archos devices on xda these days. :)
[One (M7) Q&A, Help & Troubleshooting] Kote811:
Hello,

Need your help

Long time no connected the phone to the PC

Now, after the connection is not detected

"Unknown device, error code 43"

On another computer, everything is fine

restart

remove drivers

used ccleaner

Remove and reinstall all USB controllers

But nothing helps.
[One (M7) Q&A, Help & Troubleshooting] clsA:
use these drivers

http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe

MD5: e2a21d71954d4164c1a116abb926a363
[One (M7) Q&A, Help & Troubleshooting] Kote811:
Not help (
[One (M7) Q&A, Help & Troubleshooting] clsA:
reinstall windows
[Ornate TrueSmart] morbeious:
I just got my Omate in the mail this morning.. I thought it should work on ATT and StraightTalk but my sim is recognized anyone have any luck with getting these networks working on the US 2g/3G 1900Mhz version?
[Ornate TrueSmart] pkshr:
Yes however make sure you insert the Sim correctly. Also the cell phone signal on the watch is poor, so you might want to make sure that you are in a good reception area too. Mine works only when I am outside of buildings and house.
[Ornate TrueSmart] morbeious:
It wont even recognized the sim chip, when I look in them sim menus its grayed out.. and I know the sim works I used the same sim from my nexus 5 which is straighttalk.. I think my omate might be faulty..
[Ornate TrueSmart] Lokifish Marz:
Page 29 of the manual shows how the SIM is to be inserted. The manual can be found in the "[INFO] Everything......" thread at the very top is this forum. This has alos been covered in multiple threads here as well as the G+ TrueSmart communities

Straight Talk APN's are not in the stock firmware. The correct apns are however in the Patch/MOD and have been for some time. I know because I'm on Straight talk on one TS and T-Mo one the other. If you have not applied the patch then I strongly suggest that you do.

High resolution images of how the SIM is to be inserted are linked below

Image 1- Orientation

Image 2- Insertion

Image 3- Inserted

Disable Quickboot in Settings/System/Accessibility

Reboot
[Ornate TrueSmart] morbeious:
Never-mind, it finally synic'ed up.. sim is being seen now.. thanks..
[Ornate TrueSmart] fyrfyter:
T-Mobile works great too. Went there for a prepaid plan today. $10 for the micro sim, and then choose your plan. Since I plan to use it very little on cellular, both the $3/day plan for unlimited everything, or $30/month for unlimited web and text, and 100 minutes, both look good for this device. Good strong signal and even works here inside my house.
[Ornate TrueSmart] hus3695:
So they just charge you $3 for each day you use it so if you use the watch 5 days out of a month they will only charge you $15?
[Ornate TrueSmart] fyrfyter:
Yup. I leave it on Airplane Mode, so it isn't drawing any data. You can still turn on wifi in this mode & use that. $3/day gives unlimited minutes, data and text for that day.

The other option is $30/month for unlimited data & text & 100 minutes.

This is all on T-Mobile's prepaid service.
[Ornate TrueSmart] eozdalga:
Wow where do you live? Tmobile in SF bay area is $50 a month prepaid for only 500MB data (limited talk/text)
[Ornate TrueSmart] Lokifish Marz:
The option is hidden. You have to buy the SIM and activate it online.
[Ornate TrueSmart] eozdalga:
Really!? Wow [MENTION=3795702]Lokifish Marz[/MENTION], the number of times you've helped me in the last 24 hours is countless. Thanks for everything!
[Ornate TrueSmart] fyrfyter:
I didn't have to. I live in Cincinnati, OH. I walked into the store and told them what I wanted to do. They were fine with it. Prepaid plans is where it's listed, and it shows up in their computer system. Paid for the card and put $50 into my prepaid account. Punched my IMEI into their system. They called customer care to make sure it was setup correctly. Done.
[Ornate TrueSmart] trent999:
This $30 prepaid plan from T-Mobile is what I use in my TrueSmart. It provides 5gigs of high speed data (which includes LTE on my Nexus5, but only 3G H max on the TS), then drops to unlimited Edge I think. Hard to run through 5gigs to test.

This used to be known as the Walmart Plan, but is now available via the T-Mobile website somewhere. The $3 per day plan might be better if you need a lot of talk time. My particular TS works great as a phone - no voice quality issues either end.

---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------

I did not need to have my TrueSmart imei recorded by T-Mobile. I took my already activated sim out of my Nexus4 and inserted it into my TS and it started working fine immediately.
[Galaxy S 4 Themes and Apps] kefir:
This mod will modify your build.prop to include two new values

persist.sys.screen_on=none

persist.sys.screen_off=crt

Is not my work

It is His work: http://www.ress.at/profil/member3.html

I put it only in the zip file :D
[Galaxy S 4 Themes and Apps] mjaquino1989:
I flash this using cwm but after restarted still no crt effect.
[Galaxy S 4 Themes and Apps] kefir:
its only for Deodexed Roms... Sorry
[Galaxy S 4 Themes and Apps] mjaquino1989:
Ah Okey sir that was the reason. I hope somebody do it for odex type.
[Galaxy S 4 Themes and Apps] royal_eagle:
It doesn't work with omega V18
[Galaxy S 4 Themes and Apps] Carotix:
works fine in my rom ... thanks
[Galaxy S 4 Themes and Apps] mom4ence:
NB9 ?
[Galaxy S 4 Themes and Apps] KALI2000:
Not work on nb8 next stock.

Enviado desde mi GT-I9505
[Galaxy S 4 Themes and Apps] kefir:
Should also work ...

both have the same Change List...
[Galaxy S 4 Themes and Apps] manysto:
hello I have kitkat 4.4.2 FNB8 with DOMINATION*v1.9.1*AOSP* theme will work ([MOD] CRT-Off Animation XXUFNB8)
[Xperia SP Q&A, Help & Troubleshooting] jimladen:
I need help.Every time I boot my phone busybox goes back to old binary 1.20 and I have to update to 1.22.1. And when I boot from recovery I get a massage the root maybe lost. I am on advanced kernel,and on ultimate xsp v1.01.
[Xperia SP Q&A, Help & Troubleshooting] Schokonuss:
Do you install BuysBox with FlashTool? If not, try and maybe it keeps.

The message that the root maybe gets lost you can ignore. select "Go back" or "No". I read this is normal since Android 4.3 (or only in 4.3(.1)?!). I get that message too and I never lost root. I prefer selecting "Go back" ;)
[Xperia SP Q&A, Help & Troubleshooting] jimladen:
Can you explain how to do this?
[Xperia SP Q&A, Help & Troubleshooting] Schokonuss:
Plug your phone into your computer and start FlashTool. If you don't have it download it here: www.flashtool.net

After FlashTool recognized your phone go on "My device" (or similar, it is the second option in the menu in FlashTool) and then go to busybox and check the newest one. It'll install it ;)

Gesendet von meinem Sony Xperia SP C5303