yashsingh1/xdaforums huggingface dataset:
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] DorkyDev:
Yea hook me up even with "Rom-Name-v1.zip" and I'll google search that for a mirror if they're NAND's.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] badai:
off topic: does anyone have any app/games for winmo 6.5?
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Mister B:
Aps yes, games little. the PS games emulator was quite good once setup but i'm not much of a gamer .
[Galaxy Note 4 Q&A, Help & Troubleshooting] NexusS4gFreak:
I need a new camera module/replacement. Got my note 4 and the rear camera is just wtf. Wont focus at all past a few inches and is horribly blurry. Read on androidforums.com a lot of people had the same problem but simply got a device swap from their carrier. Seeing as I got it from amazon (for AT&T service) I cant take it back to the store and honestly would rather replace it than go through that hassle. So where can I find a legit sony 16mp back cam for it and also are there any instructions on how to replace it?
[Galaxy Note 4 Q&A, Help & Troubleshooting] NexusS4gFreak:
Bump
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] cnile:
is there any other software options for a S6Edge+ right now? can i flash something? are there different ones out there?

if so where/how?
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] Лithium-Фusion:
I think 6.0 will be second option in a mount ;)
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] ng0cthang:
You can't go under the 5.1.1 neither upper 6.0 because it's still not release yet. Maybe Febuary or March .... I really hate Samsung right now
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] marcochapita:
My fear is that they promise android 6 in December /January, but they don't release until the s7 is out because they don't want to lose sales, and they know people want the best and the latest so only upgrade after the s7 ??
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] Timmer_sixXx:
this is true for the S6 and S6 edge which was released in Q1 of 2015 , however, the plus was released mid august 2015, so my guess (yes, guess as i don't work for samsung) is that they will only release the S7 (and maybe S7 edge) but i doubt they will launch/release the plus version this soon. I think samsung is being samsung, and are just slow as usual...
[HTC One A9] bzowk:
Hey Guys -

I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.

Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and

will result in not only being able to format an SD internally and be rooted, but also a working phone:)

Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!

Phone Specs

Some as currently listed in Settings

- HTC One A9

- AT&T USA

- Rooted / s-off

- Android 6.0 / Sense 7.0g

Software Number: 1.10.502.3

Kernel: 3.10.73-perf-g28d66e0

Baseband: 1.0.U00297.1@51002.2_29.05_F

Build: 1.10.502.3 CL635081 release keys

Android Security Patch Level: 2015-10-01

Steps to Fix

1. Backup any data desired (I have a nightly Titanium backup)

2. Download RUU for same version (1.10.502.3) from http://xdaforums.com/one-a9/general/wip-ruu-htc-one-a9-t3240344

Should I use newer version or are those for different carriers?

3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)

4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later

5. Install TWRP via adb/fastboot

6. Install SuperSU via TWRP

At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...

7. Download & flash modded boot.img from A9 Root post

8. Install TWRP via adb / fastboot

9. Install SuperSU via TWRP

10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use

My Questions

1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not

2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?

3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?

4. What versions of TWRP & SuperSU should I use?

Any additional suggestions would be appreciated - I just want to get this resolved once and for all! -

Thanks!
[HTC One A9] Captain_Throwback:
First off, this isn't Development.

Secondly, I explained to you how to fix this in the very root thread you linked several times.

Thirdly, there's a newer, official RUU from HTC right on their ROM Downloads website. I'd start by installing that (though I also have a recovery-flashable version of that ROM in my Base ROM thread).

Fourthly, with access to an official RUU, and my ROM decrypt script, you have access to the stock boot.img (which is also in the firmware zip in my Base ROM thread), which you can use as your baseline for restoring the verity key to the ramdisk, thereby allowing you to use adopted storage without any issues. Note however that I was only able to use adopted storage with the "forceencrypt" flag enabled.

Fifthly, you can't just restore the stock boot image (at least not if you want to stay rooted). You can be both rooted and encrypted, but you have to first make sure SuperSU is flashed and set up prior to allowing the device to be encrypted again (adopted storage only works with an encrypted device, and then you won't be able to access your storage with TWRP).
[HTC One A9] bzowk:
OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.

I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)

Using an Ubuntu 14.04 x86 VM...

1. Download & extract your decrypt script to a temp folder in linux vm

2. In Windows, run same RUU I applied and copy out rom.zip from %temp%

3. Rename "rom.zip" to "rom_a9.zip"

4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm

5. Run ./decrypt-htc and wait for script to complete to get img files

On Phone (Currently has same RUU installed + TWRP but not rooted)

6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted

7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb

Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with:)

Thanks!
[HTC One A9] Captain_Throwback:
Re-read my post. If you flash the stock boot.img, you will no longer be rooted.

And as I said in the original thread, you need to pull the rooted boot.img and add the verity key from the stock one to it. Also you'll need to add the forceencrypt and verify flag back.

P.S. You also need to re-read the instructions in the decrypt thread. You don't have to rename anything anymore.
[HTC One A9] bzowk:
Good Afternoon -

OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...

I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.

Correct me if I'm wrong, but here's all I need to do to finish....

1. Download modified A9 boot.img from top of root thread

2. Flash modded boot.img using fastboot

3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)

4. Back up boot partition just like I did before in TWRP

5. Unpack it on PC to create ramdisk and split_img folders

6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack

7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save

8. Repack rooted boot.img

9. Flash phone with repacked boot.img using fastboot

10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting

Promise not to bug anymore if I can just get this resolved. :)

Thanks again for your assistance!

UPDATE

Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks
[HTC One A9] Captain_Throwback:
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).

If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.

Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?
[HTC One A9] bzowk:
Thanks -

Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:

- One unpacked boot.img extracted from latest RUU using your script in linux

- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed

That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.

Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?

Thanks for your patience!
[HTC One A9] Captain_Throwback:
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.

P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.
[HTC One A9] bzowk:
Great - Thanks!!

Just to make sure, below's my plan with a small question @ step #5

. Does it get your stamp of approval?

Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed

1. Boot into TWRP & bypass initial screen prompting for password

2. Format Data

3. Reboot back into TWRP

4. Flash SuperSU 2.76 zip

5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?

6. Unpack backed up boot partition from phone

7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone

8. Repack rooted phone boot (which includes both new files)

9. Flash newly packed boot.img to phone using fastboot

10. Enjoy

I

really

appreciate your help and patience with me! :)
[HTC One A9] Captain_Throwback:
Good so far . . .

I'm sure this is just a typo, but that should be 2.67, not 76 (there is no 2.76).

Bolded the correct one above (no need to leave TWRP as the necessary modifications have already been made).

Looks good . . .

TWRP can also flash the new image, but fastboot is probably the most reliable way to do it.

Hopefully . . . You'll likely get a reboot on the first boot (possible multiple reboots), as SuperSU needs a reboot to install the necessary files. Since your device will also encrypt on that initial boot, I'm not sure whether there will be a conflict or not.

Guess we'll see if it all works out . . . :eek:
[HTC One A9] bzowk:
Thanks!

I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.

I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.

If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:

c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s

The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.

Thanks again!
[HTC One A9] Captain_Throwback:
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.

And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.
[HTC One A9] bzowk:
Hey, hey, hey - think it worked!!

Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you

so much

for your help! I'm going to write a guide for newbs like me to use in the future soon.

Thanks again!
[HTC One A9] Captain_Throwback:
If your adopted storage doesn't show as corrupted, and you're able to open the SuperSU app in your app drawer and not get a message that no su binary is installed, you should be good to go :).
[HTC One A9] bubu2001:
bad topic
[MDA III, XDA III, PDA2k, 9090 ROM Development] sekou0:
Hi..

I have a Blue Angel (originally T-Mobile MDA III UK) and trying to get it running on Djuice in sweden..

I successfully flashed the phone to the latest HELMI BA WM6 R0 Public rar.. but the phone keeps telling me that the sim is invalid.. when i know it isnt..

Can anyone help me here?? any suggestion?

thanks..
[Nexus 6P Q&A, Help & Troubleshooting] jimmyray1990:
If anyone has the 6P on sprint don't mind dialing *#*#DATA*#*# and select LTE and list the numbers for NextLTE BSR Timer and BSR Max thanks
[Nexus 6P Q&A, Help & Troubleshooting] jimmyray1990:
Bump
[Android Q&A, Help & Troubleshooting] xMarkdSpot:
what is the best mmorpg app today?
[Huawei Watch] Rektifying:
I originally purchased the Huawei Watch with black leather as I prefer leather bands to metal. All I ever really knew for metal watch bands was the normal steel links, which to me are heavy and rip the hairs out of my wrist. Not exactly something I would like to wear all day long. I have been curious about the Milanese style bands since I seen them advertised by Apple for the Apple Watch. Anyways, I started browsing Amazon to see what was on offer for the Huawei Watch. There are two styles as far as I can see. Milanese bands with a "clamp" style latch and a Milanese band that loops through with a magnetic "latch". I definitely was more attracted to the magnetic style band so I figured I would order it up and give it a go. The only thing I was worried about was the magnet being too weak and coming loose throughout the day, which is not the case at all. It also comes with the quick release style pins, so no tools are needed.

Needless to say, I love it! It makes the Huawei Watch look very sharp and unique in my opinion. It is very comfortable and provides a perfect fit due to the way it "latches". I am pretty sure it would provide a perfect fit for any wrist. It fits the watch so well that it appears as if it were made by the watch manufacture itself. Ever since I have swapped the leather band for the Milanese, I have had quite a few different people ask me about it and wondering "what kind of watch is that?". Also, if you compare it to the other Milanese Bands on Amazon, this one "fits" better. The band itself is slightly wider than the part that attaches to the watch / the part the pin goes through. This is how the original Huawei Watch bands are as well.

They are available in stainless steel, black, and rose gold. The stainless steel matches the standard Huawei Watch perfectly! The part that attaches to the lugs is a "brushed" finish like the sides of the Huawei Watch and not a glossy finish like the face. I actually prefer this, as it will not scratch nearly as easy. I am sure the black would match the black just fine as well. They were $17.99 when I purchased, but they are now $23.99. Still, worth every penny! I guess you could always go pay $129.99 + tax for the Huawei official Milanese band, which has an inferior clasping mechanism in my opinion.

http://www.amazon.com/gp/product/B0178KWW3C?psc=1&redirect=true&ref_=oh_aui_detailpage_o03_s00
[Huawei Watch] player911:
Very cool. I've been interested in this style since I first saw the Apple version. I've looked online but all the ones I've found were using clips to latch. The magnetic band is very cool. I ordered one to give it a shot.

I would love to see some actual pictures of it on your wrist.
[Huawei Watch] Pilz:
Can you post some pictures of the band on your watch?
[Huawei Watch] OnnoJ:
Thanks for sharing! I have been searching some 2 months ago and could not find a magnetic loop band back then. I immediately ordered this band for HuaweI Watch and also for Apple iWatch and Gear S2 Classic... (Yesoo sells for all those watches!!)
[Huawei Watch] pmathis:
I have a similar band by Hoco...black melanese mesh with magnetic clasp....couldn't recommend it enough! https://plus.google.com/111656357014042389917/posts/ePHuhxVeRpg - photo
[Huawei Watch] rant:
I just received this very same band last week and love it! After purchasing a very similar 3rd party band for my wife's Apple watch, I thought this would be a great option for the Huawei watch and am very pleased. The magnetic clasp allows you to adjust for a near perfect fit on your wrist. This also has quick change pins, so it's very easy to swap back and forth between this and the original Huawei leather band when you want a different look. The only negative I've found so far is that the hair on my wrist gets snagged in the magnetic clasp if it's not aligned to the band perfectly.
[Huawei Watch] csick:
Also bought it

I also bought one. The only thing I don't like are that some of the links stick up a little on mine near where the mesh is joined to the solid metal parts (You only notice if you look closely and from the right angle, though), and also the metal is slightly darker than the watch case.

Overall though, I'm pleased, especially considering I paid under $20 for it.
[Huawei Watch] jaimerod:
I can confirm. This is definitely the best band for this watch. I was thinking the magnetic band would come off, or the links would be messed up, but everything is perfect. As soon as I put it on I got a lot of complements about my watch. Too bad nobody know what a Huawei Watch is around where I live. They always give me a blank stare like I just spoke some foreign language.
[Huawei Watch] bmg1001:
I have both the clasp variant mesh band and this magnetic variant mesh band. The magnet is nice and easy to use, and it's very strong too, but the quality of the mesh is much higher on the clasp mesh band. Slightly thicker and feels sturdier, plus it's pretty much a 90% exact stock mesh band replica.
[Huawei Watch] Rektifying:
Sorry, I didn't even think to post pics. I will post some later today.
[Huawei Watch] Pilz:
Isn't that a given? :silly: I'm curious to see how it looks compared to the Huawei one that I have.
[Huawei Watch] Rektifying:
Here are some pics. I am no photographer and the only camera I have is the one on my Nexus 6.

http://i.imgur.com/MgouCHa.jpg

http://i.imgur.com/myky5CI.jpg

http://i.imgur.com/s5dPdoI.jpg

http://i.imgur.com/8VxT00E.jpg

http://i.imgur.com/XPPNp4s.jpg

http://i.imgur.com/fNokQFp.jpg

http://i.imgur.com/cxAN4fD.jpg

Sorry, I still can't figure out how to get pics to post directly on my comments. Why can't all forums be like overclock.net and many others and have integrated photo uploads? Where when you go to post a pic, you just upload it directly from your computer and not have to use some third party site and post links... so annoying.
[Huawei Watch] wilsonliang777:
I have the hoco milances magnetic clasp band in stainless steel and I also really like it. My only complaint is that the magnetic clasp slips when I am doing any kind of physical work. I am a social worker my day but in the weekend I like dyi projects around the house. The watch slipping lose sometime is annoying. But over all the w a huawei watch looks great with this band.