Related
Do not ask me or anyone else on these forums about how to change your ESN! It is highly illegal! Don't do it! I will not discuss that at all in this thread.
If you have activated your Optimus V on Verizon's network, and you have any of the Optimus V Froyo roms installed, the following will show you how to mod the rom to run on Verizon smoothly. Otherwise, you won't be able to send and receive sms/mms messages, and the phone will constantly complain that it is roaming. The scope of this thread is how to mod the rom once you have already activated your phone.
Always do a backup before doing anything on this page. You will need to use root explorer or adb to install these files onto the system partition. Or you can build/mod your own rom and install it.
Using adb, you would first mount system as write-able:
Code:
adb remount
Then you would push the files to the phones with the push command:
Code:
adb push file.ext /path/file.ext
Step 1: download this file pack
Step 2: Extract the files into the same folder as adb or onto your sdcard if you are using root explorer.
Step 3:
Place apns-conf.xml inside /system/etc/
Place Phone.apk inside /system/app/
Place telephony.db inside /data/data/com.android.providers.telephony/databases/
Step 4: I've included a modded framework-res.apk from the reborn rom. If you use a different rom or if the included one does not work for you, extract the original framework-res.apk from your rom located in /system/framework/. Using winrar or 7zip, add the included eri.xml to /res/xml/. Replace the original framework-res.apk on your rom.
Step 5: Using QPST, flash the included PRL file, 52299.prl
I've been using this setup for a week now without problems. I thought I would share. I tried using the LG Vortex rom on the Optimus V, but the hardware was too different. This method should also work on the Optimus S, M, and C, but I have not confirmed.
For the CM7 roms, check here: http://forum.xda-developers.com/showpost.php?p=19992286&postcount=11
nice <3 it looks awesome
I really need to find a way to repair my esn. it reads all zeros .. please help
if it truely is all zeros,then it would not be illegal to write the phone's own esn/meid back in,but it MUST be the one on the sticker of the phone. the way to do that would be to flash a rom that lets the phone show up in diag mode. I know aospCMOD does,I don't think IHO does though. experiment and you should end up with the phone showing up as a modem. then install qxdm,if you google for it its easy to find. you need qpst also,they are both on the same page if you google for them together. once you have all that,launch qxdm,go through the menus and find communication,pick the lge diag port,then in the command box,type "spc ______"<enter>where the ______ is your SPC/MSL. you can get these using cdma workshop 2.7 which is also illegal to link here,but is easy to find,just pick the diag port,click connect,then go to the security tab and pick lg method and hit read. now back in qxdm,type "RequestNVItemWrite meid 0x_______________"<enter> where the ____ is your meid from the phone's sticker. DO NOT USE THE MEID FROM ANY OTHER PHONE OR THIS IS ILLEGAL.once that is done,which should be instant,then type "mode reset"<enter> the phone should now reboot.
Message to mods: Please do not remove this post as it does not show anyone how to change an esn/meid,it only allows them to write one in if the phone does not already have one. If the phone does already have one,this method will not work to change it,it will stay at its original.
msnuser111 said:
if it truely is all zeros,then it would not be illegal to write the phone's own esn/meid back in,but it MUST be the one on the sticker of the phone. the way to do that would be to flash a rom that lets the phone show up in diag mode. I know aospCMOD does,I don't think IHO does though. experiment and you should end up with the phone showing up as a modem. then install qxdm,if you google for it its easy to find. you need qpst also,they are both on the same page if you google for them together. once you have all that,launch qxdm,go through the menus and find communication,pick the lge diag port,then in the command box,type "spc ______"<enter>where the ______ is your SPC/MSL. you can get these using cdma workshop 2.7 which is also illegal to link here,but is easy to find,just pick the diag port,click connect,then go to the security tab and pick lg method and hit read. now back in qxdm,type "RequestNVItemWrite meid 0x_______________"<enter> where the ____ is your meid from the phone's sticker. DO NOT USE THE MEID FROM ANY OTHER PHONE OR THIS IS ILLEGAL.once that is done,which should be instant,then type "mode reset"<enter> the phone should now reboot.
Message to mods: Please do not remove this post as it does not show anyone how to change an esn/meid,it only allows them to write one in if the phone does not already have one. If the phone does already have one,this method will not work to change it,it will stay at its original.
Click to expand...
Click to collapse
thanks I will try this on my brick phone as soon as I get home.
thanks it work. thanks a billion.
how do I get M.Ip settings in QPST Service programming to stick. they always revert back to original.
not working on bumblebee rom
mereed1977 said:
not working on bumblebee rom
Click to expand...
Click to collapse
if you're having problems connecting with qxdm/qpst, try booting into recovery first.
you can also restore your first stock backup and the pst's can talk while it's turned off but still plugged into the pc.
freddysam has been a God-send..He has helped me with SOOO much pertaining to all of this..I just wanted to publicly let it be known that this guy is AWESOME and SUCH A HUGE HELP!!! Thanks again bro!!!
Thanks to freddysam, I found that this was possible and I now have another Optimus V but it is on the Verizon network via Page Plus Cellular. However, instead of using the package freddysam posted here, I have built an up-to-date ROM from the IHO/CM repo hybridized for OV on the Verizon network. It is working fine for me without any issues. Instead of going through steps 1-4, you can just flash the following ROM (updated 02/22/2012)
http://www.mediafire.com/?emblkx8bb2bcoc1
MD5sum: ab4290cdccc249a5766458841d6e2565
You can check the MiRaGe build at IHO Wiki. This is the same build with VZW mods. If you also want the theme for MiRaGe ROM for VZW, it is here. Don't use the theme on the Wiki.
You still need step 5 to flash the PRL using QPST. But after that, you can update to the latest PRL by dialing to *228 and choosing option 2.
Thanks especially to Blarf and BobZhome for creating the IHO repo and VM670, VS660 ROMs.
I am attempting to get an Optimus V on Page Plus but am having trouble with Step 4.
I keep getting a boot loop or frozen flash screen after I repack and load framework-res.apk
Here is where I am at:
1)Rooted stock ROM using Gingerbreak
2)Flashed Xionia Recovery
3)Made backup of stock ROM
4)Flashed the Mirage ROM posted above after clearing caches and formatting the appropriate partitions
5)Get stuck at splash screen during boot. Sometimes it goes into a loop if I wait long enough
6)Tried using Xionia to fix boot loop, does not work
7)Tried installing the Mirage ROM in this thread using IHO_Recovery (BobZHome update for new Optimus V), still loops.
Alternatives I have tried:
1)Flashed IHO_Recovery
2)Installed BobZHome CM7 ROM. It works fine.
3)Replaced files in BobZHome CM7 ROM with the files in this thread. Everything went fine until step 4, then I would freeze at splash screen on boot.
4)Attempted to unpack/replace eri.xml/repack framework-res.apk from BobZHome CM7 ROM. Again freezes/loops at splash screen.
Any suggestions?
depthsounder said:
I am attempting to get an Optimus V on Page Plus but am having trouble with Step 4.
I keep getting a boot loop or frozen flash screen after I repack and load framework-res.apk
Here is where I am at:
1)Rooted stock ROM using Gingerbreak
2)Flashed Xionia Recovery
3)Made backup of stock ROM
4)Flashed the Mirage ROM posted above after clearing caches and formatting the appropriate partitions
5)Get stuck at splash screen during boot. Sometimes it goes into a loop if I wait long enough
6)Tried using Xionia to fix boot loop, does not work
7)Tried installing the Mirage ROM in this thread using IHO_Recovery (BobZHome update for new Optimus V), still loops.
Alternatives I have tried:
1)Flashed IHO_Recovery
2)Installed BobZHome CM7 ROM. It works fine.
3)Replaced files in BobZHome CM7 ROM with the files in this thread. Everything went fine until step 4, then I would freeze at splash screen on boot.
4)Attempted to unpack/replace eri.xml/repack framework-res.apk from BobZHome CM7 ROM. Again freezes/loops at splash screen.
Any suggestions?
Click to expand...
Click to collapse
Try wiping the partitions several times more and flashing the MiRaGe ROM over again. I had the same trouble with a new OV and it worked after trying three-four times. I have an OV with new screen and used BobZhome's recovery, see under the heading "Alternatives" in the IHO Wiki.
Success! (Sort of )
The files in this thread do work on CM7, I just could not just copy them into the respective folders without errors. Here is how I got them to work.
Warning, it took alot of rebooting and reflashing backups to figure this stuff out, make a nandroid backup before you attempt to replace the system files.
1. Follow steps 1 and 2 in OP
2. Download NinjaMorph or other app that can unpack/repack apk files. These instructions were written for NinjaMorph.
3. Copy files from Step 3 onto phone memory (I used /system), change permissions to rw-r--r--:
- Read:User,Group,Others
- Write:User
- Execute:None
If these files are not set to the correct permissions then apps will start force closing when the files are replaced.
4.MOVE (not copy) files to the folders in OP
- Place apns-conf.xml inside /system/etc/
- Place Phone.apk inside /system/app/
- Place telephony.db inside /data/data/com.android.providers.telephony/databases/
This method would not work for framework-res.apk for me, I had to rebuild the framework-res.apk that came on CM7 with the eri.xml file from the framework-res.apk in the OP. Instructions for doing so follow.
5. Rename the framework-res.apk from the OP to something else, I used VZWframework-res.apk. Open Ninjamorph, start new project and point it to the file you just renamed. It will unpack the apk into a folder on your sdcard called /sdcard/AndroidThemes/workspace. It will ask you to select a file you want to change, back out because we will do that in the next step.
6. Create a new project in Ninjamorph, this time point it to /system/framework/framework-res.apk, it will unpack this apk and ask you to select a file you want to change. Select res/xml/eri.xml, it will then ask you which file to replace it with. Point it to /sdcard/AndroidThemes/workspace/VZWframework-res/res/xml/eri.xml, note that i used VZWframework-res, your folder will be whatever name you chose in Step 5 above.
7. Select finish project, it will repack framework-res.apk and overwrite the existing framework-res.apk in your phone.
8. Reboot Phone. If your phone reboots fine and apps don't start force closing it worked! You should see a change in the taskbar, roaming should not show when the network is Verizon Wireless if you have installed the prl as described by the OP.
I still did not have MMS working at this point and even though my phone didn't say it was roaming, Cell Connectivity Tracker indicated that it was in a roaming state and data would not work without enabling roaming data. The following steps fixed these issues:
9. Move the attached Mms.apk file to /system/app Ensure that the permissions are rw-r--r-- on the file before you move it.
10. Make a copy of your original build.prop and save it on your sdcard (you are making backups this whole time right?) Rename the build.prop.txt in this post to build.prop and move it into /system/ Ensure that permissions are rwxr-xr-x
Both of the files in this post came from the VZW MiRaGe ROM that mrg666 posted above, I did not alter them and full credit goes to him for creating them, I just made them easier to access.
edited out the following due to the help from bigsupersquid and BobZHome (thanks!)
Some Notes:
-While this method got the files onto my Optimus V running CM7.2_RC0 by BobZHome without crashing it, I still do not have mms working.
-I replaced the Mms.apk in my system/app/ directory with the one from the MiRaGe VZW in hopes to fix my mms issues, but no luck.
-Even though the taskbar does not show roaming, if I go into the phone status menu it still says roaming even though I am on the Verizon Wireless network.
-I believe the above issue can be traced to the fact that my phone still thinks it is a Virgin Mobile device. If I run STMurray Cell Connectivity Tracker it gives me "Sim provider name (MCC+MNC): Virgin Mobile" in the log results.
Does anyone know which system file holds the provider information? I never activated this phone on Virgin Mobile, so I can only assume that the setting came from the CM7 ROM I installed.
/system/build.prop
thanks for the pointer to Ninjamorph.
Add/change the following in system/build.prop
ro.cdma.home.operator.alpha=Verizon
ro.cdma.home.operator.numeric=310004
ro.HorizontalVVM=true
Thanks so much for your help guys. I have everything working now including mms and data without roaming.
The tip about build.prop seemed to be the last piece of the puzzle.
I changed the settings above, but still had indications of roaming; I ended up using the entire build.prop from the MiRaGe VZW ROM and it works fine now.
I also noticed that my data usage was dominated by "dialer and dialer storage" before I fixed this roaming issue. Dialer still uses an uncomfortably large amount of data, but it isn't the 20Mb/day that it used yesterday, more like 1Mb/day now. The dialer data usage issue doesn't seem to be fully understood from what I could find; maybe my experience above is a clue.
So I am going to try and switch my optimus v details over to a samsung epic 4g, which will leave my optimus v useless. I was wondering if I could use an old verizon lg flip phone as a donor to the optimus v just for talk and text no data (i am aware mms wont work..)
My youngest brother is on my parents verizon plan and wants a smartphone but they wont pay for the data. I was thinking I could give my phone to him and make the optimus v appear as a dumbphone on the verizon network with just talk and text w/ wifi for internet. I am not asking help on HOW to do it, just do you guys think it would work?
brooksyx said:
So I am going to try and switch my optimus v details over to a samsung epic 4g, which will leave my optimus v useless. I was wondering if I could use an old verizon lg flip phone as a donor to the optimus v just for talk and text no data (i am aware mms wont work..)
My youngest brother is on my parents verizon plan and wants a smartphone but they wont pay for the data. I was thinking I could give my phone to him and make the optimus v appear as a dumbphone on the verizon network with just talk and text w/ wifi for internet. I am not asking help on HOW to do it, just do you guys think it would work?
Click to expand...
Click to collapse
I use one OV on Verizon through Page Plus Cellular prepaid plan. Everything works (data, mms ...). I just disable data since it eats all of the money quickly. I went to Canada two weeks ago, it was also roaming there and I could call back US.
mrg666 said:
I use one OV on Verizon through Page Plus Cellular prepaid plan. Everything works (data, mms ...). I just disable data since it eats all of the money quickly. I went to Canada two weeks ago, it was also roaming there and I could call back US.
Click to expand...
Click to collapse
Good to know that it can work without data. But what I am wondering is if can i switch it with the esn and meid of my old dumbphone and not put in any of the data password/settings. All I want is talk and text on it so my brother won't get charged data and verizon would think he was using the dumbphone not a smartphone. He is part of my parents family plan.
Since the information for this device is so fragmented, I decided to attempt to keep it all in one (or a series of) posts. I aim to link to the original posts as well as outline what do to with your device from the time it leaves to box to running the latest and greatest modified rom or CM9 or whatever else is out there. I will not link directly to anything, rather I will link to the thread, and I very seriously recommend reading at least the post, if not the thread, before you begin ANYTHING.
This guide is a work in progress, it is not complete, and I will work on it bit by bit until it's completed!
Section 1: So its shiny and new...how can I MOD IT?
This will be assuming the new shiny toy in question is indeed an Acer Iconia Tab A100, this is not meant to cover any other devices. And, this is assuming it's coming with Honeycomb installed, in stock form. If its used, or comes with ICS, the next section will amuse you.
First thing most users that want to mod their devices do is root their device. Now, rooting is not unlocking, as carrier unlocking is not boot loader unlocking. Rooting a device allows you to access the system in a much more in depth manner, including read/write (R/W) access to the /system partition, among other things. It allows use of programs such as Titanium Backup (TB or TiBu) ROM Toolbox, overclocking or other clock setting utilities such as SetCPU or CPU Master for overclocking (if the kernel supports it) underclocking and undervolting.
So...how do I do that rooting thing? Well assuming you are running Honeycomb and are wanting to update to ICS plus root and unlock the bootloader, we will use the info from this thread Simple Root Method by ZeroNull to update you to ICS and then gain Root access on that new ICS install!
What about rooting Honeycomb? Well most users are already running ICS and prefer it, and those on Honeycomb are likely wanting to update to ICS, so I will leave this out for now. If I have the time I will come back and include the link for that as well.
Now, ICS is installed, and you're rooted, what else can I do? Well you can unlock your bootloader, and load up a custom recovery such as CWM or TWRP and using those, install Custom ROMS! For this, we visit this thread here Install unlocked bootloader by ZeroNull. Follow ALL directions in this thread for a fully unlocked bootloader!
Custom recoveries, what are they and how do I get that shiz? Custom recoveries, CWM and TWRP, allow the user to flash anything they want, provided its for their device and properly packaged. This included custom roms, some tools, and allows you to "wipe" various parts of the device's storage and backup/restore to a previous installation. Powerful, and dangerous, do not go pushing buttons to things you do NOT understand! Also, you MUST delete or rename /system/etc/install-recovery.sh prior to flashing recovery! This will restore stock recovery every time android boots, wiping out your custom recovery. The only time you want that file there is if you are using the crossix mount swap mod, which replaces that file with a modified version that leaves recovery alone.
Safe to do wipe:
Wipe cache, data, dalvik cache, system. Theonew also reports Flex and boot can be wiped as well as SD-EXT. This is not to be confused with External SD, this is a separate partition on your External SD card, wiping it will NOT wipe external SD, only what's installed on that partition, the rest is safe and requires a separate wipe.
If you wipe system you MUST install a new rom or restore from backup!
If you wipe boot please restore or install a new ROM before rebooting! Safety first.
Not safe to wipe:
Don't wipe anything else, and always install a new rom or backup after wiping system!
Never reboot system after wiping without first restoring or installing a new ROM!
Post 2 will cover custom recovery functions in more detail, for both recoveries.
Now that you have an unlocked bootloader, what can I do? Install that custom recovery! There is two flavors, CWM and TWRP, CWM available here CWM Recovery by ptesmoke. Follow the instructions in this post to the letter! Only attempt this after you have ICS, rooted, and unlocked the boot loader correctly! Next we have TWRP Recovery here TWRP Recovery by ZeroNull. Again, follow the instructions to the letter, and attempt only after ICS, root and unlocked boot loader are finished.
Ok, gots me some custom recoveries, what about custom roms? This is why we just did all that work, to prepare for this! Custom ROMs! I'll be listing some (all?) ROMs that you can use, besides stock HC and ICS.
The list in order of version, oldest to newest, updated to retired:
4.0.3
KEBBERSROM by Hardslog Stock based 4.0.3
Flex Reaper by civato ICS 4.0.3 Modified Stock
Green ICS by lgcmn & ZeroNull ICS 4.0.3 Modified Stock
4.0.4
KEBBERSROM SHELLSHOCK by Hardslog 4.0.4, based on A500 and A700 ROMs
Nightly Builds of CM9 by pio_masaki ICS 4.0.4
Aoikaze Modified CM9 by pio_masaki ICS 4.0.4
4.1.1
CM10 Preview builds by waydownsouth 4.1.1
4.1.2
Unofficial CM10 builds by pio_masaki (stock and modded, Phone UI and Tablet UI)
Jellytime Sosei by pio_masaki Jellybean 4.1.2
Cyanosaki_Flex by Hardslog
4.2.2
CarbonROM JB 4.2.2 Unofficial by pio_masaki
These are most of the ROMs. There are others that seem to no longer be in active development and are based on the old leaks that vache was kind enough to grab for us. Development is currently only active in the KEBBERSROM builds by Hardslog, and occasional updated in the CM10 builds by pio_masaki.
That ends Section 1, preparing for awesomeness, and Post 2 will continue with installing your new custom ROM!
Section 2: Recoveries and what they can do for you.
This section will cover recoveries and what they can do, and how to do it. I will be starting with TWRP, as I use that on all of my devices, and after that I will include a CWM section, as a lot, if not most, use that. They are similar in what they do, but different in where things are.
TWRP Recovery
Official TWRP for A100 by linuxsociety
This assumes you have already done everything in section 1, including installed ICS, rooted it, unlocked your bootloader, and installed TWRP custom recovery. Links for this information is provided in Section 1, in the post above.
First thing you should ALWAYS do when you enter recovery, before doing ANYTHING ELSE, is make a nandroid backup!
Getting into recovery: Depending on what ROM you use, this is done a couple ways. First is an AOSP ROM, like CM9/AOKP, which you can hold the power button, then select Reboot, then Recovery. In modified stock or rooted stock ROMs, this menu doesn't exist, you can either use an app like Quick Boot, and select recovery, or power off, then hold the Volume - key (closest to the rotation lock switch) and while holding it, hold power, once the acer screen comes up and starts saying Recovery kernel, release both and recovery will boot provided an update.zip is NOT on the root of your external SD card. This method works for any ROM.
Now I'm in recovery, what do I do? As I mentioned, make a nandroid backup before you do ANYTHING else! From the first screen (home screen) in TWRP select Mount. In mount you can leave everything alone and at the bottom will be two options with Circles. Select Using external SD Card for Backup. This will store your backup on your external SD card, never use internal SD if possible. After you select use external SD, press the Home button in the upper right corner. Now, back on the Home screen, select Backup. Double check the boxes checked are System, Data, Boot and Recovery. At the bottom is a nice little slide bar, slide that over and sit back. Takes about 4-5 minutes depending on how full your device storage is. This does NOT backup internal SD! After this is done, you have created a nandroid backup that when restored will put the system exactly how it was last time you used it. You can make multiple backups of multiple ROMs without issue, just however big your SD card is to hold them.
The restore menu, or the OOPS SAVE MEH menu is your best friend. This will restore you back to the last state your device was in for the backup that is restored. By default TWRP saves by date and time, however you can rename this with any file manager, never caused me any issues. Theonew reminded me of an MD5 issue that can happen on renaming backups, if this does happen, rename it back to the stock naming system to fix it. Generally I'll just append the ROM name to the front, so instead of 2012-6-14--18-25-01 it'll be CM9-2012-6-14--18-25-01. Make sense? That way to restore it in case of error, just drop the name. Easy. Theonew also did some testing, and confirmed that spaces in the folder name WILL cause MD5 errors and fail the restore, please use ONLY dashes and underscores (- and _ lol) in the folder name! To restore make sure you are on the Home screen, then select Restore. In the window you will see a list of your current backups, select one. Next screen has check boxes, make sure System, Data, Boot and Recovery are checked, then slide the bar to begin. This takes a bit, make sure you let it finish! Once done, your system will be at the last point it was used for that backup.
Advanced restore...I'm to lazy to reload and reset up my stuff after a ROM flash, so this is the fast and dirty way of doing it. If you flash a ROM and you don't feel like manually restoring your apps, you can uncheck System, Recovery and Boot, and leave only Data checked. This will restore your user installed apps and settings over the current ROM install. I don't recommend this for different ROMs, only for updates of the same ROM! Up to you but if you get alot of issues, you'll know why. After advanced restoring, go to the Home Screen and select Advanced, then Fix Permissions. Press Home again and select Wipe. Wipe Cache and Dalvik Cache, then reboot system.
Alright, enough already lets get our flash on! From the Home screen, select Wipe, then press on Cache, Dalvik Cache, Factory Reset, and System. Optional you can wipe Battery Stats if your battery seems off. Leave the rest alone. Once these are all wiped, go back to the Home screen, and press Install. The window on the left is your device folders, window on the right is contents of the current folder. I hope you remembered where your rom.zip is, because you select it here. Press on the zip for the ROM of your choice, then slide the bar to flash it. After that is done, select the left button Wipe Cache and Dalvik, then select Reboot system.
OK LETS ROCK THAT ROM! Woah, slow down scooter, there's a few things to do, or not do, first. After it boots, meaning it's past the boot animation and is sitting on the Welcome screen, set it down and leave it alone for 10 minutes or longer. Don't sign in, don't do anything, just leave it be for 10 minutes. If you can't think of what to do to manage the time you have to wait for awesomness of custom ROMs, read the thread of the ROM you chose. Set the thread for 50 posts and just read. After 10 minutes, hold the power key, and either choose Power off or Reboot, Reboot depending on ROM used. After it finishes rebooting (that was alot faster wasn't it?) you can go ahead and do the Welcome stuff, log in to Google, setup your device, download your apps, restore your apps etc. After restoring your apps (try not to restore app + data if possible, though I know games and stuff you'll want to) reboot one more time. After that second reboot, use the tablet as normal. From my experience this offers the BEST possible ROM usage, a vast reduction in lag, bugs, and oddness.
What else can I do with the TWRP Recovery? Well, the most useful tools are Backup, Restore (and advanced restore) and the wipe menu, plus fix permissions. Those generally can fix anything thats wrong. If you notice alot of lagging, FCs or general unruliness, wipe Cache, Dalvik Cache, and Fix Permissions. Another useful ability is ADB, which is beyond the scope of this section, but may be included generally in a later section. ADB can be used to repair otherwise bricked devices, and offers a very large amount of tools that you don't normally get to use in Recovery. Keep in mind ADB is powerful, and can quickly destroy your device, so please, be careful using it.
Placeholder for CWM Recovery section - coming soon!
CWM Recovery for A100 by ptesmoke
Section 3
Additional Recovery tools:
Blackhole Wipe/Nullifier by pio_masaki
These are tools I created to make wiping a little easier, but please read the post completely before deciding to use it! There are multiple versions, and they can and will wipe internal SD, as well as take up to 40 minutes to run (1, not all). Please ask questions if you have them there and I will help as best I can!
AROMA Recovery Touch Recovery
A touch file manger to be used in recovery, even on non touch CWM! Good for renaming backups as soon as you make them (I tend to forget afterwards and get confused by 6 backups with just dates). Also moving a downloaded zip from internal to external or whatever before running a system wipe, any number of things. Please read the post completely before using this tool! It can cause damage if not used properly and with care!
Kernels:
linuxsociety / godmachine's A100 OC Kernel
Plenty of extra balls thrown in for good measure, a good place to look if you like high benchmarks and plenty of extra goodies baked in. Available in a few flavors, with some GPU OC thrown in for good measure.
ezterry's A100 OC/UV Kernel
The only other option for a kernel that we have besides stock and CM9's included kernel. Excellent kernel, really wakes up the A100, allows up to 1.5 GHz for some extra umph and undervolting to help conserve power on our very weak batteries.
PRO TIPS:
The 10 minute rule:
The reason I mention waiting 10 minutes on first boot of a ROM install is this: Alot of things happen the first time the ROM runs, alot of scripts run, the kernel has to settle and search and move things, files are flying all over the nand. Think of a tornado in a cubicle. That's first boot for your device. Allowing it 10 minutes uninterrupted allows all of that to happen and settle down. The following reboot lets all that new info fire up from it's new home and continue settling in. After restoring and downloading apps, that reboot allows that new info to settle into it's new home and the system to catch up. This isn't device specific, rather a general rule of thumb for all devices. Does not really apply to restores unless something is changed.
Undervolting:
Undervolting on this device is only available on ezterry's excellent kernel. The following is a rough guideline of how to do it, and do it right:
Start small, don't just dump it -200 and expect it to work. For the time you're testing, make sure it is NOT set for boot. If something goes wrong you don't want it doing it everytime it boots, right? Go in small increments, -25 is usually OK. For now, don't overclock. Starting at 1 Ghz, lower every speed range down -25, and run the device for at least 10-20 minutes, normal use, hard use, benchmark, browse the web, watch a HD movie. If all is fine and its not lagging, freezing, force closing or heating up more then usual, move everything to -50, and repeat. My device freezes at -150 but runs stable at -145. Every device and chip is different, mine may do -145 yours may do -175 or only -50.
Overclocking
Overclocking is available on ezterry's bodacious (already used excellent) kernel, up to 1.5 GHz, and the CM9 kernel up to 1.4GHz. As with undervolting, this should be done in small steps and tested between to find your max. Generally 1.5 GHz is fine for every device, however all devices and chips are slightly different, and some may not be stable at it. Mixing undervolting and overclocking can be tricky, but following the steps above for undervolting you can find that sweet spot for your device.
Batteries and why they fail
This section is entirely my opinion, other's swear one way, other's another, but this is what I've concluded from multiple posts for this device.
Consider 10% to be 0%. There have been more then a couple posts that say they let their battery fall below 10% and they can NOT get the device to work properly again afterwards. I think there's a few reasons for this, and I'll explain them now. First, a lot of batteries tend to have some kind of breaker protection if the voltage drops below a certain level. This is to prevent damage to the cells, which it does, however we can't close that breaker to restore activity from the battery, IE, it's dead anyways. This threshold varies from one device to another, one battery pack to another, some can go to 0% and be ok, others can't. I say voltage level, because while draining the voltage can spike up, and it can also spike down, which can fall below this threshold even though it says you have 5% battery life remaining, and trigger the protection.
The acer does not seem to power on without a working battery. If the battery is "dead" it doesn't seem to boot. Its basically a brick until either the battery is replaced (by acer I would assume) or the motherboard is replaced due to some sort of damage causing this. Replacing the motherboard costs almost as much as a new unit, so at this point, just save up some more and buy a new one.
For this, I never go below 10% if ever possible. Even on my phones.
Another thing I try not to do is charge in bursts, or at random times. Basically, I plug in at 10%, then allow full charge to 100%, I don't charge in between those ranges, and I don't charge for periods less then 100%. So I don't plug in at 48% then unplug at 60%. I've learned this one from my Evo 4g, the battery was fantastic for months, then I started using the car charger to top off, and the battery life over the course of 2 weeks took a very noticable hit on overall life. I lost easily 4 hours a day usage on it. This on a phone and ROM combo that got me 16 hours a day.
Again this entire section is just what I've noticed and is purely my opinion, please do whatever you please with your device, it is yours after all!
ADB and Fastboot...is it really a faster boot?
No, fastboot isn't a toggle to boot at warp 9. Fastboot is a mode you can put your bootloader into for flashing the system for upgrades, repairs, mods, or general havok if you're not careful. The bootloader is what you see when you first turn on your device, that lovely Acer logo with the text up in the left corner (usually saying bootloader version and Unlocked Mode if unlocked, or nothing if it's locked). If you go into fasboot, it will say download usb protocol, so if you see that, you're in fastboot mode for whatever reason.
How do I get into fastboot mode?
Well you can do this in a couple ways, either Quickboot app (reboot bootloader), if you're on CM9, the power menu will give the option, or you can use ADB for it.
adb reboot bootloader
I'll explain some more about adb after fastboot, I know its odd, but one does have something to do with the other at times.
Once you've rebooted to the bootloader (device will turn off, vibrate, then boot to acer screen) you can then issue your fastboot commands assuming 2 things:
Acer USB drivers are installed and working correctly (if you use adb to reboot, then it is)
Your tablet is connected to your PC over USB.
Now, at this point, its up to you to do whatever you want, but BE CAREFUL USING FASTBOOT FLASH! It doesn't care or check what you're flashing, it'll just flash it. For example, I flashed CWM Touch recovery to boot once because I was distracted and mixed up the images for whatever reason. End result: Can't boot android. Why? Because boot was recovery, it only booted to CWM Touch recovery. Booting to actual recovery booted to TWRP, which was my previously installed recovery. I got it back easy enough once I figured out what I did wrong, but not all mistakes are reversible, or fixable!
General Fastboot uses and commands...
general layout goes like this:
fastboot (this is calling the command) flash (this is what fastboot will do) recovery (where it will send it to) recovery.img (the file it will send)
So, it looks like this:
fastboot flash recovery recovery.img
it will then flash whatever img to whatever partition you said, and let you know when it's done. You can flash any img to any partition, provided it fits, which means you do have to be careful about what you flash to where!
when you are finished with fastboot:
fastboot reboot
There are plenty of other commands, but the general basic use of fastboot is to flash a recovery or bootloader, so that is what I laid out above.
This section is hugely in need of improving, I know, but the guide in general is still rough, my apologies.
What about ADB?
ADB, or Android Debugging Bridge, can be used in System or in custom recoveries to interact with the device behind the curtain, meaning what you do isn't readily apparent on the device itself, unless you do something obvious like reboot it. ADB has a ton of commands, in particular in ADB Shell mode (you drop into the device shell itself, issuing commands from within itself, not from the PC).
Some random ADB commands:
adb reboot (where to reboot to) so:
adb reboot recovery
adb pull (what file to copy) /(where to copy file to) so for example, a recovery log to the adb working folder:
adb pull /cache/recovery/last_log recovery.txt
adb push /(file to copy to) /(file to send to device) so for example, placing that recovery file back into the device:
adb push recovery.txt /cache/recovery/last_log
Thats all the time I have for now, sorry in advance, I'm still working on all of this, I swear lol
Placeholder for additional tips and usage, some ADB stuff, and anything else I can think of.
Placeholder for Toubleshooting.
Placeholder for FAQS.
System Modding
justjackyl's Iconia A100 CM10 Setup & Use Tips/Tricks
A good guide to check out to try to get the most out of your A100 on CM10 (or any JB ROM like Sosei/black bean). A must read for those new to CM10/JB on these devices or in general. Not an outright mod, but a good source of information about some modding you should browse.
Hulu Flash Hack by NoSudo
What the Hulu Flash Hack by NoSudo does is allow you to use our android browser (setup according to the thread) to watch sites like Hulu to play on your android flash player. Its basic function is to scan for, then backup, then place a modified libflashplayer.so file. Setup with script manager and run at boot for best results. As always, read the thread for more information.
Mount Swap by crossix
What the Mount Swap by crossix does is pretty awesome, it mounts your external SD as internal, meaning your 32GB external SD card shows as internal, and is used for your apps, data, downloads, whatever, as if it was your internal SD. Internal SD is then mounted as external SD. It's operation is based on install-recovery being replaced with crossix's version. Instead of replacing recovery, it runs the mount swap. Requires Root, as the file is placed into /system/etc. Designed for stock/modified stock ROMs, it can be used with AOSP/AOKP ROMs by using script manager and setting it to run as Root at Boot. Please read the thread for the files and information on how to use it.
Adapted to ICS Build Prop Mods by patrick_spd4u adapted from crossix
What the Build Prop mods do is pretty basic, however can greatly increase the abilities of the A100, including faster boot times, more apps/games available for download in the Play Store, and tons of other stuff. Adapted from crossix's mods for HC.
Guide to 2 ways of running the crossix mount swap script, Acer based and AOSP/AOKP based
Direct paste from a post I made about this earlier...details using ES File Manager, however you can adapt it for any root file manager.
Using your tab, download the crossix mod zip file.
Unzip the file to get your epic mount swap mod by crossix, it can be unzipped anywhere.
At this point, I'm using ES File Manager but you can use Root Explorer or whatever. I'll be giving directions for ES.
Go into settings, scroll down and check the box for Up to Root.
Scroll a little futher down, same menu, and check the box for Root Explorer. Tap Yes, then allow when SU asks.
Now check the box next to Mount File System.
A little notice should pop up saying system is writable. If it fails at this point, you'll need to reroot, though it should work fine.
Press back, and go to where your crossix install-recovery.sh file is, hold your finger on it, and select Copy from the menu.
Press back and keep pressing it until you get to /. You'll see folders like acct, cache, config, d, etc.
Scroll down to system, and tap on it to go into system
Tap on etc to enter the etc directory.
You should now be in /system/etc, check up top there will be the address bar showing where you are.
You shouldn't have an install-recovery.sh file there, but if you do, long press it and select rename, then rename it install-recovery.bak.
On the upper buttons, select paste.
Now hold on the install-recovery.sh and select Properties, all the way at the bottom of that menu.
Next to where it says permissions, click Change
You will get a new window showing 3 rows of 3 colums of boxes with Xs.
Check the boxes so it looks like this:
XXX
XXX
XXO
Click on OK, then OK again, you should be back to the main ES window. Go ahead and hit home, or hit back over and over to exit.
Stock or Modified stock ONLY
Reboot the device by whatever method you prefer.
Once it finishes booting, wait a minute, then check your Settings>storage and your external SD card should show as internal. You only need to do this 1 time, it will continue to do this after.
AOSP/CM9/AOKP ONLY
Go to the Play store and download Script Manager(smanager).
After it installs, open the app then select Browse as root, Allow when SU asks, then click OK.
It will likely be listing /mnt/sdcard as your default directory, press the folder with .. to go back up until it says /
Click on system, then etc
It should now show /system/etc
Find your install-recovery.sh file, and it will open a new window.
Pay close attention here!
Right under the buttons that say Run Exit Edit Save are some icons,
Fav Su Boot Net Wick Ntfy
Press on Su and Boot, then click on Save.
Now exit smanager and reboot.
Wait a minute, then check settings>storage and your external SD should show up as Internal.
Don't disable smanager from running at boot! If you disable it, your script won't run. smanager must remain installed, or the script won't run.
Thanks to:
ZeroNull: For being one of the pioneers for getting our devices cracked open for our amusement!
ptesmoke: Also for being a pioneer in getting custom recoveries on our devices!
vache: For releasing the ICS leaks way ahead of schedule and hosting them for us to use and abuse!
civato: For releasing his Flex Reaper ROMs on our devices, his modified stock ROMs are still (IMO) the slickest available!
da-pharoah: For helping me understand how recoveries work a little better, allowing me to create Blackhole Wipe/Nullifier, and general encouragement for creating things for this device! (G2x and KF forums)
ezterry: For creating an OC/UV kernel that so far is the best EVER for any ROM on our device!
Theonew: reading ALL of that, and providing some nice info I missed and left out, and catching typos (Almost made it...)
crossix: that mount swap mod is just awesome, I never run a ROM without it!
NoSudo: creating a method to easily modify the system to watch HULU and other sites that normally won't allow it!
There's more I'm forgetting, I'll be adding more as I remember, I promise.
Even though I knew everything you posted, it was very interesting and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Theonew said:
Even though I knew everything you posted, this is a brilliant guide and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Click to expand...
Click to collapse
While sd-ext is safe to wipe, using factory reset wipes that for you, and I think, could be wrong, but cwm does it on data wipes. Part of why I missed it was I confused it with my phone, where wiping sd-ext bricks the phone, and also people mix it up with external SD. I'll add it in as its a very valid point, and I shouldn't let personal things interfere with the guide.
As for boot, our devices don't need that wiped and honestly asks for problems if someone doesn't restore or install a rom to cover it. I've never wiped it on any device, however I will also add that in as it is good info. I left it out of "safe" to prevent possible issues from wiping it.
I forgot about flex and I honestly don't know what it is for lol. Again thanks for reminding me and I'll add it in.
Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Tapatalked from my Galaxy S II.
pio_masaki said:
I forgot about flex and I honestly don't know what it is for lol....Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Click to expand...
Click to collapse
In your 4th to last sentence of the "Advanced Restore" section, you have a typo . Anyways, according to here: forum.tegraowners.com/viewtopic.php?f=10&t=149, Flexrom is "a partition on the nand that acer made to hold some proprietary apks and build information".
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
pio_masaki said:
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
Click to expand...
Click to collapse
One more thing - This occurred for one of my other devices, but the problem may still exist here. I haven't tried it with TWRP, but renaming CWM backups can cause a md5 mismatch error to occur. If this happens, simply rename it back to a date (in the default format).
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Awesome write up, thanks you guys!!
What about Zeronull's .014 v1.2 rom? http://forum.xda-developers.com/showthread.php?t=1574897
I'm still digging through all the threads for the ROMs, however I included the currently developed or recently released ROMs first, ZN has since released Green ICS, which is included already. I do plan to list every ROM, but it'll take some time to finish this guide up with as much info as possible, then go back and add things in.
pio_masaki said:
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Click to expand...
Click to collapse
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Theonew said:
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Click to expand...
Click to collapse
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
pio_masaki said:
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Theonew said:
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Click to expand...
Click to collapse
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
pio_masaki said:
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Done. The error seems to only occur when spaces are used in the name.
Theonew said:
Done. The error seems to only occur when spaces are used in the name.
Click to expand...
Click to collapse
Thanks for taking the time to figure that one out, I've been testing a new rom on my phone plus a new test T20 kernel for ezterry and getting cm9 build 5 up, just kinda managed to forget that experiment lol
I'll have some time...maybe...to append that new bit into that section tonight. The "free" time has been spent trying to get aokp for the a100 but my lack of experience, random problems with the repos and devs ignoring my PMs its been going slow. And by slow I mean nowhere.
Tapatalked from my Galaxy S II.
Great read. Sorta like flashing for dummies. Thaanks for your work.
Sent from my HTC Glacier using Tapatalk
It's great to have all this information compiled in one location. Looking forward to your next installment. THX
This is a guide for noobs
First things first, ask yourself am I using a T-Mobile Note II SGH-t889?
If you are not, stop now.
Now if your phone blows up, fires nuclear missiles, activates sky net, or becomes a nice pretty paperweight, I am not responsible. You are using this guide at your own risk.
That being said I have provided the exact methods I used to do this on me device and it works perfectly.
OK let’s begin.
First plug your phone into your computer.
-If you are getting an error message about a connection you must have windows xp SP3 or higher (vista, windows 7)
-you must also have the Samsung mobile phone drivers available here http://forum.xda-developers.com/showthread.php?t=961956
-you must also have windows media player 11 available on the Microsoft website.
Now that you have all this you should be able to explore the files on your phone, it will be under mobile devices.
Now on your desktop let’s make a new folder called System Folder, and in that Folder make two folders, one called ROM and one called KERNEL.
Now back on the desktop let’s make another folder called ODIN
SYSTEM FOLDER
-ROM
-KERNEL
ODIN
Let’s go over to the T-mobile note II XDA forum page http://forum.xda-developers.com/forumdisplay.php?f=1877
Now we’re going to go to the section called ORIGINAL ANDROID DEVELOPMENT
Download the KERNEL "peruses". http://forum.xda-developers.com/showthread.php?t=1960935
Download the one that says Perseus-alpha27.4-T889-CWM.zip (though the version number may change)
Put that file in the KERNEL folder (DO NOT UNZIP IT)
Download cwm6-recovery-n7100-121014.tar : http://www.mediafire.com/?mouxvj4og7azcow CWM md5: 67208cd19e82478af8591a83ca0a39b2 (the md5 is used to check your download, make sure you have no errors)
Put this file in the ODIN folder
Download CWM SUPERSU installable ZIP: http://www.mediafire.com/?w3i20sr6r58r8ah (put this in System Folder, DO NOT UNZIP)
SU md5 : 010b98d757544d7b2971574951c1d5e6
Download PC Odin: http://d-h.st/6Er put this into the Odin folder and unzip this one
Download Xquizit rom http://forum.xda-developers.com/showthread.php?t=1960950
Download the xquizit rom kitchen too.
Put these in the ROM folder, (DO NOT UNZIP)
This rom is straight forward, once you get the hang of flashing try other ROMs.
Now copy the System Folder to your phones external SD card.
Now open Odin and select the pda button and select the cwm6-recovery-n7100-121014.tar file in the Odin folder on desktop
Now switch off device and reboot in download mode by:
Press Vol down + Home +Power, and then, press Volume UP button in Warning Page to enter the Download Mode
Connect device to PC and wait till device successfully added to com port (it will turn light blue)
Hit ‘Start’ to flash
Once it flashed successfully, you can see 'PASS' in table above the ID: COM, you can disconnect device from PC
Now reboot into CWM by: Switch off device and press Vol Up + Home +Power hold about 5 second
Install SuperSu by selecting install zip from SD card, then select install zip from external SD card, then navigate to system folder and install the superuser.zip that is there.
Reboot.
Download Triangle Away from the play store or from http://forum.xda-developers.com/showthread.php?t=1494114
Run this and it will reset your flash counter to 0.
You have now achieved root.
Install titanium backup, and backup all of your user apps+data (USER APPS ONLY or just reinstall them all from the play store) (you can do this one by one or in a batch in the third tab if you have the paid version. (DO NOT BACKUP RED NAMED FILES, ONLY WHITE)
Download APN backup and restore from the play market
Open it, you will get an error, dismiss it and press the back button
Open titanium and find APN backup and restore, long press it and select to make it a system app.
Press home.
Open APN B&R. and dismiss the error, this time hit menu and disable the ICS check. Then press back and reopen it, NO ERROR
Now backup your APN settings.
Switch off device and press Vol Up + Home +Power hold about 5 second to go back into recovery
Go to the backup/restore section, and backup your current rom (do not skip this, we are about to erase your phone and if something goes wrong and you do not have this, pretty paperweight)
Now go back to the main menu
Wipe data and factory reset 3 times over, wipe cache 3 times over, now go to advanced and wipe dalvik cache 3 times over
now go back to the install zip from sd card menu and select the external sd card, navigate to system folder, and then Rom, then install the xqizit rom.zip file it will open aroma installer, it will give you options of what you want to do, you do not need to re wipe, install typical or custom to choose what apps you want, (svoice is removed unless you add it back under custom) then you want to install the 15 toggle mod.
Now once that is done, reboot the device, wait 10 minutes.
Now open the play store and update superuser
Download apn backup and backup the new tmobile apn with the wifi fix and titanium backup and restore your apps
You are now rooted and on a custom rom with multi window support. Hold down the back button to activate multi window.
Reboot into recovery
Install the perseas kernel zip from the kernel folder
Reboot the phone
Wait for the home screen
Reboot for good measure
You will want to put triangle away back on your device and run it again
You can download CPU control apps and over clock and under clock ECT.
You can change your boot animations; see my post under themes n apps for that.
Have fun and enjoy
Special thank to Dr.Ketan , Chainfire , Chenlu, simplelife, wild child, and any others I have forgotten to mention
Well I would say this needs a sticky...
But since we cant get anything stickied for no reason at all. It will just wander off into the forgotten realm of the tmobile note 2 forums in the dark cold depths of xda where no one cares to do anything to help organize this forum.
Not only do we have worthless posts repeated day after day to no end, and the same question asked repeatedly by the same user. The foreigners that dont have a clue. And trolling to no end. But a thread that could possibly help someone one day will just die along with 'help I bricked my phone' threads. What a shame...
Someone please sticky this
Sent from my SGH-T889 using Tapatalk 2
This snt fair to let this thread go into oblivion. Mods please sticky this guy actually spemt some time making something useful but you guys wont sticky it. Yet viirus comes on here and bilks money from the community and basically steals doing absolutely nothing to back up his promises and people treat me like crap.
But you guys loved him....this is messed up.
Do something positive for the community.
I was right the first time. Please just listen to me
Sent from my SGH-T889 using Tapatalk 2
Bump for your hard work.
This seems like a great tutorial and guide. The only thing missing might be pictures for the super noobs
I haven't tried this yet but i subbed for future reference
What about backing up the IMIE? Forgive me if it's in there it's just that I am very nervous about that. I am coming from the HTC Sensation and am not familiar with flashing Samsung phones. And from what I am understanding this issue is even new to those that have been flashing Samsung phones in the past
To be honest
I havr never backed up my imei
I only use sammy
I have never had a problem
Ill look into this for you though
Good point, better safe than sorry.
Sent from my SGH-T889 using Tapatalk 2
Thankyou for your kind words.
I made this for one particular person who was a bit afrade of rooting.
As always I share with the world for those who dont think to or are afrade to ask.
Sent from my SGH-T889 using Tapatalk 2
Don't wanna be a hater, but this guide is super drawn out. There is already plenty of guides that explain it much better, A for effort tho.
Yea its long but I mean where are the other guides? This forums a mess and theres no sticky thats what I was talking about
Sent from my GT-N7105 using Tapatalk 2
Thread closed
The stickies you all want regarding root already exist in the Development forum. Everything you need to know is contained in that thread.
*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.
Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?
KingKostas said:
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?
Click to expand...
Click to collapse
May I ask quickly what steps are involved in "reflashing"? Just to make sure I don't do some extra step or miss something.
As far as the stable version goes, I looked for the d2tmo file on get.cm under the Stable tab. I'm assuming that would be the most stable build?
(Perhaps a nightly might fix it??)
Question: Is there not a way I can just install/add this "4.2" camera? I've seen videos and read that people are using that just fine on CM10. Alternately if I boot into recovery would "fix permissions" be any help?
re: odin flash
Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
First thing you need to do is to install the stock Tmobile T999 rooted firmware.
Here are the exact step by step instructions with the download link for the firmware.
After you have followed these instructions your phone will be working properly and if
you like you will be able to flash any custom roms made for the Tmobile T999 phone
or restore any backups unless the the backup is corrupted in some way or another.
Here is the link to the Tmobile Stock & Rooted firmware you need:
http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware
(a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
Here is a step by step guide for you.
Download the firmware of your choosing (use the root66 version if you want root)
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the FW you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
Misterjunky said:
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
Click to expand...
Click to collapse
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!
re: camera issue
Malumen said:
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!
Click to expand...
Click to collapse
Just download any of the custom rom zip files based on the jellybean v4.1.1 stock rom.
All of those custom roms will have the files you are looking for.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
d2vzw
This also works on the sch-i535 as well. Thank you so much.
kingsugar said:
This also works on the sch-i535 as well. Thank you so much.
Click to expand...
Click to collapse
Yes, I tried all the other options for getting my camera back on track, but only going back to a full stock (rooted) ROM got my camera up and running again. FWIW, I was running an AOSP ROM for months without issue. What kicked my camera offline (the dreaded can't connect to camera) for some strange reason was when I updated to the most recent firmware VRBMF1. Now its straight back to AOSP for me! Thanks for creating this post! Very helpful!
My fix
I'm going around posting my fix to all the camera threads in hopes of helping people find a solution sooner. I created a thread over in d2vzw http://forum.xda-developers.com/showthread.php?t=2492304
fix camera error on i9300 with cm 9 (4.0.4)
Malumen said:
*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.
Click to expand...
Click to collapse
thanks a lot, i read your post, i take your advice to copy "SlimISP" to built in (cm system) folder, its work for me perfectly.
Thanks a lottttttttttttttttttttttt, have a nice day.
Note: This is an old phone. It's no longer being supported by Samsung, and I see that nobody is selling this phone except for eBay or Amazon. I also have a new phone now and my Discover is simply sitting there for me to have fun with. I won't be actively developing for this phone. However, I will provide support with any issues you may encounter. This thread will be kept here for future reference if anyone needs help.
Update (2022): I am no longer using Android. This is my last update here.Copies of the relevant files are shared in this google drive link:
SGH740M Root Files - Google Drive
drive.google.com
Please thank Ivdoan he is the mastermind behind finding and implementing root for this phone.
Thanks to JohnnyGalto for giving us updated CWM, TWRP, and Partition Tables!
THIS THREAD IS INTENDED TO USE ONLY FOR THE SGH-S730M, AND NOT FOR ANY OTHER PHONE. I CANNOT CONFIRM THAT IT WILL WORK ON ANY OTHER SGH-S730 VARIANTS, SO USE THIS THREAD AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY DATA LOSS, OR BRICKING THAT IS A RESULT FROM YOU CHOOSING TO ROOT. HOWEVER, IF YOU SOFT BRICK YOUR PHONE, IT CAN BE FIXED VIA CLOCKWORK RECOVERY. WARNING ABOUT USING ODIN: IF YOU ARE A NOOB, ONLY CLICK ON THE BUTTONS I TELL YOU TO CLICK, AND NOTHING ELSE. I ACCIDENTALLY SOFT BRICKED MY PHONE BECAUSE I HIT THE WRONG BUTTON WHILE USING ODIN - AND DONT WANT YOU TO DO THE SAME THING. AND LASTLY, ROOTING AND MODDING THIS PHONE WILL VOID YOUR WARRANTY. SINCE THERE IS NO OFFICIAL WAY TO RETURN TO STOCK, ONCE YOU MODIFY YOUR PHONE: YOU ARE ON YOUR OWN FATE!
IF YOU HAVE THE 730G VARIANT (Tracfone, Net10), GO HERE: http://forum.xda-developers.com/showthread.php?p=47417608
Click to expand...
Click to collapse
Issues and Bugs (Known Problems)
Okay, with deodexing - sometimes the SamsungIME.apk in the /system/app directory can be a pain to deal with! I put a warning in my deodex CWR script that tells about this issue. It does seem to correct itself overtime, so I am not too worried at the moment (but still very annoyed).
Also, it seems that many users have been experiencing strange battery problems (such as the phone suddenly losing half of its charge in 3 minutes). I hope it is an software issue (correctable), or just a battery issue (fixable), rather than a hardware issue (hard to fix).
Rooting, Custom Recovery, and Unbricking Guide (Everyone)
]If you want to root your phone then follow part A.
If you want to root your phone and add custom recovery then follow parts A and B.
If you have soft bricked your phone, then please complete all steps outlined below (if not already done yet).
The tutorial is done on a Windows computer and is meant for a Windows computer. Steps will vary slightly or tremendously if it is done on any other OS.
Part A - Rooting the SGH-S730m
1. Download and install UnlockRoot Free on your PC. YOU DO NOT HAVE TO INSTALL BLOATWARE!!! PLEASE READ SETUP INSTRUCTIONS CAREFULLY!!!
2. Download and Install Samsung USB Drivers. If it prompts you to reboot for any reason, then reboot your Computer.
3. After all of this is over, you have to prepare yourself for the hardest part of this whole process, and maybe the most complicated dilemma you will ever face in the entirety of your lives.
4. Turn on your phone if it isn't already. Wait for the phone to fully boot.
5. Plug your phone into the computer via USB.
6. Run UnlockRoot on your computer and click the "Root" Button (when it prompts you to install bloatware apps on your device, say no).
DO NOT UNPLUG YOUR PHONE UNTIL UnlockRoot SAYS IT IS OK TO DO SO!!!!
Congratulations, you have should now have a rooted SGH-730m in proximity to your hands! :fingers-crossed:
How to verify your 730M is rooted
If by any reason, you feel unsure as to if your phone is actually rooted or not:
Install a root checking app.
These apps will tell you if your phone has root access or not.
Try Root Checker from the Google Play Store.
Install a terminal emulation app.
In these apps, type the command "su" (without quotes). If you get "permission denied" you have not rooted your device. If it prompts you for root privileges (ie a popup appears) then your device is rooted!
Try Terminal Emulator from the Google Play Store.
If you are a n00b (like me occasionally), and you fail to understand why something works, or, the exact opposite: Don't worry! You probably thought the auxiliary headphone jack was the USB port, or, thought you should unplug your phone early, despite me warning you not to do that. That's okay, you can get it fixed.
Part B - Installing a Custom Recovery
If you are not already acquainted with the idea of Custom Android Recovery, don’t be afraid. It allows developers, tweakers and noobs alike to backup, restore, fix, and to install custom ROMs and Kernels designed specifically for their device. It becomes extremely useful, because it allows people to remove “soft bricks†from their devices (which occurs when someone flashes data to the wrong device, or wrong parts of the device respectively).
I know you probably just want to not read this stuff anyways But I need to pay tribute to the developers Ivdoan and JohnnyGalto for there amazing work at compiling these custom binaries for the Samsung Galaxy Discover. Thanks guys.
So, lets get started – shall we?
Click to expand...
Click to collapse
YOU MUST ROOT YOUR PHONE BEFORE YOU DO THIS!!!!!
1. Download either the SGH_S730M.CWM_6.0.3.1.custom.recovery.tar.zip or the SGH_S730M.TWRP_2.5.0.0.custom.recovery.tar.zip file, and extract its contents to your desktop (if you don’t know what a desktop is, then please leave. You will probably break your device).
Just to clarify for those noobs out there: CWR stands for “ClockWork Recovery†and TWRP stands for “Team Win Recovery Projectâ€. They both are custom recoveries, and basically do the same thing. Personally, I would recommend the CWR for people that just want simplicity, and the TWRP for people that want more appeal. TWRP for this device is still under development, so be careful!
Click to expand...
Click to collapse
2. Then, download the Odin Flashing Program attached to this post. Extract its contents to wherever you find necessary.
DO NOT MESS WITH ODIN! IT IS NOT A TOY! IT CAN BRICK YOUR PHONE!
Odin, is a flashing tool. It is not made to be user friendly, and is meant for people who know how to use it. I will be very blunt by saying that I AM NOT RESPONSIBLE FOR YOU NOT DOING EXACTLY WHAT I TELL YOU! PROCEED WITH CAUTION!
Click to expand...
Click to collapse
3. Right Click on Odin, and click “Run as Administrator†(if available).
4. CLICK ON THE PDA BUTTON
5. When the file window appears, browse to the desktop directory (your desktop) and select either the S730M-CWR.tar.md5 or the S730M-TWRP.tar.md5 (depending on what version you downloaded).
6. Now shutdown your phone. Plug your phone into your computer. Boot into download mode by turning on the phone (release the power button as the phone vibrates) and holding the lower volume button and home key. Follow the instructions (press the upper volume button) to continue with download mode.
7. If your phone has been detected by Odin, the proceed.
8. Inside of Odin, press the Start button.
DO NOT DISCONNECT, UNPLUG, PLAY WITH ANY BUTTONS, OR CLICK ANYTHING ON EITHER THE PHONE OR COMPUTER UNTIL ODIN HAS FINISHED FLASHING CLOCKWORK RECOVERY ON YOUR PHONE.
8. To boot into clockwork recovery, hold down the upper volume and power key until the first vibration, then just hold the volume key.
That should be IT! :highfive:
Part C - Soft Brick Recovery (CWM Recovery Only!)
YOU MUST HAVE A MICRO SD CARD WITH AT LEAST 400 MB OF FREE STORAGE SPACE TO DO THIS!
build.prop restore script
You need busybox installed on your phone in order to use this script! If you dont have busybox, it wont work.
If you messed up your build.prop file (If you did, then you will know that you did), then you can use this script to restore you build.prop file to the original stock format.
1. Download the build.prop restore script, to your device (preferably a computer).
2. Place the zip file to the root (/) directory of your micro SD Card.
3. Remove the SD card from the computer, and turn off the SGH-S730M.
4. Remove the back plating from the phone, and insert the micro SD card into the phone. It should be named SGH-S730M CWR stock build.prop.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see install zip from sdcard as highlighted text. Using the power key as the enter button, click the power button.
7. Then, also using the volume keys, scroll down to the choose zip from sdcard option, and click the power button.
8. If you placed the zip file exactly where I told you to: you should see SGH-S730M CWR stock build.prop as an item. Scroll down to the file and click the power button. Then, when it prompts you to "Confirm Install", scroll down to "Yes - install".
9. Press the power button.
WAIT FOR THE PHONE TO BE 100% DONE EXECUTING THE SCRIP! YOU COULD MESS UP THE PHONE. DO NOT TURN OFF THE PHONE.
Full Restore (If all else fails)
To reduce confusion, please remove any backups that you may already have (which would be funny, you wouldnt have to do this anyways).
1. Download the rooted stock CWM Recovery Image (.zip) from here, to your device (preferably a computer). http://forum.xda-developers.com/showthread.php?t=2677332
2. Extract ALL of the contents of the zip file to the root (/) directory of your micro SD Card. The folder should be named "clockworkrecovery".
3. Remove the SD card from the computer, and turn off the SGH-S730m.
4. Remove the back plating from the phone, and insert the micro SD card into the phone.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see backup and restore as highlighted text. Using the power key as the enter button, hit the power button.
7. Then, also using the volume keys, scroll down to the restore option, and click the power button.
8. If you extracted the zip file the exact way I told you to: you should see a menu option. If you didn't do what I told you to, you may see "No files found". If it says "cant mound /sd" (or something similar), you probably have a bad SD Card, or, forgot to put it in correctly.
9. Press the power button.
WAIT FOR THE PHONE TO BE 100% DONE RESTORING YOUR BACKUP TO THE PHONE! YOU COULD HARD BRICK THE PHONE (BECAUSE CWM RECOVERY WRITES TO THE BOOTLOADER). DO NOT TURN OFF THE PHONE. THE PHONE IS NOT FROZEN IF IT WONT RESPOND FOR A WHILE.
10. If you did this correctly, you should have a rooted, and restored SGH-S730m!
Part E - Removing that annoying triangle from the boot sequence
Use the triangleaway script in the attatchments. (triangleaway.zip)
It resets flash counter and resets binary status to official.
Might have to do a factory reset to return current status to official.
Boot your phone into recovery mode
Extract triangleaway.sh from the zip file.
Open up ADB Shell
push triangleaway.sh /tmp
chmod 755 triangleaway.sh
execute triangleaway.sh
Reboot Phone.
Overclocking and Modding (DEVELOPERS ONLY)
SYSTEM MODS
If you don't know what you are doing, then, please don't read any further. its for your own good
The CSC directory can be deleted (and the files in the main /system directory that are associated with it). It does not affect the phone at all. Also, If you go to /system/etc/feature_default.xml you can change the phones features. So far, I have done many tweaks to the Messaging, Phone, Settings, People (Contacts) and Lock screen of the phone! If you are a developer (or tweaker like me), you should be able to enable/disable whatever you like using the feature_default.xml.
Overclocking
FitAmp has made a overclocking script for 1GHz (1000MHz). There is quite a noticeable difference in response, but, the phone still tends to lag a bit. File is attatched to the thread (S730M-OC-1000MHz.zip)
Custom ROMs
Custom ROMS by atmu5fear. All flashable ZIPs. - http://forum.xda-developers.com/showthread.php?t=2677332
I'm also making one for the Discover. It should be coming soon.
Please click :good: if it works for you!
Where can I find the OC script? Thanks
evertking said:
Where can I find the OC script? Thanks
Click to expand...
Click to collapse
The Script it attached to this post.
Procedures (using ADB)
put boot.img on sdcard:
adb push boot.img /sdcard/boot.img
Then, from adbshell:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
then reboot device.
shifattk said:
the op of this post decided to dump this thread and developing, so i decided to take over & repost this, as requested by the op.
I will also organize and add more of my stuff. That might take at least a week or so since everything is a mess right now, but i will do it.
***** original thread is here *****
please thank ivdoan he is the mastermind behind finding and implementing root for this phone.
Thanks to johnnygalto for giving us updated cwm, twrp, and partition tables!
issues and bugs (known problems)[
okay, with deodexing - sometimes the samsungime.apk in the /system/app directory can be a pain to deal with! I put a warning in my deodex cwr script that tells about this issue. It does seem to correct itself overtime, so i am not too worried at the moment (but still very annoyed).
Also, it seems that many users have been experiencing strange battery problems (such as the phone suddenly losing half of its charge in 3 minutes). I hope it is an software issue (correctable), or just a battery issue (fixable), rather than a hardware issue (hard to fix).
rooting, custom recovery, and unbricking guide (everyone)
if you want to root your phone then follow part a.
If you want to root your phone and add custom recovery then follow parts a and b.
If you have soft bricked your phone, then please complete all steps outlined below (if not already done yet).
The tutorial is done on a windows computer and is meant for a windows computer. Steps will vary slightly or tremendously if it is done on any other os.
part a - rooting the sgh-s730m
1. Download and install unlockroot free on your pc. You do not have to install bloatware!!! Please read setup instructions carefully!!!
2. Download and install samsung usb drivers. If it prompts you to reboot for any reason, then reboot your computer.
3. After all of this is over, you have to prepare yourself for the hardest part of this whole process, and maybe the most complicated dilemma you will ever face in the entirety of your lives.
4. Turn on your phone if it isn't already. Wait for the phone to fully boot.
5. Plug your phone into the computer via usb.
6. Run unlockroot on your computer and click the "root" button (when it prompts you to install bloatware apps on your device, say no).
do not unplug your phone until unlockroot says it is ok to do so!!!!
congratulations, you have should now have a rooted sgh-730m in proximity to your hands! :fingers-crossed:
how to verify your 730m is rooted if by any reason, you feel unsure as to if your phone is actually rooted or not:
install a root checking app.
these apps will tell you if your phone has root access or not.
Try root checker from the google play store.
install a terminal emulation app.
in these apps, type the command "su" (without quotes). If you get "permission denied" you have not rooted your device. If it prompts you for root privileges (ie a popup appears) then your device is rooted!
Try terminal emulator from the google play store.
If you are a n00b (like me occasionally), and you fail to understand why something works, or, the exact opposite: Don't worry! You probably thought the auxiliary headphone jack was the usb port, or, thought you should unplug your phone early, despite me warning you not to do that. That's okay, you can get it fixed.
part b - installing a custom recovery
you must root your phone before you do this!!!!!
1. Download either the sgh_s730m.cwm_6.0.3.1.custom.recovery.tar.zip or the sgh_s730m.twrp_2.5.0.0.custom.recovery.tar.zip file, and extract its contents to your desktop (if you don’t know what a desktop is, then please leave. You will probably break your device).
2. Then, download the odin flashing program attached to this post. Extract its contents to wherever you find necessary.
3. Right click on odin, and click “run as administrator†(if available).
4. Click on the pda button
5. When the file window appears, browse to the desktop directory (your desktop) and select either the s730m-cwr.tar.md5 or the s730m-twrp.tar.md5 (depending on what version you downloaded).
6. Now shutdown your phone. Plug your phone into your computer. Boot into download mode by turning on the phone (release the power button as the phone vibrates) and holding the lower volume button and home key. Follow the instructions (press the upper volume button) to continue with download mode.
7. If your phone has been detected by odin, the proceed.
8. Inside of odin, press the start button.
do not disconnect, unplug, play with any buttons, or click anything on either the phone or computer until odin has finished flashing clockwork recovery on your phone.
8. To boot into clockwork recovery, hold down the upper volume and power key until the first vibration, then just hold the volume key.
That should be it! :highfive:
part c - soft brick recovery (cwm recovery only!)
you must have a micro sd card with at least 400 mb of free storage space to do this!
build.prop restore script
you need busybox installed on your phone in order to use this script! If you dont have busybox, it wont work.
if you messed up your build.prop file (if you did, then you will know that you did), then you can use this script to restore you build.prop file to the original stock format.
1. Download the build.prop restore script, to your device (preferably a computer).
2. Place the zip file to the root (/) directory of your micro sd card.
3. Remove the sd card from the computer, and turn off the sgh-s730m.
4. Remove the back plating from the phone, and insert the micro sd card into the phone. It should be named sgh-s730m cwr stock build.prop.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see install zip from sdcard as highlighted text. Using the power key as the enter button, click the power button.
7. Then, also using the volume keys, scroll down to the choose zip from sdcard option, and click the power button.
8. If you placed the zip file exactly where i told you to: You should see sgh-s730m cwr stock build.prop as an item. Scroll down to the file and click the power button. Then, when it prompts you to "confirm install", scroll down to "yes - install".
9. Press the power button.
wait for the phone to be 100% done executing the scrip! You could mess up the phone. Do not turn off the phone.
full restore (if all else fails)
to reduce confusion, please remove any backups that you may already have (which would be funny, you wouldnt have to do this anyways).
1. Download the rooted stock cwm recovery image (.zip) i made from here, to your device (preferably a computer).
2. Extract all of the contents of the zip file to the root (/) directory of your micro sd card. The folder should be named "clockworkrecovery".
3. Remove the sd card from the computer, and turn off the sgh-s730m.
4. Remove the back plating from the phone, and insert the micro sd card into the phone.
5. After putting the phone back together, boot into recovery by holding down the upper volume and power key until the first vibration, then just hold the volume key.
6. Using the volume buttons as scrolling keys, scroll down using the lower volume until you see backup and restore as highlighted text. Using the power key as the enter button, hit the power button.
7. Then, also using the volume keys, scroll down to the restore option, and click the power button.
8. If you extracted the zip file the exact way i told you to: You should see a menu option. If you didn't do what i told you to, you may see "no files found". If it says "cant mound /sd" (or something similar), you probably have a bad sd card, or, forgot to put it in correctly.
9. Press the power button.
wait for the phone to be 100% done restoring your backup to the phone! You could hard brick the phone (because cwm recovery writes to the bootloader). Do not turn off the phone. The phone is not frozen if it wont respond for a while.
10. If you did this correctly, you should have a rooted, and restored sgh-s730m!
part d - soft brick recovery (twrp recovery only!)coming soon..
part e - removing that annoying triangle from the boot sequence..to a thread near you! (it's already here. I'm just organizing them so it is easier to understand and to use)
deodexing, overclocking and modding (developers only)
deodexing you rom
you must have a micro sd card with at least 100 mb of free storage space to do this!
so, after some work (and tons of patience), i managed to make a deodexed version of this phone. So, ive made a deodex script for cwr, that will remove you old /system/app and /system/framework directories, and makes new ones, with the new deodexed files.*
now, since this is considered a more "advanced" tweak, i am not going to post a step-by-step guide on how to do this.
Why? Well, if you really needed instructions to do this: You probably shouldn't be doing it anyways!
For developers: Make sure you have busybox installed, then install the zip here via cwr (its easy to see what file it is). Remember to wipe dalvik cache. There are some temporary bugs with the samsungime.apk, which wont work right for a while. Mysteriously though, the problem corrects itself after some time using the phone. Reply your findings!
For noobs: Don't do this, it will just make no difference, and i honestly don't feel like solving problems that don't need to be solved (or, ones due to illiteracy). Wait until you know what you are doing (and what an odex file is), then try this yourself.
system mods
if you don't know what you are doing, then, please don't read any further. Its for your own good
the csc directory can be deleted (and the files in the main /system directory that are associated with it). It does not affect the phone at all.
Also, if you go to /system/etc/feature_default.xml you can change the phones features. So far, i have done many tweaks to the messaging, phone, settings, people (contacts) and lock screen of the phone! If you are a devleloper (or tweaker like me), you should be able to enable/disable whatever you like using the feature_default.xml.
overclocking
fitamp has made a overclocking script for 1ghz (1000mhz). There is quite a noticeable difference in response, but, the phone still tends to lag a bit. File is attatched to the thread (s730m-oc-1000mhz.zip)
please click :good: If it works for you!
Click to expand...
Click to collapse
and where is the odin did you the number
thanks
manuelelitaliano said:
and where is the odin did you the number
thanks
Click to expand...
Click to collapse
Hi there,
Sorry for the late reply. I've been quite busy lately.
http://forum.xda-developers.com/showthread.php?t=2189539
^ That thread has the downloads for Odin.
???
Hey guys,
have we found a way to fix my problem with the phone, I still have no access to download, recovery, normal boot and it stays on for 7 secs max. This has ocured because I flashed the wrong file to modem. Let me know as I want to start working on development again.
camvar97 said:
Hey guys,
it stays on for 7 secs max.
Click to expand...
Click to collapse
^ That, to me looks like the battery is not charged (unless I am wrong).
camvar97 said:
Hey guys,
... I still have no access to download, recovery, normal boot and it stays on for 7 secs max. ... This has ocured because I flashed the wrong file to modem.
Click to expand...
Click to collapse
I've searched around a bit, and the best option would be to send it for repair IMO.
shifattk said:
^ That, to me looks like the battery is not charged (unless I am wrong).
I've searched around a bit, and the best option would be to send it for repair IMO.
Click to expand...
Click to collapse
as for the battery thats what samsung says might be the problem and that i need a new one
SGH-730G Users ONLY
Here is a thread I started this morning about the SGH-730G (Tracfone, Net10, Straight Talk) variant of the Discover. I created this thread so there wouldn't be confusions due to the slight differences between the 730G and the 730M variants. Right now there is a root method listed, and I am working on an Odin flashable recovery from soft brick. I will also be posting things that I have figured out so far, and in the next day or so a full deodexed version of the stock firmware. Coming later will be a custom rom. If anyone in this thread has dev experience and has the 730M variant, PM me about this custom rom as I would like to make it compatible with both versions of the phone but will have to work out the differences between the two to make it fully compatible. New thread for the 730G - http://forum.xda-developers.com/showthread.php?p=47417608
TheGeekyNimrod said:
Here is a thread I started this morning about the SGH-730G (Tracfone, Net10, Straight Talk) variant of the Discover. I created this thread so there wouldn't be confusions due to the slight differences between the 730G and the 730M variants. Right now there is a root method listed, and I am working on an Odin flashable recovery from soft brick. I will also be posting things that I have figured out so far, and in the next day or so a full deodexed version of the stock firmware. Coming later will be a custom rom. If anyone in this thread has dev experience and has the 730M variant, PM me about this custom rom as I would like to make it compatible with both versions of the phone but will have to work out the differences between the two to make it fully compatible. New thread for the 730G - http://forum.xda-developers.com/showthread.php?p=47417608
Click to expand...
Click to collapse
I've added a link to your thread to the original post such that people don't get confused and/or break their phones. Thank you fore making the thread.
shifattk said:
I've added a link to your thread to the original post such that people don't get confused and/or break their phones. Thank you fore making the thread.
Click to expand...
Click to collapse
Word. I know some people were confused in another thread. Root methods are basically the same but there are structual differences between them when it comes to mounting points for restore and such. Thanks for addinthe link to the OP. I'll go back in a few and add a link here in my OP for the same purpose.
Does anyone know how to carrier unlock for this phone yet.
question?when i try to install CMW it keeps failing nand rite mode and restarting! any solution or different ay to try,still showing stock recovery but rooted!
Hello guys is there any way to unroot??? thanks
alexandros050 said:
Hello guys is there any way to unroot??? thanks
Click to expand...
Click to collapse
You can use unlockroot software to unroot.
I tested rooted and unrooted.
x1745 said:
You can use unlockroot software to unroot.
I tested rooted and unrooted.
Click to expand...
Click to collapse
Ok thank you very much for your reply
Take a look at This, I've created a flashable zip that both roots the phone and installs the overclock kernel found in this thread. Thought you might be interested
edit: I also just posted a flashable stock rom here. it's deodexed, rooted, and overclocked.
Restl3ss said:
Take a look at This, I've created a flashable zip that both roots the phone and installs the overclock kernel found in this thread. Thought you might be interested
edit: I also just posted a flashable stock rom here. it's deodexed, rooted, and overclocked.
Click to expand...
Click to collapse
I tried flashing your ROM, get error status 255, installation aborted...
shifattk said:
The Script it attached to this post.
Procedures (using ADB)
put boot.img on sdcard:
adb push boot.img /sdcard/boot.img
Then, from adbshell:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
then reboot device.
Click to expand...
Click to collapse
Phone wont boot past samsung logo after this. Followed your instructions exactly
atmu5fear said:
Phone wont boot past samsung logo after this. Followed your instructions exactly
Click to expand...
Click to collapse
Did you make a CWM backup before doing it? If you did, boot into CWM recovery and flash the recovery package.