Related
So I've had my Atrix for a few months now, and it's mostly awesome. I'm coming from having owned an iPhone before, and it's just fantastic. I've stayed away from modding it too much however, since I knew the bootloader was locked and not a lot could really be done. But, according to several posts I see here, the bootloader seems to have been unlocked recently. Yay?
So, I ask that you forgive my ignorance. What does this mean? Does a given ROM need to be modified to work with every model of phone? If so, which ones presently work with the Atrix? Any? (It looks like the unlock was found very recently.) How does that process work exactly? Is there any way to ensure a recovery path if something were to go wrong, so that I don't brick my phone?
I'm just curious here. Presently, my phone is on the stock firmware without any upgrades at all, and I've simply rooted it and installed the webtop mod so I could play games on my TV. Other than that, it's been lots of Android Market for me. I'd like to branch out, and I don't even know where to begin.
There aren't any custom rom's for this yet, there's work being done, so it's just a matter of time. However, there is a developer build from Asia that can be flashed. There are a few issues with it, so if you are averse to troubleshooting or dealing with issues then just wait a few days.
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Can I flash the UK Firmware on a unlocked ATT Atrix now?
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
schlupp88 said:
Can I flash the UK Firmware on a unlocked ATT Atrix now?
Click to expand...
Click to collapse
_Dennis_ said:
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
Click to expand...
Click to collapse
_Dennis_ is right. You should sbf_flash -x to extract the UK firmware and use fastboot to flash just boot.img (CG56 in Froyo) and system.img (CG57 in Froyo). If you want to flash the radio, use a custom .sbf (for AT&T) with only the radio. We don't yet know whether you can replace your bootloader with a UK bootloader. We still flashed a signed bootloader to our phone. In the worst case, if you flash a UK signed bootloader and your boot ROM is looking to find an AT&T signature in your bootloader: BAD! It is fairly unclear that the unlock ALSO tells boot ROM not to care about signatures, it may very well still care. And the order of RSD: erase,write,verify is a little dangerous...
I as well, don't know much about this... but as far as I know, this will mean that developers will be able to create real operating systems for the phone and not have to wait for att/moto to do that...
in the past it was an OS from att/moto, and all the "roms" in xda were actually the same OS but with some skins and mods added to them...
Yes, if you look at the development forums for just about any other android phone, you will see full customized ROMs that can be installed. That's where we are headed.
_Dennis_ said:
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
Click to expand...
Click to collapse
I did a test with this.
I flashed 1.8.3 SBF over my unlocked bootloader to see if I could use moto-fastboot to flash over a 'stock' bootloader. It works to flash system (since it is still technically unlocked) but fails to flash boot.
So DO NOT TRY TO SBF FLASH A INTERNATIONAL VERSION unless you want to be stuck on the version with no way to get your phone back off.
I also would not flash the boot.img of a international version for the same reason.
beatphreek said:
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Click to expand...
Click to collapse
I just finished unlocking and installed the new CWM recovery, just waiting for some roms! About the full system backup with CWM, does is deposit a folder to the SD card I can remove for safe keeping like TIBu? I never used CWM to backup or restore.
climo said:
I just finished unlocking and installed the new CWM recovery, just waiting for some roms! About the full system backup with CWM, does is deposit a folder to the SD card I can remove for safe keeping like TIBu? I never used CWM to backup or restore.
Click to expand...
Click to collapse
I think that the backup will be found in a Clockwork folder on your sd card. I also think that when you do the backup you will get to choose the destination. Either sd or external sd.
I haven't used the bl unlock or the new ClockworkMod (Just waiting on a nice rom). But that is how it went for me on the previous CWM that didn't require the unlocked bootloader.
Maybe someone who has this newer stuff can shed a little more light on it.
beatphreek said:
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Click to expand...
Click to collapse
Does this essentially create an image of your device? Or does it just back up the firmware?
When CWM backs up ur files it creates a image file of
Boot.img
Cache.img
Data.img
recovery.img
system.img
so yes it does use a image.
Y'all talking about custom ROM's and such, no one seems to care about overcloking.. no one seems to realize what a beast a 1.4ghz Atrix would be.
Viamonte said:
Y'all talking about custom ROM's and such, no one seems to care about overcloking.. no one seems to realize what a beast a 1.4ghz Atrix would be.
Click to expand...
Click to collapse
+1.
ROMs will sometimes require you to have the custom kernel associated with them. CM7 for the Captivate comes to mind. With custom kernels, the Captivate was a beast. We had the VooDoo lagfix, which actually made the device usable on bootup. We were able to convert all partitions to ext4, and kind-of make the GPS work.
Overclocking is a possibility too. There's so much that is able to be done. It's a bit difficult coming from an iPhone where customization was limited, even with jailbreaking. But you'll soon get the hang of it.
GPS. Nice point too, but Moto itself promisses improvements on the 2.3.4 OTA. This is the most sorely needed fix for me, since my gps SUCKS. It can take anywhere up to 30 minutos to find my locations. Yes, you read that right.
Viamonte said:
GPS. Nice point too, but Moto itself promisses improvements on the 2.3.4 OTA. This is the most sorely needed fix for me, since my gps SUCKS. It can take anywhere up to 30 minutos to find my locations. Yes, you read that right.
Click to expand...
Click to collapse
Mine works great. You may have a hardware issue?
Sent from my MB860 using XDA App
JayRolla said:
Mine works great. You may have a hardware issue?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+2
It shouldn't take that long to lock on. Mine locks on instantly.
Is there a way to root my officialy updated to ICS, Xperia Mini(ST15i) without unlocking bootloader?(in order to downgrade etc...) I just want to root my xperia mini without messing up with the warranty....Any way to root it with locked bootloader? (4.1.B.0.431)
Thanks in advance
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Feanor88 said:
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Click to expand...
Click to collapse
downgrading needs unlocked bootloader... :/ i had bricked my mini some time ago because i tried to downgrade with locked... (( any other way?
Thanks
EDIT: flashing xperia arc's or Neo V's for example would brick my phone....wouldn't it? (and it also needs bootloader unlock...so i don't think i would do that... BUT thanks for your help mate
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Feanor88 said:
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Click to expand...
Click to collapse
man i have a problem...when i place my phone into flashmode (down key) it disconnects on its own...and that's why i bricked my phone long time ago....now i am afraid to do that i have installed the flashtool drivers from Flashtool/drivers.... but they mustn't work for my mini....any solution please give me the drivers you use for your Mini and work with it if you can i would really appreciate that!
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Feanor88 said:
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Click to expand...
Click to collapse
it takes about 1-2 minutes to disconnect.But, what if it disconnects while on downgrading?
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Feanor88 said:
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Click to expand...
Click to collapse
Pfff i'm a bit scared.....there is no hope that there will be somewhen another way to root...?
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Feanor88 said:
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Click to expand...
Click to collapse
i maybe try it later... thanks for your replies man DD i appreciate that
kwstas 13 said:
i maybe try it later... thanks for your replies man DD i appreciate that
Click to expand...
Click to collapse
Let me know if you need more help!
Feanor88 said:
Let me know if you need more help!
Click to expand...
Click to collapse
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
kwstas 13 said:
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
Click to expand...
Click to collapse
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Feanor here is a better friend for you than him, when it comes to rooting your phone.
Click to expand...
Click to collapse
Blushing
But don't forget I'm a noob after all... I'll just keep pointing other people's tutorials, like for example yours, Rick
DragonClawsAreSharp said:
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
That's strange. Anyway, if you installed PC Companion you have adb drivers. Install flashmode drivers from Flashtool installazion folder, you find the executable in \Flashtool\drivers. If Windows prompts you that the drivers are dangerous, just install them anyway.
What I can say is that you DON'T need to unlock your bootloader to use flashmode in Flashtool. Otherwise, my phone would have exploded long ago
Now let me tell you this: if you are SURE you did everything the right way, and still your phone got bricked, then maybe you shouldn't try. you never know.
If you tried to to something you didn't know how to do, you probably made a mistake, and that's why the phone got bricked.In this case, I'd give it a try.
But we're not able to see your phone and test it, so whatever you do, unfortunately, you always do it on your own risk.
I couldn't be more sincere.
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
You, and all developers/people here, are simply awesome!.... But this sh*t with unlocking bootloader and loosing warranty is so....stupid....I think i will give it a try and i am gonna sure thank you.... Somethink else....my phone has also a problem on the screen while scrolling....do you know if that is a hardware or a firmware problem?
What do i mean when i say scroll problem:
1st example: While browsing the Internet and scroll with fast moves, links are pressed on its own and new tabs are opened,as links are pressed.
2nd example: While i scroll the app drawer,fast s make apps open without my will....
3nd exapmle and the most representative: While playing fruit ninja and do fast moves to cut the fruits, the touchscreen doesn't even fell that i touch the screen!!! I do fast moves to cut the fruits and nothing happens!! As a result i always lose! (just joking....)
My phone is fast and really smooth only when my moves are slow....any thoughts about that? :/
Thanks once again for your BRAVE help!
You have a Mini, right? That's a hardware problem. Very common, even if not everyone realizes it. Check THIS thread for a (possible?) solution.
I keep seeing posts about not being able to come back from ICS to GB I want to know why? I'm not dumb and I have looked but don't really understand why you couldn't come back from a leak? There are methods of completely wiping the operating system from the phone I've done it could you not do this after installing a leak?
Sent from my DROID RAZR MAXX using XDA
Oops I don't know how to delete a post just logged in with my PC and seen the new Q&A section didn't see that on my phone mods can delete if needed or move it if possible!!!
Because 4.0.4 leaks update the bootloader and since the bootloader is locked you can't revert it back to an older one. If I understand it right.
daniel644 said:
Because 4.0.4 leaks update the bootloader and since the bootloader is locked you can't revert it back to an older one. If I understand it right.
Click to expand...
Click to collapse
Yes, this is correct. And fastbooting doesn't / can't flash bootloaders. So that's why were stuck.
Sent from my XT912 using XDA
OK
So a bootloader is like the bios of a motherboard? But locked or not if you erase everything I don't know did the bootloader not change with the first leaks?
Not quite.
The bootloader can be upgraded (this happens usually with a OTA) but cannot be downgraded.
Sent from my XT910 using xda premium
OK see what I'm saying if the bootloader gets upgraded with a OTA it can not be wiped? So not all the leaks have the bootloader upgrade within them then? This is why I'm having these questions when I upgraded flashed to the first leak I had a few problems with it and didn't fully know how to get it back off and back to stock I installed bootstrap and played with it all of about 2minutes before I had completely erased everything on my phone and could not go anywhere and had to fastboot with fastboot file. What I'm saying is if the upgrades come with a updated bootloader sometimes then formatting the internal memory can delete everything and you can apfastboot back to another stock rom right? I would belive this could work you just need a way to get to a custom recovery mode to be able to format the internal memory? I may be confusing more people than I want but wanted to understand this better!
Sent from my DROID RAZR MAXX using XDA
xgshortbus25 said:
OK see what I'm saying if the bootloader gets upgraded with a OTA it can not be wiped? So not all the leaks have the bootloader upgrade within them then? This is why I'm having these questions when I upgraded flashed to the first leak I had a few problems with it and didn't fully know how to get it back off and back to stock I installed bootstrap and played with it all of about 2minutes before I had completely erased everything on my phone and could not go anywhere and had to fastboot with fastboot file. What I'm saying is if the upgrades come with a updated bootloader sometimes then formatting the internal memory can delete everything and you can apfastboot back to another stock rom right? I would belive this could work you just need a way to get to a custom recovery mode to be able to format the internal memory? I may be confusing more people than I want but wanted to understand this better!
Sent from my DROID RAZR MAXX using XDA
Click to expand...
Click to collapse
I assume it is because the phones BIOS will allow upgrades to the bootstrap code, but not downgrades. It's probably tied to the revision string value.
The .79 leak is (I'm pretty sure) the latest leak that doesn't upgrade the bootstrap code (aka bootloader), so reverting to GB is possible from .79 or earlier leaks. I re-flashed GB from .79 last week, so I can confirm that it does actually work. I'm on .181, waiting for an OTA release of .912190282762628 from Motonverizola.
Motorola may know a trick to force a bootstrap downgrade, but I do not.
The bootloader is not the only problem, it can be downgraded without a problem (e.g. from 0A.74 to 0A.6C). The reason that we cannot downgrade from ICS to GB is the signature on each partition. The partitions are getting signed. For example the boot (kernel) partition gets a higher secure number when updated. Now, when we want to flash another boot.img, its secure number has to match with that one from the boot partition, otherwise there will come up an signature verification error. And the same thing applies to the another partitions (except /system which is unsigned). The bootloader is responsible for the signature checks. If it were unlocked the signatur checks could be turned off and we were able to flash anything to the device.
But there are some tricks possible to perform a downgrade. But this would be a lot of work (patching fastboot files to the ICS-matching secure versions or signatures. Decrypting of Motos signature is nearly impossible, so we would have to patch already signed files - too much work and not really needed)
And official ICS will come now and with it we will get a lot of nice things. We will be able to bypass the bootloader for booting custom kernels, we will get full working custom roms and we will be able to use the full power of our Razr.
I hate to be that guy but seriously:
3. Post only using a clear subject and message.
You're most likely to receive a helpful answer to your question if you use a short subject title that describes your problem and a message that explains in detail what your problem is and what you've tried to solve it.
Click to expand...
Click to collapse
OK got it now!
Sent from my DROID RAZR MAXX using XDA
I think we should start something like a community project to guess n hack the bootloader encryption. Heck, I could leave my lappy on 24x7 n use brute force.
cheekrox said:
I think we should start something like a community project to guess n hack the bootloader encryption. Heck, I could leave my lappy on 24x7 n use brute force.
Click to expand...
Click to collapse
We could use a cloud based array to crack it XD
BUT i don't think setting up this system is worth the work. Some dev are hinting that after the ics ota we will don't need the unlocked bootloader. So just wait and hope for the best
It's likely the encryption key is nigh on unbreakable even with a cloud based array it would take years, by which time we will no longer have our Razrs so it would be a waste of time.
Guide to AES encryption:
http://www.moserware.com/2009/09/stick-figure-guide-to-advanced.html
Tutorial. Bootloader unlocked. Install ClockWorkMod, Kernel and ROM
Before Flashing a Custom Kernel. You have to have your bootloader unlocked.
To Unlock Bootloader follow this link http://forum.xda-developers.com/showthread.php?t=1730874
"This tutorial is for people who just bought a cell phone and want to customize, but afraid to make any modification other than Workshops.
All I'll be teaching procedures have been tested by me (Xperia Live With Walkman Wt19a) remembering that this tutorial can also be applied to other devices on the same line, but the person is aware of everything you're doing.."
Ok So we go to our interest.
It is recommend to have the Pc and Compani SUS for any drivers.
I will describe in steps. "Before you do anything BATTERY MUST BE 100% LOAD"
1º. You need to have CWM "ClockworkMod" To do a FULL BACKUP which TER is EXTREMELY IMPORTANT. If you can not install the CWM, progress is TOTALLY PUT IN YOUR OWN RISK. (OK JA ADVISED THIS).
2º.Download CWM-Install here is the link: http://www.4shared.com/rar/qZQbLbdc/CWM-Install.html?
3º. After completing the download extract to a folder.
4º.1. Run install-cwm '. Cmd
install-cmw1.cmd - Xperia Arc / Neo
install-cmw2.cmd - Xperia Mini / MiniPro / Active / Live With Walkman
2.Enable USB Debugging on device
3.Connect your device using usb data cable
4.Follow on screen instruction
5º. Once that's done you should have already installed the CWM ClockworkMod then we will open it when you boot the phone. (When the phone shine brighter or some flashing LED FINGER TIGHT TO KEEP THE VOLUME DOWN BUTTON AND HOLD briefly) This should open the recovery console CWM.
6º. Now with the volume knob go to Backup / Restore. Hold down the middle button to enter the option. (Choose Backup) just wait a bit and BACKUP YOUR READY NOW IS READY.
7º. Restart the phone.
8º. Now a lot of attention. We will install the kernel. First of all you need to have the drivers installed ADB; So here's the link: http://www.4shared.com/zip/2KEB9taN/Android_ADB_Interface.html
9º. Now plug the phone into fastboot MODE. is vol + and connect usb cable. Blue LED must be connected. Once that's done your computer will start looking for drivers and will not find ... Then Extract the ADB drivers into a Folder and indicate to the drivers downloaded. This should work. If you are having trouble installing the drivers ADB. I recommend you download a program called Driver Identifier. To locate the driver.
10º. Now with the drivers already instaldos We Correctly Download the program called Flash Tools.
11º. Open the program Flash Tools. After clicking on the radius and choose MODE Fastboot. Not FlashBoot NOT CONFUSE. Leave the phone connected in mass storage mode. Now in clice Reboot into fastboot mode (via Fastboot) Note If you want to connect in Manual mode Fastboot can be connected normally.
12º. Now comes the most decisive moment of all :victory: ... You sure which kernel will apply. For if you apply some kernel Wrong at Risk of Damaging the Machine there only using an Advanced Backup has been done to resurrect.
13º. In my case my Mobile Live With WT19 is a Walkman So I will choose the Kernel Kamarush to show in this tutorial. Link to Kernel http://forum.xda-developers.com/showthread.php?t=1709032
TIP. BEFORE YOU HAVE A ROM A CHOICE IN MEMORY CARD. IN MY CASE TO U.S. USING THE LINK REAL ICS V5 http://forum.xda-developers.com/showthread.php?t=1707876:laugh:
14º. In the Flash Tools Click Select Kernel to Flash. Go up the file you Kernel for Low LWW Live With Walkman. Once you have the absolute certainty that the Kernel is right ok just take two clicks and it already in the kernel will install automatic a process is really fast.
15º. Now when the phone started so get in CWM.
16º. Now you need to do a reset FULL. First MAKE TO DO a FACTORY RESET AFTER A WIPE CACHE PARTITION. GO TO ADVANCED TO CHOOSE AND WIPE Dalvik CACHE.
17º. Then come back and go to install zip from sdcard. Choose choose zip from sdcard.
18º. Now go to the folder that has the ROM. done so just follow the installation procedures is an aroma "Do not clear it does not change anything already WT19 is defined as the first. Do not change anything in the options wipe.
19º. Done it now when you return to the CWM modules you need to install the WIFI to work. Link http://www.4shared.com/zip/c3qIfOdP/new_wifi_modules.html?
Installing is the same as the ROM.
20 °. Once that's done just restart your phone and you're ready. Easy Bad is not the only the beginning you have to install the drivers and ADB CWM for even those who do not have.
THIS IS OPTIONAL.
Fix Accelerometer "ICS" http://www.4shared.com/zip/w82KRrKc/Fix_Accelerometer_LWW.html?
To leave after boot a little faster. http://www.4shared.com/zip/zEQNj-ek/SlaidyBoost-B1_SGS_By_Slaid480.html?
Thema Bacana.
http://www.4shared.com/zip/L0cpG0-V/Themes.html?
Done.
After all that, you leave a thank you.
My Device. [email protected] ICS v5
Kernel: Kamarush.
: D
Thanks to all staff of the XDA tutorial that contributes to my being.
.
Go to Post 2
Some add-ons.
To make more custom than it already is....
Notification Bar Transparent icons and more personalized
Apply the first modification; NEW Nice_Notification_Toggles_For_ICS.zip. http://www.mediafire.com/?awjo5isfkb9nmpi
Then disconnect and reconnect the device again in order CWM.
After applying the Second Amendment, with Transparent statusbar toggles.zip http://www.mediafire.com/?h8b64idzy556xd3
Always remember to have backup. causo act done to a problem.
If you're in trouble then refer to our friend who has provided such work
http://forum.xda-developers.com/showthread.php?t=1690037
am I completely blind or there really isn't any disclaimer that you have to unlock your bootloader to flash custom kernels?
can you play deatrigger n real ics
Thanks For the reply.
najodleglejszy said:
am I completely blind or there really isn't any disclaimer that you have to unlock your bootloader to flash custom kernels?
Click to expand...
Click to collapse
I did not add unlocking the bootloader I have not found necessary. Because there are already Topics unlock your bootloader. If you think I need a Tutorial Add active before Unlock this Topic. I do
No Problem for Games
trantiena10 said:
can you play deatrigger n real ics
Click to expand...
Click to collapse
i'm play deadtrigger.
Perfect runs very smooth and no lag. Add active you need a little overclocking can leave with 1600 Max and 1000 Min. From to play hard and not spend so much battery. Optimal Real ICS ROM V5.1. With some Fix
Thanks for this tutorial!
God, i remember when i didn't flash kernel and when i had to do all this **** to be root and have CWM...
sounds good tht TUT
eltonpestana said:
I did not add unlocking the bootloader I have not found necessary. Because there are already Topics unlock your bootloader. If you think I need a Tutorial Add active before Unlock this Topic. I do
Click to expand...
Click to collapse
no need to put the full tutorial, you could just write that before flashing a custom kernel you have to have your bootloader unlocked, and paste the link to this topic: http://forum.xda-developers.com/showthread.php?t=1730874
najodleglejszy said:
no need to put the full tutorial, you could just write that before flashing a custom kernel you have to have your bootloader unlocked, and paste the link to this topic: http://forum.xda-developers.com/showthread.php?t=1730874
Click to expand...
Click to collapse
Thanks for the tip
excuse me,i just bought this phone.i want to do everything i did to my previous xperia:X8.Xperia X8 had a manufacture date problem
does this phone have it too?what is the danger zone?does it exist?
at x8 11w28 or older is hard brick.can this phone be 100% secure unlocked?or is there any risk?please.
shadik555 said:
excuse me,i just bought this phone.i want to do everything i did to my previous xperia:X8.Xperia X8 had a manufacture date problem
does this phone have it too?what is the danger zone?does it exist?
at x8 11w28 or older is hard brick.can this phone be 100% secure unlocked?or is there any risk?please.
Click to expand...
Click to collapse
I have not tested the method of test point, but it seems safe. If the person does not want to risk connecting something wrong. You can try to follow in the footsteps of Sony http://unlockbootloader.sonymobile.com/ according to your model. In my point of view I prefer methadone plus Sony's command in Ms Dos. Regarding the problem of manufacturing data can rest assured that no problems have at least the Sony because methadone is a specific code. Now as to the test point can not guarantee. In my view these quiet line Xperia handsets are very strong. These devices are actually very good.
eltonpestana said:
I have not tested the method of test point, but it seems safe. If the person does not want to risk connecting something wrong. You can try to follow in the footsteps of Sony http://unlockbootloader.sonymobile.com/ according to your model. In my point of view I prefer methadone plus Sony's command in Ms Dos. Regarding the problem of manufacturing data can rest assured that no problems have at least the Sony because methadone is a specific code. Now as to the test point can not guarantee. In my view these quiet line Xperia handsets are very strong. These devices are actually very good.
Click to expand...
Click to collapse
but that way they will know i unlocked my bl and my warranty will be torn.because they know my phones IMEI.they report that to the centers and they know my phone doesnt have warranty even tho i relocked,stock kernel,stock rom,no root
EDIT
and i saw on other thread that i must downgrade to gb to root the phone.is it true?
shadik555 said:
but that way they will know i unlocked my bl and my warranty will be torn.because they know my phones IMEI.they report that to the centers and they know my phone doesnt have warranty even tho i relocked,stock kernel,stock rom,no root
EDIT
and i saw on other thread that i must downgrade to gb to root the phone.is it true?
Click to expand...
Click to collapse
Yes, you can't root your device on ICS directly, you have to downgrade if you don't want to unlock your bootloader. Everything is here: http://forum.xda-developers.com/showthread.php?t=1695514
[Q]
shadik555 said:
excuse me,i just bought this phone.i want to do everything i did to my previous xperia:X8.Xperia X8 had a manufacture date problem
does this phone have it too?what is the danger zone?does it exist?
at x8 11w28 or older is hard brick.can this phone be 100% secure unlocked?or is there any risk?please.
Click to expand...
Click to collapse
managed to do what you wished?
real ICS on locked bootloader?
hi all,
my device- sony ericsson wt19i LWW
OS- ICS 4.0.4
build no.- 0.431
root- yes
bootloader- locked.
Is it necessary to unlock bootloader to install CWM?????:silly:
I just want to know If I can install real ICS rom on my fone?
if yes,should I must install some kernel before???
Please help me with this !!!!!
very nice tut tnx! :good:
cool
tany with walkman said:
hi all,
my device- sony ericsson wt19i LWW
OS- ICS 4.0.4
build no.- 0.431
root- yes
bootloader- locked.
Is it necessary to unlock bootloader to install CWM?????:silly:
I just want to know If I can install real ICS rom on my fone?
if yes,should I must install some kernel before???
Please help me with this !!!!!
Click to expand...
Click to collapse
No need to unlock the bootloader to install CWM. However you will not get to modify your kernel. Cause to modify kernel you must have unlocked Bootloader. Installs CWM puts your phone in Debug mode and apply the. Bat according to your device model http://www.4shared.com/rar/qZQbLbdc/CWM-Install.html?
The next step you will have CWM.
Now you want to unlock your bootloader? you must use the means of unlocking the Sony the best way http://unlockbootloader.sonymobile.com/
After unlocking your bootloader. Then everything gets easier. Despois to unlock your bootloader. When you apply the Kernel it will come with CWM already built there then just do a full wipe and then apply the ROM to taste.
update the links above plsss... i want to install custom rom like Real Ics..but i'm not sure what kind of kerner it would fit in my LWW WT19i..can you post the link of the kerner ang Real ICS here so that i can install custom rom..thnx!
Great Tutorial, mate :good:
---------- Post added at 02:46 PM ---------- Previous post was at 02:08 PM ----------
tsunamixtreme said:
update the links above plsss... i want to install custom rom like Real Ics..but i'm not sure what kind of kerner it would fit in my LWW WT19i..can you post the link of the kerner ang Real ICS here so that i can install custom rom..thnx!
Click to expand...
Click to collapse
Maybe this would help you, mate
All Roms and Kernels Sorted & Updated: http://forum.xda-developers.com/showthread.php?t=1887855
--->Real ICS
*Real ICS r5.2: http://forum.xda-developers.com/showthread.php?t=1707876
*Real ICS Lite r4: http://forum.xda-developers.com/showthread.php?t=1739569
--->Kernels
*MESA: http://forum.xda-developers.com/showthread.php?t=1715679
*KRsH: http://forum.xda-developers.com/showthread.php?t=1709032
*KernelPanic: http://forum.xda-developers.com/showthread.php?t=1861905
*Rage: http://forum.xda-developers.com/showthread.php?t=1398910 (Both GB & ICS)
Hi All,
I am looking for a tutorial that explains how to root the cellphone build under 32.2.a.0.305 running with Marshmallow. I haven't found any topic that state someone succeeded to root this one. Any chance someone can give me some guidance. On some other website it is mentionned that we cannot root it for the moment. So I was thinking maybe downgrade it and go back to Lollipop? But even for that I need some guidance.
Thanks in advance.
Cheers.
francisci said:
Hi All,
I am looking for a tutorial that explains how to root the cellphone build under 32.2.a.0.305 running with Marshmallow. I haven't found any topic that state someone succeeded to root this one. Any chance someone can give me some guidance. On some other website it is mentionned that we cannot root it for the moment. So I was thinking maybe downgrade it and go back to Lollipop? But even for that I need some guidance.
Thanks in advance.
Cheers.
Click to expand...
Click to collapse
Theres a perfectly detailed guide in general section , you should downgrade to lolipop so you can use the temp root tool to back up drm keys before unlocking the bootloader , but if you dont care about drm keys , you can in fact just skip to the boorloader unlock part and root. Its so simple , but i would suggest going through the whole proccess and back up your drm keys cuz once lost , forever lost so ... Yah
madshark2009 said:
Theres a perfectly detailed guide in general section , you should downgrade to lolipop so you can use the temp root tool to back up drm keys before unlocking the bootloader , but if you dont care about drm keys , you can in fact just skip to the boorloader unlock part and root. Its so simple , but i would suggest going through the whole proccess and back up your drm keys cuz once lost , forever lost so ... Yah
Click to expand...
Click to collapse
Hi Madshark
Thanks for your prompt reply. Appreciate it.
I'm at rookie level in terms or rooting smartphone, so I don't know even the basics. Can you send me the link of the "detailed guide" and also explain me what does the "drm keys" stand for?
francisci said:
Hi Madshark
Thanks for your prompt reply. Appreciate it.
I'm at rookie level in terms or rooting smartphone, so I don't know even the basics. Can you send me the link of the "detailed guide" and also explain me what does the "drm keys" stand for?
Click to expand...
Click to collapse
this is the link to the post that I used and followed its instructions to root my phone personally.
http://forum.xda-developers.com/z5-compact/general/how-to-backup-restore-ta-partition-root-t3479532
if you lose DRM keys (and that happens when unlocking the bootloader) then some functions in the device will stop working like Bravia engine, Track ID, etc and on our z5 compact some say even stock camera stops from working, and when you lose those keys you can NEVER get them back because each device has its OWN TA partition that includes its OWN DRM keys and no other device has the same so thats why each and every one who owns an Xperia device must perform this TA backup in case they ever wanted to get back to stock (unroot and relock bootloader) they can restore these keys and functions to factory functionality. if you dont back them up and unlocked the boot loader then you will never get some functions to get back to working properly if you ever wanted to get back to stock and relock your boot loader!
However; there is some thing that is called DRM fix in certain roms that when you install these roms, you will not feel like you lost your functions because they already include a fix that behaves like the DRM keys.
still, losing your DRM keys will cause your device to lose its warranty and if you didnt back them up then you will never get it back even if you relocked your bootloader. so I personally backed them up because my device has a 2 year warranty and I dont want to waste them if any thing goes wrong I would restore them and send it to get fixed.
yet the only problem is warranty to me so if you have no warranty or dont care about it you can skip the back up process but yet again I dont like taking chances so just back them up its a 2 minute thing.
and I say again, all stock based roms in this Z5 compact forum have drm fix...
and to give you my personal opinion I dont like the Xperia z5 compact rooted because as I saw, there is so little roms and so little kernel variations and all the stable roms are based on stock MM firmware and CM roms arent fully stable yet , (they are but they have bugs that I hate having) and I only rooted so i can increase the volume of my phone speakers and headset and increase the strength of the torch but it all turns out to be that all sound mods have bugs and torch mod only work properly on any thing but STOCK ftf but any thing besides stock ftf isnt fully stable so I dont see any point in rooting this device I so regret buying it I should have checked how little the modifications are that can be made on it I owned Z2 and HTC devices in the past and boy! if I wanted to try different things every day for the past 2 years I wouldnt have finished by now there is sooo much to test and so much to try and to customize ...
the only rom that can be customized and can be enjoyed as much that we have is Kryptonian - the rom of awesomeness!
I hope I was helpful
madshark2009 said:
this is the link to the post that I used and followed its instructions to root my phone personally.
http://forum.xda-developers.com/z5-compact/general/how-to-backup-restore-ta-partition-root-t3479532
if you lose DRM keys (and that happens when unlocking the bootloader) then some functions in the device will stop working like Bravia engine, Track ID, etc and on our z5 compact some say even stock camera stops from working, and when you lose those keys you can NEVER get them back because each device has its OWN TA partition that includes its OWN DRM keys and no other device has the same so thats why each and every one who owns an Xperia device must perform this TA backup in case they ever wanted to get back to stock (unroot and relock bootloader) they can restore these keys and functions to factory functionality. if you dont back them up and unlocked the boot loader then you will never get some functions to get back to working properly if you ever wanted to get back to stock and relock your boot loader!
However; there is some thing that is called DRM fix in certain roms that when you install these roms, you will not feel like you lost your functions because they already include a fix that behaves like the DRM keys.
still, losing your DRM keys will cause your device to lose its warranty and if you didnt back them up then you will never get it back even if you relocked your bootloader. so I personally backed them up because my device has a 2 year warranty and I dont want to waste them if any thing goes wrong I would restore them and send it to get fixed.
yet the only problem is warranty to me so if you have no warranty or dont care about it you can skip the back up process but yet again I dont like taking chances so just back them up its a 2 minute thing.
and I say again, all stock based roms in this Z5 compact forum have drm fix...
and to give you my personal opinion I dont like the Xperia z5 compact rooted because as I saw, there is so little roms and so little kernel variations and all the stable roms are based on stock MM firmware and CM roms arent fully stable yet , (they are but they have bugs that I hate having) and I only rooted so i can increase the volume of my phone speakers and headset and increase the strength of the torch but it all turns out to be that all sound mods have bugs and torch mod only work properly on any thing but STOCK ftf but any thing besides stock ftf isnt fully stable so I dont see any point in rooting this device I so regret buying it I should have checked how little the modifications are that can be made on it I owned Z2 and HTC devices in the past and boy! if I wanted to try different things every day for the past 2 years I wouldnt have finished by now there is sooo much to test and so much to try and to customize ...
the only rom that can be customized and can be enjoyed as much that we have is Kryptonian - the rom of awesomeness!
I hope I was helpful
Click to expand...
Click to collapse
Very helpful ! Thanks v much - I'll let you know if I succeed!
Ok, 2 more things.
Probably the most important: warranty has nothing to do with DRM keys, unlocked bootloader or what more. Sony is not/never gonna repair smartphones when there're problems caused by custom ROM or kernel, they're not gonna fix a bootloop caused by a bad flashing procedure and so on. But it's not true that you're automatically losing warranty by unlocking bootloader or getting root access.
Next to that, you don't have to go through that process of backing up your own TA, if you don't want. It's much easier to root and flash a kernel with DRM keys patched. Procedure to root is really simple. Flash new rom, unlock bootloader, fastboot to flash compatible twrp , flash supersu, flash modded kernel, done. There're already quite some tutorials to guide you through this proces.
--jenana-- said:
Ok, 2 more things.
Probably the most important: warranty has nothing to do with DRM keys, unlocked bootloader or what more. Sony is not/never gonna repair smartphones when there're problems caused by custom ROM or kernel, they're not gonna fix a bootloop caused by a bad flashing procedure and so on. But it's not true that you're automatically losing warranty by unlocking bootloader or getting root access.
Next to that, you don't have to go through that process of backing up your own TA, if you don't want. It's much easier to root and flash a kernel with DRM keys patched. Procedure to root is really simple. Flash new rom, unlock bootloader, fastboot to flash compatible twrp , flash supersu, flash modded kernel, done. There're already quite some tutorials to guide you through this proces.
Click to expand...
Click to collapse
Yah well if the bootloader is unlocked and the system has modification on it , they have every right to refuse fixing it for you because its hard to prove that what bricked the device isnt some modification that you made... Unless they have a really good heart , i had a z2 before and it was rooted but the ftf on it was custom but was on it for like 7 months and all the mods were working properly untill all of the sudden it wont turn on so they told me that what i.did caused it but i didnt do anything wrong i know they lying but can u prove it!? No..
Hi guys,
How do I flash the boot.img using cmd and fastboot ?
francisci said:
Hi guys,
How do I flash the boot.img using cmd and fastboot ?
Click to expand...
Click to collapse
first you gotta download ADB folder
you can find it here if im not wrong : http://forum.xda-developers.com/showthread.php?t=2588979
then place the adb folder in C:\
I think it automatically place it there when installing so no need to do that if so
2. go to cmd (start - type in CMD) and once it launches direct it to where the adb folder is "cd c:\adb" without the quotes of course
3. to flash boot type in "fastboot flash boot boot.img" without quotes and one space step between words only.
4. to flash recovert just type is "fastboot flash recovery "recovery name".img wihtout the quotes and copy recovery name exactly the way it is.
that it
keep in mind that any time you want to flash any thing , that thing must be inside the adb folder for example ,boot.img file must be there in the adb folder with all the other files when installing adb, and also recovery and every other thing you want to flash using fastboot.
hope this is helpful.
Hi madshark, thanks again for your help. I have been able to flash the boot img and then rename twrp into recovery and flash it as well.
Now I'm stuck the device cannot reboot so I cannot transfert the SuperSU files in to the device...
And when I type adb devices in cmd, it do not mention the device ! Seems that I'm facing an issue.
francisci said:
Hi madshark, thanks again for your help. I have been able to flash the boot img and then rename twrp into recovery and flash it as well.
Now I'm stuck the device cannot reboot so I cannot transfert the SuperSU files in to the device...
And when I type adb devices in cmd, it do not mention the device ! Seems that I'm facing an issue.
Click to expand...
Click to collapse
well youre new, mistakes like these happen Ive been there, sorry for the late reply XDA isnt giving me notification
any way, make sure after backup TA (which is on lolipop firmware) you gotta get back to original .305 firmware (MM) the process of you getting back to lolipop in the first place is so you can use Ivoyroot tool for temporary root so you can backup your TA partition, once that is done you must get back to .305 because you are flashing a kernel (boot.img) that is for build .305 I guess the guide guy didnt mention this?
second when I said copy recovery name as it is I meant what recovery name you have for example
fastboot flash recovery twrp-3.0.2-0-E5823-20160417.img
thats my recovery name the one that I downloaded, yours might say some thing else its OK I meant copy YOUR recovery name to CMD the way it is exactly in the ADB folder
and now your stuck, if your bootloader is already unlocked, just flash .305 firmware with flashtool the same way you flashed the lolipop firmware, once that is done, do the first boot settings and once device is launched into the software , just flash boot again
make sure you follow instructions to the POINT, so you gotta turn of your phone, press the volume up button keep it pressed while connecting your phone to the PC and flash boot and recovery and thats it
and after youre done with this process , then you turn on your phone connect it to your PC and place the superSU zip file in it and then go to recovery and flash it
adb isnt recognizing your device?
thats weird if you just connect your device nothing will happen, so you turn off your phone and press the volume up button and connect it, (thats how you enter fastboot mode) and if still doesnt recognize then do what I told you to do already and see what happens next
keep me updated and if its urgent just send me a PM because I dont see notification otherwise...
Thanks Madshark for your help, it has finally worked!