Hey guys,
So I've got a problem. When I had originally rooted my phone in the beginning, I hadn't installed safestrap; I installed everything else: busybox, superuser, etc. So I kept on regularly using my phone and what not, updating and making sure I kept root. I was able to follow muniz_ri's tutorials to stay up to date and keep root. So eventually I was on OE1 stock rooted rom and had stopped there (accidentally accepted an OTA update after OE1 so I quickly froze the update thing [forget what it's called] through TiBU, hence not being on the most current firmware).
I wanted Snapprefs but needed Xposed. And to get Xposed, you need safestrap (from my understanding). I followed this to get safestrap (I think that's what the overall goal of the tutorial was for) and got safestrap working. Then, tried to install xposed using this and this. Successfully got the app, but then it said something along the lines of "you have not installed the framework" or something like that (that would be the zip file that I had to download right? The file that came from following the flow chart?). Used safestrap to install the framework (aforementioned zip file), then rebooted. However, after the Samsung Galaxy S5 menu and the safestrap menu, the screen just stays black. There is nothing. When I have my phone connected to the computer, the computer makes its jingle like it recognizes it (however, nothing comes up on the computer), the phone stays black for 2-3 minutes maybe, then boots into recovery mode (not safestrap recovery but stock recovery, where you use the volume buttons). I did a wipe data/factory reset (or whatever the option is called) in the stock recovery menu hoping it would fix something but it didn't. Just trying to include as much info as possible. Would flashing with this in Odin help? Read somewhere that it would put me back at square one so I could do everything over again, which I am not opposed to. However, I thought you couldn't downgrade from OE1 or anything higher?
I'm at a loss as to what to do next. Searched everywhere but couldn't find anyone with the same problem as me. Any help would be appreciated.
Thanks guys!
P.S. Sorry for going parentheses crazy
Found out what to do right after posting. Had to flash the BOE1 factory tar image in ODIN so back to stock, unrooted with all this bloat
Will be checking back periodically in hopes of a root method for latest firmware.
Related
ATT Galaxy S4 currently running Goldeneye 6.0 and TWRP 2.6.0.0 (never installed MF3 base, but have tried both MF3 and MDL modems)
First odd thing...
[About->Status->Device Status] is listed as "Sd card" instead of the more common "Official" or "Custom".
Anybody know what that means or is telling me?
This is the latest thing I've noticed with my phone, which has been having all sorts of issues lately that I cannot seem to figure out. My main problem is, I can reinstall a new ROM, boot into the ROM, change settings around, reboot just fine, but, as soon as I install anything from the Play Store, the next reboot will hang on the initial Samsung splash screen. Wiping is the only fix I've found, and fixing permissions in TWRP errors out with an error that it cannot chown one of the new/updated .apk files.
Both Goldeneye 5 and 6 are doing this now (5.0 was installed and rock solid for several weeks before this all showed up...it started sometime after I decided to try out a couple of the aroma roms and then came back to GE).
Used ODIN to go back to factory rom, re-rooted/installed TWRP, then reinstalled GE6.0, but the same thing happened. Everything looked good until I ran updates from the store, then I was stuck again (note: used Root Explorer to check to permissions on the updated apks before rebooting and they were all correct (755)).
Other things I've noticed are:
1. Sometimes, on any reboot, the startup locks at the initial Samsung screen and I have to long press the power button to get it to reboot. It usually boots the second time around (this is before I install any additional apps and am completely unable to reboot).
2. Sometimes when wiping cache, davlik, and/or data, TWRP will seem to hang for up to a minute when trying to initialize the partition. A couple of times it even hard reboot my phone when I did a cache+davlik wipe.
3. I rolled back to a recovery image just fine; however, it was a couple months old. Everything started off looking great, but once I updated to a new ROM, my issues returned.
Trying Heimdall to go back to factory; however, I'm having issue with my laptop and getting the Zadig drivers installed. While I'm working that out, figured I'd see if anyone else has any suggestions on what else I should be trying or looking out.
thx
I would flash your phone back to MDL stock with odin using the mdl tar. This should format your paritions correctly. You could also reinstall MDL using kies since they still don't support MF3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
My N7 16GB WiFi, rooted but stock, updated successfully to 4.3 some time ago. Basically, I used Voodoo OTA to save the root, let the OTA do its work, then restored root using Voodoo OTA. It's worked flawlessly since then.
Suddenly, after weeks with no issue, it started insisting it had to install 4.3 from a downloaded file. It nags constantly, which makes it hard to use the tablet. I've got CWM as the recovery so whatever file it's trying to install won't work from there. The only way I can find to go back to stock recovery involves wiping the tablet. I don't want to do that, unless there's no other alternative.
I looked for the update.zip file in the location that the tablet insists its stored at (root of SD card), but there's no file there by that name that I can find. It only shows up if I allow the nag screen to try and install it. Of course, CWM says that it can't verify the file and aborts the install. Which puts me right back at the ever-present nag screen.
Just to be clear, I am already running 4.3. This whole situation came up months after I'd upgraded. Is there anything I can do to stop the upgrade notices, short of running a factory reset and having to set up the tablet again from scratch?
May have found an answer. Used Wug's toolkit to force-restore the standard recovery. Had to do some old ADB driver removal for a bunch of other Android devices first. Appears to have deleted the unnecessary update file as part of the process. Will keep an eye on it going forwards, but think it's good.
Nope -- didn't work. Had to do a full factory reset/restore to out-of-the-box condition to get it to stop constantly trying to re-upgrade to 4.3. Annoying.
First time poster here.....in DESPERATE need of help!
So here's the rundown: After many attempts, I was finally able to update to KitKat 4.4.2 on my G2 with root intact. I wanted this for flashing the camera for 4k and 120fps modes. I attempted to install it today via TWRP but now I've basically bricked my phone.
Here's what I did:
- Installed FreeGee
- From inside FreeGee, I installed TWRP
- Installed TWRP Manager
- Copied .zip file to sdcard
- Booted into recovery mode
- Installed camera update
- Restarted and got a neverending LG Logo screen
I have since attempted every which way to recover from this. At this point, I don't even care about my data, I just want a working phone back! I am receiving no errors other than a frozen logo screen.
Here's what I've tried thus far with no success:
- ADB sideload (said phone was connected, got the dreaded "cannot read file" error no matter what I did).
- Factory reset
- Custom wipe of all but sdcard data
- LGFlashTools attempt to restore back down to 4.2.2 "o".....phone will not connect (read more below)
- Attempted fastboot flash from CMD prompt, just said "waiting for phone" forever
Some information......I CANNOT get the phone to be recognized on my PC when in "Download Mode". It never moves past the small Download Mode label into the "Firmware Update" with the big circular arrows circle. If I am in TWRP Recovery (which I get to by holding the Power and Volume Down button [original factory reset]), the PC does recognize the phone, but only under a new label called Android Phone, not Ports. I cannot change the COM ports at all as there is no option given under Properties.
I am at my wits end here. Any idea what I can do? It still appears to function normally under TWRP interface, but outside of that it's a brick. Please please PRETTY Please, anyone been in this situation and know what to do?
Thanks for any guidance.
Just wanted to give everybody an update here in case someone else is in the same situation.
So Sideload REFUSED to work even with the correct names typed. So I scratched that approach.
I anded up using the adb "push" method to send the zip file to the phone. I was having so much trouble with it at first, but I realized that was because I was going into sideload mode on the phone! You DO NOT turn on the sideload mode in TWRP if trying to push a file to the phone. You simply need the device recognized in the command prompt "adb devices" to say "23908hjf982j0e8jdf2 RECOVERY", or something to that effect. If you have sideload mode turned on, you will get the error, "error: closed". Well duh, it's closed for a sideload function! I should have caught this earlier.
ANYWAY, once I pushed a CyanogenMod 11 rom to the phone, it installed and booted right up! I didn't like it, however and wanted to go back to stock 4.2.2. So I downloaded the stock LG Jellybean rom and attempted to install it but it failed. Not sure why. I then downloaded KitKat 4.4.2 and installed it but that also failed, and this time it REALLY bricked it. I was getting loading errors on the LG Logo screen and it would shut off and act like it was turned off. At this point, I tried to restore to CyanogenMod from TWRP recovery, but it didn't work. Go figure.
I had a bricked phone. It wouldn't even boot into TWRP anymore due to the stock rom being partially installed (but failed).
Just when I thought all was lost, I attempted the old LGFlashTool reboot. I figured that maybe, just MAYBE....the Download Mode was fixed due to the partially installed stock ROM. I was right! I cleared all my old testing/configuration drivers on my PC and reinstalled the stock LGUnitedMobile 3.10.1 drivers, set the phone to download mode and VOILA! It FINALLY popped under a newly showing PORTS (COM & LPT) in my device manager. I configured it to COM41 as needed, configured LGFlashTool to load up the stock 4.2.2. jeallybean ROM, put the phone into Download Mode once again and LGFlashTool FINALLY recognized it and loaded up the stock ROM as it did the other day I tried it.
I am now on 4.2.2. rooted "q" (updated from "o" to "q" after installing SuperSU Pro and checked the Survival Mode option). I am moving up to KitKat 4.4.2. with Survival Mode on, which will keep my Root ability (Yes, it DOES work and have already verified it worked before all hell broke lose due to the xdabbeb's update on 4.4.2. (I probably did something wrong....not saying it's his fault!).
Anyway, just thought I would post this so that it may help someone else out.
Peace out gents.
goodlookin1 said:
I am now on 4.2.2. rooted "q" (updated from "o" to "q" after installing SuperSU Pro and checked the Survival Mode option). I am moving up to KitKat 4.4.2. with Survival Mode on, which will keep my Root ability (Yes, it DOES work and have already verified it worked before all hell broke lose due to the xdabbeb's update on 4.4.2. (I probably did something wrong....not saying it's his fault!).
Anyway, just thought I would post this so that it may help someone else out.
Peace out gents.
Click to expand...
Click to collapse
If you eventually want to have recovery as well you'll need to go back to 10d as later versions (o,q) break loki and are not compatible with the custom kernel needed to load stock based KK roms. But if you just want root until the next ota you're set.
I tried to flash xdabbebs mod on KK using flash gordon flasher and it worked fine for me.. http://forum.xda-developers.com/showthread.php?t=2250555
Sent from my LG-D800 using XDA Premium 4 mobile app
SOLVED - Doing a factory reset from the stock recovery seemed to clear it up.
I updated to Lollipop via Chainfire's "update without losing root" instructions and that went well (no issues). However I was not happy with a couple things and decided I wanted to let my phone live out its life on KitKat. I thought I could just flash the: "G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_HOME.tar.md5" file however the phone is stuck on the boot screen.
I have searched for "unbricking" as that's what most call it, but I only see everyone saying to flash the ANK2 file.
Please let me know what I am missing.
Thanks
I have a Samsung Galaxy Tab 4 8” SM-T330NU running 5.1.1. The box tells me the ‘real’ model is SM-T330NYKAXAR. I decided to root the phone, because I want to get to Marshmallow and to get rid of this extra bloat where. (I will mention I have a good amount of experience rooting, including just rooting my Droid Turbo).
Anyway, after a lot of looking around the forums, I decided to use the CF-AutoRoot method (CF-Auto-Root-milletwifiue-milletwifiue-smt330nu) to root. I got Odin and installed it (along with the Samsung drivers) onto my Windows 10 PC; set debugging, on; and ran Odin. I followed the directions and it appeared to root properly; and I got to CWM recovery. Woo hoo! (Or so I thought)
So then after making sure I can get into recovery, I rebooted back into my stock ROM. Unfortunately, I got stuck at the Samsung logo; tried rebooting multiple times; even did a factory reset/wipe (as per instructions I saw on the forum) but to no avail. (Even let it set for over an hour but it never got past the Samsung logo).
After some more reading, I figured I might as well go ahead and flash a new ROM; so I think (if I remember correctly) I tried the JazzROM. It got up to about 69% and then it just quit - screen went black, and then it rebooted back to Odin mode. Obviously it didn’t work; then when I tried to get back into recovery to wipe and try the flash again, I got the message ‘Cannot mount \system - invalid argument’.
Again, after much reading and trying, I was able to get TWRP recovery installed and then wiped/formatted the system partition, which I had read would help get rid of that error. And it did seem to fix it.
So I can re-root with Odin without any issues; I can get to Recovery (either CWM or TWRP depending on which I flash), but no matter what I do, it either gets about 2/3 the way thru the flash process and then reboots back to Odin mode; or (using TWRP) I can get it certain ROMS to flash successfully, but after rebooting it goes right to Odin mode (saying it could not do normal boot). I even tried loading a stock, with the same result.
Which leads me to my first question: Exactly which ‘stock’ file should I be loading? I am having a hard time finding one - either it leads me to a dead end, or the download doesn’t work.
- When in CWM recovery, it shows the following:
At the top:
LMY47X.T330NUUEU1BOI1
Bottom:
#Manual Mode#
— Applying Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
Are these correct?
- When TWRP is installed (3.0.0-3) it starts by asking me about the ‘Unmodified System Partition’ and whether it should be kept read-only or allow modifications. I assume allow mods? Otherwise I don’t see how you could apply a new ROM? (I haven’t seen this in a while, not in my install of TWRP to the Droid Turbo). So just want to make sure I am selecting the right option.
- I am also concerned about whether I am using the right packages for this tablet. Based upon what I see on the box and sticker (which I still have) this should use the stock ROM LMY47K.T330NUUEU1BOI1 model; but I’ve also seen things referring to a BOG1 model? Mine is the T330NU English and (I assume) US model since I am in the US.
Any ideas as to what is going on? If I can at least get back to stock I could then start from scratch with the appropriate info; or just install one of the new ROMS (I’ve tried Jazz, Dirty Unicorns, UltraStock). I don’t think I am ‘bricked’ because if so I wouldn’t be able to get to Odin or recovery. Any help appreciated here. Thanks!
-Tom (Chimp)
NM, finally got it working, running DU and running fantastically, if I may say so. Getting TWRP to install finally fixed everything.
Sent from my SM-T530 using XDA-Developers mobile app