Database Info

[RECOVERY][CWM] CWM for Huawei Vitria(Y301-A2)

* Your warranty is now void.
I am not responsible if this causes your device to be bricked, for the planets to align, monkeys take over the earth, nuclear war, missed sexual favors or whatever nonsense ensues due to your device not working. Please do some research if you have any concerns before flashing.
By using this recovery you agree to these terms!
Click to expand...
Click to collapse
Clockworkmod Advanced 5
http://d-h.st/BNT
Bugs
-cwm runs in background while charging(Fixed)
-tell me?
Install
(requires unlocked bootloader)
Code:
fastboot flash recovery recovery.img
To enter CWM(or stock recovery) turn off and then hold vol up+power
https://github.com/KainXS/android_device_huawei_y301a2/tree/cwm
Credits
ShabbyPenguin - Phandroid
KINGbabasula
CNexus

Would you be able to port CWM to a Huawei G526-L22?
Specs are similar to this Vitria(Y301-A2).
Tried this .img but can't mount /cache/recovery etc
extendcommand threw up failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache
(no such file or directory)Yet that path/directory is present in file explorer.Any assistance would be much appreciated.
The device has been discounted to AU$99 so a lot of geeks have grabbed them and are looking for mods
As is the norm for android heads ;|}Regards from Down Under
Gomax

gomax said:
Would you be able to port CWM to a Huawei G526-L22?
Specs are similar to this Vitria(Y301-A2).
Tried this .img but can't mount /cache/recovery etc
extendcommand threw up failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache
(no such file or directory)Yet that path/directory is present in file explorer.Any assistance would be much appreciated.
The device has been discounted to AU$99 so a lot of geeks have grabbed them and are looking for mods
As is the norm for android heads ;|}Regards from Down Under
Gomax
Click to expand...
Click to collapse
do you have the original recovery backed up
and can you run these commands while its booted in android with adb
cat /proc/partitions (info on partition sizes)
run ls too
and did you just take the image and flash it without modifying it.

Was sent the image by a developer, who has sent a revised version which works.
Thanks for your interest.

good to hear:good:
but did you really flash the recovery without modifying anything and it booted on the 526

KainXSS said:
good to hear:good:
but did you really flash the recovery without modifying anything and it booted on the 526
Click to expand...
Click to collapse
Both versions booted OK.
The first didn't mount external card.

gomax said:
Both versions booted OK.
The first didn't mount external card.
Click to expand...
Click to collapse
wow if it booted unmodified at all, these devices must be extremely similar minus the screen, hopefully kernel source pops up for one of them, guess the recovery fstabs were different though
edit
the link is gone?

I requested the source code for the vitria a month ago and huawei just released it
http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=17935
I had time to play around with it and build it, did not boot though, wanted to clean it up some but yesterday I broke my hand so there might not be updates for a while.

how did you get the unlock password for this device? im on their website but it doesn't list this device....

mattlowry said:
how did you get the unlock password for this device? im on their website but it doesn't list this device....
Click to expand...
Click to collapse
sorry it took so long to answer but I got the unlock password from huawei by emailing them, I haven't worked on this device solidly in a while.
you might be able to also flash recovery with adb also, if you wanna try it let me know because I unlocked my bootloader before using adb but when I try it works.

remembered to upload cwm advanced 5
also have cwm 6.0.4.7 and advanced 6 but I need to fix a nasty bug with it.

forgot to add if someone were to upload the recovery.img's and a partition layout for the g526 or G740 I can more than likely try to get cwm and cwm advanced running on them.

had to change the vitria recovery to mount by name instead of block number, changed font also.
added source

KainXSS said:
sorry it took so long to answer but I got the unlock password from huawei by emailing them, I haven't worked on this device solidly in a while.
you might be able to also flash recovery with adb also, if you wanna try it let me know because I unlocked my bootloader before using adb but when I try it works.
Click to expand...
Click to collapse
Yes, it takes a few email exchanges with [email protected], but I got my unlock password in couple of days from them.
Great job, OP, works like a charm.

Finally got my unlock from Huawei after a week, and just in time! I lost my old HTC G2 (its somewhere in the kitchen, i swear!) and needed a replacement phone fast.
Enter the Vitria. installed CWM and did a full backup, then installed titanium backup and started ripping out bloatware and live wallpapers and other crap.
I have to say, i REALLY hope development of Cyanogen continues for this device, its hard enough leaving CM7 to go to jelly bean. If there's anything i can assist with with a backed up/bootloader unlocked device, let me know. Or buy you enough beer to last a weekend so you can get this compiled

Flashify
I did something different, I flashed with flashify but I realize now I shouldn't have, it reboots but has a signature error before rebooting, I sure hope there will be cynogen mod or something because this phone has a data connection problem, once data goes off it won't come back on until restart and sometimes all bars without data goes off too and then have reboot too, good phone but needs work, glad to see someone out there doing something, thanks.
OK, I think I know how to fix, but I don't have the correct IMG to fix since I have already corrupted it by flashing with flashify.
Does anybody have the recovery.img and the boot.img from a working stock for this phone?
by having a good recovery.img, I can flash with flashify and get it back to working correctly, this is what I did to fix a similar problem from flashing CWM to my LG G2 and worked.
Update, downloaded stock ROM and the recovery and boot img where there so I flashed recovery.img with flashify and everything good.
Just wondering, anybody has a recovery of their Vitria that already has CWM working properly on it, I wonder if that recovery.img contains proper CWM to be flashed to another Vitria?

this is not for the h882l, it might work on that one but I don't know.
if you try to flash without having the bootloader unlocked, it won't work, you will get a crc signature failure error every boot even if you use adb or a flashing app, after unlocking you can use adb, not sure about flashify(never tried it).

CRC Signiture Error
KainXSS said:
this is not for the h882l, it might work on that one but I don't know.
if you try to flash without having the bootloader unlocked, it won't work, you will get a crc signature failure error every boot even if you use adb or a flashing app, after unlocking you can use adb, not sure about flashify(never tried it).
Click to expand...
Click to collapse
Yes CRC Signiture Error, but the bootloader is unlocked, I use T-Mobile with phone, but only problems I see with this phone is connecting to Data all the time, I end up having to turn data off then back on then it is usually fine sometimes it has problems still, I did pay a service to get the bootloader unlocked with a code so it is unlocked.
Would like to see a nice ROM built for this phone, I haven't the slightest clue to do so, Cyanogen mod would be fine.
Did try to install CWM but could not do so, is this the touch or regular version of CWM you have listed?
Keep up the good work, thanks.

Arctic Prodigy said:
Yes CRC Signiture Error, but the bootloader is unlocked, I use T-Mobile with phone, but only problems I see with this phone is connecting to Data all the time, I end up having to turn data off then back on then it is usually fine sometimes it has problems still, I did pay a service to get the bootloader unlocked with a code so it is unlocked.
Would like to see a nice ROM built for this phone, I haven't the slightest clue to do so, Cyanogen mod would be fine.
Did try to install CWM but could not do so, is this the touch or regular version of CWM you have listed?
Keep up the good work, thanks.
Click to expand...
Click to collapse
I also use tmobile on mine and I have data problems too but haven't tried to fix it yet, don't have the time but your bootloader is unlocked right, your not confusing sim unlock with bootloader unlock right, also your using fastboot to install right.
I am not working on cyanogenmod for the vitria though, it needs a device tree and the kernel needs to be updated for it too, on mine I just run with a custom rom based on stock and a custom kernel for overclocking and stuff, thats enough for me.

Maybe sim unlocked, but thought was bootloader unlocked, I paid to get phone unlocked, they sent a code and I am able to use t-mobile sim card on MetroPCS phone, as for bootloader, it is rooted and says unlocked if that is what you mean, I have SuperSu installed, I used Framaroot as suggested.
Yes I can get into fastboot mode.
Hmm, to verify if bootloader is truly unlocked, how would I go about getting to that to verify for certainty?

Bricked MAXX, Need Help

Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!

I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?

kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.

ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.

rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing

So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.

ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse

rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.

kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk

erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).

Nvidia Shield- How Can I Avoid The Kill Switch?

I have my old Nvidia shield tablet and i have WiFi off and powered off.
I've been reading you can stop the kill switch from i guess changing the boot loader or operating system?
I new to this stuff.
Could someone just give me some directions on how to go threw this process please.
I don't know if it's to late cause i have the most recent update? but like i said it's turned off and WiFi is off and i heard that the kill switch is sent over the internet to your device and you don't have to confirm it.
So i hope my system is safe until i can do what ever you guys advise me to do.
Thank you...

treat your old tablet before connecting the new one to internet
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)

If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.

I used my new tablet and the both were working for the day, both have no problems so far.
I've been reading that they are sending out kill switches in 4 segments, by using the last 2 digits of the serial numbers system.
So mine hasn't gone threw yet i don't think.
So i need to root it?
Then delete the OTA file?
Then flash a custom firmware?
Thanks guys...

Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.

Jarocks said:
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
Click to expand...
Click to collapse
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.

Snah001 said:
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Click to expand...
Click to collapse
I see lots of root programs, is there a best one?
Can you flash with TWRP?
And someone said all i have to do is...
"Full Process
1) Unlock Bootloader.
2) Flash TWRP Recovery.
3) Get the no more OTA.zip from XDA and flash it via TWRP
4) Check if the update option is removed from Settings, if not flash it again.
Done! "
Is that ok also?
Thank you...

You need to root to flash twrp?

EowynCarter said:
You need to root to flash twrp?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader to fastboot flash anything.

amartolos said:
No, but you do need an unlocked bootloader to fastboot flash anything.
Click to expand...
Click to collapse
Yeah, that the conclusion i reached.
Flash done, now runing bliss pop. First start got me loads of errors. I went until i realized i had forgotten to wipe. It's been a while since i last played with custom roms.

oliwek said:
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Click to expand...
Click to collapse
Well, that's disappointing

oleg77 said:
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
Click to expand...
Click to collapse
Ok i followed the http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
I got to "On the tablet, select "recovery reboot"
But i didn't see it so i selected reboot, i rebooted and was on stock i think?
1) I can see that a few more steps and i'm rooted.
But i'm nervous to try this again from that point.
Should i just start at unlocking the boot loader?
2) Is rooting the device permanently unlocking the boot loader?
3) can i just no OTA from unlocking the boot loader part?

Ok i got to side loader and in the command it says error can't find device and there's an android guy on his back with a red statement mark.
So I'm in developer USB.
I have unlocked the boot loader
I'm flashing the recovery
And i get to restart in recovery.
Then i get the menus to side load the supersu.zip
I renamed it with out caps, i even made a folder in C:\Program Files\Minimal ADB and Fastboot.
Cause it installed at C:\Program Files (x86)\Minimal ADB and Fastboot.
just to avoid the (x86)
when i try and leave the menu to reset it asked me to root, but i had the error so don't want to brick it if rooting with an error on side loading supersu.zip
What do i do?
Thank you...

says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.

l337g0g0 said:
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
Click to expand...
Click to collapse
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk

frenziedfemale said:
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't have an SD card ATM. LOL
Why is the command with ADB not working?

l337g0g0 said:
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
Click to expand...
Click to collapse
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.

frenziedfemale said:
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
Click to expand...
Click to collapse
Ok that installed it.
WOW thank for that.
I guess I'm rooted, how do i test it and what does being rooted do for me?
Thank you....

Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk

frenziedfemale said:
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i just flashed nomoreOTA.zip.
It said the file was deleted and was a success.
I guess i can use the internet now?
I'm so nervous to turn the internet on and have the thing reset...
Did i need to run supersu to keep it rooted or always rooted until i use supersu to full unroot.
Thank you...

[Guide][H918] Returning to Stock on 10P/10Q/10R

Hello everyone!
A little bit of a back story here - I was on NATF's rom when I proceeded to take the flashable 10Q/10R updates posted by @dimm0k. These newer updates, starting with 10P, are Anti-Rollback. I spent some time poking around trying to find answers on how to return to stock and how I could do this in a way that seemed comfortable to me.
I have found that ARB 0 is interchangeable with anything ARB 0. Anything that is ARB1, is interchangeable with ARB1, and so forth if LG decides to up the values to '2' or maybe even '3'.
If you are ever curious and want to know on later firmwares if you have ARB and what version it is, use this dialer code:
*#*#244773825625#*#*
###
I AM IN NO WAY RESPONSIBLE FOR YOUR DEVICE. THIS IS A AT YOUR OWN RISK TUTORIAL.
###
Moving forward here - I was able to flash 10P KDZ to remove TWRP and revoke root.
Requirements:
H918 TMO V20
10P/10Q/10R partial update software by dimm0k
1. Download LGUP_Store_Frame_Ver_1_14_3.msi and search for LGUP_common.dll ( I actually used the G5 dll)
1a. Download 10P KDZ from here: https://forum.xda-developers.com/v20/how-to/t-mobile-v20-h918-10p-kdz-file-t3653797 and set this off to the side.
2a. Install both LGUP and common.dll
3. Search, download and install LGMobileDriver.
4. Completely Power off the v20 (or to remove and put the battery back)
5. Plug the USB end of sync cable to your PC
6. Press and hold "Volume Up"
7. Plug the USB in to the v20. The phone will enter download mode (or Firmware Update). Now you can release the "Volume Up".
8. Run LGUP. The program will recognize the v20.
9. At the file path, click "..." and choose the .kdz file 10P
10.Choose "UPGRADE"
11.Click "Start" and wait until the process is complete.
The phone will go thru its phases.
After about 10-15 minutes, the phone will reboot. You will land at your lockscreen. This does not wipe your data. Once you are at the lockscreen, run a factory reset within the settings app.
Let the phone cycle thru the reset and bam! You are back to stock!
To confirm my work, I adb reboot recovery to verify twrp is no longer there. Settings shows 10P software.
This guide is to return a user back to stock. I am getting ready to sell my device - this was the steps I took to return the software to stock. Don't forget to lock bootloader after.

Saving this one just in case - If you need clarification on something, please ask.I did my best to explain my process.

HiddenKnight said:
Hello everyone!
A little bit of a back story here - I was on NATF's rom when I proceeded to take the flashable 10Q/10R updates posted by @dimm0k. These newer updates, starting with 10P, are Anti-Rollback. I spent some time poking around trying to find answers on how to return to stock and how I could do this in a way that seemed comfortable to me.
I have found that ARB 0 is interchangeable with anything ARB 0. Anything that is ARB1, is interchangeable with ARB1, and so forth if LG decides to up the values to '2' or maybe even '3'.
If you are ever curious and want to know on later firmwares if you have ARB and what version it is, use this dialer code:
*#*#244773825625#*#*
###
I AM IN NO WAY RESPONSIBLE FOR YOUR DEVICE. THIS IS A AT YOUR OWN RISK TUTORIAL.
###
Moving forward here - I was able to flash 10P KDZ to remove TWRP and revoke root.
Requirements:
H918 TMO V20
10P/10Q/10R partial update software by dimm0k
1. Download LGUP_Store_Frame_Ver_1_14_3.msi and search for LGUP_common.dll ( I actually used the G5 dll)
1a. Download 10P KDZ from here: https://forum.xda-developers.com/v20/how-to/t-mobile-v20-h918-10p-kdz-file-t3653797 and set this off to the side.
2a. Install both LGUP and common.dll
3. Search, download and install LGMobileDriver.
4. Completely Power off the v20 (or to remove and put the battery back)
5. Plug the USB end of sync cable to your PC
6. Press and hold "Volume Up"
7. Plug the USB in to the v20. The phone will enter download mode (or Firmware Update). Now you can release the "Volume Up".
8. Run LGUP. The program will recognize the v20.
9. At the file path, click "..." and choose the .kdz file 10P
10.Choose "UPGRADE"
11.Click "Start" and wait until the process is complete.
The phone will go thru its phases.
After about 10-15 minutes, the phone will reboot. You will land at your lockscreen. This does not wipe your data. Once you are at the lockscreen, run a factory reset within the settings app.
Let the phone cycle thru the reset and bam! You are back to stock!
To confirm my work, I adb reboot recovery to verify twrp is no longer there. Settings shows 10P software.
This guide is to return a user back to stock. I am getting ready to sell my device - this was the steps I took to return the software to stock. Don't forget to lock bootloader after.
Click to expand...
Click to collapse
if I'm not mistaken, simply re-locking your bootloader would wipe your device and on the first boot after would restore your recovery from backup, wrong out TWRP. that said, sorry to see a fellow LGV20 user go...

dimm0k said:
if I'm not mistaken, simply re-locking your bootloader would wipe your device and on the first boot after would restore your recovery from backup, wrong out TWRP. that said, sorry to see a fellow LGV20 user go...
Click to expand...
Click to collapse
I didn't want to leave anything behind. I guess this method above is the long way and did work.
Sorry to leave. But good luck guys!

Wish I seen this before I did the OTA update for 10q ?

Couldn't you try to sell your phone with the bootloader already unlocked?
I would have paid more for one pre-unlocked.

How do you lock the bootlooder. I gotta get a replacement because my phone started to overheat regularly up to 180 degrees Fahrenheit so much so that I get severe seven retention and my DAC stopped functioning.

mookiexl said:
How do you lock the bootlooder. I gotta get a replacement because my phone started to overheat regularly up to 180 degrees Fahrenheit so much so that I get severe seven retention and my DAC stopped functioning.
Click to expand...
Click to collapse
Go to settings developer options lock bootloader done
---------- Post added at 01:01 AM ---------- Previous post was at 12:58 AM ----------
stillblaze01 said:
Go to settings developer options lock bootloader done
Click to expand...
Click to collapse
That is how to lock the bootloader but will that return to stock?????

Actually that isn't the way to lock the bootloader. You fastboot the command bootloader lock and then find KDZ stock firmware and flash.

mookiexl said:
Actually that isn't the way to lock the bootloader. You fastboot the command bootloader lock and then find KDZ stock firmware and flash.
Click to expand...
Click to collapse
You are correct. But I flashed kdz and then. Locked bootloader using dab. I did it back wards but it worked

I cant enter download mode because i changed LAF (Download Mode) for TWRP to root the device, i cant use your method and dont know how you did it if your version is the same as mine V10P

ernestico911 said:
I cant enter download mode because i changed LAF (Download Mode) for TWRP to root the device, i cant use your method and dont know how you did it if your version is the same as mine V10P
Click to expand...
Click to collapse
did u find any solution for it

Flash the zip at the end of the first post in the lafsploit thread....
-- Brian

Miggs22 said:
did u find any solution for it
Click to expand...
Click to collapse
yes just flashed the same version via TWRP

Hello, I just want to clarify since there are no other places to ask, is firmwares 10p 10q 10r 10s 10t and 10u are ARB1? or is it just 10p that's ARB0?

10a to 10o == ARB 0
10p to 10u == ARB 1
-- Brian

20G KDZ if anyone needs to return to complete stock Oreo
https://megaupload.nz/o6sfkalbb2/H91820g_00_1010_kdz
https://megaupload.nz/K0Q9j6labe/LGUP_c_dll

Unable to install OTA updates since unlocking bootloader

Hello everyone!
Since I've unlocked and rooted my Pixel 2 it keeps failing the OTA update. I get the notification and the update is downloaded but when it's being installed, there is an undefined error. For all updates I had to sideload the OTA file via ADB. Honestly, I don't really know what could have caused this issue, as the first OTA update when I got the phone with all stock settings and roms it worked fine. Currently I can only instal the OTA.zip updates via ADB.
Things I did so far which could have caused the issue:
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Things I tried to resolve the issue:
Lock the bootloader again
Flash full stock rom with fastboot and official google script (failed "couldn't write bootloader.img" altough I had it unlocked)
Factory reset
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
Does anyone else have similar experiences?

ekalz said:
Things I did so far which could have caused the issue:[/B]
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Click to expand...
Click to collapse
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
ekalz said:
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
?
Click to expand...
Click to collapse
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.

SweetSofie said:
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.
Click to expand...
Click to collapse
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.

Can you root without patching or unlocking the bootloader so you don't fail the integrity check?

robocuff said:
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.
Click to expand...
Click to collapse
Thanks for the clarification! I would love to learn more about that stuff, I'm just not sure where to start learning.

I have the same problem with my pixel 2. I have tried full factory reset by flashing stock image. I have tried the recovery script some user posted in the p2 forum.
I contacted Google support about it and now i am waiting for 2nd line to contact me.
I will post here if/when i get a solution.

With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete

socal87 said:
With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete
Click to expand...
Click to collapse
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?

smorgar said:
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?
Click to expand...
Click to collapse
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread

socal87 said:
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread
Click to expand...
Click to collapse
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)

smorgar said:
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)
Click to expand...
Click to collapse
Did you try to sideload via ADB?

socal87 said:
Did you try to sideload via ADB?
Click to expand...
Click to collapse
No I am waiting to get it resolved by Google so that I can install OTA in the future.

smorgar said:
No I am waiting to get it resolved by Google so that I can install OTA in the future.
Click to expand...
Click to collapse
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.

socal87 said:
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.
Click to expand...
Click to collapse
I was trying to fix the problem permanently so that i dont have to sideload if i dont want to.
**** went to ****... I did factory reset as the Google support person told me. Tried installing OTA again but it did not work. So they left me waiting for second line support to contact me but its now been the whole weekend and no support.
After support told me to do reset the last time the phone began to freeze and crash apps randomly. So i tried to install full factory image via fastboot but that was the last time the phone booted up. Now its completely dead.
When i try to boot the phone nothing happens. If i hold power button for 20-30 sec i sometimes get a short vibration and a line of pixels flashing by on the screen then nothing more happens. Now im waiting for Google support for real. Pray for my dead pixel2
If anyone have some tips for me im willing to try. The phone does not seem to boot and the PC does not recognize it at all.

You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.

davidisflash said:
You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.
Click to expand...
Click to collapse
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant

smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
And so how did everything work out for you? Were they able to get you resolved, or are they just RMA'ing your phone?

No resolution. I sent it back to uk for replacement via seller.

smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716

davidisflash said:
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716
Click to expand...
Click to collapse
I have done all the basic and advanced stuff. I had it dead for about a week to play around with. Used to work in a mobile repair shop so this isnt something new for me.