Related
Will (auto) root & unroot. Work for the new ota 605.7 update for the HTC thunderbolt
My friend wants to root the easy way ....NEED HELP will auto root work or not ...
sent from my rooted tbolt using XDA app
Yes but he should use the manual as most soft bricks occur with auto root.
Sent from my ADR6400L using XDA App
miketoasty said:
Yes but he should use the manual as most soft bricks occur with auto root.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
This. I don't trust "auto" roots.
The manual, ADB method is proven and not NEARLY as difficult as it may seem up front. You just have to follow the steps in jcase's thread, and you'll be done in half an hour. It's at least worth reading through.
TheStick13 said:
This. I don't trust "auto" roots.
The manual, ADB method is proven and not NEARLY as difficult as it may seem up front. You just have to follow the steps in jcase's thread, and you'll be done in half an hour. It's at least worth reading through.
Click to expand...
Click to collapse
Completely agree. You don't even need to learn adb to use it it's all just copy and paste.
Sent from my ADR6400L using XDA App
i was trying to root my friends phone with captains script which holds your hand...
I came across a problem... when trying to flash the downgrade pcimgfile... kept saying "Main version older, update failed"
As per him, he has not flashed anything on his phone, everything is stock andhe got his phone about a month after i did (for it launch day). The script was able to push the files and all seems good, but i have not been able to pin point whats causing the error. (i didnt get to take a screen shot with the firmware and stuff) Ive rooted 2 phones without issues with the script and on this particular phone, it seems to be working fine until i try to flash the update.
will using adb manually help in this case? I am thinking no.... but if anyone encountered this, mind sharing what you did?
I have not had any issue with the script. Its similar to the JCase's method it just issues the commands for you. Capt includes a copy of the commands the scrips runs in his thread so I found it helpful to look at it while I ran the scrip so I knew what it was doing and when. Like any set of instructions its always good to read through it all once before you preform it so you know what to expect. If you just download everything, click start, and expect it all to run smoothly then you are likely to run into problems.
JCase's method is good to learn off of tho and might be easier for people to pin point where errors occur.
The error i am seeing is with the phone itself. I think something may have gotten updated?
the script its doing its job. I also reboot my pc and did a factory restore.
Well Capt's script says it only works with software version 605.6 or 605.9 which I assume from when it was written means 1.12.605.6 or 1.12.605.9. If the phone your using is using software version 1.13.605.7 then you should use JCase's method here
The software is 1.12.605.6
Could it be Jcase maybe also updated the downgrade img file?
That first step is causijg the problem when i try to downgrade (the first time you flash the img file)
*looked at the thread and also went to the original thread, file md info is the same for the ruu on both posts **
I also have all the original exploit files on my pc from when i rooted MY phone... since he had a software version that was on the original root threads, i didnt have to change anything
This may be an issue you would want to ask in the chat room that there is a link to in the Development section. If you look at the scripts contents as well as the manual instructions from JCase they are exactly the same up the the point you are getting stuck at. The MD5's even match. So I wouldnt expect doing one method over the other would solve your problem. Maybe someone on the chat could help you out tho.
yeah... im gonna have to go in there....
Its the same software as mines. I didnt modify any files on my pc.... it should have just worked. thanks for the feed back. Guess i will try when i get home later and have more time to mess with it.
So I had an issue in hboot, i am not sure if something was unconnected or what but i think i am in a bootloop.
It happened during the first round where you unplug you phone, I did and it started to check the sd image and had the expected no image error message.
after it checked them all the phone displayed a error message the the "main version is older" that "update failed" and to press power to reboot.
when i do that it takes me to another screen. I think its the fastboot screen and my only options are bootloader, reboot, reboot bootloader, power down. All of which lead me to the same problem and no way that i can figure out.
I found this while searching for a fix, would i be able to pull the sd card, flash the update, and start over again? (albe it with a different root program)
Thank you before hand for your help.
I got my TF700 around April of this year. I rooted it, but left it on the stock 4.1 android it came with. A couple weeks ago, I let it go through with the stock 4.2 upgrade. Mostly fine, but I kept finding things that bugged me. One of which was that my root seemed to only be partly there. I had installed OTA RootKeeper, and it said that it had restored root after the update. What I'm finding though, is that only apps which had root before still do. Anything new gets told there is no root.
So after all that, I decided yesterday to flash to a custom ROM. Since I thought I had root, I installed GooManager to try to put TWRP on for the flashing. It never gave me any errors, but repeatedly just didn't do anything, and attempting to reboot in recovery mode always failed (once I got the "dead android" with the exclamation point, but usually it would just do a normal reboot). That lead me to figure out the no-root problem, so I decided to reinstall root. I tried with the Scott Tool and with Motochopper, but both failed. In the process of trying to fix those issues, I went ahead and did a factory wipe, but still couldn't get them to work.
So that's where I'm stuck. I have a "factory fresh" install of 4.2.1 that is apparently still locked and unrooted. I want to put root back on at a minimum, but would really like to put on a custom ROM. Nothing I have found here or elsewhere has suggested anything that has worked for me. One site suggested that I needed to use the Asus unlocking tool, however I can't find it for download anywhere (all sites point to the Asus site, but it's not providing the download link anymore). Can someone help me get this working?
Get the unlock tool from here (choose "Android" as OS):
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Unlock your device (and void your warranty), then use the fastboot method for installing TWRP, as described on their web page.
_that said:
Get the unlock tool from here (choose "Android" as OS):
...
Unlock your device (and void your warranty), then use the fastboot method for installing TWRP, as described on their web page.
Click to expand...
Click to collapse
Thanks for the link. All the ones I found would not display anything in the OS selector, so nothing was downloadable. I'm working on that step now. Do you have a link to the fastboot method? Other than seeing the term in a few posts, I have no idea what that is or where I would find the directions you mention.
techturtle said:
Thanks for the link. All the ones I found would not display anything in the OS selector, so nothing was downloadable. I'm working on that step now. Do you have a link to the fastboot method? Other than seeing the term in a few posts, I have no idea what that is or where I would find the directions you mention.
Click to expand...
Click to collapse
There's a nice tutorial here: http://forum.xda-developers.com/showthread.php?t=2277112
You can also use Scott's tool: http://forum.xda-developers.com/showthread.php?t=1938129
Just make sure you downlaod the latest TWRP version which is 2.6.3.1
You may find post # 9 from this thread interesting: http://forum.xda-developers.com/showthread.php?t=2429872
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Hello, i have asked many questions regarding my current state of the device but i just wanted to clarify for one more time, because if i mess something up there is no way i can fix it with my budget, the device is the most expensive thing i have, so please understand me and my repetitive questions regarding this.
So, i had completely stock 4.4.4 KitKat, then without any backups or anything i installed the Towelroot app, clicked a button and i was rooted. I didn't expect that at all, because from my past old experience, in order to root a device it needed a lot of work and flashing and stuff. I really do not know what i was thinking when i installed that app and pressed the button, but whats done is done.
So i had this rooted 4.4.4 KitKat device and i saw these first screenshots of LollyPop and its softkeys, soon after that i found an app on market called SoftKeyz RooT and i installed it, again without backups changed the look of buttons. At the time i did not really understood that i had modified system files (even though the app warned me all the time about it).
Also i installed app called SuperSU and it installed some binaries.
So, i have no backups of my softkey buttons (perhaps anyone can share them?) and i have rooted device, i have not done anything else, but as far as i understand i will not get OTA right?
Are there any easy way to fix my device without having to do hard-looking flashing instructions?
I am seeing many threads that have small zip files that are also flashable, and that can fix these issues, but i have 0 understanding about that and there are no instructions nowhere to be found.
If i get the backup files for my buttons, and install them using the SoftKeyZ root app, and then unroot my device using some app (suggestions?) will i be able to install OTA then?
Also, can i just flash lollypop from these .zip files, using my current state of my device ? https://developers.google.com/android/nexus/images
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
That thread has instructions for getting back to stock. It is really quite easy.
The short version is that you download the zip from google, make sure fastboot works(which it should if you were able to root) and basically run the bat file.
There isn't really an easier way. You just have to read the instructions step by step.
To sum up:
In order to restore the stock navbar buttons:
• don't you see the stock buttons into SoftkeyZ app?
• you can flash system.img from the KK factory images
Lollipop factory images aren't available yet but if you want to upgrade you can use flashable zips (from vomer's or syko's threads) - clean flash recommended.
About OTA you should read this: http://forum.xda-developers.com/google-nexus-5/general/info-rooted-user-learn-to-update-t2927876
Finally you say that your N5 is the most expensible you have... so you should take better care of it (do not so something that you do not understand, backup your data on your PC/in the cloud,....)
Thank you both for answers, but when the lollypop image comes out at the google site, can i just flash that using the instructions you posted without doing anything else?
nikssims said:
Thank you both for answers, but when the lollypop image comes out at the google site, can i just flash that using the instructions you posted without doing anything else?
Click to expand...
Click to collapse
To update to LP through the factory images use the mentioned guide: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
nikssims said:
Also i installed app called SuperSU and it installed some binaries.
Click to expand...
Click to collapse
For some reason, this made me smile.
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
spook2022 said:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
quangtran1 said:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
Click to expand...
Click to collapse
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
lightmastertech said:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
Click to expand...
Click to collapse
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
quangtran1 said:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
Click to expand...
Click to collapse
If it rooted, and has modified system, doesn't the OTA update method fail?
And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.
Hi
Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?
After this, can i flash the the SuperSU.zip with TWRP?
spook2022 said:
<snip>
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
bobby janow said:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
Click to expand...
Click to collapse
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
spook2022 said:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
Click to expand...
Click to collapse
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.
@spook2022 It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.
Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)
edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
<snip>
Click to expand...
Click to collapse
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Click to expand...
Click to collapse
Thank you so much.
bobby janow said:
...I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
bobby janow said:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
kyle4269 said:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
Click to expand...
Click to collapse
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------
lightmastertech said:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
Click to expand...
Click to collapse
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
bobby janow said:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
.
Click to expand...
Click to collapse
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
bobby janow said:
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
Click to expand...
Click to collapse
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.
Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
Sent from my Pixel using XDA-Developers mobile app
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using
Code:
fastboot update <image>.zip
and leave off the -w to keep it from wiping.
Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.
so like the title states, i'm trying to flash twrp and get root. i've tried idk how many different methods and i'm hitting a brick wall. bootloader is unlocked, recowvery is giving me an error before closing itself, not doing anything. verified device is recognized by adb.
also tried flashing recovery using flashboot, but obviously that doesn't work on a20. i'm open to suggestions as i would really like to have a custom recovery
i could flash a rooted .kdz/.tot but i have yet to find one that is a20 or higher.
ZOMGITSABEAR said:
so like the title states, i'm trying to flash twrp and get root. i've tried idk how many different methods and i'm hitting a brick wall. bootloader is unlocked, recowvery is giving me an error before closing itself, not doing anything. verified device is recognized by adb.
also tried flashing recovery using flashboot, but obviously that doesn't work on a20. i'm open to suggestions as i would really like to have a custom recovery
i could flash a rooted .kdz/.tot but i have yet to find one that is a20 or higher.
Click to expand...
Click to collapse
BUMP. please help me, someone. if i could at least get root going i'd be happy.
ZOMGITSABEAR said:
so like the title states, i'm trying to flash twrp and get root. i've tried idk how many different methods and i'm hitting a brick wall. bootloader is unlocked, recowvery is giving me an error before closing itself, not doing anything. verified device is recognized by adb.
Click to expand...
Click to collapse
Sorry, to hear that it didn't work for you. In my experience, this has to be related to not following the instructions to the point. I was also stuck myself initially, only to find out later that I missed something in the instruction. Give us more detail, otherwise no one can help you. Which firmware version are you on? Which method are you trying? Is it an automated script or manual. IMO, the manual method works best, and easier to troubleshoot.
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
suhridkhan said:
Sorry, to hear that it didn't work for you. In my experience, this has to be related to not following the instructions to the point. I was also stuck myself initially, only to find out later that I missed something in the instruction. Give us more detail, otherwise no one can help you. Which firmware version are you on? Which method are you trying? Is it an automated script or manual. IMO, the manual method works best, and easier to troubleshoot.
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Click to expand...
Click to collapse
can you help me over discord or something? i'd GREATLY appreciate it and i'll love you forever
ZOMGITSABEAR said:
can you help me over discord or something? i'd GREATLY appreciate it and i'll love you forever
Click to expand...
Click to collapse
Didn't really understand your question! What seems to be the issue?
for anyone having trouble rooting 20a, i tried this guide and FINALLY have my phone running twrp and root working fine.
http://www.droidviews.com/install-twrp-recovery-and-root-lg-g5-on-android-nougat/
for anyone having trouble rooting 20a, i tried this guide and FINALLY have my phone running twrp and root working fine.
http://www.droidviews.com/install-twrp-recovery-and-root-lg-g5-on-android-nougat/
ZOMGITSABEAR said:
for anyone having trouble rooting 20a, i tried this guide and FINALLY have my phone running twrp and root working fine.
http://www.droidviews.com/install-twrp-recovery-and-root-lg-g5-on-android-nougat/
Click to expand...
Click to collapse
If this worked, good for you.
But I don't think it should work. Last time I checked, the very fastboot flash command is disabled in LG G5. Recowvery is supposed to be the only way.
BTW, I don't trust root and unlock methods outside of xda. There are lots of clickbait articles, which has the potential to brick your device.
suhridkhan said:
If this worked, good for you.
I don't trust root and unlock methods outside of xda. There are lots of clickbait articles, which has the potential to brick your device.
Click to expand...
Click to collapse
THIS!!!!
Other root methods and apps that root and all that stuff are just BEGGING for your phone to be destroyed. I used a KingRoot solution once on an old phone that no XDA certified method still worked on....it rooted it just fine. But all the added junk it installed as system files with highly restrictive permissions that made them impossible to remove essentially made the device unusable. This was an old phone I was just using for an experiment anyway so no loss. But it illustrates why any root methods not found on XDA are highly risky.
I mean, sometimes a questionable root method gets posted on XDA too. But it's usually debunked as a bad idea within a day or two. (Sometimes within an hour) So you can read about real world experience with that method on a specific device and know if you should avoid it or not.
And there are other Android developer sites like XDA that can give good root options and solutions, as well as good advice for a phone in general. I'm not suggesting that anything outside of XDA is crap. If you find a good root solution on another website that has a reputable history and you trust it, great.! But never google "Root my phone" and try the first option that pops up on some sketchy Chinese / Russian / Martian website.
Were you on updated nougat version and rolled back to v20a using lgup?