Develop Bugs

Guide for Safe installation of any custom rom on your stock rom mobile

Installation Steps (Warranty can be restored whenever you wish)
-------------------------
Before starting your rom flashing journey it is always better to have Flashtool (latest -by androxyde) installed in your PC and your stock rom handy ; incase of any mishappenings.
Type *#*#7378423#*#* in your phone and see if your bootloader status is unlockable under service-->Configuration. Procede with below steps, only if your device is unlockable.
It is important that you follow the steps in order
1) First step for installing a custom rom over a mobile with stock rom is to backup the existing state of bootloader .Usually warranty will get void if any modification is done to bootloader. The below tool ensures that it takes the backup of existing state of bootloader when device is under warranty.
Goto
Backup TA for Sony Xperia (This tool helps you to have a )
http://forum.xda-developers.com/showthread.php?t=2292598.
Download the tool.This tool will backup your DRM Securtiy keys . Successful backup can only be taken after the existing stock rom is rooted (Use towelroot application if your device is not already rooted) .Root it first then follow the process given in above link .
Once this is over , u will have a backup of the existing state of bootloader/TA partition (If you later wish to move back to stock rom from custom rom use the same tool to restore the backup you have just created.This means you will get your Warranty back);
2) Goto this website , follow the steps and get your unlock code via e mail.
Use fastboot mode to unlock your bootloader (Make sure that you have already backuped your existing DRM keys-Step 1).Follow it fully to unlock your bootloader
http://unlockbootloader.sonymobile.com/unlock/step1
3)Download any custom rom zips with recovery, for your mobile from xda developers forum and have fun.Extract boot.img using winrar or winzip .
Flash boot.img via fastboot mode
fastboot flash boot boot.img
fastboot reboot
4)As the device reboots, when you see your LED glow press volume up or down. It will take you to CWM Recovery or TWRP recovery based on the rom that you have downloaded.
5)Just install the custom rom(*.zip ) from within the recovery.

What if that i already have the custom recovery?
So, just wipe data, dalvik, and cache, then flash the zip?
That's it?

AndreIrawan97 said:
What if that i already have the custom recovery?
So, just wipe data, dalvik, and cache, then flash the zip?
That's it?
Click to expand...
Click to collapse
yes.

AndreIrawan97 said:
What if that i already have the custom recovery?
So, just wipe data, dalvik, and cache, then flash the zip?
That's it?
Click to expand...
Click to collapse
Absolutely right. But before installing an custom rom in the first place i hope you have already backed up your DRM keys for warranty purpose(as mentioned in the guide) since if you unlock your bootloader without backing up your DRM keys, DRM keys might be lost forever .

gokukaushik said:
Absolutely right. But before installing an custom rom in the first place i hope you have already backed up your DRM keys for warranty purpose(as mentioned in the guide) since if you unlock your bootloader without backing up your DRM keys, DRM keys might be lost forever .
Click to expand...
Click to collapse
Can i backup my app on stock rom then restore it to a custom rom?

AndreIrawan97 said:
Can i backup my app on stock rom then restore it to a custom rom?
Click to expand...
Click to collapse
Sure. Easiest way to do it is by using an app called, 'Titanium Backup Pro'.But you have to root your stock rom first for this application to run(Use towelroot if you are yet to root).Except for sony proprietary apps like walkman,Album,etc (will run only on stock rom as they use sony developed system libraries/API'S) other apps will get restored/run fine on a custom rom.

gokukaushik said:
Sure. Easiest way to do it is by using an app called, 'Titanium Backup Pro'.But you have to root your stock rom first for this application to run(Use towelroot if you are yet to root).Except for sony proprietary apps like walkman,Album,etc (will run only on stock rom as they use sony developed system libraries/API'S) other apps will get restored/run fine on a custom rom.
Click to expand...
Click to collapse
And one think left.... How to know if my bootloader is unlocked or not?

AndreIrawan97 said:
And one think left.... How to know if my bootloader is unlocked or not?
Click to expand...
Click to collapse
its in the OP....on the phones dialpad, type: *#*#7378423#*#*
then look in > service > configuration
it should show the status as "bootloader locked", "bootloader unlocked", "bootloader unlockable" or "not unlockable" (sorry wording may not be exact, but you'll get the idea)

foomanjackel said:
its in the OP....on the phones dialpad, type: *#*#7378423#*#*
then look in > service > configuration
it should show the status as "bootloader locked", "bootloader unlocked", "bootloader unlockable" or "not unlockable" (sorry wording may not be exact, but you'll get the idea)
Click to expand...
Click to collapse
no.. i mean, how to know if my bootloader is already unlocked or not?
Anyway, what happened if i flash it without unlocking it first?

Sorry, did you type that in the phone and check the status? That's where it will tell you if its already unlocked or if its even unlockable at all.
Do not try to install a custom ROM on your phone if it is not unlocked! Your phone will not boot.

AndreIrawan97 said:
no.. i mean, how to know if my bootloader is already unlocked or not?
Anyway, what happened if i flash it without unlocking it first?
Click to expand...
Click to collapse
Thanks to @ foomanjackel for answering your questions.Regarding your 2nd question, 'Experience is the mother of invention'.Why don't you try and see what happens...just kidding.Couldn't resist it. Practically speaking of you install a custom rom with an custom kernel on a locked bootloader you will hard brick it.It will not boot and chances are that you might not be able to goto flashmode or fastbootmode anymoreto repair it.Reason this happens is that both your recovery and bootloader resides in the same partition in your mobile.If you try to install custom kernel on a locked bootloader in every probability, it not only corrupts your existing stocks kernel but also might corrupt your recovery leaving u helpless.
Theoretically, You should be able to install any custom-stock based rom on a locked bootloader (which runs exactly on ur stock kernel).In other words a custom rom which doesn't come up with a custom kernel but based on your existing stock kernel should be able to run on a locked bootloader.But my advice is you do not risk it.

foomanjackel said:
Sorry, did you type that in the phone and check the status? That's where it will tell you if its already unlocked or if its even unlockable at all.
Do not try to install a custom ROM on your phone if it is not unlocked! Your phone will not boot.
Click to expand...
Click to collapse
Yes it said boot loader unlockable : yes
And couple months ago, i want to unlock my bootloader, but i dont know what went wrong, but my xperia got boot loop...
So is that bcs i already unlocked it? Or... ?

AndreIrawan97 said:
Yes it said boot loader unlockable : yes
And couple months ago, i want to unlock my bootloader, but i dont know what went wrong, but my xperia got boot loop...
So is that bcs i already unlocked it? Or... ?
Click to expand...
Click to collapse
If you get this message "Bootloader unlockable: yes" then your bootloader is still locked.

gokukaushik said:
If you get this message "Bootloader unlockable: yes" then your bootloader is still locked.
Click to expand...
Click to collapse
Is unlocking bootloader can make me lose my root?

AndreIrawan97 said:
Is unlocking bootloader can make me lose my root?
Click to expand...
Click to collapse
I suppose it won't.I don't see the reason why u want to unlock the bootloader unless you want to install a new custom rom.

Is there a guide for back to stock

Hi
Is there a guide for going back to stock. I bought this mi max rooted. Right now I'm on RR rom and having the shutdown bug. So I need to go back to stock rom.
THX in advance

http://en.miui.com/extra.php?mod=rom/download&r=302&mobile=no
download the rom in .zip format flash it from twrp
make sure to check all boxes when formatting except sd card (if you have one)

Mr.Salman said:
http://en.miui.com/extra.php?mod=rom/download&r=302&mobile=no
download the rom in .zip format flash it from twrp
make sure to check all boxes when formatting except sd card (if you have one)
Click to expand...
Click to collapse
Thank you. Kind of newbe to this, will I loose root by flashing that rom? Will bootloader be locked again? Should I take the original or developer rom?
Again, thx

yes you have to root again. make sure to flash right after u flash any rom(global,dev)
global will be better dont go for dev.
it doesnt re-lock bootloader but if it does unlocking is easy

Mr.Salman said:
yes you have to root again. make sure to flash right after u flash any rom(global,dev)
global will be better dont go for dev.
it doesnt re-lock bootloader but if it does unlocking is easy
Click to expand...
Click to collapse
Thank you again!

Mr.Salman said:
yes you have to root again. make sure to flash right after u flash any rom(global,dev)
global will be better dont go for dev.
it doesnt re-lock bootloader but if it does unlocking is easy
Click to expand...
Click to collapse
Easy?,Can you tell us how to unlock bootloader if not having to wait? Been looking for a guide for ages. Can you do it on global rom or only china?

if you've unlocked once
unlocking again is nt a pain
applied ,got permission in a day
unlock took a week.
i've even unlocked with find device off on a global rom.

Bootloop after flashing stock image

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)

Mi 5s flashable firmware

I'm currently on Miui 8.5 global stable, rooted n twrpd. I'm trying to install RR Rom but keep getting Error 7 "modem check fail". So basically I can either edit a file update script. txt in Rom or flash latest firmware. I don't want to edit file as that's their for a reason so I'd rather flash firmware but can't find it.
Please could someone help?
Many thanks

I had this error when tried to install LineageOS at first.
Download and flash "Xiaomi Mi 5s Latest China Developer Version Fastboot File Download" from here: http://en.miui.com/a-234.html
And then try to flash your rom again, it worked for me

quarvin said:
I had this error when tried to install LineageOS at first.
Download and flash "Xiaomi Mi 5s Latest China Developer Version Fastboot File Download" from here: http://en.miui.com/a-234.html
And then try to flash your rom again, it worked for me
Click to expand...
Click to collapse
Will this lock bootloader? Also will I have to twrp & root again?
Can I restore in twrp after flashing above rom?

alien_jiggy said:
Will this lock bootloader? Also will I have to twrp & root again?
Can I restore in twrp after flashing above rom?
Click to expand...
Click to collapse
You can choose when you install with Mi Flash between: clean all / keep user data / clean and lock
I don't think the keep user data will work well, but I'm pretty sure you can use "clean all" without the lock and it will work.
I think I did with lock just to be sure, because unlocking again is about 20 seconds (after you received the required permission for your account from Xiaomi).
No matter what you choose to do, as long as you can unlock you bootloader, you can re-flash your recovery / rom / root / everything you want, it's not a problem.

quarvin said:
You can choose when you install with Mi Flash between: clean all / keep user data / clean and lock
I don't think the keep user data will work well, but I'm pretty sure you can use "clean all" without the lock and it will work.
I think I did with lock just to be sure, because unlocking again is about 20 seconds (after you received the required permission for your account from Xiaomi).
No matter what you choose to do, as long as you can unlock you bootloader, you can re-flash your recovery / rom / root / everything you want, it's not a problem.
Click to expand...
Click to collapse
OK many thanks
Actually this phone came with unlocked bootloader when bought from someone

alien_jiggy said:
OK many thanks
Actually this phone came with unlocked bootloader when bought from someone
Click to expand...
Click to collapse
No problem
I would recommend you to apply for unlocking permission for your MI account, so you will already have it when you need it:
http://en.miui.com/unlock

in the file script you need to remove the first two lines please enter the Video

I've actually just installed dev rom & all is working now. Thanks guys

Relock bootloader for return

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.