Ive seen a lot of threads about how to install google cam and im willing to. The probelm is i don't know how to do it properly. Is there anyone who can supply me with detailed steps to do it or is it possible to do it without root. Or is there any source of video which i can refer to. Im a noob and i need ur help. im not familiar with root
the best bet is to miflash an older update. the one that doesnt wipe everything when changing bootloader status, then use the old thread which shows the steps to enable eis and camera2api, lock the bootloader, and then update to the aug update via ota. This is the only full proof solution
pooniaprashant said:
the best bet is to miflash an older update. the one that doesnt wipe everything when changing bootloader status, then use the old thread which shows the steps to enable eis and camera2api, lock the bootloader, and then update to the aug update via ota. This is the only full proof solution
Click to expand...
Click to collapse
To flash any (old) ROM, you need to unlock the bootloader. So if you're already updated, there is absolutely no point in flashing old firmware, you'll get factory reset anyway.
---------- Post added at 08:47 AM ---------- Previous post was at 08:41 AM ----------
AlvinKyo said:
Ive seen a lot of threads about how to install google cam and im willing to. The probelm is i don't know how to do it properly. Is there anyone who can supply me with detailed steps to do it or is it possible to do it without root. Or is there any source of video which i can refer to. Im a noob and i need ur help. im not familiar with root
Click to expand...
Click to collapse
Search and study here first https://forum.xda-developers.com/mi-a1/how-to. Pretty much all guides are "proper". Be prepared to lose your data. Good luck
_mysiak_ said:
To flash any (old) ROM, you need to unlock the bootloader. So if you're already updated, there is absolutely no point in flashing old firmware, you'll get factory reset anyway.
---------- Post added at 08:47 AM ---------- Previous post was at 08:41 AM ----------
Search and study here first https://forum.xda-developers.com/mi-a1/how-to. Pretty much all guides are "proper". Be prepared to lose your data. Good luck
Click to expand...
Click to collapse
search the link you posted the op yourself and quote me a better solution resulting in a locked bootloader and camera2api+eis enabled. The only alternative is to press and hold "volume -" button while running "fastboot oem unlock/lock bootloader" to bypass wipe, but as many have tested and pointed out (https://forum.xda-developers.com/showpost.php?p=77250310&postcount=3), this method isnt the most reliable as wipe commands are still there in standby and a wipe is triggered whenever the user will boot into recovery (stock/custom). So neither your post provides any solution to the op other than searching threads for answers which he obviously would have done before typing a separate thread, but also you discredit the only viable tried and tested solution the op has atm, congrats. :good:
AlvinKyo said:
Ive seen a lot of threads about how to install google cam and im willing to. The probelm is i don't know how to do it properly. Is there anyone who can supply me with detailed steps to do it or is it possible to do it without root. Or is there any source of video which i can refer to. Im a noob and i need ur help. im not familiar with root
Click to expand...
Click to collapse
Also to the op, if you're interested and are having issues while following my post feel free to quote or pm me, i'll help you.
AlvinKyo said:
Ive seen a lot of threads about how to install google cam and im willing to. The probelm is i don't know how to do it properly. Is there anyone who can supply me with detailed steps to do it or is it possible to do it without root. Or is there any source of video which i can refer to. Im a noob and i need ur help. im not familiar with root
Click to expand...
Click to collapse
I used the following videos. They have step by step guide:
https://www.youtube.com/watch?v=HbwVsYQajC0
https://www.youtube.com/watch?v=Ai5t2cKEw2E&t=321s&frags=pl,wn
phoenix2393 said:
I used the following videos. They have step by step guide:
&t=321s&frags=pl%2Cwn
Click to expand...
Click to collapse
dang that was helpful:good:
pooniaprashant said:
search the link you posted the op yourself and quote me a better solution resulting in a locked bootloader and camera2api+eis enabled. The only alternative is to press and hold "volume -" button while running "fastboot oem unlock/lock bootloader" to bypass wipe, but as many have tested and pointed out (https://forum.xda-developers.com/showpost.php?p=77250310&postcount=3), this method isnt the most reliable as wipe commands are still there in standby and a wipe is triggered whenever the user will boot into recovery (stock/custom). So neither your post provides any solution to the op other than searching threads for answers which he obviously would have done before typing a separate thread, but also you discredit the only viable tried and tested solution the op has atm, congrats. :good:
Also to the op, if you're interested and are having issues while following my post feel free to quote or pm me, i'll help you.
Click to expand...
Click to collapse
Before blaming others, try to think about what you have suggested
1. you are on August patch, stock ROM, locked bootloader
2. you suggested to downgrade, for example to January ROM
3. so OP will install January ROM, because January ROM doesn't wipe data. But oh no, it got wiped. How's that possible, someone on the Internet told me it's safe!
4. someone on the Internet didn't really realize, that ROM flashing will unlock the bootloader and as you are already on the recent version, it will wipe your data
5. so not only you wipe your data, you downgraded your system for absolutely no reason, congrats. :good:
And if OP is total noob, he should read first and try to understand how things work. Otherwise he will still be a noob and follow whatever stupid advice he gets. But be my guest (result can be seen here https://forum.xda-developers.com/mi-a1/help/mi-a1s-destroyed-locked-please-help-t3839928)..
_mysiak_ said:
Before blaming others, try to think about what you have suggested
4. someone on the Internet didn't really realize, that ROM flashing will unlock the bootloader and as you are already on the recent version, it will wipe your data
.
Click to expand...
Click to collapse
and specifically where did i said that? and that "blaming" thing, who's even talking to you let alone blame you. I came here just to interact with the op or some other intellectual arguments that seem necessary, not this useless crap which i dont have any interest indulging in
---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------
AlvinKyo said:
dang that was helpful:good:
Click to expand...
Click to collapse
if pressing volume down button while unlocking bootloader was used in this tutorial, remember to backup data before an ota and do not boot into recovery without data backup
pooniaprashant said:
and specifically where did i said that? and that "blaming" thing, who's even talking to you let alone blame you. I came here just to interact with the op or some other intellectual arguments that seem necessary, not this useless crap which i dont have any interest indulging in
Click to expand...
Click to collapse
Dude, just read what you wrote (hint, second post in this topic). "the best bet is to miflash an older update. the one that doesnt wipe everything when changing bootloader status". You suggested a method which will wipe his data and I only corrected you. Then you brought some personal b**** into this (just re-read what you posted as you obviously forget very quickly)
Btw. if you quote me, you're talking to me. If you don't want to talk to me, don't quote me and don't respond to me. As simple as that Have a nice day/night/whatever.
_mysiak_ said:
Dude, just read what you wrote (hint, second post in this topic). "the best bet is to miflash an older update. the one that doesnt wipe everything when changing bootloader status". You suggested a method which will wipe his data and I only corrected you. Then you brought some personal b**** into this (just re-read what you posted as you obviously forget very quickly)
Btw. if you quote me, you're talking to me. If you don't want to talk to me, don't quote me and don't respond to me. As simple as that Have a nice day/night/whatever.
Click to expand...
Click to collapse
I was talking about the stock ROM, I was telling the op to flash the stock ROM that doesn't wipe everything when changing bootloader status so that he can enable EIS and relock the bootloader and no wipe will be triggered that would cause that persist commands to revert. Unlocking bootloader is meant to wipe data and there's no way around it other than the "hacks" which will delay the wipe.
Sent from my Mi A1 using Tapatalk
pooniaprashant said:
Omg! Idiot I was talking about the stock ROM, I was telling the op to flash the stock ROM that doesn't wipe everything when changing bootloader status so that he can enable EIS and relock the bootloader and no wipe will be triggered that would cause that persist commands to revert. Unlocking bootloader is meant to wipe data and there's no way around it other than the "hacks" which will delay the wipe. Why you even comment on something when you don't even get it what the person is saying?
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
That escalated quickly.. If people don't understand you, maybe it's not their fault. Try to think about it. Good bye.
_mysiak_ said:
That escalated quickly.. If people don't understand you, maybe it's not their fault. Try to think about it. Good bye.
Click to expand...
Click to collapse
I am sorry to talk that way, I was sleepy and the notifications kept waking me up irritating the hell out of me. I have edited the comment to make it social, sorry buddy.
Sent from my Mi A1 using Tapatalk
pooniaprashant said:
I was talking about the stock ROM, I was telling the op to flash the stock ROM that doesn't wipe everything when changing bootloader status so that he can enable EIS and relock the bootloader and no wipe will be triggered that would cause that persist commands to revert. Unlocking bootloader is meant to wipe data and there's no way around it other than the "hacks" which will delay the wipe.
Click to expand...
Click to collapse
That's more clear now and makes sense
Related
Disregard
jmz768 said:
There are a lot of us out there that are not comfortable attempting the recently discovered root method and would love to see a one click solution. Any word?
Click to expand...
Click to collapse
No way without an unlocked bootloader. Since you have to unlock your bootloader to root, you can do them both by following these guides!
http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
http://forum.xda-developers.com/showpost.php?p=66386870&postcount=501
disregard
jmz768 said:
Someone isn't paying attention.
Click to expand...
Click to collapse
Apparently you're not because he answered your question
disregard
jmz768 said:
Well no he didn't. I made it very clear that I did not want to go through the recently discovered process to obtain root. Since unlocking the bootloader is the first part of the process to obtain root, it shouldn't take a genius IQ to understand that I'm talking about the process as a whole, not just the second half of it.
Go troll somewhere else, kid.
Click to expand...
Click to collapse
You obviously don't understand what it takes and with that attitude you will not receive help around here.
Sent from my SM-N910V using XDA Free mobile app
I'm no expert but I've done the conversion process. It seems a bit too complex to create a toolkit or one-click method. If I had to predict, I would say no one is going to create a one-click process.
I can tell you that the rooting portion is the easy process. Once you unlock the bootloader and flash TWRP, you can simply flash one of the few pre-rooted ROMs
Sent from my SM-N910V using Tapatalk
---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------
Sadly you'll have to follow one of the guides to achieve root. Took me one try and about 10 minutes of my time. Really not that difficult if you follow the instructions accurately.
Sent from my SM-N910V using Tapatalk
disregard
It already is one click to obtain root. You just need to go through the unlock process first. It's really pretty easy.
Just read over the guide a few time, and make sure everything is downloaded and ready to go.
Mine worked first time without issue. Only took maybe 10 minutes once I started. I read through the guide several times before I started just so I was sure I understood everything and didn't miss any steps.
Me, Honestly Annoying, and 4 others are working getting root, and fastboot working on our device. As far as where we are at (as of this post), fastboot pulls up on the phone and the computer recognizes it, most fastboot commands work, but the ones involving unlocking the bootloader don't work. On every file we have tried up to this point, except for the userdebug I posted a bit ago we get file "signature verification failed", but that is due to a locked bootloader. we have been working nonstop to get the fastboot to function in our device so we can unlock our bootloader. If, and I mean if, this works right, it will easily be applied to quite a few devices. so, in short, we are working on it. We will release the files we have once we are SURE that they work like they are supposed to.
Just don't ask how long it's gonna take to be completed, cuz we honestly don't know. But we are working almost night and day to get this done
For real... Been day and night on this one
If anyone has any ACTUAL questions (ie. not an ETA), please ask them. If you would like to offer ACTUAL help (ie. not "I will test your root method" because there is none to test) please tell us here! Also, @autoprime you have been strangely quiet about all of this, can you offer some insight about where we are? It would be much appreciated
Let me know if there's any help I can render!
solitarywarrior1 said:
Let me know if there's any help I can render!
Click to expand...
Click to collapse
what's the exact model number of your device (I.E. LGLS992)?
schizoidd said:
what's the exact model number of your device (I.E. LGLS992)?
Click to expand...
Click to collapse
LGLS992
solitarywarrior1 said:
LGLS992
Click to expand...
Click to collapse
check your inbox for a skype join link.
UPDATE: modified the aboot and it booted... stay tuned for more
Can I buy yall a pizza or beer or something while you work?
INCREDIBLE WORK YOU GUYS
Sent from my LGLS992 using XDA-Developers mobile app
Honestly Annoying said:
UPDATE: modified the aboot and it booted... stay tuned for more
Click to expand...
Click to collapse
Nice!!! Are you sure it actually didn't just rewrite aboot during boot to the stock aboot? And what was modified on your aboot?
fiddy619 said:
Nice!!! Are you sure it actually didn't just rewrite aboot during boot to the stock aboot? And what was modified on your aboot?
Click to expand...
Click to collapse
We don't think so, though we will have to do some testing on that...
And schizoid cross edited the T-Mobile aboot with our aboot to see if the fastboot commands will work, we're still testing that
---------- Post added at 05:10 PM ---------- Previous post was at 04:42 PM ----------
Calling @thecubed @IllegalArgument @autoprime... we could really use your guys help on this. We're actually making some progress with this device and would love for you to be involved
Here to help
Also willing to help the cause via pizza ? or anything for that matter
fiddy619 said:
Nice!!! Are you sure it actually didn't just rewrite aboot during boot to the stock aboot? And what was modified on your aboot?
Click to expand...
Click to collapse
We checked, it definitely isn't writing the aboot back when it boots. Still won't recognize unlock commands though...
you haven't explained what's being done so there's not much to comment on.
good luck to you guys tho. :good:
autoprime said:
you haven't explained what's being done so there's not much to comment on.
good luck to you guys tho. :good:
Click to expand...
Click to collapse
Can I add you to our Skype chat? I think it would be easier to explain that way
Honestly Annoying said:
Can I add you to our Skype chat? I think it would be easier to explain that way
Click to expand...
Click to collapse
sorry, never have and never will use Skype.
I'll chat on any public XDA thread or #LG-IRC on Freenode IRC.
How are you getting fasboot, wiping recovery or laf? flashed another devices aboot?
you mention changing aboot... you have directly edited the stock Sprint LS992 aboot.img? Or flashed another devices aboot?
autoprime said:
sorry, never have and never will use Skype.
I'll chat on any public XDA thread or #LG-IRC on Freenode IRC.
How are you getting fasboot, wiping recovery or laf? flashed another devices aboot?
you mention changing aboot... you have directly edited the stock Sprint LS992 aboot.img? Or flashed another devices aboot?
Click to expand...
Click to collapse
No worries... this is OK
A while back Tungkick made me a TOT that booted into fastboot. Don't know what she did to edit it, but it works. However it did not recognize ANY fastboot commands, but once I enabled userdebug by editing the build.prop it started to recognize some of them. As far as aboot goes, that's all @schizoidd and I'll let him explain
ok so what has been edited and done. i looked at our aboot and compared it to tmobile's and noticed a few things were missing like the "welcome to fastboot" and a few other things. and on ours, there was some random characters that were in ours but not in t-mobile's nor on the verizon one, so on the stock edited, i just deleted that code. and like Honestly Annoying said, it booted without an issue. i also created another file with tmobile and sprint's aboot merged together and it also booted.
the things done on the merged aboot, sprint encryption, keysand a few other things, tmobile everything else. i have the files but will not upload to here until i know what's all going on
@autoprime ^^^ last post explains what we're doing
I have nougat already and was expecting for a easier way to unlock bootloader than in Marshmallow so I waited for it. Now with Nougat I see it very impossible to root or get Lineage. So can someone please do a guide for my problem please?
Lscastro2000 said:
I have nougat already and was expecting for a easier way to unlock bootloader than in Marshmallow so I waited for it. Now with Nougat I see it very impossible to root or get Lineage. So can someone please do a guide for my problem please?
Click to expand...
Click to collapse
Lots of guides already.
It's the same process. Downgrade bootloader to unlockable version, unlock, flash TWRP, flash ROM, flash Gapps. Pays to read and search player.
I agree readling through all these threads its mass confusion. Some say it works with nougat some say it bricks there devices. Is there a simple one click root like wugfresh has with the nexus devices
z45123qqq said:
I agree readling through all these threads its mass confusion. Some say it works with nougat some say it bricks there devices. Is there a simple one click root like wugfresh has with the nexus devices
Click to expand...
Click to collapse
I am in the same boat :c . lineage root. Magisk root . SuperSU root. No one explains
Lscastro2000 said:
I have nougat already and was expecting for a easier way to unlock bootloader than in Marshmallow so I waited for it. Now with Nougat I see it very impossible to root or get Lineage. So can someone please do a guide for my problem please?
Click to expand...
Click to collapse
Try axon7toolkit, it is supposed to work with all devices
---------- Post added at 03:31 AM ---------- Previous post was at 03:30 AM ----------
z45123qqq said:
I agree readling through all these threads its mass confusion. Some say it works with nougat some say it bricks there devices. Is there a simple one click root like wugfresh has with the nexus devices
Click to expand...
Click to collapse
yeep, axon7toolkit. Actually bkores (the man behind the tool) was based on wugfresh's stuff if I recall correctly
CLaudioman2009 said:
I am in the same boat :c . lineage root. Magisk root . SuperSU root. No one explains
Click to expand...
Click to collapse
Many guides explains very well. If you are unsure about what you are going to do with your device then my advice is that you stay on stockrom until you understand and know what you are up to.
Smedslund said:
Many guides explains very well. If you are unsure about what you are going to do with your device then my advice is that you stay on stockrom until you understand and know what you are up to.
Click to expand...
Click to collapse
This kind of answers are sh** . if you want to be helpful just give us a link or don't answer . thanks
CLaudioman2009 said:
This kind of answers are sh** . if you want to be helpful just give us a link or don't answer . thanks
Click to expand...
Click to collapse
Well to be fair you can just look things up for yourself. He does have a point, stay on the stock rom so you can learn more about the device. Read all the guides that you can find. No need to be rude, thank you.
CLaudioman2009 said:
This kind of answers are sh** . if you want to be helpful just give us a link or don't answer . thanks
Click to expand...
Click to collapse
Oh okay, let's just assume that you know what EDL mode, DFU mode, and FTM mode are. And that you know what happens if you get a DFU brick, what is the solution... Read a bunch of guides and help threads before doing anything, especially if this is your only phone or if you can't use the warranty
To be fair, there isn't a guide for using MiFlash to downgrade the device from Nougat to MM.
I'd suggest you look for the MiFlash download link in the Download Center sticky and then download the necessary MM ROM for your device.
From then on you can just follow a guide to unlock the bootloader using axon7tool and install twrp etc.
greencartim said:
Well to be fair you can just look things up for yourself. He does have a point, stay on the stock rom so you can learn more about the device. Read all the guides that you can find. No need to be rude, thank you.
Click to expand...
Click to collapse
Or you can assume people asking that here ddidnt fimd a good guide or thread about and just help posting a link.
Or be a mor** and say... Yeah yeah. "Use google" answers. What is his 4chan?
---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------
zaphy42 said:
To be fair, there isn't a guide for using MiFlash to downgrade the device from Nougat to MM.
I'd suggest you look for the MiFlash download link in the Download Center sticky and then download the necessary MM ROM for your device.
From then on you can just follow a guide to unlock the bootloader using axon7tool and install twrp etc.
Click to expand...
Click to collapse
This is a good answer.
Again with the rudeness, no need for that friendo. Since you really want a link, here it is http://bfy.tw/CdYq.
greencartim said:
Again with the rudeness, no need for that friendo. Since you really want a link, here it is http://bfy.tw/CdYq.
Click to expand...
Click to collapse
Very nice, but I think his problem is that he needs to downgrade to Marshmallow before he even attempts to unlock the bootloader.
I'm an A2017G user, not a 2017/2017U user, so it might be slightly different for you guys (didn't think it was?), but I believe that you can't unlock the bootloader if your device is already on Nougat, it must be downgraded first.
zaphy42 said:
Very nice, but I think his problem is that he needs to downgrade to Marshmallow before he even attempts to unlock the bootloader.
I'm an A2017G user, not a 2017/2017U user, so it might be slightly different for you guys (didn't think it was?), but I believe that you can't unlock the bootloader if your device is already on Nougat, it must be downgraded first.
Click to expand...
Click to collapse
Yes you do need to downgrade, there's a toolkit that does everything for you and I believe it was mentioned a few times in this thread.
Ok, go easy on me.
Since the upgrade from Lollipop to 6 my verizon Samsung S5 was slower with lag but still bearable. However after today's security patch its so slow it's almost unusable. How can I force it back to Lollipop?
I know almost nothing about rooting/JB but willing to learn something new as long I don't brick it. I just don't understand the terms and risks and process. Where do I start?
Thank you.
S.Dan
Verizon S5 16mb
Build#: MMB29M.G900VVRU2DQF2
Hardware Ver: G900V.05
Emmc: 11xxxxx
Sdanbow said:
Ok, go easy on me.
Since the upgrade from Lollipop to 6 my verizon Samsung S5 was slower with lag but still bearable. However after today's security patch its so slow it's almost unusable. How can I force it back to Lollipop?
I know almost nothing about rooting/JB but willing to learn something new as long I don't brick it. I just don't understand the terms and risks and process. Where do I start?
Thank you.
S.Dan
Verizon S5 16mb
Build#: MMB29M.G900VVRU2DQF2
Hardware Ver: G900V.05
Emmc: 11xxxxx
Click to expand...
Click to collapse
Go into settings ->storage ->internal storage ->cached data, ->delete. Restart your phone. I assure you a newer version of Android is not the reason your phone is slowing down.
Rumsfield said:
Go into settings ->storage ->internal storage ->cached data, ->delete. Restart your phone. I assure you a newer version of Android is not the reason your phone is slowing down.
Click to expand...
Click to collapse
That was first thing I did, then booted in to save mode but neither made a difference. It was fine utill I accepted the update yesterday morning. After it installed it has been EXTREMELY slow. As i type this it lags on key presses. It was definitely the update.
Rumsfield said:
Go into settings ->storage ->internal storage ->cached data, ->delete. Restart your phone. I assure you a newer version of Android is not the reason your phone is slowing down.
Click to expand...
Click to collapse
It's impressive that on so many forums everywhere people decide they need to only give their own opinion of situations instead of answering original poster's questions.
While I'm also skeptical that an official update would be the cause such a massive slowdown on his phone, that's not really what he asked to be addressed, even if the answer may be obvious to some.
Sdanbow said:
Ok, go easy on me.
Since the upgrade from Lollipop to 6 my verizon Samsung S5 was slower with lag but still bearable. However after today's security patch its so slow it's almost unusable. How can I force it back to Lollipop?
I know almost nothing about rooting/JB but willing to learn something new as long I don't brick it. I just don't understand the terms and risks and process. Where do I start?
Click to expand...
Click to collapse
Unfortunately as your S5 has the Toshiba chipset (emmc of 11) there is no way to downgrade the firmware to Lollipop or KitKat. The bootloader is locked. You are out of luck unless you or someone else figures out an exploit.
You can start here: https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909 This explains in a good bit of depth the current status of Verizon S5 bootloaders.
Other than that, just start searching and googling. It's probable that someone else has a similar issue as you. And like Rumsfield said, it's highly unlikely that an official update (which is what it sounds like you have) would be the cause of such a dramatic change in your phone's speed, so it would be worthwhile to investigate further. Have you deleted your dalvik/cache in the recovery? Have you done a hard reset? These are things you have to do before you blame the firmware, and if you have done already, it's a good idea to mention that in your original post so that you avoid unnecessary responses.
Good luck!
delfuhd said:
It's impressive that on so many forums everywhere people decide they need to only give their own opinion of situations instead of answering original poster's questions.
While I'm also skeptical that an official update would be the cause such a massive slowdown on his phone, that's not really what he asked to be addressed, even if the answer may be obvious to some.
Unfortunately as your S5 has the Toshiba chipset (emmc of 11) there is no way to downgrade the firmware to Lollipop or KitKat. The bootloader is locked. You are out of luck unless you or someone else figures out an exploit.
You can start here: https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909 This explains in a good bit of depth the current status of Verizon S5 bootloaders.
Other than that, just start searching and googling. It's probable that someone else has a similar issue as you. And like Rumsfield said, it's highly unlikely that an official update (which is what it sounds like you have) would be the cause of such a dramatic change in your phone's speed, so it would be worthwhile to investigate further. Have you deleted your dalvik/cache in the recovery? Have you done a hard reset? These are things you have to do before you blame the firmware, and if you have done already, it's a good idea to mention that in your original post so that you avoid unnecessary responses.
Good luck!
Click to expand...
Click to collapse
Its impressive how you think you are some sort of voice for the internet police. I doubt its the update and deep down you do too. Just trying to help the guy avoid making a mistake by downgrading.
Don't everyone start throwing stones at me all at one time k
Rumsfield said:
Its impressive how you think you are some sort of voice for the internet police. I doubt its the update and deep down you do too. Just trying to help the guy avoid making a mistake by downgrading.
Click to expand...
Click to collapse
I have a very uneducated question to ask, don't or do The FOTA logs in the recovery menu contain all check values and patch notes old - new? Again bare with my lack of knowledge on this topic but if pushed ota and still in log can it be pulled although maybe enough info alone in log for aboot and other values as far a checks but can it be modified even with filler as what it looks like on a battery self check and re injected through command as OTA? Last question before I'm stone to death for being the forum idiot here...if something is odexed and after the patch now labeled an 8 digit number kinda like Cid or emmc or whatever the long as chipset number for instance has the another value as an I'd in the middle of it can it inturn be reversed so parameters are matched and verified and possibly editited? Thanks
---------- Post added at 07:23 PM ---------- Previous post was at 06:24 PM ----------
Oh. Forgot to ask I didn't see a check after the
command: "/sbin/recovery" "--update_package=/cache/fota/update.zip" "--carry_out=open_fota" "--locale=en_us"
Is that a forced allowable command? The real last question and believe me I have searched threads with no luck but the mention of a dev phone and aboot.mdn
Is the recovery file system table
0/boot emmc/dev/block/platform/msm_sscc.1/by-name/boot (/dev/block/mmcblk0p15) 0
1/ ect...
2/ect..
If the 0 is a 1 would that turn any phone into dev phone or allowable options
And noticed the checks were against the chipset and matching verizon fw although att and tmo had 0 values if values were 1''s would that allow you to you the right matching chipset for att and it's fw tmo ect.. or even the 15mmc instead of the 11?
u.s.marine said:
I have a very uneducated question to ask, don't or do The FOTA logs in the recovery menu contain all check values and patch notes old - new? Again bare with my lack of knowledge on this topic but if pushed ota and still in log can it be pulled although maybe enough info alone in log for aboot and other values as far a checks but can it be modified even with filler as what it looks like on a battery self check and re injected through command as OTA? Last question before I'm stone to death for being the forum idiot here...if something is odexed and after the patch now labeled an 8 digit number kinda like Cid or emmc or whatever the long as chipset number for instance has the another value as an I'd in the middle of it can it inturn be reversed so parameters are matched and verified and possibly editited? Thanks
---------- Post added at 07:23 PM ---------- Previous post was at 06:24 PM ----------
Oh. Forgot to ask I didn't see a check after the
command: "/sbin/recovery" "--update_package=/cache/fota/update.zip" "--carry_out=open_fota" "--locale=en_us"
Is that a forced allowable command? The real last question and believe me I have searched threads with no luck but the mention of a dev phone and aboot.mdn
Is the recovery file system table
0/boot emmc/dev/block/platform/msm_sscc.1/by-name/boot (/dev/block/mmcblk0p15) 0
1/ ect...
2/ect..
If the 0 is a 1 would that turn any phone into dev phone or allowable options
And noticed the checks were against the chipset and matching verizon fw although att and tmo had 0 values if values were 1''s would that allow you to you the right matching chipset for att and it's fw tmo ect.. or even the 15mmc instead of the 11?
Click to expand...
Click to collapse
No idea what you are actually asking because you are talking like a terminator sent back to April 11, 2014 to start some sort of war about a very old phone. Obviously triggered so hard you made a new account.
Rumsfield said:
No idea what you are actually asking because you are talking like a terminator sent back to April 11, 2014 to start some sort of war about a very old phone. Obviously triggered so hard you made a new account.
Click to expand...
Click to collapse
Huh? I was just asking a question? New account? Must have me mistaken sir. I was curious about this phone what options there were after the update to gain root access I have never chimed in as I was trying to read all past and present post on this topic kind of gets a little confusing one would think outdated post and procedures would be deleted or timestamped to where if the method dosent work anymore why have it up unless only as a reference. But thank you sir for no guidance or help at all.
After marshmallow update I am no longer able to view any logs in the recovery menu.
Sent from my SM-G900V using Tapatalk
u.s.marine said:
Huh? I was just asking a question? New account? Must have me mistaken sir. I was curious about this phone what options there were after the update to gain root access I have never chimed in as I was trying to read all past and present post on this topic kind of gets a little confusing one would think outdated post and procedures would be deleted or timestamped to where if the method dosent work anymore why have it up unless only as a reference. But thank you sir for no guidance or help at all.
Click to expand...
Click to collapse
You were asking a question that was very convoluted from a "new" account, turns out you created it like 3 years ago and never posted. You quoted my response to someone else asking your question which to me made no sense, hence my weird response to you. I still don't understand why you are posting in this thread with that question unless you are trolling.
---------- Post added at 09:36 AM ---------- Previous post was at 09:33 AM ----------
lemew said:
After marshmallow update I am no longer able to view any logs in the recovery menu.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
What are you using for recovery? I have two S5's now running
twrp-3.1.0-1-klte.img.tar 9.5M 2017-04-27 21:54:26 EDT which were flashed via ODIN with no issues.
Sdanbow said:
Ok, go easy on me.
Since the upgrade from Lollipop to 6 my verizon Samsung S5 was slower with lag but still bearable. However after today's security patch its so slow it's almost unusable. How can I force it back to Lollipop?
I know almost nothing about rooting/JB but willing to learn something new as long I don't brick it. I just don't understand the terms and risks and process. Where do I start?
Thank you.
S.Dan
Verizon S5 16mb
Build#: MMB29M.G900VVRU2DQF2
Hardware Ver: G900V.05
Emmc: 11xxxxx
Click to expand...
Click to collapse
Ok so first your warranty is void (gone) also make sure you backup your phone like photos etc take screenshots of needed text messages also your phone has an 11 CID (I sadly have one to) Like you mentioned which is not unlockable so we have to go back to Lollipop to root and what do you get with root you get the ability to flash custom Touchwiz based roms anything aosp/cm/linage wont work because our bootloader is locked and there is no current exploit to unlock them there is alot of Touchwiz based roms available I added screen shots on how my S5 looks I'm running Alliance rom I have added the themes from an older version of Alliance rom and added Viper4arise Viper4arise is a really cool sound mod it gives you increddible sound there is also xposed framework now if your interested in rooting download the drivers http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows extract the zip and run the exe then download odin from https://androidfilehost.com/?fid=673368273298975100 extract the zip and run odin now power off your phone and hold Volume Down + Home + Power then click Volume Up To Accept then plug your phone into your computer make sure it shows Up in Blue in the top left in Odin Should say something like "COM" now download https://androidfilehost.com/?fid=673368273298975100 that is your lollipop tar.md5 download that and extract the zip now click AP in odin and select that tar.md5 you extracted from the zip odin might freeze but its verifying the file once its verified click start this Should downgrade the phone now you might have to pull the battery if the phone wont boot afterwards (stuck on Red Verizon Screen) and boot into recovery by powering off the device (Pull the battery) and then Holding Volume UP + Home + Power untill you see "Recovery booting" in the top left now use the Volume buttons to scroll and power to select go Down to Wipe Data / Factory Reset and click power button once its highlighted now use Volume buttons to go Down to Yes and click Power to select it when it is finished click power when Reboot now is highlighted now root the phone using this guide https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529 or this one https://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370 if you ever need help you can Private Message me on XDA.
You can even go back to kitKat and safestrap will work But you have to root 5.0 First here is a guide I made https://forum.xda-developers.com/ve...al/how-to-install-kitkat-lolipop-pb1-t3589151
Rumsfield said:
You were asking a question that was very convoluted from a "new" account, turns out you created it like 3 years ago and never posted. You quoted my response to someone else asking your question which to me made no sense, hence my weird response to you. I still don't understand why you are posting in this thread with that question unless you are trolling.
---------- Post added at 09:36 AM ---------- Previous post was at 09:33 AM ----------
What are you using for recovery? I have two S5's now running
twrp-3.1.0-1-klte.img.tar9.5M2017-04-27 21:54:26 EDT which were flashed via ODIN with no issues.
Click to expand...
Click to collapse
I have never rooted or modified my phone.
Sent from my SM-G900V using Tapatalk
rgr
Rumsfield said:
You were asking a question that was very convoluted from a "new" account, turns out you created it like 3 years ago and never posted. You quoted my response to someone else asking your question which to me made no sense, hence my weird response to you. I still don't understand why you are posting in this thread with that question unless you are trolling.
---------- Post added at 09:36 AM ---------- Previous post was at 09:33 AM ----------
What are you using for recovery? I have two S5's now running
twrp-3.1.0-1-klte.img.tar 9.5M 2017-04-27 21:54:26 EDT which were flashed via ODIN with no issues.
Click to expand...
Click to collapse
understandable. no i usually have not ran into many problems before. as it has been years since i messed with these phones and decided to mess with them again alot has changed i updated one of them and was looking for a way back being it has the 11xxx toshiba chip. as far as replying to quote i have never posted before i just thought i was replying to thread or whatever but just glad i received a response lol. i was just curious i was looking in the recovery menu at the logs from the FOTA update that i accidentally accepted. noticed they were very detailed which i thought was unusual. Again very very detailed like source code or whatever the raw format is called and was curious if it could be pulled with an adb command. the second part was a shell script whatever excuse my ignorance when it comes to this but after they were ran they were checked/verified or whatever and showed values that must have been met, which lead me to ask about is there a way to use adb to unlock the boatloader as an update.zip? thanks
The Current Latest TWRP for the v10 H901, v3.2.1, done by TWRPbuilder, was missing many options and settings,
For the most part it worked, but screen settings was wrong, my device about overheated and I like to have my screen
blink off after 60 secs..
So I took the latest STOCK N source and used the twrpbuilder.jar file to create a device tree from the STOCK Recovery..
edited the device tree to allow everything to work like it should. then built TWRP, tested and works......
Downloads:
twrp_v3.2.1_recovery_pplus-H901_210180529.tar.xz
NOTE:This is not a Flashable FILE, Make sure you extract it first: Its a ".img" file:
Device Source:https://github.com/LG-V10/v10_pplus-H901_TWRP_device
If anyone remembers me, I did hold on to my v10 this whole time.. but as I said before, the famous LG Bootloop got my V10, and LG fully Replaced it free of charge and it came back with Nougat, which means No root,
I seen that someone came up with root for it.. so I finally rooted it.. but needed to fix that twrp you all had....
also I sold my HTC10, after doing everything I could over there.. I got tired of HTC, and wanted to give LG another chance.. some say im crazy, but I love challenges..
anyhow I also bought a LG G6 for a good price....... and im not sure if I will get the g7 yet.. still going to wait a bit and see what happends.......
I just hope my freshly built TWRP seems to work better for you all that try it.......
Since I left v10 a while back, I also started a ROM, Yeah, PureFusionOS is mine.. I was main Founder of it......... with over 10k installs.
Dont believe me? Look for your self: https://stats.purefusionos.com/
We havent done much since last year.. but just now currently working on updates and kinda waiting on P.................
maybe I can bring it to this device.. who knows..
Nice to have you back!
Sent from my LG-H901 using Tapatalk
Eliminater74 said:
If anyone remembers me, I did hold on to my v10 this whole time.. but as I said before, the famous LG Bootloop got my V10, and LG fully Replaced it free of charge and it came back with Nougat, which means No root,
I seen that someone came up with root for it.. so I finally rooted it.. but needed to fix that twrp you all had....
also I sold my HTC10, after doing everything I could over there.. I got tired of HTC, and wanted to give LG another chance.. some say im crazy, but I love challenges..
anyhow I also bought a LG G6 for a good price....... and im not sure if I will get the g7 yet.. still going to wait a bit and see what happends.......
I just hope my freshly built TWRP seems to work better for you all that try it.......
Since I left v10 a while back, I also started a ROM, Yeah, PureFusionOS is mine.. I was main Founder of it......... with over 10k installs.
Dont believe me? Look for your self: https://stats.purefusionos.com/
We havent done much since last year.. but just now currently working on updates and kinda waiting on P.................
maybe I can bring it to this device.. who knows..
Click to expand...
Click to collapse
I'm on Android 7.0...how u guys flashing twrp? My bootloader is unlocked but fails when flashing any twrp via pc. Any advice?
jerryspring said:
I'm on Android 7.0...how u guys flashing twrp? My bootloader is unlocked but fails when flashing any twrp via pc. Any advice?
Click to expand...
Click to collapse
LG removed the fastboot flash commands starting with mm, leaving us with an unlockable bootloader that we can do nothing with.
This is the only working twrp install for nougat. https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942
Read, Read, Read.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
LG removed the fastboot flash commands starting with mm, leaving us with an unlockable bootloader that we can do nothing with.
This is the only working twrp install for nougat. https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942
Read, Read, Read.
Click to expand...
Click to collapse
I said....my bootloader IS unlocked! U read read read
jerryspring said:
I said....my bootloader IS unlocked! U read read read
Click to expand...
Click to collapse
I never said it wasn't. I was only explaining that LG removed the flashing commands from fastboot (they only left us with the unlock command and a few other non destructive commands (like getvar)), and that you will need to thoroughly read read read the thread I linked and follow the instructions to a T or you will run the risk of bricking your phone. LG really made it easy to brick this phone if you don't know what you are doing. That thread does state that you shouldn't brick, but if you don't get it right you'll have to flash the kdz (which is linked in another thread somewhere) to start over.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
I never said it wasn't. I was only explaining that LG removed the flashing commands from fastboot (they only left us with the unlock command and a few other non destructive commands (like getvar)), and that you will need to thoroughly read read read the thread I linked and follow the instructions to a T or you will run the risk of bricking your phone. LG really made it easy to brick this phone if you don't know what you are doing. That thread does state that you shouldn't brick, but if you don't get it right you'll have to flash the kdz (which is linked in another thread somewhere) to start over.
Click to expand...
Click to collapse
I tried VM. But I'm on Vista...I can only chose 32 bit
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
I was thinking...if we could get temp root....we can use flashify or rshr to flash twrp.....? I had to do that on a TMobile gs4
jerryspring said:
I tried VM. But I'm on Vista...I can only chose 32 bit
Click to expand...
Click to collapse
Please use the proper thread for help. This one is only for this build of twrp itself, the other one is for installing twrp. That is where people can help you with using the bootable FWUL usb flash drive img.
Sent from my Moto Z (2) using XDA Labs
Why would you hide the twrp behind such a crazy filetype?
skywalker-live said:
LG removed the fastboot flash commands starting with mm, leaving us with an unlockable bootloader that we can do nothing with.
This is the only working twrp install for nougat. https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942
Read, Read, Read.
Click to expand...
Click to collapse
Also, how is this o.p twrp to be flashed? No instructions....?
jerryspring said:
Also, how is this o.p twrp to be flashed? No instructions....?
Click to expand...
Click to collapse
Once you have the other twrp installed (https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942) boot to twrp and flash the twrp.img from this thread after you extract it from the .tar. The same way you would upgrade any twrp, so really no instructions needed. You could also substitute this .img in those instructions. Once you've rooted a few different kinds of phones some of these kinds of things will make sense to you and just become second nature. Don't get discouraged, you'll get it.
Sent from my Moto Z (2) using XDA Labs
i could use some help about other thread. im not getting t he options. like 64 bit and the such. could you help? thanks
---------- Post added at 07:00 PM ---------- Previous post was at 06:56 PM ----------
i am not getting any of these options
"Login. The password is: linux
In the VM Open Firefox (It is the little icon 4 to the right of the arrow ) and download TWRP for the H901: https://forum.xda-developers.com/tmo...-h901-t3765971
Open a terminal (click on the blue arrow thing) and select Terminal Emulator"
skywalker-live said:
Once you have the other twrp installed (https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942) boot to twrp and flash the twrp.img from this thread after you extract it from the .tar. The same way you would upgrade any twrp, so really no instructions needed. You could also substitute this .img in those instructions. Once you've rooted a few different kinds of phones some of these kinds of things will make sense to you and just become second nature. Don't get discouraged, you'll get it.
Click to expand...
Click to collapse
I already know. I been rooting for years.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
skywalker-live said:
Once you have the other twrp installed (https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942) boot to twrp and flash the twrp.img from this thread after you extract it from the .tar. The same way you would upgrade any twrp, so really no instructions needed. You could also substitute this .img in those instructions. Once you've rooted a few different kinds of phones some of these kinds of things will make sense to you and just become second nature. Don't get discouraged, you'll get it.
Click to expand...
Click to collapse
Can't we flash this img with fastboot? Be the same difference
jerryspring said:
I already know. I been rooting for years.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Can't we flash this img with fastboot? Be the same difference
Click to expand...
Click to collapse
If your on any firmware above 10c LG only gave us the fastboot unlock command, the fastboot boot and fastboot flash commands have been removed. This has been stated many times and in many threads. It has also been stated before to use the proper threads for asking questions, which is one of the rules of xda.
This thread is for the development of this version of twrp.
Those of us that have been rooting since day 1 understand that every phone is different and rooting evolves with the tighter security from the oems. Many of us started with windows phones here on xda before Android was born, or nokia "smart" phones before that.
Sent from my Moto Z (2) using XDA Labs
Honestly if you have to ask how to install twrp, I wouldn't recommend flashing it at all....
if you been doing this for years, then you would know that how to install it requires ROOT or some special way since this is the T-mo threads meaning H901,
BTW peepz, if you think gaining root for the v10 is a trick in its self, try the G6 way.. talk about risky business there.. by the same person..............
NOTE: that doesnt mean TRY the G6 way on the v10,
anyhow. you can flash twrp through your already made recovery or some app that has root......
I flashed this twrp through the recovery that I get when I used the ROOT method on latest ROM......................
I just didnt like the fact that half the options were missing........... I did do another build.. but I didnt release that yet on here.....
if anyone is still having issues, maybe I should upload the other build for you to try..
Eliminater74 said:
Honestly if you have to ask how to install twrp, I wouldn't recommend flashing it at all....
if you been doing this for years, then you would know that how to install it requires ROOT or some special way since this is the T-mo threads meaning H901,
BTW peepz, if you think gaining root for the v10 is a trick in its self, try the G6 way.. talk about risky business there.. by the same person..............
NOTE: that doesnt mean TRY the G6 way on the v10,
anyhow. you can flash twrp through your already made recovery or some app that has root......
I flashed this twrp through the recovery that I get when I used the ROOT method on latest ROM......................
I just didnt like the fact that half the options were missing........... I did do another build.. but I didnt release that yet on here.....
if anyone is still having issues, maybe I should upload the other build for you to try..
Click to expand...
Click to collapse
I'm just having issues on the steps. Some of the steps don't go with my PC, nor do I get the things posted on about the icons 4 and clicking the icons that's posted on the o.p.
---------- Post added at 01:33 AM ---------- Previous post was at 01:29 AM ----------
Eliminater74 said:
Honestly if you have to ask how to install twrp, I wouldn't recommend flashing it at all....
if you been doing this for years, then you would know that how to install it requires ROOT or some special way since this is the T-mo threads meaning H901,
BTW peepz, if you think gaining root for the v10 is a trick in its self, try the G6 way.. talk about risky business there.. by the same person..............
NOTE: that doesnt mean TRY the G6 way on the v10,
anyhow. you can flash twrp through your already made recovery or some app that has root......
I flashed this twrp through the recovery that I get when I used the ROOT method on latest ROM......................
I just didnt like the fact that half the options were missing........... I did do another build.. but I didnt release that yet on here.....
if anyone is still having issues, maybe I should upload the other build for you to try..
Click to expand...
Click to collapse
I'm not asking how to flash TWRP...I am asking hypothetical questions. Sorry to offend
See?
anyone ever try the klick it toolkit?
---------- Post added at 01:24 AM ---------- Previous post was at 01:09 AM ----------
too bad that we couldnt downgrade to mm. that would be so much easier. lol
I just got hit with the infinite bootloop on my device unfortunately, and modified this twrp image to only use the little cluster: https://www.androidfilehost.com/?fid=818222786056035329 . The cmdline additions are only: maxcpus=4 boot_cpus=0-3. Just in case anyone else wants it
Edit: given the prevalence of this bug, I'd honestly recommend people just keep a 4core twrp flashed on their device for if/when they run into it so it's easier to deal with.