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.
Related
Hey all,
I have a CWM backup of my current rom and have backups of apps and data but am stuck at a bootloop.
As I have read countless articles, it seems my error is because I have a locked bootloader(not actually sure). Though, I only tried to flash
clockcycle's wiped v20d cwm backup file. It failed part way saying it couldn't write to /system.
Since then, I haven't been able to fully enter CWM. just see the red triangle with the droid guy on his back.
I have read Cmahendra's unbricking guide but it doesn't work as I have installed JB and even the tips to unplug, wait 10s and reopen the program to flash again it still won't work. Still stops at 15% saying error connecting to the phone.
There is a similar thread which had this exact problem which said to
use the online method to recover your phone since I had already installed JB. I edited the hosts file to remove the fake offline server and opened up the b2CAppsetup.exe, clicked on customer support,
entered my model LGP769BK and my S/N and it began to start the process and 'analyze' then crashed and said "updating is not possible any longer due to a fatal error while the LG mobile phone software Update"
I've tried to search this out myself and not waste any space but I'm at loss here. If anyone has any help, it would be much appreciated
as I don't have a phone while this is not working.
I've tried all the ways to to hard reset, master reset and still I get the droid guy on his back. I can get to S/w mode like all the other posts say to do but none of those fixes seem to work for me. Am I missing something?
Do I have any options here? I have kind of read that I should just unlock the bootloader but I don't think that applies in my case as I can't turn on my phone fully.
edit: for the online method(LG support tool), it basically cancels when it goes to the 'downloading' phase --> this is what I've seen as most of the answers but doesn't work
Upon further reading,
many seemed to need to replace their u-boot and x-loader
I did so and installed fastboot using Lelus' script here:
http://forum.xda-developers.com/showpost.php?p=41768774&postcount=1
I used option 6 which allowed me to flash the u-boot and x-loader from p760(works with my 769 and others as it says in the options) for JB
I'm not sure if I needed this as I don't have an unlocked bootloader.
I'm not sure of commands in fastboot but I ran
fastboot devices and it showed something
I also ran: fastboot flash recovery recovery.img
and I put one of my cwm backups in the "yours" folder
After I activate fastboot, it brings me to the C:\fastboot\yours folder
I assume this is for me to put my intended files in but I'm unsure if I should use my cwm backup or something else?
After it flashed the recovery img, I sent a fastboot reboot command
but it still went back to the droid lying down with a red triangle.
As some of you may see, I'm not too great with this but I feel like I'm close. Does anybody have an idea of what I should be doing?
should I flash an update.zip?
I don't know many commands but hopefully this gets me going in the right direction.
PLEASE HELP ME!!!!
I guess your cmw restore formatted your system but couldnt load the new system
the recovery you run with a locked bootloader uses a technique called 2nd init which i think is somewhere stored in the system partition. so when the recovery formatted the system, it lost itself too.
I've had a similar problem. the way out would be booting into the SW upgrade mode--switch off the device, remove the battery, remove the usb cable. press the volume up button and connect the phone to the computer. wait for a couple of seconds and then insert the battery.
you should be in the SW upgrade mode
now use the B2C client. if it gives an option to upgrade, use that otherwise, go to the customer support menu and press recovery phone
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
shockah486 said:
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
Click to expand...
Click to collapse
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Tablechair said:
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
Click to expand...
Click to collapse
Thanks.I'll try this. if I have the ICS bootloader, does that mean I'll have to flash the V10G kdz? or can i do the v20d kdz
dhruvbatra205 said:
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Click to expand...
Click to collapse
I have the updated kdz fw upd .zip from the unbrick and root thread as well as downloaded a new, official B2C client but they all still hang at the download part during phone recovery.
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
shockah486 said:
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
Click to expand...
Click to collapse
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
Not yet. having problems flashing a kdz again. I've tried the 2 different software modes, as well as setting emerg and diag but still getting stuck at 15% again.
Do i have to replace my uboot and xloader with the ICS ones every time I want to use the offline flash method?
edit: yup, after replacing with ICS loaders again i'm able to flash using software upgrade. will update on whether I can restore cwm
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Help.
shockah486 said:
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Click to expand...
Click to collapse
Although I might be late, I have the same problem and the same phone and I really need help. I have a soft bricked phone lg optimus l9 and I had the same problems that you had exactly... Which is weird exept I don't have Clock Work Mod or anything ... If you get this I would really appreciate some help. Thanks
yup me too
I finally got software upgrade to work with my lg p769 that was security error cuz i still haven't unlocked the bootloader, if i knew what a good job lg and T-Mobile did in locking it i would have waited and got a g3 that my buddy rooted in like 5 min and unlocked the boot....
What worked for me is this LG FLASH TOOL 2014 THREAD ON XDA
http://forum.xda-developers.com/showthread.php?t=2797190
flashed both the 20H and 20D successfully i uninstalled everything lg in the control panel first though.
Hope this works for you cuz i was struggling on and off for a month to get this far lol
the 2014 tool ultimately worked for me too, once I fixed a couple things. I had rooted and forgotten to unlock, so it was at Security Error, and it would also disconnect at 15% .. in the 2014 tool, I had to install all the updates even though I'm in windows 7 or it would keep doing it. All good now.
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Liger878 said:
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Click to expand...
Click to collapse
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
shockah486 said:
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
Click to expand...
Click to collapse
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Hopefully you find the thread that states the exact steps bc that is off the top of my head and over a year ago by memory . GL bud
Liger878 said:
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Click to expand...
Click to collapse
Hey, I have been trying it with the fastboot but it keeps timing out and not allowing me to finish. One thing I should let you know is that, ever since I had put the device in fastboot, I am not able to get back the S/W upgrade mode. Dont know if that will help in seeing what my problem is or if you want me to explain everything from the beginning again, I am more than happy to.
Have you followed the steps that I linked to in the first 3 posts of this thread?
Follow the steps to flash the ICS bootloaders in fastboot and then you can do the fastboot trick for getting the software to recognize your device.
Right now your phone has the JB boot loader on it and is thus not recognized by the software.
recap:
step 1: flash the ICS bootloaders in fastboot (look at the linked thread in post 2)
step 2: use the software in emerg or diag mode but sitll follow the same steps as the tutorial. I think my earlier posts should explain precisely.
if you dont flash the ICS bootloaders, it won't be recognized by the KDZ installer
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
Hello there, sorry for posting, this is literally my last resort.
So, here's the whole story. In my attempts to install a custom recovery mode(first TWRP) then I tried to follow this guide: Link is here of xda forum. So, my phone runs Fastboot and doesn't really have any stock recovery (just a factory settings window, which is now gone as well). So apparently after I entered these two commands into adb
fastboot oem unlock
fastboot format userdata
Click to expand...
Click to collapse
The first command unlocks the boot-loader and I thought that the second command would erase userdata, which is just photos and files, but apparently that second command has erased the whole rom + the factory settings window, that was on the phone.
So that's basically the story, now I am searching for a Stock ROM of the Flycat Optimum 5501, Android 5.1.
My phone is:
Flycat optimum 5501
Was running Android 5.1
If any information is required, I will provide. Please help and thank you for reading!
Alright development update. I've did like hell of a lot of digging, until it hit me to check the official Flycat website, so I went back and forth through the whole website right? And bam, I literally found 2 STOCK ROMS by going to this link.
I am still currently looking into ways to how to install this rom. If anyone could give advice onto how to install it using Fastboot, I would be thankful!
Update: So I found out that an application "Smart phone Flash tool" can flash your whole phone if you accidentally ****ed up. So I went to watch a few tutorials in youtube about that application and I managed to unbrick my phone. It works as it worked at the start. Welp I managed to fix it with pure research and dedication to this **** (I gotta get some beer)
At any case, for those of you who have the same phone and run into the problem. I hope that my updates will help ya. Sorry for the constant posting, my problem is fixed ^^
I do still wanna find a custom recovery image, that would work on this phone, so if anyone finds a way, please comment!
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!
Hi, good evening to the community!
(EDIT: Anyway, I want to apologize if I'm doing something wrong. I recently joined).
I believe I made the biggest mess of my life, and now I'm desperate. I downloaded the latest version of TWRP, to update the one I already used; the problem is that. Now he is no longer in Recovery Mode. And worst of all? I had already deleted my OS. So, there's no way I can authorize OEM unlocking. So I can not use ADB & Fastboot. And I think I have to throw my device away as it is unusable. What should I do? I'm desperate and there are no solutions.
-Thanks
Lord_Miraak said:
Hi, good evening to the community!
(EDIT: Anyway, I want to apologize if I'm doing something wrong. I recently joined).
I believe I made the biggest mess of my life, and now I'm desperate. I downloaded the latest version of TWRP, to update the one I already used; the problem is that. Now he is no longer in Recovery Mode. And worst of all? I had already deleted my OS. So, there's no way I can authorize OEM unlocking. So I can not use ADB & Fastboot. And I think I have to throw my device away as it is unusable. What should I do? I'm desperate and there are no solutions.
-Thanks
Click to expand...
Click to collapse
There is no need to worry if you corrupt you recover, just enter into bootloader mode then flash the recovery.
code:-fastboot flash recovery moto.img
Note:- Moto should be replaced with the recovery name
If you want to return to stock ROM then here is the procedure:-
Firmware:-https://mirrors.lolinet.com/firmware/moto/surnia/official/
Procedure:-https://www.google.com/amp/s/forum....tore-moto-e-2015-stock-firmware-t3044936/amp/
Done now you are now stock ROM .
riyan65 said:
There is no need to worry if you corrupt you recover, just enter into bootloader mode then flash the recovery.
code:-fastboot flash recovery moto.img
Note:- Moto should be replaced with the recovery name
If you want to return to stock ROM then here is the procedure:-
Firmware:-https://mirrors.lolinet.com/firmware/moto/surnia/official/
Procedure:-https://www.google.com/amp/s/forum....tore-moto-e-2015-stock-firmware-t3044936/amp/
Done now you are now stock ROM .
Click to expand...
Click to collapse
Yes thanks! I did it yesterday, watching a Brazilian video. I had to download 3 different ROMs to be able to do such a process; so I did the process through Fastboot. Thank God I did not have to buy another device, hehe. And I'm already using another Custom Rom at the moment (RR, but I plan to change it as soon as I find another great new one that does not bug WhatsApp). Thank you again!