Ok so hopefully i can get some help with my issue here. I have just resurrected my S4 i thought was dead, but it had the power button sticking problem, and now after about 3 years its going again! This is my problem tho. I got this phone early in the releases. Rooted while on 4.3, unlocked my bootloader on 4.3, ran many ROMS and tons of flashing with no problems. Currently the phone is (ironically) running Ressurrection Remix KK V5.1.0. My Baseband version still states 1545VRUAMDK. I have been trying to get everything up to date but nothing is working right. Im on TWRP version 2.6.0 and yes i have been into recovery since getting it working again. One time when trying to update TWRP i got the Unautorized Software yellow sign sceen. Booted to Download mode and cancelled. I cant get it back into Recovery now and my TWRP wasnt updated. How has my phone became locked again, and how can i fix this? Thanks
If your really still on MDK you can just reunlock your bootloader. Any higher and your stuck on stock, or you could try your luck with flashfire but it only works with touchwiz rims and when I used it on my old s4 it hard bricked it.
You have soft-bricked
Use Odin and flash the no-wipe tar of MDK while in download mode then re-root, etc. You need to use Flashfire to update TWRP. I did the same thing as you recently testing ROM installation with different versions of TWRP. If you update by flashing the img file via TWRP it soft bricks, I found out the hard way.
Related
So my Galaxy S4 has been rooted for over 2 months now. I had heard about a move to SD card update on OTA and had to install it, I originally had TWRP recovery installed with custom backups. But when I went back to a stock backup and attempted to take the update it wouldn't allow me to with a 410 error. I flashed a file through Odin replacing TWRP with stock recovery (still couldn't install the OTA updates) And finally installed the updates through my pc on a Verizon software. I had lost root and got it back an hour later, but now I can't get TWRP back to flash a few mods. (Getting rid of annoying Wifi bar, sound boost, Wifi toggle) Any advice? When I try to install TWRP through GooManager it boots into download Odin mode. And I don't even have access to Odin anymore, I tried to flash back through Odin and it keeps saying Auth fail. Any advice would be appreciated. Feeling kinda lost here, Searched all over the threads and came up with nothing. Just feels less safe with my galaxy s4 without anyway to back it up if anything goes wrong.
Model Number SCH-I545
Android Version: 4.2.2
Baseband Version: VRUAME7
Secure boot status: Samsung
Thanks in advance.
DemonSoul1996 said:
So my Galaxy S4 has been rooted for over 2 months now. I had heard about a move to SD card update on OTA and had to install it, I originally had TWRP recovery installed with custom backups. But when I went back to a stock backup and attempted to take the update it wouldn't allow me to with a 410 error. I flashed a file through Odin replacing TWRP with stock recovery (still couldn't install the OTA updates) And finally installed the updates through my pc on a Verizon software. I had lost root and got it back an hour later, but now I can't get TWRP back to flash a few mods. (Getting rid of annoying Wifi bar, sound boost, Wifi toggle) Any advice? When I try to install TWRP through GooManager it boots into download Odin mode. And I don't even have access to Odin anymore, I tried to flash back through Odin and it keeps saying Auth fail. Any advice would be appreciated. Feeling kinda lost here, Searched all over the threads and came up with nothing. Just feels less safe with my galaxy s4 without anyway to back it up if anything goes wrong.
Model Number SCH-I545
Android Version: 4.2.2
Baseband Version: VRUAME7
Secure boot status: Samsung
Thanks in advance.
Click to expand...
Click to collapse
Don't know how you came up with nothing cause its posted all over the place. I hate to say it but you should have read FIRST and updated second. You are now officially screwed. At the present time there is only a root method for me7. You CANNOT install any custom recovery on that firmware. They changed/locked the boot loader with that update. No flashing back to MDK, no nothing. That is why there is a sticky in the general thread called Bounty. There is about $3000 worth of donations ready to go to the first person to crack the boot loader. But ad of now, no solution. Sorry man, always read first before you OTA. Hope you enjoy you apps2sd.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
It's not as though this isn't well documented- it's all over the forum and should be common knowledge at this point. You now have a device on which the loki exploit has been patched. You cannot install a recovery, kernel, or rom at this point.
If there is ever another exploit discovered, I would hope you have learned a lesson about die diligence and blindly flashing updates without having an inkling about what the update entails. Had you done your die diligence, you would have not only known about the patched bootloader, you would have also known how utterly useless the "apps to sd" feature is.
Sent from my SCH-I545 using Tapatalk 4 Beta
Wasn't just the App 2 SD I also wanted to leave hyperdrive to go back to stock. Hyperdrive would constantly crash when I run the OTA app. And S health wouldn't properly count correctly (Not that S healths important) But still a minor bug. I appreciate everyone's response, and will be keeping an eye out for the next exploit (if). Least I won't be spending all day browsing for a way to install a custom recovery. And SQLite Editor helped remove the Wifi annoying notification and added a wifi toggle. (main things I wanted to mod) And I am pretty sure there is a way around the sound increase without flashing. Anyways, sorry I was dumb and wasted 5 minutes of your guys time. And thanks for the advice. Will leave a small 20$ tip to the donations also.. xD
Hi guys,
I am trying to help someone get their phone back to stock. It's a verizon galaxy note 2 and all the information I have is that they tried to root or rom it and now it doesn't start (and to get it to boot you have to remove/put in the battery)
I'm following droidstyle's guide and I can get as far as starting the odin flash process to stock, but it goes for a few minutes and then I just get a FAIL.
UPDATE1: So I tried again but with the root66 stock VRALJB and it passed but I'm getting the system software not authorized message. I'll keep trying some things..
Anyway I can get this thing up and running again?
UPDATE2: I'm flashing the stock roms semi-successfully, but even after a PASS on the flash, I get the "Verizon has detected unauthorized software" message. Any ideas?
Bascotie said:
Hi guys,
I am trying to help someone get their phone back to stock. It's a verizon galaxy note 2 and all the information I have is that they tried to root or rom it and now it doesn't start (and to get it to boot you have to remove/put in the battery)
I'm following droidstyle's guide and I can get as far as starting the odin flash process to stock, but it goes for a few minutes and then I just get a FAIL.
UPDATE1: So I tried again but with the root66 stock VRALJB and it passed but I'm getting the system software not authorized message. I'll keep trying some things..
Anyway I can get this thing up and running again?
UPDATE2: I'm flashing the stock roms semi-successfully, but even after a PASS on the flash, I get the "Verizon has detected unauthorized software" message. Any ideas?
Click to expand...
Click to collapse
What version of stock firmware was on the phone when the person tried to root it? If it was mj9 4.3 or above you will have to flash the version that was installed through Odin to get it to work. The bootloader starting in mj9 4.3 doesn't allow to downgrade to previous version.
BluGuy said:
What version of stock firmware was on the phone when the person tried to root it? If it was mj9 4.3 or above you will have to flash the version that was installed through Odin to get it to work. The bootloader starting in mj9 4.3 doesn't allow to downgrade to previous version.
Click to expand...
Click to collapse
Good question. He doesn't really know as he was even newer to this than I am (I've done it on a couple phones in the past only a few times, so I do kinda have the hang of it, but this phone's a bit different).
Can I just try flashing 4.3 or above and see if that works? What would be the way to go if I don't know what was flashed previously?
[I just realized I'm in the wrong subforum, please move to Verizon i535 forum, thanks]
My initial intention was to backup the phone before attempting to install Cyanogenmod on it.
I ran towelroot and installed Rom Manager, and flashed the custom recovery.
Upon attempting to enter recovery, it's telling me that some non-Verizon system software is detected so I can't even get in there to backup my phone. I researched and apparently after 4.2 all the bootloaders are locked and cannot be rommed. That sucks, but anyway, this thing is already running 4.4.2 (just got in from Ebay purchase).
How can I get back the stock recovery? I've searched all over the forums but can't quite find what to do. Something with Odin and a stock image? Does that exist for 4.4.2?
TIA
You can get stock recoveries on the net but if you cant flash it you need to go to samsung-updates.com and download the latest rom for that device, flash it with odin then re root it. If there's a cf-autoroot for it you should use that, otherwise any other recommended method.
If your lastest rom on the website is earlier than 4.3 then dont worry about efs etc as custom roms dont change that
If it IS 4.3 or later do not flash anything lower than 4.3. This is because you dont know what the last stock version was.
Going back to stock via odin should solve any issues with all sammy devices. Common sense and reading a lot goes a long way.
Dont forget to reset to factory when flashing back to stock, most common cause of boot loop.
Sent from a stolen phone!
So I have an Australian (Telstra) S6 Edge 925I with stock firmware (OD1) android version 5.0.2 kernel build April 1st.
PingPong root didn't work (and obviously was ruled out also because of kernel build date)
CF Auto-root has just been sending phone into bootloop, have tried a few variants (925i, 925F, 920f, 920t)
Also tried a kernel flash (as if the phone was on 5.1.1) but just got phone stuck on boot screen.
Tried a TWRP flash, got TWRP to work but bootloop also.
-- I do have a stock firmware that I have flashed to get phone back to normal each time it has soft-bricked.
So it seems that rooting is turning out to be pretty impossible but I have seen so much success for others!
Any help would be greatly appreciated!
[also this could be the wrong place to post so redirect or whatever if you have to]
THanks!
Try the Android unified toolkit. It will help you root the proper way for your variant.
http://forum.xda-developers.com/gal...lkit-skipsoft-android-toolkit-galaxy-t3101195
Unfortunately, toolkit didn't work for me. When I was going through root process, I flashed TWRP; latest version caused some weird brightness/colour issue so I couldn't use it, flashed the recommended version, and touch screen wouldn't work. Flashed a version in between which worked, but couldn't boot into OS because of bootloop.
So unfortunately I'm still quite stuck. Toolkit seems like a great tool though, if only it would work. I'm certain I'm not doing anything wrong.
So I paid ("donated") for the pro version so I could get it done that way... Yep, device still went into bootloop... Not sure what's going here but now I have also wasted money.
in 5.1.1 you need to have a custom kernel flashed..look into my twrp thread..
CF Auto Root updated and works on my Phone. S6 Edge 925I
Still having trouble installing a recovery though
After an unsuccessful flash of Xposed Framework with Chainfire's FlashFire Beta, my device wouldn't boot past the AT&T logo. I attempted to flash NB1 stock firmware using Odin from OC4, but I have the same issue.
Specifics
Device - Samsung Galaxy S4 AT&T (jflteatt)
Firmware - NB1 Stock I think, KNOX flag is untripped but download says I have custom Android version. Tried flashing with Odin and got reset/pass. KNOX flag was tripped before, I read its an eFuse so I'm confused
Should I try flashing again or what... I'd like a quick answer as I currently have no phone. Mod feel free to move this if its in the wrong forum. If you need more information just let me know
Samsung devices are know to have issue with xposed. They made changes to the art runtime and last I heard xposed has not fixed it yet.
So if I want Xposesd I should stay on KitKat
How can I get my device working... I've tried what other threads suggested (cache wipe, factory reset, battery pull for thirty seconds). Should I try the stock image again with Odin or try Kies?
bsch27 said:
So if I want Xposesd I should stay on KitKat
How can I get my device working... I've tried what other threads suggested (cache wipe, factory reset, battery pull for thirty seconds). Should I try the stock image again with Odin or try Kies?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
xposed works fine on lollipop, but you have to use wanams version of the framework for tw
OK, thanks for the advice. FlashFire can run with a locked bootloader, right?
Also, I still can't figure out how to get my phone booting again I would greatly appreciate advice on how to get past the at&t logo
EDIT
My bootloader is locked so I can only flash with Odin and stock recovery. Took the AT&T OTA before I knew what I was doing.
I found the solution! I was trying to flash a MBL stock AIO with Odin, but after I took an OTA from AT&T a while back, they locked downgrading that far because it's vulnerable to Loki. I found a thread on another forums that stated the firmware was mislabeled. I feel lucky, could have hard bricked it! I managed to install a (proper) deodexed NB1 firmware, rooted it with Towelroot, and upgraded to Lollipop through a FlashFire flash. I was able to install Xposed successfully. Thanks for all the help! It's greatly appreciated!