yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] xsenman:
Using Repair Kit to Unbrick M110S
​

This solution is good for reviving the M110S from all major problems that you may have as well as from those that have been bricked by flashing incompatible Firmware. This solution is also good for those who had been scammed into thinking they had bought an i9000 Device bearing the the undermentioned firmware , when in fact it is only an M110S, dressed up to look like an i9000.

​

​

Firmware Version: 2.3.4

BaseBand Version: I9000ZSJPJ

Kernel Version: 2.6.35.7

Build No: Lidroid-i9000-1.2

Solutions to other problems that you may have that need to be resolved first. ( Solve them first)

1) USB Connection Problems Check [Tutorial] How to resolve micro USB connection problems [unknown USB device][code 43]

2) No Download Mode Check My Android Solutions

Also get to know the Basic M110S Flashing Procedure M110S Flashing Guide
​

Needed Downloads for this procedure:

1) Odin3 V 1.70

2) M110S Repair Kit

3) Repair Kit procedure PDF Document ( same as mentioned below)

4) For Latest ROM's kernels and anything else Check PIT STOP
​

First stage :- For every Stage of Flashing RESTART ODIN and always use Fresh ODIN

1) download repair kit and unzip it (you will have 6 tar files)

2) put phone into download mode after battery pull

2) run odin and select m110s.pit under PIT (Re-partion option will be automatically ticked)

3) select M110S-PDA-PHONE-MOVI-REV03-DG23-1409-USER.tar.md5 under PDA

4) connect phone and Press start (within 10 min your phone will reboot into Eclair Firmware)

​

you will have a fully working phone after this, only needs further updates, so continue to stage 2

Second stage:-

1) put phone into download mode after battery pull

2) run odin select S1_KOR_DE09.pit under PIT (make sure you UNTICK the re-partition option in Odin)

3) select M110S-BOOT-DG23-1409.tar.md5 under CSC

4) connect phone and press start (within a few min phone will reboot)

​

Third Stage:-

1) put phone into download mode after battery pull

2) run Odin select M110S-NPS-IMAGE-REV03-DG23-1409-USER.tar.md5 under PDA

3) selct M110S-PHONE-REV00-DG24.0151_Develop.tar.md5 under PHONE

4) Connect Phone and select start ( within few min phone will reboot )

​

Fourth Stage:-

Your Phone is currently running its FIRST out of the box Firmware used in 2010 , so now you need to upgrade to the latest 2012 Stock ROM or Custom ROM's of your choice so repeat Flashing Procedure to upgrade to Latest Firmware and remember you have to wipe and factory rest your M110S in 3e recovery after flashing the stock ROM

IF unable to complete repair procedure ​

My advice is to proceed to stage 4, meaning you Flash a Latest stock or custom after the Eclair ROM, this will solve the issue and you would be able to USE the phone .

Final Solution:-

After receiving many requests for help, concerning stage 2 of the repair procedure, Failing or unable to complete as it gets stuck on Boot-loader upgrade or similar

so if it gets stuck after stage 1 ( meaning phone functions using the oldest ROM ) , just continue to stage 4 and flash the latest Gingerbread ROM WF07 ( download from Pit Stop)​
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] BrunoNRG:
I have cwm 6.0.3.3 and android 4.3 with root installed and the only way I can access recovery is using the "rebooter" option from Rom Toolbox and select Reboot Recovery. For some reason I can't access recovery with the home + vol. up + power button combination, the phone stays on bootloop untill I release the buttons, I can enter download mode with no problems... Any idea why this happens, am I missing something?

Many thanks
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] basvanasperdt:
Weird.. I've had CWM 6.0.3.1 and 6.0.3.3 installed on Android 4.3 (stock), and entered without any problems.

May I ask you how you flashed the firmware, and how did you managed to get root? Because every time I installed CWM on my (CF root) rooted device I lost my root..
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] c.senor:
I think you have to let go of the buttons once you see the samsung logo with the red exlamation mark in the left top corner.

Then it will enter recovery mode, else if you keep pressing them it will restart... at least that is how it is for me.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] BrunoNRG:
I flashed the rom with odin, rooted using cf-auto root and flashed cwm (both flashed with odin), than updated the recovery from cwm 5.x.x to 6.3.3 from recovery itself (zip file)

The red exclamation mark did show up on 4.1.2 but it doesn't on 4.3...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] basvanasperdt:
I used the same method, only I flashed directly to a version 6 of CWM.. Will try again maybe tonight wish an other recovery file in Odin. Thanks for your reply.

And indeed, the small red mark was disappeared in 4.3.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] BrunoNRG:
But you can access cwm with the power + vol. up + home button combination? If so, can you send me a link to the cwm you flashed?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] basvanasperdt:
Yes sir, not a single problem. Maybe you are holding the buttons for to long?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] BrunoNRG:
Should I release them as soon as the Samsung Galaxy S3 GT-I9305 logo appears?

I also notticed that Triangle Away ain't working anymore...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] basvanasperdt:
Yes, you should give it a try. Just release the buttons shortly after the logo appears.

Triangle Away was based on the old 4.1.2 bootloader. By flashing the 4.3 firmware using Pc Odin, the new 4.3 bootloader is installed. You know, the one with the sh*tty KNOX everyone is complaining about. When you go flashing with this bootloader, you void your warrenty. I've done it as well, it's not a big deal. Developers are keen to find a solution for it, bjt it may take a while
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] BrunoNRG:
Thanks! Just tried it, and it sometimes it works others don't, I guess I just have to time it right... :good::good::good:

Regarding Knox, at least with root (when SuperSU updates the binaries asks to disable it) it ain't so intrusive, although the Knox Warranty Void remains active (because it's part of the bootloader), and mine already shows 1 so, just like you said, untill developers find a way ro reset / disable it, we will have to wait.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] basvanasperdt:
Great, glad it works! When I was new on the Samsung phones, I also had some difficulties in the beginning to enter the recovery mode. Timing has be be right sometimes :)

The SuperSU indeed disabled the KNOX app, so it won't mess around and complain about you giving root-permission to other apps. Unfortunately the bootloader is a different story. It will take some time, but I'm convinced some great developers here will come with a solution.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] c.senor:
Sorry I should have mentioned I did not flash original firmware so I don't have knox and all that.

That is why I still get the red exclamation mark...

Guess I was lucky I waited for comments...
[Ouya General] hiredshogun:
Hello everyone, im here trying to spread the word about an upcoming Minecraft clone on kickstarter. They've got about $200 more to go, so if anyone is interested, check it out and donate a dollar or two!

Ouya Cubed - 3 days left to join the quest! by Eric Blackburn ? Kickstarter

Screenshots:
[Samsung Epic 4G Touch] jwitt418:
My wife has a E4GT which I rooted installed cmw and a stock rooted rom about a little more than a year ago. Anyways the current rom is having some issues and I want to switch ROMs for her. I remember this phone was a bit of a pain to flash and that I had to use mobile Odin and flash back to an older rom before flashing new.

Can someone please give me some direction to flashing ROMs on this phone....ie which modem to flash back to? I'm Odin or cmw? In what order.

Thanks in advance I really don't feel like bricking her phone. Lol
[Samsung Epic 4G Touch] BIGSAMDA1ST:
Why dont you head on over to either Android Development or Original Development...They have some pretty good stuff and all have instructions on how to go about flashing them..Plus a bunch of good guys that will definitely get you going in the right direction....

GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
[Nexus 7 Q&A, Help & Troubleshooting] mrej201:
hey guys i bought my niece a 2012 nexus 7 it has the axus charge with different usb cable but it charge so slow

i was wondering if there is a rom with better charging speed

i havent root and is wifi version
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
What does "so slow" mean? As in, how many minutes to change 10% in charge?

One thing you can do to troubleshoot things is to see how long it takes to charge the tablet when it is completely shut off. It should be pretty obvious that "the ROM" has absolutely nothing to do with that scenario. Wait till the tablet is discharged to about 10%, shut it off, and charge it for 90 minutes. If it is charging normally it will be close to 70% charge when you boot it back up.

If your tablet charges slowly in that case, then there is a problem with the charger, cable, or battery in the tablet - not the ROM. So, you should surely check that out first before you start worrying about software.

A nominal N7 (2012, WiFi) will charge from 5% to 100% in about 150 minutes: 2.5 hours. That's with a STOCK ROM. If you look at the battery capacity, that works out to a minimum 1.73A charging rate. (4.325 Amp-hours / 2.5 hours = 1.73 A). It's actually higher than that because a certain amount of charging current is "lost" to heat generation while charging.

The tab will ALWAYS charge slower than that if it is in use, especially if the screen is on and the owner is doing things like streaming data or playing games. If it is under heavy use, the tablet itself could easily dissipating 1.0 A of current... so in that case the 2.5 hour charging time would be over twice as long: over 5 hours.

The "fast charge" ROMs are not what you are thinking. "fast charge" there means "fast charge under conditions normally restricted to low currents when data transfer is taking place". If you are using a charge-only cable (such as the OEM charger and cable), the tablet should always be able to draw close to 2A of current with ANY ROM - there is no data connection present, and the tablet is not restricted in the current it can draw.

The ROMs don't really throttle the battery charging rate except in that very specific condition: when there is a data connection present. So, worrying about which ROM is installed really only applies to people that want to use a Y-cable and a live USB data connection (tethering or an OTG gadget attached) - for instance in car installs or maybe with data tethering via USB.

good luck
[Nexus 7 Q&A, Help & Troubleshooting] mrej201:
thanx man now i get it it won charge fast like the note 3

i was playing fifa 14 and didnt charge at all it was loosing power
[Nexus 7 Q&A, Help & Troubleshooting] khaytsus:
Get a better cable. I was using a third party cable on my Nexus 7 for a while and realized it was only charging about 10-15%/hr.. Changed the cable out for a better one and it charges at the normal rate now, 30%/hr or so.
[Nexus 7 Q&A, Help & Troubleshooting] Lim Wee Huat:
Do check for loose connections for both battery connector and usb ribbon connector (under speakers). I’ve opened the back cover to check after slow charging problems and was solved by opening and clipping back the usb ribbon connector. Charging's back to normal now.

http://androidforums.com/nexus-7-20...esting-while-diagnosing-charging-trouble.html
[Nexus 7 Q&A, Help & Troubleshooting] mrej201:
thanx bro
[Defy Q&A, Help & Troubleshooting] 90Ninety:
Hey guys

How brilliant it was to update my laggy gingerbread Defy +, to 4.3 JB (CM10) i=.It was a massive breath of fresh air, phone seemed amazing until ... I found out the hard way that Bluetooth headsets didn't work correctly - I was absolutely heartbroken , while my manager's speech was reduced to mere fuzz as I was driving to work .

In the UK it is a legal requirement to have a Bluetooth headset or receiver if driving , the current job requires use of phone and van so keeping the 4.3 rom was illogical

What is the chances there will be a fix for the handset in newer roms , or should I cut my losses and just wait for a better smart/toughphone with jelly pre-installed?

Your thoughts
[Defy Q&A, Help & Troubleshooting] Proverbs2:
Bluetooth works on CM10 (not on CM10.1 or CM10.2), so you could switch to that for now, while we wait for it to be fixed in the newer roms.

Hang on to that Defy! If you thought JB 4.3 was amazing, wait until you try KitKat!
[Defy Q&A, Help & Troubleshooting] 90Ninety:
4.3 on-words BT compatibility

I tried CM10 and CM9 , various builds and found them buggy for whatever reason . 4.3 seemed fine apart from BT , So reverted back to 2.3.6 GB

Does the community feel confident a fix for the BT will come around ?
[Galaxy Note II Q&A, Help & Troubleshooting] fatice:
I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.

In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.

Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.

Here was what I have done:

1. Boot into Clockworkmod recovery

2. Clear all partition / factory reset

3. Select Backup and restore.

4. Select the backup directory that I want to restore from (the one without wakelock problem)

5. Wait for the restoration process to finish

6. System reboots.

After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.

1. Restore from different backups

2. Enable "download service" from application manager. (It was not disabled)

3. Reset all apps settings from "Application manager" (menu)

Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.

BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:

1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.

2. It cannot find dalvik partition to wipe.

3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.

Here is what I did to restore my phone to previous state with stock ROM:

1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.

2. Reboot the device.

3. Use Odin to flash CWM recovery.

4. Reboot the device.

5. Go into recovery and restore only the /data partition.

6. Wipe /cache.

7. Reboot the device

8. Boot back to recovery and root the device.

Now I have the phone at my previous state.

Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.

Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
[Galaxy Note II Q&A, Help & Troubleshooting] fatice:
I did not find the problem with restoration using CWM, but did find out what causes the wakelock: "Automatic call recorder Pro".

Disable the auto start function and battery drains is back to 1% per hour during standby.
[Galaxy Note II Q&A, Help & Troubleshooting] sishafie:
I have to say, I did encounter the replication of the same exact problem. It kept popping up "unfortunately com.google.process.gapps has stopped". I was using the same CWM recovery 6.0.4.3 for my N7100 using stock android 4.3.

Try to do so many things but fail to get rid of the pop up. At the end, I ended up having to flash rom using Odin.

Anyway, I think, there's some bug with CWM recovery 6.0.4.3 that caused the error to happen. I managed to use TRWP 2.6.3.1 without any problem to restore after that.

Regards,
[Galaxy Note II Q&A, Help & Troubleshooting] warlab:
Had exactly same problem, i downgraded cwm from 6.0.4.6 to 6.0.4.4 by using odin

Than restore works fine no problems with services.

Note 3 sm-n900w8
[Galaxy Note II Q&A, Help & Troubleshooting] khizerjalal:
Hi.

How did you downgraded CWM using odin? I am stuck in the same problem.

Khizer Jalal
[Galaxy Note II Q&A, Help & Troubleshooting] warlab:
Download image and overwrite existing one
[Galaxy Note II Q&A, Help & Troubleshooting] Deleted member 5662482:
Now i see that i have entered the rooting world in it's darkest time

I had the exact same problem of yours with CWM 6.0.4.3 and and the exact same problem with titanium backup(when i restore APP DATA for almost all apps they crash and keep popping messages). so there was no restore feature for me for long time

BUT TB restoring of App data is fixed when i updated TB to latest version and the CWM nandroid after-restore problem is fixed when yesterday i upgraded to philz 6.46.3, the restored ROM works flawlessly.

Now I think(not sure) what was going on is related to something called "FIX Permissions" or in other words when we restore system + data things get messed up that each app can't find it's own DATA folder causing it to crash. CWM and titanium backup didn't use to fix that mess but now they do so these problems won't occur anymore.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] corrupted_yk:
No ExtROM after downgrade from Wizard v2a to SE.....!!!

Any one......help me please..... :cry:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] joey jojo:
found this on buzzdev, see if it works, but by the looks of it, you need to run it on wm5. if your on wm2003se, try it first, before upgrading again to run it

8)
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] corrupted_yk:
Thanks to U man......!!!! :D
[T-Mobile, Samsung Galaxy SIII] happy4ya:
What is the difference between doing a factory data reset in the settings menu and doing the reset in recovery?

I have a T999 that is on stock 4.1.2 and rooted with CF-Auto-Root http://xdaforums.com/showthread.php?t=1963806

I am giving this T999 to my wife and want to wipe all my stuff from it so she can start clean and add what she wants so I'm trying to figure out the best way to do this.

Also, what's the deal with the flash counter? This phone and my T999L have been rooted so they show 1 and also under settings>about device>status, it shows the device status as "Modified". Other than for warranty reasons, is there anything else to worry about with these not being on 0 and Normal?

Both phones were bought used on eBay so there is no warranty but I was just wondering if it will prevent updates or cause any other issues. Any info would be appreciated.
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
If you're just wanting to "reset" for your wife to use, the reset from within the phone settings is good enough. The option in recovery...gives you more options, such as deleting the contents of the internal sd.

Flash counter is, as far as I know, just for warranty purposes.
[T-Mobile, Samsung Galaxy SIII] happy4ya:
Thanks. Guess I'll go with the reset option from the phone settings.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] chico1983:
Has any one been able to find away to get the Hotspot hack to work with the MK2 update
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ROMANTiC KiD:
Theres a stock rom mk2 with hotspot.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] GeoJam3s:
Some people have said that it is working, but I am quietly waiting for more confirmation before I update to MK2. I am getting ready to go on a trip to Vegas in a couple weeks and LTE is there.... free hotel wifi is not.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] Foulwx:
Check crawrj's original post in development. Fgr created one in post 337 I believe. Haven't heard from crawrj in awhile.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] jramirez1011:
hotspot mod working from the main discussion. im fully stock mk2 update. did update throught kies.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ponycarboy:
MK2 hotspot fix

Help where is this FIX where can I get it im rooted and at MK2 but I need the file anyone have it PLEASE HELP
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] leaderbuilder:
There IS a Hotspot mod that works (actually TWO! - One Odex one DeOdexed) in crawrj's thread. Last few pages I tested them and they worked for me too.

If you're stock rooted (and NOT on customized stock) choose the Odex version.

It's here search for it.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] cruise350:
You can find it in post #337 in the Hotspot mod thread in the development section.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ponycarboy:
Yes it worked great thanks
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] AceKing721:
Thanks, helped me too
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ashishgupta1973:
mk2 hotspot deodexed installed, still wifi hotpot not working

Help, i am using spring galaxy s4, with mk2 update. Have installed mk2 hotpot mod dexodexed, which installs normally.

But i am still getting the same error - hotspot not supported

software version- l720vpuemk2

hardware - l720.08

android - 4.3

baseband version- l720vpuemk2

kernel version- 3.4.78-kt-sgs4-jb4.3-tw-spr-02.05.2014-gd8c5a17

build number- triforcerom 5.4

selinux status- permissive

Wifi hotspot works when using AOSP based ROM

Please help.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] dimm0k:
I believe off a stock MK2 Sprint issues a security update not too long after the first boot that might cancel that out if you install the hotspot after the update. I can't say for certain as I was wiping and loading a few times a month or two ago when I had this problem and the only thing I could think of was to install the hotspot mod before accepting this security update. been able to use the hotspot without any problems since...
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ashishgupta1973:
wifi hotspot problem resolved

Hi, i was finally able to get the wifi-hotspot, and call forwarding settings working.After trying a number of custom roms, i finally installed - omega v19 - XXUEML6. All the above settings, which were unavailable previously are now available and working normally. I suggest, this rom to any other user, who might be facing the same issue with the sprint sgs4 model.