Related
For the few who wanted MIUI ported to the streak, you may get it soon
MIUI FOR THE STREAK7 IS NEAR OPERATIONAL STANDARDS
STOCK PARTITIONS REQUIRED!
WILL NOT WORK WHEN COMING FROM HS-R1 THROUGH HS-R6 OR ICS-B1 THROUGH B4 FROM GIVEEN
This is still a work in progress (that means not everything works, there will be bugs)
:victory:WE HAVE BOOT!:victory: however its followed by many more of them if you lock the device
landscape lock screen and portrait general use... for now
3G AND 4G HAVE NOT BEEN TESTED HOWEVER CODE IS IN PLACE FOR THEM
NO CAMERA BECAUSE ITS MORE SH!T TO WORRY ABOUT
TWRP2 or CWM 6.0.1 required
as always if you flash it and its now FUBAR its your fault
There is a possibility you will f*** up, if you do the responsibility for repairing it is yours (why would I fix your mistakes)
Bug report is to be user fed. If you have hardware faults or have something not work that you think should work (apart from the camera) then submit a logcat
Thanks to DJ_steve and Giveen for ICS B4, TheManii for porting ICS B4 to stock partitions, a bunch of crazy guys who made MIUI possible and Linus Torvalds for linux kernel
Download links will probably be up in the next 72hours
English only as XDA is in english only
If flashing through CWM doesn't work then push the files across with adb/fastboot then reboot
complaint report:
1. No GApps: you have to flash them post install. the end.
2. wouldnt it be easier if?: no, this is my way of doing it, be thankful you got this rather than being negative about the way I work
3. camera: decided you can live without it (however I may change my mind at a later date)
4. wifi: untested (though it should work)
5. possible lock ups every 20-30min: its a beta, don't expect it to be perfect
6. 3g/4g: untested
7. bluetooth: untested (though it should work)
8. when will the next rom be ready: see my signature
9. why doesnt the rom boot properly when I have CWM6.0.1.x?: because you probably came from HS-r6, have one of the failed build that I accidentally uploaded or havent cleared your caches
10. whats with the intermittent reboots?: I'm not a f***ing miracle worker here guys, I just do this in my spare time when I have had enough to drink to care about the wants of other people
Now this will be interesting!
Sent from my Galaxy Nexus using xda premium
ElfinJNoty said:
Now this will be interesting!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
What's the point in waiting for something you should get the thanks for
looking forward to it!
as are many other people, if there is anything you want included in it then its up to you guys to inform me (gApps will be removed, as always- if I include them then they are there, dont judge me)
Second build is up
I cant download this ROM from Google Docs because of access error, pls check
nicolay.n said:
I cant download this ROM from Google Docs because of access error, pls check
Click to expand...
Click to collapse
link fixed, try now
Flashable from CWM? Any wipes needed?
CWM 6.0.1.x would be worth a try and try wiping dalvik cache and perform a fac reset if it doesnt boot preoperly
Nocturnal_50, tried to flash from HoneyStreak R7 + CWM 6.0.1.0 twice. It says "MIUI ICS port ..." and so on, installing complete and... nothing changes, im on R7 with all of my apps and settings
nicolay.n said:
Nocturnal_50, tried to flash from HoneyStreak R7 + CWM 6.0.1.0 twice. It says "MIUI ICS port ..." and so on, installing complete and... nothing changes, im on R7 with all of my apps and settings
Click to expand...
Click to collapse
did you do a fac reset and clear dalvik?
Nocturnal_50 said:
did you do a fac reset and clear dalvik?
Click to expand...
Click to collapse
Before or after flashing? And factory - user data only or with internal storage?
nicolay.n said:
Before or after flashing? And factory - user data only or with internal storage?
Click to expand...
Click to collapse
try both and all options, if it works then awesome, if not then I may have uploaded the wrong image or have forgotten something in this build
Nocturnal_50 said:
try both and all options, if it works then awesome, if not then I may have uploaded the wrong image or have forgotten something in this build
Click to expand...
Click to collapse
Tried wipe before and after. Still welcome screen from HoneyStreak
nicolay.n said:
Tried wipe before and after. Still welcome screen from HoneyStreak
Click to expand...
Click to collapse
provide a printscreen/picture of your about tablet section so I can see if its flashed any settings across, perhaps flash with twrp/push the rom with adb
Nocturnal_50 said:
provide a printscreen/picture of your about tablet section so I can see if its flashed any settings across, perhaps flash with twrp/push the rom with adb
Click to expand...
Click to collapse
I cannot because it hangs on welcome screen, press on Begin button do nothing. I flashed B4 now
nicolay.n said:
I cannot because it hangs on welcome screen, press on Begin button do nothing. I flashed B4 now
Click to expand...
Click to collapse
how long have you given it on initial boot? try 15min at least
Nocturnal_50 said:
how long have you given it on initial boot? try 15min at least
Click to expand...
Click to collapse
After flashing and wiping it boots in 3 minutes and shows me welcome honeycomb screen, which from i cannot continue to set time settings and begin working with device. I will give them 15 or 20 minutes, if they need, but it boots in 3
So ive been trying to dual boot because i want to try aosp based rom but i need to be a ble to get back to touchwis. Now ive tried the patcher app which aome people said it worked but ive tried everything with no succes.
egren58 said:
So ive been trying to dual boot because i want to try aosp based rom but i need to be a ble to get back to touchwis. Now ive tried the patcher app which aome people said it worked but ive tried everything with no succes.
Click to expand...
Click to collapse
I dont't know if this helps but in the thread for the patcher app it was mentioned that if you needed to dual boot with a TW based rom it would need to be the primary in order for it to work properly otherwise the mods would need to be patched before flashing.
glm0025 said:
I dont't know if this helps but in the thread for the patcher app it was mentioned that if you needed to dual boot with a TW based rom it would need to be the primary in order for it to work properly otherwise the mods would need to be patched before flashing.
Click to expand...
Click to collapse
I swt tw as primary patched cm12 and gapps. But recovery was freezing so i tried to manually paych the file as stated. But than when i got to flash vie recovery it says fail. I have no idea what to do since i did exactly as it said.
My guess would be try asking in the dual boot thread. Others have gotten it to work.
BAD ASS NOTE 4
BACARDILIMON said:
My guess would be try asking in the dual boot thread. Others have gotten it to work.
BAD ASS NOTE 4
Click to expand...
Click to collapse
Good idea. But for some reason i cant find the dam thread now. Wtf.
egren58 said:
Good idea. But for some reason i cant find the dam thread now. Wtf.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3058835
All u need
BAD ASS NOTE 4
http://www.linuxmolecule.com/how-to-dual-boot-roms-on-the-galaxy-note-4/
I can confirm this works in T-Mobile note 4. You just have to follow the steps.
It works trust me, I'm a senior member
I managed to get it to flash but....
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Dhat Boi Swerve said:
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Click to expand...
Click to collapse
It should when you reboot the device.
Dhat Boi Swerve said:
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Click to expand...
Click to collapse
Struggling with this thing for the last 2 days. Same issue as your. Cannot switch back to the primary rom...
suhridkhan said:
Struggling with this thing for the last 2 days. Same issue as your. Cannot switch back to the primary rom...
Click to expand...
Click to collapse
you cant dual boot stock Samsung roms for some reason...
frr1 said:
you cant dual boot stock Samsung roms for some reason...
Click to expand...
Click to collapse
Just got it working, after so much trouble. Tmobile Note4 running TW Rapture as primary and CMRemix as secondary. Still no luck with the second step of patching, but manual patch has worked. This one is a better written guide, I suppose.
http://www.linuxmolecule.com/how-to-dual-boot-roms-on-the-galaxy-note-4/
I can't believe it's taken me this long to get into trying to dual boot my phone... both my desktop and laptop have ridiculous multi-boot schemes :laugh:
The main reason I haven't yet delved into this is a fairly simple question that I haven't been able to find the answer to: How much free storage space is required / will be used by installing an additional ROM and on which partition(s)?
I'd really appreciate if anyone who has this working could fill me in on that info
BTW another great thread with instructions, etc. is here: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
jazzmachine said:
I can't believe it's taken me this long to get into trying to dual boot my phone... both my desktop and laptop have ridiculous multi-boot schemes :laugh:
The main reason I haven't yet delved into this is a fairly simple question that I haven't been able to find the answer to: How much free storage space is required / will be used by installing an additional ROM and on which partition(s)?
I'd really appreciate if anyone who has this working could fill me in on that info
BTW another great thread with instructions, etc. is here: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
Click to expand...
Click to collapse
AOSP roms has very small footprint, that's why they are insanely fast... The roms itself with gapps only takes about a gigabyte, if it's CM or other aosp roms. If you dual boot 2 TW roms, of course it's gonna take huge space. It also depends on how many apps you are going to install on the second rom
Starting with a nice script by @Phil3759, I compiled a PhilZ Touch recovery for the Galaxy S5 Plus as this phone, by now, is widely spread over Europe. I took also some parts of the cwm from @Chenglu (Xiaolu). I didn't test all functionnalities, but, normally, this shouln't be very different from what is existing for Lollipop. A file is attached. Use ODIN or dd.
All credits are for these two guys, specially for @Phil3759 and many thanks to them.
Enjoy !
NEW VERSION V2.3 : [Chttp://cdn1.xda-developers.com/images/2015/editor/color.pngOLOR="Lime"] extSdCard [/COLOR](mount/unmount, save/restore...) WORKING !
adb (under Ubuntu or equivalent. For Windows, use Koush's UniversalAdbDriver) WORKING !
exfat (mount, umount,format) WORKING [/COLOR]
Flashing this recovery will trip the knox counter (knox=0x1) !
Please look at a new release including F2FS and NTFS supports - it is version 2.3 + F2FS + NTFS - :
forum.xda-developers.com/showthread.php?t=3112384 (thank you @ad0dh67)
think you forgot the file
I uploaded the file for the second time. As I am very new on this forum, I don't know exactly what to do in case of a failure. I hope It will be fine.
OBSOLETE ! SEE V 2.2 at the beginning of the thread.
xdamc2010 said:
I uploaded the file for the second time. As I am very new on this forum, I don't know exactly what to do in case of a failure. I hope It will be fine.
Click to expand...
Click to collapse
just flashed the recovery and congrats :thumbup: its working well and looking good. i sugest make topic in dev section. Good job!
Edited. Recovery does not see ext sdcard!
xdamc2010 said:
I uploaded the file for the second time. As I am very new on this forum, I don't know exactly what to do in case of a failure. I hope It will be fine.
Click to expand...
Click to collapse
Great work
xdamc2010 said:
Starting with a nice script by @Phil3759, I compiled a PhilZ Touch recovery for the Galaxy S5 Plus as this phone, by now, is widely spread over Europe. I took also some parts of the cwm from @Chenglu (Xiaolu). I didn't test all functionnalities, but, normally, this shouln't be very different from what is existing for Lollipop. A file is attached. Use ODIN or dd.
All credits are for theses two guys, specially for @Phil3759 and many thanks to them.
Enjoy !
Click to expand...
Click to collapse
You did it!! well done mate :good:
ad0dh67 said:
just flashed the recovery and congrats :thumbup: its working well and looking good. i sugest make topic in dev section. Good job!
Edited. Recovery does not see ext sdcard!
Click to expand...
Click to collapse
You are right.
it is a first step and only a strict compilation of @Phil3759 sources. Before adding other properties, I need test reports upon what is working and what is not. Then the first job will consist in making recovery seeing the extSdCard. Moreover, if I compiled this recovery, it is mainly to try to add f2fs formatting in order to replace the ext4 filesystem.
good work, when you get the ext sdcard working I will start using it.
Is this able to use backups made by the older CWM we been using?
ad0dh67 said:
just flashed the recovery and congrats :thumbup: its working well and looking good. i sugest make topic in dev section. Good job!
Edited. Recovery does not see ext sdcard!
Click to expand...
Click to collapse
Have a look to version V2
javilonas said:
Great work
Click to expand...
Click to collapse
HI,
Have a look to version v2 : extSdCard is now recognized
chrcol said:
good work, when you get the ext sdcard working I will start using it.
Is this able to use backups made by the older CWM we been using?
Click to expand...
Click to collapse
Have a look to version v2.2
xdamc2010 said:
Have a look to version v2
Click to expand...
Click to collapse
just downloaded, flashed, and yes external sd works now! congrats man, you just made a recovery, which is ready for use on our phone :thumbup: thank you
xdamc2010 said:
Have a look to version V2
Click to expand...
Click to collapse
Hello, it works great
I tested to do a backup.
I don't try to restore for the moment.
xdamc2010 said:
Have a look to version V2
Click to expand...
Click to collapse
thanks for your efforts
v2 works perfectly here, formatted and flashed a rom from extsdcard perfectly! great work mate :good:
I just noticed it says lollipop, does this mean this recovery wont work with kitkat roms?
issues I found
with touch interface enabled and pressing the circle button, I often by mistake do 2 actions, it seems it repeats even if the repeat key option is disabled.
date/time is completely wrong. time zone is set correct but the time displayed is completely wrong, my local time is 16:37 4 may and its displaying 8:14 5 may.
setting brightness has no effect, always same brightness.
dim screen delay also doesnt work (screen never dims)
ok for now I having to revert to the basic cwm as my extsdcard is exfat.
chrcol said:
I just noticed it says lollipop, does this mean this recovery wont work with kitkat roms?
issues I found
with touch interface enabled and pressing the circle button, I often by mistake do 2 actions, it seems it repeats even if the repeat key option is disabled.
date/time is completely wrong. time zone is set correct but the time displayed is completely wrong, my local time is 16:37 4 may and its displaying 8:14 5 may.
setting brightness has no effect, always same brightness.
dim screen delay also doesnt work (screen never dims)
ok for now I having to revert to the basic cwm as my extsdcard is exfat.
Click to expand...
Click to collapse
I didn't try kitkat roms as I don't need them anymore. If bootloaders are not different it could work.
Touch interface is very sensitive. Try to lower the Scroll Sensitivity.
Time appears foolish. Just tick the Qualcomm Time Daemon and you get the right time
exfat is a real problem and I try to solve this question.
xdamc2010 said:
I didn't try kitkat roms as I don't need them anymore. If bootloaders are not different it could work.
Touch interface is very sensitive. Try to lower the Scroll Sensitivity.
Time appears foolish. Just tick the Qualcomm Time Daemon and you get the right time
exfat is a real problem and I try to solve this question.
Click to expand...
Click to collapse
bootloader kitkat and lollipop are different
so what issues does different bootloader cause?
I was able to access the recovery fine with a kitkat rom installed.
chrcol said:
so what issues does different bootloader cause?
I was able to access the recovery fine with a kitkat rom installed.
Click to expand...
Click to collapse
Good news !
issues with bootloaders : mainly bootloops or phone freezes.
Basically, I had to do a battery pull on my LG D415, after the better pull, I booted up the device like I normally would. After starting the device, I am now experiencing an issue where I am unable to get past the CM13 boot logo, where it will continue the booting animation with the CM13 logo, and then the device will just shut down. Attached is a video of this happening.
Is this essentially the inevitable bootloop that is found in many Android devices? If so, how can I go about fixing the issue? I had a lot of stuff on the device and would prefer to not have to reflash anything, as I spent already hours setting up the device in the first place.
Here is the video: https://www.youtube.com/watch?v=1kgh-DFxKBg&feature=youtu.be
darkgiant said:
Basically, I had to do a battery pull on my LG D415, after the better pull, I booted up the device like I normally would. After starting the device, I am now experiencing an issue where I am unable to get past the CM13 boot logo, where it will continue the booting animation with the CM13 logo, and then the device will just shut down. Attached is a video of this happening.
Is this essentially the inevitable bootloop that is found in many Android devices? If so, how can I go about fixing the issue? I had a lot of stuff on the device and would prefer to not have to reflash anything, as I spent already hours setting up the device in the first place.
Here is the video:
&feature=youtu.be
Click to expand...
Click to collapse
Usually a bootloop restarts your phone or doesn't pass the CM (in this case) logo.. I think u can classify as bootloop nevertheless.. u can try reflashing the same version of cm13 on top of that.. you maybe won't loose anything important but I don't know what you had done in your device.. it's just my opinion..
Warimation said:
Usually a bootloop restarts your phone or doesn't pass the CM (in this case) logo.. I think u can classify as bootloop nevertheless.. u can try reflashing the same version of cm13 on top of that.. you maybe won't loose anything important but I don't know what you had done in your device.. it's just my opinion..
Click to expand...
Click to collapse
So if I were to flash CM13 (without wiping anything) I should be safe in terms of not wiping anything? Would I also need to flash GAPPS again?
darkgiant said:
So if I were to flash CM13 (without wiping anything) I should be safe in terms of not wiping anything? Would I also need to flash GAPPS again?
Click to expand...
Click to collapse
I don't know.. again it's your decision.. but if your going to flash, try 1st without Gapps.. if they don't stay then flash Gapps.. btw I saw u want to download cm13.. that's a bummer because cyanogen is over.. they closed CyanogenMod OS. So no more cm's for anyone. Instead u have lineage OS that's made by CM team and we don't have official. It's the same with changed brand.. I don't know if you will succeed downloading a cm13 version but search here in L90 forums.. maybe you find a solution..
Warimation said:
I don't know.. again it's your decision.. but if your going to flash, try 1st without Gapps.. if they don't stay then flash Gapps.. btw I saw u want to download cm13.. that's a bummer because cyanogen is over.. they closed CyanogenMod OS. So no more cm's for anyone. Instead u have lineage OS that's made by CM team and we don't have official. It's the same with changed brand.. I don't know if you will succeed downloading a cm13 version but search here in L90 forums.. maybe you find a solution..
Click to expand...
Click to collapse
Oh yeah, I totally forgot that CyanogenMod closed down its OS. This is a huge bummer, as this essentially means I need to find a new ROM anyways...
Any suggestions? Anything super stable, and runs fast is what I was looking for. If not, I might just go back to the stock ROM and stay rooted or something.
darkgiant said:
Oh yeah, I totally forgot that CyanogenMod closed down its OS. This is a huge bummer, as this essentially means I need to find a new ROM anyways...
Any suggestions? Anything super stable, and runs fast is what I was looking for. If not, I might just go back to the stock ROM and stay rooted or something.
Click to expand...
Click to collapse
I'm currently using Aicp os. Its super fast and it's working good.. it's nougat so expect a better battery life but still have some bugs.. It's going to become official.
forum.xda-developers.com/lg-l90/development/rom-android-ice-cold-project-12-1-t3559656/page3
Warimation said:
I'm currently using Aicp os. Its super fast and it's working good.. it's nougat so expect a better battery life but still have some bugs.. It's going to become official.
forum.xda-developers.com/lg-l90/development/rom-android-ice-cold-project-12-1-t3559656/page3
Click to expand...
Click to collapse
Thanks for the advice, I'll go ahead and take a look at it! As long as it's stable, and good to use as a daily driver, it works for me.
Though, I am currently having an issue with booting into TWRP to flash the ROMs, as I keep trying the volume up + power button steps to get into recovery, but it's just sending me directly to the CM13 loading logo. And because I can't even get into CM13 because of the boot issue, I am not sure if I can connect the device to a computer... Any advice on how I can fix this issue?
darkgiant said:
Thanks for the advice, I'll go ahead and take a look at it! As long as it's stable, and good to use as a daily driver, it works for me.
Though, I am currently having an issue with booting into TWRP to flash the ROMs, as I keep trying the volume up + power button steps to get into recovery, but it's just sending me directly to the CM13 loading logo. And because I can't even get into CM13 because of the boot issue, I am not sure if I can connect the device to a computer... Any advice on how I can fix this issue?
Click to expand...
Click to collapse
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. doesn't bring root by default but just flash SuperSU 2.79 (last version I think) and will work ok
Warimation said:
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. doesn't bring root by default but just flash SuperSU 2.79 (last version I think) and will work ok
Click to expand...
Click to collapse
Haha silly me, yes volume down + power did the trick. I always get confused with that because it seems to be different for many devices. Yeah as I posted in my other thread, this phone is meant for a friend who uses it daily, it sounds like that lineage 13 is pretty much fit for the task? Would it receive updates in the future? I am always open for trying other ROMS of course, as long as they are 100% working and have no issues/
darkgiant said:
Haha silly me, yes volume down + power did the trick. I always get confused with that because it seems to be different for many devices. Yeah as I posted in my other thread, this phone is meant for a friend who uses it daily, it sounds like that lineage 13 is pretty much fit for the task? Would it receive updates in the future? I am always open for trying other ROMS of course, as long as they are 100% working and have no issues/
Click to expand...
Click to collapse
As it is now lineage 13 is the best option for stable.. But dont expect updates on 13.. Later you can use 14.1 but now it have some issues..
Warimation said:
As it is now lineage 13 is the best option for stable.. But dont expect updates on 13.. Later you can use 14.1 but now it have some issues..
Click to expand...
Click to collapse
Oh okay, thanks! I'll go ahead and just do a fresh install since I forgot this phone has an SD card, so the majority of the data needed is already there. Thanks for your help! I'll keep looking at 14.1 and rest of the Nougat ROMs, and consider flashing it if they become stable soon.
Warimation said:
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. cumps
Click to expand...
Click to collapse
So I installed lineage OS, but for some reason can't provide root access to apps? Attached a screenshot, not sure why it's not allowing me to select apps, and only showing ADB...
EDIT: No idea how, but the SIM card reader stopped working... I tried flashing another ROM just to see if it was lineage, but it wasn't. The phone is still under warranty, but I assume if I send it back it'd have to be unrooted... any idea how I can go about that?
darkgiant said:
So I installed lineage OS, but for some reason can't provide root access to apps? Attached a screenshot, not sure why it's not allowing me to select apps, and only showing ADB...
EDIT: No idea how, but the SIM card reader stopped working... I tried flashing another ROM just to see if it was lineage, but it wasn't. The phone is still under warranty, but I assume if I send it back it'd have to be unrooted... any idea how I can go about that?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Do this and you have a warranty covered phone.
Warimation said:
https://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Do this and you have a warranty covered phone.
Click to expand...
Click to collapse
Oh great, thanks! I used to have the old myTouch 4G, and unrooting that phone was such a pain, I nearly spent 6 full hours because of all the steps needed and it was so easy to mess up. This looks pretty straight forward. On the bright side, I now know once I get the phone back I can flash lineage OS and should be good to go.
darkgiant said:
Oh great, thanks! I used to have the old myTouch 4G, and unrooting that phone was such a pain, I nearly spent 6 full hours because of all the steps needed and it was so easy to mess up. This looks pretty straight forward. On the bright side, I now know once I get the phone back I can flash lineage OS and should be good to go.
Click to expand...
Click to collapse
Before you flash kdz maybe the problem was bootstack.. Dont really know if that was the problem because its supposed to work if you still have a KitKat bootstack installed but try changing that.. Just be carefull to choose the right one..
https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632/page7
Hello! So, I've tried creating a device tree for the Leon LTE (H340n) based on ms345, and after some changes I've compiled TWRP for this specific model, with it identifying as c50n, which should allow for custom ROMs(I'm building LineageOS 13 right now, but don't get your hopes up) Also, there's a way to flash TWRP and get root on 6.0, here's a guide (https://forum.xda-developers.com/showpost.php?p=72501544&postcount=25) and you can flash my recovery instead.
Link: https://www.androidfilehost.com/?fid=961840155545578919
Sources: https://github.com/dadziokPL/android_.repo_local_manifests
Also, this recovery wouldn't work if it wasn't for Charles-IV's help on Github, a huuuuge thanks to him!
dadziokPL said:
Hello! So, I've tried creating a device tree for the Leon LTE (H340n) based on ms345, and after some changes I've compiled TWRP for this specific model, with it identifying as c50n, which should allow for custom ROMs(I'm building LineageOS 13 right now, but don't get your hopes up) Also, there's a way to flash TWRP and get root on 6.0, here's a guide (https://forum.xda-developers.com/showpost.php?p=72501544&postcount=25) and you can flash my recovery instead.
Link: https://www.androidfilehost.com/?fid=961840155545578919
Sources: https://github.com/dadziokPL/android_.repo_local_manifests
Also, this recovery wouldn't work if it wasn't for Charles-IV's help on Github, a huuuuge thanks to him!
Click to expand...
Click to collapse
Hi? The metro pcs version is what model? C50n? Also I found anoth4r version of twrp on 5he site twrp.me.. I saw twrp-3.1.1-0-c50.img... Is this appropriate? I hav the metro version and I'm confused what to use
jazzdglass said:
Hi? The metro pcs version is what model? C50n? Also I found anoth4r version of twrp on 5he site twrp.me.. I saw twrp-3.1.1-0-c50.img... Is this appropriate? I hav the metro version and I'm confused what to use
Click to expand...
Click to collapse
the official twrp one is for all c50 devices, but this one is specifically for the c50n, but im not sure how much of a difference it makes.
You can find out if yours is c50n or not in about phone.
Strange thing is its twrp 3.0.2 , and i cant find anything about this on the internet
Charles IV said:
the official twrp one is for all c50 devices, but this one is specifically for the c50n, but im not sure how much of a difference it makes.
You can find out if yours is c50n or not in about phone.
Strange thing is its twrp 3.0.2 , and i cant find anything about this on the internet
Click to expand...
Click to collapse
The difference is that the c50n did not have a device tree, there was no way to build custom ROMs, so I started working on a tree, and TWRP now compiles with it. It also identifies as c50n inside the recovery when checking compatibility with a ROM, so if I ever manage to get Lineage working, it will flash properly, being meant for THIS specific phone, the LG Leon 4G LTE aka H340n aka C50n. Previous TWRP was for all LG Leons, built on a common tree. With a specific tree, it allows for specific fixes for this device if needed in the future. The version is older since I used TWRP android6.0 branch, I could build an updated version, but right now I'm taking a break.
jazzdglass said:
Hi? The metro pcs version is what model? C50n? Also I found anoth4r version of twrp on 5he site twrp.me.. I saw twrp-3.1.1-0-c50.img... Is this appropriate? I hav the metro version and I'm confused what to use
Click to expand...
Click to collapse
MetroPCS is ms345, I just needed a base for C50n, the international LG Leon 4G LTE. The devices are similiar, so I thought I could use the existing ms345 tree to create a tree for the C50n. I don't know if there is a specific TWRP for the ms345, if there is, you should find it and use it. If not, the C50 from twrp.me should work. Also, my recovery for C50n should work too, just try flashing, if some **** goes sideways, just flash another one and try again. The difference is basically what TWRP thinks your device is, and if you flash a ROM for ms345 it would expect your recovery to be for ms345, and not anything else. Get it?
Hey, I'm from Brazil and I own a H342 model of this cellphone.
I was thinking about installing the v20b marshmallow kdz released for H340 because I'm done with the ***ty, ugly and laggy 5.0.1 build, but I know that even if the processor is the same for both devices the baseband will still differ.
You know how can I install 6.0 and flash the baseband from the H342 after?
Sorry for any concordances errors and thank u for your time
mateus.sc said:
Hey, I'm from Brazil and I own a H342 model of this cellphone.
I was thinking about installing the v20b marshmallow kdz released for H340 because I'm done with the ***ty, ugly and laggy 5.0.1 build, but I know that even if the processor is the same for both devices the baseband will still differ.
You know how can I install 6.0 and flash the baseband from the H342 after?
Sorry for any concordances errors and thank u for your time
Click to expand...
Click to collapse
Sorry about the lateness, but don't do it.
The baseband was built with code specifically for lollipop, flashing it on top of marshmallow will most likely lead to incompatibility.
What about LineageOS?
rusiu559 said:
What about LineageOS?
Click to expand...
Click to collapse
Any news ?
rusiu559 said:
Any news ?
Click to expand...
Click to collapse
None other than it might take a long time. @dadziokPL has a lead on what the current error is though.
Charles IV said:
None other than it might take a long time. @dadziokPL has a lead on what the current error is though.
Click to expand...
Click to collapse
It's all going so terribly wrong tho. I've managed to get it to compile, but it does not boot. Goes to "AP Watchdog bark" green screen, so probably can't even boot into the Linux kernel, since if it did we'd get some boot animation and logcats. I'm totally stuck.
Also, the recovery does not boot anymore, I'm gonna revert some commits up until you merged all the common trees, modular approach is much better
dadziokPL said:
It's all going so terribly wrong tho. I've managed to get it to compile, but it does not boot. Goes to "AP Watchdog bark" green screen, so probably can't even boot into the Linux kernel, since if it did we'd get some boot animation and logcats. I'm totally stuck.
Also, the recovery does not boot anymore, I'm gonna revert some commits up until you merged all the common trees, modular approach is much better
Click to expand...
Click to collapse
Yes, I was worried that I might break something with the merging, but we can re-merge when everything's working to see if it does break things.
The kernel might need to be modified - all I did is went onto lg leon's source code site and downloaded the H340N one. It contained two zips, one with the kernel in, and one supposedly with the rest in, but it was really messed up and I couldn't get it working.
I'll build the kernel in that tree using their instructions (not sure what I'll get!) and we'll see if we can use that as a prebuilt kernel.
Is your bootloader definitely unlocked? I remember getting a greenscreen when I was messing about with the partitions, trying to put the recovery on it etc.
Charles IV said:
Yes, I was worried that I might break something with the merging, but we can re-merge when everything's working to see if it does break things.
The kernel might need to be modified - all I did is went onto lg leon's source code site and downloaded the H340N one. It contained two zips, one with the kernel in, and one supposedly with the rest in, but it was really messed up and I couldn't get it working.
I'll build the kernel in that tree using their instructions (not sure what I'll get!) and we'll see if we can use that as a prebuilt kernel.
Is your bootloader definitely unlocked? I remember getting a greenscreen when I was messing about with the partitions, trying to put the recovery on it etc.
Click to expand...
Click to collapse
Yeah, the bootloader's got to be unlocked since old TWRP boots fine
dadziokPL said:
Yeah, the bootloader's got to be unlocked since old TWRP boots fine
Click to expand...
Click to collapse
I'm trying to figure out a way of how to unmerge, and restore the combined branch it was on - i spent so long on that! -_-
To me it looks like the error is to do with the bootloader rejecting it. Could it me something to do with the system.prop. Fingerprints, maybe?
Charles IV said:
I'm trying to figure out a way of how to unmerge, and restore the combined branch it was on - i spent so long on that! -_-
To me it looks like the error is to do with the bootloader rejecting it. Could it me something to do with the system.prop. Fingerprints, maybe?
Click to expand...
Click to collapse
I have completely no idea what the problem is. I'm gonna hard reset the repo to the last commit before the merge, but we'll lose all commit history after the merge. We'll have to start over from before you merged it all. Why'd you even do it? It was totally fine being modular
dadziokPL said:
I have completely no idea what the problem is. I'm gonna hard reset the repo to the last commit before the merge, but we'll lose all commit history after the merge. We'll have to start over from before you merged it all. Why'd you even do it? It was totally fine being modular
Click to expand...
Click to collapse
Well I'm used to a single device repo, so I tried merging it, to see if it worked. Personally I didn't like having 3 repos to look at, but three of each file is also hard!
Tbh I was surprised when you pulled it, I just did it as an experiment.
Charles IV said:
Well I'm used to a single device repo, so I tried merging it, to see if it worked. Personally I didn't like having 3 repos to look at, but three of each file is also hard!
Tbh I was surprised when you pulled it, I just did it as an experiment.
Click to expand...
Click to collapse
I thought maybe you did something important with the merge and just pulled it, but it seems like it broke it. Anyway, now I know how to revert commits, so I'll be building the recovery, and if it does not work, I'll just revert one commit back and gradually figure out at what point it broke.
dadziokPL said:
I thought maybe you did something important with the merge and just pulled it, but it seems like it broke it. Anyway, now I know how to revert commits, so I'll be building the recovery, and if it does not work, I'll just revert one commit back and gradually figure out at what point it broke.
Click to expand...
Click to collapse
When you've got recovery working, if booting still doesn't work, let me know, I've noticed a minor difference in fingerprints and build description (the same difference) in my build.prop compared to the build prop overrides. It is probably because they are different builds, and shouldn't make a difference, but if it's not working, I'll try it.
On a side note - if we change the overrides, in theory, with suhide, it should pass safetynet!
Charles IV said:
When you've got recovery working, if booting still doesn't work, let me know, I've noticed a minor difference in fingerprints and build description (the same difference) in my build.prop compared to the build prop overrides. It is probably because they are different builds, and shouldn't make a difference, but if it's not working, I'll try it.
On a side note - if we change the overrides, in theory, with suhide, it should pass safetynet!
Click to expand...
Click to collapse
Okay, so the merge must have screwed something up, since recovery works perfect now! I'll be back to building now. Also, I'm not building Lineage anymore, I switched over to RessurectionRemix, it's totally awesome.
Edit: You know what. I'm actually going to build the kernel itself for now and see if it works, since I'm on a CM12.1 ROM for ms345, it works but is quite bugged. I'll do an experiment and try to flash the kernel I'll build. Probably won't work, but I'll see what will happen
Edit 2: Okay, green screen again, I'll try to build the full ROM again, if that happens again, that is bad news, since I have no idea how to fix this thing.
Just another edit: I have an idea. I just downloaded the Qualcomm QPST tool, I might be able to debug this. No promises tho, we'll see.
dadziokPL said:
Okay, so the merge must have screwed something up, since recovery works perfect now! I'll be back to building now. Also, I'm not building Lineage anymore, I switched over to RessurectionRemix, it's totally awesome.
Edit: You know what. I'm actually going to build the kernel itself for now and see if it works, since I'm on a CM12.1 ROM for ms345, it works but is quite bugged. I'll do an experiment and try to flash the kernel I'll build. Probably won't work, but I'll see what will happen
Edit 2: Okay, green screen again, I'll try to build the full ROM again, if that happens again, that is bad news, since I have no idea how to fix this thing.
Just another edit: I have an idea. I just downloaded the Qualcomm QPST tool, I might be able to debug this. No promises tho, we'll see.
Click to expand...
Click to collapse
The kernel is probably originally for aosp 6.0.
Personally I think Lineage is better, but then I've never personally used RR.
I'll also make the fingerprint commits.
edit: trying to figure out how to only make a pr of one commit to your tree.