Greetings,
I upgraded to Goldeneye 53 from GE 49.2. But I've come to miss the Xposed Framework. I'd like to go back.
TWRP went away and I can't reinstall it. I've got my last TWRP backup, but I guess it's useless now. Fortunately my TiBu is solid.
Can I get back to 49.2 and how do I do it?
Thanks --
Could I Odin back to NB1, do Towelroot, re-install TWRP, and restore my backup?
Or will I brick my phone after Odining NB1 because I flashed GE 53 (OC3) from TWRP?
I really don't understand the whole qfuse thing very well. I mean, I understand how it works, technically (write a value to a register which applies voltage and "poof"), but I don't know when and when they won't blow.
OK! Got back to NJ4 with this process. My phone is now running a restore of my GE 49.2 backup.
Basically talking to myself here. Anyway......after restoring my backup I discovered that Wi-fi wouldn't switch on. After MUCH research and scrambling, I flashed ATT_NJ4_modules.zip from Safestrap, and all is well. Adventure complete.
Related
Oh boy, I really screwed this one up...
I purchased a used Note 3 from eBay, hoping to be able to root it after it arrived. Much to my surprise, it arrived rooted with Safestrap, Hyperdrive ROM in Stock slot, and a different Hyperdrive ROM in Slot1. I was also impressed that KNOX had not been tripped. (It said Custom, but the KNOX flag showed 0x00)
Sweet looking phone in hand, I was thrilled! I wasn't going to have to cut my teeth on rooting the device myself prior to having an opportunity to explore a rooted Android and a custom ROM. The very first thing I did was to use Safestrap to backup both the Stock slot and Slot1. After the backups, I booted the stock slot first, to see how a factory Note 3 should look. Surprise again, the stock slot booted a Hyperdrive ROM. I was a bit nervous that I didn't have a truly stock ROM, but wasn't too worried about it because I had no plans to resell or seek repairs under warranty.
I then spent a couple of days tinkering with the device. Unfortunately, half asleep during the wee hours of the morning, I was tinkering around with SuperSU -- setting grant/deny/prompt flags for different apps. Somewhere in the midst of that, SuperSU informed me that I had lost root. I checked with RootChecker, and sure enough NO Root.
Things got worse from there, as I'm sure you can imagine. RootChecker had a button to relaunch SuperSU, so I tapped it. This time, SuperSU wanted to re-install itself. Being the ignorant noob that I am, I told SuperSU to proceed, and crossed my fingers. After a few seconds of thrashing around, SuperSU wanted to reboot, so I said okay...
Now the device attempts to go into recovery, reboots itself, attempts recovery, reboots, again, and again... boot loop... and no way to charge the battery... I believe I am around 55% to 60% charged at the moment.
So I read great things about Odin and downloaded a copy -- not yet sure exactly what I was going to do with it. I have been trying to wrap my head around this for a couple of days now, but I have several questions that I hope somebody can shed some light on.
Does the rooting take place in the boot image, or in the ROM image? I am assuming it has to be in the boot image, but then I've heard you can have rooted and unrooted ROMs in different slots.
If I use Odin to flash fresh firmware, will this firmware will have a functional recovery tool bundled with it?
Since the phone is no longer rooted, the recovery will not be able to re-flash a ROM onto the device?
If an Odin installed recovery can't re-flash a ROM due to being unrooted, am I faced with JTAG options only?
If I were to use Odin to flash this firmware: http://forum.xda-developers.com/showthread.php?t=2726558 , could I perhaps get SafeStrap back and be able to restore the backups I made? The links on that page appear to be to the same (or very similar) firmware that was running prior to this disaster. NC2, Safestrap, etc.
If I can't use Odin to flash the firmware linked in the previous paragraph, and get Safestrap to restore my backups, can I use the firmware, ROMs, and PIT file linked here: http://forum.xda-developers.com/showthread.php?t=2576104 to restore the phone to factory conditions and re-root from there?
Finally, is there any way for me to avoid tripping KNOX at this point? I'm not really sure I care if it gets tripped, but if I can avoid it then I probably should. Am I likely to need KNOX container support on a private device in the near future? Is there any other reason to be spooked about losing KNOX? I really don't care much about the warranty.
Any help with this mess will be **greatly** appreciated!
lintex said:
If I were to use Odin to flash this firmware: http://forum.xda-developers.com/showthread.php?t=2726558 , could I perhaps get SafeStrap back and be able to restore the backups I made? The links on that page appear to be to the same (or very similar) firmware that was running prior to this disaster. NC2, Safestrap, etc.
Click to expand...
Click to collapse
Ok, if anybody comes across this thread looking for answers -- I did successfully use Odin to get this firmware back onto the device. Upon booting, I had Safestrap, was able to boot Slot1, and had root. When I boot from the Stock slot, still no root.
I have not yet attempted to restore the Stock slot backup, because I first want to see if I can boot Slot1 (to get root), and then find/mount the Stock slot image and see if I can find a way to re-root it manually.
lintex said:
Ok, if anybody comes across this thread looking for answers -- I did successfully use Odin to get this firmware back onto the device. Upon booting, I had Safestrap, was able to boot Slot1, and had root. When I boot from the Stock slot, still no root.
I have not yet attempted to restore the Stock slot backup, because I first want to see if I can boot Slot1 (to get root), and then find/mount the Stock slot image and see if I can find a way to re-root it manually.
Click to expand...
Click to collapse
Using any other slot other then stock is going to be problematic. So use the stock slot. You are using the nc2 firmware if you have the reboot to recovery bootloop issue. You can flash the nc4 patched firmware in beans firmware thread if you want. Reboot to recovery is not the same as reboot to safestrap. Download a fresh rom. Wipe everything but external sd under the advanced wipe button in safestrap. Flash your new rom making sure stock slot is the active slot. Setup phone like normal. Make a backup with your now freshly setup rom. Rinse and repeat for new roms. Label your backups if you want to rom jump. Always use stock slot. Odin the nc2 kernel if you have a blackscreen on first boot of a new rom.
RomsWell said:
Using any other slot other then stock is going to be problematic.
Click to expand...
Click to collapse
In my case, Slot1 is simply a rooted ROM that I can use when the Stock slot gets messed up. I have no desire or intent to tinker with Slot1. I consider it as an emergency tool only. It does seem to have an issue though. It never seems to want to power all the way down for some reason.
RomsWell said:
So use the stock slot. You are using the nc2 firmware if you have the reboot to recovery bootloop issue. You can flash the nc4 patched firmware in beans firmware thread if you want. Reboot to recovery is not the same as reboot to safestrap.
Click to expand...
Click to collapse
I am using the NC2 firmware, but I no longer have the bootloop problem. After using Odin to re-install the NC2 firmware from BeansTown, the device was once again able to boot to Safestrap. From there, I was able to select and boot either of the existing slots. Slot1 still boots to root, Stock slot is still unrooted. I should be able to use Safestrap to restore my Stock slot backup and regain root on Slot1, right?
The only reason I have not yet attempted to restore the Stock slot backup is because I hope to boot my rooted Slot1 ROM, mount the Stock ROM image, and fix the Stock ROM image. If not, then I will try to restore the Stock slot backup.
RomsWell said:
Download a fresh rom. Wipe everything but external sd under the advanced wipe button in safestrap. Flash your new rom making sure stock slot is the active slot.
Click to expand...
Click to collapse
I definitely plan to flash a new ROM, soon. I want a fresh clean ROM for personal use, and I also need to find a ROM that supports HDMI -- because I want to get Debian to display on a larger screen. My ultimate goal is to create my own ROMs. I have a bit of experience with kernel tweaking/building, and created a bootable Linux-based DVD image by hand. I believe I will someday be able to tweak phone ROMs as well, but I'm still fuzzy about much of the Android system. Stuff like locks and KNOX seem like quite a mine field and make me very nervous. A blank DVD coaster is one thing, an expensive smartphone is scary.
lintex said:
In my case, Slot1 is simply a rooted ROM that I can use when the Stock slot gets messed up. I have no desire or intent to tinker with Slot1. I consider it as an emergency tool only. It does seem to have an issue though. It never seems to want to power all the way down for some reason.
I am using the NC2 firmware, but I no longer have the bootloop problem. After using Odin to re-install the NC2 firmware from BeansTown, the device was once again able to boot to Safestrap. From there, I was able to select and boot either of the existing slots. Slot1 still boots to root, Stock slot is still unrooted. I should be able to use Safestrap to restore my Stock slot backup and regain root on Slot1, right?
The only reason I have not yet attempted to restore the Stock slot backup is because I hope to boot my rooted Slot1 ROM, mount the Stock ROM image, and fix the Stock ROM image. If not, then I will try to restore the Stock slot backup.
I definitely plan to flash a new ROM, soon. I want a fresh clean ROM for personal use, and I also need to find a ROM that supports HDMI -- because I want to get Debian to display on a larger screen. My ultimate goal is to create my own ROMs. I have a bit of experience with kernel tweaking/building, and created a bootable Linux-based DVD image by hand. I believe I will someday be able to tweak phone ROMs as well, but I'm still fuzzy about much of the Android system. Stuff like locks and KNOX seem like quite a mine field and make me very nervous. A blank DVD coaster is one thing, an expensive smartphone is scary.
Click to expand...
Click to collapse
As long as you stick to the known exploits like safestrap and towelroot then theres no worrys about knoxs. And no real way to perma brick the device. Make sure you stick to offical firmware when using odin and abuse your device like you would any other.
I have a rooted rommed Note 3 with custom recovery. Time to Edge up and need to wipe this device and return to stock. I followed the advice here and even after Odining it it came back just as it was, tried multiple times. I've been Odining phones a long time now not a noob.... . Clearly there's something I'm missing. What's the most current cleanest method to get my device back to 100% stock?
neyenlives said:
I have a rooted rommed Note 3 with custom recovery. Time to Edge up and need to wipe this device and return to stock. I followed the advice here and even after Odining it it came back just as it was, tried multiple times. I've been Odining phones a long time now not a noob.... . Clearly there's something I'm missing. What's the most current cleanest method to get my device back to 100% stock?
Click to expand...
Click to collapse
To restore back to stock 4.4.2, I used Droidstyle's Restore guide here: ( http://forum.xda-developers.com/showthread.php?p=46461911 ). If you want it on 4.4.4 when you return it to Verizon, you can find that firmware at Sammobile...the same restore instructions in Droidstyle's guide should work. Or, just restore to 4.4.2 and take the 4.4.4 OTA.
I had to do a factory reset/wipe cache in stock recovery after ODIN'ing the stock tar.
I also used Chainfire's Triangle Away app to remove the Custom unlock splash that pops up after rooting with Towelroot, as the ODIN restore and stock recovery wipe still didn't remove that. Triangle Away requires root, so you'll obviously need to use that before you ODIN back to stock.
OK, so I recently upgraded to a lollipop ROM on my locked bootloader ATT I337. To get into safestrap now, I have to use NC1 flasher to temporarily flash the NC1 kernel, and then boot into SS, then flash the OC3 kernel to get back. PITA, but it worked. So I tried restoring a backup, and when I rebooted it didn't work (black screen, kept getting FC's of every app, couldn't actually do anything). I rebooted 3 times, after which it seems to be working. Weird. However, if this happens again, how do I get back to safestrap so that I can wipe and reinstall the lollipop ROM? Can I just flash the NC1 kernel via Heimdall/ODIN? If so, which file is it? When I was looking, it seemed like I needed to start from scratch with a full KK flashable package, then upgrade, downgrade, etc, etc.
nola mike said:
OK, so I recently upgraded to a lollipop ROM on my locked bootloader ATT I337. To get into safestrap now, I have to use NC1 flasher to temporarily flash the NC1 kernel, and then boot into SS, then flash the OC3 kernel to get back. PITA, but it worked. So I tried restoring a backup, and when I rebooted it didn't work (black screen, kept getting FC's of every app, couldn't actually do anything). I rebooted 3 times, after which it seems to be working. Weird. However, if this happens again, how do I get back to safestrap so that I can wipe and reinstall the lollipop ROM? Can I just flash the NC1 kernel via Heimdall/ODIN? If so, which file is it? When I was looking, it seemed like I needed to start from scratch with a full KK flashable package, then upgrade, downgrade, etc, etc.
Click to expand...
Click to collapse
Yep, you can flash NC1 kernel in AP slot in ODIN. I'm not sure about Heimdall as I haven't used it.
NC1 kernel: https://www.androidfilehost.com/?fid=23487008491965103
Thanks, hopefully won't have to try it
Just as a bit of an update. I did another safestrap restore, and again ended up booting into the same situation, with black screen, mult FC, etc. Figured out that to exit this, boot into the system bootloader, and from there choose "reboot". For whatever reason, it then boots normally.
[Edit: Nevermind, I'm dumb, I forgot that I can just ODIN the NI2 kernel to get back to Safestrap. Please ignore or mock as needed!]
Quick question, I just want to confirm that my thought process is correct:
I have been running the Alliance Lollipop rom for awhile now, but lately my phone has been acting crappy. For awhile now, it would boot and then say that the SystemUI is unresponsive, and i was just getting lots of random reboots. Anyway, today I had to battery pull, and now it's bootlooping. I get past the Verizon screen, and then the boot animation just spins forever. I'm actually OK with this, because I've been wanting to go back to Kit Kat anyway.
Currently:
I have the FlashFire apk installed, but can't get it to boot completely.
I had originally installed the ROM from a KK kernel -> Safestrap -> OK3 ROM / OD5 Kernel
I can get into stock recovery. I tried wiping my cache and rebooting from there, no dice. I'm on an OD5 bootloader, with an OK3 build.
I see that there's a new fancy Lollipop friendly Safestrap from jrkruse (http://forum.xda-developers.com/verizon-galaxy-s5/development/safestrap-5-0-lollipop-t3313800), but I'm not sure it helps me at this current time.
This is what I think the next steps are:
ODIN - NI2 Stock Kernel, and then NI2 stock Firmware?
Install Safestrap apk?
Reboot to Safestrap recovery and install 4.4.4 ROM?
Am I missing a step? It's been awhile, and all of my old instructions that I had saved are outdated, and I'm trying to get up to date and dust off my memory, and hopefully not spend the rest of my work day flashing things (or people?) Thanks!
I have a Galaxy S4 AT&T i377 UCSGOK3 5.01. I have been fiddling with it and broke the recovery mode. When I select "reboot system now" it reboots, BUT has numerous "Unfortunately...has stopped" errors, finally resulting in unresponsive blank screen. I then have to factory reset and rebuild again. I CAN use recovery mode, IF I remove the battery instead of "reboot system now".
Here are the chain of events leading up this this:
- successfully rooted with Kingroot and replaced with Super SU
- attempted to install TWRP with "Official TWRP App" (I know, should not have done that)
- before attempting TWRP install, made backup of recovery.img (original one) with Official TWRP App
- tried to reinstall original recovery.img with Official TWRP App, Odin, and Flashify. Not working, does not boot into recovery mode.
- installed extracted NB1 recovery.img. From "AT&T Galaxy S4 SGH-I337 UCUFNB1 (Android 4.4.2)" with Odin. This one works, but has the reboot error problem.
Questions:
Is there a Stock AT&T OK3 firmware I can get a recovery.img from or will it still be a NB1 recovery?
Would it be helpful to do a complete re-install of stock firmware? Which one?
Can I install Safestrap on OK3?
Is there a fix for the numerous "Unfortunately...has stopped errors" after recovery reboot?
Thanks in advance,
Todd K.
The bootloader on the phone is locked and cannot run any version of TWRP or any custom ROM that is not based off a stock Samsung ROM.
The reboot problem may be due to a mismatch between the bootloader and recovery.
There is no stock OK3 ROM because AT&T never released a Odin-flashable version of the ROM. OK3 was only offered as an OTA update.
I suggest going back to stock OK3. This thread may help: https://forum.xda-developers.com/showthread.php?t=2616221
The S4 is a great phone and I still have one as my backup phone.
audit13 said:
I suggest going back to stock OK3. This thread may help:
Click to expand...
Click to collapse
Thanks Audit13. just to clarify, Do you suggest sticking with stock OK3 instead of safestrapping to some compatible custom ROM?
For some people, a rooted and no-bloat stock ROM is the most suitable as it's pretty stable and works with many apps.
You can try a custom ROM with safestrap but they'll all be based off a stock ROM which may not run the apps you need.
audit13 said:
For some people, a rooted and no-bloat stock ROM is the most suitable as it's pretty stable and works with many apps.
You can try a custom ROM with safestrap but they'll all be based off a stock ROM which may not run the apps you need.
Click to expand...
Click to collapse
Thanks, I got it to Stock OK3 rooted after a couple of tries. 1st time, I installed the rootable NB1, rooted with towelroot. It wouldn't take the upgrade zips to get from NB1 to OK3. I started over with the plain Stock NB1 ROM, then upgraded in steps from NB1 to OK3, no problem. Then kingrooted and replaced with SuperSU using root.sh script.
I then de-bloated with "System app remover (ROOT)" I wasn't sure what was safe to remove and was afraid of bricking it and having to start over, but it seems to be OK as I was conservative.
Which method do you recommend to de-bloat?
Finally is there a way to do a complete system, app, data, settings backup without CWM/TWRP? Safestrap? ADB? I have Titanium Backup but I don't think it will restore settings and ONLY the apps I want without the bloatware.
Thanks,
Todd K.
I have never owned the sgh-i337 as I'm in Canada and the sgh-i337m (unlocked bootloader, works with TWRP) is the version carried by Canadian carriers.
When dealing with bloatware, I either manually freeze or remove it with Titanium Backup.
toddk63 said:
Thanks, I got it to Stock OK3 rooted after a couple of tries. 1st time, I installed the rootable NB1, rooted with towelroot. It wouldn't take the upgrade zips to get from NB1 to OK3. I started over with the plain Stock NB1 ROM, then upgraded in steps from NB1 to OK3, no problem. Then kingrooted and replaced with SuperSU using root.sh script.
I then de-bloated with "System app remover (ROOT)" I wasn't sure what was safe to remove and was afraid of bricking it and having to start over, but it seems to be OK as I was conservative.
Which method do you recommend to de-bloat?
Finally is there a way to do a complete system, app, data, settings backup without CWM/TWRP? Safestrap? ADB? I have Titanium Backup but I don't think it will restore settings and ONLY the apps I want without the bloatware.
Thanks,
Todd K.
Click to expand...
Click to collapse
I use the mybackup app (formerly called my backup root) to debloat/freeze bloat. It's sort of like titanium backup. You can use flash fire on the play store to do a system backup without safe strap, just using safe strap is better and probably faster.