Hi,
I tried to install MARSHMALLOW on my XT1528 without unlock the bootloader and now got stuck on Flash Mode screen.
"XT1521_SURNIA_RETASIA_DS_6.0_MPI24.65-39_cid7_subsidy-DEFAULT_CFC.xml"
Later I realized that I cant unlock the bootloader of verizon mobile.
I have tried to install
"XT1528_SURNIA_VERIZON_5.1_LPI23.29-17.5_cid2_subsidy-DEFAULT_CFC.xml"
and got a error message "version downgraded for primary_gpt"
I also tried verizon software repair assistant.
Is there anything I could do to boot into my mobile?
Awaiting your assistance
I did the same thing several weeks ago, and posted warning people not to do it. Sorry, we're screwed.
rodalpho said:
I did the same thing several weeks ago, and posted warning people not to do it. Sorry, we're screwed.
Click to expand...
Click to collapse
did you find any way to make the device usable?
There are two versions of firmware for XT1528, one marked LPI23.29-17 and LPI23.29-17.5. It may seem like a negligible thing but if a device works with one then it won't work on the other. Try flashing both and hopefully one will work, that's you're best option
Kilara said:
There are two versions of firmware for XT1528, one marked LPI23.29-17 and LPI23.29-17.5. It may seem like a negligible thing but if a device works with one then it won't work on the other. Try flashing both and hopefully one will work, that's you're best option
Click to expand...
Click to collapse
Thanks for the reply. May I know where can I download the firmware? I tried google and can't find the exact one.
arunzone said:
did you find any way to make the device usable?
Click to expand...
Click to collapse
Umm, no. Like I said, we're screwed.
Related
Hello guys!
I have troubles unlocking my Atrix for a while........
I am rooted with 2.3.4/4.5.91 AT&T stock version.
When I try to unlock my device I get OEM Unlock is not implemented....
Now I know that this is due to the fact that the bootloader is not unlockable. That's why I try to flash the sbf file with the one that is unlockable but this is where i actually fail...............
When I try to Flash the phone with RSD Lite (I have tried with both 4547-fix-try2.sbf and with the big one 1.4GB) it goes to 100% when the phone is suppose to reboot. The phone actually reboots but get stuck at the MOTO LOGO while the RSD Lite gives me the ERROR Unable to Re-enumerate something.... Even if i w8 an hour is still dosnt boot until i pull off the battery. Then my phone starts normaly.........
I have tried to go into fastboot after the freez and try the fastboot oem unlock but still I get the OEM Unlock is not implemented.....
I guess that the whole reason for not unlocking the phone is that I am unable to flash the sbf file.
I want to point out that I have all drivers installed and working correctly.
Also I am unable to Install 2.3.6 OTA Update. It downloads it from the servers and when the phone reboots it gets the triangle mark and unable to update then loads normally .....
So everything points out to not being possible to update sbf...
I am asking for any solution or sugestions since I have tried everything on the forums... I love the phone it's been surving me good for 1 and a half year already. I am not afraid of breaking it since it had its times. Only newer version would save it from replacement (tried of that laggy blur interface....)
PS: Thats wierld phone i cant even hardbreak....
I would be realy happy if someone can help ... ;(
Noone ;(
you've got yourself a blocked bootloader. No one has been able to get passed it. Unfortunately you can't unlock it.
Sorry bro... You got unlucky and got an atrix with an impossible boot lock. There is one method i know of.. It hard bricks so many phones it wasnt worth the devs time to finish.
Dohhh
Well may u link the thread so I can see it
Would be interesting to me..
pre4speed said:
you've got yourself a blocked bootloader. No one has been able to get passed it. Unfortunately you can't unlock it.
Click to expand...
Click to collapse
I am not sure if this is true. I have a permalocked boot loader and only know this to be a problem on 4.5.141. I may be wrong but I would keep at it.
But you do seam to get the same error on phone. It is strange that you cannot OTA. I was locked on 4.5.141 and just took the soak test OTA to I think it was 4.5.145 or something like that
affiatic said:
I am not sure if this is true. I have a permalocked boot loader and only know this to be a problem on 4.5.141. I may be wrong but I would keep at it.
But you do seam to get the same error on phone. It is strange that you cannot OTA. I was locked on 4.5.141 and just took the soak test OTA to I think it was 4.5.145 or something like that
Click to expand...
Click to collapse
Have you tried to unlock again after the OTA? Would be interesting to know if its unlockable now.
pre4speed said:
Have you tried to unlock again after the OTA? Would be interesting to know if its unlockable now.
Click to expand...
Click to collapse
Yes tried and failed. Same error message as 4.5.141.
affiatic said:
Yes tried and failed. Same error message as 4.5.141.
Click to expand...
Click to collapse
Damn Motorola. Wont give ice, wont give you the options to make your phone better. Makes me double glad I went to Samsung.
pre4speed said:
Damn Motorola. Wont give ice, wont give you the options to make your phone better. Makes me double glad I went to Samsung.
Click to expand...
Click to collapse
On the galaxy note here. Selling atrix Friday. Held off to try the soak. Nothing great in it so selling.
My wife is keeping her atrix on cm10 for now.
affiatic said:
On the galaxy note here. Selling atrix Friday. Held off to try the soak. Nothing great in it so selling.
My wife is keeping her atrix on cm10 for now.
Click to expand...
Click to collapse
Im not selling mine. Gonna keep as a backup. I've actually got 2 atrixes, one is my bf and I keep the other for the backup to his and in case my Sammy (skyrocket) dies. Its not a bad phone just the manufacturer has burned too many bridges over wide rivers.
pre4speed said:
Im not selling mine. Gonna keep as a backup. I've actually got 2 atrixes, one is my bf and I keep the other for the backup to his and in case my Sammy (skyrocket) dies. Its not a bad phone just the manufacturer has burned too many bridges over wide rivers.
Click to expand...
Click to collapse
Just put cm10.1 jelly beer on note today. Very smooth and fully functional. I recommend. Sorry to OP for off topic
affiatic said:
Just put cm10.1 jelly beer on note today. Very smooth and fully functional. I recommend. Sorry to OP for off topic
Click to expand...
Click to collapse
I agree, we got a little off topic.
My bone stock Nexus 9 went into a bootloop after taking the update to 6.0.1. It appears that the Nexus help forums are blowing up with many Nexi owners of various flavors experiencing the same problem.
Unfortunately, I never checked "allow OEM unlock," so I couldn't just flash a new image. Clearing cache and factory reset were also no help. I got the dreaded (or standard, depending if you've been tinkering) "your device is corrupt" nastygram before it went into bootloop.
Fortunately it was still under warranty. Does anyone know what HTC does with these units when they are returned? Do they have the ability to unlock the bootloader and fix it by flashing the vendor image or something along those lines?
Try the solution here: - http://forum.xda-developers.com/nexus-9/help/failed-marshmallow-update-stock-android-t3226704
corkiejp said:
Try the solution here: - http://forum.xda-developers.com/nexus-9/help/failed-marshmallow-update-stock-android-t3226704
Click to expand...
Click to collapse
It's already at the HTC repair facility in Memphis. I didn't see that thread earlier, or else I would have tried that. Thanks for trying to help...
Mine is on it's way to Memphis:} Talked to Google, they are well aware of the 6.1 fu. Said they are working on another update for a "fix". Can't fix a dead OS with an update though. Anyone here thought about a "class action"? Just a thought:}
For something like this they should not be charging anyone. They have had the exact same issue on Nexus 7s in the past, and they were taking care of it free of charge even if you were out of warranty.
Hah, so it's not just me then! Mine is off to whatever the UK version of Memphis is. Probably Milton Keynes.
corkiejp said:
Try the solution here: - http://forum.xda-developers.com/nexus-9/help/failed-marshmallow-update-stock-android-t3226704
Click to expand...
Click to collapse
This worked for me! Thanks, corkiejp. I had to wipe everything, but at least it saved me from sending my tablet off to get worked on.
HTC sent me a new tablet. It seems like every time there's an update some of us get a corrupted OTA and it bricks the device. I can't believe that they haven't come up with a secure way do deal with a dead OS, especially since the fix is so expensive for them if it's under warranty.
corkiejp said:
Try the solution here: - http://forum.xda-developers.com/nexus-9/help/failed-marshmallow-update-stock-android-t3226704
Click to expand...
Click to collapse
Works well. Thanks.
You need this for latest OTA zip
http://apk-bro.blogspot.com/2015/12/download-android-601-marshmallow-ota.html
Good day everyone.
Please, give me an advice. How to unlock FRP HONOR 5X (Android 6.0.1, EMUI 4.0, Kiw-L21) ????
Thank you for your advice
Tatrox said:
Good day everyone.
Please, give me an advice. How to unlock FRP HONOR 5X (Android 6.0.1, EMUI 4.0, Kiw-L21) ????
Thank you for your advice
Click to expand...
Click to collapse
remove your google accounts from the phone reboot
You can follow this guide to successfully unlock your phone.
Hope this helps you.
Did you ?
Hey !
Did you succeed unlock FRP ?
I have the same problem to be able to flash a stock recovery...
I have no access to the Stock Custom and I'm not able to remove any google Account (my Phone has no rom).
If you did something for this, please keep me inform
And excuse my language : I'm french.
Cheers
Did some searching around and found this thread.
http://forum.xda-developers.com/honor-5x/help/unlock-bootloader-issues-kiw-t3411032
The information is here:
tohc1 said:
To answer my own problem/ for anyone else having problems it is necessary to remove the factory reset protection (frp) to do this you need to remove all pin/password/fingerprint locks, then remove all google accounts and finally do a factory reset.
Then the usual adb/fastboot commands work fine.
As linux33it says the bootloader can be unlocked without the option in the developer options.
Click to expand...
Click to collapse
While this works for some - it failed to work for me. Maybe because I didn't enable a little option on the screen about allowing OEM unlock. Maybe. But I (stupidly?) ended up where I was sent in this external guide.
http://www.modaco.com/forums/topic/...our-honor-5x-official-and-unofficial-methods/
Basically went to this site and used their tool (cost me USD$16) to wipe the FRP.
https://www.dc-unlocker.com
Maybe if you enable the option about the OEM unlock in Developer Mode this isn't necessary..........
Hopefully this helps someone. So to outline - let me show what I did - including errors.
Wipe the phone / factory reset.
Reboot and ensure everything is removed. Factory reset again.
Tried the commands - got error.
Did search for FRP unlock and found site.
Followed instructions on site which led me to download DC Unlocker and pay for their FRP unlock.
Reboot and setup phone (with no accounts or password or fingerprints).
Enabled "OEM UNLOCK" in developer options (which I didn't see before.........)
Run commands (they all now work).
Bootloader unlocked successfully.
Device factory resets.
Setup device again skipping accounts/password/fingerprints.
Follow instructions for flashing TWRP and finishing up.
Complete.
Again - hopefully this helps someone.
id recomend official one.. seems easy
thilak devraj said:
id recomend official one.. seems easy
Click to expand...
Click to collapse
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
khat17 said:
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
Click to expand...
Click to collapse
Look at the twrp thread in android development section..
There is a detailed guide how to
khat17 said:
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
Click to expand...
Click to collapse
It's a worthwhile effort. Appreciate it buddy.
khat17 said:
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
Click to expand...
Click to collapse
Even newbies can do it right. Provided that they strictly follow the steps.
Sent from my Galaxy Tab 3 using XDA Labs
I agree. But I don't recall seeing anything in the original instructions about the FRP which shows / states ensuring OEM unlock is checked. Unless I missed it. I DO recall seeing it somewhere else in another thread where someone mentioned it. But I still don't know if the case is enabling it means you don't need to use the DC Unlocker program.
thilak devraj said:
id recomend official one.. seems easy
Click to expand...
Click to collapse
adriansticoid said:
Even newbies can do it right. Provided that they strictly follow the steps.
Sent from my Galaxy Tab 3 using XDA Labs
Click to expand...
Click to collapse
khat17 said:
I agree. But I don't recall seeing anything in the original instructions about the FRP which shows / states ensuring OEM unlock is checked. Unless I missed it. I DO recall seeing it somewhere else in another thread where someone mentioned it. But I still don't know if the case is enabling it means you don't need to use the DC Unlocker program.
Click to expand...
Click to collapse
you dont need dc unlocker, unless you have not checked "oem unlock" option in dev. options..(thats also only case if you were on lollipop)
and if you are on mm, you dont even need to check that option,
Thanks for that info. Next one I get my hands on will try that out and see.
thilak devraj said:
you dont need dc unlocker, unless you have not checked "oem unlock" option in dev. options..(thats also only case if you were on lollipop)
and if you are on mm, you dont even need to check that option,
Click to expand...
Click to collapse
khat17 said:
Thanks for that info. Next one I get my hands on will try that out and see.
Click to expand...
Click to collapse
what happened with the current one??
thilak devraj said:
what happened with the current one??
Click to expand...
Click to collapse
I had basically bricked it and brought it back. Think the one I got had some issues, because I couldn't update it at all. Even before rooting it wouldn't update. Then I realized that when the update was running it rebooted into TWRP - so I flashed back the stock recovery and tried again. No luck. This was done with disabling OEM unlock as well and still nothing. So I got an UPDATE.APP as well as a nandroid that I believe was supposed to be able to update the phone. None worked.
khat17 said:
It's a little bit of both. Those are the steps I followed to get root access. However, I don't recall seeing anything about the FRP in any of the previous guides.
As for my specific issue, I can't update regardless of what I try. After de-bricking the device I got it to this stage. I'll upload the screenshots shortly.
*EDIT*
So this is my phone now. Partly upgraded it seems. The device is now at B331 instead of B151, but still on EMUI 3.0
And what I want to point out is - after enabling DEVELOPER MODE - ensure you check the OEM UNLOCK option.
Because I can't confirm at this point if doing that will prevent having to pay for the FRP unlock.
Click to expand...
Click to collapse
But now that you've confirmed that there's no need to pay for the bootloader unlock, I would go ahead and do some experimenting if you suggest. For science. But I'm a little reluctant to try and re-lock the bootloader and then unlock it again. If you can confirm or even partly guarantee that it works however, I'll do some messing around with it. For science. Otherwise, I've managed to get the device to a working state now - wouldn't want to mess with it much.. Only if I can try something else to get EMUI 4 on it.
khat17 said:
I had basically bricked it and brought it back. Think the one I got had some issues, because I couldn't update it at all. Even before rooting it wouldn't update. Then I realized that when the update was running it rebooted into TWRP - so I flashed back the stock recovery and tried again. No luck. This was done with disabling OEM unlock as well and still nothing. So I got an UPDATE.APP as well as a nandroid that I believe was supposed to be able to update the phone. None worked.
.
Click to expand...
Click to collapse
thats something wiered,, you shouldve got it into service center before rooting, saying that it wasnt updating....
thilak devraj said:
thats something wiered,, you shouldve got it into service center before rooting, saying that it wasnt updating....
Click to expand...
Click to collapse
I live outside of the country of purchase. Doubt I can send it back now anyways. And I got it working so it's fine.
I like it better than the BLU and the Samsung I had. FAR easier to root. Even with the issues I had.
khat17 said:
I live outside of the country of purchase. Doubt I can send it back now anyways. And I got it working so it's fine.
I like it better than the BLU and the Samsung I had. FAR easier to root. Even with the issues I had.
Click to expand...
Click to collapse
how did you manage to get working??
thilak devraj said:
how did you manage to get working??
Click to expand...
Click to collapse
I posted it in this other thread.
khat17 said:
Hi all. I'd like to put forward some suggestions to be placed in the first post. I literally paid cash to learn and figure some stuff out. Even if you're good at following instructions or partially experienced in these things, when you're eager to get it done or impatient (like me) you find the fastest route.
Here are some links in case someone wants to just go through the whole thing themselves.
http://forum.xda-developers.com/honor-5x/how-to/unlock-frp-t3444584#post69917735
So here's what happened. I got the phone and was very eager to just get my stuff on it right away. Rooting is the first thing I wanted to do and looked that up to get it done. Made a mistake in the process and ended up paying cash to learn. Hopefully others will read this and not suffer the same fate.
What I Did (Including Mistakes)
Wipe the phone / factory reset.
Reboot and ensure everything is removed. Factory reset again.
Tried the commands - got error about FRP protection.
Did search for FRP unlock and found site.
Followed instructions on site which led me to download DC Unlocker and pay for their FRP unlock.
Reboot and setup phone (with no accounts or password or fingerprints).
Enabled "OEM UNLOCK" in developer options (which I didn't see/enable before.........)
Run commands (they all now work).
Bootloader unlocked successfully.
Device factory resets.
Setup device again skipping accounts/password/fingerprints.
Follow instructions for flashing TWRP and finishing up.
Complete.
Some other things to ensure you note - if you're migrating from any Samsung device, don't do restore of Samsung stuff like XPOSED to the Huawei. And don't just arbitrarily do a restore from Titanium either. Select only the apps you want to use, or do the longer process of getting them from Google then restoring the data after.
Something else I noticed on my KIW-L24 is that I can't update. At all. I tried using different methods including the UPDATE.APP file for the phone, but it just gets stuck in a boot-loop. Currently going to load the B151 UPDATE.APP and see if I can de-brick it. Will edit and update the thread.
*EDIT1*
And just my luck. Didn't work. So stuck in a boot-loop. Working on it and will update when done or I give up.
*EDIT2*
So during the boot-loop I held VOL-DOWN+PWR and it went to a FASTBOOT+RECOVERY option. From there I flashed TWRP back to it and the system is now up and working. So lesson learned there. No idea why my own won't go to 6 though. Don't mind 5, but wanted to go up to 6..............still - better to have it working than not working. So happy there.
Click to expand...
Click to collapse
Yeah. So after TWRP was flashed, I did a restore from a backup I found online. And that's how I managed to get it up. The restore was for 151 not 331.
khat17 said:
I posted it in this other thread.
Click to expand...
Click to collapse
anyway, nice to see that youve got it working,...
A little ways ago, I bought an unlocked LS998, which was converted to US998 via the Frankenstein method. I thought to try the installation of a custom ROM (A.I.S., if it helps), but after failing to get that working, I reverted to a TWRP backup I made prior to the install. Now however, the phone kicks me a warning that "The Phone is Permanently Locked and Cannot Be Unlocked", which I can't for the life of me figure out. Is there a way to restore the old functionality?
Alsedarna said:
A little ways ago, I bought an unlocked LS998, which was converted to US998 via the Frankenstein method. I thought to try the installation of a custom ROM (A.I.S., if it helps), but after failing to get that working, I reverted to a TWRP backup I made prior to the install. Now however, the phone kicks me a warning that "The Phone is Permanently Locked and Cannot Be Unlocked", which I can't for the life of me figure out. Is there a way to restore the old functionality?
Click to expand...
Click to collapse
Maybe this is what you were talking about... I'm not sure.
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
ChazzMatt said:
Maybe this is what you were talking about... I'm not sure.
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Click to expand...
Click to collapse
Thanks for the tip--I did have to use that initially to get back into my phone, but the lock I'm talking about is on using my SIM card (confirmed good by my carrier, and which works perfectly if put into another unlocked device).
Well--bit the bullet, deleted EVERYTHING and flashed the latest firmware. Problem seems to be resolved!
Alsedarna said:
Well--bit the bullet, deleted EVERYTHING and flashed the latest firmware. Problem seems to be resolved!
Click to expand...
Click to collapse
Can you specified what did you do?
I'M getting in the sam situation here... no service
Mrxyzl said:
Can you specified what did you do?
I'M getting in the sam situation here... no service
Click to expand...
Click to collapse
Do forgive me if my memory is a tad hazy, as I've since switched phones, but from what I recall, I wiped out every trace of everything from TWRP, flashed a stock, factory image, and in one fell swoop the device was working good as new once more.
Hi! I'm having serious issues trying to revive an XT1527 which apparently "Failes to validate boot image". I am stuck in the Fastboot screen. Trying to do Factory or Recovery modes seems to just pop up the Motorola logo for a few seconds and then throws me back to the Fastboot, sometimes with the message "Failed to pass validation". I was not doing anything for it to go to this state, and It seems a little bit late for being an update error considering this phone came 4 years ago and It's last update I could recall was in the second half of 2017.
Searching on Google (And XDA) I found that the only solution seems to be flashing the Stock ROM with fastboot (Or mfastboot). Now here's the thing, there is not such thing for this specific version apparently! I searched all over the internet, the version seems to be "MPI24.65.39-4/3_CID12", and the most similar I could find out there was the MPI24.65.39-4 (And even then it was for the XT1514 or so); none of the "Rom archives" I find has the Rom I need, there is people having this same problem with the same model since at least first half of 2018 so Motorola is just not doing anything about it? this seems really unfair coming from one of the most respected phone manufacturers of today.
I'll give you some additional info which helps to make even harder the current situation, Bootloader is LOCKED, and USB debugging is not enabled (This is strange, since I would swear I had enabled it some years ago). Please, there must be this Rom somewhere! I refuse to run out of solutions for such a ridiculous excuse, considering I've been playing the role of the "nice customer" that will not void the warranty and trust official updates
15Jacob said:
Hi! I'm having serious issues trying to revive an XT1527 which apparently "Failes to validate boot image". I am stuck in the Fastboot screen. Trying to do Factory or Recovery modes seems to just pop up the Motorola logo for a few seconds and then throws me back to the Fastboot, sometimes with the message "Failed to pass validation". I was not doing anything for it to go to this state, and It seems a little bit late for being an update error considering this phone came 4 years ago and It's last update I could recall was in the second half of 2017.
Searching on Google (And XDA) I found that the only solution seems to be flashing the Stock ROM with fastboot (Or mfastboot). Now here's the thing, there is not such thing for this specific version apparently! I searched all over the internet, the version seems to be "MPI24.65.39-4/3_CID12", and the most similar I could find out there was the MPI24.65.39-4 (And even then it was for the XT1514 or so); none of the "Rom archives" I find has the Rom I need, there is people having this same problem with the same model since at least first half of 2018 so Motorola is just not doing anything about it? this seems really unfair coming from one of the most respected phone manufacturers of today.
I'll give you some additional info which helps to make even harder the current situation, Bootloader is LOCKED, and USB debugging is not enabled (This is strange, since I would swear I had enabled it some years ago). Please, there must be this Rom somewhere! I refuse to run out of solutions for such a ridiculous excuse, considering I've been playing the role of the "nice customer" that will not void the warranty and trust official updates
Click to expand...
Click to collapse
Here it the link for xt1527 firmware:-
https://mirrors.lolinet.com/firmware/moto/surnia/official/AMXLA/
And if you need any more help,do quote to me so I can know and help you
riyan65 said:
Here it the link for xt1527 firmware:-
And if you need any more help,do quote to me so I can know and help you
Click to expand...
Click to collapse
Again, that's the MPI24.65-39, and I need the MPI24.65-39-4/3, I tried the one you linked me to, but it will fail uppon trying it with the mfastboot commands
15Jacob said:
Again, that's the MPI24.65-39, and I need the MPI24.65-39-4/3, I tried the one you linked me to, but it will fail uppon trying it with the mfastboot commands
Click to expand...
Click to collapse
Use fastboot only not mfastboot.
riyan65 said:
Use fastboot only not mfastboot.
Click to expand...
Click to collapse
Tried it, won't work either
Besides, I read somewhere that you can't "downgrade" the ROM, just boot the same or a newer version, that's why I stopped insisting with the MPI24.65-39 and started looking for the MPI24.65-39-4/3, which is my phone's current version apparently
15Jacob said:
Tried it, won't work either
Besides, I read somewhere that you can't "downgrade" the ROM, just boot the same or a newer version, that's why I stopped insisting with the MPI24.65-39 and started looking for the MPI24.65-39-4/3, which is my phone's current version apparently
Click to expand...
Click to collapse
You can flash that rom, but you need to remove the bootloader and gpt codes so your device won't get brick.
riyan65 said:
Use fastboot only not mfastboot.
Click to expand...
Click to collapse
riyan65 said:
You can flash that rom, but you need to remove the bootloader and gpt codes so your device won't get brick.
Click to expand...
Click to collapse
And how do I do that? Recovery nor Factory are working, and bootloader is locked. With the MPI24.65-39 I get usually the error "preflash validation failed"
For anyone reading, after almost two months of searching for solutions and un-flashable stock roms I came to the conclusion that it is the internal storage which is screwed. Nothing I can do besides taking it to service
15Jacob said:
For anyone reading, after almost two months of searching for solutions and un-flashable stock roms I came to the conclusion that it is the internal storage which is screwed. Nothing I can do besides taking it to service
Click to expand...
Click to collapse
Are you able to boot in bootloader then the device internal storage should be right.