Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
andrew88 said:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
Click to expand...
Click to collapse
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
TerribleChoices said:
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
Click to expand...
Click to collapse
andrew88 said:
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
Click to expand...
Click to collapse
Oh dear.
Yeah it does sound like something got deeply ****ed up in this case. I had the luck to somehow get past the smart switch error when the phone died of low battery. As I attached it to the charger I quickly boot it into download mode before the screen would become a bootloop again and that's where I was able to reinstall the latest version of TWRP recovery. After that, I was able to flash a stock ROM of Nougat that didn't have a ****ed up bootloader like I had. Specifically the one from this thread: https://forum.xda-developers.com/galaxy-s6/help/device-5-binary-3-s6-sm-g920f-t3706025
by forumber2.
It's the Netherlands stock-ROM. Not sure if you're from the US and the carrier would be wrong with that CSC, but it was a good bet for me. I got my phone back to working normally now.
Worst case scenario I'd say see if you have a phone repair shop nearby and ask them an opinion on what could be wrong. I'm just an amateur like you.
Still, I wish you the best of luck with it. Maybe there's still some hope. :/
Related
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Dr. Light said:
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Click to expand...
Click to collapse
first of all you can't flash anything on a stock recovery hence the need of a custom recovery. Second you don't accept the OTA when rooted as it can cause the exact issue that you have. Last there isn't a way to fix your problem via another android device that I know of.
U are going to need a pc and then u will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery. Then you can access your backups.
Always_Jonezen said:
U will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery.
Click to expand...
Click to collapse
He doesn't have access to his PC PLUS he already knows what to do on that end.
jmxc23 said:
He doesn't have access to his PC PLUS he already knows what to do on that end.
Click to expand...
Click to collapse
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Thanks for all of advice guys. I'll prob just wait it out till Monday. Thanks again.
Always_Jonezen said:
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Click to expand...
Click to collapse
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
jmxc23 said:
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
Click to expand...
Click to collapse
hey all, I've been reading , downloading etc for hours trying to get back into my GS3.. i was as usual roaming around and saw a post that said something to this effect "do ya need to get back to stock?" and figured yes i need to so i jumped in with both feet ..i had my boot loader unlocked and for some reason locked the darned thing remembering it was locked before i rooted and then i get the screen that says ie: "System software not authorized ~~~~~~~~~~~~" with a yellow triangle over it with an "!" mark in it..
all would have been ok except the line up of the way to do things was kinda outta line.. after i had locked bootloader "which is the way the GS3 came" i thought. at any rate i am now where i said i was and if i can be helped it would be appreciated.. and no repeated.. next time i'll read their whole line up first.. so help me if ya can and i am game right now for about anything ..
Hey guys, I somehow managed to soft brick my verizon GS3 this afternoon. I just need a little help in getting the thing back up and running and possibly an explanation on were I went wrong. I thought I had unlocked the bootloader and then rooted the phone. I managed to install TWRP 2.5.0.0 and do a backup. Then I installed a custom ROM and got the infamous "Software not authorized" message with the yellow triangle.
1st, is it possible to get this far with the bootloader still being locked??
2nd, If I understand correctly, I need to use ODIN to go back to stock and start over. Correct? Or is there another way to salvage this situation. If I have to go back to stock, can someone point me to the latest files? I've found links to a lot of different ones and I don't want to make a bad situation worse. BTW, I can't get into recovery but I can get into ODIN mode.
Any help is greatly appreciated!!
Ok, using ODIN, I was able to get a stock ROM onto the phone and get the thing booted. So essentially I'm back to square 1 and I still didn't figure out what I did wrong the first time around. Bummer Eh?
scheirere said:
Ok, using ODIN, I was able to get a stock ROM onto the phone and get the thing booted. So essentially I'm back to square 1 and I still didn't figure out what I did wrong the first time around. Bummer Eh?
Click to expand...
Click to collapse
Yea, I soft bricked once and was able to boot into recovery by holding volume up, power, and home at the same time while the phone was off. I thanked my lucky stars I had a nandroid backup. I would make sure you unlocked the boot loader properly. When I first started rooting YouTube was great for instructions. I would post a link to a YouTube video but it won't allow me until I have ten posts, I swear some of these rules are retarded. Anyway search in YouTube having visual and audio guide helps a lot. good luck!
Hey guys and guyettes!
I somehow managed to put my One mini into a boot loop!
None of the options on the fastboot menu do anything other than turn the screen black and then go back to the boot menu... If anyone has any ideas on how to fix this it would be greatly appreciated!
And before anyone asks for whatever reason, no it is not rooted!
Things I've tried:
- Using ADB and SDK to unbrick it
- Hard resets, recoveries and factory resets
The last thing I did before it started the loop was install King of Thieves (a game).
Before the loop it ran out of power so I plugged it in and it went to the menu like it usually does then it just started too loop!
Thanks for any suggestions
~James
I'm currently chasing the same thing on my wife's phone. This is the 2nd time this has happened. (the first time was replaced by factory warranty). The ROM and everything is completely stock so I'm trying to unlock the bootloader using the HTC dev tools and I can flash the Unlock_code.bin but the screen never prompts me to actually unlock it... I'm hoping someone has a tried and true way of fixing this.
iceterminal said:
I'm currently chasing the same thing on my wife's phone. This is the 2nd time this has happened. (the first time was replaced by factory warranty). The ROM and everything is completely stock so I'm trying to unlock the bootloader using the HTC dev tools and I can flash the Unlock_code.bin but the screen never prompts me to actually unlock it... I'm hoping someone has a tried and true way of fixing this.
Click to expand...
Click to collapse
I have the bootloop menu which suddenly appeared for no apparent reason seeing as I haven't rooted the phone. It's an annoying problem that I see many people have except most people I see haven't quite got the same problem as myself...
Same issue...
I have a customer's phone, having the same issue. The customer brought it to me like this and I thought I would try to repair it. He is mentally challenged and so I really wanted to help him. But it's doing exactly what the OP stated. I even tried the same things before I found this thread. Unlocked the bootloader (but it did not actually bring up the screen to unlock the bootloader, the WinDroid Universal Toolkit simply stated it was unlocked). And yes, I did acquire the unlock.bin or whatever it was called.
So the phone will do nothing but reboot. I'm not sure how it got this way or if it can be fixed. That is why I am here.
Any ideas?
Thanks!
Da
PAinguINx said:
So the phone will do nothing but reboot. I'm not sure how it got this way or if it can be fixed. That is why I am here.
Any ideas?
Da
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showpost.php?p=57727218&postcount=1365
probably this is the case
THIS IS NOW RESOLVED. PLEASE DO NOT CONTINUE TO POST ON MY THREAD. YOUR CIRCUMSTANCES WILL NOT BE THE SAME AS MINE NORE ARE THEY LIKLEY TO RESOLVE ISSUES YOU HAVE, AS MINE WAS CAUSED BY A VERY SPECIFIC PROBLEM. START YOUR OWN THREADS DONT HIJACK MINE
Good morning XDA Devolopers,
I have used this site for many a year now but today had to sign up to get some help.
I purchased my SM-920F from Ebay, and low and behold, it had been blocked here in the UK, ever the optimist i looked about online and indeed there are several options online, including some services for remote unlocking, i decided it was worth a shot and ordered it, only from there on it goes from bad to worse.
After the unlock i was constantly greeted with Security Errors and Warning, i contacted the company who unlocked it, and was told to re-flash the rom with the same baseband version, after alot of hunting i found a rom from SAM Mobile and away i went, flashed and all seemed to go well i waited and waited, phone stuck on the boot screen. Galaxy S6, powered by Android...
I returned to the unlocking company asking for advice, only to be called a liar and they would never suggest i reflash the rom or firmware.
So now im stuck with a brick, ive tryed all i can think off and all i can research and i just cant make any progress. I did note after the unlock SuperSU had been installed on my phone (i wasnt made aware the unlock required them to root my phone, they tripped knox in the process).
I have a SM-920F origonally on O2 UK, i have tryed flashing there rom with no joy.
Im desperate to have this phone orking, even if its just for calls, my wife is currently at the hospital with our son whos fighting for his life against cancer, and all i get is abuse from here, i dont get paid till the 1st of the month so a new phone is out of the question at present. The unlocking company i used are tools, and to think iw as mighty impressed at the time.
I do have SOME cash, if theres a pro out there who wants to make a few bucks and can remote connect to me to help me solve this it would be much appreciated, i am just now stuck and desperate and badly need the help of the community.
Galaxy S6 920F
64GB Blue
Android 5.1.1
(Rooted by network unlockers)
WIndows 7 Ultimate - Odin (I have just about all of them these days)
Avalable Roms on my Machine (ALL O2 Roms and some other international variants for france and germany)
If anyone out there can help me please, if i could get on my knees and beg i would, im so desperate now to be able to just recieve calls from my wife and the hospital at this **** time for us.
Please please please someone somewhere must be able to help me out
Thanks
M
shir199m said:
Good morning XDA Devolopers,
I have used this site for many a year now but today had to sign up to get some help.
I purchased my SM-920F from Ebay, and low and behold, it had been blocked here in the UK, ever the optimist i looked about online and indeed there are several options online, including some services for remote unlocking, i decided it was worth a shot and ordered it, only from there on it goes from bad to worse.
After the unlock i was constantly greeted with Security Errors and Warning, i contacted the company who unlocked it, and was told to re-flash the rom with the same baseband version, after alot of hunting i found a rom from SAM Mobile and away i went, flashed and all seemed to go well i waited and waited, phone stuck on the boot screen. Galaxy S6, powered by Android...
I returned to the unlocking company asking for advice, only to be called a liar and they would never suggest i reflash the rom or firmware.
So now im stuck with a brick, ive tryed all i can think off and all i can research and i just cant make any progress. I did note after the unlock SuperSU had been installed on my phone (i wasnt made aware the unlock required them to root my phone, they tripped knox in the process).
I have a SM-920F origonally on O2 UK, i have tryed flashing there rom with no joy.
Im desperate to have this phone orking, even if its just for calls, my wife is currently at the hospital with our son whos fighting for his life against cancer, and all i get is abuse from here, i dont get paid till the 1st of the month so a new phone is out of the question at present. The unlocking company i used are tools, and to think iw as mighty impressed at the time.
I do have SOME cash, if theres a pro out there who wants to make a few bucks and can remote connect to me to help me solve this it would be much appreciated, i am just now stuck and desperate and badly need the help of the community.
Galaxy S6 920F
64GB Blue
Android 5.1.1
(Rooted by network unlockers)
WIndows 7 Ultimate - Odin (I have just about all of them these days)
Avalable Roms on my Machine (ALL O2 Roms and some other international variants for france and germany)
If anyone out there can help me please, if i could get on my knees and beg i would, im so desperate now to be able to just recieve calls from my wife and the hospital at this **** time for us.
Please please please someone somewhere must be able to help me out
Thanks
M
Click to expand...
Click to collapse
Turn off your phone, and then turn it on pressing and holding Volume Up, Home, and Power button at the same time until you see a warning. Then press Volume Up to continue, and navigate using volume keys and select wipe cache/factory reset with the Home button, then reboot.
Please note that by doing this all your data will be lost.
Uzair40 said:
Turn off your phone, and then turn it on pressing and holding Volume Up, Home, and Power button at the same time until you see a warning. Then press Volume Up to continue, and navigate using volume keys and select wipe cache/factory reset with the Home button, then reboot.
Please note that by doing this all your data will be lost.
Click to expand...
Click to collapse
Remains Stubbornly stuck on the boot screen.
Samsung Galaxy S6 - Powered By Android.
shir199m said:
Remains Stubbornly stuck on the boot screen.
Samsung Galaxy S6 - Powered By Android.
Click to expand...
Click to collapse
Donwload Phone INFO Samsung, and post screenshots.
Uzair40 said:
Donwload Phone INFO Samsung, and post screenshots.
Click to expand...
Click to collapse
Cant install any apps, phone dont boot.....
shir199m said:
Cant install any apps, phone dont boot.....
Click to expand...
Click to collapse
Try to update via Smart Switch
Uzair40 said:
Try to update via Smart Switch
Click to expand...
Click to collapse
Smart switch flashes with no issues, phone will not boot.
Even after recovery menu > Factory Data Reset & recovery menu > Format Cache
shir199m said:
Smart switch flashes with no issues, phone will not boot.
Even after recovery menu > Factory Data Reset & recovery menu > Format Cache
Click to expand...
Click to collapse
Install TWRP via Odin, and then do a factory reset
Uzair40 said:
Install TWRP via Odin, and then do a factory reset
Click to expand...
Click to collapse
Can you please provide me with a link to a guide of some kind, i dont mind doing that But id like to understand the process before i start it, if you can point me to a decent ish guide (and im aware of the risks TWRP may present)
Many thanks
shir199m said:
Can you please provide me with a link to a guide of some kind, i dont mind doing that But id like to understand the process before i start it, if you can point me to a decent ish guide (and im aware of the risks TWRP may present)
Many thanks
Click to expand...
Click to collapse
Thanks for ya info.
Having installed TWRP i noticed something very intresting, TWRP reports no operating system is installed.
Ive taken a leap of faith and using ODIN am now flashing the Stock 5.1.1 ROM.
Will report back in a few mins.
Okay so TWRP is installed, it reported no operating system.
I reflashed the Stock rom, all went well as expected, phone still refuses to boot.
I have reflashed TWRP and completed a factory reset. Again no dice, still wont boot.
Any further help would be much appreciated.
Thanks
M
shir199m said:
Okay so TWRP is installed, it reported no operating system.
I reflashed the Stock rom, all went well as expected, phone still refuses to boot.
I have reflashed TWRP and completed a factory reset. Again no dice, still wont boot.
Any further help would be much appreciated.
Thanks
M
Click to expand...
Click to collapse
Install a custom ROM.
Uzair40 said:
Install a custom ROM.
Click to expand...
Click to collapse
Yeah now were where i didnt want to be.
Okay ill try that, is there a particular rom you would recommend?
Ill take anything so long as i can make calls, my wifes just walked in the door and gone of like a fricking nuclear warhead
Oh dear god you should hear this haha.
Ill look on google for roms, but if you have any suggestion on a rom ill defer to you
shir199m said:
Yeah now were where i didnt want to be.
Okay ill try that, is there a particular rom you would recommend?
Ill take anything so long as i can make calls, my wifes just walked in the door and gone of like a fricking nuclear warhead
Oh dear god you should hear this haha.
Ill look on google for roms, but if you have any suggestion on a rom ill defer to you
Click to expand...
Click to collapse
OH THAN JESUS CHRIST.
I am not a god believing man, but i am very very very greatfull to the chap who has helped me with this.
I will update the OP Later, with full instructions of how ive done it... (Like once ive confirmed it all works)
shir199m said:
OH THAN JESUS CHRIST.
I am not a god believing man, but i am very very very greatfull to the chap who has helped me with this.
I will update the OP Later, with full instructions of how ive done it... (Like once ive confirmed it all works)
Click to expand...
Click to collapse
There is a ROM called AllianceROM, I've read that it's on of the best for the G920F.
Okay so as promised.
1. Flash Stock 5.1.1 ROM (Phone will not boot after)
2. Flash TWRP with ODIN
3: Reboot into TWRP and mount filesystem via MPT (i had to disable then enable it for my computer to detect it)
4: Copy ROM to phone (As a ZIP)
5: Using TWRP install ZIP
6: Follow Instructions
7: Dalvik / Cache Clear (it asks after the rom is installed)
8: Reboot
9: Wait
10: Wait Some More
11: TADA
Phone has booted and connected to the network, the AllianceROM suggested above will work in very much the same way! same process.
Thats all i did. After a week of gueswork i want to thank the chap who provide me some guidance both here and via PM
Phone is now running and working, i wish i could have stock rom but you cant have it all.
On a side note if you choose to use IMEI Gurus to unlock your phone, i highly suggest you dont, there after sales support are shocking, and they refunded my money even though its not what i wanted, had the provided the help i found here id not have been so stressy with them. There service does work, but they will root your device (which they dont mention in there sales pitch they will trip knox (again not mentioned) and once done you cant actually factory reset the phone with any method. ANd youll be here reading this.
Yes there services work, but guys please make your own informed decisions about there service, would i buy again from them? i doubt it, but needs must and all that.
THanks everyone
This is now resolved. Please do not continue to post on my thread. Your circumstances will not be the same as mine nore are they likley to resolve issues you have, as mine was caused by a very specific problem. Start your own threads dont hijack mine
I flashed the Google assistant some time ago and everything was fine but yesterday I decided to do some minor build prop edits and accidentally bricked my phone. Now that's fine because they have multiple ways of unbricking the T-Mobile LG v20. But when I tried to unbricking it using LGup nothing works because it registers my phone as a pixel and now my phone can't be restored. So take it from me..Don't do it!!! It isn't worth the loss. I have a brick now. An official lg v20 brick. Sigh
EDIT:
IM EDITING THIS TO ADD WHAT I DID.
Here's the story
I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.
Do you not have TWRP you can reboot into, and re-flash a backup or new ROM?
CharlzO_2000 said:
Do you not have TWRP you can reboot into, and re-flash a backup or new ROM?
Click to expand...
Click to collapse
Nope, the only thing my phone does it boot into the mode where it says "Firmware update" mode. I really think I destroyed my phone.
remix435 said:
Nope, the only thing my phone does it boot into the mode where it says "Firmware update" mode. I really think I destroyed my phone.
Click to expand...
Click to collapse
Take it to the store and tell them it happend when the phone was updating.
slayerh4x said:
Take it to the store and tell them it happend when the phone was updating.
Click to expand...
Click to collapse
That's actually a pretty good idea. I'm going as soon as TMobile opens.
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Leonarddale said:
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Click to expand...
Click to collapse
This.
remix435 said:
I flashed the Google assistant some time ago and everything was fine but yesterday I decided to do some minor build prop edits and accidentally bricked my phone. Now that's fine because they have multiple ways of unbricking the T-Mobile LG v20. But when I tried to unbricking it using LGup nothing works because it registers my phone as a pixel and now my phone can't be restored. So take it from me..Don't do it!!! It isn't worth the loss. I have a brick now. An official lg v20 brick. Sigh*
Click to expand...
Click to collapse
That is very strange, I recently bricked my phone to the point where I didn't have a system at all on it. When you boot to firmware update mode (power + volume up) and pluged it in LGUp recognized it instantly. You have the correct DLL for your device right?
shadowxaero said:
That is very strange, I recently bricked my phone to the point where I didn't have a system at all on it. When you boot to firmware update mode (power + volume up) and pluged it in LGUp recognized it instantly. You have the correct DLL for your device right?
Click to expand...
Click to collapse
My issue was that when I flashed the assistant mod it turned my device name into " google pixel" so when I hooked it up to lgup it read it as a pixel and failed the restore every time. That was the issue I couldnt change the name of my devixe back to the v20.
Leonarddale said:
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Click to expand...
Click to collapse
I disnt have anything on my phone. No twrp and I couldnt install it. The assistant mod changed my device name to PIXEL and when id connect it to the pc it read as a pixel and failed every update I LG V20 I pushed to it..that was a new type of brick lol. But I told t mobile that if I what happened and I got another one.
These old assistant mods would be taken down. The only thing needed to enable it without spoofing a phone as a Pixel is adding "ro.opa.eligible_device=true" to build.prop, and the Google app updated via Play Store.
remix435 said:
My issue was that when I flashed the assistant mod it turned my device name into " google pixel" so when I hooked it up to lgup it read it as a pixel and failed the restore every time. That was the issue I couldnt change the name of my devixe back to the v20.
Click to expand...
Click to collapse
That's the thing my phone didn't have a system on it at all and LGUp read it as what it was. When you on the firmware screen it should read based on hardware ID right? Have you tried using LG bridge? Are you on the T-Mobile variant?
This is a contributing factor in why these companies lock bootloaders. People do stupid things because they don't know what they're doing and then others encourage them to just return it and get a new one and lie. Not cool at all. How about don't root your phone if you don't know what you're doing.
markbencze said:
This is a contributing factor in why these companies lock bootloaders. People do stupid things because they don't know what they're doing and then others encourage them to just return it and get a new one and lie. Not cool at all. How about don't root your phone if you don't know what you're doing.
Click to expand...
Click to collapse
WTF! With your logic no one would learn anything.
My phone was rooted just fine. How was I suppose to know that after I flashed the stock build prop my phone was going to stay as a pixel device?? That wasn't stupid of me that was trial and error. Something stupid is if I did it again. No one specified that my phone would stay as a pixel device, go read the instructions and tell me where it says that. Also, I have "Jump on demand" so I used one of my jumps to get a brand new phone..So I paid a price for it. It wasn't just "me lying and getting a free phone" I still paid for it I paid for my mistake and Yes initially I lied but still paid and am still paying for this phone. Plus I have an s7 edge and a Huawei honor note 8 all rooted and have never ran into any issues. Why?? Because I never did what people instructions told me not to do. I always follow instructions. I've been rooting phones since I was a milk drinker all the way back to the G1 days. I'm very careful but if instructions don't cover all the basis then what?? PEOPLE, including me should continue to root and try new things. But you can't blame them if YOU(not you in particular but in general) as a developer make something and can't catch all the bugs(it isn't The developers/modders fault either)..Modding is a giant community of trial and error. The only people at fault are idiots who don't read and do some ****. Other than that we are all out here finding our way with these new devices. So yes, I have a new v20 that I paid for with MY "Jump on demand" plan that is now rooted and unlocked. Now am I going to use the Google assistant mod again?? No, because that would be stupid of me. Now get off my post.
I was just warning people so they wouldn't make the same mistake as me.
Whats the stupid part is how you managed to erase TWRP and lose access to fastboot on your device. Not that your changed something in build.prop. His logic is not flawed, whatever you did to lose access to the two essential parts of having a rooted phone is the flaw here.
Also simply doing build.prop edits should not make you lose access to TWRP nor being able to access fastboot - or did you relock your bootloader?
twistedvip said:
Whats the stupid part is how you managed to erase TWRP and lose access to fastboot on your device. Not that your changed something in build.prop. His logic is not flawed, whatever you did to lose access to the two essential parts of having a rooted phone is the flaw here.
Also simply doing build.prop edits should not make you lose access to TWRP nor being able to access fastboot - or did you relock your bootloader?
Click to expand...
Click to collapse
In stead of assuming what happened with my device how about y'all ask me the details first. But coming off the bat assuming that I just did foolishness is asinine.
I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.
So once again where's the stupidity on my part when I didn't know that my phone was still going to be labeled a a pixel after a factory reset? Please, both of you have several seats in the back.
All I'm doing is warning people about what could possibly happen. Y'all can miss me with your unnecessary opinions and comments.
No I appreciate you wanting to warn the community, but you most certainly did not post that story. You posted saying you got bricked from doing edits to your build.prop and then because of using a Google assitant mod you are hard bricked. Post that entire story as a warning because even having your phone appear as a Pixel won't do any harm - but flashing a .kdz and having it fail midway may indeed cause harm. Lack of details causes much misinformation to spread around quickly
twistedvip said:
No I appreciate you wanting to warn the community, but you most certainly did not post that story. You posted saying you got bricked from doing edits to your build.prop and then because of using a Google assitant mod you are hard bricked. Post that entire story as a warning because even having your phone appear as a Pixel won't do any harm - but flashing a .kdz and having it fail midway may indeed cause harm. Lack of details causes much misinformation to spread around quickly
Click to expand...
Click to collapse
My bad I'll edit it. And apologies for the response tone.
It's called taking responsibility. You had a phone with root and did something stupid. Instead of taking responsibility you lie and tell them the phone is defective. That is 100% your fault. I bet it worked fine before you started messing with it. Whatever man I'm gonna let this be but you can bet that when these companies look at the supposed drfrctive returned phones and see they have been tamperred with and that people are being dishonest to get a new phone when they're the sole reason the phone stopped working, eventually they will all say screw it and just lock everything down.
Hopefully you learned from this.
markbencze said:
It's called taking responsibility. You had a phone with root and did something stupid. Instead of taking responsibility you lie and tell them the phone is defective. That is 100% your fault. I bet it worked fine before you started messing with it. Whatever man I'm gonna let this be but you can bet that when these companies look at the supposed drfrctive returned phones and see they have been tamperred with and that people are being dishonest to get a new phone when they're the sole reason the phone stopped working, eventually they will all say screw it and just lock everything down.
Hopefully you learned from this.
Click to expand...
Click to collapse
Actually the phone had a few random rebootsa and use to freeze on stock. I decided to keep it because of the note 7 fiasco and I was too frustrated and pissed to return it and then they ran out. So this was well over due. But once again you know nothing Jon snow. And yes I did lie but this device already had issues. Soooo???