It's been 3 days I've been up and down the forums, was on CM11, dirty flashed over the nebulas, ran into a few problems decided to go back and make it a clean flash, got 4.1.1, couldn't find one CASUAL that worked, went to 4.1.2, same problem, Yes i tried other cables, other computers, no difference.
Then updated 4.3 boot looped all kinds of problems tried Nand Erase All, didn't work, one way or another root66 stopped working. nothing would flash, it would all fail or if it did say it worked it just boot looped,
I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5
To work. So now I'm 4.3 Stock, with no root.
I want to get back to Nebulas,
I want to take this step by step because it's been a nightmare and I can't find any solutions to questions that have been asked before.
From what I research the next step is to flash:
sch-i605-16gb.pit file
+
KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5
But when I try I get sboot.bin fail. Got a tip somewhere to flash the just the PIT, this actually fixed it without needing to flash anything else.
Now I know I'm down grading so it's going to boot loop because nothing is compatible. Boot into recovery and do a wipe to fix that. I boot into the OS just to make sure I'm doing 4.1.2. Which it is. and enable usb debugging.
Now to root and bootloader.
I try the newest verison of CASUAL R991b-JenkinsBuild
I get Error Failed to confirm end of pit file transfer
Pit Upladoing Failed
ok, so I pull battery and reboot. Trying R515b because that's the one in the tutorial:
I get Pit upload successful
Error: Bootloader upload failed!
This corrupt the bootloader and it will fail the boot, taking a step back and reflashing the mc3 fixes this.
Then I try this tip "most times you will need to delete and uninstall the Samsung Mobile usb from your Computer's device manager while ur device is connected already in download mode. i failed several times to execute casual successfully until i did this and it worked like charm!"
That didn't do anything, Tried verision 535 same results.
Said screw that I'll just flash some Root and recovery. But it always fails to flash recovery.img or if i put in the PIT and say repartition it will fail after the NAND Write Start. I've tried
openrecovery-twrp-2.6.3.1-t0ltevzw.img
CF-Auto-Root-t0ltevzw-t0ltevzw-schi605.tar.md5
philz_touch_6.07.9-i605.tar.md5
and none work.
Any idea what I should do at this point? Everything fails the only thing I can do is flash 4.1.2 and 4.3 reliable.
In the middle there you say at one point you were stock 4.3. If that is correct you are done. Currently you can not unlock 4.3. You can only root with Kingo.
Galaxy S4 way works on MJ(
TonikJDK said:
In the middle there you say at one point you were stock 4.3. If that is correct you are done. Currently you can not unlock 4.3. You can only root with Kingo.
Click to expand...
Click to collapse
Not true -- but it took me HOURS to find it:
http://forum.xda-developers.com/showthread.php?t=2565758
give the guy a thanks, huh?
TX_Jax said:
Not true -- but it took me HOURS to find it:
http://forum.xda-developers.com/showthread.php?t=2565758
give the guy a thanks, huh?
Click to expand...
Click to collapse
I must be missing it. I see that it roots, but I don't see where it unlocks a VZW bootloader.
TonikJDK said:
I must be missing it. I see that it roots, but I don't see where it unlocks a VZW bootloader.
Click to expand...
Click to collapse
That's correct -- so you are looking to unlock the phone? Have you tried the fee-for-service sites?
There is no unlock method on any 4.3 Samsung device that I'm aware of.
TonikJDK said:
In the middle there you say at one point you were stock 4.3. If that is correct you are done. Currently you can not unlock 4.3. You can only root with Kingo.
Click to expand...
Click to collapse
But right now I'm on 4.1.2, I flashed back to that. that's where i've been trying to find a way to get to the next step.
mavermc said:
But right now I'm on 4.1.2, I flashed back to that. that's where i've been trying to find a way to get to the next step.
Click to expand...
Click to collapse
You are unable to flash a recovery because your bootloader is locked, from when you flashed 4.3. That was game over. How you got part way back to 4.1.2 I don't know, but be careful. I would flash back to 4.3, root it and hope someone unlocks the bootloader for 4.3
TonikJDK said:
You are unable to flash a recovery because your bootloader is locked, from when you flashed 4.3. That was game over. How you got part way back to 4.1.2 I don't know, but be careful. I would flash back to 4.3, root it and hope someone unlocks the bootloader for 4.3
Click to expand...
Click to collapse
Well that really sucks, with this soft root, any chance I could atleast get back my NFC on while screen off?
u can. look for the exposed installer, I seen it on here somewhere. theres a option for nfc on with screen off on it. I'll try to remember where I seen it and post for ya.
mike7728 said:
u can. look for the exposed installer, I seen it on here somewhere. theres a option for nfc on with screen off on it. I'll try to remember where I seen it and post for ya.
Click to expand...
Click to collapse
I use the Wanam Xposed module for NFC with the screen off.
jcollier said:
I use the Wanam Xposed module for NFC with the screen off.
Click to expand...
Click to collapse
I got Xposed working so I'll be checking this out, thanks!
Any idea how to get the features from the other roms in this? like smart scrolling with your eyes and the other features that the [ROM] N3BULA [MJ9] has snuck in from the note 3?
Related
Yes I have searched, yes I have tried google and yes I am still stuck...
I *think* I have tried just about everything and I have read through about 10 "soft brick" or "stuck on samsung screen after rooting on stock ICS" (and most combinations of) but nothing is working. I'm sure it's probably an easy fix but I just can't seem to get anywhere. Here's what happened.....
I googled rooting galaxy not after ICS update and found this http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
It was all I could find about rooting after the ICS OTA update, so I did it. Everything seemed fine. I had CW but no superuser so I DL it from the market as well as my old Titanium pro from back when I rooted my HTC. I rebooted my phone to get it all settled in and decided to run Titanium and get this party started. I got an error message that busybox was not installed so.... I installed it but when I clicked the app on my phone it said it would not install because I didn't have root access.... This is where the confusion starts to set in.
So I restarted to see if I could get into CW but when I rebooted the soft brick started.... I was stuck at the "samsung" screen.
I IMMEDIATELY ran to XDA and began my search. I can still get to DL mode, Odin and CW so I know there is hope. I tried the files listed in the "All in one guide for noobs" and the "Galaxy Note Super Everything Thread (I717)".
There was a suggestion to use Kies but when I put in my serial # and model name i get the "galaxy note does not support initializing" message.
I'm not new to flashing/rooting, although things are a bit different, I have a basic understanding of the process but I ain't no Einstein either...
I also tried to flash the stock Telus ICS rom but I got an error message and my lil droid guy went belly up....
Any help would be greatly appreciated! I love my note and this is killing me...
I have to go to work so if I don't reply immediately its because I have no email access at work.... Especially without my Note....
The steps are correct in the link you gave.
Did Odin3 say success?
Did you get CWM installed?
Did you flash superuser?
Is there a superuser icon in your apps?
Ranger is on it....
I'm thinking we dont have CWM on the device....????
And no SU flash, from within the recovery that doesnt exist....g
He has cwm, he did not flash superuser, Looks like he assumed flashing cwm would automatically root him.
Since you can get into recovery... i would just go ahead and download a Rom zip, transfer to phone by mounting in cwm (mounts and storage if you didn't know) and flash that sumbitch
Oh yep...found that.......Thanks brother....g
That means do or redo steps 13 to 16 in the guide you posted.
agreed....g
im back...
Just got in, thanks for the replies.
Yes I have CWM and can access it. I have tried to flash the CM roms as well as the stock telus ICS rom but was denied at install. I got a "assert failed getprop (ro.build.device)" message and 2 other "ro." error messages when I install the cm nightly quincyatt rom.
rangercaptain said:
The steps are correct in the link you gave.
Did Odin3 say success? Yes
Did you get CWM installed? Yes
Did you flash superuser? Yes
Is there a superuser icon in your apps?
Click to expand...
Click to collapse
Cant see my apps but when I first flashed CWM and was able to see my screen there was a SU app on my home screen because I DLed it from the market.
You need to update your CWM. Get it here:
http://forum.xda-developers.com/showthread.php?p=28040353
Look right under the big green arrow in the first post of the thread.
Readreadread. Then thankbigjoethankbigjoe.
Of course, come back here if further assistance is needed or you solve the issue.
I thought I was on the latest. Someone else suggested that also, so I flashed the touch CWM Updated 04/14
rangercaptain said:
You need to update your CWM. Get it here:
http://forum.xda-developers.com/showthread.php?p=28040353
Look right under the big green arrow in the first post of the thread.
Readreadread. Then thankbigjoethankbigjoe.
Of course, come back here if further assistance is needed or you solve the issue.
Click to expand...
Click to collapse
Yup, thats the one I flashed, its working and I get a successful message when I flashed SU so I assume its there also. Any recommendations of a rom to try and flash? Still hanging at the samsung screen.....
I appreciate the help by the way, I know how frustrating it can be to try and help with tech situations from emails and messages (Hi Mom ).
Thanks has been pushed....
That assert error is in the script used by CWM to flash and it is saying 'wrong rom for your device'. So for sure you have the correct CWM and rom for your phone? Just checking because errors at this point make your phone useless.
rangercaptain said:
That assert error is in the script used by CWM to flash and it is saying 'wrong rom for your device'. So for sure you have the correct CWM and rom for your phone? Just checking because errors at this point make your phone useless.
Click to expand...
Click to collapse
I got my CWM from the link you posted but the rom I am iffy about. Any suggestions for a rom to try and flash? something stable?
EDIT: going to try and flash this rom and modem http://forum.xda-developers.com/showthread.php?t=1801689
Downloading now..... Sloooooowly. lol
Holy McCrappy dance!
Okay... so I flashed the stock ATT with odin. just at start screen now.... Don't think it is rooted so now.... How do I get back to telus and root right the first time?
Edit: so it appears the ATT rom was a GB ver so I am assuming that I was somehow reverted to GB instead of my stock ICS. Now to try and flash a stock Telus GB rom, update then try to root.... AGAIN! Thank gawd I don't have a $600 paperweight now!
Thanks everyone
I recommend this rom:
http://forum.xda-developers.com/showthread.php?t=1766933
Select the pure stock. There is no point in using the Telus rom.
Please read carefully. Good luck.
^^^ what ranger said. No point in repeating trust and go!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
rangercaptain said:
I recommend this rom:
http://forum.xda-developers.com/showthread.php?t=1766933
Select the pure stock. There is no point in using the Telus rom.
Please read carefully. Good luck.
Click to expand...
Click to collapse
I would like my ota ICS back but I guess no bother huh? I am back on the stock telus GB and for some reason it wont let me update to ICS anyway.... LOL
Might as well root it up and go go go!
Thanks again Ranger.
WOW! that pure stock is a big ole file! lol
Ok, take it easy for a few days. Just read up and, now that you've survived the worst scenerio, you might want to try a more custom rom or other modifications. Pretty soon you will be pulling someone else's a$$ out of the fire. Good luck.
I think I'm okay now. Was a skeerty one though. Lol
Very quick question. I have "root only" on my dad's S4 and he's not using root like he thought so if he just takes the update that keeps nagging him, won't mess anything up other than ruining the fact it would patch the root, correct?
K-OtiK said:
Very quick question. I have "root only" on my dad's S4 and he's not using root like he thought so if he just takes the update that keeps nagging him, won't mess anything up other than ruining the fact it would patch the root, correct?
Click to expand...
Click to collapse
If all that has been changed is root access, you will probable be ok. Should update and root access will be lost.
ellisz said:
If all that has been changed is root access, you will probable be ok. Should update and root access will be lost.
Click to expand...
Click to collapse
So now I have a problem....I did what you said, it worked just fine. The issue was that it left the "custom/lock" splash screen on. We left it alone and there were no issues. Well now, he has a problem with his phone and has to have it "warrantied"
We have an even bigger problem. I figured out that the right way would have been to just unroot it the proper way from the beginning. Welp unfortunately that is not possible because he took the 4.3 update and now has VRUEMJ7 any ideas how to fix this? Or are we screwed until a new exploit is available?
Please help!?
K-OtiK said:
So now I have a problem....I did what you said, it worked just fine. The issue was that it left the "custom/lock" splash screen on. We left it alone and there were no issues. Well now, he has a problem with his phone and has to have it "warrantied"
We have an even bigger problem. I figured out that the right way would have been to just unroot it the proper way from the beginning. Welp unfortunately that is not possible because he took the 4.3 update and now has VRUEMJ7 any ideas how to fix this? Or are we screwed until a new exploit is available?
Please help!?
Click to expand...
Click to collapse
Your flash counter should be fine, i would think maybe a factory reset and as many as 3 or 4 reboots you should be fine. Basically if you only every rooted before this update you like only get the custom padlock because of the exploit, not from system being changed.
Hard to say for sure since this update is so new, a lot of security has been put in place.
Thing is though if you are warrantying anyways, you might as well try wiping. Backup whatever you can.
Sent from my SCH-I545 using Tapatalk
kdo23 said:
Your flash counter should be fine, i would think maybe a factory reset and as many as 3 or 4 reboots you should be fine. Basically if you only every rooted before this update you like only get the custom padlock because of the exploit, not from system being changed.
Hard to say for sure since this update is so new, a lot of security has been put in place.
Thing is though if you are warrantying anyways, you might as well try wiping. Backup whatever you can.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I've wiped it a time or two already and the "custom" splash screen is still there. :-/
I have the same issue, however I have not tried to wipe yet. I tried the No-Wipe factory restore, however odin fails during the write every time...
Maybe it would work for you:
http://forum.xda-developers.com/showthread.php?t=2301259
K-OtiK said:
Yeah I've wiped it a time or two already and the "custom" splash screen is still there. :-/
Click to expand...
Click to collapse
Full wipe, custom splash gone
Using this link as a guide http://forum.xda-developers.com/showthread.php?t=2301259
and this specific recovery image for the VRUEMJ7 http://forum.xda-developers.com/showthread.php?t=2507253
I was able to completely wipe (and unroot) my dad's verizon galaxy S4. It no longer has the custom splash screen (which was created by Vroot)
I don't know if this is new but what happened was that I bought my Verizon s4 with build mi1.
I went full on noob rooted it and tried to flash twrp with goo manager. I soft bricked my phone I think as I was unable to boot and got the download screen with some red text saying it was unable to boot (don't remember the exact error).
So afterwards I searched for a stock firmware to reflash via Odin and I chose the mdk stock tar. I rebooted into download mode and got it to work. I'm now rooted on mdk with cwm recovery installed via loki method.
However when I install aosp roms I'm unable to receive and end calls. Just throwing the information out there, maybe it provides some insight or something. I'm now back on stock mdk with no issues.
jay876 said:
I don't know if this is new but what happened was that I bought my Verizon s4 with build mi1.
I went full on noob rooted it and tried to flash twrp with goo manager. I soft bricked my phone I think as I was unable to boot and got the download screen with some red text saying it was unable to boot (don't remember the exact error).
So afterwards I searched for a stock firmware to reflash via Odin and I chose the mdk stock tar. I rebooted into download mode and got it to work. I'm now rooted on mdk with cwm recovery installed via loki method.
However when I install aosp roms I'm unable to receive and end calls. Just throwing the information out there, maybe it provides some insight or something. I'm now back on stock mdk with no issues.
Click to expand...
Click to collapse
How the hell did you downgrade? As far as this community is concerned, there is no way to downgrade.
Sent from my SCH-I545 using xda app-developers app
jay876 said:
I don't know if this is new but what happened was that I bought my Verizon s4 with build mi1.
I went full on noob rooted it and tried to flash twrp with goo manager. I soft bricked my phone I think as I was unable to boot and got the download screen with some red text saying it was unable to boot (don't remember the exact error).
So afterwards I searched for a stock firmware to reflash via Odin and I chose the mdk stock tar. I rebooted into download mode and got it to work. I'm now rooted on mdk with cwm recovery installed via loki method.
However when I install aosp roms I'm unable to receive and end calls. Just throwing the information out there, maybe it provides some insight or something. I'm now back on stock mdk with no issues.
Click to expand...
Click to collapse
MANY others have tried, and have checked the code that checks the qfuses... So you are either mistaken, lying, or your phone is some amazing anomaly...
Nothing other then odin and a stock image? have a link to where you downloaded the image from?
Screen shot of about phone screen?
scryan said:
MANY others have tried, and have checked the code that checks the qfuses... So you are either mistaken, lying, or your phone is some amazing anomaly...
Nothing other then odin and a stock image? have a link to where you downloaded the image from?
Screen shot of about phone screen?
Click to expand...
Click to collapse
I'm not lying. It was ODIN/download mode with the green android logo with some red text saying the phone was unable to boot. I tried to flash the mdk tar in that state and it failed so I rebooted into download mode holding down the 3 buttons and it was flashed successfully.
I used this stock image - http://downloadandroidfiles.org/download-sch-i545_mdk_562219_stock_restore-zip/
requested screenshot -http://imgur.com/1IJEBB6
jay876 said:
I'm not lying. It was ODIN/download mode with the green android logo with some red text saying the phone was unable to boot. I tried to flash the mdk tar in that state and it failed so I rebooted into download mode holding down the 3 buttons and it was flashed successfully.
I used this stock image - http://downloadandroidfiles.org/download-sch-i545_mdk_562219_stock_restore-zip/
requested screenshot -http://imgur.com/1IJEBB6
Click to expand...
Click to collapse
Did you buy your phone used?
Sent from my SCH-I545 using Tapatalk
heath2805 said:
Did you buy your phone used?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Would be my second guess. I have seen people think their phone was downgraded after flashing an MDK radio.
Could this be the opposite, where the phone already had custom recovery I could see it having a stock Mi1 rom and showing Mi1 in the about phone while its still MDK base.
I'd love for this to be true, and don't mean to offend the OP... but this has been tried a ton of times and does not work, and its just so much more likely there is some confusion here rather then his phone simply not checking qfuses... Well, hopefully someone smarter than me will pick this apart tonight.
scryan said:
Would be my second guess. I have seen people think their phone was downgraded after flashing an MDK radio.
Could this be the opposite, where the phone already had custom recovery I could see it having a stock Mi1 rom and showing Mi1 in the about phone while its still MDK base.
I'd love for this to be true, and don't mean to offend the OP... but this has been tried a ton of times and does not work, and its just so much more likely there is some confusion here rather then his phone simply not checking qfuses... Well, hopefully someone smarter than me will pick this apart tonight.
Click to expand...
Click to collapse
Yeah but the scary thing is I don't recall ever seeing a MI1 stock build for mdk users.
Sent from my SCH-I545 using Tapatalk
heath2805 said:
Did you buy your phone used?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yea it was slightly used. When I checked it out it had the mi1 firmware and I think someone tried to root it because it had terminal emulator and superuser installed. I ran root checker and it did not have root access so it was a failed attempt.
I factory reset everything at that point though then that's where my story began. Rooted, rom manager > goo manager > soft brick (odin/download mode) > flashed mdk stock > root > loki bypass bootloader for cwm > aosp rom issues with receiving and ending calls > stock with custom recovery
When I downloaded rom manager, I didn't know at the time that mi1 firmware was unable to get a custom recovery installed.
Could he have purchased used developers s4?
jamesd1085 said:
Could he have purchased used developers s4?
Click to expand...
Click to collapse
That's probably it. Now that it has a non-developer bootloader, it's now bootloader locked.
k1mu said:
That's probably it. Now that it has a non-developer bootloader, it's now bootloader locked.
Click to expand...
Click to collapse
It was previously a vrudmi1 bootloader. I don't think that's a dev unit. If it was a dev unit wouldn't I have been able to install the custom recovery successfully before right after rooting? Blah I guess it was a stroke of luck somewhere.
k1mu said:
That's probably it. Now that it has a non-developer bootloader, it's now bootloader locked.
Click to expand...
Click to collapse
Yeah...but seems like once surge gets the rest of the missing parts for his dev mdk tar he should be able to flash it back to dev
jay876 said:
It was previously a vrudmi1 bootloader. I don't think that's a dev unit. If it was a dev unit wouldn't I have been able to install the custom recovery successfully before right after rooting? Blah I guess it was a stroke of luck somewhere.
Click to expand...
Click to collapse
No, it was previously a MI1 build That's not the same as a MI1 bootloader.
You can have a MDK phone running a MK2 ROM. The build will show MK2 even though it's an older bootloader.
k1mu said:
No, it was previously a MI1 build That's not the same as a MI1 bootloader.
You can have a MDK phone running a MK2 ROM. The build will show MK2 even though it's an older bootloader.
Click to expand...
Click to collapse
Oh ok. Thanks. I didn't know that could be the case.
jay876 said:
Oh ok. Thanks. I didn't know that could be the case.
Click to expand...
Click to collapse
Well lets just make sure. Open terminal and type the following:
Code:
su
mount -o remount, rw /system
echo ON >/efs/carrier/HiddenMenu
Then dial *#1234# and post back with a screenshot of that screen
Surge1223 said:
Well lets just make sure. Open terminal and type the following:
Code:
su
mount -o remount, rw /system
echo ON >/efs/carrier/HiddenMenu
Then dial *#1234# and post back with a screenshot of that screen
Click to expand...
Click to collapse
http://imgur.com/uPmLbok
jay876 said:
http://imgur.com/uPmLbok
Click to expand...
Click to collapse
Hmm...looks like good ole run of the mill MDK...keep it...hard to get anymore
jay876 said:
http://imgur.com/uPmLbok
Click to expand...
Click to collapse
Okay, that was unexpected. Tell me how do you know for sure you were on VRUDMI1? Do you have a back up from then?
Open terminal post the output of the following commands:
Code:
su
cat /proc/version
cd /dev/block/platform/msm_sdcc.1/by-name
hexdump -C aboot|grep SW_ID
And since this has already caught surge's attention... He may be able to verify that flashing MDK modem +hlos bin may fix your aosp issues...
Surge1223 said:
Okay, that was unexpected. Tell me how do you know for sure you were on VRUDMI1? Do you have a back up from then?
Open terminal post the output of the following commands:
Code:
su
cat /proc/version
cd /dev/block/platform/msm_sdcc.1/by-name
hexdump -C aboot|grep SW_ID
Click to expand...
Click to collapse
Can't really figure out whats going on here..
First of all if you tried to flash MDK via odin on a MI1 BL you should have gotten an error "SW REV. CHECK FAIL: FUSED: 4, Binary: 1"
I've unlocked my bootloader, rooted and installed CWM custom recovery. Not surprisingly the Sense 6 update will download but it won't install. I tried to flash it manually with CWM but that won't work either. Again, no surprise.
Is there a workaround that I can use to install the Sense 6 update?
appro77 said:
I've unlocked my bootloader, rooted and installed CWM custom recovery. Not surprisingly the Sense 6 update will download but it won't install. I tried to flash it manually with CWM but that won't work either. Again, no surprise.
Is there a workaround that I can use to install the Sense 6 update?
Click to expand...
Click to collapse
Yes, you need the stock recovery not custom recovery to install the ota plus stock rom installed.
jerrycycle said:
Yes, you need the stock recovery not custom recovery to install the ota plus stock rom installed.
Click to expand...
Click to collapse
Ok, I flashed stock recovery and the update looked like it was going to install but it failed about a third of the way through and gave me a red triangle. I rebooted and fortunately the phone is still working. I tried installing the update a second time with the same result. Any ideas?
appro77 said:
Ok, I flashed stock recovery and the update looked like it was going to install but it failed about a third of the way through and gave me a red triangle. I rebooted and fortunately the phone is still working. I tried installing the update a second time with the same result. Any ideas?
Click to expand...
Click to collapse
You have to have a pure stock rom. You may have to nandroid a stock or RUU but you have to decide that, but it have to be stock not root or any system file edits. Sorry, missed the bootloader need to be locked.
jerrycycle said:
You have to have a pure stock rom. You may have to nandroid a stock or RUU but you have to decide that, but it have to be stock not root or any system file edits. Sorry, missed the bootloader need to be locked.
Click to expand...
Click to collapse
My rom is stock (Telstra Australia) but I've installed a few Xposed mods. If I do a factory reset I'm assuming that will take the rom back to stock. If I then remove root and relock the bootloader will I then be ok to flash the Sense 6 update?
Mate, I'm having same issue, Telstra Australia.
Check out his thread. I think you need to save three files that get wiped when you unlock bootloader. The update looks for them. I'm still trying to get it to work.
http://forum.xda-developers.com/showthread.php?t=2800140
Cjohn1200 said:
Mate, I'm having same issue, Telstra Australia.
Check out his thread. I think you need to save three files that get wiped when you unlock bootloader. The update looks for them. I'm still trying to get it to work.
http://forum.xda-developers.com/showthread.php?t=2800140
Click to expand...
Click to collapse
Thanks. I tried the 3 files thing and it didn't work for me probably because the bootloader was still unlocked. I got sick of dicking around with it and decided to try to get S-off which I'd been having trouble achieving with Hboot 2.49. Finally got S-off and then flashed this.... http://forum.xda-developers.com/showthread.php?p=53890999
Cheers.
appro77 said:
My rom is stock (Telstra Australia) but I've installed a few Xposed mods. If I do a factory reset I'm assuming that will take the rom back to stock. If I then remove root and relock the bootloader will I then be ok to flash the Sense 6 update?
Click to expand...
Click to collapse
appro77 said:
Thanks. I tried the 3 files thing and it didn't work for me probably because the bootloader was still unlocked. I got sick of dicking around with it and decided to try to get S-off which I'd been having trouble achieving with Hboot 2.49. Finally got S-off and then flashed this.... http://forum.xda-developers.com/showthread.php?p=53890999
Cheers.
Click to expand...
Click to collapse
Which method did you use to gain s-off? I couldn't get it to work.
Cjohn1200 said:
Which method did you use to gain s-off? I couldn't get it to work.
Click to expand...
Click to collapse
Nothing was working for me and I'd almost given up but I was pointed to this.... http://firewater-soff.com/instructions/
I was already rooted but for some reason the first method wouldn't work for me. ADB is very new to me so I may have done something wrong even though I tried it a couple of times. I used the second method but didn't use temproot cause I figured as I was already rooted I didn't need it. When I used the commands in the second method S-off was achieved.
The rom I mentioned above looks really good btw.
Cjohn1200 said:
Which method did you use to gain s-off? I couldn't get it to work.
Click to expand...
Click to collapse
appro77 said:
Nothing was working for me and I'd almost given up but I was pointed to this.... http://firewater-soff.com/instructions/
I was already rooted but for some reason the first method wouldn't work for me. ADB is very new to me so I may have done something wrong even though I tried it a couple of times. I used the second method but didn't use temproot cause I figured as I was already rooted I didn't need it. When I used the commands in the second method S-off was achieved.
The rom I mentioned above looks really good btw.
Click to expand...
Click to collapse
Yeah it does look pretty slick. Wasn't sure about the large icons through. I watched a review on youtube. Looked a little strange...
Cjohn1200 said:
Yeah it does look pretty slick. Wasn't sure about the large icons through. I watched a review on youtube. Looked a little strange...
Click to expand...
Click to collapse
Not sure what you are referring to there. I didn't see anything overly large. Was that on the stock launcher? I'm using Apex.
When the OTA update fails and you get the red triangle, have you tried holding the vol up button then pushing the power button?
This should take you to stock recovery and you can see why the update failed...
Might give you a point to work from.
Cjohn1200 said:
When the OTA update fails and you get the red triangle, have you tried holding the vol up button then pushing the power button?
This should take you to stock recovery and you can see why the update failed...
Might give you a point to work from.
Click to expand...
Click to collapse
No I didn't do that. I'm on a custom recovery and custom rom now though.
I'm all back to stock with the three files saved. Just waiting for the OTA update to download now.
I'll let you know if it works.
So what's the sense 6 camera app like? I have never really been happy with the camera on the max.
Cjohn1200 said:
So what's the sense 6 camera app like? I have never really been happy with the camera on the max.
Click to expand...
Click to collapse
I haven't had a really good look at it but I don't like the fact that you have to tap a button before you choose video. On the old app both camera and video were one tap away. Now if you aren't in video already it's 2 taps.
appro77 said:
No I didn't do that. I'm on a custom recovery and custom rom now though.
Click to expand...
Click to collapse
I ended up getting this to work....
When you save the three files that are missing with a root file manager, you have to save them to \data\preload NOT system\data\preload
Worked a treat after I did this:good:
How did you get firewater to work?
I keep getting a kernel error. It says that my kernel has a anti firewater patch. Very frustrating i just want to be able to lock my bootloader so my finger print scanner works properly again.
Cjohn1200 said:
I ended up getting this to work....
When you save the three files that are missing with a root file manager, you have to save them to \data\preload NOT system\data\preload
Worked a treat after I did this:good:
How did you get firewater to work?
I keep getting a kernel error. It says that my kernel has a anti firewater patch. Very frustrating i just want to be able to lock my bootloader so my finger print scanner works properly again.
Click to expand...
Click to collapse
That's interesting what you say about the 3 files. Now I know why it wouldn't work for me. Regarding Firewater I just followed the instructions in the link I posted earlier.
I've actually reverted to a Nandroid of my stock Sense 5.5 rom. I like it better than Sense 6.
Hey guys, I've recently come across a VZW GS4 and I'm stuck on rooting. I know nothing about Samsung phones so this is pretty new to me. I tried towelroot and it was not sucessfull even after entering the different codes. The picture below is of the "About phone" section in settings. If you could just point me in the direction of a thread that would help me or let me know what do you, I'd really appreciate it.
http://forum.xda-developers.com/showthread.php?t=2959613
aznjosh said:
http://forum.xda-developers.com/showthread.php?t=2959613
Click to expand...
Click to collapse
So I flashed the first thing, as per your recommended post and wifi will not enable afterwards. I open towelroot v3 and it asks to be connected to the internet. So now I'm stuck there. Any advice?
YOu need to flash modules or Goglies wifi fix
Ahhhhh, I see how that could help. Thank you very much.
Sent from my LG-D850 using XDA Free mobile app
XxD34THxX said:
YOu need to flash modules or Goglies wifi fix
Click to expand...
Click to collapse
How do I flash in ODIN? Just the same place as the NC5, under AP?
EDIT: Okay so not in ODIN. Like I said, I know nothing about Samsung devices. Seeing as how it is a .zip file I assume I need to flash it in a recovery on the phone. I jumped to conclusions with the wifi fix so I am now going to actually look up the proper way to apply it.
ConnorAAVance said:
How do I flash in ODIN? Just the same place as the NC5, under AP?
EDIT: Okay so not in ODIN. Like I said, I know nothing about Samsung devices. Seeing as how it is a .zip file I assume I need to flash it in a recovery on the phone. I jumped to conclusions with the wifi fix so I am now going to actually look up the proper way to apply it.
Click to expand...
Click to collapse
If you haven't found it, you flash the fixes in Safestrap recovery
aznjosh said:
If you haven't found it, you flash the fixes in Safestrap recovery
Click to expand...
Click to collapse
Is safestrap just the stock recovery or is it a custom like TWRP or CWM? And another thing, whenever flash an old firmware so I can root, it doesn't seem to actually change. I'm still at NK4 every time I change it. You know what I'm doing wrong? I've looked into a few different posts nothing is working. I've tried towelroot and Kingo.
And I suppose I should actually address your reply instead of just going on a tangent, I did and it put the phone in a bootloop and I have yet to address that. I just reflashed NK1 deal with it for the moment.
ConnorAAVance said:
Is safestrap just the stock recovery or is it a custom like TWRP or CWM? And another thing, whenever flash an old firmware so I can root, it doesn't seem to actually change. I'm still at NK4 every time I change it. You know what I'm doing wrong? I've looked into a few different posts nothing is working. I've tried towelroot and Kingo.
And I suppose I should actually address your reply instead of just going on a tangent, I did and it put the phone in a bootloop and I have yet to address that. I just reflashed NK1 deal with it for the moment.
Click to expand...
Click to collapse
You can try the instructions here http://forum.xda-developers.com/showthread.php?t=2720163
I would ask your questions in the root threads to get better answers
aznjosh said:
You can try the instructions here http://forum.xda-developers.com/showthread.php?t=2720163
I would ask your questions in the root threads to get better answers
Click to expand...
Click to collapse
That is the thread I've been looking at most actually. But I just can't catch a break. Every time I try to download the files I want, my G3 fails instantly and my friends Wi-Fi just won't download at all. I think I now know an even better reason to why I've never bothered getting a Samsung haha.