yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] Vader™:
Newbie question,

how to unroot if i rooting the phone using this metode?

and how to go back to original rom?
[G2 and Desire Z Android Development] Aegishua:
Firstly, to root the phone just follow the steps and once you've finished them all you will be done.

Second, it should technically be possible once you've rooted the phone to simply do a NANDROID backup via ClockWorkMod Recovery before you start flashing new ROMs. If you have backed it up and later decide you want to unroot then all you would need to do from there is restore your nandroid backup and unroot the phone through this method.

Using this method you don't have to worry about your CID. If you make a goldcard it will completely bypass the need for one of the CID's listed in the first post. So to put it simply, you don't need to worry about your unique CID if you create and use a goldcard to downgrade.
[G2 and Desire Z Android Development] Vader™:
okay, but we need to root the device first right? before ClockWorkMod Recovery can run, the problem is, if I root the device first, the device must be downgrade to build 1.34.405.5, and now my Desire Z using build 1.82.xxx.x

is it if we backup via ClockWorkMod, the ROM that we backup is 1.34.405.5? not my current build?

please help bro, really confused here :D
[G2 and Desire Z Android Development] jmpcrx:
Hi forceonature, im no expert, but when i was having a look myself, i found out it was simply my enviroment variables wernt set up for the directory fastboot was located.. an easy way round this was just to enter the directory fastboot was in (program files, 'some directory'.. do a quick search) within your command prompt, and type the second command from there.. hope that helps..
[G2 and Desire Z Android Development] riahc3:
Everything goes fine until

mmap() failed. Operation not permitted

when I put in

adb shell /data/local/tmp/psneuter

Any help?
[G2 and Desire Z Android Development] riahc3:
Also I can only put su and Superuser.apk on my sdcard if I manually transfer them.
[G2 and Desire Z Android Development] chevy2410:
I tried the same thing to get my DZ phones CID and the first one worked and the second didn't. If I don't have to make a gold card all the better. How can I find out for sure if my CID is on the list or not? Also if I have to make a gold card do I need to have a micro SD card to make the gold card?

Thanks,

Chevy
[G2 and Desire Z Android Development] Aegishua:
You should get a line that says INFOt.cid=XXXXXXXX or any of the lines that say your 8 Digit CID. However, as you can see there are multiple lines that say it and they should all be the same.

If your CID does match one on that list then you will not need a goldcard.

I've attached a screenshot to make things easier.

Yeah, you can only have a NANDroid backup of 1.34.xxx because there is no way to get clockwork onto a 1.72+ rom.
[G2 and Desire Z Android Development] Shauli20:
Hi, I'm new to rooting the G2. Iv'e been trying to follow this tutorial, but I'm having some trouble. After renaming Rom.zip to PC10IMG.zip I booted into the bootloader and it says 'no image found' or something like that. What am I doing wrong? Am I not supposed to put the zip file on the root of the SD card? Is it possible to just use the RUU to downgrade?

And regarding the downgrade, the build number on my G2 shows 1.22 . Isn't that lower than 1.34?

Any help is appreciated!
[G2 and Desire Z Android Development] PlinXoom:
I followed the instructions twice and both times I get to

"/data/local/tmp/misc_version –s 1.33.405.5"

I get

/

Patching and backing up partition 17

Error opening backup file.

#

The first time around I iqnored it and went through hboot, the rom PC10IMG.zip was checked and verified and finally failed prompting "the main version is older"

what am I missing?

EDIT: checked SD card, unmount and remounted phone/sdcard no avail.

Will try 1.33 Bell rom next.

EDIT2: Patching and backing up sucessful, problem was I couldn't get my phone to stay in debugged mode without being in DISK DRIVE, had to start HTC Sync to mount the phone in that way to relieve the sd card, allowing adb to patch the file. Now running through PC10IMG.zip with fingers crossed.

EDIT3: Everything went smooth after that! Thanks. Now I will attempt to update to 2.3 and Sense 3.0

EDIT4: Now running on 2.3.3 and Sense 3.0 Virtuous port. Testing...probably going back to more stable gingerbread and sense 2.1
[Desire Q&A, Help & Troubleshooting] lawrrtan:
Guys! Which Gingersense ROM is the best one as of the moment? AuraxTremeGinger 8.5, Leedroid V3.0.4, or Reflex 1.9?
[Desire Q&A, Help & Troubleshooting] Meaple:
Try them all and see for yourself.

Sent from CM7
[Desire Q&A, Help & Troubleshooting] COOLBGT:
Edit: Delete
[Thunderbolt General] jcstahl1:
anyone else try this and getting an error about the app only being available to active verizon customers?
[Thunderbolt General] otto888:
Getting it here... hope it gets cracked... also getting maintenance message on My Verizon....
[Thunderbolt General] ncwildcat:
Check the Tesla coil thread under the development section...there is an apk that you can install to fix this

sent from my personal space
[Thunderbolt General] otto888:
Does not help at all.
[Thunderbolt General] ncwildcat:
Worked fine for me...Copy it to system/app, restart, fix permissions, and click the file to install.....

Next time maybe post what you did, not that it didn't work..
[Thunderbolt General] remmbermytitans:
I'm using CM7 Test4 on my Thunderbolt and I really want to use my NFL Mobile App, how can I get it to work?
[Thunderbolt General] hendeeze:
Has anyone figured out how to fix this? Its the only thing keeping me from using CM7.

I'm not entirely sure what file the previous post is mentioning, And I have tried both the VZW files located in http://xdaforums.com/showthread.php?t=1138759 as well as the VzqSigSSOEngine.apk but still havent gotten to work successfully. Thanks
[Thunderbolt General] remmbermytitans:
Can we bring this thread back? The NFL is back and I would really like this to work on my Thunderbolt. I'm using CM7.
[Thunderbolt General] nrfitchett4:
droidtheory has a senseless rom that has working nfl mobile. Watching it right now.
[Thunderbolt General] remmbermytitans:
I wonder if he has any tips for making it work on CM7. Does he have some method to send him a message?
[Thunderbolt General] nrfitchett4:
I don't think cm7 has the verizon sso engine apk that nfl mobile needs. Try this one:

http://xdaforums.com/showpost.php?p=14621388&postcount=22
[Thunderbolt General] remmbermytitans:
Doesn't work for me. Does it need a fresh install?
[Thunderbolt General] Turb0wned:
Try this one. I don't have a thunderbolt anymore but it worked for me when I did. Flash this in cmw.

http://xdaforums.com/showthread.php?t=1189360
[Thunderbolt General] bill102938:
This really blows :mad:

Can anyone confirm that they've gotten the NFL mobile app to function on CM7 RC1.3 or RC1.4?

I've tried two different versions of the SSO client to no avail.
[Thunderbolt General] remmbermytitans:
I can confirm that this does NOT work on RC 1.4. :(
[Thunderbolt General] ViperZ28:
I went as far as restoring my BAMF nandroid backup where NFL Mobile is working, copying NFL Mobile, Verizon Single SignOn and MyVerizon. I loaded those into CM7 and the same result. I have been trying to look into the code but I am stuck now as I cannot decompile the lua files which are located in NFL Mobile app.
[Thunderbolt General] idkwhothatis123:
Yeah the mobiauth.lua file is what needs to be edited but I can't find anything anywhere on how to decompile it. Its not even reading the build.prop though because I replaced the entire build prop with bamfs and no dice.
[Thunderbolt General] ViperZ28:
Seems we need a decompiler for Lua 5.2, I cannot find one yet.
[Thunderbolt General] ViperZ28:
I see in the file it requires core-3.12, does anyone know what that is and how to check it?
[Thunderbolt General] appleju:
I sure hope this gets fixed by September. Otherwise I will be forced back into sense and bamf for my NFL mobile...
[Thunderbolt General] sgtguthrie:
Agreed, I need my NFL mobile :-)
[Thunderbolt General] lrs421:
I've been back on a sense based stripped rom since the lockout ended, lol.
[Thunderbolt General] remmbermytitans:
SAME HERE. I love CM7, but if it can't have NFL Mobile, it may require me to move to back to Sense. Someone please help us out!
[Thunderbolt General] CBMC:
I notice that the app has been updated. I am getting a different error now, but still can't open it.
[Thunderbolt General] lrs421:
I was just about to ask if anyone tried the updated version. Too bad, believe it or not the NFL app is one of the reasons I switched to Verizon. I'll continue to run a stripped sense rom, not so bad I guess.
[Thunderbolt General] H4zyBuddha:
Now the NFL app requires a Verizon login account, but at least its working

Sent from a smoke filled room
[Thunderbolt General] CBMC:
You were able to get it to work on cm7? I am getting "this service is temporarily unavailable".
[Thunderbolt General] Powell730:
Still nothing on this? Mine tells me the content is only viewable to active verizon users then only allows me to hit exit.
[Thunderbolt General] MrHawaii:
Lol I know you!
[Thunderbolt General] nrfitchett4:
Y'all might try this:

http://xdaforums.com/showpost.php?p=16568610&postcount=61
[Thunderbolt General] stmcmurray:
NFL mobile app WORKING on CM7

For anyone who hasn't got it working yet. Follow the link in the quote. It works great.
[Thunderbolt General] stmcmurray:
I retract my previous statement, it was working last night, but not this morning.
[Thunderbolt General] lrs421:
That's what happens when the log in expires.
[Thunderbolt General] Haz Esco:
nfl mobile needs to work like asap
[Thunderbolt General] unexpected62:
any update on this? I'm gonna want to use CM7 on my D3 when it comes out but I'll want NFL Mobile as well.
[Thunderbolt General] tarigand:
has anyone got this to work yet?
[Thunderbolt General] jerrycycle:
No, there is nothing new on getting this to work. Boot manager or flash a working sense rom to view.
[Thunderbolt General] jackdubl:
Now that the Galaxy Nexus is finally coming out, what are the chances we finally get this to work on AOSP?
[Thunderbolt General] orcsbane13:
Still a waiting game. As of right now NFL mobile doesn't work on the galaxy nexus either.
[Thunderbolt General] jackdubl:
No, but My Verizon does work. Therefore, whatever the app needs to be able to sign in and verify a Verizon customer is most likely already on the phone. I doubt there is anything in the NFL mobile apk itself that has anything to do with getting it working on AOSP. My guess is we could get it working right now.
[Eee Pad Transformer General] jcarrz1:
I have both input and questions.

First question, directed mostly to the devs who've started this and the average transformer owner's impression of what's going on:

What do you see the future of this tablet being? do you see it as very successful with a lot of roms, or do you see it as something that slides by with not much more dev than modified stock roms?

I will update this post with information for people interested in buying the Transformer and explicitly interested in development as soon as there is new information.

Another set of points:

I've seen people ask several questions in this forum, and i've congregated these ideas and some of my own.

CyanogenMod (with enhancements from the viewsonic Gslate)

Ubuntu

Multi-booting off SD or 16g main partition

Other roms from other tablets (as cool device-manufacturer software overlays come out)

AOSP for development (honeycomb of course, google has to release source :P)

KERNELS KERNELS KERNELS (i can see already that this is the strongpoint in XOOM development insofar)

I will update this list as necessary.

Thanks for reading. This thread will hopefully become a congregation of information for people who WANT TO BE DEVELOPERS and are considering BUYING THIS DEVICE. I want this Tablet to be as good as a platform as my G1 has been (it's still hoppin' in there :P), and what i've seen spring up on devices like the Galaxy S line (2 of those devices here), and with the xoom already.

Thanks.

I will be responsible and be updating this thread. I may imitate RoyalKnight's Rom Bible in this thread (cf. G1 or MT3GS DEV)

I also have interest in becoming a Transformer Mod, let me know if that's available (of course i want to buy the thing first) lol.

Paul at MoDaCo has one. This is good. :) Also no offense to BadWolve1, I didn't know there was already a Mod for this section, i'll leave the above up for timesake.
[Eee Pad Transformer General] Badwolve1:
Theres a long list ;)

I'll leave this in Dev, as it does contain Development info.

Badwolve1
[XPERIA X8 General] andrasandhi:
hi everyone.

i think everyone in this forum must be know how about 'our' AndroidOS.

thankz....
[XPERIA X8 General] chewdaniel:
look around google there are a lot of sites that do 2.2 vs 2.3 reviews, etc. 3.0 is an entirely diff ballgame altogether. those are meant for tablets but of course u can find info on that too
[XPERIA X8 General] MrCzAjNiK:
HONEYCOMB is unreal at this moment for X8. There is only alpha version on it.

PL: Na x8 MiniCM (2.2.1) działa najlepiej. 2.3.3 ma za dużo bógów, a mini już jest w wersji 1.0
[XPERIA X8 General] mati96PL:
Minicm - nie działa aparat poprawnie.

Na nexus rom v2 masz Wszystko działające poprawnie.
[XPERIA X8 General] proadi96:
Mam pytanko :)

Jak instaaluje minicm rc 1 to normalnie sie instaluje alle jak robie reboota to dochodzi do logo se i reboot i tak w kolko .... co zrobic xD
[XPERIA X8 General] andrasandhi:
I guess you dont understand what I mean. This isnt about the ROM!!

I mean, what is the excess of Froyo version, or the advantages of the version of Gingerbread. f.e, eclair version doesn't support app2sd, but Froyo version already support. and so forth.
[Nook Color Q&A, Help & Troubleshooting] ewhac:
I sort of did myself in with a perfect storm of derp, but I'm hoping I can still recover...

My NookColor is -- or rather, was -- a rooted v1.1.0 system (AutoNooter'd). I last picked up my NookColor a couple of days ago. During that interval, it downloaded and applied the 1.2 system update.

As it happens, I had an SD card installed that I was using for other things, but which also contained the old AutoNooter tools for rooting a 1.0.1 system. So the 1.2 update was applied, the system rebooted, and the AutoNooter started applying patches for a 1.0.1 system. The result was a machine that wouldn't get past the 'n' logo.

Since there was nothing important on the machine, I decided to wipe it and restore it to default using the 8-reboot trick. But... Surprise! I had installed ClockworkMod 3.0.0.5 earlier (as part of applying the rooted 1.1 update), and it was now taking control of the restore process. I used it to format both /system and /data, in the hope that the regular boot process would notice they were blank and do a restore from /rom (or wherever). But no, that didn't work. And CWM has no option to mount /rom and attempt restores from there.

I tried downloading the 1.2 update ZIP file from B&N's site, copying it to an SD card, and using CWM to install it, but CWM refused, claiming it couldn't open the file (the error message was simply, "(bad)"). I tried using 'zip -F' to repair the ZIP file, but it still wouldn't work.

So, I'm now officially stuck. Can anyone point me to resources on how to get my NookColor back into working order?
[Nook Color Q&A, Help & Troubleshooting] ewhac:
Hmm. This thread appears to describe how to do a full restore to 1.0.1, complete with links to SD card images. This falls under the "good enough" category, so I'll be trying that shortly (just as soon as I can find a usable uSD card).

But feel free to chime in with additional suggestions.
[Nook Color Q&A, Help & Troubleshooting] chrislj:
Create a new CWR 3.0.0.5+ sd card. Get hold of the 1.01 restore and 1.2 update. Copy 1.01 to the CWR sd and boot it up. Do a wipe on the nook using CWR. I think it's system and data under the mount and restore menu. Then run the 1.01 restore and reboot. Do all the registering and such. Then attach to usb and drop the 1.2 update into the "nook color" drive that pops up. It will update shortly and you should be up and running again with 1.2 again.
[Nook Color Q&A, Help & Troubleshooting] chrislj:
Sorry if that is kind of thrown together. I don't give very good directions. lol
[Galaxy Tab General] BeauGiles:
Following on from the announcement that Vodafone AU is testing Gingerbread on the Galaxy Tab, looks like Optus is also testing it on the Galaxy Tab.

Only a matter of time people. :-)

@Optus
[Galaxy Tab General] natious:
So its out, i wonder why it hasnt been leaked yet, either way, ill just wait for a proper cm now
[Galaxy Tab General] DarkPal:
Cant anyone try to get it leaked from those operators lol. Told my bro in australia to try :D
[Galaxy Tab General] ssserpentine:
Yeah, i am excited. But it does make you wonder why this hot item hasnt been leaked yet.
[Galaxy Tab General] Aspi914:
I would hope that Telstra are doing the same thing !!!!!
[Galaxy Tab General] guildamx:
I don't think se are talking about a fake news. Vodafone Australia is also reported to be testing gingerbread on the tab.
[Galaxy Tab General] DarkPal:
A call to our fellow australian tabbers. IF you get Gingerbread send some our way pleaaaaaase :D
[Galaxy Tab General] BozaBonanza:
I'll be sure to upload it when I get my hands on it! :D
[Galaxy Tab General] DarkPal:
Australian tabbers asked vodafone on twitter. They said they are still testing for 2.3 once that changes they will post.
[Galaxy Tab General] grukko:
I read on another forum whose name I can't remember now that an Optus rep said it would be out mid-May for what it's worth.
[Galaxy Tab General] wackymix:
still in testing GINGERBREAD

Your right
[Galaxy Tab General] Aspi914:
Looks like Telstra's a no....

Might have to look at rooting the Tab and loading up an overseas version of 2.3.3. Asked Telstra a simple question, got a simple answer - NO...

:mad:
[Galaxy Tab General] natious:
Telstra are fools and don't know anything, I wouldn't hold my breath waiting for any sort of update from them

swyped from a galaxy far far away...
[Galaxy Tab General] tigersman1000:
Still no update from Optus on the Galaxy S! C'mon guys :(
[Galaxy Tab General] bricked_tab:
I know I'm quoting an old post, but I'd like to try again to flash my tab with whatever's better out there. I've had it with the wifi dropping out - it's been 6 months now geez. If I hadn't stupidly bricked it the first time I wouldn't have this problem anymore. Now where to start....
[Galaxy Tab General] wakey74:
Does anyone have any updates on Optus pushing gingerbread out to the Galaxy tab. KIES is still not showing anything. If not what ROm should I go to if the last one Optus pushed out was P100XXJMA which looks to be the European one according to the list at the start of this thread
[8525, TyTN, MDA Vario II, JasJam General] adrianomoutinho:
I am wondering if it is possible to configure my hermes to wake up from sleep using the touch screen.

After the phone went to sleep, by pressing the power button for example, I could just touch the device to wake it up. I don't think pocket dial is such a big deal, I could use a lock screen to prevent that.

Only solution I found is to configure windows not to turn the device off. But I think the battery will drain faster if the device can't go to sleep mode.

Any thoughts?
[EVO Shift 4G General] derik123derik123:
alright, so I was wondering why when I use smart keyboard pro keyboard if I enable physical keyboard corrections that my *period* key stops working?

Every other key works, just not the period key?

would there be a way to remap it or is that strictly a app issue?

Cause its only when I use smartkeyboard pro

Thanks
[EVO Shift 4G General] derik123derik123:
Bump!!!! Anyone know?
[EVO Shift 4G General] nativ73:
fn + .com won't work with either, if I remember right I had the same problem with better keyboard before I switched to skb.
[EVO Shift 4G General] derik123derik123:
what's skb? Is it better or on par to smart keyboard pro?

Is there anyway to fix smart keyboard pro period?
[Droid Incredible Q&A, Help & Troubleshooting] jetcitydevices:
I've been hunting around and haven't found any good information on this so I thought I'd ask.

I have an HTC Droid Incredible with an SLCD in it and the screen has cracked. Unfortunately, the SLCD seems to no longer be available in the market (I've looked everywhere). All I can find are the Samsung AMOLED versions.

So here's my question: Is there any way to root the Incredible (originally designed for the SLCD) and get it to work with the AMOLED version of the LCD?

I'm thinking no but I thought if the connectors are identical, then maybe new software would allow me to run a different LCD in the phone.

Thanks.
[Droid Incredible Q&A, Help & Troubleshooting] konker:
I've a set with broken screen too.

How can I tell if it's SLCD or AMOLED?

I'm also looking for a replacement screen.

The label on the back of the screen has this numbers:

P/N: 60H00291-00P
[Droid Incredible Q&A, Help & Troubleshooting] k_nivesout:
If you can see the screen well enough to navigate to settings>about phone, if the hardware version is 002 its amoled, 003 is slcd.
[Droid Incredible Q&A, Help & Troubleshooting] jetcitydevices:
Sorry to be a pain about this but I'm not asking how to tell the difference between the parts. There's tons of posts about that (from looking at the hardware version, to the part numbers on the back, to walking into a dark room and turning the phone on).

The question here is: Can you root a DInc that shipped with a Sony LCD and get it to work with a new Samsung LCD (AMOLED version)?

Thanks.
[Droid Incredible Q&A, Help & Troubleshooting] taustin52:
I don't think anyone has ever tried it. I'm not an expert, and i have never attempted to do what you are doing, but it seems like it could work. Actually i'm thinking you wouldn't even have to root the phone, can't you just grab the most recent RUU file and restore the phone from that? The most recent would have to include both AMOLED and SLCD drivers in it? Is a root required to restore from a RUU file? I have never done it haha. Also you would have to check if the connectors are the same, i think chances are good that they are the same though. Anyway, good luck and keep us updated as to whether it worked or not.
[Droid Incredible Q&A, Help & Troubleshooting] smith2martin:
any update?

Hey JetCity,

Same issue as you, can't find the S-LCD anywhere. Did you have any luck swapping out for the AMOLED?

Thanks.

Martin
[Droid Incredible Q&A, Help & Troubleshooting] ACD168:
I cna't imagine it would be an issue, set your phone to the most recent stock RUU and then install the new AMOLED screen. id be very surprised if it didnt work.
[Droid Incredible Q&A, Help & Troubleshooting] Amphibliam:
I wouldn't rely on that. It used to say 002, then I flashed GB and it said 003. Really weird. I'm sure mine is AMOLED.
[Droid Incredible Q&A, Help & Troubleshooting] synaptyc:
Did anyone ever get this to work?

I have an Incredible with a cracked SLCD, but I have a spare/working AMOLED from a parts Dinc. Can someone point me to a RUU to download that might have both drivers so I can possible use my spare LCD?
[Droid Incredible Q&A, Help & Troubleshooting] loonatik78:
step aside from for the hardware geek

No driver in the world is going to help you make an AMOLED work with an SLCD. You're problem is hardware on the board. The drive electronics for the SLCD and AMOLED are different. One very notable difference in the electronics would be no provision to drive a back light on an AMOLED.

As for finding SLCD and AMOLED screens, I've looked and they're out there. I haven't looked into this, but the hardware inside the Nexus One is nearly identical to the dInc and that screen may work in it.