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.
Related
Hi,
I need help guys.
I have S4 and I was trying to mess with it and now I don't have it at all. (pic 1)
the Samsung logo and unlock lock icon are as far as my phone goes now, and after that u cant even power it off u have get battery out. (pic 2)
I am able to go to download mode (pic 3)
and I was able to get to there (up+menu+power key), but now I cant even go there. I get black screen when I am trying to do it. (pic 4)
Thanks for your time,
Ps. Help me
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
answer
Eeiden said:
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
Click to expand...
Click to collapse
I was trying to flash rom, I was trying to make in international phone so it could work in Europe with out any Verizon build in stuff, just pure Samsung.
I can go do download mode, I was able to go for recovery before. That why there is the 4th picture, in stead of regular recovery a had that "teamwin" screen. Now when I press up menu and power is saying its going to recovery boot but then it resets it self and going back to Samsung unlock icon screen and just stays there...
You hold volume down + power to get to download mode. Then connect to a pc and download the all in one tool found in the development thread. Ignore the messages about having your phone in USB debugging and tell it to flash twrp 2.6.0.0. If it doesn't take In download mode, try rebooting your phone while it tries to flash twrp.
If that doesn't work flash stock with Odin and re-root and unlock the phone.
Sent from my SCH-I545 using xda app-developers app
I'm having the exact same problems right now. I tried flashing a 4.3 i9505 rom and now I can't get back into recovery and I can't boot into the OS. I can get into download mode and use ODIN, but I don't know what to do from there. I tried using the All-In-One tool to install TWRP, but it just says Device Not Found. I also tried flashing the stock sch-i545 kernel in ODIN, and it completed successfully, rebooted, and its still doing the same thing. Is there some other way that I've missed to return to stock? I'm kinda bummin here.. but thats what comes with the territory I suppose. Any help you can offer would be greatly appreciated. Thanks.
Found the factory image thread. Going to follow instructions. Will report back.
it works but not completly
So guys going back to my problem I was trying to do everything like lahma69 was trying too...
in odin was error that device not found, all off that...
but what I did, I look more online and I found this one guy...
and what I did in download mode I use odin, and in PDA selection I use this file stockroms(dot)net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
now boom... its kinda works... I am back with my os, I got the android root.
but some things are not right... my phone is very hot, maybe because its charging its self for the first time in weeks.
more important is Whats is happening right now, in boot menu I get errors, no commands, it was not able to do factory reset until I went into os and did it over there... and I cant do software update from Verizon... it goes to root and its trying but then gets error and going back to os...
and I am worry about that file that I download...
so we got little progress and lahma69 I can at least operate os and I have back stock root...
but until we will not going to make it 100% hold on with what I did...
U cant flash a rom thats not made specifically for the verizon variant (i545). The i9505 is the international version of the phone. Hence your phone not booting. Youre going to have to flash the stock mdk firmware through odin and start over (reroot, etc).
SCH-I545 using Tapatalk 2
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
lahma69 said:
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
Click to expand...
Click to collapse
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
SaNNeK said:
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
Click to expand...
Click to collapse
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
root problem and upgrate
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
SaNNeK said:
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
Click to expand...
Click to collapse
Did you see what I said about doing Samsung software updates? The rooting threads for the Verizon GS4 say that the new VRUAME7 OTA update can't be rooted. After flashing the stock image from oden, why don't you reroot your device according to http://forum.xda-developers.com/showthread.php?t=2290798 and then install Goomanager, click the menu key, click "Install open recovery script" and that will install TWRP recovery. From there, flash a verizon rom of your choice and all should be well, no? I only use TWRP so I can't give you any input on other recoveries. Make sure you didn't somehow get updated to VRUAME7.
township japinove
lahma69 said:
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
Click to expand...
Click to collapse
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
SaNNeK said:
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
Click to expand...
Click to collapse
Whats your build number in Settings -> About Phone ?
lahma69 said:
whats your build number in settings -> about phone ?
Click to expand...
Click to collapse
jdq39.i545vruamdk
Working progress
SaNNeK said:
jdq39.i545vruamdk
Click to expand...
Click to collapse
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
SaNNeK said:
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
Click to expand...
Click to collapse
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
lahma69 said:
And by the way,for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
And thats the most important part, because if you do you will lose root and your ability to customize your phone. In layman's terms? You will be re-VZ-navigated.
I am having a similar issue. Got the "Samsung Custom" boot screen with no boot to the OS after clean wipe and install of Hyperdrive 7. Since then I have been troubleshooting the issue and have tried many things including the "No-Wipe Factory Image". Once complete I am still getting the Samsung Custom boot screen and no loading of the OS.
Any ideas as to what I can try.
Thanks in advance,
Tony
lahma69 said:
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
as my understanding its not.. I just did that no wipe recovery...
sorry I was out of town today... so I assume I will have to do root but which one is the best? there is so many different ones...
Hey,
I've bought a G2. After I rooted it, I noticed the "rooted"-status in the downloadmode. I've read about it. I now fear that I can not exchange the unit if something is broken. The warranty is void?
So i tought about to send it back to amazon (14 days time to send it back) and get another phone?! Do you think this is ja good idea or stupid?
Thx for help.
I've never rooted a phone before but I read that when you successfully unroot the LG G2, the 'rooted' status goes away.
From what I've read, G2's bootloader is unlocked, so you can root and unroot withou LG knowing it. But take a look to the thread "return to stock".
yyz123 said:
I've never rooted a phone before but I read that when you successfully unroot the LG G2, the 'rooted' status goes away.
Click to expand...
Click to collapse
The problem is, that I can no longer unroot the device, when it should be broken. That is the real problem...
edit:
whit "another phone" i mean not a G2. i think i will buy the Sony Z1 or Htc One
I have reconsigned (returned?... send back... you know what i mean :silly: ) the device. I think I'll buy a Sony. So I have no problems with the root.
Cic3ro said:
I have reconsigned (returned?... send back... you know what i mean :silly: ) the device. I think I'll buy a Sony. So I have no problems with the root.
Click to expand...
Click to collapse
hope you don't mess the sony up! the g2 is a far better phone than the sony - if you root, you can unroot and the "rooted" returns to" unrooted" better luck next time
it sounds to me like you have messed your phone up and now you want to send it back and you expect a new one. if I was the person at the other end I would have voided your warranty and if you cant sort it im afraid you should not be flashing anything until you know what you are doing there are far too many people doing this and then returning their phones as "faulty" when basically they messed it up what happens when you do the same to the sony -will u just send that back as well- no wonder manufactures are making it more difficult for people to root in the first place please don't keep doing this as it just makes it worse for the rest of us,who flash stuff and know what they are doing--rant over, hope you take a little time to learn what you are doing in future.
martindar said:
hope you don't mess the sony up! the g2 is a far better phone than the sony - if you root, you can unroot and the "rooted" returns to" unrooted" better luck next time
it sounds to me like you have messed your phone up and now you want to send it back and you expect a new one. if I was the person at the other end I would have voided your warranty and if you cant sort it im afraid you should not be flashing anything until you know what you are doing there are far too many people doing this and then returning their phones as "faulty" when basically they messed it up what happens when you do the same to the sony -will u just send that back as well- no wonder manufactures are making it more difficult for people to root in the first place please don't keep doing this as it just makes it worse for the rest of us,who flash stuff and know what they are doing--rant over, hope you take a little time to learn what you are doing in future.
Click to expand...
Click to collapse
no haha. i think you don't understand me (or i'm to dopy to write understandable english....). the device is not broken. i was thinking about, what could happen, if the device is broken and rooted. i know how to root or flash some rom. that is not my problem. the problem is, that LG has a rootchecker and Sony literally allows the root and flashing roms without unlocking the bootloader. this is why i want to send the G2 back and buy a new Z1.
Cic3ro said:
no haha. i think you don't understand me (or i'm to dopy to write understandable english....). the device is not broken. i was thinking about, what could happen, if the device is broken and rooted. i know how to root or flash some rom. that is not my problem. the problem is, that LG has a rootchecker and Sony literally allows the root and flashing roms without unlocking the bootloader. this is why i want to send the G2 back and buy a new Z1.
Click to expand...
Click to collapse
To my understanding most of the newer devices have indicators buried in the settings to list rooted.
As long as the device powers on you can unroot the LG with the return to stock method and it will show unrooted. You just boot into download mode, and run the tools listed.
If it doesn't power on... then does it matter? It wouldn't be viewable under standard warranty anyways.
Enjoy the other phone if that's your choice, but you made a poor one IMHO.
digitard said:
To my understanding most of the newer devices have indicators buried in the settings to list rooted.
As long as the device powers on you can unroot the LG with the return to stock method and it will show unrooted. You just boot into download mode, and run the tools listed.
If it doesn't power on... then does it matter? It wouldn't be viewable under standard warranty anyways.
Enjoy the other phone if that's your choice, but you made a poor one IMHO.
Click to expand...
Click to collapse
Agreed but it still shows rooted in download mode after going back to stock.
fr8cture said:
Agreed but it still shows rooted in download mode after going back to stock.
Click to expand...
Click to collapse
I don't believe so.
I have the ATT version, and I nuked it with a bad flash and a brain fart that caused me to forget to backup first in TWRP.
I couldn't get anything on the device so I did the restore to stock using the flash tool, and when I was done I'm pretty sure it showed green until I rooted it again.
digitard said:
I don't believe so.
I have the ATT version, and I nuked it with a bad flash and a brain fart that caused me to forget to backup first in TWRP.
I couldn't get anything on the device so I did the restore to stock using the flash tool, and when I was done I'm pretty sure it showed green until I rooted it again.
Click to expand...
Click to collapse
Ah mine showed rooted but I tried the back to stock for all variants and it didn't work (worked the first time not the second) so then I did the vzw only back to stock and that worked but still showed rooted in download mode.
After the unroot yesterday the "rooted" in the downloadmode was gone too
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Please help, Boot Loop. "Your device is corrupt cannot be trusted and may not work"
My phone has been working absolutely fine since I've had it for about 4 months. Out of nowhere tonight, i pulled my phone out of my pocket and it was stuck in a boot loop. the LG screen flashes then i get the message "your device is corrupt cannot be trusted and may not work properly". I have no idea what to do about it and i can't find any other similar issues or fixes online.
I've taken out the battery and used another and that didn't help.
I booted into recovery mode by pressing and holding the power + volume down button at the same time
and wiping cache partition but that didn't help.
I have the Sprint model phone. I have never attempted to root or flash with this phone so i'm completely baffled. Any advice is greatly appreciated and thank you for your time.
Never heard of anything like that..
Maybe factory data reset in recovery would help..
Sent from my LG G5 (H850) via tapatalk
Alttu said:
Never heard of anything like that..
Maybe factory data reset in recovery would help..
Sent from my LG G5 (H850) via tapatalk
Click to expand...
Click to collapse
I've read online with other phone having this issue that factory reset does not resolve the issue. Apparently the early version of the G4 was notorious for a similar issue.
https://www.youtube.com/watch?v=9Flg3nZr6nU
I had the same bootloop and messages. However it was caused when I tried to install a new rom. The solution for me was to wipe and format the memory, then flash the original 10c zip from this forum.
The Trick is to Format Data after flashing SuperSU (Not just wipe). Many People for get this Step. You're also in the wrong Forum...
EDIT: You're on Sprint so no Root. But this Message means that Youre Data is broke. You should be able to fix it with the Flash Tool for Your Phone... Have You tried to Root it? Can't understand how You managed to break it. But You should also have Your warranty without Bootloader Unlockand Root
Miustone said:
The Trick is to Format Data after flashing SuperSU (Not just wipe). Many People for get this Step. You're also in the wrong Forum...
EDIT: You're on Sprint so no Root. But this Message means that Youre Data is broke. You should be able to fix it with the Flash Tool for Your Phone... Have You tried to Root it? Can't understand how You managed to break it. But You should also have Your warranty without Bootloader Unlockand Root
Click to expand...
Click to collapse
Thanks. Which forum do i need to be in?
I haven't tried root or anything. I should be find with warranty, but i would like to try and recover my data before i format the phone....
Screenshots
Fadman37 said:
Screenshots
Click to expand...
Click to collapse
It's moved Now to the right Forum. But let me say that Your Data are lost... Even if You get Root and a Recovery. Your last Chance is the LG/Sprint Repair Service.
The other *fast* way is to recover the Firmware with a PC. But also in this Case You will lose Your Data
I'm sorry to say that
Seen a couple people on Reddit with Sprint G5 phones report the same thing after a firmware update. Maybe that's the issue
I had a boot loop with my Samsung Galaxy S6 and Samsung had to replace the PBA (Mother Board) under warranty.
So high likelihood that it is a hardware problem.
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.