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
So I'm no stranger to this but I've mainly used devices on Verizon and all of which were always fully unlockable and s-off etc etc, mainly I've used HTC devices, the Samsung devices I've used were blessed by Adam Outler, so my point is anything as far as flashing ROMs goes was just fastbooting a recovery did the trick and flashed a ROM and done. When I added a gsm device to the line up I got the Nexus 5 than got the Oneplus One, than picked one of these up for fun because love love live gigantic big F U screens haha.. So the Nexus and Oneplus were the same deal. The Z Ultra is the US LTE gsm unlocked c6806 variant stock not the GPE. So my buddy told me to dial a number via my dialer and see if its bootloader unlockable and it was so I followed Sony's bootloader unlock method and it was successful!!! Woohoo!!! But... This is where I ran in to some snags. Me being me I jumped right in to fastboot and I fastbooted Team Win Recovery the latest one 2.8.3.0 and it was successful as far as the terminal output goes, but when I tried to boot to recovery I noticed I lost my violet LED and all methods to boot to recovery failed.. I thought being unlocked fastbooting a recovery would be no problem but in my case it wasn't.. It took a day of messing around when I finally ran the ZU dual recovery with TWRP and Philz and that worked. I don't know why but it did and now I'm able to boot to both recoveries.. So I rooted with the latest SuperSU and boom I have root no problems! So now my next confusion is flashing ROMs.. I made a nandroid backup and tested it to make sure it did restore and everything was good and it was. So I went ahead and flashed the CM12 fxp build from December 31st on December 31st and flashed a Gapps package and after a few minutes and it booted up no problem. I DID NOT fastboot the boot.img from the zip first I just flashed the ROM flashed the Gapps and it works with no problem, the kernel is indeed the Cyangon kernel built on Dec 31st [email protected] blah blah... That's the ROM I've been on since than and have no problems and I haven't updated yet because there has been so significant changes since than so I found no need to. Why do every ROM threads state to fastboot the boot.img from the zip first than flash the ROM and Gapps? Is this for locked bootloaders only? Am I missing something? So yeah to sum it up basically, if I'm bootloader unlocked #1 how come I can't just fastboot flash recovery openrecovery-twrp-2.8.3.0.img and why doesn't that work? #2 How come when I came from stock 4.4.4 Sony firmware and flashed the ROM and Gapps without fastbooting the boot.img and that worked no problem? I'm trying to understand how Sony devices work so I don't run in to any issues. Sony works slightly different than what I'm use to. Oh also every time I looked for this flashtool people talk about the links are all bad... Please if someone can thoroughly enlighten me I would sincerely appreciate it. Thanks guys and maybe gals I looked forward to some solid replies!!! Feel free to PM as well if you'd like for some one on one if it makes things easier...
I can't believe 113 views and not a single response..... Well I'm glad I at least know Android and familiarized myself with Sony! To anyone hung up with recovery issues or with losing recovery whether you have the violet light or not, my best suggestion would be to just straight up start over period..
What I did was downloaded the latest Flashtool, I downloaded the latest FTF file for my device which my model is the C6806 LTE US Unlocked version...
I backed up my data and launched Flashtool, select the lightening bolt icon and select flashmode, the FTF file was downloaded in a .zip format, thats as in dot zip, you want to extract the zip file so you have the physical firmware FTF file which will end in .ftf as in dot ftf
You need to take that ftf file and navigate to Flashtools firmware folder and copy it to that directory.
Let Flashtool load that file and when completed you'll be greeted with a notification to power off the device and plug it in to the computer while holding volume down.
Flashtool will begin to do it's thing, I left all the Flashtool settings at their default settings.
When completed you will see in Flashtools window that the device is connected in flashmode, might I also add through the whole process for me the screen was black and there were no lit LED lights..
I rebooted back to complete stock, than rerooted my Z Ultra with the latest version of Easyroot Tool to regain root access.
A that point I downloaded NUTs latest version of his DualRecovery and ran the installer via my Macbook Pro to get back my custom recovery
I flashed the latest version of SuperSU version 2.45 at the time of this post and than made a Nandroid backup all for safe purposes, than rebooted the device and made sure everything was good to go.
Went back to recovery and wiped all reinstalled the latest CM12 and Gapps and here is where I went wrong last time at this point I flashed the DualRecovery flashable zip which I didn't do last time and it was clearly stated in NUTs OP to always refresh the recoveries after flashing any custom ROM to make sure you don't lose recovery like I did last time lol!
Now at this very moment I'm on the latest CM12 with my recoveries working and I have ZERO issues finally!!!!! Thanks to me for figuring it all out and some minor assistance from my boy es0tricha0s for reassurance... ANYONE having problems with their devices and recovery issues I can now most likely help you out now that I'm beginning to understand the way Sony works.... I'll even go as far as Teamviewing in to you and helping you remotely fix your device up so you don't end up the way I did....
Also FYI I started all of this bootloader unlocked and remained bootloader unlocked
So I messed up pretty badly. I recently bought an HTC One M8 for the ATT network that was previously rooted. I noticed it was on 4.4.2 and wouldn't upgrade to 5.0 so of course I tried to remove root. I went into TWRP recovery (which I know is why it wouldn't update because I didn't have stock recovery. For the life of my I couldn't get ADB to recognize my device to flash it.) I went over to "wipe" did the advanced wipe and ticked all the available options. Now, upon rebooting I noticed that I deleted the entire OS. After trying and trying I couldn't get it to boot past the HTC screen. Finally I figured out how to flash a rom using the information here "http://forum.xda-developers.com/showthread.php?t=2736694". After flashing the rom, it was still stuck at the HTC screen when trying to boot. I found some information about extracting the boot.img and flashing it using "fastboot flash boot boot.img"
Now this sort of fixed my problem. After turning the phone on, it stays stuck on the HTC screen until the screen times out. When pressing the power button to wake it up it goes into the setup page and from there to the home screen of the phone. There are apps missing, and no home or return keys on the bottom of the screen. So if I go into settings, I'm stuck there unless I power off the phone, turn it back on, let the screen time out, and wake it up.
Any one have any suggestions? As you could tell I'm not very experienced and would have never bothered with this stuff if the phone weren't already rooted when I bought it. I'd be very happy to buy someone a coffee if they can help me out
nikicollazo said:
So I messed up pretty badly. I recently bought an HTC One M8 for the ATT network that was previously rooted. I noticed it was on 4.4.2 and wouldn't upgrade to 5.0 so of course I tried to remove root. I went into TWRP recovery (which I know is why it wouldn't update because I didn't have stock recovery. For the life of my I couldn't get ADB to recognize my device to flash it.) I went over to "wipe" did the advanced wipe and ticked all the available options. Now, upon rebooting I noticed that I deleted the entire OS. After trying and trying I couldn't get it to boot past the HTC screen. Finally I figured out how to flash a rom using the information here "http://forum.xda-developers.com/showthread.php?t=2736694". After flashing the rom, it was still stuck at the HTC screen when trying to boot. I found some information about extracting the boot.img and flashing it using "fastboot flash boot boot.img"
Now this sort of fixed my problem. After turning the phone on, it stays stuck on the HTC screen until the screen times out. When pressing the power button to wake it up it goes into the setup page and from there to the home screen of the phone. There are apps missing, and no home or return keys on the bottom of the screen. So if I go into settings, I'm stuck there unless I power off the phone, turn it back on, let the screen time out, and wake it up.
Any one have any suggestions? As you could tell I'm not very experienced and would have never bothered with this stuff if the phone weren't already rooted when I bought it. I'd be very happy to buy someone a coffee if they can help me out
Click to expand...
Click to collapse
Best advice would be to just run the AT&T stock RUU. It will return your phone back to 100% stock, from there you can decide if you want to root, use a custom recovery, and install a ROM. But an RUU will be your best bet as its quick, simple, and risk free. You can download the AT&T RUU in the link I posted which will be the latest 5.0.2 Lollipop firmware, its a simple .exe file so all you have to do is connect your phone to your computer and double click the file you downloaded (RUU), it will handle the rest. http://www.htc.com/us/support/htc-one-m8-att/news/
Good luck!
root lollipop
CavyS said:
Best advice would be to just run the AT&T stock RUU. It will return your phone back to 100% stock, from there you can decide if you want to root, use a custom recovery, and install a ROM. But an RUU will be your best bet as its quick, simple, and risk free. You can download the AT&T RUU in the link I posted which will be the latest 5.0.2 Lollipop firmware, its a simple .exe file so all you have to do is connect your phone to your computer and double click the file you downloaded (RUU), it will handle the rest. http://www.htc.com/us/support/htc-one-m8-att/news/
Good luck!
Click to expand...
Click to collapse
Hi There --- Can someone help me out? I'm trying to find the correct procedure for updating the At&t M8 on lollipop......
I'm not sure if towelroot will temp root on lollipop --- based on what i've read it wont....
Any help is appreciated....i've searched but can't seem to find anything about rooting lolli on the at&t m8....
biswasd said:
Hi There --- Can someone help me out? I'm trying to find the correct procedure for updating the At&t M8 on lollipop......
I'm not sure if towelroot will temp root on lollipop --- based on what i've read it wont....
Any help is appreciated....i've searched but can't seem to find anything about rooting lolli on the at&t m8....
Click to expand...
Click to collapse
This isn't really related to the OP, so I'm not sure why you posted it to this thread.
I'm confused by the second sentence in your first line. Are you trying to update or trying to root?
Towelroot won't work if the bootloader is locked, that is the whole point of a locked bootloader.
You need to unlock the bootloader. At that point, you can root by a variety of methods. I think towelroot will work (as long as its intended for Lollipop), but you can also just flash a custom recovery and then flash a current version SuperSU (the most common method).
Hey guys so I've been killing myself just trying to find ways to get my newly rooted xperia z2 phone to boot into recovery mode.
Essentially I followed this guide to the bone and successfully rooted my phone --> http://forum.xda-developers.com/xperia-z2/development/stock-d6502-23-1-0-726-complete-guide-t3085893
The big problem is whatever I do, no matter the selection of recovery apps(quickboot, twrp manager, etc.) I install I can never get back into recovery mode, my phone turns off and goes into normal bootup, even when I try to do manual recovery mode the light indicator on top doesn't show up and the phone ends up starting normally.
I have factory resetted my phone a couple of times to have a fresh start each time I try something new but nothing seems to work.
On top of that SDFix and it's other variants does not work on my phone, so I can't install any apps on my micro sdcard. I'm really at a loss for what to do here(been at it for 3 days now) so I'm seeking help.
I'm not sure what information to give but I'll try to give as much details as I can about my situation, I'm really desperate to have recovery and my sd card working normally as I am currently very limited with the stuff I want to do on my phone. :crying::crying:
Info:
Model Number: D6503
Android Version: 5.0.2
Kernel Version: 3.4.0-perf-g72984dd [email protected] #1
Build Number: 23.1.A.0.726
SuperSU Installed
Phone is factory reset and rooted.
No other mods & apps installed aside from pre-installed apps and SuperSU
I would very much appreciate it if someone can help me with this problem, thank you!! :cyclops::laugh:
I can't access recovery mode either. Led light doesn't come on when I turn on the phone as well.
I was thinking abt rooting my phone but nvm now.
saedted said:
I can't access recovery mode either. Led light doesn't come on when I turn on the phone as well.
I was thinking abt rooting my phone but nvm now.
Click to expand...
Click to collapse
I think it doesn't matter whether your phone is rooted or not for you to be able to access recovery mode(not sure about this to be honest). I know rooting(and all this headache) is worth it for any android phone especially the xperia z2 which is why I'm hellbent on getting this fixed.
I wanna install cyanogen mod but those two things I've mentioned in my first post is really limiting what I can do with this phone sadly.
disenx34 said:
I think it doesn't matter whether your phone is rooted or not for you to be able to access recovery mode(not sure about this to be honest). I know rooting(and all this headache) is worth it for any android phone especially the xperia z2 which is why I'm hellbent on getting this fixed.
I wanna install cyanogen mod but those two things I've mentioned in my first post is really limiting what I can do with this phone sadly.
Click to expand...
Click to collapse
Sony devices don't have recovery partition, either unlock your BL (and lose DRM keys) and flash a kernel with a built-in recovery , or keep your BL locked and install nut's dual recovery (you need a rooted system before installing).
All the info needed for both options is here on xda but i think you guys need to read a lot more before you start messing with your devices....
ptmaniac said:
Sony devices don't have recovery partition, either unlock your BL (and lose DRM keys) and flash a kernel with a built-in recovery , or keep your BL locked and install nut's dual recovery (you need a rooted system before installing).
All the info needed for both options is here on xda but i think you guys need to read a lot more before you start messing with your devices....
Click to expand...
Click to collapse
I already did everything I possibly could think of (i.e. unlocked bootloader through sony website, rooted, etc.) like I mentioned in the OP, I actually just recently discovered(like 15 minutes ago) that apparently there's this thing called Sony RIC and that's what's disabling me from installing anything on the system and limiting what I can do with my phone because everything(sd card + system folders) are read only and not write-able.
I found out from this thread (http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141/page3) that there's no updated version of 'Sony RIC KILLER' for lollipop version 5.0.2. so I guess I'm stuck. I tried installing TWRP recovery through TWRP manager on my phone and it wouldn't even get to the recovery mode.
I'm gonna keep trying other variants of dual recoveries till one successfully works, I'll also try your suggestion of flashing a kernel with a built-in recovery that's one area I haven't dabbled in yet, this is my first android device so I'm still figuring out where the red line is on everything. :laugh::good:
disenx34 said:
I already did everything I possibly could think of (i.e. unlocked bootloader through sony website, rooted, etc.) like I mentioned in the OP, I actually just recently discovered(like 15 minutes ago) that apparently there's this thing called Sony RIC and that's what's disabling me from installing anything on the system and limiting what I can do with my phone because everything(sd card + system folders) are read only and not write-able.
I found out from this thread (http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141/page3) that there's no updated version of 'Sony RIC KILLER' for lollipop version 5.0.2. so I guess I'm stuck. I tried installing TWRP recovery through TWRP manager on my phone and it wouldn't even get to the recovery mode.
I'm gonna keep trying other variants of dual recoveries till one successfully works, I'll also try your suggestion of flashing a kernel with a built-in recovery that's one area I haven't dabbled in yet, this is my first android device so I'm still figuring out where the red line is on everything. :laugh::good:
Click to expand...
Click to collapse
On stock rom / kernel only nut's dual recovery will work. IT will also disable sony ric for you in the process. check here: http://forum.xda-developers.com/showthread.php?t=2261606
On custom kernel you have to choose a kernel with the recovery you want and flash that (don't forget to unlock BL before or you'll end up with softbrick). Recovery managers won't work as there is no recovery partition on your device...
install latest version of nuts recovery for z2 and install it after finish phone well reboot into recovery
Then dont update busybox it well break recovery
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