Related
Hey guys I just finished runny simple root OTA edition. Everything went well and now I'm rooted. I am running into a couple of questions now.
1. Whats happens now? I'm rooted now how do i get those nice custom roms onto my phone?
2. I purchased ROM Manager because baked snacks rom says it was necessary for install but i can't get it to install clockwork mod, it keeps saying something about error running privileged commands.
3. How do I go back to stock ROM I'm starting to feel like I might be over my head at this point.
Thanks for your help guys.
I'm in the same boat. The two main reasons for rooting was for a new ROM and to use it as a hot spot (which so far I haven't been able to do.)
ROM Manager gives me the same error message about clockwork. Also, I would like to stop paying the $30 a month for the hot spot, so any help in that area would be appreciated.
Darrell
Keep at it!
loztboy said:
Hey guys I just finished runny simple root OTA edition. Everything went well and now I'm rooted. I am running into a couple of questions now.
1. Whats happens now? I'm rooted now how do i get those nice custom roms onto my phone?
2. I purchased ROM Manager because baked snacks rom says it was necessary for install but i can't get it to install clockwork mod, it keeps saying something about error running privileged commands.
3. How do I go back to stock ROM I'm starting to feel like I might be over my head at this point.
Thanks for your help guys.
Click to expand...
Click to collapse
0. Please read everything before doing anything. My post is a little chaotic, but you should be fine if you read everything first.
1/2. The usual disclaimer: I'm not telling you to do anything. I'm just providing information. I'm not liable for anything you do to you phone.
1. ROM Manager is definitely the easiest way, though the "real way" is to load your ROM of choice on the SD card and then flash it from Recovery (more on recovery later).
1 & 1/2. By the way, you should install Titanium backup from the market five minutes ago. Yes, it is that important. When jumping ROMs, you often have to wipe everything out. Without Titanium Backup, you could end up having to repurchase apps and redownload all of your free ones, losing progress in games and settings in apps, etc. The free version of Titanium Backup lets you back up easily enough, but you want the donate version to prevent restores from taking a few hours of user interaction (Yes, I said user interaction, meaning sitting there and pressing buttons for hours). Once you throw $4.00-$50.00 (you can pick within that range, you get the same product regardless of amount) at Titanium Backup (and wait a day or so to get the license key file), you can do a restore in 15 min without any interaction beyond hitting start (or, more accurately, begin batch process). This app has saved my life time and time again. I literally did my first backup out of curiosity for the app and then totaled my phone in the next five minuets. It even backs up your home screen layout. GET IT NOW!!! YOU WILL HATE YOURSELF IF YOU DO NOT GET IT!!! At least get the free version, because, as stated above, it does backups fine. You (like me) will be scared into paying when you realize that you just wreaked everything and really don't want to spend the next few hours restoring. However, Titanium backup will not function until you get Superuser app working, as detailed in point 2 below.
***EDIT: I forgot to mention that Titanium Backup should work after running this program. It should even fix clockwork for you***
2. There are three possibilities for that error: 1: You don't have the superuser app installed. It dishes out the privileges. If you don't have it (if you do go on to potential issue number two and be grateful), you can install it by downloading this file and putting it on the root of the SD card. Then boot into recovery (I'm sure there is a tutorial for getting into recovery floating around here somewhere, just search the EVO section) and flash the .zip Presto! Superuser app is installed. If you prefer not to go around flashing random packages recommended by strangers on the internet, you can research and download superuser app at the source 2: If you found the Superuser app in the app drawer (the screen with all the applications where you scroll down in alphabetical order and pick the one you want to use), open it. You may have bumped "never give superuser access to this app" (or words to that effect) the first time you opened ROM Manager. If so, it will be listed in the Superuser app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as red. Just have the superuser app forget ROM Manager and then try to flash custom recovery from within the ROM Manager again, being sure to say "Yes!" when it asks for superuser privileges. 3: If you have no recovery to flash superuser from or superuser is installed and ROM Manager is green inside and it still fails, the SimpleRoot failed. If you skipped a step in the rooting process, go back and do that step. If not, just start over and run all the steps from the beginning, Also note that if you accepted the over the air update, you need the OTA version of SimpleRoot, not the original one.
3. Now, about total reversal. I'll be honest: There is probably a way to go back to stock that works without finishing the root process (probably something to do with PC36IMG.zip) files, but I don't know it. The way I would do it would be picking the OTA Stock ROM from this page and flashing it after getting recovery installed at the end of a successful root process. However, then you would have succeed in your original endeavor and would have no need to go back. There is a program here that supposedly does just enough tweaking to the phone to give you the recovery you need to flash back to the stock ROM, but I have not used it myself and therefore cannot vouch for it.
dws51 said:
I'm in the same boat. The two main reasons for rooting was for a new ROM and to use it as a hot spot (which so far I haven't been able to do.)
ROM Manager gives me the same error message about clockwork. Also, I would like to stop paying the $30 a month for the hot spot, so any help in that area would be appreciated.
Darrell
Click to expand...
Click to collapse
If you both succeed in the root process (and I encourage you to persevere, the reward is spectacular), I personally recommend Cyanogen Mod 6. I believe that you can get the nightly builds of CM6 from ROM manager, but the release candidate is likely more stable. I use the RC myself and have never looked back. My battery lasts forever and my phone is never unresponsive. And because the CM6 ROM is based of of Android 2.2 (Froyo), free tethering is built in to the OS and done so rather elegantly, meaning no more dirty hacks for tethering. Just know that if you go that route, though you have the best of the best, you will need to tinker a bit to get everything working. Also, 4G, the FM Radio, and HDMI output are flat out not working in the RC (I'm sure they will be fully functional in the final release, and the not-workedness is a software thing, meaning that the hardware is fine and will come online when you again install a ROM that supports it). On the other hand, with this ROM you can force the phone to roam on Verizon's network when Sprint's 3G speeds are less than desirable.
I'm not sure where to put this, so I'm sticking it here. As soon as you get custom recovery working, you want to backup with Nandroid. The easiest way is from ROM Manager. Just hit "Backup ROM". This backs up not only your setup (like Titanium Backup), but also all the crucial bits that lie underneath and keep your EVOs humming, bits very very difficult to replace. HOWEVER, this is NOT a replacement for Titanium Backup, because it can only restore to the same ROM. If you attempt to restore to a different one, it will put the one you had at the time of the backup back on.
Whichever way you go, I wish the both of you luck. You're entering into the wild and wonderful world of devices that you actually own!
that was a great post im in the same boat as those guys above and im sure we are not the only ones, when you say put the file on the root of the sd card what is the root of the sd card? if i dont know that should i just not even be rooting?
edit
I just downloaded rom manager and i get the same response " an error occurred while attempting to run priviliged commands" i went through the root process and it said i was rooted, i read earlier that to check it i was rooted and nand unlocked that if i checked my hboot and it was 0.76 i was rooted and nand unlocked if i was 0.79 the root didnt work i was .76. Is there a different way to check if my root went through
The root of the SD card is the 'directory' you're in when you plug the card into the computer & you see folders like ".Mail" "Android" "DCIM" etc.
It's up to you if you think you can handle rooting. I used SimpleRoot & it was incredibly easy, but i have been familiar with modding phones for awhile now.
jdjozwia said:
that was a great post im in the same boat as those guys above and im sure we are not the only ones, when you say put the file on the root of the sd card what is the root of the sd card? if i dont know that should i just not even be rooting?
edit
I just downloaded rom manager and i get the same response " an error occurred while attempting to run priviliged commands" i went through the root process and it said i was rooted, i read earlier that to check it i was rooted and nand unlocked that if i checked my hboot and it was 0.76 i was rooted and nand unlocked if i was 0.79 the root didnt work i was .76. Is there a different way to check if my root went through
Click to expand...
Click to collapse
The root of something simply means not in a folder, e.g. on your computer it would be just G:/ (or whatever letter your SD card is mounted to). Just open the SD card and put whichever file you are referencing right there, not in any folder.
By the way, anyone can root, so long as you are willing to learn and willing to take a few risks. As long as you stay well informed, you usually don't break anything. And there is usually a way out, even if you make a train wreak, though it may be ugly. Independent developers (not me; smart people like Cyanogen and Toast who actually make these awesome ROMs and roots) have a better track record for keeping dangerous stuff out than some corporations. ***Cough***McAfee antivirus broke thousands of computers with a defective update***Cough*** Scientia est vox. Knowledge is power. Know what you're doing, and you'll be fine. You will make mistakes (I know I have), but stay sharp and know the consequences, how to go back, who to ask when things go South, and you'll do alright. The community here at XDA is one of the best and most helpful I have ever seen. If you're not totally hosed, someone will pull you out of the fire. It probably won't even be me. I'm no pro. But there is no shortage of pros here at XDA.
so what would you guys say the next step for me is, should i just do the simple root over? how can i check to see if im rooted? and what should i do about this rom manager giving me trouble with flashing the clockwork mod
See Above
jdjozwia said:
so what would you guys say the next step for me is, should i just do the simple root over? how can i check to see if im rooted? and what should i do about this rom manager giving me trouble with flashing the clockwork mod
Click to expand...
Click to collapse
If titanium backup works, you have root. As for Clockwork, please see my first post, where I went over it in detail.
OK well i installed titanium back up and busy box and it looks like im rooted? Im going to try to flash that superuser app tmw i left my usb cord at work so in about 12 hours ill probly be back with more questions
thanks for the encouragement the answers and most of all your time
Cut the cord
jdjozwia said:
i left my usb cord at work
Click to expand...
Click to collapse
It's personal preference, but there is a throughly cool free app called Awesome Drop that lets you send files without a cable. When you use it, files end up in the /drop directory on your phone. If necessary, you can move them out with a program like Astro File Manager.
By the way, Titanium backup shouldn't work without SU app, so I'm wondering if you do in fact have it. Have you looked through the S section of the App Drawer?
Techrocket9 said:
It's personal preference, but there is a throughly cool free app called Awesome Drop that lets you send files without a cable. When you use it, files end up in the /drop directory on your phone. If necessary, you can move them out with a program like Astro File Manager.
By the way, Titanium backup shouldn't work without SU app, so I'm wondering if you do in fact have it. Have you looked through the S section of the App Drawer?
Click to expand...
Click to collapse
I just went through my S' and all i have are the ones that came with the phone no super user but when u say it shouldnt work what should happen when i open the app?
jdjozwia said:
I just went through my S' and all i have are the ones that came with the phone no super user but when u say it shouldnt work what should happen when i open the app?
Click to expand...
Click to collapse
It should complain about being unable to acquire root privileges.
___
An army of pacifists can be defeated by one man with the will to fight.
yeah when i open it it doesnt say that and it says my root access is ok,
I DL astro and when i open it one of the folders is clockwork mod and if i search i find super user app on my sd card when i reboot my phone by holding the down volume it goes to the hboot screen and askes me if i want to update my phone i say no and then when i go to recovery it does not give me the option to flash the super user app. it takes me to android system recovery with four options. At the very bottom it says E: cant open/cache/recovery/command
?
Is one option to flash zip from SD card?
___
An army of pacifists can be defeated by one man with the will to fight.
How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
As for CM6, don't get me wrong, I LOVE CM6, but, Fresh 1.0.1 or the latest Damage Control might be a safer bet. For your first rom CM6 needs more coaxing than you might like. Also tethering is installed by default in the 2.1 roms from those guys and it's (imho) easier and more obvious to use.
Keep at it, there will be times you feel like giving up even after you get past this point, just don't take it too seriously and remember that as long as you are still getting phonecalls your phone is still doing it's primary job, the rest is just icing. Icing that gets more delicious with time, like beer, mmmmmm beer.
Where was I?
Oh yeah, good luck!
Crap, forgot, when someone says "put it on the root of the SD card" the easiest way to do that is hook it up via USB, hit the status tray that says "usb connected" and check the Hard Drive option. Then just copy your file to the new drive that will show up in windows (might pop up automatically depending on your windows settings) and boom, it's on the root of the SD card.
As for the "real" way to flash. Do the above, putting the .zip file containing whatever rom you want (for instance CM6, or Fresh 1.0.1 which you can obtain over in Development forum from their respective posts) on the root of the SD card. Safely remove the device (on windows it will be in your status bar, usually looks like a plug with a green arrow, click it, choose Mass Storage Device and then hit Stop, it will tell you when its done, make sure you have the folder closed before you do this or it will grump at you) and switch back over to Charge Only on your phone. Then power off the phone (hold the power button with the phone unlocked, choose Power Off, then Ok) and hold the volume down button. Then press power, don't let go of volume down but you don't have to hold power, just press it to turn it on. A white screen should come up, let go of the volume button, and one option will be Recovery. Use volume up and down to select it and press the power button to select. It should then boot you into recovery which should have an option to "wipe", you want to wipe dalvik cache, then cache, then factory defaults. Then go back up (in AmonRA that means hitting vol-up and vol-down at the same time), then goto "Flash .zip from sdcard" select it, hit power, select the zip file, power again, power one more time to confirm.
Once it's done you hit Reboot System Now and viola, first boot takes FOREVER so don't fret.
alcaron said:
How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
QUOTE]
where exactly do i type adb shell? when i did the simple root i do not remember replacing my recovery with a recovery of my choice so thats probly where my problem is and i do not know how to check my superuser permissions
Click to expand...
Click to collapse
Techrocket9 said:
Is one option to flash zip from SD card?
___
An army of pacifists can be defeated by one man with the will to fight.
Click to expand...
Click to collapse
no the option i get is update to zip and when i click that it does stuff for me and i cannot choose a file i think my problem lies to not choosing what recovery i wanted?
jdjozwia said:
no the option i get is update to zip and when i click that it does stuff for me and i cannot choose a file i think my problem lies to not choosing what recovery i wanted?
Click to expand...
Click to collapse
It is possible. The program I mentioned earlier (unrEVOked) should install a custom recovery for you. I can't put a link in this post because I'm on my phone, but a quick google search should find it.
An army of pacifists can be defeated by one man with the will to fight.
jdjozwia said:
alcaron said:
How to check if you are root: Assuming you have ADB installed (you used simpleroot so, possibly not) just type "adb shell" into a command prompt. If it comes up with a "#" you are root, if it comes up with "$" type "su" and hit enter, if it switches to a "#" you are rooted. Also you can get a terminal emulator app (I love Better Terminal Emulator) and open it, type "su" and see if it gives you "#".
Did you do the SimpleRoot step where you replaced the recovery with your recovery of choice? I know more than one person that didn't do that step. Though the app should at least still TRY to reboot.
As said before, check your SuperUser permissions to make sure you didn't disallow Rom Manager.
QUOTE]
where exactly do i type adb shell? when i did the simple root i do not remember replacing my recovery with a recovery of my choice so thats probly where my problem is and i do not know how to check my superuser permissions
Click to expand...
Click to collapse
If you just did SimpleRoot (i.e. didn't download the android SDK) you probably don't have ADB installed on your PC. So then you'd want to go the terminal route. Search the market for Better Terminal Emulator
Click to expand...
Click to collapse
This should work for any and all a100 Honeycomb builds, you'll need to install an app from the market called terminal emulator. Also, you'll need a file manager like Astro to unzip the file.
This mod should root your tab in a matter of seconds after the script file is launched. I've tested this on my tab from a clean build and it works like a champ.
Here we go!
- Install the following apps from the market:
Terminal Emulator
https://market.android.com/details?id=jackpal.androidterm&hl=en&rdid=jackpal.androidterm&rdot=1
Astro File Manager
https://market.android.com/details?id=com.metago.astro&hl=en
- Download the attached file from this post.
- Extract and put both the root.sh and su in /mnt/sdcard from the root.zip file.
(Using Astro, find the root.zip file it might be in /mnt/sdcard/Downloads or could be else where if your not using the website to view XDA. Copy it from where ever it's at and paste it in /mnt/sdcard. Press your finger on the zip file and tap Extract when the menu pops up. Tap "Extract to This Directory".)
- Next, open terminal emulator and copy / paste the following:
sh /mnt/sdcard/root.sh
Text will fly by, the script will automatically copy the su binary and install it to the proper location.
Once the script finishes running, be sure to install superuser from the market:
Very Important, if you skip this you won't be "officially rooted yet"!!!
https://market.android.com/details?id=com.noshufou.android.su
Open the superuser app once it's installed, click on the wrench in the upper right corner, scroll to the bottom and find "Su binary v... Tap to check for updates" and tap that link. It should bring you to an update screen, click the button at the bottom to update!
Once you have done the above, then install busybox, Titanium, etc.. if needed.
Thanks goes to abliss for origionally coming up with the root commands!
This mod really just automates his work.
permission denied every step of the way. Used both script manager and terminal
ok terminal manager is out, I didn't realize that doing a hard reset wouldn't wipe the /system/xbin directory completely so technically busybox tools were still installed and sh wouldn't normally be there. I'll see if there's another way..
this method work for any build? and if so, is there any problem during the process that could "kill" my a100 or it's safe?
This method should, yes and it's safe.. It's actually more safe (if that's possible) than the method origionally posted in the dev section since there really isn't any room for user error.
Sent from my MB860 using XDA App
Ill give the new method a go around tomorrow and report back for you.
I wasn't expecting it to anyway, but I figured I'd let you know this doesn't work on the A101.
Hoping someone can find a working root method for this model.
Sorry to hear about the a101, that thing sounds like a tough nut to crack!
Sent from my MB860 using XDA App
This working for me i manage to root my a100
It works and its so simple
Thank you so much for this! It was so easy. Though the only problem I had was with the terminal emulator, no fualt of the Dev, but it might help someone. When I was trying to write in the line of code I kept getting errors because I couldnt get the keyboard to write lower case. So copy and paste if your a noon like me to get it through the terminal.
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
mvan4310 said:
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
Click to expand...
Click to collapse
You sure you don´t have an a101? what build number are you running?
A100_2.007.04_COM_GEN1
Most definitely an A100...
mvan4310 said:
A100_2.007.04_COM_GEN1
Most definitely an A100...
Click to expand...
Click to collapse
I have no idea then.. the only thing I could say is to try and restore from a "Full" rom, like Acer_A100_1.014.08_COM_GEN1 and try to root it before doing anything else. It wouldn't hurt to try anyway and the worst that could happen is that you'd have to restore all your apps and stuff. If we can ever get this thing to run cwm and a different kernel, you'll definitely be needing root.
Works great!
Thanks so much for the script and instructions. Im enjoying my rooted tab yay!
mvan4310 said:
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
Click to expand...
Click to collapse
Did you check the boxes for USB Debugging and Unknown sources just in case?? (in Settings > development)
I checked them both. Root Checker shows I have root, but other apps cant get root access, and SuperUser cant update because of this issue... I dont know what the hell to do because this has me stuck atm... Im gonna flash back to 1.018 and see if that helps, probably not, but it wont hurt to check.
EDIT:
I reverted back and got root. It seems to be the newest update that stopped it. Im updating back up again to see if I retain root. What a pain...
Edit 2:
Yep, Im rooted now. It unrooted me when updating, ran the script you provided and its working now. Dont know why it didnt take before reverting back, but works wonderfully now. Now that Im rooted, let me know what I can do and peek around at to help out here.
Has anyone tried that on an A500?
A500 has its own rooting methods. You can find info about the A500 here
http://forum.xda-developers.com/forumdisplay.php?f=1136
Thanks alot crossix. Worked like a charm.
Sent from my A100 using Tapatalk
I have the Hong Kong variant of the Galaxy Nexus GSM (yakjuzs) running 4.0.2.
I haven't even unlocked the bootloader yet. (Stupid, I know.)
I've had the phone long enough to know "how it's supposed to behave" so that when I unlock and root a ROM I'll know if something is behaving badly, so now I'm looking to switch to the latest/greatest yakju (who comes up with these terrible names?) 4.0.4.
However, before I do so, I'd like a perfect backup of my phone 'as-is' so that if something goes horribly, horribly wrong I can get back to the 'original state'.
Now, I've done some reading around and I'm confused. It looks like I need several different kinds of backups, and I'm not even sure if all of them are going to be 'worth it'.
First, I found the Galaxy Nexus Toolkit. It only mentions the yakju variant, not my yakjuzs, but it "seems to" work for making a backup of my phone's data. I just haven't tested the backups, nor do I know how to, so I don't know if it's actually working or not.
I'm just not sure what it's backing up. It's obviously NOT backing up the ROM or radios (is there anything else it's not backing up?), and I don't know what it means by "System Apps", nor "apps data". Obviously it's backing up all the APKs I've installed from the market, etc. That part I get. What else is it backing up? (I know it's also backing up the virtual SD card if I tell it to, as long as I uninstall Google Currents first, which seems to have a directory structure that doesn't jive well with Win7.)
Secondly, I found this thread about backing up the Desire S which I'm going to take a wild guess and say that the advice given in it still applies to my phone as well: namely that a "NANDROID" backup will backup the ROM and radios and other 'stuff' on my phone that the GNT doesn't grab.
Thing is: I don't know what "Clockwork Recovery Mod" or "NANDROID" are, or where to get them. If I Google "Clockwork Recovery Mod", it takes me to this page which doesn't have anything on it called "Recovery Mod" at all. Is it the "ROM Manager" app?
A little more Googling suggests that this is true, or at least that I can get "Clockwork Recovery Mod" through that app (weird way of getting it, honestly), but I thought I'd ask here first.
Is "NANDROID" a part of CRM? I'd use this, which is the first thing that shows up when I Google 'Nandroid', but it seems to be four years old, and references phones that I might not even be able to find on eBay, so I'm thinking it's not a trustworthy source.
Of course, all of this requires root, right? I've been told this requires unlocking the Bootloader, though I do see this exploit that lets you get Root without doing that. So, basically, I can root with that exploit, then download that 'ROM Manager', use it to flash CRM over my locked Bootloader, then use that to do a NANDROID backup of my phone?
Right?
And, regarding that whole 'rooting/superuser' thing, I know that the 'standard' is to use 'superuser.apk' for root permissions for apps. I've read about SuperSU, the 'superior' superuser alternative. Does that require superuser.apk, or can it be used as a replacement for it? And if it can be a replacement for superuser.apk, does that mean I can use it *instead* of superuser.apk in that root exploit? How would I get the APK to use? Buy it on the market, and then somehow (adb pull? Is that it?) take the APK off of my phone and on to my computer?
I'm asking mostly because any app that checks for 'root permissions' (such as Google Movies Play Movies Play Play Movies or whatever it's called) apparently dislikes root permissions being available on a phone, but only checks for a file called 'superuser.apk'. If I don't have that file, no problem, right?
Finally, how do I get the 4.0.4 yakju straight-from-Google ROM? Do I need new radios for that? Where do I get those? No, I don't want AOKP or CM9.
Moleculor said:
[snip]
Of course, all of this requires root, right? I've been told this requires unlocking the Bootloader, though I do see this exploit that lets you get Root without doing that. So, basically, I can root with that exploit, then download that 'ROM Manager', use it to flash CRM over my locked Bootloader, then use that to do a NANDROID backup of my phone?
Right?
Click to expand...
Click to collapse
Right. Root with the exploit, install ROM Manager from the market, use ROM Manager to flash CWM recovery, boot into CWM recovery, and perform a (nandroid) backup. This will be saved in a folder in /sdcard. Now you have to pull all of the data off your phone somehow*, and save it to your computer. Then follow this guide to flash yakju 4.0.4.
*The easiest way to pull the data off your device is to boot into CWM recovery, and plug into your computer (assuming you have the drivers set up properly), open a command prompt in the directory where you have your adb.exe file, and type adb pull /data/media. This will put everything in /sdcard onto your computer.
Moleculor said:
And, regarding that whole 'rooting/superuser' thing, I know that the 'standard' is to use 'superuser.apk' for root permissions for apps. I've read about SuperSU, the 'superior' superuser alternative. Does that require superuser.apk, or can it be used as a replacement for it? And if it can be a replacement for superuser.apk, does that mean I can use it *instead* of superuser.apk in that root exploit? How would I get the APK to use? Buy it on the market, and then somehow (adb pull? Is that it?) take the APK off of my phone and on to my computer?
I'm asking mostly because any app that checks for 'root permissions' (such as Google Movies Play Movies Play Play Movies or whatever it's called) apparently dislikes root permissions being available on a phone, but only checks for a file called 'superuser.apk'. If I don't have that file, no problem, right?
Finally, how do I get the 4.0.4 yakju straight-from-Google ROM? Do I need new radios for that? Where do I get those? No, I don't want AOKP or CM9.
Click to expand...
Click to collapse
Just flash su and you will be fine. There are still some issues with supersu that have not been sorted out yet. (And by the way, the file that the apps look for is su, not Superuser.apk. Superuser.apk does not give root access - it basically acts as a firewall for apps requesting root from the su binary.)
efrant said:
Right. Root with the exploit, install ROM Manager from the market, use ROM Manager to flash CWM recovery, boot into CWM recovery, and perform a (nandroid) backup. This will be saved in a folder in /sdcard.
Click to expand...
Click to collapse
Ok, this is one thing I've never understood: I don't have an /sdcard, or at least I don't see it. Is this because I don't have root, and thus when I access my phone's internal storage, it's shortcutting me directly into /sdcard as if it's the root directory, thus I never see the directory /sdcard is in?
efrant said:
Now you have to pull all of the data off your phone somehow*, and save it to your computer. Then follow this guide to flash yakju 4.0.4.
*The easiest way to pull the data off your device is to boot into CWM recovery,
Click to expand...
Click to collapse
Ok. Wat? I've booted into the stock bootloader once before, would I do that same process to get into CWM recovery once CWM recovery is installed? And can a CWM recovery be installed on a phone with a locked bootloader (but with root)? Or should I just bite the bullet and unlock the bootloader?
efrant said:
and plug into your computer (assuming you have the drivers set up properly), open a command prompt in the directory where you have your adb.exe file, and type adb pull /data/media. This will put everything in /sdcard onto your computer.
Click to expand...
Click to collapse
Wait, what? Ok. I'm an ancient IBM-DOS and MS-DOS user, so I 'get' directory structures, but... where exactly is /sdcard? What's the directory structure of the phone like? Because /data/media doesn't exactly scream "/sdcard" to me.
efrant said:
Just flash su and you will be fine. There are still some issues with supersu that have not been sorted out yet.
Click to expand...
Click to collapse
Aww. SuperSU looked so nifty.
efrant said:
(And by the way, the file that the apps look for is su, not Superuser.apk. Superuser.apk does not give root access - it basically acts as a firewall for apps requesting root from the su binary.)
Click to expand...
Click to collapse
Hm. So if the APK were to instead look for... say... "tacolicker" instead of "su" for root access, apps that detect root would be less likely to find root access and be all DRM-y?
----
Also, I downloaded the binaries for 4.0.4 from the AOSP, including radios, drivers, etc. Do I leave them in the tarballs? (Those are called tarballs, right? The TGZ files? Only used linux for two minutes in my life, not counting this phone,) Or do I extract them first? And I'm assuming some of this goes onto my phone... somehow?
Moleculor said:
Ok, this is one thing I've never understood: I don't have an /sdcard, or at least I don't see it. Is this because I don't have root, and thus when I access my phone's internal storage, it's shortcutting me directly into /sdcard as if it's the root directory, thus I never see the directory /sdcard is in?
Click to expand...
Click to collapse
Yes, it is shortcutting you there.
Moleculor said:
Ok. Wat? I've booted into the stock bootloader once before, would I do that same process to get into CWM recovery once CWM recovery is installed? And can a CWM recovery be installed on a phone with a locked bootloader (but with root)? Or should I just bite the bullet and unlock the bootloader?
Click to expand...
Click to collapse
Yes, CWM can be installed with root and a locked bootloader. What I suggested to do is root, install CWM, backup, then unlock.
Moleculor said:
Wait, what? Ok. I'm an ancient IBM-DOS and MS-DOS user, so I 'get' directory structures, but... where exactly is /sdcard? What's the directory structure of the phone like? Because /data/media doesn't exactly scream "/sdcard" to me.
Click to expand...
Click to collapse
That is because /sdcard is just a symlink (linux term -- just a link/shortcut) to /data/media, which is the actual directory.
Moleculor said:
Aww. SuperSU looked so nifty.
Hm. So if the APK were to instead look for... say... "tacolicker" instead of "su" for root access, apps that detect root would be less likely to find root access and be all DRM-y?
Click to expand...
Click to collapse
Yes.
Moleculor said:
Also, I downloaded the binaries for 4.0.4 from the AOSP, including radios, drivers, etc. Do I leave them in the tarballs? (Those are called tarballs, right? The TGZ files? Only used linux for two minutes in my life, not counting this phone,) Or do I extract them first? And I'm assuming some of this goes onto my phone... somehow?
Click to expand...
Click to collapse
Follow the directions in the link I provided in my previous post. If you do that, you will need to extract everything: the tgz, the tar, and the zip inside.
efrant said:
Yes, CWM can be installed with root and a locked bootloader. What I suggested to do is root, install CWM, backup, then unlock.
Click to expand...
Click to collapse
Ok, just to completely clarify... to boot into CWM Recovery, I hold both volume buttons and turn the phone on? Or is that just the bootloader, and Recovery is something different? Or am I right, but I'm missing a step?
efrant said:
That is because /sdcard is just a symlink (linux term -- just a link/shortcut) to /data/media, which is the actual directory.
Click to expand...
Click to collapse
S'what I thought. They use the same thing in Win7, apparently.
Thanks!
Moleculor said:
Ok, just to completely clarify... to boot into CWM Recovery, I hold both volume buttons and turn the phone on? Or is that just the bootloader, and Recovery is something different? Or am I right, but I'm missing a step?
Click to expand...
Click to collapse
To boot into CWM recovery (after you flash it), you can:
1) Hold both volume buttons and turn the phone on to get you into the bootloader, then scroll with the volume buttons until you see recovery and then select it with the power button; or
2) Install Quick Boot from the market. Awesome app.
---------- Post added at 10:38 PM ---------- Previous post was at 10:34 PM ----------
Moleculor said:
[snip]
Also, I downloaded the binaries for 4.0.4 from the AOSP, including radios, drivers, etc. Do I leave them in the tarballs? (Those are called tarballs, right? The TGZ files? Only used linux for two minutes in my life, not counting this phone,) Or do I extract them first? And I'm assuming some of this goes onto my phone... somehow?
Click to expand...
Click to collapse
And you don't need to download the binaries. All you need to download is the IMM76D "factory images" found here: http://code.google.com/android/nexus/images.html
efrant said:
To boot into CWM recovery (after you flash it), you can:
1) Hold both volume buttons and turn the phone on to get you into the bootloader, then scroll with the volume buttons until you see recovery and then select it with the power button; or
2) Install Quick Boot from the market. Awesome app.
Click to expand...
Click to collapse
Excellent. Thanks. So Recovery shows up as another option in the bootloader. Or something.
efrant said:
And you don't need to download the binaries. All you need to download is the IMM76D "factory images" found here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Ohh, good to know, since I downloaded both that AND the drivers. So, no drivers, just that one image. K.
Dumb question: What's 'fastboot'? I "get" adb... but what's "fastboot"?
Moleculor said:
Dumb question: What's 'fastboot'? I "get" adb... but what's "fastboot"?
Click to expand...
Click to collapse
Nexus devices have two interfaces: fastboot and ADB.
Fastboot commands (used via the fastboot.exe file) can only be used when your device is booted in the bootloader (or fastboot mode).
ADB commands (used via the adb.exe file, along with two .dll files) can only be used when your device is booted normally with USB Debugging enabled in your device's settings, or booted into CWM.
They each do different things. For example, fastboot allows you to unlock/re-lock your bootloader, flash images to partitions on your device, boot kernels on your device without flashing them, erase partitions, etc. ADB has a set of commands that let you interface with the OS. As well, it allows you to execute shell commands directly on the phone using adb shell.
Aha. Weird that there would be two separate interfaces... unless technically the bootloader and Android are two separate OSes?
Final questions I hope (since I have your attention)... this might actually be more appropriate in the exploit thread, but once I have root access, how do I clean up after myself? i.e. Delete the files I put into /data/local/tmp? Did I create the /tmp directory when I pushed those files onto the phone, or is there other stuff in there too?
EDIT:Scratch that, I just used cd, ls, and rm to remove the files, rmdir to remove the ../tmp directory... but now I note that /data/local is empty too. Can I safely delete that?
Does the ROM Manager ROM backup thing that I'm running (is this nandroid? I didn't have to boot into the bootloader to do it) back up the /data/local/tmp directory? If so, I think I might need to delete my ROM backup, delete those files, and rerun the backup.
It's running now. I'm assuming it's dumping everything into one file, or something?
And is this the nandroid backup thing, or is that something in the recovery mode?
Actually, where can I read about the directory structure and all what each directory is for? /data/media is the fake SD Card, obviously, so what's /data/local? Etc.
Moleculor said:
Aha. Weird that there would be two separate interfaces... unless technically the bootloader and Android are two separate OSes?
Click to expand...
Click to collapse
Think of the bootloader as the BIOS, nothing more. The recovery is like a mini OS.
Moleculor said:
Final questions I hope (since I have your attention)... this might actually be more appropriate in the exploit thread, but once I have root access, how do I clean up after myself? i.e. Delete the files I put into /data/local/tmp? Did I create the /tmp directory when I pushed those files onto the phone, or is there other stuff in there too?
EDIT:Scratch that, I just used cd, ls, and rm to remove the files, rmdir to remove the ../tmp directory... but now I note that /data/local is empty too. Can I safely delete that?
Click to expand...
Click to collapse
No, you did not create the /tmp directory. And there is no harm in leaving the three files there, but feel free to remove them.
Moleculor said:
Does the ROM Manager ROM backup thing that I'm running (is this nandroid? I didn't have to boot into the bootloader to do it) back up the /data/local/tmp directory? If so, I think I might need to delete my ROM backup, delete those files, and rerun the backup.
Click to expand...
Click to collapse
Yes, a backup in CWM is called a nandroid backup. The three files that you copied there don't matter. They can be deleted at any time, with or without root.
Moleculor said:
It's running now. I'm assuming it's dumping everything into one file, or something?
And is this the nandroid backup thing, or is that something in the recovery mode?
Click to expand...
Click to collapse
It's creating a backup and storing it in /clockworkmod/backup/
Moleculor said:
Actually, where can I read about the directory structure and all what each directory is for? /data/media is the fake SD Card, obviously, so what's /data/local? Etc.
Click to expand...
Click to collapse
Look in these forums. When I first started, I spent hours reading before I attempted anything.
Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
I tried a simple way which is format everything and flash another ROM but the problem remains.
TRS_80 said:
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
Click to expand...
Click to collapse
I don't know that we are in the same situation since at home I often got a good signal and this happened to me only since yesterday.
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Dan Law 001 said:
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Click to expand...
Click to collapse
Results..??
Sent from my GT-I9001 using xda premium
jabrif said:
Results..??
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I need to get the firmware first... since I already passed the download quota for today... need to wait until tomorrow...
Mmm... I heard that you mentioned clearing the EFS in your given procedure, but I do not think that I modified that folder... However, about few days ago, since I want to gain better control on the volume on my headphone remotes, I did modify the file called Generic.kl in system/usr/keylayout, but I restore it after since it didn't work. However, I don't think that this modification will trigger something in the efs folder since it has different directory. By the way, I did some research online and they say that the efs contains information about the carrier on the phone, so will there's a greater chance that the problem is caused by the possible modification on the efs than any other factor and will there also something else that possibly trigger the similar effects?
Sent from my GT-N7100 using xda premium
Still nothing
I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.
Allmystical1 said:
I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.
Click to expand...
Click to collapse
No problem, we are all new at this once, right?
First Step: Downloads!
TWRP:
http://dualhoki.vim.hu/bubor/dev/twrp-i927/twrp-2.8.4-for_odin.tar.md5
ROM:
Here is a matter of preference. If you want the latest *working* version, you can upgrade to 5.0, but you lose the camera. I presume you want the camera to work, so I suggest Bubor's CM11 for KitKat. There are other good roms too, like PAC and SediRom, but we will start with Bubor's CM11.
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip.md5sum
ODIN:
http://www.mediafire.com/download/7us5q44aab1xl9d/Odin304.zip
Second Step: Prepare.
I am presuming that you are using a Windows computer. If you are using a Linux computer, I can tell you what to do also, but these instructions are for Windows. I am also presuming that you have an external SD card in your phone, if you do not, go buy one and put it in your phone.
Unzip the Odin304.zip by right clicking on it and say unzip/extract, etc. If your Windows does not have this option, you need to download a program like winzip or 7zip so you can unzip this file. If you need those programs, they can be googled and downloaded.
Third step: Further preparation.
Turn on your phone and plug it into a usb cord and plug the usb cord into your computer. If you are using Windows, it will try to find drivers for the phone. It should be automatic and just work. If it does not, then you need the drivers, which are here:
http://www.mediafire.com/download/0up21ccc9gajwjv/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
*If you downloaded this file, just double click it like a program, it should open and install drivers for your phone. Do not do this unless your computer cannot find drivers for your phone!
Fourth step: Charge your phone.
Plug in your phone and FULLY charge it. ALL the way to 100% CHARGED. No exceptions. No shortcuts. Do it. Then UNPLUG YOUR PHONE AND TURN IT OFF.
Fifth step: Put TWRP on your phone.
a. Your phone should now be unplugged and off. Open the ODIN folder that you unzipped earlier and double click on ODIN to open the program.
b. Click on the PDA button ( you and I both know that your phone is not a PDA, this is not a typo ) and it will open a browser. Find the twrp-2.8.4-for_odin.tar.md5 file and select it. It should now fill in the blank line next to PDA with this info.
c. WHILE HOLDING THE UP VOLUME BUTTON ON YOUR PHONE, press and hold the power button. When you see "SAMSUNG" you can release the power button, but KEEP HOLDING THE UP BUTTON, untill you see a yellow triangle and warning notice. If you hold too long, that is okay as it will take you straight to the download mode with the green android that says "ODIN" at the top and "Downloading" in the middle. If you got stopped at the yellow warning/triangle, press up again to go to download mode.
d. Plug your phone into the usb, and the usb into your computer.
e. In the Odin program, press start.
You should now see a serries of verbage going by on the left, at the top a green bar may fill in, and hopefully, in the end it says "success" or "pass". Your phone should reboot all by itself. If ODIN says fail, ask for further instructions. If passed, close Odin.
Sixth step: Put your CM11 files on your phone.
Your phone should have rebooted and looks just like it did before, now powered on, and in your stock Ice Cream Sandwich firmware. As with any file transfer, plug your USB into the phone and computer. Drag the CM11 files to the phone. Anywhere will do, but if you have an external SD card in your phone, I recommend you put it there.
Seventh Step: Boot into TWRP.
a. Turn off your phone.
b. Unplug the USB.
c. HOLD THE DOWN VOLUME BUTTON and press the POWER BUTTON. When you see "Samsung" release the POWER BUTTON, but keep holding the VOLUME DOWN BUTTON. At the top of the screen, white letters should say something like "entering recovery".
d. When you see "Team Win Recovery Project" release the down volume button.
Eighth step: Make a backup!
a. Press "Backup" button on screen.
b. Check all checkboxes (system, cache, data, boot, Android Secure)
c. Press "Storage: sdcard (xxxx mb)" bar.
d. Select "External_sd" to choose to backup to your external sd card.
e. Slide the swipe bar to the right to backup. This will take a few minutes, with progress bar.
NOTE: if the screen dims, when you touch it, you will see a TWRP lock icon, swipe right to unlock it.
f. When backup is completed, it will say "reboot system", do not click that. Click the "home" icon in the lower left corner.
g. Click the "Wipe" button.
h. Swipe right to factory reset.
i. Click the "home" icon in the lower left corner.
j. Click the "install" button.
k. At the top, click on the "Storage: sdcard (xxxx mb)" bar.
l. Select "External_sd"
m. choose the cm-11-20160126-UNOFFICIAL-i927.zip
n. When that is done, click on the "reboot system" button.
The system will reboot. You should now see CM11's boot screen. The first boot takes a bit of time.
Ninth step: Thank Bubor.
a. Log into XDA.
b. Go to http://forum.xda-developers.com/captivate-glide/development/dev-cm-11-0-t2802184
c. Slap every thanks button that is for a post by Bubor untill it tells you that you cannot slap any more thanks buttons (that is only 8 thanks per day).
Tenth step: Enjoy your phone!
....I think you know how to do that.....
If you have ANY questions, please just post them here and we will see if we can answer them.
I am thanking you so very much! Also... I do apologize for such a time lapse in my reply. Life happened.
I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.
tr3sie7e said:
I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.
Click to expand...
Click to collapse
Great question, and an interesting problem!
First, I am really glad that you followed the instructions and made a backup! It is good to know that you can always go back to the way it was.
I recommend that you download another rom from the developer section here, such as Sedi-rom, omni-rom, etc., and try flashing that. If you flash one of those roms, does your IMEI stay for those roms?
Try this one: http://forum.xda-developers.com/showthread.php?t=2789727
You can do steps 7 through 10 with any of the roms in the developer thread. If this other rom works, you can use it, or download others and try them. If the SediRom does not work also, then we will need to sit down and figure this out.
I really appreciate the fact that you're here to help.
I downloaded and installed SediRom 2.1.2 and my IMEI still shows as "Unknown." However this time I should add there is a serial number, which I don't believe was present in CM11 or in the stock ROM, although I'm not sure if that's at all significant. I made an external backup of the efs file from the stock ROM, is there some way I could just reinstall CM11 and replace/overwrite the efs to give it an IMEI number? I'd really like to use CM11 if possible, I was enamored by how good it looked and how functional it was, especially since the last time I tried CM a long time ago I didn't have such a good opinion of it. Plus the bootloader is friggin sweet !
I recently got the phone unlocked off eBay, so I don't know its past history but I was able to access the network when I had the SIM card in prior to initially installing CM11 but not afterwards. I'm trying to use a T-Mobile SIM but like I said I was able to successfully access the network prior to installing CM11. But the IMEI doesn't show at all regardless if the SIM is in at all.
Is there some kind of different hardware/firmware like in a newer slightly different version of the phone that came out resulting in compatibility issues? I'm not the most experienced but I've dipped by toes in this before, so I would be willing to go the extra mile if it meant I could get CM11 to work, because honestly it looked like everything I could ever want from this phone with a good looking theme too...
Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs
xdajog said:
Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?
tr3sie7e said:
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?
Click to expand...
Click to collapse
Well restoring efs have to be done in recovery only! Do not try to do this while android is running!!
To be honest the absolute best way is having a dd partition dump of the whole partition. When you have followed the mentioned guide do you have used also dd like this?
dd if=/dev/block/mmcblk0p1 of=/storage/external_SD/efs.img
I don't know if copying the efs folder alone would work.. better is restoring the whole partition if possible. Do you have such kind of backup?
Sent from my LG-H815 using XDA Labs
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.
azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
Redownload. Maybe the file you had downloaded gets corrupted or is incomplete ..
.
Sent from my LG-H815 using XDA Labs
bubor said:
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.
Click to expand...
Click to collapse
Many thanks bubor! Renaming worked like a charm.
FYI, I tried re-downloading it, but that didn't seem to work yesterday.
I really appreciate all of your work, everything is working great.
Thanks for the quick responses.
All the best!
So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...
tr3sie7e said:
So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...
Click to expand...
Click to collapse
Check my faq here:
http://forum.xda-developers.com/showthread.php?t=2789727&p=54075993
Scroll down to restore efs.
.
Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...
tr3sie7e said:
Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...
Click to expand...
Click to collapse
Please paste the output of the results. Doing this in twrp is the correct way.