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 DO NOT TAKE CREDIT FOR THE WORK. I ONLY TRANSLATED THE SCRIPTS TO ENGLISH .
I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
I have managed to find a bat file which will allow you to root your F-02E japanese phone.
I have also found a script to allow system R/W made by kikuhare
Steps Involved:
Make sure your phone has 100% charge.
Download the Root + System Mount
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from "usb_driver_F-02E_1.0.zip". Wait for drivers to install.
Make sure the phone is connected as PTP not MTP.
CMD into the folder "f-02e_oneclick_su_installer". It is inside the "Root + System Mount_1" files folder.
Run the runme.bat.
Download "Root Checker by joeykrim" from the Play Store.
Run the "Root Checker" app
Wait for the process to finish.
UPDATE System R/W
Connect phone to computer
Download the System Read Write Mounter_1.zip <<<<<< Only need to download if you did not download the "Root + System Mount_1.zip" file.
CMD into the "F-02E_system-mounter" It is inside the "Root + System Mount_1" files folder.
Extract the file and run the"START.bat"
Run everytime the system restarts to mount system as R/W.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores. I will have to run start.bat inside F-02E_system-mounter folder everytime the phone restarts to get system R/W
Drivers: usb_driver_F-02E_1.0.zip
Root Includes System Mount: Root + System Mount_1.zip
System R/W Mounter: System Read Write Mounter_1.zip
Screenshots:
Feel free to ask questions.
anaschillin said:
Hi, I have managed to find a bat file which will allow you to root your F-02E japanese phone. I do NOT take CREDIT for the work. I have merely found the zip. I have tested it and it works. I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
Steps Involved:
Make sure your phone has 100% charge.
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from usb_driver_F-02E_1.0.zip. Wait for drivers to install.
CMD into the folder where you extracted the f-02e_oneclick_su_installer.zip files.
Run the runme.bat.
Download RootChecker from the Play Store. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Reboot the phone.
Run the RootChecker app
Wait for te process to finish.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores.
Drivers:
http://www.4shared.com/zip/kGmw0Suu/usb_driver_F-02E_10.html?
Root: http://www.4shared.com/zip/D90h9kH2/f-02e_oneclick_su_installer.html?
Feel free to ask questions.
Click to expand...
Click to collapse
I havent even got the phone yet but are there any custom roms that work on this phone? Thanks
the-blind-bandit said:
I havent even got the phone yet but are there any custom roms that work on this phone? Thanks
Click to expand...
Click to collapse
No, not enough developers and interest for the phone outside Japan. I doubt anyone will be willing to put in effort as well
Oh well, but it is a very good phone, i think ill still get it though. I just wanted to know is half of it in Chinese even if you select english, i just heard this on youtube about another one of fujitsu's phones?
Sent from my Xperia T
the-blind-bandit said:
Oh well, but it is a very good phone, i think ill still get it though. I just wanted to know is half of it in Chinese even if you select english, i just heard this on youtube about another one of fujitsu's phones?
Sent from my Xperia T
Click to expand...
Click to collapse
Only Docomo and Fujistu apps are in Japanese. Everything else is in English.
Thats fine i suppose with root explorer i can delete those apps by deleting the apk in system app? Also if you have xposed app settings you can change the language per app would that also work?
Sent from my Xperia T
the-blind-bandit said:
Thats fine i suppose with root explorer i can delete those apps by deleting the apk in system app? Also if you have xposed app settings you can change the language per app would that also work?
Sent from my Xperia T
Click to expand...
Click to collapse
I have just frozen them, just incase if the phone needs the at somepoint. Xposed framework doesnt work as it need system R/W and the root method has not allowed system R/W mainly because the phone bootloader not unlocked. Secondly make sure you do not uninstall/disable the Phonebook and Phonebook Service provided by Docomo. Its key to allowing you to add and sync contacts.
So Xposed wont work at all then, thats a shame what about lucky patcher, does that need R/W?
Sent from my Xperia T
Improved the .bat file. Now you will have system R/W
Download the root file again and run it. Follow the steps starting at 10 if you have already rooted. :good:
Thanks
Sent from my Xperia T
anyone else besides the OP got their f02 rooted with this?
I may not be able to help any further. I have boot looped my phone. I cannot get it past the NTT Docomo screen. I think I know what is causing it but I cannot get the phone connected to the PC. I may need to send it into Fujitsu.
Good luck on fixing it
Sent from my Xperia T
I tried the following OP method didnt work for me
Thank! i just got the F-02e today. will try to root it.
btw, have you overcome a heating and self-shutting off prob on this phone?
anaschillin said:
Hi, I have managed to find a bat file which will allow you to root your F-02E japanese phone. I do NOT take CREDIT for the work. I have merely found the zip. I have tested it and it works. I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
Steps Involved:
Make sure your phone has 100% charge.
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from usb_driver_F-02E_1.0.zip. Wait for drivers to install.
CMD into the folder where you extracted the f-02e_oneclick_su_installer-improved.zip files.
Run the runme.bat.
Download RootChecker from the Play Store. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Run the RootChecker app
Wait for the process to finish.
UPDATE
Download ES File Explorer. Run it.
Press Menu then scroll down the list and click Root Explore.
Change the directory to root. (Meaning where you can see all system folders)
Look for system and hold the folder, then press more then properties.
Press Change in permissions.
Tick all the boxes at the bottom.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores. I have not been able to mount system as R/W and I had trouble installing BusyBox.
Drivers: usb_driver_F-02E_1.0.zip
Root: f-02e_oneclick_su_installer-improved.zip
Screenshots:
Feel free to ask questions.
Click to expand...
Click to collapse
anaschillin said:
I may not be able to help any further. I have boot looped my phone. I cannot get it past the NTT Docomo screen. I think I know what is causing it but I cannot get the phone connected to the PC. I may need to send it into Fujitsu.
Click to expand...
Click to collapse
i hope they can fix it immedietly, only you have work for this device (i hope any other)
question:
anyone have a stock rom for this device? may show me that's link?
Click to expand...
Click to collapse
Hi I am in the same situation, uninstall many applications in Japanese that I have the phone now in its box sirbe not all, send email to the seller took days with him and a solution is supposedly looking for me if I were to fix it passeth forums or sbrire a new post with the solution that would not be other than the original rom flaseo greetings
GattacaWroclaw said:
Hi I am in the same situation, uninstall many applications in Japanese that I have the phone now in its box sirbe not all, send email to the seller took days with him and a solution is supposedly looking for me if I were to fix it passeth forums or sbrire a new post with the solution that would not be other than the original rom flaseo greetings
Click to expand...
Click to collapse
You can reset the factory settings. Reboot the phone and hold the volume up, the phone will boot into recovery mode. You will be able to do a factory recovery.
armei said:
Thank! i just got the F-02e today. will try to root it.
btw, have you overcome a heating and self-shutting off prob on this phone?
Click to expand...
Click to collapse
I have not been able to overcome the issue. It is a design issue. Because it is waterproof phone the heat cannot disperse.
The only thing I have been able to do is keep the CPU frequency down to lower the time it takes for the phone to heat up.
garynsa said:
I tried the following OP method didnt work for me
Click to expand...
Click to collapse
What does it, when you run the root file?
Could you also tell your build number. Is it VR17xxx or VR16xxx?
Hi,
I am going to unlock my Arc S BL. I read many here, but need some clarifications:
My goal is to have XUHD 5.0.1 with suggested kernel (Lupus). Right now I have XUHD 3 (with mod), phone is rooted (I did it somehow:laugh. It got slow and buggy after a while, so I need to refresh it totally.
THE PLAN:
1. Unlock BL using SE Bootloader Unlocking v1.6 by quangnhut123 (seems easier for a newbie than "sony" way, not mentioning the test point one).
2. Using the same tool flash LuPuS Kernel Stock.
Now to be confirmed: All I have to do is to enter IMEI and select file LuPuS_anzu_Stock-iCsv16-full.img. Done?
What would I get after that? Shell I turn on the phone as usual (and it is supposed to run as normal, maybe fresh)?
Should I remove my SD card while doing steps 1-2? Is the contentt of the SD card erased after the process?
Gaps - totally new to me - should I do something with them?
3. Flash the ROM. Well I did it earlies and it worked, so I believe when I will get confirmatoion of above I might succeed.
To be confirmed: to "make phone as new" - what pratition should I wipe? I am going to backup everything possible earlier.
I would like to add my own ringtone. How to do that? (I was told it can be done after installing ROM - via CWM - need suggestions...)
Do I miss something? Do I have to check anything before I start (dont want to finish with not working device...)
Any help would be VERY appreciated.
big thanks in advance.
tman_pl said:
1. Unlock BL using SE Bootloader Unlocking v1.6 by quangnhut123 (seems easier for a newbie than "sony" way, not mentioning the test point one).
Click to expand...
Click to collapse
That is the "sony" way but all the process is done with this app. You lose same features as with the "sony" way.
tman_pl said:
Now to be confirmed: All I have to do is to enter IMEI and select file LuPuS_anzu_Stock-iCsv16-full.img. Done?
Click to expand...
Click to collapse
Put phone into fastboot mode, enter IMEI, then get unlock code, then unlock BL, then select the file and flash the kernel.
tman_pl said:
What would I get after that? Shell I turn on the phone as usual (and it is supposed to run as normal, maybe fresh)?
Click to expand...
Click to collapse
You get unlocked bootloader, custom kernel installed. When you have installed the custom kernel, enter Recovery (press Volume Down button many times during kernel boot logo), wipe the necessary partitions (depends on the ROM) and install new ROM.
tman_pl said:
Should I remove my SD card while doing steps 1-2? Is the contentt of the SD card erased after the process?
Click to expand...
Click to collapse
Not necessary. No SD Data is touched during this process. Unlocking bootloader though does remove all data from your phone inside (not SD), so make backups if necessary.
tman_pl said:
Gaps - totally new to me - should I do something with them?
Click to expand...
Click to collapse
Gapps stand for Google Apps. They are only required, if you install non-stock based ROM (CyanogenMod aka CM or any other).
tman_pl said:
3. Flash the ROM. Well I did it earlies and it worked, so I believe when I will get confirmatoion of above I might succeed.
To be confirmed: to "make phone as new" - what pratition should I wipe? I am going to backup everything possible earlier.
Click to expand...
Click to collapse
For most ROMs, you need to wipe /data, /cache and /system. Non-stock based may require you to not wipe /system.
tman_pl said:
I would like to add my own ringtone. How to do that? (I was told it can be done after installing ROM - via CWM - need suggestions...)
Click to expand...
Click to collapse
If it is on your SD card, your phone can find it. Alternatively, you can put it to /system/media/audio/ringtones folder with any file explorer, that can edit system directory (I personally use ES File Explorer).
tman_pl said:
Do I miss something? Do I have to check anything before I start (dont want to finish with not working device...)[/B]
Click to expand...
Click to collapse
Seems fine for now, nothing that I can think of.
THANK YOU VERY MUCH, your help is very appreciated. All issues adressed perfectly:highfive:!
I am downloading the tools and backing up data (want to format as much as possible)..
Someguyfromhell said:
If it is on your SD card, your phone can find it. Alternatively, you can put it to /system/media/audio/ringtones folder with any file explorer, that can edit system directory (I personally use ES File Explorer).
Click to expand...
Click to collapse
The reason to put it to device memory instead of card one it that when phone is connected to PC in mass storage mode it switches the default ringtone (phone does not have acces to the card)
Well, I did try copy to devuce filesystem, but I get Read Only file system warning, no files copied. I used ES with root permission. I was told it can be done by flashing, but dont know how to do that..
BIG, BIG thanks for your help
tman_pl said:
The reason to put it to device memory instead of card one it that when phone is connected to PC in mass storage mode it switches the default ringtone (phone does not have acces to the card)
Well, I did try copy to devuce filesystem, but I get Read Only file system warning, no files copied. I used ES with root permission. I was told it can be done by flashing, but dont know how to do that..
BIG, BIG thanks for your help
Click to expand...
Click to collapse
Open ES File Explorer, press the Menu button, make sure Root Explorer is turned on, then click on Root Explorer, Mount R/W, make sure /system is set to RW.
SUPERB, thanks again. Working like a charm.
I backed up all I needed. I started SE Bootloader Unlockin Tool, but after I enter my IMEI and hit Get Unlock Code the text-area where the code should appear chnaged color to light-gray only, and nothing more.
I am running win764 if matters...
Should I proceed as told? (hit unlock BL even if Unlock code is not displayed?
I sould I get the code via http://unlockbootloader.sonymobile.com/, paste it and than proceed?
tman_pl said:
SUPERB, thanks again. Working like a charm.
I backed up all I needed. I started SE Bootloader Unlockin Tool, but after I enter my IMEI and hit Get Unlock Code the text-area where the code should appear chnaged color to light-gray only, and nothing more.
I am running win764 if matters...
Should I proceed as told? (hit unlock BL even if Unlock code is not displayed?
I sould I get the code via http://unlockbootloader.sonymobile.com/, paste it and than proceed?
Click to expand...
Click to collapse
Yes get the code from official website
Cheers,
AJ
yep, I got the code from website, But I woder wheter I should use SE BU to unlock if it doesnt get the code properly...?
Well... I will try... What I need is the flashing kernel button
All swept, but I used SEBU with the code I got from official site.
And it seems it all worked!
Just installed the rom and can see configuration screen.
BIG thanks to ALL
delete
well easy to do it