Samsung Galaxy S7 Active Root! (SUCCESS) - Samsung Galaxy S7 Active Questions & Answers

I have an AT&T Galaxy S7 Active - US Model - SM-G891A
I haven't seen any credible sources with a root for this device. From what I can tell, it is identical to the Qualcomm version of the Galaxy S7(non-edge) with one exception; The S7 Active has the "Active button".
Since almost every Qualcomm variant of the Galaxy S7 has been rooted, is there a chance that the S7 active is rootable? or is there already a root?
Let me know if you need any other information or if you would like a test dummy.
UPDATE: Successful Root Of the Galaxy S7 Active (Qualcomm)
PLEASE USE THE POLL TO LET US KNOW WHAT VERSION OF FIRMWARE YOU END UP ROOTING. IF YOU FAIL, PLEASE PROVIDE US WITH AS MUCH INFORMATION, ABOUT YOUR EXPERIENCE, THAT YOU CAN. THIS WAY WE CAN DO OUR BEST TO HELP YOU AND CONTINUE IMPROVING THIS ROOT.
ROOT - CLICK BELOW
Original Tutorial Credit(HERE)
Updated for Galaxy S7 Active (by NotSoMiniGun)
Make sure you have downloaded these files:
• SuperSU v2.74 (updated) SuperSU v2.76
• Modified ODIN
• Unlock boot.tar
• Fastboot
• Samsung Official USB Drivers v1.5.40
Make sure you meet these requirements:
• Firmware PG7, PH2, PI2, PK2, PL1(6.x.x only)
• NO NOUGAT SUPPORT YET (1/30/2017)
• >60% Battery charge
Additional suggestions and warnings:
• Make sure you know both your Samsung account info and your Google account info. You will need these, for Factory Reset Protection, if something goes wrong and you need to wipe your phone.
• I, also, recommend rooting a clean/wiped/reset phone. This rules out quite a few things that could cause failures or strange behavior during or after the rooting process.
• You WILL lose some speed and battery life. This is not an optimized root. If you are comfortable with that fact, then go ahead. You’ve been warned. Do not complain about it on this thread.
• Install the Samsung drivers even if your computer already seems to have them. Right click and run the .exe as administrator. REBOOT after install. This rules out another potential point of failure.
• MAKE SURE YOU ONLY HAVE YOUR PHONE PLUGGED IN. Make sure there are as few USB devices, as possible, plugged into your computer during the rooting process.
• DISABLE YOUR ANTI-VIRUS
Step 1:
Read EVERYTHING above. Twice.
Step 2:
Open Settings->About Device and scroll down to “Build Number”. Tap it repeatedly until it says you have activated “Developer Mode”.
Step 3:
Open Settings->Developer Options and turn ON both “USB Debugging” and “OEM Unlock”.
Step 4:
Turn phone OFF. Once off, hold (Volume Down, Center Home, and Power) until you see a blue warning screen.
Step 5:
Press Volume Up and plug your phone into your computer. You should have blue screen that says “Downloading”.
Step 6:
All of the files should be downloaded to your computer and be sitting in your “Downloads” folder. Un-zip the ODIN-modified.zip, right click the ODIN .exe, and run as administrator.
IF YOU DON’T SEE A BLUE BOX AT THE TOP LEFT OF ODIN THEN DO THESE STEPS AGAIN:
1. Run the Samsung USB Drivers .exe again.
2. Reboot your computer.
3. Make sure your data cable isn’t damaged and is plugged in all the way.
Step 7.
Select AP and choose the ENG Boot file ending in .tar. Then click “Start”. The blue box should eventually turn green and say “PASS”.
IF YOU GET STUCK IN A BOOT LOOP:
“If your phone ends up in a bootloop (which most likely will), you will need to do a factory reset. To do this, hold down Volume Down, Center Home, and Power buttons together until your phone resets then quickly switch the Volume Down to Up key while holding the rest of the buttons down until you see “Recovery booting” at the top-left of the screen. If you mess up, don’t worry you can keep trying until you get it right. Once in stock recovery, choose “Wipe data/factory reset” then “yes” to do a factory reset. THIS WILL ERASE EVERYTHING ON YOUR PHONE! Reboot and after 5-10 minutes, you should be welcomed by a welcome screen, go ahead and login.”
Step 8:
Go through the set-up screens until you can repeat Steps 2 & 3.
Step 9:
Unzip fastboot.zip to its own directory. Unzip the contents of SuperSU and copy them to the fastboot folder.
Step 10:
Shift-RightClick in the white space below the files in the fastboot folder. Click “Open Command Window Here”.
Step 11:
Type the following in the Command Prompt:
Code:
adb devices
Code:
root.bat
Watch your phone for any messages and make sure to tap OK. If it freezes, unplug your phone, plug it back in, and restart from Step 10.
Step 12:
Install BusyBox from the app store. Open the app and make sure it installs to “/system/xbin”. DO NOT INSTALL IT ANYWHERE ELSE. THIS WILL CAUSE PROBLEMS AND REQUIRE A FLASH AND RE-ROOT.
Step 13:
You are now successfully rooted. Read the rest of this post carefully to fix the following items:
WiFi password reset
SecurityLogAgent
General Lag and other issues.
TO UNROOT - CLICK BELOW
Link to Instructions Provided By (jembot)
WARNING:
DO NOT uninstall "SecurityLogAgent", DO freeze it using Titanium Backup. Uninstalling it seems to cause instability and random system crashes.
DO NOT attempt to update SuperSU BINARY UPDATE:You can update to v2.76 from v2.74 with the provided file (updating the app is also ok) after root. Other attempts to update will break WiFi, Cellular Data, Access to the Play Store, and will require a reflash in ODIN to regain functionality.
If you do accidentally do this, just reflash to PI2 firmware and check for OTA updates, or use the update packages, to bring your device back to PL1 Firmware. It will lag a lot, so be patient.
FIRMARE AND PACKAGE DOWNLOAD LINKS
PI2 Firmware Download Password: G891AUCS2API2_FULL_FSFD (Cost me $10 lol)
PG7 Firmware Download
PG7 to PH1 Update
PH1 to PI2 Update
PI2 to PK2 Update
PK2 to PL1 Update
PI2 to PL4 Update
PK2 to PL4 Update
PL1 to PL4 Update
SuperSU v2.74
SuperSU v2.76
Modified ODIN
Unlock boot.tar for PL1 or earlier (credit activefan01)
Original boot.tar for PL4 (use if updating to nougat)
imsservice.apk (use to remove VoLTE and RCS icons)
Fastboot (bundle used in the rooting tutorial)
Samsung Official USB Drivers v1.5.40
Other Issues and Solutions:
If you get and MD5 error:
Your download for the tar file was probably incomplete or corrupt. To fix, re-download and make sure it downloads completely before trying again.
If ODIN does not recognize the file or doesn't display it in the browser:
The file should end in a .tar extension, not a .MD5 extension. Use THIS tutorial to show file extensions in windows(if you can't see them), and make sure the file ends in .tar
If you still experience significant lag or battery usage:
1. Try any of the suggested CPU governor apps on this thread.
2. I, personally, noticed the biggest improvement with Device Control [root] from the play store
3. Enable - Power Efficient Workqueue
Enable - LCD power reduce
Core Limits - 1593 MAX - 307 MIN and Lock Frequencies
Governor - Interactive and Lock Governor UPDATE: "PERFORMANCE" seems to work significantly better at removing lag and, surprisingly, saving battery
Enable - Automatic FStrimming
Enable - Core Control and MSM-Thermal
Enable - Reapply on boot with a 15 second delay
4. Under developer options, consider setting all of the animation speeds to 0
5. As always, you are responsible for any damage to your device or data
For those of you who want Xposed:
1. Install Flashfire from the Play Store
2. Put these 2 files on your phone FRAMEWORK and APK
3. Use Flashfire to flash the zip to your phone.
4. Install the APK and Reboot.
5. Enjoy
6. Avoid these modules or risk bricking your phone:
- Gravitybox - Confirmed
- Xblasttools - Confirmed
For those of you who want to Tether/Hotspot:
1. Install XTether in Xposed
2. Activate and Reboot
3. The native hotspot/tether options will now work in settings
4. Enjoy more.
If you have issues with AT&T keeping you from setting up your phone:
1. Make sure you connect to WiFi on first step of the Samsung setup
2. Do the normal setup until you get to the AT&T Setup portion
3. Let the setup "scan" for connections on WiFi
4. Dismiss the warning about limited WiFi and turn the WiFi OFF
5. Proceed with the rest of the setup by hitting NEXT or SKIP when available
6. You should now be able to use your phone and should be able to setup all AT&T related software separately.
To fix WiFi password reset issue:
1. Install BuildProp from the Play Store
2. Change the value of ro.securestorage.support=false
3. Save, reboot, enter WIFI password for the last time!
How to remove the VoLTE and RCS(hurricane looking thing) icons: (tested by FtaWolf)
1. Install a file explorer like FX
2. Set Read/Write access to System Partition, use the 3 dot menu in the top right
3. (be careful not to touch anything else, I soft-bricked my phone twice on accident)
3. Navigate to /system/priv-app/imsservice
4. Rename file imsservice.apk to imsservice.apk.bak, tap and hold to rename
5. Copy THIS file into the same folder
6. Then set permission to 644, again, tap and hold to change permissions
7. Reboot and you should be good to go.
How to add HotSpot and MobileData toggles or remove unwanted toggles (credit slimshouki)
1. Install CSC Feature Expert from the PlayStore
2. Scroll down until you find "Config Def Quick Setting Item" (Do not search for it, you wont find it)
3. Add " ,WiFiHotspot,MobileData"
4. (OPTIONAL) Delete any toggles you don't want. Make you there is a single comma between all values
5. Open Settings->Personal->Backup and Reset->Reset Settings
6. After it reboots you should see the toggles.
COMPATIBILITY STATUS:
Galaxy S7 & S7 Edge Qualcomm Variant Root: Confirmed Successful On: PG7, PH2, PI2, PK2, PL1 || Fails On: PL4, Android 7.0 Update
Poot Debug APK Qualcomm Root: Incompatible
Dirty Cow Exploit: Temp/Partial Root
TO DO:
Determine Root Method/Source (activefan01, perhaps you can weigh in)
Custom Recovery (if possible)
Optimize Current Root Method (currently takes a decent toll on battery life)
7.0.0+ Root (currenty only works on pre-nougat systems)

If no one has any answers on the availability of a functioning root for the Samsung Galaxy S7 Active, can some one tell me why the Active series of phones seem to be actively ignored? Is there an extreme difference in hardware? Is it difficult for devs to get their hands on the device? Is there not enough interest?

The basic gist with the Active line is: nobody really cares in terms of development because they're just not popular devices in terms of sales. They're better devices, in my opinion, but that doesn't mean much to anyone else obviously.
Root would be nice to muck around with I suppose, be able to do some more things, run some root-required apps and so on but, I can live without it so far.
The fact that there is no working firmware available from AT&T or Samsung anywhere could have something to do with it as well perhaps. I've been looking for a pure stock image just in case I have issues but so far it's just non-existent and probably always will be unavailable.
The Active models are great devices, just not popular to the majority of buyers unfortunately and that immediately translates into not being popular with developers or the community in general. I'm getting 2.5 days of battery life per charge with at least 7 hours of SOT with this one I have now so I'm a happy camper without any complaints.

br0adband said:
The basic gist with the Active line is: nobody really cares in terms of development because they're just not popular devices in terms of sales. They're better devices, in my opinion, but that doesn't mean much to anyone else obviously.
Root would be nice to muck around with I suppose, be able to do some more things, run some root-required apps and so on but, I can live without it so far.
The fact that there is no working firmware available from AT&T or Samsung anywhere could have something to do with it as well perhaps. I've been looking for a pure stock image just in case I have issues but so far it's just non-existent and probably always will be unavailable.
The Active models are great devices, just not popular to the majority of buyers unfortunately and that immediately translates into not being popular with developers or the community in general. I'm getting 2.5 days of battery life per charge with at least 7 hours of SOT with this one I have now so I'm a happy camper without any complaints.
Click to expand...
Click to collapse
I'm only getting 4hrs of sot..... Hmm

I don't use cellular except when I'm out and about, I use about 40-45% brightness or less (auto brightness when out and about), I have roughly 155 packages disabled with Package Disabler Pro, that's about it.
With a 4000 mAh battery, the GS7A better last as long as mine is lasting or something is absolutely wrong I'd say - it's not that hard to get this kind of battery life and usage but as always YMMV.

I am also searching for root. I got some link in google search, but they are not working. I bought this unlocked device in India. While it works fine with old network, but it does not work with new network which are purely 4g and use voice over LTE for calls.
Sent from my SAMSUNG-SM-G891A using Tapatalk
---------- Post added at 02:13 PM ---------- Previous post was at 02:12 PM ----------
I need to put Indian CSC on this phone.
Sent from my SAMSUNG-SM-G891A using Tapatalk

br0adband said:
I don't use cellular except when I'm out and about, I use about 40-45% brightness or less (auto brightness when out and about), I have roughly 155 packages disabled with Package Disabler Pro, that's about it.
With a 4000 mAh battery, the GS7A better last as long as mine is lasting or something is absolutely wrong I'd say - it's not that hard to get this kind of battery life and usage but as always YMMV.
Click to expand...
Click to collapse
Would you be willing to compile a list of all the packages you disabled? Maybe then I can get better battery life.
Sent from my SAMSUNG-SM-G891A using Tapatalk

Here's the list as XML and it's attached as well for import to Package Disabler Pro:
Code:
<importExportSetting>
<disabledPackages class="java.util.ArrayList">
<string>com.mobeam.barcodeService</string>
<string>com.monotype.android.font.rosemary</string>
<string>com.matchboxmobile.wisp</string>
<string>com.sec.android.widgetapp.samsungapps</string>
<string>com.samsung.android.app.galaxyfinder</string>
<string>com.sec.android.app.chromecustomizations</string>
<string>com.samsung.android.app.aodservice</string>
<string>com.samsung.svoice.sync</string>
<string>com.drivemode</string>
<string>com.sec.android.app.clipvideo</string>
<string>com.sec.android.devicehelp</string>
<string>com.android.wallpapercropper</string>
<string>com.sec.android.app.wfdbroker</string>
<string>com.att.android.digitallocker</string>
<string>com.samsung.android.app.withtv</string>
<string>com.sec.android.app.safetyassurance</string>
<string>org.simalliance.openmobileapi.service</string>
<string>com.samsung.android.easysetup</string>
<string>com.android.externalstorage</string>
<string>com.sec.android.easyonehand</string>
<string>com.sec.factory</string>
<string>com.cequint.ecid</string>
<string>com.directv.dvrscheduler</string>
<string>com.samsung.android.qconnect</string>
<string>com.amazon.mShop.android.install</string>
<string>com.sec.android.app.tourviewer</string>
<string>com.sec.android.Kies</string>
<string>com.samsung.faceservice</string>
<string>com.monotype.android.font.foundation</string>
<string>com.sec.android.widgetapp.easymodecontactswidget</string>
<string>com.samsung.android.email.provider</string>
<string>com.samsung.android.firmware.tsp</string>
<string>com.google.android.configupdater</string>
<string>com.sec.android.app.billing</string>
<string>com.sec.android.app.minimode.res</string>
<string>com.samsung.android.game.gamehome</string>
<string>com.samsung.android.slinkcloud</string>
<string>com.dti.att</string>
<string>com.dsi.ant.service.socket</string>
<string>com.sec.android.AutoPreconfig</string>
<string>com.sec.android.app.soundalive</string>
<string>com.samsung.android.securitylogagent</string>
<string>com.android.carrierconfig</string>
<string>com.samsung.android.app.watchmanager</string>
<string>com.samsung.android.app.assistantmenu</string>
<string>com.locationlabs.cni.att</string>
<string>com.samsung.SMT</string>
<string>com.samsung.aab</string>
<string>com.samsung.vvm</string>
<string>com.sec.android.ofviewer</string>
<string>com.samsung.hs20provider</string>
<string>net.aetherpal.device</string>
<string>com.sec.att.usagemanager3</string>
<string>com.dsi.ant.sample.acquirechannels</string>
<string>com.samsung.android.smartface</string>
<string>com.android.mms</string>
<string>com.android.backupconfirm</string>
<string>com.sec.android.app.SecSetupWizard</string>
<string>com.hancom.office.editor.hidden</string>
<string>com.sec.bcservice</string>
<string>com.android.calendar</string>
<string>com.samsung.android.providers.context</string>
<string>com.sec.android.preloadinstaller</string>
<string>com.sec.android.uibcvirtualsoftkey</string>
<string>com.samsung.android.sdk.professionalaudio.utility.jammonitor</string>
<string>com.android.sharedstoragebackup</string>
<string>com.yellowpages.android.ypmobile</string>
<string>com.samsung.android.app.colorblind</string>
<string>com.android.printspooler</string>
<string>com.android.dreams.basic</string>
<string>com.att.myWireless</string>
<string>com.sec.android.app.dictionary</string>
<string>com.samsung.android.app.talkback</string>
<string>com.samsung.android.game.gametools</string>
<string>com.asurion.android.mobilerecovery.att</string>
<string>com.sec.smartcard.manager</string>
<string>com.sec.allsharecastplayer</string>
<string>com.samsung.app.slowmotion</string>
<string>com.samsung.android.smartcallprovider</string>
<string>com.directv.promo.shade</string>
<string>com.dsi.ant.plugins.antplus</string>
<string>com.samsung.android.personalpage.service</string>
<string>com.samsung.advp.imssettings</string>
<string>com.samsung.android.app.advsounddetector</string>
<string>com.sec.android.app.clockpackage</string>
<string>com.samsung.android.app.mirrorlink</string>
<string>com.samsung.android.sm</string>
<string>com.sec.android.widgetapp.locationwidget</string>
<string>com.google.android.apps.walletnfcrel</string>
<string>com.samsung.android.controltv</string>
<string>com.samsung.mdl.radio</string>
<string>com.sec.spp.push</string>
<string>com.dsi.ant.server</string>
<string>com.samsung.android.gamepad.service</string>
<string>com.samsung.android.allshare.service.fileshare</string>
<string>com.synchronoss.dcs.att.r2g</string>
<string>com.sec.android.mimage.photoretouching</string>
<string>com.samsung.android.universalswitch</string>
<string>com.samsung.helphub</string>
<string>com.sec.android.app.sns3</string>
<string>flipboard.boxer.app</string>
<string>com.google.android.feedback</string>
<string>com.google.android.apps.photos</string>
<string>com.android.managedprovisioning</string>
<string>com.sec.android.providers.tasks</string>
<string>com.ubercab</string>
<string>com.monotype.android.font.chococooky</string>
<string>com.android.dreams.phototable</string>
<string>com.samsung.safetyinformation</string>
<string>com.facebook.katana</string>
<string>com.samsung.app.highlightplayer</string>
<string>com.sec.android.app.vepreload</string>
<string>com.android.providers.partnerbookmarks</string>
<string>com.cleanmaster.sdk</string>
<string>com.samsung.android.keyguardwallpaperupdator</string>
<string>com.android.wallpaper.livepicker</string>
<string>com.samsung.android.beaconmanager</string>
<string>com.amazon.mShop.android</string>
<string>com.samsung.android.app.FileShareClient</string>
<string>com.facebook.system</string>
<string>com.sec.android.soagent</string>
<string>com.samsung.android.fmm</string>
<string>com.samsung.android.mdm</string>
<string>com.smlds</string>
<string>com.ws.dm</string>
<string>com.samsung.knox.appsupdateagent</string>
<string>com.samsung.android.spayfw</string>
<string>com.samsung.app.newtrim</string>
<string>com.samsung.android.spay</string>
<string>com.sec.hearingadjust</string>
<string>com.samsung.android.dlp.service</string>
<string>com.samsung.android.bbc.bbcagent</string>
<string>com.samsung.android.voicewakeup</string>
<string>com.sec.android.splitsound</string>
<string>com.wssnps</string>
<string>com.samsung.android.app.watchmanagerstub</string>
<string>com.policydm</string>
<string>com.samsung.android.app.FileShareServer</string>
<string>com.enhance.gameservice</string>
<string>com.americanexpress.plenti</string>
<string>com.sec.svoice.lang.es_US</string>
<string>com.lookout</string>
<string>com.samsung.android.sm.provider</string>
<string>com.monotype.android.font.cooljazz</string>
<string>com.android.bluetoothmidiservice</string>
<string>com.facebook.appmanager</string>
<string>com.samsung.voiceserviceplatform</string>
<string>com.samsung.aasaservice</string>
<string>com.samsung.android.allshare.service.mediashare</string>
<string>com.sec.android.app.mt</string>
<string>com.sec.knox.switcher</string>
<string>com.qualcomm.atfwd</string>
<string>com.sec.android.app.magnifier</string>
<string>com.samsung.android.video</string>
<string>com.amazon.kindle</string>
</disabledPackages>
</importExportSetting>

Thank you. I'm going to mess around with it later.
Sent from my SAMSUNG-SM-G891A using Tapatalk

Here first run with sot with S7 Active.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SAMSUNG-SM-G891A using Tapatalk

FtaWolf said:
Here first run with sot with S7 Active.
Click to expand...
Click to collapse
That's awesome, really it is, but what does that have to do with this thread and rooting it?

br0adband said:
That's awesome, really it is, but what does that have to do with this thread and rooting it?
Click to expand...
Click to collapse
Not thing. What did disabled package pro have do with thread. You didn't ? It.
Sent from my SAMSUNG-SM-G891A using Tapatalk

Back On Track
While I agree the S7 Active is a fantastic phone with fairly substantial battery life, those merits should be discussed in another thread such as HERE. The main goals of this thread are:
1. Determine if there is an available Root for the Samsung Galaxy S7 Active
2. Determine if any current exploits, for other models, could be modified to Root the S7 Active
- The Galaxy S7 (snapdragon model) Root
- Dirty Cow
- etc.
3. To offer help or a reward to anyone willing to make progress on this topic.
I personally am wiling to donate $50+ to anyone able to provide a legitimate root (or to a charity of their choice).
Please let me know if there is an official way of presenting a bounty or if there is any other way I can help progress this project.

I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system

-snip-

Poot
Is there any evidence that the POOT generic Qualcomm root would work on the Galaxy S7 active?

NotSoMiniGun said:
Is there any evidence that the POOT generic Qualcomm root would work on the Galaxy S7 active?
Click to expand...
Click to collapse
Most likely not as that is an old method. You could try the method mentioned a few posts up.
Sent from my SAMSUNG-SM-G891A using Tapatalk

first of all, I apologize for my "English", I had to use google translator.
I am edu present, I'm from Argentina, and was looking for information on how to root the s7 active, no luck, but I found information that perhaps more experienced people can help them find a solution ....
Qualcomm Quadrooter Exploit
QuadRooter Android sounds like another serious security exploit. Which one can allow a malicious app Apparently to gain root access based on Qualcomm Android phones and tablets, enabling the app to do pretty much what Then it pleases. , According to Check Point, the research group discovered That QuadRooter, up to 900 million Android devices Qualcomm Could be AFFECTED. This exploit targets the drivers Qualcomm Which is why it is specific to this hardware. As of the 1st Augusts security update Google has patched 3 of the 4 will patch vulnerabilities and the last one in the September 1st update. To keep your device safe from bugs it is always in Original bests to stay on top of your security updates. One of the best ways to protect your phone from malicious software is to download apps only from trusted sources or google play.
If you want to check and see if your device can possible be vulnerable to this threat Then you can download and run QuadRooter Scanner by check point. Personally I am hoping That a developer can figure out this exploit and use it to get many android users root access. I am sure someone can create a app gets root then a INJECTS That SuperSU and their binary into the device. If you are hoping for the same I recommend not updating to new security patches and give the developers some time to get root access devices.
I would not be surprise to see this QuadRooter vulnerability Implemented into Kingroot app some time soon, as it would make there app on Android devices unstoppable. What do you think about this bug please comment below and let me know.
This information I found in rootjunky.
I hope you can serve something
---------- Post added at 01:58 AM ---------- Previous post was at 01:45 AM ----------
rahuldixit2010 said:
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
Click to expand...
Click to collapse
how did it go?

I tried it but not got success.

rahuldixit2010 said:
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
Click to expand...
Click to collapse
That's awesome! Now, who is familiar with Linux... can dump boot.img and kernel.img from the phone...
I found that it's here:
cd dev/block/platform/soc/624000.usfshc/by-name/
dd if=/dev/block/sda6 of=/sdcard/efs.img
dd if=/dev/block/sdd10 of=/sdcard/aboot.img
dd if=/dev/block/sda13 of=/sdcard/fota.img
dd if=/dev/block/sda16 of=/sdcard/modem.img
dd if=/dev/block/sda17 of=/sdcard/boot.img
dd if=/dev/block/sda18 of=/sdcard/recovery.img
I don't know, will these comands work in linux?

Related

[n00b Guide] Your USA T-Mobile Defy: Rooting, Roms, and fixing 3G

Disclaimer: I make no warranties expressed or implied. This information is provided for research and educational purposes only. By reading this post, you agree not to hold me, my estate, my heirs, or my dog responsible for anything ever and waive all of your rights to legal action against said parties forever in perpetuity. Amen.
Note: this guide covers Android 2.1 (Eclair). Various builds of Android 2.2 (Froyo) are available in the forum. You should NOT use my guide if you are installing a build of Android 2.2 (Froyo). Currently I am running the Jboogie Froyo Rom, Orange DeBlur v4, which is great and (in my opinion) the best Froyo Rom out there for USA T-Mobile. Froyo is not much faster than Eclair in terms of benchmarks, but the apps are better, especially if you need the Android email app for connecting to an exchange server.
Now, on to the guide:
Goal: starting with a fresh-out-of-the-box Defy from T-Mobile USA, root the phone, install a non-US (or other) Rom, and recover your 3G capabilities.
Why: non-US Roms have much less bloatware from T-mo and Motorola, and allow you to install JIT/Deodex if you want
0) Oh noes! You've got to sign up for a Motoblur account just to use your phone! Create a throwaway email address at any of the webmail providers (gmail, yahoo etc.) and then go through the motions on the phone to set it up and get to the main home screen. Editorial note: wtf!!!
1) Get root access to your phone. Following Sorensiim's excellent guide, download the Z4Root app, which allows you to root (and unroot) your Defy. (thanks to Sorensiim for hosting!)
>> n00b notes:
First, go to Settings -> Applications and check "Unknown Sources" so you can run the Z4Root app.
Also go to Settings -> Applications -> Development and check "USB Debugging" so you can connect to your phone from your computer later.
Then open your phone's browser, navigate to this page, and download the app directly to your phone.
Install the app from your "Downloads" folder (accessible inside your Browser)
Run the Z4Root app on your phone, hit the "root" button and wait for it to work its magic.
This is what you will see if you run Z4Root after you reboot from rooting:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Install recovery so that you can make a backup of your operating system to your SD card before you do anything else - that way you can go back to the stock T-mobile OS if you need to.
Following Sorensiim's excellent guide, and many thanks to tenfar who put it together for us, just go here to download the Recovery App. (thanks to Sorensiim for hosting!)
>> n00b notes:
Just like before, visit this page on your phone's browser. Click the link to download the recover app, and once it's done, install it.
Allow the app to have root access, and check the box to always allow.
Once you are in the System Recovery program, click "Install Recovery System"; it will let you know when it's successfully installed (see image below):
3) Make a backup by opening the System Recovery app, and then press the "Recovery Boot" button. Back it up! Once again, details here, big thanks to tenfar!
>> n00b notes:
Once you have booted into recovery, you'll see the black/green screen shown below.
Use the volume buttons to navigate the menu and the power button to select an option.
Go to "Backup and Restore", and then "Backup".
If you need to restore later, just do the same thing except hit "Restore" and then select the one you want.
4) Flash a different ROM! Now here's where it get's a little more tricky. First, you'll want to follow Higgsy's Debranding Guide closely. I won't repeat his excellent guide, but here are my comments on the steps in the guide:
>> n00b notes:
Technically this step is optional - you can still weed out the bloatware and overclock while keeping your stock USA ROM. However, you will miss out on being able to install JIT/Deodex and having other features of non-USA roms, such as tethering.
Step 1: I used the consumer drivers package - Motorola 4.8.0 Driver with MotoConnect - since I am using 64 bit Windows 7. You can also use the developer drivers that Higgsy links to in his guide (available here).
Step 2: I used the JRDNEM_U3_2.34.1 firmware from central Europe, since you don't have to deal with Motoblur that way. You don't have to use this Rom of course, there are a bunch of different options, but I wanted to stick with a "real" Rom from Motorola as a starting point. Note that a firmware version is not the same as an Android version - i.e. v2.34.1 is NOT android 2.3, it is still anroid 2.1. Confusing, I know. Other Rom options include custom Roms that people put together and list in the XDA Developers forum. If you want to use one of those, you would follow their instructions for installing that particular custom Rom.
Step 3: In case the RSD Lite download link in the guide doesn't work, you can also get it from Megaupload the password for the site and the rar file is 'alabama'.
Step 7: Before booting the phone into the bootloader, you may want to clear out your data manually (aka "wipe your phone"). Go back into the System Recovery app, go to "Recovery Boot", and then when you're back on the black screen, select "Wipe DATA/Factory reset", "Wipe CACHE Partition" and then also go to "Advanced" and then select "Wipe Dalvik Cache". Then hold down the power button to turn off your phone. You won't be able to boot your phone after this, except by holding down the volume up + power on buttons together to get into the bootloader, so I would make 100% sure you have the drivers and RSD Lite installed and working!
Step 8: I would recommend waiting until it says "PASS" on the right side of the RSD Lite window before closing the program (this is after the "PLEASE START PHONE MANUALLY" phase is completed).
You should now have a working phone, with EDGE connectivity (little "E" in your status bar at the top) but no 3G or H icons. What, no 3G? We'll fix that next.
5) Re-root your phone and reinstall System Recovery following steps 1 and 2 above.
6) Install JIT/Deodexed: Optional step if you flashed either the 2.21 or 2.34 ROM. If you want to make your phone a bit faster, this is for you. Higgsy's guide is here if you want to do this!
>> n00b notes:
Update: on my third time flashing the phone, I was able to get JIT/Deodexed working fine. I think my failure the first time may have been due to my old SIM card, which I replaced because I was having problems reading the card and sending text messages (couldn't update the SMSC number).
Originally, I couldn't get the JIT/Deodexed package to work on my USA phone after installing the 2.34.1 firmware (too many 'untoward things happening' like Higgsy warned about), so I just skipped it the second time I flashed the 2.34.1 firmware.
The process of installing the packages is super easy, although you may want to make a backup before you start just in case. You can never have too many backups, because you can always transfer them to your computer if your SD card gets full. They are stored on your SD card under /goapkrev/backup/
The performance improvements are substantial - see graphs below.
Obviously you must get the package that matches the version of the ROM you installed. If you didn't flash a new ROM and still have the stock USA one, you are out of luck.
7) Make another backup! Now you want to backup your freshly-installed (and possibly JIT/Deodexed) Non-US Rom. Your first backup was the USA T-mobile Rom. You'll want to make this backup in case you eff something up in one of the next couple steps and want to go back to a fresh Non-US install and try-again.
Following the instructions in Step 3 above, load the System Recovery app, Recovery Reboot, and make a backup. Then reboot your phone!
8) Install ADB and/or Android SDK on your computer - there is a great guide on the Cyanogen Mod Wiki here. Just go slow, and follow the instructions. Once you can do "adb devices" and see your phone, you're good to proceed onward.
>> n00b notes:
To open a Command Prompt in Windows, go to "start" -> "run" and type "cmd" in the box or just go to "start" -> "all programs" -> "accessories" -> "command prompt").
Note that if you have 64-bit windows, you'll still need to install the regular 32-bit Java Development Kit (JDK), not the 64-bit version.
When you're editing your "path" environment variables in windows, note that you can't have spaces before or after semicolons. This is what my full path looks like (and iTunes works now - it didn't when I accidentally left a space after QTSystem\;
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\;[B]%SystemRoot%;C:\Program Files (x86)\Android\android-sdk-windows\platform-tools;C:\Program Files (x86)\Android\android-sdk-windows\tools[/B]
9) Fix 3G
*** NOTE: This step only applies to USA phones. If you're not in the USA, your 3G probably works fine.
Download HandlerExploit's 3G fix from the 2.21 UK ROM or my 3G fix from the 6.19 US ROM. Thanks to HandlerExploit for figuring this out for us.
>> n00b notes:
There's not much difference between the two 3G fixes, except that each one will display different info in the "About Phone" section (either v2.21 or v6.19). For example, if you use my fix, "About Phone" will tell you that you have "Build number: JORDN_U3_6.19.0" installed - this is a side affect of the patch. For HandlerExploit's fix, "About Phone" will report v.2.21 GB
You may want to write down what Rom you actually installed if you think you might forget (for example, my phone actually has "JRDNEM_U3_2.34.1" even though it reports 6.19.0 in "About Phone")
If you downloaded HandlerExploit's 3gFix, you can choose to follow his instructions or the ones below, which are basically the same as what is in his, except you enter the commands line-by-line instead of running them through a script. I prefer line by line because I like to know what I'm doing. Both methods should work fine.
If you are unfamiliar with basic command prompt commands (cd dir ls etc.) please see my reply later in this thread
Once you download the zip file, extract it somewhere, like your desktop.
Alright, time to get some ADB skills. Plug your phone in via USB and open a command prompt. First we connect to the phone by typing this, each command followed by the "Enter" key:
Code:
adb shell
Then you want to run some commands as a super user so type:
Code:
su
Quick! Look at your phone, and tell it to always allow superuser access. You only have to do this once.
You should have a "#" command prompt now (instead of a "$" like before) indicating that you are working as a superuser (#=superuser). Now some more commands to enter. (n00b tip: you can copy and paste each line into the command prompt by copying the line from this guide and right clicking "paste" on the command prompt window)
Code:
mount -o remount,rw -t ext3 /dev/block/mmsblk1p21 /system
chmod 0777 /system/etc/motorola/bp_nvm_default
chmod 0777 /system/etc/motorola
chmod 0777 /system/etc
chmod 0777 /system/app
chmod 0777 /system/lib
chmod 0777 /system/lib/modules
chmod 0777 /system
exit
exit
So now we have set CHMOD Permissions for some folders on your phone, and then quit the adb shell. Now we've got to push some files to the phone:
Navigate to the folder where you extracted the files from the 3g fix you downloaded above, for example, type:
Code:
cd c:\users\administrator\desktop\3gfix\
then enter:
Code:
adb push system /system
This will copy all the files in the subfolder "system" to your phone's "/system" folder, overwriting them (which is why we made a backup earlier). Then enter:
Code:
adb reboot
to reboot your phone. You should have 3G connectivity now - note that it may take up to a minute or so for it to appear the first time, and you may not see the icon at all if you have WiFi enabled (so disable it in your settings to test it out).
If it still doesn't work, try going to "Settings" -> "Wireless & Networks" -> "Mobile Networks" -> "Access Point Names" -> (settings button of four squares) -> "Reset to default". Also make sure the APN name is highlighted with a green dot. You may also have to go to "Settings" -> "Wireless & Networks" -> "Mobile Networks" -> "Operator Selection" -> "Select Automatically"
This is what the 3G icon looks like of course:
10) The phone is yours. You can:
Install some apps: Titanium Backup & Launcher Pro for example.
Weed out the bloatware, overclock, and scale: see Sorensiim's awesome guide here. I highly recommend doing this, just bumping up to 1000mhz overclock makes the phone's performance much more snappy. If you overclock, you should definitely use Sorensiim's scaling method and his scaling files -- it makes a very noticeable improvement in battery life.
Benchmark your phone: with Quadrant Standard Edition, available in the app market
Play Angry Birds all day: :-D
Here is my phone benchmarked, with no overclocking, no bloatware removal, no JIT/Deodex packages, just the stock JRDNEM_U3_2.34.1 firmware (note that the phone with the US Rom straight out of the box benchmarks a little higher at 987. I'm not sure why this is.):
Here it is after overclocking to 1000mhz and my own customized bloat removal (not as much as most people, i use some of the default apps), also still no JIT/Deodex. Obviously you can get it to go faster if you want to overclock more, install JIT/Deodex, and remove more bloat:
Edit: These are the apps I disabled for the second benchmark (renaming them using Sorensiim's guide )
AdService.apk
ArcPhotoworkshop.apk
ArcVideoEditorLite.apk
esmusica_2_0_0012_embed_Signed_2010-04-13_11-05-17.apk
FBAndroid-1.3.2.apk
Fota.apk
hiphopofficial_2_0_0012_embed_Signed_2010-04-13_11-08-31.apk
Kindle-1.0.2-OEM-SingleSign.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
MySpace.apk
Protips.apk
Quickoffice_BasicViewer_2.0.52.apk
revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.apk
truecountry_2_0_0012_embed_Signed_2010-04-13_11-06-12.apk
WeatherWidget.apk
Here is what I got to after JIT/Deodexed was installed on 2.34 - same apps removed, same overclock at 1000mhz. Removing VisualizationWallpapers.apk and YouTube.apk got me to 1308.
Wow, great guide! I might try this later.. I do have a question though, if we've already set up our phones on a stock rom, can Titanum Backup or the recovery backup our apps and settings and then restore them to our new deblured ROM?
Sent from my MB525 using XDA App
Passa91 said:
Wow, great guide! I might try this later.. I do have a question though, if we've already set up our phones on a stock rom, can Titanum Backup or the recovery backup our apps and settings and then restore them to our new deblured ROM?
Click to expand...
Click to collapse
Yes, you would do that with Titanium Backup. System Recovery is for making entire images. It's easier to replace things piece-by-piece with Titanium Backup.
Thanks for this...along with handler's tips on SA I got it working.
Although I´m not an US user (hence got working 3G) I´m still on the 2.34.1 ROM, and I still use som of the default apps.
Just wondering though: which ones did you remove? I´m not going to get into ADB, but I was thinking of removing some of ´em with TB.
Slightly OT - can you safely remove Swype? There´s no swedish language support for that, and I´ve gotten used to TouchPal anyway...
heglen said:
Although I´m not an US user (hence got working 3G) I´m still on the 2.34.1 ROM, and I still use som of the default apps.
Just wondering though: which ones did you remove? I´m not going to get into ADB, but I was thinking of removing some of ´em with TB.
Slightly OT - can you safely remove Swype? There´s no swedish language support for that, and I´ve gotten used to TouchPal anyway...
Click to expand...
Click to collapse
Sure you can remove Swype, theres still the standard android keyboard installed as well. Check out scandinavian keyboard from the market too
I had a big problem in step #8, installing ADB. No matter what I tried, the command "adb devices" would not work. But I was able to solve it by following this:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
You have to download the ADB files from
http://www.megaupload.com/?d=RTEY0Q97
and put them into your
Android\android-sdk-windows\tools
directory. Word is, they were taken out by Google for whatever reason in the R08 version, and must be restored in order for ADB to work.
After I extracted the files into the Tools folder, and used the 'adb devices' command, it worked like a charm!
Quick noob question.
If I install a custom ROM on my Defy following this guide and then restore the T-mo US 3G connectivity - will I be able to use the "Web2 go" unlimited plan without being detected and blocked by T-mo? Currently as I have the stock firmware/ROM it does not let me connect to neither 3G nor Edge. I've tried my SIM with Nokia N900 and 3G works fine, since the T-mo network doesn't recognize it as a smart phone. Please let me know if de-bluring/debranding my Defy will solve this problem for me.
Thanks in advance.
nvvass said:
If I install a custom ROM on my Defy following this guide and then restore the T-mo US 3G connectivity - will I be able to use the "Web2 go" unlimited plan without being detected and blocked by T-mo?
Click to expand...
Click to collapse
Why did you buy an android smartphone if you don't have a plan for it? Can't help ya.
rob-t said:
Why did you buy an android smartphone if you don't have a plan for it? Can't help ya.
Click to expand...
Click to collapse
I do have a plan. Many friends' Nexuses work fine with the same plan. I know a guy with a Nokia N900 and it works in 3G even with his grandfathered T-zone for $4.99. Why pay more? You didn't answer my question though - can you give a specific answer? As in "will work" or "won't work".
Thanks.
nvvass said:
You didn't answer my question though - can you give a specific answer? As in "will work" or "won't work".
Click to expand...
Click to collapse
Seeing as how I never had even heard of web2go before your post, I really have no idea. I'm not entirely sure I know what T-zone and web2go even /are/.
If you follow the instructions above and you still can't use your web2go thing, you can always roll back to your first backup and then use Z4root to unroot your phone, effectively returning it to 'stock' condition.
Wifi Calling?
Great tutorial for us noobs! Thanks! How does this affect wifi calling?
rob-t said:
Seeing as how I never had even heard of web2go before your post, I really have no idea. I'm not entirely sure I know what T-zone and web2go even /are/.
If you follow the instructions above and you still can't use your web2go thing, you can always roll back to your first backup and then use Z4root to unroot your phone, effectively returning it to 'stock' condition.
Click to expand...
Click to collapse
I'm sorry I assumed you're familiar with T-mo US, but thanks for responding anyway. Basically, web2go is an unlimited data plan for $10, that T-mo used to provide for "dumb" phones. T-zones was it's previous version (before 3G times) priced at $4.99 and was offered for all phones other than BBs. I remember getting a Dash (T-mo branded HTC Excalibur), witch was one of the first phones T-mo started to call "smart", and was able to get full Inet access with my T-zones just by tweaking some APN settings on the phone. In fact I (and many others) was able to get that without any data plan for awhile, before T-mo caught up with it and started blocking it. Of course it was too slow for browsing (EDGE/GPRS), but you could get your e-mails pretty easily and search stuff when in a pinch. Speaking of that - anybody remember when texting was free? Anywho, at some point in time T-mo started blocking smart phones from accessing data services on a "dumb" data plan - apparently by adding a piece of code to the FW of all T-mo branded phones, that allows their network to recognize the phone as "smart" and then block access if a "dumb" plan is used. Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan. So, I hope this long explanation helps you understand where I was coming from with my original question. Obviously, when you flash the Defy with a non-T-mo ROM you get rid of the piece of code that makes the phone identifiable, but then when you copy part of the original ROM to restore 3G functionality, does that part contain the ID code also, I was wondering. At any rate, if you're not familiar/don't use T-mo you wouldn't know, I understand, I guess I'll have to go through the steps and figure it out for myself. Thanks anyway.
bcrawf68 said:
Great tutorial for us noobs! Thanks! How does this affect wifi calling?
Click to expand...
Click to collapse
WiFi calling seems to work fine for me.
nvvass said:
Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan.
Click to expand...
Click to collapse
Ah OK thanks for the explanation. I currently use T-mobile but I don't really know much about their offerings. I would try the 2.21 or 2.34 firmware and then apply the UK 3G fix made by HandlerExploit, instead of the USA 3G fix I made from the US firmware.
Only one way to really find out though...
Excellent!
Steps 1-8 of your guide are also very helpful for non-US Defy users!
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.
cloogshizer said:
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.
Click to expand...
Click to collapse
Thanks, yes, I updated the guide accordingly. 3G fixing should only be necessary in the USA.
nvvass said:
I'm sorry I assumed you're familiar with T-mo US, but thanks for responding anyway. Basically, web2go is an unlimited data plan for $10, that T-mo used to provide for "dumb" phones. T-zones was it's previous version (before 3G times) priced at $4.99 and was offered for all phones other than BBs. I remember getting a Dash (T-mo branded HTC Excalibur), witch was one of the first phones T-mo started to call "smart", and was able to get full Inet access with my T-zones just by tweaking some APN settings on the phone. In fact I (and many others) was able to get that without any data plan for awhile, before T-mo caught up with it and started blocking it. Of course it was too slow for browsing (EDGE/GPRS), but you could get your e-mails pretty easily and search stuff when in a pinch. Speaking of that - anybody remember when texting was free? Anywho, at some point in time T-mo started blocking smart phones from accessing data services on a "dumb" data plan - apparently by adding a piece of code to the FW of all T-mo branded phones, that allows their network to recognize the phone as "smart" and then block access if a "dumb" plan is used. Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan. So, I hope this long explanation helps you understand where I was coming from with my original question. Obviously, when you flash the Defy with a non-T-mo ROM you get rid of the piece of code that makes the phone identifiable, but then when you copy part of the original ROM to restore 3G functionality, does that part contain the ID code also, I was wondering. At any rate, if you're not familiar/don't use T-mo you wouldn't know, I understand, I guess I'll have to go through the steps and figure it out for myself. Thanks anyway.
Click to expand...
Click to collapse
cloogshizer said:
Steps 1-8 of your guide are also very helpful for non-US Defy users!
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.
Click to expand...
Click to collapse
first of all.. thank's for the great tutorial man..!!
second of all, I got this T-mobile defy from my uncle and I used it in Indonesia.. It's true what nvvass said, that the T-mo firmware constantly tries to connect with the "smart phone" data plan.. which caused me to unable to connect to my local provider data connection.. after I flashed the defy with the central-europe de-blur firmware, Voila..!! I got 3G connection directly..!! without any settings at all..
hope this helps for anyone using US T-mobile defy outsite of US.. cheers mate..
if i have no reception (the signal bars have a red circle with a line through it on top) will this kind of 3g fix but relevant to australia fix the issue?
Jt612 said:
if i have no reception (the signal bars have a red circle with a line through it on top) will this kind of 3g fix but relevant to australia fix the issue?
Click to expand...
Click to collapse
where did you get the phone from? if it from US and still locked with T-mobile, than it would refuse to connect with local provider.. you need unlock code..
i bought it in australia its an australian phone... works fine when i restore my backup of australian software but i would like to use the 2.34.1

[REF} All in One guide for NOOBS with Videos! "WORK IN PROGRESS"

If you just switched from iPhone or BB or this is ur first android. Read this thoroughly and see ur questions get eliminated by this guide. if you find this helpful then show your appreciation and hit that thnx button.
As of now this thread is under construction, I have not seen any noob helper all in one thread & i have always had one for the phone I have. So here it goes for Note 2. Feel free to give me suggestion but keep in mind that I only do this on my free time so this might take while to finish.
I don't take any credit I Googled everything. I do take credit of modifying some stuff in word.
Little in-depth information about Android. Must Read. Thank You Pirateghost.
Pirateghost said:
Android itself is OPEN. you can go and build your very own version of 4.0 ICS right now from source code. there are very few phones you can STABLY and RELIABLY run it on though.
The NEXUS line of phones exists for a reason. they are untouched by carriers (verizon teabagged the Galaxy Nexus a little), and do not have some stupid overlay on them. they are developer devices in that it is the first phone to get android updates straight from google (no manufacturer interference required).
every other phone is tainted with a manufacturer's UI. Touchwiz on Samsung phones (galaxy nexus is a samsung but they provided the hardware not the software), Sense on HTC, 'non-blur' on Motorola, whatever Sony calls theirs...lol, LG, etc
on top of that tainted Android interface is a carrier branding or lockdown (doesnt apply to the entire world, but im only referring to US here)
so google releases new version of Android
manufacturers build phone, and customize android to fit their model (this is where android almost stops being OPEN)
carriers get a hold of the manufacturers build of android and tweak and modify it themselves (more than likely they just tell the manufacturers what they want), as you know they love to include bloat and lock it down from the user
you receive your android phone after it has gone through all those steps....long process huh? we dont get updates to newer versions as quickly because of that long process...and they would rather us buy new phones instead of improving perfectly good hardware.
Android is open in the sense that manufacturers can use it however they wish, within reason. it is not necessarily meant to be 'open' to the average end user, and manufacturers dont want you messing with the phone they built. its the reason XDA is what it is today, albeit with roots deep in WinMo hacking.
Click to expand...
Click to collapse
ADB → Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device..
Android →Unveiled on 5 November 2007, Android is a mobile operating system running on the Linux kernel developed by Google.
AOSP → Android Open Source Project
Apps2SD → Move applications from the internal NAND memory on the device to a removable SD Card.
BLN → BackLight Notification
Bloatware → Software bloat is a process whereby successive versions of apps include an increasing proportion of unnecessary features that are not used by end users, or generally use more system resources than necessary, while offering little or no benefit to its users. Like all the crap that comes from At&t
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware."[
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed.
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Busybox → BusyBox provides several stripped-down Unix tools in a single executable. It runs in a variety of POSIX environments such as Linux, Android, FreeBSD and others, such as proprietary kernels, although many of the tools it provides are designed to work with interfaces provided by the Linux kernel. It was specifically created for embedded operating systems with very limited resources. Platforms counterparts, but they are pretty close and useful nonetheless.
CWR OR CWM ClockworkMod Recovery →A custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
DEODEX → Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace file (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Flashing → The process of applying a firmware image (or ROM) to a device. It generally entails a very specific order of steps. Failing to complete any one of these steps properly may result in bricking the device.
Firmware → is a term often used to denote the fixed, usually rather small, programs and/or data structures that internally control various electronic devices. Programs stored in the ROM, EPROM, or flash memory that usually control various internal electronic devices (Hard Drives, Keyboards, Displays, etc). Firmware is typically 'fixed' software that is not updated in consumer devices, however it is often updated (or 'flashed') by advanced users to fix bugs or add features to the device. Flashing firmware designed for one device onto a different device, or not following a specific procedure while flashing will often render the device unusable.
Kernel → is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components
Radio → The cellular radio on the device which needs control software called firmware to control it.
ROM → Read Only Memory. In the context of an Android device, ROM is the internal flash memory where the core operating system resides. It can also refer to a specific version firmware that can be applied to a device through a process usually referred to as flashing. An improperly flashed ROM can often brick the device, rendering it unusable.
Superuser→ A program, which gives unlimited access privileges to perform any or all operations on the operating system.
ODIN → Odin is the Samsung software used to update Samsung phones. It does not work with any other devices other than official Samsung phones.
OTA or FOTA → (F)OTA stands for (Firmware) Over The Air and is the process by which required updates and enhancements to your phone's basic operating system can be sent to you through the cellular network. The Galaxy S II software update will be sent via FOTA and is available through Samsung Kies mini.0
ODEX → In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
SDK → Software Development Kit.
Logcat → A debugging tool built into Android devices that displays system logs as they occur. See Logcat.
NANDroid → A set of tools that will enable anyone who has root on their Android device to make FULL system backups, in case something goes wrong or you want to try out that new experimental ROM/theme. NANDroid will backup (and restore) /system, /data, /cache, and /boot partitions.
Recovery Mode → A special environment that you can boot into for troubleshooting and upgrading purposes.
Kang → The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
Rooting → is a process that allows users of mobile phones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem with the goal of overcoming limitations that carriers and manufacturers put on some devices.
Credit for this Post goes to TRusselo!!!!
Here is how to do Advance research/help your self + Mods!​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is how to Root Your Note 2 Mac & Windows!​
Root Note 2 on Windows without Tripping Flash counter!!!
Step 1: Download the files Here and unzip them.
Step 2: Do this Only if you want CWM. Connect your phone to computer and copy over CWM recovery.img to your internal sd card. Make sure you do not put that in any folder.
Step 3: Put your phone into down load mod. First Turn off your phone. Then Press Volume down, Power and home button. You will see following screen.
Step 5: Then Press Volume Up and you will see following screen.
Step 3: Open up Odin folder and run Odin3 v1.85 and unselect F. Rest Time.
Step 6: Connect your Note 2 to computer. Once you connect your phone you will see yellow box on upper left corner on Odin.
Step 7: Now Press PDA and browse for the location of the downloaded files. And Select root files that you downloaded and open it.
Step 8: Press Start.
Step 9: Phone will reboot once its done flashing. And you will get Pass on upper left corner.
Step 10: Now download any of the app that requires root permission(titanium back up) and make sure you have root.
Option One: Install CWM Recovery Hard way!
Step 1: Go to your phone and enable usb debugging under setting>developer's option.
Step 2: Connect your phone to your windows computer and open up command prompt.
Step 3: Type adb on your command prompt then you will see all the commands that adb offers.
Step 4: Type adb shell then type su after that type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Step 5: You will see following in your command prompt.
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
13992+0 records in
13992+0 records out
7163904 bytes transferred in 1.672 secs (4284631 bytes/sec)
Step 6: Now Just type " reboot recovery " in command prompt.
Step 7: You now have rooted At&t Note 2 with CWM installed.
Option 2: Flash TWRP Easy Way!
1) Download Goo Manager from Play Store.
2) Open the app & press Menu button. (Make sure to give superuser permission)
3) Press "Install OpenRecoveryScript"
4) Recovery will be downloaded & installed.
5) Once You see message saying Recovery Installed, press boot into recovery.
6) Done you have custom Recovery.
Here is How to Unroot Your Note 2.
fourth for all in one links.
fifth for video reviews.
sixth for themes.
seventh for how to use xda
This order may get changed.
eight for how to flash themes.
Last one
appdroid said:
Last one make sure to hit thnx guys.
Click to expand...
Click to collapse
Getting my Note 2 in a week and I'm new to Android.
If you root can you delete the At&t bloat apps? Or do you have to do something else to get that?
Also is there some option to disable 4G and just go on 3G?
Thanks
used all my thanks!! great write up!!! you always provide us with great information!!!
fxbreaker said:
Getting my Note 2 in a week and I'm new to Android.
If you root can you delete the At&t bloat apps? Or do you have to do something else to get that?
Also is there some option to disable 4G and just go on 3G?
Thanks
Click to expand...
Click to collapse
Rooting will allow you to completely remove an app. You can disable(removes from app drawer and totally deactivates the app) without rooting by doing the following:
Go to setting/applications manager
Select desired app
Will give option to 'disable'
Select disable and the app will no longer run or be visible.
If the option shows 'disable updates' select that then go back and select the app again and it will then let you disable the app.
This method leaves the file on your phone so it doesn't free up any space but it will free up some memory as you will no longer have this 'bloat' running.
Sent from the Millennium Falcon
I Don't know why someone would rate this thread down???
appdroid said:
I Don't know why someone would rate this thread down???
Click to expand...
Click to collapse
Maybe cause every other word you type is "hit my thnx button", "dont forget to hit my thnx button", "I love getting my thnx meter up!"........just a thought.
Maybe folks are confused. Are you trying to ramp up your thanks numbers? Or are you truly trying to help the community. If its the latter you wouldnt or shouldn't care what your thanks meter says.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
For me the best way to get pumped up to do this kind of work is getting thnx. Just little reward that i look forward to when i am done writing all this. It keeps me going. & Its not like I am asking for $$ u know its shows appreciation. May be ppl are getting me wrong, but i love getting thnx specially after long nite of writing.
& question about helping out community? Well in my mind there is no doubt. But i can't speck for others as everyone has there opinion. I been quite for long time on xda, just got note and thought i would do something again that would help my fellow members but i don't think its working out.
cdshepherd said:
Maybe cause every other word you type is "hit my thnx button", "dont forget to hit my thnx button", "I love getting my thnx meter up!"........just a thought.
Maybe folks are confused. Are you trying to ramp up your thanks numbers? Or are you truly trying to help the community. If its the latter you wouldnt or shouldn't care what your thanks meter says.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
appdroid said:
For me the best way to get pumped up to do this kind of work is getting thnx. Just little reward that i look forward to when i am done writing all this. It keeps me going. & Its not like I am asking for $$ u know its shows appreciation. May be ppl are getting me wrong, but i love getting thnx specially after long nite of writing.
& question about helping out community? Well in my mind there is no doubt. But i can't speck for others as everyone has there opinion. I been quite for long time on xda, just got note and thought i would do something again that would help my fellow members but i don't think its working out.
Click to expand...
Click to collapse
To be honest I dont see a problem with your noob guide. Dont misinterpret my reply:thumbup:. If people find your post helpful they will thank you. Regardless if you ask for it not. :beer:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
I appreciate the work done in this thread. and all he is asking for is a thanks in exchange for hours and days of research sounds good to me .goodjob op keep it up
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Gonna take ur words for it cd since i have known u from skyrocket days lol. Ya will stop asking. & do what i do best finish this guide.:silly:
cdshepherd said:
To be honest I dont see a problem with your noob guide. Dont misinterpret my reply:thumbup:. If people find your post helpful they will thank you. Regardless if you ask for it not. :beer:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
appdroid said:
Gonna take ur words for it cd since i have known u from skyrocket days lol. Ya will stop asking. & do what i do best finish this guide.:silly:
Click to expand...
Click to collapse
Ahhhh the skyrocket days. Life was soo simple
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

ZTE U950 - Root, Recovery, ROM (& Google Play)

I AM NOT RESPONSIBLE FOR ANY NEGATIVE IMPACTS OR CONSEQUENCES ON YOUR PHONE IF YOU SO CHOOSE TO USE THIS GUIDE.
I own the ZTE U950 and had realized that there is very little information (in English) on how to do anything beyond stock for this incredible phone. After hours of research and translation I was able to figure out everything needed to get this phone to a "better" state. Since then I - and other XDA members - have been trying to keep the ZTE U950 alive...
ZTE U950 SPECS
NVIDIA TEGRA 3 (1.3MHz)
1GB RAM
4.3" Display (480x800)
5MP Front Camera/0.3MP Back Camera
Android OS 4.0.4
DRIVERS
Here are the "Join Me" drivers so that your PC can recognize the ZTE U950.
KERNEL
Stock - This is the stock kernel's source file.
Custom - This is a custom kernel for stock ROMs that can be OC'd to 2.5GHz.
ROOT
1) Make sure you have USB Debugging Mode and Unknown Sources checked in your phone Settings.
2) Connect your phone to your PC.
3) Download and open Genotools.
4) The program will open, click the 4th tab (last tab on the right).
5) Ensure that your phone is plugged into your PC.
6) Click the 2nd ROOT button.
7) A popup window will appear, press OK.
8) Your phone will then have a popup window, click the "Restore My Data" option.
9) The phone will restart several times, leave it for a few minutes.
10) This is the odd part... The phone will likely not stop restarting, and when you try to click the unlock key for the screen, it will automatically restart. Disconnect the phone. It should continue to restart.
11) Force the phone off.
12) Restart the phone.
13) If you have SuperUser, you are then rooted. If not, repeat these steps.
ROOT - NEW VERSION #1 (UNTESTED!):
1) Download the file here.
2) The instructions read verbatim are, "1 If your phone is not acquired before the ROOT privileges, we choose 1 root [next line] 2 after enter". Which I assume means click root, then enter...
ROOT - NEW VERSION #2 (UNTESTED!):
1) Download the root kit here made for the ZTE U950 (it uses the Chinese recovery), and extract to your desktop.
2) On your phone, go into Settings and enable USB Debugging under Developer options.
3) Connect the phone to your PC (Windows OS should fail to recognize the device).
4) Run either DrvInst_x64.exe or DrvInst_x86.exe. If you are unsure what you have, run both, the wrong one will fail with an error message.
5) After installation, unplug and replug your phone.
6) Go into Device Manager. You should be able to see a "ZTE TD Handset ADB Interface" under the "Android Phone" section. If you don't, reinstall the drivers again.
7). To root, simply run the U950_Root.bat file, and follow the instructions.
RECOVERY (CWM/TWRP)
1) Download the Chinese CWM or English TWRP recovery.img and place it into the root folder of your external SD card.
2) Download a terminal emulator. (If you are unable to download one, use the APP TRICKS described near the bottom to install a terminal emulator onto your phone.)
3) Open the terminal emulator.
4) Type in "su" then hit the return button.
5) Now type in the following:
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
(and press the return button)
6) There should be a few lines beginning with something like 14052 or 14272, if not, then the above input was not typed correctly. If so, the recovery should now be installed.
GET INTO RECOVERY
1) Turn the phone off.
2) Hold the Power button + Volume Down button. When the ZTE logo comes up, count two seconds and then let go of the buttons.
3) The phone will enter into recovery. Use the Volume rockers for up and down and the power button to choose (if on CWM), or simply touch the buttons (if on TWRP).
4) I will describe the standard processes here if using CWM - the menus are top-to-bottom on the phone, which are written left-to-right here:
The Main Menu:
[*] Reboot system now
[*] Select zip to flash/install
[*] Wipe data
[*] Wipe cache
[*] Backup and restore
[*] Flash memory/Format
[*] Advanced setting
[*] Turn off phone
The Zip Menu:
[*] Install from zip
[*] Install from internal
Wipe Date:
[*] Confirm wipe data
[*] Do not wipe data
Wipe Cache:
[*] Confirm wipe cache
[*] Do not wipe cache
Backup and Restore:
[*] Backup
[*] Restore
ROMS (ALWAYS MAKE A BACKUP BEFORE FLASHING ANY ROMS TO THIS PHONE!)
Factory ROMs (in order of release)
U950V1.0.0B02
U950V1.0.0B14
U950V1.0.0B18
U950V1.0.0B22
U950V1.0.0B04
U950V1.0.0B05
Custom ROMs (in no particular order)
6240-jingjian
MIUI3.3.7
CustomRom-B14
DeodexedMIUI3.3.7
EN&CN-MIUI3.3.7-msdfyc4zwg
MIUI3.2.8-ysdfyc4zwg
Signed-121223-MZECN-CookedROM
SignedROM
V2.0.0-Hiapk-XC-iSignFile
12-21ROM
4.2CameraROM
RandROM
MIUI1220
V2-MaunJ
CM10/.1 - HeatSka Edition
This should be listed under ROMS, but I felt that it needed its own section. Ska and I worked on this for quite some time getting all the kinks worked out. We did not create the original version of this unofficial Cyanogenmod port, but the original had many issues and was not maintained after its initial release. All the major problems have been worked out in our HeatSka edition.
The ROM was initially CM10 (4.1.2), but it has been mixed with files that list it as 4.2.2 (CM10.1) under the information section. In either case, it is Jelly Bean! Aside from the fixes we have implemented, there are also numerous tweaks and mods for UI speed, network speed, battery consumption, app installs, and much more. There is almost no theming, just enough to know that this is our enhanced (and better) variation.
The only known issue that may arise is CPU throttling. We have included an app called, "LGP880 Booster". This app will allow a CPU speed boost when turned on, with a temperature threshold to prevent overheating. If you wish to save battery, only enable this app when playing a game or using CPU-intensive apps.
DOWNLOAD: CM10.1/2 - HeatSka
FLASH A ROM
1) Download a ROM.
2) Place the ROM in the root of the phone's SD card.
3) Enter into recovery.
4) Wipe data.
5) Wipe cache.
NOTE: Wipe data and cache are the Factory Reset button in TWRP.
6) Follow the menus to get to the ROM in the SD card.
7) Click the power button to choose the ZIP if on CWM (or just push the designated button on TWRP).
8) The ROM is being flashed.
9) Follow the left arrow (the last selection) on the menus to get back to the main menu.
10) Choose the first option on the main menu to reboot on CWM (or click Reboot followed by System in TWRP).
NOTE I: The ROM will probably be in Chinese. Find the Settings icon and click it. Go down to the Language & Input setting and click it (there is a capital "A" next to it). Click the top setting and choose the desired language.
NOTE II: There may not be an English keyboard available, so download this 4.2 keyboard ZIP file and flash it in recovery.
INSTALL GOOGLE PLAY
1) Download and install a file explorer like ES Explorer (free) or Root Explorer (paid). (If the phone is unable to download a file explorer, use the APP TRICKS described near the bottom to install one onto the phone.)
2) Download and take the three files from the RAR file for Google Play and place them in a folder on the phone that can easily be reached with a file explorer.
3) Open up a file explorer.
4) Move the three files to the "/System/App" folder on the phone.
5) Give the three files each the same permissions (Read for all three groups, and Write for User).
6) Restart the phone and Google Play should now be installed.
Notes: a) There are cases where two Google Play store icons may appear. They should both work and not cause problems.
b) If the store does not show, redo the process above.
c) This trick does seem to work on other Android devices as I have successfully done this on a Galaxy Note N7000.
INSTALL FACTORY ROM
1) Download a Factory ROM from above and place the "update.zip" file in the root of your external SD card.
2) Go to Settings.
3) Go down to About Phone and click that.
4) Click on System Updates.
5) Remove the check mark.
6) Click OK.
7) The phone should restore to whichever factory update file was used.
APN FIX (MOBILE DATA FIX)
If your mobile data is not working then use this method to fix your APN:
1) Revert to stock ROM (or any custom ROM where mobile data does work).
2) Download and open a file explorer like Root Explorer or ES Explorer.
3) Go to /system/etc
4) Copy "apns-conf.xml".
5) Go to /sdcard/
6) Paste "apns-conf.xml".
7) Flash ROM.
8) Download a file explorer and open it.
9) Copy "apns-conf.xml".
10) Go to /system/etc
11) Paste "apns-conf.xml" (overwriting the existing file).
12) Reboot the phone.
13) Mobile data should now work.
GAME SUPPORT FOR ZTE U950 (WORKS ONLY FOR U950V1.0.0B02)
Note: I have not tested this. Apparently the first firmware version of this phone is not recognized by Google Play for certain Tegra games. If this occurs, try the following method.
1) Make a backup of the System folder. (It is easier to make a Backup of the entire ROM in recovery...)
2) Insert the build.prop file from this file.
3) Clear the Data for Google Play store (Settings > Apps > Google Play > Clear Data).
4) Reboot the phone.
5) When opening Google Play it should make give their agreement again. If it doesn't, then Data has not been cleared.
6) The rows modified in the build prop is as follows:
Desire ro.product.model = X
HTC ro.product.brand =
Desire ro.product.name = X
Desire ro.product.device = X
...
HTC ro.product.manufacturer =
AGAIN, I HAVE NOT TESTED THIS SO USE AT YOUR OWN RISK!
APP SUPPORT FOR ZTE U950
Note: Some apps will throw package errors after downloaded and then will not install. This method will help a lot of these errors from occurring. It doesn't work for all, but it will for some [tested with Dead Trigger 2].
1) Download this file.
2) Use a file explorer like ES Explorer (free) or Root Explorer (paid) and put com.google.android.maps.xml in /system/etc/permissions
3) Put com.google.android.maps.jar in /system/framework
4) Reboot the phone and now apps should install without issue.
DEAD TRIGGER 1
1) Enable graphics details to High in Setup/Others.
2) Exit the game.
3) Use a file explorer like ES Explorer (free) or Root Explorer (paid) and go to /data/data/com.madfingergames.deadtrigger/shared_prefs/
4) Edit the com.madfingergames.deadtrigger.xml file.
5) Change <int name=”UnityGraphicsQuality” value=”1″ /> to <int name=”UnityGraphicsQuality” value=”2″ />
6) Change <int name=”OptionsGraphicDetail” value=”2″ /> to <int name=”OptionsGraphicDetail” value=”3″ />
7) Save the com.madfingergames.deadtrigger.xml file.
8) Remove all write permission on User, Group and Other for the com.madfingergames.deadtrigger.xml file.
9) Delete the com.madfingergames.deadtrigger.xml.bak file.
Note: This technique works on any non-Tegra device.
APP TRICKS
If apps cannot be downloaded normally (from Google Play), this guide will show an alternative method on how to install them:
1) Download the necessary apk file online.
2) Open the 4.2LatinIme.zip with 7zip or WinRAR and delete the keyboard APK (or keep it if not installed yet).
3) While the ZIP is open go into "/Sytem/App" and place in it any APK you want installed.
4) Boot into recovery.
5) Flash the ZIP file.
6) Reboot and the app(s) should be installed.
Note: I have noticed that certain apps do not flash properly so an alternative APK needs to be downloaded. However, once you have the right apps to install Google Play, you should be able to download any apps from the store.
HARDWARE FIXES BY SKA
NOTE: Always work without the battery attached to the phone.
SIM Card No Longer Works
INFO: There is a diode which provides voltage to the SIM card. Somehow it has become loose, which disallows current to the SIM. Thus, the baseband cannot recognize the SIM card any longer.
FIX: The easiest way to fix and check something is to "re-flow" the PCB (printed circuit board). The modem soldering must be re-flowed in order to reconnect the loose diode and re-allow voltage back to the SIM card.
Touchscreen Not Displaying
Open up your phone. If you don't know how, then you won't be able to continue...
There are three connectors on the left soc side. Check the upper connector near the audio jack and try to seat with a pair of tweezers very gently.
There is a white line on every connector - apart from the battery connector - pull up straight. It must be exactly at the of the beginning of the brown clip when pulled downwards.
MISC
I have successfully paired this phone with a PS3 controller using Sixaxis. This is not unique to my phone as I have verified that there is support within the Kernel for this.
It does seem that Wii controller support can be turned on according to the kernel...
There are no known custom kernels for this phone, however, the incomplete Cyanogenmod ROM available does seem to use its own kernel.
The phone is "stuck" on ICS 4.0.4 with almost every ROM. The incomplete Cyanogenmod ROM upgrades the OS to JB 4.1.2.
The phone is known to have heating issues on different (all?) firmware versions. While these do not seem to attribute to hardware failure, it is an annoyance.
Different firmware versions apparently produce varying levels of GPU performance: The best in GPU performance is U950V1.0.0B14, but this build may produce issues in some games. The worst in GPU performance is U950V1.0.0B18, but it is stable. The U950V1.0.0B22 is stable as well but has better GPU performance than B18. I have found no information on how well the first and last firmware versions perform in terms of GPU.
To disconnect the battery connector you need to place a spudger beneath and lift up. It is the same method used for the connectors of fans, temperature sensors, and the battery in a MacBook Pro 2006/7/8.
Thank you for this Tutorial.
Do you know a method to change language in CWM ?
Best regards
cmoegele said:
Thank you for this Tutorial.
Do you know a method to change language in CWM ?
Best regards
Click to expand...
Click to collapse
Unfortunately I haven't found anything that would suggest that you can. The best I could do is have one of my friends tell me what each section states, but that may be a long while from now.
The menus I have figured out and listed are the most necessary. The others are just icing I suppose.
Unable to switch it back on
Hi,
first of all, please excuse me if this is not exactly related to this post, but I see there is not much discussion around this device so I figured this would be an okayish place to ask.
I got my ZTE U950 just today, put my SIM and MicroSD cards in it, turned it on, all OK. I played with it for a while, changed the language into English, tried some apps, deleted lots of default installed Chinese apps (such as Baidu, QQ, Baidu maps, etc).
I run Debian on my machine, so this guide wasn't working for me. However, I tried to run Genotools on Wine and followed the first steps, but no pop-up showed in my phone and I decided that probably Wine wasn't forwarding the USB dev properly. The phone kept on working normally for a while, I even recieved a phone call.
Then I turned it off just to switch the SIM back to my old phone and, after that, I haven't been able to switch the ZTE back on again. At first I thought it'd be the battery running out (although it reported 50% left while it was on), but I've had it connected for about 30 minutes now and I still can't turn it on...
Do you guys know if there is something I can try?
Thanks a lot and excuse me again if I posted in the wrong place... (and if I have, could you please point out where should I post it?)
Bernat.
EDIT: Today I woke up, I pressed the power button and... surprise! It just worked!
No Popup on phone
Hello
I have tried to follow the steps as you have mentioned.
Root>2nd Button>Popup>ok
But nothing appeared on my phone.
Can you guide me what should I do.
I have USB debugging and Unknown Source checked but no popup appeared on my phone.
raoyasir said:
Hello
I have tried to follow the steps as you have mentioned.
Root>2nd Button>Popup>ok
But nothing appeared on my phone.
Can you guide me what should I do.
I have USB debugging and Unknown Source checked but no popup appeared on my phone.
Click to expand...
Click to collapse
Do you have the usb-drivers installed ? (doublechek in device manager for windows ) Sometimes Win7-64 or Firewalls block uncertified drivers to install correctly. For 7-64 you can press F8 during early boot and choose "force unsigned drivers" or something simiar. On linux you should go through an Android adb installation howto, to correctly get debuginterface running.
Once you have installed chinese recover you can install some prerooted images from the hungarion or chinese sites.
br
cm
PS: has someone skills for implementing other languages or removing the chinese letters on some menues ?
I just bought ZTE V985 which is also tegra 3 device. Can anyone help how to root it?
Sent from my HTC Desire using xda app-developers app
how to root zte v985
someone please tell us how to root zte v985.
3G
Hi guys,
does anybody know if/how it is possible to connect to a 3G network with this terminal? In the specs it says it can only connect to Chinese 3G networks, so I'd like to know whether this is a software or a hardware restriction.
If it's a hardware one, I guess the solution must be pretty complex...
Cheers!
alz_uk said:
someone please tell us how to root zte v985.
Click to expand...
Click to collapse
I was able to root my ZTE V985 couple days ago. Download root installation package from:
http://pan.baidu.com/share/link?shareid=68344&uk=2753639880
1. Install ZTE USB driver first: Goto Settings -Developer options - enable Driver CDROM. Connect your phone to the computer and install driver package from ZTE. 985root.7z package has also ZTE USB driver but it didn't work on my Win 7, so I installed drivers from phone.
2. Turn off CDROM mode and enable USB debugging mode and Unknown sources
3. Unzip 985root.7z file to any folder
4. Run xxxroot.bat and command window appears. Script will stop and ask you to press any key (in Chinese)
5. Check that your phone is connected and press any key. Script will upload files to your phone
6. There will be popup window on your phone. Click Restore my data
7. Phone will then boot up but keep it connected to PC and wait until it is fully booted
8. if there's nothing going on in command window, press any key and command window closes. If your are rooted, you have SuperUser app
Original instructions from here:
http://bbs.gfan.com/android-5226211-1-1.html
And Google translation:
http://translate.google.com/transla...=http://bbs.gfan.com/android-5226211-1-1.html
suunnittelija said:
I was able to root my ZTE V985 couple days ago. Download root installation package from:
http://pan.baidu.com/share/link?shareid=68344&uk=2753639880
1. Install ZTE USB driver first: Goto Settings -Developer options - enable Driver CDROM. Connect your phone to the computer and install driver package from ZTE. 985root.7z package has also ZTE USB driver but it didn't work on my Win 7, so I installed drivers from phone.
2. Turn off CDROM mode and enable USB debugging mode and Unknown sources
3. Unzip 985root.7z file to any folder
4. Run xxxroot.bat and command window appears. Script will stop and ask you to press any key (in Chinese)
5. Check that your phone is connected and press any key. Script will upload files to your phone
6. There will be popup window on your phone. Click Restore my data
7. Phone will then boot up but keep it connected to PC and wait until it is fully booted
8. if there's nothing going on in command window, press any key and command window closes. If your are rooted, you have SuperUser app
Original instructions from here:
http://bbs.gfan.com/android-5226211-1-1.html
And Google translation:
http://translate.google.com/transla...=http://bbs.gfan.com/android-5226211-1-1.html
Click to expand...
Click to collapse
Thank you very much my freind, you are a kind and intelligent person.
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
nabax said:
Hi guys,
does anybody know if/how it is possible to connect to a 3G network with this terminal? In the specs it says it can only connect to Chinese 3G networks, so I'd like to know whether this is a software or a hardware restriction.
If it's a hardware one, I guess the solution must be pretty complex...
Cheers!
Click to expand...
Click to collapse
Hahaha you silly billy, i know whats happened to you! You got the ZTE U985 instead of the V985. The ZTE U985 only supports TD-SCDMA 3g network which is CHINA only. You should have bought the ZTE V985 which is WCDMA 800/1900/2100 mhz which supports western 3G networks. LMFAO. I feel sorry for you fella.
Where did you buy the v985 ? I only can find offers from 350-400$ and for this pricing I can´t find any real advantages buying a chinese phone , there is also no DualSim,and normally very limited languages ( chinese cwm?),....
cmoegele said:
Where did you buy the v985 ? I only can find offers from 350-400$ and for this pricing I can´t find any real advantages buying a chinese phone , there is also no DualSim,and normally very limited languages ( chinese cwm?),....
Click to expand...
Click to collapse
I bought it from fastcardtech.com, only 275 USD with free delivery.
From hardware specs point of view this is a really good phone, fast as my Asus TF700T tab with Tegra 3. It also supports WCDMA 900/2100MHz which are the most used 3G frequencies in EU. It does have only English and Chinese languages, but I used MoreLocale 2 to get more choices. More Locale does not change system language (like settings, caller app etc) so those will remain in English, but for example now other apps like Google play, Chrome etc. supports the language you have chosen in MoreLocale.
Sent from my ZTE V985 using xda app-developers app
cmoegele said:
Where did you buy the v985 ? I only can find offers from 350-400$ and for this pricing I can´t find any real advantages buying a chinese phone , there is also no DualSim,and normally very limited languages ( chinese cwm?),....
Click to expand...
Click to collapse
Dont get it wrong my mate the zte v985 is a beast of a phone + a smart piece of hardware. Only downfall i see is the limited rom/root/customization support since its new (october 2012)
Reasons why you should purchase the zte v985:
1. really supports APP2SD (install apps to external sd so you never run out of space and you dont have to throw away your phone when internal memory of 4GB gets full like most other android phones)
2. quad core cpu + 12 core NVIDIA gpu (theres websites full of games made only for this cpu + gpu)
3. USB OTG (using your superfast cpu and gpu together with usb otg you can turn your phone into an high class gaming system using two usb game controllers playing arcade roms and 3d games ON YOUR PHONE!). This is an awesome feature that not all phones support even some high performance quad core phones dont have this function.
4. 720P HD screen + 1080P HD Playback/Recording
5. Full MHL support (usb to hdmi)
6. Cheapest all round high performance quad core. Awesome price (£190) for a phone compared to other quad core high performance phones e.g galaxy note 2 @ £500
NOTE: if you would like to buy this phone for the price mentioned leave a message with your email or contact me i know a seller in china.
NOTE: Or you could wait another month or two and buy the new mtk 6589 quad core phones such as the UMI X2 which is quad core, DUAL SIM, usb otg, 2GB RAM, 32GB ROM and dirt cheap (£200!!!)
I get my ZTE V985 today through the post, cant wait till i get it!
Recovery in english language?
Hi
Anyone found Recovery in English language?
Google play
I can install google play, but if i open it, it immediatly shuts down again...
Any idea's ?
cwm zte u950 test 1 (build, 28 nov 2012) by me.
===================================
(cwm-u950-6.0.2.3-permanent)
-------------------------------------------
CRC32 : D2CD4005
MD5 : A1C6B72375B2E79100AA9BE52D0F30C2
SHA-1 : C7B3165D1E1F7463BFF16C0DE7747E6B3EC3F807
xxx.media*fire.com/download.php?0411sb2m1kkyrv4
(cwm-u950-6.0.2.3-temporary)
------------------------------------------
CRC32 : 830121A8
MD5 : 8239E70CB81548FE4427C505A5184749
SHA-1 : 9CF9CED3EC6CA2B79AE174E03A423435BB0FFFAC
xxx.media*fire.com/download.php?m90c896m17u0o9p
sorry.. i still need to learn..
please report cwm zte u950 test 1 (build, 28 nov 2012).
suunnittelija said:
I bought it from fastcardtech.com, only 275 USD with free delivery.
From hardware specs point of view this is a really good phone, fast as my Asus TF700T tab with Tegra 3. It also supports WCDMA 900/2100MHz which are the most used 3G frequencies in EU. It does have only English and Chinese languages, but I used MoreLocale 2 to get more choices. More Locale does not change system language (like settings, caller app etc) so those will remain in English, but for example now other apps like Google play, Chrome etc. supports the language you have chosen in MoreLocale.
Sent from my ZTE V985 using xda app-developers app
Click to expand...
Click to collapse
ZTE Grand Era V985 Recovery (support English)download link: pan.baidu.com/share/link?shareid=372147&uk=973327405
If you have any problems,please sent a email to me ,my email address is '[email protected]' ,i can help root your ZTE Grand Era V985,and install the recovery,the recovery includes English language.At last,the Android 4.2 for V985 will coming soon,maybe in April,if anyone need ,i will send to you.Thank you.
i found twrp for the zte u950 in english in this package, it is in the folder recovery_3 :good:
what do you think? is it possible to make the zt3 u980 to work with european 3g network? i thought to flash the baseband from zte v985 on the zte u950... do you think its possible?
More stuff in English
hey Heatshiver...u can add these in your OP
I found some roms HERE for U950 which support english language..and atleast instructions are in english
2 or 3 of them are based on MIUI ...
I've tried the 1st one...works perfectly so didn't flash others
Extracted img file of twrp recovery (english) from the package provided by superpfpf - attached in the post

Jiayu G2S - "unofficial forum"

JIAYU G2S
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Jiayu G2S was released on January 1, 2013. It was a significant upgrade to the G2 with a lot of hardware changes. For the price, it had an impressive list of specifications:
MTK MT6577T ARMv7 Cortex-A9 Dual-core 1.2GHz processor
GPU: PowerVR SGX531
4 inch QHD IPS screen, 960x540 pixel display, OGS (One Glass Screen)
Dual SIM cards supporting GSM 850/900/1800/1900mhz & WCDMA 3G 2100mhz network (only one 3G slot)
1GB RAM / 4GB ROM
Supports up to 32gb class 12 microSD card (TF card)
8MP rear camera, 2MP front camera
Supports WiFi a/b/g & WiFi hotspot, Bluetooth with EDR & A2DP, GPS & AGPS
Android 4.1 OS (Jelly Bean), multi-language
FM Radio
Gravity Sensor, Proximity Sensor, Light Sensor, Magnetic Sensor, Gyroscopic Sensor
2200mah battery
Size: 125 x 61x 9.9mm
Weight: 145g with battery
Overall, I really like the look and feel of the phone. Except for the ear speaker hole, the front is one solid piece of glass, wrapped around with a very solid metal frame. The metal frame is not just a thin piece of sheet metal, but is cast metal, provides for complete rigidity for the whole phone, and should do a good job of protecting that large piece of screen glass. This also means that the phone has a bit of weight, but that feels good in my hand. Additionally, I like the more rectangular design of the phone and the more square edge down the sides that the flat metal frame provides. It is very easy to hold onto.
Call quality is very good for me. Reception seems on par with other phones I've used. The wifi might be a bit weaker than my Huawei G300, but it is fine. The screen is very nice to look at and very sensitive, but you should read below about the "jump screen" problem. You should also read below about potential problems with GPS connection issues. I've now owned two of these phones. The first had the jump screen problem, and was replaced under warranty. The replacement has terrible GPS pickup, but no jump screen problem.
The large battery means that I have no problem getting through a day of use, and I probably could use it for two days without a charge most of the time. (But I do not use the phone for gaming.) The phone runs most of the time at 1001mhz or 250mhz when on, and will only jump to 1200mhz in extreme conditions. "Deep sleep" mode is for when the screen is off, but the phone will run at 1001mhz when charging no matter if it is on and being used or not. That is an issue for phones based on this MTK chipset and not exclusive to the JY G2S.
Jiayu includes a few apps targeting the Chinese market for this phone, but other than that, the OS is mostly "vanilla" Android Jelly Bean (AOSP). The phone comes already rooted, so freezing or deleting unwanted apps is a simple solution for what you don't want. There are a number of modified roms available already, including the Lewa rom (http://www.needrom.com/phone-roms/jiayu/g2s/). But you should note that later hardware versions of this phone have different components. You should make a note of what the rom version is that came installed on your phone so that you know what hardware version you are using.
"Jump Screen" Problem Solved?:
Many of the first batch of phones were plagued with screen problems. Commonly referred to as the "jump screen" problem, the result is that when scrolling through screens of data, the screen just "jumps" to a different location without any apparent reason. The screen also "quivers" when touching it, even if you aren't moving your finger. Jiayu promptly acknowledged the problem and tried to correct it with a quick ROM update released on January 9, 2013. (The build number of the ROM is: G2S 20130108-104044.) This ROM update did seem to work for some, but for others the problem persisted.
At this point, I personally don't know if the problem has been completely solved in the manufacturing of subsequent batches of the phone. My phone had the problem, and flashing the new ROM did not solve it. I returned the phone for replacement under warranty and did receive a replacement phone that does not have the problem. So whether or not there still is a manufacturing problem, Jiayu can replace the phone with one that works. However, see below for the GPS connection problem that I now have.
GPS Connection Problems:
There are also a number of users here who are reporting difficulty with weak GPS fix. My GPS fix on my first phone was excellent, but my replacement phone is not good at all. It has been suggested to install "Faster GPS" from the Play Store, which will let you set your location. Also, you can look at this post from later in this thread for more information: http://forum.xda-developers.com/showpost.php?p=39975417&postcount=209. (Please post any solutions you discover in this thread.)
ROM Flashing:
One of my initial struggles was getting the official rom flashing tool to work. I finally got things going, and I hope I can help others who "just don't get it". So if you want some detailed instructions in English for how to flashing a new official ROM onto the Jiayu G2S, have a look at the second post. (If you are flashing a third-party rom, follow the rom builder's instructions.)
ClockworkMod Recovery:
"Thingbreaker" has provided us with a working CWM Recovery. Here's his post link: http://forum.xda-developers.com/showpost.php?p=37521066&postcount=28
There are two ways to flash the CWM Recovery image: using the ROM flashing tool (harder) or using Mobileuncle Tools (easier).
To use Mobileuncle Tools, install it from the Play Store (free). Copy the CWM Recovery image file to the root of your SD card, making sure there are no spaces in the filename. Run Mobileuncle Tools and choose Recovery Update. Choose the recovery image file that Thingbreaker provided.
To use the ROM flashing tool, you first you need to understand how to flash a complete rom as explained in the second post of this thread directly below. After you know how to do that, then look at this post to learn what is different about only flashing the recovery image: http://forum.xda-developers.com/showpost.php?p=37499848&postcount=23
Conclusion:
I do not recommend purchasing this phone. Period. Until Jiayu can do a better job of quality control, I don't recommend their products. There are other companies out there who's phones are only slightly more expensive, but who have a much better reputation for quality control.
Jiayu, if you are reading this, you need to do better! And you really need to improve your repair department as well. Sending me a replacement phone with a GPS problem causes me to wonder if you are using the "shuffle" method of passing around bad phones instead of repairing them. I'm NOT a satisfied customer.
“Unofficial” Guide to Flashing the Official Jiayu G2S ROM
Disclaimer: I’m just one guy who got this to work after a lot of trial and error. I’m only telling you how I did it. I don’t claim it will work for you. I don’t guarantee you won’t brick your phone by following these instructions. And you should understand that if you don’t bother to read carefully and do exactly what I say, you really can brick your phone. Also, it seems there has been an upgrade to some of the components in later versions of the phone released in March 2013, and you will want to verify which version of the phone you have before installing any roms. You should be able to check the rom build information for the date on your particular phone. This guide only describes how to flash the official rom from Jiayu for the G2S. If you intend to install some other third-party rom, please follow that rom builder's instructions.​
Pre-requisites:
You need a PC running Microsoft Windows 2000 or higher.
If you haven’t previously installed msxml 6.0 and .net Framework 4.0 or higher on you Windows PC, do so first. Get them directly from Microsoft. (I assume you know how to search.)
Download the following:
Latest Jiayu G2S ROM update; the rom I installed was the G2s_20130109-104044 stock rom: http://pan.baidu.com/share/link?shareid=157669&uk=839171988 (Note: the build number of the ROM after installation is: G2S 20130108-104044; don't be confused by the name of the file.) Use Google Translate if you need to see which button to push to start the download. Also note that there is a newer official rom for newer versions of the phone. The rom date is 20130306. I don't know what happens if you install the newer version on an older phone.
This zip file contains the Android USB driver, VCom drivers, SP Flash Tool, and a document of these instructions (ReadMe.doc): http://www.mediafire.com/?tc4q3wy5eabowhf
Unzip the files you downloaded and move/copy folders and files where they need to go:
Within the rom zip that you downloaded from the Baidu website, you can find the \G2s_20130109-104044 sub-folder. This folder contains the actual rom files (14 files). Move this entire folder onto your desktop. The reason for doing this is that there are folders within the zip file whose names contain characters that your version of Windows might not be able to read, even if you can see them in Windows Explorer (the filemanager). This will cause you trouble when you try to flash the rom.
After unzipping the driver and flash tool zip file, you will find the \USB-VCOM-Drivers folder with \INF and \SYS sub-folders. In the \INF folder there are three other sub-folders: \ 2K_XP_COM, \Vista, and \Win7.
Copy the \INF\cdc-acm.inf file into your C:\Windows\inf folder. (You may have to give permission to do this.)
Based on your version of Windows (2K-XP, Vista, Win7, 32-bit or 64-bit), locate the one correct usb2ser_????.inf file and copy it to your C:\Windows\inf folder. (You may have to give permission to do this.)
Copy both the \SYS\androidusb.sys and \SYS\usbser.sys into your C:\Windows\System32\driver folder. (You may have to give permission to do this.)
Install the drivers:
Plug your phone into your computer with a USB cable. If you had not previously installed the drivers, the system will start trying to install them.
If the system asks you to choose to install the drivers, click on “install the software automatically” and proceed.
If system is unsuccessful in locating and installing the drivers, you can try to go back and locate the drivers yourself by pointing to the individual files, but this should not happen if you properly copied the drivers over to your C:\Windows system folders.
BACKUP YOUR DATA NOW!
Proceeding beyond this point is going to mean that EVERYTHING on you phone is going to be deleted and a new system will replace it.
You have been warned!
Warning!
Attempting to install a rom that does not use the correct “scatter” file (see description below) will brick your phone. Don’t do it. If you aren’t sure a rom is made for your phone, don’t attempt to install it.
Install the updated ROM:
1. Turn off your phone, open the back, and remove the battery.
2. Plug your USB cable into your PC and phone. If your PC attempts to install drivers, let it finish.
3. Unplug your phone from the cable.
4. Start the SP Flash Tool program by clicking on the Flash_tool.exe file. If you get a security warning, allow it to run.
5. Click on the “Scatter-loading” button on the right side.
6. Browse to your \Desktop\G2s_20130109-104044 folder and choose the MT6577_Android_scatter_emmc.txt file. All other files will be chosen automatically.
7. Click on the “Firmware -> Upgrade” button.
8. Plug your USB cable firmly into the phone. The Flash Tool will automatically start flashing your new rom. Wait for it to finish and show you the green circle.
9. Unplug your phone from the cable.
Rebooting the phone:
1. Install your battery.
2. Very carefully, without touching the screen, push the power button.
3. Do not touch the phone as it boots!
4. After it has completed booting, you may again use your phone normally.
Following the advice that it might help if the phone is very cold when updating to the new rom, I tried putting it in the refrigerator. Unfortunately, that did not seem to help in my case. The phone still has the "jump screen" problem.
Of course, any other ideas would be appreciated as well.
Has anyone yet been successful in creating a Recovery mod (i.e. ClockworkMod Recovery)?
Tell Me Some Unofficial Way Of Hacking Based On Geograohical Location
Any Jealousy people Tell Me Some Unofficial Way Of Hacking Based On Geographical Location.
twrock: Make sure you do not have screen protector applied and you do not touch the screen during the first boot after flashing.
Thanks for the advice. But I'm not using a screen protector, and I am being very careful about not touching the phone. Nothing seems to help.
Sent from my G2S using xda app-developers app
Have you identified production date of your phone? Is there a sticker anywhere? We might come to a conclusion later on, of which date onward the factory has solved the problem... It might be a hardware problem after all.
Still waiting for mine to arrive...
hi there, for those who already have in their hands the g2s is it possible to give more reviews about its gps and the camera especially at night? thanks
Hi.
I have just created a ClockWorkMod recovery image for the Jiayu G2S.
I don't have the phone yet, it is still on its way, so I can't guarantee that it will work.
Download: http://db.tt/vFO4S6Mc
When flashing this recovery, use the same scatter file as for the stock rom.
If you don't have the scatter file here it is: http://db.tt/Z4TWPowQ
Please try it at your own risk, and give me feedback.
I received mine today. I am stunned. This thing is amazing. After all the HTC's I have this is a dream.
Mine doesn't seem to have the screen problem, but has the 20130108 firmware. I will wait a couple of days and see how it's running and the flash it.
CWM for this would be amazing and unabridged CyanogenMod would be even greater. Wonderful times!!!
fcsabika said:
Hi.
I have just created a ClockWorkMod recovery image for the Jiayu G2S.
I don't have the phone yet, it is still on its way, so I can't guarantee that it will work.
Download: http://db.tt/vFO4S6Mc
When flashing this recovery, use the same scatter file as for the stock rom.
If you don't have the scatter file here it is: http://db.tt/Z4TWPowQ
Please try it at your own risk, and give me feedback.
Click to expand...
Click to collapse
I'll give it a try.
What method did you use to create it? Did you use Koush's "builder"?
I also tried to make a CWM Recovery using the builder. The builder said it was successful, but the resulting CW recovery would not boot.
I'll let you know when I have the time to try it. Thanks.
Anyone know how to get rid of the Google search bar at the top of the standard Launcher? I'd guess that Google doesn't want us to be able to get rid of it.
sdssss said:
hi there, for those who already have in their hands the g2s is it possible to give more reviews about its gps and the camera especially at night? thanks
Click to expand...
Click to collapse
I don't know if my experience is much help. I live in Taiwan, so I suspect my GPS satellite locks were about the same as they would be in China. So for what it's worth....
My first GPS use locked in less than two minutes. I was outside in a parking lot on a clear day when I started. I got into the car after about 30 seconds and put the phone on the dashboard. It was locked in before the screen shut off (which is set at 2 minutes). I did not have Wifi connected, so no help from that. Subsequent to that first use, locking in took less than 15 seconds.
I haven't taken any pictures at night, so I can't help you there.
I'll mention here that if I decided to order this phone today, I'd find a way to get it straight from Jiayu. I ordered mine from Etotalk.com (and wasted money on their "Etotalk mod rom"), and they aren't being very helpful with aftersales follow up. I finally gave up on them and am now talking straight to Jiayu support. But I have to wait until after Chinese New Year to send it back. They said that they would not be able to replace the phone until after Chinese New Year anyway, so sending it back now would only mean I would be without the phone longer.
hello, i'm G2S first batch too, what do you mean about shaking problem? is it shake hard ? i got the problem while charging the phone, but if it's unplug, it's seems to be normal.
i'll try the new firmware from this thread, thanks for the link :laugh:
by the way, i've ported the CWM recovery for G2S, i'll upload it if you need it
For those who already have the phone, is the signal strong even if you are inside buildings?
I'm asking this because many users report that jiayu g3's signal is very week when you get indoor, and i'd like to know if it was corrected in this version.
sempracurtir said:
For those who already have the phone, is the signal strong even if you are inside buildings?
I'm asking this because many users report that jiayu g3's signal is very week when you get indoor, and i'd like to know if it was corrected in this version.
Click to expand...
Click to collapse
my phone is work normally even inside the buildings it depends on the network carrier, except you're in the basement
by the way, i've flashed the newest firmware from the page1, and the "jumpscreen" error while charging is now fixed. More stable touchscreen, thanks man :laugh:
Gps
fix ok, but not accurate.
The worst gps that I have had.
Solutions?
Hello
verbal
twrock said:
I'll give it a try.
What method did you use to create it? Did you use Koush's "builder"?
I also tried to make a CWM Recovery using the builder. The builder said it was successful, but the resulting CW recovery would not boot.
I'll let you know when I have the time to try it. Thanks.
Click to expand...
Click to collapse
Yes I have used the builder.
So did anyone try my CWM recovery?
fcsabika said:
Yes I have used the builder.
So did anyone try my CWM recovery?
Click to expand...
Click to collapse
Sorry, how can I install it?
I read your post yesterday but I didn't understand.
Can you explain me better?
Thanks.
lelepanz said:
Sorry, how can I install it?
I read your post yesterday but I didn't understand.
Can you explain me better?
Thanks.
Click to expand...
Click to collapse
You can install it the same way as the official rom.
See the second post by twrock.

Help rooting a BLU Dash M

I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Unlock OEM in developer mode and try it whit Kingroot
AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Sent from my RCT6873W42M using XDA Labs
---------- Post added at 03:04 AM ---------- Previous post was at 02:56 AM ----------
TechTeen17 said:
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Click to expand...
Click to collapse
You can download the tool at the bottom of this thread.
Sent from my RCT6873W42M using XDA Labs
Root BLU Dash M
AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
i know this is an old thread but.... i rooted mine (Dash M) with KingoRoot (look it up on Google)... i tried lots of stuff with no results, everything failed (i've already tried to root with KR in windows) but the only thing that worked was rooting with the android app in KR page... i felt really stupid after trying everything with no results when i've been using KR for other "hard phones".... either way, the only downside is that their SU manager displays all the time ads no matter where in the phone you are... but you can freeze the app to fix this and unfreeze it when you need to assign permissions....
BTW: its KingoRoot not kingroot (just in case)

Categories

Resources