Related
Hi everyone, I have an Xperia Acro S and recently I wanted to unlock my bootloader to get acces installing custom ROMs, now I've a question about unlocking the bootloader, I have read/seen many tutorials/videos where explain the official way to unlock the bootloader, in all of them say that I need to provide the IMEI to the Sony web, so I can get an unlock code; the IMEI has 15 digits, but I've seen only first 14 digits it's needed, today I used the entire 15 digits, got an unlocked code, but I don't know if I'm in the right way, or I need to ask for another code using just the first 14 digits.
I hope anyone could help me.
Thanks in advance.
Strik3_rAm said:
Hi everyone, I have an Xperia Acro S and recently I wanted to unlock my bootloader to get acces installing custom ROMs, now I've a question about unlocking the bootloader, I have read/seen many tutorials/videos where explain the official way to unlock the bootloader, in all of them say that I need to provide the IMEI to the Sony web, so I can get an unlock code; the IMEI has 15 digits, but I've seen only first 14 digits it's needed, today I used the entire 15 digits, got an unlocked code, but I don't know if I'm in the right way, or I need to ask for another code using just the first 14 digits.
I hope anyone could help me.
Thanks in advance.
Click to expand...
Click to collapse
Nah You are doing right, only first 14 digits are shown online since it is not safe to publish own imei on internet. Since You received an unlock code, it is safe to assume that You are going the correct way.
Mirhawk said:
Nah You are doing right, only first 14 digits are shown online since it is not safe to publish own imei on internet. Since You received an unlock code, it is safe to assume that You are going the correct way.
Click to expand...
Click to collapse
So, you're telling me that It's ok I provided the entire 15 digits to the web, and got an unlock code, so I can continue the procedure and unlock my bootloader? This just scare me, because I don't want to make unusable my device. Thanks for your reply.
Strik3_rAm said:
So, you're telling me that It's ok I provided the entire 15 digits to the web, and got an unlock code, so I can continue the procedure and unlock my bootloader? This just scare me, because I don't want to make unusable my device. Thanks for your reply.
Click to expand...
Click to collapse
Yes, as long as You provide it on the Sony website, it is safe to do the procedure. And don't worry, it won't make Your device un usable.
Mirhawk said:
Yes, as long as You provide it on the Sony website, it is safe to do the procedure. And don't worry, it won't make Your device un usable.
Click to expand...
Click to collapse
Sir, can you please help me with this... I wanted to get this ROM for my Xperia Acro S http://forum.xda-developers.com/show....php?t=2790532, I just don't want to make it wrong, the instrucctions in the thread shows a Samsung S2 https://www.youtube.com/watch?v=jDQ_ER0mU9Y, can I use the same instructions and flash it to my Acro S? I already have unlocked my bootloader, and I'm on 4.1.2 - 6.2.B.1.96, and CMW-based Recovery v6.0.3.0.
Thanks for the reply.
Strik3_rAm said:
Sir, can you please help me with this... I wanted to get this ROM for my Xperia Acro S http://forum.xda-developers.com/show....php?t=2790532, I just don't want to make it wrong, the instrucctions in the thread shows a Samsung S2 https://www.youtube.com/watch?v=jDQ_ER0mU9Y, can I use the same instructions and flash it to my Acro S? I already have unlocked my bootloader, and I'm on 4.1.2 - 6.2.B.1.96, and CMW-based Recovery v6.0.3.0.
Thanks for the reply.
Click to expand...
Click to collapse
1-Put the rom on sdcard
2-Flash boot.img (inside zip) with fastboot
3-Boot into recovery and wipe system, data, cache and dalvik
4-Install the rom then gapps
5-Reboot
Strik3_rAm said:
Sir, can you please help me with this... I wanted to get this ROM for my Xperia Acro S http://forum.xda-developers.com/show....php?t=2790532, I just don't want to make it wrong, the instrucctions in the thread shows a Samsung S2 https://www.youtube.com/watch?v=jDQ_ER0mU9Y, can I use the same instructions and flash it to my Acro S? I already have unlocked my bootloader, and I'm on 4.1.2 - 6.2.B.1.96, and CMW-based Recovery v6.0.3.0.
Thanks for the reply.
Click to expand...
Click to collapse
darknessmc said:
1-Put the rom on sdcard
2-Flash boot.img (inside zip) with fastboot
3-Boot into recovery and wipe system, data, cache and dalvik
4-Install the rom then gapps
5-Reboot
Click to expand...
Click to collapse
Do as per the instructions given by darknessmc, just an addition that clean only cache and dalvik immediately after You flash the ROM.
Thank you both, I finally got what I wanted, finally got a ROM on my device, actually was very scary, because the TWRP was in chinesse, I've got a hearthattack when I saw the symbols. :S:S:S
But Google translator and another guides helped me out. :good:
Hi guys, I've a question, if I want to install ahother ROM, do I just follow the steps you gave me before? I mean, that step when I need to enter in fastboot mode and flash the boot.img. Thanks @Mirhawk @darknessmc
Strik3_rAm said:
Hi guys, I've a question, if I want to install ahother ROM, do I just follow the steps you gave me before? I mean, that step when I need to enter in fastboot mode and flash the boot.img. Thanks @Mirhawk @darknessmc
Click to expand...
Click to collapse
Yes, if it is a Kitkat based ROM.
@Mirhawk
Hello, how have you been? Mr. I have another question about all this, flashing with FLASHTOOL is the same as flashing with the recovery? If i want to flash a new ROM and in its instructions says I need to flash it using the flashtool, do I just follow your previous steps or I need to install the flashtool? thanks
Strik3_rAm said:
@Mirhawk
Hello, how have you been? Mr. I have another question about all this, flashing with FLASHTOOL is the same as flashing with the recovery? If i want to flash a new ROM and in its instructions says I need to flash it using the flashtool, do I just follow your previous steps or I need to install the flashtool? thanks
Click to expand...
Click to collapse
Hello, If you flashing a stock rom you use flashtool but if it's a custom rom your phone has to be rooted. Please follow the steps to root and etc.
"If you come from a stock Sony firmware image please flash this kernel before via fastboot:
Quote:
Attention: your bootloader need to be unlocked to flash a custom rom like SlimBean.....a good step by step tutorial you find here:
http://androidlegend.com/how-to-unlo...peria-s-lt26i/
after that you can go ahead with the next steps below
1. Download:
(Kernel or if the rom has a boot.img file that will work)
2. Turn your phone off and hold the volume up button and plug in your USB connection and wait till the LED is getting blue
3. Terminal command to flash:
fastboot flash boot boot.img
4. Reboot your phone and wait till your LED turns violett....in this moment push the volume up button and you have access to your custom recovery
5. Connect your phone with USB and push the downloaded roms and gapps to your phone now with the terminal command:
adb push <filename> /sdcard/
6. Wipe data/cache/dalvic, format system, flash the rom and the gapps and you are finished "
The end. Good luck Please have you custom ready on hand. Download SMS backup app to backup your sms's, root not need for this. Your apps should download on it's own after a few minutes when the phone is on and working.
Happy modding.
Strik3_rAm said:
@Mirhawk
Hello, how have you been? Mr. I have another question about all this, flashing with FLASHTOOL is the same as flashing with the recovery? If i want to flash a new ROM and in its instructions says I need to flash it using the flashtool, do I just follow your previous steps or I need to install the flashtool? thanks
Click to expand...
Click to collapse
No, flashing with flashtool and recovery is different.
Flashtool : You can only flash stock firmware(the .ftf files) or kernel (.img , .elf etc) using flashtool.
Recovery : The recovery is used to flash the ROM and kernel's in zip format, they cannot flash .ftf files. Also they can't flash files if they are not in zip.
If You are going to use a stock based ROM(i.e. JB ROM's) then some Developers need You to flash the Stock firmware(ftf file) first and then flash their ROM. So You flash the stock firmware(ftf) via flashtool and then flash the ROM after installing a recovery.
If You are going to flash a Kitkat ROM, then simply follow the earlier steps.
From what I've read it seems that you have to unlock bootloader to do this. Which is something I am finding hard to digest.
Do I really need to unlock bootloader to flash official build? Or is there some official way which I can't seem to find?
Piyush Rawal said:
From what I've read it seems that you have to unlock bootloader to do this. Which is something I am finding hard to digest.
Do I really need to unlock bootloader to flash official build? Or is there some official way which I can't seem to find?
Click to expand...
Click to collapse
Didn't find a way without data wipe.. but my bootloader is locked and never rooted on this OP3, as long as your OP3 is encrypted I don't think there is a way without loosing data.
I have completely wiped the system using stock recovery and now I can't flash anything. When I try to sideload it says can't read the zip file.
I've tried with both community and official zip.
Any idea what's going on?
Piyush Rawal said:
I have completely wiped the system using stock recovery and now I can't flash anything. When I try to sideload it says can't read the zip file.
I've tried with both community and official zip.
Any idea what's going on?
Click to expand...
Click to collapse
Seems like adb drivers issue (on Windows?) many are facing. What worked for me is to cut/paste zip to desktop and then immediately cut/paste back to adb folder (without closing command prompt) and typing adb sideload zip again..
See if it helps..
Piyush Rawal said:
I have completely wiped the system using stock recovery and now I can't flash anything. When I try to sideload it says can't read the zip file.
I've tried with both community and official zip.
Any idea what's going on?
Click to expand...
Click to collapse
Had that issue recently. Just rebooted my PC, and that fixed it.
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)
Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?
flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !
porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does
flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well
I am not responsible for any brick.
I tested this guide myself and decided to share it.
Make a backup before this guide because you will lose your data!
The unlock method has been updated and now you can unlock the bootloader more easily without the risk of bricking after an OTA and without changing the bootloader.
Now you can safely unlock the bootloader using mtkclient.
Link: https://github.com/bkerler/mtkclient
TWRP can be installed via mtkclient or manually from rooted Android.
TWRP Download link: https://github.com/XRedCubeX/twrp_meizu_m5c/releases
IF you unlocked the bootloader with the old method you can follow these steps:
1) Download the attached package.
2) Download OTA zip from flyme, link: http://www.flymeos.com/firmwarelist?modelId=70&type=1
3) Download the latest version of SP Flash Tool.
4) Download MTKClient and follow the instructions to install it.
5) Power off the phone and keep unplugged it from PC.
6) Open SP Flash Tool, select the downloaded package and select all partitions, then press the download button, don't plug phone for now.
7) Boot to recovery with vol +, plug the phone on PC, depending on recovery, TWRP or stock, use adb sideload or put update.zip in internal memory and install the zip.
8) Let the phone reboot or reboot it manually.
9) Now start the flash from SP Flash tool automatically, let it finish.
10) After the flash, unplug the phone and reboot into recovery.
11) Paste the update.zip in the phone and flash it.
12) After reboot, let your phone reboot into android and power off.
13) You can follow the guide to unlock bootloader with mtkclient.
FAQ:
A) But will I lose the data with this guide?
Yes.
Make sure to back up your data in any case!
B) But this guide is a bit different than usual, where is "fastboot oem unlock"? Or "fastboot flashing unlock"?
Meizu has not implemented an unlock command and in this case to unlock the bootloader we have to use a tool that makes us change the unlock status.
C) Are there Custom ROMs?
There is only one custom ROM for this device, the Lineage OS 14 but I advise against using it because it has a bit of a bug but I haven't had more time to work on it yet.
D) But wasn't the guide different?
It has been updated with a better method with more advantages.
E) My device is in Hard Brick! How can I solve?
There are various types of Hard Brick and it depends from situation to situation.
F) I have installed Lineage OS 14 but I am not satisfied, I want to go back to Flyme!
Flash update.zip from official website.
G) Can I relock the bootloader?
From MTKClient readme:
for relocking use:
python mtk da seccfg lock
Click to expand...
Click to collapse
H) TWRP? I am interested in Device Tree, where is the link?
Here: https://github.com/XRedCubeX/twrp_meizu_m5c
I) I have a Meizu A5 (Chinese M5c) will it work on it?
I can't assure you anything but it could work, the only way to be sure is to test on a Meizu A5.
J) Can I flash twrp from fastboot?
Fastboot refuses to flash partitions, strangely, I don't know if downgrade or anything changes the situation but for now I was able to flash it with mtkclient.
I can remove the FlameOs from the Meizu M5c and install a custom rom. So far I haven't found any rom for this device?
Mortaux said:
I can remove the FlameOs from the Meizu M5c and install a custom rom. So far I haven't found any rom for this device?
Click to expand...
Click to collapse
Im working on a Lineage OS 14 for this device.
I tried the procedure and it failed. Apparently it just formatted it but couldn't finish the process, returned an error. Then I tried to reinstall the stock ROM and it generated the error S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004). Now my phone is off and I can't turn it on anymore.
I tried this method but it didn't work:
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004) Follow the following steps: 1. Get SP flash tools (Latest version) 2. Download your...
forum.xda-developers.com
I know it's my responsibility, but I don't know what else to do. Could someone please help me?
thiagosousa777 said:
I tried the procedure and it failed. Apparently it just formatted it but couldn't finish the process, returned an error. Then I tried to reinstall the stock ROM and it generated the error S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004). Now my phone is off and I can't turn it on anymore.
I tried this method but it didn't work:
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004) Follow the following steps: 1. Get SP flash tools (Latest version) 2. Download your...
forum.xda-developers.com
I know it's my responsibility, but I don't know what else to do. Could someone please help me?
Click to expand...
Click to collapse
You unplugged the device while it was formatting, consequently it no longer has the bootloader, that error means that the device needs an authorization file that unfortunately only meizu has, shortly if I can try to release a tool to unbrick it in cases similar to these
XRed_CubeX said:
You unplugged the device while it was formatting, consequently it no longer has the bootloader, that error means that the device needs an authorization file that unfortunately only meizu has, shortly if I can try to release a tool to unbrick it in cases similar to these
Click to expand...
Click to collapse
It's a shame .. I hope you can really release this tool, so I can revive my phone. Thank you.
You can make a video on youtube showing the procedure on the Meizu M5c. Installing Twrp and LineageOs 14? Just to make sure it works
Mortaux said:
You can make a video on youtube showing the procedure on the Meizu M5c. Installing Twrp and LineageOs 14? Just to make sure it works
Click to expand...
Click to collapse
For now I can't make the video because I can't release the Lineage because I'm fixing some bugs and I want to do some checks before releasing it publicly
thiagosousa777 said:
It's a shame .. I hope you can really release this tool, so I can revive my phone. Thank you.
Click to expand...
Click to collapse
Ok i found a working guide, tried on my M5c and it works:
Search on YouTube: flash mtk without da ,
You will find a video called, just exactly as I write here: "How to flash MTK secure boot devices without a custom DA" and follow the video tutorial for unbrick your device.
P.S:Obviously when the guide ends you flash the ROM from SP flash tool as you normally would
XRed_CubeX said:
Ok i found a working guide, tried on my M5c and it works:
Search on YouTube: flash mtk without da ,
You will find a video called, just exactly as I write here: "How to flash MTK secure boot devices without a custom DA" and follow the video tutorial for unbrick your device.
P.S:Obviously when the guide ends you flash the ROM from SP flash tool as you normally would
Click to expand...
Click to collapse
I'll try that, thanks a lot!
thiagosousa777 said:
I'll try that, thanks a lot!
Click to expand...
Click to collapse
Did you finally manage to fix the device?
Were you able to get on with the guide?
XRed_CubeX said:
Did you finally manage to fix the device?
Were you able to get on with the guide?
Click to expand...
Click to collapse
I haven't had time to do it yet. When I have time I will follow the tutorial and tell you if it worked.
thiagosousa777 said:
I haven't had time to do it yet. When I have time I will follow the tutorial and tell you if it worked.
Click to expand...
Click to collapse
Ok good luck
XRed_CubeX said:
Ok good luck
Click to expand...
Click to collapse
XRed_CubeX, I followed the tutorial from start to finish. I used the SP Flash Tool to install the M5c stock ROM, the ROM was flashed 100%, but after disconnecting the USB cable the phone did not turn on.
thiagosousa777 said:
XRed_CubeX, I followed the tutorial from start to finish. I used the SP Flash Tool to install the M5c stock ROM, the ROM was flashed 100%, but after disconnecting the USB cable the phone did not turn on.
Click to expand...
Click to collapse
Have you flashed the Stock ROM or the Engineering ROM? I remind you that even if you have flashed the eng rom only once previously, you can no longer return to the flyme bootloader so use the normal stock ROM but you will have to flash the Engineering rom
XRed_CubeX said:
Have you flashed the Stock ROM or the Engineering ROM? I remind you that even if you have flashed the eng rom only once previously, you can no longer return to the flyme bootloader so use the normal stock ROM but you will have to flash the Engineering rom
Click to expand...
Click to collapse
Well, I flashed the stock ROM a second time, using the Firmware Upgrade option, and it worked. My phone turned on and I'm in the initial setup screen.
By the way, this Engineering ROM is the ROM you shared above? Do you think it is stable enough to be used? Maybe another day I'll install it, with care to not do anything wrong again
thiagosousa777 said:
Well, I flashed the stock ROM a second time, using the Firmware Upgrade option, and it worked. My phone turned on and I'm in the initial setup screen.
By the way, this Engineering ROM is the ROM you shared above? Do you think it is stable enough to be used? Maybe another day I'll install it, with care to not do anything wrong again
Click to expand...
Click to collapse
Yes, the ROM in this thread is ROM engineering, about the stability I can't tell you why I haven't tested it, the main purpose FOR ME was to get the bootloader unlock with this ROM, if you want to switch to ROM engineering you CAN install the flyme after installed the Engineering ROM but you must always modify the OTA zip so that some partitions do not flash but if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering
XRed_CubeX said:
Yes, the ROM in this thread is ROM engineering, about the stability I can't tell you why I haven't tested it, the main purpose FOR ME was to get the bootloader unlock with this ROM, if you want to switch to ROM engineering you CAN install the flyme after installed the Engineering ROM but you must always modify the OTA zip so that some partitions do not flash but if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering
Click to expand...
Click to collapse
Actually, the ROM I installed with SP Flash Tools was not the update.zip from the official Flyme OS website. I downloaded the stock rom from needrom.
I have done this several times before.
But now, strangely I can no longer update to the latest version. The version I'm running is Flyme 6.0.2.0G. I tried to download the update.zip file and install it manually by clicking on it, and it appeared "corrupted file". I also tried to use the Update application and "network error" appeared. But everything else is working perfectly.
XRed_CubeX said:
if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering
Click to expand...
Click to collapse
I would like to know how to install the latest version of Flyme OS via TWRP. If you can tell how to do this..
XRed_CubeX said:
can't release the Lineage because I'm fixing some bugs and I want to do some checks before releasing it publicly
Click to expand...
Click to collapse
Are you working on a custom Lineage OS ROM for this device? I'm interested, when you can publish it.. Do you have a prediction of when you will be able to release that ROM?
thiagosousa777 said:
I would like to know how to install the latest version of Flyme OS via TWRP. If you can tell how to do this..
Are you working on a custom Lineage OS ROM for this device? I'm interested, when you can publish it.. Do you have a prediction of when you will be able to release that ROM?
Click to expand...
Click to collapse
Ok, I'll explain in detail how it works: In the guide you will have read that you cannot return to the flyme using the stock rom or an unmodified OTA. This is a tip because once you flash the Engineering ROM, the engineering bootloader (which is essential for unlocking) will also be flashed, but the problem is that if you flash the stock bootloader (the flyme one, the one you surely have when you get the phone), the device for a reason unknown to me, probably the Engineering ROM modifies something in the device (?) and then goes into brick if you try to return to the flyme bootloader. To flash an OTA flyme on TWRP, you must first have some precautions: you must take the OTA on your computer (or a file explorer capable of editing zip files) and remove the following files: lk.bin preloader.bin (it will have a name longer but you still have to remove that) and tz.bin / trustzone.bin. Done like this, now the OTA becomes safe to install, you install it from TWRP, at the end of the flash it will give you an error but it is because it does not find the files we have removed but we can safely ignore it because it will have successfully installed the flyme on the device.
Regarding lineage: I'm still working on it a bit and gradually I'm discovering bugs. I already warn you that the camera will not work in the Lineage, I have tried in every way to try to make it work but it does not want to go, I have asked for help everywhere but no one has been able to answer so I do not know what to do, for the rest I want to keep a little longer the ROM under test to fix the remaining bugs