yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] crushalot:
This thread will show you how to extract the master rom.zip from the RUU.exe

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

After you have done that it should be a zip that you can open and pull out the parts you need.
[Sprint HTC One (M7)] bleichtman:
Hey there. New to the one and was wondering if there were any cm10 roms that can be flashed with s-on
[Sprint HTC One (M7)] coal686:
As far as I understand it, any ROM can be flashed s-on without issue on the One (caveat below). It's different than the 3D. But the revone method of s-off is super easy so it's worth doing (see my web signature for a link). Also, from my understanding, some people have bricked their Ones trying to flash AOSP ROMs. I think s-off people have better luck with it.
[Sprint HTC One (M7)] bleichtman:
Hearing the word brick doesn't make it seem worth it. Thanks man. That being said, which roms seem to be the most stable for the sprint one?
[Sprint HTC One (M7)] coal686:
The Sense ones. I use the Team 420 one, but I'm biased. The Team D3rp one is really good too. I haven't tried any others though so try others and find your favorite.
[Sprint HTC One (M7)] Knixson:
The Two That I know of and have done my self are Viper and cyanogenmod. I have not take the step to s off yet as I am very new to this and am learning before I do just as you described (Brick my phone). You can easily find these two ROMs here on this site.

ViperROM v1.1.0

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

CyangenMod

http://download.cyanogenmod.org/?type=nightly&device=m7spr

and that is where I got the ones I used as well.

It does matter which carrier you have as I made that mistake and was in bootloop which you dont want to do.

For information on that see this thread:

http://xdaforums.com/showthread.php?t=2353956
[Sprint HTC One (M7)] sauprankul:
FWIW I was one of the people who got bricked, and I and some others helped to compile a list of victims. The last brick was on 6/29 after which the kernel was really overhauled.

Most (including me) are calling the bug squashed.
[Sprint HTC One (M7)] coal686:
Good to know. I've thought I had heard the same, but wasn't sure.
[Sprint HTC One (M7)] bleichtman:
Thanks for all the info guys.
[Sprint HTC One (M7)] Knixson:
Also here is a good Link I found

http://xdaforums.com/showthread.php?t=2338613
[Sprint HTC One (M7)] Logain38:
Bricking a phone would def suck! but i was under the impression, and maybe im wrong, that there is usually a way to fix it. Again im no pro but i kind of jumped into the whole rooting thing without knowing ANYTHING about it on my 3D and never seemed to mess it up more than having to flash a new RUU at worst. anyway i really love the IllusionRom. but cant seem to get google wallet to work, which is kind of a bummer. but i also really love Sense 5, and dont mind using stock one bit. I suggest going for it and checking everything out, more than likely you'll be fine. best of luck
[Sprint HTC One (M7)] sauprankul:
A brick can never be recovered. It must be replaced. A BORK can pretty much always be fixed via ADB.

Also, I heard there was a workaround for the wallet issue. Just search it up. It has something to do with the build . prop.
[Sprint HTC One (M7)] Rirere:
Or if not ADB, judicious use of fastboot and RUU. I cut my teeth on a Samsung Galaxy Player 4.0, and after a three-month long recovery process, nothing the HTC One can pull is likely to faze me anymore.

Anyway, there are certain devices that can be recovered from a low-level brick (assuming by brick we're saying a device is completely non-responsive to input, hardware and software wise) but it's pretty involved at the best of times.
[Android Q&A, Help & Troubleshooting] Amphibian59:
First off, I am no expert so please be gentle! I previously rooted my old Samsung Galaxy S i9000 and installed ICS, which went OK, but the phone became quite slow and unstable. I was advised to install RemICS and downloaded all the zip files from this forum, and put them on the external SD card. I followed the developer's instructions to the letter, as well as reading everything I could find on the subject. The reset and data wiping went fine, but the installation of the ROM didn't. It halted with an error message -`ROM incompatible, trying to use an invalid partition'. I repeat that this is supposed to be the specific ROM for the i9000. The phone now won't boot into recovery. It stops with an orange Android logo and the text `Powered by Mackay Kernel'. It won't boot into download mode either. The Mackay screen stays there however long I leave it. I really need help from the ROM developer but I can't post to that forum. How can I either boot into recovery or into download mode? Is this ROM reliable? What could I have done wrong?
[Android Q&A, Help & Troubleshooting] Amphibian59:
More info:

Presumably everyone is on holiday! But just in case anyone is reading, there is further news. The reason I could not start recovery mode was that the button sequence was different from what I had been told. It now boots reliably into Mackay (which of course is TWRP). I have found that the phone is unable to mount the partitions DATA and SYSTEM - they seem to be corrupted. Hence it has not wiped DATA, although TWRP wrongly reports success. I have tried updating the partitions to ext3 or ext4 but this fails every time. I could format the thing from Windows but that will wipe everything including recovery of course. I need a tool to repair these partitions, but have not found anything so far. This may well have been the reason the phone was getting creaky in the first place.

I have copied a new ROM to the external SD card, using a card reader, and inserted this into the phone. Strangely the TWRP file manager reports that EXTERNAL SD is a sub-folder of SD CARD, and that is empty. The file manager does not show the real external SD card. But the real external SD shows up on the Windows USB connection. What is going on?

When I try to mount the partitions, DATA and SYSTEM can't be checked - the other partitions (Cache, sdcard, and emmc are all checked).
[Android Q&A, Help & Troubleshooting] Amphibian59:
kingGrn Copeland

Well for the benefit of anyone else with the same problem, I have managed to re-flash the ROM back to stock. It just took 3 days of intensive web browsing until I understood how to do it, and found software that worked - a lot of stuff out there has errors.

To summarise, the problem was:

1. Data and System partitions became damaged, so phone became unstable.

2. Attempt to upgrade ROM failed because of damaged partitions.

3. Could not boot phone into recovery or download because button combination was different from what I was told.

The solution was:

4. Boot into download mode using correct button combination.

5. Re-flash back to stock ROM and re-partition using Odin.

Yes, someone did tell me that, and I would have done that straight away if I could have gotten into download mode. We live and learn
[Android Q&A, Help & Troubleshooting] neteagle86:
Thanks this wa useful for me too.
[Galaxy S 4 Q&A, Help & Troubleshooting] lax_22:
I've read some reviews on the s view cover which say that once you flip it open it will bypass your lockscreen (if you don't have a passcode/gesture lock) and go straight to your homescreen.

Does the same thing happen if you have widgetlocker installed? I'd prefer it to go to my lockscreen when I open the case and don't want to shell out for one if that's not what happens.
[Galaxy S 4 Q&A, Help & Troubleshooting] worf9910:
Yes it will:D

But you can change this under the root section of widget locker
[Galaxy S 4 Q&A, Help & Troubleshooting] lax_22:
Bibuto sons

Thank you! So I would need to root the phone to make this work?
[Galaxy S 4 Q&A, Help & Troubleshooting] negrobembon:
no root needed, it doesnt bypass widgetlocker as far as i know

i have widgetlocker installed and everytime i open the sview it opens i widgetlocker
[T-Mobile Samsung Galaxy S 4] damond:
i was looking to fix unkown baseband on my phone i flash it with baseband file using odin but no luck, after i flash with stock fimware and modem and then root the phone with cfroot and then i try restoring efs folder, idecide to restore it back to stock fimware and pull the battery out to put phone in download mode but it wont power on only appear as Qdloader 9008
[T-Mobile Samsung Galaxy S 4] AxAtAx:
What device are we talking about, and what modem did you flash?
[T-Mobile Samsung Galaxy S 4] damond:
t-mobile m919 i flash the modem from http://xdaforums.com/showthread.php?t=2282342
[T-Mobile Samsung Galaxy S 4] Biker1:
Hi. It's a little difficult to follow you with the run on sentences, so let me start with the basics.

I'm not sure what you have installed on your phone at the moment regarding Firmware, modem and ROM.

If you can power up and look in Settings, you can tell me. If not, follow these steps:

- download the following Samsung Stock Firmware, if you have not done so already.

http://samsung-updates.com/device/?id=SGH-M919&details=Galaxy_S_4_T-MOBILE

- verify the MD5 Checksum to see you have a match.

- open up ODIN on your pc.

- place device in ODIN mode, connect via usb cable (make sure the cable is a good cable) and that ODIN 'Com' recognizes device.

- place the Samsung tar md5 file in the PDA box.

- check Auto reboot & time reset (I forgot what it exactly says) boxes.

- press Start and wait till install completes, and S4 Reboots.

See how that goes.

The above will get you back to stock, then you can install custom recovery and root afterward if you want.

Use Triangle Away if you want to reset your counter, but you must be stock and rooted to do so. Usually resetting counter is not necessary unless you are sending your device back for warranty, etc.
[T-Mobile Samsung Galaxy S 4] damond:
odin not reconizing the phone , the com port appears as Qualcom HS- USB QDLoader 9008
[T-Mobile Samsung Galaxy S 4] qbanlinxx:
If it won't turn on, your gonna have to send it in for service. Same thing happened to me last month, the replaced the pcm board I believe on mine
[T-Mobile Samsung Galaxy S 4] Biker1:
I came across this thread:

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

While it is not about your device, the discussion in the linked thread is about an issue that may be similar to yours. You can read it to see if there is a relationship.

I've read all 4 pages.

There is a file below:

QHSUSB

Which I think you need to find for your device. I believe it is a Driver that you are missing. If this is what you need, you need the correct driver. I'm uncertain if the file linked in page 4 is the one you need. But googling QHSUSB and bricked Samsung S4, etc. may help you.

Again, I think the above may set you down the right path to help with your issues, but I'm not 100% certain, but I'm just researching to try to help you out.

This may avoid you having to jtag your device, but again, research the above, and see where it leads.

Edit:

Just in case it's needed.

http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair/

You may also want to read this to get a better idea of what your issue probably is:

https://developer.qualcomm.com/comment/6221#comment-6221
[T-Mobile Samsung Galaxy S 4] damond:
well it seems to be my solution is jtag, so im going to order a jtag
[T-Mobile Samsung Galaxy S 4] Biker1:
You'll have it back before you know it ;)
[T-Mobile Samsung Galaxy S 4] qbanlinxx:
Does the device turn on at all? Mine was hard bricked, and Samsung fixed mine without issues
[T-Mobile Samsung Galaxy S 4] maxshah912:
Don't order J Tag call Samsung tell them your S4 is not turning off they will send u shipping label on your email ship phone in 4 business days u will get your phone back. It happen to me 3 times 2 on my S3 by flashing wrong roms by my brother. and s4 for modem
[T-Mobile Samsung Galaxy S 4] damond:
i allready fix the phone using jtag, but i found this software if anyone have this issue they can try with this
[Nook HD, HD+ Q&A, Help & Troubleshooting] MonaLisaOverdrive:
Having just spent the last few days reading, downloading, returning and cursing, and finally getting CM10.1 running on my NOOK HD from sdcard...working on a Windows 7 laptop...I thought I'd write up a few quick tips from my (limited) experience. Hopefully someone will find these helpful.

One

To get ADB working correctly...which you'll want to do...get the usb_driver_r04-windows.zip from the NOOK developer's site by following the instructions here. Connect the NOOK to your workstation first and let the OS try to detect and install the drivers. When it fails, open Device Manager, and look for the MTP device, which will have a warning icon next to it. Right-click it, click 'Update driver...' and use the "browse my computer" option for driver software, and use the location where you unzipped the drivers that you downloaded.

Install Java and the Android SDK. Instructions for what to download and how to install are here for Java, and here for the Android SDK. You can ignore the steps for configuring the PATH variable for Java, however you'll want to configure your PATH for the /tools and /platform-tools directories in the Android SDK. You can do this via the GUI but using cmd is easier: Open a cmd prompt as administrator, and type path /? for instructions

After adding the path, add the device ID to the adb_usb.ini file using the instructions here.

After adding the device ID, make sure ADB access is enabled on the NOOK using the instructions here, then verify connectivity by using the instructions here. Run adb kill-server, then disconnect your NOOK

Two

Burn the CWM image file to an sdcard (4GB or greater) using win32diskimager . The CWM image file is found in this thread. Key note: all CWM and CM files for the NOOK HD will have the -hummingbird prepend. You can also download the CM-10.1 image and appropriate gapps version for CM from this thread. Do so.

Pop the sdcard into the NOOK HD and reboot. Once the CWM menu appears, connect the NOOK to your laptop. Windows 7 will not see the device, so you will need to re-install the drivers. Open device manager, look for a device in the list called Barnes and Noble HD (or similar) with a warning icon nearby, right click, select 'Update drivers...', choose the 'Search for driver software on my computer' option and navigate back to the folder where you unzipped the drivers. You will be using the SAME drivers that you downloaded initially.

Once driver install is complete, mount the sdcard using the menu options in CWM. Push the CM-10.1 zip file and gapps.zip file you downloaded to the sdcard using the command adb push <filename> /sdcard.

Install the CM10-1 file first, using the CWM menu options. Reboot the device using the CWM menu after installing CM before installing gapps. According to the instructions in this thread, you don't have to, however, with the three installs I've done so far, for the two that have worked successfully I've rebooted before installing gapps.

That's it. Hopefully these tips will help someone else with a NOOK HD.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] mattbunce:
Does the Orange SPV M2000 come with an upto date rom / bluetooth version? Or is there an update available?

What would you recommened doing to an M2000 out the box? Upgrade bluetooth etc.
[Vibrant Android Development] driodmaster92:
Quote:

Illusion is BACK!!! We'd like to give HUGE credits to SLIM Roms for an incredible base! We'd also like to give credit to AOKP, Paranoid Android, TeamBaked, CyanogenMod. These people helped make what you guys are using (about to use) what it is today .

VIDEO REVIEW:

Nyone on the fence about flashing watch this IllusionRom Review

FEATURES:

Dark UI

Permissions Management

LCD Density Settings

Illusion Settings & ROM Control:

Per-App Permissions Manager

Dual Pane

Low Battery Warning

cLock

Custom Hardware Keys

Widgets Viewpager

Notification Drawer Options

Power sound on plug-in/plug-out

Custom Lockscreen Sliders & Shortcuts

Navbar Customizations

PIE Controls

Power Menu Controls

Power Widget Settings

Custom QuickSettings

Custom Statusbar Options

Custom Sounds Settings

Custom Phone Settings

Custom MMS Settings

Integrated Superuser

Trebuchet

......Much more in detail

For Downloads/changelogs visit here​

Please help me justify all my time spent on building these roms by considering a small donation​
[Vibrant Android Development] driodmaster92:
one for me
[Vibrant Android Development] driodmaster92:
one more for me
[Vibrant Android Development] skinzy98:
First!!! Let me know if you need any help!
[Vibrant Android Development] driodmaster92:
Test and report back
[Vibrant Android Development] skinzy98:
2.1 drops tomorrow for Samsung devices
[Vibrant Android Development] driodmaster92:
could not get you???
[Vibrant Android Development] skinzy98:
Hmmm? The Facebook page for illusion roms says Samsung devices tomorrow. I know it's not official I'm just excited to see where illusion goes. By the way just flashed. No problems yet. Keep up the good work
[Vibrant Android Development] driodmaster92:
Oh that's for the s4 and s3 devices my builds are not included there
[Vibrant Android Development] shree_tejas:
Downloading now :D

Edit: It would be great if you actually linked the download link to the post containing the rom rather than directly to your blog home page. Just a headsup :)
[Vibrant Android Development] samsgun357:
I don't see a DL for vibe in the link

Edit* nm I found it, had to put it in desktop mode
[Vibrant Android Development] edwin270:
Love the looks already, based on slim...the only Rom my phone prefers using.....makes yours Rock.

Can't wait to flash and start using right away.
[Vibrant Android Development] skinzy98:
Yes it is quite amazing :rolleyes:
[Vibrant Android Development] samsgun357:
This ROM is running solid! I haven't had much time to test but just scrolling through it is really smooth. Thanks for keeping the vibe alive.

Lies, spewed poetically from galaxy S3!
[Vibrant Android Development] shree_tejas:
Any ways I can change the colour of halo circle? Looks like freaking rangoli :D

And I don't know if its a ROM specific thing but where do I control the animations? Not the launcher... Other ones. Its just random. If it can be set to a single one it would be great ( but that's a personal opinion :) )
[Vibrant Android Development] driodmaster92:
Setting>>developer options
[Vibrant Android Development] edwin270:
Love you Rom but found a few things that will need fixing.

1. The battery icon does not show the charging icon on the status bar (that is when charging), though it can be seen in the tile.

2. Gallery does not show previous images already captured prior to flashing this new Rom.

3.stored ringtones and notification does not also show in sounds settings unlike the base Rom you used(slim beans).

Other than what stated above, loving the speed and looks.

Thanks.
[Vibrant Android Development] shree_tejas:
Is it me or does the xposed thing work for everyone??

i tried a basic battery mod and even after rebooting like crazy... nothing changes. :(
[Vibrant Android Development] edwin270:
Was the app settings in the xposed installer activated?
[Vibrant Android Development] Hobbesfed:
Battery icon shows up for me. I tried out all of the battery icons just to make sure (I was using the stock android icon before though). They all show up as charging. Gallery images show up for me too; I took pictures with SuperNexus ROM and RemICS-JB ROM back who knows when and they all show up. Dunno about the last one, though that can be easily remedied. Just download File Manager by Rhythm Software and next time you select ringtones, it'll ask you to choose between that and the system ringtones. You can easily find all of your stored ringtones using that.

And yes, I agree, this ROM is really awesome. :good:
[Vibrant Android Development] Cooptx:
I am using this ROM on my SGS4G and my Vibrant.

The battery icon doesn't show charging on both devices using the default setting, if you change it to any other read out like the circle with percentage, it will show you that it is charging.

I didn't experience the other two issues. This ROM is nice and smooth I really enjoy the KeyLimePie theme that comes with it :)
[Vibrant Android Development] edwin270:
Good to know that, but want to believe that due to some of this things, that is why this is still in beta, some things will work for some and not for others.on the other hand whatsapp is also not functioning well, the contacts on the phone is not showing.works perfect in other roms.
[Vibrant Android Development] driodmaster92:
Whatsapp working fine for me...anyways yeah there are some issues we are working hard to sort them out...
[Vibrant Android Development] Cooptx:
Contacts work, you just have to try again. Most of the time, on the second attempt that contacts will show
[Vibrant Android Development] edwin270:
Managed to solve the problem.Thanks.
[Vibrant Android Development] fire6water:
I just wanted to say this is a great and stable ROM. The customizations are amazing and battery life is great. Keep it up dev and can't wait to see how this progresses. No issues so far.
[Vibrant Android Development] testomat:
How to solve your contact problem ? My google contacts did'nt synchronize.

GMail always crashing. How to solve it ? But using K9 Mail works.

I had Baseband Unknown Problem. Solved it. I deleted the init.d scripts and then it works after reboot.
[Vibrant Android Development] driodmaster92:
flash slim gapps add on and fix permission
[Vibrant Android Development] testomat:
I reflashed gapps. Synchronization works now, but Gmail still crashed
[Vibrant Android Development] phonephixer:
Everything seems to work perfectly for me so far. After about two days of usage things do get a little laggy. Love the ROM over all. Best i've tried so far. Transitions are beautiful! More people need to show more love to the dev.
[Vibrant Android Development] driodmaster92:
Okay Guys got the 4.3 to boot up ,I know we are a little late to the party ...still...BTW no PA PIE and Hybrid for now...Next version Hybrid ...got halo and ribbons right now...and a new theme...its in alpha stage right now...

KeyLimePie theme will be hosted on Google Docs, along with a new theme called KeyLimePurple lol (i think).
[Vibrant Android Development] skinzy98:
Congratulations on being the first to get 4.3 to boot on vibrant (I think)
[Vibrant Android Development] driodmaster92:
Oops no...I booted this up on my device I9000, I was under the impression Derteuful fixed it...Sorry you people may have to wait
[Vibrant Android Development] skinzy98:
Yeah it hasn't been fixed yet as derteufel is on vacation right now
[Vibrant Android Development] driodmaster92:
Hello Everyone....

I think everyone here knows that we have been working hard to get the ROM up...Finally its up ...running fine and awesome for me here on I9000 and on mako for Andreas....You must also know that we have a team of high quality developers and maintainers ....just a themer is missing from our team .......Stay tuned for more updates .....or visit our IllusionRoms G+ Community Here
[Vibrant Android Development] skinzy98:
You guys have updated all the source?
[Vibrant Android Development] driodmaster92:
Yeah we are doing
[Verizon Samsung Galaxy S III] ayush20m:
When using the original touchwiz ROM the S3 has an inbuilt capability to work as a DLNA server. But after the upgrade to some ROMs like cyanogemmod that function is gone. Does anyone have alternate solution for it. I was looking at an app PixelDMS. Anything better?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mkfryan:
Came from sprint and their policy on rooting was they will support the hardware not software even with root what is AT&T policy for rooted devices?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
Short and sweet: they won't support it. I've never heard them make that distinction. Wish they would but its easy to flash back to show as if it never was
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mkfryan:
Ya it's almost stupid it's so simple just wanted to know if they had a stance one way or another thanks for the input