Related
OK so we got a SE Experia Arc S LT18i with 1253-8238_4.0.1.A.0.165 ('prototype' model on loan from a friend = prehistoric!) and looking into upgrading the thing if at all possible.
So if I am correct it's a case of: 1st: Root, 2nd: Unlock bootloader, 3rd: Install recovery, 4th: Flash ROM of choice
Bootloader is locked and phone not rooted.
Tried using Flashtool to root phone but it is greyed out so tried Tools > Root > Force zergRush = fail, (not tried Force psneuter/Emulator ?)
Tried unlocking bootloader using Flashtool, but this also failed (SE unlock website wanted IMEI code one digit less than the phone reports?!! got a code by ditching the first 0 of the IMEI, but didn't work anyway - crashed phone)
Attempted to root using command line ADB method to push zergRush and execute the script, but this too doesn't work (phone crashes and reboots).
Fastboot? I have it installed but not yet come across any how-to's that use this (did I say yet? )
The apps available on Play Store seem to be automations of above methods for one-click users.
Further exhaustive reading/searching here and on talk.sonymobile.com leads me to believe that the first step might be to flash a different kernel version before it's possible to root, after which everything else should fall into place...I'm up for trying this but of course don't want to risk bricking the phone, so backing up first would be a good plan, *but* I need root to be able to install recovery! I know enough about booting operating systems to know that changing kernel version with a locked boot loader might just result in bork! This is where the expertise of you guys comes in!! Maybe you know that flashing another (similar?) kernel will be fine with Fashtool even without unlocking bootloader and rooting phone? Perhaps I missed a simple and easy way of rooting? Any suggestions very welcome - thanks in advance!
FYI: *I only run Linux* so pointing me at any of the windows tools on offer is of no help to me
Oh and PS: yes I have searched and found a ton of helpful info, well actually *way too much* info to the point of saturation and confusion!! :laugh:
There can never be too much information, yours and others problem is that you try rushing through it, because if you didn't you'd find the answers you were looking for.
Sent from my CM9'd Arc
XperienceD said:
There can never be too much information, yours and others problem is that you try rushing through it, because if you didn't you'd find the answers you were looking for.
Sent from my CM9'd Arc
Click to expand...
Click to collapse
Well it's not the quantity of info, but the quality of info! Failing that the filtration system used to distill the good stuff out!
Anyroads, I was still hoping for someone to chip in with something like "Yeah go for it, that will work fine"! or "Don't do it, try this instead"!
I'm believing from my readings so far, that short of flashing an incorrect radio, or interrupting a flash process, it isn't easily possible to brick an Arc?
acesabe said:
Anyroads, I was still hoping for someone to chip in with something like "Yeah go for it, that will work fine"!
Click to expand...
Click to collapse
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
acesabe said:
it isn't easily possible to brick an Arc?
Click to expand...
Click to collapse
No, you would just use the flashtool to flash a stock ROM.
XperienceD said:
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
Click to expand...
Click to collapse
Well, that's because you are XperienceD!
No, you would just use the flashtool to flash a stock ROM.
Click to expand...
Click to collapse
Ok cool, so Flashtool can be used to save an unbootable device too then...
acesabe said:
Well, that's because you are XperienceD!
Click to expand...
Click to collapse
It's how I got to be experienced. :silly:
acesabe said:
Ok cool, so Flashtool can be used to save an unbootable device too then...
Click to expand...
Click to collapse
Yep, you just need to flash a stock ROM.
XperienceD said:
I would have just tried it instead of starting a thread to ask, failing that I would have then read the stickys/guides explaining how to unlock and root.
Click to expand...
Click to collapse
Me too.
Thread closed.
Hello
My phone's screen is stuck at opening htc logo. I never rooted it - shall I just flash it with standard stock rom? Would you please be so kind to point me in the right direction? Bless...
My kindest regards
Pete
Try booting without the sd card.
How old is the phone? What happened / did you do (if such is the case) for it to get like that? Etc.....
Sent from a dream.
Teichopsia said:
Try booting without the sd card.
How old is the phone? What happened / did you do (if such is the case) for it to get like that? Etc.....
Sent from a dream.
Click to expand...
Click to collapse
Tried that before without result...also did a factory reset but to no avail. Phone was just over a year old when it happened, got it from my insurance policy so it's possibly a refurbished one. I can't remember doing anything to cause this...
phosphen said:
Tried that before without result...also did a factory reset but to no avail. Phone was just over a year old when it happened, got it from my insurance policy so it's possibly a refurbished one. I can't remember doing anything to cause this...
Click to expand...
Click to collapse
You Need to provide the Cid number and the Main Version. Do You know how to Get that?
glevitan said:
You Need to provide the Cid number and the Main Version. Do You know how to Get that?
Click to expand...
Click to collapse
Sorry, no idea...
phosphen said:
Sorry, no idea...
Click to expand...
Click to collapse
Ok, enable USB debugging, plug the phone to the PC and then open a CMD ON the PC and type adb reboot-bootloader and once in bootloader type fastboot getvar all. You Need to post the INFOcidnum and INFOmain
How old is your phone? Isn't there still any warranty? If so you may try to contact your reseller, service provider or the manufacturer. If not glevitan may be your hero
glevitan said:
Ok, enable USB debugging, plug the phone to the PC and then open a CMD ON the PC and type adb reboot-bootloader and once in bootloader type fastboot getvar all. You Need to post the INFOcidnum and INFOmain
Click to expand...
Click to collapse
Sorry mate, I was offline for a whole day, just managed to get back on it
How can I enable USB debugging if I can get onto HBOOT menu only? Is it possible to switch it on from there? Saludos
phosphen said:
Sorry mate, I was offline for a whole day, just managed to get back on it
How can I enable USB debugging if I can get onto HBOOT menu only? Is it possible to switch it on from there? Saludos
Click to expand...
Click to collapse
Yes, from fastboot, plug the phone (You will see fastboot USB in red) type: fastboot getvar all
sounds like a boot loop?
try removing the battery, once you have done that re boot into boot loader from there you should see an option for recovery.you may want to do a full wipe and re flash the rom.:silly: keep in mind the initial flash normally will take the longest,best to leave it be for a few minutes while the phone adjust to the new settings,that sometimes will seem like you may have an issue, but patience most times is all that is needed.hope this helps.
rdub504 said:
try removing the battery, once you have done that re boot into boot loader from there you should see an option for recovery.you may want to do a full wipe and re flash the rom.:silly: keep in mind the initial flash normally will take the longest,best to leave it be for a few minutes while the phone adjust to the new settings,that sometimes will seem like you may have an issue, but patience most times is all that is needed.hope this helps.
Click to expand...
Click to collapse
It's not rooted, so I don't think that will work.
bananagranola said:
It's not rooted, so I don't think that will work.
Click to expand...
Click to collapse
excellent point,but if that's true what is he flashing?
rooted phone=flash capable non rooted =stock rom with no admin access. am i mistaken,if so slap me and call me susan,if not box that thing up and bring it back,and if that's not an option then warranty time.because that device is chap.
rdub504 said:
excellent point,but if that's true what is he flashing?
rooted phone=flash capable non rooted =stock rom with no admin access. am i mistaken,if so slap me and call me susan,if not box that thing up and bring it back,and if that's not an option then warranty time.because that device is chap.
Click to expand...
Click to collapse
Hello susan
Sent from a dream.
Teichopsia said:
Hello susan
Sent from a dream.
Click to expand...
Click to collapse
LOL,I guess i'm susan and my face now hurt.can you please elaborate a bit so i can also understand what i am missing.
rdub504 said:
LOL,I guess i'm susan and my face now hurt.can you please elaborate a bit so i can also understand what i am missing.
Click to expand...
Click to collapse
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Sent from a dream.
Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Bullet point,impressive. now a refurb with s off would mean a root from a previous owner?
"S-ON, which means it blocks you from flashing radio images — the code that manages your data, Wi-Fi and GPS connections. Switching your phone to S-OFF lets you flash new radios. Rooting doesn’t require S-OFF, but many rooting tools will give you S-OFF in addition to root access" So hince my question if attempting to flash a rom ,it would be a safe bet he would be rooted,because without it he would have no admin access,recovery or superser access and would not be able to complete the flash process.a factory reset would normally on a stock rom not result in a loss of the entire stock rom but only a loss off data i.e contacts apps etc. and with these things in mind it would seem to be a safe to assume its a hardware issue or a rooted refurb phone from a previous owner in a bootloop becauce a factory reset there would wipe everything?
Click to expand...
Click to collapse
Factory reset resets the phone to it's "as fabricated"-condition, wich means it wipes user data and cache on the phone. With or without root the procedure is the same and should usally not affect /system or /boot.
So we have to find out, if the phone is S-On/S-Off (phosphen, more information on the topic can be read for example here, second post).
Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Sent from a dream.
Click to expand...
Click to collapse
rdub504 said:
Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Bullet point,impressive. now a refurb with s off would mean a root from a previous owner?
"S-ON, which means it blocks you from flashing radio images — the code that manages your data, Wi-Fi and GPS connections. Switching your phone to S-OFF lets you flash new radios. Rooting doesn’t require S-OFF, but many rooting tools will give you S-OFF in addition to root access" So hince my question if attempting to flash a rom ,it would be a safe bet he would be rooted,because without it he would have no admin access,recovery or superser access and would not be able to complete the flash process.a factory reset would normally on a stock rom not result in a loss of the entire stock rom but only a loss off data i.e contacts apps etc. and with these things in mind it would seem to be a safe to assume its a hardware issue or a rooted refurb phone from a previous owner in a bootloop becauce a factory reset there would wipe everything?
Click to expand...
Click to collapse
Cfhappy said:
Factory reset resets the phone to it's "as fabricated"-condition, wich means it wipes user data and cache on the phone. With or without root the procedure is the same and should usally not affect /system or /boot.
So we have to find out, if the phone is S-On/S-Off (phosphen, more information on the topic can be read for example here, second post).
Click to expand...
Click to collapse
Sorry guys, but before hijacking this thread maybe you can go and follow the discussion in the off topic thread. The idea here is to lend a hand to someone that is stuck and a noob and this for certain not helping him. Let's keep it clean....
BTW, the only solution in his case is to flash the OEM RUU or make a goldcard and flash an unbranded rom. With no s-off there´s no other way.
Click to expand...
Click to collapse
I couldn't resist.
Maybe it's good practice for him to read through all to learn to discern right info from wrong.
Sent from a dream.
Teichopsia said:
I couldn't resist.
Maybe it's good practice for him to read through all to learn to discern right info from wrong.
Sent from a dream.
Click to expand...
Click to collapse
Yeah, that is right, but with the phone stuck in the splash I don´t think is a good time to think about learning. This experience will definitely be worth for him in the future. :victory:
Hello guys,
I have a problem with my Galaxy Google Nexus GT-I9250 ! Of course, the update for 4.3 JB came up on my phone. When I pressed the button to install it, after a few second the installation stopped. It said : "Installation aborted" and then "Signature Verification Failed" . I tried to search through the other forums and threads, but as I`m a kind of a newbie with that technology I would be really pleased if someone explain me how to fix that, maybe, silly problem.
Oh, and also what is this thing named OTA.zip ?
Thanks.
It's exactlly the same thing that's happening to me
I opened a new thread but didn't include that detail, but it cant update.
irvingh30 said:
It's exactlly the same thing that's happening to me
I opened a new thread but didn't include that detail, but it cant update.
Click to expand...
Click to collapse
yes..hopefully someone explain us how to fix it... :\
stefangrozev68 said:
Hello guys,
I have a problem with my Galaxy Google Nexus GT-I9250 ! Of course, the update for 4.3 JB came up on my phone. When I pressed the button to install it, after a few second the installation stopped. It said : "Installation aborted" and then "Signature Verification Failed" . I tried to search through the other forums and threads, but as I`m a kind of a newbie with that technology I would be really pleased if someone explain me how to fix that, maybe, silly problem.
Oh, and also what is this thing named OTA.zip ?
Thanks.
Click to expand...
Click to collapse
something you have on your phone isnt stock. thats why it fails.
what did you modify on your phone?
Zepius said:
something you have on your phone isnt stock. thats why it fails.
what did you modify on your phone?
Click to expand...
Click to collapse
Well, I recently rooted the phone. There is also SuperSU on it.. I don`t know whether this changes something.
Zepius said:
something you have on your phone isnt stock. thats why it fails.
what did you modify on your phone?
Click to expand...
Click to collapse
In my case I bought it like this, how can i know if something is not stock?
you mean i have to go back to stock and flash it again through Odin?
I saw a post from someone here showing how to do that, but i wasn't quite sure either...
stefangrozev68 said:
Well, I recently rooted the phone. There is also SuperSU on it.. I don`t know whether this changes something.
Click to expand...
Click to collapse
depends on if you changed something else. if you just have root, no. but if you installed busybox, i know it modifies some system files
http://forum.xda-developers.com/showthread.php?t=1626895
follow that. easiest way to go back to stock. if you dont want to lose you data, just dont flash userdata.img
DONT USE ODIN.
Zepius said:
depends on if you changed something else. if you just have root, no. but if you installed busybox, i know it modifies some system files
http://forum.xda-developers.com/showthread.php?t=1626895
follow that. easiest way to go back to stock. if you dont want to lose you data, just dont flash userdata.img
DONT USE ODIN.
Click to expand...
Click to collapse
My Phone is encrypted, does that make any difference?
irvingh30 said:
My Phone is encrypted, does that make any difference?
Click to expand...
Click to collapse
In a short answer, yes. The OTA update needs to verify that the software on your phone matches what it needs to update. This is why you will get a "signature verification failed" message. If you phone is encrypted, the OTA updater will not be able to verify that software. Decrypt your phone, once complete goto settings - about phone - system updates and retry to download and install the OTA update.
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
Let's keep this simple guys... If you want the OTA update to work properly and reliably you must be completely stock. No root, no mods, no encryption, no nothing! Most people having issues with the OTA not working fail to mention some little mod they installed making them not "completely stock".
jaizero said:
[/COLOR]Let's keep this simple guys... If you want the OTA update to work properly and reliably you must be completely stock. No root, no mods, no encryption, no nothing! Most people having issues with the OTA not working fail to mention some little mod they installed making them not "completely stock".
Click to expand...
Click to collapse
this and always this. there have been so many of these threads i feel like im on repeat
I don't know about any mods or anything I just bought the phone a few months ago.
The screen shot may throw a little more light here and tell you guys exactly what I have.
Sent from my Galaxy Nexus using xda app-developers app
But how?
jaizero said:
In a short answer, yes. The OTA update needs to verify that the software on your phone matches what it needs to update. This is why you will get a "signature verification failed" message. If you phone is encrypted, the OTA updater will not be able to verify that software. Decrypt your phone, once complete goto settings - about phone - system updates and retry to download and install the OTA update.
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
Let's keep this simple guys... If you want the OTA update to work properly and reliably you must be completely stock. No root, no mods, no encryption, no nothing! Most people having issues with the OTA not working fail to mention some little mod they installed making them not "completely stock".
Click to expand...
Click to collapse
Sorry for my ignorance here again man
but, how do I do that, do you mean i have to factory reset the phone..?
Everything went successfully! Thank you all friends!! :highfive:
Hello, I rooted using this method: www .youtube .com/watch?v=GiZ7D2zjJdA (sorry xda wont let me post links)
The root worked fine all was well until I tried setting a font using a font installer, when I set the font the phone shut off rebooted and is now just sitting at the AT&T icon which I think is called a boot loader. I am running Android 4.3 which has knox and this bootloader. I can get into the stock recovery by vol up + power + home and I can "wipe data/factory reset" would this work? I just want my mistake fixed im so mad at myself for doing this I am not a pro at this at all and im scared of what to do, I really need someones help.... can kies update the phone and fix it? or can I wipe data/factory reset? All my phone has is just root, no cwm and stuff.
Please help someone!
Are my threads seen? Seems like no one ever replies to anything I post. Anyways I tried to wipe the data and factory reset and it did not work, I also tried booting into safe mode and still no luck. I need someones help please.
Thanks
what is your firmware version?? 4.3 OTA or 4.3 Leak?
Gotnitro said:
Are my threads seen? Seems like no one ever replies to anything I post. Anyways I tried to wipe the data and factory reset and it did not work, I also tried booting into safe mode and still no luck. I need someones help please.
Thanks
Click to expand...
Click to collapse
you need to provide more information. What recovery your using and what version, what rom, bootloader version, how you rooted your phone, etc etc. Also, the search bar is your friend.
We all have lives outside of XDA we cant post a response as soon as a new thread comes up. Be patient. Like I said, do a little searching while your waiting for a response instead of waiting for someone to do it for you.
Mojar7070 said:
you need to provide more information. What recovery your using and what version, what rom, bootloader version, how you rooted your phone, etc etc. Also, the search bar is your friend.
We all have lives outside of XDA we cant post a response as soon as a new thread comes up. Be patient. Like I said, do a little searching while your waiting for a response instead of waiting for someone to do it for you.
Click to expand...
Click to collapse
The YouTube link is what I used to root. I have stock everything.Open a new phone out of a box use the method I used in the YouTube link in the first post and that's what I have. I'm not trying to make people search for me. Im lost, I don't know even of what to search.... All I know is I have OTA 4.3 and I have a sgh-i747. A guy on YouTube told me to just get a official 4.3 firmware for the gs3 and flash it. Problem is I don't know where to get that... I've been searching for 3 days now.. Maybe im not searching the right place? Also guys my post from before I wasent trying to be rude, I'm sorry... Im just mad that I did this to my phone and I'm needing your help.
Gotnitro said:
The YouTube link is what I used to root. I have stock everything.Open a new phone out of a box use the method I used in the YouTube link in the first post and that's what I have. I'm not trying to make people search for me. Im lost, I don't know even of what to search.... All I know is I have OTA 4.3 and I have a sgh-i747. A guy on YouTube told me to just get a official 4.3 firmware for the gs3 and flash it. Problem is I don't know where to get that... I've been searching for 3 days now.. Maybe im not searching the right place? Also guys my post from before I wasent trying to be rude, I'm sorry... Im just mad that I did this to my phone and I'm needing your help.
Click to expand...
Click to collapse
Bump
Gotnitro said:
Hello, I rooted using this method: www .youtube .com/watch?v=GiZ7D2zjJdA (sorry xda wont let me post links)
The root worked fine all was well until I tried setting a font using a font installer, when I set the font the phone shut off rebooted and is now just sitting at the AT&T icon which I think is called a boot loader. I am running Android 4.3 which has knox and this bootloader. I can get into the stock recovery by vol up + power + home and I can "wipe data/factory reset" would this work? I just want my mistake fixed im so mad at myself for doing this I am not a pro at this at all and im scared of what to do, I really need someones help.... can kies update the phone and fix it? or can I wipe data/factory reset? All my phone has is just root, no cwm and stuff.
Please help someone!
Click to expand...
Click to collapse
did you finally foun your answer that you where searching for? if not i know a method to unroot the phone and put back to 4.3
email me if so : [email protected]
Since your are running 4.3, you cannot flash anything newer older than 4.3. Do not flash any 4.1.1 or 4.1.2 ROM as this will make matters worse. ATT never released a complete stock 4.3 ROM that could be flashed via Odin. You can try to debrick it using this thread: http://forum.xda-developers.com/showthread.php?t=2549068
Edit: According to another thread, DO NOT USE Kies to re-install the firmware. It WILL BRICK your phone.
Can you get into download mode? Has the Knox counter been tripped? If it hasn't been tripped, maybe you could get it repaired under warranty. If it's been tripped, you can still try to get it repaired under warranty. Just be prepared for Samsung to refuse warranty service because Knox has been tripped.
[Q&A] [ROOT / TWRP][D851 ONLY][OSX/Linux/Windows] Root/TWRP your TMO G3 with PurpleD
Q&A for [ROOT / TWRP][D851 ONLY][OSX/Linux/Windows] Root/TWRP your TMO G3 with PurpleDrake!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT / TWRP][D851 ONLY][OSX/Linux/Windows] Root/TWRP your TMO G3 with PurpleDrake!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
will there be an update to the PurpleDrake method on the D851 with the new 10m update? for it to work properly?
YOu can still get rooted if u are on 10m. I did. It wont exit properly so u will need to pull the battery after it is done.
Nsx93 said:
YOu can still get rooted if u are on 10m. I did. It wont exit properly so u will need to pull the battery after it is done.
Click to expand...
Click to collapse
Correct. However, it does not install TWRP, nor the custom Boot.IMG to prevent triggering the root counter. I too would like to see an update to include these items.
tribalartgod said:
Correct. However, it does not install TWRP, nor the custom Boot.IMG to prevent triggering the root counter. I too would like to see an update to include these items.
Click to expand...
Click to collapse
I see your concern.. you can manually install twrp but i have no idea bout the boot.img
i did all except that. Someone mentioned you can flash back to stock and it will fix the root counter. If you ever need to send in your phone that is... but i do understand its easier if this would be one package kind of thing.
IDK how to even check that yet. LOL. I have already rooted and unrooted, just to familiarize myself with the process.
Does this root method work on the t-mobile D851 10M
johnny quest said:
Does this root method work on the t-mobile D851 10M
Click to expand...
Click to collapse
Yes, but as stated above, it will glitch. The glitch just freezes on the permaroot steps. Once this happens, removing the battery and rebooting still keeps your device rooted. With 10M, currently, you will have to manually install TWRP. I recommend downloading the IMG file online, and using Flashify to flash it.
tribalartgod said:
Yes, but as stated above, it will glitch. The glitch just freezes on the permaroot steps. Once this happens, removing the battery and rebooting still keeps your device rooted. With 10M, currently, you will have to manually install TWRP. I recommend downloading the IMG file online, and using Flashify to flash it.
Click to expand...
Click to collapse
Thank you for the response. Do you think its worth rooting since 5.0 is coming out soon? I still want to root but will I have to unroot in order to get the 5.0 upgrade? or better yet, will the LG get the upgrade any time soon. Sorry for these questions. And also, since this phone has the top notch camera resolution, will rooting affect the camera?
johnny quest said:
Does this root method work on the t-mobile D851 10M
Click to expand...
Click to collapse
johnny quest said:
Thank you for the response. Do you think its worth rooting since 5.0 is coming out soon? I still want to root but will I have to unroot in order to get the 5.0 upgrade? or better yet, will the LG get the upgrade any time soon. Sorry for these questions. And also, since this phone has the top notch camera resolution, will rooting affect the camera?
Click to expand...
Click to collapse
I unrooted to ensure I get the update. If you are rooted, and have not turned off OTA, you might get the OTA, and it might break something. I personally like the LG camera better than any other so far. Another reason I went back to stock. Rooting and keeping the stock OS, should leave the camera alone. If you flash a different ROM, your mileage may vary.
We should be getting 5.0 before the end of the year, officially. LINK
tribalartgod said:
I unrooted to ensure I get the update. If you are rooted, and have not turned off OTA, you might get the OTA, and it might break something. I personally like the LG camera better than any other so far. Another reason I went back to stock. Rooting and keeping the stock OS, should leave the camera alone. If you flash a different ROM, your mileage may vary.
We should be getting 5.0 before the end of the year, officially. LINK
Click to expand...
Click to collapse
I really appreciate your response. Thank you I will make sure that I have OTA on and maybe root and leave stock.
LG G3 D851: Root before or after Lollipop
My question is do I root now while on Android 4.4.2 or will I be safe to wait until after Lollipop has rolled out? I really want root but I'm afraid that it may not be an option after the update. Any guidance will be appreciated! Thanks in advance!
Waiting for device...
Hey, sorry to bug you. I cannot seem to get past Waiting for device...
I've installed the recommended drivers package, I've made sure it's in PTP mode, USB debugging connected, drivers appear to've installed properly: nothing. Just sits there.
Anything I could be missing? D851 running 4.4.2, Windows 7
SAMMMMMM said:
Hey, sorry to bug you. I cannot seem to get past Waiting for device...
I've installed the recommended drivers package, I've made sure it's in PTP mode, USB debugging connected, drivers appear to've installed properly: nothing. Just sits there.
Anything I could be missing? D851 running 4.4.2, Windows 7
Click to expand...
Click to collapse
Did you change the port number in device manager?
tribalartgod said:
Did you change the port number in device manager?
Click to expand...
Click to collapse
No, perhaps I didn't. Is there a long and detailed explanation of how to use this rooting tool? The first post doesn't mention anything about a port change.
SAMMMMMM said:
No, perhaps I didn't. Is there a long and detailed explanation of how to use this rooting tool? The first post doesn't mention anything about a port change.
Click to expand...
Click to collapse
My apologies, that's for restoring stock... I see in your posts, you have it set to PTP... Mine was set to MTP. While "waiting for device" was on screen, I unplugged and replugged the phone. Aside from that, seems like you have done everything else properly...
Anyone else having issues making backups of AOSP ROMs? The backup folder is empty.
---------- Post added at 05:16 PM ---------- Previous post was at 04:55 PM ----------
datdirtyscrew said:
Anyone else having issues making backups of AOSP ROMs? The backup folder is empty.
Click to expand...
Click to collapse
Looks like its only when backing up to external SD. Internal backs up fine.
tribalartgod said:
My apologies, that's for restoring stock... I see in your posts, you have it set to PTP... Mine was set to MTP. While "waiting for device" was on screen, I unplugged and replugged the phone. Aside from that, seems like you have done everything else properly...
Click to expand...
Click to collapse
I mean I'd be more frustrated if I wasn't waiting for lollipop to drop, so I'm shelving this for now, but I hope it isn't a persistent nag.
Sent from my SM-N900T using XDA Free mobile app
PurpleDrake issue
i was just rooting my G3 with purpledrake, and while it was doing the permaroot part, purpledrake closed on my computer and now my phone is stuck on a screen showing a red hand with a cross through it and a usb cord plugged into the side of a phone. What should i do?