Related
Hi Im a complete Noob for doinf this :silly:
Coming from Htc One there was a method posted on the Htc one forums to get the bootloader locked.
http://forum.xda-developers.com/showthread.php?t=2475914
And stupid me without thinking I used the command echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
to reset the unlocked to lock stats.
Well now the phone doesnt even turn on no booloader no recovery nothing, pc detects it as an unkown device but I dont know what to do with it.
is there anyway possible to bring this brick back to life or do i have send it back to google?
Any suggestions or Advice is welcome.
Thanks
If it doesn't turn on I think you're hosed. You messed up one the partitions running the commands you did Please read the pinned (stickies) threads on the general forum before you do anything on your new device.
You wiped an important partition of the phone, and now it won't boot. Looks like you are out of luck. You can probably call Google and tell them your phone won't turn on, but technically that would be lying because you broke it without reading.
If you do get a replacement, and want to unlock the bootloader just get fastboot and type 'fastboot oem unlock'. That's it. This is a Nexus.
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
xXxG0dzRAgexXx said:
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
Click to expand...
Click to collapse
I hope I do get a replacement , Im in the Uk so i cant get in contact with Google support till Monday now. I was stupid for doing that and I have learned a valuable lesson.
That's what happens when you do not read. Good luck.
xXxG0dzRAgexXx said:
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
Click to expand...
Click to collapse
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
unvaluablespace said:
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
Click to expand...
Click to collapse
iPhone's are pretty much impossible to hard brick. Was in the jailbreak scene for 2 and a half years, and there is no way to hard brick one. Very early on it was possible, but not anymore. Android devices are pretty hard to brick usually. Just make sure you follow a guide for your device and all should be well. Only risky thing really is flashing the wrong firmware or radio on a device. Flashing roms, mods, or wiping the entire device is always fixable (not important partitions though, but that's only possible via command terminal like in this case). I was at first scared with my HTC One since it was my first android device, but realized as long as you know what your doing all should go well.
unvaluablespace said:
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
Click to expand...
Click to collapse
Don't be too scared. Honestly bricking a nexus device is quite hard as long you are somewhat literate. With most situations (if you have access to the bootloader) you have the option of flashing the factory images which will get your phone up and running 95% of the time. Basically if you can access the bootloader, there is nothing to panic or worry about.
The only reason this guy bricked his phone is because he thought it was a good idea to root his nexus 5 using a guide that teaches you how to unlock the bootloader on an HTC One.
Just make sure you read a bit, understand what you are doing, and don't blindly follow random instructions that you find on the interwebz. If you follow that advice i doubt you will have any problems.
Sent using xda-developers app
uronfire said:
Hi Im a complete Noob for doinf this :silly:
Coming from Htc One there was a method posted on the Htc one forums to get the bootloader locked.
http://forum.xda-developers.com/showthread.php?t=2475914
And stupid me without thinking I used the command echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
to reset the unlocked to lock stats.
Well now the phone doesnt even turn on no booloader no recovery nothing, pc detects it as an unkown device but I dont know what to do with it.
is there anyway possible to bring this brick back to life or do i have send it back to google?
Any suggestions or Advice is welcome.
Thanks
Click to expand...
Click to collapse
Still having issues? I've got a couple of ideas you could try. I managed to fix my nexus after I completely screwed up the bootloader, willing to share how I fixed it
daniel.kusy said:
Still having issues? I've got a couple of ideas you could try. I managed to fix my nexus after I completely screwed up the bootloader, willing to share how I fixed it
Click to expand...
Click to collapse
How did you manage to fix yours? Mine's still bricked but can only get access to the bootloader. Have tried every option of flashing factory but still no luck.
How do you brick a Nexus?
I wish I could feel pity but man....
Tell them it won't turn on. Send it back I'm sure they won't know. Hope they don't at least. Better than keeping a paperweight.
sent from my Nexus 5
jphilippon said:
How do you brick a Nexus?
I wish I could feel pity but man....
Tell them it won't turn on. Send it back I'm sure they won't know. Hope they don't at least. Better than keeping a paperweight.
sent from my Nexus 5
Click to expand...
Click to collapse
I used ChainFires auto root and it quite simply did not work and bricked my phone. Nothing else to it… it just bricked my N5. No interruptions, all correct drivers installed. Now I'm stuck with a phone displaying unlocked boot loader (which I can lock temporarily using fast boot command.) but when the device restarts into fast boot it's back saying unlocked. Nightmare really.
Meakii said:
I used ChainFires auto root and it quite simply did not work and bricked my phone. Nothing else to it… it just bricked my N5. No interruptions, all correct drivers installed. Now I'm stuck with a phone displaying unlocked boot loader (which I can lock temporarily using fast boot command.) but when the device restarts into fast boot it's back saying unlocked. Nightmare really.
Click to expand...
Click to collapse
there is a person in the franco's thread who even corrupted the bootloader he managed to recover using some lg flsh tool something like kdz
it was some kind of methord used to unbrick nexus 4
Meakii said:
How did you manage to fix yours? Mine's still bricked but can only get access to the bootloader. Have tried every option of flashing factory but still no luck.
Click to expand...
Click to collapse
have you tried the flash-all.bat (factory image using command prompt from the sdk/platform-tools folder )?
Sent from my Nexus 5 using Tapatalk
floxrin said:
have you tried the flash-all.bat (factory image using command prompt from the sdk/platform-tools folder )?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yea mate. No luck.
Meakii said:
Yea mate. No luck.
Click to expand...
Click to collapse
If you can get into bootloader does fastboot work? If you can get into the bootloader virtually anything can be fixed. What happens when you click the flash all.bat file?
Try LG download mode
Sent from my Nexus 5 using Tapatalk
daniel.kusy said:
If you can get into bootloader does fastboot work? If you can get into the bootloader virtually anything can be fixed. What happens when you click the flash all.bat file?
Click to expand...
Click to collapse
See the attached. I can't do anything. Every attempt to write anything to the internal SD fails. I wish it could be fixed but have tried everything. Worst part is even after fastboot oem lock cmd when it restarts it's unlocked again. Meaning when I return it warranty will probably be void.
This guy has the same problem. http://forum.xda-developers.com/showthread.php?p=315800
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
There is a way. I posted in previous forum.
Use fastboot
Fastboot wipe cache
Fastboot wipe user data
Try this if not pm me and I will help you out one on one
That should fix your issue
Sent from my XT1080 using xda app-developers app
phositadc said:
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
Click to expand...
Click to collapse
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
Ha...well there is that But what fun would that be?
The sad part is that the manufacturers could care less about giving us an unlocked bootloader. Android is a great ecosystem to play with and learn with and improve with. It's the carriers that are so paranoid about taking any tiny dent in their enormous profits that want to keep us locked out. So shame on them.
But, to be fair, I know the risks of the world we live in and this is my first brick in four Android phones, so I'm fine with it.
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
My point was merely that it's somewhat ironic that, by trying to prevent bricks by locking bootloaders, Verizon actually causes some bricks that would be avoided with an unlocked bootloader.
Not saying anything about whether what he was doing is right or wrong, or whether Verizon prevents more bricks than it causes.
Sent from my Nexus 7
Edit: but you've got to wonder. Are you more likely to brick using one of these crazy complicated methods we have to use to get around Verizon security? Or using fastboot OEM unlock + flash superuser. I bet per hundred rooted phones, less Nexus's (and other unlockable phones) are bricked than phones that are tightly locked down. Pure speculation of course.
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
It sounds like you're actually stuck partially on JB, partially on KK, hence why you're bootlooping. I had a very similar issue when I tried to install the KK update through update.zip .......... after a couple hours, I finally got it back up and running.
My method - use the Method 2 Manual flash steps I posted in Dev section here - http://forum.xda-developers.com/showthread.php?t=2580060
Let me know if it works. I had problems at first, but that should cover it. Getting system to flash was actually the hardest part
Hi all, so i brought my phone in late December. I have been using it every day since then. And i have not done a single factory reset, even though i download new apps every day, download files etc. Basicly somewhat heavy usage. So last week i downloaded Towelroot, i didnt believe it will work to be honest, but apparently it did. So i had a rooted nexus 5, and i did not back up my stock rom. First thing i did i brought an app called SoftKeyZ root, that allows you to change the look of software buttons. Beeing on the hype of getting root, i didnt save my stock rom and i changed the buttons. I suppose i wont be getting OTA updates now? And since last week my google drive doesn't work any more, it doesnt give any upload speed at all. And my phone battery is draining super fast, the phone lags occasionally, and shutters or freezes completely for few seconds. Can this be because i rooted it? And will factory reset do any good? Since i suppose it will not remove root. Will it reset my buttons though? And how do i unroot my device easily and get my stock European rom back? Is there no app like Towelroot-unroot that unroots the device just by clicking one button? I am very worried now so please explain very detailed and what would you do. I do not have the money to fix my phone if i brick it or something. I have changed roms before but for some reason ibdo not want to fiddle with this phone because literally this is the most expensive thing i have had. Awaiting your replies!
So you've done nothing and you're all out of ideas?
Go here and read. You need it more than you know.
http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
I did read a lot, i just want to know what is appropriate for my situation, most unrootings require flahsing backup rom which i do not have
nikssims said:
I did read a lot, i just want to know what is appropriate for my situation, most unrootings require flahsing backup rom which i do not have
Click to expand...
Click to collapse
All the info you need was posted in the link posted above
Sent from my Nexus 5 using Tapatalk
Thanks for the link! Looks pretty easy but is that really the only option? No easier way without flashing? I ruinded S1 by flashing and deleting wrong cache. That is why i really dont want to do that.
Also the problems i face, could they be because of root?
And if i decide not to unroot, will i get OTA updates despite what i already have done?
nikssims said:
Thanks for the link! Looks pretty easy but is that really the only option? No easier way without flashing? I ruinded S1 by flashing and deleting wrong cache. That is why i really dont want to do that.
Also the problems i face, could they be because of root?
And if i decide not to unroot, will i get OTA updates despite what i already have done?
Click to expand...
Click to collapse
You can get OTA if rooted, so yes you can get OTA without root.
Follow the guide. Flashing is the best way. The process wont let you "delete wrong cache". It's the official, google process.
Greetings. I found myself in a situation of being stuck at Alcatel splash screen after rebooting following a flash. Phone wouldn't respond to adb/fastboot commands, or upgrade tool. I kept powering off, and rebooting holding combo of power, vol up, down, and both. Finally after several tries, it booted into TWRP! I wish I could say it was a particular combo, but it was just repetition of power off, and combo of power/ vol buttons. Was able to do this twice with this "method". I have 60450 (Cricket). This Phone doesn't respond how I am used to getting into download (power+vol down), or recovery (power+vol up) Hope this helps if you find yourself in a similar situation.
I've developed an issue as well. I can get into twrp just fine and all is fine there but any combination of ROM or kernel even stock makes my phone reboot every 2-5 minutes. Last night after messing around with a few cm builds and then going back to stock after I couldn't get the phone to cool down..... Stock no longer wanted to cool down either. It's been running way to hot so I turned it off for the night. Turn it back on today and same issues. It even restarts on the powered off battery charging screen , I took it a step further and deleted system, data, cache, and internal storage as well as removing my external sd so no ROM or files was on it at all and it still wanted to reboot at the charging screen! Only place it doesn't is in TWRP. I'm not sure if it's a battery safety issue because it's noticing how hot the device is but I was proven wrong with that too, put it in the freezer for 3 mins and it rebooted then too lol. I'm not sure what to do as even download mode reboots. Wtf. Idk if maybe there's some stock files I could attempt to flash through adb? Can anyone help?
have you tried to flash some stock rom? there is a thread around here which has some twrp backups on stock roms. maybe it helps to get into download mode and repair the phone with the Q.
jani0417 said:
have you tried to flash some stock rom? there is a thread around here which has some twrp backups on stock roms. maybe it helps to get into download mode and repair the phone with the Q.
Click to expand...
Click to collapse
Just did. Damn i thought for sure it was the answer, but nope, the phone has rebooted 3 times since i just restored the backup from that thread 20 mins ago. It feeezes for a sscond and then will reboot. Whats even worse is it soemtimes doesent let me charge the phone when powered down. Instead of showing the charging battery screen it just boots up into Android. Its highly annoying. I can get into download mode, it just won't stay there.
that suxx. did you unlocked the bootloader? maybe you should relock it.... it's just an idea, really don't have any more idea
jani0417 said:
that suxx. did you unlocked the bootloader? maybe you should relock it.... iitt's just out oan idea, really don't have any more idea
Click to expand...
Click to collapse
i want to see if twrp is causing the pgone to reboot of download mode. i need ghe stock recovery img for 60450 bu i cant find it.
carnivalrejectq said:
i want to see if twrp is causing the pgone to reboot of download mode. i need ghe stock recovery img for 60450 bu i cant find it.
Click to expand...
Click to collapse
HEre's the original recovery
https://mega.nz/#!NsEXkJZY!S-W9OtDSHVi3EBVcHBKdLX_Ru0yKrGI8g4saaHAtgPY
aleksandar.d123 said:
HEre's the original recovery
https://mega.nz/#!NsEXkJZY!S-W9OtDSHVi3EBVcHBKdLX_Ru0yKrGI8g4saaHAtgPY
Click to expand...
Click to collapse
Thanks. Unfortunately it didn't work. No matter what I do the phone reboots out of DL mode during the process and ruins it. I'm at My wits end with this phone. Have never had this many issues before. I've done everything. I even used the backup from that old thread to restore stock for 6450. All should've been well but I got reboots even on stock at 90% charged. What's very strange is the only thing I can do to keep this from rebooting is use YOUR kernel from the latest Flyme ROM. No idea why but reboots are minimal with it. They still happen but a lot less. All other ROMs and kernels have issues.
carnivalrejectq said:
Thanks. Unfortunately it didn't work. No matter what I do the phone reboots out of DL mode during the process and ruins it. I'm at My wits end with this phone. Have never had this many issues before. I've done everything. I even used the backup from that old thread to restore stock for 6450. All should've been well but I got reboots even on stock at 90% charged. What's very strange is the only thing I can do to keep this from rebooting is use YOUR kernel from the latest Flyme ROM. No idea why but reboots are minimal with it. They still happen but a lot less. All other ROMs and kernels have issues.
Click to expand...
Click to collapse
Sorry for your trouble, but i dont know why you havent send your device to warranty repair allready and instead of that you wrote your troubles across several threads
DallasCZ said:
Sorry for your trouble, but i dont know why you havent send your device to warranty repair allready and instead of that you wrote your troubles across several threads
Click to expand...
Click to collapse
I found him a flashable stock that he got to work. Part of, if not all, of his problem is I think he only has access to a sub-par pc or tablet or something. Anyway, I remember when I didn't know how important it is to have patience and not freak out, and quite a few people had the patience for me , and guided me. I learned. Perhaps this is where he is at. I post things that I have run into, and figured out to try and repay the kindness shown to me. He was trying on his own to figure it out, and that is WAY better than people who don't even try to search, and expect others to do everything for them. This is a community, and just like life, people are at different places. As long as someone is trying, I will try to help if I can. You can't send a rooted phone running CM for warranty.
EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
carnivalrejectq said:
EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
Click to expand...
Click to collapse
Hey......we all get flustered and forget the basics sometimes. Plus, for me, this phone doesn't respond like all the HTC, Nexus, and Samsung phones I've rooted and modded. That, and the insistence for every carrier/region to have their own variant, even on these cheaper phones. The T-Mobile Note 3 and 4 were even different depending on whether you had the black or white one! Hope this gets you back to normal, and if you don't have an SD card, at least get a cheap 8gb, and keep a stock backup on it. I've had that be a lifesaver more than once. Good luck my friend, and maybe stick to stock rooted? Lol
dongarritas said:
Hey......we all get flustered and forget the basics sometimes. Plus, for me, this phone doesn't respond like all the HTC, Nexus, and Samsung phones I've rooted and modded. That, and the insistence for every carrier/region to have their own variant, even on these cheaper phones. The T-Mobile Note 3 and 4 were even different depending on whether you had the black or white one! Hope this gets you back to normal, and if you don't have an SD card, at least get a cheap 8gb, and keep a stock backup on it. I've had that be a lifesaver more than once. Good luck my friend, and maybe stick to stock rooted? Lol
Click to expand...
Click to collapse
All is back to normal, no reboots. I do have an SD card and did have a backup the thing is though I accidentally saved another back up over the original with custom kernel so it was useless lol. And oddly the reboots sort of stopped happening right before but I was using the custom kernel from Flyme which is the only one that seemed to be working. I'm hoping that the issue is with root and not a hardware one from the phone getting to hot flashing things.
For those who haven't rooted and have received the new OTA or updated manually via LG Bridge, have you seen or read of any changes from the update? Of course, other than them patching out the Dirty Santa exploit we've used for root. Speaking of which... (sidebar) manufacturer pushing out exploit patches shortly after root being achieved on a device sounds very Note7-nostalgic to me.
So far root has been a disaster for non devs. Bricks and other problems with stuff not working. I wouldn't root this phone yet, it is not like a Samsung where you can just easily fix everything with Odin. That said, I will not accept an OTA update if all it does is patch the root method. They had better have some useful things like camera focusing faster, battery lasting more than 3 hours, etc. for me to update.
Root is fine and everything world perfect. At least for h918.
hotstocks said:
So far root has been a disaster for non devs. Bricks and other problems with stuff not working. I wouldn't root this phone yet, it is not like a Samsung where you can just easily fix everything with Odin. That said, I will not accept an OTA update if all it does is patch the root method. They had better have some useful things like camera focusing faster, battery lasting more than 3 hours, etc. for me to update.
Click to expand...
Click to collapse
Quite honestly I've only seen a couple of people who have hard bricked their devices - mainly just either one who used the dirtysanta on a phone that was not listed as compatible and the dev of dirtysanta when testing out reverting back to stock per request by users.
Rooting/Unlocking this phone has significantly increased battery and performance especially after installing Tilde88's ROM. Sure for the others who have variants outside of T-Mobile (like me), we have the static boot screen, but considering how minimal the impact is - it's well worth it. To each their own, but I would not say rooting is a disaster for this phone.
Nougat is still really new. Only a handful of phones support it. Hell, if you look at the Pixel forums, I've seen many more bricks there than over here.
twistedvip said:
Quite honestly I've only seen a couple of people who have hard bricked their devices - mainly just either one who used the dirtysanta on a phone that was not listed as compatible and the dev of dirtysanta when testing out reverting back to stock per request by users.
Rooting/Unlocking this phone has significantly increased battery and performance especially after installing Tilde88's ROM. Sure for the others who have variants outside of T-Mobile (like me), we have the static boot screen, but considering how minimal the impact is - it's well worth it. To each their own, but I would not say rooting is a disaster for this phone.
Nougat is still really new. Only a handful of phones support it. Hell, if you look at the Pixel forums, I've seen many more bricks there than over here.
Click to expand...
Click to collapse
I agree with @twistedvip. Definitely not a disaster. I am on @OvrDriVE 's ROM coming from stock rooted h918 and the phone is definitely faster with better battery life. Everything works. Couldn't be happier.
twistedvip said:
Quite honestly I've only seen a couple of people who have hard bricked their devices - mainly just either one who used the dirtysanta on a phone that was not listed as compatible and the dev of dirtysanta when testing out reverting back to stock per request by users.
Rooting/Unlocking this phone has significantly increased battery and performance especially after installing Tilde88's ROM. Sure for the others who have variants outside of T-Mobile (like me), we have the static boot screen, but considering how minimal the impact is - it's well worth it. To each their own, but I would not say rooting is a disaster for this phone.
Nougat is still really new. Only a handful of phones support it. Hell, if you look at the Pixel forums, I've seen many more bricks there than over here.
Click to expand...
Click to collapse
I do have a T-mobile. Is Tilde88's ROM a stock rom with just some tweaks or not Noughat? Also is there a program like Odin that you can flash back to non-rooted whenever you want? Say I want to play PokemonGo, well you can't if rooted. So with Samsung phones you just have supersu unroot, play, and then odin flash root back. It literally takes 1 minutes and nothing ever goes wrong. Is there a program like Odin to do that? If not, then LG phones really aren't ready to be rooted and unrooted to use Android Pay, PokemonGo, and all the other software that you can't use when rooted. And don't get me wrong, I have had and rooted every Samsung phone since the S3. But this is my first LG, and I just don't see an easy way to do things like via Odin. Hell even if you brick a Samsung you can usually just Odin flash stock rom and be back to new. How do you do this with LG?
Unfortunately LG doesn't provide as powerful of a tool as Odin is. They have LG bridge and Uppercut (I believe those are the two names) where you can flash TOTs and KDZ files to be able to restore back to stock completely and flash updates. I believe currently we dont have any way to flash TOT files though and thus are stuck. But for T-Mobile users, you should be able to simply relock your phone and go right back to stock very easily.
As for switching back between root and stock - using this dualboot-patcher you might be able to do what you're looking to do. Just know the root method used is dependent upon the dirtycow exploit. T-Mobiles 10i update has the Dec 5 security update which fixed that exploit. I don't know much about the dualbooting though so it may not be what you're looking for after all.
Too bad lg bridge keeps returning unable to download update error.
Sent from my LG-H918 using XDA Premium HD app
It worked for me but it took forever. Also it failed mid way and I had to pull out the battery, disconnect and reconnect the phone but then it updating without any problems.
The only thing I noticed so far is that it brings the Android security patch up to December 1st, so it's not completely useless.
hotstocks said:
I do have a T-mobile. Is Tilde88's ROM a stock rom with just some tweaks or not Noughat? Also is there a program like Odin that you can flash back to non-rooted whenever you want? Say I want to play PokemonGo, well you can't if rooted. So with Samsung phones you just have supersu unroot, play, and then odin flash root back. It literally takes 1 minutes and nothing ever goes wrong. Is there a program like Odin to do that? If not, then LG phones really aren't ready to be rooted and unrooted to use Android Pay, PokemonGo, and all the other software that you can't use when rooted. And don't get me wrong, I have had and rooted every Samsung phone since the S3. But this is my first LG, and I just don't see an easy way to do things like via Odin. Hell even if you brick a Samsung you can usually just Odin flash stock rom and be back to new. How do you do this with LG?
Click to expand...
Click to collapse
First off, if you don't know about something, you should probably keep your opinions to your self. It took me the ability to read, and twenty minutes to unlock the bootloader and root my LG-H918 (T-Mobile) then when I had to take it back I flashed the stock odexed rom, unrooted, and locked the bootloader in about 20 minutes as well... I'm no developer, but I'm smart enough to read instructions, comprehend them, and follow them to get a desired result... And if you can recover from a brick... Ever, then you aren't hard bricked. Hard bricked means your device is dead, and unrecognizable by any means, or unrecoverable. You are referring to a soft brick. Please learn what you are talking about before posting.
"sometimes it is better to keep one's mouth shut and be thought a fool, than to open it and remove all doubt"
Sent from my LG-H918 using Tapatalk
ZDeuce2 said:
First off, if you don't know about something, you should probably keep your opinions to your self. It took me the ability to read, and twenty minutes to unlock the bootloader and root my LG-H918 (T-Mobile) then when I had to take it back I flashed the stock odexed rom, unrooted, and locked the bootloader in about 20 minutes as well... I'm no developer, but I'm smart enough to read instructions, comprehend them, and follow them to get a desired result... And if you can recover from a brick... Ever, then you aren't hard bricked. Hard bricked means your device is dead, and unrecognizable by any means, or unrecoverable. You are referring to a soft brick. Please learn what you are talking about before posting.
"sometimes it is better to keep one's mouth shut and be thought a fool, than to open it and remove all doubt"
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Think what you want, but I am also not a dev, but a techie guy. To me it is irrelevant if you have a soft brick if you don't have the tools and knowledge to recover it, which 99.99% of LG V20 users DON'T HAVE. So your soft bricked LG V20 might as well be a hard brick. My point is that 90% of regular Joes can use Odin and recover easily from a soft brick, on the LG V20, NOT SO MUCH. If you think finding LG's cryptic flashing software, learning ADB, and whatever else is needed is something that most users can do, you are greatly mistaken. Sure, one day there might be freely available, easy to use LG V20 flashing software similiar to Odin, but right now there isn't yet. I've rooted and flashed HTCs and Samsungs never with issues, but this LG is a far more complicated beast. I am not saying it can't be done, I am saying that most people can't do it or recover if there is a mistake. Just sayin don't mess with it if you are a newb yet, until there is more mature flashing software.
ZDeuce2 said:
when I had to take it back I flashed the stock odexed rom, unrooted, and locked the bootloader in about 20 minutes as well...
Click to expand...
Click to collapse
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
MidtownHD said:
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
Click to expand...
Click to collapse
I think they took that update out coz everyone is having trouble updating.
I really want to update, there's many bugs right now but I don't want to lose my root
hotstocks said:
Think what you want, but I am also not a dev, but a techie guy. To me it is irrelevant if you have a soft brick if you don't have the tools and knowledge to recover it, which 99.99% of LG V20 users DON'T HAVE. So your soft bricked LG V20 might as well be a hard brick. My point is that 90% of regular Joes can use Odin and recover easily from a soft brick, on the LG V20, NOT SO MUCH. If you think finding LG's cryptic flashing software, learning ADB, and whatever else is needed is something that most users can do, you are greatly mistaken. Sure, one day there might be freely available, easy to use LG V20 flashing software similiar to Odin, but right now there isn't yet. I've rooted and flashed HTCs and Samsungs never with issues, but this LG is a far more complicated beast. I am not saying it can't be done, I am saying that most people can't do it or recover if there is a mistake. Just sayin don't mess with it if you are a newb yet, until there is more mature flashing software.
Click to expand...
Click to collapse
Speak for yourself, you are definitely in the minority, most of us know how to do these things or we wouldn't be here doing them... And I could care less if you want to call it a pb&j, it's still a soft brick...
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:12 PM ---------- Previous post was at 03:07 PM ----------
MidtownHD said:
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
Click to expand...
Click to collapse
Remove root in SuperSU app. And I did not change recovery, just relocked the bootloader
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------
wing_addict_usa said:
I really want to update, there's many bugs right now but I don't want to lose my root
Click to expand...
Click to collapse
NATF's latest rom is the update... On LGH918
Sent from my LG-H918 using Tapatalk
ZDeuce2 said:
Remove root in SuperSU app. And I did not change recovery, just relocked the bootloader
Click to expand...
Click to collapse
What happens after you re-lock the bootloader? does it work well with TWRP installed? or does it replace it automatically with the stock one? and everything becomes "stock"?
MidtownHD said:
What happens after you re-lock the bootloader? does it work well with TWRP installed? or does it replace it automatically with the stock one? and everything becomes "stock"?
Click to expand...
Click to collapse
Honestly, I went back as stock as possible to see if it fixed my speaker distortion problem, (it did not) but just left it that way and locked it before I returned it just so the can't be check for corruption screen didn't appear, it still worked fine, but I never checked whether the stock bootloader overwrote twrp. The corruption screen went away which is what I was trying for.
Sent from my LG-H918 using Tapatalk
Has anyone been able to capture the URL or the zip for the update?
MidtownHD said:
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
Click to expand...
Click to collapse
So if I may join in I flashed a back up and I can't get into my device is there a tool I can't get into recovery for some reason
Sent from my Nexus 6P using Tapatalk
ZDeuce2 said:
Speak for yourself, you are definitely in the minority, most of us know how to do these things or we wouldn't be here doing them... And I could care less if you want to call it a pb&j, it's still a soft brick...
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:12 PM ---------- Previous post was at 03:07 PM ----------
Remove root in SuperSU app. And I did not change recovery, just relocked the bootloader
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------
NATF's latest rom is the update... On LGH918
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
This says M https://forum.xda-developers.com/v20/development/rom-natf-1-00-test-5-debloated-stock-t3509750