[ROM] [STOCK] [H901] V10_H901_V20L Update: [11/12/2016]

[civilwarrock]

Im sad to report I found a problem..

I always charge my phone while its off, powering it off completely and then plugging it in, and tonight it went to show the battery charging symbol but then the black square that says "Device cannot be checked for corruption" showed up and I thought maybe it will still charge normally. Sadly this is not the case. After a few seconds my device rebooted and went back into the system.

I really hate to bother you with this Eliminater74, but is there a way we can fix this one?

I greatly appreciate your work, so please don't take this the wrong way. If there is anything I can do to help, please let me know.

Thanks!

 

[shawn1]

Otherwise from. "device cannot be checked for corruption" on start up Rom works good

 

[ceyo14]

Well I pulled the battery after flashing part 2 the 1.3gb one and got the red letters, something about mismatch, but proceeded to unlock bootloader.... took the command like normal and when it booted, got the "Your device software can't be checked for corruption" screen... I can see the lg logo screen behind it... well the powered by android part, but it stays there, it gets really hot. left it there for a while but doesn't do anything else. can enter fastboot but not recovery. cant execute fastboot oem relock...

this was Stock 5.1.1 rooted. didn't unroot or anything. just followed this guide. had the MM TWRP, and part 2 took like 30 minutes on extracting data...

 

[OriginalShinken1]

When I flashed the original 2 part (prior to deodex) I was using twrp 3.01 and the Korean port.
Fastboot and adb are all working great. This is the stock Rom I've been waiting for. Thank you, Eliminater74.
P.s. I've been coming to this site since my HTC Tytn days (winmo) and this is one of the best devs I have had the pleasure of using his work. Thanks again and a beer coming your way this week.

-sent from this device using this app.

 

[gustav30]

Hi,
Just curious if this is a rom only, or is it also flashing firmware files? Radio, hboot, etc...

Thanks

Sent from my LG-H901 using Tapatalk

 

[Kalash]

Weird issue.... RESOLVED (see bottom of post)

Everything flashed fine from TWRP 3.0.0-2
It's working great - except for one problem that developed - I can't get text messages any more. I can send them... calls work... but I'm not getting any incoming texts.

I DID get texts - verification for Google 2-step authentication during device setup - but now they aren't working (trying to get another text to verify the account to setup Google Authenticator).

I didn't root - kinda wanted Android pay for once...
Chatting with t-mobile trying to figure out the texting thing...

---------- Post added at 05:46 AM ---------- Previous post was at 05:35 AM ----------

Hi,
Just curious if this is a rom only, or is it also flashing firmware files? Radio, hboot, etc...

Thanks

Sent from my LG-H901 using Tapatalk

It does everything (part one) and then the OS (part two).

T-mobile said they're sending an over the air activation to get texting to work - give it two hours, get the "welcome text" - reboot, try sending myself a message, and see what happens. She "assures me it'll work." HA!
We'll see in a couple hours.




ALSO - UPDATE FOR INSTALLATION INSTRUCTIONS; when pulling the battery from recovery, ALSO pull the microSD card so it's not wiped when you do the OEM unlock in Fastboot.
A backup is still a good idea, but we know what step wipes the card, and you have the back off the phone anyway....
(unless not wiping my SD card, and putting it back in after the OEM wipe is the reason my texts stopped working, but I can't believe that's the case....)



UPDATE:
Ok - SMS works again. I don't know if it was contacting T-mobile and having them send the OTA activation, or if it was one of the apps I installed... I uninstalled MightyText and Beeter (twitter app), and as soon as beeter was uninstalled, texts started working again.
I put them back on in reverse order - beeter, then MightyText, and SMS still works....
So.... I dunno. Either a problem with Beeter - or you may need to contact T-Mobile if SMS breaks after a couple hours.

 

[alphahere]

Im sad to report I found a problem..

I always charge my phone while its off, powering it off completely and then plugging it in, and tonight it went to show the battery charging symbol but then the black square that says "Device cannot be checked for corruption" showed up and I thought maybe it will still charge normally. Sadly this is not the case. After a few seconds my device rebooted and went back into the system.

I really hate to bother you with this Eliminater74, but is there a way we can fix this one?

I greatly appreciate your work, so please don't take this the wrong way. If there is anything I can do to help, please let me know.

Thanks!

My device has the error message but does not boot into system. Battery charges while phone is off without rebooting.

Just another data point.

 

[Kalash]

My device has the error message but does not boot into system. Battery charges while phone is off without rebooting.

Just another data point.

I'll second this. Plug in, error message, black, battery, screen goes off, battery again (or I just stopped paying attention, or wiggled the cable or something), then black and (presumably) charging.
Tap power - back to battery, still indicates it's charging. Press (briefly - not really a press and hold, but longer than the quick tap for battery check) to reboot.

Fingerprints DO NOT work to unlock after a reboot, but as soon as I tap code in, fingerprints work in-apps and for screen unlocks until another reboot.
I can live with this - since I rarely reboot anyway, but it is a thing to note.

 

[alphahere]

Same error message here but so far working great. I flashed it twice thinking I did something wrong but still have the wonderful error message - "Device cannot be checked for corruption". I kinda like the error message. Reminds me of samsung Knox error message. Whatever. After LG pulled this BS, this will be my last none nexus device unless something drastic changes. I hate this because I really like this device better than current nexus devices. I really like a device with a removable battery but that looks like a thing of the past. Disposable locked down phones equals to bigger profits is the way to go for the companies that makes these phones.

Anyway looks like all devices are being locked down. To protect the poor user, Right!

Thanks to the wonderful developers and the excellent instructions my devices is still free to root.

Whatever.

 

[HtcOnekid]

Fingerprints DO NOT work to unlock after a reboot, but as soon as I tap code in, fingerprints work in-apps and for screen unlocks until another reboot.
I can live with this - since I rarely reboot anyway, but it is a thing to note.

Fingerprint unlock we always require a pin or code after a reboot. Like iPhone every time you reboot you need to enter your password first

Sent from my LG-H901 using XDA-Developers mobile app

 

[ceyo14]

Update, I WAS able to boot to TWRP (harder this time for some reason, maybe just timing from frustration) although it did show the message and got stuck a little, i left it a little bit more and it booted TWRP! was able to flash the part 2 zip again using SD Card since computer wouldnt recognize the phone for adb sideload and restarted at after a bit it booted up completely. YAY!

so, recap, flash part 2, and make sure it finishes!, if not reboot to recovery again (using buttons) and flash again! (I used the same download, so maybe a fluke from the phone, dont know, but it did flash correctly afterwards)

after it succesfully flashed, even if you get the red letters, do the fastboot oem unlock (I actually did this before the succesful flash and it still worked.)

This is what I did and it worked! everything is working, only thing the fingerprint needs knockcode at first boot.

---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------

Fingerprint unlock we always require a pin or code after a reboot. Like iPhone every time you reboot you need to enter your password first

Sent from my LG-H901 using XDA-Developers mobile app

The thing is, this is new. It wasnt like this in LP...

 

[Galadriel7966]

Just to give positive feedback and clarify problems are not occurring on all devices.. Fingerprint, and pretty much everything else is working excellent!! I followed the directions in original op and also read to find the directions about the oem unlock.. and everything works great.. Been running for a few days now.. Excellent work!!!

Sent from my LG-H901 using XDA-Developers mobile app

 

[Kalash]

Just to give positive feedback and clarify problems are not occurring on all devices.. Fingerprint, and pretty much everything else is working excellent!! I followed the directions in original op and also read to find the directions about the oem unlock.. and everything works great.. Been running for a few days now.. Excellent work!!!

Sent from my LG-H901 using XDA-Developers mobile app

Now that SMS is working again, I'm issue free (for now )
The fingerprint thing is a change from LP - where you could use a fingerprint for the initial unlock after a boot. It isn't a problem - but it is an undocumented change that may make it APPEAR that the finger print reader isn't working (it was bugging me for a while until I got distracted, set the phone down during my insanely long setup process and it locked - then the fingerprint reader worked).

There used to be a saying, "That's not a bug, that's a feature."
And... yeah... that's what it is. Extra security after a reboot. It's a feature that's interpreted by spoiled lazy LP users (What? I'll admit to anything, if it's true.) as a bug. On the bright side, since you'll have to use it after a reboot, you're less likely to forget your lock code - seeing as how you only needed it when your fingers were cold or wet in LP =P

 

[baturcotte]

Folks, don't panic about the "Device cannot be checked for corruption" messages. It is a side effect of modified/unlocked bootloaders: see this article for more explanations: http://www.androidauthority.com/goo...rrupted-and-modified-android-software-629180/

 

[truckerdewd]

Folks, don't panic about the "Device cannot be checked for corruption" messages. It is a side effect of modified/unlocked bootloaders: see this article for more explanations: http://www.androidauthority.com/goo...rrupted-and-modified-android-software-629180/

After reading that article, I now remember reading it last after MM started rolling out in the late summer/early fall. Some thought it meant goodbye to root.

Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

 

[Amd4life]

The OP is an ALL STAR. Amazing work. Some of your posts in this thread are extremely helpful for those that want to learn, and I'm certainly impressed that the OP learned to code just to stay out of trouble. WOW!!

 

[shawn1]

I gotta say this ROM is awesome it looks very good as fast as heck I had a little issue but I am loving it thanks again man thank you very much for sticking with the V10

 

[Eliminater74]

FYI: I just want everyone to know that This isnt all my work. With the help of @aclegg2011 Who isnt affiliated with Nebula, but works great as a team with me, And not to mention all you users
who didnt give up and kept trying........ My father was a captain in the military, and Giving up was not an option... And the word CANT.. Doesnt exist...........

But what I just read in this thread, Now reminds me of my g3 threads.. Good to see peepz learning and sharing..........................

Thank you all for your help............................ But as I said, Dont forget @aclegg2011, Hes the one that brought you CM13 before he even had the device in his hands..
That dude is very good at what he does............................

Working as a TEAM is what made America what it is.. Same here.. Help each other rather then bashing each other..............

Im sorry about my attitude lately, but I got alot of stuff going on... and I still Develop for the G3.. Them peepz count on me.. and I refuse to let them down..................
When my Main board went out in my G3.. Them G3 peepz are the ones that paid for my new board.. Now you understand.. I cant and wont turn my back on them............

 

[shawn1]

To each and every one. Help build this rom I just wanted to say thank you all I love it

 

[ragzz03]

So I am already on 6.0 specifically the korean port of MM. The whole bricking your phone if you try to go backwards is kinda scary so I am hesitant to flash anything. At which step should I jump in on in the instructions. Step 1 assumes im not on 6.0 so if you are, at which point should i pick up? @Eliminater74

I am also on TWRP 3.0.1-0

thanks in advance.