Related
Recently, Xperia Acro S was been removed from the Unlocking Bootloader list on the Official Sony site.
As maintaining a thread on Acro S section, some of my friends were unable to unlock their bootloader due to missing device in the list.
So, I Emailed Sony few weeks ago requesting them to re-list Acro S, and they said, they'll look at this. Now its been Re-listed.
I have even attached three screenshots for your conformation. So see it, Just check out below three links,
SS-01 || SS-02 || SS-03
For those who were waiting to unlock their phone, here's a good news for you all. Go ahead and get the unlock code from official Sony site providing them your IMEI.
1. To Get Unlock Code just click HERE!
2. Unlocking Bootloader step-by-step Guide, just click HERE!
Regards,
hitman-xda
As I said, I'll notify you after Acro S is re-listed, I'll mention you here; @bluvn || @sky202_how89 || @els_sand
Wow, Thanks for the surprise! U make my days!
sky202_how89 said:
Wow, Thanks for the surprise! U make my days!
Click to expand...
Click to collapse
That sounds good
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
sky202_how89 said:
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
Click to expand...
Click to collapse
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
hitman-xda said:
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
Click to expand...
Click to collapse
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
sky202_how89 said:
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
Click to expand...
Click to collapse
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
hitman-xda said:
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Click to expand...
Click to collapse
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
Click to expand...
Click to collapse
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
hitman-xda said:
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
Click to expand...
Click to collapse
I will try & let you know soonest. Kinda busy this few days.
---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------
Mirhawk said:
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
Click to expand...
Click to collapse
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
---------- Post added at 05:41 PM ---------- Previous post was at 05:35 PM ----------
Latest UPDATE about the issue, PLEASE TAKE NOTE BECAUSE YOU'RE ABOUT TO BRICK YOUR PHONE JUST LIKE ME. THIS IS IMPORTANT!
@hitman-xda , Please pass this message around. Btw, How to quote the name?
If everyone here in this post flashed their phones with Flashtool 0.9.19.x version, then congrats my friends, we're all become owners of bricked phones with no network signal. Flashtool 0.9.19.x versions have sript error which replaces original Ta partition leading to unlocked bootloader to become locked and loss of network signal. If you're guys haven't backuped your Ta partition prior to bootloader unlocking then that's all.
Check here http://forum.xda-developers.com/show...68&postcount=4 and here http://forum.xda-developers.com/show...postcount=2758
Click to expand...
Click to collapse
http://forum.xda-developers.com/xpe...ice-detect-t3200650/post62904161#post62904161
sky202_how89 said:
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
Click to expand...
Click to collapse
Flashing with latest flashtool flashes a partition which renders modem of the phone useless. Yes, I mean the TA partition. Each phone's TA partition is unique, so if You flash mine or other person's TA partition, Your phone would not even boot.
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.
sky202_how89 said:
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.
Click to expand...
Click to collapse
Did nothing worked?
hitman-xda said:
Did nothing worked?
Click to expand...
Click to collapse
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Androxyde said:
On 0.9.18.X, even if simlock is included, it is excluded from flashing
On 0.9.19.5 I did this way :
- simlock is excluded by default with a warning when including it (unticking button)
- When simlock is included, when flashing, a YES/NO box appears asking if you are absolutely sure you want to flash this unit.
- When creating bundles, simlock can be included (no risk with 0.9.18 as it is always ignored)
So if you have a TA backup, with 0.9.19.5 you can restore the 07DA unit (then reactivating the phone). Thing you cannot do with any previous release as 07DA unit is hardcoded_excluded.
I will publish another patch that will backup any TA unit that is about to be flashed. That way there will always be a solution to come back to the previous state.
simlock, if present, is always ignored in 0.9.18 release
simlock, if present is excluded by default with the ability to include it with a warning and a user query before flashing the unit
people who had issues are ones using ftf bundles created prior to 0.9.18 with simlock included. Never had issues on 0.9.18 as it is excluded by default, I forget to keep this exclusion on 0.9.19.[1234] and added a defautl exclusion on .5 with the ability to include it anyway.
But maybe it is not the right way ... I was asking myself when I did it. I want to give the ability to restore 07DA unit if ever a backup exists
The only way to recover from locked phones is to reactivate them in a service center or to restore the 07DA unit.
Click to expand...
Click to collapse
sky202_how89 said:
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Click to expand...
Click to collapse
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.
hitman-xda said:
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.
Click to expand...
Click to collapse
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.
sky202_how89 said:
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.
Click to expand...
Click to collapse
I can't do that. Coz I have already unlocked my bootloader months ago
hitman-xda said:
I can't do that. Coz I have already unlocked my bootloader months ago
Click to expand...
Click to collapse
That's bad but still not too late. Your next Sony in future will be secured
I'm already ordered the replacement mainboard.
What kind of mainboard-Lock BL or Unlock BL, I do not know because it's not a new one.
Waiting for shipment.
Hi,
Everybody is looking for official stock roms for Moto G4/G4 Plus *AWAY* from Motorola support, which looked to me like kind of weird but I now know why: people are looking for stock roms that will allow them over the air upgrades. If you have a developer edition or a moto with unlocked bootloader, Moto's own roms are flashable and *COMPLETELY WORKING*
motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Go to above URL, quick login using G+, follow instructions to get to the download list. The listed download for XT1625 will also work just fine for XT1642.
Or, you can just use this direct link: motorola-global-portal.custhelp.com/cc/ajaxCustom/getBootFile/fileName/ib65qpz53y
may also require login.
******** VERY IMPORTANT ************
Everybody lists fastboot utility commands with which you restore a Moto stock rom. They do not tell these severe warnings:
- Never flash a gpt.bin file unless you really absolutely ultimately intentionally and knowingly NEED TO. Why? in 99.9% of the cases it is useless to your phone and your needs and all it will do is deprive you the ability to downgrade to an earlier version or flash an older boot file, system file, ...etc. You get the picture. BTW, gpt.bin is only a partition image containing Moto's partition table scheme, with versioning for downgrade prevention. Keep away from it. It is pure EVIL.
IF YOU SEE gpt.bin FILE, DELETE IT WITHOUT HESITATION.
- Our second vanity: bootloader.img or bootloader.bin or anything that spells BOOTLOADER. EVIL. DELETE IT. It will 99.9% only mess up your cellular capability and render your phone without voice calls, with out SMS and without 2G/3G/4G; no data whatsoever. It will convert your phone into a 5.5 inch SIM-less tablet. It will KILL YOUR SIM SLOTS.
Instruction are on the first link, but anyway, here we go:
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down Alternatively, you can reboot into fastboot mode if you have adb...
adb reboot bootloader.
Next flash the images using fastboot:
Code:
"DELETED COMMAND HERE WAS SUPPOSED TO FLASH THE GPT.BIN. NEVER DO IT"
"DELETED COMMAND HERE WAS SUPPOSED TO FLASH THE BOOTLOADER. NEVER DO IT"
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
enjoy
****removed****
MK+2017 said:
****removed****
Click to expand...
Click to collapse
I would like back to MM from Nougat on XT1642. This firmware comes from a trusted source, but have you tried this firmware, no problems after flashing? Do I have to have an unlocked bootloader ?
kkamelot said:
I would like back to MM from Nougat on XT1642. This firmware comes from a trusted source, but have you tried this firmware, no problems after flashing? Do I have to have an unlocked bootloader ?
Click to expand...
Click to collapse
if you have not unlocked boot-loader you are covered by warranty and I advise you keep it that way. Motorola is a BI***.
if you really can't live without older stock, go to moto service and ask them to do it for you. should not cost you much, if any.
if what you hate is stock firmware, you can unlock bootloader, get warranty off, and flash LinageOS. Stable enough although still in nightly builds (successor of CyanogenMod)
hope that helps.
PS1: what you would fear the most is lose your SIM slot, happens a lot. Be safe!
PS2: asking if I tried it yes, I did. it worked. but I was on 6.0.1 at the time. do not take risk.
PS3: Motorola is a *****. DON'T MESS WITH IT.
MK+2017 said:
if you have not unlocked boot-loader you are covered by warranty and I advise you keep it that way. Motorola is a BI***.
if you really can't live without older stock, go to moto service and ask them to do it for you. should not cost you much, if any.
if what you hate is stock firmware, you can unlock bootloader, get warranty off, and flash LinageOS. Stable enough although still in nightly builds (successor of CyanogenMod)
hope that helps.
PS1: what you would fear the most is lose your SIM slot, happens a lot. Be safe!
PS2: asking if I tried it yes, I did. it worked. but I was on 6.0.1 at the time. do not take risk.
PS3: Motorola is a *****. DON'T MESS WITH IT.
Click to expand...
Click to collapse
Thank you for your answer !
I have one more question, is there way (like in nexus) to back to original software (Nougat can be) after changing OS or make a modifications?
kkamelot said:
Thank you for your answer !
I have one more question, is there way (like in nexus) to back to original software (Nougat can be) after changing OS or make a modifications?
Click to expand...
Click to collapse
There is, but if you are not good with command line, think twice. Check here: https://forum.xda-developers.com/moto-g4-plus/help/complete-partition-backup-script-xt1644-t3608408
you would typically use that alongside full TWRP backup.
I can assure you nothing will go wrong if you jump straight to LineageOS, it might only go wrong if you take the bad decision of going back to stock. The dd images would give you solid backup, though.
In case you lose your sim slot, you can use help from here: https://forum.xda-developers.com/showpost.php?p=72343095&postcount=101
I intuitively contributed to that solution Giving is taking!
Thank you @m.sawastik and @givitago
MK+2017 said:
There is, but if you are not good with command line, think twice. Check here: https://forum.xda-developers.com/moto-g4-plus/help/complete-partition-backup-script-xt1644-t3608408
you would typically use that alongside full TWRP backup.
I can assure you nothing will go wrong if you jump straight to LineageOS, it might only go wrong if you take the bad decision of going back to stock. The dd images would give you solid backup, though.
In case you lose your sim slot, you can use help from here: https://forum.xda-developers.com/showpost.php?p=72343095&postcount=101
I intuitively contributed to that solution 😊Giving is taking!
Thank you @m.sawastik and @givitago
Click to expand...
Click to collapse
I would also be happy to assist you if you want to jump to LineageOS. I won't assist you with dd backup, just because you need to take that responsibility on your own
My XT1625 is already on Lineage OS Andriod N. However, I feel like the cellular reception and thus battery life has been worse versus stock.
I wanted to flash only the latest baseband from the latest stock Andriod N but your Moto link only has 6.0.1 for XT1625.
What gives- I thought Motorola already updated the G4 to 7.0?
Will OTAs work with this?
Will OTAs work with these?
If I just want to upgrade my modem/baseband and then go back to LOS, do I just need to type "fastboot flash modem NON-HLOS.bin" or do I need to make a full install?
it works for moto g4 t1625 amazon version?? compilation number npj25.93-14.5 ?????? i answer this because in the web site motorola its appear the moto g4 rom xt1625 build MPJ24.139-64
Works!
I just want to say that I had a Moto G4 Plus (XT1642) that had no SIM recognition, no IMEI, no Wifi, and thanks to the instructions at the top of this thread, I now have it all.
I spent the whole day trying all sorts of things. Now it finally works!
Thanks!
How do I flash?
Hi friend, sorry but my English is not good.
My phone will receive nougat via OTA?
Something has broken my sound notifications
When I try this procedure I get a lot of these errors against some of the commands
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) will fail: flash:aboot
FAILED (remote failure)
And now sounds that accompany any notifications from any applications fail to make any sound. Vibrate does initiate.
I am trying to find a way to enable hotspot on my ATT Moto G4 plus, if I flash this rom can anyone confirm it will unlock this feature? Torn between flashing or just going in to kernel and make change for this feature, any advice appreciated..
how to restore the sim slot after flash( i have no service)
i had frp, and after remove it with 3rd party tool i flash new rom.
now i have no service(but it detect the sim), there is any way to restore the sim slot?
i flashed the original rom from motorola site and it didnt help.
i flash the lineage OS and it didnt helped.
thanks
ggc201 said:
there is any way to restore the sim slot?
Click to expand...
Click to collapse
I've been searching for a fix for a few months now, whenever I get free time. Most threads about the subject die and aren't revisited. Someone will inevitably come to this page on a Google search wondering like us. I haven't found anything that will help and so I'm calling it quits. This phone is so outdated it would be better suited to find a deal somewhere else.
Thanks... can't find the button.
I have the xt1625 amz channel version and the: XT1625-XT1644_ATHENE-RETUS_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip > provided enhanced LTE whereas the official OS did not support. I can actually do sh** on my phone without hanging up.
I want you and yours to be blessed forever and great post.
Bootloader is unlocked but somehow it is stuck between root and no root. Will figure it out....
Again... thanks... this is a big deal for me. :good:
non-developer edition?
If you have a developer edition or a moto with unlocked bootloader, Moto's own roms are flashable and *COMPLETELY WORKING*
Click to expand...
Click to collapse
Can anyone attest to having successfully flashed an unlocked non-developer edition G4 with this ROM? Motorola clearly warns against doing this:
IMPORTANT! Do not use these images/packages on non-developer edition devices or on devices with a locked bootloader.
Click to expand...
Click to collapse
(sorry, I'm a new member so I'm not allowed to include a link)
so i was flashing a nougat 7.0 update on moto z play and then all of a sudden my phone wouldnt even power on the screen was all black so i decided to use blank flash. Blank flash did take me to the bootloader but even when trying to boot to recovery and system it wont work.
help plz.
Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
what do you mean
Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
ahmed12389 said:
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
Click to expand...
Click to collapse
Do you see the device listed in Windows?
Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
yes I can see it
Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
what do you suggest I do
ahmed12389 said:
what do you suggest I do
Click to expand...
Click to collapse
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
Yes I have flashed stock firmware on my device I remember downgrading to marshmallow then updating back to nougat then my device fully shut down it was all black. After this incident, i did what you would normally do and that was to use blank flash to at least get the bootloader back, as I did get the bootloader I could not use the boot options such as recovery mode. so I am basically stuck on the bootloader and can do nothing. My device is an addison XT1635-02 and before I flashed nougat ota I had the marshmallow December security update.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
I also believe my device is hard bricked as I cant access boot options at all it just keeps boot looping once I try to access a boot option. also is it normal for my bootloader to say that my software status is modified because I think after you flash blank flash your software status modified. finally, I have been trying to flash stock firmware but for some reason, gpt and bootloader.img always fail to flash. Thanks for the reply I hope you can help.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
ahmed12389 said:
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
Click to expand...
Click to collapse
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
ok the thing is I am certain I used the wrong blank flash zip therefore meaning that I flashed the wrong things this is probably why I'm boot looping do you have any idea how to revert the changes of blank flash so I can flash the propper blank flash. Is their even any blank flash for Moto z play anyways
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I was flashing the July security patch stock firmware and it's giving me these errors
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
if i flash that stock frimware it takes straight to 7.1.1 is that correct
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
ahmed12389 said:
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
Click to expand...
Click to collapse
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
ahmed12389 said:
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
Click to expand...
Click to collapse
If your device was ever on stock Nougat (7.0 or 7.1.1), then flashing that marshmallow ROM won't likely work in repairing your bootloader. You need a firmware that is the same or newer than the latest firmware your device had. Downgrading stock firmware does not usually downgrade your bootloader, hence the corruption and need to have same or newer firmware to repair. Your bootloader would otherwise reject old firmware via preflash validation errors.
Hopefully the 7.1.1 firmware will help fix things. You will lose data however in the process of flashing your device, so hopefully you have backups.
echo92 said:
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
Click to expand...
Click to collapse
oh my freaking god you fixed it!!! you are literraly my idol thanks to you i dont need to take it to service from now on I'm never flashing again. but thank you very much you fixed my phone you absolute legend.
ahmed12389 said:
what do you mean
Click to expand...
Click to collapse
how is it recognized by the PC in device manager?
TWRP DIRTY PORT FOR G7 PLAY
My friend was looking to get a G7 Play, so I wanted to whip something up for him really quick. I managed to make a dirty port of TWRP for the G7 Play, taken from the G7 TWRP image since they're the same SDM632 chipset. Until you guys get a real, proper build of TWRP done with the proper source code, consider this a stop gap to at least be able to flash things! It's not perfect obviously but hopefully it's good enough for now!
AS ALWAYS, I DO NOT TAKE RESPONSIBILITY IF FLASHING THIS BRICKS YOUR PHONE. WHAT YOU CHOOSE TO DO TO YOUR PHONE IS ON YOU!!!
WHAT WORKS:
It boots! As you can see here, the G7 Play is in fact running this recovery image just fine
Not sure, don't have the phone to test for myself
WHAT DOESNT WORK:
Because this is a dirty port, the recovery will think this is a G7, when as we all know this is in fact a G7 Play. There is nothing I can really do about this, this is the nature of dirty ports
Not sure, don't have the phone to test for myself
DOWNLOAD:
DOWNLOAD LINK HERE
I cannot provide any source code since this was a dirty port, so no actual source was used. The only things I used to make this were a G7 TWRP image, a G7 Play boot image, and carliv's image kitchen
HOW TO USE:
Reboot to fastboot
Flash the dtbo with fastboot flash dtbo dtbo.img
After that boot from the recovery with fastboot boot recoveryname.img
THANKS TO:
@Alberto97 for the G7 TWRP image I dirty ported from
The G7 Play Telegram group for testing out the image I made, since I don't have a G7 Play to test this on myself. Specifically @noslen7 for testing the image and figuring out how to get it to run (need to flash the dtbo first) and for sending me the image I used above to show it's working and bootable
Carliv for that Carliv Image Kitchen he made, that tool rocks!
I can't test it anymore but if it's uses the same things as the one I built which was inspired by Alberto, do not try to install the TWRP unless you have already flashed the second bank.
fastboot boot recovery.img indeed won't harm so you can try that.
Any idea what works more then the one I built?
Which dtbo.img are we supposed to flash - the one from the stock ROM, or something else?
Great work!
First of all thanks for your hard work. I was really happy to see your post. I have followed the instructions exactly and I got "Failed (too many links)" when it attempted to boot my phone into recovery.
I am using XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-5
Any ideas why it might have failed?
Thanks
jwreidmoto said:
First of all thanks for your hard work. I was really happy to see your post. I have followed the instructions exactly and I got "Failed (too many links)" when it attempted to boot my phone into recovery.
I am using XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-5
Any ideas why it might have failed?
Thanks
Click to expand...
Click to collapse
That's the same one I'm trying to use, tried the dtbo from the same firmware got the same results. Possible EU/Canada firmware as the screenshot of the phone that was shared is in celcius
This is how i boot this recovery successfully
daftshanks said:
That's the same one I'm trying to use, tried the dtbo from the same firmware got the same results. Possible EU/Canada firmware as the screenshot of the phone that was shared is in celcius
Click to expand...
Click to collapse
step 1 fastboot flash dtbo dtbo.img
s000.tinyupload. com/download.php?file_id=26286860633744490329&t=2628686063374449032989765
step 2
fastboot boot "recovery above"
s000.tinyupload. com/download.php?file_id=24332259722784445351&t=2433225972278444535138860
noslen7 said:
step 1 fastboot flash dtbo dtbo.img
s000.tinyupload. com/download.php?file_id=26286860633744490329&t=2628686063374449032989765
step 2
fastboot boot "recovery above"
s000.tinyupload. com/download.php?file_id=24332259722784445351&t=2433225972278444535138860
Click to expand...
Click to collapse
I appreciate your reply on this. However the dtbo filebyou provided is about 3/5ths of the dtbo from my stock firmware, normally they would be at least close to the same file size. Can I ask you what firmware you are on? And were you able to permanently install TWRP? Possible root?
Downloaded dbto.img got same result
I downloaded the above dbto.img and flashed it instead of my own stock dbto.img and got the same result when I tried to boot from recovery - Failed ( too many links). I think the recovery IMG is not working for our Canadian ROM edition.
anybody with XT1952-1 RETEU reading this here, you can help!
https://forum.xda-developers.com/showpost.php?p=79655902&postcount=5
Which dtbo.img to use? In the download area you only have the image of recovery
HOW TO USE:
Reboot to fastboot
Flash the dtbo with fastboot flash dtbo dtbo.img
After that boot from the recovery with fastboot boot recoveryname.img
dbto.img
That was in response to another query. I used my own dbto.img from my stock ROM. That part flashes fine it's the recovery.img that comes back with " failed( too many links) I have a Canadian phone.
Flashing dtbo.img will erase the smartphone data? Will I lose app data?
thank you
it worked for me fine it did give me some problems when i tried booting direct so i flashed to boot then went to recovery mode thru bootloader menu and it worked once in twrp i installed the original boot.img and im good.
Yo I'm coming from the g6 play forum with a quick question. Does this by chance work with the same current root method for the g6 play which is booting in twrp and formatting data to decrypt it then flashing twrp and flashing through twrp the encryption disabler zip then flashing magisk. If someone is able to confirm that I can possibly try to make a decent guide for you guys. We don't have a offical twrp that decrypts on its own and the twrp we have ain't a dirty port so I know there may be some differences when it comes to twrp related issues but it's better than nothing lol
ninjakira said:
Yo I'm coming from the g6 play forum with a quick question. Does this by chance work with the same current root method for the g6 play which is booting in twrp and formatting data to decrypt it then flashing twrp and flashing through twrp the encryption disabler zip then flashing magisk. If someone is able to confirm that I can possibly try to make a decent guide for you guys. We don't have a offical twrp that decrypts on its own and the twrp we have ain't a dirty port so I know there may be some differences when it comes to twrp related issues but it's better than nothing lol
Click to expand...
Click to collapse
There is one significant difference (as it regards rooting) between the Moto G6 Play and the Moto G7 Play. The G7 Play uses the A/B partition index while the G6 Play uses a standard GPT index. The current dilemma with root for the G7 Play involves the A/B partition config. Developer topjohnwu has been notified of this issue on the Magisk support thread, and has stated that he is working on a resolution at present.
Viva La Android said:
There is one significant difference (as it regards rooting) between the Moto G6 Play and the Moto G7 Play. The G7 Play uses the A/B partition index while the G6 Play uses a standard GPT index. The current dilemma with root for the G7 Play involves the A/B partition config. Developer topjohnwu has been notified of this issue on the Magisk support thread, and has stated that he is working on a resolution at present.
Click to expand...
Click to collapse
There has to be more to it than this. There are plenty of devices using A/B partitioning that can be rooted with Magisk. As far as I know, Magisk has supported A/B since version 17.1. Reading through the threads it sounds like more a TWRP problem than a Magisk one.
Has anyone tried patching boot_a and boot_b with Magisk and flashing both at once?
Spaceminer said:
There has to be more to it than this. There are plenty of devices using A/B partitioning that can be rooted with Magisk. As far as I know, Magisk has supported A/B since version 17.1. Reading through the threads it sounds like more a TWRP problem than a Magisk one.
Has anyone tried patching boot_a and boot_b with Magisk and flashing both at once?
Click to expand...
Click to collapse
You try and let's us know
Fdraco10 said:
You try and let's us know
Click to expand...
Click to collapse
I don't have the device otherwise I would. That's why I'm asking if anyone has tried it yet.
Spaceminer said:
I don't have the device otherwise I would. That's why I'm asking if anyone has tried it yet.
Click to expand...
Click to collapse
Yes. I patched both boot_a and boot_b with Magisk v19.3. My device booted into the OS with no problems at all, yet Magisk Manager indicates that root is not installed. Topjohnwu has been notified of the root issue with the Moto G7 Play, and has stated on the Magisk support thread that he is looking into a resolution. It's not a TWRP issue at this point because there is no unofficial or official TWRP for the G7 Play as of yet. Like you, I fully agree this is a bizarre issue. Root strategies which are working on the Moto G7, G7 Power & G7 Plus are not working on the G7 Play. Although Magisk has certainly supported A/B devices for some time now, no universal root method is completely infallible. There are many devices -- both A/B and standard GPT -- that encounter problems with Magisk from time to time. Luckily for the Android community, topjohnwu works hard on resolving any known issues like the one at hand.
Viva La Android said:
Yes. I patched both boot_a and boot_b with Magisk v19.3. My device booted into the OS with no problems at all, yet Magisk Manager indicates that root is not installed. Topjohnwu has been notified of the root issue with the Moto G7 Play, and has stated on the Magisk support thread that he is looking into a resolution. It's not a TWRP issue at this point because there is no unofficial or official TWRP for the G7 Play as of yet. Like you, I fully agree this is a bizarre issue. Root strategies which are working on the Moto G7, G7 Power & G7 Plus are not working on the G7 Play. Although Magisk has certainly supported A/B devices for some time now, no universal root method is completely infallible. There are many devices -- both A/B and standard GPT -- that encounter problems with Magisk from time to time. Luckily for the Android community, topjohnwu works hard on resolving any known issues like the one at hand.
Click to expand...
Click to collapse
I read the responses in his thread about that, and it seems like you guys aren't getting root without a working TWRP. The problem that was laid out, is that fastboot can't patch existing files, it can only overwrite them. Without a custom bootloader, Magisk would never be able to patch existing files through fastboot.
Personally, I think that's a very sh*tty position to be in, and I want to help you guys out. If you or anyone else wants to upload your most recent boot.img, it'll save me some time. I'm not too familiar with the A/B partition setup, but I am very familiar with TWRP. I think that I can get it working for you folks. I will make this happen or break my brain trying. No phone with an unlockable bootloader should go unrooted! Thank you for answering my question by the way. That's one less thing to troubleshoot.
I just want to confirm a few things before I get to work.
Is your base model number xt1952?
Is your code name Channel?
Where is the current TWRP hacked from? (Moto G7, G7 Power, G7 Plus?) - Moto G7. I found it in the OP.
And are you guys arm32 or arm64?
Article here
What do you think? Will this finally let us unbrick redmi note 8 pro without mi authorized account?
Did some dev look into this yet?
yes i've tested it it works. i couldnt do anything with it though but it shouldnt be that hard to let us flash cfw and twrp or unlock the bootloader using spflashtool right. this thing is huge i mean granted its not the easiest to do but honestly its not even that hard if you know what you're doing which you should if you're on xda, it took about 10 mins on me
it is possible, we're just waiting for a dev to implement it, right now there isnt much you can do w sp flash tools
wentaas said:
it is possible, we're just waiting for a dev to implement it, right now there isnt much you can do w sp flash tools
Click to expand...
Click to collapse
Why not? The scatter file is sitting there on /images folder in every fastboot rom distribution. Look for MT6785_Android_scatter.txt.
After that, your device should be a blank slate. The rest, is up to you.
Well, I think flashing vanilla rom should be your priority, since everything can be done when your device is up-and-running. And extra cautious of course.
kekesed97 said:
Why not? The scatter file is sitting there on /images folder in every fastboot rom distribution. Look for MT6785_Android_scatter.txt.
After that, your device should be a blank slate. The rest, is up to you.
Click to expand...
Click to collapse
wdym by blank state? and is that safe to do?
wentaas said:
wdym by blank state? and is that safe to do?
Click to expand...
Click to collapse
Not a blank state, a blank slate. You know, a blank board which you can write or draw anything you like? But that's not important right now.
Theoritically it should safe. It's like removing a boulder that blocking your way.
If you have access to SPFT, theoritically you should be able to flash your vanilla ROM, given the security measures are null (or rather, bypassed). If your device is chinese based you should flash chinese ROM there. Do a wipe and lock procedure. Let the bootloader locked for now, since you can unlock it later. Do not do crossflash there, without bootloader unlock (this should be a common sense).
But theory is a theory. I can't test it since my device is up-and-running.
My knowledge may be obsolete, since the last device I flashed was MT6572 back on its glory days, no security measures and bootloader was unlocked back then. You can't flash only and only if your eMMC is damaged, which is the worst case (oppo phones was prone to eMMC failure back then, and that happened to me). But afaik the flash process isn't changed that much, just an additional security measure was added, so I think my knowledge still apply.
Additional note: try to flash without nvram and nvdata to avoid losing IMEI (someone from Redmi Note 9 forum lose his IMEI).
kekesed97 said:
Not a blank state, a blank slate. You know, a blank board which you can write or draw anything you like? But that's not important right now.
Theoritically it should safe. It's like removing a boulder that blocking your way.
If you have access to SPFT, theoritically you should be able to flash your vanilla ROM, given the security measures are null (or rather, bypassed). If your device is chinese based you should flash chinese ROM there. Do a wipe and lock procedure. Let the bootloader locked for now, since you can unlock it later. Do not do crossflash there, without bootloader unlock (this should be a common sense).
But theory is a theory. I can't test it since my device is up-and-running.
My knowledge may be obsolete, since the last device I flashed was MT6572 back on its glory days, no security measures and bootloader was unlocked back then. You can't flash only and only if your eMMC is damaged, which is the worst case (oppo phones was prone to eMMC failure back then, and that happened to me). But afaik the flash process isn't changed that much, just an additional security measure was added, so I think my knowledge still apply.
Additional note: try to flash without nvram and nvdata to avoid losing IMEI (someone from Redmi Note 9 forum lose his IMEI).
Click to expand...
Click to collapse
ooh thanks for the explanation, to be clear, my phone is working fine right now but i hate miui. so my intention was to unlock the bootloader if possible, or install cfw and twrp if its not, or if thats not possible either, just installing a custom rom (probably aosp a11)
wentaas said:
ooh thanks for the explanation, to be clear, my phone is working fine right now but i hate miui. so my intention was to unlock the bootloader if possible, or install cfw and twrp if its not, or if thats not possible either, just installing a custom rom (probably aosp a11)
Click to expand...
Click to collapse
Well, for unlocking bootloader there's no other method than the official one. But in some cases the waiting time could be forever (well, many failed attempts would lead to loong waiting time, practically doesn't worth the wait).
My device was resurrected (around May 20, when everyone make a fuss about the lockout). And it can do UBL and root just fine, and tripped AVB many times. It's pretty safe to say tripping AVB on device with unlocked bootloader is recoverable. Just do fastboot flash via MiFlash Pro, and you are set! But never do "Flash and Lock" operation. It would lead to the lockout. You would regret it.
kekesed97 said:
You can't flash only and only if your eMMC is damaged, which is the worst case (oppo phones was prone to eMMC failure back then, and that happened to me)
Click to expand...
Click to collapse
Thanks for sharing your experience. This eMMC failure is because of Oppo or Mediatek? I have a Realme C12.
3 guys 'hard bricked' their devices. No sign of life. Flashing in SP Flash Tools results 'RAM_EXCEPTION (0xC0050005)'. Not able to readback too. It seems like eMMC replacement is only solution.
What are your ideas in this?
Thanks
HemanthJabalpuri said:
Thanks for sharing your experience. This eMMC failure is because of Oppo or Mediatek? I have a Realme C12.
3 guys 'hard bricked' their devices. No sign of life. Flashing in SP Flash Tools results 'RAM_EXCEPTION (0xC0050005)'. Not able to readback too. It seems like eMMC replacement is only solution.
What are your ideas in this?
Thanks
Click to expand...
Click to collapse
Maybe because oppo tried to cut corners since they're using mediatek? I don't see any reason for them to not cut the corner any further. It was 2015, it have a mediocre specs with mediocre quality for their price.
It's been a long ago, I forgotten the error messages. I'm afraid you are facing a worst case scenario.
If you can pull out your eMMC and put that on a jtag reader, there's might be a slight chance of revival.