Related
Dear Developers and Users
I have moto E xt1021 some time ago. Once it happen that my phone Android crashed then I successfully flashed back new kitkat 4.4.4.
My phone worked fine and even checked if there is any software updates, I think this was my mistake. Then I upgraded to Lollipop 5.0.2.
Also I installed CWM recovery but as a beginner, did not thought of backing up all my data, another mistake because all my data are gone now.
Every thing was fine for about one month. Suddenly, last week my phone starts freezing and not responding to any touch.
Well, the quick solution is re-start. But it never came back again to more than the Moto logo.
Depending on what I was reading since last week, I think my phone is brick now, hopefully soft, because the situation of my phone is as follows
Stops by Moto logo when pressing power on.
I can go to the Bootloader menu.
I can see my CWM-recovery menu. But from here I am not able to flash new ROM, Stock, or even recovery.
My phone is unlocked and rooted as far as I remember, I hope it is still.
and the most important part:
USB debugging mode WAS NOT ENABLED before it crashes and it still not enabled.
I installed on my PC SDK, fastboot and ADB tools, Motorola Drivers.
I have been trying for a week now several tens of threads but unfortunately never succeeded to bring it back working.
I don't care for my data now. Important to get alive.
I am sorry for the long thread. I tried to put all information needed and hope nothing is missing that clarify this problem. BTw, I bought my phone from Germany.
Any help or recommendation what to do would be highly appreciated, Especially with enabling the USB DEBUGGING MODE which I think is the key solution.
Thanks in advance
Sadam.
What about: http://forum.xda-developers.com/showthread.php?t=2755857
If you can boot your phone into fastboot mode you should be fine. Just follow the flashing tutorial.
Alternatively, if you can only get into cwm recovery there is an option in moto e android development to restore to android 5.
am2012 said:
What about: http://forum.xda-developers.com/showthread.php?t=2755857
If you can boot your phone into fastboot mode you should be fine. Just follow the flashing tutorial.
Alternatively, if you can only get into cwm recovery there is an option in moto e android development to restore to android 5.
Click to expand...
Click to collapse
Thanks for your answer am2012
I followed this tutorial and many other similar threads.
It gives me always the same error whenever I ran command with mfastboot.exe (I mean the whole bunch of mfastboot commands). Please check the error.jpg in the attachment. Maybe some one have seen such error and how to solve it.
Could be also something to do with the partition of my device ? If yes, Any suggestions are appreciated!
Thanks
SadamHazaimeh said:
Thanks for your answer am2012
I followed this tutorial and many other similar threads.
It gives me always the same error whenever I ran command with mfastboot.exe (I mean the whole bunch of mfastboot commands). Please check the error.jpg in the attachment. Maybe some one have seen such error and how to solve it.
Could be also something to do with the partition of my device ? If yes, Any suggestions are appreciated!
Thanks
Click to expand...
Click to collapse
So you can actually boot into cwm recovery not just bootloader?
Can you take a picture of your phone in recovery? I might have an idea.
I asked a friend and he said go to bootloader and flash 4.4.4 using adb. http://forum.xda-developers.com/showthread.php?t=2759495 You must flash 4.4.4, not earlier or phone will brick.
am2012 said:
I asked a friend and he said go to bootloader and flash 4.4.4 using adb. http://forum.xda-developers.com/showthread.php?t=2759495 You must flash 4.4.4, not earlier or phone will brick.
Click to expand...
Click to collapse
I tried it and again the same failure as in the first reply
I attached my bootloader menu and Recovery menus as well.
Thanks
SadamHazaimeh said:
I tried it and again the same failure as in the first reply
I attached my bootloader menu and Recovery menus as well.
Thanks
Click to expand...
Click to collapse
It's a little beyond me now. I have found this YouTube video: https://www.youtube.com/watch?v=pYjQePBRzhk
Let me know if it is any good?
If you search for the error codes there are lots of results on google.
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
OK. I'm running the Moto Z unlocked 64GB version. Everything is stock. I unlocked the bootloader, and then flashed a custom logo to get rid of the "Unlocked bootloader" warning screen. Now the phone will not get past the new logo that I flashed. What can I do? I can get into fastboot or recovery, or boot twrp from fastboot(stock recovery still installed)
How can I get my phone to boot? Even if I have to live with the unlocked bootloader warning I'm cool with that. Please help!
Willing to pay $20 paypal or google wallet to anyone that can help me get my phone back working....
SixShots said:
OK. I'm running the Moto Z unlocked 64GB version. Everything is stock. I unlocked the bootloader, and then flashed a custom logo to get rid of the "Unlocked bootloader" warning screen. Now the phone will not get past the new logo that I flashed. What can I do? I can get into fastboot or recovery, or boot twrp from fastboot(stock recovery still installed)
How can I get my phone to boot? Even if I have to live with the unlocked bootloader warning I'm cool with that. Please help!
Click to expand...
Click to collapse
You should be fine, I'm assuming you flashed that boot logo without installing a custom kernel to disable force encryption and here's how I flashed stock when i did something similar.
This is exactly what I did from a bricked phone. I got a strange "error" message after flashing this that looks like the no command error, but after holding power it rebooted to Nougat.
Using Minimal adb and Fastboot:
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps!
I used the Mexican Nougat firmware from here, I'm on 32GB UK model though. https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Just don't flash a MM one if you're coming from Nougat, that will not work. And remember to check the number of system chunks it may not be 16 for whichever firmware you use.
I'm currently downloading the stock MM firmware in hopes that it helps, gotta love living in the middle of nowhere with a 3mb DSL connection :-\
So basically I can't flash a logo unless I flash the kernal first?
Secondly, With this stock MM that i'm downloading, once I flash all of it using fastboot it should be back to stock completely except still have the "Bootloader unlocked" warning, yea?
SixShots said:
I'm currently downloading the stock MM firmware in hopes that it helps, gotta love living in the middle of nowhere with a 3mb DSL connection :-\
So basically I can't flash a logo unless I flash the kernal first?
Secondly, With this stock MM that i'm downloading, once I flash all of it using fastboot it should be back to stock completely except still have the "Bootloader unlocked" warning, yea?
Click to expand...
Click to collapse
Okay so you haven't ever been on Nougat? Just making sure because when you OTA to Nougat there's no way back.
I think so, to be honest I only changed the boot logo after I flashed LineageOS so I'm not sure.. but you need to disable forced encryption by flashing custom kernel to modify system files without it getting stuck booting up. I went through this myself when i first unlocked it, this is what fixed it for me. Good luck!
Yup it should be back to stock but still unlocked bootloader.
supacrazyguy42 said:
Okay so you haven't ever been on Nougat? Just making sure because when you OTA to Nougat there's no way back.
I think so, to be honest I only changed the boot logo after I flashed LineageOS so I'm not sure.. but you need to disable forced encryption by flashing custom kernel to modify system files without it getting stuck booting up. I went through this myself when i first unlocked it, this is what fixed it for me. Good luck!
Yup it should be back to stock but still unlocked bootloader.
Click to expand...
Click to collapse
No I'm on Nougat now, But when I tried to flash one of the Nougat zip's from the post above it stated that I needed to have either 6.0* something OR 7.* something. Which made me think I could flash the 6.0 as an OTA, is that wrong?
I have the XT1650-03, which version of Nougat should I be pulling from that post? The one I got was obviously the wrong one :-\
SixShots said:
No I'm on Nougat now, But when I tried to flash one of the Nougat zip's from the post above it stated that I needed to have either 6.0* something OR 7.* something. Which made me think I could flash the 6.0 as an OTA, is that wrong?
I have the XT1650-03, which version of Nougat should I be pulling from that post? The one I got was obviously the wrong one :-\
Click to expand...
Click to collapse
Okay if you've updated to Nougat there's no way a MM firmware will work, thanks to Moto updating the bootloader making it incompatible. Where was the message that said you needed something? Did you unzip the file and flash each chunk in fastboot?
I think Rogers was a good option, i also have XT1650-03. Maybe try the Retmx like i did.
supacrazyguy42 said:
Okay if you've updated to Nougat there's no way a MM firmware will work, thanks to Moto updating the bootloader making it incompatible. Where was the message that said you needed something? Did you unzip the file and flash each chunk in fastboot?
I think Rogers was a good option, i also have XT1650-03. Maybe try the Retmx like i did.
Click to expand...
Click to collapse
Well... I was able to download and flash the entire ROGERS version, My phone will boot to the Cyan M logo screen and then instead of the animation "ring ring hello moto" the screen just goes black. Eventually it connects to my computer but I can't find a way to turn the screen on or do anything. Downloading the RETLA version to see if that works since I'm pretty sure that was what was on the phone to begin with... *sigh*
SixShots said:
Well... I was able to download and flash the entire ROGERS version, My phone will boot to the Cyan M logo screen and then instead of the animation "ring ring hello moto" the screen just goes black. Eventually it connects to my computer but I can't find a way to turn the screen on or do anything. Downloading the RETLA version to see if that works since I'm pretty sure that was what was on the phone to begin with... *sigh*
Click to expand...
Click to collapse
Ah I don't know why that is, as i said I'm at sure what's best for your model sorry. The easy flash to Nougat guide link i sent you may be better, but yeah if you know it came with RETLA then give that one a try :good:
I think your best bet is to try that RETLA firmware.
I'm not sure how it does with Moto phones, but some variants are kinda picky with their software channels. Factory images designed for retail ("RETxx") devices might have a better chance since my RETAPAC model is on a RETMX build of Nougat. It's slightly older than the TELUS build that's newer and comes with some bug fixes, including one that resolves an issue where the 2 HP CPU cores "park" after some time of use, although I've heard of some issues when using that build with some devices. Mine's a bit iffy, but otherwise seems to run quite nicely.
Once flashed, if you wanna flash system mods, do not boot just yet. Flash or boot into TWRP and try the following kernel
https://forum.xda-developers.com/moto-z/development/kernel-turbo-z-custom-kernel-moto-z-t3493354
This disables forced-encryption and dm-verity (the latter is what's responsible for your phone refusing to boot). Additionally, you can flash SuperSU using the following method.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
D13H4RD2L1V3 said:
I think your best bet is to try that RETLA firmware.
I'm not sure how it does with Moto phones, but some variants are kinda picky with their software channels. Factory images designed for retail ("RETxx") devices might have a better chance since my RETAPAC model is on a RETMX build of Nougat. It's slightly older than the TELUS build that's newer and comes with some bug fixes, including one that resolves an issue where the 2 HP CPU cores "park" after some time of use, although I've heard of some issues when using that build with some devices. Mine's a bit iffy, but otherwise seems to run quite nicely.
Once flashed, if you wanna flash system mods, do not boot just yet. Flash or boot into TWRP and try the following kernel
https://forum.xda-developers.com/moto-z/development/kernel-turbo-z-custom-kernel-moto-z-t3493354
This disables forced-encryption and dm-verity (the latter is what's responsible for your phone refusing to boot). Additionally, you can flash SuperSU using the following method.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
Click to expand...
Click to collapse
At this point i'm just trying to get my phone to boot lol. I wish I had read more to begin with... Knowing that unlocking the bootloader now breaks the safety net for Android Pay(it didn't with Moto X) is making me worry that it will also cause my Wells Fargo Mobile app to not work. At which point I might as well not even have the phone.
As of now I am able to flash the RETLA version but once I get past the Cyan M logo screen the screen goes blank and does not turn on even though my computer is recognizing that it's there. I'm about to try flashing the RSD rogers MM firmware(without the gpt and bootloader commands) and then sideloading Nougat to see if that gets me anywhere. If i can get it to boot normally I can at least sell it(at a loss) and buy another one. But I need it to at least boot up that way I don't have to sell it for 100 bucks lol. Any other ideas are welcome but I feel like i stepped in quicksand and the more I struggle with it the worse it's getting.
SixShots said:
At this point i'm just trying to get my phone to boot lol. I wish I had read more to begin with... Knowing that unlocking the bootloader now breaks the safety net for Android Pay(it didn't with Moto X) is making me worry that it will also cause my Wells Fargo Mobile app to not work. At which point I might as well not even have the phone.
As of now I am able to flash the RETLA version but once I get past the Cyan M logo screen the screen goes blank and does not turn on even though my computer is recognizing that it's there. I'm about to try flashing the RSD rogers MM firmware(without the gpt and bootloader commands) and then sideloading Nougat to see if that gets me anywhere. If i can get it to boot normally I can at least sell it(at a loss) and buy another one. But I need it to at least boot up that way I don't have to sell it for 100 bucks lol. Any other ideas are welcome but I feel like i stepped in quicksand and the more I struggle with it the worse it's getting.
Click to expand...
Click to collapse
Well, if you want my advice, if you can find it, flash the firmware that your device was last at before you flashed Nougat.
An OTA bricked my Z, but flashing the full firmware made exactly for my variant brought it back to life. If you can find it for yours, you might get a lucky break.
Also, Magisk can help with SafetyNet, though it needs root access.
D13H4RD2L1V3 said:
Well, if you want my advice, if you can find it, flash the firmware that your device was last at before you flashed Nougat.
An OTA bricked my Z, but flashing the full firmware made exactly for my variant brought it back to life. If you can find it for yours, you might get a lucky break.
Also, Magisk can help with SafetyNet, though it needs root access.
Click to expand...
Click to collapse
My issue with that is I can't figure out which firmware was made for my device. I thought it was the RETLA version but apparently I was wrong. Is there any way to figure out which one i need? I have all of the info from my getvar command in fastboot but it's not giving me any info(that i understand) that will point me in the direction of the correct firmware.
I'm currently downloading the rogers MM firmware to see if i can flash back to MM and then sideload nougat but I don't know if that's going to do any good considering that the screen won't load right now with the Nougat firmware I have on it.
SixShots said:
My issue with that is I can't figure out which firmware was made for my device. I thought it was the RETLA version but apparently I was wrong. Is there any way to figure out which one i need? I have all of the info from my getvar command in fastboot but it's not giving me any info(that i understand) that will point me in the direction of the correct firmware.
I'm currently downloading the rogers MM firmware to see if i can flash back to MM and then sideload nougat but I don't know if that's going to do any good considering that the screen won't load right now with the Nougat firmware I have on it.
Click to expand...
Click to collapse
Try RETUS if it fails?
I'm crossing my fingers hoping that the ROGERS firmware can help.
D13H4RD2L1V3 said:
Try RETUS if it fails?
I'm crossing my fingers hoping that the ROGERS firmware can help.
Click to expand...
Click to collapse
You mean the RETUS 6.0 firmware? And basically go through the same thing as the ROGERS firmware (flash mm without GPT and bootloader) and then try to upgrade? I haven't been able to find a RETUS 7.0 firmware anywhere yet so I assume that's what you mean...
SixShots said:
You mean the RETUS 6.0 firmware? And basically go through the same thing as the ROGERS firmware (flash mm without GPT and bootloader) and then try to upgrade? I haven't been able to find a RETUS 7.0 firmware anywhere yet so I assume that's what you mean...
Click to expand...
Click to collapse
Yeah.
Because the only other fix I can think of is basically flashing the entire firmware including GPT and bootloader via RSD. But that requires firmware that's made exactly for that device and bootloader just to make sure everything is fine.
I'm still crossing my fingers in the hopes that your Z will make it through.
D13H4RD2L1V3 said:
Yeah.
Because the only other fix I can think of is basically flashing the entire firmware including GPT and bootloader via RSD. But that requires firmware that's made exactly for that device and bootloader just to make sure everything is fine.
I'm still crossing my fingers in the hopes that your Z will make it through.
Click to expand...
Click to collapse
Well... to be honest the only reason I wasn't planning on rooting or using a custom ROM was because of the whole not working with android pay/wells fargo deal. If Magisk will help with that then that's definitely an option as well... Especially right now considering that I can't get ANYTHING to work if i can root, install a stock ROM and use magisk to hide the safetynet I'm totally fine with that as well. Any ideas?
SixShots said:
Well... to be honest the only reason I wasn't planning on rooting or using a custom ROM was because of the whole not working with android pay/wells fargo deal. If Magisk will help with that then that's definitely an option as well... Especially right now considering that I can't get ANYTHING to work if i can root, install a stock ROM and use magisk to hide the safetynet I'm totally fine with that as well. Any ideas?
Click to expand...
Click to collapse
Well, to even get Magisk and root to work, you need a working firmware.
The fact that your device showed the cyan Moto screen means that the firmware is recognized, and how your PC recognizes the phone means that something is indeed working.
But somehow, it's not displaying anything.
Sadly, the best piece of advice I can give right now is to try to flash a full firmware, especially one that was made for your device just to be safe. Motorola support probably won't be of much help since your warranty is void, though some did have success in the past, but I'd say that you might not get too much from them.
dm-verity is a pain, so I don't understand why it's not disabled when the bootloader is unlocked.
D13H4RD2L1V3 said:
Well, to even get Magisk and root to work, you need a working firmware.
The fact that your device showed the cyan Moto screen means that the firmware is recognized, and how your PC recognizes the phone means that something is indeed working.
But somehow, it's not displaying anything.
Sadly, the best piece of advice I can give right now is to try to flash a full firmware, especially one that was made for your device just to be safe. Motorola support probably won't be of much help since your warranty is void, though some did have success in the past, but I'd say that you might not get too much from them.
dm-verity is a pain, so I don't understand why it's not disabled when the bootloader is unlocked.
Click to expand...
Click to collapse
So right now my best course of action is to start with the MM firmware and work my way forward either way. Can I root/install stock 7.0 ROM/magisk from the MM firmware even if I'm keeping the 7.0 gpt and bootloader?
SixShots said:
So right now my best course of action is to start with the MM firmware and work my way forward either way. Can I root/install stock 7.0 ROM/magisk from the MM firmware even if I'm keeping the 7.0 gpt and bootloader?
Click to expand...
Click to collapse
Well, here's the problem.
If you're on the 7.0 GPT and bootloader, you're out-of-luck. Because Moto has changed the rules on those to not accept Marshmallow-based firmware. Trying to flash a MM firmware will result in failure. Trying to downgrade the bootloader may cause your device to be F.U.B.A.R.
If you're still on the MM bootloader, just use the steps outlined earlier in the thread to flash N and then use the instructions and threads I linked to flash both the custom kernel and root access. If everything goes well, your Z should come back to life with those sweet-sweet notification shade goodness.
Something really weird happened while I was installing roms. Someone how my OEM got locked and I flashed and voila stuck on the oneplus logo. I have my fastboot working properly also got twrp installed. The thing is that my bootloader is locked so i cant flash and I cant unlock bootloader because I cant flash and set oem unlock. I know this is ****ed up and also my volume up key is not working so we have to work without that. . Whenevr i turn on the device the powered by android quickly disappears and i am in the fastboot. If I do oem unlock it sends me to the recovery. I am not sure why i can't OEM unlock in fastboot. I don't care about data and stuff. Just want the phone working. The unbrick guide wants me to press the volume up key to get to the qualcomm flashing. Unfortunately i can't do that. Need of dire help please ;_;
I kind of have the same problem as of 2 days (see https://forum.xda-developers.com/android/help/bricked-oneplus-x-unlock-bootloader-t3816387), which is kind of strange, as I haven't read anywhere else about it on the internet.
I'll be following this topic.
Japeroen said:
I kind of have the same problem as of 2 days (see https://forum.xda-developers.com/android/help/bricked-oneplus-x-unlock-bootloader-t3816387), which is kind of strange, as I haven't read anywhere else about it on the internet.
I'll be following this topic.
Click to expand...
Click to collapse
I've solved it bud. IF you have a working recovery and bootloader. Flash the stock OS. It'll flash even though the bootloader is locked and then your can oem unlock and do whatever.
KenSha105 said:
I've solved it bud. IF you have a working recovery and bootloader. Flash the stock OS. It'll flash even though the bootloader is locked and then your can oem unlock and do whatever.
Click to expand...
Click to collapse
That's good news! But I think I've tried that, but had no succes. Can you link me the ROM you've flashed?
Japeroen said:
That's good news! But I think I've tried that, but had no succes. Can you link me the ROM you've flashed?
Click to expand...
Click to collapse
https://downloads.oneplus.com/oneplus-x/oneplus_x_oxygenos_3.1.4/
There.
KenSha105 said:
https://downloads.oneplus.com/oneplus-x/oneplus_x_oxygenos_3.1.4/
There.
Click to expand...
Click to collapse
Thank you. I've tried it, but the problem is that I'm stuck with the Oneplus recovery, as I've mentioned in my post. From there, I have 2 options to flash:
1) from internal memory. When I click this, nothing happens (no new screen or anything, nothing)
2) from USB (adb sideload). When I try to sideload the ROM using this option, it starts promising, but after a few seconds, it just says 'Installation failed' without any reason why. Just like for all other ROMS.
So... No progress here. I've also tried to flash the stock recovery (even though it should be on my phone already, maybe another version) using fastboot, but my OPX won't take it because the bootloader is still locked.
Last resort: I'll try the Oneplus live chat tomorrow, but I do not expect any useful information from that...
Japeroen said:
Thank you. I've tried it, but the problem is that I'm stuck with the Oneplus recovery, as I've mentioned in my post. From there, I have 2 options to flash:
1) from internal memory. When I click this, nothing happens (no new screen or anything, nothing)
2) from USB (adb sideload). When I try to sideload the ROM using this option, it starts promising, but after a few seconds, it just says 'Installation failed' without any reason why. Just like for all other ROMS.
So... No progress here. I've also tried to flash the stock recovery (even though it should be on my phone already, maybe another version) using fastboot, but my OPX won't take it because the bootloader is still locked.
Last resort: I'll try the Oneplus live chat tomorrow, but I do not expect any useful information from that...
Click to expand...
Click to collapse
Well guess what, they could solve it.
Or at least partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
Hey guys:
I did unlock bootloader unload/root according to this guide.
First Wifi worked.
Then I did try to figure out OTA issues, could not uninstall Magisk, so temporary flashed stock image back.
From here on out - no matter, if stock, or Magisk_patched image: No chance to turn WiFi on.
In the WiFi-Menu, if I touch "turn on", it will show for one second: Turning Wi-Fi on", and then just return to the WiFi off-setting...
I did do factory reset from recovery - no success, flashed again (stock and patched) - no success.
I can't figure it out! Anybody an idea?
Are you sure that you are using correct boot.img version? It must be the same version as your system - build number and EU/GB variant must match.
Yes. I did, unless I had an older Version on a different slot and somehow did change slots and started messing around there. Could be an explanation.
Got tired of messing with it. Did download the whole stock rom, flashed it and will stay "unrooted" for now. Not worth the hassle to me.
BUT: What a mess that these manufacturers make it so hard to have working and rooted phone.
My guess would be that you flashed incorrect stock boot image.
Also how come that you couldn't uninstall Magisk?
Rooting is pretty straightforward, even if Mi A3 has a slight complication with missing "fastboot boot" command support, but otherwise it's nothing special. Take the correct boot.img, patch it, flash it and you're done.
First take your phone into fastboot mode. write fastboot set_active a .unzip stock rom and you will see flash_all.bat click it and you will succesfully have brand new rom with no issue. Note:If anything bad happens or goes wrong im not responsible. Its all your decision to do it
_mysiak_ said:
My guess would be that you flashed incorrect stock boot image.
Also how come that you couldn't uninstall Magisk?
Rooting is pretty straightforward, even if Mi A3 has a slight complication with missing "fastboot boot" command support, but otherwise it's nothing special. Take the correct boot.img, patch it, flash it and you're done.
Click to expand...
Click to collapse
Magisk said: no backup. tht's why I did install the original boot.img back, and this is where the WiFi-issue started.
I wanted to go this route, but did not manage it after several hours, so gave up and went stock:
https://forum.xda-developers.com/mi-a3/how-to/guide-create-manual-backup-stock-boot-t3988345
WorstCases said:
Magisk said: no backup. tht's why I did install the original boot.img back, and this is where the WiFi-issue started.
I wanted to go this route, but did not manage it after several hours, so gave up and went stock:
https://forum.xda-developers.com/mi-a3/how-to/guide-create-manual-backup-stock-boot-t3988345
Click to expand...
Click to collapse
Yeah, you need to create first backup manually. The guide works perfectly, I tested all methods (otherwise I wouldn't mention them ). What issues did you have?
The system is probably installed in b partition, you need to set partition a as active and reinstall rom via mi flashtool