Related
I got my G2 D802 (International model) about 4 weeks ago, and rooted it almost immediately. It has been working great so far, but today I decided to try the latest CM nightly - and that's where I have hit a stumbling block.
I tried first by installing ROM Manager (5.5.3.0, latest version at the time I am writing). Under Recovery Setup, I found that I supposedly had already installed both ClockwordMod Recovery and TWRP. I honestly don't recall installing either one, but the options were available. I tried to "Reboot into Recovery" first with CWM, then with TWRP - both times, after the initial LG logo, I was greeted by the broken android with the red triangle. I also tried to reinstall CWM by choosing the corresponding option "Install or Update Recovery"), but the result was always the same. Each time, I was able to restart the phone, which is still working fine.
I then decided to flash a new CWM. I downloaded CWM Touch, then used Flashify to flash the new image and reboot the phone. This time, the boot process stopped after the LG logo appeared, but an error appeared right above it. I repeated the process two more times (once with CWM Touch and once with the default CWM), and the message that I read was something like:
Code:
Secure booting error
Error: Boot Certification Verify!
At this point, I am wondering if the problem might be a locked bootloader, or if it might be something else altogether. Could someone please point me in the right direction? I am not exactly a noob, as I used to root and flash my Nexus devices in the past. After a couple of years using Asus Padfones, however, I am a little rusty.
I have the exact same problem, I installed CWM using rom manager after rooting the phone.
---------- Post added at 08:16 AM ---------- Previous post was at 07:50 AM ----------
FIXED - Just use this method - http://forum.xda-developers.com/showthread.php?t=2500441
Just installed CWM Touch using this method, took me less than 2 minutes... works perfect.:good::good:
Someone should really write to lg about unlocking the bootloader.
Sent from my LG-D802 using xda app-developers app
j0sh1 said:
I have the exact same problem, I installed CWM using rom manager after rooting the phone.
---------- Post added at 08:16 AM ---------- Previous post was at 07:50 AM ----------
FIXED - Just use this method - http://forum.xda-developers.com/showthread.php?t=2500441
Just installed CWM Touch using this method, took me less than 2 minutes... works perfect.:good::good:
Click to expand...
Click to collapse
I just got around to trying what you suggested... it worked perfectly. Thanks!
can you boot in to syste m , i have the same problem , do you know any way to fix it
can you boot in to syste m , i have the same problem , do you know any way to fix it i also cant boot in to system , . .
janukpalm said:
can you boot in to syste m , i have the same problem , do you know any way to fix it i also cant boot in to system , . .
Click to expand...
Click to collapse
Read my post here, and see if it helps.
not working in lg g2. 4.4.2
not working in lg g 2 (d802)...
4.4.2
lohitkumar said:
not working in lg g 2 (d802)...
4.4.2
Click to expand...
Click to collapse
I was having the same issue. I found this nice link that worked like a charm and is VERY easy. If you're rooted, just download the appropriate apk for your device and it will install twrp. I was driving myself crazy earlier trying to fix this and then I find this app AutoRec... Genius!
http://www.droidviews.com/install-twrp-recovery-on-lg-g2-running-android-4-4-2-kitkat/
Hope this helps everybody who's just as frustrated as I was.
I had this issue too.
I had this issue too:
Every time I tried to boot into recovery I got the error from OP. Every time i ran the loki script i got some error about reading aboot. Mind you I could still boot, I just couldn't get into recovery.
I went to this page, downloaded the apk, installed it and let it do the rest.
http://www.droidviews.com/install-twrp-recovery-on-lg-g2-running-android-4-4-2-kitkat/
Hey, this is a long-shot but,
I ended up using the AutoRec KitKat app for the D803 variant and go custom recovery to work that way which let me instal my rom. But the rom I got is acting glitchy and I can't install another one or re-install it since I'm getting this recovery error again and the lolipop version of the AutoRec app isn't for D803.
Any suggestions?? The rom I have seems to switch network type automatically/having a network glitch so I'm disconnecting every couple minutes.
for security boot error, and QHUSB_BULK and many drives showing up. i just used download mode and used flash tools to go back to stock..
An Easy Fix
Here's what worked for me:
-Like all of you I would get the secure boot error. To fix it I decided to reinstall the software from the official LG app on PC (Windows) and it worked!
-You need:
Official LG app on PC
The ability to enter download mode on your phone
A cable to connect the phone to the PC
How to do it:
-Turn of the phone completely, the enter download mode by holding the vol+ button and the inserting the USB cable before it reaches the LG logo (it's precise timing so it may take a few tries). If you did everything right you should get a message saying entering dowload mode and see a screen in which there is a USB logo and progress bar and some other writing. On your PC go to the LG app and it will offer you the latest software update. Do the update. It will download the software the upload it to your phone and after installation it will power on and voila your phone is alive and there is no data loss at all
-I hope this works for all who have this problem and since this is my first reply/post ever I hope it's useful.
Hi guys,
So I'm a little lost. After flashing the 01/05 ParanoidAndroid rom for the D802, I got stuck in a bootloop. So I did a hard reset and entered twrp recovery again. There I flashed the other rom which was working before, but also after that I got stuck in a bootloop. Now I don't know what to do anymore.
I already tried to flash the kdz file, but it didn't work.
Can someone please help me out?
Casparovic said:
Hi guys,
So I'm a little lost. After flashing the 01/05 ParanoidAndroid rom for the D802, I got stuck in a bootloop. So I did a hard reset and entered twrp recovery again. There I flashed the other rom which was working before, but also after that I got stuck in a bootloop. Now I don't know what to do anymore.
I already tried to flash the kdz file, but it didn't work.
Can someone please help me out?
Click to expand...
Click to collapse
According to this: http://forum.xda-developers.com/showthread.php?t=2688144
You can't flash a kdz only a tot, not tried it yet though. Though I'm in the same situation
There is also mention on the PA page that you need an official LG KK modem image to flash after the ROM & GAPPS: http://forum.xda-developers.com/showthread.php?t=2502789
Though that's as far as I've got so far. Will let you know once I've got mine working again.
---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------
There is this: http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop Generic advice on how to fix a boot loop
And this: https://www.youtube.com/watch?v=jZBHZQEI96o which is how to install TWRP and later on in the vid, how to get into TWRP, since I figure if people are looking more info is always better
More as I get it.
praxis22 said:
According to this: http://forum.xda-developers.com/showthread.php?t=2688144
You can't flash a kdz only a tot, not tried it yet though. Though I'm in the same situation
There is also mention on the PA page that you need an official LG KK modem image to flash after the ROM & GAPPS: http://forum.xda-developers.com/showthread.php?t=2502789
Though that's as far as I've got so far. Will let you know once I've got mine working again.
---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------
There is this: http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop Generic advice on how to fix a boot loop
And this: https://www.youtube.com/watch?v=jZBHZQEI96o which is how to install TWRP and later on in the vid, how to get into TWRP, since I figure if people are looking more info is always better
More as I get it.
Click to expand...
Click to collapse
So, you have the exact same problem? I don't know what to do anymore
I will keep on looking, let's keep each other up to date
praxis22 said:
According to this: http://forum.xda-developers.com/showthread.php?t=2688144
You can't flash a kdz only a tot, not tried it yet though. Though I'm in the same situation
There is also mention on the PA page that you need an official LG KK modem image to flash after the ROM & GAPPS: http://forum.xda-developers.com/showthread.php?t=2502789
Though that's as far as I've got so far. Will let you know once I've got mine working again.
---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------
There is this: http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop Generic advice on how to fix a boot loop
And this: https://www.youtube.com/watch?v=jZBHZQEI96o which is how to install TWRP and later on in the vid, how to get into TWRP, since I figure if people are looking more info is always better
More as I get it.
Click to expand...
Click to collapse
The first link you proposed worked for me. Very nice Thnx. You should try it also
Yup, I can get into download mode and TWRP, and I've tried to flash what I had (0430) twice, in various ways. No joy. Now I'm going to try sideloading a file via ADB in TWRP, as I'll need gapps and possibly the LG KK modem too. I'm just documenting it all, so I have a complete workup of what worked and what didn't. I'm sure somebody else will find it useful, (as will I) when it inevitably happens again. Luckily I have my old Galaxy S (Omni 4.4.2) that I can jump my SIM into, so I at least have a phone
Video of somebody unbricking a phone: https://www.youtube.com/watch?v=kqw_LFuyHbE AT&T in this case but the same procedure as above for the d802 in general.
After many hours of diligent back and forth last night, I gave in and restored from a backup, my last stop before flashing back to stock. That actually worked. So I'm back to the point of being rooted with TWRP installed, (Seriously, make a backup) but at least I have still have all my data.
I've actually used the stock LG interface for more time now than I did after I picked up the phone. God it's awful. I can understand that as an OEM, you need sales bullet points, and something to fill a product launch with, as such you largely have to add to what exists in stock android. But I doubt they ever did any UX tests, either that, or the focus group they had were all "normals" who've never seen a smartphone before. But I digress..
I spent most of the time getting adb to work again, and experimenting with that. I re-installed the drivers, available at my first link above. After that nothing seemed to work, so I manually found the 64bit USB installer and ran that, still no joy, then rebooted the PC. Once I reconnected the phone, then the installers kicked in, though MPT failed. But all you really need is the ADB interface.
I also found out that "adb devices" only ever sees the phone when it's booted into the system, and stuck at the boot animation after the LG logo. If I booted into TWRP recovery it, even in sideload mode, Nothing worked.
adb is part of the SDK which you can get from here:
http://developer.android.com/sdk/index.html
Though all you need is a couple of binaries and a few dll's, and you can find all that in IORoot25 here:
http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
File: http://bit.ly/1hPLwsj
These are basic guides for adb:
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/ (basic)
http://www.herongyang.com/Android/adb-push-and-pull-Command.html (push & pull)
http://stackoverflow.com/questions/11074671/adb-pull-multiple-files (advanced pull)
http://www.androidcentral.com/android-201-10-basic-terminal-commands-you-should-know (10 cmds)
The adb shell is UNIX, not DOS, just FYI. these have you covered:
http://forum.xda-developers.com/showthread.php?t=502010
http://developer.android.com/tools/help/adb.html#shellcommands
I used it to upload more PA roms, gapps, etc. None of which worked. regardless of how I did it. Dirty or clean, (with the exception of fully wiping data.) I found the most useful functionality was the command, adb reboot recovery, which will drop you directly into TWRP without the need for the Vulcan handshake. Which is often frustrating, a bit hit & miss, at least for me.
I tried to flash 0429, 0430 & 0501, none of them worked, though I was on 0430 when it borked.
Just FYI
NEW 22.21.11 OTA Zip posted on the site 12/1/14
YOU MUST BE ON 22.11.6 TO UPDATE
NEW 22.11.6 OTA Zip posted on the site 11/11/14
http://www.graffixnyc.com/motox.php
OTA is there!
Instructions:
This is ONLY for the XT1095 Pure edition.. Support priority will be given to those with a XT1095. If you have another model number you will have to figure out how/if you can run this OTA. It's not up to this thread to support devices the OTA was not meant for.
IF YOU ARE ON THE FIRST SOAK TEST OTA .5 YOU CANNOT UPDATE TO .6. IT WILL FAIL! YOU WILL HAVE TO DOWNGRADE TO 4.4.4 THEN APPLY THE .6 OTA
Follow @SolarTrans Guide found here: http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
Be unaltered unrooted system. The device cannot be rooted and then unrooted.. it must be a never rooted system or the update will fail. It seems it's failing on devices that were rooted and then unrooted. On devices that were never rooted or where the user had stock back up they made prior to rooting the ota will update fine
Boot into Stock Recovery
ADB Sideload the zip
For people getting the modem error. Make sure you back up your current modem using the DD command (google if you don't know how)
After that download the AT&T modem from my website, flash it, then take the OTA. You MAY lose LTE after the update. If you do just reflash your old modem and you'll be good to go. It's also been confirmed if you reflash the AT&T modem after the update you will get LTE back.
Download Links can be found on my website: http://www.graffixnyc.com/motox.php
Also, please do not PM me for support. PM's will not be answered. Post it in the thread. It helps other's having the same issue find a solution. If it's over PM it only benefits you and not everyone else
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
This is going to sound really nooby but do i just flash this in recovery? Or in the bootloader?
Sorry, this is my first Moto device, have had Nexus and HTC phones before this
Use ADB sideload to flash on a stock unrooted system. Went through perfectly for me and currently optimizing apps. Thanks
jellydroid13 said:
Use ADB sideload to flash on a stock unrooted system. Went through perfectly for me and currently optimizing apps. Thanks
Click to expand...
Click to collapse
So, unroot, flash stock recovery, then go to the bootloader and adb sideload?
THEindian said:
So, unroot, flash stock recovery, then go to the bootloader and adb sideload?
Click to expand...
Click to collapse
yeah but go to recovery and sideload
I'm rooted, but still stock recovery. Can I still boot to stock recovery and sideload?
Also, how do I adb sideload? Can someone explain? I have somewhat of an idea, but want to make sure before I go ahead and do so.
dmbfan13 said:
I'm rooted, but still stock recovery. Can I still boot to stock recovery and sideload?
Also, how do I adb sideload? Can someone explain? I have somewhat of an idea, but want to make sure before I go ahead and do so.
Click to expand...
Click to collapse
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
Go to the SuperSU app, go into the 3rd tab with all the settings, in there, there should be an option, something along the lines of "clean unroot", hit that, it should only take a minute or so
If you still see the SuperSU app once thats done, go into the play store and uninstall it
You are unrooted
To flash, plug in your phone and type in "adb reboot recovery"
You'll the that little android, once you see this, press the UP volume button, then power button, then release
Scroll down to where it says apply update from adb
type in "adb sideload BLAH BLAH BLAH.zip"
It should start applying. Hope this helps!
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!
Can be root achieved?
sent from my Nexus 7
THEindian said:
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
<snip snip>
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!
Click to expand...
Click to collapse
Same thing happened to me. I suppose we'll have to flash stock back?
THEindian said:
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
Go to the SuperSU app, go into the 3rd tab with all the settings, in there, there should be an option, something along the lines of "clean unroot", hit that, it should only take a minute or so
If you still see the SuperSU app once thats done, go into the play store and uninstall it
You are unrooted
To flash, plug in your phone and type in "adb reboot recovery"
You'll the that little android, once you see this, press the UP volume button, then power button, then release
Scroll down to where it says apply update from adb
type in "adb sideload BLAH BLAH BLAH.zip"
It should start applying. Hope this helps!
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!
Click to expand...
Click to collapse
It seems like either the install-recovery.sh file was removed when you unrooted (SuperSU uses that file) or it detects it has been modified and is failing. You will have to ask someone to pull it from a non rooted device
I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.
Is there a guide to re-root?
will I get the next OTA if I sideload the soak test?
just wondering.
Mine is also bricked due to using unroot in supersu....
THEindian said:
I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.
Click to expand...
Click to collapse
I am in the same boat as you.
edwardgtxy said:
Mine is also bricked due to using unroot in supersu....
Click to expand...
Click to collapse
Yeah... mine's in a bootloop that I can't seem to stop. Holding the power button doesn't actually seem to turn it off. The screen goes black... and then eventually it just starts up again.
Im getting an error that says /modem/image/modem.b00 has unexpected contents.
any clues?
matt99017d said:
Im getting an error that says /modem/image/modem.b00 has unexpected contents.
any clues?
Click to expand...
Click to collapse
Same here.
THEindian said:
I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.
Click to expand...
Click to collapse
No, do not mirror my files. I like to keep count of my downloads. Get a better internet connection. I downloaded the file in less than 5 minutes as others did.
It appears you need a non-rooted system image that's never been rooted. You need to be fully stock. Not rooted and then un rooted. I believe the unrooting process still leaves files in an altered state than their original. If there is a single extra character in a file, if it's the slightest smallest difference the file is considered altered and will fail OTA checks.
Quite a few people have tried this and it has worked. It seems the ones it's failing on are ones that were rooted then unrooted. Derek Ross just told me it worked like a charm for him.
any tips to stop the boot loop? I am parking mine in recovery now to drain the battery.
Btw, it seems the OTA modified modem, system and boot. So theoretically, we can just use fastboot to go back to the your imgs, and the phone should still work right?
If anybody can put up a step-by-step guide, or a video that shows how to properly install it all, I'm sure myself, and much of the community would appreciate it.
Recently, my laptop that I had ADB, and every tool imaginable for Androids, and specifically the Galaxy Series, took a huge dump on me and I lost it all. I installed it so long ago, that embarrassingly I've forgotten how I did it all. If someone could post how they rooted their GS7 (non-edge variant), I would be very appreciative. And I'm sure much of the community would be too. I'm embarrassed to even have to ask as someone who used to formerly develop mods on phones. But it is what it is. It's been so long since I've set it all up, and I've had to do so much since that time that I've simply forgotten how I did it/how to do it. Any help would be GREATLY appreciated. Thank you ahead of time...
I've tried following the instructions in the sticky above. I ran the 930X ROOT.TAR in the special version of ODIN. And every ran OK. It said "Success" and then rebooted. All seemed well, then it froze on the AT&T Boot Logo. What can I do from here? I know from history that this is one of the points that people panic and claimed "brick" (though I've never seen a real brick from rooting). Any help would be greatly appreciated
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
twizt3d said:
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
thank you for that. I'll check it out. Hopefully it'll get me past this bootscreen issue
yup. Great instructions. All set rooted now. Now time to play with xposed and V4A and the like. Yay
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
thanirs said:
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
Click to expand...
Click to collapse
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
52brandon said:
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Click to expand...
Click to collapse
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
Click to expand...
Click to collapse
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
Click to expand...
Click to collapse
so you got it all figured out and running great now right? No other issues right?
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
twizt3d said:
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
Click to expand...
Click to collapse
Can you please try restoring to af2?
Thanks for the ping. I think so. One thing I ran into which I don't know if its related to rooting. When I am in a phone conversation, audio on the other end goes in and out after a few minutes into the call. This happens with bluetooth or not. Still figuring out this issue.
52brandon said:
so you got it all figured out and running great now right? No other issues right?
Click to expand...
Click to collapse
Seeing battery drain. So went back to stock /unroot for now.
I was not trying to root my phone but reflash to an earlier version. I tried the Prince version of Odin and it did not work. The version that ended up working is in this thread
http://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930a-edge-variant-afp-stock-t3415344
http://click.xda-developers.com/api...ww.mediafire.com/download/2t...din_3.12.3.rar
Hello everyone actually I have a G360T1 with the latest system update (G360T1UVU1AGP2) and I want to customize my phone, root it and/or install a custom ROM but it's my first time messing around with a Samsung phone and I need some help because I don't want to do something wrong with my phone
BEFORE YOU DO ANYTHING ENABLE DEVELOPER OPTIONS AND ENABLED OEM UNLOCKING AND USB DEBUGGING! Use Chainfires auto root method. Google cf auto root and find the page. Use ctrl-f to search for sm-g360t1 and download the appropriate file (it will be .zip) Extract it (make sure you have USB drivers from Samsung) Put you phone in download more (turn it off, then turn it on while holding home, power, and volume down buttons at the same time. Press the volume up bottom to continue) Run the Odin program and then plug your phone in while in download mode. Make sure it says connected. Next click the AP button in Odin and select the cf auto root .md5 you extracted earlier. Click start. The phone will reboot and root itself. If it seems to restart more than 3 times just pull the battery out and pop it back in. TADAH! YOU'RE NOW ROOTED!
syran123 said:
BEFORE YOU DO ANYTHING ENABLE DEVELOPER OPTIONS AND ENABLED OEM UNLOCKING AND USB DEBUGGING! Use Chainfires auto root method. Google cf auto root and find the page. Use ctrl-f to search for sm-g360t1 and download the appropriate file (it will be .zip) Extract it (make sure you have USB drivers from Samsung) Put you phone in download more (turn it off, then turn it on while holding home, power, and volume down buttons at the same time. Press the volume up bottom to continue) Run the Odin program and then plug your phone in while in download mode. Make sure it says connected. Next click the AP button in Odin and select the cf auto root .md5 you extracted earlier. Click start. The phone will reboot and root itself. If it seems to restart more than 3 times just pull the battery out and pop it back in. TADAH! YOU'RE NOW ROOTED!
Click to expand...
Click to collapse
That sounds pretty easy, but do I need a custom recovery? Also, does this method have any consequences?
Auraburst said:
That sounds pretty easy, but do I need a custom recovery? Also, does this method have any consequences?
Click to expand...
Click to collapse
With this method you do not need a custom recovery. However, I would suggest that you still get one so you can perform backups and restores. There are a few consequences but nothing major. When the phone boots it will have a small line of text that said "set warranty bit: kernel" and also with all rooting processes your warranty will be void.
---------- Post added at 12:09 PM ---------- Previous post was at 12:00 PM ----------
If you have any more questions keep them coming. I've bricked this phone a few times so I know how scary it can be so if I didn't explain something well tell me and I will do better. I would hate for you to brick yours because I said something poorly
syran123 said:
With this method you do not need a custom recovery. However, I would suggest that you still get one so you can perform backups and restores. There are a few consequences but nothing major. When the phone boots it will have a small line of text that said "set warranty bit: kernel" and also with all rooting processes your warranty will be void.
---------- Post added at 12:09 PM ---------- Previous post was at 12:00 PM ----------
If you have any more questions keep them coming. I've bricked this phone a few times so I know how scary it can be so if I didn't explain something well tell me and I will do better. I would hate for you to brick yours because I said something poorly
Click to expand...
Click to collapse
Well, now I understand a little more, just a few questions, which custom recovery should I use? I've read about TWRP is available for this phone, also, what should i avoid to install or do with the stock ROM and don't brick my phone? As I said, it's my first time messing around with a Samsung phone and it's my main and only phone atm
As far as I know TWRP is the only available custom recovery at this time. I would suggest getting the unofficial one created by shinyside because the official one has a few issues. Some things you should not do with this phone is use a reboot app to reboot to things like boot loader and recovery. If you need to access special boot modes such as those I would recommend just using the correct button combo. Also if at some point you want to get xposed make sure you check and double check that it is the version for Samsung phones and your arm version. If you do successfully install the xposed framework make sure the modules you download are for touchwiz/Samsung.My two major pieces of advice though would be to have the stock ROM and Odin on your pc at ALL times. And if you plan on changing any thing on the system (such as build.prop) make sure you do a backup with TWRP. If something goes wrong first try using twrp recover and if that doesn't fix it use Odin. I've bricked this phone several different ways and Odin has always fixed the issues. Mostly just be careful when you see something you want to change. Samsung does a lot of modifications to android so not everything works correctly. However, once you get everything running nice and smooth it is the best thing EVER!
---------- Post added at 03:37 AM ---------- Previous post was at 03:34 AM ----------
To summarize the above post stay away from xposed till your 100% sure of what your doing. Don't use a 3rd party app to restart the phone, you WILL get stuck in a bootloop(this includes xposed modules) Make sure to have a TWRP backup before you change anything. And finally have the stock ROM on your PC at all times (including Odin) so that you can restore at any time. It may suck to reset but it's a lot better than a bricked phone.
I forgot one last thing. When you are leaving the TWRP recovery to go back to android DO NOT let it install supersu. If you do it will brick the phone. Other than that it should work perfectly.
syran123 said:
As far as I know TWRP is the only available custom recovery at this time. I would suggest getting the unofficial one created by shinyside because the official one has a few issues. Some things you should not do with this phone is use a reboot app to reboot to things like boot loader and recovery. If you need to access special boot modes such as those I would recommend just using the correct button combo. Also if at some point you want to get xposed make sure you check and double check that it is the version for Samsung phones and your arm version. If you do successfully install the xposed framework make sure the modules you download are for touchwiz/Samsung.My two major pieces of advice though would be to have the stock ROM and Odin on your pc at ALL times. And if you plan on changing any thing on the system (such as build.prop) make sure you do a backup with TWRP. If something goes wrong first try using twrp recover and if that doesn't fix it use Odin. I've bricked this phone several different ways and Odin has always fixed the issues. Mostly just be careful when you see something you want to change. Samsung does a lot of modifications to android so not everything works correctly. However, once you get everything running nice and smooth it is the best thing EVER!
---------- Post added at 03:37 AM ---------- Previous post was at 03:34 AM ----------
To summarize the above post stay away from xposed till your 100% sure of what your doing. Don't use a 3rd party app to restart the phone, you WILL get stuck in a bootloop(this includes xposed modules) Make sure to have a TWRP backup before you change anything. And finally have the stock ROM on your PC at all times (including Odin) so that you can restore at any time. It may suck to reset but it's a lot better than a bricked phone.
Click to expand...
Click to collapse
syran123 said:
I forgot one last thing. When you are leaving the TWRP recovery to go back to android DO NOT let it install supersu. If you do it will brick the phone. Other than that it should work perfectly.
Click to expand...
Click to collapse
I did it without problems, thanks a lot! :victory:
Something i've noticed after i rooted my phone: Sometimes the system freezes randomly, but is only a issue that happens a few hours after i've rooted, now works as usual
Check out this thread. It has everything you need for this device
http://forum.xda-developers.com/gal...des-faq-one-stop-shop-metropcs-t3266173/page1
I can confirm almost all of these working perfectly as I have this device and it is my daily driver
Hope this helps