Flashing a Recovery,Kernel and Rom[FAQ'S][NOOB FRIENDLY] - HTC One V

Easiest guide to flash a custom ROM and custom kernel
Lets accept it,we all have been here,confused what should do after i root/boot unlock
we think i know enough so lets get this going but then, we get stuck in the splash/welcome screen and we think **** this was such a bad idea
SO i created this thread for anyone who ever is confused,lost,seeking help.
IF YOU FIND THIS THREAD HELPFUL, BE SURE TO RECOMMEND IT TO OTHERS AND PRESS THE THANKS BUTTON :d
Thread Contents
1.Common terms/Android Slangs
2.Basic Requirements
3.Download links for Recovery Images for PRIMO U/ PRIMO C]
4.How To flash recovery
5.FAST BOOT FILES(download links) : HTC ONE V DRIVER (DOWLOAD LINKS)
6.How To Back Up Your Current Rom
7.Installing Your ROM
8.Choose Your Kernel(download links)
9.Flashing The Kernel[windows]
*Flashing The Kernel[MAC]
10.people who have already flashed a ROM and are confused how to upgrade it
11.Upgrading KERNEL
12.Stuck in Bootloops, Cant Pass the HTC welcome Screen
13.Some tips from me
Click to expand...
Click to collapse
Hope u have successfully rooted and boot unlocked
Common Terms/Android Slangs
a small guide on some of the android terms my Diablo67
Bootloader:This small program's only job is to load other data and programs which are then executed from RAM.Often, multiple-stage boot loaders are used, during which several programs of increasing complexity load one after the other in a process of chain loading.
Fastboot:A diagnostic protocol used primarily to modify the flash filesystem in Android smartphones from another computer over a USB connection. It is part of the Android Debug Bridge library.
Utilizing the Fastboot protocol requires that the device be started in a boot loader or Second Program Loader mode in which only the most basic hardware initialization is performed. After enabling the protocol on the device itself it will accept any command sent to it over USB via a command line. Some of most commonly used fastboot commands include:
•flash - Overwrites a partition in flash with a binary image stored on the host computer.
•erase - Erases a partition in flash.
•reboot - Reboots the device into the either the main operating system or the system recovery partition.
•devices - Displays a list of all devices (with Serial #) connected to the host computer.
Flashing:The ROM memory used in smartphones and tablets etc. is often same as flash memory found in SD cards and USB flash drives, simply optimized for better speed and performance while running the operating system.
Kernel:A kernel is a layer of code that allows the OS and applications to interface with your phone's hardware. The degree in which you can access your phone's hardware features depends on the quality of code in the kernel. The homebrew (rooting) community for HTC has made several kernel code improvements that give us additional features from our hardware that the stock kernel does not. When you flash a custom ROM, you automatically get a kernel. But you can also flash a standalone kernel ROM on top of the existing one, effectively overwriting it. These days, the difference in custom kernels is less about new features and more about alternate configurations. Choosing a custom kernel is basically choosing one that works best with your ROM.
Nandroid:To backup the current running rom.
Recovery Mode:A small separate operating mode you can boot your device into, used for device administration. Two popular custom recovery modes are Amon Ra and Clockwork.
Basic Requirements
1.A Boot-unlocked and Rooted HTC One V
2.Charge it till above 75% battery
2.A PC(this guide is for now only for windows)
3.usb cable
4.HTC driver download here or HTC SYNC
5.FastBoot Files[ click here>>> download them and put in a folder in c drive ]
> example c:\fastboot or c:\android
6.A recovery image(for image scroll down)
7.A Rom(thats ur choice)
8.boot image(scroll down)
9.put the rom(.zip file) in sd card
Here Are The Recovery Images
Recovery Images[PRIMO U/GSM]
1. CWM 6 by Lloir
2. TWRP 2.6.0 <<Ill Recommend [very user friendly]
3. CWM v5 Touch Recovery
Recovery Images[PRIMO C/CDMA
1. [VM/PRIMOC][RECOVERY] CWM Recovery
2. [VM/PRIMOC][RECOVERY] TWRP2 Recovery
3. [RECOVERY] [PRIMOC/CDMA] CWM 6.0.1.5
How To flash recovery
HOPE U HAVE THE FAST BOOT FILES
[IF NOT]
click here download them and put in a folder in c drive
example c:\fastboot)
>>Now enter Fast boot(power button +volume DOWN(for 15 + sec))<<<
u might have arrived at Hboot boot mode>>> now move up down by pressing the volume buttons and select fastbootwith the power button
Flash it via cmd(command prompt)
Enter these commands
Code:
[B][COLOR="Red"]fastboot flash recovery recovery.img
[/COLOR][/B]
How To Back Up Your Current Rom
(must for first time flashers)(nand=backup of current ROM)
1. Once the CWM/TWRP recovery installed:
Now enter Fast boot(power button +volume DOWN(for 15 + sec))
now move up down by pressing the volume buttons and select fastbootwith the power button
2. Once you are in the RECOVERY menu:
click backup and restore
click backup
the backup process is running. It will be a max 20 minutes to complete.
(optional step just to be sure)
3. once complete, check whether the backup is successful
click backup and restore
click restore
you will see your backup files, for example 2012-11-27 11-7
it should complete with in a span of time
4.Now if that is over go back to the previous menu
use the back button
click reboot system now to boot your device
Installing Your ROM
5.just do a factory reset and wipe cache, then click on install from sd card
6.flash it(the ROM in ur sd card shud be in a .zip format)
7.NOW.DON'T REBOOT UR PHONE GO TO FAST BOOT MODE (VOLUME DOWN+ POWER BUTTON)(or there will be a option to reboot into bootloader)
Choose Your Kernel
9.download whichever kernel u want
[CDMA/PRIMO C]
SuperSick kernel Click ME
SICK kernel PRIMO C/CDMA click here
[GSM/PRIMO U]
SuperSick kernel Click ME
SICK kernel CLICK here
TITANIUM KISS kernel SENSE users CLICK here
HELLBOY kernel FOR AOSP based ROMS(cm9/cm10/AOKP/PA)USE THE LATEST ONE FOR 4.2.2 >click<
Flashing The Kernel[windows]
8.HOPE U HAVE THE FAST BOOT FILES (if not click here download them and put in a folder in c drive)
rename it boot.img and put it in the folder as the fastboot files
GO TO FAST BOOT MODE (VOLUME DOWN+ POWER BUTTON)(or there will be a option to reboot in recovery)
10.flash it via CMD
Enter these commands
Code:
11.[B][COLOR="Red"]Fastboot flash boot boot.img [/COLOR][/B]
12.[B][COLOR="Red"]fastboot reboot[/COLOR][/B]
Flashing The Kernel[MAC] by kalaker
kalaker said:
Go developer.android.com and download the SDK & move it to your home directory ("~" or /Users/<username>)
Go to <sdk-location>/tools and launch "Android"
Download the platform tools
Open terminal
Open Finder to <sdk-location>/platform-tools
In terminal, type "sudo cp"; drag adb from the Finder window into the Terminal window; type "/usr/bin/"; hit enter
Enter your password
Repeat the above three steps, but drag "fastboot" instead of "adb"
Close terminal
Open terminal (it sounds weird, but just do it)
Now, and forever, do this to install a kernel:
Download kernel
Connect phone to computer
Make sure USB Debugging is enabled (Settings>Development>USB Debugging)
In terminal, type "adb reboot bootloader"
In terminal, type "fastboot flash boot"; drag in the kernel from finder; hit enter
Examples:
Code:
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
adb reboot recovery
fastboot flash boot /Users/Username/Downloads/boot.img
Click to expand...
Click to collapse
13.enjoy
First boot takes some time have patience......be sure to ask questions or doubts
Ok For people who have already flashed a ROM and are confused how to upgrade it
Upgrading ROM
1.download your needed ROM
2.put in SD card
3.boot into recovery
4.no need to wipe everything,wipe caches(and if the dev says to full wipe do it)
5. (Unless u come from a different ROM eg.From Amazing Sense To CM10, in this case a factory reset i needed
6.flash the ROM
7.reboot
8.flash GAPPS
9. enjoy
Upgrading KERNEL
1.boot in bootloader
2.do the required steps(as mentioned above)
3.wipe caches
5.enjoy
Stuck in Bootloops, Cant Pass the HTC welcome Screen
ok, calm down, everyone has this problem while flashing, i get it so many times, they can cause by the following reasons
bad flash
wrong rom
you forgot to flash the kernel
wrong kernel
messed up the order in flashing
ok,
1.Bad flash-this occurs if the .zip file is corrupted
solution:= re flash the ROM, if still no, download the file again and try
2.wrong ROM- u may have downloaded a ROM that is not for ur device or a ROM which is of not ur description
for example u might me a PRIMO C device/CDMA and u downloaded a PRIMO U/GSM ROM
3.Wrong Kernel-Kernel is the link between ur software and hardware, if u flash the wrong one like the case mentioned above , download the correct one and re flash
4.[ FLASHING YOUR KERNEL SHOULD BE THE LAST STEP][UNLESS U HAVE A S-OFF DEVICE]
Ok Some Tips Which May Help You
1.Battery Draining fast?
-----get an app called BetterBatteryStats,run it over night.then next morning open it and check whats waking your device
Click to expand...
Click to collapse
2.Can i use scripts?
-----Your wish, the rom works perfect,running a script can ruin it in some cases(chill,even i run some)
Click to expand...
Click to collapse
3.Good/best/recommended ROMS?
-----all roms are good in their own way, but i can give u a list of recently updated roms
-----1.sphongle(4.2.2) 2.Slimbean 3.Cm10
Click to expand...
Click to collapse
will add more cheers
Hope this helps u

another get thanks quick scheme thread?
Sent from my One V

paarthdesai said:
another get thanks quick scheme thread?
Sent from my One V
Click to expand...
Click to collapse
LOL :silly:

no i plan to help!

My works
You call that work ??
Those are just tips

Y do u have a problem with that
Sent from my One V

No but that work word is pissing me off ..... For using it in a inappropriate place

donhashem.dh said:
No but that work word is pissing me off ..... For using it in a inappropriate place
Click to expand...
Click to collapse
Don't read it
Sent from my One V

to clarify, step 6: "flash" should be edited to say " install ROM from zip" to avoid the "flash" misconception associate with flashing kernels:good:

more detailed work should be there.. like you said install cwm or twrp.... give a link to where they are embedded in the words will be good...
and the above goes for the flashing rom part also...embed the link to the dev section
make it easy and tidy instead of all those ugly looking clutters you did
Sent from my One V

will work into that!

did it!

cybervibin said:
flash it via cmd
Enter these commands
Fastboot flash recovery recovery.img
Click to expand...
Click to collapse
You forgot to mention to boot into fastboot. No offence, but it has to be much better written. Its not noob friendly at all.

m sorry abt that! guess missed it! wrote the thread throygh my phone!
any other problems i corrected the one u said!

cybervibin said:
m sorry abt that! guess missed it! wrote the thread throygh my phone!
any other problems i corrected the one u said!
Click to expand...
Click to collapse
Yeah, you could try creatign sub sections, like thinigs to have before swap, then steps after that. Eg in step 1 you say
>>Now enter Fast boot(power button +volume DOWN(for 15 + sec))<<<
and
1.Flash CWM 6 by lloir
or TWRP 2.3.1.0 ill recommend TWRP
>>PRIMO C /CDMA click here<<
To flash recovery HOPE U HAVE THE FAST BOOT FILES(IF NOT click here download them and put in a folder in c drive
example c:\fastboot
Click to expand...
Click to collapse
First you mention the ROM, then out of the blue you mention recovery. ROM should be introduced after a nand backup. You should also explain in short what a nand backup is. A sentence with an analogy is sufficient. I am a software developer and I would like to share a rule that I follow: If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Dont get me wrong, I am not trying to insult or berate or anything, but I got it read by a friend who wants to flash his One V, and he got back to me with more questions than the guide answered. There a some step holes in the guide, and you have to write is as if you are a noob
Lastly, thanks a lot, this particular guide and your answers have been really helpful to me and the community.
Cheers!

now ill consider that! hard being a noob!

thetuxracer said:
If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Click to expand...
Click to collapse
Nice, I liked this!
Sent from my One V using xda app-developers app

soham_sss said:
Nice, I liked this!
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
thetuxracer said:
Yeah, you could try creatign sub sections, like thinigs to have before swap, then steps after that. Eg in step 1 you say
First you mention the ROM, then out of the blue you mention recovery. ROM should be introduced after a nand backup. You should also explain in short what a nand backup is. A sentence with an analogy is sufficient. I am a software developer and I would like to share a rule that I follow: If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Dont get me wrong, I am not trying to insult or berate or anything, but I got it read by a friend who wants to flash his One V, and he got back to me with more questions than the guide answered. There a some step holes in the guide, and you have to write is as if you are a noob
Lastly, thanks a lot, this particular guide and your answers have been really helpful to me and the community.
Cheers!
Click to expand...
Click to collapse
how about now, noob friendly enough?

Yup, pretty cool! If there was a way to thank again..

ty!! please keep the recomendations coming!

Related

Idiot's guide to flashing the Xoom (for fun and profit)

This guide is for you that have a new Xoom (WiFi only, US model) with Android 3.1 and want to
- get root access
- enable the external SD card unit
Please note that Android 3.2, which now is available for the US Wifi models, make this guide more or less obsolete. If your aim is to have root access, then there are probably simpler methods.
What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and dont try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned!
I strongly recommend you to read the entire guide before trying this. In fact, read it twice to ensure that you have understood everything. If there is wierd stuff that you dont understand, dont hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but noone (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
If someone else adapts this guide for the EU model or the 3G model, feel free to drop me an IM and I will update the guide for these devices too. Until then, this has only been tested on a WiFi only, 32 GB device bought in the US. If you brick your 3G or EU bought model, dont call me ...
0. Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity)
2. Install Java SDK and Android SDK tools (for adb and fastboot commands)
3. Unlock the device for flashing (allowing replacement of recovery and boot images)
4. Install a modified recovery image (ClockWorkMod recovery for Android)
5. Root the device (Allow r/w access to the device filesystem)
6. Flash a kernel that supports the SD card (SD card access, overclocking etc.)​
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows XP x86 SP3. Windows 7, Mac and Linux users will probably have to do some steps differently.
Update July 7: I have tested the procedure on Windows 7 x86 now and the procedure is identical to Windows XP.
1. Install the latest Motorola USB drivers
The installation file can be found here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2. Installation of development software
Java SDK 6 and Android SDK (for Honeycomb at least) need to be installed. You can find the installation kits here.
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
http://developer.android.com/sdk/index.html
2.1 Install them as any other software.
2.2 What I had to do was to manually modify the PATH environment variable. I use Windows XP so I did that by right clicking on My Computer, choose Properties and select Advanced. Here I added the path to platform-tools and Tools
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\QuickTime\QTSystem\;D:\Java\Android-sdk\platform-tools;D:\Java\Android-sdk\tools
Note: If the Android SDK complains that the Java Dev Kit cant be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
2.3 Test that ADB and FASTBOOT works. You should open a command window and go to your Android installation directory. Plug in your Xoom to your computer and write 'adb devices'. Your Xoom should now be listed like this
C:\Documents and Settings\Anders>adb devices
List of devices attached
0288414343813157 device​
Did your device not show up? Make sure that you have USB debugging enabled in Settings / Applications / Development
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to rescure important data before you start.
3.1 Power up and start the Xoom
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'My Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal, but now ready for step 4
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
4.1 Boot into flash mode with 'adb reboot bootloader'
4.2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img​
4.3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.4 Enter CWM with the following procedure
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. There are ways to prevent this (see posts below), but I recommend you to redo step 4 instead of messing with removal of system files. But both methods would probably work. Experiment!
5. Rooting the Xoom
The root zip file is located here
5.1 You need to transfer the ROOT zip file to a working micro SD card. You can do this on a computer or cell phone, but the ROOT zip must be located in the root directory of the SD card.
5.2 Insert the now prepared SD card in the Xoom
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option
5.4 Select 'Install ZIP from sd card'
5.5 Select 'Choose ZIP'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install the ROM Manager app and start it. If the rooting was successful, then ROM Manager should start without any complaints.
6. Flashing a new kernel that supports SD cards (and maybe more ...)
The kernel that I used is described here http://forum.xda-developers.com/showthread.php?t=978013
The kernel zip file is located here
6.1 This step is identical to 5, but swap the ROOT zip towards the KERNEL zip. For simplicity, you may want to prepare the SD card with both zip files at the same time in step 5.1 ...
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
okantomi said:
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Click to expand...
Click to collapse
Of course, done
juDGEY2k10 said:
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
Click to expand...
Click to collapse
This is only tested on a US device. OP updated.
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
When you unlock your Xoom, it will wipe all user data.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
You're right. I rooted 1st and flashed CWR later. I then used brd's method to update to 3.1, re-root and flash the new bootloader and kernel. So there is a step missing after Step 3. I'm sorry, I don't remember exactly how to do this from HC 3.1. (meaning what files to use) as I was on HC 3.0 at the time.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
Yes it will. Read 3.4 again, it will do factory reset.
The root file may vary from case to case, but the procedure is the same AFAIK. I used the one that "charge light off"... There are probably others too.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
This is true, and I will update the OP to reflect that.
So has anyone followed this guide successfully yet? I don't really want to be the first...
yordikins said:
So has anyone followed this guide successfully yet? I don't really want to be the first...
Click to expand...
Click to collapse
Hi
I did!. And you know that someone gotta be first (actually second). Why not take the credit?
pingvinen said:
This is true, and I will update the OP to reflect that.
Click to expand...
Click to collapse
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Abracastabya said:
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
cam30era said:
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
Click to expand...
Click to collapse
Sounds good and thanks B-)
Sent from my Xoom using XDA Premium App
Tnx . Very help full .
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
rmcsc said:
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
Click to expand...
Click to collapse
Try again, and remember that timing (3 seconds) are key to success ...
I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.
I'll update in a few. Thanks!
Sent from my T-Mobile G2 using Tapatalk

[Q] Wanna up 4.0.4 for my nexus

i am a green hand in here and also abt all rooting,
just wanna up my nexus to 4.0.4 as i read that it optimized the nexus in a best way,
however know little abt that,
just find the latest post from Mike http://forum.xda-developers.com/showthread.php?t=1392310
i have some Qs b4 moving on-;
1. is it okay if i only follow Mike's youtube for upto 4.0.4?
2. rooting means no more maintenance from samsung?
3. the kernel provided by Mike can run at 1.35Ghz?
Hope i can reach some replies from you guys, many thx
bk
I never use anything but stock kernels (its the best for me) so i cant tell you about overclocking..you really dont need to on this beast of a phone....
NOTE: if you ever root your phone and it gets dropped or something just flash the stock files and you can send it into service and it will be fine.
Here is a simple tutorial. (you can find more detail by googleing it)
1. (sorry i forgot) set up ADB - google it...its long
1. Unlock bootloader (this will wipe everything) - "fastboot oem unlock"
2. put the 4.0.4 update.zip on the sd card.
3. flash cwm recovery (using the toolkit or fastboot - "fastboot flash recovery PUT_NAME_HERE.img when you are in fastboot (all keys together till vibrates)
4. reboot into recovery (after flashing it it will stay at the menu...use volume keys to get "recovery mode" to show up at the top then power to select it.
5. flash the zip.
6. reboot (you will lose cwm recovery)
7. lock the bootloader - "fastboot oem lock" in fastboot
8. your done..stock 4.0.4..not rooted...still get support.
ezcats said:
I never use anything but stock kernels (its the best for me) so i cant tell you about overclocking..you really dont need to on this beast of a phone....
NOTE: if you ever root your phone and it gets dropped or something just flash the stock files and you can send it into service and it will be fine.
Here is a simple tutorial. (you can find more detail by googleing it)
1. (sorry i forgot) set up ADB - google it...its long
1. Unlock bootloader (this will wipe everything) - "fastboot oem unlock"
2. put the 4.0.4 update.zip on the sd card.
3. flash cwm recovery (using the toolkit or fastboot - "fastboot flash recovery PUT_NAME_HERE.img when you are in fastboot (all keys together till vibrates)
4. reboot into recovery (after flashing it it will stay at the menu...use volume keys to get "recovery mode" to show up at the top then power to select it.
5. flash the zip.
6. reboot (you will lose cwm recovery)
7. lock the bootloader - "fastboot oem lock" in fastboot
8. your done..stock 4.0.4..not rooted...still get support.
Click to expand...
Click to collapse
many thx for ur reply.
But i still have some Qs abt that
1. root = wipe? i always confuse abt these 2 terms
2. set up ADB? adb is a prog/file?
3. fastboot oem unlock is a prog again?
4. haha nexus is the best? but... from the score prog nexus is not the best lol
billkkc said:
many thx for ur reply.
But i still have some Qs abt that
1. root = wipe? i always confuse abt these 2 terms
2. set up ADB? adb is a prog/file?
3. fastboot oem unlock is a prog again?
4. haha nexus is the best? but... from the score prog nexus is not the best lol
Click to expand...
Click to collapse
1- no. root = administrator/superuser acess in nix-based systems, like it was supposed to be, in our point of view. there are several kinds of wipe (cache, dalvik, userdata).
2- http://source.android.com/source/building-devices.html - check "Building fastboot and adb"
3- http://source.android.com/source/building-devices.html - check "Booting into fastboot mode" and "Unlocking the bootloader"
4- benchmarks aren't everything..
bk201doesntexist said:
1- no. root = administrator/superuser acess in nix-based systems, like it was supposed to be, in our point of view. there are several kinds of wipe (cache, dalvik, userdata).
2- - check "Building fastboot and adb"
3- - check "Booting into fastboot mode" and "Unlocking the bootloader"
4- benchmarks aren't everything..
Click to expand...
Click to collapse
thx for ur reply
i really need to do more search on net b4 moving into next steps
seems the up to 4.0.4 is a complex procedure
btw i c some posts talking abt baseband and kernel, is it 2 diff stuff?
i am puzzling with those terms
billkkc said:
thx for ur reply
i really need to do more search on net b4 moving into next steps
seems the up to 4.0.4 is a complex procedure
btw i c some posts talking abt baseband and kernel, is it 2 diff stuff?
i am puzzling with those terms
Click to expand...
Click to collapse
its not complex at all (even for you)
you don't need baseband and kernel (yes they are different) but you don't need to worry about that (when you flash the file it will do that for you)
just follow the instructions here: (or my post) and you should be fine...(credit to kangxi)
Change to update.zip and flash through stock recovery or CWM *STOCK CDMA NEXUS ONLY*
*02/05 update*
For those having issues, try flashing it with CWM using the toolkit in the dev section.
http://www.mediafire.com/?l1wxw3exb9195w7
Root not required but bootloader must be unlocked
1. Download the toolkit
2. Put your phone into fastboot mode
3. Open the toolkit
4. Choose the option to "Boot into Clockwork Mod without permanently flashing it"
5. Once in CWM, choose install from SD card
6. Choose install "update.zip" if you renamed it to that. Otherwise, choose the option to choose the file.
7. Viola!
JUST TO BE CLEAR YOU NEED THE VERIZON VERSION!!!!
ezcats said:
its not complex at all (even for you)
you don't need baseband and kernel (yes they are different) but you don't need to worry about that (when you flash the file it will do that for you)
just follow the instructions here: (or my post) and you should be fine...(credit to kangxi)
Change to update.zip and flash through stock recovery or CWM *STOCK CDMA NEXUS ONLY*
*02/05 update*
For those having issues, try flashing it with CWM using the toolkit in the dev section.
Root not required but bootloader must be unlocked
1. Download the toolkit
2. Put your phone into fastboot mode
3. Open the toolkit
4. Choose the option to "Boot into Clockwork Mod without permanently flashing it"
5. Once in CWM, choose install from SD card
6. Choose install "update.zip" if you renamed it to that. Otherwise, choose the option to choose the file.
7. Viola!
JUST TO BE CLEAR YOU NEED THE VERIZON VERSION!!!!
Click to expand...
Click to collapse
thx for ur reply,
i plan to up 4.0.4 in this coming sat,
btw i read something on g+
"4.0.4 ROM + franco kernel"
what means "franco kernel"?
is it a meaning of rooting or just wipe a latest room?
billkkc said:
thx for ur reply,
i plan to up 4.0.4 in this coming sat,
btw i read something on g+
"4.0.4 ROM + franco kernel"
what means "franco kernel"?
is it a meaning of rooting or just wipe a latest room?
Click to expand...
Click to collapse
Its just a kernel made by a guy called Franco...if you don't know what it is NY recommendation is to just leave it.alone...you don't need that for the 4.0.4 from tow rock..
so just leave it alone...hope this helps and isnt too pate..

I am donating USD 100$ to the person who will write a STEP by STEP guide

Hi Guys
I am currently on Mike's ARHD 18.2 Rom and I am thinking of reverting back to completely stock Jelly Bean Rom .
So I am donating a USD 100$ to the person who will write a STEP by STEP guide with links to the correct download points etc. But my stock Rom should be ROOTED and all necessary apps like Busybox , SuperSU, etc should be flashed too.
Also this guide should mention how to achieve those steps , for example
Insetad of saying , FIND OUT YOU PHONE'S CID , it should explain me how to find out the CID such as : Goto Bootloader Mode by pressing Volume Down and Power button > Fastboot USB > Then on your PC at ADB screen type - fastboot oem readcid etc. etc.
Currently I am on Mike ARHD Rom 18.2 , my HBOOT is 1.39
Regarding on how to choose which person will get the 100$ , I think the people who want to make this guide should post a message here and I will choose who and tell him to proceed with the Guide .
I am an XDA member since 2006 and my word is trustable . If you look at Mike's Donation list , I am the highest single donator as well.
I want to make myself clear once more , think of me as a person who does knows just a little on HTC and Rooting and Flashing and ADB and etc. So do not think of me as a professional like you guys.
I prefer somebody who already uses Mike's ARHD rom for One X .....
Thanks Guys
Procedure is very simple: relock your bootloader and flash JB ruu
Re: ROOTing my phone, want to make sure a few things
Sent you PM.
I said , the stock rom then should be rooted as well ......
Yes, yes. No problem at all.
I will compile you a totally noob proof step-by-step guide, just read my PM.
doublecheese said:
Hi Guys
I am currently on Mike's ARHD 18.2 Rom and I am thinking of reverting back to completely stock Jelly Bean Rom .
So I am donating a USD 100$ to the person who will write a STEP by STEP guide with links to the correct download points etc. But my stock Rom should be ROOTED and all necessary apps like Busybox , SuperSU, etc should be flashed too.
Also this guide should mention how to achieve those steps , for example
Insetad of saying , FIND OUT YOU PHONE'S CID , it should explain me how to find out the CID such as : Goto Bootloader Mode by pressing Volume Down and Power button > Fastboot USB > Then on your PC at ADB screen type - fastboot oem readcid etc. etc.
Currently I am on Mike ARHD Rom 18.2 , my HBOOT is 1.39
Regarding on how to choose which person will get the 100$ , I think the people who want to make this guide should post a message here and I will choose who and tell him to proceed with the Guide .
I am an XDA member since 2006 and my word is trustable . If you look at Mike's Donation list , I am the highest single donator as well.
I want to make myself clear once more , think of me as a person who does knows just a little on HTC and Rooting and Flashing and ADB and etc. So do not think of me as a professional like you guys.
I prefer somebody who already uses Mike's ARHD rom for One X .....
Thanks Guys
Click to expand...
Click to collapse
Check mike's threads! He is providing stock roms with root busybox etc...
Sent from my HTC One X using xda premium
I know that
All I need is a Guide, I can not risk making errors and bricking my device.
So guys please do not send me ideas or where to collect the info, you all know what I want and I am ready to pay for it.
I prefer a ARHD rom user to write the guide, but if there isn't any around, I will give TToivanen the go to write the guide.
doublecheese said:
I will give TToivanen the go to write the guide.
Click to expand...
Click to collapse
Thank you. First of all, please reply to your private message, I've got some things to ask.
Odp: I am donating USD 100$ to the person who will write a STEP by STEP guide
1: Download a stock ROM with root & busybox.
2: Put it into the phone's memory.
3: Get into recovery.
4: Make a factory reset/wipe.
5: Flash the ROM.
6: Reboot into fastboot.
7: flash boot.img
8: Reboot
9: Now you've got a stock ROM with the features you wanted.
Sent from my BMW E32 using XDA App
TToivanen said:
Thank you. First of all, please reply to your private message, I've got some things to ask.
Click to expand...
Click to collapse
Ok man, thanks for your energy
Please START the guide , I will reply your PM
But I don't use Gtalk that much just for your info ...........
OK EVERYBODY , DEAL IS CLOSED , TTOIVANEN WILL START THE GUIDE !!!!
Even if you didn't pay me i would have done it ..... of i got a 100 bucks from everybody here i wrote a step by step guide i didn't have to do any other work no more !
Why not just come to IRC? I can do the stuff remotely for you
Before you begin, make sure USB-debugging is enabled, and that you have more than 50% of battery!
Enable USB-debugging by going to settings -> developer options -> USB debugging​
First download the needed files
Stock ROM
boot.img
Flashable .zip that installs superuser and busybox
(Thanks to mike1986. for the original files)
Transferring the required files onto your phone's internal sdcard
Connect your One X to your PC
Copy One_X_3.14.401.31_odexed.zip and Android_Revolution_HD_Root_and_BusyBox.zip to your phone.
Keep the USB cable connected
​
Flashing the boot.img
Copy boot.img to the folder on your PC that contains the files for adb/fastboot
Open fastboot command prompt
Type the following commands:
Code:
adb reboot bootloader
Wait until you see FASTBOOT USB on your phone's screen. Then type the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot erase cache
Flashing the ROM and rooting
Disconnect the USB cable from your phone
Using volume buttons, navigate to HBOOT, confirm by pressing power button.
Using volume buttons, navigate to RECOVERY confirm by pressing power button. Device will boot into recovery.
select wipe/factory reset
confirm by selecting yes
select install zip from sdcard
select choose zip from sdcard
select One_X_3.14.401.31_odexed.zip
confirm by selecting yes
select install zip from sdcard
select choose zip from sdcard
select Android_Revolution_HD_Root_and_BusyBox.zip
confirm by tapping yes
Select reboot system now
​There you go! If you have any problems, hit me up on Gtalk!
TToivanen said:
Before you begin, make sure USB-debugging is enabled, and that you have more than 50% of battery!
Enable USB-debugging by going to settings -> developer options -> USB debugging​
First download the needed files
Stock ROM
boot.img
Flashable .zip that installs superuser and busybox
(Thanks to mike1986. for the original files)
Transferring the required files onto your phone's internal sdcard
Connect your One X to your PC
Copy One_X_3.14.401.31_odexed.zip and Android_Revolution_HD_Root_and_BusyBox.zip to your phone.
Keep the USB cable connected
​
Flashing the boot.img
Copy boot.img to the folder on your PC that contains the files for adb/fastboot
Open fastboot command prompt
Type the following commands:
Code:
adb reboot bootloader
Wait until you see FASTBOOT USB on your phone's screen. Then type the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot erase cache
Flashing the ROM and rooting
Disconnect the USB cable from your phone
Using volume buttons, navigate to HBOOT, confirm by pressing power button.
Using volume buttons, navigate to RECOVERY confirm by pressing power button. Device will boot into recovery.
select wipe/factory reset
confirm by selecting yes
select install zip from sdcard
select choose zip from sdcard
select One_X_3.14.401.31_odexed.zip
confirm by selecting yes
select install zip from sdcard
select choose zip from sdcard
select Android_Revolution_HD_Root_and_BusyBox.zip
confirm by tapping yes
Select reboot system now
​There you go! If you have any problems, hit me up on Gtalk!
Click to expand...
Click to collapse
Thanks man, you did it very well, just like a guide should be , really appreciated, send me your paypal address $$$
mike1986. said:
Why not just come to IRC? I can do the stuff remotely for you
Click to expand...
Click to collapse
Sorry I didn't know that ...
Anyway TToivanen made a great guide and now in a few minutes I will follow it step by step .
I already preordered my HTC One , and while waiting for it I will play around with my One X and I hope to get rid of the LOW VOLUME LEVEL bug I am faced with by going completely stock .
I realised on some calls the volume level seems OK, but in some calls the volume is so low I can not hear the opposing person if I am in my car or outside ( where there are other noises around)
Since 1 friend has a completely stock HOX , I hope to reach his Volume Levels when I turn stock , another friend has the ARHD 9.8 and his Volume level is much higher than mine too.
I think the Step by Step guide that is made by TToivanen is just perfect, this is how a guide should be done , some peoble write guides too but I barely see one this clear and easy to understand .
I agree, it's perfect. But not everyone is getting 100$ for writing those guides
doublecheese said:
I think the Step by Step guide that is made by TToivanen is just perfect, this is how a guide should be done , some peoble write guides too but I barely see one this clear and easy to understand .
Click to expand...
Click to collapse
It just looks like a copy and paste from other guides already available online IMO (no offence )
EddyOS said:
It just looks like a copy and paste from other guides already available online IMO (no offence )
Click to expand...
Click to collapse
Doesn't matter if copy or not, it is what I asked for and he did it
Really that lazy you have to pay people instead of searching lmao?
Sent from my HTC One X using xda premium

[Q] Any 1 here experienced with kernels? Need your help for my Kitchen.

Ok firstly this may seem a bit confusing, I am copying this from a PM i sent to @wedgess
Hi, I am wondering if you would be able to make a bootable recovery image with TWRP as i have no idea how to do it and i can only find CWM ones which requires signature for "--update_package="
I don't want a kernel and i don't want a cwm image but i want just simple a TWRP recovery.img which is bootable like http://forum.xda-developers.com/showthread.php?t=1493996 but TWRP instead
Your kernel's work fine but i need it to boot a recovery.img then flash the new rom via "--update_package=" and then reboot device.
For more information check http://forum.xda-developers.com/showthread.php?t=2391169
I hope you can help, Thanks.
-------------------------------
TWRP works great with both the last 2 options so i need to some how create a bootable recovery img based on TWRP but i don't have a clue about kernel development... Could i maybe replace ramdisk with existing bootable recovery or something?
-------------------------------
So to put it simply, I need to switch out CWM on this recovery.img and put TWRP on it (The reasons for this are complicated to explain but i would be extremely thankful if any one could help and credit will be giviven)
So please can any one help me Thanks.
Sorry I didn't reply to your final PM as I said due to real life and limited time I cannot do it for you, But happy to help assisting you if needed. Championswimmer has a tutuorial on what to change in the device tree for TWRP. Search function is down ATM so I can't link you to the thread.
wedgess said:
Sorry I didn't reply to your final PM as I said due to real life and limited time I cannot do it for you, But happy to help assisting you if needed. Championswimmer has a tutuorial on what to change in the device tree for TWRP. Search function is down ATM so I can't link you to the thread.
Click to expand...
Click to collapse
Yeah no worries, Decided to ask any one else, As i really don't have the time to do this aswell as all the other stuff im doing. And it will take some one with experience a lot less time.
I tried switching out the /sbin folder but it didn't work and i didn't expect it to
I am hoping to find some 1 with a linux enviroment all sorted as i don't have a clue when it comes to kernels. surely there is a simple way to switch out a prebuiilt CWM Recovery with a TWRP recovery? Do you know what files TWRP and CWM use?
Thanks.
Altenatively any ideas on what needs to be changed to boot it to recovery always? if so i could modify a existing TWRP kernel (yours for example) and then force it to recovery.
EDIT
I assume you meant this guide?
PORT TO STOCK/ICS/YOU-FAVOURITE-KERNEL
A boot.img consists of the kernel image and the ramdisk (additionally and optionally RPM.bin and commandline). If you want to use TWRP for some other kernel, you have to do this
1. decompile this boot.img (for 2011 models it's a true boot.img, for 2012 models, it's actually a kernel.elf file renamed to boot.img, so you have to decompile accourdingly. you can use my kernel kitchen to do the same)
2. replace the kernel zImage with the one from the kernel you want to port to
3. replace /sbin/ramdisk.cpio with the "UNCOMPRESSED" ramdisk of the kernel you want to port this to. (usually ramdisk is compressed with gzip i.e. ramdisk.cpio.gz. you need to uncompressed ramdisk image i.e. ramdisk.cpio)
4. do not touch anyother thing
5. pack it up into a boot.img (for 2011) or kernel.elf (for 2012) and fastboot it
@wedgess ok so i got it working it now auto boots to TWRP but ADB isn't working, Any ideas?
Thanks so much i got it all working that guide helped
I am curious of what you are trying to do...
As i understand you want:
-flash (only) twrp recovery in fastboot mode
-reboot to recovery and flash rom from pc (adb sideload maybe?)
-reboot to fastboot again to flash kernel
-reboot
If i understand correctly you want to flash ROM (and kernel) from PC side, not dong it from phone?
Bakisha said:
I am curious of what you are trying to do...
As i understand you want:
-flash (only) twrp recovery in fastboot mode
-reboot to recovery and flash rom from pc (adb sideload maybe?)
-reboot to fastboot again to flash kernel
-reboot
If i understand correctly you want to flash ROM (and kernel) from PC side, not dong it from phone?
Click to expand...
Click to collapse
ok this is what happens
1. Download rom and kernel from my kitchen via helper application on windows
2. verifiy md5's
3. fastboot fllash new kernel
4. fastboot boot "recovery.img"
5. once in the new bootable recovery i created/edited, send adb command "adb shell" > recovery --update_package=ROM
6. wait for rom to install, reboot
7. DONE! new rom and kernel flashed
All done automagically and without any user interaction other than picking the rom.
Check post 1 and 2 for more info - http://forum.xda-developers.com/showthread.php?p=46111684
fma965 said:
ok this is what happens
1. Download rom and kernel from my kitchen via helper application on windows
2. verifiy md5's
3. fastboot fllash new kernel
4. fastboot boot "recovery.img"
5. once in the new bootable recovery i created/edited, send adb command "adb shell" > recovery --update_package=ROM
6. wait for rom to install, reboot
7. DONE! new rom and kernel flashed
All done automagically and without any user interaction other than picking the rom.
Check post 1 and 2 for more info - http://forum.xda-developers.com/showthread.php?p=46111684
Click to expand...
Click to collapse
One word: WOW :good:
Not just you have ideas what you can do, but knowledge to do it. You have my respect man :highfive:
i'll check that app ASAP
Bakisha said:
One word: WOW :good:
Not just you have ideas what you can do, but knowledge to do it. You have my respect man :highfive:
i'll check that app ASAP
Click to expand...
Click to collapse
Thanks current released version is quite buggy but new version coming soon
Any way since this problem is now solved, I will close the thread. if you want to discuss this then post on my kitchen thread or pm me

[TUT] How to install CyanogenMod 11 /or any other ROM on your Xperia S 6.2.b.1.96

Okay guys,
I spent a whole day yesterday to exterminate lame SONY's firmware, and get a refreshment alternation
so I gathered all tutorials, which I had followed to give my Xperia S new soul, and made this all-in-one tutorial for anyone, who's not sure how to do it.
Big thank to DooMLoRD, who's is making all this awesome tools and stuff to make our Xperias alive again.
Before proceding, Your Xperia S should run on the latest official Sony's firmware (6.2.b.1.96). Otherwise...otherwise you probably ought to update it to the latest version.
Here are the links to the sites I used. I also recommend you to check them out, because there may be a more recent version of a file:
http://forum.xda-developers.com/showthread.php?t=2555243
http://forum.xda-developers.com/showthread.php?t=2447319
http://forum.xda-developers.com/showthread.php?t=2417672
1. Bootloader unlock
Checking (source: JuniorMember's post: http://forum.xda-developers.com/showpost.php?p=44713761&postcount=14)
1.1.1. In dial pad, type in *#*#7378423#*#*
1.1.2.Go to Service Info > Configuration
1.1.3. And check the Rooting Status
If it's Bootloader unlock allowed:Yes/No, then its not unlocked. If it says NO, you're not able to unlock it.
And if it's Bootloader unlocked:Yes, then it's (already) unlocked.
Unlocking (source: DooMLoRD's tutorial)
[ before we begin unlocking bootloader ]
1.2.1 Get the IMEI code for your device: type *#06# in phone dialer to find it out; note only the digits (no dashes)
1.2.2 Download the fastboot package with usb drivers (alternate drivers if the ones in package dont work OR this)
IMPORTANT: if you are using Windows 8 you will need to enable few things to allow driver installation
1.2.3.Make sure you have a windows PC with USB cable to connect the phone
1.2.4.Power down your phone and keeping the Volume Up button pressed connect the USB cable to PC; this will trigger FASTBOOT mode and windows will start driver installation, extract the above package and point the driver install to that location (usb_driver) folder.
If a phone enters but does not stay in a fastboot mode:I had that kind of problem, but I'm not sure how I actually fixed it; I only remember I did that:
1.2.4.1. Download and install Flashtool . After Installing, go to the folder where fastboot is installed and look for drivers folder; there you'll find Flashtool-drivers.exe. Install that: Be aware that there are Flashboot and Fastboot drivers at the bottom or at the top of the list Check also your phone's name.
1.2.4.2. If still does not work go to Device manager, trigger fastboot mode, connect to your computer, and quickly (when S1 Boot or sth like that appers in Device Manager) click with right mouse button (go to properties), then update driver and point to (usb_driver) folder in fastboot_with_Android_USB_file folder -> step 1.3.6.
1.2.5. Once drivers are installed just disconnect cable and power on device
[ how to unlock ] (official way)
1.3.1 First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu: steps 1.1.1 - 1.1.3
1.3.2 Go to: http://unlockbootloader.sonymobile.com/ and read everything!
1.3.3 At the bottom click 'Start Unlocking the Bootloader'. Scroll to the bottom of the page and click "Continue" You will get numerous prompts, read all info and if you agree, click on "Accept"/"OK"/"Proceed"
1.3.4 Finally you will get a "Create Unlock request" page, enter your IMEI (sometimes the last digit needs to be removed for this to work), name and email address
1.3.5 You should now receive your unique unlock key via EMAIL, SAVE THIS KEY SAFELY
1.3.6 Extract fastboot_with_Android_USB_file.rar and open fastboot folder
1.3.7 Hold SHIFT and right click on the background of the folder Select 'Open command window here'
1.3.8 Connect your phone in fastboot mode (turn phone off, hold Volume UP button and plug in USB Cable) [make sure drivers are installed as explained above)
1.3.9 In the cmd windows type in fastboot.exe -i 0x0fce getvar version
1.3.10 If a value is returned (it will return 0.5), it means the phone is correctly connected
1.3.11 Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
1.3.12 You're device should now be bootloader unlocked. You can check by followin steps 1.1.1 - 1.1.3.
2. Root (source: DooMLoRD's tutorial)
2.3.1 Download the three files from the download section in this post.
2.3.2 Open FlashTool and flash the XperiaS_LT26i_6.2.B.0.211_KernelOnly.ftf - 6.36 MB file, this is JUST the kernel of an older firmware which was rootable.
2.3.3 How to flash Put XperiaS_LT26i_6.2.B.0.211_KernelOnly.ftf to firware folder, which you can find in Fastboot's installation folder. Then hit the lighting strike, select Flashboot mode and select the kernel and hit flash and follow instructions how to enter flashmode.
2.3.4 Now once flashing is done reboot device and connect to PC in usb debuggin mode
2.3.5 CLOSE FLASHTOOL <<< VVVIMP STEP (Very very very important step it took me some time to figure out its meaning)
2.3.6 Extract the file DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit.zip to root directory on c:\
execute runme_ file corresponding to your OS on desktop PC, this will execute a SPECIAL version of DooMLoRDs easy rooting toolkit <<< VVVIMP STEP
2.3.7 the above step is crucial! if you use any older version of the toolkit then IT WILL NOT WORK!
2.3.8 after rooting is over the device will restart
2.3.9 you can verify if device is rooted by checking for SuperSU app (it is the newest version)
2.3.10 once that's done, power down device and open FlashTool again
2.3.11 now flash XperiaS_LT26i_6.2.B.1.96_KernelOnly.ftf - 6.33 MB file to get back to the true kernel for the firmware
that's it after flashing is done just disconnect and power on device and enjoy rooted phone! Check with Root Checker app from GPlay.
3. CWM Recovery (source: hm9408's thorough version of DooMLoRD's tutorial)
3.1 Go to google play and download busybox. Once installed, open the app and tap install Also, make sure, you have SuperSU installed.
3.2. This should be relatively easy now. Your phone is now rooted, and you will now flash CWM Recovery on your phone. For this, hm9408 found a quick installer by DooMLoRD.
3.3 Just extract it anywhere, run it (cwm-install-en.bat, press Enter 3 times and it will start) while your phone is connected via USB, and you should be just fine. I had to do this step twice, because I didn't know you have to grant something with SuperSU. So during the process, watch the phone's screen.
3.4 You know CWM was flashed correctly when you shut down your phone, turn it on and your see the LED turns on BLUE when the Sony logo comes up. When it does, press the Volume Up button and the LED should turn GREEN for a couple of seconds, then boot into Recovery.
4. Installing custom ROM and gapps (google apps)
There's a link toCyanogenMod 11 beta 3 by RaymanFX which has already included kernel.
Other ROMs may not have included kernel, so you'll have to (1) flash it with Flastool, if it has kernel extension or (2) install it via recovery, it it has .zip extension.
4.1 Copy your ROM and gapps (their extensions have to be .zip.
4.2 Boot into recovery (step 3.4).
4.3 Navigate (with volume + and -, and power to select) to install zip, then select the file of you rom, install it, then install also the gapps by selecting the gapps.zip.
4.4. This is the most important step, DO NOT SKIP IT AT ALL COSTS For God's sake, in the main menu, wipe the cache and partitions and dalvik's cache. (I'm not sure if it's available to wipe dalvik's cache, but if it is, wipe it).
I forgot to wipe, and, holy cow, almost lost my pants, because phone didn't start, there was only sony's logo, slowly passing away again and again.
Well if that happens, look for an Xperia S firmware (e.g.) and appropriate kernel (e.g.), flash them via flashtool and wipe your sweat .
I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.
xDroidZz said:
I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.
Click to expand...
Click to collapse
Lol ya.
Sure?
xDroidZz said:
I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.
Click to expand...
Click to collapse
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!
Joej970 said:
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!
Click to expand...
Click to collapse
are you kidding me? it takes me max 1 hour to read tutorial, unlock BL, flash custom kernel and flasch CM rom :laugh:
Joej970 said:
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!
Click to expand...
Click to collapse
Nah. Max is 1H. there are alot of TUT already. but thanks anyways for this TUT helps alot of people who are actually new to this device
dobi235 said:
are you kidding me? it takes me max 1 hour to read tutorial, unlock BL, flash custom kernel and flasch CM rom :laugh:
Click to expand...
Click to collapse
It takes you one hour once you exactly know how to do it and in case you already have all files downloaded.
And about tutorials: they're often incomplete. In my case, I struggled with finding drivers for fastboot and making them work 4hs. The unlock tutorial says to install one drivers then try another, but none of them worked. So it took me time to search forums and find something out. Here, I wrote what I'd done, so anyone else would know what to do.
Edit: every tutorial about unlocking says Windows should report unsuccessful installation when you connect the device in fast boot mode. Well, my didn't report that, so I wasn't able to point to the usb_folder. And then phone booted up after 5secs in fastboot.
Joej970 said:
It takes you one hour once you exactly know how to do it and in case you already have all files downloaded.
And about tutorials: they're often incomplete. In my case, I struggled with finding drivers for fastboot and making them work 4hs. The unlock tutorial says to install one drivers then try another, but none of them worked. So it took me time to search forums and find something out. Here, I wrote what I'd done, so anyone else would know what to do.
Edit: every tutorial about unlocking says Windows should report unsuccessful installation when you connect the device in fast boot mode. Well, my didn't report that, so I wasn't able to point to the usb_folder. And then phone booted up after 5secs in fastboot.
Click to expand...
Click to collapse
no it took me hour to search for tutuorials (doom has for root and for unlocking BL too), read that, backup TA partiton, unlock, root, flash... DONE
I needed an whole afternoon, too! If you have to read everything from beginning and you are not able even to deal with the technical terms it needs long time. So, if I wouldn't have done it before, this tutorial would have been very useful to me :good:
magician
dobi235 said:
no it took me hour to search for tutuorials (doom has for root and for unlocking BL too), read that, backup TA partiton, unlock, root, flash... DONE
Click to expand...
Click to collapse
Well okay. Then write that down to a paper and stick it to a mirror, so you'll see your extraordinary achievement every time you wake up, and be proud of yourself, cause you did all that for the fisrt time in only one hour, although everyone else needed an afternoon. You're probably the smartest person I've ever seen, cause you apparently do magic :good:
Repair shops should totally hire you, since they often need an eternity to do their job.
Cheers
Joej970 said:
Well okay. Then write that down to a paper and stick it to a mirror, so you'll see your extraordinary achievement every time you wake up, and be proud of yourself, cause you did all that for the fisrt time in only one hour, although everyone else needed an afternoon. You're probably the smartest person I've ever seen, cause you apparently do magic :good:
Repair shops should totally hire you, since they often need an eternity to do their job.
Cheers
Click to expand...
Click to collapse
i only wanted to say that this thread is completely unnecessary.. this phone is more than 2 years old... last update was i think 1year ago.. so there is nothing new... tutorials for unlocking BL (2nd March 2012) and for rooting (17th June 2013) are here for more than a year...and tutorial for instaling CM you can find in almost every CM thread... thats all I wanted to say :victory:... have a nice day
It is kinda necessary..
Some people still dont know how to flash these roms...And then end up spamming other threads...:/
Joej970 said:
Okay guys,
I spent a whole day yesterday to exterminate lame SONY's firmware, and get a refreshment alternation
so I gathered all tutorials, which I had followed to give my Xperia S new soul, and made this all-in-one tutorial for anyone, who's not sure how to do it.
Big thank to DooMLoRD, who's is making all this awesome tools and stuff to make our Xperias alive again.
Click to expand...
Click to collapse
Your method is long and unnecessarily beating around the bush. Here's a much quicker way (how I did it in less than half an hour):
1) Copy the ROM zip to your internal storage
2) Unlock bootloader with Sony's info on their site.
3) Extract boot.img from the ROM zip / kernel zip.
4) In fastboot mode,
Code:
fastboot flash boot boot.img
fastboot reboot
5) Go into recovery while it's rebooting, wipe everything & flash the ROM zip.
TBH, DoomLord's stuff is not required, never really was for me..
Sure, it's good stuff, but not required in this case..
The tutorial is good, it's just unfortunate, is that after more than two years, yet no one has been able to unlock the bootloader problem that allows not be unlocked.
Sent from my LT26i using XDA Premium 4 mobile app
Great_Geek said:
Your method is long and unnecessarily beating around the bush. Here's a much quicker way (how I did it in less than half an hour):
1) Copy the ROM zip to your internal storage
2) Unlock bootloader with Sony's info on their site.
3) Extract boot.img from the ROM zip / kernel zip.
4) In fastboot mode,
Code:
fastboot flash boot boot.img
fastboot reboot
5) Go into recovery while it's rebooting, wipe everything & flash the ROM zip.
TBH, DoomLord's stuff is not required, never really was for me..
Sure, it's good stuff, but not required in this case..
Click to expand...
Click to collapse
Hey, hey, hey,
where do you type that code in? In terminal emulator on a phone or maybe cmd on a computer? I've seen a lot of tutorials ordering to type a code, but none of them actually explained how and where you have to write it.
Thankss!
Joej970 said:
Hey, hey, hey,
where do you type that code in? In terminal emulator on a phone or maybe cmd on a computer? I've seen a lot of tutorials ordering to type a code, but none of them actually explained how and where you have to write it.
Thankss!
Click to expand...
Click to collapse
You use fastboot.exe or the fastboot binary for linux, same one that you used for unlocking bootloader..
Finding something to type into terminal emulator is pretty rare, and it'll usually be specified that you need to type it there..

Categories

Resources