yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] Meola:
Ok so I have been trying to mess around with my S3 for the last few days, I just converted over after 6 years of using iOS products and have absolutely no knowledge of Android at all, most of the info I can find that pertains to my device is limited to very basic instructions that make no sense to me having no droid background, I tried following information from other devices and that didn't change any of my issues. I have rooted the phone successfully and with no issues; however my next step of installing a custom rom has had me hit a brick wall.

I have gotten as far as installing the rom onto my phone (CM10) yes I was trying to use the proper d2att version of the nightly updates, most current one. I have CWM running fine, created a nandroid backup, booted back to stock, wiped all the cache's, wiped the phone. But any time I try to install the rom it gives me some BS status 7 error, which from all the searching I did came back with an issue of it not being the correct rom for my phone. But according to everything blasted on this site and on CM's site my phone (Rogers GS3) uses all the d2att stuff, thats what I used to root my phone and as mentioned that went flawlessly, 10 minutes maybe. Big thanks to the people here that put the Toolkit package together.

If it makes any difference I was trying to install via CWM via the install from zip on SD

Terribly sorry if this is the wrong spot for this but its been three hours of horrible frustration on something that people do in a 6 minute video on YouTube, followed one to the word and still had this status 7 error.

TL;DR - Help a converted apple noob with his perpetual status 7 error from hell!
[Sprint Samsung Galaxy S III] epic4GEE:
First thing, you posted in the sprint section :) and as for status7 error I want to say you have a bad download, try downloading it again.
[Sprint Samsung Galaxy S III] Meola:
Ah crap! Thats what I get for going on a flurrey of cross board reading, could have sworn I was still in the AT&T section, probably wait a day or two for a new download or possibly try and older version. Thanks for the heads up.
[Sprint Samsung Galaxy S III] Xontic:
Won't hurt to try an older version, or another ROM to make sure your phone runs that ATT coding properly. If a different/older ROM works, then I would chalk it up under the bad download/bad update for that ROM and wait for the next increment. As long as you have the Nandroid (without getting crazy) you should be free to explore different things.
[Nexus 7 Q&A, Help & Troubleshooting] luvmybacon:
updated the jellybean to 4.1.2 using the clear-data-method-in-GOOGLE-SERVICES-FRAMEWORK

My N7 is not rooted

I am now unable to surf internet using my company's wifi network. Was previously able to log on & surf before the update.

I am able to connect to the wifi network but the icon remains greyed out. I cant get on the internet.

I get prompted to log-in the network - which is the logon page for the administration of the router Dlink 660[or something] -> which i dont have authority to do so.

Company running wpa/wpa2 psk type with mixed 802.11 n & g settings on the router

I have NO problems with wifi at home.

Have tried :

1) Tried using static instead of DHCP in wifi settings, but still no go

2) Nothing wrong the the settings of the DATE/Time

3) Deleting & re-adding Google account

Am at a loss what to do. Please - any assistance for my problem.
[Nexus 7 Q&A, Help & Troubleshooting] Billchen0014:
Your company like my school have a desperate login page. You need to open a browser and type your user name and password. Clear the browsers data and cache before doing this.
[Android Q&A, Help & Troubleshooting] mdky:
Hello,everyone.I've got a Sprint optik(zte v55) 7" pad coming with HC 3.2.

After I flash a modified kernel, Its usb debugging mode can't work properly and my pc can't recgonize it.

Before I flash the kernel, when I switched to usb debugging mode and connect to my pc(runing win7), v55 will display a icon in taskbar showing it's connected with pc, my pc will show a new driver that showing the dirs and files in v55's internal storage, and when I run command "adb devices", it will show v55 is connected.

now, all the above is not happening anymore.

Can anybody know what should I do now ? My intention is to root and flash CM10 to v55,and can be recongize by my pc again.

The kernel I flashed into is in http://xdaforums.com/showthread.php?t=1473555,kernel #60 for v55.
[Android Q&A, Help & Troubleshooting] wildstang83:
Hi, here are some things to keep in mind when using adb.

Be sure of the command you are issuing

Insure you are in fact cd'd to wherever on your pc the adb binary is located

Insure your jdk is included in your path on your pc

To make things easier you can always also add the tools and platform-tools folder of the android sdk to your path

Lets make sure you are properly set up first before you start flashing things randomly.

For more info, you should check Android's page on ADB if you would like. http://developer.android.com/tools/help/adb.html

I'm not sure if any of this is actually directly related to your issue, but it is nice to start with the basics.
[Android Q&A, Help & Troubleshooting] mdky:
Thank you for reply.

The adb command I use is install by v55's driver.Everytime I use adb, I always go into the driver's dir (C:\Program Files\ZTE Tablet V55 USB Driver) which adb.exe is in.

And this dir is in my path.

The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?

Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.

when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
[Android Q&A, Help & Troubleshooting] wildstang83:
Ooook now we're getting somewhere, I think :)

Make sure when you send your fastboot flash command you send it like so:

fastboot flash recovery recovery.img

Replace 'recovery.img' with the actual name of the img, whatever it is.

Also if you are getting the device offline error try killing server:

adb kill-server

and then restart it

adb start-server

See if that helps.
[Android Q&A, Help & Troubleshooting] mdky:
I will try these command when I get home, thank u!:good:
[Android Q&A, Help & Troubleshooting] mdky:
"adb kill-server" and "adb start-server" works fine.They turn v55's "adb devices" from "offline" to "recovery".

And I run command "adb reboot-bootloader", it seems that v55 is in bootload mode.

But after that,I run command "fastboot flash recovery CWMrecovery.img",it returns '<waiting for device>' and stuck there.

Before I flash the kernel #60, I can run "fastboot boot CWMrecovery.img" to boot to cwm,so I think it's not likely be the driver's problem,am I right?
[Android Q&A, Help & Troubleshooting] wildstang83:
Sorry to take so long to reply. I think it is not a driver issue. Do you know if debugging/adb is even enabled in the ramdisk? This generally would have to be done by the dev who created the kernel. Speaking of that, have you tried to contact that dev for further support? For sure they would know more than me since I don't own the device myself. I just know enough to be slightly dangerous, lol :cool:
[Android Q&A, Help & Troubleshooting] mdky:
It's very nice of you to keep help me here ,thanks again:good:!

After keep trying in past two days, I found that in ftm mode adb is enabled, and 'adb reboot bootloader' truly made the device into bootloader mode.

On my win7 pc, It can't be recognized.I switch to my old xp pc,and install the driver come from other zte user,and then...fastboot works.

Now I have the v55 running CM10,Awesome!Thanks to all contributors.

Still, my win7 pc and xp pc can't recognize my v55 through usb.But it's not big deal now.I can use tf and wifi and other ways to transfer file to v55.
[Android Q&A, Help & Troubleshooting] wildstang83:
Oh wow, that is quite the ordeal, but atleast its something huh, lol

I wonder if you could run adb and fastboot commands in xp mode on your win7 pc?

I know there is a way to run programs in XP mode, its just been awhile since I've done it.

And its no problem to keep trying to help, even if I don't know the device and all that. Maybe I can learn to while we are at it, and maybe make a new friend along the way :)
[Samsung Galaxy Nexus] jimmyco2008:
...As for the poll, it's pretty pointless, if a mod happens by, please remove it! No need to worry about bricking (for obvious reasons), and the lack of radio support is no excuse, just battery pull and reboot to get back to Android.... No reason to wait till someone else does it, I just did it!...So go for it!

-----------------------------------------------

Re-Booting Open WebOS after doing it once before!

Now reboot your GalNex to the bootloader (you know how to do that)

./adb reboot-bootloader ...or just power off and hold vol up + vol down + power.

Okay here's where the official guide will really **** you up... The file isn't called what the guide states it's called, at least for me...

Type (don't copy and paste this one either):

sudo fastboot boot *click and drag whatever file is closest to "zImage-tuna.fastboot" in our "Foxtrot" directory. Mine had a bunch of numbers, it was like zImage 8246237860837462387462038756012831982 .fastboot. Make sure the file you drag to Terminal ends in ".fastboot", there's one that ends in ".bin".

So: sudo fastboot boot *that file dragged over*

Now it should do its thing, may see a black screen on the Galaxy Nexus for a minute or two. Eventually you'll see a clock where it would be in WebOS (top-middle) and "First Boot" (something like that, I forget) at the upper-left corner.

Now we have to send a couple of simple commands to this WebOS thing from Ubuntu to get Luna (the UI itself) to boot.

You'll see that there is an Ethernet connection in Ubuntu, mine was Wired Connection 2.... Click on the network icon on the top bar in Ubuntu, click "Edit Connections", click on Wired Connection 2, add an Address. Address is 192.168.7.1, Netmask is 255.255.255.0 (actually you can probably get away with entering the default value), Gateway is 192.168.7.2 . Save that bad boy.

Now in a fresh Terminal window, enter, one at a time of course (remember to omit the dollar signs, just good syntax):

$ stop LunaSysMgr

$ touch /var/luna/preferences/ran-first-use

$ start LunaSysMgr

Congratulations! Give it a few seconds, you should be in Open WebOS! Woo!
[Samsung Galaxy Nexus] jimmyco2008:
Got it booting just now lol, and the instructions at webos-ports could be... better, clearer, so if anyone wants to try this out, it doesn't affect their Android installation and you can just reboot into Android easily enough.

If you encounter issues, post here, I should be able to help you out!
[Samsung Galaxy Nexus] lemonspeakers:
Would you mind writing a simplified version?

Their instructions are Daunting!
[Samsung Galaxy Nexus] jimmyco2008:
Sure, here's a really layman version, I'll add to it over the next day or so:

Okay so what we're doing is using Linux (specifically Ubuntu if you're following this guide to a tee) to build the WebOS image for the Galaxy Nexus which webos-ports.org put out. Then we're using ADB and Fastboot to push the image to a certain directory within sdcard0 (the emulated SD Card on the Galaxy Nexus), then we're using Fastboot to deploy, not flash (over the Android boot.img), to the Galaxy Nexus to tether-boot WebOS. It actually boots a really basic version, not sure what it's called exactly... From there we connect via ssh (like telnet) to the Galaxy Nexus with IP to send the final commands to initiate Luna (the WebOS UI).

EDIT: Actually I'll edit the OP with the instructions...
[Samsung Galaxy Nexus] savagehax:
Why would anyone want web os? Ugh awful..
[Samsung Galaxy Nexus] jimmyco2008:
Why would anyone want iOS? Ugh awful..
[Samsung Galaxy Nexus] retskrad:
Does anyone have a video of this working on a Galaxy Nexus? :)
[Samsung Galaxy Nexus] jimmyco2008:
Yeah.... I'm not making a video, but there's a couple on YouTube.
[Samsung Galaxy Nexus] Raphi86:
Really cool. Im a ubuntu beginner and hope i can pass the installation o.O ^^ thank you for this guide. Have a gsm (maguro) gnex -> calling/sms/3g is working?!
[Samsung Galaxy Nexus] -Jesco-:
3g isnt working , call and sms is .
[Samsung Galaxy Nexus] jimmyco2008:
Beat me to it lol... Yeah I may have to pick up a GSM Nexus, no one ever supports CDMA :/

Unless some kind sir out there in the community is ambitious enough to port the radios, not sure how involved that is...
[Samsung Galaxy Nexus] Raphi86:
Why is there no easier way to install it? Cant they compile a "ready to flash" rom for maguro/toro etc?

(Sorry for my bad english)
[Samsung Galaxy Nexus] jimmyco2008:
Not really, this isn't Android... But it may work if I just upload the two files needed to start WebOS, instead of having everyone compile it for 6 hours or whatever. I'm looking into that.
[Samsung Galaxy Nexus] Raphi86:
Sounds good :) Makes it a lot easier. Thanks
[Samsung Galaxy Nexus] jimmyco2008:
Alright check the OP for the download link, it's about 550 MB or so.
[Samsung Galaxy Nexus] Raphi86:
Okay.... after 3 Hours its running.

It feels very good on gnex, but there is a lot of work to do.

On my Maguro wlan works. Bluetooth isnt.

The gesture bar is very very cool and works like a charm.

The os (+Launcher) itself is very smooth. Apps in fullscreen are laggy.

The virtual keyboard and some apps look like cutted up

Cant open phone, but i think its because i have a simlock on my card. cant find a sms button?!

Is the ext2 image build with the lastest source/uploads? the keyboard, especially the scaling, looks better in this version -> http://youtu.be/XelmomAq91o?t=1m19s

Thanks a lot for your guide... it helped me a lot!!! :good:

Two things:

-

Rename "webos-dev-image-tuna-20130226032314.rootfs.ext2" File to "rootfs.ext2"

-

ssh root@192.168.7.2

stop LunaSysMgr

touch /var/luna/preferences/ran-first-use

start LunaSysMgr
[Samsung Galaxy Nexus] jimmyco2008:
Glad to hear it, what about the two things, could you elaborate?

The files linked were what I got when I built them a couple days ago, the difference in the video is probably from it being the normal image whereas I built and uploaded the dev image...Damn, there is a difference I guess, well who wants the Dev image over the one that looks and works better (supposedly)?

I deleted my Ubuntu VM for housekeeping, considered moving it, but in any case I won't be able to build for a little bit, anyone care to upload the normal 500 MB image? I can take it and upload to my cloud so you're not losing space.

EDIT: Oh I gotcha, fixed. Thanks!
[Samsung Galaxy Nexus] jimmyco2008:
Just thought I'd remind people that this exists... And does anyone out there have any interest in this, either as a user or a developer?
[Samsung Galaxy Nexus] -Jesco-:
webOS ? i wont mind .
[Verizon Samsung Galaxy S III] alexcolodner:
I know there are rooted versions of VRALHE floating around, but is there an unrooted base with VRALHE included anywhere?
[Verizon Samsung Galaxy S III] Neverendingxsin:
You should just be able to take the OTA if your not rooted
[Verizon Samsung Galaxy S III] alexcolodner:
I am rooted. I want to use it for some script testing
[Samsung Galaxy Nexus] 19blacktiger77:
Hi to all,

i heard of many people had this problems, and appens me too.

I try to flash kernel, boot.img, system.img, wipe data, restore baclup...

Nothings works!

Then i make a backup with TWRP ( will also be good with CWMR), save all sd data to computer, and with Galaxy Nexus ToolKit i flash the stock rom. ( yakju-jro03c-factory-3174c1e5.tgz)

Copy back all the SD from computer, install same recovery, and restore backup.

All goes right!!! :good:

I didn't try this procedure:

Download Factory Images

Extract 4.1.2.rar

Extract FlashNoWipe.rar inside 4.1.2 folder

Extract only bootloader, radio and image inside 4.1.2 folder

Phone in bootloader and launch flash-all.bat

This don't wipe all, but since i think it's a problem of file system corrupt, you may try this before do the first procedure. In every case, save your backup. Or you have to install all again!!!

Hope you find usefull!:fingers-crossed:
[Samsung Galaxy Nexus] Dragn4rce:
Be better if u put this under general I think. This isn't a question. :p

--------------------------------------------------

If I have helped you.... hit that sexy thanks button. ^_^
[Samsung Galaxy Nexus] 19blacktiger77:
There is a way to move post or i have to create a new one???

Thanks!
[Samsung Galaxy Nexus] Dragn4rce:
Contact a mod and request it.

--------------------------------------------------

If I have helped you.... hit that sexy thanks button. ^_^
[Samsung Galaxy Nexus] beekay201:
Huh... no more toolkits please.

Sent from my i9250
[Samsung Galaxy Nexus] sumit hooda:
keep it simple. back up using titanium bckup . data nd cache wipe and than install factory image .

unll b good to go. nd restore only app , app+data for only necessary apps
[Transformer TF300T Themes and Apps] funnel71:
I use text plus for SMS on the tablet. It seems adaway blocks the ads, but also prevents texts from being sent, but I can still receive strangely enough. Anything I can do, or have the devs just gotten wise here?
[Transformer TF300T Themes and Apps] moisaal:
use another sms app? or see if romtoolbox pro's ad blocker is enough to do the trick.
[Transformer TF300T Themes and Apps] madferret:
You can add the app to the Ad Away white list, that should sort it out.
[Transformer TF300T Themes and Apps] funnel71:
Yes I just now spotted that, now my question is how do I know what to add? I can't seem to add an application, but I can add a URL but I'm not sure what the URL is/are
[Transformer TF300T Themes and Apps] Flashben:
Some app requires ads enable in order to use... its the app issue, not ad away..
[Transformer TF300T Themes and Apps] funnel71:
Think I got it, I just tried adding *textplus* with the wildcards and it seems to like that. Messages are still going through. I can ignore the ads on that and still have it active on other things.
[HTC One S] mikeyinid:
ive looked and cant seem to find a flashable zip of the most recent tmo firmware. i found a nandroid but wifi didnt work. if someone knows where one is or can post one id appreciate it.
[HTC One S] fmedrano1977:
It's not going to work for you regardless. There is firmware you need included in update for Wi-Fi to work on that build.

HTC One™ S
[HTC One S] mikeyinid:
maybe why there isnt one posted lol. thanks man
[HTC One S] puiutzuusa:
I personally had to relock the bootloader and flash the 1.53 RUU, get the 2 updates, unlock bootloader, flash recovery and finally root....... Took me 2 hours :) but worth it, everything works
[HTC One S] mikeyinid:
Do you find wifi connectivity is better on the latest firmware? That's the reason I want it. I have the oldest and have bad wifi issues. Won't stay connected.
[HTC One S] fmedrano1977:
I personally had no Wi-Fi issues running stock 2.21 RUU and data network speeds where faster than this latest T-Mobile release too. Thinking of going back to it.

HTC One™ S
[HTC One S] mikeyinid:
I went ahead and took all the updates. Now wifi seems solid but data sucks. Speed test app won't even run. Keeps saying network issues. With full bars. I think I effed up :eek:

Sad thing is you can't ruu back to older versions afaik
[HTC One S] fmedrano1977:
Yeah once you apply 2.35 update, you can only go back to 2.31 & 2.21 AFAIK.

One™ S
[HTC One S] mikeyinid:
very sad too cus my phone blows now.
[HTC One S] fmedrano1977:
2.21 runs great with awesome data speeds. I was on that for weeks till yesterday, giving this 2.35 a test drive. 2.31 gave me random reboots.

I'm on T-Mobile US.

HTC One™ S
[HTC One S] mikeyinid:
Hmm. So I was having even worse data/wifi issues after updating. Like I said the speed test app wouldn't work, wifi calling wouldn't work. So I found the newest ruu which is posted here in the q@a section, like 2.85 or whatever. Ran the ruu and I'm having zero issues. Something with taking the updates ota didn't agree with my phone. If you're having issues after the ota I'd suggest just running the ruu. Seems flawless now.
[Samsung Galaxy Nexus] Mondo__Man:
i have a GSM Galaxy Nexus and i'm rooted running the Thunderstick soft and chewy 4.1.1 rom. much to my surprise today my phone received an over the air update asking me to install 4.1.2 ; first of all, i didn't know a non stock custom rom could receive an ota update and i've been rooted on custom roms now since the beginning of ics and my phone has NEVER once ever before received an ota. especially now given that i'm already on a 4.1.1 and i got an ota update asking me to go to 4.1.2; so pretty surprised to put it mildly.

secondly i have GNofficial update app which tells me that my phone is either updated by google or not updated by google which i've found to be depending on what rom i'm using and currently my thunderstick rom makes it say i'm not updated by google. even if i wasn't rooted i never thought i would be updated by google anyway since i'm in canada not the united states and on some little ****ty carrier called Mobilicity. the last thing i ever expected was to receive an ota update. who sent it? Mobilicity? Google? i don't even have a clue where exactly this ota update is coming from. am i to believe that my galaxy nexus which came with android 4.0.1 originally out of the box and has never once before ever received an ota update would suddenly send me 4.1.2? so to re-cap that means if i had never rooted i would still have been at 4.0.1 and suddenly be getting 4.1.2 and in Canada and on Mobilicity of all things. so i'm super confused but that's not even my real question.

what i'd like to know is what will this update do to me? will it bring me from this beautiful exquisite custom thunderstick soft and chewy 4.1.1 to the STOCK 4.1.2??? and unroot me? it wont stop pestering me about it either, it just keeps prompting me do go for it! i checked on rom manager and there isn't a thunderstick 4.1.2 yet. mostly i'm very confused at even receiving it and that it keeps prompting me as if i have to do it or it wont go away. i could just imagine me doing it and then it sucking cause it's stock and not like thunderstick's soft and chewy which i've fallen in love with and then me going to the trouble of re-rooting and re-flashing thunderstick and then probably receiving the damn OTA all over again! has anyone else had this happen? why am i receiving a stock ota update when i'm already not even running stock?
[Samsung Galaxy Nexus] Mondo__Man:
is there a way i can make it stop asking me to install the ota update? can i make it stop appearing in the notification?
[Samsung Galaxy Nexus] tcu:
I recently aquired a Nexus and when the phone said there was an update available I hit ok. During the reboot the phone became stuckc on the "X" logo screen and has been that way for way longer than it should. I tried clearing the cache and even a reset and it is still stuck on that screen. What do I do? I'm desperate!

I'm also not very savy with this kind of thing so please take it easy on me lol
[Samsung Galaxy Nexus] Demanufacturer:
I find after I do an update / flash, it stays on the boot animation (the x) for a really long time. Try giving it 10 minutes.. dont be eager to battery pull (i've done it before thinking, omg, its screwed! but just waited and it was fine..)

If that doesn't work, you can go down the route of rooting it and installing a custom rom.. many guides out there on that..

google "wiki galaxy nexus cyanogenmod root" for instance