yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario ROM Development] its right:
very nice ones, for welcome screen, if you can edit the logo and texts to be on the top left corner like others :rolleyes:

very great work and the competition is really started, i think i will use all of them, for now, i used hamin ones for the next release and i'm sure your style is another great one :D

tnx
[8125, K-JAM, P4300, MDA Vario ROM Development] its right:
very very nice pictures man, you are great designer :D

now, i know why you wrote "its right" on capital letters, in small letters the name is not really clear, so if it easy on you to edit Hermes one to have the name as capital letters (just for "its right" text). sorry for that.

thanks one again, anyone noticed the Hermes screen!!! unbelievable designer Hamin
[8125, K-JAM, P4300, MDA Vario ROM Development] the greyzter:
is this more like what u wanted?????
[8125, K-JAM, P4300, MDA Vario ROM Development] abdoofikry:
i think u should take this
[8125, K-JAM, P4300, MDA Vario ROM Development] its right:
i'm talking about the other one :D

thanks bro
[8125, K-JAM, P4300, MDA Vario ROM Development] dielo:
i lke hanmin's work...realyy great designs...i've learned a lot from him....especially the box art..
[8125, K-JAM, P4300, MDA Vario ROM Development] hanmin:
thanks for the comment. I've just recently moved.. and getting an interview tomorrow, I'll do the Hermes one ASAP when I'm available :) sorry for the delay.

UPDATE:

Attached :D
[8125, K-JAM, P4300, MDA Vario ROM Development] solomhamada:
you know what i think ? TNT needs a new set of graphics for the new great rom!
[8125, K-JAM, P4300, MDA Vario ROM Development] Simonkjam:
I think this is a good style for TNT, the splash screen title is "Light my phone"...

I hope you like it, have a nice day bro!

View attachment 104799
[8125, K-JAM, P4300, MDA Vario ROM Development] dhawal4u:
pls do whatever but dont include screen which have like this because its hard to see what has been written there .
[XDA Assist] XDA Visitor:
Hi, i recently soft bricked my oneplus 2 (4 GB) so now whenever i try to reboot the phone, it is stuck on the logo screen, there is no recovery(i had twrp installed) but the phone can enter into fastboot mode. I tried installing custom recovery using my computer but its no good. Anyone has a solution?
[XDA Assist] Trafalgar Square:
Hello and thank you for using XDA Assist,

please create an account and ask your question here:

OnePlus 2 Q&A, Help & Troubleshooting

The experts should be able to help you!

Kind regards and good luck :svetius:

Trafalgar Square

XDA Assist
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] darksarken:
I need urgent help, I was using TWRP manager and tried to install that over the clockword mod recovery, now the phone is n a booting into recovery loop and wont boot at all.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] darksarken:
I was using resurrection remix as a custom rom and that was 6.0.1. Is there anyway I can go back to 5.1.1 stock? I get SW REV Check Failed:Fused 2>Binary 1
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] BoiBundy:
Want to help

If you remember what version of android were you on?

Can you boot into download mode?

If you can answer those 2 questions then my best guess is you can ODIN back to stock with out an issue.

Just download ODIN 3.09 from some where shouldn't be to hard to find.

and download the top link from here: http://xdaforums.com/note-4-tmobile/development/mirror-stock-tw-t3260858

unzip the samsung firmware(only once), put your phone in download mode, plug it into your computer, open odin, click "AP" and find the file that you just unzipped

make sure you click no boxes but "AP" and hit start and let odin do its thing.If yu have any questions Id be glad to answer
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] darksarken:
Help

Okay after this passed my phone is still rebooting in a loop for some reason? Do you know why?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] nine5raptor:
Factory reset from recovery should fix it.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] BoiBundy:
Raptor is right, pull your battery for about 20 seconds replace it and hold volume+up and home while powering on. And you should be presented with a dead android. From there I believe you factory reset your phone.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] BoiBundy:
Sorry, in literally always busy but here is the exact step by step method of resetting from recovery:

Turn off the phone. If the phone will not turn off, remove and re-insert the battery.

Press and hold the following three buttons at the same time:

Volume Up key

Home key

Power key.

When the phone vibrates, release the Power key.

When the Android System Recovery screen appears, release all keys.

Press the Volume down key several times key to highlight 'wipe data / factory reset.'

Press Power button to select.

Press the Volume down key until 'Yes -- delete all user data' is highlighted.

Press Power button to select and start the master reset.

When the master reset is complete, 'Reboot system now' is highlighted.

Press the Power key to restart the device
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Stiria:
I'm actually having the same issue, but seems more complicated.

I was using resurrectionremix, and bluetooth/lte wasn't working so well so I decided to factory reset it and install the stock factory image.

But when I try to flash using Odin (3.07, 3.09 tried both) it gives me this error.

<ID:0/015> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> N910TUVU1ANK4_N910TTMB1ANK4_N910TUVU1ANK4_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/015> Odin v.3 engine (ID:15)..

<ID:0/015> File analysis..

<ID:0/015> SetupConnection..

<ID:0/015> Initialzation..

<ID:0/015> Get PIT for mapping..

<ID:0/015> Firmware update start..

<ID:0/015> SingleDownload.

<ID:0/015> aboot.mbn

<ID:0/015> NAND Write Start!!

<ID:0/015> sbl1.mbn

<ID:0/015> rpm.mbn

<ID:0/015> FAIL! (Auth)

<ID:0/015>

<ID:0/015> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

And on the phone

UDC START

SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1

[1]eMMC write fail : ABOOT

And teh firmwares I tried are

NIH, NK4, COD

MTP Isn't working, the phone isn't recognizing my microSD card either so there's no way for me to flash anything through zip TWRP.

Can somebody help me out? Thanks
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] d12unk13astard:
By chance are you already on 5.1.1 firmware, if you are you can't downgrade back to those lower fws and the stock factory Odin is dok2. Try that 1 instead.
[HTC 10 Questions & Answers] stevedebi:
I have had the same Transcend 64Gb MicroSD card in my M9 for a year. When I got my HTC 10 last week, I transferred the card to my new phone. Then the past couple of days the camera app has been complaining about the card, and this morning it failed entirely. I replaced it with a backup 32 GB for now, but I'm wondering if anyone else has lost their card?

The card won't even format on my PC. It is possible it just failed, of course.
[HTC 10 Questions & Answers] badzi0r:
HTC 10 damaged my micro SD card. Did happen to anyone else?

I listened music form my phone on my way to work in the morning and then, on way back home firstly music didn't play, so I found that card is not recognized by the system even after restart. I have checked it later on two computers with 2 different adapters and no appliance can recognize the card. Branded 64 GB Lexar fast card. HTC wasn't restarted or so, wasn't even hot I kept in whole day in the pocket. I'm not sure what to do, I mean don't want to lose another memory card which I probably buy.

And maybe, by any chance, someone have any idea how to check memory card whether is completely dead?
[HTC 10 Questions & Answers] dottat:
Did it ever occur to you the card could have had a hardware failure?
[HTC 10 Questions & Answers] argenteloup:
It's more likely a short life span micro sd card, and this kind of suck always happen once a while.

Don't blame your phone unless other one or two micro sd cards also die in the first two weeks.
[HTC 10 Questions & Answers] badzi0r:
Hi, The reason I'm asking is to avoid the risk in the future. If it happens to anybody else I will rather buy some cheaper card.

That memory card was bought for GoPro so I use it for many other apliances without any problem and suddenly it broke with HTC 10. At least I noted it here for statistics.
[HTC 10 Questions & Answers] nobnut:
...and if it had broken in one of your "many other appliances" it wouldn't have been broken by your HTC 10.

Cards fail. Cheap cards fail often.

Lesson, buy more than one card and don't recycle them from device to deice.

Another lesson, don't ever buy cheap cards.
[HTC 10 Questions & Answers] Eagle1337:
lexar isn't usually horrible, but yeah sd cards fail. On the notes of sd cards dying my t3i must have killed my sandisk ultra 2, it couldn't have been the card that died.
[HTC 10 Questions & Answers] ztescorer:
The HTC 10 does appear to be finicky with microSD cards. My 128GB Sandisk that worked totally fine on a Galaxy S5 kept giving me problems on the HTC 10. I wonder if the phone is stressing the cards too much somehow (for instance if it is scanning the card too often for media files and you happen to have tons of media content on the card like in my case).
[HTC 10 Questions & Answers] badzi0r:
Thank guys for the reply,

I never broke before any memory card and that one was not cheap. Happily I can buy now double capacity and double speed for half of the price which I spend for the last one. I'm planning to buy Lexar 128GB. That card did work perfectly but only few days. ;)
[HTC 10 Questions & Answers] Obnixe:
I'm having issues with my card as well. I purchased the SanDisk Ultra 200GB Micro SD from amazon. I put it straight into the phone and ran diagnostics on it to confirm it was a true SanDisk card and its read/write speeds which were in line with manufacturer's specs (88 read/ 14 write). Within the day it was having issues pulling images off the card. All the images saved directly to the card had a grey area or "box" over some portion of the photo that would correct after a few seconds leaving the full picture to view. The images could be sent with no problem but eventually they seemed to become corrupted. I figured it was the slow write speed causing the issue so I replaced it with a new Samsung ProPlus 128GB card (95 read/ 90 write) and the issue still persists. Not sure if anyone else is seeing anything similar.
[HTC 10 Questions & Answers] afuller42:
if your looking for a new one, this one is great. very fast speeds 90mb write 95mb read. bit on the spendy side so hopefuly it was just the card failing and not the HTC 10 eating them ;)

I haven't had any issues with 1000s of files on mine so far, crossing fingers
[HTC 10 Questions & Answers] rockyk86:
Same here, Kingston 128 GB micro SD worked fine on my s7 edge. Inserted the same card in my HTC 10 and it was readable for the first hour, after that the card was not recognised by the device. The card wasn't even recognised by my Mac and PC. I'm glad I had my photos backed up on google photos.
[HTC 10 Questions & Answers] alexp999:
My 64gb kingston kicked the bucket in my HTC 10. Last weekend I woke my phone up and it said sd card unexpectedly removed. Card was not readable in any other device.

Got a Sandisk as a replacement as never had an issue with their cards in the past. The kingston only lasted 4 weeks, but I'm putting it down to just a faulty card.

If the sandisk dies too, then I'll be a bit concerned it could be the phone...
[HTC 10 Questions & Answers] DrearierJester1:
Im Using Lexar Pro SDCARD 128gb and havent had issues using it. The card was also formatted as adaptive.
[HTC 10 Questions & Answers] badzi0r:
So, there is two of us. There is one only connection - 64gb.

Where is Sherlock? ;)

by tapatalk@htc10
[HTC 10 Questions & Answers] Rioter_78:
You're made me worry. I use SanDisk 200 Gb, it's kinda expensive one.
[HTC 10 Questions & Answers] Haldi4803:
Worry for what?

I don't have any issues with my HTC10, but I broke a 64gb Sandsik in my Sony X10i, phone just got hot. Shut down, Card didn't work anymore. And another one SanDisk 128gb was in my Sony Z2 when I replaced the back plate somehow the MicroSD got broken.

The 64gb Card had a Lifetime Warranty and the 128gb a 10 year. Not sure how long my 200gb card is now. Think they reduced it to 3years or 5.

But yeah, went to their Homepage, registered the cards. Requested replacement, they sent someone here to pick them up, 5-9days later I got the new Cards via Mail :)

So yeah, always back Up your important stuff somewhere else and who cares if they fail. It's annoying Yes, but **** happens.
[HTC 10 Questions & Answers] richii0207:
SD cards can fail in ANY device. I wouldn't go as far as saying it failed because of the device. Quality of the cards is what really dictates how soon failing can occur. A knockoff SanDisk failed in a few months while the real one has lasted years for me. I highly recommend SanDisk and Samsung SD cards because I have had no issues with their original products.

EBay and some Amazon sellers have tendencies to sell fake cards so beware.
[HTC 10 Questions & Answers] mauiblue:
I woke up this morning and my HTC 10 says that the micro card couldn't be recognized. Crap. Did a search and found this thread. The card is a Lexar 64gb card. I went to Walmart this afternoon and got a Samsung 128gb card. Hoping this card will last my long tern stress test. Ha!
[HTC 10 Questions & Answers] SacredDeviL666:
+1

been using this without any problem 128gb and prior to this i tried samsung evo + 128 and that worked fine....

but as the OP stated it is true that many users using diferent sd cards has been facing issues with htc 10.....

some has issues on some firmware, some on custom kernels, some on different formats so its wise to say that there is something beyond a faulty sd card itself.

in all the custom rom threads you could see sd card issues highlighted at one point or other by mutliple users including devs
[HTC 10 Questions & Answers] hdavid185:
I have the same issue, and now i remember this is the second one in my htc 10, first one a pny 128gb worked well for more than one year in my previos s5 and after a month in my htc it failed, i blame the sd card that day and decide to buy an 128gb lexar and today after 5 months it failed, or i have a very bad luck now or my htc is damaging my sd cards.
[HTC 10 Questions & Answers] BillTheCat:
SanDisk cards have a reputation for being unreliable with many devices. Try a Samsung Evo next and you'll probably have better results.
[HTC 10 Questions & Answers] BartuG:
I had problems with my Sandisk 128gb in the past as well, but usually formatting the SD card once in a while helps, especially if you keep plenty of files it can cause problems eventually.
[Nexus 9 Q&A, Help & Troubleshooting] fkinell:
Hi, In removing Beta N from my Nexus 9 using NRT (which has worked flawlessly with everything b4) I am unable to Flash Stock + Unroot.

The process goes through un-hindered until I get ..

Formatting is not supported for filesystem with type ‘f2fs’

On Reboot I am stuck at the Google Screen and nothing happens!

Either I or the solution to this is “Simple” I am sure.

I appear to have full control over the N9, I can access TWRP I can wipe and format partitions …etc.

Just can’t get the N9 to accept a stock ROM after the Beta N trial (which was becoming unusable anyway)

Please help..

I can post the whole output of WUG NRT.
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
Maybe post in the NRT thread

or

Manually Flash using fastboot, don't forget vendor.img and radio if on lte.

fastboot flash vendor vendor.img

As your going from N version back to stock, a wipe of data partition is recommended.
[Nexus 9 Q&A, Help & Troubleshooting] fkinell:
Hi, Ta for reply - at a total loss here..

Was hoping that NRT would do the biz regards all *.img, as I have never manually flashed (ooooeerr) b4.

I seem to be able to do what ever I desire .. just do not know where to start without NRT (which fails)

I feel I have a lot to learn... and will need to do such.

:crying:
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
[MENTION=7494156]fkinell[/MENTION] Here is more detailed guide.

Stay in thread for more assistance if needed, if I help you by PM, no one else will be able to read the solution if needed.
[Nexus 9 Q&A, Help & Troubleshooting] JMooney5115:
I will need the solution :). I'm in the same boat as OP but I tried to go from rooted M to latest M so I could get N OTA. In NRT I did 'Stock+Unroot.'

The bootloader is Unlocked and I can get into TWRP and fastboot in windows, but when I go into recover I get the laying down android with 'No commands' shown.

I tried 'fastboot flash vendor *.img' but it failed. Where am I going wrong?

Edit: HBOOT 3.48.0.0137

c:\>fastboot devices
H**********5 fastboot

c:\>fastboot flash vendor volantis-ota-mob30g-555f0865.img
target reported max download size of 518205818 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 508793803 is not a multiple of t
he block size 4096
erasing 'vendor'...
OKAY [ 0.422s]
sending sparse 'vendor' (506060 KB)...
error: write_sparse_skip_chunk: don't care size 508793803 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 508793803 is not a multiple of t
he block size 4096
OKAY [ 30.406s]
writing 'vendor'...
(bootloader) Device State : Unlocked
FAILED (remote: image update error)
finished. total time: 31.257s
[Nexus 9 Q&A, Help & Troubleshooting] corkiejp:
First of all you have stock recovery, hold Power and Press vol + to get the menu.

Second you where trying to flash an OTA image to vendor image, which is totally wrong.

Third you can just flash N factory images over what you have already without the need to go through the OTA process, if you joined the Beta Program, you will still get further OTA's if you keep your device stock.

Follow the linked guides exactly above.
[Nexus 9 Q&A, Help & Troubleshooting] fkinell:
My N9 has recovered ! Just fine... using NRT !! Just like always !!

The only thing I did that was different ... was install NRT onto a different PC (laptop actually) .. and I doubt that has anything to do with my success ! (more necessity on my behalf as my PC crashed)

I even got the same F2FS error .... but this time .... it worked!

All I did was blow back the last Nexus 6 MOB30G - nothing ticked, and I did nothing different than I have ever done whilst recovering my tablets using NRT.

So ... I am none the wiser ...

The N9 is asking me to update to the Beta N again ... not a hope !!! About to opt out ASAP.

Thank you for the advice on XDA .. its a relief that there is somewhere to go when stuff like this happens - Ta all.

NB: Just a thought ... in case its pertinent .. My N9 totally ran out of juice.. 0% battery.. I had to recharge it before I could restart NRT stock process.

Out of interest .. my N9 is unlocked, it has been rooted, it has been recovered numerous times before with NRT.
[Nexus 9 Q&A, Help & Troubleshooting] JMooney5115:
It helps when I read. The process is straight forward. Thanks for your help!
[Samsung Gear S2] dhehdwls90:
Hi!

I want Gear S2 usr folder root authority....

1. cmd->c:/tizen-sdk/tools/sdb root on(fail)

How to gear s2 rooting?

Does anybody know?
[Samsung Gear S2] benzso63:
I wanna know too.
[Samsung Gear S2] dhehdwls90:
google search -> Not found ..

plz know way of solution
[G4 Q&A, Help & Troubleshooting] amdev0101:
If you recently had a bootloop issue and recovered it with method from the title you probably experienced the bugs I will name below. I do it to avoid unneeded questions under other posts or adding new threads about the same thing over and over again. So:

-If you reflash the stock kdz of Marshmallow or Lollipop you will get a bootloop again since the cores are disabled ONLY by changes in the firmware and are not permanent.

-Yes your device will run much slower.

-If you can't get the things right it will be too slow. Even though you have disabled only two, after boot actually only one core is awake and the rest 3 are in 'sleep' mode.

-To enable the cores you need to be rooted. To root it simply flash recovery and superSU. Then install Device Manager from the Play Store and by changing frequency turn all the 4 cores on. Doesn't work with Kernel Auditor.

-You can flash custom ROMs still.

-But not stock based - you overwriting firmware hence bootloop again.

-You can flash any CM/AOSP based ROM.

- On customs I found a main bug - You cannot set the screen lock, app just crashes due to some error made by changing the firmware. This applies to ALL of the custom ROMs so DO NOT BLAME DEVELOPERS FOR BRINGING BUGS INTO THE ROMS.

Feel free to add anything more, maybe you have found other vulnerability. Thank you!
[G4 Q&A, Help & Troubleshooting] Hisham alshaeer:
I have same issue but i can't fit it :(
[G4 Q&A, Help & Troubleshooting] elementalfusion:
H815 SEA here, flashed the .tot to disable the main cores multiple times, still bootlooping.

Really regret getting the G4. Already bought 2 refurbished G3s from aliexpress for my wife and myself...
[G4 Q&A, Help & Troubleshooting] arctic02:
I regret purchasing g4 :(
[G4 Q&A, Help & Troubleshooting] amdev0101:
Have you flashed it over LL? Also if you've downgraded it from MM try to factory reset it.
[G4 Q&A, Help & Troubleshooting] amdev0101:
I think every one does, or will do.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Soundtallica:
I'm thinking of picking up a Z5 Compact for my switch to AT&T. But which model should I get?

I already know that the E5823 supports cat 6 LTE while the E5803 only supports cat 4 (which I don't care about) and that both models will work in the US, but I'm more curious on the software update front. Since the E5803 is obviously an older batch, will it get updated less frequently and have less dev support than the E5823? Are mods and roms between the two models different?

I'm only asking since I can get the E5803 for $20-$30 cheaper on Amazon and is eligible for Prime shipping, while the E5823 is more expensive and doesn't have Prime shipping. I'd like to go the cheaper and faster route if possible.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] bigdfmartin:
The 5823 is the International version, the 5803 is the US version. The US version has the fingerprint sensor disabled. You can flash different firmware to get the fingerprint sensor working, I've read. I bought the International version. Works just fine here in South Carolina.

dave
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Soundtallica:
That's weird, the E8503 on Amazon that's cheap claims to be an international version and has no warranty. I'll investigate further. It is tempting to get the US version and enable the fingerprint sensor just for the warranty though. I want a fingerprint sensor, that's the only reason I'm going for the Z5C over something like a Z3 or any other last generation flagship.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] bigdfmartin:
I see the listing you're talking about. Judging from the comments and Q&A, it's not really clear which model it is. If the US warranty is important to you, you may need to make sure you can return it if it is the wrong model. From what I've read about Sony service, though (especially here in the US), you're probably gonna be frustrated if you ever need to use it.

I opted for the International version so that the fingerprint sensor would work right out of the box. I've owned several Sony and Sony-Ericcson phones and never had any problems with them. I've rooted and flashed all of them except for my Z5c because it's already very capable unmodded,, the firmware is still current, and I didn't want to lose the DRM keys.

dave
[Xperia Z5 Compact Q&A, Help & Troubleshooting] civicsr2cool:
I went for the international the day the US version came out as it was cheaper and had fingerprint scanner. Now that we know the only difference between the two is software you should just get whatever is cheapest.