First of all sorry for my english.
I hope someone can help with this
The thing is that the screen burn issue showed up, so i've seen a guide to remove it (kernel auditor and that..) So i was going for root my device (Nougat)
and i've unlocked my bootloader and installed twrp but the thing is that i didnt installed Elemental Kernel, and ****ed it up installing superSU..
So i decided to install another rom, coming from npj25.93-14 , i've installed Extended AOSP 7.1.2. And everything it's ok but the volume isn't working properly, so i want to install my previous rom npj25.93-14 (Nougat) from the stock xt1622 how can i do it?
Cant find any rom of npj25.93-14 xt1622 , even if i found one, i dont really know the steps to do it properly ( i mean: flashing with twrp, or fastboot.. )
Can someone please make a little "guide"?, i fell so lost right now
Alexmofu said:
First of all sorry for my english.
I hope someone can help with this
The thing is that the screen burn issue showed up, so i've seen a guide to remove it (kernel auditor and that..) So i was going for root my device (Nougat)
and i've unlocked my bootloader and installed twrp but the thing is that i didnt installed Elemental Kernel, and ****ed it up installing superSU..
So i decided to install another rom, coming from npj25.93-14 , i've installed Extended AOSP 7.1.2. And everything it's ok but the volume isn't working properly, so i want to install my previous rom npj25.93-14 (Nougat) from the stock xt1622 how can i do it?
Cant find any rom of npj25.93-14 xt1622 , even if i found one, i dont really know the steps to do it properly ( i mean: flashing with twrp, or fastboot.. )
Can someone please make a little "guide"?, i fell so lost right now
Click to expand...
Click to collapse
If you didn't make a backup then you need to grab the stock MM firmware for your XT1622, flash it via fastboot, and take the OTA.
Maybe if you used a cool little tool called "le Google" along with the forums here on XDA, you wouldn't have these issues. There are so many goddamn guides that it's almost ridiculous.
negusp said:
If you didn't make a backup then you need to grab the stock MM firmware for your XT1622, flash it via fastboot, and take the OTA.
Maybe if you used a cool little tool called "le Google" along with the forums here on XDA, you wouldn't have these issues. There are so many goddamn guides that it's almost ridiculous.
Click to expand...
Click to collapse
I've been searching for a long time, and some people said that i cant get OTA if i downgrade to MM..
Alexmofu said:
I've been searching for a long time, and some people said that i cant get OTA if i downgrade to MM..
Click to expand...
Click to collapse
If you're rooted, then yea, OTAs won't work. If you're not OTAs should work fine- just restore stock MM, take the OTA to N and then root.
Also, you could give RevivorOS a shot- it's based off the latest 14-4 N build and works fine on all G4/G4+ models.
negusp said:
If you're rooted, then yea, OTAs won't work. If you're not OTAs should work fine- just restore stock MM, take the OTA to N and then root.
Also, you could give RevivorOS a shot- it's based off the latest 14-4 N build and works fine on all G4/G4+ models.
Click to expand...
Click to collapse
Thanks!
negusp said:
Maybe if you used a cool little tool called "le Google" along with the forums here on XDA, you wouldn't have these issues. There are so many goddamn guides that it's almost ridiculous.
Click to expand...
Click to collapse
True that! But there are probably 10x as many people (not always noobs), who have made the same or similar mistakes. We all tend to get in a hurry at times and have regrets. Patience is an honorable virtue, both for the student and the teacher. Just sayin'.
Related
I'm really going to die soon. I spent the whole day trying to restore my IMEI as I don't have the original box (bought it second hand just the phone alone) and did not have EFS back up prior to flashing.
So, the whole mess was when I flashed Dorimanx for D800 instead of my variant which is D805 (my careless mistake, the title of the page was really confusing). Ever since, I lost my IMEI is shown as 0 or null so does my baseband. I then flashed ResurrectionRemix, PowerG2, etc. but still unable to get any mobile network connection.
I've tried reverting to stock KitKat firmware but to no avail. I've flash other modems as well with no success. I've even tried the QST NvManager switching from Windows 10 to 7 and re-installing the USB drivers numerous times still no luck. I followed so many forums and watched endless youtube tutorials none of them can fix my problem.
I'm really desprate, please help me.
how can the tile be confusing.? even qhen you go to download page theres all the variants. was kernel really the culprit of this.? am not really sure that kernel would damage imei and baseband i think flashing bootloaders do. twrp wrong rom. ect. you should post this in the q&a thread. i know some have restored imei.
raptorddd said:
how can the tile be confusing.? even qhen you go to download page theres all the variants. was kernel really the culprit of this.? am not really sure that kernel would damage imei and baseband i think flashing bootloaders do. twrp wrong rom. ect. you should post this in the q&a thread. i know some have restored imei.
Click to expand...
Click to collapse
Dear @raptorddd
Thank you for your feedback and I'm sorry. I did not blame the kernel as in whole context but rather my careless mistake and take note I suspected my problem was flashing the kernel for the wrong model variant so it was not actually Dorimanx's issue, no offense I even admitted my wrong-doing.
Anyway, after reading your reply at least there is a light to my answer. I will do some more research on bootloaders for my exact variant because most of the threads found here are for D802 International while mine is Brazil (Latin America) although I'm from SEA.
I was very happy when I see 6.0 MM on this frakenstein device but now I have this network problem making me sad. It's like having an old car with a new engine but no wheels. Please help.
cglegion said:
Dear @raptorddd
Thank you for your feedback and I'm sorry. I did not blame the kernel as in whole context but rather my careless mistake and take note I suspected my problem was flashing the kernel for the wrong model variant so it was not actually Dorimanx's issue, no offense I even admitted my wrong-doing.
Anyway, after reading your reply at least there is a light to my answer. I will do some more research on bootloaders for my exact variant because most of the threads found here are for D802 International while mine is Brazil (Latin America) although I'm from SEA.
I was very happy when I see 6.0 MM on this frakenstein device but now I have this network problem making me sad. It's like having an old car with a new engine but no wheels. Please help.
Click to expand...
Click to collapse
lets see what @Art Vanderlay has to say if he can help.
cglegion said:
Dear @raptorddd
Thank you for your feedback and I'm sorry. I did not blame the kernel as in whole context but rather my careless mistake and take note I suspected my problem was flashing the kernel for the wrong model variant so it was not actually Dorimanx's issue, no offense I even admitted my wrong-doing.
Anyway, after reading your reply at least there is a light to my answer. I will do some more research on bootloaders for my exact variant because most of the threads found here are for D802 International while mine is Brazil (Latin America) although I'm from SEA.
I was very happy when I see 6.0 MM on this frakenstein device but now I have this network problem making me sad. It's like having an old car with a new engine but no wheels. Please help.
Click to expand...
Click to collapse
I don't know how a kernel can wipe your imei. Have you changed roms succesfully before? Have you used ioroot on it? Ioroot makes efs backups automatically. That would help.
cglegion said:
I'm really going to die soon. I spent the whole day trying to restore my IMEI as I don't have the original box (bought it second hand just the phone alone) and did not have EFS back up prior to flashing.
So, the whole mess was when I flashed Dorimanx for D800 instead of my variant which is D805 (my careless mistake, the title of the page was really confusing). Ever since, I lost my IMEI is shown as 0 or null so does my baseband. I then flashed ResurrectionRemix, PowerG2, etc. but still unable to get any mobile network connection.
I've tried reverting to stock KitKat firmware but to no avail. I've flash other modems as well with no success. I've even tried the QST NvManager switching from Windows 10 to 7 and re-installing the USB drivers numerous times still no luck. I followed so many forums and watched endless youtube tutorials none of them can fix my problem.
I'm really desprate, please help me.
Click to expand...
Click to collapse
i will solve ur issue through teamviewer just msg me on my whatsaapp no +917744894155
Art Vanderlay said:
I don't know how a kernel can wipe your imei. Have you changed roms succesfully before? Have you used ioroot on it? Ioroot makes efs backups automatically. That would help.
Click to expand...
Click to collapse
@raptorddd @Art Vanderay
I figured out. My phone is actually the D802 variant. It is obviously shown at the back of the case and when I open the back case, the model number is also printed just underneath the battery D802. I thought it was D805 because when I bought this phone it was already rooted and running PowerG2 and the model shown at the About page was D805. This is why I started looking for stock firmware for D805, TWRP D805, Dorimanx D805, and everything D805. So, when I downloaded ResurrectionRemix 6.0 MM, that was when my phone started to act weird but I'm very sure it was not RR issue as well. I wipe all my partitions without making any backup just before I started flashing things. I've done this 1000 times with no problem and this is the only time I got it wrong. I've tried flashing the bootlader changer aroma, then KitKat bootloader stock and still no IMEI, the phone number shown as unkown. I now got back my baseband because I flashed the KitKat baseband.
I'm going to start all over again today, and I'm getting all the files for D802 instead and will let you guys know if I can restore my IMEI back. Thank you for your participation on my thread, very much appreciated.
kalpesh patil said:
i will solve ur issue through teamviewer just msg me on my whatsaapp no +917744894155
Click to expand...
Click to collapse
I'm sorry, I have a soft-bricked phone right now with no spare phones, so I don't have WhatsApp at the moment but thank you really for your effort and offer. Can you explain on the forum instead of TeamViewing so others that have this problem and reading this thread can solve theirs? +1 for you.
YES YES YES!!!!!!!!!!!!!!!!!!!!! I FOUND THE ANSWER ALREADY. Please ignore the caps, this is just to show you how happy I am.
I've spent approximately 48 hours to figure what the heck is going on.
What I did was:
1. Flash stock firmware Brazil KitKat D805 .kdz through LG FlashTool 2014.
2. Use ioroot25 to root it via adb.
3. After rooting, download AutoRec.apk for KitKat and install that.
4. Download TWRP bumped latest and flash it to replace AutoRec's old version of TWRP.
5. Flash Dorimanx KitKat 10.9 (at the time of this post) or latest.
6. Flash KitKat stock baseband and modem for 20d.
After rebooting system, everything is ok. I got back my mobile network now. So happy!!! I'm requesting the moderator to close this thread as my question as been solved.
cglegion said:
YES YES YES!!!!!!!!!!!!!!!!!!!!! I FOUND THE ANSWER ALREADY. Please ignore the caps, this is just to show you how happy I am.
I've spent approximately 48 hours to figure what the heck is going on.
What I did was:
1. Flash stock firmware Brazil KitKat D805 .kdz through LG FlashTool 2014.
2. Use ioroot25 to root it via adb.
3. After rooting, download AutoRec.apk for KitKat and install that.
4. Download TWRP bumped latest and flash it to replace AutoRec's old version of TWRP.
5. Flash Dorimanx KitKat 10.9 (at the time of this post) or latest.
6. Flash KitKat stock baseband and modem for 20d.
After rebooting system, everything is ok. I got back my mobile network now. So happy!!! I'm requesting the moderator to close this thread as my question as been solved.
Click to expand...
Click to collapse
great news, but i got confused is it a d802 or 805?
raptorddd said:
great news, but i got confused is it a d802 or 805?
Click to expand...
Click to collapse
I'm not sure also. The back case written as D802 and just below the battery also written as D802. But when I tried to go back to stock I was unable to use D802 firmware but only can use D805 stock firmware. I'm now on Google Edition 1.3 the model is written as D802. When I try to flash stock D805 firmware I can't get through already. Im not sure why but as long as I can use the phone right now, I don't want to bother so much about that.
cglegion said:
I'm not sure also. The back case written as D802 and just below the battery also written as D802. But when I tried to go back to stock I was unable to use D802 firmware but only can use D805 stock firmware. I'm now on Google Edition 1.3 the model is written as D802. When I try to flash stock D805 firmware I can't get through already. Im not sure why but as long as I can use the phone right now, I don't want to bother so much about that.
Click to expand...
Click to collapse
LOL yeah at least you got it working. say hows google edition.? have you used other and compare?
raptorddd said:
LOL yeah at least you got it working. say hows google edition.? have you used other and compare?
Click to expand...
Click to collapse
So far, Google Edition 1.3 is the best/stable among all other ROMS that I've tried like Power G2, RR, etc. Nice battery life, 100% in the morning and came back from work still have another 30%-40% (usage mainly for WhatsApp, Facebook, internet browsing occasionally, no movie/music/games-just COC once or twice). This is the most straight-forward ROM and the closest to Stock Lollipop from Google without any other 3rd party apps and bloatwares. Very stable, no FC, great camera, and knock code gestures (flashed additional QuickMemo+ which isn't included by default). Awesome!
cglegion said:
So far, Google Edition 1.3 is the best/stable among all other ROMS that I've tried like Power G2, RR, etc. Nice battery life, 100% in the morning and came back from work still have another 30%-40% (usage mainly for WhatsApp, Facebook, internet browsing occasionally, no movie/music/games-just COC once or twice). This is the most straight-forward ROM and the closest to Stock Lollipop from Google without any other 3rd party apps and bloatwares. Very stable, no FC, great camera, and knock code gestures (flashed additional QuickMemo+ which isn't included by default). Awesome!
Click to expand...
Click to collapse
thanks i will try it in the future when they release for d800, i could do the patch to any rom but........ ill wait. :good:
kalpesh patil said:
i will solve ur issue through teamviewer just msg me on my whatsaapp no +917744894155
Click to expand...
Click to collapse
My G3 is OK now! Thak's to @kalpesh patil
100% trusted member!
So I am wanting to root my phone (for multiple reasons - tether reenabled, other fun software, etc), but if I do that, I'd like to move to 6.0.1 if possible. Before I do it, I wanted to check to see if the Stock rom in this would work: http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242 I am a little concerned about using this ROM since it's modified from the 1572 ROM and what might happen with little bugs. Wish I could just do an easy root without having to do a whole bunch of crap to get it done (like my old Galaxy S4 that was easy to root with towelroot.)
Are there any other disadvantages to using this besides not having future OTA updates? (not that I am really expecting any more for Motorola these days.)
this is all documented in the original 6.0.1 thread. Flash all 6.0.1 files except modem, flash twrp, flash su 2.62-3, flash franken.
lafester said:
this is all documented in the original 6.0.1 thread. Flash all 6.0.1 files except modem, flash twrp, flash su 2.62-3, flash franken.
Click to expand...
Click to collapse
Sorry, I didn't think it was that clear.
Thank you.
Hello everybody,
I have a Moto x play running CM 13. I followed the process listed somewhere in this forum and successfully installed cm 13.
Bad news is my laptop got stolen at uni. I had installed Motorola drivers and all that stuff in there, so now I'm wondering if I can go through this process without that laptop. I hope I can.
I only have the cellphone and I would like to return it to its original firmware so I can sell it.
Is there a safe way to do this without "bricking" my phone? I'm not very well versed in these processes and managed to install cm13 only because the procedure was very clear. I hope you guys can help me!
The original carrier is Iusacell (Mexico), although the cellphone itself is unlocked and takes any Sim.
thanks in advance!
gabrsmn said:
Hello everybody,
I have a Moto x play running CM 13. I followed the process listed somewhere in this forum and successfully installed cm 13.
Bad news is my laptop got stolen at uni. I had installed Motorola drivers and all that stuff in there, so now I'm wondering if I can go through this process without that laptop. I hope I can.
I only have the cellphone and I would like to return it to its original firmware so I can sell it.
Is there a safe way to do this without "bricking" my phone? I'm not very well versed in these processes and managed to install cm13 only because the procedure was very clear. I hope you guys can help me!
The original carrier is Iusacell (Mexico), although the cellphone itself is unlocked and takes any Sim.
thanks in advance!
Click to expand...
Click to collapse
to flash original firmware without PC you can use Chainfire's Flashfirehttp://forum.xda-developers.com/general/paid-software/flashfire-t3075433, however - it's still kinda experimental, needs some knowlege, and I'm not really sure if it supports our device. Reading through its thread may give you some clues. This will not revert your phone to out-of-the-box condition - that would take relocking your bootloader and PC is needed to do so (warranty will be still voided anyway). So maybe just try flashing some stock ROM in TWRP. The procedure will be the same as flashing CM.
minimale_ldz said:
to flash original firmware without PC you can use Chainfire's Flashfirehttp://forum.xda-developers.com/general/paid-software/flashfire-t3075433, however - it's still kinda experimental, needs some knowlege, and I'm not really sure if it supports our device. Reading through its thread may give you some clues. This will not revert your phone to out-of-the-box condition - that would take relocking your bootloader and PC is needed to do so (warranty will be still voided anyway). So maybe just try flashing some stock ROM in TWRP. The procedure will be the same as flashing CM.
Click to expand...
Click to collapse
I feel more comfortable with the second option. I found this github with MXP ROMs for my country and carrier: https://github.com/motoxplay/stock
I honestly can't remember if I had it at the beginning with Android 5 or 6. What happens if I flash Android 6 and it originally was 5? I suppose I should make a backup "nandroid" first.
BTW, can the bootloader be locked again via a new PC?
gabrsmn said:
I feel more comfortable with the second option. I found this github with MXP ROMs for my country and carrier: https://github.com/motoxplay/stock
I honestly can't remember if I had it at the beginning with Android 5 or 6. What happens if I flash Android 6 and it originally was 5? I suppose I should make a backup "nandroid" first.
BTW, can the bootloader be locked again via a new PC?
Click to expand...
Click to collapse
Flashing newer firmware won't break anything, it's a normal update. Worse thing would be if you tried to flash Lollipop over Marshmallow.
Making backup is always a good idea, do mind however, that flashing full stock firmware means overwriting your TWRP with stock recovery. Also, be aware the files you linked are actually firmware and not TWRP flashable zips.
And yes, you should be able to relock bootloader with original firmware.
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 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