First off I already have an unlocked bootloader.
I decided to use the kdz offline flash method to flash all of the kdz versions from first to last starting with the metro v10d then all the way up to the t-mobile v20h so I could get all the firmware updates. Then I used the CMahendra method for installing CWM recovery for unlocked bootloaders where you install lgpwn then flashify and then use flashify to install the cwm image. Now after that I got the security error?! I have an unlocked bootloader why is it doing this?? I flashed the ics uboot boot and recovery after that so I could use s/w upgrade mode to restore stock now back at stock I try again to install cwm and yet again it gives me security error?
Can someone please tell me why?? The cwm image works on my device before you ask I had it installed before.
I think you relocked the bootloader by flashing stock, try unlocking again.
Sent from my LG-P769 using XDA Free mobile app
leereyzhe said:
I think you relocked the bootloader by flashing stock, try unlocking again.
Sent from my LG-P769 using XDA Free mobile app
Click to expand...
Click to collapse
Based on my research the bootoader can never be locked again. I figured it out and it turns out the lookout app that comes packed with the stock T-Mobile kdz was interfering with flashing the recovery. After it bricked again I reflashed the stock V20H kdz then I disabled the lookout app, rooted with CMahendra method for unlocked bootoaders then I installed busybox and Rashr Flash Tool and used that to flash the CWM 6.0.4.9 and then installed Kang 4.4.4 latest + gApps and it was fixed after that!
I love this phone!
Lookout security, ew. :thumbdown:
Hey, what exactly was the benefit of flashing through the stock roms tho?
Sent from my LG-P769 using XDA Free mobile app
leereyzhe said:
Lookout security, ew. :thumbdown:
Hey, what exactly was the benefit of flashing through the stock roms tho?
Sent from my LG-P769 using XDA Free mobile app
Click to expand...
Click to collapse
Because I'm paranoid of firmware level rootkits/malware and I wanted to try something. I got super root access and took sha256 hashes of everything in ./ then I flashed all the firmware kdz packs from 10b to 20h, after that I installed kang and retook the hashes. Many were different proving that core firmware code was changed on the previous install. So now I'm reading through the code in files that have the differences and I found where the malware was phoning home. It was pretty sophisticated due to me not being able to use NetworkLog to see where in my previous install... probably an encrypted RAT in one of the apk I pirated lol.
Oh i see, so, if my phone came with V20H am i good? (i'm paranoid too.)
Sent from my LG-P769 using XDA Free mobile app
leereyzhe said:
Oh i see, so, if my phone came with V20H am i good? (i'm paranoid too.)
Sent from my LG-P769 using XDA Free mobile app
Click to expand...
Click to collapse
Not necessarily. If you download and install pirated apks like from unknown sources you run the risk of installing malware amd if you have root it's possible for that malware to get root and inject itself into firmware code that is nonspecific to devices. The way it usually works is you have people that put up cracked versions of apks like on youtube or piratebay for instance and those people create encrypted stubs from their RAT software and inject it/bind it to the APK. This kind of malware is really hard to detect because it is encrypted and it evades all antimalware software because the antimalware software can't even read it. The malware is usually a RAT and can bind itself to the kernel or any other process or application that is allowed to send/receive packets in the network/app firewall. So even if the apk is blocked from network it will still be able to report back to the C&C server. The person operating the C&C can view your screen in realtime and get a remote root shell on your device. This kind of malware is also rampant in google play store as well. So you have to be careful and only use FOSS from sources like f-droid, but even then you're still not guaranteed 100% security from it. Malware like this is really bad because they can get all of the information on the device 24/7 even if it's powered down. Phone security is a big issue
and you should be cautious of custom roms as well because the devs could easily write a backdoor in it. Kang for this by dhiru seems ok so far though. Hell even Sony, LG and several other manufacturers have been caught spying on their customers with firmware rootkits in their products.
Creepy. I don't recall ever installing anything shady but it's better to be safe.
Just flash them all with UpTestEX right? what else would you recommend? (besides not installing those apks )
leereyzhe said:
Creepy. I don't recall ever installing anything shady but it's better to be safe.
Just flash them all with UpTestEX right? what else would you recommend? (besides not installing those apks )
Click to expand...
Click to collapse
I'm still writing a guide on the subject. This guide will give you ultimate security. Should be done maybe in a week.
from what you described I don't think you have a unlocked bootloader...what it shows in S/W mode...if it doesn't show unlocked bootloader in S/W mode, then your bootloader is locked...I suspect it is the case, as the steps you mentioned don't unlock boot loader (e.g. lgpwn..it only roots your device)
CygnusBlack said:
First off I already have an unlocked bootloader.
I decided to use the kdz offline flash method to flash all of the kdz versions from first to last starting with the metro v10d then all the way up to the t-mobile v20h so I could get all the firmware updates. Then I used the CMahendra method for installing CWM recovery for unlocked bootloaders where you install lgpwn then flashify and then use flashify to install the cwm image. Now after that I got the security error?! I have an unlocked bootloader why is it doing this?? I flashed the ics uboot boot and recovery after that so I could use s/w upgrade mode to restore stock now back at stock I try again to install cwm and yet again it gives me security error?
Can someone please tell me why?? The cwm image works on my device before you ask I had it installed before.
Click to expand...
Click to collapse
Related
Ok I recently got a tf201. I have finally decided 2 go for it and trying 2 get a custom rom.
Untill now (using a SGS) I needed 2 root the phone then get a custom kernel then apply the rom.
How is the procedure for a prime? I tried 2 root but shortly found out that i had the .21 update, Im guesing I can downgrade not sure.
does "unlock" = root?
can some1 clarify the process tree to get to a new rom?
http://transformerprimeroot.com/tra...ow-to-unlock-bootloader-on-transformer-prime/ <--- how hard is it 2 succeed this without bricking it?
b3ava said:
Ok I recently got a tf201. I have finally decided 2 go for it and trying 2 get a custom rom.
Untill now (using a SGS) I needed 2 root the phone then get a custom kernel then apply the rom.
How is the procedure for a prime? I tried 2 root but shortly found out that i had the .21 update, Im guesing I can downgrade not sure.
does "unlock" = root?
If any1 can redirect me 2 the appropriate topics I can never spot out what I want :/ and can some1 clarify the process tree to get to a new rom?
Click to expand...
Click to collapse
You will have to unlock via the asus unlock tool (you can just google that and get it directly off of the Asus website). Then you will have to use Fastboot to flash CWM onto your device. From there the usual, back up the stock rom, and install any custom rom of your liking.
omac_ranger said:
You will have to unlock via the asus unlock tool (you can just google that and get it directly off of the Asus website). Then you will have to use Fastboot to flash CWM onto your device. From there the usual, back up the stock rom, and install any custom rom of your liking.
Click to expand...
Click to collapse
unlock tool from asus website. ok but can u explain 1 thing 2 me? if its on asus website why does it void your warranty? and root and unlock are different?
If you are planning to flash a custom rom, check out androwookie v1.2 its good.
Unlock gives you the ability to install a custom recovery e.g. cwm, you then use this to flash a pre-rooted rom. Root just means having access to the root directory. It enables access to features and functions that are normally made inaccessible.
Using the fastboot method is pretty simple and guides can be found easily. I just did it yesterday after having previously only rooted and installed cm 7+9 on my sgs2.
Thats my understanding anyway
b3ava said:
unlock tool from asus website. ok but can u explain 1 thing 2 me? if its on asus website why does it void your warranty? and root and unlock are different?
Click to expand...
Click to collapse
It's just one of their stipulations. Most manufacturers are like that in regards to using their unlock tools.
Root = enhanced permissions to run apps like Titanium Backup, Root Explorer (if you're modifying anything in the/System directory), stuff like that.
Unlock = your bootloader is "unlocked," you can now put ClockworkMod recovery on your device, flash ROMs and kernels. These things can't be done while only being rooted.
I hope I cleared it up for you a bit
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
It's just one of their stipulations. Most
Root = enhanced permissions to run apps like Titanium Backup, Root Explorer (if you're modifying anything in the/System directory), stuff like that.
Unlock = your bootloader is "unlocked," you can now put ClockworkMod recovery on your device, flash ROMs and kernels. These things can't be done while only being rooted.
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
so with unlocking the device I wont have root privs? so things like you said titanium backup wont work?
1 more thing. is unlocking considered harder? and does any1 have a video of unlocking so that I know what I can expect b4 freaking out?
b3ava said:
so with unlocking the device I wont have root privs? so things like you said titanium backup wont work?
1 more thing. is unlocking considered harder? and does any1 have a video of unlocking so that I know what I can expect b4 freaking out?
Click to expand...
Click to collapse
Unlocking doesn't instantly get you root, it just makes rooting a lot easier to do. Like they said, unlock, put CWM on it, flash a rooted ROM and bam, rooted. But correct, apps like Titanium won't work if you're only unlocked, you would need root.
As far as I know, unlocking just requires downloading the .apk from Asus' site, installing it and going through the prompts. It doesn't sound hard at all. I personally don't know the ins and outs of it, as I never unlocked my Prime, but that's all it really sounded like. Sounds pretty simple. I believe there's some videos on it on YouTube though.
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
Unlocking doesn't instantly get you root, it just makes rooting a lot easier to do. Like they said, unlock, put CWM on it, flash a rooted ROM and bam, rooted. But correct, apps like Titanium won't work if you're only unlocked, you would need root.
As far as I know, unlocking just requires downloading the .apk from Asus' site, installing it and going through the prompts. It doesn't sound hard at all. I personally don't know the ins and outs of it, as I never unlocked my Prime, but that's all it really sounded like. Sounds pretty simple. I believe there's some videos on it on YouTube though.
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
buddy thanx for all of this info was just wondering if the link i posted is the process for this unlocking? as every1 is describing? and where do i get that CWM?
b3ava said:
buddy thanx for all of this info was just wondering if the link i posted is the process for this unlocking? as every1 is describing? and where do i get that CWM?
Click to expand...
Click to collapse
No problem! And yep, the link in the first post is a great looking guide for unlocking. Nice and easy, step by step. And after you have unlocked, just download ROM Manager from the market and you can flash CWM through the app itself. From my understanding that's the easiest way to do it, at least. Sorry it's been a few days since I responded, I haven't really been checking out the Q&A section lately
Sent from my Transformer Prime TF201 using XDA Premium HD app.
Bootloader unlock:
Custom Kernel possible
Official updates impossible
Waranty impacted
CWM backups possible
Need to use community ROMs in future
improved but not great chance of recovering from bad ROM flash (really needs NVFLASH)
Rooted:
Now possible with firmwares up to .28
Permits write access to /system partition
Makes it easier to brick and block OTA updates
Should be reversable
Allows most tweaks to be applied except for replacing kernel (which is a prerequisite for some kernels)
Going to make this a FAQ I think...
Hello, recently I have rooted my phone using the toolkit. The current recovery I have is TWRP. I wanted the root in the first place to be able to use xposed. However, it wont work, Whenever I try to install the update or new version it force reboots my phone. Also I found out I cannot update my software! I tried unrooting using the unroot option on SU but it was only temporarily. I want a permanent unroot and back to stock.
Android version : 4.4.2
Software number : 1.12.502.18
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me. Thank you.
Update
So i just downloaded a different image. I flashed it successfully! I am currently rebooting from the original recovery! Currently I am on the htc one loading screen. It's been a couple minutes, hopefully I did not brick it...
NOPE! I successfully returned to stock! ANother issue...I still have root access! How can remove SU? I tried the unroot option in the app but I am still rooted after reboot...
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
helpmeunrootmyphone said:
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know if the app is that big of a deal to you, but if it is, your options are...
1. Try factory reset in settings (may or may not work)
2. Reflash TWRP and flash the SuperSU.zip again than do a full unroot in settings.
3. Reflash TWRP and flash stock Sense ROM
Also, I made a guide in general which will help you fully return to stock. To begin the guide, you will need to be unlocked, rooted, and S-Off. That guide will help you hide the tampered and relocked banner.
If you don't care about the banners and the SuperSU app, it's probably not worth the effort and time.
Good luck.
Sent from my HTC One_M8 using Tapatalk
So you had an issue with Xposed, and you solution was to unroot? Wouldn't it have made more sense to troubleshoot the xposed problem? If you bothered to unlock the bootloader and root in the first place, IMO unrooting is a step backwards.
I'm also not a big fan of applying OTAs to a modded device. Yes, you cannot install official OTA updates on a modded phone. In particular, if stock recovery is not present, as its required for the OTA to install. If you want the latest software, just wait until the rooted version is posted in the Development section. Custom ROMs based on the 1.58 update started to be posted one day after the OTA started rolling out; and the stock rooted version was posted only 2 days after OTA release. For some people, getting it from here may even be faster than waiting for the OTA! That's pretty much how it goes. As long as there is developer interest in the device, you can rely on the latest software being available very quickly in the Development section.
The stock AT&T software is garbage anyway. I can't stand the amount of bloat, gimped features (WiFi hotspot) and other AT&T meddling. I don't understand why anyone would prefer this over other options. Software updates are always going to go to the international version first, anyway (AT&T is notorious for delaying updates for "testing"). What are you really getting with the 1.58 update? Extreme Power Savings mode, and a few other fixes? International M8 has had EPS mode for some time now.
---------- Post added at 09:31 AM ---------- Previous post was at 09:17 AM ----------
helpmeunrootmyphone said:
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me.
Click to expand...
Click to collapse
Why do you need to use the toolkit at all, to flash recovery? Flashing recovery is a single fastboot command. Easy.
The toolkit adds unnecessary complication; and I've seen them cause errors when doing it "manually" works just fine. The toolkit might not be the problem in your case, but we would never know unless you try to do it manually.
If you really want to flash stock recovery (not my personal recommendation), I would start by wiping cache and flashing recovery with fastboot. I've seen maybe dozens of cases where issues with flashing a recovery was solved simply by wiping cache:
fastboot erase cache
fastboot flash recovery "filename.img"
I am having the same issue as above using the same build file from the link given in the other thread. However, whenever I am in Bootloader, the computer or terminal does not recognize my device.
1.12.502.18
Anytime I try to use the toolkit or manually through the command line, it gives me "unc paths are not supported" or "device not found". It is the same for both Bootloader and Recovery. My original problem was the person I bought it from had root on it so I decided to wipe the OS without backing up and now cannot get the Stock Recovery ROM or any other Custom ROM to install on the phone. I have also tried the SD card method and that brought up an error as well resulting in "failed."
Any help would be appreciated as the phone as it sits right now does not have any OS on it so it is stuck on the HTC Boot up screen.
Thanks in advance for those that can help.
I had Lollipop and after doing a reset, it was stuck on boot animation. I have successfully downgraded to stock 4.4.4 using fastboot and I didn't flash gpt.bin, motoboot.img and logo.bin while doing so.
Now I want Lollipop again but I don't know what should I do-- whether to simply place the OTA on SD card and get it detected or flashing the TWRP-flashable LP zip? I wonder if following the native OTA method will brick the phone, I'm scared.
Please help
Same problem here ! Will look for solutions , if found will post here !
Sent from my XT1022 using XDA Free mobile app
I applied back the OTA, that's it, that worked. All we have to make sure is that we don't downgrade the bootloader (motoboot.img) and partition table (gpt.bin) while downgrading android. We can successfully upgrade but not downgrade those two. And I think this restriction began with 4.4.2.
nilanko said:
I applied back the OTA, that's it, that worked. All we have to make sure is that we don't downgrade the bootloader (motoboot.img) and partition table (gpt.bin) while downgrading android. We can successfully upgrade but not downgrade those two. And I think this restriction began with 4.4.2.
Click to expand...
Click to collapse
No, that's not right I think. I just flashed from 5.0.2 to 4.4.4. I flashed all the files including the motoboot and the got file and my moto e is working fine ! I used a windows tool some developer here had developed !
Sent from my XT1022 using XDA Free mobile app
kirtybs12 said:
No, that's not right I think. I just flashed from 5.0.2 to 4.4.4. I flashed all the files including the motoboot and the got file and my moto e is working fine ! I used a windows tool some developer here had developed !
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
It's not possible to flash motoboot.img and gpt.bin of 4.4.4 once you upgrade to 5.0.2. There must have been a "Preflash validation failure" while flashing these two which you probably didn't notice.
What was that tool? A batch file or what? Or an application? Fastboot won't allow the downgrade. Only OTAs have the power to downgrade those two.
nilanko said:
It's not possible to flash motoboot.img and gpt.bin of 4.4.4 once you upgrade to 5.0.2. There must have been a "Preflash validation failure" while flashing these two which you probably didn't notice.
What was that tool? A batch file or what? Or an application? Fastboot won't allow the downgrade. Only OTAs have the power to downgrade those two.
Click to expand...
Click to collapse
I am not so sure , but I was observing the commands being executed in fastboot and as far as I can tell there was no warning related to failure. There was one which comes whenever we downgrade our motoboot and it said boot downgraded or something like that but it didn't show a failure. Anyways , that too was a an application made in java that cud run in windows. It is in beta but did the job of flashing the stock rom. Of course, it must have included the commands to be executed in its coding. So either you run a batch file or that app, I guess you r bound to get the same results! I might b wrong about the failure message, but as I said I was checking and it didn't come to show up !
BTW , are you on lollipop, if yes , I am assuming you flashed it via flashable 5.0.2. If I am wrong let me know , so did u try to reset your phone ? Cause I had flashed lollipop via flashable zip and when I tried to reset the phone, it got stuck in moto logo. It was then , that I used that tool and came back to 4.4.4 !
Sent from my XT1022 using XDA Free mobile app
kirtybs12 said:
I am not so sure , but I was observing the commands being executed in fastboot and as far as I can tell there was no warning related to failure. There was one which comes whenever we downgrade our motoboot and it said boot downgraded or something like that but it didn't show a failure. Anyways , that too was a an application made in java that cud run in windows. It is in beta but did the job of flashing the stock rom. Of course, it must have included the commands to be executed in its coding. So either you run a batch file or that app, I guess you r bound to get the same results! I might b wrong about the failure message, but as I said I was checking and it didn't come to show up !
BTW , are you on lollipop, if yes , I am assuming you flashed it via flashable 5.0.2. If I am wrong let me know , so did u try to reset your phone ? Cause I had flashed lollipop via flashable zip and when I tried to reset the phone, it got stuck in moto logo. It was then , that I used that tool and came back to 4.4.4 !
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
I had noticed that "boot downagraded" message comes after flashing boot.img which is not the bootloader but is the kernel. I guess once we have lollipop bootloader and gpt, we can't go back, if we do via OTA update, phone will hard brick. Okay, I'm too scared to use any automated app, I would rather do it manually :silly:
Yes I am on lollipop and no, I just applied the OTA. Okay so here's s what you wanna know: I had 4.4.4 (brand new just-flashed, some settings adjustments, 2-3 apps installed by me), then I applied the OTA. After it was upgraded, I did a reset from the android system. Phone rebooted and I was greeted with the intial setup system of LP, filled all the required info, etc. and finally reached homescreen. After installing a few apps, rooting it and installing xposed, I was facing some issue (due to my own fault) so I decided to reset again. After doing so, it was stuck at the boot animation. So I think, it's most probably xposed that's causing the problem. Once you have it flashed, resetting will cause a bootloop (this same thing had happened earlier too), though I am still not sure if xposed framework is to be blamed. After all this, I downgraded to 4.4.4 and re-applied the OTA.
nilanko said:
I had noticed that "boot downagraded" message comes after flashing boot.img which is not the bootloader but is the kernel. I guess once we have lollipop bootloader and gpt, we can't go back, if we do via OTA update, phone will hard brick. Okay, I'm too scared to use any automated app, I would rather do it manually :silly:
Yes I am on lollipop and no, I just applied the OTA. Okay so here's s what you wanna know: I had 4.4.4 (brand new just-flashed, some settings adjustments, 2-3 apps installed by me), then I applied the OTA. After it was upgraded, I did a reset from the android system. Phone rebooted and I was greeted with the intial setup system of LP, filled all the required info, etc. and finally reached homescreen. After installing a few apps, rooting it and installing xposed, I was facing some issue (due to my own fault) so I decided to reset again. After doing so, it was stuck at the boot animation. So I think, it's most probably xposed that's causing the problem. Once you have it flashed, resetting will cause a bootloop (this same thing had happened earlier too), though I am still not sure if xposed framework is to be blamed. After all this, I downgraded to 4.4.4 and re-applied the OTA.
Click to expand...
Click to collapse
Thanks for the info, though I feel xposed is not to be blamed, cause I did not have xposed installed but still faced the same issue of bootloop on resetting. And , did u apply the ota by the renaming method ? Placing it in internal and then detecting and applying it ?
Sent from my XT1022 using XDA Free mobile app
Oh, it must be something else then-- probably superSU?
And yeah, renaming method only.
nilanko said:
Oh, it must be something else then-- probably superSU?
And yeah, renaming method only.
Click to expand...
Click to collapse
Perhaps , SU might be the problem as people have been having problems in rooting lollipop and maybe the process of rooting is not stable and that causes the problem. It can be anything , I am not sure of anything in particular !
Sent from my XT1022 using XDA Free mobile app
As some of you may have seen, I've found a root method that seems to work and be stable. I just unrooted, tried it again and failed once, tried it immediately after and it was successful. I think I may have found out the glitch why it's not working for some of you. During the root process, you absolutely can NOT let the screen go blank, timeout, or change. Mine has failed every time doing that, when I keep it on and uninterrupted, I've had success with it in about a minute.
Secondly, I know a lot of you want to make custom roms and complain about the bootloader being locked. That's true, but mine is unlocked, even though I did trip the Knox warranty counter. From the testing I've done so far, I've made a backup from the Online Nandroid backup app. I have learned that it is impossible to restart the phone in recovery in any way, shape or form without triggering the *Unauthorized software found, return to AT&T* error message. However, what I've been doing there to get my phone back is going into download mode, using Odin 3.07 and flashing the bootloader from the stock NE7 firmware. That can be found here: http://www.mediafire.com/download/9...711751_REV01_user_low_ship_MULTI_CERT.tar.md5 None of my stuff is lost, phone will reboot normally, everything looks good.
Now, as far as custom roms are concerned, since I have no idea about how to do that, I do have a custom recovery image saved through the other thing, but I don't know how to restore it through Odin. I do get kernel fail message if I try to enter recovery mode still, generally, all I have to do is power off and restart, it should work fine. If not, I load the bootloader image.
Having said that, it has me thinking. Since I'm basically using a custom rom already, I uninstalled the bundled bloatware and I *think* that's why I'm getting the error when I try, it may be possible to build around all of that and simply reflash the bootloader. I admit at this point, I'm in totally uncharted territory for myself and I'm not really even sure what trying to do a factory restore might do, but I do know I can recover using the stock firmware and then hopefully getting root access back to reload everything from Titanium Backup.
Until I get some sleep and enough nerve plus free time to try the factory restore to see if that is causing the issue, it's all theoretical. The point I'm getting at, and wanting to ask since I don't really know how it works, is if I can take the total stock rom as it is, root it without removing anything, and get it to boot into recovery from the phone or even through Odin, would that help the developers out there be able to come up with a workaround solution for this? I know I'm onto something, but I don't have the experience to proceed.
Since this phone has been dead and most of you have relegated it to a drawer or something, if you still have it, I'm guessing the Knox warranty 0x1 won't really mean a whole lot, so testing can be done. I'm trying my best with the total lack of knowledge I have and looking through different forums, but as I said, its beyond my experience level. I've cracked open the door folks, I can tell you absolutely, even if it does go into a bootloop or AT&T error, that bootloader will work without any loss except for the time it takes to get it done. I'm a bit brain fried right now, so if anyone has any suggestions, ideas, or whatever please comment. I believe this can be done, it was only a short time ago everyone said Root would never be on here, and now here it is. I also read in the Note 4 threads that once root access is gained, custom roms and things aren't going to be far behind.
Maybe there is a way to integrate that stock bootloader into a custom image without having to go around like I'm doing. I don't know programming very well. I'm sure that some of you folks with more experience and better minds than mine can come up with something based on my initial findings.
just used this on my i527 running i527UCUBNJ1.
ran root check and all good..tested romtool box,backed up some app s,all good..over clocked cpu no problem..awsome wrk.
now for kernels and roms..
Sent from my SAMSUNG-SGH-I527 using xda premium
Nice detailed post. Thank you.
I wish I had I527 to help out. (I have 527M and R960). I do care about Knox on my 527M but I don't care much about R960 as it's already Knoxed-out. So I might be able to help, but I ask all members who have I527 to chip in.
I have opened 527M and hardware-wise it's same as 527 (it even says 527 on my 527M board), so theoretically it should be same. But as I said in thee other thread, even KingRoot.apk fails to root it!!! ???
I didn't do anything to it. I unrooted last night and had it fail, but it worked again after.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
If anyone is interested, I successfully completed root process again with the kingo root app which allowed me to install and update SuperSU. Not sure if it will work for everyone, but it will work if you've already gained root access and want to change super user programs and had trouble previously.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
KingRoot not KingoRoot right?
Does anyone know how KingRoot achieves rooting? I want to know the actual mechanism of it.
Yes, kingroot. No idea how it works.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Good News and Bad News
I just tried to a factory reset without deleting my SDcard data. The bad news is, it went to the unauthorized error screen again. Good news is, the bootloader flash worked and I still haven't lost anything. Even if/when I unroot, it still says custom. Perhaps if I enable Knox before unrooting, I can restore the official version.
Wow, this phone is so stubborn! Goddamnit Samsung! What the hell...
idoit said:
Wow, this phone is so stubborn! Goddamnit Samsung! What the hell...
Click to expand...
Click to collapse
I'm thinking more AT&T than Samsung. There are so many of their apps embedded in the OS as well. Not sure which direction to take, I've frozen a few of them too.
You guys in the south should stop buying phones from AT&T. I'm sure you know they have been fined for millions of dollars to FCA for misleading advertisement (read = cheating).
Good News and Bad News
It is possible to go back to the stock image of NE7. I did it, I'm waiting on the update to NJ1 now. I was unable to do a straight factory reset from the phone, I got the same error, I even tried it again through Odin and it left everything as I had it. I unrooted, did everything I could then used all the firmware from the stock image to reload. I haven't been able to test the backups I made, they keep crashing in Odin. When I get updated and hopefully regain root access, I'll try to use the images I made to restore. If not, I still have everything backed up from Titanium. I don't know if this will work yet. I also don't know why Knox has been tripped on others devices. I didn't have a problem with restarting or anything until I tried a custom recovery. I guess that's just the nature of the beast. I'm planning on trying to make a totally stock image with root backup once I get this finished, if possible.
NE7 is Android 4.4.2 and NJ1 is ???
It's the latest update of 4.4.2.
Any progress in getting a working recovery for this monster?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
does anyone know about or have a working recovery?
I've asked....no response yet.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
txnolesfan93 said:
I've asked....no response yet.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
no working recovery as of yet
Sent from my SAMSUNG-SGH-I527 using XDA Forums Pro.
Has anyone tried exposed?
Sent from my SAMSUNG-SGH-I527 using Tapatalk
Same result. So far. I'm using exposed now and get some random app errors. I think it's from lucky patcher though.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I am on tmobile lg g5, twrp installed, unlocked bootloader, rooted, running fulmics. I am returning the phone since the gps issues are becoming worse, and it has even started dropping cell service almost hourly which requires me to reboot. Can I completely restore to stock via flashing in twrp? Trying to avoid having to drive somewhere and use LGUP on a windows PC as I don't own one. Will the bootloader automatically relock if I flash the stock rom without flashing SU along with it? Appreciate any help.
jamesvmccann said:
I am on tmobile lg g5, twrp installed, unlocked bootloader, rooted, running fulmics. I am returning the phone since the gps issues are becoming worse, and it has even started dropping cell service almost hourly which requires me to reboot. Can I completely restore to stock via flashing in twrp? Trying to avoid having to drive somewhere and use LGUP on a windows PC as I don't own one. Will the bootloader automatically relock if I flash the stock rom without flashing SU along with it? Appreciate any help.
Click to expand...
Click to collapse
There are stock ROMs (H83020a and H83020c) available to flash from twrp. You will not lock your bootloader nor lose twrp; but in order to get root again(in case you want), you will need to flash su. It worked​ for me perfectly and I have no issues with anything on my phone. The only thing that does not work (check screenshot for details) is google pay because since the phone is rooted "it does not meet the google's security standards." Now if you want to return the phone to factory state I believe there are threads here for that. If you still want to keep the phone just flash the appropriate zip and enjoy removing tmobile bloatware if you wish.
LG G5 Downloads:
Important!!!Do not flash H83010a. I read that it can brick your phone.
TMobile model is H830.
Android 6.0.1 is H83010i
Android 7.0 is H83020a and the latest version is H83020c. Find the zip of your choice.
http://downloads.codefi.re/autoprime/LG/LG_G5
jamesvmccann said:
I am on tmobile lg g5, twrp installed, unlocked bootloader, rooted, running fulmics. I am returning the phone since the gps issues are becoming worse, and it has even started dropping cell service almost hourly which requires me to reboot. Can I completely restore to stock via flashing in twrp? Trying to avoid having to drive somewhere and use LGUP on a windows PC as I don't own one. Will the bootloader automatically relock if I flash the stock rom without flashing SU along with it? Appreciate any help.
Click to expand...
Click to collapse
Ok. If you're wanting to do 100% stock, download the complete zip for 20c from http://downloads.codefi.re/autoprime/LG/LG_G5/H830/H83020c/LG-H83020c-Flashable.COMPLETE-ARB01.zip there. Put it on your extsd card. Backup everything that is on your internal sd (phone memory) like pictures, videos, SMS, etc. Once you've done that, boot to TWRP. Once in TWRP wipe everything except externalsd card, I also recommend using the format option to format the internal sd. Once you've wiped and preferably formatted data go to install and install the 20c complete zip you put on your extsd card. After it's done installing just reboot. This will overwrite TWRP and you will NOT have root. Your bootloader will still be unlocked though, so you still need a PC to relock your bootloader. Also I don't think encryption will be re enabled unless you flash the kdz though. Anyways that's your best way to return to stock without using PC.
mlatelcom said:
There are stock ROMs (H83020a and H83020c) available to flash from twrp. You will not lock your bootloader nor lose twrp; but in order to get root again(in case you want), you will need to flash su. It worked​ for me perfectly and I have no issues with anything on my phone. The only thing that does not work (check screenshot for details) is google pay because since the phone is rooted "it does not meet the google's security standards." Now if you want to return the phone to factory state I believe there are threads here for that. If you still want to keep the phone just flash the appropriate zip and enjoy removing tmobile bloatware if you wish.
LG G5 Downloads:
Important!!!Do not flash H83010a. I read that it can brick your phone.
TMobile model is H830.
Android 6.0.1 is H83010i
Android 7.0 is H83020a and the latest version is H83020c. Find the zip of your choice.
http://downloads.codefi.re/autoprime/LG/LG_G5
Click to expand...
Click to collapse
Just curious what type of brick? Hard or soft? Just wanna know for future safety
Sent from my LGE LG-H830 using XDA Labs
Nick216ohio said:
Just curious what type of brick? Hard or soft? Just wanna know for future safety
Click to expand...
Click to collapse
I don't remember very well; but I believe it's hard brick. When I was researching to root my phone y read that somewhere, maybe here. I'll try to find the info on my PC when I get home.
Update:
I found the link. The advice is in the FAQ. Not sure if that would happen in your case since you have a custom ROM. The danger is when downgrading from H83010D to H83010A.
Here is the link:
https://forum.xda-developers.com/tm...ock-h830-10d-rom-flashable-zips-imgs-t3406505
mlatelcom said:
I don't remember very well; but I believe it's hard brick. When I was researching to root my phone y read that somewhere, maybe here. I'll try to find the info on my PC when I get home.
Update:
I found the link. The advice is in the FAQ. Not sure if that would happen in your case since you have a custom ROM. The danger is when downgrading from H83010D to H83010A.
Here is the link:
https://forum.xda-developers.com/tm...ock-h830-10d-rom-flashable-zips-imgs-t3406505
Click to expand...
Click to collapse
Thanks bro. I totally believe it because past phones had exact issue.
Sent from my LGE LG-H830 using XDA Labs
Just for clarification, if you're on Android 7, you can not downgrade to Android 6 without first downgrading your bootloader as it won't flash correctly. Also just something to always keep in mind with LG phone's at least, is that LG uses a antirollback system. Never attempt to downgrade from a higher ARB # to a lower ARB #, if you're somehow successful it will lead to a hard brick. Every firmware that autoprime has posted states what antirollback number it is on, so always check that. On h830, every firmware since 10D has been ARB01, only 10A or earlier was ARB0. While lgup shouldn't allow you to flash (should error out), no reason to take that chance. Hopefully that helps clarify