yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Q&A, Help & Troubleshooting] amartolos:
Your message seems to be unclear about one very important thing:

1. Are you able to successfully access the bootloader? I don't mean your custom recovery. I mean the black screen with very small font words with your serial and shows whether your bootloader is Locked or Unlocked.

From where I'm sitting, it looks like you flashed v1.2.1 without using "flash -w", as well as forgetting to flash ALL the stock img files. Next, it looks like you're expecting a direct boot into the bootloader, which is not possible. You need to hold down the Vol_down button and then hold the Power button until the screen comes on, THEN you need to let go of the Power BUT KEEP HOLDING the Vol_down. If done correctly, you should be at the bootloader.

From the bootloader, you will not be able to run adb commands. Instead, the bootloader takes "fastboot" commands. All this is assuming you've installed the latest nVidia Shield Family drivers from the nvidia gameworks download site.
[Shield Tablet Q&A, Help & Troubleshooting] ThunderArts:
Thanks for your answering. I flashed all .imgs, the blob file and the .dtb file . Everything but not the userdata.img. I can't access the bootloader with holding down the vol down + power button. I only can access the apx mode with power + vol up.
[Shield Tablet Q&A, Help & Troubleshooting] amartolos:
I notice in your sig that you do in fact seem to have a fully working new replacement tablet. That got me thinking along the following:

1. new tablet is fully functional, old one is not

2. both tablets have the same hardware spec

3. pull firmware from new one, and somehow get it onto the old one

4. hopefully old tablet should work!

The biggest problem is step 3... I only know of nvflash that might be able to help here, but I've never used it myself so I'm completely useless here. Maybe someone more knowledgeable could help out here, but otherwise it seems like you might be out of options.

If you do want to take a stab at nvflash yourself, THIS PAGE has a nice writeup of what some commands do, BUT BEWARE! It's not for our device, so don't just copy-paste commands! As long as you're not writing things to the new tablet, it couldn't hurt to try stuff, right?
[Shield Tablet Q&A, Help & Troubleshooting] ThunderArts:
It wish someone could help me with NvFlash because I have no knowledge with it.

So it's possible to make a copy of the system of my working tablet and flash it on my old tablet with NvFlash?

I hope someone helpful with NvFlash experience could help me out.

Btw I need to have an un-blob'd stock rom version to get it back alive? Afaik is there no public version.
[Shield Tablet Q&A, Help & Troubleshooting] sbdags:
NVflash is only useful if you have backed up using it BEFORE you brick it. :(
[Shield Tablet Q&A, Help & Troubleshooting] ThunderArts:
I have a replacement tablet. I could make a backup from it and use it with my bricked tablet. Do you know how this could work? (As I said I don't have experience with Nvflash yet.)
[Shield Tablet Q&A, Help & Troubleshooting] ThunderArts:
-deleted-
[Shield Tablet Q&A, Help & Troubleshooting] sbdags:
No the blobs are specific to the device.
[Shield Tablet Q&A, Help & Troubleshooting] ThunderArts:
Okay. So it seems that there is no way to rescue it. Btw is there no accessible bootloader in OTA 1.2.1 because I flashed the boot.img without any error and I don't understand why I can't access it.
[Shield Tablet Q&A, Help & Troubleshooting] Bogdacutu:
can you actually back up anything for nvflash? afaik there's nothing that works on the tegra k1 yet
[Shield Tablet Q&A, Help & Troubleshooting] sbdags:
Indeed - I was just talking about nvflash use in general. I haven't seen it used since tegra 3.
[X Play General] convolution:
or every other night? What's better for the battery? I hear different smart batteries have different technologies. When I was using my custom ROM and kernel on my Nexus 4, I can set it so the battery charges to 95% and stay there. I am not sure how original Android works. Does it charge to 99% and stop? Does it charge to 100% and stop, and then top it off again after the phone drains to 95%? Can I set how the charging behaves on stock android?

thankkssss =D
[X Play General] Brewtality:
As far as I know it wont matter if you charge it to 95% or 99%, it's still a charging cycle.

The million dollar question is: How many cycles does the batt endures?

That depends on charging current, voltage, depth of discharge and many other things and can vary from 300 to 7000 cycles.

So, long answer to your questiond: Just charge it to fit your needs. Don't make strict rules about when and how to charge your phone, battery life depends on so many variables it becomes unpredictable.
[X Play General] habskilla:
I leave the house with a fully charged battery because you just never know how much you'll use your phone that day.
[Upgrading, Modifying and Unlocking] pala17:
Hi!I got T-mobile mda compact but it has german language wm2003SE ROM,but i dont speak even a word in german,and i would change it to english but i dont know how and where can i get the program.Ca somebody help me?
[Upgrading, Modifying and Unlocking] djfwat:
MDA Compact

I've just debranded my mda compact III,

Have a look here to point you in the right direction.....

Look here to see your device:-

http://xdaforums.com/index.php

You need to unlock the Country ID before flashing, if you don't do this first you could brick your phone. cid = country id i.e. locked to that country/language/vendor cid unlock for the artemis is here with USPL http://xdaforums.com/showthread.php?t=311403

Rom I used for my MDA Compact III

http://xdaforums.com/showthread.php?t=317160

Read forums for your device first and remember to CID Unlock before doing anything...
[Android General] GruggerBaby:
Hello,

I have this phone: http://ztedevices.ca/en/zte-grandx.html (zte grand x v933)

and the issue is this phone is stuck at android jelly bean 4.3 and I want at least kitkat or lollipop.

I have seen other threads on this forum for options for other phones (zte Blade, zte grand x in, zte grand x Plus/max options)

But I want to be sure that I will not brick it. I have seen nothing for my phone. My question is, if the cpu/gpu is the same for other zte phones and their custom roms, will the rom still work on my phone and not brick? (if I try something like cynagenmod , or cwm etc)

Thanks
[Other Tools & General Discussion] Bonded6640:
I have a Samsung Galaxy s4 i337m .. Two different ROM's now have worked great, but same two screwed up after I got everything set up. Once it reboots it gets stuck on the first screen (Samsun Galaxy S4) and will not move forward from there into the program. Any ideas as to how I can fix this problem. You thing it could have anything to do with the kernel. The phone is rooted but is it rooted deep enough? I don't know i'm at a loss.. I'm Andy ( bonded6640@outlook.com ) if you can help :(:confused:
[Galaxy Grand Prime General] Fahd95:
1-Download the zip file from MOD EDIT,, pay per click links not allowed

2-extract the zip files and flash file (2_cache_recovery_stock_mohan...) via Odin

3-now your phone is rooted but you need to reflash the stock recovery.

4-to flash the stock recovery download (Stock recovery ) and flash it via Odin

5-open recovery >wipe cache partition>reboot system now.

Stock recovery link :

----------------------------------------------------------------------------------------------------------

Note: to best performance you can replace the superuser app

via installing kingroot app and click start

after that open kinguser > click on (uninstall tool) > click on superuser > click uninstall.
[Galaxy Grand Prime General] HighMans:
Works for me, thank you!
[Galaxy Grand Prime General] npredtorch:
OT: what's your SGP? I have a G530HXCU1AOA2 , what method and rom do you use to make it LOLLIPOP? Is it working on my baseband version? Thank you!

Gonna try your root instruction after upgrading to LP
[Galaxy Grand Prime General] Fahd95:
download the lolipop rom from h t t p : / / f o r u m . y o u m o b i l e . o r g /downloads/?sa=view&down=4710

and flash it via odin
[Galaxy Grand Prime General] npredtorch:
Thank you! Working good!
[Galaxy Grand Prime General] mrllokman:
Damn after doing this my knox warranty void is ox1
[Galaxy Grand Prime General] dcduartee:
Does this work on the G530FZ?
[Galaxy Grand Prime General] npredtorch:
what do you mean by that? is it bad?

Did your phone got rooted successfully?

i haven't use the procedure to root LP SGP
[Galaxy Grand Prime General] Fahd95:
What does Knox Warranty Void 0x1 mean >>>> w w w . s o l v e m i x .com/index.php/android-smartphones/695-what-does-knox-warranty-void-0x1-mean-solution
[Galaxy Grand Prime General] tutibreaker:
you should read the forum rules before make a threat [MENTION=6905155]Fahd95[/MENTION]
[Galaxy Grand Prime General] Whiskey103:
13. Advertising and Income Generation

Commercial advertising, advertising referral links, pay-per-click links and other income generating methods are forbidden. Do not use XDA-Developers as a means to make money.

XDA Rules
[Galaxy Note 4 Q&A, Help & Troubleshooting] khaledmhawesh:
i was wondering is double tap to wake available for the note 4 or not ?
[Galaxy Note 4 Q&A, Help & Troubleshooting] pratik_193:
Install a custom kernel ,

http://xdaforums.com/note-4/orig-development/tw-kernel-emotroid-team-t2990557
[Galaxy Note 4 Q&A, Help & Troubleshooting] khaledmhawesh:
too bad i have th C version of my note . iam gannna search for a one compatible with mine. if you know one please tell me thanks
[T-Mobile Samsung Galaxy S6 Edge] 215Aphillyated:
I am on a rooted t-mobile s6 edge running the older 5.0.2 software (didn't take the update)any devolopers working on a way to just simply flash a zip in recovery for what's need to run custom roms and kernals?coming from the htc m8/m9 it just seems like things are more complicated for this device
[T-Mobile Samsung Galaxy S6 Edge] sweets55:
I'm in the same boat. I'm on a 5.1.1 Rom but have the 5.0.2 base. I want to update the bootloader and modem but not sure how.
[T-Mobile Samsung Galaxy S6 Edge] 215Aphillyated:
I'm afraid to flash anything..lol...flashed a kernal 2 days ago based on 5.0.2...that is it...Samsung is very finicky..and it ducks for us
[Nexus 6 Q&A, Help & Troubleshooting] SomeArabDude:
After I flashed Android M Preview 3 this came up but I am able to boot fine and have already tried flashing back to 5.1.1 and repeating it. Any help? I have experience rooting and modifying system but this has never came up before.
[Nexus 6 Q&A, Help & Troubleshooting] obtained:
No worries, it's a new feature that comes with preview 3 and the bootloader.
[Nexus 6 Q&A, Help & Troubleshooting] orangechoochoo:
Never mind.
[Nexus 6 Q&A, Help & Troubleshooting] SomeArabDude:
Thanks! I was freaking out at first because I read in an article that is it says device is corrupt then that is very dangerous and your device could give out at any time.
[Nexus 6 Q&A, Help & Troubleshooting] kidhudi:
i had the same prob.

stopped when i flashed the non encrypted bootloader i think fixed it for me
[Nexus 6 Q&A, Help & Troubleshooting] edved:
I got that too! What's up with that? Others have seen it here...

---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------

http://xdaforums.com/general/help/strange-boot-error-message-t3156708/post61848119#post61848119

I did a factory reset and it disappeared!
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
Really? I never heard of such a thing... Where did you find it?

:rolleyes:
[Nexus 6 Q&A, Help & Troubleshooting] BackInA88:
I'm guessing he meant "boot.img"?
[Nexus 6 Q&A, Help & Troubleshooting] BackInA88:
I did a factory rest and it didn't work for me?
[Nexus 6 Q&A, Help & Troubleshooting] akellar:
The bootloader has nothing to do with encryption. This doesn't exist.
[Nexus 6 Q&A, Help & Troubleshooting] obtained:
Is it not this? http://www.droid-life.com/2015/07/27/operating-system-warnings-may-soon-come-to-your-boot-screen/

If it is, your device is fine. It just means your modified the operating system, and Google would like you to know that your data may no longer be safe with a modified system.

Further explanation of the warning here: https://support.google.com/nexus/answer/6185381?p=verified_boot&rd=1
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
Ignore. It's Google-policy. Google is growing and also the distance to the users. They don't like that we will modify the phone to our needs instead of the needs of Google or Telecom providers.
[Nexus 6 Q&A, Help & Troubleshooting] y2whisper:
Its weird for me as I got the message but my system hasnt been rooted or anything (on my N9). was thinking of doing a factory reset. Still might do that just to get rid of it. (I did dirty flash preview 3 over preview 2)
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
Factory reset won't fix it. Out of curiosity, do you have a decrypted kernel? Or TWRP recovery installed?
[Nexus 6 Q&A, Help & Troubleshooting] y2whisper:
neither left my n9 alone on that front.
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
Hhmm.. So you have the M3 system.img, bootloader, vendor.img, and stock recovery and still getting the message?
[Nexus 6 Q&A, Help & Troubleshooting] y2whisper:
Correct. Thus me thinking it was just something went wrong by dirty flashing over preview 2 (which was completely stock as well)
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
Yes, makes sense. If it bothers you, you could do a clean install....
[Nexus 6 Q&A, Help & Troubleshooting] y2whisper:
Yeah plus the new restore feature on M works pretty well with restoring app data (provided you don't cut off your connection during the restore)
[Nexus 6 Q&A, Help & Troubleshooting] Semseddin:
My nexus 6 is completely stock and i get that annoying " corrupt " message as well. It is just my bootloader that is unlocked if it's the reason of that message.

edit : i fixed my issue, check here if anyone have corrupt warning with a fully stock system.
[Nexus 6 Q&A, Help & Troubleshooting] inspiron41:
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.

Have TWRP install.

From TWRP install the Despair.R20.6.Shamu.zip

then flash BETA-SuperSU-v2.49.zip.

Reboot

PRESTO, Device Corrupt is GONE

I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
[Nexus 6 Q&A, Help & Troubleshooting] sklarskyj:
Ugh, all I wanted was to install 6.0 and keep my data.

I was on 5.1.1 stock rooted, xposed and wanted to go to 6.0 stock unrooted, but not lose data.

I thought I could use Titanium Backup, flash MRA58K (full wipe), root, restore app data, then unroot by flashing MRA58K (no wipe), but now I get the dreaded red triangle.

Even though I'm getting the red triangle, I am able to at least add cards to android pay (haven't tested using them) since I am not rooted and have a factory stock image, presumably.

When the OTA gets captured, I'm wondering if flashing LMY48W (without flashing userdata) to downgrade to 5.1.1 and then installing the OTA zip without rebooting in between would get me back on track without losing user data?
[Nexus 6 Q&A, Help & Troubleshooting] Jsunn:
I saw your post, but I still couldn't figure it out. Can you please help me get rid of the message?

Thanks!

-Jason
[Nexus 6 Q&A, Help & Troubleshooting] Semseddin:
Hi Jason,

Assuming you've flashed every stock image manually, when the phone boots up for the first time, there's a setup screen where you start with selecting phone Language. That is the initial setup screen i'm talking about., Skip all of them, into settings and make a factory reset. You will not get " CORRUPT " message this time. When you're in initial setup screen again, skip the page where it asks you to add your google account. When you're done, click PLAY STORE app icon and add your google account. This is how i fixed my persisting corrupt message. Hope it helps.
[Nexus 6 Q&A, Help & Troubleshooting] m0bstr:
im having this problem, how do I fix it. I tried to flash marshmallow over it but it didnt work
[Nexus 6 Q&A, Help & Troubleshooting] lfg7000:
excellent it works

Thanks for finding this fix
[Nexus 6 Q&A, Help & Troubleshooting] Semseddin:
Funny that my "fix" doesn't work for me anymore.
[Nexus 6 Q&A, Help & Troubleshooting] :
Same problem here, too. I've flashed OTA "from LMY48T to MRA58K" then tried to root with the bat file in "CF-Auto-Root-shamu-shamu-nexus6". After restarting the message appeared. Then, flashed entire MRA58K factory image through the flash-all.bat file so everything should be stock now but the message is still there.

Nexus Root Toolkit gets me that message about "system.img" not found or something...
[Nexus 6 Q&A, Help & Troubleshooting] Semseddin:
Allright,

This is my final solution for those who have " the corrupted can not be trusted " message with their %100 stock phones. Just downgrade to Lollipop 5.1.1 and take OTA to Marshmallow, you won't get that annoying message anymore. I fixed my issue like that.
[Nexus 6 Q&A, Help & Troubleshooting] adrian.gab:
After attempting to flash mra58k, I got the dreaded "Your device is corrupt. It can't be trusted and may not work properly" message non stop and it would even turn off after briefly blinking the message. Since I already had TWRP installed I did the following to fix the issue:

When the phone is off, hold power and volume up,

Use the volume button to reboot in to recovery, which runs TWRP,

There is a button at the bottom that while inside TWRP it lets the phone run MTP so that you can copy files across to the SD, I then copied across Despair.R20.6.Shamu.zip and BETA-SuperSU-v2.49.zip to the SD,

Then from within TWRP install the Despair.R20.6.Shamu.zip

Then install BETA-SuperSU-v2.49.zip.

I wiped the dalvik cache

Reboot

And now I don't get the message and it's at the Android is upgrading - optimising app 54 of 141.

Thanks to inspiron41 for the details.
[Nexus 6 Q&A, Help & Troubleshooting] mudk1pz:
Please HELP! I am completely new to the Nexus 6 and I just flashed TWRP 2.8.7.1 and after that I get the corruption error and the phone won't boot up anymore. Please help me. :crying: I tried flashing stock with nexus toolkit but it is still there.

please help me anyone.

alright found a how to and fixed it by manually flashing everything
[Nexus 6 Q&A, Help & Troubleshooting] Philip:
The latest SuperSU Beta is V2.52. http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Curious as to why you used 2.49?
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
found where the image is located with root explorer :silly:
[Nexus 6 Q&A, Help & Troubleshooting] adrian.gab:
That was the advice I had at the time and it works fine.
[Nexus 6 Q&A, Help & Troubleshooting] TMG1961:
I got the message as well, but unable to boot the phone. Took me well over 10 minutes to even get it booted into fastboot. Scared the living daylight out of me..dont even dare to root it anymore. Now busy with nexus root toolkit to flash stock and unroot and going back to 5.0 and then staying away from all for the time being. Too scared i end up with a dead phone.
[Nexus 6 Q&A, Help & Troubleshooting] rbrandser:
I ended up here after fastboot flash recovery, my device would not boot into android.

¨problem fixed thanks to you guys in this tread, adb pushed new kernel from here http://www.devfiles.co/download/6LafvfSE/Despair.R20.6.Shamu.zip
[Nexus 6 Q&A, Help & Troubleshooting] Rom Racer:
Can you give me the files? Please
[Nexus 6 Q&A, Help & Troubleshooting] blyndfyre:
Any way to avoid this "corrupt" message while maintaining a stock system so I can continue to update via OTA in the future?

If I install TWRP and flash that zip, then flash stock recovery again will my system be modified due to the kernel and therefore not update via OTA?
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
OTAs only come to untouched systems. You can't fool it by disabling the "corrupted" message, because it calculates checksums from all partitions, so a changed kernel, or a root gives totally different checksums, and it will refuse to update. The only thing it allows to differ from a factory supplied device is the unlocked bootloader. Any other modification will make it refuse to update. This is for security reasons.

And also, if your device is already unlocked then you don't have wait for OTAs, just flash factory images manually as they appear. If you pay attention and don't flash userdata.img then you will just continue where you were.
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
Out of curiosity, where is it located?
[Nexus 6 Q&A, Help & Troubleshooting] DonkeyAlex:
I suggest to return to stock ROM, and then use WUGtool's temporary recovery to flash ROM in zip format. Using this method i've never seen the corrupt message anymore...
[Nexus 6 Q&A, Help & Troubleshooting] ghost010:
After Rooting the R build, it wont boot past the warning message(never got the mesage until R build). Stock R works fine.. but i need root.

Using the nexus root toolkit for this all and not flashing custom recovery
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
Don't use toolkits, they aren't yet-up-to date with the Marshmallow security changes yet. To root Marshmallow you also need a custom kernel with the permissive SELinux patch, and the toolkits don't provide them. If you're not planning to use a custom kernel, then look here: http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
[Nexus 6 Q&A, Help & Troubleshooting] ghost010:
Root worked fine on the other Marshmallow build. why not this one? The other build didnt need a custom kernel.

Also, chainfire su isnt really my thing any more after reading this: http://xdaforums.com/nexus-6/general/root-t3231211
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
Are you sure? Did you root it yourself, or just used a toolkit and click-click-click?
[Nexus 6 Q&A, Help & Troubleshooting] ghost010:
Used Nexus root toolkit on the K build, every thing worked fine, no messages about coruption and all rooted aps worked.

Nexus root toolkit doesn't flash a custom kernel. It's pretty much the first time I heard of root needing a custom kernel. And I have rooted enough devices.

Used 2.0.5 on K build. Seems .6 and .7 do use chainfire kernals.. Stil doesn't explain how I got root on K.
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
Yeah, it did flash a custom kernel, you need to disable SELinux in the kernel for SuperSU 2.52 to work. And not only a custom kernel, but also a changed ramdisk, with verity removed from the fstab, so no red triangle. These two mean flashing a modified boot.img by the rootkit you used.

And that is why people say don't use rootkits, but instead search for the solutions yourselves, because this will be a problem for every update that came after the rootkit version you use.

Are you really sure, you were using stock?
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
Because the corrupt message is not true, we could bring G. to court.
[Nexus 6 Q&A, Help & Troubleshooting] cam30era:
I agree with you. While I did (do) everything manually with fastboot, I found the same result. No problem with MRA48K, but with MRA48R I got this message. It does seem like something changed, but the bootloader is the same so I don't quite understand what's going on.
[Nexus 6 Q&A, Help & Troubleshooting] Droidphilev:
lol, i think not. after all it IS corrupt.
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
You can still disable verity in the boot.img. But it's still to show your phone has been tampered with, and it does no harm.