Develop Bugs

PLEASE HELP to revive dead e-ten. HAVE MERCY!

Hi guys. I know I know, wrong place, but maybe some one here could help too! Just maybe.. You guys are very smart peps here. You've helped me with many XDA's I own. And I'm just hoping you wouldn't let me down this time too. Any way I’ve killed my eten (typhoon my guide m500 German) and hoping some one could help me to bring it back to life. Please understand that I have exhausted all my resources in order to find the solution my self but came up empty handed. I have read every single post in this forum as well as few others in order to find the solution. And now I am hoping that some one could help. I may have overlooked some little but important piece of info. Please except my apologies if this request may be annoying.
This is what happened and what I’ve done about it.
I’ve got Typhoon MyGuide m500 (E-Ten m500) Original rom was German.
The reason I say “was” is since I had german OS that I can’t read it I wanted to flash the device with WWE Rom. But the device would not accept any other rom and at the time of reflashing through RUU, I get message “the os image is not compatible with your device”. I understand a lot of people have this problem, but still, some succeed. I have tried all the possible roms that are available there. I’m sure you’ve heard that before too Finally I’ve succeeded in flashing CHT WM2003 rom that came with WM 5 Rom update for downgrade purposes. But, I can’t read chinese either so I tried to flash wwe at this time. Hoping that chinese rom would allow upgrades in different language. But the upgrade went bad I’ve ended up with formatted e-ten with no OS installed. It was only showing white screen when turned on or it would boot into boot loader when soft reset and power was pressed.
At that time, since the device would not boot and I couldn’t active sync it, I’ve tried SD flashing with RescueDLX.bin. As well USB download utility. It flashed the device, but I was stuck at the green m500 screen when tried booting. So that didn’t work either. I’ve tried SD flashing with temp.dat saved as .bin from all possible roms, including the first chineese that worked once for me. But again, I got “the os image is not compatible with your device”
Well, here is where I’ve screwed up big time. Since the rescueDLX.bin was actually flashing into my device, and I was not getting “the os image is not compatible with your device” message, I’ve opened the rescueDLX.bin with Hex Editor, copied first 400 bytes of the header, then using Hex Editor opened the temp.dat from WWE rom update that I wanted to use and pasted this 400 bytes from rescuedlx.bin over the first 400 bytes of temp.dat file and saved it as a bin. Then copied on SD card, put it in the device, entered into the boot loader and started flashing process. Amazingly, I didn’t get the “the os image is not compatible with your device” message! But worst thing happened The boot loader was going through all the check lists and everything was ok but device froze at the last one, “looking for FPTP” or something like that.. Apperantly I copied to much stuff or it just plain incompatible. Well, now my device would not even load into the boot loader! I think I’ve erased it too So no more updating for me, that is for a sure not through RUU, not through USB Update Utility that I found on etens forum, and not even through SD with devices internal boot loader. There isn’t one anymore
So here we go, I’ve got really nice looking paper weight Oh, and I can use it as a flash light too When turned on, the screen lights up with bright white light
So any way, can any body help?! Is there any way to revive this thing? Or the road is straight to manufacturer? I don’t think I even have a warranty on this device; it’s in brand new condition, but its second hand. So I have only one hope that some smart gurus of this forum would show mercy and would help! Like I said, I’ve researched all over the internet, all forums, even xda developers and spv developers forums, but this is different device. Deferent rules… But I know it’s doable, I’ve seen posts that others did it! So please, share how you guys did it!
Thank you in advance. And sorry for such a long post!

[Q] Unable to access hidden menu [On Custom Rom]

Hello all! I've been an avid fan of the site for years now and a long time lurker.
So I recently bought a D855 International Version LG G3. Proceeded to root it, then installed TWRP, then the Resurrection ROM and gapps.
Now, I need to access the hidden service menu.. which I was able to do before (on the stock LG firmware). Problem is.. none of the codes work :crying:
When I type them into the dialer (I realize mine should be 3845#*855#).. nothing happens.. And if I press call.. it properly gives me an error.
I saw in another thread that the menu should still work under custom roms.. so, what is going on here? I would appreciate any and all input.
My best regards and thanks!
Albert

Stock rom Lg k10 K430TV.

Hello people!
So I got a Lg K10 and he gave Infinite Loop, alone, out of nowhere, he hung up, and when it came time to call again, he did not come back.
I'm trying to recover the ROM stock, however, I could not see the model in time, and behind the battery, it's not written.
After so many searches, I discovered that it is the K430TV, I went to download, but I came across some variants:
K430TV10r_00_0422.kdz
K430TV10t_00_0628.kdz
K430TV10y_00_0820.kdz
K430TV11g_00_1222.kdz
K430TV11h_00_0316.kdz
K430TV11i_00_0426.kdz
K430TV11j_00_0605.kdz
Can anyone tell me if there is any difference, if any, which ones?
Hugs

To find out the correct version, use LGUP software, and it will show you the correct version.
I have the same problem, but the correct version for my device is K430TV11v and there is nowhere to download. :crying:
Does anyone have?

Help with a unsupported build

I've been trying to figure this out for a while, and I have made some headway but I think I need to make custom build. If anyone could point me in a direction, it would be super helpful. I have a few ELO ESY15i1 android computers. They are EOL now, and only supported up to kitkat. ELO does not release their kernel source, but I do have their peripherals.
This is how far I have got with this thing, and what I was able to do/determine.
After a bunch of digging, I'm pretty sure that this thing is just a modified S4 i9505. Hardware specs seem to match, outside of the CPU only being 1.7 instead of 1.9ghz. I'm *assuming* that they have down clocked it maybe? The first unit I was working with, apparently had a bricked recovery (had bough it 2nd hand). I was able to boot it into TWRP using the jfltexx image, but I would get no picture. I know it was booted because I could access TWRP via cmd, and it was giving me responses back.
I was able to root it in a very round about way. Since I do not have any volume buttons, I'm limited to adb etc. I was able to root it with iRoot, convert that to supersu, and eventually get flashfire to install. I could finally access almost everything I needed. At some point, I got it stuck in a mode where "QHUSB_DLOAD" was shown to me, with a folder called "image" which I took a copy of. Any google results with that, was just people who had bricked their device, I was able to boot in and out of this, so I'm not sure what was going on or broken.
Here is what the device props listed out: hXXps://pastebin.XXX/FtgQ0DUE
This is the mobilodin report: hXXps://pastebin.XXX/BZrDAFg4
Finally, the "image" I copied: hXXps://anonfiles.XXX/lcQ7RfJ8o0/ESY15i1-image_rar
(sorry can't post links)
The first unit I was working on, I gave to a buddy to mess around with. The 2nd one I have, I have now bricked and it is officially stuck in the "QHUSB_DLOAD" mode. I made a poor choice, and modified the i9505 "updater-script" in lineage-17.1-20200723-nightly-jfltexx-signed to include my "msm8960" device. I flashed it via FlashFire which did go through, just bricked me in the process.
I had a samsung download jig, but I can't find it anywhere, so I have a new one on order. I'm too lazy to cut up a micro usb plug and make one. I have yet to get odin to recognize it at all, or get it into download mode. When I try over adb, it will reboot, try to go in some mode, then reboot again back to the rom.
Any input / help would be greatly appreciated. These machines are super cheap on ebay, the only problem is being stuck on kitkat. I can think of loads of things to use these for, doesn't look like anyone has tried to do anything with them. From all my searching I just found one guy who was trying to root one, and that was about it.

Hi,
I have one 22 inch unit, which I'd like to use with monitoring system and some else, but I need android version with multi windows support, so I'd like to ask you if you succeed with installing new ROM ?
Thanks in advance for reply
Maciek

Well, I've been dinking around with it again, I think I have the HW figured out. I'm pretty sure it's an LG Optimus G, LGE970 is what I'm trying.
I was able to take the stock "ATT-Stock-E97020j" non KDZ zip, pull the boot.img off of it, and flash that.
Now when I connect to my computer, I'm getting LGE Androidnet for Diagnostics, and LGE Androidnet USB serial, as 2 devices.
Just keeps hanging right away when I try and flash the KDZ.

LG G4 Bricked? Attempt to install alternate Mobile OS

Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock

Lilrock said:
Greetings,
General
I've been all over the Internet trying to gain access to more information about how to repair my LG G4. Well... Let's start from the beginning.
Story
I have an LG G4, it's old and I've had it for over 4-5 years now... I can't exactly remember how long I had it for. It still works, just needs a new battery and cable (cats chewed the cable and batteries don't last when you forget to disconnect them from the device, leave it plugged in for weeks and let it completely die for longer then a week).
I recently saw a video about the Pine phone and the fact that it was able to run a linux mobile distribution and when I looked into installing a custom OS into LG G4, it was possible... If I manually ported it myself.
I actually got fairly far using my Xubuntu system with configuring and compiling, the trouble I ran into was that I couldn't root or fastboot my device.
So, now here's where the problem began, I have a LG G4 factory reset and when I load up the Recovery mode, it brings up the android guy with their chest open and an exclamation mark in a yellow triangle, no message. After attempting to boot into recovery mode, I wait a little while and the phone automatically resets back to normal. When I use ADB to force the phone into fast boot, it skips it and starts the phone normally.
Now I'm on a mission to find a way to either fix the boot or flash the firmware (in hopes that it fixes the boot/recovery).
I have already tried:
Installing LGFlashTool
Versions, 2.0.1.6, 2.0.1.9, Year: 2014 and 2.0.2.5. Other than year 2014, the other ones were installed from LGFlashTool.com
Since Xubuntu can't run these files properly, I just ran them on my wife's Windows computer
I installed the LG Mobile Drivers and LGFlashTool had registered that it was the correct DLL but, it didn't seem to find the phone
Year 2014 LGFlashTool had found the phone but, I may have had the incorrect kdz file.
The Flash starts and the phone goes to firmware update, but the phone stops at zero and sits there while the program crashes saying that there was an error (in which no means to read, understand or locate the description of this error) and to try again by unplugging and removing the battery.
This version was downloaded from xda-developers.com
Conclusion
Once I can get into fastboot, I'll be able to root my phone and attempt to install the mobile OS I have ready.
Otherwise, I think I might be able to install a microSD card with the OS but, I don't think that will work if I can't get into the option to boot from a separate location (I believe that's called fastboot). But, then again... I think the phone needs to be rooted first... Then that brings me to the previous issue.
Details and Information
The phone details (as far as I see) are:
When I remove the battery I can see:
FCC ID: ZMFH810
IC ID: 2703C-H812
Model Number: LG-H812
I'm not exactly sure what KDZ file I got but the name is: PR H810PR10a_02.kdz, I also have the _04.kdz
I'm using H815 as my compile for the mobile OS, I may switch to H810 when I get back to that point.
Useless information: I still have the original leather backing... Removed from the phone because I didn't like it. If I find it, I can ship it to someone.
That's about it... I am very terrible about research and using Google properly (I have no idea why, I think it's a terrible flaw to have but, I have it). So, if you find the solution by typing words I didn't use or finding a similar post, I am very sorry. Hope I have everything posted here to help solve the issue, linking to posts that can resolve the issue or posting questions on what I might be missing will help.
Thanks in advance for the support of this community,
Lilrock
Click to expand...
Click to collapse
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.

steadfasterX said:
Well first of all you need to unlock your phone. H812 can't be unlocked officially though. Check my sig for the only unofficial one. Once unlocked you can flash custom ROMs but first of all you should read about ARB (antirollback) also in my sig and ensure you understand the risks all this brings. Gl.
Click to expand...
Click to collapse
Thanks for the positive feedback, I will attempt to fix my phone with your solution. This phone is technically almost garbage and when I fully update the phone, it runs like trash. So, if I can install a custom ROM, it may run a little better or have the tools I would personally like in a phone.
I'll let you know the details of my attempt,
Lilrock

You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.

SkewedZeppelin said:
You might be able to use:
GitHub - Lekensteyn/lglaf: LG Download Mode utility and documentation
LG Download Mode utility and documentation. Contribute to Lekensteyn/lglaf development by creating an account on GitHub.
github.com
It is more reliable then the factory tools when it works.
Click to expand...
Click to collapse
Which is included in mAid (https://maid.binbash.rocks).. ... Even with a UI...

Thank you very much with your support. I was able to unlock, bootloader and install the image installer.
I'm on the verge of compiling and installing Ubuntu Touch on my LG G4 H812.
Hope you guys proceed with everything you're doing right!