Related
Hello all, and please help me with some small details before rooting.
I have an LG G2 with stock KITKAT 4.4.2., baseband M8974A-1.0.190084,kernel 3.4.0., build D80220b, software D80220b-219-02.
My questions
- do I need to upgrade stock firmware to D802d or D802f before rooting, and if yes wich is more stable
- is a SIM card needed (as inserted in the phone) for rooting process
- do I need to unlock the phone before rooting since it is locked with my local carrier (TELE 2 HR)
- does a custom ROM automaticly eliminate OTA upgrade and so prevent from bricking, or it must be unchecked manualy
- when installing a custom ROM (probably Cludy G3) do I need to flash a new custom kernel or it doesent mater (probably Bruce if it is compatibile)
- how does one check for compatibility ROM - kernel, is it just simple as finding "stock ROM" - "stock kernel" in the title
- do I need to instal a new KK baseband before custom ROM since I am allready on KITKAT
- do I need to do any kind of factory reset and/or wipe before rooting or later instaling a custom ROM
Thank you very much in advance, I have been searching all over for this simple answers but couldnt find any,
Sorry if the questions are too noobish but I am afraid tostart anything before I find the answers
tomarin said:
Hello all, and please help me with some small details before rooting.
I have an LG G2 with stock KITKAT 4.4.2., baseband M8974A-1.0.190084,kernel 3.4.0., build D80220b, software D80220b-219-02.
My questions
- do I need to upgrade stock firmware to D802d or D802f before rooting, and if yes wich is more stable
- is a SIM card needed (as inserted in the phone) for rooting process
- do I need to unlock the phone before rooting since it is locked with my local carrier (TELE 2 HR)
- does a custom ROM automaticly eliminate OTA upgrade and so prevent from bricking, or it must be unchecked manualy
- when installing a custom ROM (probably Cludy G3) do I need to flash a new custom kernel or it doesent mater (probably Bruce if it is compatibile)
- how does one check for compatibility ROM - kernel, is it just simple as finding "stock ROM" - "stock kernel" in the title
- do I need to instal a new KK baseband before custom ROM since I am allready on KITKAT
- do I need to do any kind of factory reset and/or wipe before rooting or later instaling a custom ROM
Thank you very much in advance, I have been searching all over for this simple answers but couldnt find any,
Sorry if the questions are too noobish but I am afraid tostart anything before I find the answers
Click to expand...
Click to collapse
1. You don't have to upgrade because you can use rooter that is compatible with your current firmware build, the differences between the firmware are only on their features, with less case of minor problem solved from previous build.
2. No, you don't need to put your SIM on.
3. Custom ROMs are meant to give you better performance of the current build, especially if it is Stock Based Custom ROM. Why you shouldn't update via OTA? because with several changes in the custom ROM, Official build will find it different from its official release, which would cause errors that could ended up with bootloop, even worse.. Hopefully, several developers also have their own OTA feature so people can easily get the update.
4. It doesn't matter since Custom ROMs sometimes come with their own suggested kernel that fit with the ROM. But you can also try other kernels if it suits you.
5. Yes, it is quite that simple, but also try to find out whether it is compatible or not with the ROM.
6. No, if you already on KitKat, you don't need to flash KK baseband.
7. Only when you are about to flashing new ROM..
Rei Zazie said:
1. You don't have to upgrade because you can use rooter that is compatible with your current firmware build, the differences between the firmware are only on their features, with less case of minor problem solved from previous build.
2. No, you don't need to put your SIM on.
3. Custom ROMs are meant to give you better performance of the current build, especially if it is Stock Based Custom ROM. Why you shouldn't update via OTA? because with several changes in the custom ROM, Official build will find it different from its official release, which would cause errors that could ended up with bootloop, even worse.. Hopefully, several developers also have their own OTA feature so people can easily get the update.
4. It doesn't matter since Custom ROMs sometimes come with their own suggested kernel that fit with the ROM. But you can also try other kernels if it suits you.
5. Yes, it is quite that simple, but also try to find out whether it is compatible or not with the ROM.
6. No, if you already on KitKat, you don't need to flash KK baseband.
7. Only when you are about to flashing new ROM..
Click to expand...
Click to collapse
Thank you very much for your detailed answers !! :good::good:
Sry about the terrible shorthand. Finally broke down and factory reset my verizon gs5. Before setting up i decided to roll it back, root it, and get a debloated PB1 rom from here:
https://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
So, if like me, and you have the nov/dec VZW OTA update on your phone PJ2 if i recall, this link got me rolled back and rooted. This method added busybox which i didn't really understand, safestrap which i actually kinda liked, and initially kingroot then the flash went to superSU.
I kinda liked the marshmallow os a touch better with the google now launcher and everything verizon as removed as possible vs 5.x.x. Basically the verizon OTA update to marshmallow essentially bricked my phone (not enough space after like 3 years of never re-formatting). I love my tablet that essentially runs just a bare bones no BS google android marshmallow software similar to what a pixel has or nexus had.
Doin more reading looking for such a rom i found this link:
https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909
This successfully unlocked the bootloader. They omit that you should make sure you have the rom on he phone or sd card before starting. So before using odin make sure the rom is on the phone and matched the bootloader unlocker you wish to use. This method of flashing used TWRP recovery which i found to be...different than safestrap but functional all the same.
QUESTION 1
Is there a rom for the SM-G900V that is similar or identical to a non branded google device like how the pixel comes stock?
I haven't messed around with the phone since unlocking the bootloader and flashing it to the VZW_BPB1_ODEX_DEODEX_V9 using the TWRP Recovery. Basically if my best bet is a debloated stock but rooted vzw rom that is 6.x.x and then manually removing/deactivating the garbage from vzw apps i'll do it. But figured this was the place to ask if there was already a rom out there that works on the SM-G900V. Because i can easily put a rom that does the job instead of tinkering more than i have too.
QUESTION 2
Now that i used the SafeStrap_PB1_Bootloader_Unlock_AIO.zip and flashed VZW_BPB1_ODEX_DEODEX_V9.zip using the method from the second link. It APPEARS i can just load a 6.x.x rom and use TWRP Recovery to flash that. Am i mistaken? Will i need to do the unlock bootloader process over for the PD1 PF4 or whatever boatloader unlocker corresponds with the rom. OR...now that the bootloader is no longer verizon'ed can i basically swap roms to my hearts content as long as they do not also try to install a new bootlaoder??
I have no idea how to "tag" either poster from the links i mentioned but i'm certain many here as well as they could answer both questions easily.
Hi, I have a big doubt about this. Is it possible to install a custom ROM based on Lollipop on a Pure updated to Marshmallow? Do I have to downgrade before doing that?
Thanks in advance.
PD: why not downgrading? because I still like Marshmallow, and I don't want to screw things up
lucianogm said:
Hi, I have a big doubt about this. Is it possible to install a custom ROM based on Lollipop on a Pure updated to Marshmallow? Do I have to downgrade before doing that?
Thanks in advance.
PD: why not downgrading? because I still like Marshmallow, and I don't want to screw things up
Click to expand...
Click to collapse
I've never tried this on this phone. My experience with other phones is that custom roms really don't care what firmware is on the phone. The worst thing I've had happen when flashing an outdated custom rom is it either won't boot at all, or sometimes it boots but won't work with your modem, you can't get data, maybe you can't make calls, and maybe the imei looks blank. Any time that has happened restoring a backup has fixed it for me, so don't panic and try to start restoring efs or injecting imei. Just make sure you have a nandroid backup available, or wipe and flash a known good rom. Everything will go back to normal on an up to date rom. Custom roms are just a boot image and a system, they aren't going to mess with your bootloader or modem; they just might not work with them.
We had working TWRP for clark before Marshmallow rolled out. When Marshmallow rolled out TWRP stopped booting on the Marshmallow bootloader. Hashbang fixed it pretty quick. I kind of suspect that Lollipop roms might fail to boot on the Marshmallow bootloader unless they are up to date enough to have that fix incorporated, but I'm just guessing. I also know from that week or two that some people rolled back to the Lollipop bootloader with no apparent ill affects. Read through late November to early December 2015 in the TWRP thread if you're curious.
This phone isn't particularly picky about flashing modems either. You would probably be ok if you rolled it back too, but I just wouldn't recommend it. You won't be able to downgrade the partition table. Lollipop firmware GPT.bin will fail if you try to fastboot flash a full firmware downgrade, and you'll be left in this weird mixed firmware environment. This phone really isn't very finicky about firmware, but tinkering too much with bootloaders and modems, particularly going backwards, is kind of asking for a brick. People get in all kinds of weird mixed states on clark and usually it just breaks wifi until they get things properly matched up again, not like some Samsung phones where mismatching the bootloader and modem or even just looking at them funny results in a hard brick. I'd just really hate for you to end up being one of the few who hard bricks, though.
---------- Post added at 09:11 AM ---------- Previous post was at 09:04 AM ----------
Oh yeah, almost forgot. That was all for AOSP or CM based roms.
If you try to flash a stock based LP rom on MM firmware it will almost certainly bootloop. If it does manage to boot, wifi probably won't work and maybe some other problems.
jason2678 said:
I've never tried this on this phone. My experience with other phones is that custom roms really don't care what firmware is on the phone. The worst thing I've had happen when flashing an outdated custom rom is it either won't boot at all, or sometimes it boots but won't work with your modem, you can't get data, maybe you can't make calls, and maybe the imei looks blank. Any time that has happened restoring a backup has fixed it for me, so don't panic and try to start restoring efs or injecting imei. Just make sure you have a nandroid backup available, or wipe and flash a known good rom. Everything will go back to normal on an up to date rom. Custom roms are just a boot image and a system, they aren't going to mess with your bootloader or modem; they just might not work with them.
We had working TWRP for clark before Marshmallow rolled out. When Marshmallow rolled out TWRP stopped booting on the Marshmallow bootloader. Hashbang fixed it pretty quick. I kind of suspect that Lollipop roms might fail to boot on the Marshmallow bootloader unless they are up to date enough to have that fix incorporated, but I'm just guessing. I also know from that week or two that some people rolled back to the Lollipop bootloader with no apparent ill affects. Read through late November to early December 2015 in the TWRP thread if you're curious.
This phone isn't particularly picky about flashing modems either. You would probably be ok if you rolled it back too, but I just wouldn't recommend it. You won't be able to downgrade the partition table. Lollipop firmware GPT.bin will fail if you try to fastboot flash a full firmware downgrade, and you'll be left in this weird mixed firmware environment. This phone really isn't very finicky about firmware, but tinkering too much with bootloaders and modems, particularly going backwards, is kind of asking for a brick. People get in all kinds of weird mixed states on clark and usually it just breaks wifi until they get things properly matched up again, not like some Samsung phones where mismatching the bootloader and modem or even just looking at them funny results in a hard brick. I'd just really hate for you to end up being one of the few who hard bricks, though.
---------- Post added at 09:11 AM ---------- Previous post was at 09:04 AM ----------
Oh yeah, almost forgot. That was all for AOSP or CM based roms.
If you try to flash a stock based LP rom on MM firmware it will almost certainly bootloop. If it does manage to boot, wifi probably won't work and maybe some other problems.
Click to expand...
Click to collapse
So there shouldn't be no big issues with an AOSP/CM ROM, right?
lucianogm said:
So there shouldn't be no big issues with an AOSP/CM ROM, right?
Click to expand...
Click to collapse
That's right. It might not work right, but it's nothing you can't recover from easily. Just make sure you have a backup or a zip for a ROM you know is OK handy.
jason2678 said:
That's right. It might not work right, but it's nothing you can't recover from easily. Just make sure you have a backup or a zip for a ROM you know is OK handy.
Click to expand...
Click to collapse
Yeah, that's the good thing. I have lots of zips and an old backup, I think I'm good to go
will update after flashing a rom. Thanks for your help!
The only issue you might run across is connectivity, the radio firmware changed a lot from Lollipop to the first Marshmallow release to current Marshmallow release... It is possible WiFi or Mobile data will not work, but you could either restore back to a working ROM or flash the correct radios from Lollipop ROM.
Be aware, although the Moto X is pretty tolerant of flashing lots of varied stuff, Moto devices in general like to complain when being downgraded, and some E/G series have been semi-bricked doing this depending on what version they started with.
Hi everyone I'm new to samsung devices but definitely not to android in general since I come from years of htc devices, root, flashing and so on.. still I am facing a bit of confusion here so instead of writing in every single thread I'll ask you here my questions:
1. As I read on TWRP official thread "it's incredibly hard to brick a sam device"; anyway I understand that this is never a risk free process but reading the comments it seems like people on nougat firmware are facing some kind of trouble so my question is: Is it safe to flash twrp on nougat firmware? And which one? 3.1.1-0 latest version should be fine right?
2. Let's suppose I'm now on twrp but instead of rooting the stock rom I flash directly a custom rom, I still need to flash "dm-verity and force encryption disabler"? After some reading I see people that flashes this after every new rom, someone suggests to use 2.2 version but the latest is 5.xx and the content of the zips is different between this two versions (5.xx contains a chromeos folder, the other one no??)
3. "Update modem and bl" , this is meant for those who want to flash a rom based on a higher firmware right? I'm on the latest (may security update) so there's no need to update modem and bl at least I think (?)
That's all, I'm sorry for this long post and my bad english!
Hi All,
Complete noob here, so please be gentle!
I recently bought a new, "unlocked" LG V20 from an auction site.
The trouble is it came with AT&T carrier ROM, which being in the UK and not on AT&T means that it's stuck with the all of the branding and no access to updates.
Build number: NRD90M
Software version: H91010I
Android security patch level: December , 2016
If it's at all possible, I'd like to flash it with a generic non-carrier LG ROM, but unsure of what ROMs are safe to use on this phone, or exactly how to go about doing it.
I've looked at lots of forums and Youtube videos, but many of the links I've found are broken, or the instructions assume a level of previous knowledge that I don't have.
I'm not looking for the very latest firmware, or any trick customisations. I just want a phone that doesn't annoy me!
Can anyone advise what ROM to use, where to download it, and step by step instructions to install it without bricking my phone.
TIA
Bassman_62
Bassman_62 said:
Hi All,
Complete noob here, so please be gentle!
I recently bought a new, "unlocked" LG V20 from an auction site.
The trouble is it came with AT&T carrier ROM, which being in the UK and not on AT&T means that it's stuck with the all of the branding and no access to updates.
Build number: NRD90M
Software version: H91010I
Android security patch level: December , 2016
If it's at all possible, I'd like to flash it with a generic non-carrier LG ROM, but unsure of what ROMs are safe to use on this phone, or exactly how to go about doing it.
I've looked at lots of forums and Youtube videos, but many of the links I've found are broken, or the instructions assume a level of previous knowledge that I don't have.
I'm not looking for the very latest firmware, or any trick customisations. I just want a phone that doesn't annoy me!
Can anyone advise what ROM to use, where to download it, and step by step instructions to install it without bricking my phone.
TIA
Bassman_62
Click to expand...
Click to collapse
Theirs a h910 root thread in the guide section >
https://r.tapatalk.com/shareLink?ur...share_tid=3664500&share_fid=3793&share_type=t
Being on 10i dirty santa method may work
I always stayed with stock rooted debloated roms on the V20. Most all the custom roms don't support the second screen or have something else I just didn't like.
I have a stock rooted Oreo thread in the developer section that I used for months until I got the PH1 [emoji16]
Sent from my PH-1 using Tapatalk
Use dirty santa, to unlock the bootloader and root, then you can flash 996 rom which should be unbranded
Sent from my LG-H910 using XDA Labs
Try Super Rom. It's bare bones. No bloatware from LG or ATT.
Follow the steps here to flash TWRP https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500. I'm having trouble with backups fully restoring, but it works otherwise.
I'd imagine you could install Super Rom right after you can access TWRP, but I haven't tried it. I did it after flashing 10r.
Download Super Rom and put it on your SD card. Flash it after wiping everything https://forum.xda-developers.com/v20/development/rom-superv20-h918-t3764390. During the installation, it will ask you if you want to flash a kernel. Select mk2000. The speed difference is astounding. It's slow and lags without the kernel, but extremely fast if you include it. Boot system and set it up. Then go back to TWRP and flash SuperSU for root.
jeremyn87 said:
Try Super Rom. It's bare bones. No bloatware from LG or ATT.
Follow the steps here to flash TWRP https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500. I'm having trouble with backups fully restoring, but it works otherwise.
I'd imagine you could install Super Rom right after you can access TWRP, but I haven't tried it. I did it after flashing 10r.
Download Super Rom and put it on your SD card. Flash it after wiping everything https://forum.xda-developers.com/v20/development/rom-superv20-h918-t3764390. During the installation, it will ask you if you want to flash a kernel. Select mk2000. The speed difference is astounding. It's slow and lags without the kernel, but extremely fast if you include it. Boot system and set it up. Then go back to TWRP and flash SuperSU for root.
Click to expand...
Click to collapse
Wrong! Flash root immediately after you flash the rom
Sent from my LG-H910 using XDA Labs
You can just flash a US996 KDZ using patched LGUP, unticking modem. Don't accept OTA updates though
Thanks all,
Not been ignoring you - just crazy busy.
So if i understand correctly, the 996 rom will give me a stock, unbranded V20 with the 2nd screen working?
Is there any particular version of the rom to look for, or any to avoid.
TIA (again)
Update
I posted something else here, which wasn't relevant.
Bassman_62 said:
Thanks all,
Not been ignoring you - just crazy busy.
So if i understand correctly, the 996 rom will give me a stock, unbranded V20 with the 2nd screen working?
Is there any particular version of the rom to look for, or any to avoid.
TIA (again)
Click to expand...
Click to collapse
Just flash the newest US996 KDZ, don't worry about modem (they're both GSM only devices, so US996 modem should work on the h910, and it'll also change the unlocked-bands to US996). Use the patched LGUP from this forum, it allows cross flashing