Related
Is there a little more specific brake down of the rooting process (Laymen or lame man). How to place on the root sd drive and when I tried to open zip files, i was told they were invalid. I got them from this site.
http://forum.xda-developers.com/showthread.php?t=705113
helpful links
thanks for the help but the first link doesn't work
Which link? They work fine for me.
I got as far as step 23 in the 30 step process from XNeckFaceX but I don't see a option for select the USB-MS toggle, just the 6 wipe options. Should I have loaded the new rom flash first. I can't even power down or get out of the wipe menu. I am afraid if I remove the batt I could not reboot. What to do?
ADB FOR BEGINNERS, the rest are fine
Rockmeal said:
I got as far as step 23 in the 30 step process from XNeckFaceX but I don't see a option for select the USB-MS toggle, just the 6 wipe options. Should I have loaded the new rom flash first. I can't even power down or get out of the wipe menu. I am afraid if I remove the batt I could not reboot. What to do?
Click to expand...
Click to collapse
Hopefully by now you got through everything ok. If you are using Amon_Ra recovery, USB MS is on the main menu. Press both VolUP+DWN at the same time to go up a menu.
Rockmeal said:
ADB FOR BEGINNERS, the rest are fine
Click to expand...
Click to collapse
Sorry, I didn't know you were referring to my Sig. It's fixed now.
Try Simple Root Guide
Rockmeal said:
Is there a little more specific brake down of the rooting process (Laymen or lame man). How to place on the root sd drive and when I tried to open zip files, i was told they were invalid. I got them from this site.
Click to expand...
Click to collapse
It doesn't get any easier than the Simple Root Guide. Try that one if you have trouble with any others.
All you do is download one zip file and run the EXE (making sure you have .NET framework and HTC sync installed first), click each button for each step. And done.
webs05 said:
It doesn't get any easier than the Simple Root Guide. Try that one if you have trouble with any others.
All you do is download one zip file and run the EXE (making sure you have .NET framework and HTC sync installed first), click each button for each step. And done.
Click to expand...
Click to collapse
I did this method and it looks like it's fine but I can't use wireless tether. I get a message saying my phone is in an unknown state and to reboot (which of couse I did) but the problem persists.
gapoochi said:
I did this method and it looks like it's fine but I can't use wireless tether. I get a message saying my phone is in an unknown state and to reboot (which of couse I did) but the problem persists.
Click to expand...
Click to collapse
This usually means you need to enable USB debugging, step 2 didn't work, or you need to flash a custom ROM. To test root type "su" in a terminal. You should get "#" back. If you get that try enabling USB debugging or flashing a custom ROM. If you don't get that flash a custom ROM.
What is it and why am I getting this prompt? I'm rooted with 2.3.4
Obviously I shouldn't accept this update but does anyone know what this is?
Sent from my Xoom using xda premium
Hi. I am new.
I just installed the ROM 2.3.4 last night that was posted in the xda forum(upgraded manually from 2.2 on a Unrevoked rooted Dinc).
I installed the 4.06 ROM and I am reading the official was 4.08...
Do I need another upgrade? Or is this 'the' upgrade that is for root users?
Not trying to steal your post ugxvibe. both of our questions might have similar answers.
if you update will you lose root control? What about all the apps? I'm most concerned about not being able to tether...
Just flash wildstangs 4.08.605.2 ota rom. It is the newest ota update, but already rooted.
how do I do that? Through rom manager?
Is there a way to stop the update reminder from popping up without actually installing it? I'm afraid I might mess up my phone and don't want to risk losing everything g on it.
Guys, to stop the prompt from appearing just press install and it will try to reboot but will just error and u will never see it again trust me .
Sent from my HTC Droid Incredible using xda premium
d-pabs said:
how do I do that? Through rom manager?
Is there a way to stop the update reminder from popping up without actually installing it? I'm afraid I might mess up my phone and don't want to risk losing everything g on it.
Click to expand...
Click to collapse
Yes thru rom manager.
You can dissable the notifications by editing your /system/build.prop file. Look for:
ro.config.htc.nocheckin = 0
and change the 0 to a 1. If you dont see that line add it somewhere in the file.
I went to make the nocheckin = 1 modification, but I already had it, and I'm still getting the update notifications. Not even sure how it got there. All I've done is root with Unrevoked, maybe that does the edit?
NetGoo said:
I went to make the nocheckin = 1 modification, but I already had it, and I'm still getting the update notifications. Not even sure how it got there. All I've done is root with Unrevoked, maybe that does the edit?
Click to expand...
Click to collapse
It should have worked, you may need to clear the cache partition. Or there is another method go to /etc/security and rename otacerts.zip to otacerts.zip.bak
Like what was said above...
If you have Clockwork or some other custom recovery, if you just allow it to update when prompted, it will not install and will cause no other problems. You must have the stock recovery in order for the update to install.
It CANNOT install if you don't have the stock recovery.
But, I would also go into the /cache directory and find the update file and zap it (It will be obvious). I just use ADB and "rm" it from my PC. You could use root explorer or something. Otherwise you will have a big update file just sitting there and hogging space.
cmlusco said:
It should have worked, you may need to clear the cache partition. Or there is another method go to /etc/security and rename otacerts.zip to otacerts.zip.bak
Click to expand...
Click to collapse
I found the file thru root explorer but cannot change it due to message that says it's read only. other options?
Thanks.
bgtruitt said:
I found the file thru root explorer but cannot change it due to message that says it's read only. other options?
Thanks.
Click to expand...
Click to collapse
At the top of the screen in Root Explorer, change r/o to r/w. Then make your change.
Sent from my ADR6300 using xda premium
im rooted n using the clockworld mod for roms, I attempted to run the 4.08 update from User wildstang following the instructions but after installing the update n rebooting it just sits at "Dorid incredible" white screen and never boots. I may be doing something wrong here, can someone break it down for me? suggestions?
NOTE: I use CWMR 5X. Some wipe options below are not included in earlier recovery versions. Still wipe what is available the best you can.
1. Put the Rom on the root of your SD Card
2. Compare MD5 Sum
Windows: MD5 Calculator
LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
Mac: Open a terminal and type: md5 [path to the rom on your sd card]
3. Reboot to Recovery
4. Wipe these:
Main Screen:
wipe data/factory reset - x2
wipe cache partition - x2
Advanced:
Wipe Dalvik Cache - x3
Wipe Battery Stats - optional
Mounts and Storage:
Format-
/boot - x2
/system - x2
/datadata - x2
/data - x2
/cache - x2
5. Install Rom from SD Card by going back and selecting install from SD card.
6. Reboot and enjoy!
followed each step to the letter but still wont boot : /
Ok i changed nothing in the method of installing the rom and for whatever reason it worked!! 4.08 now phone is 10X faster and im loving it. Only issue i see now is i cannot get back into clockworld mod! why is that? i hold down power and vol down for a long time and when release it just starts the boot sequence any suggestions?
clutchdroid said:
Ok i changed nothing in the method of installing the rom and for whatever reason it worked!! 4.08 now phone is 10X faster and im loving it. Only issue i see now is i cannot get back into clockworld mod! why is that? i hold down power and vol down for a long time and when release it just starts the boot sequence any suggestions?
Click to expand...
Click to collapse
Uncheck fastboot in menu > applications.
Thank you sir.
clutchdroid said:
Ok i changed nothing in the method of installing the rom and for whatever reason it worked!! 4.08 now phone is 10X faster and im loving it. Only issue i see now is i cannot get back into clockworld mod! why is that? i hold down power and vol down for a long time and when release it just starts the boot sequence any suggestions?
Click to expand...
Click to collapse
I had the same problem, but after two times running the install its still getting the hang. Hopefully I'll get better luck on try #3.
Did you figure out what caused the temporary issue?
spitzaf said:
I had the same problem, but after two times running the install its still getting the hang. Hopefully I'll get better luck on try #3.
Did you figure out what caused the temporary issue?
Click to expand...
Click to collapse
I may have missed a format inside mounts and storage make sure you hit them all.
cmlusco said:
Yes thru rom manager.
You can dissable the notifications by editing your /system/build.prop file. Look for:
ro.config.htc.nocheckin = 0
and change the 0 to a 1. If you dont see that line add it somewhere in the file.
Click to expand...
Click to collapse
OK I've found the file you're talking about and it doesn't have that line in it so I need to add it. I can't easily get access to a computer right now to run the command line on my phone so i have been trying to use the terminal emulator instead. It says I doesn't have a text editor...is there a way to edit via the emulator? Do you wkno which commands to use?
Thanks again
Yep, still having a minor issue with this. I have added the line suggested and I have cleared my cache yet I still get periodic prompts to install the update. I'm not really keen on doing so. Can anyone else suggest a way to stop the (weekly) prompts?
Thanks
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.
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.
Sometimes Password lags or something and you will not be able to use your phone, here's a ROOT-ONLY method.
Are you a veteran? Here's a short guide. (in "/data/system" delete locksettings.db, locksettings.db.shm, locksettings.db.wal)
Not a veteran? (Don't know a lot about phone stuff)
Read this guide.
Code:
Alert, do NOT delete any file from system to "free up space", this will kill your device. I'm not responsible if you do something -outside this guide- that might damage your phone, read carefully and good luck!
REQUIREMENTS:
-You will need a recovery that can delete files (has a 'file manager' feature), Recommend: TWRP Recovery
GUIDE:
Step 1: Reboot to recovery mode,
This can be done -on the galaxy a10- by turning your phone off and long-clicking volume up button THEN power button (at the same time), but it might ask for password while turning it off, so we need to reboot it manually.
While the phone is on... long click power and volume down for 7.5 seconds, it will turn off. Immediately when it turns off you need to keep clicking power but click volume up instead of down, when the phone boots it will get in the recovery mode, for sure.
Step 2: Locate the password file
The password file is the file your phone stores your pin/pattern/password at. it is called 'locksettings.db'
We need to delete it -and all it's "variants"- from your device.
In twrp... choose 'ADVANCED'.
choose 'FILE MANAGER' after that.
it will show you the files on your phone. If you look at the top file (the highest one) it will be called (up a level), click it again and again until it disappears. If you don't see that file that means you are at the deepest folder (ROOT).
choose "data" folder
choose "system" folder
Scroll down until you find "locksettings.db" tap it and click DELETE.
Do the same for "locksettings.db.shm" and "locksettings.db.wal" (delete them too)
Step 3: Rebooting into the os
To turn your phone on again click the back button and return to the home screen.
Click "REBOOT"
Click "SYSTEM"
That's all now the password is removed.
Tested on Samsung Galaxy A10
Need more help? Contact me on my telegram, https://t.me/BrudherBoard
"-You will need a recovery that can delete file"
You can't install a custom recovery without Usb Debugging and OEM unlocking.
What's the point of the tutorial ?
gsmer87 said:
"-You will need a recovery that can delete file"
You can't install a custom recovery without Usb Debugging and OEM unlocking.
What's the point of the tutorial ?
Click to expand...
Click to collapse
well you can see [ROOT] at the end of the title, so
rooting your phone means unlocking bl, so [ROOT] means your bootloader is unlocked and you have a custom recovery that can install zips such as magisk so you can grant root access to apps.
now tell me what's the point of your message?
BrotherBoard said:
well you can see [ROOT] at the end of the title, so
rooting your phone means unlocking bl, so [ROOT] means your bootloader is unlocked and you have a custom recovery that can install zips such as magisk so you can grant root access to apps.
now tell me what's the point of your message?
Click to expand...
Click to collapse
The point of my message is that your tutorial is useless. You can't root your phone without data loss and putting the [ROOT] in your [GUIDE] doesn't make it less useless.
PLEASE prove me wrong ! I wold realy like to be wrong about this .
Total useless nowadays
Now all device's have FRP & KG enable
And with this you can't flash any custom image
gsmer87 said:
The point of my message is that your tutorial is useless.
Click to expand...
Click to collapse
Mr Hassan said:
Total useless nowadays
Click to expand...
Click to collapse
I have to disagree a bit with these statements. It's not entirely useless but the demographic this targets is very limited.
For this tutorial to work you have to
1) Have your phone rooted with a custom recovery
2) Have your data unencrypted by going out of your way to keep it unencrypted
Not everyone meets these 2 criteria but for those who do, this is somewhat helpful so that you know which files exactly are responsible for your lock method in lockscreen.
I'd probably add those 2 as perquisites so that you don't get bombarded with noobs asking why they can't access their data partition even if they have a custom recovery.
ShaDisNX255 said:
I have to disagree a bit with these statements. It's not entirely useless but the demographic this targets is very limited.
For this tutorial to work you have to
1) Have your phone rooted with a custom recovery
2) Have your data unencrypted by going out of your way to keep it unencrypted
Not everyone meets these 2 criteria but for those who do, this is somewhat helpful so that you know which files exactly are responsible for your lock method in lockscreen.
I'd probably add those 2 as perquisites so that you don't get bombarded with noobs asking why they can't access their data partition even if they have a custom recovery.
Click to expand...
Click to collapse
i've literally put a [ROOT] at the title
gsmer87 said:
The point of my message is that your tutorial is useless. You can't root your phone without data loss and putting the [ROOT] in your [GUIDE] doesn't make it less useless.
PLEASE prove me wrong ! I wold realy like to be wrong about this .
Click to expand...
Click to collapse
in new phones that are not rooted, there is no way to remove lock screen without data loss, sir imagine locking your house up with the key inside, how would you get in?
BrotherBoard said:
in new phones that are not rooted, there is no way to remove lock screen without data loss, sir imagine locking your house up with the key inside, how would you get in?
Click to expand...
Click to collapse
There are so many ways to get into a house without a key; you can't even imagine.
Wait.. Is the house rooted? :]
Timmmmaaahh! said:
There are so many ways to get into a house without a key; you can't even imagine.
Wait.. Is the house rooted? :]
Click to expand...
Click to collapse
maybe but I'm talking about not being able to use your phone, not breaking in a house :]
BrotherBoard said:
maybe but I'm talking about not being able to use your phone, not breaking in a house :]
Click to expand...
Click to collapse
Hey, you started the house analogy. And it was over 2 months ago, you're too late for a retort
Timmmmaaahh! said:
Hey, you started the house analogy. And it was over 2 months ago, you're too late for a retort
Click to expand...
Click to collapse
ok bro no hate, you have replied to a thread that I was just bored and like why not to write that up on xda and I have put a [ROOT] in the title, I see I have made no mistakes at this.
BrotherBoard said:
Sometimes Password lags or something and you will not be able to use your phone, here's a ROOT-ONLY method.
Are you a veteran? Here's a short guide. (in "/data/system" delete locksettings.db, locksettings.db.shm, locksettings.db.wal)
Not a veteran? (Don't know a lot about phone stuff)
Read this guide.
Code:
Alert, do NOT delete any file from system to "free up space", this will kill your device. I'm not responsible if you do something -outside this guide- that might damage your phone, read carefully and good luck!
REQUIREMENTS:
-You will need a recovery that can delete files (has a 'file manager' feature), Recommend: TWRP Recovery
GUIDE:
Step 1: Reboot to recovery mode,
This can be done -on the galaxy a10- by turning your phone off and long-clicking volume up button THEN power button (at the same time), but it might ask for password while turning it off, so we need to reboot it manually.
While the phone is on... long click power and volume down for 7.5 seconds, it will turn off. Immediately when it turns off you need to keep clicking power but click volume up instead of down, when the phone boots it will get in the recovery mode, for sure.
Step 2: Locate the password file
The password file is the file your phone stores your pin/pattern/password at. it is called 'locksettings.db'
We need to delete it -and all it's "variants"- from your device.
In twrp... choose 'ADVANCED'.
choose 'FILE MANAGER' after that.
it will show you the files on your phone. If you look at the top file (the highest one) it will be called (up a level), click it again and again until it disappears. If you don't see that file that means you are at the deepest folder (ROOT).
choose "data" folder
choose "system" folder
Scroll down until you find "locksettings.db" tap it and click DELETE.
Do the same for "locksettings.db.shm" and "locksettings.db.wal" (delete them too)
Step 3: Rebooting into the os
To turn your phone on again click the back button and return to the home screen.
Click "REBOOT"
Click "SYSTEM"
That's all now the password is removed.
Tested on Samsung Galaxy A10
Need more help? Contact me on my telegram, https://t.me/BrudherBoard
Click to expand...
Click to collapse
Was useful for me bro
SsamsungA10 said:
Was useful for me bro
Click to expand...
Click to collapse
are you Samsung A10 from telegram
...was also helpful for me. Thank you!