Related
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. You MUST use this interim CWM version for the moment, as the others do not work properly. Some things like USB mount dont work in this interim version, but the important functions like wipe and flash, backup and restore, and restart do work. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
bump... i see US users still asking.
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Worked great for me
Sent from my HTC VLE_U using xda premium
So if we root and flash a custom ROM is there any way to get the phone back to factory state, and get rid of the *TAMPERED* and *UNLOCKED* notification??
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
cyberchuck9000 said:
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
Click to expand...
Click to collapse
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
nickmv said:
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Click to expand...
Click to collapse
+1
androidcues said:
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
Click to expand...
Click to collapse
If you need to perform a hard reset on the One S, you hold down the power button for about 7-10 secs.
First of all, thanks for this thread...I used the HTC One S All in one tool kit to unlock my phone, unfortunately I miss understood one of the directions(#5) and stopped using the tool kit and followed another thread, much to my surprise, my bootloader is unlocked, hooray My question is, how do I get back to the original state if that is possible? The reason I ask, is I would like to go back and do it correctly...I used better terminal emulator to see if I had root, but all I got was the $ sign instead of the # sign So I would like to start over...
Thanks in advance for the help
I'm honestly not sure what the procedure is for relocking an HTC bootloader. Perhaps do some Google research on some of the latest models, and I bet you'll find something.
That being said, once you unlock the bootloader a single time, the best you can do is go to **RELOCKED** state. You'll never get back **LOCKED**. Once it's gone it's gone. I'm curious about the **TAMPERED** message though. That's an ugly word.
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
suhailtheboss said:
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
Click to expand...
Click to collapse
Uh oh that doesn't sound good
Sent from my HTC VLE_U using xda premium
yeah, tried reflashing both CWM & stock recovery. phone still boots to CWM everytime.
Luckily i can still access the phone via ADB, (while in recovery) so i'm sure i'll be able to sort it out. just need to take a fresh crack at it tomorrow. gonna switch back to my galaxy nexus tonight. (oh wait, i dont have any other phones that use microsim)
haha.
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
nickmv said:
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. Some things like USB mount dont work, but the important functions like wipe and flash and restart do. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart. I cant speak for the non-interim solutions, but from what I can gather, they are problematic, so avoid them for now.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
Click to expand...
Click to collapse
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Thongvilay said:
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Click to expand...
Click to collapse
That step is only if you want to flash ROMs, or need to wipe cache, dalvik, etc. CWM is used for flashing and recovery/backup purposes. If you're not using ROMs yet, then you have no need for it.
nickmv said:
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
Click to expand...
Click to collapse
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
suhailtheboss said:
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
Click to expand...
Click to collapse
Wow, I have no idea dude. That sounds kinda crazy. Hopefully all will be well in the future and you won't come across it again.
the only variable i can think of is that i did have the phone about a week before launch. HTC mailed it to me directly.
I thought maybe that had somethign to do with it, but as far as i can tell the phone was the final shipping version.
I sent you a PM, trying to find a solution.
So I feel like I am pretty experienced when it comes to the whole ROM/Root scene, I've had the OneXL, Galaxy S3, and Nexus 4.. but I've always had a difficult time with the One XL and ROMs... I always seem to run into major problems.. Right now I can only access the fastboot area of the phone, it will not go into recovery (i have even tried reflashing recovery but no luck) and no matter what, it bootloops constantly. I had ViperXL running fine on the device but I tried to install ElementalX kernel for the first time and now the phone is Kaput.. Any ideas??? Could this be a semi-brick?
did you specifically try to go into fastboot and fastboot flash recovery recovery.img
?
because this phone is pretty much either "it's reading qsb mode in device manager bricked" or "i don't know what i'm doing and cannot figure out what to do next NOT BRICKED" (i'm not rippin on you; if you pull up my history, it even happened to me once and i had to make a baww thread for someone to help me figure it out. turns out, don't click factory reset in bootloader.) there is one other way, but it involves acceptin the OTA with your CID having been changed
wdkingery said:
did you specifically try to go into fastboot and fastboot flash recovery recovery.img
?
because this phone is pretty much either "it's reading qsb mode in device manager bricked" or "i don't know what i'm doing and cannot figure out what to do next NOT BRICKED" (i'm not rippin on you; if you pull up my history, it even happened to me once and i had to make a baww thread for someone to help me figure it out. turns out, don't click factory reset in bootloader.) there is one other way, but it involves acceptin the OTA with your CID having been changed
Click to expand...
Click to collapse
Actually, I was just about to post that I fixed it!! I relocked the bootloader, then unlocked again(i thought maybe it would wipe all my data for me, and it did!!) So I then reflashed the recovery and got into it, reformatted the USB mount in windows with FAT32 and then placed a new ROM onto the device. And it booted right on up!
By the way, this ind of thing happened to me too before... but I never had to do the bootloader thing.. Thanks for the input though!
Hello, I have bricked my lg g2, I started to try to unlock the bootloader on my phone so I could flash custom roms and such. Well, being the dumb idiot like I am, I used the wrong unlocker for the wrong variant of the G2. It was stuck in fastboot mode. As I was about to get out of the brick that I had, I deleted aboot. This was the real mistake. It wouldent let me put on the aboot.bin back into the phone because of some directory problem on my computer... (ended up being my fault... AGAIN...) well, now, It doesnt even boot anymore... It vibrates as if it would turn on, then just goes to an extremely dark screen (looks like it's still off...) I tried to put aboot.bin back into the phone via command prompt, I figured out how to find the directory of aboot.bin, but it just waits for the phone. If there is any way I can save this phone, I would love to. I am inexperienced in rooting androids and flashing and this whole root thing was a mistake :silly:
Thanks
- soups
delicioussoups said:
Hello, I have bricked my lg g2, I started to try to unlock the bootloader on my phone so I could flash custom roms and such. Well, being the dumb idiot like I am, I used the wrong unlocker for the wrong variant of the G2. It was stuck in fastboot mode. As I was about to get out of the brick that I had, I deleted aboot. This was the real mistake. It wouldent let me put on the aboot.bin back into the phone because of some directory problem on my computer... (ended up being my fault... AGAIN...) well, now, It doesnt even boot anymore... It vibrates as if it would turn on, then just goes to an extremely dark screen (looks like it's still off...) I tried to put aboot.bin back into the phone via command prompt, I figured out how to find the directory of aboot.bin, but it just waits for the phone. If there is any way I can save this phone, I would love to. I am inexperienced in rooting androids and flashing and this whole root thing was a mistake :silly:
Thanks
- soups
Click to expand...
Click to collapse
doubtful it can be fixed if it wont boot, but you can try asking your question in the g2 q&a. maybe some expert in your device forum can help.
Hey,are you able to boot into boot loader...if you can just lock the boot locker back and type the reboot command from PC itself
arunbiju969 said:
Hey,are you able to boot into boot loader...if you can just lock the boot locker back and type the reboot command from PC itself
Click to expand...
Click to collapse
sorry, but that is actually the worst possible thing you could do in this situation. locking the bl back will prevent you from flashing any further software if needed or possible, to fix this issue.
the g2 bl isnt unlocked as you suggest. it is bypassed with an exploit and not really unlocked.
bweN diorD said:
sorry, but that is actually the worst possible thing you could do in this situation. locking the bl back will prevent you from flashing any further software if needed or possible, to fix this issue.
the g2 bl isnt unlocked as you suggest. it is bypassed with an exploit and not really unlocked.
Click to expand...
Click to collapse
Ok, is there a command that I can use to boot back up?
delicioussoups said:
Ok, is there a command that I can use to boot back up?
Click to expand...
Click to collapse
its been a long time since i used my g2, thats why i suggested you ask in the g2 help forum in post #2.
please dont take my correction of the other guys post as there being a fix for yours. i really believe there is not, but his advice was blatantly wrong, so i had to correct it.
i think aboot is download mode/fastboot (if you have that). so deleting that when the phone cant boot is very bad. if the phone was booting, and rooted, it would be easy to put on a new aboot with dd code.
bweN diorD said:
its been a long time since i used my g2, thats why i suggested you ask in the g2 help forum in post #2.
please dont take my correction of the other guys post as there being a fix for yours. i really believe there is not, but his advice was blatantly wrong, so i had to correct it.
i think aboot is download mode/fastboot (if you have that). so deleting that when the phone cant boot is very bad. if the phone was booting, and rooted, it would be easy to put on a new aboot with dd code.
Click to expand...
Click to collapse
Alright thank you!
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???
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. :/