Is there any custom ROM for H840 version? I looked everywhere but nothing shows up. I just messed up my phone, wiped everything from TWRP and does not have OS now.
Slaughtermind said:
Is there any custom ROM for H840 version? I looked everywhere but nothing shows up. I just ****ed up my phone, wiped everything from TWRP and does not have OS now.
Click to expand...
Click to collapse
Did you ever find a solution, mate?
Only H850/H830/RS988 ever had LineageOS builds. Obviously you can install custom recovery (TWRP) on other versions of the LG G5, but that's as good as it gets since you cannot unlock the bootloader to boot into a custom ROM.
If you're stuck without an OS on other variants, you're better off doing a full restore using the LGUP software tool.
EDIT: It seems the SE H840 can also be bootloader unlocked officially by LG, although people have posted mixed experiences depending on what "region" it came from. From what i've seen through searches, people have been asking for custom ROMS for the H840 since 2017 but nothing has come up.
Bump... Just in case anyone has come across an alternative ROM.
I unlocked my UK H840 without issue .. just need a new ROM to replace the old stock..
Any news? Would like to install an application that isn't supported on stock Android 7.0.
This is not the right location for questions. H840 will never have custom ROM support in all likelyhood.
Related
My phone has been bricked for months. I am trying this guide on xda: http://forum.xda-developers.com/showthread.php?t=2542219
So far all the stock firmware seems to not work. I am 90% sure my phone is US Retail but I am not sure if it is XT1032, XT1045, Falcon, Peregine, or whatever it is.... So I am confused as to which files I am supposesd to flash to return to stock; and where they are located.
I currently have access to the bootloader and have TWRP custom recovery installed but I don't know how to install the stock firmware. If anyone could help me understand which model my phone is / why my flashing isn't working, it would be more helpful than they could imagine... :good:
Other threads I made on this simply redirected me to that thread, but I can't find any help or related topics :/
Additional info: I strongly believe that the model number is the issue as I followed countless other guides on how to install Cyanogen Mod and a couple other roms since I got this phone brand new. None of the roms flashed properly, none of the recoveries worked, until now. All I have is a recovery left and a bricked phone...( + access to the bootloader of course)
For your Model number Check Ur Mobile Bill/Box...
Could you also look it up with the imei #? In case a box is not available
http://imei-number.com/imei-number-lookup/
Voiding said:
My phone has been bricked for months. I am trying this guide on xda: http://forum.xda-developers.com/showthread.php?t=2542219
So far all the stock firmware seems to not work. I am 90% sure my phone is US Retail but I am not sure if it is XT1032, XT1045, Falcon, Peregine, or whatever it is.... So I am confused as to which files I am supposesd to flash to return to stock; and where they are located.
I currently have access to the bootloader and have TWRP custom recovery installed but I don't know how to install the stock firmware. If anyone could help me understand which model my phone is / why my flashing isn't working, it would be more helpful than they could imagine... :good:
Other threads I made on this simply redirected me to that thread, but I can't find any help or related topics :/
Additional info: I strongly believe that the model number is the issue as I followed countless other guides on how to install Cyanogen Mod and a couple other roms since I got this phone brand new. None of the roms flashed properly, none of the recoveries worked, until now. All I have is a recovery left and a bricked phone...( + access to the bootloader of course)
Click to expand...
Click to collapse
try one of these http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
Thanks for the help, but I found the problem.
Opened the back of the phone to check the model number and it was XT1045 like I thought, so I had the right stock images. Problem was I did not have the Motorola drivers for mfastboot installed correctly. I used a guide to install them universally on mac and my phone is back up and running!
I've been on mm 6.0 and back to 5.1 .
I restored a twrp 5.1 recovery directly back from 6.0 using twrp . My boot loader
Is unlocked and I've used my own rooting
Method and flashifyed my twrp on both lp and mm. Since i'm on 5.1j with my bootloader still unlocked indicated on my
Splash screen can i safely flash the skinny rom on my metro g stylo with out a boot loop or a soft brick
Why did you go back to 5.1 if you wanted to flash the Skinny ROM?
I am going to try this Skinny debloated ROM soon. I have rooted T-Mobile Marshmallow on my MetroPCS Stylo and am missing some features that didn't flash correctly on my T-Mobile marshmallow.
I am always building stuff. I was working on a complete one click unlock Bl, Root and twrp and then another mm Rom build or two.
I always go back to my own builds cause I personalize them just for me but ran across the skinny while surfing and it caught my attention. I've been around for years and been doing this as a hobby since i retired and keeping myself busy.
viperdink said:
I am always building stuff. I was working on a complete one click unlock Bl, Root and twrp and then another mm Rom build or two.
I always go back to my own builds cause I personalize them just for me but ran across the skinny while surfing and it caught my attention. I've been around for years and been doing this as a hobby since i retired and keeping myself busy.
Click to expand...
Click to collapse
Makes sense now.
Let me know how it goes when you (if) flash that Skinny debloated MM ROM.
I am curious if it works and if all the features like advanced text msgng and video calling and all the MM stuff is on it.
This rom works great so far. With the metro update and this it shouldn't take much to get both versons 6.0 mm. Sure would get custom roms going.
Thanks for your enlightenment.
Skinny Rom works great. The new MS63120B_00_0429.KDZ IS OUT. My Metropcs version phone can be set back to stock and I was wondering If using the new LG UP flasher will care that My Bootloader is UnLocked. I don"t know if it will Interfer and check its status.
viperdink said:
Skinny Rom works great. The new MS63120B_00_0429.KDZ IS OUT. My Metropcs version phone can be set back to stock and I was wondering If using the new LG UP flasher will care that My Bootloader is UnLocked. I don"t know if it will Interfer and check its status.
Click to expand...
Click to collapse
thats a good question...i sure hope it doesnt matter to that tool that the bootloader is unlocked...if for some reason it did, maybe you could use lg flash tool 2014 and flash the lollipop kdz?
I went from t--mo mm to metro Loli..to get the metro mm...
I noticed that the bootloader was still unlocked after the Loli flash and kinda got concerned...
But, it never caused any probs...updated to mm metro and rooted smoothly....
I was kinda wondering if i could just wipe and flash skinny without extra caution and precautions...and then if i thought it was ( in my own opinion I'm entitled to) kinda not what i want..flash my mm metro back up...
Doesn't seem like it's been done..i could be wrong..
The drive to dev for this phone isn't as strong as i was hoping...
But, being the first android I've kept vanilla rooted with few tricks...it's not disappointing.
@Cyconumnum
Does the splashscreen still show
" unlocked bootloader "
And did you take the ota or
Flashed metro mm with lg up or the 2014 tool
I don't know what was debloated. The "Skinny" ROM itself is fine but what was taken out?
viperdink said:
@Cyconumnum
Does the splashscreen still show
" unlocked bootloader "
And did you take the ota or
Flashed metro mm with lg up or the 2014 tool
Click to expand...
Click to collapse
I used the flash tool to flash metro lollipop..
After that I went into fastboot to unlock the bootloader ...and it reported to be already unlocked...
It still showed "bootloader unlocked" at the top of the LG splash on the initial metro lollipop boot...
And reported it again booting the metro mm update
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
Sorry..the LG flash tool
I'm back on my personal juicy lp. I gotta get some new fast sd cards. I am working on another twrp for a friend in my spare time and have to hold up on roms and the total one click project. I would like to do the kdz 6.0 but i need parts .
Update; Found 16gb class 10 and worked skinny Rom, metro ota, and lg up flash tool. They both, metro ota and Lg Flash Kdz never showed skinny rom id'd. It said unknown device firmware. So bye bye skinny Rom. They both left the bootloader unlocked when finished flashing metro updates. As i stated before adb pkg and SuperSu needed updating and reinstalling for root and recovery was required. Splash screen still indicated an unlocked bootloader and loading the kdz from 5.0 kept data partition and required all out of date apps to be updated. Namely goggle playservices, adaway 311 needed (thanks guys) and xposed modules i uninstalled till I get time. Advance messageing was an Lg update not inclued in metro updates. Plenty of bloatware to lighten the load but still seemed less than skinnys bloatware. Good to be back on metro software and all the advance messaging and video calls worked. Now i DO gotta get more new sd's. Really out of parts to work with . Going to best buy to hold me over..
CHEERS ALL hope it helps you guys.
Edit; Forgot to add "Quickboot.apk" works 100% take you into all available modes.
i'm actually really content with it being on a stock rooted with various mods.....wish i could get the soft buttons to theme..that's nothing bad thou lol..
MM is a nice environment ..i wish i could install themes from cm13 .....but, as much i do ..i'm not gonna brick my phone with themes...did it before just changing the font on my F6...ha
but, it's great....makes enough sense....
my guess about the bootloader not getting changed with the ROM would be a bios type thing...i'm not toooo android savy..
Cyconumnum said:
i'm actually really content with it being on a stock rooted with various mods.....wish i could get the soft buttons to theme..that's nothing bad thou lol..
MM is a nice environment ..i wish i could install themes from cm13 .....but, as much i do ..i'm not gonna brick my phone with themes...did it before just changing the font on my F6...ha
but, it's great....makes enough sense....
my guess about the bootloader not getting changed with the ROM would be a bios type thing...i'm not toooo android savy..
Click to expand...
Click to collapse
I like the Stock ROM. There are several options for themes.
Layers in the Play Store
G4 Tweaksbox (requires root)
LG Apps Theme Engine (requires root)
LG SmartWorld (no root required but only available on Marshmallow T-Mobile Stylo ROM)
I've been using Samsung devices with custom ROMs for a while. Sadly my most recent purchase of a S7 obviously came with a locked bootloader and the eBay seller updated it to it's latest G930TUVS9CSC1 firmware.
I've looked around for guides and methods of flashing a custom ROM with very little trustworthy advice and links. I'm hoping someone who has flashed a custom ROM on the v9 bootloader has a method they can share.
The ROM I'd like to flash is this LineageOS build. Hopefully it doesn't affect cell signal and NFC like it did on my Note 3.
https://forum.xda-developers.com/galaxy-s7/development/lineageos-15-android-8-0-0-herolte-t3710107
Hi all, I'm relatively new to the Android world and seeking help from experts here.
I recently bought a used S7 (SM-G930K), it came with Android 8.0 and I want to downgrade to 7.0.
I tried downgrading using its stock firmware with Odin. Attempted many times but only realized that it can only be downgraded as far as the bootloader version goes.
Think my S7 was on bootloader version 2. So as checked for the available stock firmwares, the "earliest" version 2 was still on Android 8.0 (PDA G930KKKU2ERJ1 and CSC G930KKTC2ERJ1).
Anyone can advise me how to go about downgrading to Android 7.0? Though this S7 may not be my primary phone and there's obviously no warranty, I won't want to brick anything.
Do I have to downgrade the bootloader version to 1.0 first? And how do I do that?
Apologies, do excuse these noob questions, I'm not familiar with many Android terms. Cheers!
Model: S7 SM-G930K (KT Telco)
Android version: 8.0
Baseband version: G930KKKU2ERJ1
Security patch: Oct 1, 2018
Basically, on Samsung phones, once you upgrade your bootloader, they put a lock on it, so you can never downgrade it, for security reasons, of course.
The only thing you can do is flashing custom rom, or stock rom with custom recovery & kernel.
Mohamedkam000 said:
Basically, on Samsung phones, once you upgrade your bootloader, they put a lock on it, so you can never downgrade it, for security reasons, of course.
The only thing you can do is flashing custom rom, or stock rom with custom recovery & kernel.
Click to expand...
Click to collapse
I see, now i understand why..
"Custom roms" - does this mean it's made by users like us? And what does "stock rom with custom recovery & kernel" mean?
Can you point me where can i find these roms for my S7? Is it the same as flashing them on Odin?
Many thanks!
Yes custom ROM's are community made. The kernal is kind of like the foundation that sits beneath the ROM, so you can use the official ROM but run a custom kernal to tweak phone behaviour.
Flashing ROM's involves using TWRP instead of Odin. If you're going down that path I would recommend you read very carefully and educate yourself, instead of just gung ho'ing it. Wouldn't want to brick your device.
It's also worth mentioning while you can flash an older custom ROM via TWRP, that doesn't downgrade your bootloader with it. Having a newer bootloader on an older ROM can cause issues.
Most custom ROM's are also made for G930F, while some also support the G930K you may want to make sure before flashing anything.
Beanvee7 said:
Yes custom ROM's are community made. The kernal is kind of like the foundation that sits beneath the ROM, so you can use the official ROM but run a custom kernal to tweak phone behaviour.
Flashing ROM's involves using TWRP instead of Odin. If you're going down that path I would recommend you read very carefully and educate yourself, instead of just gung ho'ing it. Wouldn't want to brick your device.
It's also worth mentioning while you can flash an older custom ROM via TWRP, that doesn't downgrade your bootloader with it. Having a newer bootloader on an older ROM can cause issues.
Most custom ROM's are also made for G930F, while some also support the G930K you may want to make sure before flashing anything.
Click to expand...
Click to collapse
Definitely will be more mindful as rooting does involve some kind of risk of bricking my phone.
Wow that's great info, really appreciate you explaining this to me.
Something new I've learnt! :good:
i have looked everywhere.
i am trying to find the stock recovery for oneplus 7 pro
- t-mobile version (if required)
10.0.1 oos
Honestly this phone has been the worst experience ever.
From t-mobile not allowing me access to files to fix my device, to forums being dead, sluggish and from several developers not caring about the issues others experience. to a single phone with 7 different variations. and the one I'm stuck with has 0% help.
ive seen multiple request for these files to go look and see "nvm i just flashed international rom..."
honestly it should be illegal for companies to not provide these files.
ivoe said:
i have looked everywhere.
Click to expand...
Click to collapse
That is because you are looking for something that does not exist. This phone doesn't have a recovery partition. On A/B partition devices, the recovery resides on the boot.img partition (along with kernel and ramdisk). The A/B partition scheme is very confusing if it is new to you (as it is to a lot of folks). You can possibly fastboot flash the stock boot.img partition, depending on what exactly you are trying to accomplish.
I don't buy carrier branded phones anymore, for some of the reasons you are experiencing. Converting the T-Mob 7 Pro to be "international", seems to be a pretty popular thing.
This device is far from being "dead" the most common thing to do with the T-Mo version is to flash the international ROM. The only thing people do on the T-Mo ROM is to SIM unlock, thus allow bootloader unlocking, then go right back to the international ROM.
CosmicInsight said:
This device is far from being "dead" the most common thing to do with the T-Mo version is to flash the international ROM. The only thing people do on the T-Mo ROM is to SIM unlock, thus allow bootloader unlocking, then go right back to the international ROM.
Click to expand...
Click to collapse
i have had to many issues with international that i msm back to tmobile.
i just didnt want to lose everything over an over doing this when things go wrong
i believe i have dumped the boot.img
i just hope it works when i do need it again.
Here's what I did whenever T-Mobile update to Android 10.0.1 I downloaded the OTA Update from off the internet then extracted it on my desktop then I used the payload-dumber-win64 to get the recovery and boot.img to use Incase I needed them. I used the extracted boot.img from the payload-dumber-win64 and followed instructions on how to use magisk patcher to patch my own boot.img. search Google for the T-Mobile update then use the tools to extract the whole thing.