Hello all, I am new to the S4 and got the root process to take by following the guide. However right after gaining root I downloaded goomanager and tried to flash the recovery from inside the app. It said the recovery was flashed successful but upon restarting I get the downloading screen and it just sticks there. Did I miss a step with installing the custom recovery? Also, I am using the ME7 version on my phone. Any help is very appreciated. I am hoping to install hyperdrive rom.
There is no custom recovery for ME7 S4's.
««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
Recovery is not possible for ME7 at this point. Root is the only thing we have thus far.
Is there no way to get the new ROM on that version or do I need to downgrade to the previous version (if possible).
smayer85 said:
Is there no way to get the new ROM on that version or do I need to downgrade to the previous version (if possible).
Click to expand...
Click to collapse
No, you can't install a custom recovery or a custom ROM on ME7.
No, you can't downgrade to the previous release (MDK) that would allow you to do the above.
smayer85 said:
Is there no way to get the new ROM on that version or do I need to downgrade to the previous version (if possible).
Click to expand...
Click to collapse
There is no way to downgrade from ME7. Bootloader is locked. ME7 only has root.
So there is no way to flash a custom rom on my phone....awesome lol time to theme and freeze the bloatware.
Yes unfortunately we have a rather small sandbox to play in right now BUT it's better than no sandbox at all.
««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
Go here for ME7 discussion...http://forum.xda-developers.com/showthread.php?p=44920037#post44920037
Related
The first step for flashing Alliance was making sure i have the 4.3 firmware. Flashed via Odin.
I experfienced some trouble with a bootloop issue so i changed cables and then partitioned with the .pit file.
All's well now, it at least runs the stock firmware just fine. Now i'm strugglling with the most basic simple part IMO... how do i install the custom Rom without the recovery??
sduffy89 said:
The first step for flashing Alliance was making sure i have the 4.3 firmware. Flashed via Odin.
I experfienced some trouble with a bootloop issue so i changed cables and then partitioned with the .pit file.
All's well now, it at least runs the stock firmware just fine. Now i'm strugglling with the most basic simple part IMO... how do i install the custom Rom without the recovery??
Click to expand...
Click to collapse
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
KuNiT said:
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
Click to expand...
Click to collapse
I chose to bump up my android version cuz i friend another SIM card. I tether for my Hulu, Netflix, Amazon Prime, and whatever else, thankfully my laptop can get weak unsecured internet signals, but i'm walking my Note around the apartment trying to get good 1x reception Problems may be overlapping but next step is something basic from the Play Store to verify root.
I read of some luck with root for 4.3, just not bootloader. Am i correct?
KuNiT said:
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
Click to expand...
Click to collapse
Not rooted. it sounds like rooting is still an option, just not custom recovery?
Is using ODIN to flash stock rooted an option? No valuable files on phone currently.
(Fortunately I'm at work right now so I have time to make well informed decisions. Thanks for your help)
sduffy89 said:
Not rooted. it sounds like rooting is still an option, just not custom recovery?
Is using ODIN to flash stock rooted an option? No valuable files on phone currently.
(Fortunately I'm at work right now so I have time to make well informed decisions. Thanks for your help)
Click to expand...
Click to collapse
I believe if you took/flashed the OTA update, your kinda out of luck and stuck now. I'm not 100% certain of this though but I think it probably relocked the bootloader and the only thing to do is wait for someone to root/unlock 4.3.
KuNiT said:
I believe if you took/flashed the OTA update, your kinda out of luck and stuck now. I'm not 100% certain of this though but I think it probably relocked the bootloader and the only thing to do is wait for someone to root/unlock 4.3.
Click to expand...
Click to collapse
Correct. If you took the OTA it relocked your bootloader and you are stuck. You can still root the official 4.3 but you are stuck waiting until someone unlocks the bootloader. This means no custom ROMs/Recovery.
Which 4.3 firmware did you flash? If its the OTA then yes you're outta luck.
If you did follow the Alliance's rom thread. There is a 4.3 MJ9 firmware you need to flash. It doesn't have the locked bootloader. You are then able to boot up in the basic recovery and then flash either TWRP or CWM recovery.
I just recently rooted and flashed CM11 on my little brothers phone because well.. I could.. So yeah I basically had to! But I would kiiiillll for baseband MDK at the moment. Is their any way to get that? Or at least get CM on a me7, Other than looking to buy an old phone..
Nope
Unfortunately CM is out of reach for you. In order to run it you must have the MDK bootloader. It is the only one that can be exploited (via loki) to allow the installation of a custom recovery such as CWM or TWRP. Without one of those you cannot flash CM. Safestrap will not allow the use of CM.
Does that mean, if I Odin back MDK and take the Loki approach - can I install CM11 then?
You are unable to Odin back to MDK once you have upgraded.
jmgib said:
You are unable to Odin back to MDK once you have upgraded.
Click to expand...
Click to collapse
This is correct. And if you do try at best the process will fail and you will reboot to where you were before, worse case you risk bricking your device.
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Saint Isaiah said:
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Click to expand...
Click to collapse
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
joshm.1219 said:
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
Click to expand...
Click to collapse
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Also, what in the world does it mean to "Loki" a ROM after installing it? Kinda confused there
Saint Isaiah said:
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Click to expand...
Click to collapse
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
joshm.1219 said:
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
Click to expand...
Click to collapse
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Saint Isaiah said:
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Click to expand...
Click to collapse
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
joshm.1219 said:
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
Click to expand...
Click to collapse
Awesome, thanks Josh! This might make a great sticky for the "what is Loki?" newvies and explaining the importance of MDK for those still on it and not sure why.
EDIT: with Davey126's stock recovery file, my problem is solved. Thanks!!
Hi xda!
Long time follower here. Wanna thank all the people here for the great work and help to the android community.
On to my issue, I can't get into stock recovery now. If I flash safestrap, I can boot to recovery, but not when I uninstall safestrap.
This is what happened: I was on Thor 13.3.2.5 rooted. I downgraded to 13.3.1.0 then 13.3.2.3.2 rooted (backed up), then left OTA on. When I came back to it, it was in a boot loop. I powered off and back on holding power button, now it boots to 13.3.2.5! And when I check version, it says 13.4.1.1 available. But the update always fails because the HDX never goes into stock recovery.
I then reinstalled safestrap and restored. Now I am running 13.3.2.3.2 but can't boot to stock recovery.
Question: 1) where and how do I get the recovery image? 2) can I use the recovery image for Apollo?
Thanks very much in advance.
ssrtist
ssrtist said:
Hi xda!
Long time follower here. Wanna thank all the people here for the great work and help to the android community.
On to my issue, I can't get into stock recovery now. If I flash safestrap, I can boot to recovery, but not when I uninstall safestrap.
This is what happened: I was on Thor 13.3.2.5 rooted. I downgraded to 13.3.1.0 then 13.3.2.3.2 rooted (backed up), then left OTA on. When I came back to it, it was in a boot loop. I powered off and back on holding power button, now it boots to 13.3.2.5! And when I check version, it says 13.4.1.1 available. But the update always fails because the HDX never goes into stock recovery.
I then reinstalled safestrap and restored. Now I am running 13.3.2.3.2 but can't boot to stock recovery.
Question: 1) where and how do I get the recovery image? 2) can I use the recovery image for Apollo?
Thanks very much in advance.
ssrtist
Click to expand...
Click to collapse
Don't use an Apollo recovery. While I have no direct evidence it won't work the risk seems unacceptable given you only have partial control of your device and (probably) a locked bootloader.
Stock 13.3.2.6 recovery here. I have been told there were no changes from 3.2.5. You can use flashify to install it.
Obviously there is risk associated with this approach. Might want to wait a day or two for additional responses to see what others think.
Thanks! So I don't actually need to go to 13.3.2.3.2? Also, did I downgrade the recovery when I downgraded the stock rom?
Sent from my Nexus 7 using XDA Free mobile app
ssrtist said:
Thanks! So I don't actually need to go to 13.3.2.3.2? Also, did I downgrade the recovery when I downgraded the stock rom?
Click to expand...
Click to collapse
A previous post suggested you are already at 3.2.3. Bit confused regarding your question. Not sure what happened to your recovery during the previous rollbacks/upgrades. I have seen something similar happen to folks who have installed twrp then upgrade past 3.2.3.
What's your objective? Are you looking to run CM11/12 or stick with rooted stock? If the former you'll need to rollback again (if not already on 3.2.3), block OTA and then install native twrp. Once you have a working recovery you should uninstall safestrap before beginning the rollback process. Safestrap isn't part of the equation going forward.
Davey126 said:
Not sure what happened to your recovery during the previous rollbacks/upgrades. I have seen something similar happen to folks who have installed twrp then upgrade past 3.2.3.
Click to expand...
Click to collapse
I think that's what I did ?
My goal is to try both cm12 and rooted 4.5.2. (Separately). Is flashing 3.2.6 recovery the way to go?
Thanks?
ssrtist said:
I think that's what I did
My goal is to try both cm12 and rooted 4.5.2. (Separately). Is flashing 3.2.6 recovery the way to go?
Thanks?
Click to expand...
Click to collapse
Depends where you are now. If on rooted 13.3.2.3 then you should be able to flash twrp directly after getting rid of SafeStrap. Note there is now a recommendation to unlock your bootloader before installing twrp but that seems to be optional (bootloader unlocking is not for the faint of heart). You can then install CM11/12.
If currently above 3.2.3 then you need to get a working recover before taking next steps. Flashing 3.2.6 recovery seems to be a reasonable choice but as previously noted there is risk associated with this approach. Assuming it works you then need to start the rollback process all over again.
4.5.2 is an entirely different beast. Still need to get a working recovery before upgrading unless you flash it directly via adb which is risky.
Without an unlocked bootloader anything you do can lead to an unrecoverable brick. Make sure you think ahead and read up on others experiences before proceeding.
Thanks Davey!! Your answers are very informative! I will read a bit more before i tackling the bootloader...
Sent from my Nexus 7 using XDA Free mobile app
I'm currently rooted on 4.3 MJ4. Yes I'm outdated and decided to finally update. I'm going to flash to stock 4.3 MJ4. My questions is, after I flash to stock 4.3 MJ4. Can I flash NC5 from MJ4? Or would I have to do it in these steps ( MJ4 then NAB then NC5? ).
Why not PH1? If you're wanting to stay with KK, NK4 is the last I believe. NH7 is the one most people used. Just trying to find out what you're trying to achieve
Also, if you're flashing a stock ROM, you don't need to first flash MJ4. Just flash what you want.
evilvoice said:
Why not PH1? If you're wanting to stay with KK, NK4 is the last I believe. NH7 is the one most people used. Just trying to find out what you're trying to achieve
Also, if you're flashing a stock ROM, you don't need to first flash MJ4. Just flash what you want.
Click to expand...
Click to collapse
Awesome! Thanks! I am trying to flash a stock rom, but thought I would need to go in steps instead of instantly flashing to the most current version.
As for my plan: I'm rooted and on a custom rom. I want to go back to stock rom and then root again and flash to either cm12.1 or cm13. From what I've read, I cant flash to either cyanogenmod roms until I was on either lollipop or higher. I was also thinking, would it work if I was to flash a rooted current version of a stock rom, that way I don't have to flash a stock rom and break root and have to root it again?
For better results, I would flash a full PH1 rom and root, then install whatever rom you want. Usually they want the bootloader to be upgraded to lollipop and that really only happens when either flashing a full Odin rom or a bootloader image. Doing only the bootloader doesn't upgrade anything else and may cause issues.
evilvoice said:
For better results, I would flash a full PH1 rom and root, then install whatever rom you want. Usually they want the bootloader to be upgraded to lollipop and that really only happens when either flashing a full Odin rom or a bootloader image. Doing only the bootloader doesn't upgrade anything else and may cause issues.
Click to expand...
Click to collapse
What is the PH1 rom? I've already flashed to stock NC5 so far and lost root.
It's the latest rom. I don't think an Odin has been posted, but you can grab from the Samsung firmware site. Load that, then root by flashing TWRP and boot into recovery and flash SuperSU. Done.
evilvoice said:
It's the latest rom. I don't think an Odin has been posted, but you can grab from the Samsung firmware site. Load that, then root by flashing TWRP and boot into recovery and flash SuperSU. Done.
Click to expand...
Click to collapse
EDIT: I went ahead and used the Full Restore. Fortunately, it did not WIPE any data. YEAH! And it looks like I am on my way to an updated NOTE3.
Hello. My Note3 is on 4.3. It was rooted a couple of years ago, but out of use since Oct 2015. I still want to use the Note3 for non-cell phone operations, browsing, camera, etc. I want to upgrade, but the OTA is locked out.
I am lost on all of the many, many posts on how to updated a rooted Note3, but most of them are outdated. I have it mostly backed up as far as handwritten notes, photos, etc. But I don't really want to have to start from scratch if I don't have to.
I am currently reviewing rwilco's one click options. There are two software packages listed in his directory. One of them is dated 02/27/15 and is called nodata restore. Will this keep from wiping the phone as opposed to the fullrestore exe posted 04/12/14 vs the tar posted 02/27/15.
I am not a complete dodo, but I am having a hard time getting this phone unrooted and updated.
Thanks for any detail instructions or links to the best way to update this as of 9/5/2016!!!
Everything you need to know is explained here. http://forum.xda-developers.com/galaxy-note-3/general/guide-how-to-disable-air-command-pop-t2960839
Sent from my SM-N920C using XDA-Developers mobile app