Reaching out for some help... I'm stuck at this point. I need to get a recovery working. Preferably cwm at this point. All other questions I found when searching were users on previous versions of Android and honestly the whole baseband build thing confuses it. I can still boot to the normal phone and use it as usual but I do want to get a working recovery again.
Device: I337 / Rooted
Android: 4.4.4
Baseband: I337UCUAMF3
Rom: Cyanogenmod Nightly 8/6/14
Kernel: 3.4.0-cyanogenmod-g433243c / [email protected] #1 / Wed Aug 6 2014
I was on TWRP and tried flashing to CWM with Rashr. I did this because TWRP was not compatible with the new CM nightlies.
Recovery now only boots to: "System software not authorized by ATT has been found on your phone"
Is there a way I can get a working recovery going now?
Help is appreciated.
Thanks.
did you flash loki-doki after CWM and before reboot?
I never had issues with TWRP 2.5.0.2 and have latest Cm M9--
rugmankc said:
did you flash loki-doki after CWM and before reboot?
I never had issues with TWRP 2.5.0.2 and have latest Cm M9--
Click to expand...
Click to collapse
No I'm totally unfamiliar with Loki as I've never had to deal with it. I never had any issues before this. I guess the TWRP that I had it was already built in?
Is that still an option now? ROM Manager is showing that I have both CWM and TWRP on my phone. I'd be fine with getting rid of TWRP and just using CWM. If I reload CWM in ROM Manager could I then do Loki?
Thanks.
RiG14LA said:
No I'm totally unfamiliar with Loki as I've never had to deal with it. I never had any issues before this. I guess the TWRP that I had it was already built in?
Is that still an option now? ROM Manager is showing that I have both CWM and TWRP on my phone. I'd be fine with getting rid of TWRP and just using CWM. If I reload CWM in ROM Manager could I then do Loki?
Thanks.
Click to expand...
Click to collapse
You're probably going to have to use Odin and start all over again. If you're able to use twrp or cwm recovery you're on mdl firmware. You can get that at sammobile.com. Extract it with 7-zip or winrar and use the .tar.md5 in Odin. You'll have to re-root and put your custom recovery back on. Back everything up before starting as Odin will wipe your device.
Sent from my Nexus 5 using XDA Free mobile app
Here is the loki zip flashable in recovery.
https://www.dropbox.com/sh/yhrq0tia8512rj9/AAB3C9mLkMe_WeHQgP4QHiKra/loki-doki.zip
I haven't used or kept up with CWM for several years. So, don't know if it loki's a rom/kernel if dev hasn't loki'd rom/kernel.
You can Google loki-doki. But it is how we on MDL can flash custom roms/recoveries/kernels and those above MDL can't. It bypasses Sammy's security and allows kernel to flash. Newer builds are locked down and no similar exploit has been developed yet for them.
Once you get sorted as jd mentioned, use it right before you reboot. Doesn't hurt even if rom/kernel is not loki'd.
:good::good:
BTW, you didn't have issues before bc most att roms esp TW are loki'd--
jd1639 said:
You're probably going to have to use Odin and start all over again. If you're able to use twrp or cwm recovery you're on mdl firmware. You can get that at sammobile.com. Extract it with 7-zip or winrar and use the .tar.md5 in Odin. You'll have to re-root and put your custom recovery back on. Back everything up before starting as Odin will wipe your device.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
rugmankc said:
Here is the loki zip flashable in recovery.
https://www.dropbox.com/sh/yhrq0tia8512rj9/AAB3C9mLkMe_WeHQgP4QHiKra/loki-doki.zip
I haven't used or kept up with CWM for several years. So, don't know if it loki's a rom/kernel if dev hasn't loki'd rom/kernel.
You can Google loki-doki. But it is how we on MDL can flash custom roms/recoveries/kernels and those above MDL can't. It bypasses Sammy's security and allows kernel to flash. Newer builds are locked down and no similar exploit has been developed yet for them.
Once you get sorted as jd mentioned, use it right before you reboot. Doesn't hurt even if rom/kernel is not loki'd.
:good::good:
BTW, you didn't have issues before bc most att roms esp TW are loki'd--
Click to expand...
Click to collapse
Thanks guys.
So it seems like I have no choice but to start over completely since I can't get into recovery to flash Loki. Which sucks since I have no idea about the current procedures for rooting and getting recovery. It was pretty messy when I first got my S4 last year.
I almost want to just leave my phone as is and wait to buy a nexus 6 :cyclops:
RiG14LA said:
Thanks guys.
So it seems like I have no choice but to start over completely since I can't get into recovery to flash Loki. Which sucks since I have no idea about the current procedures for rooting and getting recovery. It was pretty messy when I first got my S4 last year.
I almost want to just leave my phone as is and wait to buy a nexus 6 :cyclops:
Click to expand...
Click to collapse
It's not so bad. Use Odin to get your system up and running again. Then use this to root and get a custom recovery on http://forum.xda-developers.com/showthread.php?p=41892523
Sent from my Nexus 5 using XDA Free mobile app
Yes it just takes studying. I used Mottochopper also, very good. When you are done, I do recommend TWRP 2.5.0.2. Also, if you are flashing kernels always wipe caches before rebooting.
Sent from my SGH-I337 using Tapatalk
if it has mf3 baseband i'm pretty sure you will have to use safestrap and a touchwiz rom. no cyanogen or cwm or twrp.
OP has MDL build his radio "baseband" is mf3. He can flash any radio he wants after rooted.
Sent from my SGH-I337 using Tapatalk
iateshaggy said:
if it has mf3 baseband i'm pretty sure you will have to use safestrap and a touchwiz rom. no cyanogen or cwm or twrp.
Click to expand...
Click to collapse
He's using twrp and cm. Baseband is most likely from the cm version here's on.
Sent from my Nexus 5 using XDA Free mobile app
rugmankc said:
Yes it just takes studying. I used Mottochopper also, very good. When you are done, I do recommend TWRP 2.5.0.2. Also, if you are flashing kernels always wipe caches before rebooting.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I just remembered I made a recovery backup in Rashr before trying to go to CWM. So I restored that in Rashr and am now back on TWRP 2.7.0.1.
This is great but I still want to be able to flash the new CM11 nightlies and TWRP isn't compatible with CMs new kernel.
Are you guys familiar with this situation?
RiG14LA said:
I just remembered I made a recovery backup in Rashr before trying to go to CWM. So I restored that in Rashr and am now back on TWRP 2.7.0.1.
This is great but I still want to be able to flash the new CM11 nightlies and TWRP isn't compatible with CMs new kernel.
Are you guys familiar with this situation?
Click to expand...
Click to collapse
When did that start. As I said I flashed M9 a few days ago with 2.5.0.2.
Sent from my SGH-I337 using Tapatalk
rugmankc said:
When did that start. As I said I flashed M9 a few days ago with 2.5.0.2.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
The 8/8 or 8/9 nightly.
Another question...what would happen if I flash CWM with TWRP? Would CWM just over write TWRP and be my active recovery?
RiG14LA said:
The 8/8 or 8/9 nightly.
Another question...what would happen if I flash CWM with TWRP? Would CWM just over write TWRP and be my active recovery?
Click to expand...
Click to collapse
Yes I change recoveries as needed but have been on current for awhile. Read up on flashing CWM to be sure you know of any issues and exact steps. If it is a zip no issues should be encountered. Never liked to use Rom MGR.
Sent from my SGH-I337 using Tapatalk
Read last 7 pages of cm11 thread. They talked about changing updater script of cm rom. If you flash CWM recovery zip remember to flash loki before rebooting. Uncheck sig check in twrp before flashing CWM. You can't restore twrp nandroid with CWM and vice versa. They list a flashable CWM zip there too.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 11:42 PM ---------- Previous post was at 11:39 PM ----------
Also, My M9 milestone seems to be last stable build--many reboots etc on recent nightlies. But, that is part of the game with nightlies. As I "age" I need more stable roms--less stress--
---------- Post added at 11:43 PM ---------- Previous post was at 11:42 PM ----------
RiG14LA said:
I just remembered I made a recovery backup in Rashr before trying to go to CWM. So I restored that in Rashr and am now back on TWRP 2.7.0.1.
Click to expand...
Click to collapse
Oh, the salvation of nandroids--:good::good:
I used an app like Rashr long time ago, but didn't like it. Maybe not a bad idea to have it and keep a backup just in case--
Related
I rooted my phone successfully and then I installed TWRP and it rebooted the phone and I got this message which now I have to use kies to go back to stock.
"System software not authorized by ATT has been found on your phone"
Sounds like you didn't install the Loki twrp
Sent from my A500 using Tapatalk HD
StolenVW said:
Sounds like you didn't install the Loki twrp
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
I downloaded goo manager and installed it from there. Could you please link me to the right one?
I haven't used goo manager but I have herd they have a Loki version of twrp in goo manager you have to make sure its for the att s4
Sent from my A500 using Tapatalk HD
If I use this method, will it work?
http://forum.xda-developers.com/showthread.php?t=2297900
Capt said:
I rooted my phone successfully and then I installed TWRP and it rebooted the phone and I got this message which now I have to use kies to go back to stock.
"System software not authorized by ATT has been found on your phone"
Click to expand...
Click to collapse
You are not flashing the correct kernel, I have seen that error, many times. Just boot to recovery, and flash a different kernel.
---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------
Capt said:
If I use this method, will it work?
http://forum.xda-developers.com/showthread.php?t=2297900
Click to expand...
Click to collapse
yes, but what ever rom you are flashing, most likely will included their kernel, flash the att compatible kernels, it will work.
Use Tibu to freeze "knox".
Twrp does not auto loki. you have to either flash a loki kernel or flash loki doki after flashing the rom and then reboot.
Loki doki can be found here: http://tau.shadowchild.nl/attn1/?p=483
He did not try to install a rom.....he got that after installing twrp
Sent from my A500 using Tapatalk HD
I keep having the same error. I used the latest "Lokifyed 3way Tool" as well as AdamOutler's "Casual Root and Recovery". Everything works fine until I try to install a ROM (tried various ROMs, Infamous/Revolt). After a successful ROM install, I reboot and get this error. I have the latest Samsung USB drivers installed, flashed back to stock, did a factory reset, cleared cache/dalvik, rerooted, frozen anything with "knox" in it, reinstalled both recoveries (on separate tries of course), and tried installing the loki-doki patch and lokied kernals before and after the ROM successfully installs, to which they both fail and abort install. I feel I have tried everything but any suggestions would be appreciated.
Methods I used to root and install lokied recovery:
bhp090808's "[TOOL](OneClick)Updated 6-1-13 ATT ROOT RECOVERY ODIN LOKIFYED"
http://forum.xda-developers.com/showthread.php?t=2297033
^used the CWM OUDHS 1.0.3.5 recovery^
AdamOutler's "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13"
http://forum.xda-developers.com/showthread.php?t=2297900
Kernal and loki patch I used (both fail when trying to install):
[KERNEL][ATT][AOSP/TW][6/3/2013] KT-SGS4 - MDM - LOKI'd - KTweaker
http://forum.xda-developers.com/showthread.php?t=2292341
http://tau.shadowchild.nl/attn1/?p=483
adr1aN said:
I keep having the same error. I used the latest "Lokifyed 3way Tool" as well as AdamOutler's "Casual Root and Recovery". Everything works fine until I try to install a ROM (tried various ROMs, Infamous/Revolt). After a successful ROM install, I reboot and get this error. I have the latest Samsung USB drivers installed, flashed back to stock, did a factory reset, cleared cache/dalvik, rerooted, frozen anything with "knox" in it, reinstalled both recoveries (on separate tries of course), and tried installing the loki-doki patch and lokied kernals before and after the ROM successfully installs, to which they both fail and abort install. I feel I have tried everything but any suggestions would be appreciated.
Methods I used to root and install lokied recovery:
bhp090808's "[TOOL](OneClick)Updated 6-1-13 ATT ROOT RECOVERY ODIN LOKIFYED"
http://forum.xda-developers.com/showthread.php?t=2297033
^used the CWM OUDHS 1.0.3.5 recovery^
AdamOutler's "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13"
http://forum.xda-developers.com/showthread.php?t=2297900
Kernal and loki patch I used (both fail when trying to install):
[KERNEL][ATT][AOSP/TW][6/3/2013] KT-SGS4 - MDM - LOKI'd - KTweaker
http://forum.xda-developers.com/showthread.php?t=2292341
http://tau.shadowchild.nl/attn1/?p=483
Click to expand...
Click to collapse
Use the recovery I am linking to flash whatever it is. It will auto-loki for you. Loki is required to bypass the bootloader authentication.
http://forum.xda-developers.com/showthread.php?t=2291956
CamFlawless said:
Use the recovery I am linking to flash whatever it is. It will auto-loki for you. Loki is required to bypass the bootloader authentication.
http://forum.xda-developers.com/showthread.php?t=2291956
Click to expand...
Click to collapse
This recovery is included in the 3way tool I used and it is the recovery I choose to use when going through the root/recovery process.
I have the same error "System software not authorized by at&t has been found on your phone" but when I press vol up and power it says rebooting to recovery but just boots back to that error. Anyway to fix this? TIA
irus said:
I have the same error "System software not authorized by at&t has been found on your phone" but when I press vol up and power it says rebooting to recovery but just boots back to that error. Anyway to fix this? TIA
Click to expand...
Click to collapse
What did you flash and how did you flash it? And do you have the i337 or what?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
What did you flash and how did you flash it? And do you have the i337 or what?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
sorry for not giving more detail. I have the sgh-i337 at&t version. Like I said I pressed the volume up with power and did not release until it said rebooting into recovery in the upper left of the display.
irus said:
sorry for not giving more detail. I have the sgh-i337 at&t version. Like I said I pressed the volume up with power and did not release until it said rebooting into recovery in the upper left of the display.
Click to expand...
Click to collapse
Are you on stock, or did you flash a rom? And of so how did you flash it
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
---------- Post added at 05:38 PM ---------- Previous post was at 05:36 PM ----------
Have you read this whole thread? Because the other guy didn't flash the correct kernel. You probably didn't either
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I was on stock. I rooted, then installed cwm recovery the installed v1.3 of Google play stock. I did not install the loki patch because it says its auto Loki patch. So not sure what I did wrong :-\ thanks for helping with this
jd1639 said:
Are you on stock, or did you flash a rom? And of so how did you flash it
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
---------- Post added at 05:38 PM ---------- Previous post was at 05:36 PM ----------
Have you read this whole thread? Because the other guy didn't flash the correct kernel. You probably didn't either
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
irus said:
I was on stock. I rooted, then installed cwm recovery the installed v1.3 of Google play stock. I did not install the loki patch because it says its auto Loki patch. So not sure what I did wrong :-\ thanks for helping with this
Click to expand...
Click to collapse
You didn't read the whole op for v1.3 because it says to Loki patch. Do that and you'll be fine.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
My problem is I can't get back into recovery. I press volume up and power and it says rebooting into recovery but the I just get the same error. Is there something else I need to do?
jd1639 said:
You didn't read the whole op for v1.3 because it says to Loki patch. Do that and you'll be fine.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
irus said:
My problem is I can't get back into recovery. I press volume up and power and it says rebooting into recovery but the I just get the same error. Is there something else I need to do?
Click to expand...
Click to collapse
You need to go into download mode and get a stock rom that is rooted through odin. I can't really explain through text how to use odin, so just use google and YouTube to your advantage.
sent from that HUGE Phone
Hey guys I'm new to android had an iPhone for 6 years. Just got the gs4 two months ago. I rooted the phone took out bloat ware apps using titanium back up. Have a few other rooted apps. Got Interested in ROMs and kernels so did some research looked around on here to how to do it. I downloaded infamouses newest ROM. I have ROM manager and I downloaded cwm recovery through the Rom manager. When I go to back up my current ROM and everything it boots into recovery mode but it isn't cwm recovery. The emblem doesn't come up and I believe its the stock recovery. My question is how can I get the cwm recovery so I can back up my current ROM and then wipe it and install the new one. I'm new so sorry if this is easy or anything I appreciate all the help
Download goo manager and let it install twrp then just flash cwm thru twrp . Or keep twrp and remember to flash loki doki if needed.
Wait!
What firmware is your phone currently on? MDL OR MF3?
If MF3, stop now. Do not flash anything.
Sent from my SGH-I337 using xda premium
Okay I figured out the problems. When I hit reboot and superuser is supposed to grant root permissions an error comes up saying superuser has stopped working then goes into the stock recovery mode. The only thing I found with MDL in it was the baseband version 1337UCUAMDL
Your safe to continue flashing custom recovery on MDL Baseband
Sent from my SGH-I337 using xda app-developers app
Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.
Division4thor said:
Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.
Click to expand...
Click to collapse
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.
scott14719 said:
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.
Click to expand...
Click to collapse
Yeah Idk I'm so over this getting so frustrated. I'm new to this I read that post. Not all 51 pages hope you didn't mean that..
This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you
TheAxman said:
This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you
Hey thanks for the help. I got twsp recovery through goo manager and worked perfectly. I'm having such a bad experience trying to install this rom. I went into the recovery mode after backing up my current rom and system. I wiped everything out then went into my sd card amd installed the zip that is listed in the infamous page in the developers part. I hit install and then said I'm not rooted and would I like to install superuser. I slide the thing and then went to reboot and now has been stuck saying samsung and custom with an open love under it. Pulled the batter went back into twsp and tried to reboot and still stuck. This is all after I thought I installed the rom already and nothing changed except wiped my phone. Can anyone help
Click to expand...
Click to collapse
Are you installing loki doki after the rom ?
hey all,
I'm a complete noob when it comes to rooting
I've been searching online on how to root a nexus 4 using a mac.. every single guide is different, some skip the unlocking bootloader part, some skip other parts, and most guides are just outdated.
I'm running on absolute stock, 4.4.2.
What's the best (and most current) guide out there? I'm interested in rooting my phone mainly so I can get LTE access.. do no care too much for non stock ROMS (not yet at least)
I think this is the easiest for noobs: http://forum.xda-developers.com/showthread.php?t=1999065 . It's a tool that will do all the work for you.
Sent from my Nexus 4 using Tapatalk
update:
I set up adb on my mac and unlocked bootloader, that was easy.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
so now I'm confused about the whole Rom part.. which one do I download? There's a ROMs column, a stock recovery, and stock touch recovery. What are those?
You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk
Yuoko5 said:
You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?
If you're device is rooted I think you won't be able to install OTA updates from google anymore. But, you can flash these stock roms easily. I'm sure people make flashable zips of every new version of Android. About the columns: ROMs=you can download custom roms (you don't need that); Recovery and recovery touch is basically the same thing. The difference is one recovery can be controlled with the touchscreen and the over with the volume and power button. It's just what you like best.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
beegbear said:
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?
Click to expand...
Click to collapse
Get it?
Sent from my Nexus 4 using Tapatalk
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
Cwm(clockworkmod recovery) is a side load which helps u to flash different ROMs and zip files. It also helps u to wipe battery stats, partition sd card(not with case of n4)
Factory image is the stock ROM that Google provide that u r having in your nexus 4
Sent from my Nexus 4 using xda app-developers app
beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.
Lt.Win said:
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.
Click to expand...
Click to collapse
So let me make sure I'm following this..(sorry, I'm sure you saw such questions countless times before)
CWM (or TWRP) is a custom recovery instead of the stock 'recovery' option that's found in the bootloader. If I choose to go with either CWM or TWRP, how much of an issue is it to flash back to stock recovery? would it be done through ADB the same way the custom recovery was flashed in the first place?
As I understand.. the first thing I should do after unlocking the bootloader (already done) and flashing a custom recovery (not done yet) is to create a backup through the custom recovery. Does that back up the radios as well? If I decide to flash the all in one LTE zip and it doesn't work or what not.. will using that recovery flash back the old radios?
Now to the actual rooting..
so flashing super su is what actually does the root? How would I go about returning to complete stock if I ever need to? (stock recovery, remove root, lock bootloader)
When flashing a different ROM, how come I need to make a backup of my apps? what if I want to start completely fresh? Would I not be able to go to the playstore after flashing a custom rom and downloading everything I need? or there is not going to be a play store after flashing? (that's why GAPPS are needed?)
so I rooted and flashed the hybrid radio, works like charm!
I answered most of my own questions in the post above just by going through the process.
What happens if I decide to factory reset through settings? will CWM stay? will the root stay? will the lte fix stay?
Yes...yes...yes.....you really should take advantage of the countless guides people have written explaining all of your questions.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I bought a phone pre rooted and everything. It was nice, but the problem is I am having trouble changing the recovery on the phone.
For a long time I had TWRP 2.6.3.4. I could not flash any recovery over it. I was finally able to flash TWRP 2.6.3.1 using the same method to get TWRP. At that point I'm still not able to flash a recovery over TWRP.
I just discovered "flashify" tonight where I had flashed the CWR image for the d800. Now I can't even boot into recovery. It acts like I have non. I can boot into android no-problem though.
When I use "flashify" or "Recovery Tools" they claim I still have TWRP 2.6.3.1.
______________________________________________________________________________________________________________________
Can someone please help me.
I too tried flashing CWM over TWRP using Flashify, but it didn't work, it still said I had TWRP. However, Flashify did work to revert back to Stock Recovery.
I still have the backup file of the Stock Recovery, I can upload it somewhere if you want to, then maybe you can install CWM.
I have a D802 myself, not sure if my backup would work with your D800 though. but if you're adventurous...
Hid3rs said:
I too tried flashing CMW over TWRP using Flashify, but it didn't work, it still said I had TWRP. However, Flashify did work to revert back to Stock Recovery.
I still have the backup file of the Stock Recovery, I can upload it somewhere if you want to, then maybe you can install CMW.
I have a D802 myself, not sure if my backup would work with your D800 though. but if you're adventurous...
Click to expand...
Click to collapse
I was able to get back a version of TWRP following this: http://theunlockr.com/2013/11/03/flash-custom-recovery-lg-g2-versions-video/
Still don't know why I can't get other recoveries like CWR or why almost all versions of CM will fail to flash using TWRP
EDIT
I miss read you post. I thought you had a copy of TWRP. Go ahead and send the the stock recovery as that's one thing I have yet to try..
Traceguy said:
I was able to get back a version of TWRP following this: http://theunlockr.com/2013/11/03/flash-custom-recovery-lg-g2-versions-video/
Still don't know why I can't get other recoveries like CWR or why almost all versions of CM will fail to flash using TWRP
EDIT
I miss read you post. I thought you had a copy of TWRP. Go ahead and send the the stock recovery as that's one thing I have yet to try..
Click to expand...
Click to collapse
Well now I'm not sure if it's a good idea. Even for custom recoveries there are different files to download for D800 and D802. I don't think my backup would be compatible with your variant.
If you want CM, try flashing Official Nightlies. I've heard they are stable. I flashed CM11 Nightly with TWRP 2.6.3.4 just fine. You can grab it for D800 here.
Hid3rs said:
Well now I'm not sure if it's a good idea. Even for custom recoveries there are different files to download for D800 and D802. I don't think my backup would be compatible with your variant.
If you want CM, try flashing Official Nightlies. I've heard they are stable. I flashed CM11 Nightly with TWRP 2.6.3.4 just fine. You can grab it for D800 here.
Click to expand...
Click to collapse
Mine never works. I think its a MD5 error or something. I can only get one version of CM running and I think it's 10.2, I assume my whole phone is just messed up. Not being able to flash CM or recoveries.
Try going back to stock and starting over? Did you by chance take the 10o ota? That seems to be causing issues for others.
Sent from my LG-D800
btm fdr said:
Try going back to stock and starting over? Did you by chance take the 10o ota? That seems to be causing issues for others.
Sent from my LG-D800
Click to expand...
Click to collapse
I'm not sure.
Is there a windows software out there that can bring me to stock sort of like the NexusToolkit for Nexus devices.
Traceguy said:
I'm not sure.
Is there a windows software out there that can bring me to stock sort of like the NexusToolkit for Nexus devices.
Click to expand...
Click to collapse
Settings - about phone - software information
See what software version you have.
Sent from my LG-D800
btm fdr said:
Settings - about phone - software information
See what software version you have.
Sent from my LG-D800
Click to expand...
Click to collapse
I'm currently running CyanogenMod "10.2.0-d800", there is no "Software Information" or "Version"
Recovered back to Clean ROM 2.0
Software version: d80210b
EDIT:
Using this guide here: http://forum.xda-developers.com/showthread.php?t=2468858
I was able to get CWM.
So far I've come to the conclusion. The only way to change recoveries is through the PC and not from the phone it's self
Found it, nevermind
Sent from a PollutedG2 using the xda premo app
I have an i337. Never had any OTAs. I was using a recovery that would 'auto-loki' so I never had to flash the lokidoki zip before.
I'm trying to install the latest GPE by Danvdh and I keep ending up booting into twrp(2.6.0.0).
I wipe all that one would normally wipe.
Then I flash the ROM.
The aroma installer starts, I've tried the googy kernal and (mostly) the stock kernal.
I uncheck the reboot now option at the end of the aroma installer to get back into twrp
I then flash the lokidoki zip.
I reboot and get kicked back into the recovery.
I'm thinking I may need a newer version of TWRP, but I'm not sure. I dont want to use odin to get back on jellybean just to update the recovery unless I know that's the issue.
the loki zip is ~10MB
Any info is much appreciated. I've been at this for hours.
You need a newer version of twrp. You don't need to use Odin. Look for the flashify app in the play store.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You need a newer version of twrp. You don't need to use Odin. Look for the flashify app in the play store.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
My phone is only booting into recovery though. I have the latest twrp image. Is there a way to flash it from within twrp?
a_rocklobster said:
My phone is only booting into recovery though. I have the latest twrp image. Is there a way to flash it from within twrp?
Click to expand...
Click to collapse
If you can find a zip. I'd make one for you, they're easy once you know how, but I'm traveling on business and don't have access to a computer.
Edit, @a_rocklobster it's your lucky day https://www.androidfilehost.com/?fid=95916177934537984
Sent from my Nexus 5 using XDA Free mobile app
Sweet! I'll try that today!
Thanks very much for the help