yashsingh1/xdaforums huggingface dataset:
[Galaxy S6 Q&A, Help & Troubleshooting] MrManH:
Hey guys,

I currently have a Tmobile Galaxy S6 updated to the latest 5.1.1 release (OTA).

I'm trying to figure out the steps in flashing the XtreStoLite Deo-Mod Edition 2.1 ROM.

The instructions for flashing the ROM say to begin by rooting using cf-autoroot. Looking at the cf-autoroot thread, people say that cf-autoroot won't work and cause problems when already running on 5.1.1 which I am.

Would the following work:

-Odin TWRP to phone

-using TWRP, flash XtreStoLite Deo-Mod Edition 2.1 ROM (comes with unikernel)

-using TWRP, flash latest version of unikernel

Taking those steps, would the following be achieved:

-root

-deep sleep

-functional fingerprint scanner

I've been doing a lot of reading but the information is scattered and it would be of great help knowing if this is the right order of doing things.

Thanks!
[Sony Xperia P, U, Sola, Go] odintheterrible:
Greetings,

Does anyone have a link to a download for the USB driver for the ST27i please ???

Thanks
[Nexus 9 Q&A, Help & Troubleshooting] cdkg:
I know it's got a tegra chipset, but what about the modem/radio?
[One (M7) Q&A, Help & Troubleshooting] scirto:
Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):

HBOOT 1.56

S-ON

Bootloader unlocked

TWRP v2.8.7.0 installed

SuperSU BETA 2.94

Android 4.1.2

Software 1.26.502.15

I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an

adb backup

(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an

adb restore

to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.

Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.

Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.

I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)

At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.

And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://xdaforums.com/showthread.php?t=2545227 via Flashify and seeing if that works.

If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...:eek:
[One (M7) Q&A, Help & Troubleshooting] scirto:
Ignore my last paragraph. I completely misread what that file was providing (stock recovery, duh, of course that's what it's providing. Not what I need).
[One (M7) Q&A, Help & Troubleshooting] scirto:
Also, if this helps:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.56.0000

(bootloader) version-baseband: 4T.24.3218.09

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.18.502.7

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HT344W907896

(bootloader) imei: 354439054277373

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 3849mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-c6bbb6d4

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.

You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed ;)

The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/

Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.

fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader

Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.

Then you can take OTA updates safely before unlocking your bootloader again :good:

Sent from my M7 ARHD 84-Kitkat
[One (M7) Q&A, Help & Troubleshooting] scirto:
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.

So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.

Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?

Anyways, more to come shortly...

EDIT: I will also note that my last attempt with an RUU was with my phone starting on the home screen. Not sure if starting in bootloader/fastboot is better or worse or makes no difference? I'll try that too
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
The problem is because your s-on. The way firmware is flashed is very strict with s-on.

You must Relock the bootloader.

You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.

You can only flash a signed ruu or firmware that is the same as your current version or one update above.

So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.

The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes ;)
[One (M7) Q&A, Help & Troubleshooting] alray:
deleted
[One (M7) Q&A, Help & Troubleshooting] scirto:
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!

Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.

Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good: :)

Sent from my M7 ARHD 84-Kitkat
[One (M7) Q&A, Help & Troubleshooting] scirto:
Exactly... Might be the software developer in me, but I feel a huge sense of relief as long as I start to see something different happening. OTA is downloading, no root is detected, so the process should complete successfully. Major kudos to you, my friend.
[One (M7) Q&A, Help & Troubleshooting] scirto:
So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!! :D:D:D:D:D:D
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Your Welcome. Enjoy
[YotaPhone] adamo86:
help after installing the stock modded recovery i used twrp to flash xposed it ran for a few days all well.today my epd froze so i restarted device but the epd is still frozen and the front screen is blue its in a boot loop.
[YotaPhone] recallrules:
Did u fix it?
[YotaPhone] adamo86:
Yes
[YotaPhone] recallrules:
can u share the file ?? i have got the phone back !1

regards
[Fascinate General] Ophidian_DarkCore:
thanks to xc-racer99, humberos, and the beautiful vmware.... no wait, f#ck you vmware.

In the coming days, there will be builds of omnirom 5.1 coming out. I just finished my windows 10 install and I'm deciding how to setup my build OS for the future.

Pics or gtfo? Ok, http://i.imgur.com/XrkWPuQh.jpg

Cya guys. For early testing, harass hhp

Cheers to whoever is still here.
[Fascinate General] skepticmisfit:
OMG

you guys are legends. i had a fascinate a while ago, but i come back to troll here. and whattya know.

if i still had my fassy i'd totes mcgotes test this for you guys. but great job, it's nice to see someone still cares.
[Fascinate General] Ophidian_DarkCore:
I have two fassys your getting my dev one after I declare these builds stable. You aren't getting my extended battery one with 64gig sd. No, that's my baby.

hhp also has two fassys.

and the reason for this development is because I absolutely adore the WM8994. this phone is like a toyota supra to me.

and that this is the original galaxy s, which went from rfs to ext4, bml to mtd, linux 2.6 to 3.0.101(Someday 3.4 ;), and now to f2fs and lp gives it sentimental value to me aside from the audio. http://xdaforums.com/showthread.php?t=1288093 http://xdaforums.com/showthread.php?t=1233273 http://xdaforums.com/showthread.php?t=956349 http://project-voodoo.org/history Supercurio is right up there with NWavguy for me. Equipped with chainfire3d I used to adore this little thing. Oh the nostalgia. but I digress, off to listen to some flacs :p while this source finishes syncing. Hope to see you around.
[Fascinate General] skepticmisfit:
dude please don't send me a fassy lol

im a teenager and my parents would get worried

and yea the fascinate was always a kickass little music player device, but i'm not the biggest audiophile in the world and Qualcomm's DAC does the trick for me just as well as the Wolfson dac in the fascinate did. lol
[Fascinate General] Ophidian_DarkCore:
That made me giggle a little too much. LOL

I'm a teen too, I just tell my parents to **** off. They know I work on 'stupid' stuff. :rolleyes:
[Fascinate General] skepticmisfit:
were you part of the lollipop port for the fassy? or are you just a close bystander?
[Fascinate General] Ophidian_DarkCore:
aries kernel and aries-common was already updated. the only work that needed to be done was to bringup the device tree. i provided the files to xc racer and helped him with partitions. then i tested the build and showed him what needed to be fixed. he is responsible for the bringup, i'm responsible for debugging, and humberos did the kernel. several people did aries-common. i'm now going to be the maintainer for this device. and will be responsible for improving performance, compatibility, and doing bug fixes. the kernel still needs a lot of work.

EDIT: and hhp was my tester and will remain so.
[Fascinate General] adinatale978:
New to everything here

Hello everyone, I am new to this website as well as flashing and ROMs. Could someone help me get started on how to flash this lollipop onto a Samsung Mesmerize? (US Cellular version of Fascinate)
[Fascinate General] alaneddy:
1) Update recovery to newest TWRP or CWM Touch.

2) Reboot to recovery

3) Factory reset

4) Wipe cache/dalvik cache

5) Install CM12.1 (for your device)(dont reboot when done)

6) Install GAPPS (for your version it's open gapps 5.1, google it)

7) Reboot when finished.

8) Wait for 1st boot to finish.

9) Enjoy!

Edit: This is assuming you have already downloaded all necessary files and have them copied to your SD Card.
[Fascinate General] pcwizzy37:
My fascinate is my best dev device I have! My only other dev device is my LG Lucid, but it is very buggy and I can't get binary blobs or even compile for it. My other devices have locked bootloaders, that's no fun.

FYI, Ubuntu 14.04 with LXDE desktop environment is probably the best dev environment, because Unity just takes too much power!
[Fascinate General] Ophidian_DarkCore:
bbqlinux, check it out mayne
[Fascinate General] alaneddy:
nice :)
[Fascinate General] pcwizzy37:
Hey, I hate Windows Vista, 8, 8.1 and 10. get ubuntu 14.04 with LXDE.
[Fascinate General] Ophidian_DarkCore:
screw off with that. i have arch on my p4 box. i'll let you see my kernel later hehe. ubuntu even with lxde would make me puke. i sont even have a mouse plugged in. tty1

p.s. windows 10 pro makes me happy. uefi bios updater. alpha drivers for everything. all 'paid' version software. vmware ws pro puts out enough power for me to make every now and then builds ok. i grew up on xp.

as you can tell though, im a rolling release type of guy. anything less is unacceptable.
[JAMin, XDA Neo, S200 ROM Development] davidebeatrice:
...to be or not to be?

there will be a touch version of this rom or not? I don't understand if or not...:)
[JAMin, XDA Neo, S200 ROM Development] story:
why do you make another thread, there are two threads talking about it
[JAMin, XDA Neo, S200 ROM Development] jincongz:
no there isn't, there's .0.5 and .0.5a, but no touch thread
[JAMin, XDA Neo, S200 ROM Development] davidebeatrice:
exactly!:) :)
[JAMin, XDA Neo, S200 ROM Development] jincongz:
and so we're waiting, Shooter said within the week, maybe
[JAMin, XDA Neo, S200 ROM Development] cpc:
Pls. Pls. implement TouchFlo on this ROM!!!!
[JAMin, XDA Neo, S200 ROM Development] jincongz:
Here's your answer...

Taken from here: http://xdaforums.com/showpost.php?p=1366718&postcount=32
[JAMin, XDA Neo, S200 ROM Development] ahcal:
Hope the new PDAViet 4.0.0.0.5 Touch will not have not have any bug and run smoothly on our Prophet. I did a search on the specification of all the Prophet. It seems that HTC Touch uses the same processer, same memory size and same size LCD screen. Lets look on the bright side and support PDAViet on their ROM cooking :)
[JAMin, XDA Neo, S200 ROM Development] Mogi:
yeah hope that they remove the wmp & replace it using htc audio manager & using tcpmp as the default video player.
[JAMin, XDA Neo, S200 ROM Development] yoda_143:
I like WMP, because it syncs perfectly with WMP11 on my desktop PC. HTC audio manager also doesn't support playlists as far as I know.
[JAMin, XDA Neo, S200 ROM Development] jincongz:
Yes it does...

But I still like WMP more than TCPMP...
[JAMin, XDA Neo, S200 ROM Development] orian:
Audio Manager sorts albums by track title... nuff said

Stupidest implementation of playing an album ever!
[JAMin, XDA Neo, S200 ROM Development] yoda_143:
But wasn't there a problem with HTC audio manager playing songs on an album in the correct order?

*EDIT:

That's exactly what I meant.
[JAMin, XDA Neo, S200 ROM Development] bankir:
Why not create a playlist in Audio Manager? I think Audio Manager is great!. Or perhaps you can do a SHUFFLE??
[JAMin, XDA Neo, S200 ROM Development] davidebeatrice:
now gullum rom it's the best form me...but when 4.0.0.0.5 touch will be released? so I can test this rom too...:)
[JAMin, XDA Neo, S200 ROM Development] davidebeatrice:
nothing?:)
[JAMin, XDA Neo, S200 ROM Development] davidebeatrice:
but touch version r.i.p.?:(

no news...:( :(
[JAMin, XDA Neo, S200 ROM Development] gullum:
There is something about the toucj version on pdaviet side but I don't read vietnamise so I don't know. there are some screenshots but no download link
[JAMin, XDA Neo, S200 ROM Development] davidebeatrice:
me too...:(
[JAMin, XDA Neo, S200 ROM Development] Cloudyfa:
PhamQuang uploading it, you should wait 1 or 2 hours to get the link.

P/s: This version is cooked from 4.0.0.0.5a by PhamQuang. I'm too busy to release my version now. Maybe i'll release it in 1 or 2 weeks!
[JAMin, XDA Neo, S200 ROM Development] davidebeatrice:
great!!!!:D

and always waiting for your always gret roms!!!!:)
[JAMin, XDA Neo, S200 ROM Development] kespir:
Rom 4.0.0.0.5 Touch

ROM 4.0.0.0.5 TOUCH

Download Link

Password: PDAVIET

New Rom --> New Thread
[JAMin, XDA Neo, S200 ROM Development] davidebeatrice:
thanks!!! :):):)
[JAMin, XDA Neo, S200 ROM Development] Kaoh:
It doesnt add much over the .5 Cross version except pool size.

So Cloudyfa we really want yours with the cube ;)
[Fire TV Q&A, Help & Troubleshooting] Organized_Chaos:
I bought a refurbished AFTV from Amazon. According to the serial number, this thing shipped with a rootable version of software. I have no way of knowing if Amazon has updated the software or if it's been sitting in a warehouse for months and still has old software installed. So I want to register it without doing the update, just in case.

I blocked three domains in my router that I found on AFTVnews. I can edit those in later when I get to a computer. I start up the AFTV, pair the remote, select my network, and enter my credentials. It doesn't error out on me, it just sits on the screen where it says it's registering my account. it never progresses past that point.

Any ideas?
[Fire TV Q&A, Help & Troubleshooting] {ParanoiA}:
Yea you have to block them with opendns and use your router set to opendns dns server. Its free and easy to do. It will get you past that screen to check your software version
[Fire TV Q&A, Help & Troubleshooting] realtuxen:
check the atfvnews page it has several methods. best way i figure is this: http://www.aftvnews.com/start/

it will take you all the way step by step, and quickly give you a definite answer.

if you unblock Amazon’s update domains.. basically it seems like you can do something like this in most cases (but not all!) with a wired connection (read it all through properly on aftvnews first)!:

quote:

"If you purchased your Fire TV from somewhere else or if you just factory reset your Fire TV, you will need to enter your Amazon account information. With the internet still disconnected, enter your email address and password. Reconnect the Fire TV’s internet connection, wait for the light to turn white, and then click sign in. As soon as it signs in, a welcome video will start. Disconnect the Fire TV’s internet connection as soon as the video starts."

---------- Post added at 11:19 PM ---------- Previous post was at 10:51 PM ----------

sorry about the edit i missread you.
[Galaxy S6 Q&A, Help & Troubleshooting] DanialAt:
I am having a serious problem with my Galaxy S6. The keyboard and any pop up menu for selection are not visible. I can see the keyboard and any selection menu when I rotate the screen then it vanishes very quickly.

I have disabled keyboard, cleared data and cache then restarted but it doesn't seem to work.

I have wiped all the cache partition, done a factory reset, flashed a stock 5.1.1 but the problem still exists. I would really appreciate any help or tip to get this fixed.

Thanksgiving
[Galaxy S6 Q&A, Help & Troubleshooting] roydok:
Try downloading a 3rd party keyboard from Playstore.
[Kindle Fire Q&A, Help & Troubleshooting] NizzleFish98:
I was wondering if anyone could help me with a situation I'm having with my Kindle Fire 1st Gen. I was in the middle of the flashing TWRP process when all of a sudden fastboot commands weren't working. I followed some steps (likely incorrectly) to get fastboot commands working and now the device won't do anything but sit at the Kindle Fire boot screen forever. I cannot get into fastboot, adb, or any utilities and am this close to smashing it into a brick wall. Is there any hope or help anyone could offer? Thanks in advance to anyone that can assist me!
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
Power off, connect to wall charger

What does it do?
[Kindle Fire Q&A, Help & Troubleshooting] NizzleFish98:
It powers on into the incessant Kindle FIre boot logo and stays there forever.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
Animated boot logo or static?

Does it Lite up then dim slightly?

Or no change.
[Kindle Fire Q&A, Help & Troubleshooting] NizzleFish98:
Static Logo and it looks like it just stays lit for the entire time.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
That should be fastboot mode.

Did use install.drivers.bat from Kindle Fire Utility v0.9.9?
[Kindle Fire Q&A, Help & Troubleshooting] NizzleFish98:
I have them installed but I can't exactly figure out how to apply them to the KF.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
Just run the install.drivers.bat in windows, and reboot

Kindle Fire should be listed as Android adb interface in Device manager.

---------- Post added at 06:47 PM ---------- Previous post was at 06:46 PM ----------

Did you watch my video

[6.3.3] Flashing FFF and TWRP without Fastboot Cable
[Kindle Fire Q&A, Help & Troubleshooting] NizzleFish98:
Every time I plug in my Kindle nothing shows up in the Device Manager. I plug it in and it says Windows does not recognize the device. I will watch the video now.

Not plugged in (Pic 1), Plugged in (Pic 2)
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
Likely bootloader is borked, but could just be drivers were not installed correctly.

In Device manager>select unknown device or device with a yellow triangle>Update driver software>

browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>

show all(uncheck show only compatible)>look for ADB interface or android phone

select yes to Ignore warning

may need to reboot both.﻿

[IMG="Kindle Drivers"]http://tapatalk.imageshack.com/v2/15/02/20/ecf4e5b2f40a0f7a9fa9c41c5cbf0fea.jpg[/IMG]
[Kindle Fire Q&A, Help & Troubleshooting] NizzleFish98:
I think it's just about unfixable. Couldn't even find any ADB drivers or anything remotely close. I hugely appreciate all of your help. TIme to find a hammer.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
If you couldn't find the drivers, that's a Windows problem.

Which windows version?