Related
Hi
The development of this ROM has been suspended at the moment due to my busy and conflicting schedule. However, fellow developer krabappel2548 is working on an AOSP ROM too. You may like to check out his work on the XDA Forums and on Facebook. I would like to thank all members of the XDA community for your generous assistance and kind support.
I am new to Android development and have recently gotten myself a brand new Xperia S. After browsing through many forums and websites, I have discovered that our Xperia S was once an experimental device of the AOSP. However, I have noticed that there are hardly any AOSP ROMS built for our device. As I'm having a break now, I have some free time on my hands so I thought why not have a go at building an AOSP ROM for our device. So, I present to you XDantheManX Jellybean, a vanilla AOSP ROM for our Xperia S.
Basically, I downloaded the Android sources from the official repository, cloned the Xperia S AOSP repository, included the software binaries for Xperia S from Sony Mobile and built an Android system for our device. I will be uploading my sources onto a GitHub repository for all to contribute in the near future.
WARNING! This is an unstable PRE-ALPHA release. I will not be held responsible if you brick your device.
DOWNLOAD XDantheManX Jellybean 4.2.1 (Unflashable)
DOWNLOAD XDantheManX Jellybean 4.1.1 (Recommended)
DOWNLOAD XDantheManX Jellybean 4.1.1 (Flashable CWM Zip)
Pre-requisites
- Unlocked bootloader. Instructions here.
- Installed fastboot driver for Xperia S if using Windows.
- Android SDK
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installation instructions
1. Download XDantheManX Jellybean (CWM flashable zip) and flash using CWM Recovery.
2. Flash a CM10 kernel eg. FXP/NOVA of your choice.
Bugs
Report bugs here!
At present, we have issues with compiling the ROM and getting it to boot because:
- Sony's Github device files are in the progress of being modified for Android 4.2
- Therefore, we are unable to create a fully-working 4.1 ROM
- We are also unable to create a fully-working 4.2 ROM as the migration has not been completed.
So, we're stuck somewhere in the middle :/
- Fastboot flashing method is stuck on system.img for 4.1.2
Please post any bugs on this thread and inform me if it is working/not working. PM me if you require any assistance or would like to work together in developing this ROM.
Let's work together to improve this ROM! :highfive:
Hit the Thanks :good: button if this made your day!
Good luck man, it's good to see a AOSP ROM for our device
That is really nice. I look forward to test this on my device soon. Good job man :good:
EDIT: Why such a complicated way of installing this? Can't it be a little bit more user-friendly? Like install ROM with CWM, and maybe flash the kernel with fastboot?
And both links lead to AOSP 4.1.2. No link for JB 4.2.1.
Felimenta97 said:
That is really nice. I look forward to test this on my device soon. Good job man :good:
EDIT: Why such a complicated way of installing this? Can't it be a little bit more user-friendly? Like install ROM with CWM, and maybe flash the kernel with fastboot?
And both links lead to AOSP 4.1.2. No link for JB 4.2.1.
Click to expand...
Click to collapse
Link to JB 4.2.1 fixed!
I'm still quite new to this and am not sure how to create a flashable CWM zip. Could you teach me how please? Thanks.
Thx for supporting XS and this community
I will try it soon
Sent from my Xperia S using xda app-developers app
XDantheManX said:
Link to JB 4.2.1 fixed!
I'm still quite new to this and am not sure how to create a flashable CWM zip. Could you teach me how please? Thanks.
Click to expand...
Click to collapse
I don't know how to do that, sorry
I never did anything with that instalation method, and even being quite a experienced user, I'm scared of that
Try asking help for championswinner (AOKP dev) or Krabappel (KA ROM dev).
XDantheManX said:
Link to JB 4.2.1 fixed!
I'm still quite new to this and am not sure how to create a flashable CWM zip. Could you teach me how please? Thanks.
Click to expand...
Click to collapse
try this - [GUIDE] How to make a cwm recovery flashable zip - http://forum.xda-developers.com/showthread.php?t=1721680
First 4.2.1 for our device...
Thank you so much...
As it is a pre alpha ,i wanted to ask are the basic things working like mobile data ,wifi ,bluetooth, camera etc etc??
Edit:- First Vanilla 4.1.2 for our device as 4.2.1 has some problems....
Sent from my iPhone 6 using Key Lime Pie
ap030993 said:
First 4.2.1 for our device...
Thank you so much...
As it is a pre alpha ,i wanted to ask are the basic things working like mobile data ,wifi ,bluetooth, camera etc etc??
Sent from my iPhone 6 using Key Lime Pie
Click to expand...
Click to collapse
especially the Wi-Fi, the CM10 rom never seems to read the MAC from my telephone and gives it a MAC adress build in the rom itself, since me and my father both had cm10 we had had same MAC, the wifi gives ip's based on MAC so that conflicted a lot. (thus i went back to CM9.1)
does this rom read the actual telephone's MAC adress?
This way of installing is the same as the way in which Sony released the ICS beta for the 2011 line. It's totally safe, don't worry
Update: Receiving error when executing first command in instructions?
fareeed said:
This way of installing is the same as the way in which Sony released the ICS beta for the 2011 line. It's totally safe, don't worry
Click to expand...
Click to collapse
If you say so, I will do it. To go back, the only thing is installing a kernel with a recovery and go back, right? Kinda confused.
Felimenta97 said:
If you say so, I will do it. To go back, the only thing is installing a kernel with a recovery and go back, right? Kinda confused.
Click to expand...
Click to collapse
Doesn't seem to flash throws out errors when trying to execute the first command,
Code:
fastboot flash userdata out/target/product/lt26/userdata.img
Yeah to return just flash kernel with recovery and restore your nandroid or w/e
fareeed said:
Doesn't seem to flash throws out errors when trying to execute the first command,
Code:
fastboot flash userdata out/target/product/lt26/userdata.img
Yeah to return just flash kernel with recovery and restore your nandroid or w/e
Click to expand...
Click to collapse
Ok. And you're saying that the first command line isn't working?
Felimenta97 said:
Ok. And you're saying that the first command line isn't working?
Click to expand...
Click to collapse
Yeah, I think fastboot flash userdata userdata.img may work. Not too sure, best off waiting for the dev to reply I think.
fareeed said:
Yeah, I think fastboot flash userdata userdata.img may work. Not too sure, best off waiting for the dev to reply I think.
Click to expand...
Click to collapse
fareeed said:
This way of installing is the same as the way in which Sony released the ICS beta for the 2011 line. It's totally safe, don't worry
Update: Receiving error when executing first command in instructions?
Click to expand...
Click to collapse
Are you using the 4.1.2 or 4.2.1 build? I would recommend using the 4.1.1 build.
Apologies for my mistake in the instruction. I stated to move the extracted files to the Android SDK Tools folder where fastboot resides. Therefore, since both files reside in the same directory, to flash userdata.img, the code should be:
Code:
fastboot flash userdata userdata.img
Hope the flashing is successful now! :fingers-crossed:
I built this ROM following the instructions on the Sony Xperia S AOSP Github as I have a powerful machine and wanted to develop an AOSP ROM for the community. However, I have yet to test it as I currently have a locked bootloader, having gotten it recently. Nevertheless, I am planning to unlock it in the near future though as software development has always been my passion and the I am planning to use the Xperia S to test and develop more software, such as Firefox OS, which I'm very interested in at the moment.
Do you know if unlocking the bootloader will void my warranty, and to what extent? Thanks.
XDantheManX said:
Are you using the 4.1.2 or 4.2.1 build? I would recommend using the 4.1.1 build.
Apologies for my mistake in the instruction. I stated to move the extracted files to the Android SDK Tools folder where fastboot resides. Therefore, since both files reside in the same directory, to flash userdata.img, the code should be:
Code:
fastboot flash userdata userdata.img
Hope the flashing is successful now! :fingers-crossed:
I built this ROM following the instructions on the Sony Xperia S AOSP Github as I have a powerful machine and wanted to develop an AOSP ROM for the community. However, I have yet to test it as I currently have a locked bootloader, having gotten it recently. Nevertheless, I am planning to unlock it in the near future though as software development has always been my passion and the I am planning to use the Xperia S to test and develop more software, such as Firefox OS, which I'm very interested in at the moment.
Do you know if unlocking the bootloader will void my warranty, and to what extent? Thanks.
Click to expand...
Click to collapse
I will flash 4.2.1 just for a quick try and such.
About unlocking bootloader, the theory is that they still should fix your device if no hardware harm due overclocking or anything like that happened, but most stores don't fix it just because being unlocked. Also it breaks Download Music Info from Walkman and Bravia Engine on Stock ICS (it's a bug).
ERROR while flashing the second part:
If I type "fastboot flashall" it gives me:
"error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
What should I do?
I already flashed userdata.img...
Even after flashing ramdisk.img, the system got stuck on flashing boot.img, so I stopped, tried to flash the dual.elf (dual boot kernel) and failed. I rebooted the phone (Had to do so, fastboot command didn't worked) and I still have dual boot recovery. Restoring backup now. Hope not to have any problems with the userdata.img thing.
Felimenta97 said:
I will flash 4.2.1 just for a quick try and such.
About unlocking bootloader, the theory is that they still should fix your device if no hardware harm due overclocking or anything like that happened, but most stores don't fix it just because being unlocked. Also it breaks Download Music Info from Walkman and Bravia Engine on Stock ICS (it's a bug).
ERROR while flashing the second part:
If I type "fastboot flashall" it gives me:
"error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
What should I do?
I already flashed userdata.img...
Even after flashing ramdisk.img, the system got stuck on flashing boot.img, so I stopped, tried to flash the dual.elf (dual boot kernel) and failed. I rebooted the phone (Had to do so, fastboot command didn't worked) and I still have dual boot recovery. Restoring backup now. Hope not to have any problems with the userdata.img thing.
Click to expand...
Click to collapse
Thanks for testing out the ROM, @Felimenta97! There have been some reported problems with flashing the boot.img for Android 4.2.1 and I was not sure if they have been addressed yet, therefore I did not recommend to flash it. However, Bjorn Andersson, the lead developer on Sony Xperia S AOSP has stated that Sony will be addressing these problems in a future update of their Github repositories. I will then rebuild 4.2.1 again after the update.
userdata.img is flashed as the /data partition on the ROM. Therefore, if you wipe the data partition using your recovery, your phone should be working fine after the restore.
I will be unlocking my bootloader and testing the ROMs soon, during which I will try to address the reported errors. Are you able to get a working BRAVIA Engine/ BRAVA Engine 2 on the stock/custom ROM after unlocking the bootloader? Have you tried flashing 4.1.2? Thanks!
XDantheManX said:
Thanks for testing out the ROM, @Felimenta97! There have been some reported problems with flashing the boot.img for Android 4.2.1 and I was not sure if they have been addressed yet, therefore I did not recommend to flash it. However, Bjorn Andersson, the lead developer on Sony Xperia S AOSP has stated that Sony will be addressing these problems in a future update of their Github repositories. I will then rebuild 4.2.1 again after the update.
userdata.img is flashed as the /data partition on the ROM. Therefore, if you wipe the data partition using your recovery, your phone should be working fine after the restore.
I will be unlocking my bootloader and testing the ROMs soon, during which I will try to address the reported errors. Are you able to get a working BRAVIA Engine/ BRAVA Engine 2 on the stock/custom ROM after unlocking the bootloader? Have you tried flashing 4.1.2? Thanks!
Click to expand...
Click to collapse
I get it, I think... Anyway, I will wait for it then. I didn't tried the 4.1.2 because it isn't exactly what I want. I kinda want to check what is working on 4.2, the new things etc. I have 4.1.2 on PA, so I'm happy with it
But I can try flashing 4.1.2 for testing if you want. Btw, what I have to do with that kernel file?
About BRAVIA, it's a bug related to ICS and bootloader. No one knows how to make it work on Stock ROMs. Some say Bravia is working on PAC (AOSP based) ROM. I'm not sure about it, though.
Felimenta97 said:
I have 4.1.2 on PA, so I'm happy with it
But I can try flashing 4.1.2 for testing if you want. Btw, what I have to do with that kernel file?
About BRAVIA, it's a bug related to ICS and bootloader. No one knows how to make it work on Stock ROMs. Some say Bravia is working on PAC (AOSP based) ROM. I'm not sure about it, though.
Click to expand...
Click to collapse
Thanks @Felimenta97! I would love it if you could test 4.1.2 to check if there are any problems with the flashing.
You may disregard the kernel file. I had included it as it was output when I built the ROM. After further reading, I understand that the kernel has been merged together with ramdisk.img into boot.img so I'm clueless to the file's purpose at the moment too.
Is PA 4.1.2 working well as a ROM for daily use? Thanks for your assistance!
XDantheManX said:
Thanks @Felimenta97! I would love it if you could test 4.1.2 to check if there are any problems with the flashing.
You may disregard the kernel file. I had included it as it was output when I built the ROM. After further reading, I understand that the kernel has been merged together with ramdisk.img into boot.img so I'm clueless to the file's purpose at the moment too.
Is PA 4.1.2 working well as a ROM for daily use? Thanks for your assistance!
Click to expand...
Click to collapse
I'm using it more as a test ROM and backup ROM. I'm the PA, Dark PA and PAC main tester, so...
But yes, PA works fine for me. One of the best AOSP ROMs so far.
I will test it now.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Warning
This recovery will TRIP your Knox Counter and your warranty will be void.
This recovery is only for Samsung Galaxy E500H Qualcomm Snapdragon variant running 5.1.1 (lollipop).
Tested Safely on following devices.
Samsung Galaxy E500H
Samsung Galaxy E500M
Why TWRP ? Why not some rooted firmware which keeps warranty safe ?
TWRP is a custom recovery. It has many more functionality than stock recovery! if something goes wrong while flashing something you can always make a backup use this recovery which can be restored when things get messed. if mess is of large extend you can always flash stock firmware.
Instructions
Follow the instructions carefully.
Step 1 :
Install Samsung Drivers and connect your device to PC. let it install drivers and if its updating let it update. your device drivers should be perfectly installed without a single failure.
Link to Samsung Drivers
Step 2 :
Download Odin 3 you can use 3.07 or 3.09
You can download Odin from here
Download the TWRP Recovery
Step 3:
Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see Galaxy E5 Logo
Press vol up to confirm
Step 4:
Now that you are in Odin Mode connect your device via USB cable.
Now open Odin3 3.09 or 3.07 that you have downloaded.
If there is a pop-up like Installing ADB drivers let it get finished it usually updates.
Make sure the COM : xx (xx is usb port number it can be any number so dont worry about it,just verify COM is lit up)
Now select AP and browse to where you have .tar file and select it
Make Sure only Default Auto Reboot and F. Reset Time is ticked and nothing.verify twice only these 2 are ticked.
Untick Auto Reboot if you are installing recovery for first time!
Click Start and wait for the process to end. DO NOT Interrupt during this time.
Once it says PASS. BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON.
Done.
Credits:
TWRP Team for their awesome recovery.
Dario (For testing it on Samsung Galaxy E500M)
@kevinkoge
Downloads
TWRP Build 1
TWRP Build 2
TWRP 3.0.2.0 (Build 3)
Sources
Kernel Source
Changelog
May 24, 2016
Fixed MTP Media Transfer
Updated TWRP to latest 3.0.2.0
Added EFS Backup Option
Fixed TimeSetup
04/02
Fixed Brightness Issue
Merged with latest TWRP Changes (Lollipop)
Removed TWRP Inbuilt SU Installation Support (Wont work anymore)
Added TWRP Theme Support
10/11
Fixed Data Partition mount
Fixed SD Card detection
Fixed MTP
Fixed mounts
thanks buddy for this awesome work
Thank you! Looking forward to custom recovery for E7000 and lollipop cm12.1 for E7!
hi guys,
has anyone successfully rooted 5.1.1 with this method?
I'm using e500h, followed all the steps and stucked at Samsung logo after installing supersu.zip.
what I did...
1. Upgraded to 5.1.1 via odin using India firmware.
2. Flashed twrp, no problem found.
3. Flashed the latest stable supersu, stucked at Samsung logo.
4. Flashed the lastest beta supersu, same problem.
Even if I installed supersu via Play, it said the phone must be rooted manually first.
Now I'm back to kitkat
Any idea guys?
t88 said:
hi guys,
has anyone successfully rooted 5.1.1 with this method?
I'm using e500h, followed all the steps and stucked at Samsung logo after installing supersu.zip.
what I did...
1. Upgraded to 5.1.1 via odin using India firmware.
2. Flashed twrp, no problem found.
3. Flashed the latest stable supersu, stucked at Samsung logo.
4. Flashed the lastest beta supersu, same problem.
Even if I installed supersu via Play, it said the phone must be rooted manually first.
Now I'm back to kitkat
Any idea guys?
Click to expand...
Click to collapse
I have same problem, I tried with india, Russia. Recovery works with supersu less than 2,46 phone turn on but din´t root.
If anyone can root please let us know.
Thanks!
---------- Post added at 10:10 PM ---------- Previous post was at 09:59 PM ----------
sorry I forget to say, I tried several time back to kitkat and I can´t stock in bootloader is the closer that I have to use my phone in kitkat
pd: sorry for my english
how ?
t88 said:
hi guys,
has anyone successfully rooted 5.1.1 with this method?
I'm using e500h, followed all the steps and stucked at Samsung logo after installing supersu.zip.
what I did...
1. Upgraded to 5.1.1 via odin using India firmware.
2. Flashed twrp, no problem found.
3. Flashed the latest stable supersu, stucked at Samsung logo.
4. Flashed the lastest beta supersu, same problem.
Even if I installed supersu via Play, it said the phone must be rooted manually first.
Now I'm back to kitkat
Any idea guys?
Click to expand...
Click to collapse
bro . Can you tell me the procedure on how you went back to kitkat ? . When I flash kitkat I get stuck on Samsung logo .. . Can't go to recovery
donaldistoopro said:
bro . Can you tell me the procedure on how you went back to kitkat ? . When I flash kitkat I get stuck on Samsung logo .. . Can't go to recovery
Click to expand...
Click to collapse
I too had that problem. I flashed 5.x and 4.4.2 back and forth few times, wiped/formated everything and factory reset (while you have 5.x and TWRP) including hard reset. For some reason, it went ok and I'm able to use Kitkat again.
I think it may not be the proper way to do it. I just tried every possible thing that I can think of.
I also tried Kingroot, not working. Bummer!
Someone please email chainfire the boot.img or kernel.img he may listen to us and update cf-auto-root ?
notredame said:
I have same problem, I tried with india, Russia. Recovery works with supersu less than 2,46 phone turn on but din´t root.
If anyone can root please let us know.
Thanks!
---------- Post added at 10:10 PM ---------- Previous post was at 09:59 PM ----------
sorry I forget to say, I tried several time back to kitkat and I can´t stock in bootloader is the closer that I have to use my phone in kitkat
pd: sorry for my english
Click to expand...
Click to collapse
donaldistoopro said:
bro . Can you tell me the procedure on how you went back to kitkat ? . When I flash kitkat I get stuck on Samsung logo .. . Can't go to recovery
Click to expand...
Click to collapse
t88 said:
I too had that problem. I flashed 5.x and 4.4.2 back and forth few times, wiped/formated everything and factory reset (while you have 5.x and TWRP) including hard reset. For some reason, it went ok and I'm able to use Kitkat again.
I think it may not be the proper way to do it. I just tried every possible thing that I can think of.
I also tried Kingroot, not working. Bummer!
Click to expand...
Click to collapse
harshal10398 said:
Someone please email chainfire the boot.img or kernel.img he may listen to us and update cf-auto-root ��
Click to expand...
Click to collapse
Its not recovery fault its SAMSUNG. normal root flash will not work on stock anyhow and even chainfire knows it. this is the same issue were S6 Edge suffered too. its security which checks any modification in system partition on boot and if found it wont allow system to boot thus causing bootloop and at no way recovery is at fault!
New build is UP!
KINDLY DO NOT FLASH SUPERSU IT WILL BOOTLOOP DEVICE!
More info please.
Sent from my SM-E500H using Tapatalk 2
t88 said:
More info please.
Sent from my SM-E500H using Tapatalk 2
Click to expand...
Click to collapse
what more info you want ?
do i need to be rooted in order to install cyanogenmod rom and TWRP custom recovery ?
Good morning sir jackeagle .can I still root my phone now that I'm on lollipop 5.1.1?
The link is not working it is just showing the home page?
donaldistoopro said:
Good morning sir jackeagle .can I still root my phone now that I'm on lollipop 5.1.1?
Click to expand...
Click to collapse
Hi,
I dont think so SuperSU will work on 5.1.1 but many have said that Kingroot works so you can try that but CM is pre-rooted so anyway its possible
WeZLi1 said:
The link is not working it is just showing the home page?
Click to expand...
Click to collapse
Download links Fixed!
jackeagle said:
Hi,
I dont think so SuperSU will work on 5.1.1 but many have said that Kingroot works so you can try that but CM is pre-rooted so anyway its possible
Download links Fixed!
Click to expand...
Click to collapse
thanks bro
t88 said:
hi guys,
has anyone successfully rooted 5.1.1 with this method?
I'm using e500h, followed all the steps and stucked at Samsung logo after installing supersu.zip.
what I did...
1. Upgraded to 5.1.1 via odin using India firmware.
2. Flashed twrp, no problem found.
3. Flashed the latest stable supersu, stucked at Samsung logo.
4. Flashed the lastest beta supersu, same problem.
Even if I installed supersu via Play, it said the phone must be rooted manually first.
Now I'm back to kitkat
Any idea guys?
Click to expand...
Click to collapse
You need a custom kernel + beta su 2.51 in order to get root access on tw 5.1.1 roms
Hi guys!
I built TWRP [Ver: 3.1.1] from scratch for LG G4c.
Update: TWRP is official now!
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Supported Models:
LG G4c
Click to expand...
Click to collapse
First, UNLOCK the bootloader!
Steps:
(1) Download the Official TWRP App.
(2) Open Official TWRP App > Select TWRP Flash > Select A Device > Search for G4c (c90).
(3) Select G4c (c90). Then select "twrp-3.1.1-0-c90.img".
(4) It opens a broswer and select download "twrp-3.1.1-0-c90.img".
(5) Open Official TWRP app again, select "Select a file to flash.." and select the file you just downloaded and then select "Flash To Recovery". Confirm flash.
(6) Then reboot to recovery.
You are in TWRP!
NOTE: To boot into recovery with hardware buttons use this method. Power off the device > press and hold Power + Volume Down buttons simultaneously > keep pressing them until the LG logo shows up > when the LG logo shows up, let go of the buttons for 1 second and then press them again. A factory reset menu will show up. Select "Yes" two times to "wipe" your device. Don't worry, this will actually NOT wipe your device. It will boot into recovery normally. This is because LG phones are a bit different and they instruct the recovery (TWRP in this case) to automatically perform a factory reset of the phone by triggering the /misc wipe flag. I mapped /misc partition to a different partition (/pad) so TWRP doesn't perform a factory reset.
BUGS:
None!
Device Tree I created for G4c: https://github.com/PVineeth/android_device_lge_c90_recovery
Thanks to my friends on XDA for helping me in building device tree and building TWRP from scratch!
Thanks for your efforts in porting TWRP to the H525n. Hope this will motivate skilled people to unlock its bootloader.
Side questions:
- Did you test it?
- How is it affected by the locked bootloader
- What can we do exactly with TWRP, flashing easily stock roms (that would be terrible )?
Thanks again!!
Anghirrim said:
Thanks for your efforts in porting TWRP to the H525n. Hope this will motivate skilled people to unlock its bootloader.
Side questions:
- Did you test it?
- How is it affected by the locked bootloader
- What can we do exactly with TWRP, flashing easily stock roms (that would be terrible )?
Thanks again!!
Click to expand...
Click to collapse
I will be posting the bootloader unlock method in few days. After that you can flash TWRP. Yes you can easily flash stock roms through TWRP.
You are the man!!!
Hey, by the way, why didn't you post it into the LG g4 forum? You would have had more visibility from H525n owners no?
Anghirrim said:
Hey, by the way, why didn't you post it into the LG g4 forum? You would have had more visibility from H525n owners no?
Click to expand...
Click to collapse
Ok will do that.
Anghirrim said:
Hey, by the way, why didn't you post it into the LG g4 forum? You would have had more visibility from H525n owners no?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g4/development/unofficial-twrp-3-1-1-lg-g4c-t3613824
You are fast
Anghirrim said:
Thanks for your efforts in porting TWRP to the H525n. Hope this will motivate skilled people to unlock its bootloader.
Side questions:
- Did you test it?
- How is it affected by the locked bootloader
- What can we do exactly with TWRP, flashing easily stock roms (that would be terrible )?
Thanks again!!
Click to expand...
Click to collapse
Flash this patched aboot:
https://yadi.sk/d/1Dw4_bod3EgUMU
pvineeth97 said:
Flash this patched aboot:
https://yadi.sk/d/1Dw4_bod3EgUMU
Click to expand...
Click to collapse
Hello, do you mean this is the patched aboot that unlocks the phone!?
Thanks man!!
I unfortunately won't do it now as it is for my wife's phone and someone got long term sick in her family. So it's not time now to mess up with her phone.
Just for my information. Do you know to which stock rom version this aboot is linked?
Thanks again man!
Anghirrim said:
Hello, do you mean this is the patched aboot that unlocks the phone!?
Thanks man!!
I unfortunately won't do it now as it is for my wife's phone and someone got long term sick in her family. So it's not time now to mess up with her phone.
Just for my information. Do you know to which stock rom version this aboot is linked?
Thanks again man!
Click to expand...
Click to collapse
It doesn't matter which stock rom the aboot is linked to.
pvineeth97 said:
It doesn't matter which stock rom the aboot is linked to.
Click to expand...
Click to collapse
Ok thanks. So if I understood and read well, this aboot is the one from the H440n (LG Spirit) and not the original from H525n but they are supposed to work anyway, correct ?
Anghirrim said:
Ok thanks. So if I understood and read well, this aboot is the one from the H440n (LG Spirit) and not the original from H525n but they are supposed to work anyway, correct ?
Click to expand...
Click to collapse
Yes.
pvineeth97 said:
Yes.
Click to expand...
Click to collapse
Should we follow the instructions from this post?
https://forum.xda-developers.com/lg-k10/how-to/bootloader-unlocked-guys-bootloader-t3558810
So I guess we should use the following post partition layout to identify what needs to be flashed (unless you already know it when you built TWRP)?
https://forum.xda-developers.com/showpost.php?p=72985598&postcount=28
Anghirrim said:
Should we follow the instructions from this post?
https://forum.xda-developers.com/lg-k10/how-to/bootloader-unlocked-guys-bootloader-t3558810
So I guess we should use the following post partition layout to identify what needs to be flashed (unless you already know it when you built TWRP)?
https://forum.xda-developers.com/showpost.php?p=72985598&postcount=28
Click to expand...
Click to collapse
yes.
yes.
We are moving to Slack. Here's an invitation link for everyone: https://join.slack.com/t/g4cdevcamp...U2MmQxYzE0YmYxMjMxYjRkMmNjYzcxNjFlNzMwYWYwNDU
oh man it's official? niceeee. i bought my G4c last year because my xperia died on me and i never had root or twrp on it but you just brought life to it again. going to flash los
Hello, updating resources link, seems the old one is dead:
My shared drive
Hello, seems like the old links are kinda broken.
For anyone who need access, please send me a request on XDA prior to sending request through GoogleDrive.
I won't give access to anyone who does not post here.
Updated link
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Backups works
- Flash Rom works
- Sdcard works
Download:
TWRP
To Flash the TWRP:
Code:
fastboot flash recovery twrp-RMX1921-20191018.img
Then reboot in TWRP manually.
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/thesprintster/device_realme_RMX1921/commits/android-9.0
Precompiled Stock Kernel in use
Credits:
Thanks to other testers for the tests and the support
Created 2019-10-17
XDA:DevDB Information
[RECOVERY][3.3.x][RMX1921] TWRP, Tool/Utility for the Realme XT
Contributors
thesprintster, mauronofrio
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2019-10-17
Last Updated 2019-10-17
Reserved
Thanks sooo much bro, great work :good::good::good::good::good::good:
Hey thanks for the great work. Can you please provide the method you used for bootloader unlock... I'm trying from past 2 hours but I'm not able to find and drivers for my realme xt.
naushad.016 said:
Hey thanks for the great work. Can you please provide the method you used for bootloader unlock... I'm trying from past 2 hours but I'm not able to find and drivers for my realme xt.
Click to expand...
Click to collapse
Just search in the realme community
They made it official
sandy_9 said:
Just search in the realme community
They made it official
Click to expand...
Click to collapse
Unlock Bootloader Tutorial for realme XT
https://c.realme.com/in/post-details/1184740422732218368
Okay, I got the official method in realme community, but there is no ADB drivers on that post. If anyone have ADB drivers for realme xt please share it here. It will be great help. So far I've tried a few drivers which claimed to work on it.
naushad.016 said:
Okay, I got the official method in realme community, but there is no ADB drivers on that post. If anyone have ADB drivers for realme xt please share it here. It will be great help. So far I've tried a few drivers which claimed to work on it.
Click to expand...
Click to collapse
Use this link for ADB drivers installation.
https://www.xda-developers.com/install-adb-windows-macos-linux/
I'm getting error "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image". I am able to get fastboot mode, but selecting recovery mode redirects me to the same error screen. and it bootloops.
flashing the same recovery that is available here again from fastboot is not helping either.
what should I do now?
help will be appreciated.
naushad.016 said:
I'm getting error "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image". I am able to get fastboot mode, but selecting recovery mode redirects me to the same error screen. and it bootloops.
flashing the same recovery that is available here again from fastboot is not helping either.
what should I do now?
help will be appreciated.
Click to expand...
Click to collapse
Hi please have a look on this link. Haven't tried my own but i think this should work.
https://forum.xda-developers.com/showpost.php?p=80447545&postcount=17
ashman8123 said:
Hi please have a look on this link. Haven't tried my own but i think this should work.
https://forum.xda-developers.com/showpost.php?p=80447545&postcount=17
Click to expand...
Click to collapse
thanks for the quick reply but I doubt it will work as I was able to successfully boot in to TWRP and flashed the Linage unofficial build. It appeared after booting normally (first boot for linage, which never happened).
I really don't want to lose fastboot functionality.
---------- Post added at 09:53 AM ---------- Previous post was at 09:51 AM ----------
naushad.016 said:
thanks for the quick reply but I doubt it will work as I was able to successfully boot in to TWRP and flashed the Linage unofficial build. It appeared after booting normally (first boot for linage, which never happened).
I really don't want to lose fastboot functionality.
Click to expand...
Click to collapse
It didn't work. And I can not even get the fastboot mode now. it is BRICKED.
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
naushad.016 said:
thanks for the quick reply but I doubt it will work as I was able to successfully boot in to TWRP and flashed the Linage unofficial build. It appeared after booting normally (first boot for linage, which never happened).
I really don't want to lose fastboot functionality.
---------- Post added at 09:53 AM ---------- Previous post was at 09:51 AM ----------
It didn't work. And I can not even get the fastboot mode now. it is BRICKED.
Click to expand...
Click to collapse
I think going to a service centre is the only available option.
naushad.016 said:
thanks for the quick reply but I doubt it will work as I was able to successfully boot in to TWRP and flashed the Linage unofficial build. It appeared after booting normally (first boot for linage, which never happened).
I really don't want to lose fastboot functionality.
---------- Post added at 09:53 AM ---------- Previous post was at 09:51 AM ----------
It didn't work. And I can not even get the fastboot mode now. it is BRICKED.
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
I think going to a service centre is the only available option.
Click to expand...
Click to collapse
Sad to hear. If it serious concern try to go to service center as you think.
But as per my previous experience .. if you did all things carefully, you will not be in such a serious condition. Try to search some more options before you go to service center, if you dare.........otherwise please go on to service center.
naushad.016 said:
I'm getting error "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image". I am able to get fastboot mode, but selecting recovery mode redirects me to the same error screen. and it bootloops.
flashing the same recovery that is available here again from fastboot is not helping either.
what should I do now?
help will be appreciated.
Click to expand...
Click to collapse
100% will work. Move vbmeta.img to adb directory, boot into fastboot and type the command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
There is no way to give a link to vbmeta.img
Shurx said:
100% will work. Move vbmeta.img to adb directory, boot into fastboot and type the command:
There is no way to give a link to vbmeta.img
Click to expand...
Click to collapse
You have BL relocked ?
naandha114 said:
You have BL relocked ?
Click to expand...
Click to collapse
Bootloader unlocked. Stock firmware showed a breakdown. I flashed vbmeta.img and the phone booted.
Shurx said:
Bootloader unlocked. Stock firmware showed a breakdown. I flashed vbmeta.img and the phone booted.
Click to expand...
Click to collapse
I have unlocked....now I want to relock BL
naandha114 said:
I have unlocked....now I want to relock BL
Click to expand...
Click to collapse
In technical support they answered that a brick is possible.
Shurx said:
In technical support they answered that a brick is possible.
Click to expand...
Click to collapse
Phone will brick for sure.
Thankx for the twrp, but in realme forum they r saying after bootloader unlock we will not be able to use fingerprint scanner and ota updates ?, is there any fix ?
thank you it works!!!
If you are using TWRP version 3.6.2 then you should flash TWRP 3.7.0 for more stable. I just built a TWRP Zip for you to flash without installing via PC, no IMG file, but just a Zip file, you can flash it. I will show you how to install TWRP version 3.7.0.
Step 1: Download the TWRP Zip below.
Step 2: Reboot to custom Recovery and Flash Zip file
Step 3: Reboot Recovery
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about doing this to your device
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
We need to have twrp already to flash this new twrp right? If we don't?
BlueChris said:
We need to have twrp already to flash this new twrp right? If we don't?
Click to expand...
Click to collapse
Yes, you need to have TWRP already installed.
i have a brand new and virgin A52s, how do i install TWRP for then rooting?
fluoroom said:
i have a brand new and virgin A52s, how do i install TWRP for then rooting?
Click to expand...
Click to collapse
You need unlock bootloader and use Odin to flash TWRP
trananhdat2710 said:
You need unlock bootloader and use Odin to flash TWRP
Click to expand...
Click to collapse
Just download a tar image from official twrp.me website and flash with Odin.
Arm1nas said:
Just download a tar image from official twrp.me website and flash with Odin.
Click to expand...
Click to collapse
Yes
thanks!
fluoroom said:
thanks!
Click to expand...
Click to collapse
Have you flashed?