Related
Hey,
I just wanted to inform you about an issue that happens in TWRP. I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B. I think TWRP should inform the user that rebooting will brick the device. What are your thought on that? It could be done similar to how TWRP informs the user to install supersu if the phone isnt rooted.
This would be really helpful as it would prevent many people like myself from bricking their phones.
Now if I connect my pixel it only shows Qualcomm HS-USB Diagnostics 900E (COM3). No bootloader, fastboot, or recovery is present.
Here are a coupe of links of other people that did the same thing:
https://productforums.google.com/forum/#!topic/phone-by-google/sXjCoQ8glac
http://forum.xda-developers.com/pixel-xl/help/pixelxl-bricked-t3517310
Thanks!
Edit
I contacted the devolper of TWRP and he says that it should have boot loader regardless.
Here is the history: At work 3pm, froze Android system apk and some other telephone apps to troubleshoot something, I know I shouldn't do this. Resulted into boot loop. Go into twrp recovery and wipe data. It boots up fine and I see it downloading updates but it never goes through, I attempt to go back to recovery and apparently it's back to the stock recovery even though I originally had TWRP rc1.
I get home at 7 pm, I want to install TWRP rc1 so I send the command to boot into TWRP and then I install the zip, then I install sr5 SuperSU. I change to slot b and it's been bricked since.
It arrived November patch and it stayed like that since I was rooted. It attempted to install 7.1.1 but it returns installation problem. I think the bootloader was removed because of the failed update.
Your in download mode. I had this happen once on my Nexus 7. I held power for 90 seconds and it went back to bootloader. However I dont know about the pixel. Its still a new and uncharted device.
You also have to realize TWRP is in an unstable stage. You really should not flash anything until its in final release mode. I know I know... Hindsight is 20/20.
If you have insurance you could get it replaced.
Good luck.
sorry to hear dude..
bahehs said:
I think TWRP should inform the user that rebooting will brick the device. What are your thought on that?
Click to expand...
Click to collapse
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
bahehs said:
I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B.
Click to expand...
Click to collapse
Does anyone have an understanding about how something like this could potentially happen? Do these phones ship without information on the second slot? After my phone OTA updated, I switched slots without issue back to the previous version by following the information from Android Police. I'm not clear on what exactly would need to happen for the noted situation, and how someone could potentially get into a similar situation, unless the phone ships without information on the second slot. Switching slots worked without issue the times I tried it, but my phone had been through a typical OTA update before switching slots, so there was definitely information on both slots when I tried it.
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Scott said:
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Click to expand...
Click to collapse
Same, mine is on slot B. Dunno if it came that way, but it is only two days old. I let it take the OTA then flashed Francos kernel and then booted the root su image.
I really regret not watching more closely how all of impacted which slot it was on.
Sent from my Pixel XL using XDA Labs
Everytime you get OTA update you will switch slots. If you update via flashall it will say on the same slot.
This mode can't be a complete brick but it doesn't look like anyone has a solution yet. Maybe we will need some HTC tool?
Also when you root or modify you take responsibility for anything that happens. There is always a chance of a brick. At least Google will still probably warranty these devices.
Sent from my Pixel using Tapatalk
CZ Eddie said:
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
Click to expand...
Click to collapse
This comment is unnecessary and serves no purpose in this thread.
Sent from my Pixel XL using XDA-Developers mobile app
I'm okay with that.
Updated op with more info
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
reb1995 said:
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
Click to expand...
Click to collapse
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Sent from my Pixel XL using Tapatalk
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
Sorry for the long delay. No I was not rooted.
yearn2burn said:
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Click to expand...
Click to collapse
Bump
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
You are right a failed OTA could brick a pixel phone
DR3W5K1 said:
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
You are right a failed OTA could brick a pixel phone
Click to expand...
Click to collapse
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
aholeinthewor1d said:
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
Click to expand...
Click to collapse
Failed bootloader flash? The Google .IMG files contain bootloader's.
EDIT I do believe the flash_all.sh flashes the bootloader
So you cant even run ADB commands ( a.k.a Bootloader / Recovery mode ), its a hard brick or soft ?
Does your PC detect the device when its on and connected via USB ?
Why did you switch slots in the first place ? if your taking an OTA on a rooted device with SU an OTA wont even apply via TWRP, you have to manually flash with the flash-all.bat script or part by part and the A / B boot slots are handles by the updates so you don't accidentally boot with a slot with no bootloader.
There is no need to swap A / B manually and if your going to flash and want to play with the A / B slots you should at least flash the partitions first but hindsight is a wonderful thing.
Aboot here might be your friend, but as this device is still quite new to many devs and or the tools might not be publicly available . . .
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Did you get it fixed?
frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm
What roms can we use with dirty santa root?
me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.
Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.
Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir
Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you
Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.
So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery
Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...
can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.
Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.
Tracfone version
I'm having no luck with Kingroot. It says no root available for device.
According to 'one-click-root' website, the device has no way of rooting it.
Is there any updated information?
.
device specifics:
model: SM-S920LZAATFN
android: 5.0.2
build: LRX22G.S920LUDU1APK2
hardware version: S920L.03
.
[edit: was hoping to change the title to reflect that this post is about the tracfone version]
TWRP recovery method?
TWRP recovery method?
I've read that a phone may possibly be able to be rooted by using odin to download a TWRP recovery, then booting into that new recovery using hardware keys, instead of rebooting normally. And this results in a rooted phone?
I think I have seen a TWRP that may work with this phone. Any help is appreciated. I'd like to be able to update this thread to include a step by step approach to this and other versions of the same model 920.
I'll continue to post updates as I discover more information.
DIY time : crash course in brain surgery
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)
friimynd said:
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)
Click to expand...
Click to collapse
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.
c3p0u812 said:
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.
Click to expand...
Click to collapse
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.
Inuyashian said:
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.
Click to expand...
Click to collapse
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:
c3p0u812 said:
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:
Click to expand...
Click to collapse
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.
Inuyashian said:
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.
Click to expand...
Click to collapse
Hey, I thought I'd let you know LineageOS 14.1 is available to us now. I can't find a specific thread on it, but you can download it from http://grandprime.ddns.net/jenkins/job/LOS_Builds/# Flash it with twrp. You will want to flash that and then flash open gapps [ARM - 7.1] and then whichever from here http://opengapps.org/ I did all that first, set it up rebooted and then installed Magisk.
It has Substratum pre-installed and it let's you theme it nicely. There is only an unofficial xposed version so far.
Anywho, thought I'd throw that out there.
thanks for the replies, gives me inspiration to keep on trying; the phone is pretty ho-hum with default stuff and the general blah blah of social media, etc.;
thanks for the tips, feel free to post more details as they come in
My Turn
I'm about to try and put 14.1 and Magisk on mine. Wish me luck!
downloading twrp recovery and rooting
in google search up twrp click on the first link then click on devices on the top right corner then search up your phone download the twrp.img.tar file
power off your phone and press volume down + home button + power button to boot into download mode
in odin select AP then select the twrp.img.tar you downloaded then press start
your phone will reboot then download the SuperSU zip file
then go to settings then go to find my mobile you have to get a samsung account then you will see reactivation lock option turn that off
then power off your phone then press volume up + home button + power button to reboot into twrp recovery
once booted tap the install option then select where you downloaded the supersu zip file swipe to flash it once done flashing you will see the reboot system option to reboot your phone
then your phone should be rooted!
Hello,
Can someone help me with some instructions to install twrp and then flash either stock rom or custom rom. I want to have twrp as the recovery so i can flash things in the future and also make twrp backups.
Im running stock 8.1 beta with unlocked bootloader
I know there are guides out there but all of them are 2-3 months old. Since then we've had the 8.1 beta.
Any help will be much appreciated.
ZAFAR- said:
Hello,
Can someone help me with some instructions to install twrp and then flash either stock rom or custom rom. I want to have twrp as the recovery so i can flash things in the future and also make twrp backups.
Im running stock 8.1 beta with unlocked bootloader
I know there are guides out there but all of them are 2-3 months old. Since then we've had the 8.1 beta.
Any help will be much appreciated.
Click to expand...
Click to collapse
You can't.
There is no TWRP for 8.1 so it isn't possible.
This phone has no traditional recovery. Recovery is part of boot.
That means that the boot image needs to be patched for tarp and still be able to boot the system.
Currently, or at least until 8.1 is no longer beta you will not see a tarp that can stay permanently and coexist with 8.1.
ZAFAR- said:
Hello,
Can someone help me with some instructions to install twrp and then flash either stock rom or custom rom. I want to have twrp as the recovery so i can flash things in the future and also make twrp backups.
Im running stock 8.1 beta with unlocked bootloader
I know there are guides out there but all of them are 2-3 months old. Since then we've had the 8.1 beta.
Any help will be much appreciated.
Click to expand...
Click to collapse
If you wanna flash a custom ROM, you can use TWRP (LOS 15.1 and AOSIP are both 8.1 ROMs that can be flashed with TWRP), but I suggest you get very comfortable with ADB and fastboot BEFORE you wipe your phone. As Tech_head said, TWRP gets flashed to the boot, not recovery, so you have to flash TWRP with fastboot each time you want to boot into it, it won't stick.
This phone is not real friendly for flashaholics. Also, be prepared to lose EVERYTHING on your phone if you start flashing custom ROMs, because if you start having problems or want to flash back to stock, you're going to need to wipe all your data (fastboot -w) (this wipes all your media too!). In fact, if you want to flash a custom ROM, you should wipe everything anyway, and don't count on TWRP being able to complete a nandroid backup or restore one. I haven't been able to once. Good luck, this phone's a *****!
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
gimpy1 said:
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
Click to expand...
Click to collapse
Its not that Essential is blocking any development of TWRP. Development for this phone, and all A/B partition phones for that matter, are really minimal right now, but especially the Essential because so few units were sold. Until Project Treble really gets going and more manufacturers start shipping A/B partition devices, you won't see much development for this phone. Eventually, someone will solve the issues with TWRP, but I doubt well ever see a lot of custom ROMs. When I say this phone's a *****, it's because of the issues with TWRP more than anything. Dirty flashing isn't working for me on AOSIP, Nandroid backups don't work, and flashing firmware can only be done using fastboot AFAIK (yes, with a computer). If you're not computer savvy, then you better pass on this phone if you want to run custom ROMs. It's a great phone even stock though, so up to you if you can settle for stock or u wanna learn more about ADB and fastboot, it's worth it IMO. If u want a phone recent that has good development, go with the OnePlus 5T, but even that phone can be a bit tricky for flashing, as I said, TWRP is not very compatible with Oreo 8.1 yet for any phone. You have to disable your pin/fingerprint each time you boot TWRP because they haven't figured out how to decrypt 8.1 yet. This is all common knowledge if you follow the development threads for these phones. The old days of flashing five ROMs in a day are over man, at least for the time being.
gimpy1 said:
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
Click to expand...
Click to collapse
A) LG phones are not root friendly. Only certain SKUs of any model (1 in maybe 8) can even bootloader unlock. Indeed, even rooting is problematic and only the result of security "flaws". If you are a flash-a-holic, you definitely don't want an LG. Or a Samsung, or any phone sold with carrier-specific hardware or firmware....IIRC the Samsung S8 took a calendar year to root.
B) The technical hurdle here on the Essential is also present on Pixel phones. Getting a Pixel will not free you from this.
The A/B partition scheme and boot layout is shared by Pixel and Essential. The easy flashing processes went away with the Nexus program. A/B isn't that bad-but you must learn fastboot and ADB commands. There aren't a whole lot of common one you really need, but you need familiarity with the toolset.
Thx, I will do some googling and reading.
The easiest way i found is to flash TWRP, Flash dump for your phone, then flash 8.1 boot.img so it don't bootloop. The recovery won't stay but you will be stock.
Download the dump for your phone from there
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
So flash TWRP
Flash dump from internal sd
flash stock boot image
gimpy1 said:
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
Click to expand...
Click to collapse
I mean no offense by this at all but one would think even a "semi-flashoholic" would be fairly well versed with Fastboot and ADB. Im curious how you have much experience with twrp if you dont know what those two things mean. Unless of course youre coming from an S3 or something and especially someone thats on verizons network. Theyve been pretty famously against unlocking bootloaders since i can remember. Also, it doesnt matter if youre buying off contract or get your phone through your carrier. Youre going to pay the same price in the long run either which way, and contrary to many believers that are stuck in that mind set of "they used to give free phones away or at most like $200" you were still paying the full 699.99-899.99 as you are now days . so my suggestion, buy straight from the source (google, lg, samsung, or even off amazon) and pay with a credit card because especially if you have a zero interest for x amount of time its going to be cheaper in most cases and you dont have to have that out of pocket cash for taxes on the device to pay that day. Ive worked for 3 out of 4 of the top carriers in my life and trust me, its the way to go. Also yes if you are looking for a root friendly phone to flash away on, this thing is not going to be your best choice either. Kick ass phone but not very developer/flash friendly.
Well, after considerable thought, I finally decided against going with the Essential or any unlocked bl.
I just received my LG (vs996) from Verizon day before yesterday.
gimpy1 said:
Well, after considerable thought, I finally decided against going with the Essential or any unlocked bl.
I just received my LG (vs996) from Verizon day before yesterday.
Click to expand...
Click to collapse
Good luck with that...just dumped my v20. LG can suck it.
Well, to each his own, I guess.
Pretty nice phone, but, in still learning to do things without root.
gimpy1 said:
Well, to each his own, I guess.
Pretty nice phone, but, in still learning to do things without root.
Click to expand...
Click to collapse
No root is the least of it...stuck on 7.0.0 forever, and its first and likely last os upgrade isn't likely to come until June 2018 at the soonest.
Pathetic for a supposed flagship.
I was an excited fool, and paid new retail at release. Never again am I buying an LG
Mine came with 8.0 (from Verizon).
gimpy1 said:
Mine came with 8.0 (from Verizon).
Click to expand...
Click to collapse
Oh that is right. I was confusing vs995 and vs996. Oh well.
I have a bricked LG G2 that is stuck in a boot loop.
I was running a custom rom and lent the phone to my ex-gf and she tried said yes to OTA update. Then instead of telling me she attempted the fix the phone herself and in doing so used TWRP to wipe backups/all data/everything.
I can get into TWRP. I can use adb sideload.
That is it. No recovery mode, No download mode.
Can't get device detected by qhsusb_bulk
I think I need to fix the stock firmware/image. LG flashtool doesn't work and I think that is because I cannot boot the phone into android and because I can't get into Download mode.
Here is a semi-revelant thread on XDA, I posted there but haven't had a lot of replies, I doubt many people check the G2 forums as its an old phone at this point, yet its still in perfect condition, has a 1080p screen and runs fast.
https://forum.xda-developers.com/showthread.php?t=2582142&page=375
Please please help. Ill paypal someone $75 if they can help me get it working.
Thanks
Which variant? D802? Which firmware were you using before, kitkat, lollipop, stock or custom ROM? PM me if you want, I have bricked and unbricked mine many times
bigfamine said:
I have a bricked LG G2 that is stuck in a boot loop.
I was running a custom rom and lent the phone to my ex-gf and she tried said yes to OTA update. Then instead of telling me she attempted the fix the phone herself and in doing so used TWRP to wipe backups/all data/everything.
I can get into TWRP. I can use adb sideload.
That is it. No recovery mode, No download mode.
I think I need to fix the stock firmware/image. LG flashtool doesn't work and I think that is because I cannot boot the phone into android and because I can't get into Download mode.
Here is a semi-revelant thread on XDA, I posted there but haven't had a lot of replies, I doubt many people check the G2 forums as its an old phone at this point, yet its still in perfect condition, has a 1080p screen and runs fast.
https://forum.xda-developers.com/showthread.php?t=2582142&page=375
Please please help. Ill paypal someone $75 if they can help me get it working.
Thanks
Click to expand...
Click to collapse
Yeah sure can help.had this problem before too
zizuka said:
Which variant? D802? Which firmware were you using before, kitkat, lollipop, stock or custom ROM? PM me if you want, I have bricked and unbricked mine many times
Click to expand...
Click to collapse
D803
I was running a custom rom. I *think* it was lollipop.
Basically the phone sat in my desk for two years without use as I had a work from home job and could get by with a free app on my iPad, I lent it to my ex and this happened a few days later
I now need a mobile phone for a new job I am starting and this phone is still beautiful I would really like to use this instead of dishing out multiple hundreds of dollars
Not a problem to help. I've bricked my old G2/my wife's G2 not less than 10 times, and all gonna Ok later. If you has TWRP saved backups - then I can help unbrick it even if it stuck on "LG" logo! Can PM me foor details
As long as EFS is not wiped or you have a backup you can just flash a new ROM with TWRP right? Or flash a backup?
As long as you can access TWRP you can also connect to USB in case you do not have any ROMS stored on the phone and transfer them that way.