yashsingh1/xdaforums huggingface dataset:
[G3 Q&A, Help & Troubleshooting] An4u:
My G3 D858HK got bricked after trying autorec lollipop ( I was running MM stock + King root ).

After spending quite a few hours and reading through various ,sites, forums, and POST's , I could finally unbrick my phone.

I am just writing down steps I have followed .

Disclaimer: Use these steps on your OWN risk. I don't hold any responsibility. All the SW tools / roms / files referred in this thread is developed by great developers in XDA, please Thank them / donate them in respective threads.

Please visit and Thanks author of this thread . I deduced complete steps from that great guide ( Only difference: I haven't opened my Phone ).

1. remove and reconnect battery.

2. While holding Vol UP button I have insertUSB cable

3. Open device manager and noted new device under COM ports

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

Note: Initially it was showing as RELINK QS driver ( even if it is QS_BULK device , please follow this instruction ) . With this driver I was hitting error "device not found in dload trying flash programmer" in board diag tool

Following steps required to change it qualcomm driver.

type "change device installation settings" in windows search .

Change to " Never install driver from windows update".

Now uninstall RELINK driver by right clicking it from device manager ( Check box to delete driver )

Now install Qualcomm driver from following link http://xdaforums.com/atta...5&d=1433975241

remember to enable test mode using following commands ( as Admin ). if you already have it

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS

bcdedit -set TESTSIGNING ON

reboot server

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

4. Now repeat steps 1-3 and made sure Qualcom device is listed under COM ports ( Note: if red and blue LED glowing you may not see , com device , repeat step 1-3)

5. Note down com port from device manager.

6. Now open Board Diag tool and select the proper chipset (B2 ) . use the com PORT number noted in step 5 , in board diag tool

7. Use KK TOT file ( Magnetic Link ) and extract it to a location using board diag tool

8. Use the same directory in board diag target directory field

9. Select recovery image to flash in following order ( aboot , backupgpt-boot-dbi-laf-primarygpt-recovery-rpm-tz-sbl1 )

Note: Keep the device manager open , after each component flash , phone may get reset and we may loose com port, repeat step 1 to 3 to get the com device back.

10 After flashing sbl1 phone may to recovery - now repeat step 1 and 2 you will see download mode

11. Now use MM KDZ file and follow steps from this guide to install MM stock rom

################################################## ###
[Android Q&A, Help & Troubleshooting] kenerwin:
Hi all,

I was bought Dell Venue 8 7840 in China and I struggled to install Google Play Services without success.

Already root..

What should I do know?

Thanks
[General Questions and Answers] Propphet:
Hello, i was wondering if it is possible to see witch date your phone is rooted.
[Nexus 7 (2013) Q&A] nightang3l:
My microUSB port is messed up and will not charge by wire anymore. I got this device as a gift from my family. Do you think I should have it repaired?
[Nexus 7 (2013) Q&A] echow2001:
If you are comfortable soldering a new one on then yes. If you are looking to buy a new daughter board then it is not worth fixing. Just buy a wireless charger
[X 2014 Q&A, Help & Troubleshooting] Gumg:
Hi everyone,

I bought a car that has a infotainment system that supports "MirrorLink interoperability" but I realised that Moto X or any Motorola phone does not has this feature.

Somebody knows if there is a way to enable it by root the phone or any another way to make it work?

I already root my Moto X.

Best Regards,
[Xiaomi Redmi 2 Questions & Answers] newronaldo@7:
It will be great if we get custom kernel for kitkat roms.. Like miui/cm11 .. Kitkat roms are best in terms of stability. So I request devs to compile kernel for kk if possible :)
[Xiaomi Redmi 2 Questions & Answers] pirej:
A request to your request.. build it your self, its faster than waiting for someone who is not gonna do it..

Here are some kitkat kernel sources..

The first one that ever existed..

The second one
[Xiaomi Redmi 2 Questions & Answers] Dyt199412syam:
Its marshmallow time. Why you wanna go down to kitkat when the stable MM roms is available now? Its out date. As pirej said, build your own custom kernel if you really want it!!!
[Xiaomi Redmi 2 Questions & Answers] potlapalli1:
i don't know why? really like kitkat rom very much. i heavily use internet with both 3g and wifi for almost 15-18 HOURS per day. i know marshmallow is stable now but with heavy usage cpu temperature goes over 50 it makes phone very hot we can't touch it. in kitkat with same usage got temperature around 44-46 and never crosses 50. so i am staying with kitkat. he is just requesting u not forcing u to make a kernel
[Xiaomi Redmi 2 Questions & Answers] gustavray:
yeah like he just said, kitkat doesnt overheat like Lollipop and Marshmallow. Unfortunately building a kernel isnt as easy as flashing a Rom so many of us can't do it. I myself keep flashing over and over again, coz when im on M, my phone overheats and i miss MIUI interface. when im on kitkat, i feel outdated. i have an internal conflict :((((
[Xiaomi Redmi 2 Questions & Answers] saurabh1234:
same here...
[Xiaomi Redmi 2 Questions & Answers] lr7745:
Could anyone tell me what's the best (most stable) kitkat rom for 2014818? All I can find are 2014813 roms :(
[Xiaomi Redmi 2 Questions & Answers] newronaldo@7:
Yaah Kitkat is outdated but I like it more than MM and Lp and Its my personal wish that I want a Kitkat kernel.. I'm not forcing or ordering anyone to make a kernel for me.. I'm just requesting.. If I was able to make kernel then I would not ask others to make it.. Don't know whats your problem If I'm requesting
[Xiaomi Redmi 2 Questions & Answers] newronaldo@7:
Sir If I can make one by myself I wouldn't ask anyone to do it.. I'm not forcing.. I'm just requesting
[Xiaomi Redmi 2 Questions & Answers] Lennoard:
Hey yo, Just like him I am back with the MiUI KK.

Every MM rom I've tried I couldn't proper use the GPS and the adb.

So, if you know any MM rom that these 2 features are working fine, please tell me!

My model is HM2014819
[Xiaomi Redmi 2 Questions & Answers] Dyt199412syam:
No gps and adb bug here on my 2014813. If you want install bugless mm rom, install cm13 rom. Just follow this instruction http://xdaforums.com/redmi-2/how-to/rom-install-official-cyanogenmod-13-t3374589?nocache=1, and you will enjoy it. Happy flashing bro!!
[Xiaomi Redmi 2 Questions & Answers] olegst:
I'll reveal the secret-CM does not need ... no one needs, in general
[Xiaomi Redmi 2 Questions & Answers] Lennoard:
Thanks, it seems that everything is ok now.

I can use adb but only on PTP mode (which is not that bad anyway)

GPS seems ok too I thought it was device problem...
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] topjohnwu:
System Verity Checks​

Thanks to the investigation of [MENTION=2605798]nkk71[/MENTION]

Data Encryption and Data Signal​

Short Story:

Decrypting the DATA partition will break signal

Full Story:

I was testing out data decryption one day and did some tests. Soon I found out that my phone cannot receive any signal.

At first, I thought it was caused by Xposed, so I restore system and boot, flash SuperSU to patch the boot image. The result is still the same, no signal.

Then I thought it might be SuperSU, so I manually modified the fstab of the ramdisk, the signal is still broken.

Before doubting the hardware might be broken, I restored everything back to stock (include forceencrypt boot), and it everything works!!

I've done the tests above several times, just in case I missed anything. The results are always the same: once the data is decrypted, the signal won't work.

Conclusion:

Don't try to decrypt your data until people found out the reasons.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
I look forward to exploring this further once I have my 10. Looks like it'll be loads of fun :)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jcase:
I wouldn't worry about s-off, soon enough. SunShine will support m10 in the near future (dont ask for ETAs or anything of the sort). There are bound to be some issues we need to fix up once we have our devices, but I am confident we will find a solution shortly.

I'd also stick to flashing full RUUs (official or repacks, makes little difference) when updating a modified device, I've never been a fan of OTAing a modified device, and there is a lot of good reasons not to. Especially if the new boot.img is fully expecting an encrypted userdata partition and you don't have one. Rom developers, recovery developers, kernel developers, and yes exploit developers need to get used to working with an encrypted userdata partition.

If you can get me a logcat from boot on wards on a unencrypted device with radio not working, I will gladly look at it.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] topjohnwu:
Here you go :)

RUUs are not easy to get, especially the newer devices that are not US versions.

Really hope HTC can provide official RUUs to restore our devices.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jcase:
We will see RUUs for it

Will look when i get back home
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
[MENTION=4470081]topjohnwu[/MENTION]

Can you upload a copy of the OTA zip when you get a chance? I'm curious to see how the contents look. Thanks!
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] topjohnwu:
I'm uploading everything now :)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Superguy:
Just curious - if this ends up being a huge PITA, anyone know what HTC's return policy is? For me it was between the 10 and the Exynos S7, and I'm giving this a try first.

Does Sammy encrypt the data portion on the S7s as well?

Glad to see Sunshine's coming our way! :)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] PhoenixPath:
He mentioned TWRP. Did he try stock recovery? (or did I miss that in the post?)

Don't get me wrong; I know the guy is a wizard with HTC devices, but I want to know that was tried and failed...
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] topjohnwu:
I had tried restoring the system back to 1.21.709.2, then flash 1.30.709.1 stock recovery, still the OTA won't show up on the device.

So it might detect that the recovery and system doesn't match and refuse to push update. There is possibility that HTC is not actually detecting the boot loader unlock, but instead detecting the stock recovery.

However, I have no chance to test it since there is no way to get 1.20.709.2 stock recovery, only if someone unlocks the boot loader now and test if he can detect the OTA, or HTC releases a new OTA so I can test from 1.30.709.1
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Did you revert your main version? That's the only way you'd be able to take the OTA again.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] topjohnwu:
Yes of course :)

It is the same issue, same logcat error.

So I simply guess that HTC blocked all bootloader unlocked phones to receive OTA. But it might be detecting the matched recovery with the system though.

Have to wait for someone to unlock their bootloader, or HTC has to release the next OTA for me to test (right now I only got the new recovery)

However, the new recovery still works on the old version.

The trick I used to upgrade my device is about grabbing/guessing the OTA link from HTC server. Then I can manually flash the OTA zip.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] mahdibassam:
So considering these issues, there is no stable root for the 10 as it will cause the signal to drop off right?

Sent from my Galaxy S7 Edge
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Incorrect. You can still root via the usual/normal means. You just can't be decrypted. That's apparently what is breaking signal.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] topjohnwu:
(Apr 26 Update)

By tests from other HTC 10 owners, we now confirmed that unlocked bootloader without any modifications can receive the OTA.

So it means that HTC didn't detect the bootloader status when pushing OTAs, it is depending on other factors.

What comes up my mind is the following two possibilities (both personal guesses, no confirmations):

The 1.21 stock recovery is different from the 1.30 one, although both functions the same and can accept flashing the OTA.

HTC checks if the stock recovery is valid before allowing the OTA to show up on the device.

HTC introduces some protection method like the Samsung knox: un-official boot images cause the phone to write some flags to the device.

If this is the case, [MENTION=2376614]jcase[/MENTION] might be interested in it :)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] mahdibassam:
Oh ok. Marshmallow is encrypted by default if I'm not wrong, so if you don't manually decrypt you should be ok then? Also, since there is no root here on XDA for the 10, we would just have to flash twrp and download and flash super su and that's it? Thanks for your reply.

Sent from my Galaxy S7 Edge
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Correct. You can choose any root method (SuperSU isn't the only option), but that's been the standard way to root HTC devices for the past several years.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Superguy:
Maybe I misunderstood, but didn't someone say that we needed to be decrypted in order to put a Rom on, it us that just so we don't have to wipe the /data and internal SD each time?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] topjohnwu:
Yes, that's the usual case. What I was pointing out here is that, you can no longer decrypt the data partition anymore (at least for now).

If you want to flash roms, you have to use external sdcard or use adb sideload, and yes if you want to clear data, you have to also clear all internal storage.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
When you manually modified the boot.img while decrypted, what exactly did you change? It is possible that the system is performing a checksum validation of the boot block device to determine whether it's been modified, prior to allowing an OTA to install. But it's also possible that certain modifications to the ramdisk cause it to error out as well.

It might just perform the same signature check that causes the "red text" to appear when booting the device, in which case yes, the boot.img would need to be fully stock for the device to accept an OTA. As long as the recovery is signed and is from the current OTA of the previous version, that shouldn't be an issue for taking the OTA, as the only check done there should be for the device name and build fingerprint.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Alright, so per your request, I tested this.

Yesterday I had to format data, so I decided to help test [MENTION=398245]LeeDroid[/MENTION]'s ROM for a bit. Afterwards, I restored stock 1.53.617.5 system image and ran that until this morning. This morning, I created a Download-mode flashable zip of the 1.21.617.3 stock boot and system images. I flashed that, then booted the device. Then I checked for Software updates. First, I got an update for Camera and installed that. Then I checked for updates again, and got the 1.53.617.5 OTA notification, which I then downloaded. It prompted me to install, which it then booted into TWRP to try to install (yes, I've had TWRP installed the entire time - at no point did I flash back to stock recovery). I'm using a test version of TWRP right now, so the OTA didn't install, but I was able to then install the OTA zip I had previously downloaded in TWRP. Then, to get all the way back to 1.53.617.5, I flashed the boot.img from the 1.53.617.5 firmware.zip that I'd previously extracted. I then flashed SuperSU to get root back (since flashing the stock boot.img removed it).

Right now my device is booting and "Android is upgrading..." so I'm not sure what to tell you. It seems you're missing something in the process, or the Taiwan device is somehow different, though that doesn't make any sense to me.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jollywhitefoot:
It may be different, but there are plenty of people with the issue on the US Unlocked version as well. For everyone except one person plus [MENTION=4470081]topjohnwu[/MENTION], flashing the new firmware package solved the issue (myself included). Flashing only the stock boot from the firmware has not fixed it for anyone that I've seen. So for most of us, something that we've done during the unlock, root, s-off process is breaking the ability to take OTA, but the new firmware fixes the problem. BTW, the solution of flashing firmware has solved the issue for both s-on and s-off devices.

Is it possible that the difference is the test version that you're using?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Test version? You mean of TWRP? No, that wouldn't matter. If the issue was having a non-stock-recovery flashed, it doesn't matter which version of TWRP I'm using.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jollywhitefoot:
Yes, I meant the test version of TWRP. But my question was more along the lines of does our public version of TWRP do something to the device that your test version does not do.

Anyway, it's not a big deal, just kind of a mystery. For most people I've seen, flashing the firmware fixes their issue with downloading and applying OTA.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Nope, my test TWRP is built using the same source as the official. It just has some extra pieces. Nothing that affects anything besides recovery, though.

It sounds like people are touching system somehow without realizing it, or not being careful with the verity flag when rooting. I've gone back and forth a few times, and it's not as if my device is somehow different or special. So it seems that there is user error causing most of the problems, likely because people don't necessarily understand what they should or should not be doing, or the proper order of operations when formatting data or backing up system image and the like.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] jollywhitefoot:
That's highly likely in my case. I'll probably do what you did and restore back to 1.21 and try to break OTA again to see exactly what step in the process is breaking it for me.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
You know, as I think back on my process from the beginning, one thing I might have done that I'm not sure anyone else did was to restore stock system image through TWRP immediately after SunShine S-OFF, and restore dm-verity (I had to disable it for SunShine to run).

That got me back to a valid starting point for everything to follow.

EDIT: Also, I didn't back up "System" in TWRP prior to S-OFF, just "System Image". The former is unnecessary, and I didn't want TWRP to "accidentally" mount system and break verity (not that it happens, but I like to be cautious).

EDIT 2: Figured I might as well detail my complete procedure here, so others can confirm whether it works for them (or not):

Unlocked bootloader via HTC Dev

Flash TWRP

Boot into TWRP (Cancel decryption prompt & leave system read-only on boot)

Backup "Boot" and ""System Image" in TWRP to External SD

Wipe - Format Data (or Wipe Encryption) in TWRP

Boot device and let it re-encrypt

Reboot back into TWRP (Cancel decryption prompt & leave system read-only on boot)

In adb shell or TWRP Terminal, echo KEEPFORCEENCRYPT=true>>/cache/.supersu

Flash BETA-SuperSU 2.72 from external SD card

Reboot back to system, and the device will reboot itself once as SuperSU installs

Do the SunShine

Boot into TWRP, restore stock boot and system image backup & Wipe - Format Data (or Wipe Encryption) again

Reboot device and let it encrypt again

Reboot back into TWRP (Cancel decryption prompt & leave system read-only on boot)

In adb shell or TWRP Terminal, echo KEEPVERITY=true>>/cache/.supersu (the file should still be there, so both commands will now be present)

Flash BETA-SuperSU 2.72 (again) from external SD card

Reboot back to system, and the device will reboot itself once as SuperSU installs (again)

Now you're rooted, with pristine stock system image and with forced encryption and dm-verity still enabled. In this state, you should be able to Download OTAs, use Android Pay, etc.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] FreydNot:
[MENTION=1162986]Captain_Throwback[/MENTION], can you discuss why you used only KEEPFORCEENCRYPT in step 8 and then added KEEPVERITY in step 15? Why not use them both, both times? Did Sunshine fail to work unless Verity was disabled?

EDIT: also, how can you verify that Verity was maintained? Is there a command to run that will give a pass/fail on the status of the partitions verity?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
The first part of your post I answered at the top of the post you were referring to, I guess you missed it:

As far as your second question, I usually just look in /fstab.qcom when I boot into Android and confirm the flags on the first line say "wait, verify". The "verify" means dm-verity is enabled. There is a getprop you can run to know verity status, probably. But I don't use that.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] topjohnwu:
[MENTION=1162986]Captain_Throwback[/MENTION]

Thanks for testing, here I would also write my whole procedure:

Got my device at 4/15, I unlocked bootloader, flashed TWRP, Backup System Image and Boot immediately TWRP boots up.

With my system image and boot backed up, I flash Xposed and SuperSU to my phone, and started to do some modifications to the system.

Some time later, I received the camera app update (maybe a week later). Installed without an issue.

More time later, the 1.30.709.1 OTA pushed to the 10. With my modified system, it showed up "My system is corrupted"

I restored system and boot image immediately, but it still shows "My system is corrupted"

I confirmed that many Taiwanese also experienced this issue (they are developers not noobs)

After some panic I managed to get the OTA link. Then I flashed the stock recovery from the OTA firmware, and tried to manually apply the OTA. It worked flawlessly.

With the OTA applied successfully, I am sure my system image backup is legit, and starting to suspect other factors that causes the "System is corrupted" message

I cannot find anything wrong with all what I've done.

The only difference I see with your procedure and mine is that you have never seen the "System is corrupted" message. All the time you tried to apply OTA, your system is always pure stock.

If you'd like to test more, would you try to let the "System corrupt" message to show up, then try to restore things to fix that message. I know it's weird, but I cannot think up of anything that could cause OTA to fail.

I could live with manually flash OTA zips though :), all this testing is just for the truth.

Thanks a lot man.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
After getting that message, did you ever try clearing data for the Updater app in Settings?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] topjohnwu:
I even tried full data wipe.

It has already driven me crazy lol. I tried everything I can. It just won't work for me :eek: