yashsingh1/xdaforums huggingface dataset:
[Google Pixel Questions & Answers] dwegiel:
OTA update failed, the phone spontaneously shut off and rebooted to the beautiful "Your device is corrupt. It can't be trusted and may not work properly." screen. After being greeted by said screen, the phone reboots and goes to the same screen. Recovery doesn't boot. Fastboot doesn't allow me to flash any image (even signed from google). If I boot into fastboot and do a "fastboot continue", the phone boots to a blank screen with adb running in recovery mode, but with the port closed (can't flash a recovery OTA).

Someone please help. I've tried all solutions I could think of. I don't know what is left.
[Google Pixel Questions & Answers] mruno:
Sounds like a trip to a Verizon store is in your future :/
[Google Pixel Questions & Answers] dwegiel:
Any chance Google themselves would be able to take care of this?
[Google Pixel Questions & Answers] bobby janow:
I wonder if the OP unlocked the bootloader and rooted. If so, they might not take too kindly to replacing the device. If it's stock then head there today and get a new one. How about a factory reset attempt?
[Google Pixel Questions & Answers] dwegiel:
Impossible to factory reset. Recovery does not boot. Bootloader is locked, as fastboot flashing unlock returns as invalid.
[Google Pixel Questions & Answers] PiousInquisitor:
Recovery doesn't boot? Do you get the dead Android or something else?
[Google Pixel Questions & Answers] dwegiel:
Same "Your device is corrupt. It can't be trusted and may not work properly.", and recovery fails to boot. Nothing on the display, phone either shuts off or boots to charging mode.
[Google Pixel Questions & Answers] PiousInquisitor:
What was your situation before this started? Unlocked? Rooted?

Edit: I see you were updating.
[Google Pixel Questions & Answers] dwegiel:
None of the above, stock Android OS.
[Google Pixel Questions & Answers] bobby janow:
Recovery is sometimes not easy to get in to. I had to do it 3 times in a row before I got it to take. So I'm sure you know it's hold the power button and then hit vol up. But if you don't get it just right it will reboot or turn off. Does adb work?
[Google Pixel Questions & Answers] dwegiel:
Ok so this is getting weirder by the second. Just saw a teamwin recovery screen pop up...

I purchased this device second hand and used it with no problems until the first update, but it definitely looks somewhat tampered with. Any advice?

This occurs when I perform a fastboot continue. At that point I have adb up in recovery mode. But since I see nothing on screen, I can do nothing. Can't sideload because it's not at the sideload screen. Suggestions?

EDIT: Okay, so I have a VERY basic adb shell up through TWRP. I can't access TWRP directly because it "hasn't started". Ideas?

EDIT2: adb shell has basic busybox commands and is running root. I have downloaded a new TWRP image. What is the partition where the pixel has its recovery? Under /dev/block/mmc....?
[Google Pixel Questions & Answers] nednednerb:
Can you get into bootloader?

Which slot is active?

Can you

Fastboot set_active _b

Or

Fastboot set_active _a

And try getting to recovery or booting?
[Google Pixel Questions & Answers] dwegiel:
b slot is active. Will reboot now and (attempt to) switch to a. Found the appropriate fastboot by googling, please hold...

Setting current slot to 'a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.098s

What a surprise

Also to clear up, the only way for me to get thrown into this psuedo adb shell in TWRP is to "fastboot continue" at the fastboot screen. Recovery fails to boot. System fails to boot. Fastboot is useless because oem unlock is not possible.
[Google Pixel Questions & Answers] dwegiel:
Partition table dumped. Any ideas for where the recovery resides?

Side note: I have never ever seen this many partitions on any device. Ever.

# cat /proc/partitions
major minor #blocks name

8 16 4096 sdb
8 17 4052 sdb1
8 32 4096 sdc
8 33 4052 sdc1
8 48 49152 sdd
8 49 1024 sdd1
8 50 8 sdd2
8 51 32768 sdd3
8 52 128 sdd4
8 53 4 sdd5
8 54 4 sdd6
8 55 1024 sdd7
8 56 4 sdd8
8 57 2048 sdd9
8 58 2048 sdd10
8 59 1024 sdd11
8 60 4 sdd12
8 61 9020 sdd13
8 0 124866560 sda
8 1 512 sda1
8 2 512 sda2
8 3 512 sda3
8 4 512 sda4
8 5 2048 sda5
8 6 2048 sda6
8 7 512 sda7
8 8 512 sda8
8 9 512 sda9
8 10 512 sda10
8 11 512 sda11
8 12 512 sda12
8 13 256 sda13
8 14 256 sda14
8 15 256 sda15
259 0 256 sda16
259 1 4096 sda17
259 2 4096 sda18
259 3 32768 sda19
259 4 32768 sda20
259 5 32768 sda21
259 6 32768 sda22
259 7 128 sda23
259 8 128 sda24
259 9 71680 sda25
259 10 71680 sda26
259 11 256 sda27
259 12 256 sda28
259 13 256 sda29
259 14 256 sda30
259 15 307200 sda31
259 16 307200 sda32
259 17 2097152 sda33
259 18 2097152 sda34
259 19 119758848 sda35
259 20 4820 sda36
8 64 36864 sde
8 65 512 sde1
8 66 6144 sde2
8 67 4096 sde3
8 68 2048 sde4
8 69 16384 sde5
8 70 7636 sde6
8 80 8192 sdf
8 81 16 sdf1
8 82 256 sdf2
8 83 2048 sdf3
8 84 4 sdf4
8 85 5824 sdf5
[Google Pixel Questions & Answers] dwegiel:
SUCCESS. Stock recovery boots.

Used the gimped TWRP adb shell to push aboot.img and boot.img from a stock rom. And dded them to the respective partitions, on the _b boot slots.
[Google Pixel Questions & Answers] BakedTator:
May I suggest unlocking the bootloader now that you have things going better for you?

Did you ever get the system to boot up?
[Google Pixel Questions & Answers] dwegiel:
Can't FRP is locked. Guess the FRP partition got screwed.
[Google Pixel Questions & Answers] azn6929:
I have the same problem. I'm trying to follow your steps, but I'm lost :confused:

Currently, phone is on Boot-slot: b

fastboot set_active_a
usage: fastboot [ <option> ] <command>

doesn't do anything

sorry I'm noob. Please help.
[Google Pixel Questions & Answers] milan187:
How do you have the same problem. You have a locked bootloader with TWRP?

---------- Post added at 04:03 AM ---------- Previous post was at 04:01 AM ----------

Can you push full OTA image in stock recovery?
[Google Pixel Questions & Answers] azn6929:
My Verizon Pixel (unlocked BL, rooted) was working fine for about a month, then it went crazy

Incoming calls freeze up the phone(cannot talk, hang up...)

Restart randomly, then stuck on Google logo after reboots (4 out of 5 times)

I tried to wipe/factory reset, clear cache and everything. No luck.

I couldn't find any instruction to reLock BL (after being dePixel8'ed).

I just lock it, like the non-dePixel8 version. Yes, I know, stupid right ? :crying:
[Google Pixel Questions & Answers] dwegiel:
While in fastboot mode, run fastboot continue. After the phone fails to boot, hold volume down and power and it will enter the a slot. You can not change slots officially without a bootloader unlock.
[One (M8) Q&A, Help & Troubleshooting] Dewzone:
Searched the cm threads and google much. still no solution for the system image unconditionally problem?

how to fix ? tried many times and still same.

Is it the partition format problem or?

tried cm 13 and RR rom but same patching problem.

Twrp : 3.0.2.0

s-on.
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
keep it here as suggested in the other thread

all cm based rom will give you the patching system unconditionally line while flashing

IT'S NORMAL nothing to worry about

about the firmware i ask you because some roms manipulate the partitions which isn't your case

all the rom you posted above are fine no need to flash firmware when you decide to flash another rom

anyway if you need the firmware you can search in this thread in post#5 about your device firmware ( search by cid&mid )

http://xdaforums.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
[One (M8) Q&A, Help & Troubleshooting] Arutemu:
Sorry, can you help me? I have similar problem, I can't install any rom with system.new.dat.

This line is of updater script fails to work, and I don't know why, since everything seems ok to me.

block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")

It looks like this:

patching image system undonditonally

E: unknown command [log]

E: unknown command [log]

detected file system ext4 ...

As a result, my system dir is empty and so there is no system.
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
what makes you sure it's this line error ?

I have those errors on every AOSP N roms and it's booting normal
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
What hboot number, and OS number on the bootloader screen? Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

What version TWRP?

What ROMs specifically?

I have a feeling its due to wrong version TWRP and/or outdated firmware. Otherwise, I see no reason for multiple ROMs failing to install (assuming you are flashing the correct ROMs for your version M8).

As ahmed touched upon, it has nothing to doo with the message "patching unconditionally". That is just the message that happens to occur, before the ROM install fails.
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
I believe he is asking what's wrong with the updater-script and

I guess he is not talking about M8 but his updater-script problem on Desire Eye.
[One (M8) Q&A, Help & Troubleshooting] Arutemu:
I'm sorry for late answer. Thank you all for your replies, the problem is solved :)

Yeah, I was trying to modify updater-script to work on my Desire Eye. And yeah, it worked, but only after factory reset.

Now I need to compile CM kernel to boot it properly ?

Hboot version was the same as on One M8, and twrp was 3.0.2-0, FYI.

Thank you all again!
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Trying to flash to a completely different device would have been a important fact to have mentioned. Plus, due to this, your issue was really in no way similar or related to the that of the OP.
[One (M8) Q&A, Help & Troubleshooting] Arutemu:
Yeah, you are right, sorry for that. At that moment I just was confused by problems with installing CM in common, so I was looking for a solution for any device.
[Samsung Galaxy S7 Edge Accessories] x017in:
Pics :

Review :

This is by far my favourite case from Ringke.

I got the frost gray color option from amazon for 9$. It's a semi transparent case. This allows the back logo or skin to be seen through.

Look and feel :

The case has the cutouts at the right places. The edges are smoothly finished. The back n sides have a soft touch finish, giving a premium feel. The cutouts for the power and volumes keys are precise. I don't have a gear VR so haven't tried with it. The wireless charger works as expected.

I have a skinomi screen protector which extends to the edges. Most cases do not work well this protector and would eventually cause the protector to peel at the edges. With this case, there aren't any such issues.

Being a slim case, the protection offered is the bare minimum. There is a elevated area on the rear to protect the camera. On the front, the top and bottom are slightly raised to protect the screen in case the phone is placed face down.

The other good part is that all 4 sides of the frame are covered, protecting the metal from dents.

This case, this may not take heavy falls, but offers the minimal protection I was looking for.

Overall I would rate this 9/10 for look and feel, and 5/10 for protection and 10/10 for compatibility with screen protector and accessories.
[Samsung Galaxy S7 Edge Accessories] fortesquieu:
I have the black color one, and it meshes nicely with a black S7E. It seems like there's no case at all.
[Samsung Galaxy S7 Edge Accessories] JoaoVr:
Does it work nice with regular protector films?
[Samsung Galaxy S7 Edge Accessories] binniebin:
Best slim case

Wysłane z iPad za pomocą Tapatalk
[Samsung Galaxy S7 Edge Accessories] x017in:
Works with every type of protector
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aih1977:
Please vote on if he should keep the voice command or not to keep it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] silent_killa:
Where is the voting poll?

Im a MS Voice Command user so i say leave it out. But then not everyone will want to fork the cash for it.........
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
LOL this is pointless.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aih1977:
No it is not because dutty wanted to know if he should leave it or remove it.

so i want to see if alot of people what keep it or not.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] duttythroy:
HI MATE I finish the roms and I left it in, its not a big deal most eople dont use voice command:)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] e-dub:
damn, really. i couldn't imagine my device without it!

eric b
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pkley:
I'll say...just got a txt msg from my wife today and it read it (thankfully) to my headset - "I feel like poo, head hurts eyes swollen" I was laughing out loud in my office when I heard the mechanical voice say "I feel like poo":D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] leoiden:
if you mean microsoft voice command then you have my vote to have it in the rom but no cyberon hated !
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aih1977:
MS Voice Command is what i use i don't like training the commands manual every time i flash my rom and i think it is a waste of time.

OH YEAH CYBERON SUCK!!!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackleung:
Cyberon voicedial suck but Cyberon Voice Command is very good
[LG G5 Guides, News, & Discussion] xjqlfq:
1，unlocked bootload，https://www.gizdev.com/lg-g5-h850-twrp-3-0-rooting-guide/

2，install rec for h850 ，http://thunderztech.com/root-lg-g5-on-android-7-0-nougat-with-twrp-recovery/

3，into rec and flash LG-H85010E-Flashable.Bootloader.zip from autoprime,http://xdaforums.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273

4,lg up flash 6.0.1 kdz,http://xdaforums.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273

5,wipe you device by keep volume- always and power,when look lg logo,press power again and keep it ,then press yes,yes

you have downgrade to 6.0.1
[LG G5 Guides, News, & Discussion] autoprime:
good info.

I can make it even easier... instead of downloading my 10E COMPLETE ZIP

Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
[LG G5 Guides, News, & Discussion] xjqlfq:
thanks，get it
[LG G5 Guides, News, & Discussion] fuxi222:
I had several problems with this procedure (coming from V20a):

1. After flashing 10C BOOTLOADER ZIP via TWRP, LGUP was not able to detect my device type anymore, but this worked with previous bootloader. Why?

2. Flashing the 10C COMPLETE ZIP did result in a loss of TWRP (although recovery.img is not part if complete ZIP). Why?

3. Flashing the 10E COMPLETE ZIP caused FCs and a bootloop :( Reset in system recovery did help to get the device up again.

After that LGUP did find again my H850 and upgrade option works now with M KDZs (which did not work under Nougat). But the refurbish option is still not working and says "not supported".
[LG G5 Guides, News, & Discussion] autoprime:
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.

2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.

3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
[LG G5 Guides, News, & Discussion] fuxi222:
At first: Big thanks for your quick response!!!

to 1.: The reason for 10C instead of 10E is simple: you do not have a KDZ file for 10E on your codefire drive (only a ZIP), but for 10C the KDZ was available. And the links to LG server were not working yesterday for me.

I read Uppercut the first time now and will give it a try today in the evening (German time). :fingers-crossed:

to 2.: Understood. Thank you! :good:

to 3.: Then how can I get rid of the 3 error messages on start-up related to NT-code ("Can't find matched cust for NT-code" + "OP name for Buyer-code...")? I understood, that refurbish will flash new cust partition and this will solve the problem. I see cust.img also on your drive, but it is not inluded in the COMPLETE ZIPs. Would it help to flash this?

Or can LG Bridge help in this case? It does refuse to flash my phone, maybe because of the bootloader unlock?!

I read so many threads yesterday, but nothing solved this issue... :crying::crying:
[LG G5 Guides, News, & Discussion] autoprime:
cust should be getting flashed regardless of selecting refurbish or not as far as I know.. but perhaps I'm wrong. :confused:

if you have root/twrp just zero out the cust partition or simply delete the files inside the cust folder using a file explorer app... and the error msg should go away on next reboot.

this is in the FAQ/Q&A section in the OP of all my stock threads for H850.

if you're on M and must flash a KDZ with refurb option... just use the old LGUP methods. but if you're sticking with TWRP there's not really any need to flash any KDZ.. you can flash whatever in TWRP instead.
[LG G5 Guides, News, & Discussion] fuxi222:
"and the error msg should go away on next reboot." I get 3 error messages related to this. Will I get rid of all of them?

"old LGUP methods" means tool version 1.11 instead of 1.14? So use version 1.11 for MM and 1.14 for N?!

Unfortunately, refurbish does not work even under MM for me regardless if I use version 1.11 or 1.14. :(

BTW: The old version 1.11 asks my each time I trigger the refurbish process to "Input new NT code" (the new version does not behave like this). Is my problem maybe caused by this or can this be used to input a working string there?
[LG G5 Guides, News, & Discussion] autoprime:
i dont have an H850 so idk.. but any time ive had someone zero cust theyve said errors have gone away. so if they dont for you.. you must be special. try it and find out... then report back. if it doesnt work... Â¯\_(ãƒ„)_/Â¯

old lgup methods = 1.11 + dll msi installer, yes. but i see no reason to use 1.11 simply for refurbish option. most people should be able to use LGUP 1.14 + UPPERCUT for most situations on G4/G5/V20.

i dont know abotu the NT code stuff with LGUP.. again.. I dont have a H850. but if you have TWRP then there's really no need to be messing with LGUP at all unless you want to be 100% stock/unrooted with no TWRP. just zero cust or try flashing the cust.img that's in the folder.

I cant help any more on this NTCode subject without a device that uses it. good luck.
[LG G5 Guides, News, & Discussion] fuxi222:
Only if someone is on the same point: For me, it is only working to flash the COMPLETE ZIP! When I flash bootloader only, LGUP does not detect the model type of my device anymore (detected type is "Unknown"). I have tried it now for 2 times with similar results...

BTW: I used this method to get rid of the annoying NT code issue: http://xdaforums.com/showpost.php?p=66957161&postcount=4
[LG G5 Guides, News, & Discussion] TH4N1X:
[MENTION=2684188]autoprime[/MENTION] Can't we just flash 10E with the refubrish option? Somehow I'm unable to get into recovery with the button combination after downgrading and updating again, even though I'm doing it properly and I was able to do it before.

EDIT: So refubrish stopped working now too. Dang. I installed the recovery through Dirty Cow, flashed the bootstack and went back to 10E, but I still don't have a recovery. ;_;

Ok, I've tried everything and button combination for recovery still doesn't work, so think if you really wanna risk being unable to easily factory reset your phone.
[LG G5 Guides, News, & Discussion] chrcol:
Well I am trying to flash stock EE rom, which I have the KDZ for.

I am flashing via upgrade, and all that happens is when the phone boots it is unstable, phone app crashing etc.

All settings still intact, no myee app, app from open EU rom still exists, very very strange.

Is it possible to convert a KDZ to a twrp flashable zip as twrp seems far easier.

I suspect if I used refurbish it would fix this issue as upgrade seems to not be clearing everything.
[LG G5 Guides, News, & Discussion] Pphish20:
Did u try what I suggested in other thread? Wipe internal storage before first boot, reboot recovery afterwards before booting system; are u clean flashing? Are you trying to restore any data at all besides things like messages and call logs?

Going from an openEU.kdz to a branded .Kdz would definitely require a Twrp data format and a recovery reboot, perhaps do all this b4 using LGUP with kdz.

Yes it is possible to make a .zip from a kdz, but it's not a simple process and there is no EE branded 20a.zip

Autoprime already stated that refurbish option can be used if you use LGUP v1.11 instead of latest 1.14 but don't forget the .DLL file. Also all refurbish does is wipe data and internal storage; which can be done via TWRP using the method I mentioned above. Try what I mentioned and then reflash kdz;forget about any data besides text messages just take the extra 30min to resetup device from scratch.

What version of LGUP are you using? Can u give more info be more descriptive about what's happening?
[LG G5 Guides, News, & Discussion] chrcol:
it is resolved now but I was just trying to get it in a good state to return the phone to EE.

Doing a factory reset in twrp didnt work, but what did work is I did a reset from in the rom, and after the reboot it was properly reset.

What was odd is when I wiped system and data manually in twrp that also didnt work.

I think I forgot to check if I completely wiped the internal storage, photos etc. As I was rushing to get the phone to be sent back. But the description for the reset option in android says it does wipe all personal data so hopefully that did it.
[LG G5 Guides, News, & Discussion] fifa_05:
How can I downgrade LS992?
[LG G5 Guides, News, & Discussion] aardc:
İs this possible for lg g5 H860?
[LG G5 Guides, News, & Discussion] friz:
For H850 just download H85010i_00_OPEN_EU_OP_0923.kdz flash it with LGUP 1.4(uppercut) after it's finished reset the phone then just flash android 6 firmware that you like.
[LG G5 Guides, News, & Discussion] sad_but_cool1:
i have h850 ,

current firmware is v20a updated via fota

no root , no bootloader unlock ,,, compleatlly stock phone

i want to downgreade to any 6.0.1 firmware without losing data (if possible)

if not, what to check and what steps to do without tripping on cust ot drk or modem or .... issues ?

pleas advice me ....
[LG G5 Guides, News, & Discussion] Binh Vo:
LGUP corrupts whenever i hit Start, but it works just fine with N kdz (mine is 20a). I have tried to flash bootloader but still ended up with the same outcome.