yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] umair241995:
Firstly,

Idk exactly about USB debugging but what i do know is that...

"USB Debugging is intended for development purposes only. It can be used to copy data between your computer and your device, install applications on your device without notification, and read log data." A few apps use it, like the aforementioned PdaNet app. USB Debugging can also be used with ADB when issuing commands from a command line on your computer to your Android handset or tablet. One-Click root apps often require USB Debugging to be enabled to deliver the exploit that roots your device.

SIM card wouldn't affect anything, so it doesn't matter if you leave it in the phone..

After Flashing the JB, first check whether the phone goes into boot loop or anything like that....if you experience any problems then do the factory reset, wipe cache...though its usually recommended to factory reset anyways..

I don't think we need to flash the "emmc_EXT4_16GB.pit" or the other pit file..

The reboot process shouldn't take more than 5-10 minutes max..

Well i have gone from custom ROM 4.1.2 XXLSJ back to the stock 4.0.4 using the usual flashing steps of ODIN....I didn't experience any problems..

If its anything above Odin3v1.85 it shouldn't be a problem...

Press thanx if i helped..
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
Is there any need to do any factory reset/cache wiping from recovery before flashing 4.1.2?
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
I guess that when I flashed jb leak I had all those questions, and maybe a couple of more.

Then I read about Mobile Odin, flashed & rooted my device in half a smoke (3 mins). All I had to do was select the 3 tar files.

The flash did network lock my device. Galaxysim Unlock solved it for me.

good luck and happy flashing.
[Galaxy S II Q&A, Help & Troubleshooting] Spiralzz:
Only once. Either before flashing the ROM, or after. Order doesn't matter.
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
I would imagine then it's better to do it whilst on 4.0.4 prior to flashing (since I have the sane chip) so that you don't get the possible failed boot after flashing 4.1.2 with odin.

So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
[Galaxy S II Q&A, Help & Troubleshooting] Spiralzz:
No, I don't think so. Come to think of it, I've never tried that :P A battery pull works though :D
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
Do you mean it's not better to factory reset before flashing or the long press doesn't turn off the phone from recovery (in which case best to pull the battery out)?
[Galaxy S II Q&A, Help & Troubleshooting] TheATHEiST:
Well since your flashing 4.0.4 its pretty much a must to also install custom kernel to avoid possible silly bricks by wiping data.

So simply flash rom via odin and then do same for custom kernel like Siyah and then reboot into kernel and wipe data/factory reset and you're off ;)
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Sane chip, he's already off.
[Galaxy S II Q&A, Help & Troubleshooting] TheATHEiST:
Yeah didnt notice OP was on sane chip. Was speaking more in general though anyway.
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head. :p
[Galaxy S II Q&A, Help & Troubleshooting] TheATHEiST:
:laugh:
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
I know what you mean. I haven't even done this procedure yet and I'm dreaming of bricked phones/ corrupted IMEIs etc.

Probably a bit melodramatic I know.

It did occur to me that instead of flashing stock 4.1.2 from stock 4.0.4, it may be better to flash the Siyah kernel to my current 4.0.4. This way I can back up efs, do a nandroid and titanium - before embarking on fully fledged ROM flashing etc.

What do you think?
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Well...the beauty of flashing is that you can do both Stock & Custom. You can also Dual Boot if you want.

My advice is this:

1) Always Back up EFS folder (HC-ktool is a good app for that).

2) Get Titanium Back up Pro.

3) Flash CMW or Flash siyah, it can't never hurt (well, if you go JB leak, might wanna try usin stock kernel first and the flash a custom kernel)

4) Get mobile odin Pro (so you can flash as many stock ROMs as you like, with the chance of getting bricked or soft bricked close to none + you'll always be rooted)

5) Read about ROMs features. You are the only person in the world that knows what ROM will fit your needs.

6) Start flashing.

7) If you are scared about bricks, read the bricked device's threads. That way you will know what NOT to do.

In my experience, I went jb and never came back.

Now, you really dream about IMEI, lol, that's something :p
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
I haven't flashed 4.1.2 yet. I was going to do it last night but realised I had forgotten my GPS active and the battery went flat. I took this as an omen and aborted the mission.

I've been reading around the subject for days. There seem to be so many people that encounter problems that it is difficult to have any perspective. The myriad of users that flash stuff via odin without any trouble obviously don't post that it went well - so you read 10 problem posts and never see the other thousand flashes that went without a hitch.

I also have read on xda that the leaked JB 4.1.2 is somewhat buggy. I'm not sure how buggy, but the lock screen freeze would be annoying in practice.

Again the carrot of official jb has been dangled before us - supposedly in February now.......Given that this will probably be the last official release for the S2 I might hang on and wait for it - then embark on the routing/custom ROM journey.
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Well, you read 10 problems while flashing, right now we got 50.000 users going thru these threads, here, at XDA.

Jb is buggy, it's a leak, but too buggy? don't think so.

As for the bugs, we got plenty of people coming up with work arounds & fixes every day. In my case, I only have the lockscreen issue (let's face it, it doesn't always happens, like maybe 1 time a day and it's only for 3 seconds till the capacitive buttons light up. If you lock the screen and re unlock it with the power button, you're off. For me, it's not even an issue). I don't even remember when was the last time I had this issue, maybe 3 days ago now that I think about it.

Where's flashing, there's risk. TRUE. That's why I layed the Mobile Odin Pro option for you, that could be the best way to lose you flashing's fright.

BTW: we are getting the lime pie update, SII Plus was released just now ;)
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
I have had a look at mobile Odin Pro and I like the look of it. Thanks for the tip. To use it I need to root the S2.

I have seen this guide http://xdaforums.com/showthread.php?t=1501719 - this seems simple. I could also flash the Siyah kernel via Odin. Which root method would you recommend? The first method seems to avoid the triangle issue - although this is not a big deal.

With a routed device I can backup efs etc before flashing anything else. Does the efs folder contain the simlock status?

Also, as you know I have been looking at the leaked jb, but perhaps it might be worth looking at neatrom 4.1.2 (or similar) instead?

I seem to get the impression that mobile Odin Pro is a safe method. Is it safer than using PC Odin?
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Okay, lets see.

Nice method, I rooted this way when I updated to ICS & lost root.

If you go on and flash siyah, brick bug will be history for you, no more worries about that.

If you don't want to root via recovery (cmw + busybox) and odin/mobile odin (siyah), you can look into ExynosAbuse's one-click-method.

You could pick either one.

About what ROMs to flash, I dunno, I can't tell you what would be best, that is up to you. I don't even like custom roms, but that's just me. As I'm running JB leak, people that checks out my device go like "hey, what is this? doesn't feel like my S III/NeXus".

Bare in mind that Stock ROMs

should be flashed

via Odin/Mobile Odin meanwhile custom ROMs

should be flashed

via CMW/recovery.

About

Odin

&

Mobile Odin

.

They share the same ground. Chainfire took PC's odin and

plugged it into a phone

.

Is it safe? Pretty much yes, It

checks the files signatures

, so you won't flash some crap, It

checks you battery level

(>50%), It

uses its own kernel to flash

(no brickbug there), It

roots your phone while flashing a new ROM

(EverRoot option on PRO) which is just great not having to root your device everytime you flash a stock ROM, It

flashes the phone with the phone

, so no power off danger there nor pc won't see the device crap.

If you get yourself stucked on boot, you always have PC odin to fix it so, as I said, pretty much yes, it's safe.

EFS folder:

ALWAYS

back it up, HC-ktool does it very well. That folder contains a lot of your device information (IMEI, Network and whatnot) and it can make it unusable.

Titanium back up Pro is another app that's a MUST. Should look into it.

EDIT: Forget what I said about brick bug, your chip is sane.
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
Am currently doing my mobile odin pro homework. A key feature of this is the tooting whilst flashing stock and being able to wipe data/cache as part of the flash procedure.

In all the videos I have seen one ROM file is selected that is then allocated to PDA/MODEM/CSC etc.

In the leaked stock jb 4.1.2, the PDA/MODEM/CSC files are separate. Is it possible to select them individually in mobile odin - or in other words how would you select them all?
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Select however you wish, Mobile Odin places them by itself :)

That jb leak is from Sammobile.com right?
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
There is only one select file button (rather than individual in as in pc odin) - so I'm guessing you go through the open file process 3 times - once each for PDA, CSC and MODEM?

Yes, downloaded from SAMMOBILE.

I will try this at the weekend when I have some time.

You mentioned that mobile odin pro is for stock ROMs. So you could not use this to flash say a custom kernel?
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Yes, you can.

On the other hand, never seen/read-about anybody flashing a custom ROM with Mobile Odin. For what I recall, in the words of Chainfire, is meant for "Leak Stock ROM Addicts", so I assume that it's for stock ROMs only.

Flash it during the weekend, the flash is about 3-4 minutes overall, the "checking out JB" took me for about 3 hours :laugh:
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
I will root then back up efs. The routing method I linked to gives you stock recovery which makes doing a nandroid backup harder. I have seen an app that will do a nanndroid without entering recovery in Google Play (Online Nandroid Backup) - makes sense to use this.
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Yep, that's a good one. I wouldn't know, never backed anything up rather than in my PC.

Will check that app tho, sounds intersesting.
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
I thought I'd try the routing bit now. I placed CWM.zip and busybox on the root of the external sd card.

But when I enter recovery and select install from external memory, I could not see these 2 files (they are visible in android zip file manager).

Perhaps they need to be placed on the internal storage?
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Not necessarily, make a copy of both zip files and past them in a new folder on your External SD Card.

So now you have the 2 files located in the root of the SD card and 2 files inside a new folder.

Recovery sees the external SDcard right?
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
There seems to be some confusion about what is internal and external sd with my unit (or there's something wrong with me - the more likely scenario).

Anyway, am now rooted and have installed mobile odin pro (which I imagine would tell me if I wasn't rooted).

I'm going to let my heart rate come down now and see about the flashing over the weekend after backups.
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
lol, you can check with root check app in play store.

Congrats on your new status:
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
If you use mobile odin pro to go flash ICS 4.0.4 and you tick wipe data/cache in mobile odin - are you exposed to the insane chip wipe data bug - or does mobile odin use some other method to do this?
[Galaxy S II Q&A, Help & Troubleshooting] Spiralzz:
You've got a sane chip. You don't need to worry about that brick bug. Pretend that it doesn't exist for you. :P
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
Understood. I'm just conscious that other users may read this that have the insane chip.

I actually did a factory reset on my device long before I ever heard of sane/insane chips. Man, ignorance is bliss sometimes!
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
Well this went without a hitch using mobile Odin. Now it's a question of having some fun checking out jelly bean!

Mobile Odin is worth its weight in gold. I can't see me ever flashing any other way again. The automatic rooting is clever in the extreme. Why doesn't everyone use this method?

Anyhow, thanks for the help and guidance.

One question, can CWM.zip (used to root in my case - running this zip from stock recovery - it loads itself so you can install busybox - but is not permanent) be used to reinstall a nandroid backup? Or would you have to install a permanent (fully flashed) CWM to do this?
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Congrats on your first successful flash. :)

Hope you're enjoying JB.

M.O. is gold alright, and a lot of people use it, more than you can imagine.

I think that you still have that CMW you flashed to root. You can check it by accessing Recovery Mode.

You nandroid backup is there somewhere, dunno where exactly. If you wanna keep all these flashing, rooting and backing while you are running android, check this app.

---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------

Mobile Odin flashes with its own kernel, so no worries with the wipping there (4.0.4 insane chippers).
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
I have to say I like many things about 4.1.2 - and I see what you mean about the lock screen bug being a non-issue.

This question is probably premature, but when 4.1.2 is finally rolled out for the S2 - can it be flashed via mobile odin in the same way? Naturally I will hang back until this is known for sure rather than being the pioneer/crash test dummy. I am also presuming that updating via KIES will not be possible from the leaked version.

The reason I ask this is that I have read that 4.1.2 needs to take 1GB from the internal SD as it needs more room for itself. Some reports have said that the update is huge and may take up to one hour to install through KIES when released (although how this is known is a mystery to me). But flashing the leaked version was unbelievably quick via mobile odin - so how can you tell if it did take 1GB from the internal storage? If it didn't will the proper release fit - or does mobile odin sort this?
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Lol, that lock screen thing happened twice yesterday, I think there's a fix posted in the general forum. I don't mind anyways, haven't seen that happen for 4 days before yestersday.

Don't worry, I'll also be monitoring the updates of the true pioneers of flashing ;)

But yeah, the update should be Mobile Odin Flashable.

Expect no updates (Kies/OTA) from the leaked version, as it's a leak, technically, we shouldn't have it.

About that re-partition, I don't know, I've seen that post that the korean devices will have to go thru that extensive update. In my opinion, is just crazy, a lot of things can happen in 1 hour time, and you are talking about unexperienced users, most of them aren't even familiar with the word brick. They could be facing a big Korean brick-o-rama. Who knows.

I don't worry too much because 1 o 2 things (maybe both) will happen:

1) Chainfire is gonna see a way around it with a new app or a M.O. Update.

2) The guys here at xda will post a step-by-step guide to flash it without much effort.

And yeah, M.O is fast, how long did it take for you?
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
Something like 3 or so minutes I think. Then it took about 2 minutes for the phone to boot back up - this is the bit I don't like - will it/wont it - how long is enough etc.

Strangely, at some point after the flashing the status (under about phone) said Custom. The when I checked it again a while later (and ever since) it says Official.
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
It's normal to get those 2 min on the samsung animation boot.

Didn't notice that "custom" label.

Sent from the little guy
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
As part of the routing process described earlier CWM.zip was used. This is a temporary touch recovery that you get to via stock recovery.

I have just read that this CWM.zip has bricked the Galaxy Note http://xdaforums.com/showthread.php?t=1810954

I had no trouble using it to root ICS 4.04 so that I could install Mobile Odin.

Is CWM.zip temporary touch recovery safe for the S2?
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
I've never heard anyone complain about cmw.

Then again, philz kernel's got a touch recovery. When JB leak was out, everybody said "flash philz", but I think issues were found and siyah updated to be JB compatible.
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
I might try one of the custom kernels. Having read around it would seem that these can be flashed using mobile odin too.
[Galaxy S II Q&A, Help & Troubleshooting] gastonw:
Yeap, It can.

Tell me how's the performance after you give it a go.
[Galaxy S II Q&A, Help & Troubleshooting] dimbo33:
There will have to be some benefit for me to try one (custom recovery is not enough on its own). I will have a read around.
[General Questions and Answers] Infoto:
Hi guys,I am new here :)

Today I flashed my vision with custom rom (2.3.7+root) from a Russian forum.Everything was OK,then I installed the Beats app and restarted.Now the phone is constantly rebooting.How can I fix it? ?Please help

PS: I try to get in recovery menu,but I cant :(
[General Questions and Answers] eddydc1:
do you have backup? if you have

try to get recovery via adb

type ' adb reboot recovery '

and then restore
[General Questions and Answers] Infoto:
I dont have backup.I managed to get into recovery and made factory defaults, but nothing.It keeps restarting.I uploaded the rom to my sd card.And I saw "download rom from sd card" in the recovery menu.If I click it,would it flash the rom?

And another thing is that i cant remove the battery and that is why it is so hard to get into recovery :(

PS How it is possible to get into recovery mode when the phone is constantly restarting and I cant remove the battery?
[General Questions and Answers] eddydc1:
use adb to get recovery, when the phone boots, quickly type 'adb reboot recovery'
[General Questions and Answers] sweeho:
Huawei U8850 keeps rebooting

Mine already brick...
[General Questions and Answers] syafiqjohn95:
1. Hold the Vol (+) and Power button and hold it until the screen is black. Count to 10 seconds. (Hard reset)

2. Remove a second finger from the Power button and return back to Power button (Quickly release and immediately press it back.) Huawei logo should appear just for a second and then it will turn off. Count to 10 seconds.

3. Remove your fingers and wait for the phone to turn on again, if not then good, if on then do it all over again.

4. Enter recovery mode

5. Flash it back using SUT L3.
[General Questions and Answers] sivakarthick:
bricked my mobile...Help!!!!

I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
[General Questions and Answers] sebby4u:
I have same PROBLEM, anny help?
[T-Mobile, Samsung Galaxy SIII] mgbotoe:
I was not sure where to post this since I do not have enough posts...to make replies in the developer thread.

I noticed the rate at which my phone is charged decreased after installing DaRTHSTALKER S3 EDITION VERSION #8. It normally took about 3 hours to charge my phhone (which is long as it is) Now i am looking at about 5 hours. I did a clean installation and still having the problem.

I am not sure how to go about fixing this. It only happens with this rom :confused:
[T-Mobile, Samsung Galaxy SIII] shahkam:
Backup flash another rom to confirm...
[Android Q&A, Help & Troubleshooting] Aravoth:
I've been searching the forums, and google for a while and can't seem to find a solution that works at all for me. First off, a little history. I am a n00b, and I very stupidly rooted my phone last night, without a recovery.... Actually I don't think just rooting was a big deal, it was me changing the vm heap properties that was really stupid. Why did I change it when the phone was working fine you might ask? Because I quickly gleaned over a forum post about adjusting the heap size to make your phone blazing fast, so, like any other idiot would, I did what the thread suggested, and instead of blazing fast speeds I got a boot screen logo....... forever... Talk about a huge mistake on my part....

Here's the problem,

Phone is stuck on the bootscreen, I can boot into system recovery (stock).

Android System Recovery has a message on the bottom of the screen that says "E: Cannot load volume /misc!"

I have wiped the cache partition, and did factory reset according to the manufactures website.

I cannot get ADB of Fastboot to see the device, even with drivers installed.

I do have a back up of build.prop that is unscathed, but I have no idea how to flash it, or "push" it or whatever.

I do not have CWM installed, and it appears that usb debugging is disabled.

My phone is a Kyocera Hydro. I'm using Windows 7 64bit.

I know I should never have done this, it was idiotic, and easily the dumbest thing I've done in a while. I'm hoping someone out there can help me fix this. Is it possible to put the backup of build.prop on the SD card and have it overwrite the corrupted one? Is there any hope at all?
[Android Q&A, Help & Troubleshooting] Aravoth:
I guess it can't be done then? I had hoped that as long as the bootscreen could come on that there was hope. Hopefully someone out there knows how to push the backup build.prop back onto the phone.
[Android Q&A, Help & Troubleshooting] sashank:
Well right now you're pretty screwed. There's no way to restore it without a custom recovery. You have 2 options -

1) Wait for someone to make a custom recovery for your phone.

2) Try to claim warranty and get it restored/exchanged at the service center. Say it just randomly rebooted and got stuck at the boot screen.
[Android Q&A, Help & Troubleshooting] Hinzman420:
Where did you get the phone Boost, Amazon Wal-Mart?
[Nexus 4 Q&A, Help & Troubleshooting] neotekz:
This has been happening often at certain low reception spots in my house. It would lose reception then get it back but still shows no service or emergency calls only. I'm on AOKP with Franco kernel.
[Nexus 4 Q&A, Help & Troubleshooting] kibox:
Stock, rooted
[Nexus 4 Q&A, Help & Troubleshooting] neotekz:
bump...at least it seems like it not only me. Ive never seen soemthing like this, usually with other phones it can take a long time to get a signal again once it's lost but it never shows signal and then give no service.

Can you make calls or txt when it is like this?