yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] jaskaransingh:
I've been hearing about adb shell but don't know what it is... Can you help me??

Sent from the UK by a Samsung Galaxy Ace S5830
[General Questions and Answers] CyaNn:
adb is the server where your device connect when you develop from your desktop.

you can read logs in real time with it, get some screenshots, send your apk to test it, debug..... ect.

You have a good gui to use it on eclipse, or use it with command line is possible.
[General Questions and Answers] post-mortem:
Android Debug Bridge
[General Questions and Answers] Lifehacker7:
First of all, you need to know what "SEARCH" is!

Cuz that answers most of your questions.!

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

DON'T GIVE UP ON YOUR DREAMS!

KEEP SLEEPING. :P
[Nexus 10 Q&A, Help & Troubleshooting] rdsreference:
Just to let you know after waiting patiently for the 4.2.2 update which I began installing ,a system error shows up on my screen so I have to reboot in recovery mode. Now I can't get it back or do I want to?. Sending it back is a headache as its not available in Ireland .Any suggestions? its buggy as hell although its only chrome it seems which is the same in my windows 7 work PC ,constantly crashing. They seriously need to get their act together.

Anybody with some info

R
[Nexus 10 Q&A, Help & Troubleshooting] avdaga:
Come on man, use search or at least scan through the topics to see whether you can find something relevant. If you would have done so, you would find at least 1 topic with exactly the same question. Please start using your brains.
[Verizon Samsung Galaxy S III] NYGiants4Natic:
I need help guys,

I used Odin to root the phone and did my first custom rom which is the clean rom...it went through the process and when it was about to reboot i got the system software not approved by verizon and take phone to store

I have been told to odin back to stock but it wont let me. The stock image on odin wont work it says fail

I tried the first method and used odin in download mode to flash the stock image

Failed:

This is what I get

added

Odin V3 engine

File Analysis

all threads completed (succeed 0 / Fail 1)

In the Odin Download mode on the phone the top left reads as follow

Odin Mode (Red Letters)

Product Name (SCH-I535)

Custom Binary Download : Yes (1 counts )

Current Binary Custom

System Status Custom

Qualcomm Secureboot: Enable
[Verizon Samsung Galaxy S III] NYGiants4Natic:
One thing I gotta mention is that when I got the phone last week it had an OTA update from Verizon which I did install and then a few days later I rooted the phone and when I tried to use Clean Rom it gave me the dreaded Verizon message
[Verizon Samsung Galaxy S III] bobAbooE:
Sounds like you didn't unlock the bootloader.
[Verizon Samsung Galaxy S III] Stranger_84:
Ya your bootloader is locked again ... unlock it and redo the steps everything should be fine after that
[Verizon Samsung Galaxy S III] NYGiants4Natic:
Guys I know that the bootloader is locked but i cannot get back to stock to unroot phone and then unlock the bootloader

Odin recognizes phone but the stock image goes into fail mode right away

I cannot get into recovery and the only thing I can do is go to download mode and Odin but nothing else
[Verizon Samsung Galaxy S III] Stranger_84:
http://xdaforums.com/showthread.php?t=1840030&highlight=jtag

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

http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/

http://www.android.gs/fix-bricked-verizon-galaxy-s3/

one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
[Verizon Samsung Galaxy S III] jmxc23:
You are aware he can Odin flashed the latest OTA instead of that you have provided. Here it is :http://xdaforums.com/showthread.php?t=2046439. This will also help fix his phone being that it is recent. Forgot this link to get him back on track: http://xdaforums.com/showthread.php?t=1974114.
[Verizon Samsung Galaxy S III] Stranger_84:
i thought thats what he already tried? but yes you can odin any ota file being that an unlocked bootloader isnt needed.
[Verizon Samsung Galaxy S III] NYGiants4Natic:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
[Verizon Samsung Galaxy S III] Stranger_84:
I'm not sure being ive never had that issues ... im sorry and good luck
[Verizon Samsung Galaxy S III] andybones:
try flashing odin stock ROM, not bootchain
[Verizon Samsung Galaxy S III] jmxc23:
Did you put the file in PDA in Odin they only work if you checked PDA.
[Verizon Samsung Galaxy S III] BattsNotIncld:
I had a similar issue once. This helpful post by h3llsdr0id eventually got me up and running. Took a total of like 4 hours though lol.

http://xdaforums.com/showpost.php?p=30569324&postcount=26

Make sure you have the correct files. This is for the original root66 so it's ICS. Once I booted up and activated I took the Verizon OTAs all the way to JB and then rooted/unlocked bootloader.

edit: I actually had to go back to ICS to reprovision my SIM so not sure you have to go through all of this. Try to odin stock JB ROM like mentioned above.
[Verizon Samsung Galaxy S III] NYGiants4Natic:
Thank YOU so much guys you have made my day.

After trying all last night and today I got it back to stock with the OTA file through ODIN. That is all I needed and it went right back to brand new stock phone using 4.1.1

WOW.

I thought I was going to have a dead phone.

Thank you all
[Verizon Samsung Galaxy S III] Stranger_84:
Glad you got it up and working!!!!!
[Verizon Samsung Galaxy S III] Gatanater:
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
[Verizon Samsung Galaxy S III] mj76:
I'm having the same problem and can't get into download mode

Hi there,

Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.

Thank you in advance
[Verizon Samsung Galaxy S III] HHF2:
You have to get into download mode to use Odin. It will go into download mode, if you will search, there are ways to pull battery along with button combo to get it there. After rooting, use EZ Unlock 1.2 and that will unlock your bootloader without then unauthorized message from Verizon. Make sure you use only that version, the others don't work.
[Verizon Samsung Galaxy S III] flammablepez:
Re: I'm having the same problem and can't get into download mode

Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
[Verizon Samsung Galaxy S III] mj76:
Thank you for your response. I tried pulling the battery out and holding volume down, home and power keys at the same time while putting battery in, even as i plugged it into my phone, but nothing but the unauthorized error screen comes up. I should note that my phone is note 2 not s3. I apologize for posting it here, but this thread seemed to be just like the problem i was having.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jirv311:
So building and flashing ROMs is nothing new to me. I've been doing this since the Captivate days and have done this with all of my Android devices including my new Kindle Fire 2 (which is running 4.2) but for the life of me, I cannot get a 4.2 ROM running smoothly on my GS3.

Here's the deal. When flashing any 4.2 ROM, I get the same issues. Most times, it takes several (as in at least 8) presses of the Power button or home button to wake the screen. When it finally wakes, the animation on the "unlock" button freezes. I can sometimes still swipe it to unlock but most times, the button itself doesn't move. The phone typically runs fine once unlocked.

I know there are some camera issues still but mine make it totally unusable. I can open the camera but rotating it typically screws the orientation up on screen and no other screen presses work afterward. If I tap to open settings or flash settings, the options show up on screen but then again, screen presses are no longer working. I have to exit camera and start over which typically results in a couple Gallery FCs before it finally opens again.

What I've done to no avail. I've tried multiple combinations of wiping cache, system, dalvik, internal SD card, all within TWRP as well as checking MD5 on the ROMs after they've been copied to my SDCard and am running the latest TWRP available for my phone. I have also tested this without restoring ANY data and using the packaged launchers and I get the same behavior. If I go back to a 4.1.1 ROM, everything is perfectly fine. This ONLY happens on the 4.2 ROMs available.

I'm looking for any help on getting this sorted not because it's a big deal but because it's driving me friggin' insane! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peecs121:
Re: [Q] ALL 4.2.2 ROMs hate my phone. Help thread.

Have you tried CWM Recovery yet? It's what I use and have literally tried every rom put there with no problems ever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
You don't mention it, but did you use the wipe option that is at the bottom left of the TWRP wipe menu screen? The scary looking one that says it's probably not needed?

I do that one every time.

I would restore to stock 4.1.1. Then flash TWRP's latest again and try one more time by flashing something mainstream like CyanogenMod 4.2.2.

Flashing stock ROM's has fixed a couple weird issues for me lately.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jirv311:
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.

I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.

EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
Have you tried a different kernel? I run ktoonsez KT747 with Task's AOKP with awesome results. Nothing against Task's underwear kernel, but maybe the 4.2 version just doesn't like your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Intub8:
yes if you flash the 4.1.1 stock file through the desktop odin you will upgrade the bootloader , with the new boot loader everythime you reboot the phone with a custom recovery like cwm or twrp it will raise the flash counter. Here is what I would do. reboot to twrp , wipe data/factory reset , wipe cache wipe dalvic and wipe system. then go to advanced and reboot into bootloader/download mode. once in downlaod mode flash the rooted ics 4.0.4 rom with desktop odin, I was going to link the thread by mrrobinson but it seems someone un-stickied it so your going to have to try and find it.either go back to stock from sammobile.com and root it or get a pre-rooted file. once your back on stock rooted ics download goomanager from the play store. inside the goomanager click install open recovery script. this will install twrp on your phone. after that put the rom you want back on your and follow the op for that rom. do it exactly as it states.I reccomend task650's rom. If you still have a problem try a different kernel. Not all phones are the same, some phones wont even boot up with certain kernel's. hope this helps

edit here is the link http://xdaforums.com/showthread.php?t=1739426
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jirv311:
I just did exactly this just now and the same exact symptoms occur. Even after flashing ktoonz kernel. This is the weirdest thing I've ever dealt with.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Intub8:
yes that is very odd. If it works fine on stock or 4.1 rom's then it definatly not a hardware issue with the button. Im sorry man , I have no idea what it could be.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jirv311:
Yeah I'm confused as well. I just flashed the last CM10.0 4.1.2 and it runs flawlessly. Definitely a head scratcher. :confused:
[Sony Ericsson Xperia Neo, Pro] spa856:
Hi All.

I have a problem with my original battery.

When it arrives at 15% the phone go to shut down.

I know is not normal, but I don't find solution.

Could you help me?

:laugh:
[Sony Ericsson Xperia Neo, Pro] Bertellio:
R: Why Devs Develop ROMs that Look like XPERIA Builds ? Y You No Change the Look

Try to calibrate battery:

Drain battery untill phone power off itself.

Plug in the charger and wait a couple of minutes

While phone is charging, power it on, switch off all connections and lock it.

Let it charge alone till 100% then wait 20 minutes more.

Reboot phone to cwm and wipe battery stats.

Reboot phone and wait 10 minutes after it reaches 100% of charge (just wait if charge has not gone down)

Finally plug off the charger.

Now only for the next time plug charger in only after phone has shut it off by itself, then charge directly to the 100%.

After this problem should be gone, if not change battery pack or go to service.

Flashing roms frequently is by far the best cause to get a bad calibration.
[Sony Ericsson Xperia Neo, Pro] spa856:
Ok, i will try.

I flash ROM every month.

:laugh::laugh:
[Sony Ericsson Xperia Neo, Pro] mon22:
Certified ROMaholic! :good:
[Sony Ericsson Xperia Neo, Pro] khanjan2khan:
Got similar problem.... Mine varies from 39 to 20 % .... after reaching this it goes directly to 1%... n shut down... Already tried your method... not working ... Is it time for me to buy a new battery?
[Sony Ericsson Xperia Neo, Pro] Attitude.SSJ:
Do you flash too many roms?
[Sony Ericsson Xperia Neo, Pro] khanjan2khan:
I have flashed almost every ROM but not frequently... Minimum of a month apart from trying each ROM... Is it bad? Currently using AOKP by mikegapinski and the previous stable ROM i was using was Pureness Build 14 by ThilinaC.
[Sony Ericsson Xperia Neo, Pro] Attitude.SSJ:
When I used to flash frequently I used to get bad battery levels... But you dont flash so frequently.. So maybe battery needs replacement...
[Sony Ericsson Xperia Neo, Pro] spa856:
I have solved this issue - 3 days -, now it works.

When your phone arrive at 20% --> 1% start to charge.

Shut down your phone and go to sleep.

This operation for 3 days.

Only for the first morning, reboot your phone (always in charge) and go to cwm. Clear battery stats.

Reboot, wait 5 mins with the phone in charge and after unplugged.

In the 4° day yo can charge with your phone on and you must see 1% --> 2% etc...if display shows that, your phone works.

During the day, if your charge are finishing, you can charge (not full).

Ok?
[Sony Ericsson Xperia Neo, Pro] khanjan2khan:
I'll try this and let u know the results... thanx in advance...
[Sprint Samsung Galaxy S III] poit:
I have used my SGS3 for a while now with the built-in bluetooth phone connection in my car. The first time I used it I had to go through the pairing process, ever since then it automatically connects as soon as I turn on the car. I don't have to touch anything, as long as I have bluetooth turned on it connects.

So, I added a Logitech bluetooth audio receiver to the car http://www.amazon.com/Logitech-Wireless-Speaker-Bluetooth-980-000540/dp/B004VM1T5S

This unit paired with the phone fine, and remembers the pairing. Only problem is every time I turn it on, I have to go to the bluetooth menu on the phone and tap the entry for the logitech adapter to get it to connect. It's a few more steps that I'd like to make this work.

Can anyone suggest a way to my phone to auto connect this pairing?
[Sprint Samsung Galaxy S III] poit:
I know it's uncool to bump your own post, but really........nobody?
[Sprint Samsung Galaxy S III] Ragnar:
Really unsure but try deleting the device from your phone reboot and pair again. All I can think of.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] m20120:
I have the same problem and I have not been able to solve the problem. I am using a Blackberry Bluetooth Stereo Gateway. It would auto connect just fin to my Evo 4G. It will not auto connect on the SIII. If I look at the Bluetooth settings I will see it briefly show Connecting before dropping off when I power up the gateway. It has been this way since I got the SIII. I have only tried the stock ROMs. I am thinking about trying an AOSP ROM to see if it makes a difference.
[Samsung Epic 4G Touch] leaderbuilder:
Wait - you are sure to be asked the above ^ by someone I'm sure. :P

Thanks RWILCO12 for this excellent tutorial and write up. I may have more free time in the next few months and may be digging back in to the world of coding and compiling. ;)

It's folks like you and all the other devs and contributors that make this such an awesome community! Thanks again.
[Samsung Epic 4G Touch] rwilco12:
Lol truth be told I think I get a PM or email at least once a week asking... :(

I would love to share with everyone but I myself bricked my phone as part of the learning process. I would hate to see it rushed and have someone brick their own and other people's devices.

When you get back into the game hit me up and we'll see if we can get you going. :)
[Samsung Epic 4G Touch] Nicamarcel1:
Cool thanks for your time I'm learnin... yeah :D
[Samsung Epic 4G Touch] aveulivm:
Thanks for all the work you put in for all of us.
[Samsung Epic 4G Touch] MotoDefier:
i have a T999L and am trying to get a working stock rooted odin flashable rom built, the only problem i see in your what needs to be written into the tarball is the T999L has sbl1 sbl2 sb3 and is the zmage the same as the Tz or no, i know how to dump all of the partitions but i dont know about zimage or the hidden img factory fs is the system partition right so it would be dd if=/dev/block/mmcblk0p14
[Samsung Epic 4G Touch] rwilco12:
The steps in this guide are specific to the Sprint Epic 4G Touch but with a little creativity could in theory be applied to all Samsung related.

Good news is that not all devices have a hidden.img so if it's not there I wouldn't worry about it.

The sbl being in multiple positions isn't uncommon either. Add them to the TAR ball in numeric order and that should take care of that.

I'm mobile right now so I can't confirm the exact devblock but Factoryfs is equivalent to system.img on other devices so you should be good.

As for the question on zImage, I've not heard of a tz partition. Is that the kernel on the t999? If so I would assume it would go in the place of the zImage.

Hopefully this helps a bit!
[Samsung Epic 4G Touch] MotoDefier:
here is a list of all partitions, zimage is not one of them.

aboot p5

backup p20

boot p7

cache p17

efs p11

fota p19

fsg p21

grow p23

modem p1

modemst1 p12

modemst2 p13

pad p9

param p10

persist p16

recovery p18

rpm p6

sbl1 p2

sbl2 p3

sbl3 p4

ssd p22

syste p14

tz p8

userdata p15

all are on mmcblk0

im guessing since it doesnt have a zimage that the tz is the kernel
[Samsung Epic 4G Touch] majdinj:
Thank you for such comprehensive tutorials,,

I got 3 question here..

1) How could I tell that the tar file created use the correct order if I was not the one who create it?

2) Could I use this command line to tar all dumps that I extracted from the ROM (by using wild star):

tar -H ustar -c *.img *.bin zImage > package.tar

3) And another query, after creating tar, I checked the permissions given to files by opening the tar by 7-zip.. In this created tar, all files are given the full permissions (0rwxrwxrwx); however, in the shipping original one, each file has different permissions!!!. The following is just an example:

Is this going to affect the flashing process later on?
[Samsung Epic 4G Touch] rwilco12:
In answer to your questions:

1) How could I tell that the tar file created use the correct order if I was not the one who create it? This one is really hit and miss. The best method is to find a stock from the manufacturer TAR and flash it. Odin will flash it in the correct order. Take note of what Odin shows in the progress section and then use that as your flashing order. If you don't have that available it is a lot harder. You have to take them and put them in what you think is the best order and flash to see if you boot. If you don't try again. If you do? Awesome! You've got the boot order!

2) Could I use this command line to tar all dumps that I extracted from the ROM (by using wild star):

tar -H ustar -c *.img *.bin zImage > package.tar

In theory yes, but in practice no. The order that you put them in the TAR is what determines the flashing order. If you were to flash all the .img files and it grabbed the wrong .img file as the first item it could cause the device to not boot. I have played with the wild cards and have decided that best practice is to always to type them out one by one.

3) And another query, after creating tar, I checked the permissions given to files by opening the tar by 7-zip.. In this created tar, all files are given the full permissions (0rwxrwxrwx); however, in the shipping original one, each file has different permissions!!! Is this going to affect the flashing process later on? Long story short? Don't worry about it. Odin applies the correct permissions during the flash process. Each file within the img files (or bin, etc) comes with their own set of permissions and these are not inherited from the permissions within the TAR.

If you have any other questions or need any help let me know. More than happy to help. :)

Thanks!
[Samsung Epic 4G Touch] majdinj:
Thanks a lot for this spirit man,, that's why I love xda tooooooo much :laugh:

I am planning to make a utility for win users by which you will be able to do partitions dumps and then TAR them as flashable odin file.. It will be good idea especially for dumping some ROM leak versions. of course I will include linux reader tool to be able to extract the dumped img for custom ROM cooking..

In the meantime, I will concentrate on studying since I have promotion exam coming after 18 days..

Thanks again ;)
[Samsung Epic 4G Touch] MotoDefier:
[QUESTION] so I have been working on an odin flashable rom for the T999L with another developer, when I tarball my files, if I open it in 7zip it doesn't show any permissions for the files, what am I doing wrong in the tar command? Also do all odin roms have to be tarballed in a certain order, or is that for the device you wrote this for only?
[Samsung Epic 4G Touch] rwilco12:
Permissions really aren't important for the TAR file as Odin sets them as it is flashing the TAR. All Odin ROM's have to be TAR balled in a specific order that is unique to that device. However, the order is generally bootloader, kernel, data, system, modem (or very close to that).