Database Users

[GUIDE 25/02/2012]UK ONLY /Orange/ T-mobile – ROOTING, UNLOCKING BOOTLOADER

I have updated this guide as I have a new replacement from t-mobile. This guide was based on my previous atrix which was running froyo (2.2.2) This time I have applied OTA 45.21.2.Mb860.T-mobile.en.gb and everything works perfect so if you have updated your phone to 2.3.4 then you can use this guide as well
I have decided to create this thread as I have seen many people confused about the difference between At&t phones and their UK ones. This thread will help you make the decision whether you want to hack your phone or not. I own T-mobile UK Atrix and whatever I have done worked perfectly for me. I’m not responsible for any bricks. You doing this on your own risk – good news is that no one (UK) had their mobile bricked. ALL CREDITS GOES TO DEVELOPERS AND OTHERS THAT CREATED SIMILAR THREATS – THANKS
ROOTING – If you running froyo (2.2.2) I have used gingerbreak method which is very easy:
Code:
1. Download Gingerbreak.exe from here: [url]http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1046626&v=1&libid=1311795059566&out=http%3A%2F%2Fbandbinnovations.com%2Fxda%2FGingerBreak.exe&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D997%26order%3Ddesc%26page%3D4&title=%5BHOWTO%5D%20Easy%20Root%201.5.7%20%26%201.83%20using%20GingerBreak%20-%20xda-developers&txt=http%3A%2F%2Fbandbinnovations.com%2Fxda%2FGingerBreak.exe[/url]
2. Make sure you have got debugging mode ON(settingsApplications Development) and you have installed drivers for your atrix
3. Run Gingerbreak.exe on your pc
4. In your phone you will find new app called gingerbreak – run it and select root. Mobile will reboot itself once is done.
5. Congratulation you are rooted.
NOTICE: You need to have External SD Card and also be aware that rooting this way will format your internal storage.
ROOTING – If you running gingerbread (2.3.4) use superoneclick (http://forum.xda-developers.com/showthread.php?t=803682) and fallow the instructions on the original thread. Very easy way.
If you want to try ANY Custom ROM you need to Unlock your Bootloader:
Code:
1. You need to download and install RDS lite on your PC: [url]http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277[/url]
2. Download and extract IHOP_Bell.rar: [url]http://diamantephoto.com/IHOP_Bell.rar[/url]
3. Download and extract Fastboot tools [url]http://gititbit.ch/FAST[/url]
4. Power down your Motorola Atrix
5. Take out your microSD card and SIM card for the flashing process
6. While turning the phone on, hold the Volume Up button until it acknowledges RSD
7. Your device will say “Starting RSD protocol support”
8. Run “RSD Lite” on your computer
9. Press the “. . .” button next to the box labeled “Filename”
10. Load up the SBF file – IHOP_Bell.sbf
11. Plug your device into your computer
12. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
13. Press the “Start” button
14. Be patient while the phone reboots. It will take a long time.
15. Open and extract the Fastboot package from above
16. Open a command prompt window
a. On Windows, press Start and type “cmd” then press the enter button
17. Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example: cd C:\Users\Kenneth\Desktop\fastboot-package)
a. cd your directory here
18. Power down your Atrix device
19. Hold the power button and the downward volume button until you see “Fastboot”
20. Let go of the buttons and press the upward volume button once
21. You will now see “Starting Fastboot protocol support”
22. Plug your device into a USB port in the back slot of your computer
a. Front slots sometimes do not have enough power to stay connected to the device.
23. Type the following command:
a. fastboot oem unlock
24. You will now receive a warning along with a unique device ID
25. Type the following commands using your unique device ID in place of the ####:
a. fastboot oem unlock ####
b. fastboot reboot
26. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
I recommend to install romracer's Recovery : http://forum.xda-developers.com/showthread.php?t=1204500.
Instalation:
Code:
$ fastboot devices
TA20700KXH fastboot
$ fastboot erase recovery
erasing 'recovery'... OKAY [ 0.741s]
$ fastboot flash recovery recovery.img
sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]
The reason I recommend this recovery is because the official clockwork recovery doesn't support external sdcard (bug?). If this doesn't bother you then you can download Rom manager from market and install official recovery.
Most of the roms have unified kernel which means you don't need to apply anything after installation. This includes roms like aura, the dark side, cyanogen mod.
However if you do have issues with memory then download kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1156040

Thanks for this - thats my night sorted

Very useful and thorough guide. Thanks a lot Mr Foka. I left you a "thanks" btw.

thank you so much! just going to unlock my orange atrix
Sent from my MB860 using XDA Premium App

Jibraldor said:
Very useful and thorough guide. Thanks a lot Mr Foka. I left you a "thanks" btw.
Click to expand...
Click to collapse
That's very kind. Thanks

Hi there,
sorry, a quick question regards to the custom ROMS, you mentioned if I am going to apply the AT&T ROMs, I need to apply custom kernels,
Foka002 said:
You can now install ANY Custom ROM. However if you want to install ROM That is designed for AT&T you will have to apply FIXED Kernel for international (faux’s or eveal kernels working excellent for our devices - http://forum.xda-developers.com/showthread.php?t=1169409 or http://forum.xda-developers.com/showthread.php?t=1156040)
Click to expand...
Click to collapse
but in eval-'s thread, he mentioned:
I suspect these boot.img will 'fix' RAM for unlocked internationals on any Gingerbread 2.3.x build (only), but this as faux123 helpfully points out, your modules must match (important for wifi, vpn) ! So for now, these boot.img with quick & dirty RAM fix are only for this Orange FR 2.3.4 system.img!! (Unless you want to copy around dhd.ko and parts of /system/lib/hw between /systems...)
Click to expand...
Click to collapse
So can I just apply his kernel on the AT&T firmware?
Cheers,

Well I tried eval kernel few times and long time ago. For every rom I had it I used faux kernel so it's safer to use it with recent roms.
Sent from Motorola Atrix

Hi thanks for the time and effort but I was hoping someone could help me.Trying to follow the guide but having trouble with two parts.Firstly when running pudding through rsd how long exactly do you leave it?It says to leave it at android lockscreen but rsd dhows as not finished like 38% rebooting at this time/Also when to connect or disconnect is confusing as I read a guide previously to yours am not sure if phone gets disconnected after rsd?Lastly and I think my most serious problem is that I cant get the fastboot command to work.It will either say unable to find the path specified or no command on internal or external etc.Any ideas?Thanks

Great guide! Thanks for putting this together.

So correct me if im wrong but I can follow this guide, and put on gingerbread on my orange ATRIX and it will work fine?!?!?!?
Also once the official update hits UK can I just install that?
Great work btw
Sent from my MB860 using XDA App

Just to ask / add
There is going to be an official Orange OTA update isnt there? I could do it this way but for a change want to try it the offical way

scotty7910 said:
Hi thanks for the time and effort but I was hoping someone could help me.Trying to follow the guide but having trouble with two parts.Firstly when running pudding through rsd how long exactly do you leave it?It says to leave it at android lockscreen but rsd dhows as not finished like 38% rebooting at this time/Also when to connect or disconnect is confusing as I read a guide previously to yours am not sure if phone gets disconnected after rsd?Lastly and I think my most serious problem is that I cant get the fastboot command to work.It will either say unable to find the path specified or no command on internal or external etc.Any ideas?Thanks
Click to expand...
Click to collapse
In order to use fastboot you need to have motorola drivers installed. Im not sure about eds but if your device is recognised then it is fine. Im not sure about waiting time in rsd but if you did fallow this guide step by step you shouldn't have any problems.
Roberts56
Yes you will be able to flash gingerbread but you won't be able to use official OTA unless you downgrade to 2.2.2 using fruitcake method. The thing is if you want to play with custom roms then there is no point in waiting for official release because its not going to be any better than any rom we've got now. Just keep in mind once you unlock your bootloader you will lose warranty.
Uk OTA is coming for sure but I have no idea when. Rumours says in sep/oct

Boot screen
Hi
After flashing IHOP_BELL, everytime I reboot I get a menu instead of Motorola Logo at beginning. Is that normal?? When I leave it there it will boot Android and will show the Motorola Logo.
It looks like this:
http://2.bp.blogspot.com/-dPOywn12xbg/Th6albF5xPI/AAAAAAAAAGw/BStIYOa7B_A/s1600/11.JPG
Thanks for your help

R3wt3d said:
Hi
After flashing IHOP_BELL, everytime I reboot I get a menu instead of Motorola Logo at beginning. Is that normal?? When I leave it there it will boot Android and will show the Motorola Logo.
It looks like this:
http://2.bp.blogspot.com/-dPOywn12xbg/Th6albF5xPI/AAAAAAAAAGw/BStIYOa7B_A/s1600/11.JPG
Thanks for your help
Click to expand...
Click to collapse
Strange...I've never seen this before. Can anyone tell why is that ?

hmm it's not normal then?
Any idea if I could overwrite with IHOP_BELL again downloaded freshly from xda?
I downloaded it from here.
http://diamantephoto.com/IHOP_Bell.rar
thanks

R3wt3d said:
hmm it's not normal then?
Any idea if I could overwrite with IHOP_BELL again downloaded freshly from xda?
I downloaded it from here.
http://diamantephoto.com/IHOP_Bell.rar
thanks
Click to expand...
Click to collapse
Notice of on your photo it says that your phone is unlocked! Is that right?
Did you flash a recovery? Romracer's I hear is good at the moment.
Then did you flash a rom? As says no OS DETECTED!
Can recommend http://forum.xda-developers.com/showthread.php?t=1169409
But you can use fruitcake s
Swyped from "Mount" Olympus

nitrox1 said:
Notice of on your photo it says that your phone is unlocked! Is that right?
Did you flash a recovery? Romracer's I hear is good at the moment.
Then did you flash a rom? As says no OS DETECTED!
Can recommend http://forum.xda-developers.com/showthread.php?t=1169409
But you can use fruitcake s
Swyped from "Mount" Olympus
Click to expand...
Click to collapse
yeah it's unlocked. and after that menu I flashed ORFR boot system webtop
U guys never seen that menu? I got it right after flashing sbf...well during sbf flashing.

R3wt3d said:
yeah it's unlocked. and after that menu I flashed ORFR boot system webtop
U guys never seen that menu? I got it right after flashing sbf...well during sbf flashing.
Click to expand...
Click to collapse
Did you flash the rom with it too, as webtop is a separate part?
Never seen that menu, but never tried to boot just after ihop either though, as has no rom as party of it, check out size of the file, and size of a normal sbf.
Swyped from "Mount" Olympus

I think this is soft brick...Is this UK atrix ??

Noob questions
Do I need to root before I flash this ROM? Because I don't have an SD card I'm a bit confused if I can do this or not. Once flashed to Orange France 2.3.4, if the OTA comes through what should I do? Accept? Decline? I'm very doubtful that Motocrap will update us to ICS, so can we update to ICS manually if I flash right now? Finally, if I do Brick, what can I do? I don't have insurance. Can I backup to a PC? I want something that no matter what happens I can restore to. Thanks for the answers ( if I get any )
Kartik

[Q] Probs installing Cyanogenmod 7.1 on x8(E15i)

Hey.
I'm having difficulties with new cyanogenmod 7.1
I Followed different tutorials and none of them helped me.
I started with stock 2.1 rom and did all the unlocking bootlader stuff , then installed custom kernel and managed to install cyanogenmod 7.1 but then occurred a funny thing . There was only FreeXperia logo showing up, nothing else, and it rebooted all the time. Then I flashed stock rom again and tried to understand what's wrong and tried to use different kernels and nothing.
So my question is. Is there anything I'm missing here?
Henri.

Full wipe after you install rom.
Dot forget to make backups first.

about that...
i always do full wipe after installing roms, so it has to be something else.
Thnks anyway..
But after browsing several topics in XDA forum I saw that I'm not only one with the problem.
If anybody has had the problems like I do and got the solutions, every kind of tips are welcome.

Thread closed
I got it all working, but I don't know what was the reason, because, I just did the whole thing again about three or four times, and then it just booted and worked.

I never could install Cyanogenmod in my phone... could you?

Hey!!!
I could write a total working tutorial how I managed to get to work everything, but it takes time, so if you want tutorial send me private message , so I create it for you.
Henri

Does wifi and/or 3G work for you longer then 15 minutes?

No, but at the moment I'm using RC1 flawlessly.
Sent from my E15i using XDA App

coffee-break said:
I could write a total working tutorial how I managed to get to work everything, but it takes time, so if you want tutorial send me private message , so I create it for you.
Henri
Click to expand...
Click to collapse
umm..why not post it publicly man ? It will be useful for everyone including myself.

Would also like that tutorial

ok,
i'm gonna post it here after finishing it.

So, the wanted tutorial is here!
Firstly it's for xperia x8(E15i) to be superclear.
I'm gonna put that tutorial into steps.
STEP 1
You need to have stock 2.1 rom with baseband XXX015 , if you don't have it, then go to Sony Ericsson's webpage and download the upload service and flash it back into your phone.
STEP 2
You phone has to be rooted. Easieset way is using Superoneclick(sorry, i'm not gonna provide the link, because it's just google-ing thing to you who need rooting program)
STEP 3
Now, everything comes to the unlocking process for bootloader. there is also tutorial how to succeed when using s1tool and msm7227 (if you have problem, then I don't know). Try to undestand the tutorial of doing it.
S1tool is for identifying if your phone is unlocked or not.
and msm7227 is for unlocking
tut is here - LINK
I wish luck, don't brick your phone, but it's not so hard to understand tutorials if you have right phone and right tutorial.
STEP 4
I totally suggest to install stable rom. The reason is that released 7.1 has bugs and incompatibility with some phones and i haven't got wifi and 3g working , but tried different roms and kernels.
I provide links i got from deani77, big thanks to him.
You can try this link for FXP028 ROM - http://www.multiupload.com/IIWIPG1ALH
For FXP030 kernel try this link - http://hotfile.com/dl/132650338/7b17...USTOM.ftf.html
(that release is RC1 of Cyanogenmod 7.1 but I think it's the best at the moment!)
and you download all the files as usual. Rom zip package should be in the SD card's root folder, so you can easily install it after flashing kernel
STEP 5
installing is quite simple actually. You need to use flashtool that is provided with rom(link in step 3)
firstly you flash kernel. Kernel file is the one you downloaded .ftf file. You have to put that file(X8_custom.ftf) into firmware folder which is inside of flashtool folder.
Then you open flash tool and you click FLASH, then appears little window and you click ok and then you need to plug in your phone into usb while holding down back button. Your phone has to be off when you are doing that. Then flashtool identifies your phone and will flash the kernel into your phone. when everything comes smooth then you now have fxp custom kernel. it has clockworkmod recovery and you need to click several times back button when FreeXperia logo appears.
STEP 6
You have to do factory reset and format, also i suggest from advanced menu using format system.
Then you select from the recovery menu install custom zip... and you browse your rom .zip file and if everything is OK then it should display "installing update or smth" if it's done then good for you, you reboot and it should work.
IF YOU WANT GOOGLE APPS , then google the link and install it same way you did with the rom. You can do it any time.
..
So if anything is not understandable then ask. I'm not an expert or anything, I just did things like I described.
Best,
Henri.

i have still had problems with bootloop and passing md5 checksum any idea on how to fix this?

mm.. at the moment I don't know but what that md5 checksum means?

I fixed my bootloop issue when I flashed back to stock rom, then I just did all the steps I describe again (not unlocking bootloader because it was unlocked already) .. but I don't know what's really does the bootlooping thing. I just got lucky. It took me like billion hours until I got it working...

Chinese Atrix - Questions about FW, Bootloader, Root

Hi Guys!
I know, some people will hate me now because I opened a thread for that.
But the search did not help for chinese FW, so I wanna give it a try here!
I just got a chinese Atrix with the following information in settings:
System Version:45.2.14.ME860.ChinaRetail.en.CN
Android: 2.3.5
Baseband: BP_N_01.41.00R
Webtop: Unavailable
Kernel:2.6.32.9-00007-g9570040 [email protected]#2
Build number: 4.5.3-118_OLY-14
Superuser is already instaled and when i bootup the phone, "Unlocked" is shown in the upper left corner!
What I wanna know:
Is it rooted (yes of course, I think!)
Is the bootloader unlocked (never had a phone that says "unlocked" when booting up with an unlocked BL...)
Can I just flash CM9 for example or is there anything I should be aware of?
Sorry for beeing an Atrix n00b =)
And thanks for all suggestions!

The Unlocked text on the Motorola screen is an indicator that your device's boot loader is unlocked. I would recommend referencing the NOOB threads covering rooting and flashing ROMs for the rest.

Thanks for that!
But it's already rooted (super user is installed and I tried apps that need root).
What I wanted to know is, if I can just flash new roms or do I have to be cautioness, like many threads say: Don't flash back if u use build nr. xyz...

muhski said:
Thanks for that!
But it's already rooted (super user is installed and I tried apps that need root).
What I wanted to know is, if I can just flash new roms or do I have to be cautioness, like many threads say: Don't flash back if u use build nr. xyz...
Click to expand...
Click to collapse
Check if you have cwm recovery installed. If not install the latest and flash the latest version of cm9 through cwm
Sent from my MB860 running Jokersax's CM9

unlock is needed for flash custom ROM in CWM

weiyin5210 said:
unlock is needed for flash custom ROM in CWM
Click to expand...
Click to collapse
Did you read the first post?
"Superuser is already instaled and when i bootup the phone, "Unlocked" is shown in the upper left corner!"
Click to expand...
Click to collapse

Atrix 4g from Taobao 19 Apr.
Hi muhski,
I am in the same situation.
I just buy Atrix 4g from Taobao and receive it on 18 Apr.
When Gapps is not installed, I was very disappointed and call them to complain.
They ask me to send it back but I tried to get to know the phone more.
System Version:45.2.14.ME860.ChinaRetail.en.CN
Android: 2.3.5
Baseband: BP_N_01.37.00R (Yours is BP_N_01.41.00R)
Webtop: WT-1.2.0-163_11 (Yours is Unavailable)
Kernel:2.6.32.9-00007-g9570040 [email protected]#2
Build number: 4.5.3-118_OLY-14
Superuser is already installed and rooted.
Booting up the phone, "Unlocked" is shown in the upper left corner!
If you do a thorough search, you will know that to start to flash cm9, you need:
1. bootloader unlocked, machine rooted
2. clockworkMod (cwm) flashed
3. then flashing CM will be easy. Just put some zip files in root of sd card and then run ClockworkMod.
See but dun follow the cwm installation:
wiki点cyanogenmod点com/wiki/Motorola_Atrix_4G:_Full_Update_Guide
Your Atrix and mine are probably in stage 1.
Last night I tried to follow the old instruction in the link above to flash cwm.
But the fastest manner to run cwm is by installing Rom Manager instead.
Rom manager is super easy to use and I manage to get it to flash cwm in my Atrix. With cwm running, I boot from it and get cwm to flash Gapps in my Atrix.
Now I got cwm & gapps both running very well.
All my gmail, gPlay, gCalendar, gMap..... running quite well.
The next step I can make is to save cm9 zip files in the root of sd card and run cwm to flash it.
I am currently stuck like you. I wan to flash ics thru cm9 but worrying bricking Atrix. Moto may come up with ics for atrix real soon so I dun know if I want to wait.
Good luck

Sounds like you are on the right track. Once you have cwm flashed you can reboot, hold the volume down rocker as the phone reboots. Once you see another option under the "unlocked" text you can then tap the volume down rocker until you get to the recovery option, then tap the volume up rocker. This will bring up a whole new menu that you can use to clear cache, Dalvik cache and factory wipe.
When I flashed my first ROM I was very nervous that I was going to ruin my phone, but I have flash many ROMs since then some with gapps included and some that require you to flash gapps seperate. I have enjoyed many ROMs and have not run into any problems I couldn't fix by rebooting into recovery.
Good luck and enjoy the ROMs of your choice!

Hey guys!
Thanks for all your help!
First, I forgot to say, it's not the first time doing this stuff xD
It's my third android phone, so all is very similar to the Defy, but still I like to ask one time too often instead of crying about a bricked phone =)
What I have done now: Because bootloader was already open and cwm was already insalled, I could skip the hardest part and jumped right into flashing.
Ok, not really, because I updated cwm to romracers version (not really necessary, but everyone suggested it...)
Right now I'm running Neutrinos CM7 mod because other mods gave me randome reboots
First problem was: My Radio version does not work with this rom! "About phone" says "Baseband unknown".
I went crazy bcs I thought I got a broken phone from taobao, but smart as I am (hrhr) I made a nandroid backup before, flashed it back, and tadaa, with the old backup I had network connection....
So I googled a little more and found out about the Radio-Thread here.
Now I'm testing all the radios to ind the best one...
Good thing is, network connection is working now, bad thing is, it sucks my battery dry like a h**ker that gets too much money
@qqqqaa: does your radio version work with CM9?
Maybe I should try yours...

Can any of you with the Chinese ROM confirm that call recording works on your phone and if possible, do share a dump of your ROM.

[GUIDE] How to: Install CM10.2 on LOCKED bootloader [Xperia SP]

Disclaimer:
I am not to be held responsible for any actions that you take by following this guide that result in harm to your device. Sony devices are almost impossible to brick.
pre-requirements:
You're going to need the following things:
Flashtool
CWM Xperia SP Package
.266 4.3 kernel
.257 firmware
DooMLoRD easy rooting toolkit
CyanogenMod 10.2 Package & gapps
Step 1:
extract Flashtool, place the .257 firmware file in the firmwares folder and then run flashtool, flash the .257 firmware. This process could take 5-10 minutes.
To do this, click the electric bolt symbol in FlashTool, and select Flashmode, select .257 and then when the prompt says to connect your device in flashmode, power off your phone and holding volume down, plug your phone into the computer. This will then flash the files.
Turn your phone back on and enable USB debugging in android development settings.
Step 2:
Extract DooMLoRD's easy rooting toolkit and make sure that you have your phone connected and adb is enabled, while the phone is powered on run the script and this will then root your phone, do this by double clicking runme_win.bat, your phone will reboot in this process and it will be rooted.
Step 3:
Time to install a custom recovery, unpack the CWM Xperia SP package listed above. Make sure your phone is still turned on and in adb mode (USB debugging enabled) and then run install.bat from the package. You will need to accept a superuser request prompt on your phone meaning that you will need your phone screen on. Recovery is now installed.
Step 4:
Copy the CyanogenMod 10.2 package & google apps package to your phone, reboot into clockwork recovery by pressing the volume UP button once when you see the blue LED light up and feel a short vibration while your phone is booting. In CWM choose factory reset, and then install the two files we put on your phone using install zip from sd card option. Use volume rockers to navigate and power button to select options. Make sure you install CM zip then Google apps zip
Step 5:
After installing the ROM, power off your device in CWM and then connect your device in FlashMode again (hold vol down while plugging into computer) and then flash the .266 kernel only file. Reboot your phone.
Step 6:
Enjoy! You now have CyanogenMod and CWM installed on your phone, even with a locked bootloader. Recovery is now accessed with volume down.
I appreciate thanks greatly, and any issues I can help with and you can discuss them in this thread. I hope I have helped.
KeiranFTW

awesome

That. It's one good guide that anybody can follow. Just one question. Will this rom be as stable as normal cm, will it be full cm or just a stripped down version
Sent from my C5303 using Tapatalk

can this rom be flashed on ROOTED device running 4.3

zolaisugly said:
That. It's one good guide that anybody can follow. Just one question. Will this rom be as stable as normal cm, will it be full cm or just a stripped down version
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
I don't see why it can't be as stable as normal CM.. The only thing that isn't working at the moment is GPS, everything else to be honest it runs smoother than stock.
I'm going to work on getting AOKP to work if they have a compilable 4.3 branch. I'm also going to try and encourage ROM devs to add locked bootloader support and I shall show them how
pchetan2 said:
can this rom be flashed on ROOTED device running 4.3
Click to expand...
Click to collapse
Just follow the steps, if you have CWM installed on your XSP with 4.3 already all you need to do is flash the ROM in CWM nothing else..
I posted method for 4.1.2 because I'm presuming the user does not have root, and this is only rootable firmware.
Sent from my C5303 using Tapatalk

Awesome job to able get this rom on my lock xperia sp bro. And also am looking forward from you ,that you will bring other roms on my lock xperia sp which is the best phone ever.:good:

To have root on CM I need to flash SuFix as in existenz?

I have never used cm roms before...when the gps. Is fixed I will try rhis out,sadly I use gps alot due to work and driving into towns I don't know etc...
(Q) Due to limited space on sp can we use apps like link2sd and foldermount.
Or does the scripts not run.
Sent from my C5303 using Tapatalk

radeon6002 said:
To have root on CM I need to flash SuFix as in existenz?
Click to expand...
Click to collapse
Nope, su binary is included and root is already in the ROM.
CyanogenMod also features its own root permissions app (Settings -> Superuser) so you dont even need to install supersu or any equivalent, it works out the box.
zolaisugly said:
I have never used cm roms before...when the gps. Is fixed I will try rhis out,sadly I use gps alot due to work and driving into towns I don't know etc...
(Q) Due to limited space on sp can we use apps like link2sd and foldermount.
Or does the scripts not run.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Theoretically yeah, these scripts should run. I will look into it soon
Sent from my C5303 using Tapatalk

I had just posted a thank-you in another thread for the same - outstanding work. A big thank-you from one who prefer not to touch the BL
And thanks for the lucid instructions. Will download the stuff when I am off work.:good:

yeah i did it succesfully ..need to wipe data and factory reset .then install the rom and gapps....... thank you a lot

Note: the link to the 257 firmware is dead.
[not applicable to those who already rooted their phones ]
EDIT:
Just installed the rom. Also 'upgrage' kernel to 266 (had preferred 254 as it was faster, but with this new rom...)
Question:
a. could one just live with 254 kernel instead of flashing 266 at the end?
b. Now that I have flashed 266, could I re-flash to downgrade (just the kernel) to 254 later on?
Fun time - rom is working on my device.
Thanks a million!

headache59 said:
Note: the link to the 257 firmware is dead.
[not applicable to those who already rooted their phones ]
EDIT:
Just installed the rom. Also 'upgrage' kernel to 266 (had preferred 254 as it was faster, but with this new rom...)
Question:
a. could one just live with 254 kernel instead of flashing 266 at the end?
b. Now that I have flashed 266, could I re-flash to downgrade (just the kernel) to 254 later on?
Fun time - rom is working on my device.
Thanks a million!
Click to expand...
Click to collapse
If you flashed the .254 kernel your Phone won't boot...you just get a bootloop. You need. 266
don't downgrade kernel without downgrading rom as well.
Sent from my C5303 using Tapatalk

Great work by @bagyusz and @KeiranFTW for the initial spark idea. I thot all was lost when i got vendorlocked sp.
I would love to have MIUI (4.3 based) using cm10.2 as base. @OP, if you have any experience of using MIUI patchrom, please help me.
The steps i have already done are:
1. make workspace
2. Make firstpatch
3. Make fullota
now i have to diff and patch the smalis, but not sure exactly how many smalis need to be patched for boot, and how do i know when to stop.
Having LB means to test my port, i have to go thru all the hassle of flash ftf, rooting and then check for every failed attempt.
THanks in advance
Yasir
I know there is an MIUI thread already there, but the OP states its for UBL only, plus he uses 4.2.2 as base. so thot this might be the right place.
---------- Post added at 09:01 PM ---------- Previous post was at 08:56 PM ----------
btw, @ keiran...
I once thot about this... can u confirm im true....
what if we dont format /system partition in updater script of cm.zip... every time, we flash, system wont be formatted so recovery will stay, and if there was something wrong with cm.zip, we can try to fix and flash the new cm.zip and it will overwrite the previous versions of every file hence we know it boots or not.
If it boots, we can do a clean install.
Correct me if im wrong here. Thanks

neXus PRIME said:
Great work by @bagyusz and @KeiranFTW for the initial spark idea. I thot all was lost when i got vendorlocked sp.
I would love to have MIUI (4.3 based) using cm10.2 as base. @OP, if you have any experience of using MIUI patchrom, please help me.
The steps i have already done are:
1. make workspace
2. Make firstpatch
3. Make fullota
now i have to diff and patch the smalis, but not sure exactly how many smalis need to be patched for boot, and how do i know when to stop.
Having LB means to test my port, i have to go thru all the hassle of flash ftf, rooting and then check for every failed attempt.
THanks in advance
Yasir
I know there is an MIUI thread already there, but the OP states its for UBL only, plus he uses 4.2.2 as base. so thot this might be the right place.
---------- Post added at 09:01 PM ---------- Previous post was at 08:56 PM ----------
btw, @ keiran...
I once thot about this... can u confirm im true....
what if we dont format /system partition in updater script of cm.zip... every time, we flash, system wont be formatted so recovery will stay, and if there was something wrong with cm.zip, we can try to fix and flash the new cm.zip and it will overwrite the previous versions of every file hence we know it boots or not.
If it boots, we can do a clean install.
Correct me if im wrong here. Thanks
Click to expand...
Click to collapse
No need to, I am creating build repository that will be able to build CyanogenMod using the cyanogenmod build system, basically I just add the files that are needed for the hack into the repository and then I will be able to build CM and flash it straight off - I'll do this so when the ROM is built it includes recovery and hijack in the /system partition and so when you flash it, it will still be there.
As soon as I get access to a build server I will build AOKP for locked bootloader (jb-mr2)

All work except my wifi. It's grayed out. I got data though...
Just to note: that I was on 4.1.2 (254) rooted when I flashed this rom and GAPPS. After which I flashed the 266 kernel.
Edit:
I did a factory reset under recovery (CWM) and now my wifi has turned on (blue). Unfortunately I am away from my wifi (home) point, so can't test it out fully.
Back to reinstalling of data...

babicsbalu said:
Well done, nice job! :highfive:
Click to expand...
Click to collapse
Don't quote the whole post.

Just preparing for this, I downloaded the kernel from the main thread not the one linked by KeiranFTW do we only need to flash the kernel.sin or do we need other files like fotakernel.sin like when flashing existenz?

Oblox said:
Just preparing for this, I downloaded the kernel from the main thread not the one linked by KeiranFTW do we only need to flash the kernel.sin or do we need other files like fotakernel.sin like when flashing existenz?
Click to expand...
Click to collapse
The link on both threads only feature the .266 kernel - for use after installing cyanogenmod.
The .257 is the full firmware for rooting purposes.
I have already rooted my SP previously therefore, I merely installed CM and flashed the .266 kernel at the end of the process (actually I used my country's version, unchecked all but kernel only) - worked for me.

headache59 said:
The link on both threads only feature the .266 kernel.
I flashed the kernel at the end of the process (actually I used my country's version, unchecked all but kernel only) - and it worked for me.
Click to expand...
Click to collapse
Ahh ok, does the countries kernel make any difference whatsoever?

How do I unlock my bootloader?

Hi all, new to Android and Samsung, so sorry for the noob question.. and sorry if its been answered before, Ive done a HEAP of reading and Im still confused...
I recently bought an S4 GT-I9505, thinking that getting into Android and maybe tweaking it a bit would be fun..
This phone was a Warranty replacement for a Telstra "POST Paid" service and has been sitting in a cupboard for a few years, It is NOT network locked. The phone had never been used before I bought it but has since ran out of warranty,,
I can't remember what ver of Android was on the phone when I got it but Its now updated to 5.0.1 and ofcourse has KNOX.. I obviously dont care about KNOX Warranty tripping to 0x1 as its ran out anyway...
My question is though....
Every guide or thread I read about installing custom ROMs and such says "phone must have an UNLOCKED bootloader" ... So how do I "UNLOCK" the bootloader or is this something that happens when flashing a custom ROM? ... What am I missing here guys?
Thanks in advance
kingsdene

Only few devices have a locked bootloader.
Verizon and AT&T devices have a locked bootloaders.
If you're device is none of the above then you're good to go.

GDReaper said:
Only few devices have a locked bootloader.
Verizon and AT&T devices have a locked bootloaders.
If you're device is none of the above then you're good to go.
Click to expand...
Click to collapse
Hi thanks for your reply,,
That clrears things up a bit,,
I read somewhere that the international versions weren't locked.. and in another thread I read they said the I9505 is international but on that same thread someone else said that it wasn't international, only the i9500 was,, so that confused me a little...
but on wikipedia the I9505 and I9506 are listed as international.... so if thats the case I definitely should be right hey???
Also because Im from AUS and not much is listed in terms of Australian Service providers.. would it be worth me trying to contact Telstra because its a Telstra "POST Paid" phone and asking if there would be any restrictions on it???

kingsdene said:
Hi thanks for your reply,,
That clrears things up a bit,,
I read somewhere that the international versions weren't locked.. and in another thread I read they said the I9505 is international but on that same thread someone else said that it wasn't international, only the i9500 was,, so that confused me a little...
but on wikipedia the I9505 and I9506 are listed as international.... so if thats the case I definitely should be right hey???
Also because Im from AUS and not much is listed in terms of Australian Service providers.. would it be worth me trying to contact Telstra because its a Telstra "POST Paid" phone and asking if there would be any restrictions on it???
Click to expand...
Click to collapse
It might at worst have a network/carrier lock on it, but that would be it, no other locks.
See here for info/fees: https://whirlpool.net.au/wiki/phone_unlocking
I believe post paid phones are unlocked from the word go, but you may want to check...easiest way is to grab a sim from a family member/friend on another carrier and put it in and see if it registers on the network...prolly quicker than waiting on the phone to telstra...only to be told its not locked .
Here you go, more info:
http://www.acma.gov.au/theACMA/engage-blogs/engage-blogs/Telco/The-key-to-unlocking-your-mobile
Me im in Aus too, i bought my S5 i9505, a former Telstra S4, a few days back knowing it was unlocked fortunately....took it home and rooted it, debloated it and living happily on the stock 5.01 TouchWiz ROM with TWRP Recovery and Xposed , ill prolly chuck a custom one on at some point....

stylemessiah said:
It might at worst have a network/carrier lock on it, but that would be it, no other locks.
I believe post paid phones are unlocked from the word go, but you may want to check...easiest way is to grab a sim from a family member/friend on another carrier and put it in and see if it registers on the network...prolly quicker than waiting on the phone to telstra...only to be told its not locked .
Me im in Aus too, i bought my S5 i9505, a former Telstra S4, a few days back knowing it was unlocked fortunately....took it home and rooted it, debloated it and living happily on the stock 5.01 TouchWiz ROM with TWRP Recovery and Xposed , ill prolly chuck a custom one on at some point....
Click to expand...
Click to collapse
Hi mate, Thanks very much for the reply/info
Thats really good to know.. Looks like Im all set then,, I knew it wasn't networked locked, I tested with an Optus sim..
Would you mind sharing your process on how you rooted it and installed TWRP? Did you use apps or flash from Odin/Heimdal etc,, I know theres heaps of guides and different ways of doing so.... Im just curious on different peoples experiences
Oh and just thaught id let you know I noticed in your sig you've listed you device as S4 I9095

kingsdene said:
Hi mate, Thanks very much for the reply/info
Thats really good to know.. Looks like Im all set then,, I knew it wasn't networked locked, I tested with an Optus sim..
Would you mind sharing your process on how you rooted it and installed TWRP? Did you use apps or flash from Odin/Heimdal etc,, I know theres heaps of guides and different ways of doing so.... Im just curious on different peoples experiences
Oh and just thaught id let you know I noticed in your sig you've listed you device as S4 I9095
Click to expand...
Click to collapse
Nice pickup on the sig
Im the king of typos...i have a wonky brain, and it doesnt always connect my hand with the right keys Sig corrected
Heres what i did on mine, and how i remember doing it, though if some steps dont match up, let me know via PM or email, in my profile:
Required utils/files (assuming you have a standard i9505):
Odin: http://dl.sammobile.com/Odin3-v3.11.1.zip
CF Auto Root: https://download.chainfire.eu/316/CF-Root/CF-Auto-Root/CF-Auto-Root-jflte-jfltexx-gti9505.zip
TWRP: https://dl.twrp.me/jfltexx/twrp-3.0.2-0-jfltexx.img.tar.html
1) Rooting
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC via cable
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the CF Auto file downloaded
f) Press Start
g) It should upload to phone and phone should reboot into recovery and do its thing and then reboot
h) Unplug the phone form the cable
i) You may get, i did, a Google Play update to update SuperSU. I did this and rebooted, you may also get a prompt to update the su binary, do this using the Normal method, and reboot
2) TWRP
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the TWRP file downloaded
f) Click options, and untick Auto Reboot - if you dont manage to catch the device using the recovery boot keys as it reboots, it may boot normally and over-write the recovery, and you'll have flash it again, so i turned this off
f) Press Start
g) When its uploaded, unplug phone,and hold down Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left (lines of blue, yellow, red text), let go at this point, a
the device should boot to recovery and install recovery
h) Unplug the phone form the cable
i) Power down the phone (i got a cache mounting issue - discovered when i was flashing Xposed, that you may need to fix...best to do it anyways, and do it now to fix the issue before you try and flash a custom ROM in the future etc)
j) Boot to recovery again - Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left, let go at this point, the device should boot to recovery
k) Go into Mount and see if Cache is mounted, if it is, youre fine, if it isnt, try mounting it by ticking Cache. If it wont mount:
i) Click Wipe,
ii) Click Advanced Wipe
iii) Tick Cache
iiii) Click Repair or Change File System
iv) Click Change Filesystem
v) Click Ext4
vi) Swipe to change
It may take some time to fix....
l)Reboot when done
3) Debloating (highly recommended on the stock ROM)
Theres a few pages on which apps and files to remove using a root uninstaller app, or you can Install this and tick the items you want removed: https://play.google.com/store/apps/details?id=com.adamioan.s4lollipopdebloater&hl=en
Please dont ask me what to tick or leave ticked Theres descriptions in the app, or more info on the forums. Personally i tend to decimate ROM's from all non-essential apps, but what works for me may not work for you, you may use things i dont.
When done, reboot
Optional though recommended: Boot into recovery and wipe your dalvik & cache (note: once Dalvik is wiped your next reboot will be long due to app optimising - it will be shorter than normal with less apps though)
Hope this helps

stylemessiah said:
Nice pickup on the sig
Im the king of typos...i have a wonky brain, and it doesnt always connect my hand with the right keys Sig corrected
Heres what i did on mine, and how i remember doing it, though if some steps dont match up, let me know via PM or email, in my profile:
1) Rooting
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC via cable
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the CF Auto file downloaded
f) Press Start
g) It should upload to phone and phone should reboot into recovery and do its thing and then reboot
h) Unplug the phone form the cable
i) You may get, i did, a Google Play update to update SuperSU. I did this and rebooted, you may also get a prompt to update the su binary, do this using the Normal method, and reboot
2) TWRP
a) Put phone into download mode - Power + Home + Vol Down, then Vol Up
b) Connect to PC
c) Run Odin
d) Tick next AP
e) Press AP and browse to locate and select the TWRP file downloaded
f) Click options, and untick Auto Reboot - if you dont manage to catch the device using the recovery boot keys as it reboots, it may boot normally and over-write the recovery, and you'll have flash it again, so i turned this off
f) Press Start
g) When its uploaded, unplug phone,and hold down Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left (lines of blue, yellow, red text), let go at this point, a
the device should boot to recovery and install recovery
h) Unplug the phone form the cable
i) Power down the phone (i got a cache mounting issue - discovered when i was flashing Xposed, that you may need to fix...best to do it anyways, and do it now to fix the issue before you try and flash a custom ROM in the future etc)
j) Boot to recovery again - Power + Home + Vol Up until it reboots and you see the recovery boot text appear in the top left, let go at this point, the device should boot to recovery
k) Go into Mount and see if Cache is mounted, if it is, youre fine, if it isnt, try mounting it by ticking Cache. If it wont mount:
i) Click Wipe,
ii) Click Advanced Wipe
iii) Tick Cache
iiii) Click Repair or Change File System
iv) Click Change Filesystem
v) Click Ext4
vi) Swipe to change
It may take some time to fix....
l)Reboot when done
3) Debloating (highly recommended on the stock ROM)
Theres a few pages on which apps and files to remove using a root uninstaller app, or you can Install this and tick the items you want removed: https://play.google.com/store/apps/details?id=com.adamioan.s4lollipopdebloater&hl=en
Please dont ask me what to tick or leave ticked Theres descriptions in the app, or more info on the forums. Personally i tend to decimate ROM's from all non-essential apps, but what works for me may not work for you, you may use things i dont.
When done, reboot
Optional though recommended: Boot into recovery and wipe your dalvik & cache (note: once Dalvik is wiped your next reboot will be long due to app optimising - it will be shorter than normal with less apps though)
Hope this helps
Click to expand...
Click to collapse
Haha your not the only one with a wonky brain bro.....
And WOW wasn't expecting all that... Thanks very much man, your a legend.
I really appreciate your help
Ill give it a crack and see how I go..
Cheers mate

stylemessiah said:
Heres what i did on mine, and how i remember doing it
Click to expand...
Click to collapse
Hi mate,, just thaught I'd let you know I followed your guide and all was sucsessful, thanks again, I had it running for a while and I really like the stock ROM when unbloated.
Since then I've flashed a Resurrection Remix Marshmallow ROM -ver 5.6.7 and its running well except for a few glitches but nothing serious.
I have a question for you though, if you dont mind... I am planning on getting the latest RR ROM and upgrading to that to see how it runs...
But if I were to downgrade to a Lollipop version of RR, would I be ok flashing it from my current state? I have read somewhere that flashing to an earlier version of Android (Marshmallow to Lollipop) is a bit of a different process?
And also if this were true.... Than when I made a TWRP Backup of my rooted stock 5.0.1 Lollipop before I flashed RR 6.0.1 Marshmallow.. If I were to try now to restore from my backup it wouldn't work? because of the different Android versions?
I have done heaps of reading and can't seem to find a great deal on this... only when it comes to stock ROMs
Cheers
kingsdene

kingsdene said:
Hi mate,, just thaught I'd let you know I followed your guide and all was sucsessful, thanks again, I had it running for a while and I really like the stock ROM when unbloated.
Since then I've flashed a Resurrection Remix Marshmallow ROM -ver 5.6.7 and its running well except for a few glitches but nothing serious.
I have a question for you though, if you dont mind... I am planning on getting the latest RR ROM and upgrading to that to see how it runs...
But if I were to downgrade to a Lollipop version of RR, would I be ok flashing it from my current state? I have read somewhere that flashing to an earlier version of Android (Marshmallow to Lollipop) is a bit of a different process?
And also if this were true.... Than when I made a TWRP Backup of my rooted stock 5.0.1 Lollipop before I flashed RR 6.0.1 Marshmallow.. If I were to try now to restore from my backup it wouldn't work? because of the different Android versions?
I have done heaps of reading and can't seem to find a great deal on this... only when it comes to stock ROMs
Cheers
kingsdene
Click to expand...
Click to collapse
Im glad that my wonky memories of rooting/twrp and debloating worked out for you. The stock 5.01 ROM is great without the bloat. Ive since moved onto Optimised CM13, which is going well.
Im afraid i cant help you on downgrading from LP to MM, as ive never done it on this device, but i cant see how that would in any way be an issue as you have a custom recovery installed...afaik thats all thats needed...at least on the S2 it was as easy as flash what the hell you want to on it as long as you had at least a KK recovery installed..
Cant help on backups, as i literally never use them, i never carry over stuff from one ROM to the next, i clean install everything

kingsdene said:
Hi mate,, just thaught I'd let you know I followed your guide and all was sucsessful, thanks again, I had it running for a while and I really like the stock ROM when unbloated.
Since then I've flashed a Resurrection Remix Marshmallow ROM -ver 5.6.7 and its running well except for a few glitches but nothing serious.
I have a question for you though, if you dont mind... I am planning on getting the latest RR ROM and upgrading to that to see how it runs...
But if I were to downgrade to a Lollipop version of RR, would I be ok flashing it from my current state? I have read somewhere that flashing to an earlier version of Android (Marshmallow to Lollipop) is a bit of a different process?
And also if this were true.... Than when I made a TWRP Backup of my rooted stock 5.0.1 Lollipop before I flashed RR 6.0.1 Marshmallow.. If I were to try now to restore from my backup it wouldn't work? because of the different Android versions?
I have done heaps of reading and can't seem to find a great deal on this... only when it comes to stock ROMs
Cheers
kingsdene
Click to expand...
Click to collapse
The downgrading is only a problem on stock to stock ROMs. Any combination of custom to stock should work.
And TWRP has a problem with TouchWiz ROM backups. So your backup might not work either.
I mean, it will work, but you get errors.