Related
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
I dont own a Z3V however i own a Z3, i haven't experienced boot loop on the Z3, however i have with previous Xperia Devices i solved the issue by installing Flashtool and downloading my stock FTF file.
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
Whoever told you that you can install these doesn't know the z3v. It's a different phone from any other z3 and can't take those custom Rom.
Your best solution is to try the tft install as described in the downgrade section of the root thread. That would bring you back to a stock Verizon.
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
Sorry I did not check your PM much earlier to prevent you from doing this. Whoever did tell you about flashing a custom rom sure does owe you another phone. You have to wait until Verizon brings out the Lollipop rom, but until then, you have to somehow flash back to the original rom that came with. 4.4.4 is enjoyable enough as it is, just the lack of volte is what's the wait for on the Lollipop rom.
A rep told me today that when the Z4v, there's sure likely a quick follow up on releasing the update since they may as well base it off of it. And that's hoping if the new one even gets VoLTE...
Thanks for the help guys, I can access the phone via USB with fastboot. I am trying to flash the ftf file but I don't think I am doing it right or its not working. Is there any way I can switch it to adb mode through a fastboot command?
Sorry I don't entirely know what I am doing.
Seannnn said:
Thanks for the help guys, I can access the phone via USB with fastboot. I am trying to flash the ftf file but I don't think I am doing it right or its not working. Is there any way I can switch it to adb mode through a fastboot command?
Sorry I don't entirely know what I am doing.
Click to expand...
Click to collapse
to connect in flashmode you need to hold volume down and connect the phone to the pc with a usb cable
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Seannnn said:
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Click to expand...
Click to collapse
It's a good thing you were fortunate enough to have it replaced with no charge. Now don't make that same mistake again and wait like the rest of us. At least you confirmed for sure that flashing an incompatible ROM is death of the phone. lol
Seannnn said:
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Click to expand...
Click to collapse
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
sherdog16 said:
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
Click to expand...
Click to collapse
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
tsachi said:
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
Click to expand...
Click to collapse
yes you can... simply exclude warranty on non OEM code... very simple to solve....
sherdog16 said:
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
Click to expand...
Click to collapse
That is why the Z3v has a hash code on the phone that shows when you root it and can't be flashed over so they know if it has been rooted even if you flash back to the correct firmware. "Settings>About phone>Status" You send it in they charge you full price.
tsachi said:
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
Click to expand...
Click to collapse
Uh, VZW says it is about the "network", not bad flashes on phones. So which is it?
If VZW wasn't so anal about rooting Sony lets you root in a foolproof way, failed rooting is VZW's fault if it happens.
Any one got the solution.... my phone not working
shashikiran said:
Any one got the solution.... my phone not working
Click to expand...
Click to collapse
What did you do this time?
no recovery mode
GigaSPX said:
What did you do this time?
Click to expand...
Click to collapse
flashed flashable prerooted.zip file and not even getting recovery mode, no charging symbol, only can access fastboot mode. continiously rebooting with vibration. no display
My Z3v is rooted and is working just fine, except the annoying ads I get on my quick charge screen, now.
Anyway... I assume you haven't tried to use the Sony/Verizon Software Upgrade Assistant? It comes on your phone to install to your PC and lets you upgrade (probably never gonna get an upgrade) and factory your phone over USB. Not sure if you can download it, or if it only comes on the phone as a separate partition to install from. Can't hurt to try.
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!
I accidentally update magisk to the latest one (I totally forgot that it can only run on version 17) and now its stuck on the v30 thinq logo
can anyone help?
Are you able to boot into TWRP by powering off completely then Volume Down + Power till you see the logo then release/re-press Power (keep holding Volume down the entire time, of course)? Or can you get into the stock recovery if that's on the device (can't see how considering Magisk being on it but hey, who knows)?
If not then you could be looking at needing to reflash the entire thing using LGUP and starting clean, at least as far as my experience says. The boot loop you're experiencing isn't magically going to fix itself, so if you can't get into recovery, whether stock or TWRP, there's not much else you can do except potentially start clean.
Could be missing something here but from just what you said it might end up being the only viable solution: a clean flash with LGUP, so be prepared about having to do that, more than likely.
Gray Fullbuster said:
I accidentally update magisk to the latest one (I totally forgot that it can only run on version 17) and now its stuck on the v30 thinq logo
can anyone help?
Click to expand...
Click to collapse
You can run the Magisk 18.0 from WTF thread and even update to 18.1. I've long had Magisk 18 attached to WTF Instructions and recommended in the WTF instructions...
However, Magisk 19.x has issues flashing the stock based TWRP-flashable zips.
It's simple! If u can get to TWRP, then flash magisk uninstaller. Then reboot.
ChazzMatt said:
You can run the Magisk 18.0 from WTF thread and even update to 18.1. I've long had Magisk 18 attached to WTF Instructions and recommended in the WTF instructions...
However, Magisk 19.x has issues flashing the stock based TWRP-flashable zips.
Click to expand...
Click to collapse
I re read the thread and remembered that version 19 wont work, I feel stupid
br0adband said:
Are you able to boot into TWRP by powering off completely then Volume Down + Power till you see the logo then release/re-press Power (keep holding Volume down the entire time, of course)? Or can you get into the stock recovery if that's on the device (can't see how considering Magisk being on it but hey, who knows)?
If not then you could be looking at needing to reflash the entire thing using LGUP and starting clean, at least as far as my experience says. The boot loop you're experiencing isn't magically going to fix itself, so if you can't get into recovery, whether stock or TWRP, there's not much else you can do except potentially start clean.
Could be missing something here but from just what you said it might end up being the only viable solution: a clean flash with LGUP, so be prepared about having to do that, more than likely.
Click to expand...
Click to collapse
ah okey Im glad that its not bricked or anything, I tried to clean install using LGUP earlier and it boot like normal. so now my question is will I be able to follow the WTF guide for root?
ChazzMatt said:
However, Magisk 19.x has issues flashing the stock based TWRP-flashable zips.
Click to expand...
Click to collapse
Hmm. I've been using 19 ever since they were released as stable on stock flashable zips. No issues that I've noticed.
What kind of issues do People end up having ?. Maybe I'm having them just haven't noticed
tech_infinity said:
Hmm. I've been using 19 ever since they were released as stable on stock flashable zips. No issues that I've noticed.
What kind of issues do People end up having [emoji28]. Maybe I'm having them just haven't noticed
Click to expand...
Click to collapse
The problems only arise if they start with 19. If you were on 18 and update it to 19 there's no problem.
Sent from my LG-US998 using Tapatalk
Hi,
I tried to upgrade my US998 from Oreo to Pie using LGUP patched. The upgrade process went well until the phone restarted and have this error message:
"Your device has failed a routine safety check and will not boot..."
I did try using LG Bridge to fix = not working
I did try fastboot boot laf.img (using extracted laf from H93031a_00_OPEN_EU_OP_1105) not working.
Any other solution?
Thanks
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
JanBoyGamer23 said:
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
Click to expand...
Click to collapse
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
jaacoozee said:
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
Click to expand...
Click to collapse
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
JanBoyGamer23 said:
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
Click to expand...
Click to collapse
I'm not sure. Normally I access download mode using volume up and power button. The download mode was there for a sec and then the screen back to
"Your device has failed a routine safety check and will not boot..."
again.
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
JanBoyGamer23 said:
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
Click to expand...
Click to collapse
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
JanBoyGamer23 said:
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
Click to expand...
Click to collapse
Unfortunately my LG V30 is US region. The official bootloader site not support my phone. Thanks for your info anyway
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
schwinn8 said:
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
Click to expand...
Click to collapse
Thanks for the reply.
I didnt install TWRP or any recovery tools to my phone. My phone bootloader still locked thou.
I have read the WTF thread but the problem is I cant get into my Download mode.
Ok, what steps are you using to try to get into download mode? Presumably turning off the phone, then holding the volume up button and plugging in the USB cable (other end already connected to a Windows computer), correct? If that doesn't work, can you try other USB cables? Sometimes a bad cable could prevent the phone from going into download mode.
i grabbed this for one purpose, reading manga, mostly on the SJ app, only i didnt think when buying it that the app wouldnt work on it, so i figured OK then just whack a custom on there, so i went to try and unlock the BL, nope just fires back "command not allowed" so i thought fine do it the old fashioned way, i got root and as per the instructions DDd the twrp image over the FOTA partition but no amount of reboots worked
i then downloaded the official twrp util from the play store, said it all flashed OK, even tried multiple versions but still no matter what i try i cant get into twrp and as such cant load in lineage etc. the only thing i thought may work was Philz but the files seem to be gone for that.
anyone know if its even still possible to get twrp on a BL locked device?
Emba4 said:
i grabbed this for one purpose, reading manga, mostly on the SJ app, only i didnt think when buying it that the app wouldnt work on it, so i figured OK then just whack a custom on there, so i went to try and unlock the BL, nope just fires back "command not allowed" so i thought fine do it the old fashioned way, i got root and as per the instructions DDd the twrp image over the FOTA partition but no amount of reboots worked
i then downloaded the official twrp util from the play store, said it all flashed OK, even tried multiple versions but still no matter what i try i cant get into twrp and as such cant load in lineage etc. the only thing i thought may work was Philz but the files seem to be gone for that.
anyone know if its even still possible to get twrp on a BL locked device?
Click to expand...
Click to collapse
For stock firmwares and locked booloaders look at this thread
https://forum.xda-developers.com/t/devdb-twrp-philz-touch-xzdualrecovery-2-8-26-release.2261606/