yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Themes and Apps] vinhpz0:
Hi ! I'm using it now and i'm happy :)
[General Questions and Answers] jcampolo:
I received this phone and it would boot to just the HTC screen. It will boot to the bootloader screen and I can access it with fastboot.

The filesystem seems to be locked down and I don't know how to unlock it. ADB won't work since it won't boot the OS. It also wouldn't boot into the stock recovery. When I try to boot into Amon Ra recovery, it shows the progress bar on the upper right side of the screen but then goes on into a boot loop. So parts of Amon Ra are being installed and working but not much.

At first it would boot to the HTC screen and sit there. I installed 605.2 via the PH98IMG.zip on SD method and it went along fine.

Now it just gets to the HTC screen and reboots like it has no or the wrong kernel. I unlocked the bootloader, flashed amon ra and it won't boot into recovery either. I tried to erase several things, it will only let me erase "cache" not "boot", "recovery" or "system. So I'm stuck until I find out how to allow writing to these areas of the system. It also doesn't read the files in light green in boot loader mode like it should.

I think if I can get s-off I can write over what I want, but I don't know how to downgrade or where to find the files. I tried RUU_Vigor_3.14.605.10_PH98IMG but that didn't help, it just gave me an error for trying to downgrade.

I am sure if I can get access to the complete file system I can get this thing going.

C:\ADB>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 2.27.0000

(bootloader) version-baseband: 2.22.10.0801r/2.22.10.0803r

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.03.605.2

(bootloader) serialno: FA28YS208261

(bootloader) imei: 990000652356066

(bootloader) product: vigor

(bootloader) platform: HBOOT-8260

(bootloader) modelid: PH9810000

(bootloader) cidnum: VZW__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 3861mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: ad3368f2

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!
[Galaxy Note II Q&A, Help & Troubleshooting] gorelow:
im on stock. my last 3 phones. touchpro etc were all rooted within minutes of getting them. ive searched for the benefits of rooting this phone. cant really find a list. can i get any opinions on it please? the benefits were obvious with the epic 4 g for instance but just wondering besides the obvious bloatware, if ill see that much difference rooting or not.. thanks aliot
[Galaxy Note II Q&A, Help & Troubleshooting] carlitos66:
Previously I have never rooted my SGS 2 or Note 1st generation model but I rooted Note 2. Reasons: better brightness, louder in call volume. I am very happy with the phone right now. I followed Dr. Ketan guide to root.
[Sprint Samsung Galaxy Note II] eloyho:
Can somebody trying..to make this theme work whit tw base roms for Note 2 sprint . I pay whatever to get my phone work whit this theme som. Work on this it will going to be a hit....

Delicious theme ...

Trust me work on it and you will like it.

Sorry I dont know how to uploaded it but you can find on

GT-N7100 themes thread the name is

Elegant theme is:

147Mb size ...

Pelease somebody read this and work out....

Thanks people my first post ...:D want good news
[Sprint Samsung Galaxy Note II] Skripka:
I presume this is the theme the OP is talking about?

http://xdaforums.com/showthread.php?t=2043767
[Sprint Samsung Galaxy Note II] eloyho:
Sorry it is Verizon note 2 trhead themes.....

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

This is the theme watch it ....and tell me if I was worng ...is A ****ing good job...
[Sprint Samsung Galaxy Note II] vWvSTATICvWv:
Themes have been to a minimal around here because of Aroma...just sayin :)
[Sprint Samsung Galaxy Note II] fryingpan0613:
What does aroma have to do with it? Many here prefer the unthemed roms. That's why my rom is a stock base, even tho I prefer a theme. Themes are a add on in my updater so that everyone wins.
[Sprint Samsung Galaxy Note II] vWvSTATICvWv:
I'm saying that because of Aroma you can pretty much do whatever you like to an extent....therefore, there aren't many devs themeing. If we didn't have the luxury of Aroma, this section would definitely have at least a handful of themes.
[Sprint Samsung Galaxy Note II] fryingpan0613:
That has nothing to do with stand alone themes. 1 developer making a theme aroma installer doesn't stop the entire forums. Joshbeach has his own theme applied to his rom. Sleshepic has his own theme applied. My rom has available themes.

Those who usually make stand alone themes are the ones who don't have there own rom, so they make a universal theme. It wouldn't make sense for the rom creators to make universal themes on top of their rom.

I also believe the community here prevents more themes from being created. Go read a thread like Jellybomb and every page has someone complain about the theme. I assume that's why Sleshepic made a mostly stock themed rom. And that's why my base is mostly stock themed.

I had one member who tried Lab Rats and was bashing it in another rom thread for having a custom boot animation and pull down. What's a rom if there is nothing specific to the rom?

Obviously I'm only speaking on my behalf and my thoughts, not anyone else mentioned in this post.
[Sprint Samsung Galaxy Note II] Skripka:
I'm not sure it is the community preventing anything.

People with chops for, or a desire to learn Android OS building/theming usually go right at making a full ROM rather than a theme for another ROM on the Sprint Note 2. That is just the way this device on Sprint has been. Even folks who are admitted beginners at the dev game, basically have taken a handful of standard patches (4-way reboot/all-apps-in-multi-window/Perseus-Kernel for example) applied them to the latest vanilla deodexed ROM and then themed the snot out of it as a new fll ROM rather than a theme patch....when they could have just themed the snot out of someone else's ROM which already basically had all the patches they wanted. I don't mean to single or look down on any one dev or person's work out in that statement, just to be clear. It is just an observation.

Hence the current situation we have...lots of folks of varying ability all pushing out their own themed TWiz ROMs, all with basically the same patches between them. It is an easy comparison to Ubuntu linux, and the dozens (hundreds rather) of themed clones that Ubuntu has....when people could just make a red theme for Ubuntu, rather than using RemasterSys and cooking an entire new Ubuntu Red themed distro.

Where's the community preventing anything? I mean maybe if devs made thorough documentation on how to theme the TWiz ROM available it would help....but that is more work for devs with lives, and that is still not the community at large's fault.
[Sprint Samsung Galaxy Note II] fryingpan0613:
I guess I could have worded it better. I didnt mean it's the communities fault there is no themes, I just don't believe there had been much of a desire for them. I have seen more anti theming posts then requests for them in general. Then there is the user above that says all we need is the Aroma theme chooser, if everyone is happy with that, then it doesn't encourage others work. I started with helping anothers rom on my last phone.

I have a few people over here that we have taken under our wing to learn, that's what keeps xda alive. I have answered multiple pm's asking for help, and do my best to help them. It's annoying tho when you repeatedly help someone and they don't even Thank you in the op, but that's a different matter.

There are many tutorials available on how to theme, all you have to do is search. While most roms have some of the same features like 4 in 1 reboot, I believe that's because it's considered a must have to most users.

OP could google how to port it, but chooses not to try or failed and didn't get help. Users should be more proactive in my opinion, but only they can choose to.
[Sprint Samsung Galaxy Note II] Skripka:
I hadn't seen the theming guides for TWiz for making a theming patch...then again I hadn't looked.

I think most end-user people are usually against it, as theming is a personal choice and what pleases one person inevitably causes 2 more people's eyes to wince in pain. Hence why (the PITA of keeping) Morphology is a cool thing for those that want a themed TWiz....but on the dev side, keeping all of Morphology working is a PITA like I said. We've been swearing at Morphology and MA7 of late behind the scenes.

Users could be more proactive....but at the same time, there's cost and reward and how many headaches you're willing to go to to just change the color of say the SMS or SPen app.
[Sprint Samsung Galaxy Note II] fryingpan0613:
I doubt there is a guide that will tell you where every file is because tw is such a pain with its naming. I couldn't of the top of my head tell you where a lot is, I tear apart apps and find what I think is it and test it. It's a lot of trial and error.

You can Google big parts of it tho, I have done it myself to find stuff when I was stuck. Maybe I will make a thread with some basic locations like status bar pngs. I don't know how many people would find it useful, but I guess we can see how many people are willing to try stuff on there own.
[Sprint Samsung Galaxy Note II] Skripka:
Well...and as soon as such a database or wiki document or whatever is compiled....the next TWiz update will render all of it obsolete.
[Sprint Samsung Galaxy Note II] shiftr182:
Theming touchwiz is a pita because the roms are all different. My theme is based on stock, and it actually comes from my own rom, but it has taken me many, many hours to get it the way I want it. First you spend a ton of time themeing the stock rom, then devs come out with tweaked roms, and now people want you to go back and tweak you theme for each rom, or add tweaks that are rom specific to your theme, etc. It also seems like samsung/sprint tweak little bits of stuff between each leak/update so everytime something changes there is a resources that change so you have to recompile the whole freaking thing.
[Sprint Samsung Galaxy Note II] fryingpan0613:
Which is why such list will never be complete. That's why I said basic stuff like signal bars, battery, etc that shouldn't change much.

So true. I couldn't imagine making a stand alone theme.
[Sprint Samsung Galaxy Note II] eloyho:
All right ..Aint nowbody got time for that!!!!!

Jesus this is...

People ok and how I can get this Elegant dialer theme on morphology... Cause Morphology dont have it on options

Make more things .....is boring the same thing and thats is boring...:cool:

Aint nowbody got time for that...
[Sprint Samsung Galaxy Note II] slick_rick:
Give me $200 and I'll port that theme for you ;)
[Sprint Samsung Galaxy Note II] SALTY22:
Lol jajajajajajajajajaja you f@@###### crazy bro nice try ass
[Samsung Galaxy Nexus] bluroot:
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.

I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
[Samsung Galaxy Nexus] Soul reaper:
the proper term to use here is bootloop

ur phone bootlooped and u need to flash back the stock firware via odin

go back in the dev section and find somethng relatd to odin

remmbr bfre flashing any rom u shud always backup ur rom via clockworkmod

u must have done something wrng while flashng jellybean mod...take the steps crrctly

EDIT:- http://xdaforums.com/showthread.php?t=1827685

heres the link to fix ur phone

properly take the steps plzz
[Samsung Galaxy Nexus] Garner:
Are u able to boot into CWM recovery, Power and both volume up and down?
[Samsung Galaxy Nexus] bluroot:
When I do, I have that "Downloading..do not turn off the target!" message. Why this - I did remove the supersu file, although I think I left my clockworkmod file on the root because now you have to re-flash that every time you use it. Now I have no option other than "Start" - any chance of breaking through now?
[Samsung Galaxy Nexus] Zepius:
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode

the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.

you really need to do some reading before you start modifying your phone
[Samsung Galaxy Nexus] bluroot:
Do you mean that I need to continually rock the Volume key up and down while holding the Power button? Volume Up with Power put it in boot mode, and when I tried rocking it a couple of times I got the same result. It I understand you correctly, the idea sounds tricky. Is this supposed to work on a Galaxy Nexus?
[Samsung Galaxy Nexus] Zepius:
press and hold both ends of the volume button and the power button... its really not that hard.
[Samsung Galaxy Nexus] bluroot:
What I really should have done was slow down, or quit while I was ahead to get some rest last night! I had researched the root process for my phone ad nauseum, which I know is why I succeeded at getting ClockworkMod safely installed. By the time that was done I was tired, but I counldn't stand the thought of living without my files loaded on my phone - I was in the bad state of needing too much to complete what I had intended to do. I see I had the wrong impression that ClockworkMod would take care of the whole process once I had that working, guess it didn't. When you've been through the process of installing a hundred versions of Windows and Linux on a PC, which never needs to be pre-wiped (the new OS does that), who would have thunk it's that much different with a phone computer?
[Samsung Galaxy Nexus] bananagranola:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
[Samsung Galaxy Nexus] bluroot:
This is another thing I never would have guessed without being told specifically, that it's even possible to hold down both ends of a rocker switch and have it do a different function - I tried this, and now it works! I had used my PC to root my phone last night, and right now I'm at work, where there will be time to go through this in a couple of hours. I took a brief look at the tutorial recommended by Zepius, and am wondering if I am set to proceed. I plan on using my work PC, not the one at home with the drivers I used to root my phone. Nobody else uses it and I have never used it for anything phone-related. Can I presume any drivers which I'm warned should be uninstalled would be on the PC which is used, and not the phone?
[Samsung Galaxy Nexus] bluroot:
Sorry, I had to work, but now there's time and I thought I would try my work PC, which is virgin (so to speak) of mobile devices and drivers. It's a Windows XP system, and right now it's not looking good because when my phone is plugged in, there isn't a "Portable Devices" or "Mobile" category under Device Manager. Do I have a better chance of this working on my home Windows 7 system?
[Samsung Galaxy Nexus] bluroot:
I guess that's a never-mind, I should have had my phone on! It's in Fastboot mode now, but I still don't know if what I see in Device Manager is good for what I'm trying to do. No portable device, phone, nor galaxy nexus, but what did change is I have "Broadcom Nextreme 57xx Gigabit Controller" appearing under "Network Adapters". Is this a problem to be dealt with differently when your phone is bricked?
[Samsung Galaxy Nexus] Zepius:
1) your phone is not bricked. dont call it that

2) best way to check if your drivers are installed correctly

open a command prompt in the folder where your fastboot.exe is and type: fastboot devices

if you get a device ID, your drivers are setup properly for fastboot

3) at this point, just return to stock: http://xdaforums.com/showthread.php?t=1626895
[Samsung Galaxy Nexus] bluroot:
I got a device ID (long string of characters) on that fastboot command, but I'm still concerned that my phone won't talk to Device Manager at all. Windows 7 doesn't pop up a connection window when it's plugged in, should that be expected?

What I mean by "not talking to Device Manager" is that the only item under Portable devices is just E:\ - no device listed here! The tutorial in your signature hinges on there being a device listed "without thde yellow exclamation point", for the installation of new drivers, therefore I don't know how to follow it from here. The adk drivers which were used to root my phone (they were good, the problem began when I tried to flash a rom and missed a step or three) are stil there, but I'll replace them if I can find a process which can talk to my phone in it's present state.

On a side note (and only because it held me up in responding tonight from my Windows system), is this site partial to Firefox? I am able for the first time to login, and I wonder if it isn't because I quit trying to through my Windows 7 system. It has only Windows IE, and Chrome (which couldn't even browse this site). I am currently on my Ubuntu system with Firefox.
[Samsung Galaxy Nexus] Zepius:
good lord... you have a device ID so just use the fastboot commands... start at part D
[Samsung Galaxy Nexus] bluroot:
I said much the same myself.

For the fastboot devices test, I have a string of characters, but no device name, only "fastboot" on the single output line with those characters. Is this a valid device ID?

"...just use fastboot" Ok, but how? Should (can I) even do this use fastboot to transfer files to my phone under it's somewhat anonymous status with Windows? Since last night's fiasco nothing was named under "Portable Devices", only "E:\" was displayed. I have no graphical display in the file manager, so how am I supposed to transfer the necessary files to the root of my phone? I don't even see a way of addressing it to install drivers now.

I will need drivers because I attempted to follow this tutorial (which doesn't account for what I am (not) seeing on my system. I got as far as uninstalling the good drivers which I used last night in favor of what was offered for use with the tutorial, and now Device Manager doesn't even have a Portable Devices category. The "Universal Naked Driver" was to replace my uninstalled drivers, and interestingly the contents of it's expanded folders don't even contain fastboot (the adb package which I used last night did). In light of this, how am I supposed to have even fastboot?

I hate to be a PIA about this, but I guess I'm more a n00b than was presumed in this tutorial - it's either that or my situation really is too different that I can use it as is. Could I please get a few clues in light of what the tutorial doesn't address? Do I have any means of installing anything and transferring files with my device-PC communications as they are, and if so how can I do it? I'll give it a run if I understand how.

Thanks.
[Samsung Galaxy Nexus] bluroot:
I see now that Part D calls for flashing JO03C from my PC, not the device root, ok.

Also, after rebooting my laptop, the E:\ is back under Portable Devices in Device Manager. When I double-click this I get the statement

Device: Portable Devices

Manufacturer: Generic-

Location: on UMBus Enumerator

I don't think this looks better than the Microsoft default, but is it good enough for what I need to do?

I still have the driver package android-sdk-windows, which contains adb and fastboot, so perhaps I should just use this according to Part D and see what happens?
[Samsung Galaxy Nexus] Garner:
Seriously I respect the fact that your a noob we was all here once :p but if it your device is boot-looping all you need to do is the above ;)
[Samsung Galaxy Nexus] bluroot:
Good god, I never should have read Zepius's tutorial - I didn't need my PC at all! If I understood what bananagranola had said, I could have saved a lot of time!
[Samsung Galaxy Nexus] bluroot:
Oh, no, now I can't connect with the server!

Could I have possibly lost my radio from what I did earlier? I was able to boot up, and I was upgraded to 4.2.1 when I did the data wipe. Starting over, I should have had a prompt to connect with gmail and download my contacts, but this didn't happen. My People app is unpopulated, so I chose to connect to "sign into an account". While I am sure of my login input, it didn't recognize this, and then the process ended with a "couldn't finish - couldn't open connection with the server" error. Any clue where to go from here?

Some standard apps are missing too, including the Play Store app!
[HTC Inspire 4G] vvvikranth:
Hi

I have unlocked the bootloader using htc-dev unlock as there is no aahk. i followed the link tau.shadowchild.nl/attn1/?p=88[/url] and i have done upto step 4. after that i tried installing cwm and it fails. after reeboting my phone its on stock firmware 2.3.5 and sense3.0. i want to flash a custom rom onto this device. can u people help me when i tried to enter into hboot mode the top of my inspire 4g screen says bootloader - relocked. What to do now. How to flash cwm into it and install custom roms.

Thanks in Advance.
[HTC Inspire 4G] bananagranola:
Why are you following that guide? It is for preparing an Inspire 4G with the latest update for AAHK, which no longer exists.

You cannot flash CWM unless you re-unlock your bootloader; you can't flash anything when the bootloader is locked.
[HTC Inspire 4G] vvvikranth:
How to re-unlock my boot loader.
[HTC Inspire 4G] glevitan:
using the same unlock_code.bin as before:

Plug the phone with usb debugging enabled.

Open a cmd as admin and type adb reboot-bootloader.

When in fastboot usb (you should read that in the phone) navigate to where the unlock_code.bin file is in.

Type fastboot flash unlocktoken unlock_code.bin

Voilá...you are done.

If you don't have the unlock_code.bin, then get another token from phone the same way as you did before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mook111:
I am a complete Android noob so pardon me beforehand. I have a rooted ATT Galaxy S3. I recently flashed 2 CM 10.1 nightly builds. I wasn't happy with the performance of the ROMs and want to reset my phone to stock rom ( default out of the box ICS Touchwiz UX). What ROM file do I need to download and what method to use to restore/flash (TWRP, Odin, etc.) I have read countless threads on this but still have not understood how to go about doing this, so don't blame me about spam. Thanks for all your help! :)