Related
Hello. i want to ask if someone have Clockwork mod or some custom firmware on Prestigio PMP5670c Android 4.1.1.
I managed to root it, but i realy dont like this Android version and Prestigio is not intrested in upgrading.
Hey can someone make a recovery for this tablet.
Sent from my PMP5670C_DUO using xda premium
Shawes said:
Hello. i want to ask if someone have Clockwork mod or some custom firmware on Prestigio PMP5670c Android 4.1.1.
I managed to root it, but i realy dont like this Android version and Prestigio is not intrested in upgrading.
Click to expand...
Click to collapse
I started to do some work on that tabled, but stuck with kernel touchscreen configuration. See here.
Touch chip is Goodix GT911, screen size is 800x1280 px. I managed to get touch working but partialls. First aprox 1.2 inches of top of screen are not responsive to to touches. After that 1.5" touch works normally.
I'm pretty sure I'm sending wrong configuration data array to chip and thats why its not working as it should, but have no time at the moment to toy with it. If anyone experienced with Goodix chips, pm me with ideas...
stane1983 said:
I started to do some work on that tabled, but stuck with kernel touchscreen configuration. See here.
Touch chip is Goodix GT911, screen size is 800x1280 px. I managed to get touch working but partialls. First aprox 1.2 inches of top of screen are not responsive to to touches. After that 1.5" touch works normally.
I'm pretty sure I'm sending wrong configuration data array to chip and thats why its not working as it should, but have no time at the moment to toy with it. If anyone experienced with Goodix chips, pm me with ideas...
Click to expand...
Click to collapse
Update: I started to toy with stock kernel and cm10.2 (my first CM ever, was working with AOSP based SoC manufacturers sources). Problem is that device uses separate partition for internal sdcard, so have to disable emulated storage.
Things done:
- recovery
- android is built against precompiled stock kernel
Status:
- after bootanim and starting apps screen android reboots and starts back with bootanim. This was one day tryout, will debug it later today. Thanx to TeamNostalgia's preparation for cm10.2 on Amlogic MX. I used their framework and device stuff, upgraded with latest amlogic version of sources. Because of SLA I have with Amlogic, I cannot put it online.
any news abouth root final this tablet?
thx for info
stane1983 said:
I started to do some work on that tabled, but stuck with kernel touchscreen configuration. See here.
Click to expand...
Click to collapse
klobasica said:
any news abouth root final this tablet?
thx for info
Click to expand...
Click to collapse
On the link abouve is posted rooted stock firmware (mine post). To lazy ones click here
no, no...sorry i mean custom rom if is posable to create for this tablet...
klobasica said:
no, no...sorry i mean custom rom if is posable to create for this tablet...
Click to expand...
Click to collapse
It is. I'm not CM guy really, but its possible. If anyone interested, TeamNostalgia's github does have decent tree for Amlogic MXS tablets. I did some CM10.2 work for that tablet, but ended up with bootloop and reboot eventually. Didn't had time do debug it.
Here 4pda.ru/forum/index.php?showtopic=504411&view=findpost&p=29560411 is a customized firmware from Prestigio PMP3970B to work on Prestigio PMP5670C. But it does not run on PMP5670C, stands on the splash screen. Maybe someone will take to complete the firmware, it is better factory firmware for the tablet PMP5670C
ksh2000 said:
Here 4pda.ru/forum/index.php?showtopic=504411&view=findpost&p=29560411 is a customized firmware from Prestigio PMP3970B to work on Prestigio PMP5670C. But it does not run on PMP5670C, stands on the splash screen. Maybe someone will take to complete the firmware, it is better factory firmware for the tablet PMP5670C
Click to expand...
Click to collapse
I fixed U-Boot (wrote my own to support device tree kernel - 3.10.10) and fixed touch screen. I did not upload this fw, started to work yesterday on amlogic's 4.4 sources (they support both mx and m8 chipsets) (no, I cant share, I have SLA with them), I have boot, only left few things to test and then I'll upload 4.4.2.
Thank you for keep working! Waiting for rom)
Sent from my GT-I5510 using xda app-developers app
cyanodeff said:
Thank you for keep working! Waiting for rom)
Sent from my GT-I5510 using xda app-developers app
Click to expand...
Click to collapse
Here's beta version of rom: http://www.stane1983.com/prestigio_pmp5670c/
Read install instructions, needs to be installed twice, uboot still not perfect. Waiting for feedback
Btw, it's 4.2.2 rom, KitKat doesn't work good (unstable) on MXS chip.
Installed today morning. Seems all good! Thank you very much
Sent from my GT-I5510 using Tapatalk 2
babicsbalu said:
Unfortunatelly I can not able to install it because the second install is freezing all the time, now I can not install official 1.0.0.5 ROM, it stucked during the installation.
Click to expand...
Click to collapse
Rename uImage_recovery to recovery.img (when installing back stock firmware).
babicsbalu said:
Now I successfully installed the 1.0.05 but there is a quite big issue: I can not able to install anything from Play, the Download Manager is acutally (lots of system apps too) 0.0kb
Click to expand...
Click to collapse
I'm really sorry for inconveniences. With 1.0.05 files on sdcard, delete factory_update_param.aml file and boot into recovery (as if you want to install firmware). From menu using vol +/- and power for select choose factory reset (data partition is not formatted using old partition layout, thats why you have 0kb). After that you also can reflash firmware if you want (just select zip from sdcard).
stane1983 said:
Here's beta version of rom: http://www.stane1983.com/prestigio_pmp5670c/
Read install instructions, needs to be installed twice, uboot still not perfect. Waiting for feedback
Btw, it's 4.2.2 rom, KitKat doesn't work good (unstable) on MXS chip.
Click to expand...
Click to collapse
My daughter get this tablet from her grandfather on 03.05.2014 ( I guess she is lucky about that date ), and it was so slow and ugly and everything.
I installed your bety rom and everything is perfect. BUt after first reboot i get setup wizard again, but the first time after Install I only get FC ( just like I should ) but it didnt throw me back to setup wizard again.
Can I expect wizard setup every time I reboot or?
And Yes, thank you a lot for this awesome and fast work. The tablet is now so much more usable.
HVALA TI STANE MNOGO => THANK YOU STANE A LOT
@stane1983 I have the same problem as @babicsbalu. My pmp5670c is also stuck at black screen after rebooting and installing new stock firmware. I did both, renaming from uImage_recovery to recovery.img and deleting factory_update_param.aml and every time with the same result.
Please help me!
Or you can PM me (I'm from Croatia)
Hvala ti!
Well I also have prestigio tablet pmp5670C_BK_DUO and within a week it got bricked somehow. I guess that broken charging pin on cable had something to do with it - probably did a short circuit or something and boot loader got corrupt. Tabled was responding to connection of new charging cable, but only backlight turned on. There was no logo or anything.
I browsed several pages and nothing worked. I tried with official upgrade from SD card but it didn't work. It started to upgrade, android-upgrade logo came up, but after reboot nothing happened. Damaged bootloader was unable to start the tablet.
After a day or so I finally found a way how to unbrick it! Yeah.... So in attached file there is the detailed procedure, which I found on some Russian page.
Good luck!
Recovery.rar no longer available
imarkic said:
Well I also have prestigio tablet pmp5670C_BK_DUO and within a week it got bricked somehow. I guess that broken charging pin on cable had something to do with it - probably did a short circuit or something and boot loader got corrupt. Tabled was responding to connection of new charging cable, but only backlight turned on. There was no logo or anything.
I browsed several pages and nothing worked. I tried with official upgrade from SD card but it didn't work. It started to upgrade, android-upgrade logo came up, but after reboot nothing happened. Damaged bootloader was unable to start the tablet.
After a day or so I finally found a way how to unbrick it! Yeah.... So in attached file there is the detailed procedure, which I found on some Russian page.
Good luck!
Click to expand...
Click to collapse
I had a similar problem here and this method seems promising, but the recovery file indicated on the PDF is no longer available. Would you still have it lying around somewhere?
Thank you!!
PMP5670c Duo
I got this tablet 2 month ago, i have found on w w w 4pda ru 4 custom rooms for this tablet and i used google chrome to translate in english to understand what i have to do, i have instaled every one rom but i got a problem, with all custom rom the internal storage disapear. I instaled stock version now and the internal storage is there ready to be used. Custom roms are better than stock rom but it's annoyng me the missing internal storage. Anyone with this problem or anyone know how to fix it?
Edit: I instaled stock rom then i instaled again Firmware v.1.0.10 from MrCheba Repack and now i have internal storage working maybe reinstall the stock rom fix it.
This is the stock US KitKat ROM for The Galaxy Tab 3 7" Tablet. Finally found it after a bunch of hassle online, and figured I'd post it here to make things easier for everyone.
When I Odin'd this ROM, it actually upgraded my tablet, and left all my items installed (not guaranteeing this will work the same for everyone else).
Afterwards, I just Odin'd TWRP to reroot using Chainfire's SuperSU (no other Superuser would work) and called it good.
Caution: if you are using a custom ROM, this may not work without reflashing stock 4.1.2 since the 4.4.2 ROM appears to be an update, rather than a full ROM.
Rooted devices and custom kernels that are otherwise stock should be fine.
The cache, and if possible dalvik-cache should be cleared before flashing. Some of those files can sometimes interfere with upgrades.
It might be necessary to pinpoint apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
If that fails, it might be necessary to factory reset the device.
The Stock 4.1.2 ROM for the T210R is available here: http://forum.xda-developers.com/gal...-stock-sm-t210r-4-1-2-jellybean-odin-t2958676
The T210R...XAR file is for the 210R:
https://drive.google.com/open?id=0B2iEgzRTFjrQTmI0ZjRBbWtOajQ&authuser=0
The ITV file is for the T210 (no R)
To download these ROMs, a torrent client is required (such as utorrent).
Anyone who wishes to contribute, please seed if you can after downloading ("Force Starting" the torrent will seed it indefinitely.)
Can I flash this on the SM-T210?
john410 said:
Can I flash this on the SM-T210?
Click to expand...
Click to collapse
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.
Greaper88 said:
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.
Click to expand...
Click to collapse
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?
[email protected] said:
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?
Click to expand...
Click to collapse
I did not have this problem, but I didn't have much on my Tab either. (Some apps don't play well with KitKat upgrades.)
Torrents have multiple segmented hashchecks to make sure you get an uncorrupted download, but it might still be possible. I'm reasonably sure my file is OK since I've used it (can't speak for the non R file though).
Did you clear your cache, and if possible your dalvik cache? I've read that some of those files interfere with upgrades.
If you can pinpoint the apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
Other option would be to try a factory reset and see if that fixes it. (I understand not wanting to do that though.)
One more thing, if your ROM isn't stock, or stock rooted (custom kernel should be ok too), you may have to flash 4.2 before the 4.4 ROM will work on the device.
Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught
void.naught said:
Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught
Click to expand...
Click to collapse
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.
thank you for finding and posting the correct files for this tab
hi i have a galaxy tab kid t2105 rooted, is it possible to install any other rom after 4.1.2?
Greaper88 said:
Rooted devices and custom kernels that are otherwise stock should be fine.
Click to expand...
Click to collapse
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J
ubuntujason said:
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J
Click to expand...
Click to collapse
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.
Greaper88 said:
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.
Click to expand...
Click to collapse
Awesome, thanks!
~J
Could you upload the T210 ITV file? This torrent is going to take 10 hours
No system file
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.
Sorry, m'y post an error
ragnaroksangel said:
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.
Click to expand...
Click to collapse
Are you looking for the Stock Rom?
Darthlord064 said:
Are you looking for the Stock Rom?
Click to expand...
Click to collapse
I am, can you help?
Greaper88 said:
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.
Click to expand...
Click to collapse
For some (unknown) reason, Odin3 nor JOdin3 doesn't seem to work for flashing my Samsung Galaxy Tab3 device. For that reason I tried Heimdall-Frontend, but to make that work you need to extract the content of a stock ROM first.
Anyways, it still didn't lead to get my device into factory reset yet.
But that's another story on which I still have not yet found the answers needed to get the device successfully back into factory reset.
My guess is that the 'system.img' file, of Android 4.4.2, successfully has been loaded from Heimdall-Frontend, yet by going into reboot right away after Heimdall-Frontend releases the connected device, the download may be deleted.
I read that the cause of that may lie in the fact that Android 4.4.2 is only an update and no full ROM.
This is a WW SKU ROM with custom Kernel based on the latest ASUS stock firmware. It has been pre-rooted, zipaligned and debloated. The ROM has busybox, some added applications and minor tweaks.
Some of the things removed
ASUS Browser
Asus Email
Asus Setup Wizard
Asus Story
File Manager
Kindle
Omlet
Press Reader
What's Next
Zinio
... and more
... and even more (r150131)
Things added
Latest SuperSu
Total Commander (replaces the ASUS file manager)
The good old ASUS Tree
Day Scene live wallpaper
The new Pixelmaster Camera (r150131)
RootDim (r150301)
Features
The ROM will not touch your custom recovery, plus it installs over any previous ROM
eMMc fstrimmed during setup
Mobile data is now disabled by default
Auto-wipe dalvik cache (r150131)
Default CPU governor is now Interactive (r150301)
Minimum brightness lowered to 1 in kernel (plays nicely with Rootdim) (r150301)
How to install
Make sure your phone is unlocked
Flash CWM recovery 6.0.2.9
Boot into recovery mode
Select "wipe data/factory reset"
Select "install zip from sideload" (my preferred), or "install from zip" (if you have copied the ROM previously to the root of your phone)
Wait until it says it's done, then reboot* (see next section below)
Wait some more until it configures itself for the first time
*Fairly relevant
When CWM asks "ROM may flash stock rocovery on boot. Fix?" Choose "No"
When CWM asks "ROM access possibly lost. Fix?" Choose "No"
Downloads
CWM 6.0.2.9
Tari's ASUS PadFone 2 ROM+KERNEL (KitKat 4.4.2 r150301)
tari01 said:
[*]The ROM will not touch your custom recovery, plus it installs over any previous ROM
Click to expand...
Click to collapse
so i can install this over the GuerillaROM (4.1.1) from SiSSiDroid??
BPM said:
so i can install this over the GuerillaROM (4.1.1) from SiSSiDroid??
Click to expand...
Click to collapse
I see no reason why you couldn't. I only advise you to flash the CWM recovery first, then do all the wiping as mentioned (note that this will be a clean install, so back up anything of importance to you).
If you are paranoid enough (this generally applies to any ROM installation), you can enter CWM, and mount + format ALL the partitions you see there one-by-one. After this (rather extreme preventive measure) boot into recovery again and do whatever you wish.
Please do tell me about you installation experience, so others could learn, and I could improve the instructions.
tari01 said:
I see no reason why you couldn't. I only advise you to flash the CWM recovery first, then do all the wiping as mentioned (note that this will be a clean install, so back up anything of importance to you).
If you are paranoid enough (this generally applies to any ROM installation), you can enter CWM, and mount + format ALL the partitions you see there one-by-one. After this (rather extreme preventive measure) boot into recovery again and do whatever you wish.
Please do tell me about you installation experience, so others could learn, and I could improve the instructions.
Click to expand...
Click to collapse
flashing works without problems. do not forget to wipe dalvik cache because device will hang on boot if you forgot this!!
its not my primary device any more so i have not really test it now.
will test a bit more and report back.
want to sell my device and have to be sure that everything works without problems
Finally a custom kitkat rom for our Padfone 2!
I am on the latest stock kitkat version of the device. I really want to test your rom, but i am a noob and have no experience on flashing the device. I tried to flash CWM using fastboot as a first step, but i am failing.
Do i need to unlock or root the device first ?
impact79 said:
Finally a custom kitkat rom for our Padfone 2!
I am on the latest stock kitkat version of the device. I really want to test your rom, but i am a noob and have no experience on flashing the device. I tried to flash CWM using fastboot as a first step, but i am failing.
Do i need to unlock or root the device first ?
Click to expand...
Click to collapse
Yes, custom recoveries/ROMs can only be flashed onto unlocked devices.
tari01 said:
Yes, custom recoveries/ROMs can only be flashed onto unlocked devices.
Click to expand...
Click to collapse
Whats the easiest way to unlock the device? Mine is under latest kit kat and rooted.
Thanks in advance!
rafael_mfr said:
Whats the easiest way to unlock the device? Mine is under latest kit kat and rooted.
Thanks in advance!
Click to expand...
Click to collapse
See this post.
tari01 said:
See this post.
Click to expand...
Click to collapse
I just managed to unlock my bootloader on kitkat WW11.8.4.23 using just the Asus UnLock.apk after I changed my GMail "less secure app settings" without any difficulties!
Then I easily flashed CWM using fastboot. I'm going to flash your rom as soon as I download it. Thanks.
ansarijavid said:
I just managed to unlock my bootloader on kitkat WW11.8.4.23 using just the Asus UnLock.apk after I changed my GMail "less secure app settings" without any difficulties!
Then I easily flashed CWM using fastboot. I'm going to flash your rom as soon as I download it. Thanks.
Click to expand...
Click to collapse
Wow. That is very good news. If you have the time, you could go to the other thread and post step-by-step instructions in case somebody is interested. Thanks for sharing this.
tari01 said:
Wow. That is very good news. If you have the time, you could go to the other thread and post step-by-step instructions in case somebody is interested. Thanks for sharing this.
Click to expand...
Click to collapse
I just downloaded the UnLock.apk here: http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone2/UnLock.zip
What I did was simply as follows:
1. Installed UnLock.apk and ran it.
2. Accepted warnings.
3. Inserted my gmail password (it automatically identified my account).
4. It failed with the "not valid password message.
5. In my gmail inbox, I got a message that gmail had blocked access from "less secure app", of course UnLock.apk!
6. I followed a link in the gmail message and changed the settings so that "less secure apps" could access my account.
7. I repeated steps 2 and 3 again, this time my phone restarted quickly, on the bootloader, I got a message that bootloader was "Unlocked".
8. then I downloaded the CWM you provided and flashed it (fastboot flash recovery cwm.img) in CMD.
@tari01,
I wondered if this thread is still monitored. I have a problem with my Padfone 2 and I wondered if you could help me...
gentle_giant said:
@tari01,
I wondered if this thread is still monitored. I have a problem with my Padfone 2 and I wondered if you could help me...
Click to expand...
Click to collapse
Well, I get E-mail notifications and I still own a PadFone 2 - so I guess the answer is yes. Whether I can help you remains to be seen
great, perhaps you can help me further.
It is only indirect related to this tread. My Padfone 2 was soft-bricked, I found this tread, followed the instructions, the ROM starts up well but if I restart it the same old thing. It stops at the boot logo and stays there.
using CWM I can see that every time after a restart, in recovery, /data, /sdcard, /system, /persist and /tombstone are not mounted.
Perhaps this is normal when in discovery, anyway, I can mount all the items except /sdcard.
In CWM I can also see warnings:
E: can't open /cache/recovery/log
what could be going wrong?
gentle_giant said:
great, perhaps you can help me further.
It is only indirect related to this tread. My Padfone 2 was soft-bricked, I found this tread, followed the instructions, the ROM starts up well but if I restart it the same old thing. It stops at the boot logo and stays there.
using CWM I can see that every time after a restart, in recovery, /data, /sdcard, /system, /persist and /tombstone are not mounted.
Perhaps this is normal when in discovery, anyway, I can mount all the items except /sdcard.
In CWM I can also see warnings:
E: can't open /cache/recovery/log
what could be going wrong?
Click to expand...
Click to collapse
I think this could be beyond me, but I can give you a few pointers. If you are planning to flash "my" Kernel and ROM:
- Make sure every file is from the links I provided
- Start the whole flashing thing all over again from the first step
- After CWM is installed, try to format EVERY partition you can find
- If your phone is not unlocked and the motherboard has been serviced, all sorts of things could go wrong
- Note that the ROM is based on the WW firmware, make sure your phone is the same
- Do not use Linux live sessions for flashing - use a full instalation
That's about it. I really can't think of anything clever to add - I hope it helps you somewhat.
thanks for the info Tari01.
the first 3 points were done as per instructions. I formatted all partitions twice on two separate occasions.
As far as I know the phone is unlocked but I didn't use the unlock app after I tried to flash your ROM, or any other ROM for that matter.
But once unlocked it stays unlocked isn't it? I mean, I can flash any recovery.
The second last point: I'm aware of this. I always choose WWE based roms.
your last point: I don't know anything about Linux command lines etc. As a matter of fact, when I use ADB or fastboot I just go through the motions as per instructions but I hardly know what I'm doing.
On the bright side; I'm most likely not the only one.
I will use this phone solely as a learning devices for better understanding of the Android platform and ADB etc.,...
@tari01 - greetings and thanks for a wonderful custom ROM - I have just flashed it and it seems very stable for now.
Two questions though - did you remove the Audio Wizard from the stock ASUS ROM? Don't know 'bout you, but I think the sound was more "vibrant" when docked into the tablet when using a Stock ROM (but the stock rom was more unstable, I have NO IDEA why - gapps/android.system/everything kept crashing after a few hours).
Second, is your custom ROM compatible with Stone Kernel? I would like to try it out (OC version, because, overclock, why not? )
Thanks in advance for a cool ROM, and I shall await your reply.
tassadaru said:
@tari01did you remove the Audio Wizard from the stock ASUS ROM? Don't know 'bout you, but I think the sound was more "vibrant" when docked into the tablet when using a Stock ROM
Click to expand...
Click to collapse
I removed the Audio Wizard because I saw it as unnecessary bloatware. I doubt it would make any difference, since it only changed audio profiles. I use Rocket Player for music and BS and MX Player for video: all these can be tuned to sound as you like.
tassadaru said:
@tari01is your custom ROM compatible with Stone Kernel? I would like to try it out (OC version, because, overclock, why not? )
Click to expand...
Click to collapse
I am not sure what would happen if you used an older kernel. In the one that I've built , the CPU governor is not set in stone: If you want to use another one, there are many apps in the Play Store that will allow you to change it, and you can also set the desired frequencies. Note, that of all the CPU governors the one that I set proved to be the most efficient - it runs on a single core when you don't need CPU power, then, as applications request more power, it activates the entire CPU and delivers as much as it can - all this saves a lot of battery power. Overclocking will definitely drain your battery much faster, and I'm not sure you'd get noticeable performance.
@tari01 - thank you for the quick reply and the info provided. I am replying because, as I said, I encountered problems when using stock 4.4.2 - it seems your ROM is not exempt from those problems.
To be more specific, everything on my home screen disappears completely, only the live wallpaper remains, then when I try to open any app from the apps menu, com.google.process.gapps and android.process.acore keep crashing (Unfortunately, xxx has stopped message).
This happens after the phone/tablet is in idle for a few hours (as far as I could test it). I tried wiping cache, etc, but to no avail.
Android 4.1.1 does not have this issue, but the phone/tablet moves like an earthworm compared to 4.4.2 and support is limited.
Any ideas/pointers? I flashed your ROM over a stock 4.4.2 using the images you provided, and using the instructions you provided.
Thank you in advance!
tassadaru said:
@tari01 - thank you for the quick reply and the info provided. I am replying because, as I said, I encountered problems when using stock 4.4.2 - it seems your ROM is not exempt from those problems.
To be more specific, everything on my home screen disappears completely, only the live wallpaper remains, then when I try to open any app from the apps menu, com.google.process.gapps and android.process.acore keep crashing (Unfortunately, xxx has stopped message).
This happens after the phone/tablet is in idle for a few hours (as far as I could test it). I tried wiping cache, etc, but to no avail.
Android 4.1.1 does not have this issue, but the phone/tablet moves like an earthworm compared to 4.4.2 and support is limited.
Any ideas/pointers? I flashed your ROM over a stock 4.4.2 using the images you provided, and using the instructions you provided.
Thank you in advance!
Click to expand...
Click to collapse
Well, I'm afraid this seems to be out of my league. I'm still using my PF2 (in fact, it's my only phone/tablet), but I have no issues with it. Perhaps the only thing worth mentioning is that I don't use live wallpapers, I let my apps regularly update via Wi-Fi, and that I have a hacked Play Store. The rest is pretty much the same as you'd find it after flashing the ROM. I really have no idea what could be causing the errors you get
NOTE: If you've tried to download this ROM before and Google Drive didn't let you access it, I have reuploaded the ROM directly to this post​
First, the usual disclaimer:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
About the ROM
This is a build of LineageOS 14.1 (Nougat) for the Samsung Galaxy SL (GT-I9003)
Things to take a note of
This ROM is still a Work In Progress. As such, some features do not work, as listed ahead
Make sure you keep a backup of your files. This update WILL wipe every partition (/system, /cache, /data, /sdcard).
IMPORTANT: Returning to an older ROM is non-trivial because this update applies a different partitioning scheme. To return to another version, flash the boot.img (possibly using heimdall or bml_over_mtd) of the ROM you wish to install, reboot to recovery, and flash.
ADB does not authenticate any requests. Hence, ensure you disable ADB if you're not a developer.
Steps to flash
Reboot to Recovery.
Wipe Data / Factory Reset.
Select the ROM zip from your SD Card and flash. It will reboot to TWRP.
Flash the ROM zip again. It WILL fail on this flash to let you go back to an older boot.img to stop installation if you wish to. Flash again to continue.
Flash GApps (OpenGApps pico package recommended).
Reboot. First boot can take 15mins or so.
NOTE: When upgrading from an older version of this ROM, it's recommended to wipe /system due to certain issues with the installer not updating the boot image correctly.
Downloads
ROM: lineage-14.1-20181008-UNOFFICIAL-galaxysl.zip Check the attachments on this post
Older version: lineage-14.1-20170826-UNOFFICIAL-galaxysl.zip
Things that work
WiFi
Bluetooth
Calling
SMS
Vibrator
Audio playback
LegacyCamera (no front camera)
Things that don't work
Adopted storage
Camera2
Mobile data
GPS
Video playback
Anything that is not explicitly listed as working
Tips and tricks
For forcing high end graphics (transparency in UI), add the following to build.prop
Code:
persist.sys.force_highendgfx=true
XDA:DevDB Information
LineageOS 7.1.2 for Samsung Galaxy SL i9003, ROM for the Samsung Galaxy SL i9003
Contributors
Technohacker1995, xc-racer99, Dheeraj CVR (@dhiru1602)
Source Code: https://github.com/Technohacker/android_device_samsung_galaxysl
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 14.1
Beta Release Date: 2017-08-26
Created 2017-08-26
Last Updated 2017-08-26
Known Issues:
Other than the above listed features not working, none as of now
Just curiosity- what is the sense in 7 android on so weak hardware?
dominatos1 said:
Just curiosity- what is the sense in 7 android on so weak hardware?
Click to expand...
Click to collapse
Just to show that it can be done, and a passion for reusing old hardware
Can someone pls enlighten me as soon as possible.....?? Is this ROM stable?? And it is written in the post that the status is given as Beta........ wt does that mean??.......Nd i did not understand......Why is it not possible to go back to an older ROM?? I need a detailed instructions (if pssble) how to get back to the previous ROM...... Currently iam using CM 11.......Can't I get back to my previous nandroid backup of this current ROM ?? pls answer this ASAP......Want to try how this ROM actually looks like on my GT-I9003......And i sincerely request someone to post the screens of this ROM pls..............
And would like to know wat is the difference btwn This Lineage ROM nd the Omni ROM....??
smsry said:
Can someone pls enlighten me as soon as possible.....?? Is this ROM stable?? And it is written in the post that the status is given as Beta........ wt does that mean??.......Nd i did not understand......Why is it not possible to go back to an older ROM?? I need a detailed instructions (if pssble) how to get back to the previous ROM...... Currently iam using CM 11.......Can't I get back to my previous nandroid backup of this current ROM ?? pls answer this ASAP......Want to try how this ROM actually looks like on my GT-I9003......And i sincerely request someone to post the screens of this ROM pls..............
And would like to know wat is the difference btwn This Lineage ROM nd the Omni ROM....??
Click to expand...
Click to collapse
You don't have to double post
This ROM is *somewhat* stable, however there are features missing (mobile data, GPS, video playback, etc.). Alpha and Beta are measures of how stable a version is (Alpha < Beta < Stable, in order of stability).
The reason you cannot go to a previous Android version is because I have repartitioned the phone's internal storage for a bigger /system partition and no internal /sdcard storage (it is now emulated storage). You can return to a previous ROM by flashing the stock ROM (to be more specific, the boot.img), rebooting to recovery and restoring your ROM backup.
I can post some screenshots soon, if needed
I started by porting Omni to our phone, to see if it was possible. Then I went for Lineage because it contains more features. So the Omni port is no longer active, It's recommended to use this LineageOS port.
Also, the Omni port uses the same partitioning format as older ROMs but at the disadvantage of having no system partition space for GApps and lesser fixes.
Cheers!
Thanks fr the reply!!!!
YES!!! i would love to see some screenshots.......
sorry but iam a noob at all this......I actually have another doubt too......
As u said that i should flash the stock rom..... here wt does a BOOT.IMG mean??
If u reply to this As soon as possible i would like to know wat all precautions should i take before flashing this rom.....
Bcoz this is the frst time iam seeing that u can't go back to the previous rom....
Usually i would take a nand. backup and test out a new rom nd then i wld go back to my previous backup......
Iam askin all these because the first time i flashed the Omni Rom a month before....... Nd i actually bricked my phone......
I got this "phone -exclamation-pc" icon everytime i try to get into BOOT mode or RECOVERY........
Then i recoverd safely after flashing the stock rom.......
Nd Instead of 7.1.2 for i9003 I would love to see 5.0 or 6.0 for this device......
Cant find any Lollipop or Marshmellow ROMS for the SL......
And i sincerely thank you for creating this NEW ROM for the SL.....
Have'nt seen any new ROMS lately after the CM11
(nd plssssss once think abt making a 5.0 ROM fr the SL.......What is ur opinion abt it......?? Iam sure it would look great on the SL.....)
Once again thank u for the reply.....
(ppl on xda surely are pretty friendly..... )
smsry said:
Thanks fr the reply!!!!
YES!!! i would love to see some screenshots.......
sorry but iam a noob at all this......I actually have another doubt too......
As u said that i should flash the stock rom..... here wt does a BOOT.IMG mean??
If u reply to this As soon as possible i would like to know wat all precautions should i take before flashing this rom.....
Bcoz this is the frst time iam seeing that u can't go back to the previous rom....
Usually i would take a nand. backup and test out a new rom nd then i wld go back to my previous backup......
Iam askin all these because the first time i flashed the Omni Rom a month before....... Nd i actually bricked my phone......
I got this "phone -exclamation-pc" icon everytime i try to get into BOOT mode or RECOVERY........
Then i recoverd safely after flashing the stock rom.......
Nd Instead of 7.1.2 for i9003 I would love to see 5.0 or 6.0 for this device......
Cant find any Lollipop or Marshmellow ROMS for the SL......
And i sincerely thank you for creating this NEW ROM for the SL.....
Have'nt seen any new ROMS lately after the CM11
(nd plssssss once think abt making a 5.0 ROM fr the SL.......What is ur opinion abt it......?? Iam sure it would look great on the SL.....)
Once again thank u for the reply.....
(ppl on xda surely are pretty friendly..... )
Click to expand...
Click to collapse
Will send screenshots soon
You can ignore that and just go ahead with flashing the stock ROM. The boot.img file is essentially the file that contains the boot code and recovery of the phone (in simplified terms)
The main precautions you should keep in mind are that the Internal SD card is now emulated, so wiping data will wipe any photos/music stored in internal storage. The safest place to keep your files are on an external SD card (keep your CM11 backup there, too)
The exclamation mark error is when the phone can't find the boot code, that might've been the ROM flash geting stopped partway. You can recover from that using Odin.
I actually did make a 5.0.2 NamelessROM build, but it's not very usable as such. Lollipop had an issue which used up phone RAM too much. Our phone having 512MB of RAM just made it worse. In between I was away on other tasks and so, by the time I returned, Nougat was latest. Hence, it didn't make sense (atleast to me ) to make a Marshmallow ROM when Nougat was the one in development.
You're welcome
As said above, a 5.0.2 build exists, which isn't very usable. A Marshmallow ROM doesn't exist for our phone but if one wishes to build CyanogenMod 13.0 for our device, I can give help
XDA and other internet forums are not all that friendly, just make sure you follow the rules of the forum
Cheers!
i need stable recovery for i9003
adm_83 said:
i need stable recovery for i9003
Click to expand...
Click to collapse
In the i9003 and other Samsung devices, the recovery is part of the boot partition. You can't switch recoveries independently of the current ROM (unless the main reason you want the recovery is just for the recovery or you patch the boot.img)
If you want to run a recovery, you have to get the boot.img file (taken from a ROM or otherwise) and flash it to the phone using heimdall/odin/flash_image. You'll have a recovery but it won't boot into Android.
Trying to update from cm-11-20160705-UNOFFICIAL-galaxysl and gives me error: assert failed: run_program("/tmp/updater.sh") == 0
Tried from sd (sideload aborts at ~60% with error * failed to write data 'protocol fault (couldn't read status): Connection reset by peer' *)
Any suggestions?
CWM is 6.0.5.1
Does it update OTA?
No news on this rom?
Inviato dal mio MI PAD 2 utilizzando Tapatalk
Yea..... what happened??
Why r there no updates??
Nd i had a question.......What do u think abt the new Android Go concept by Google for Old nd Less RAM Phones??
Do u think we'll get it for our device??
Hi,
I have the same problem. Is there a solution ?
When , i choose "Toggle script asserts" on CWM , this error disappear and the installation continue.
But at the end, the phone has a loop reboot on TWRP . No way to boot on LineageOS.
MiDi0815 said:
Trying to update from cm-11-20160705-UNOFFICIAL-galaxysl and gives me error: assert failed: run_program("/tmp/updater.sh") == 0
Tried from sd (sideload aborts at ~60% with error * failed to write data 'protocol fault (couldn't read status): Connection reset by peer' *)
Any suggestions?
CWM is 6.0.5.1
Click to expand...
Click to collapse
Thank you.
LineageOS 15.1 Oreo (Go edition)
dominatos1 said:
Just curiosity- what is the sense in 7 android on so weak hardware?
Click to expand...
Click to collapse
Technohacker1995 said:
Just to show that it can be done, and a passion for reusing old hardware
Click to expand...
Click to collapse
@Technohacker1995 , do you plan to support LineageOS 15.1 Oreo (Go edition) for our devices ?
I Think it will be a great idea to get this device to work with "LineageOS 15.1 Oreo (Go edition)".
The OS is built to deal with a device with low ram and with optimized apps for better performance and lower space
Yehia2amer said:
@Technohacker1995 , do you plan to support LineageOS 15.1 Oreo (Go edition) for our devices ?
I Think it will be a great idea to get this device to work with "LineageOS 15.1 Oreo (Go edition)".
The OS is built to deal with a device with low ram and with optimized apps for better performance and lower space
Click to expand...
Click to collapse
I'm thinking of doing that, actually (more for Project Treble, rather). I can't guarantee anything though
If I get enough time, I'll try porting it over
What remains to be fixed in the 7.1 port, however, is Mobile Data, GPS, H/W Video acceleration and other features listed in the main post. The same pains would be applicable here too.
Technohacker
(P.S. MAN, what happened to XDA? It never notified me for all these posts )
MiDi0815 said:
Trying to update from cm-11-20160705-UNOFFICIAL-galaxysl and gives me error: assert failed: run_program("/tmp/updater.sh") == 0
Tried from sd (sideload aborts at ~60% with error * failed to write data 'protocol fault (couldn't read status): Connection reset by peer' *)
Any suggestions?
CWM is 6.0.5.1
Click to expand...
Click to collapse
avbuuren said:
Hi,
I have the same problem. Is there a solution ?
When , i choose "Toggle script asserts" on CWM , this error disappear and the installation continue.
But at the end, the phone has a loop reboot on TWRP . No way to boot on LineageOS.
Thank you.
Click to expand...
Click to collapse
This ROM uses LVM partitions for a bigger /system partition. Hence it isn't compatible with previous partitioning schemes. I've actually added a part in the script to make sure it flashes and boots into TWRP first, because it acts as an intermediary for the actual install. You'll want to flash the ROM thrice: 1) Install LVM-partitioned TWRP (Reboots), 2) Act as a confirmation step (fails) 3) Actual install by wiping everything (should succeed) (there were supposed to be messages for each flash) .
As for a solution, if you're comfortable with Heimdall, flash the NORMALBOOT partition in download mode with the boot.img in the zip file. Then boot into recovery (TWRP) to continue for the two flashes.
Download mode is ALWAYS accessible, so don't worry, your phone isn't dead.
ryouza said:
No news on this rom?
Inviato dal mio MI PAD 2 utilizzando Tapatalk
Click to expand...
Click to collapse
I've been quite busy with other things, so I couldn't put much focus onto this.
smsry said:
Yea..... what happened??
Why r there no updates??
Nd i had a question.......What do u think abt the new Android Go concept by Google for Old nd Less RAM Phones??
Do u think we'll get it for our device??
Click to expand...
Click to collapse
It's a nice possibility, and if I'm able to get Project Trble support for the device, it'll get equal support for later releases as any other launch-Oreo device
Vershawn_Tan said:
Does it update OTA?
Click to expand...
Click to collapse
No, it doesn't, because it's an unofficial build.
Again, sorry for not responding earlier, XDA never notified me of these posts
K.....I know i may sound frustrating, but when can we expect the new update for this rom??
smsry said:
K.....I know i may sound frustrating, but when can we expect the new update for this rom??
Click to expand...
Click to collapse
I don't think it'd be any time soon, quite busy with other things, sorry :\
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
beta 2 uploaded
dt2w works, bluetooth audio works, camcorder works.
wifi still partially broke and is a wip. after that its on to lineage os 15 for the h631
wifi works now and the end? of lineage 14.1 dev is here. everything seems to work now
release 1 is posted in the op.
Awesome work! I've finally got me a full featured daily driver
I still got my OG Stylo lying around somewhere. Guess I'll give this ROM a try...
After attempting to reboot after installing, I got a "Kernel Crash!" error. Now my Wi-Fi won't work after restoring a Nandroid backup. Good thing the OG Stylo isn't my primary phone, anymore.
EDIT: I just realized Bluetooth is busted, too.
EDIT 2: After reading from sources outside of XDA, the firmware should have definitely been on v20k before flashing this. Oh well. I might check into attempting to fix the issues, one day.
But ever since I moved on to the OnePlus 5, I only use the OG Stylo as an alarm clock. As long as that still functions, at least it won't end up in the dumpster.
Gave this ROM a go. VERY pleased! WiFi had a hiccup but now working. I can connect to Bluetooth but can not hear audio. Any others come across this? I'm on the metro version of the Stylo.
Thanks in advance.
Z
Sent from my LG-H631 using Tapatalk
I have a MS631 (MetroPCS).
S/W : MS63120p
Is it possible to install and any plan to post Official Release (14.1 or 15 later)?
Thanks..
This is cool... hoping to get a Google-less minimal fernsprecher going, but this time (compared to your other 14.1 build) I can't see any providers-- just 'error while searching for networks.' Now I'm guessing the reason is the same in both cases-- I started from wrong official ROM. Can anyone point to a 63120k kdz? All the old links I found yet are dead
ed: Tried to prove to myself that a kdz was even useful. I have a few wrong kdz sitting around still-- 10j, 20b, 20l. LG Flash Tool wouldn't actually change anything, ever, no matter what. ("Consult your system administrator". Well, he's me... baka.) And LGUP looked like it was doing great the first time, right up until it gave me back a shiny brick (QHSUSB__BULK), so ...maybe later?
:: phasepalm ::
ed-2: found https://lg-firmwares.com/lg-ms631-firmwares/ so now all I have to do is get QFIL to do anything.
I love this OS. I removed the Nexus launcher and installed the new pixel 2 launcher in its place though. Every now and again I have to disconnect and reconnect Bluetooth. But that's not really a problem for me. WiFi sometimes drops but reconnect. I can't wait for the new lineage OS.
Any update?
pnaralove said:
Any update?
Click to expand...
Click to collapse
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Revenant Ghost said:
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Click to expand...
Click to collapse
Thank you for the reponse
Please let me know how it is after you try this ROM.
won't boot all the way through, logcat without complete boo
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hello, everything seems to be fine but it won't boot all the way through. Also I am still a noob and am wondering how to get a logcat without being able to get all the way into the operating system? Any help would be appreciated
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
gameplayerdo2 said:
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
Click to expand...
Click to collapse
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
derpendicular said:
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
Click to expand...
Click to collapse
Hey there I got it. What I did was I hooked up to LG Bridge and let LG do the repair from the upgrade repair button and it got my phone back to square one which was fine. From there i unlocked the bootloader and booted from TWRP 2.8.7.1 image file and then once inside TWRP I installed version TWRP 3.2.0-0 recovery from the zip file. At that point I then was able to do an advanced wipe and wipe out the system and then do the lineage install from there. Once that worked I wiped it out and installed CyanogenMod just to see if it will go on as well and it did. So I went back and wipe that out and put the lineage OS back on there with the opengapps and it's running flawlessly! I also installed magisk to root it and everything is running fine. The only thing I miss from the LG part of the software was the knock on knock off feature. And I downloaded a tap on tap off app for that but you can't use any other locks with it. but I'm good, and thanks! Because I hated that stock operating system with all the bloatware even though MetroPCS didn't have as much garbage as the T-Mobile or other versions but still now I can control Play Store and everything else. I in fact use APK pure to get most of my apps if I can find the software there.
Hey I got my LG g Stylo and might use it again with lineage on it. I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
elwhiteboy01 said:
I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
Click to expand...
Click to collapse
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
derpendicular said:
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
Click to expand...
Click to collapse
The phone is bricked now. I did a fastboot boot twrp and installed magisk zip. Then installed flashify and flashed twrp image. Then formatted data and installed the lineage os and it didn't go through. I was in a hurry so I didn't backup the stock ROM. And so I pulled the battery and put it in download mode and flashed kdz. And when it finished the screen went black and shows no signs of life no matter what I do.