I have never expected to see myself posting for help with my boot-looping S4, but here I am!
I had the Verizon Galaxy S IV on MJ7 running perfectly fine. I followed:
http://forum.xda-developers.com/showthread.php?t=2512981
I'm assuming I did not follow the directions and renamed framework-res.apk to framework-res.apk.bak instead of overwriting the file directly. The phone crashed and is now stuck in a boot loop. I would be posting in that thread but being a new user, I am unable to. I have tried ADB and every other possible method, no avail. I did search the forums extensively!
When I do try ADB, I put my S4 into recovery mode and ADB update. The device appears but every time I try adb shell, the result is error: closed. I've been trying for hours and considering using the factory reset in the recovery because I can not find the stock Verizon MJ7 rom for ?flashing.
I am in dire need of help. The device was rooted and has SuperSu. I have removed all knox and mostly verizon bloat. Thank you all for taking the time to read this.
Edit:
I've found http://mirror41.downloadandroidrom..../roms/Android4.3/I545VRUEMJ7-Stock-Deodex.zip
Now that I have the file (still not sure if it is the correct one) I am trying to find out what in the world to do with it!
EnUfor said:
I have never expected to see myself posting for help with my boot-looping S4, but here I am!
I had the Verizon Galaxy S IV on MJ7 running perfectly fine. I followed:
http://forum.xda-developers.com/showthread.php?t=2512981
I'm assuming I did not follow the directions and renamed framework-res.apk to framework-res.apk.bak instead of overwriting the file directly. The phone crashed and is now stuck in a boot loop. I would be posting in that thread but being a new user, I am unable to. I have tried ADB and every other possible method, no avail. I did search the forums extensively!
When I do try ADB, I put my S4 into recovery mode and ADB update. The device appears but every time I try adb shell, the result is error: closed. I've been trying for hours and considering using the factory reset in the recovery because I can not find the stock Verizon MJ7 rom for ?flashing.
I am in dire need of help. The device was rooted and has SuperSu. I have removed all knox and mostly verizon bloat. Thank you all for taking the time to read this.
Edit:
I've found http://mirror41.downloadandroidrom..../roms/Android4.3/I545VRUEMJ7-Stock-Deodex.zip
Now that I have the file (still not sure if it is the correct one) I am trying to find out what in the world to do with it!
Click to expand...
Click to collapse
You should flash the MJ7 no-wipe ROM - that "deodex" rom is not stock and won't flash using stock recovery/bootloader.
Go here for the MJ7 no-wipe ROM.
k1mu said:
You should flash the MJ7 no-wipe ROM - that "deodex" rom is not stock and won't flash using stock recovery/bootloader.
Go here for the MJ7 no-wipe ROM.
Click to expand...
Click to collapse
Wow, all this because I renamed one file. I just found that file a few minutes ago! Once I have the zip, what exactly should I be doing with it? I see it possibly have the .tar file for ODIN but by no means am I sure of it yet.
Thank you!
EnUfor said:
Wow, all this because I renamed one file. I just found that file a few minutes ago! Once I have the zip, what exactly should I be doing with it? I see it possibly have the .tar file for ODIN but by no means am I sure of it yet.
Thank you!
Click to expand...
Click to collapse
What you need to do is explained in the thread that I pointed you to. Flash that in ODIN.
k1mu said:
What you need to do is explained in the thread that I pointed you to. Flash that in ODIN.
Click to expand...
Click to collapse
You're the best! Everything is back Now I need to make sure to never to that again!
k1mu is absolutely right. Also in the directions of my thread it says:
"Please read the instructions; accidents while flashing framework-res.apk can and do happen and those mistakes lead to having to use full Odin restore tars. I almost made open1your1eyes0 brick had he not caught my mistake in the code. Luckily he was nice enough to test again, luckily that one worked"
...just saying'
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
k1mu is absolutely right. Also in the directions of my thread it says:
"Please read the instructions; accidents while flashing framework-res.apk can and do happen and those mistakes lead to having to use full Odin restore tars. I almost made open1your1eyes0 brick had he not caught my mistake in the code. Luckily he was nice enough to test again, luckily that one worked"
...just saying'
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are correct; I don't blame you for my mistakes. I was following the Alternate Method from your post but failed to follow the MOVE instruction. I'll just need to be more cautious when dealing with such delicate files. Maybe I'll give it another shot later on since now I know how to fix the mess I made.
Related
Hey guys, I was trying to root my Note 2 and I ran into a problem. I used the method outlined in this thread: http://forum.xda-developers.com/showthread.php?t=2024207 which uses Odin to install the root66 Odin image. Everything went just fine and I used rootchecker to confirm root. Superuser was good to go. Next I went to install a recovery (CWM) so I could do a backup. I installed ROM manager from google play and installed a custom recovery. When I rebooted into recovery I got a message saying the phone had non authorized software on it and to take it to a verizon store. I did a little searching and found a thread that recommended using Odin to reflash the image. Did that. And got the same thing. Should I restore it to stock image as descriped a little further down in the thread (mentioned above)?
Follow instructions to restore with the LL4 update. Then unlock your boot loader next time before installing cwm.
Also next time post this in the right section (QA). Pretty sure you're not releasing anything. I went ahead and reported this to get it moved
Sent from the dark on a Note 2
Sorry about posting in the wrong area.
Anyhow, I'm a bit confused. Were exactly are the instructions to restore with the LL4 update?
I tried to restore per the instructions and Odin failed. Not sure what to do next.
scheirere said:
Sorry about posting in the wrong area.
Anyhow, I'm a bit confused. Were exactly are the instructions to restore with the LL4 update?
I tried to restore per the instructions and Odin failed. Not sure what to do next.
Click to expand...
Click to collapse
He says to use the alternate restore download in the thread you linked. Si Odin alternate route from here
http://forum.xda-developers.com/showthread.php?p=35265728
Sent from the dark on a Note 2
I tried that but Odin doesn't recognize the alternate file. How do I flash it?
scheirere said:
I tried that but Odin doesn't recognize the alternate file. How do I flash it?
Click to expand...
Click to collapse
Extract it before trying to Odin. So right click and choose extract. If it didn't work download 7 zip and use it to extract the file
Sent from the dark on a Note 2
Ok, got it this time. I didn't realize I had to extract the alternate file first.
I was able to flash the correct file this time and the phone is back up and running.
Thanks a bunch for the help.......I majorly appreciate it!!
I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
ebsk8er06 said:
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
Click to expand...
Click to collapse
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
villainous said:
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
Click to expand...
Click to collapse
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
villainous said:
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
Click to expand...
Click to collapse
I'm sure it will. In a few days. I'm surprised the verizon repair tool doesn't have MJ7.... maybe that'll take a while too.
antisomnic said:
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
Click to expand...
Click to collapse
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
tech_head said:
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
Click to expand...
Click to collapse
yeah i actually did that and have been using my s4 for a few days
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
This is an ODIN factory image similar to the one posted here but this is an emergency recovery image that will help you recover and restore your device from nearly ANY possible soft-brick by entirely wiping, refreshing, and repartitioning your device to out-of-box OEM firmware.
WARNING: Please use this with caution as this will wipe your ENTIRE device with no chance of restoring back old data afterwords!
How to Use
Download file from: http://www.androidfilehost.com/?fid=23203820527944861
Unzip file to your computer (desktop or some location)
Use ODIN v3.09 to flash in AP section once your device is connected
Click to expand...
Click to collapse
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
antisomnic said:
yeah i actually did that and have been using my s4 for a few days
Click to expand...
Click to collapse
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
mickrg123 said:
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
Click to expand...
Click to collapse
Untested, but you can unzip the attached and flash it in ODIN - it's the stock MJ7 recovery. With a bit of luck that'll get you repaired.
If not, flash the no-wipe MJ7 ROM from the Android Development forum, but that'll probably cause you to lose root.
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
wrong post
Awesome
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
SmOoThEm said:
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
Click to expand...
Click to collapse
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
emtownsend said:
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23203820527944861
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
antisomnic said:
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
Click to expand...
Click to collapse
antisomnic said:
I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Click to expand...
Click to collapse
Just an FYI. Whenever you take an OTA from the Carrier it's written so you cannot revert back to an earlier build or a soft and possible hard brick can occur. This has been discussed numerous times in various forums. You were lucky this time.
So I have bricked my GS4. It was just a black screen, so I took the battery out and was able to get to the Odin Mode screen. I downloaded Odin and the MD5 file and the Samsung Drivers. When I run Odin it says FAILED. I can not seem to find any information on how to fix this on XDA forums. Can anyone out there help me with this please?
stewdaddy123 said:
So I have bricked my GS4. It was just a black screen, so I took the battery out and was able to get to the Odin Mode screen. I downloaded Odin and the MD5 file and the Samsung Drivers. When I run Odin it says FAILED. I can not seem to find any information on how to fix this on XDA forums. Can anyone out there help me with this please?
Click to expand...
Click to collapse
You have to download MK2 Tar file if you were on MK2 before it bricks. Here is the link for MK2 Tar, just follow instruction and odin back to stock MK2, it should work.
http://forum.xda-developers.com/showthread.php?t=2578209
Thanks! - I will give it a try and let you know
urcboss07 said:
You have to download MK2 Tar file if you were on MK2 before it bricks. Here is the link for MK2 Tar, just follow instruction and odin back to stock MK2, it should work.
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
Very Nice!! It worked. I forgot to put the .pit file in for the "Emergency Restore" but I just let it go through, so not a full wipe but it worked fine. You were a life saver for me, I was freaking out. Gonna give the hacking thing a rest for a while
urcboss07 said:
You have to download MK2 Tar file if you were on MK2 before it bricks. Here is the link for MK2 Tar, just follow instruction and odin back to stock MK2, it should work.
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
I am glad it worked for you, if you want to root for MK2, you can use "saferoot" and it works like a charm.
stewdaddy123 said:
Very Nice!! It worked. I forgot to put the .pit file in for the "Emergency Restore" but I just let it go through, so not a full wipe but it worked fine. You were a life saver for me, I was freaking out. Gonna give the hacking thing a rest for a while
Click to expand...
Click to collapse
Glad you got it fixed. Don't give the "hacking" stuff a rest. Just research more and learn from your mistakes; knowledge is power. Use caution and always read important stuff twice. No one got anywhere by playing it safe
I re-rooted with saferoot last night after I got my phone back up.....and yes you are right, I'm not gonna give it a rest. I'm gonna try and flash a ROM tonight probably, now that I have a sort of "fail-safe". What bricked my phone in the first place was trying to flash the Foxhound ROM. I didn't really understand the instructions and really shouldn't have gone through without fully understanding things. I haven't tinkered with a phone in about 3 years (I've had iphone for past 3 years).
gnubian said:
Glad you got it fixed. Don't give the "hacking" stuff a rest. Just research more and learn from your mistakes; knowledge is power. Use caution and always read important stuff twice. No one got anywhere by playing it safe
Click to expand...
Click to collapse
stewdaddy123 said:
I re-rooted with saferoot last night after I got my phone back up.....and yes you are right, I'm not gonna give it a rest. I'm gonna try and flash a ROM tonight probably, now that I have a sort of "fail-safe". What bricked my phone in the first place was trying to flash the Foxhound ROM. I didn't really understand the instructions and really shouldn't have gone through without fully understanding things. I haven't tinkered with a phone in about 3 years (I've had iphone for past 3 years).
Click to expand...
Click to collapse
Ewww iphones lol. Welcome back! Yeah foxhound is just a backup that you restore, not flash. Happy hacking!
I was wondering about that with Foxhound. How far into the backup directory do I place the Foxhound folder. My back up is stored on my external sd card. Here is the file route I have: TWRP - BACKUPS - 8e12f1e6 - STOCK1970-01-03-18-09-55blahblahblah. Do I put it in just the BACKUPS folder, or put it in the folder titled 8e12f1e6, or do I put it in with the actual backup folder, the last folder that begins with "stock"?
gnubian said:
Ewww iphones lol. Welcome back! Yeah foxhound is just a backup that you restore, not flash. Happy hacking!
Click to expand...
Click to collapse
stewdaddy123 said:
I was wondering about that with Foxhound. How far into the backup directory do I place the Foxhound folder. My back up is stored on my external sd card. Here is the file route I have: TWRP - BACKUPS - 8e12f1e6 - STOCK1970-01-03-18-09-55blahblahblah. Do I put it in just the BACKUPS folder, or put it in the folder titled 8e12f1e6, or do I put it in with the actual backup folder, the last folder that begins with "stock"?
Click to expand...
Click to collapse
Make it the same structure as your stock backup. For example:
Twrp/Backups/random#/stock backup/backup files
twrp/Backups/random#/foxhound/foxhound files
Ok, that's the way I had it. I just wanted to make sure. Thanks for all your help. Peace
gnubian said:
Make it the same structure as your stock backup. For example:
Twrp/Backups/random#/stock backup/backup files
twrp/Backups/random#/foxhound/foxhound files
Click to expand...
Click to collapse
stewdaddy123 said:
Ok, that's the way I had it. I just wanted to make sure. Thanks for all your help. Peace
Click to expand...
Click to collapse
No problem.
So I bricked my s4 while flashing stang5litre Edition 5.0 NON MDK v2. My device went through the process and never turned back on. I am rooted on ota updated 5.0.1 using kingroot but now have supersu.
My phone will connect to my computer and my computer will make the connecting noise but does not show up and does not turn on.
Its not my usb, I cannot get the phone to turn on, get into recovery or download mode.
I am stuck, my phone doesnt even vibrate, any ideas how to unbrick?
So I tried to root my Note 2 today. I had rooted it once before using Casual this past summer, but due to circumstances i had to get a new one.The replacement came in today, and i tried to root it with the same methods. I believe my mistake was using Casual while i had 4.3 installed on my device. I'm not TERRIBLY android savvy, but i knew enough to know that if i ****ed up i should stop while i'm ahead and ask you guys.
tl;dr
Long story short, while using Casual to root my Note 2 with 4.3 on it, i got this message
ERROR: Failed to confirm end of file transfer sequence!ERROR: recovery upload failed!ERROR: Failed to send end session packet!waiting for device
waited for a good 30 minutes, nothing was changing, turned off phone and now it's bricked, looping at the "Samsung Galaxy Note 2" Splash screen.
I believe i have to use Odin for something but i could really use some help and reassurance before i continue.
Needless to say i will be jamming f5 on my thread until everything is resolved!
Thanks in advance!
mzaric said:
So I tried to root my Note 2 today. I had rooted it once before using Casual this past summer, but due to circumstances i had to get a new one.The replacement came in today, and i tried to root it with the same methods. I believe my mistake was using Casual while i had 4.3 installed on my device. I'm not TERRIBLY android savvy, but i knew enough to know that if i ****ed up i should stop while i'm ahead and ask you guys.
tl;dr
Long story short, while using Casual to root my Note 2 with 4.3 on it, i got this message
ERROR: Failed to confirm end of file transfer sequence!ERROR: recovery upload failed!ERROR: Failed to send end session packet!waiting for device
waited for a good 30 minutes, nothing was changing, turned off phone and now it's bricked, looping at the "Samsung Galaxy Note 2" Splash screen.
I believe i have to use Odin for something but i could really use some help and reassurance before i continue.
Needless to say i will be jamming f5 on my thread until everything is resolved!
Thanks in advance!
Click to expand...
Click to collapse
UPDATE: Since i posted this, i tried to flash a stock firmware on Odin (4.1.2 i believe) and it failed halfway through the procedure. with nothing more to be done, i reset my phone, and where before it was just bootlooping, it now shows me an entirely different screen reading "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Since then i have tried a different firmware file, still 4.1.2, Odin get's to the very end of the procedure, and crashes at what i assume is the reboot portion. Desperately need assistance!
You can't flash anything other than 4.3 if you have the 4.3 bootloader.
akellar said:
You can't flash anything other than 4.3 if you have the 4.3 bootloader.
Click to expand...
Click to collapse
OH. That makes a lot of sense....
I will try to flash a 4.3 firmware right now. Will i need some sort of .pit file or something to fix the initial bootloop? Or is that problem just totally blown out of the water at this point?
mzaric said:
OH. That makes a lot of sense....
I will try to flash a 4.3 firmware right now. Will i need some sort of .pit file or something to fix the initial bootloop? Or is that problem just totally blown out of the water at this point?
Click to expand...
Click to collapse
I cant seem to find the file anywhere. Only on terafile via SamMobile, but the download link doesn't seem to work.
What are my options as far as this bootloader go?
Did you look in the general section at the unbricker thread?
Sent from my MB886 using xda app-developers app
palmbeach05 said:
Did you look in the general section at the unbricker thread?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I did a bunch of searches on the site as i was f****ing my phone up, systematically. Im really sorry if this thread doesn't go here, i just didn't know who else to ask
YES!
Found the proper 4.3 file, flashed it via Odin. Everything is stock and ready. If anybody wishes to help me root it from here or point me in the right direction that'd be great but other than that, thanks for letting me post here and thanks to those who helped me out!
mzaric said:
YES!
Found the proper 4.3 file, flashed it via Odin. Everything is stock and ready. If anybody wishes to help me root it from here or point me in the right direction that'd be great but other than that, thanks for letting me post here and thanks to those who helped me out!
Click to expand...
Click to collapse
Currently the only way to root your OTA 4.3 Note 2 is to use saferoot, read this thread carefully
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
Sent from my SCH-I605 using Tapatalk
I found myself in the same situation. Where might I find the PIT file? I can't reboot the phone to get the PIT file because it's soft bricked like mzaric's phone was. I'm using Mac OS X so I'm having to use JOdin3 to flash the stock 4.3 firmware back, but without the PIT file I can't continue and I've searched endlessly to find the PIT file. Also a somewhat related question, I heard JOdin isn't good for flashing big files, but I have no alternative, is the stock firmware which is 1.1gb too big to flash?
EDIT: I sadly didn't search hard enough thank you droidstyle for the guide. But my next question is I'm unsure of what version the phone is because when I originally tried to do the CASUAL unlock I believe it was on 4.1.2, but I think it softbricked to begin with because it was 4.3. Should I just try doing the 4.1.2 and if it doesn't take, retry with the 4.3?
If you flashed n7100 firmware you are screwed. If not just Odin back to stock. You were on 4.1.2 if you were unlocked using casual. Don't go to 4.3
Sent from my SCH-I605 using Tapatalk
I'm sure this has been asked before but I have no idea how to find the right thread, I've been searching but I'm not sure which method to use. I used towel root to root my S4 with NC5 build running 4.4.2 a while back and lately my phone has been randomly powering off. It shuts down instantly as if holding down the power button for 10 seconds. I'm not sure if this matters but I have xposed installed and before I found out about the locked bootloader I tried to install TWRP and CWP, so when I boot up it says custom. I want to factory reset the phone to hopefully solve this powering off problem, and I wanna be able to root again so I can put xposed back on. I have a laptop to use odin on if I need to. If someone could help me out it would be very much appreciated.
Start here.
http://forum.xda-developers.com/showthread.php?t=2735172
-
meazz1 said:
Start here.
http://forum.xda-developers.com/showthread.php?t=2735172
-
Click to expand...
Click to collapse
Thank you that helps so much. So I should do the full wipe correct? And how do I extract the PIT file? Should I just download the one from the thread?
Autokill45 said:
Thank you that helps so much. So I should do the full wipe correct? And how do I extract the PIT file? Should I just download the one from the thread?
Click to expand...
Click to collapse
You want stock yes? Should just download Odin and the NC5 image. Place the NC5 in PDA if I remember correctly, been a while but should be. Once it is flashed you can then re root and do what not And yes I would do full wipe.
Illogi.xbone said:
You want stock yes? Should just download Odin and the NC5 image. Place the NC5 in PDA if I remember correctly, been a while but should be. Once it is flashed you can then re root and do what not
Click to expand...
Click to collapse
Yes I want stock NC5 so I can use towel root again. Sorry if these are stupid questions, this is my only experience with anything like this and I'm having trouble understanding.
So I should download Odin amd the full wipe NC5 image, unzip the image and place it in AP correct? But in the video he talks about drivers, do I need these and if so where do I get them? And in the thread under the directions for the full wipe step 3 says to extract the PIT file from your phone, do I need to do that?
Autokill45 said:
Yes I want stock NC5 so I can use towel root again. Sorry if these are stupid questions, this is my only experience with anything like this and I'm having trouble understanding.
So I should download Odin amd the full wipe NC5 image, unzip the image and place it in AP correct? But in the video he talks about drivers, do I need these and if so where do I get them? And in the thread under the directions for the full wipe step 3 says to extract the PIT file from your phone, do I need to do that?
Click to expand...
Click to collapse
We all start from somewhere :highfive: Yes, follow the instructions to the letter. Follow step 3 and you are golden. First Check to see if you already have drivers installed. Open Odin with your phone in download mode and plug it in. If Odin finds it then you already have the drivers if not windows may install them for you, if you are on 7 and up I know for sure. :laugh: Had to use Odin a lot before with my old S4.
Well I finally figured it out. Nearly had a heart attack when I pushed the run button lol. Thank you guys so much for the help!
Autokill45 said:
Well I finally figured it out. Nearly had a heart attack when I pushed the run button lol. Thank you guys so much for the help!
Click to expand...
Click to collapse
No problemo man :highfive:
I did the full wipe via Odin to restore to NC5 and the only hiccup I'm having is that WiFi will not connect. I've done multiple reboots, too, just FYI.
Any suggestions, please?
Do you have Safestrap installed? Sounds like you need the right modem.
Sent from my SCH-I545 using XDA Free mobile app