[xperia 2012] The big Q&A thread - Sony Xperia P, U, Sola, Go

Hi all,
Because we developers don't like all the questions we get in a development thread, i maked this thread for that people.
So please read this first before you post a question in a dev topic!

Questions about roms:
Q: Do I need to have a unlocked bootloader for (fill in the name of the rom?)
A: Most likely you need to have a unlocked bootloader, but there are some roms who don't need it. Please read the topic title/first post of the thread first!
Click to expand...
Click to collapse
Q: Do I need to have CWM installed to install (fill in the name of the rom)?
A: For almost all roms you need to have CWM installed (this is by almost all custom kernels included) except the KA xperia Sspeed roms for the xperia sola and U (
Click to expand...
Click to collapse
Q: Is (fill in the name of the rom) also compatible with (fill in the name of the device)?
A: if the topic title or the first post says: this rom is for (fill in the name of the device) and they don't call the name of your device it will not be compatible
Click to expand...
Click to collapse
Q: How can i flash (fill in the name of the rom)?
A: Download the rom and place it on your phones internal storage. Then enter cwm (turn on the device and when it vibrates press volume buttons) then go to flash zip from sdcard, chose zip from sdcard and go to the folder where the rom is located. Chose the rom with pressing the home button and then click on yes.
Click to expand...
Click to collapse

Kernel:
Q: how do i need to flash (fill in the name of the kernel)?
A: normally you need to have fastboot on your pc. if you have it you need to open a terminal and cd to the location of fastboot. Then you need to copy/paste the downloaded kernel to the fastboot folder. Then you need to type in terminal:
Fastboot flash boot (name of the kernel file)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Q: wifi doesn't work after flashing (fill in the name of the kernel), how can i solve this?
A: probaply you forgot to flash the wifi modules with CWM. Download the modules and place it on your phones internal storage. then enter cwm (turn on the device and when it vibrates press volume buttons) then go to flash zip from sdcard, chose zip from sdcard and go to the folder with the wifi modules. Chose the wifi modules with the home button and then click on yes. Now reboot and your wifi will works again.
Click to expand...
Click to collapse

More Q&As to come!!

Last one

Related

[SK17] Xperia Mini Pro, NOW unlocked bootloader and rooted, what's next?

Thanks to all the guys posting in this forum.
I finally managed to:
- unlock bootloader with the hardware trick (without loosing DRM?)
- upgrade from stock FW 335 to 368
- unroot device
so far i can help anyone having troubles with it
now i need to:
- install CM7.1 using rom manager, but the question is:
which is the Clockworkmod Recovery for the SK17? (it's not listed in the RM options).
Thanks for answering
giank30 said:
Thanks to all the guys posting in this forum.
I finally managed to:
- unlock bootloader with the hardware trick (without loosing DRM?)
- upgrade from stock FW 335 to 368
- unroot device
so far i can help anyone having troubles with it
now i need to:
- install CM7.1 using rom manager, but the question is:
which is the Clockworkmod Recovery for the SK17? (it's not listed in the RM options).
Thanks for answering
Click to expand...
Click to collapse
the boot image is there in the download of the rom on freexperia thread , same process flashboot replace boot img , and then flash the cynogenmod via recovery simple.
berz said:
the boot image is there in the download of the rom on freexperia thread , same process flashboot replace boot img , and then flash the cynogenmod via recovery simple.
Click to expand...
Click to collapse
I wanted to see what recovery mode looks like, but i cant enter it. Do i have to replace boot.img first to even enter it?
I'm new. =)
edit: im rooted on latest stock
berz said:
the boot image is there in the download of the rom on freexperia thread , same process flashboot replace boot img , and then flash the cynogenmod via recovery simple.
Click to expand...
Click to collapse
ok for reflashing boot.img w/ flash boot, but what is "recovery simple", can you try to explain how to do that? (sorry for the stupid question)
giank30 said:
ok for reflashing boot.img w/ flash boot, but what is "recovery simple", can you try to explain how to do that? (sorry for the stupid question)
Click to expand...
Click to collapse
he meant recovery mode. you can enter it by pressing volume down key during first 5 seconds of boot. you should wipe data and apply cm7 zip file there.
but i cant enter it. im wondering if i have to replace boot.img first :S
yes thats right , u need to replace boot image first.
berz said:
yes thats right , u need to replace boot image first.
Click to expand...
Click to collapse
ok thanks.
people are reporting that menu LEDs are very bright. do you know if theres a way to reduce brightness or disable the light completely?
for what i know this the vol down at boot should trigger the Clockworkmod Recovery, but as I cannot install it it's obvious that we cannot see it...
inside update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip there is a boot.img but don't know how to handle it... :-/
is it that the file that should be flashed using fastboot?
giank30 said:
for what i know this the vol down at boot should trigger the Clockworkmod Recovery, but as I cannot install it it's obvious that we cannot see it...
inside update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip there is a boot.img but don't know how to handle it... :-/
is it that the file that should be flashed using fastboot?
Click to expand...
Click to collapse
yes, boot.img via fastboot.
the instructions are on the official CM thread. here's the post for Mini Pro. http://forum.xda-developers.com/showpost.php?p=16822404&postcount=4
so i must:
1: estract boot.img from update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip
2: flash via fastboot
3: put update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip on the sd card
4: trigger the recovery mode via vol down on boot
5: flash CM7.1?
right?
giank30 said:
so i must:
1: estract boot.img from update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip
2: flash via fastboot
3: put update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip on the sd card
4: trigger the recovery mode via vol down on boot
5: flash CM7.1?
right?
Click to expand...
Click to collapse
i believe so.
there are some issues. LEDs under menu keys are super bright, and some people are reporting vibration and keyboard layout issues. keyboard layout can be solved (theres a thread for it) and vibration could be due to not wiping data before applying CM. keyboard layout could be due it as well.
so basically, LEDs is the only known issue right now.
sulkie said:
i believe so.
Click to expand...
Click to collapse
update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip is 91Mb, is that correct? should I flash it over 4.0.A.2.368?
giank30 said:
update-cm-7.1.0-XperiaMiniPro-SK17i-signed.zip is 91Mb, is that correct? should I flash it over 4.0.A.2.368?
Click to expand...
Click to collapse
yes, except my file is 89mb. is it 91 on sdcard or on your local harddrive?
edit: its 89.2 on my sdcard as well.
91.384 Kb.. so 89 Mb...
boot.img (inside the zip file) is 4,27 MB (4.481.024 byte) dated 29.2.2008, right?
giank30 said:
91.384 Kb.. so 89 Mb...
boot.img (inside the zip file) is 4,27 MB (4.481.024 byte) dated 29.2.2008, right?
Click to expand...
Click to collapse
indeed.
i got my file from CM's site. theres also a 110mb file on the official xda thread hosted on hotfile. im downloading it now to see if theres any difference
I can't find the link, can you share it?
btw, i got the Freexperia logo on boot but then it stucked...
how do I trigger recovery mode?
tnx
giank30 said:
I can't find the link, can you share it?
btw, i got the Freexperia logo on boot but then it stucked...
how do I trigger recovery mode?
tnx
Click to expand...
Click to collapse
link is here : http://forum.xda-developers.com/showpost.php?p=16822404&postcount=4
did you wipe data in recovery before applying zip file?
cant you enter recovery mode again with volume down key?
edit: files are the same, hotfile one just has extra apps. google apps and some SE ones.
i didnt installed the zip yet.
and i didnt enter in recovery mode too...
shall i push voldown + on button at the same time to enter recovery?
giank30 said:
i didnt installed the zip yet.
and i didnt enter in recovery mode too...
shall i push voldown + on button at the same time to enter recovery?
Click to expand...
Click to collapse
yes. i linked you the instructions on the official thread several posts ago
Got iT! thank you... +1 for you

Sense R3 Cannot wifi

Hello, i have a problem, i have sense R3 with SR-MOD 3 and my wifi cannot work, help me please.
Go to link in my signature (unlocking, rooting...), part about custom rom flashing and find a part about flashing of boot.img.
Do you have fastboot installed on your PC?
Sent from my awesome fridge
nlooooo said:
Go to link in my signature (unlocking, rooting...), part about custom rom flashing and find a part about flashing of boot.img.
Click to expand...
Click to collapse
Where is? I cant see link
You can't see it if you're browsing from your phone. Here you go:
http://forum.xda-developers.com/showthread.php?p=36138808#post36138808
nlooooo said:
You can't see it if you're browsing from your phone. Here you go:
http://forum.xda-developers.com/showthread.php?p=36138808#post36138808
Click to expand...
Click to collapse
I have rooted my phone, with R1 wifi is Ok, but R2,R3 doesnt work, my eng. is bad Iam from CZECH
matejvc said:
I have rooted my phone, with R1 wifi is Ok, but R2,R3 doesnt work, my eng. is bad Iam from CZECH
Click to expand...
Click to collapse
R1 is based on 1.14 RUU so you still have boot.img from 1.14. R2 i R3 are based on 1.18 so you need to flash boot.img based on 1.18, because when you flash rom boot.img included in rom.zip doesn't get flashed, you have to do it manually. Go to tutorial, I told you where, and you'll find a solution.
EDIT-EXPLANATION
Files from boot.img and some parts of zImage (kernel image) correspond to a correct lib files (modules from lib folder). So when you have one part (boot.img) from one base and the other part (modules) from different, and if manufacturer made some changes to ether one of them, you'll end up with some stuff not working (usually wifi, mobile data, gps...).
nlooooo said:
R1 is based on 1.14 RUU so you still have boot.img from 1.14. R2 i R3 are based on 1.18 so you need to flash boot.img based on 1.18, because when you flash rom boot.img included in rom.zip doesn't get flashed, you have to do it manually. Go to tutorial, I told you where, and you'll find a solution.
EDIT-EXPLANATION
Files from boot.img and some parts of zImage (kernel image) correspond to a correct lib files (modules from lib folder). So when you have one part (boot.img) from one base and the other part (modules) from different, and if manufacturer made some changes to ether one of them, you'll end up with some stuff not working (usually wifi, mobile data, gps...).
Click to expand...
Click to collapse
Where I download boot.img on 1.18 ??
It's included in the ROM.
Sent from my awesome fridge
matejvc said:
Where I download boot.img on 1.18 ??
Click to expand...
Click to collapse
Read the tutorial, There is written:
- Download the rom of your choice and put it on the sd card of your device
- Unpack boot.img from rom.zip and put it on the root of c: drive on your PC
- Reboot phone to recovery
- Choose option ‘wipe data/factory reset’
- Choose option ‘wipe cache partition’
- Choose option ‘advanced’ and in next menu choose ‘wipe dalvik cache’
- Go back to main menu and choose ‘install zip from sd card’ and then ‘choose zip from sd card’
- Navigate recovery to rom zip you put on sd card and choose it
- Wait until the installation is finished
- Reboot your phone to fastboot and connect it to your PC
- Open command prompt, lead it to folder where you installed adb and fastboot (remark: unlocking bootloader guide pointed you to make a folder c:\Android for this) and issue commands
fastboot flash boot c:\boot.img
fastboot reboot-bootloader
fastboot erase cache
- Reboot your phone
nlooooo said:
Read the tutorial, There is written:
- Download the rom of your choice and put it on the sd card of your device
- Unpack boot.img from rom.zip and put it on the root of c: drive on your PC
- Reboot phone to recovery
- Choose option ‘wipe data/factory reset’
- Choose option ‘wipe cache partition’
- Choose option ‘advanced’ and in next menu choose ‘wipe dalvik cache’
- Go back to main menu and choose ‘install zip from sd card’ and then ‘choose zip from sd card’
- Navigate recovery to rom zip you put on sd card and choose it
- Wait until the installation is finished
- Reboot your phone to fastboot and connect it to your PC
- Open command prompt, lead it to folder where you installed adb and fastboot (remark: unlocking bootloader guide pointed you to make a folder c:\Android for this) and issue commands
fastboot flash boot c:\boot.img
fastboot reboot-bootloader
fastboot erase cache
- Reboot your phone
Click to expand...
Click to collapse
Oh thank you my friend, wifi works Thank
matejvc said:
Oh thank you my friend, wifi works Thank
Click to expand...
Click to collapse
Friend are you know how I get jelly bean theme ? (http://cdn.teamandroid.com/wp-content/uploads/2012/06/disable-android-notifications-1-337x600.png)
I dont know if I can download somewhere.
matejvc said:
Oh thank you my friend, wifi works Thank
Click to expand...
Click to collapse
That's what the thanks button stands for.
---------- Post added at 08:59 PM ---------- Previous post was at 08:36 PM ----------
matejvc said:
Friend are you know how I get jelly bean theme ? (http://cdn.teamandroid.com/wp-content/uploads/2012/06/disable-android-notifications-1-337x600.png)
I dont know if I can download somewhere.
Click to expand...
Click to collapse
I don't know, ask Marteen, he's up with that.
matejvc said:
Friend are you know how I get jelly bean theme ? (http://cdn.teamandroid.com/wp-content/uploads/2012/06/disable-android-notifications-1-337x600.png)
I dont know if I can download somewhere.
Click to expand...
Click to collapse
Do you just want the settings app with the JB theme or the whole ROM with JB/AOSP theme?
Sent from my awesome fridge
MaartenXDA said:
Do you just want the settings app with the JB theme or the whole ROM with JB/AOSP theme?
Sent from my awesome fridge
Click to expand...
Click to collapse
Both, if possible. Please
Install the Sense Revolution ROM and flash AOSP invertion mod.
Sent from my awesome fridge
MaartenXDA said:
Install the Sense Revolution ROM and flash AOSP invertion mod.
Sent from my awesome fridge
Click to expand...
Click to collapse
Thanks, but I flash with Sense.RevolutionAOSP.Theme.V10, my phone not Boot, start, but after dispaly is off and buttons dont work. I dont know what I doing wrong.
With R3, use the one I posted in the sense revo thread.
Sent from my awesome fridge
MaartenXDA said:
With R3, use the one I posted in the sense revo thread.
Sent from my awesome fridge
Click to expand...
Click to collapse
Ok, I must install Sense R3, then SR3-MOD, then Sense.Revolution.JB_TRANS.zip ??
matejvc said:
Ok, I must install Sense R3, then SR3-MOD, then Sense.Revolution.JB_TRANS.zip ??
Click to expand...
Click to collapse
Not the JB_TANS.zip, check the 5th post and use the AOSP Invertion mod for R3 by me.

[Tutorial] How To Root HTC Desire X Jelly Bean

I have seen that since the update notification for Jelly Bean has arrived, Many people (Including me) have been asking for a Tutorial to root the Jelly Bean updated HTC Desire X (HTC DX for short). In this tutorial I would like to mention the steps to root Android Jelly Bean (JB) on HTC DX.
UPDATE: Tutorial with Screenshots here : HTC Desire X Root
This was what had worked for me when I recently rooted by HTC Desire X with Jelly Bean Update, So I hope it works for you too. I am assuming you have just installed the OTA Update and are now sitting with a Stock Jelly Bean on your device.
Summary:
1. Unlock Bootloader (if not already unlocked).
2. Install Jelly Bean compatible Custom Recovery.
3. Flash Super User and Install Busy Box.
4. Enjoy.
Steps.
1. Unlocking Bootloader.
There is a fully explained thread on unlocking bootloader and rooting android ICS put up by user nlooooo, Follow that thread and unlock your bootloader.
http://forum.xda-developers.com/showthread.php?t=2076675
2. Install Jelly Bean compatible Custom Recovery.
Once you update via OTA for the JB Update, Your HBoot becomes JB Hboot instead of the old ICS Hboot so you need a JB Hboot compatible Custom Recovery to flash the Super User and Root.
Our fellow user atis112 fixed the recovery by neXus PRIME to make it work with JB. So you need to download the JB Custom Recovery from the attachment and put it in your C Drive, So the file location would be C:\recovery.img
2.1] Download JB Recovery.img from here : http://forum.xda-developers.com/showpost.php?p=39662992&postcount=66 OR You can use the TWRP Recovery Image made by Yasir. Download from here : http://d-h.st/tSc
2.2] Once you put it in C Drive you need to connect your HTC Mobile to PC and Install HTC JB Drivers, You can install the drivers from here : http://forum.xda-developers.com/showthread.php?t=2222501. Make sure you have installed the Drivers correctly.
2.3] Open your Android SDK (Download it from here if not already) and Go to the \sdk\platform-tools folder. If on Windows 7, Keep the Shift Key pressed + Right click on an empty place in the platform-tools folder > Open Command Window here.
2.4] Type in the following command and see if your device is detected.
adb devices
Click to expand...
Click to collapse
After it is detected, Type the following command.
adb reboot bootloader
Click to expand...
Click to collapse
Once you are in the bootloader, Type the following command.
fastboot flash recovery c:\recovery.img
Click to expand...
Click to collapse
followed by
fastboot reboot-bootloader
Click to expand...
Click to collapse
and
fastboot erase cache
Click to expand...
Click to collapse
2.5] Now you have installed your custom recovery. Now Reboot your Phone.
3. Install SuperUser and Busybox.
3.1] Once again connect your HTC to PC, Download the attached SuperUser.zip and copy it to your SD Card.
3.2] Open the command prompt again as said earlier by going to platform-tools folder and using the adb devices command to check if the phone is detected.
3.3] Once it is connected, Type the following command.
adb reboot recovery
Click to expand...
Click to collapse
3.4] Now you are in the recovery, Use the Volume Up and Down keys to navigate it (Use the power button to select an option).
Navigate to Install Flashable Zip. (This should be the first option and already selected.)
Press Power Button once.
Select "Choose Zip from internal SD-Card" or "external SD-Card" accordingly as to where you put the Superuser.zip.
Press Power Button once.
Scroll and select the Superuser.zip using the Volume Keys.
Press Power Button once.
Then you have flashed your Zip successfully and you are rooted.
Go back to the Main screen using the "Go back" option. Select the "Reboot System Now".
Once you are in the HTC Main screen > Go to App Drawer > Google Play Store > Search for Busy Box and Install it.
That is it, You are now on Jelly Bean and Successfully Rooted.
To Check If You Are Rooted.
1. Open Playstore and search for an app named "Terminal Emulator".
2. Install it.
3. Open it and type in su and execute it.
4. You will get a prompt from Superuser to allow or deny > Allow it.
If you get that prompt, You are successfully rooted.
I hope I have provided credits to all the users whose threads I have mentioned. If not please let me know.
Thanks for reading this.
Or you can refer to my TWRP for JB. Its much better than the fixed neXusRecovery.
Hey, I didn't check that.. Can you give a link to the recovery?
Droid.Anoop said:
Hey, I didn't check that.. Can you give a link to the recovery?
Click to expand...
Click to collapse
Here: http://d-h.st/tSc
xpirt
xpirt said:
Here: http://d-h.st/tSc
xpirt
Click to expand...
Click to collapse
Done. Added it to the post. Thanks Yasir and Xpirt
Droid.Anoop said:
Done. Added it to the post. Thanks Yasir and Xpirt
Click to expand...
Click to collapse
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
neXus PRIME said:
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
Click to expand...
Click to collapse
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Both my recoveries are touch enabled.
1. TWRP (JB)
2. neXusRecovery. (discontinued for updates)
I'm not really a fan of buttons.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
xpirt said:
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
Click to expand...
Click to collapse
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Droid.Anoop said:
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Click to expand...
Click to collapse
I think ckpv5 found a way. Just think.
xpirt
xpirt said:
I think ckpv5 found a way. Just think.
xpirt
Click to expand...
Click to collapse
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Droid.Anoop said:
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Click to expand...
Click to collapse
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
xpirt said:
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
Click to expand...
Click to collapse
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
neXus PRIME said:
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
Click to expand...
Click to collapse
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Droid.Anoop said:
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Click to expand...
Click to collapse
Look at flar2's thread but use the files from ckpv5's ROM, but first ask him for permission.
xpirt
root JB without flashing custom recovery?
Hi!
I haven't flashed TWRP v2.5.0.0 but only boot the phone into this custom recovery, which is working perfectly. (I want to keep the stock recovery.)
I can install and use the Aroma File Manager (TWRP with Aroma File Manager did not work.)
I can mount the system partition and change / delete files.
However, with a reboot, all my changes will be undone.
Before installing Aroma File Manager for the first time, I installed SuperSu1.34.zip. No error. I installed Aroma File Manager right after it, and I think it said "rooted".
Using TWRP's SuperSu does not work (no error message, but system reboots, and it says it's not rooted.)
My question: can I root my phone while only booting into a non-stock recovery or do I have to flash TWRP and then root the phone?
Would I see the system apps e.g., after mounting /system, even if the phone was not rooted?
I am new to JB, I had 2.3.7 before, which I could root without flashing a custom recovery.
I am not sure if I have to flash the custom recovery because of the s-off problem with HTC devices?
If I flash a custom recovery and root the device, can I flash the stock recovery afterwards without loosing root again?
Would you recommend using SuperSu or Superuser? Which version?
I don't think I need busybox.
I only want to delete bloatware and change the battery symbol.
Thanks for your help!
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On. But after you rooted using a custom recovery you can flash the stock recovery again without loosing root. But keep in mind that you won't be able to change system partition. Also, you can't flash zips which aren't signed by HTC.
Sent from my HTC Desire X using xda premium
dansou901 said:
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On.
Click to expand...
Click to collapse
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
mary-lou said:
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
Click to expand...
Click to collapse
How do you boot into a custom recovery without flashing it first? It has to be on recovery partition to work correctly.

[Q] Actual way to install FirefoxOs B2G coconut

Is there's anyone can teach me how to install firefox os rom with the simplest way?
Thanks
zachseng said:
Is there's anyone can teach me how to install firefox os rom with the simplest way?
Thanks
Click to expand...
Click to collapse
You could use this firefox build
Then you just have to flash the kernel (boot.img) using flashtool or simply fastboot and afterwards you flash the zip in cwm and select your coconut in the aroma installer
If I were you I'd read my guide on how to install a custom rom/kernel which is in the stickies in general forum :good:
zachseng said:
Is there's anyone can teach me how to install firefox os rom with the simplest way?
Thanks
Click to expand...
Click to collapse
You Must Unlock BootLoader.
First Download These
1.FireFox OS- http://d-h.st/9li
2.Kernel for Lww- http://d-h.st/eb2
.
Then Go to Fastboot Mode(Turn off and Connect Pressin Vol up Button,Blue Led Confirms)
.
Then Flash Kernel Using Pc Terminal or Flashtool
Command String
fastboot -i 0x0fce flash boot Coconut_B2G_kernel.img
.
Or just Flash Via Flashtool
Guide- http://forum.xda-developers.com/showthread.php?p=43897224
.
Then Go to Recovary (keep pressing vol down while FXP logo comes Up.
.
Install .zip from sd card and select in aroma.
.
.
Original Thread-
http://forum.xda-developers.com/showthread.php?t=2370964
.
.
.
Close threads?
Anyway i solved the problems i've face to
so anyone help to close this thread cuz i got no idea bout it LOL
zachseng said:
Anyway i solved the problems i've face to
so anyone help to close this thread cuz i got no idea bout it LOL
Click to expand...
Click to collapse
There's no need to close it, because if there are any other members having the same problem, then they are able to ask their question in this existing thread here
If you want to close it, use the orange triangle (the report button) and tell the moderator to close it
Sent from my Nexus 4 running Android 4.2.2

Development [RECOVERY] TWRP for Samsung Galaxy Tab A7 Lite [Universal] [UNOFFICIAL] [Android 13]

Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite.​
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releases​Known Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issues​Telegram support group - https://t.me/gta7litegroup​
How to install​
[Boot Into Download mode by inserting an usb cable while holding both volume buttons]
Flash the latest .tar release from releases.
Hold the recovery combination (Volume Up + Power) while the .tar is flashing via the odin tool.
When booted up into TWRP go Flash and flash this zip, then go to Wipe > Format Data, all your data will be lost.
You can now boot into your system and do whatever you want.
Click to expand...
Click to collapse
​Flashing Disabled vbmeta (To boot a modified system)​
Spoiler: View
Extract the vbmeta.img.lz4 from the AP slot in your firmware.
Remove it's lz4 compression [for Windows use lz4]:
Code:
sudo apt-get install lz4 -y
lz4 vbmeta.img.lz4
Click to expand...
Click to collapse
Reboot into fastboot from TWRP flash vbmeta using this command line:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Sources​
TWRP Source - https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
Device Tree - https://github.com/DevZillion/android_device_samsung_gta7litewifixx/
Kernel Source - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx
Click to expand...
Click to collapse
Special thanks to:​
TeamWin for the Recovery Project.
Zillion for doing the device tree & kernel.
Click to expand...
Click to collapse
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Genial!!
Zillion said:
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite WiFi.​
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releases​Known Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issues​Telegram support group - https://t.me/gta7litegroup​
How to install​
​Flashing Disabled vbmeta (To boot a modified system)​
Sources​
Special thanks to:​
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Click to expand...
Click to collapse
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
dda7lite said:
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
Click to expand...
Click to collapse
Please, read the How To Install section.
Zillion said:
Please, read the How To Install section.
Click to expand...
Click to collapse
I did but the file that needs to be flashed is unavailable in that link
dda7lite said:
I did but the file that needs to be flashed is unavailable in that link
Click to expand...
Click to collapse
Thanks for reporting the issue, link fixed.
Zillion said:
Thanks for reporting the issue, link fixed.
Click to expand...
Click to collapse
i have other problem error "E:unable to open block device /dev/block/sda: No medium found"
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
chocovo said:
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
Click to expand...
Click to collapse
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
dda7lite said:
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
Click to expand...
Click to collapse
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
chocovo said:
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
Click to expand...
Click to collapse
I only did once and I didn't use the stock vbmeta I just searched "vbmeta disabled Samsung" it should show up with vbmeta disabled android 11 but works the same on 13 and I didn't use TWRP only fastboot so i don't know how to flash it there.
Btw your English is good don't worry.
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Yeah
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
Bootloop after
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
chocovo said:
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
Click to expand...
Click to collapse
If you really want to flash a gsi and can't get it to work use a fastboot enabled recovery that's what I did
dda7lite said:
Bootloop after
Click to expand...
Click to collapse
Disable vbmeta, it's the only thing I can see you missed.
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Gian-D said:
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Click to expand...
Click to collapse
Force restart and keep the usb cable connected to the PC and tablet then as soon as screen blinks hold volume +and-

Categories

Resources