[CWM] current DIRTY way to install new ICS ROM as [ICS kernel + CWM] not yet out +OTH - Sony Xperia P, U, Sola, Go

Ok guys with itchy hand me included =_="
This guide is for those who know what I'm talking about, and since ICS kernel with CWM is under its way soon. but we just dont want to make our lovely dev stop making new rom.
This thread originally made for Sola but i think the others will also work if you know what to do and what i mean.
well... I've tested this many times and its ok to flash kernel and also ok to jump from one to another.
!!!disclaimer!!!
!!!with this guide you are the one responsible on what you did to your phone bricking it included, not me or anyone else!!!
We have everything in our hands already.
things needed to make this happen
-A working fastboot
-ANY working kernel with CWM
-Stock kernel
grab that stock ics tft file and open archive using 7Zip and rip that kernel.sin
-remember this... POWER + Vol-up wait for the 3 combo vibrate is force POWER OFF <-- unless you can pull out your battery
-and the rom that you want to test
now lets get things moving
1. power off your phone and put it into fastboot mode "vol-up + usb to pc" purple LED
2. flash your favorite gingerbread kernel with working CWM
fastboot flash boot [NAME OF KERNEL+CWM.elf]
3. unplug the phone and power on. wait for LED light than press "vol-up" to get to CWM
4. if you have not copy the rom, this is a good time to visit mount usb and do your things.
5. wipe data.
6. flash your test ROM
7. after the zip have been completely flashed in to the system. dont bother to reboot phone. instead
8. FORCE power off by holding "vol-up and power button" wait for the 3 combo vibrate. now the phone is OFF.
9. put phone into fastboot mode "vol-up + usb to pc" purple LED again
10. flash that kernel.sin that you rip of from the whole tft... the ICS stock kernel
fastboot flash boot kernel.sin
11. power on and wait the first boot that take ages
12. there you are.... A new test rom
14. Give feed back to ROM dev
note: if it got stuck at Sony logo, where you should expect animation boot screen. force power off and on it again to test. and wonder did you flash the rite kernel.
note2: I'm not putting links as you should know where to get the stuff above. give them proper thanks by hitting the thanks button or donate beer for them if you can.
--------------- Added entry -----------------
* if you lost root, try Bin4rys method to trick the phone that in need to restore the root function<-------- updated 5th oct 2012 >__<
-----------------------------------------------------------------------------------------------------------------------------------------
This will be a big one.... <--------5th OCT 2012
-----------------------------------------------------------------------------------------------------------------------------------------
OK guys, I'm on a windows7 64bit machine and i'm not a linux guy...
the next entry will try to smooth the process and have lots of future use
------------------------------------------------------------------
only for your pc side
------------------------------------------------------------------
things to do
1. add system path
2. ease of access your cmd ^^
3. some batch file ideas that automate things
you should have known this as it have been floating around in xda,
skip this if you dont need it.
-----------------------------------------------------------------------------------
WARNING, we are going to touch some windows stuff,
try not to mess up. but if you do mess things up you are
the one responsible for it ^^
-you are here to learn something. try not to copy paste.
------------------------------------------------------------------------------------
1. add a system path
here's some basic and recap that's have been around xda.
set your windows system variable for ease of command key via your local cmd.
we need a place to start. as i know most of you have installed flashtool. flashtool have a good set of adb and fastboot within its folder.
where else if you want to use android sdk's folder thats up to you to look for the adb and fastboot folder.
here's the location of flashtools adb and fastboot "C:\Flashtool\x10flasher_lib" on my machine <----- yours might be different
we are going to add "C:\Flashtool\x10flasher_lib" into the system path
So, where is it??? (i'm on a windows 7 so you have to figure out where it is ok... )
from the control panel look for system,
In the System window, on the left panel click on the Advanced System Setting.
a System Properties window will pop up
In the Advanced section, click the Environment Variables button.
Finally, in the Environment Variables window (as shown below), highlight the Path variable in the Systems Variable section and click the Edit button. Add or modify the path lines with the paths you wish the computer to access. Each different directory is separated with a semicolon as shown below.
e.g (the ones below is mine... dont follow you should have yours)
C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Program Files (x86)\AMD APP\bin\x86;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QT Lite\QTSystem;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Flashtool\x10flasher_lib
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so, in this path property click the "Edit" button, go to the end of the whole string.... and add a semicolon( ; ) and paste the address of where adb and fastboot located
and continue to 'OK' and close the rest of the windows that you dont need.
to test, press this combo [window key + "R"] to have to run windows up and just type cmd and hit ok
in the cmd try just type adb... and it'll give you feed back that just adb is not enough and throw you a list of things adb can do.
now you can fire up adb and fastboot anywhere you want.
2. ease of access your cmd ^^
make a cmd shortcut that will start at the current folder and also run as admin
as you will now go to the folder where you most likely do flash something or adb something
right-click on an empty space and hit new ---> shortcut.
Type the location of the item:
cmd
click next and finish..
now you have a cmd shortcut that only start in the system32 folder...
than we got 2 more things to do with this short cut before its usable.
1.right click the new cmd shortcut and hit properties
EMPTY the "start in:" text box, you want it to start anywhere the short cut is located.
2.still in the same properties and hit the "Advanced..." button and activate "Run as administrator"
OK than apply... you are done. now you can copy paste this short cut any where you want with proper use .
3. some batch file ideas that automate things
the good thing about adb and fastboot.. it will wait for your device. thus automating things can give a good approach.
bare in mind that automation is a good thing. but if you have multiple device. be careful dont automate the wrong command
we call a [something].bat file a [something] batch file...
with the "path" to your adb and flashtool done earlier, you can start making batch file to auto mate things in any folder you wish. just make sure all the other ingredient are in the same place or you can link it to. Bin4ry root tool that you just had is a good place to learn and i'm sure there are other tutorial floating in XDA... just use the search or ask GOOGLE for it.
and you can always right click and add a new ---> text document
fire up notepad and start writing automated fastboot comand or adb install "stuff"
and save as ".bat" file.... you should know what i mean. NOT "filename.bat.txt"
File name: [something].bat
Save as type: All Files
eg: a batch file "flash stock ICS kernel.bat" and "kernel.sin" MUST in the same folder where this batch file located
Code:
@echo off
COLOR 0A
fastboot flash boot kernel.sin
ping 127.0.0.1
PAUSE
echo device will boot after ping
ping 127.0.0.1
fastboot reboot
PAUSE
eg: logcat.bat
Code:
adb logcat
PAUSE
to exit the logcat press Ctrl+C
it will ask you if you really want to stop.
i add a ping 127.0.0.1 just to make a ping delay so that we can see the batch have done the fastboot and do other job like ping local host
4 times and proceed to fastboot reboot. PAUSE if you want it to wait it for you to hit any key than proceed. COLOR 0A to make things green.
there are many more to learn.
NOW... SOMEMORE OLD SCHOOL FUN ^_____^ batch files..... i love them and so will you
------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------
Last but not least, I would like to thank Koush who made CWM. next i want to thank the DEVs here who spend there time making good kernel with CWM. AND also ROM developers who made our android so fascinating! and those of us with itchy hands that made this forum fun and alive. and rohit3221 for lightning fast upload the ICS tft
LETS HAVE SOME FUN with OLD SCHOOL STYLE >_<
ouch!!!
@cooleagle OR E.Cadro- please send this thread to Xperia S, P, U, Sola, Acro S General. I think this tutorial fit as the others will be going trough the same process...
the only different is that some phone can take there battery out to force power off. This should also work for JB if theres no JB+CWM kernel. since CWM have nothing to do with the kernel or how the phone is running... its just a recovery part of the phone that should be there in the first place but Sony just didn't prepare us a recover partition..

psyionx said:
Ok guys with itchy hand me included =_="
This guide is for those who know what I'm talking about, and since ICS kernel with CWM is under its way soon. but we just dont want to make our lovely dev stop making new rom.
This thread originally made for Sola but i think the others will also work if you know what to do and what i mean.
well... I've tested this many times and its ok to flash kernel and also ok to jump from one to another.
!!!disclaimer!!!
!!!with this guide you are the one responsible on what you did to your phone bricking it included, not me or anyone else!!!
We have everything in our hands already.
things needed to make this happen
-A working fastboot
-ANY working kernel with CWM
-Stock kernel
grab that stock ics tft file and open archive using 7Zip and rip that kernel.sin
-remember this... POWER + Vol-up wait for the 3 combo vibrate is force POWER OFF <-- unless you can pull out your battery
-and the rom that you want to test
now lets get things moving
1. power off your phone and put it into fastboot mode "vol-up + usb to pc" purple LED
2. flash your favorite gingerbread kernel with working CWM
fastboot flash boot [NAME OF KERNEL+CWM.elf]
3. unplug the phone and power on. wait for LED light than press "vol-up" to get to CWM
4. if you have not copy the rom, this is a good time to visit mount usb and do your things.
5. wipe data.
6. flash your test ROM
7. after the zip have been completely flashed in to the system. dont bother to reboot phone. instead
8. FORCE power off by holding "vol-up and power button" wait for the 3 combo vibrate. now the phone is OFF.
9. put phone into fastboot mode "vol-up + usb to pc" purple LED again
10. flash that kernel.sin that you rip of from the whole tft... the ICS stock kernel
fastboot flash boot kernel.sin
11. power on and wait the first boot that take ages
12. there you are.... A new test rom
14. Give feed back to ROM dev
note: if it got stuck at Sony logo, where you should expect animation boot screen. force power off and on it again to test. and wonder did you flash the rite kernel.
note2: I'm not putting links as you should know where to get the stuff above. give them proper thanks by hitting the thanks button or donate beer for them if you can.
Last but not least, I would like to thank Koush who made CWM. next i want to thank the DEVs here who spend there time making good kernel with CWM. AND also ROM developers who made our android so fascinating! and those of us with itchy hands that made this forum fun and alive. and rohit3221 for lightning fast upload the ICS tft
LETS HAVE SOME FUN with OLD SCHOOL STYLE >_<
ouch!!!
@cooleagle OR E.Cadro- please send this thread to Xperia S, P, U, Sola, Acro S General. I think this tutorial fit as the others will be going trough the same process...
the only different is that some phone can take there battery out to force power off. This should also work for JB if theres no JB+CWM kernel. since CWM have nothing to do with the kernel or how the phone is running... its just a recovery part of the phone that should be there in the first place but Sony just didn't prepare us a recover partition..
Click to expand...
Click to collapse
nice trick...

ouch....
forgot to stress Nandroid backup as do your things at #4

psyionx said:
... combo vibrate is force POWER OFF <-- unless you can pull out your battery ...
Click to expand...
Click to collapse
This threat is under sola Android development ... And The battery of Sola (as far as i can see ) is sealed (mine is)
BTW: NICE TRICK

Moved to General per op's request
Sent from my Nocturnalized One XL using Forum Runner

Dude what if i install a GB ROM with a Kernel supporting CWM first..... then flash the ICS custom rom via CWM... then when the device is off connect it with the flashtool in flashmode and flash only by selecting the kernel.sin file from the official firmware ( given that the official ics rom is in the firmware folder) it should work..... do u have any opinion??? its may save us from unzipping and fastbooting (2nd time).....

pulak861 said:
Dude what if i install a GB ROM with a Kernel supporting CWM first..... then flash the ICS custom rom via CWM... then when the device is off connect it with the flashtool in flashmode and flash only by selecting the kernel.sin file from the official firmware ( given that the official ics rom is in the firmware folder) it should work..... do u have any opinion??? its may save us from unzipping and fastbooting (2nd time).....
Click to expand...
Click to collapse
yup, it'll work.
you'll have the option to wipe data and the other stuff came with the tft packages...
ok.... i'll add something on the "added entry" to speed things up... hope you guys can catch what i'm trying to pass...
stay tuned... [fingers crossed]

1. I flash a gingerbread kernel with CWM on my XPERIA U running ICS.
2. I fastboot or flash mode flash kernel.sin from the ICS ftf.
3. When done I'll have the ICS firmware with ICS kernel with CWM recovery.
Is that right?
Tapatalked !

Rapier07 said:
1. I flash a gingerbread kernel with CWM on my XPERIA U running ICS.
2. I fastboot or flash mode flash kernel.sin from the ICS ftf.
3. When done I'll have the ICS firmware with ICS kernel with CWM recovery.
Is that right?
Tapatalked !
Click to expand...
Click to collapse
I don't think you will have CWM with ICS kernel.When you flash ICS kernel CWM will be gone.

Rapier07 said:
1. I flash a gingerbread kernel with CWM on my XPERIA U running ICS.
2. I fastboot or flash mode flash kernel.sin from the ICS ftf.
3. When done I'll have the ICS firmware with ICS kernel with CWM recovery.
Is that right?
Tapatalked !
Click to expand...
Click to collapse
nope.... like other android phone... they have another partition called the recovery partition. Some phone like the one we have Xperia does not have this special partition. Sony Ericsson than Sony just didn't give us this partition.
normally we will just fastboot flash recovery [cmd-recovery] and we have a cmd recovery replacing the ones given.
but we dont have this recovery partition.
thus what the dev here came with the idea to cook the recovery with kernel together. And we have a working recovery side by side with kernel in boot partition.
in the early days of xperias.... i remember Xrecovery is cook into the system. well... i do hope this will turn up since building a kernel+recovery need kernel sourcecode. where else Xrecovery need to change some file in android system to make it accessible from boot.
i did try putting xrecovery in system folder along with the other files. and boot the phone with my fingers at the [back] touch button. the phone just hung there. thus it need further changes to make it work.

Also using the wrong kernel is quite regularly known to brick phones, so be careful not to turn it on without the correct installed!
Sent from my LT26i using Tapatalk 2

Ben36 said:
Also using the wrong kernel is quite regularly known to brick phones, so be careful not to turn it on without the correct installed!
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
well... if you put it that way. There's always a risk...
eg, the accidental USB unplug or thouse usb cable that you just need to twist the cable to get a connection really need to avoid... place your phone somewhere safe while working. and Keep cats away.... they just likes wriggling wires.
^ __ ^

I think you'll be fine as long as you don't turn it on to boot up with the wrong kernel. Lol
Sent from my LT26i using Tapatalk 2

Ben36 said:
I think you'll be fine as long as you don't turn it on to boot up with the wrong kernel. Lol
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
did that many times.... it'll just get stuck and loops....
unbrick by flashing the correct ones ^ ^

Will this method work for locked bootloaders?

kevin.26 said:
Will this method work for locked bootloaders?
Click to expand...
Click to collapse
no

Related

Install ClockworkMod Bootloader and Cyanogen 7 ROM to Samsung G5 I5500

This is how to root and install a custom ROM on the Samsung I5500 mobile phone. I believe this may work on other Samsung handsets like the I5503 and I5508 but the I5500 is the only handset I have unlocked with the following tutorial.
I have tested this method using a new G5 in December 2011 but please understand that neither I nor the publishing website will take any responsibility for damage that may occur to your phone if you choose to follow this procedure and something goes wrong.
Firstly I’d like to thank JC_Master and CLShortFuse from XDA Developers and psyke83 from the ever informative MADTEAM for their work to make this possible.
There are a few different ways of doing this and I think I have tried them all, some resulting in a dead phone, some that just don’t work and some that are badly explained. This method has been tried and tested by myself and I will do my best to tutor it as simply as I can so that even a novice computer user may successfully flash / de-brand their phone from the putrid Samsung software!
OK, you ready?
Step 1
1.1 We need to install a boot-loader as the Samsung one is very limited and just plain awful! That said, it wasn’t intended to be used for anything other than the Samsung software so it’s not awful from their point of view but it’s pretty unfriendly to us.
1.2 If you know what a boot-loader is then skip to 1.3. A boot-loader is like a computers BIOS menu. If you have ever noticed when you turn on your computer there is some written text displayed (usually ‘Press F2 or DEL to enter Setup’) before it starts to boot Windows or whatever operating system it uses. If you push F2 or DEL when your computer tells you that you can you will go into a control interface that has options that you can set to tell your computer what to do when it is turned on and how to do it. Most computers are set to boot from the hard-disk first which is why yours starts to load your operating system. Many mobile phones work in the same way and the boot-loader (or BIOS) that we need to install will give us options to install our new ROM, to backup our phone data, to root it (gain entry to the system files – like being able to enter your ‘C:’ hard disk in Windows) and much more that the Samsung boot-loader will not.
1.3 Fortunately for us there is a clever bunch of people over at clockworkmod.com that have released a nice boot-loader for us that is just the job. They make these modded software files for us for free so please do donate something to them if you use their software so they can continue their work. Create a new folder called Samsung in your computers (C hard disk drive by left clicking Start Menu, Computer (or My Computer), double left click (C, right click (not on a file or icon) select New, Folder, type Samsung and the double click the folder to open it. Now resize the folder so it is not using the whole screen or minimize it but don’t close it. If you do close it, you know where it is! ‘C:\Samsung’
1.4 Download ClockworkMod-Galaxy5-v0.5 (Click the link) and SAVE it to your ‘C: \Samsung’ folder. For non I5500 mobile phones find your boot-loader here
1.5 Now let’s get the nice new Android ROM and its latest hotfix too. Remember to donate here as these boys have got to eat too! Download update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip and v1.7.2-hotfix1.zip SAVE to your ‘C: \Samsung’ folder.
1.6 Once this is all done we can install an app from the ClockworkMod team called ‘ROM Manager’ which will allow us to recover, backup and restore our phone. Download it now to the same folder and we’ll do that last ROM Manager APK
1.7 Lets also get the latest Google applications pack to install later too gapps-gb-20110828-signed.zip
1.8 **Ignore this step** In order to write any new information to the phones system files we need to get permission to do so and Samsung don’t give you this permission, this is known as ROOT access. There are many installable applications for the G5 that claim to root your phone but the only one I have found that works is Super One Click. This is a Windows installed based program (.exe) and not an APK (.apk – Android phone installed application). Download it here SuperOneClick usual folder!
1.9 Next we need to download and install the Samsung USB drivers. If you have Samsung Kies running then stop or disable it. If you don’t know what I mean then don’t worry about it! Download SamsungUSB to anywhere on your PC and double click it to install it.
1.10 We now need ODIN 4.28 which is the Samsung software that runs on Windows that will allow us to flash our new boot-loader and ROM over the USB cable that came with the phone. We also need an OPS file which is a text type document that specifies the phones perimeters to ODIN so that it can flash (install) the ROM correctly. Download to your Samsung folder ODINv4.28 and the OPS file EUROPA_v1.0.ops
Step 2 – Let’s Do It!
The following tutorial (edited) taken from MADTEAM with acknowledgement and thanks to MayurV
Copy to your phones micro SD card, ‘update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed’, ‘v1.7.2-hotfix1’ and ‘gapps-gb-20110815-signed’ before proceeding. This is best done by removing it and inserting it into a P.C’s or laptop’s SD card reader, if it has one.
2.1 First we have to get into Samsung standard recovery mode. You can enable this mode by following screenshot shown below. You phone must be turned off with the USB unplugged before doing this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.2 Now start Odin Multi Downloader v4.28 in your C:\Samsung folder on your PC. You will see following window.
- At first you may notice Odin says ‘Android’ and not ‘GT-I5500’. This is because we have not yet loaded the OPS file.
Your phone must now be in Download Mode and should be connected to the PC with the USB Cable that the phone shipped with. This is the only way Odin can detect your phone.
2.3 Select the OPS file in by clicking the OPS button (No.3) and the ClockworkMod-Galaxy5-v0.5 by clicking the One Package button (No.4).
Once you click on start button you will see all files will write on your phone, it will take around 1-7 minutes.
Once you see “PASS” in ODIN tool, you can remove USB cable from PC. Once your phone has rebooted and you will see following screen shown below.
*Edit** you do not need to wait for the PASS sign anymore. Once you see the handset screen change to the picture below, close Odin with the red ‘X’ window button, disconnect your USB cable and continue.
2.4 If you are new to use ClockworkMod recovery manager then before doing anything, please have a look at next screen to learn the navigation keys.
2.5 First we have to wipe our old DATA which is not compatible with ClockworkMod. Wiping old DATA is necessary if you are installing for the first time.
- Press BACK (H/W) button on phone and follow next screen.
- Press BACK (H/W) button on phone and follow next screen.
- Press BACK (H/W) button on phone and follow next screen.
- Press BACK (H/W) button on phone and follow next screen.
2.5 Now it’s time for the ROM installation.
Important Note:
• You MUST install the three files in this exact order:
• The main ROM package ‘update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip’
• The hotfix package ‘v1.7.2-hotfix1.zip’
• The Google Apps package ‘gapps-gb-20110828-signed.zip’
- Select to ‘Choose file from SD card’ that you have saved earlier.
Both file should be in ZIP format only. Don’t extract, keep it in ZIP format and store it on SD card.
2.6 Once you are done with installation of these files. Press the BACK button until you return to the first screen shown below. Go to the first option and do reboot.
2.7 On next start-up, you will see CyanogenMod 7 Logo and system will load in few mins. Enjoy your new phone software!
We hope you all get successful installations of ClockworkMod 7 ROM’s
Written by Phillip Thorne – A.K.A sparkyuiop
Nice summary, thanks. Can I add a couple of points? Do not use CWM v6, it just times out when flashing with Odin. If you want to flash a new UK baseband you can download the latest one (I5500XWJP4) here http://www.multiupload.com/81IBI2MD0X - the one listed on the baseband page does not work.
Baseband and unlocking?
dwl99 said:
If you want to flash a new UK baseband you can download the latest one ...
Click to expand...
Click to collapse
What does flashing the baseband achieve? I assume this will not unlock the phone?
I would also like to add that once people have loaded this ROM onto their Samsung G5 there are many safe ways to extract the 8 digit passcode number to unlock the phone to any network.
I had previously used Jc_master method to extract the passcode which worked on the first one and second one that I did but for some reason the second one failed to reboot after and became bricked. (This was done prior to flashing a non-samsung ROM on both phones and I believe it will not work on the Cyanogen ROM)
This method looks good but I have not yet tried it: method
sparkyuiop said:
What does flashing the baseband achieve? I assume this will not unlock the phone?
I would also like to add that once people have loaded this ROM onto their Samsung G5 there are many safe ways to extract the 8 digit passcode number to unlock the phone to any network.
I had previously used Jc_master method to extract the passcode which worked on the first one and second one that I did but for some reason the second one failed to reboot after and became bricked. (This was done prior to flashing a non-samsung ROM on both phones and I believe it will not work on the Cyanogen ROM)
This method looks good but I have not yet tried it: method
Click to expand...
Click to collapse
Flashing a new baseband ensures that the GPS & phone will continue to work. Although you might want to do it only if anything doesn't work after you flash the ROM.
It isn't working, it will not detect the ops file despite my downloading it to C:/Samsung. Any advice?
Update:
I removed the .txt from the ops filename, now its working
Rad, clear and concise.
Cheers!
gwildor said:
Rad, clear and concise.
Cheers!
Click to expand...
Click to collapse
Thank You. I'm no expert at this so I'm pretty chuffed it's working out for people.
Tactics119 said:
It isn't working, it will not detect the ops file despite my downloading it to C:/Samsung. Any advice?
Update:
I removed the .txt from the ops filename, now its working
Click to expand...
Click to collapse
The OPS file should not be a text (.txt) extension (as you found out). One way to check it has the correct extension is to do this:
Open 'Computer' or 'My Computer'
At the top of the page click 'Organize' or 'View'
Select 'Folder and search options' or 'View'
Move the radio dot from 'Don't show hidden files, folders and drives' to 'Show hidden files, folders and drives'
Click 'Apply' then 'OK'
Go back to your OPS file and read it
Your OPS should read like this: EUROPA_v1.0.ops
If it reads: EUROPA_v1.0.ops.txt or EUROPA_v1.0.txt edit it so it looks like how it should read.
Clockwork Mod isn't a bootloader, it's a recovery!
Sent from my GT-I5500 using Tapatalk
It would be useful for someone, maybe, to update this good how-to, wouldn't it?
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
brainvision said:
It would be useful for someone, maybe, to update this good how-to, wouldn't it?
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
Click to expand...
Click to collapse
Hey man don't steal me thunder! LOL, that's fine with me!
followed all the instructions and the phone just says android in white writing then goes to the samsung screen and back again?
in a cycle?
anyone help me im desparate!
thanks
edit after a few attempts i use odin to flash again and get into clock work.........
anyone please please !!!1 its my wifes phone and shes going mad!
managed to get it back by flashing I5500XXJED_Android_2.1 with odin............
does this help and why i cant flash cynogen or any other rom?
Gavin01 said:
followed all the instructions and the phone just says android in white writing then goes to the samsung screen and back again?
in a cycle?
anyone help me im desparate!
thanks
edit after a few attempts i use odin to flash again and get into clock work.........
anyone please please !!!1 its my wifes phone and shes going mad!
managed to get it back by flashing I5500XXJED_Android_2.1 with odin............
does this help and why i cant flash cynogen or any other rom?
Click to expand...
Click to collapse
Yes I am getting same screen after following installtion steps here, Please help..
anishmathw said:
Yes I am getting same screen after following installtion steps here, Please help..
Click to expand...
Click to collapse
did you wipe the phone with ClockworkMod?
Is it me or dose the installing of the samsung usb drivers take a long time to install( about 1 hour)...??
---------- Post added at 10:32 PM ---------- Previous post was at 09:47 PM ----------
Thanks for this...worked perfect,I now have ClockworkMod 7 on my Samsung Galaxy 5 (Europa) phone... 5 stars..
anishmathw said:
Yes I am getting same screen after following installtion steps here, Please help..
Click to expand...
Click to collapse
Gavin01 said:
followed all the instructions and the phone just says android in white writing then goes to the samsung screen and back again?
in a cycle?
anyone help me im desparate!
thanks
edit after a few attempts i use odin to flash again and get into clock work.........
anyone please please !!!1 its my wifes phone and shes going mad!
managed to get it back by flashing I5500XXJED_Android_2.1 with odin............
does this help and why i cant flash cynogen or any other rom?
Click to expand...
Click to collapse
brainvision said:
did you wipe the phone with ClockworkMod?
Click to expand...
Click to collapse
i have having the same issues as well... flash CWM with odin, boots fine into CWM, flash CM7 and gapps, and just get the white android writing
i did the following steps:
1. flash CWM with odin
2. in recovery, wiped data, wiped cache, wiped dalvik, wiped battery stats
3. flashed CM7 and gapps
4. just for good measures i wipe cache and dalvik
4. reboot
doing that gets me into boot loop, just keeps giving me the white android writing over and over again.
(off topic here a bit)
tried to go back to stock with odin and still have bootloop with samsung writing on the screen.... so far the phones a brick... cannot get it to boot into any ROM at all
Just let you know that on my phone the camera is not working properly,when recording it shudders and if you switch back to photo mode it crashes.
---------- Post added at 05:43 PM ---------- Previous post was at 05:04 PM ----------
c_86 said:
i have having the same issues as well... flash CWM with odin, boots fine into CWM, flash CM7 and gapps, and just get the white android writing
i did the following steps:
1. flash CWM with odin
2. in recovery, wiped data, wiped cache, wiped dalvik, wiped battery stats
3. flashed CM7 and gapps
4. just for good measures i wipe cache and dalvik
4. reboot
doing that gets me into boot loop, just keeps giving me the white android writing over and over again.
(off topic here a bit)
tried to go back to stock with odin and still have bootloop with samsung writing on the screen.... so far the phones a brick... cannot get it to boot into any ROM at all
Click to expand...
Click to collapse
I have put this rom on my phone twice now and it sounds like you are doing it wrong and missing the file "v1.7.2-hotfix1.zip"..
This is how i did it..
Started odin
This is how mine looks..
Remember to copy update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip,v1.7.2-hotfix1.zip,gapps-gb-20110828-signed.zip to your sd card,If you can't via phone use your card reader on your pc.
But all mine files are in the Samsung folder,so..
OPS - C:\Samsung\EUROPA_I5500_v1.0.ops
One Package - C:\Samsung\ClockworkMod-Galaxy5-v0.5.tar(ClockworkMod recovery manager)
Make sure everything is left ticked when starting odin just make sure one package is ticked..
switch phone off and plug in usb cable in phone(make sure you have installed the usb drivers,once in download mode you will see them installing wait for them to finish installing.)
Download mode - hold vol - down then middle button then off/on button and wait for download mode pic to come up.
you will see COM3 go orange in odin,press start and it will download ClockworkMod recovery manager to your phone and boot it..
Now wipe - data/Factory reset - yes
Now wipe - cache partition - yes
Now wipe - advanced - Dalvik cache - yes - back - Battery Stats - yes
You MUST install the three files in this exact order:
The main ROM package ‘update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip’
The hotfix package ‘v1.7.2-hotfix1.zip’
The Google Apps package ‘gapps-gb-20110828-signed.zip’
all files should be in ZIP format only. Don’t extract, keep it in ZIP format and store it on SD card.
on phone - ClockworkMod recovery manager - install zip from cdcard - choose zip from sdcard - click on each file and install it in order,once you have done that restart your phone and your done..
Well that how I did it and it worked every time..
Good luck..
P.S If anyone wants to show a video on how to do it let me know.
Video here.. http://www.youtube.com/watch?v=dYmTps4tdwU
Looks like I bricked it...help please.
Tried this today and only got as far as attempting to install ClockworkMod. ODIN went to downloading recovery image and then hung there. Over an hour there. So I disconnected...now my phone is ummm...not working. Any ideas?
Benglian said:
Tried this today and only got as far as attempting to install ClockworkMod. ODIN went to downloading recovery image and then hung there. Over an hour there. So I disconnected...now my phone is ummm...not working. Any ideas?
Click to expand...
Click to collapse
It's obvious that it doesn't work anymore for now: I presume it shows up an interrupted link between the phone and PC..
So remove the battery, restart the PC and do it again.. maybe you miss the USB Samsung driver: try to reinstall them.. and use the 0.5 or 0.7 tar file for now
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
brainvision said:
It's obvious that it doesn't work anymore for now: I presume it shows up an interrupted link between the phone and PC..
So remove the battery, restart the PC and do it again.. maybe you miss the USB Samsung driver: try to reinstall them.. and use the 0.5 or 0.7 tar file for now
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
Click to expand...
Click to collapse
Just the 0.7 tar,

TF201 Big Time Noob in waaay over his head

The Good:
I used the unlocker, and installed clockworkmod from fastboot.
The Bad:
Mistake 1: I was not logged into a google account when I used the unlocker. When the device boots, it says that it is unlocked in the top left, but I can't shake the feeling that it was not done correctly,
Mistake 2: I did not make a backup. I was coming off a factory reset, and figured I had no app data to protect, so why do a backup? I followed some instructions I found on the net, did some cmd: commands on my computer, and BAM: Clockwork Mod.
Mistake 3: When I could not get a rom to load in CWM, (would not detect update.zip), I started looking for fixes all over. Root Checker said I was not rooted. I tried using an APK to root that I found in a forum, that did not work either. The exploit involving using an app backup did not go through for me.
Mistake 4: In an attempt to get rid of Mistake 1, I thought "why not do a factory data reset?". Now, my Transformer prime only boots into CWM. I am sitting here looking at v5.8.2.0.
Any time I select "reboot system now", I end up back here.
I realize that as a total noob, I do not deserve the kindness of this forum, however, any mercy/help that you give me will give you several karma points.
Please help.
Any links you can provide will not just help me, but any additional noobs that are dumb enough to do what I did.
Mistake 1: google account has nothing to do with unlocking. If you have fastboot access you're unlocked! so forget mistake 1 and 4
Mistake 2: no comment except that i don't understand what instructions you followed from the net, the cmd part... A backup is performed within CWM ... Nevertheless you're bricked so it isn't very important.
Mistake 3: a big mess in your head. If you just unlocked and flashed cwm it's logical that you are not rooted in your ROM. CWM has nothing to do or care with root !! CWM is totally independant from the ROM, it has by default root power as it runs froms a different partition and deals with /system and /data etc from 'outside'.
You gain root by either flashing a custom ROM (they are all rooted) or flashing the super user itself only (SU.zip).
Mistake 4: don't use cwm on that device.
Mistake 5: you are a monkey typer.... STOP trying every crap you find 'on the net' ! You seem to have quite blurred knowledge of what is an android device, so be extremelly carefull or you'll end with a real hard bricked prime.
Prime is very specific, don't use things that have not been designed specifically for it.
You are in recovery bootloop, see in dev section the unbrick thread (in stickies threads), option 1a.
Don't use cwm.
Use TWRP.
big time noob said:
The Good:
I used the unlocker, and installed clockworkmod from fastboot.
The Bad:
Mistake 1: I was not logged into a google account when I used the unlocker. When the device boots, it says that it is unlocked in the top left, but I can't shake the feeling that it was not done correctly,
Mistake 2: I did not make a backup. I was coming off a factory reset, and figured I had no app data to protect, so why do a backup? I followed some instructions I found on the net, did some cmd: commands on my computer, and BAM: Clockwork Mod.
Mistake 3: When I could not get a rom to load in CWM, (would not detect update.zip), I started looking for fixes all over. Root Checker said I was not rooted. I tried using an APK to root that I found in a forum, that did not work either. The exploit involving using an app backup did not go through for me.
Mistake 4: In an attempt to get rid of Mistake 1, I thought "why not do a factory data reset?". Now, my Transformer prime only boots into CWM. I am sitting here looking at v5.8.2.0.
Any time I select "reboot system now", I end up back here.
I realize that as a total noob, I do not deserve the kindness of this forum, however, any mercy/help that you give me will give you several karma points.
Please help.
Any links you can provide will not just help me, but any additional noobs that are dumb enough to do what I did.
Click to expand...
Click to collapse
Okay so you messed up... slightly... no big deal... here is what you do..
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
blackbean found here... http://rootzwiki.com/index.php?/topi...ackbean-(8-15)
eos found here.. http://forum.xda-developers.com/showthread.php?t=1782413
Download and install http://forum.xda-developers.com/showthread.php?t=1426502 naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here http://androidroot.mobi/?p=452
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
Now there is a chance this does not work.. don't worry... if it doesn't work .. go here ....http://forum.xda-developers.com/showthread.php?t=1615990 this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions... http://forum.xda-developers.com/showthread.php?t=1774352
start again from ******now boot to recovery....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Yes it does seem like a lot... but unless you want to sell me a paper weight for $5 you need to complete this... if you need further assistance write here or pm me..... good luck Luke... may the force be with you...
A helpfull answer without trolling? really.. Whats this world coming to!!
anyway.. I added a "thank you" even though I didnt brick my prime ( yet )
johanjonker said:
A helpfull answer without trolling? really.. Whats this world coming to!!
anyway.. I added a "thank you" even though I didnt brick my prime ( yet )
Click to expand...
Click to collapse
Your welcome ... I think.... did I get you out of a jam?
I dont troll I try to help people from what i have experienced..... I myself have made some questionable decisions.... just figure since I have learned from them .. no reason to make others suffer through needless anxiety......
big time noob said:
The Good:
Mistake 3: When I could not get a rom to load in CWM, (would not detect update.zip), I started looking for fixes all over. Root Checker said I was not rooted. I tried using an APK to root that I found in a forum, that did not work either. The exploit involving using an app backup did not go through for me.
Click to expand...
Click to collapse
The others already answered everything else, but here I'm wondering if it's not just a simple mistake.
If I remember correctly, there are 2 options in CMW to flash a zip file : either an update.zip file which has to be in a specific directory, or choose the file from the storage.
My guess is that you tried the first option which returned an error because you don't have an update.zip file.
Have you tried browsing to the ROM file manually?
Besides that, you might want to setup NVFlash on your device (be sure to ask for help in the NVFlash thread if you have any doubt about one of the steps, so you don't end up with a brick).
The NVFlash thread is here : http://forum.xda-developers.com/showthread.php?t=1774352
Since you don't seem to understand Android very well, having NVFlash would at least protect you from most (if not all) software bricks in case you make a bigger mistake like flash an Official Asus ROM on your unlocked device..
Hopefully this will help.
Mithrandir007 said:
The others already answered everything else, but here I'm wondering if it's not just a simple mistake.
If I remember correctly, there are 2 options in CMW to flash a zip file : either an update.zip file which has to be in a specific directory, or choose the file from the storage.
My guess is that you tried the first option which returned an error because you don't have an update.zip file.
Have you tried browsing to the ROM file manually?
Besides that, you might want to setup NVFlash on your device (be sure to ask for help in the NVFlash thread if you have any doubt about one of the steps, so you don't end up with a brick).
The NVFlash thread is here : http://forum.xda-developers.com/showthread.php?t=1774352
Since you don't seem to understand Android very well, having NVFlash would at least protect you from most (if not all) software bricks in case you make a bigger mistake like flash an Official Asus ROM on your unlocked device..
Hopefully this will help.
Click to expand...
Click to collapse
Very valid point Mithrandir007.... just to be cleear when following the nvflash instructions.... follow step by step.... all the way to the end..... from this thread http://androidroot.mobi/t3_nvflash/ dont stop until you see the statement ... coming soon... then you are actually done....
Thanks
Thank you guys for your help, and not being too hard on me...except maybe the first guy.
I will try those things when I get back from work.
Seriously...
Gage_Hero said:
Okay so you messed up... slightly... no big deal... here is what you do..
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
Download and install naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
Now there is a chance this does not work.. don't worry... if it doesn't work .. go here .... this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions...
start again from ******now boot to recovery....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Yes it does seem like a lot... but unless you want to sell me a paper weight for $5 you need to complete this... if you need further assistance write here or pm me..... good luck Luke... may the force be with you...
Click to expand...
Click to collapse
I ask this next question with a scared expression on my face...what if the TF201 is not taking a charge now?
Last night it would boot into clockworkmod, and I did not plug it in, so it just sat there burning battery in clockworkmod screen.
Today, I go to plug it into the usb, and I briefly get the screen that shows the battery in the red, then it fades out.
I am going to try plugging it into the wall when I get home, but I am scared that I might not get the chance to fix my device.
It comes vaguely in my mind that I read something about cwm not supporting charging but I'm not sure.
If the battery is drained completely it will need several minutes with wall charger to come back to life.
You are really messed up. Download a Rom from development section.. put it in your Sdcard.
First plug your phone to charger.. let it charge for an hour.
When your mobile switches ON.
Enter CWM recovery or anyone you have.. go to mount option, wipe everything except sdcard. Go to advance and wipe dalvik cache.. then go to Install zip from sdcard option in it.. select the downloaded file.
big time noob said:
I ask this next question with a scared expression on my face...what if the TF201 is not taking a charge now?
Last night it would boot into clockworkmod, and I did not plug it in, so it just sat there burning battery in clockworkmod screen.
Today, I go to plug it into the usb, and I briefly get the screen that shows the battery in the red, then it fades out.
I am going to try plugging it into the wall when I get home, but I am scared that I might not get the chance to fix my device.
Click to expand...
Click to collapse
Some usb connections don't charge... my pc at work is like that.... or they charge so little that it barely makes a difference. Plug it into the wall for at least a hour... preferably longer since you are going to be doing things that may not work out so well if the battery dies in the middle of things.... Also given how frail the charger socket is, unless you have it sitting on a flat surface, I wouldn't attempt doing the work while it is plugged in... Would want you to get the software fixed and you bust up the charging socket or cable...
Prime needs 15 volts to charge, USB only delivers 5, so it's discharging while plugged to an USB most of the time.
Don't know how to fix your CWM problem but I do know the Prime will charge on a USB port if it's turned off. It does take a very long time though.
From the TF201 manual:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Might help
Mithrandir007 said:
The others already answered everything else, but here I'm wondering if it's not just a simple mistake.
If I remember correctly, there are 2 options in CMW to flash a zip file : either an update.zip file which has to be in a specific directory, or choose the file from the storage.
My guess is that you tried the first option which returned an error because you don't have an update.zip file.
Have you tried browsing to the ROM file manually?
Besides that, you might want to setup NVFlash on your device (be sure to ask for help in the NVFlash thread if you have any doubt about one of the steps, so you don't end up with a brick).
The NVFlash thread is here : http://forum.xda-developers.com/showthread.php?t=1774352
Since you don't seem to understand Android very well, having NVFlash would at least protect you from most (if not all) software bricks in case you make a bigger mistake like flash an Official Asus ROM on your unlocked device..
Hopefully this will help.
Click to expand...
Click to collapse
Thanks for the response. On the nvflash page it says NOTE: THIS REQUIRES A NON-BRICKED AND UNLOCKED DEVICE. IT WON'T WORK ON ALREADY BRICKED DEVICES
Does that mean me? If so, I might be stuck.
I tried installing with the update.zip option, didn't work. I also tried installing by browsing, but weirdly, it does not give me the options of any of the roms I have on the SD card...when the prime was stock, it saw the files on the SD card, but now it just shows me options of several folders that do not actually exist, a couple of subfolders, but no actual files or zip files.
When I boot (holding the power and down volume button) The message basically says, The device is unlocked, Android cardhu-user bootloader. Says something about the version I was running, .28, and that it is looking for an ota update. At the bottom, it says booting recovery kernel image. Then it loads clockworkmod.
I installed the naked drivers, so I can now see the Android ADB interface on my windows device manager. I cannot see the device as one of the drives from windows explorer.
I hope that info helps. What do you think? How screwed am I still?
rr0yy said:
You are really messed up. Download a Rom from development section.. put it in your Sdcard.
First plug your phone to charger.. let it charge for an hour.
When your mobile switches ON.
Enter CWM recovery or anyone you have.. go to mount option, wipe everything except sdcard. Go to advance and wipe dalvik cache.. then go to Install zip from sdcard option in it.. select the downloaded file.
Click to expand...
Click to collapse
The options I get there are:
format system
format cache
format staging
format data
Which one do I pick? All of them?
big time noob said:
The options I get there are:
format system
format cache
format staging
format data
Which one do I pick? All of them?
Click to expand...
Click to collapse
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
big time noob said:
The options I get there are:
format system
format cache
format staging
format data
Which one do I pick? All of them?
Click to expand...
Click to collapse
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
The image is from 5.5 but it says install zip from sdcard... if you adb push the rom there you will be able to install...
Gage_Hero said:
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
The image is from 5.5 but it says install zip from sdcard... if you adb push the rom there you will be able to install...
Click to expand...
Click to collapse
2 things:
1. I cannot see the sd card in the mount/unmount area of CWM. I feel like this is a big part of my problem.
2. The instructions I see for nvflash involve fastboot. I could be wrong, but if I cannot get to the fastboot screen on my prime, how can I run the fastboot command lines? I can only get to the cwm screens.
Gage_Hero said:
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
The image is from 5.5 but it says install zip from sdcard... if you adb push the rom there you will be able to install...
Click to expand...
Click to collapse
Attached 2.1.2 twrp....give it a go....

[TUTURIAL] BIGINNERS GUIDE TO EXTRACT FTF FILES[ics]

Complete method to extract system files from ftf files of xperia devices for ics​​​
(For gb u can use nero young method which is simple, but for ics u will get system files from ftf by this method (for windows)u will not get extracted folder by nero young method )​
whom is this tutorial for?
Click to expand...
Click to collapse
For those who need exact system files from FTF of SONY XPERIA smart phone ​
Click to expand...
Click to collapse
TOOLS NEEDED
Flash tool for xperia devices (use flash tool version v 0.9.0.0 get it from here:http://androxyde.github.com/)
unyaffs tool (get it from here : http://www.mediafire.com/?h631v46n8v6efe3 )
Click to expand...
Click to collapse
METHOD :
step 1:
Open the ftf file using winrar
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
step 2:
Extract which ever file u need (in this case i need system folder so i extracted system.sin )
step 3:
Open flash tool and click advanced option and then click sin editor
step 4:
Go to system.sin file from where u had extracted and open file
step 5:
Click dump data option
Wait for it to finish the process
step 6:
After finishing the process u will get two files in the folder where u r having original system.sin (one will be system.partinfo and other will be system.yaffs2 ) so tht u get yaffs2 file continue with the next step
Click to expand...
Click to collapse
step 7:
Download unyaffs tool from the link provided first and extract unyaffs.exe and cygin1.dll to c drive of ur system by making a folder named "unyaffs"
Click to expand...
Click to collapse
step 8:
Go to the folder where u get system.yaffs2 ( the file we get though the flash tool process) and copy the file
step 9:
Paste it to the unyaffs folder in "c"
step 10:
While u are in unyaffs folder press shift + right mouse button then only u will get "open command window here option", click that.... Other wise u can go to this folder using usual command method
step 11:
U will get command window inside unyaffs folder
step 12:
U should type inside the command window "unyaffs.exe system.yaffs2" (app name)(space)(name of the file u need to extract, if u need to extract kernel use tht file name here) and then press enter
step 13:
Wait for some time " until u see end of image " and u can see the extracted folders appearing in the unyaffs folder
through this method u can get any .sin file inside ur ftf
thankyou for reading my tutorial
DONT FORGET TO PRESS THANKS IF I HAD HELPED U ​
Click to expand...
Click to collapse
Super Thanks Bro
This tutorial is Very Helpful and Should Be Pinned
Copying files from phone to PC was Killing Me
Okay, i have a serious question
First of all, yes i have read in TONS of articles, blogs, and many forums about the problem i have, and it could be useful for everyone if we get sorted out.
See, my phone has locked bootloader. even if i unlock it with s1tool, it wont enter fastboot mode (because fastboot mode is disabled, and no one knows how to enable it apart from paying someone with stool or omnius. and YES, I DID THE PROCEDURE PRESSING THE CORRECT BUTTON AND EVERYTHING, IT'S NOT ABOUT ME NOT KNOWING HOW TO FASTBOOT). so, even if i unlock my bootloader, i cannot flash kernels because i can't enter fastboot mode.
BUT!
My phone is rooted, which means I can flash roms and practically anything that's not a kernel through recovery mode (x-parts) in zip files, right? So, here's my question:
What if I extract the contents of the kernel IMG file, and then make a flashable zip file out of it? Would it work to flash my kernel? I would have tried it before asking, believe me, but I do not know how to extract a IMG kernel file
Thanks in advance
juhn777 said:
What if I extract the contents of the kernel IMG file, and then make a flashable zip file out of it? Would it work to flash my kernel? I would have tried it before asking, believe me, but I do not know how to extract a IMG kernel file
Thanks in advance
Click to expand...
Click to collapse
Whether it works or not ,IDK ,You should Ask some Dev whom works with Kernels ,I guess there's a reason why in sony devices we Always use .img files instead of .zip when it comes to kernels
Anyway
to Extract IMG Files You can try The following programs (Windows)
Alcohol 120% , UltraISO , Nero
you don't have to buy anything ,you can work it out with trial :good:
juhn777 said:
Okay, i have a serious question
First of all, yi have read in TONS of articles, blogs, and many forums about the problem i have, and it could be useful for everyone if we get sorted out.
See, my phone has locked bootloader. even if i unlock it with s1tool, it wont enter fastboot mode (because fastboot mode is disabled, and no one knows how to enable it apart from paying someone with stool or omnius. and YES, I DID THE PROCEDURE PRESSING THE CORRECT BUTTON AND EVERYTHING, IT'S NOT ABOUT ME NOT KNOWING HOW TO FASTBOOT). so, even if i unlock my bootloader, i cannot flash kernels because i can't enter fastboot mode.
BUT!
My phone is rooted, which means I can flash roms and practically anything that's not a kernel through recovery mode (x-parts) in zip files, right? So, here's my question:
What if I extract the contents of the kernel IMG file, and then make a flashable zip file out of it? Would it work to flash my kernel? I would have tried it before asking, believe me, but I do not know how to extract a IMG kernel file
Thanks in advance
Click to expand...
Click to collapse
hey bro check whtr ur bootloader is unlocked with the unofficial bootloader unlocking SE tool..
roninnbaby said:
hey bro check whtr ur bootloader is unlocked with the unofficial bootloader unlocking SE tool..
Click to expand...
Click to collapse
man, i did verify if my bootloader was unlocked through both s1tool and flashtool, both tell me i have unlocked bootloader (give me a code like r384u28 instead of R384u28) so yes I HAVE UNLOCKED BOOTLOADER, but can't enter fastboot anyway :crying: for ****s sake
i would pay for it to be unlocked, really, but i live in Chile and no one knows **** about anything around here. if anyone could do it for me, i could make a bank transfer or something since i don't (and can't) have a business card or something like that (because of the ****ty laws around here, requiring people to win lots of money before getting a credit card or stuff like that).
anyone knows what can i do? ):
Thanks man.
Working like charm!.
juhn777 said:
man, i did verify if my bootloader was unlocked through both s1tool and flashtool, both tell me i have unlocked bootloader (give me a code like r384u28 instead of R384u28) so yes I HAVE UNLOCKED BOOTLOADER, but can't enter fastboot anyway :crying: for ****s sake
i would pay for it to be unlocked, really, but i live in Chile and no one knows **** about anything around here. if anyone could do it for me, i could make a bank transfer or something since i don't (and can't) have a business card or something like that (because of the ****ty laws around here, requiring people to win lots of money before getting a credit card or stuff like that).
anyone knows what can i do? ):
Click to expand...
Click to collapse
ho did u tried to enter to fast boot???
roninnbaby said:
ho did u tried to enter to fast boot???
Click to expand...
Click to collapse
i stated in a previous post that i did the correct procedure to enter fastboot, so again, here's what i do/did:
-before everything, i installed busybox, correct fastboot drivers, correct phone drivers, proper adb drivers, etc
-flashed some roms with both flashtool and cwm, so my cable is not the problem, neither is my cellphone hardware since i can flash stuff
-many, many times, and in many, many different ways i turned off my phone, pressed the menu key and without letting go the menu key i connected the usb cable (also tried vol up, vol down, home key, etc)
-never heard any "connected hardware" sound from windows
-never got the blue light for more than 2 sec, then it started charging the phone instead, with green light
so yes, I DO KNOW THE PROCEDURE, really, i'm not that noob you know, been trying this for months actually
that's the problem, because i've tried everything and nothing seems to work, so looks like i gotta pay someone with wotan server, se tool 2, omnius or something like that, but here in chile there is NO ONE, and i really mean NO ONE who knows even what those programs do
and here i come to you my dear friends... thanks to all who try to help me
juhn777 said:
i stated in a previous post that i did the correct procedure to enter fastboot, so again, here's what i do/did:
-before everything, i installed busybox, correct fastboot drivers, correct phone drivers, proper adb drivers, etc
-flashed some roms with both flashtool and cwm, so my cable is not the problem, neither is my cellphone hardware since i can flash stuff
-many, many times, and in many, many different ways i turned off my phone, pressed the menu key and without letting go the menu key i connected the usb cable (also tried vol up, vol down, home key, etc)
-never heard any "connected hardware" sound from windows
-never got the blue light for more than 2 sec, then it started charging the phone instead, with green light
so yes, I DO KNOW THE PROCEDURE, really, i'm not that noob you know, been trying this for months actually
that's the problem, because i've tried everything and nothing seems to work, so looks like i gotta pay someone with wotan server, se tool 2, omnius or something like that, but here in chile there is NO ONE, and i really mean NO ONE who knows even what those programs do
and here i come to you my dear friends... thanks to all who try to help me
Click to expand...
Click to collapse
hey dont be angry...i try to help u only ... so be patient... otherwise none in this forum will help u... because no one is having responsiblity to serve u ,,,... ok...
actually the problem is with ur bootloader...i think so ...we cant give u a complete help until u give correct answers for wht they ask...trial and error method is only one possible in this field...u try to unlock the bootloader via official tool once more and check whtr ur both "r" is in small letters...
yes, sorry... i didn't mean to be rude, i was just clarifying it's not the common problem every noob has, it's something more than that
i cannot unlock via the official way (sony site, right?) because my phone says "unlock bootloader allowed: no", so it won't let me (won't enter fastboot anyways)
keep on getting the error broken image file...
emwno said:
keep on getting the error broken image file...
Click to expand...
Click to collapse
use flash tool version 0.9.0.0 or 0.9.6...
roninnbaby said:
use flash tool version 0.9.0.0 or 0.9.6...
Click to expand...
Click to collapse
I got 9.4. Downloading 9.6
How to rebuild it back?
pls help me
thanks
12793080 said:
How to rebuild it back?
pls help me
thanks
Click to expand...
Click to collapse
if u are in a starting phase u need to setup android kitchen and u can customize ur rom... u need more reading
12793080 said:
How to rebuild it back?
pls help me
thanks
Click to expand...
Click to collapse
rebuilding back to ftf is not possible usually they are cooked by the developers and ziped file by signing it so tht u can flash through CWM recovery
if u know any other way than this please post the link to this thread so tht it will help in future
I think this thread should be in Xperia threads as a sticky since ftf files r more or less found only in Xperia line up...
Sent from my ST25i using xda premium
Hey man thanks for tut. Im using flashtool 9.8 and i dont need yaffs2 extractor you can extract yaffs2 files with flashtool too (Tools>Extractors>Yaffs2)

[HOW TO] Unlock bootloader, Root, Flash Custom ROM, Flash Kernel

Post 1: How to unlock your bootloader, flash a recovery and root
Post 2: How to flash a custom ROM and kernel (boot.img)
Post 3: How to reverse everything and go back to stock
Post 4: How to ADB Sideload a ROM
Alright. This is for everyone who wants to root their phone. I've seen MULTIPLE threads of the same question "Can I root my phone and How do I do it". So I hope I never have to see it again! In this tutorial, I use use my toolkit as the way to root. Doing it manually takes forever and that is why I made my toolkit.
Requirements:
HTC One X+ (charged to at least 70%)
Windows XP,Vista,7 (8 is not officially supported since I don't have the drivers)
USB cable
Ability to read and follow step-by-step
Understanding that I am no way guaranteeing anything. If you screw up your phone, you probably didn't follow my steps and made a foolish mistake.
Let's begin.
Download my toolkit from here.
Link 1 and Link 2
Extract the FOLDER to your C: drive or to your desktop.
MAKE SURE YOUR DIRECTORY DOES NOT HAVE A PERIOD OR SPACE.
Open One X.exe
So now you have my program open. Great.
On your phone, go to Settings -> Developer Options and Enable USB Debugging.
From my toolkit, Click 1. Install HTC Drivers.
After the drivers install, restart your computer.
After your computer loads up, open my toolkit and connect your phone to the computer. Your phone should now be recognized.
Now, click 2. Register at HTCDev. Register with a VALID email address and LEAVE the web browser open.
Now, under the commands section of my toolkit, press Boot into Bootloader.
You should have a nice, white, shiny screen that says FASTBOOT USB.
Click 3. Get Token ID. Look at the pop up and it will tell you how to get the Token ID.
Highlight where it says < < < < Identifier Token Start > > > > all the way to < < < < < Identifier Token End > > > > > and right click and it will automatically copy it.
Now, click Submit Token ID. Your web browser should now open a new tab. Scroll down and in the empty box, paste your Token ID. Press submit. HTCDev now emailed you your unlock token.
Your phone should still be in the bootloader. Now, go to the email address you registered to HTCDev and DOWNLOAD your unlock_code.bin. Press 5. Unlock Bootloader. Locate your unlock_code.bin and it will flash it to your phone.
READ the warning. THIS WILL WIPE ALL YOUR DATA FROM THE PHONE.
When you agree to it, press the volume up button and press the power button to accept it. Your phone will now restart.
When your phone loads up, go through the set up wizard. Then, on your phone, go to Settings -> Developer Options and Enable USB Debugging.
Under the Extras section, press Perm Root. It will push SuperSU.zip to your phone.
Under commands, press Boot into Bootloader once again.
Now, it is time to flash a recovery. The custom recovery is for 2 different devices
TWRP (Team Win Recovery Project) is a custom recovery that will allow you to flash custom ROMs, Mods, etc.
If your phone is from AT&T or Telus, then flash the one that says TWRP ATT/Telus.
If your phone is NOT from AT&T or Telus, then flash the one that says TWRP International.
After it flashes, remove the USB cable and have HBOOT selected in bootloader. Press the power button and it will reload to another screen. Press the Volume Down button until you get to Recovery. Press the power button to select it.
Go to Backup and back up your boot and system partition. Always have a back up before you flash or do anything.
After that, go to Install and locate SuperSU.zip. Click it and slide the screen on the bottom to flash it. After it flashes, reboot the phone.
In your app drawer (your menu with all the apps), open SuperSU. If it says the binary needs to be updated, then update it. If it doesn't, then you are fully rooted!
Post 2: How to flash a custom ROM and kernel (boot.img)
The fun part! Now, I will teach you how to flash a ROM and boot.img
Find a ROM you like, the first thing you should do is make sure it is COMPATIBLE with your phone. If you find a ROM that is for AT&T and you have the International model, don't be an idiot and flash it. I will not help you with that since you already agreed to my warning from the first post.
AT&T and Telus ROMs are compatible with each other.
International models won't work on an AT&T/Telus HOX+ and Vice Versa.
Also, DO NOT ASK IF YOU CAN FLASH A ROM FROM ANOTHER DEVICE!
Will it work? NO! Will it ever work? NO! Can I flash it anyways? Brick your device, I don't care. I warned you.
Let's get back on task. So you found the ROM you want to try, so go ahead and download it. KEEP THE THREAD OPEN! MAKE SURE YOU READ EVERYTHING AND REREAD IT AGAIN! READ WHAT USERS SAID ABOUT IT AND ABOUT BUGS! GO AHEAD AND READ THE WHOLE ENTIRE THREAD! GAIN KNOWLEDGE!!
Connect your USB cable to your phone. View the folders on your phone. I like to make a folder called ROMs on my phone and transfer it in there.
After you transfer it, open my toolkit and press Boot into Recovery. When you are in TWRP, MAKE A BACKUP!!!
After you make a backup AKA a Nandroid, click Wipe. Wipe Cache, Dalvik, Factory Reset and System. NOTHING ELSE! If you click anything else, IT WILL WIPE YOUR SD CARD AND YOU WILL HAVE MORE ISSUES ON YOUR HEAD!
So you wiped everything. Great. Your phone is ROMless, Yay!
Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it.
After it flashes, press reboot from the phone.
Congrats! Enjoy your fully working or borked ROM! Remember, DO NOT ASK FOR ETAs, DO NOT BUG/PM A DEV ABOUT UPDATES, and BE RESPECTFUL TO THE DEVELOPERS!
Post 3: How to reverse everything and go back to stock
Now, let's talk about getting back to stock. There are 2 ways to do this.
1. Flash the stock RUU (If available) (Recommended)
2. Restore your Nandroid (backup that I told you to make earlier)
1. I'll talk about flashing the stock RUU first.
Open up my toolkit and press "Factory RUU" from the links sections. I usually have the most updated RUUs that Football releases on my Dev-Host account. Download the correct RUU for your phone.
Now, back up all your data (pictures, contacts, etc) since this will put your phone back to complete stock.
Connect the USB cable to your phone. Press Boot into Bootloader.
It should now say FASTBOOT USB on your screen.
Press Relock bootloader. It may give you a security warning error or it may say failed. Who cares, ignore it. It's normal.
Your phone will boot up normally.
When the phone is fully loaded. Unplug and replug the USB cable back in the phone. Now,run the RUU you downloaded and follow the instructions.
Your phone will be back to stock.
2. Now, we will talk about restoring your nandroid backup.
Connect your phone to the computer. Open up the folder to view the files on your phone.
From your computer, Go to TWRP -> BACKUPS -> (Your hardware Serial Number) -> (Folder you wish to restore to) -> and copy boot.emmc.win to your computer. Rename boot..emmc.win to boot.img
Open my toolkit and press boot into recovery.
Click Wipe. Wipe Cache, Dalvik, Factory Reset and System. NOTHING ELSE! If you click anything else, IT WILL WIPE YOUR SD CARD AND YOU WILL HAVE MORE ISSUES ON YOUR HEAD!
Press back and press Restore. Choose the backup to restore to.
After it finishes, press the back button. Press Reboot and select bootloader.
Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it.
You are now back to your stock Nandroid.
4. How to use ADB Sideload
You may have seen what ADB Sideload around the forums but have no idea what it is. Since our HOX+ does not have an SD card, it makes things harder when you have to flash a ROM.
Here's a scenario when we need to use ADB Sideload.
1. You accidentally wiped your internal SD and have no ROM on your phone
2. You wiped your ROM and forgot to transfer a custom ROM/have no backups(Nandroid) available.
3, You have none of the above and there is no available RUU for your phone. <----- This is a real bummer.
Here are the steps to load on a ROM
I placed TWRP in my toolkit for a reason. CWM does not support ADB Sideload (as far as I know) and TWRP does.
Boot into recovery manually. Turn your device off and hold the VOLUME DOWN + POWER button together until the BOOTLOADER pops up. Press the VOLUME DOWN button until you have selected RECOVERY. Press the POWER button to get into RECOVERY.
Connect the USB Cable to your phone and computer.
In TWRP, click "Advanced" and select ADB Sideload.
Download a ROM to your computer (if you haven't already done so). Rename it as one word. For example CM10.zip, QX.zip, ARHD.zip, etc.
In my toolkit, under the extras section, press ADB Sideload a ROM. Press "Yes" when it asks you if you are in recovery. Then select the ROM you want to install. It will then sideload it to your phone and flash it.
After it finishes, press the back button. Press Reboot and select bootloader.
Pull the boot.img from the zip file and extract it.
Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it.
You now have a ROM on your phone!
and for the hell of it in case I want to add even more.
hasoon2000 said:
Post 3: How to reverse everything and go back to stock
Click to expand...
Click to collapse
Can't wait for this one...
I'm a little confused as to how to do it!
Need to send mine back - faulty :'(
Sent from my HTC One X+ using Tapatalk 2
great tutorial, thanks.
but i think you should organize your posts using bold, colored and stepwise sentences. that would be great for clarity.
I followed instructions exactly. How long should phone show cyanogenmod boot image?
I've tried two different roms and made sure i installed the boot.img according to instructions but I can't seem to get past boot image.
---------- Post added at 06:13 PM ---------- Previous post was at 05:14 PM ----------
targett said:
Can't wait for this one...
I'm a little confused as to how to do it!
Need to send mine back - faulty :'(
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Hold down power, volume up and down. Boot into bootloader. Select recovery. Select restore. Select one of your backups.
This should take you back.
my phone stuck on boot screen when i tried to restore it from the NAND backup ...
anyway a great tool and make the life easier especially to the people who aren't familiar with black screen and white things :laugh:
Updated the Third Post!
targett said:
Can't wait for this one...
I'm a little confused as to how to do it!
Need to send mine back - faulty :'(
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Look at post 3
daredevil_off said:
great tutorial, thanks.
but i think you should organize your posts using bold, colored and stepwise sentences. that would be great for clarity.
Click to expand...
Click to collapse
I'll fix it up later. At least the general idea is there.
prissysox said:
I followed instructions exactly. How long should phone show cyanogenmod boot image?
I've tried two different roms and made sure i installed the boot.img according to instructions but I can't seem to get past boot image.
Click to expand...
Click to collapse
Shouldn't take more than 5 minutes to boot. Ask the respective devs about it.
PopAhmad said:
my phone stuck on boot screen when i tried to restore it from the NAND backup ...
anyway a great tool and make the life easier especially to the people who aren't familiar with black screen and white things :laugh:
Click to expand...
Click to collapse
Look at post 3. It should help now
Added how to ADB Sideload a ROM in post 4.
What else would you guys like to know with my toolkit?
my phone wont go into the bootloader screen (the white one) it shows that the command is not recognized.....
Stock RUU
In the links I am not seeing anything to get me to the stock RUU. I am having call quality issues with my phone and I have to send it back for warranty. I have relocked the phone per the instructions but I need the stock RUU to flash. I would appreciate anyone's help.
Thanks,
Joe
hasoon2000 said:
Post 3: How to reverse everything and go back to stock
Now, let's talk about getting back to stock. There are 2 ways to do this.
1. Flash the stock RUU (If available) (Recommended)
2. Restore your Nandroid (backup that I told you to make earlier)
1. I'll talk about flashing the stock RUU first.
Open up my toolkit and press "Factory RUU" from the links sections. I usually have the most updated RUUs that Football releases on my Dev-Host account. Download the correct RUU for your phone.
Now, back up all your data (pictures, contacts, etc) since this will put your phone back to complete stock.
Connect the USB cable to your phone. Press Boot into Bootloader.
It should now say FASTBOOT USB on your screen.
Press Relock bootloader. It may give you a security warning error or it may say failed. Who cares, ignore it. It's normal.
Your phone will boot up normally.
When the phone is fully loaded. Unplug and replug the USB cable back in the phone. Now,run the RUU you downloaded and follow the instructions.
Your phone will be back to stock.
2. Now, we will talk about restoring your nandroid backup.
Connect your phone to the computer. Open up the folder to view the files on your phone.
From your computer, Go to TWRP -> BACKUPS -> (Your hardware Serial Number) -> (Folder you wish to restore to) -> and copy boot.emmc.win to your computer. Rename boot..emmc.win to boot.img
Open my toolkit and press boot into recovery.
Click Wipe. Wipe Cache, Dalvik, Factory Reset and System. NOTHING ELSE! If you click anything else, IT WILL WIPE YOUR SD CARD AND YOU WILL HAVE MORE ISSUES ON YOUR HEAD!
Press back and press Restore. Choose the backup to restore to.
After it finishes, press the back button. Press Reboot and select bootloader.
Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it.
You are now back to your stock Nandroid.
Click to expand...
Click to collapse
Joai said:
my phone wont go into the bootloader screen (the white one) it shows that the command is not recognized.....
Click to expand...
Click to collapse
You have a directory issue. Place the toolkit folder in the c drive.
joejensen0 said:
In the links I am not seeing anything to get me to the stock RUU. I am having call quality issues with my phone and I have to send it back for warranty. I have relocked the phone per the instructions but I need the stock RUU to flash. I would appreciate anyone's help.
Thanks,
Joe
Click to expand...
Click to collapse
The link is in my toolkit.
Sent From My HTC Amaze 4G via Someone's Room
and that was the issue...everything works now. Really appreciate it! Would donate but I just spent a grip on this phone ysterday! keep up the good work! one question...what ROMS are good for this device?
Stock RUU
I have attached a screen shot of the toolkit running. I have been looking under "Useful Links" am I looking in the wrong place?
As I mentioned I need a stock RUU, ATT version for the HTC One X+
Thanks,
Joe
The link is in my toolkit.
Sent From My HTC Amaze 4G via Someone's Room [/QUOTE]
Joai said:
and that was the issue...everything works now. Really appreciate it! Would donate but I just spent a grip on this phone ysterday! keep up the good work! one question...what ROMS are good for this device?
Click to expand...
Click to collapse
Rom choice depends on what you want to get out of your device, its not difficult to pick out a couple roms and compare what you think will work best for you.
joejensen0 said:
I have attached a screen shot of the toolkit running. I have been looking under "Useful Links" am I looking in the wrong place?
As I mentioned I need a stock RUU, ATT version for the HTC One X+
Thanks,
Joe
The link is in my toolkit.
Sent From My HTC Amaze 4G via Someone's Room
Click to expand...
Click to collapse
[/QUOTE]
Your running v1.1 of the toolkit, hasoon has since updated the kit to v2.0 which has the link your looking for. Alternatively if you look through the forums im sure you could find a link to it.
Will try it when I get back home...
Sent from my HTC One X+ using Tapatalk 2
Stock RUU
hasoon2000 said:
You have a directory issue. Place the toolkit folder in the c drive.
The link is in my toolkit.
Sent From My HTC Amaze 4G via Someone's Room
Click to expand...
Click to collapse
Updated, worked perfectly. I am back to stock and good to send back. Thank you for your help. The toolkit is awesome!
Thanks,
Joe
Worked!
It worked for me, I got SU Access, but for the purpose i got SU access it failed. WiFix is not working, and I have the dreaded android SIM Card Inset wifi disable issue.
hasoon2000 said:
Post 1: How to unlock your bootloader, flash a recovery and root
Post 2: How to flash a custom ROM and kernel (boot.img)
Post 3: How to reverse everything and go back to stock
Post 4: How to ADB Sideload a ROM
....................................................................................................................................
Click to expand...
Click to collapse

[Q] Rooting & Unlocking a Rezound in 2013 (w/Updates)

Hello All,
I bought my mom an HTC Rezound back in 2011 and given that I've been possessed with rooting, unlocking, and modding, I got my hands on her device the other day and nearly died when I saw all of the bloatware she had on it. Now she's at least updated to ICS, however I would like to root/unlock and mod her device so I can make it run a lot better.
The question is - what is the best way to root/unlock this device? I've read a lot of the XDA threads and done some Google searches, but most of the XDA guides are old and a lot of the comments (on XDA and Google) is that several of the methods don't work for the "updated" Rezounds. I reiterate that hers is an old version (original from 2011) but has the 2012/2013 updates.
If someone could please provide a link to a known working method for the 2012/2013 updated Rezounds, that would be great!
Thank you!
-Taxmaster
The basic method hasn't changed. Unlock the bootloader at htcdev.com, flash a recovery with fastboot, then go from there. You might see stuff talking about charging problems with CWM...you can safely ignore that, it's old news. There is no issue with the new CWM. You might also see stories of issues flashing things with TWRP. Again, that's old news. The recent versions of TWRP have no issues. A lot use Amon-ra, but I don't like it and haven't used it since TWRP and CWM were fixed, so I can't really say much more about it.
Hansoon's all-in-one toolkit will still work fine with this phone through the initial
Kernels can't be flashed in recovery unless you go the extra step of getting S-OFF. They can still be flashed, but only through the bootloader (using either fastboot or a PH98IMG.zip, if the ROM or kernel provides it). S-OFF also removes version checks which normally prevents downgrading of radios and bootloader. However, this phone is essentially unbrickable while it's S-ON, so there is a tradeoff.
Keep in mind that unlocking this phone's bootloader will wipe /data and emmc, so find a way to backup anything important before you start.
As for ROMs, AOSP is 99% working now...it's actually better here now than it is on the Note 2, and I prefer it to Sense on this phone, but there are some great Sense ROMs out as well. The only caveat is that MHL is only working on Sense 3.6 and I think one Sense 4+ ROM...no AOSP ROM has it working and most Sense 4 ROMs don't.
shrike1978 said:
The basic method hasn't changed. Unlock the bootloader at htcdev.com, flash a recovery with fastboot, then go from there. You might see stuff talking about charging problems with CWM...you can safely ignore that, it's old news. There is no issue with the new CWM. You might also see stories of issues flashing things with TWRP. Again, that's old news. The recent versions of TWRP have no issues. A lot use Amon-ra, but I don't like it and haven't used it since TWRP and CWM were fixed, so I can't really say much more about it.
Hansoon's all-in-one toolkit will still work fine with this phone through the initial
Kernels can't be flashed in recovery unless you go the extra step of getting S-OFF. They can still be flashed, but only through the bootloader (using either fastboot or a PH98IMG.zip, if the ROM or kernel provides it). S-OFF also removes version checks which normally prevents downgrading of radios and bootloader. However, this phone is essentially unbrickable while it's S-ON, so there is a tradeoff.
Keep in mind that unlocking this phone's bootloader will wipe /data and emmc, so find a way to backup anything important before you start.
As for ROMs, AOSP is 99% working now...it's actually better here now than it is on the Note 2, and I prefer it to Sense on this phone, but there are some great Sense ROMs out as well. The only caveat is that MHL is only working on Sense 3.6 and I think one Sense 4+ ROM...no AOSP ROM has it working and most Sense 4 ROMs don't.
Click to expand...
Click to collapse
Thank you for covering this so thoroughly! Can you clarify what Sense is and what (if any) advantage it has over AOSP? I have a Galaxy Note 2 so I haven't come across this before.
Also, my plan is to use TWRP and only flash ROMs that have a custom kernel as part of the ROM (no separate flashing).
Sent via Tapatalk 2 using my:
Verizon Galaxy Note 2 (SCH-I605)
Unlocked, Overclocked, and Undervolted
CleanROM 4.7 w/Perseus 33.6 Kernel
Sense is HTC's overlay on top of Android...
http://en.wikipedia.org/wiki/HTC_Sense
Ah, so Sense is to HTC as Touchwhiz is to Samsung.
Sent via Tapatalk 2 using my:
Verizon Galaxy Note 2 (SCH-I605)
Unlocked, Overclocked, and Undervolted
CleanROM 4.7 w/Perseus 33.6 Kernel
Taxmaster said:
Ah, so Sense is to HTC as Touchwhiz is to Samsung.
Sent via Tapatalk 2 using my:
Verizon Galaxy Note 2 (SCH-I605)
Unlocked, Overclocked, and Undervolted
CleanROM 4.7 w/Perseus 33.6 Kernel
Click to expand...
Click to collapse
100% correct with that. Personally i like the AOSP roms better then sense. they just seem to work very well and alot of bugs have been worked out and they seem alot quicker then sense roms. The few things that you are missing from not having a sense rom are min and not a lot of people really notice. I use Neo's Infection 2.5. great rom, great speed, and very stable
clmowers said:
100% correct with that. Personally i like the AOSP roms better then sense. they just seem to work very well and alot of bugs have been worked out and they seem alot quicker then sense roms. The few things that you are missing from not having a sense rom are min and not a lot of people really notice. I use Neo's Infection 2.5. great rom, great speed, and very stable
Click to expand...
Click to collapse
That actually was the ROM I was planning on using!
Here is my plan of attack (check to see if this looks okay):
Backup: MyBackup Pro (later on use Titanium Backup, but apparently temp. root doesn't work anymore after the ICS update).
Unlock/Root: Hassoon's All-In-One Kit: http://forum.xda-developers.com/showthread.php?t=1504824
ROM to flash: Neo's Infection 2.5: http://forum.xda-developers.com/showthread.php?t=2070947
Let me know if you give this plan of attack a thumbs up! Also, please let me know if you have any suggestions or things I should be aware of along the way!
Thanks!
-Taxmaster
Taxmaster said:
That actually was the ROM I was planning on using!
Here is my plan of attack (check to see if this looks okay):
Backup: MyBackup Pro (later on use Titanium Backup, but apparently temp. root doesn't work anymore after the ICS update).
Unlock/Root: Hassoon's All-In-One Kit: http://forum.xda-developers.com/showthread.php?t=1504824
ROM to flash: Neo's Infection 2.5: http://forum.xda-developers.com/showthread.php?t=2070947
Let me know if you give this plan of attack a thumbs up! Also, please let me know if you have any suggestions or things I should be aware of along the way!
Thanks!
-Taxmaster
Click to expand...
Click to collapse
I've never used the all-in-one kit. I was never a big fan of them, but other people have had good success with it. From what it looks like it would be the same as doing it step by step manually. so i would say use that.
But yea that looks good, also make sure if you are going to stay s-on, to extract the boot.img file from the rom and flash it in fastboot.
Also just remember when you go ahead and do the unlock from HTC, it WILL data wipe your phone, so anything that needs to be backed up back it up..as you did say backup i think you already know that
other then that i say thumbs up
clmowers said:
I've never used the all-in-one kit. I was never a big fan of them, but other people have had good success with it. From what it looks like it would be the same as doing it step by step manually. so i would say use that.
But yea that looks good, also make sure if you are going to stay s-on, to extract the boot.img file from the rom and flash it in fastboot.
Also just remember when you go ahead and do the unlock from HTC, it WILL data wipe your phone, so anything that needs to be backed up back it up..as you did say backup i think you already know that
other then that i say thumbs up
Click to expand...
Click to collapse
Okay, well I plan to stay S-On given that when I flash Neo's Infection 2.5 ROM it includes the Hiro Kernel. I went to download his ROM (which version should I use btw? I downloaded Infection_2.5.zip and there are others that say inverted, slim, dev, etc.) and extracted boot.img. I haven't worked with fastboot yet so could you give me a brief walkthrough on how to proceed with that?
By the way, do you recommend the AMON RA recovery that Neo mentions? I'm personally a TWRP fan.
Thanks!
-Taxmaster
Taxmaster said:
Okay, well I plan to stay S-On given that when I flash Neo's Infection 2.5 ROM it includes the Hiro Kernel. I went to download his ROM (which version should I use btw? I downloaded Infection_2.5.zip and there are others that say inverted, slim, dev, etc.) and extracted boot.img. I haven't worked with fastboot yet so could you give me a brief walkthrough on how to proceed with that?
By the way, do you recommend the AMON RA recovery that Neo mentions? I'm personally a TWRP fan.
Thanks!
-Taxmaster
Click to expand...
Click to collapse
yeah no problem.
the difference are this
Slim is basiclly a stripped down version of the rom, min amount of apps and stuff no google stuff or anything..you have to download each thing seperate
the dev version is the one he uses to dev with, it was more less setup for Neo to use and play with for testing..nothing special with it just more stripped down then the standards
the inverted and non inverted are the same roms. the big difference is the inverted uses a dark them with bright lettering where as the non inverted uses a light theme with dark lettering. this also has the google apps installed
I use the inverted as i think it looks cool, always like the darker themed stuff. personal pref on that tho
fastboot is pretty simple to use. First you will need to download it.. ive always used the android SDK and then downloaded it from that and then removed the SDK. If you do some digging around im sure you can find the fastboot and adb stuff by itself.
so once you get the phone unlocked via htcdev you need to flash the recovery file. I do use amon ra like neo suggest. TWRP and CMW work just as well now that they fixed alot of the issues they were having. Im like amon so i tend to stick with it..its clean easy to use and never had a problem with it
to flash the recovery, you will need to use fastboot
to enter fastboot, pull the battery and put it back in, hold down the power and vol down button till you get the bootloader, then use the vol keys to select fastboot, then hit the power button. plug the phone into the computer
open the command prompt and go to where you have fastboot downloaded and then make sure the recovery img is there
type fastboot flash recovery recovery.img then hit enter. This will flash the recovery to the phone,
then do your typical flashing of the rom in the recovery. after you have flashed the rom, if you are using amon, back out till you hit the main menu and go down to dev options and select boot to bootloader..this will reboot your phone into the bootloader again, then just go back into the fastboot like you did to flash recovery. then open up the rom with a zip program like 7zip winrar and you will see a boot.img file. take that file out and put it in the same location as the recovery file on your computer that also has the fastboot program
go back to the command promt and type
fastboot flash boot boot.img to install the boot img into the phone and then when its down you can reboot..all should be good to go
hopefully this make since to you lol if not let me know and i will clearify it
---------- Post added at 08:06 PM ---------- Previous post was at 07:58 PM ----------
Oh and one last thing he no longer includes hiro for the kernel. The stock kernel with that ROM is snuzzo funkybean
Sent from my Infected Rezound using Tapatalk 2
clmowers said:
yeah no problem.
the difference are this
Slim is basiclly a stripped down version of the rom, min amount of apps and stuff no google stuff or anything..you have to download each thing seperate
the dev version is the one he uses to dev with, it was more less setup for Neo to use and play with for testing..nothing special with it just more stripped down then the standards
the inverted and non inverted are the same roms. the big difference is the inverted uses a dark them with bright lettering where as the non inverted uses a light theme with dark lettering. this also has the google apps installed
I use the inverted as i think it looks cool, always like the darker themed stuff. personal pref on that tho
fastboot is pretty simple to use. First you will need to download it.. ive always used the android SDK and then downloaded it from that and then removed the SDK. If you do some digging around im sure you can find the fastboot and adb stuff by itself.
so once you get the phone unlocked via htcdev you need to flash the recovery file. I do use amon ra like neo suggest. TWRP and CMW work just as well now that they fixed alot of the issues they were having. Im like amon so i tend to stick with it..its clean easy to use and never had a problem with it
to flash the recovery, you will need to use fastboot
to enter fastboot, pull the battery and put it back in, hold down the power and vol down button till you get the bootloader, then use the vol keys to select fastboot, then hit the power button. plug the phone into the computer
open the command prompt and go to where you have fastboot downloaded and then make sure the recovery img is there
type fastboot flash recovery recovery.img then hit enter. This will flash the recovery to the phone,
then do your typical flashing of the rom in the recovery. after you have flashed the rom, if you are using amon, back out till you hit the main menu and go down to dev options and select boot to bootloader..this will reboot your phone into the bootloader again, then just go back into the fastboot like you did to flash recovery. then open up the rom with a zip program like 7zip winrar and you will see a boot.img file. take that file out and put it in the same location as the recovery file on your computer that also has the fastboot program
go back to the command promt and type
fastboot flash boot boot.img to install the boot img into the phone and then when its down you can reboot..all should be good to go
hopefully this make since to you lol if not let me know and i will clearify it
---------- Post added at 08:06 PM ---------- Previous post was at 07:58 PM ----------
Oh and one last thing he no longer includes hiro for the kernel. The stock kernel with that ROM is snuzzo funkybean
Sent from my Infected Rezound using Tapatalk 2
Click to expand...
Click to collapse
Okay, so here's where I'm at:
1. I downloaded the Android SDK and installed it. I went into the folder Downloads/adtbundle..../sdk/platform-tools
In this directory I see an adb and a fastboot file. When I try to open and run either one of them, a window opens and terminates less than a minute after. I don't know if this is normal or not if if I'm supposed to use a different directory, but this is where I extracted these files to. (x64 Win 7 Ultimate btw).
2. When you say open the command prompt, which one are we talking about here and how do I get to it? When I think of command prompt, I'm thinking Windows "Run" (start+R).
3. You noted to have the amon ra recovery in the same directory as fastboot (at least that is what I believe you're inferring). Is the directory I noted above the appropriate place to put this Ra3.15PH98IMG.img file in? Am I supposed to leave it in this format?
4. Do I type "fastboot flash recovery recovery.img" in verbatim or do I type in something else (a different command), perhaps fastboot flash recovery Ra3.15PH98IMG.img ?
5. I'm confused regarding when I'm supposed to flash the ROM itself using Amon Ra. It seems like first I unlock, then I use fastboot to install Amon Ra, then I use fastboot to install the image extracted from the Infection 2.5zip. Once this is all done, then do I flash the Infection2.5.zip itself using Amon Ra?
6. How is the snuzzo funkybean kernel? Is it a better kernel than the Hiro? Overclock etc?
Sorry in advance for the many clarifying questions lol, the last thing I want is to break my mother's phone and be on the hook to buy her a new one lol.
-Taxmaster
Taxmaster said:
Okay, so here's where I'm at:
1. I downloaded the Android SDK and installed it. I went into the folder Downloads/adtbundle..../sdk/platform-tools
In this directory I see an adb and a fastboot file. When I try to open and run either one of them, a window opens and terminates less than a minute after. I don't know if this is normal or not if if I'm supposed to use a different directory, but this is where I extracted these files to. (x64 Win 7 Ultimate btw).
2. When you say open the command prompt, which one are we talking about here and how do I get to it? When I think of command prompt, I'm thinking Windows "Run" (start+R).
3. You noted to have the amon ra recovery in the same directory as fastboot (at least that is what I believe you're inferring). Is the directory I noted above the appropriate place to put this Ra3.15PH98IMG.img file in? Am I supposed to leave it in this format?
4. Do I type "fastboot flash recovery recovery.img" in verbatim or do I type in something else (a different command), perhaps fastboot flash recovery Ra3.15PH98IMG.img ?
5. I'm confused regarding when I'm supposed to flash the ROM itself using Amon Ra. It seems like first I unlock, then I use fastboot to install Amon Ra, then I use fastboot to install the image extracted from the Infection 2.5zip. Once this is all done, then do I flash the Infection2.5.zip itself using Amon Ra?
6. How is the snuzzo funkybean kernel? Is it a better kernel than the Hiro? Overclock etc?
Sorry in advance for the many clarifying questions lol, the last thing I want is to break my mother's phone and be on the hook to buy her a new one lol.
-Taxmaster
Click to expand...
Click to collapse
Your totally fine buds, i tend to not make thing totally clear..its my learning disabilty, i think of it in my head but sometimes my fingers dont always type what i think. so lets take this 1 step at a time
as you have downloaded the SDK already i will skip that..but here pretty much the step by step. If you are using the all-in-one
1.) Go to http://www.htcdev.com/bootloader/ and fill out the form, it tells you how to do everything from the site on how to unlock your phone
2.) Once you have unlocked it, you will need to install the custom recovery amon ra
3.) make a directory under the c drive called phone and copy the platform-tools from the SDK there. so you should see something like this
C:\phone\fastboot.exe
C:\phone\adb.exe
etc....
4 copy the boot.img and the recovery img to c:\phone (for ease rename amon to recovery.img)
5.) pull the battery on your phone and reinstall it...hold down power button and the vol down button
6.) once you are in the bootloader select fastboot from the menu and hit the power button
7.) connect the phone via usb to the computer and open a command prompt window ( Crtl + r then type cmd and hit enter)
8.) type in cd\ and then hit enter
9.) type cd c:\phone and then hit enter
10.) type fastboot flash recovery recovery.img and then hit enter...you should see it loading and end up saying succesfull
11.) go back into the bootloader by selecting it from the menu on the phone and then use the vol down key to select recovery. this will boot into amon
12.) once you are in amon, select mount as usb drive..i think its the second option in the menu and then mount either of the sd cards.
13.) copy the ROM zip the phone and then once its down hit the power button to turn that function off
14.) go to the wipe menu and wipe everything 3 times, this will give your phone a clean slate
15.) back out and then select the flash zip menu and then select where you saved the rom and let it flash away.
16.) once you have flashed back out to the main menu again and then select the dev option in the menu and select reboot to bootloader, you are going to select fastboot again.
do steps 9 and 10 again if you closed the previous window other wise type in fastboot flash boot boot.img, and you will see a similuar screen like you did on the recovery file, once its done reboot your phone and you are now running a custom rom
I dont think that funky is overclocked by default, but the option is there to over/under click if thats your liking. Ive always had good luck with his kernals so i tend to stick to snuzzos kernals. ive used Hiro before and never really noticed much of a huge difference between the two. I live by the saying if it isnt broke dont fix it. so tend to stick with the funky just because i know it works and its never given me problems
hopefully this clears things up
clmowers said:
13.) copy the ROM zip the phone and then once its down hit the power button to turn that function off
14.) go to the wipe menu and wipe everything 3 times, this will give your phone a clean slate
15.) back out and then select the flash zip menu and then select where you saved the rom and let it flash away.
16.) once you have flashed back out to the main menu again and then select the dev option in the menu and select reboot to bootloader, you are going to select fastboot again.
do steps 9 and 10 again if you closed the previous window other wise type in fastboot flash boot boot.img, and you will see a similuar screen like you did on the recovery file, once its done reboot your phone and you are now running a custom rom
Click to expand...
Click to collapse
I followed you up to step 13 (thanks for getting me this far btw!)
Questions:
1. You say to copy the ROM zip "the phone" and then once "its down" hit the power button to turn that function off. I'm totally confused as to what this means. For one, I don't know if I'm supposed to copy the Infection2.5.zip to the C:\phone or to the extSDCard. Then I just don't follow what you mean by "its down" and "turn that function off".
2. Just to clarify, it sounds like this is the order of operations (excluding wipes):
--Unlock/Root
--Fastboot Recovery
--Use Recovery to Flash ROM
--Fastboot boot.img (from ROM)
--Reboot system (restart phone)
Does this seem correct? Also, is there a cache/dalvik-cache clear in order at some point?
Thanks!
-Taxmaster
Taxmaster said:
I followed you up to step 13 (thanks for getting me this far btw!)
Questions:
1. You say to copy the ROM zip "the phone" and then once "its down" hit the power button to turn that function off. I'm totally confused as to what this means. For one, I don't know if I'm supposed to copy the Infection2.5.zip to the C:\phone or to the extSDCard. Then I just don't follow what you mean by "its down" and "turn that function off".
2. Just to clarify, it sounds like this is the order of operations (excluding wipes):
--Unlock/Root
--Fastboot Recovery
--Use Recovery to Flash ROM
--Fastboot boot.img (from ROM)
--Reboot system (restart phone)
Does this seem correct? Also, is there a cache/dalvik-cache clear in order at some point?
Thanks!
-Taxmaster
Click to expand...
Click to collapse
Sorry those were miss types lol it should read this
copy the ROM to the sdcard and then once its done hit the power button to turn off usb mass storage
Basiclly what you are doing is copying infection 2.5 to your SDcard on your phone itself so you can flash it
Yes that would be the correct order.
As for wiping when you get into the wipe menu you will see the caches, and yes you will have to wipe both cache and devlik cache
Your very welcome btw
clmowers said:
Basiclly what you are doing is copying infection 2.5 to your SDcard on your phone itself so you can flash it
Click to expand...
Click to collapse
One last clarification, when you say to the "SDcard on your phone itself" do you mean extSDCard or sdcard0 ? My plan was to insert the extSDCard while the phone is currently running the stock ROM, format it, connect it to the PC (MTP) and then copy/paste the Infection2.5.zip over to it (extSDCard). I would then leave that file on the extSDCard and use it as the reference directory for the ROM flash. Is this appropriate, or is it required to store the ROM zip on sdcard0 (built-in memory)?
Thank you!
-Taxmaster
Yes the exsdcard will work. That's the external sdcard and will work just fine As for getting the ROM on the extsdcard..that's totally up to you. It just need to be there for flashing
Sent from my Infected Rezound using Tapatalk 2
clmowers said:
Yes the exsdcard will work. That's the external sdcard and will work just fine As for getting the ROM on the extsdcard..that's totally up to you. It just need to be there for flashing
Sent from my Infected Rezound using Tapatalk 2
Click to expand...
Click to collapse
Alrighty then! I'm going to go for it and I'll let you know how it goes!
-Taxmaster
Its sounds more complicated then it really is...yea def let me know how it goes. If you have any questions along the way just ask
Sent from my Infected Rezound using Tapatalk 2
I just wanted to let everyone know that I got my mom's phone up and running using this method! Thank you guys for all of your help!
Sent via Tapatalk 2 using my:
Verizon Galaxy Note 2 (SCH-I605)
Unlocked, Overclocked, and Undervolted
Bean's ROM 18 w/Perseus 33.6 Kernel
Wouldn't it be great if everyone got answers like this?
Sent from my SCH-I925 using Tapatalk HD

Categories

Resources