Related
I recently got the Xperia S {No SD Card Slot, 32gb internal Storage}
I know it may sound silly, but could someone point me in the right direction for Flashing and Rooting this, what what's the best Rom/Kernal/Recovery Menu for this awesome device?
Just want to say, I do have experience on flashing stuff, installing roms ect
Just wondering what tools are needed to Root and Flash this thing
Thanks All!
this is the xS index for tutorials and guides and everything in between
regarding the part about best rom, you're always gonna receive a biased opinion on that coz that pretty much boils down to user preference
GrimTech said:
I recently got the Xperia S {No SD Card Slot, 32gb internal Storage}
I know it may sound silly, but could someone point me in the right direction for Flashing and Rooting this, what what's the best Rom/Kernal/Recovery Menu for this awesome device?
Just want to say, I do have experience on flashing stuff, installing roms ect
Just wondering what tools are needed to Root and Flash this thing
Thanks All!
Click to expand...
Click to collapse
Check first: *#*#SERVICE#*#* >>service info>>configuration
if it says Bootloader unlocked allowed=yes then try as explained below ! It will definitely works !
I suggest you to first unlock your bootloader via the easy tool described at here http://forum.xda-developers.com/show....php?t=1560613
then flash the Doomkernel with the flashtool booting at fastboot mode. Before doing that never forget to install the necessary drivers.
The kernel is preloaded with custom recovery CWM and TWRP. While booting when you see doom logo pressing at 'vol +' you'll get CWM and pressing at camera button you'll get TWRP.
And flash the su and busybox package via recovery (CWM or TWRP)
for flashtool http://androxyde.github.io/
for kernel and su & busybox package: http://forum.xda-developers.com/show....php?t=2305591
& then enjoy Rooted jelly bean
ALL THE BEST !
pracas said:
Check first: *#*#SERVICE#*#* >>service info>>configuration
if it says Bootloader unlocked allowed=yes then try as explained below ! It will definitely works !
I suggest you to first unlock your bootloader via the easy tool described at here http://forum.xda-developers.com/show....php?t=1560613
then flash the Doomkernel with the flashtool booting at fastboot mode. Before doing that never forget to install the necessary drivers.
The kernel is preloaded with custom recovery CWM and TWRP. While booting when you see doom logo pressing at 'vol +' you'll get CWM and pressing at camera button you'll get TWRP.
And flash the su and busybox package via recovery (CWM or TWRP)
for flashtool http://androxyde.github.io/
for kernel and su & busybox package: http://forum.xda-developers.com/show....php?t=2305591
& then enjoy Rooted jelly bean
ALL THE BEST !
Click to expand...
Click to collapse
My Bootloader is locked, Guessing I'm kinda screwed?
GrimTech said:
My Bootloader is locked, Guessing I'm kinda screwed?
Click to expand...
Click to collapse
Locked, ok...but is it unlockable : YES or NO ?
GrimTech said:
My Bootloader is locked, Guessing I'm kinda screwed?
Click to expand...
Click to collapse
If it says Bootloader unlocked allowed=yes then only follow the above steps carefully !
Then if Bootloader unlocked allowed=no, Remember your phone will never be unlocked !
zupadroid said:
Locked, ok...but is it unlockable : YES or NO ?
Click to expand...
Click to collapse
Ah, it says NO
I thought what I said was the same thing, Sorry, but it says NO
GrimTech said:
Ah, it says NO
I thought what I said was the same thing, Sorry, but it says NO
Click to expand...
Click to collapse
I'm guessing I can't root or Flash this thing
GrimTech said:
Ah, it says NO
I thought what I said was the same thing, Sorry, but it says NO
Click to expand...
Click to collapse
You said locked, not unlockable but that's too bad that it says NO, man.
zupadroid said:
You said locked, not unlockable but that's too bad that it says NO, man.
Click to expand...
Click to collapse
So I have no luck with Rooting or flashing?
Sigh, Guessing that's ok, I have a Galaxy Tab 2 7.0 Rooted and Flashed
GrimTech said:
So I have no luck with Rooting or flashing?
Sigh, Guessing that's ok, I have a Galaxy Tab 2 7.0 Rooted and Flashed
Click to expand...
Click to collapse
You can root it, but you can't flash custom ROM's.
zupadroid said:
You can root it, but you can't flash custom ROM's.
Click to expand...
Click to collapse
That sucks I guess, but Rooting is something I guess. was there a link on here already to root it in this thread?
GrimTech said:
That sucks I guess, but Rooting is something I guess. was there a link on here already to root it in this thread?
Click to expand...
Click to collapse
CLICK HERE
zupadroid said:
CLICK HERE
Click to expand...
Click to collapse
Heh, I tried this, but I get Error Type 3, I have no idea what it means though.
I have the ADB Drivers installed ect.
GrimTech said:
Heh, I tried this, but I get Error Type 3, I have no idea what it means though.
I have the ADB Drivers installed ect.
Click to expand...
Click to collapse
Search this and try it : DooMLoRD_Easy-Rooting-Toolkit_v14_perf-event-exploit
zupadroid said:
Search this and try it : DooMLoRD_Easy-Rooting-Toolkit_v14_perf-event-exploit
Click to expand...
Click to collapse
I did it, restarted. Did not appear to be rooted
GrimTech said:
I did it, restarted. Did not appear to be rooted
Click to expand...
Click to collapse
Install RootCecker and see if it is rooted. After that you can also try this SuperSU-1.25-Busybox-1.20.2-UPDATE.
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
Hello guys, I'm on LineageOS. I want to go back to Oxygen OS. But I can't because of my locked bootloader.
I did try to connect with the pc via adb: "Fastboot flash recovery recovery.img" and it's says everytime bootloader is locked enable OEM. I know the OEM is in the Developer Options but not for me. It's not available.
What to do now?
Code:
fastboot oem unlock
It will wipe all of your data.
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
djmcnz said:
It will wipe all of your data.
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Click to expand...
Click to collapse
Just did it. And than this error.
tap build number 7 times to enable developer options, enable usb debugging, then u do the adb.
MrTalon4 said:
Just did it. And than this error.
Click to expand...
Click to collapse
Yes, that means it's not enabled in developer options.
Now you say you don't have that OEM option available in the developer options - are you sure you've turned developer options on? If not do as @gorillaCF says above.
If you have done that and still don't have the option then back everything up, do a factory reset and try again immediately after that.
Flash factory images and go back to clean stock. Boot OOS and enable oem unlock in dev options
EugenStanis said:
Flash factory images and go back to clean stock. Boot OOS and enable oem unlock in dev options
Click to expand...
Click to collapse
Flash with locked bootloader? Is this possible?
What's broken with TWRP? What happens when you boot to recovery? Do you have adb access in any sort of recovery state?
djmcnz said:
What's broken with TWRP? What happens when you boot to recovery? Do you have adb access in any sort of recovery state?
Click to expand...
Click to collapse
I can't boot in recovery I will be stuck in the OnePlus logo.
And yes, I have adb access but my bootloader locked...
MrTalon4 said:
I can't boot in recovery I will be stuck in the OnePlus logo.
And yes, I have adb access but my bootloader locked...
Click to expand...
Click to collapse
Can you boot the stock recovery using fastboot?
the Doctor said:
Can you boot the stock recovery using fastboot?
Click to expand...
Click to collapse
It always says FAILED: "unlock device to use command". (Fastboot boot recovery.img)
MrTalon4 said:
It always says FAILED: "unlock device to use command". (Fastboot boot recovery.img)
Click to expand...
Click to collapse
There is always this, but it will wipe everything and completely reset your phone:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
^
do that.
LineageOS 15.1 doesn't have the OEM unlock feature. Normally, if you temper with the system and lock the bootloader it won't boot at all making this option useless. At least that's what I've experienced. As others stated you can only use the unbrick tool which will definitely work or contact OnePlus for an L2 technician who will use the same tool to do so.
So how did you do this? Did you do "fastboot oem lock" with TWRP and LineageOS on the device?
Macusercom said:
LineageOS 15.1 doesn't have the OEM unlock feature. Normally, if you temper with the system and lock the bootloader it won't boot at all making this option useless. At least that's what I've experienced. As others stated you can only use the unbrick tool which will definitely work or contact OnePlus for an L2 technician who will use the same tool to do so.
Click to expand...
Click to collapse
Why the hell LineageOS 15.1 don't have the OEM unlock? This makes no sense, because now I have a big problem.
Yeah, the unbrick tool I'm lucky but for the others with different devices will not have this unbrick tool. That's very stupid. It will be last time for me, with LineageOS.
the Doctor said:
So how did you do this? Did you do "fastboot oem lock" with TWRP and LineageOS on the device?
Click to expand...
Click to collapse
I did nothing like this. It was just locked I was surprised to.
MrTalon4 said:
I did nothing like this. It was just locked I was surprised to.
Click to expand...
Click to collapse
Normally, it is impossible to lock it without fastboot. Again, it's not LOS's fault. You should never lock your bootloader if on a custom ROM or modified system. I've been running LOS 15.1 for almost a week and never had such an issue.
MrTalon4 said:
Flash with locked bootloader? Is this possible?
Click to expand...
Click to collapse
Yes, afaik You can flash factory images without unlocking bootloader
EugenStanis said:
Yes, afaik You can flash factory images without unlocking bootloader
Click to expand...
Click to collapse
Sorry sir, but the factory Images means stock ROM and stock recovery.
Can't flash both
Why there is no backdoor for this situation? Why is this not possible, that you need by Factory images no unlocked bootloader. That would fix many problems.
Hello!
i have got a Problem...
my usb c port is broken. the only thing that is working is loading the battery.
i can factory reset the smartphone for return to google, but my problem is the bootloader. any ideas, how i can relock the bootloader withput using my computer? ?
thank you!
Blooddrunked said:
Hello!
i have got a Problem...
my usb c port is broken. the only thing that is working is loading the battery.
i can factory reset the smartphone for return to google, but my problem is the bootloader. any ideas, how i can relock the bootloader withput using my computer?
thank you!
Click to expand...
Click to collapse
if you're returning it to Google they don't really care if it's locked or not. I've sent them back for an RMA both ways never had any problems
Agree, relocking shouldn't be needed for a RMA...
Just make sure your device is completely stock at the very least.
Personally, I'd flash the factory images to both slots and lock the bootloader. However, if others have suggested they don't have any issues sending it back with the bootloader unlocked, then just flash the factory images.
Although, it is just one command to lock it (just be absolutely sure you're completely stock before locking, if you go that route).
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ??
Blooddrunked said:
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ?
Click to expand...
Click to collapse
You can't, and don't worry about it.
Blooddrunked said:
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ??
Click to expand...
Click to collapse
You could download the OTA zip and move it to your data folder with a root explorer type app, then flash it with twrp. Will twrp not decrypt without screen lock security?
Badger50 said:
You could download the OTA zip and move it to your data folder with a root explorer type app, then flash it with twrp. Will twrp not decrypt without screen lock security?
Click to expand...
Click to collapse
Thank you! it worked!
Blooddrunked said:
Thank you! it worked!
Click to expand...
Click to collapse
Well there ya go! Your welcome. :good::good:
how long does it take to get the replacement from google??
That's exactly why I never unlock the bootloader, root, install custom ROMs, etc. I don't want to be in the situation where I can't use my warranty or insurance.
kismetmookz said:
how long does it take to get the replacement from google??
Click to expand...
Click to collapse
My bootloader was unlocked and it was not an issue. I sent my phone back and got a new phone in 6 days. I guess it would also depend on where you live. I live on the east coast and sent my phone to Texas and they sent me a new one from Illinois.
Hey guys,
i just want to ask if there is a tested method to relock the bootloader of a rooted A2 Lite.
I use the stock rom, just unlocked and rooted it.
I've read something about the MiFlashTool and the Clean and Lock Option.
But I'm not sure about that, because the MiFlashTool is for Miui.
So what are the steps to relock the bootloader?
Thank you for your help
Mansil234 said:
Hey guys,
i just want to ask if there is a tested method to relock the bootloader of a rooted A2 Lite.
I use the stock rom, just unlocked and rooted it.
I've read something about the MiFlashTool and the Clean and Lock Option.
But I'm not sure about that, because the MiFlashTool is for Miui.
So what are the steps to relock the bootloader?
Thank you for your help
Click to expand...
Click to collapse
The MiFlashTool is also for the Stock Rom of the Mi A2 Lite (Not only MIUI!)
Download the Stock Rom and you can flash it via MiFlash. If you choose the option, you can relock the Bootloader when you do this.
Woah there buddy, if you try to lock a rooted phone you will have a hard brick. Don't try to lock the bootloader of a phone that is rooted or have system/boot etc. modifications.
marstonpear said:
Woah there buddy, if you try to lock a rooted phone you will have a hard brick. Don't try to lock the bootloader of a phone that is rooted or have system/boot etc. modifications.
Click to expand...
Click to collapse
And If i First delete the root-rights?
Mansil234 said:
And If i First delete the root-rights?
Click to expand...
Click to collapse
Not sure if it would work, the cleanest way would be to download official fastboot ROM, flash it via MiFlash (select clean and lock option). This will erase all your data and turn your phone to stock ROM. I'm saying this is the cleanest way because you may have issues by unrooting and locking the phone. Maybe it would work. Unsure.
marstonpear said:
Not sure if it would work, the cleanest way would be to download official fastboot ROM, flash it via MiFlash (select clean and lock option). This will erase all your data and turn your phone to stock ROM. I'm saying this is the cleanest way because you may have issues by unrooting and locking the phone. Maybe it would work. Unsure.
Click to expand...
Click to collapse
But you said that this would brick my device?
Mansil234 said:
But you said that this would brick my device?
Click to expand...
Click to collapse
He meant: If you have root acces with magisk first of all uninstall root and relock bootloader
Kineceleran said:
He meant: If you have root acces with magisk first of all uninstall root and relock bootloader
Click to expand...
Click to collapse
Ok, this was a misunderstanding
If you lock your bl at a modified system, you will get the message "your system got destroyed", I once had this. But I was lucky being able to unlock again... So no hardbrick... But doing all that leads to nothing. Btw. it's always useful to have an open bl... For example, if you mess up with a magik module and stuck @boot... Just ignore the stupid message of xiaomi!
Voodoojonny said:
If you lock your bl at a modified system, you will get the message "your system got destroyed", I once had this. But I was lucky being able to unlock again... So no hardbrick... But doing all that leads to nothing. Btw. it's always useful to have an open bl... For example, if you mess up with a magik module and stuck @boot... Just ignore the stupid message of xiaomi!
Click to expand...
Click to collapse
To prevent this, i want to remove the root access in the first place.
That i have a clean stock rom.
I tried it with no-data-loss method and it says, system is destroyed, i have it to unlock it.
With root, you can relock it, but it's useless.
Mansil234 said:
To prevent this, i want to remove the root access in the first place.
That i have a clean stock rom.
Click to expand...
Click to collapse
Backup up everything first
Download MiFlash and the correct ROM (not OTA version)
Then you can flash the Stock ROM which will remove everything
You can also choose to leave unlocked or lock the bootloader (re-lock is selected by default)
As this is a somewhat new device I wouldn't tick the option to save your data.
capajga said:
Backup up everything first
Download MiFlash and the correct ROM (not OTA version)
Then you can flash the Stock ROM which will remove everything
You can also choose to leave unlocked or lock the bootloader (re-lock is selected by default)
As this is a somewhat new device I wouldn't tick the option to save your data.
Click to expand...
Click to collapse
What is the correct rom if not the OTA-Version?
Mansil234 said:
What is the correct rom if not the OTA-Version?
Click to expand...
Click to collapse
Take a look at this thread:
https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913
you can find pretty much all ota's and fastboot rom links.
All full ROMs end with .tgz extension
like this one:
http://bigota.d.miui.com/V9.6.4.0.O...0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2.tgz
you have to extract it to be able to use it with MiFlash but I'm sure you'll find all the answers in the thread above
capajga said:
Take a look at this thread:
https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913
you can find pretty much all ota's and fastboot rom links.
All full ROMs end with .tgz extension
like this one:
http://bigota.d.miui.com/V9.6.4.0.O...0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2.tgz
you have to extract it to be able to use it with MiFlash but I'm sure you'll find all the answers in the thread above
Click to expand...
Click to collapse
Thanks! Everything went fine!
Mansil234 said:
Thanks! Everything went fine!
Click to expand...
Click to collapse
Glad to hear it :laugh: