Database Users

[Q] Major problems with Google 4.3 ROM! Please Help!

Hi,
I flashed the Google 4.3 S4 Rom and used TWRP 2.5.0.2 and Goo with instructions I found on the boards.
- I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
So now the problems:
1) I originally installed it and it was constantly stuck on 'Samsung Galaxy S4' Screen, couldn't proceed barely got into recovery and reflashed; this worked and it booted google and i realized why this happened is because i accidentally erased my data.
2) The second time, I simply turned off my phone and turned it back on, again i was stuck on 'Samsung Galaxy S4' Screen, no way of doing anyhing except turnging off the phone and trying again and again to get to recovery, I then flashed to 4.3 again off the external.
3) I simply tried to open facebook and the phone booted and went on to the 'Samsung Galaxy S4' Screen and is stuck again! Even when I reboot through Team Win Recovery v2.5.0.2 to System I get the same boot loop.
I am super frustrated with this, what can I do and at this point I'm getting to the point where I would like some help to go back to stock. I would also like some input as to why this is happening if anyone has any suggestions or help it would be greatly appreciated.
Thank You.

notorious99 said:
Hi,
I flashed the Google 4.3 S4 Rom and used TWRP 2.5.0.2 and Goo with instructions I found on the boards.
- I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
So now the problems:
1) I originally installed it and it was constantly stuck on 'Samsung Galaxy S4' Screen, couldn't proceed barely got into recovery and reflashed; this worked and it booted google and i realized why this happened is because i accidentally erased my data.
2) The second time, I simply turned off my phone and turned it back on, again i was stuck on 'Samsung Galaxy S4' Screen, no way of doing anyhing except turnging off the phone and trying again and again to get to recovery, I then flashed to 4.3 again off the external.
3) I simply tried to open facebook and the phone booted and went on to the 'Samsung Galaxy S4' Screen and is stuck again! Even when I reboot through Team Win Recovery v2.5.0.2 to System I get the same boot loop.
I am super frustrated with this, what can I do and at this point I'm getting to the point where I would like some help to go back to stock. I would also like some input as to why this is happening if anyone has any suggestions or help it would be greatly appreciated.
Thank You.
Click to expand...
Click to collapse
Have you try using Odin to go back to stock?

shizs14 said:
Have you try using Odin to go back to stock?
Click to expand...
Click to collapse
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?

notorious99 said:
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
Click to expand...
Click to collapse
Rule #1. Learn Odin before attempting anything on Samsung phones

notorious99 said:
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
Click to expand...
Click to collapse
You need to read these threads and make sure to read the threads linked in these threads that have to do with your phone...
http://forum.xda-developers.com/showthread.php?t=2301762
and
http://forum.xda-developers.com/showthread.php?t=2312444
You can use the forum's search function to help you find specific information. Good luck.

agreed, odin should be the first thing any noob should learn.
Scott, you da man...

scott14719 said:
You need to read these threads and make sure to read the threads linked in these threads that have to do with your phone...
http://forum.xda-developers.com/showthread.php?t=2301762
and
http://forum.xda-developers.com/showthread.php?t=2312444
You can use the forum's search function to help you find specific information. Good luck.
Click to expand...
Click to collapse
So I flashed a different rom (4.2.2 google) and I tested turning my phone off and then on again, and SAME issue, it boot loops at the S4 screen, what is the deal with that specifically? does anyone have any ideas?

notorious99 said:
So I flashed a different rom (4.2.2 google) and I tested turning my phone off and then on again, and SAME issue, it boot loops at the S4 screen, what is the deal with that specifically? does anyone have any ideas?
Click to expand...
Click to collapse
Which google rom 4.2.2? there are a few, meaning where did you get the rom?
Which kernel did you use?
you say you have this...both roms require a certain kernel. Depending on whose rom you flashed.
I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed

TheAxman said:
Which google rom 4.2.2? there are a few, meaning where did you get the rom?
Which kernel did you use?
you say you have this...both roms require a certain kernel. Depending on whose rom you flashed.
I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
Click to expand...
Click to collapse
THE ROM
Google Edition 4.2.2 - v1.3 - http://d-h.st/Lm8
posted here: http://forum.xda-developers.com/showthread.php?t=2341376
MY KERNEL as it is on my phone currently is:
Baseband: 1337MVLUAMDJ
Kernel: 3.4.0-Google-Edition, [email protected]#1,
Build Number: JDQ39.1337
AND I'm using TWRP Custom
-----------------------------------------

notorious99 said:
THE ROM
Google Edition 4.2.2 - v1.3 - http://d-h.st/Lm8
posted here: http://forum.xda-developers.com/showthread.php?t=2341376
MY KERNEL as it is on my phone currently is:
Baseband: 1337MVLUAMDJ
Kernel: 3.4.0-Google-Edition, [email protected]#1,
Build Number: JDQ39.1337
AND I'm using TWRP Custom
-----------------------------------------
Click to expand...
Click to collapse
Ok, now we're cooking, thanks for the info...
I haven't tried that rom yet, I am going to d/l it and give it a shot. Be back shortly.

ODIN back to stock, and start over from there, and take care to flash/erase properly. backup user apps/data if you can (there are non-root options) and restore when you finish flashing 4.3 and are sure its stable.

Ok..back...I flashed this rom I booted with the kernel supplied in rom. Hmm..it is kernel related for sure. Have you posted the issue in that roms thread? May want to give that a shot.

I'm on canadian S4 aswell and I also flashed the 1.3 Google edition but flashed faux kernel. Works like a charm.
Sent from my SGH-I337 using Tapatalk 4 Beta

Thank you to all you guys. I successfully used odin to get back to stock. I still have no idea why I had so many problems but will try the Google Rom again when I feel more comfortable.
Thanks again!

notorious99 said:
Thank you to all you guys. I successfully used odin to get back to stock. I still have no idea why I had so many problems but will try the Google Rom again when I feel more comfortable.
Thanks again!
Click to expand...
Click to collapse
Proper wiping steps is key when changing ROM bases. Do a factory reset, wipe both caches, format /system, and if coming from TW, format the internal also.

Here is a post by TeamWin on wiping for Roms. Formatting Data is not part of "normal" wipe process. It wipes your internal sd.
http://teamw.in/whattowipe
These guys are far above me. But my preferred method is to "Wipe" System/Data/Both Caches. I actually do it twice. I know many say no need, but I do. I did this for many years on previous phones and never had issues. If on Nightlies or incremental updates did not wipe unless OP said to.

rugmankc said:
Here is a post by TeamWin on wiping fro Roms. Formatting Data is not part of "normal" wipe process. It wipes your internal sd.
http://teamw.in/whattowipe
These guys are far above me. But my preferred method is to "Wipe" System/Data/Both Caches. I actually do it twice. I know many say no need, but I do. I did this for many years on previous phones and never had issues. If on Nightlies or incremental updates did not wipe unless OP said to.
Click to expand...
Click to collapse
The internal wiping isn't necessary, but it does get rid of TW folders that you don't need if switching to AOSP.

I think you could delete them individually as opposed to formatting entire internal with other rom backups/kernels/gapps etc. I also have music/pics on internal too. Also, I like some will go back and forth btwn aosp and tw. So, I would want to keep them. I never did that, but read about some having issues after Formatting Data
All IMHO--

rugmankc said:
I think you could delete them individually as opposed to formatting entire internal with other rom backups/kernels/gapps etc. I also have music/pics on internal too. Also, I like some will go back and forth btwn aosp and tw. So, I would want to keep them. I never did that, but read about some having issues after Formatting Data
All IMHO--
Click to expand...
Click to collapse
You're right, it's an overkill. Just my OCD nature kicks in sometimes.

+1
I understand OCD hence my wiping twice--hey sometimes 3x
Monk has nothing on me, If you are familiar with that tv show--
I am OCD thru and thru--

[Q] Soft-Brick Assistance

Note: I may not use terms correctly, I have spent the past hour reading threads similar to mine in order to (hopefully) use the correct terms to describe my predicament.
I was using TriForce ROM 3.0 and I wanted to mix things up a bit because it was too much like the stock ROM. I found Negalite S4 and tried my hand at that, with devastating consequences. I booted my phone into TWRP did a wipe and then proceeded to install the Negalite S4.zip onto my phone. It got stuck in a boot loop. After a good 30~ minutes of it continuously rebooting I turned it off and booted back into TWRP. However, now that my phone was wiped, it is not a recognized device by my computer any longer. Since I wiped the phone clean the .zip is no longer on my phone either. So, all I have now is a phone that can boot into recovery (TWRP); which is a soft-brick (correct me if I'm wrong).
I have read other threads and the xda community informs the user to use KIES or ODIN (I have used ODIN once before). However, try as hard as I can to understand their directions... I don't know what to do with ODIN.
My computer does not recognize my device at all. It will only boot into recovery otherwise it's stuck in an infinite boot loop. I am really scared that I have ruined such a valuable phone and so I am not thinking clearly - which is only adding to my "noobishness."
Can anyone please help me out in a way that I can understand? All help is much appreciated!

_retro said:
Note: I may not use terms correctly, I have spent the past hour reading threads similar to mine in order to (hopefully) use the correct terms to describe my predicament.
I was using TriForce ROM 3.0 and I wanted to mix things up a bit because it was too much like the stock ROM. I found Negalite S4 and tried my hand at that, with devastating consequences. I booted my phone into TWRP did a wipe and then proceeded to install the Negalite S4.zip onto my phone. It got stuck in a boot loop. After a good 30~ minutes of it continuously rebooting I turned it off and booted back into TWRP. However, now that my phone was wiped, it is not a recognized device by my computer any longer. Since I wiped the phone clean the .zip is no longer on my phone either. So, all I have now is a phone that can boot into recovery (TWRP); which is a soft-brick (correct me if I'm wrong).
I have read other threads and the xda community informs the user to use KIES or ODIN (I have used ODIN once before). However, try as hard as I can to understand their directions... I don't know what to do with ODIN.
My computer does not recognize my device at all. It will only boot into recovery otherwise it's stuck in an infinite boot loop. I am really scared that I have ruined such a valuable phone and so I am not thinking clearly - which is only adding to my "noobishness."
Can anyone please help me out in a way that I can understand? All help is much appreciated!
Click to expand...
Click to collapse
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.

3ncrypt3d said:
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.
Click to expand...
Click to collapse
Thank-you for the detailed response, I'll get started now! I did wipe the SD card, you're right. I'm so glad that you posted, thanks again.
If I need help I'll edit this post (no bumping within 24 hours). I'm hoping I have enough smarts to knock this out though. Again, thank you so much.
EDIT: Excuse my ignorance. I'm not sure what MDL stock is, I figured it was the default ROM - I have a nandroid of that. However, even after re-installing the samsung drivers, rebooting both my phone and computer - nothing happens. I don't know how to proceed from here. I can imagine I'm becoming a pain and do apologize.

_retro said:
Thank-you for the detailed response, I'll get started now! I did wipe the SD card, you're right. I'm so glad that you posted, thanks again.
If I need help I'll edit this post (no bumping within 24 hours). I'm hoping I have enough smarts to knock this out though. Again, thank you so much.
EDIT: Excuse my ignorance. I'm not sure what MDL stock is, I figured it was the default ROM - I have a nandroid of that. However, even after re-installing the samsung drivers, rebooting both my phone and computer - nothing happens. I don't know how to proceed from here. I can imagine I'm becoming a pain and do apologize.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2375523
The link above is the tar file for stock MF9. If you just use the link for the from the first post you just need to download the first file (not the kernel). Once downloaded you need to extraxt that zip and you will get a .tar.md5 file from it. Later open odin and make sure only auto reboot is checked. Click on the PDA slot and find the .tar.md5 file you downloaded click on it. Next put your phone into download mode and connect it to your computer. Wait for it to install drivers and you will see a yellow box with "com:[some number]" once you see that click start and from there let it do its thing and whoola you have your phone back to MF9 stock. Good luck!
Sent from my SPH-L720

ROMANTiC KiD said:
http://forum.xda-developers.com/showthread.php?t=2375523
The link above is the tar file for stock MF9. If you just use the link for the from the first post you just need to download the first file (not the kernel). Once downloaded you need to extraxt that zip and you will get a .tar.md5 file from it. Later open odin and make sure only auto reboot is checked. Click on the PDA slot and find the .tar.md5 file you downloaded click on it. Next put your phone into download mode and connect it to your computer. Wait for it to install drivers and you will see a yellow box with "com:[some number]" once you see that click start and from there let it do its thing and whoola you have your phone back to MF9 stock. Good luck!
Sent from my SPH-L720
Click to expand...
Click to collapse
Well, you did it! That post is solid, I understood every-bit! My phone (most likely) is downloading the firmware now. I don't know how long it will take to get off the "Downloading... Do not turn off target !!" screen, but I'll edit this post after letting it sit over night! Thank you both so much.

_retro said:
Well, you did it! That post is solid, I understood every-bit! My phone (most likely) is downloading the firmware now. I don't know how long it will take to get off the "Downloading... Do not turn off target !!" screen, but I'll edit this post after letting it sit over night! Thank you both so much.
Click to expand...
Click to collapse
Your welcome glad to help again, should take less than 10 mins. If its more than that just reboot your computer and repeat the steps from opening odin and finding your file. Another GS4 saved ;D
Sent from my SPH-L720

ROMANTiC KiD said:
Your welcome glad to help again, should take less than 10 mins. If its more than that just reboot your computer and repeat the steps from opening odin and finding your file. Another GS4 saved ;D
Sent from my SPH-L720
Click to expand...
Click to collapse
You were right, it was quite snappy. I cannot believe I was so panicked over this! My babies safe ... for now.

So how did Twrp wipe nor SD card? When by boot into recovery and immediately click on Wipe, it'll wipe everything Necessary except the internal and external memory. Did you click the option to choose what you want to wipe? Happens more than ya may think, cause I've done it myself lol. Good to hear it's back up, I still get freaked out by those occurrences
Sent from my SPH-L720 using Tapatalk 2

reverepats said:
So how did Twrp wipe nor SD card? When by boot into recovery and immediately click on Wipe, it'll wipe everything Necessary except the internal and external memory. Did you click the option to choose what you want to wipe? Happens more than ya may think, cause I've done it myself lol. Good to hear it's back up, I still get freaked out by those occurrences
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
It wasn't human error through TWRP, it was an error while flashing Negalite. It asks if you want to wipe everything, data, or nothing at all. Silly me thought let's wipe EVERYTHING! Heheh

3ncrypt3d said:
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.
Click to expand...
Click to collapse
ODIN IS NOT RECOGNISING MY PHONE ...WHAT TO DO????:crying::crying::crying:

Ridddeathmetal said:
ODIN IS NOT RECOGNISING MY PHONE ...WHAT TO DO????:crying::crying::crying:
Click to expand...
Click to collapse
Reinstall drivers, use different USB ports, used different USB cables?
Sent from my SPH-L720 using xda app-developers app

romantic kid said:
reinstall drivers, use different usb ports, used different usb cables?
Sent from my sph-l720 using xda app-developers app
Click to expand...
Click to collapse
tried 4 ports...in different pc also but same result used 3 cables...but none recognising it.....drivers have been downloaded and reinstalled

[Q] Galaxy s4 Rooted and Custom Rom Problems

I have a Canadian S4 and rooted using the twrp method and then installed the vigin google play edition rom. Everything worked fine at first when I installed it but i was fiddling around after in twrp and thought i should format the internal storage and start completely fresh and now if I install any rom including my original backup the device will boot up into the system fine for the first time but if the device resets after that it just hangs on the galaxy S4 logo and i have to reboot into recovery and flash again. Any ideas on how i could fix this? Thanks!!!

Try this, in twrp go into advanced wipe and wipe dalvik cache, cache, system, data and android secure. Then flash your nandroid.

I don't have a nandroid I have a twrp backup

Jaygrippa said:
I don't have a nandroid I have a twrp backup
Click to expand...
Click to collapse
That is a nandroid.

Dont use TWRP for the S4
From what I have experience and I believe others have as well, if you used TWRP to format where you had to type yes, you are pretty much screwed trying to get things working properly again. Maybe it is certain phones, sd cards, roms, who knows, but after I typed yes in TWRP to format everything, I could flash a rom but couldnt restart and things were buggy. I had to use odin to flash back to stock, re-root and flash the rom again. Now everything is 190% considering my battery life went from 6 hours to 28 with medium usage.
I have always loved TWRP on my other phones, but for the S4, its more frustration and using with caution than its worth.
Another word of caution, use windows to fix your phone. Im on linux and its too much of a pain in the ass to use odin/heimdall to go back to stock for newbs. On windows I went to stock and rooted again in no time.
Good luck!

jd1639 said:
That is a nandroid.
Click to expand...
Click to collapse
After doing that stuff in twrp should I flash right back to my backup of stock touch wiz or straight into the ROM of my choosing? Whenever I would have to reflash I would have to format he internal memory or it wouldn't work

Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?

Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
You might have to. I had the same problem today where if the phone rebooted I would just get a black screen. I ended up using Odin with the stock rom, reinstalling twrp and then restoring my backup. I'm pretty sure it was a rom I flashed that caused the initial problem and only Odin would clear things up.

Start Over
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.

ericchaffey said:
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
Click to expand...
Click to collapse
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Now the only problem is i have to find a Fido ROM

Jaygrippa said:
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Click to expand...
Click to collapse
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.

ericchaffey said:
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
Click to expand...
Click to collapse
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!

Jaygrippa said:
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Click to expand...
Click to collapse
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.

jd1639 said:
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
Click to expand...
Click to collapse
ya even they dont have a specific "Fido" firmware...

Anyone know if I can just use the Rogers ROM its pretty much the same company

Jaygrippa said:
Anyone know if I can just use the Rogers ROM its pretty much the same company
Click to expand...
Click to collapse
It'll work. It'll just put their bloatware on and the boot animation will be theirs

Reflashed
Ok so i reflashed to the stock rom using odin and bam it works again, im just wondering what is a good way now too root, and install the same rom i had

This will have everything you need http://forum.xda-developers.com/showthread.php?p=42320391

Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order

Jaygrippa said:
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Click to expand...
Click to collapse
Glad to here it. Have fun.

[Q] Odin Troubles... >_<

So here we go again...
I tried using Odin to get back to stock but, Odin just kept crashing
every time I tried loading the 'MD5' file. I tried multiple versions as well..
Then I realized even though the computer would say Odin was
'Not Responding' I continued to wait, and finally it loaded the MD5!
So I went ahead and tried going back to stock, but when I did
every stock MD5 file causes my device to close
Google Play, Google Location, and SystemUI rapidly...
I was able to get my original Recovery in there and restore a backup,
but I'd really like to try and go back to stock for a bit and start fresh.
What the heck in the world is going on with my phone?!
I thought Odin was my safety net, here to help me, but
instead I'm getting more and more hassle trying to get it workin'...
Any help at all would be greatly appreciated!!!

Just tried flashing MK6 using Odin
(MK6 came on my phone originally)
and I get the same issue..
Everything I try ends up failing..
Egads!​

Adizzzle said:
So here we go again...
I tried using Odin to get back to stock but, Odin just kept crashing
every time I tried loading the 'MD5' file. I tried multiple versions as well..
Then I realized even though the computer would say Odin was
'Not Responding' I continued to wait, and finally it loaded the MD5!
So I went ahead and tried going back to stock, but when I did
every stock MD5 file causes my device to close
Google Play, Google Location, and SystemUI rapidly...
I was able to get my original Recovery in there and restore a backup,
but I'd really like to try and go back to stock for a bit and start fresh.
What the heck in the world is going on with my phone?!
I thought Odin was my safety net, here to help me, but
instead I'm getting more and more hassle trying to get it workin'...
Any help at all would be greatly appreciated!!!
Click to expand...
Click to collapse
What firmware are you on? What version of Odin are you using? Perhaps try using a different version. Also use original usb cable not universal one. Seems to make a difference.

Adizzzle said:
So here we go again...
I tried using Odin to get back to stock but, Odin just kept crashing
every time I tried loading the 'MD5' file. I tried multiple versions as well..
Then I realized even though the computer would say Odin was
'Not Responding' I continued to wait, and finally it loaded the MD5!
So I went ahead and tried going back to stock, but when I did
every stock MD5 file causes my device to close
Google Play, Google Location, and SystemUI rapidly...
I was able to get my original Recovery in there and restore a backup,
but I'd really like to try and go back to stock for a bit and start fresh.
What the heck in the world is going on with my phone?!
I thought Odin was my safety net, here to help me, but
instead I'm getting more and more hassle trying to get it workin'...
Any help at all would be greatly appreciated!!!
Click to expand...
Click to collapse
So the flash was successful but when booting up u get FC's correct? If that is the case then I would guess it's because u didn't wipe data/factory reset preflash. Doing this from recovery should solve ur problem if I understood u right

John The Rhino said:
What firmware are you on? What version of Odin are you using? Perhaps try using a different version. Also use original usb cable not universal one. Seems to make a difference.
Click to expand...
Click to collapse
Im on MK6 originally, on Pac ROM
While I figure all this out…
I have used every 'newer' version
of Odin available and am using the
Original cable..
blankingblank said:
So the flash was successful but when booting up u get FC's correct? If that is the case then I would guess it's because u didn't wipe data/factory reset preflash. Doing this from recovery should solve ur problem if I understood u right
Click to expand...
Click to collapse
So Odin doesn't wipe / factory reset
on its own?
The first time I forgot to wipe but
every other time Im sure I wiped in
recovery before hitting up download
mode.
I did make a ROM using NC1
firmware and added KT kernel to
it. The ROM was a dud and that's
why I wanted a fresh start.

Adizzzle said:
Im on MK6 originally, on Pac ROM
While I figure all this out…
I have used every 'newer' version
of Odin available and am using the
Original cable..
So Odin doesn't wipe / factory reset
on its own?
The first time I forgot to wipe but
every other time Im sure I wiped in
recovery before hitting up download
mode.
I did make a ROM using NC1
firmware and added KT kernel to
it. The ROM was a dud and that's
why I wanted a fresh start.
Click to expand...
Click to collapse
The way I understand it there are 2 types of Odin flashable fws: full wipe and no full wipe. Full wipe fws are the ones that come in separate parts, i.e. BL, AP, CP etc. and no full wipe fws are the complete tar.md5 files. I recently went back to stock to get a fresh start as well and had the same issue with FC's on boot up. Factory reset fixed it

blankingblank said:
The way I understand it there are 2 types of Odin flashable fws: full wipe and no full wipe. Full wipe fws are the ones that come in separate parts, i.e. BL, AP, CP etc. and no full wipe fws are the complete tar.md5 files. I recently went back to stock to get a fresh start as well and had the same issue with FC's on boot up. Factory reset fixed it
Click to expand...
Click to collapse
So I was using an .md5 file, therefore Odin
wasn't able to fully wipe my S4?
I could have sworn I tried wiping..
Will give it another go though! :highfive:

Adizzzle said:
So I was using an .md5 file, therefore Odin
wasn't able to fully wipe my S4?
I could have sworn I tried wiping..
Will give it another go though! :highfive:
Click to expand...
Click to collapse
They're all .md5's. One comes in 4 parts and the other all bundled in one. The latter, as has been my experience, does not wipe data

blankingblank said:
They're all .md5's. One comes in 4 parts and the other all bundled in one. The latter, as has been my experience, does not wipe data
Click to expand...
Click to collapse
I hate to sound dumb here but where
would I find individual parts to do a full
restore of my phone?

Adizzzle said:
I hate to sound dumb here but where
would I find individual parts to do a full
restore of my phone?
Click to expand...
Click to collapse
The single all in one tar will restore all parts of your phone.
Sent from my Nexus 5

jd1639 said:
The single all in one tar will restore all parts of your phone.
Sent from my Nexus 5
Click to expand...
Click to collapse
Well it sure didn't work last time I tried..
I can get the phone to boot but Wifi remains
locked in the off position and my baseband
remains at MK6 when I was trying to flash
the 4.4.2 NC1 build..
Could this be due to the KT kernel I
flashed before trying to restore?
I flashed the Kernel before all this
happened, then realized the kernel
dropped my wifi, so that's why I tried
restoring to stock, but the wifi still
drops on me after odin'ing back to
stock…

jd1639 said:
The single all in one tar will restore all parts of your phone.
Sent from my Nexus 5
Click to expand...
Click to collapse
Ya that's what I used too. I just formatted all the individual partitions first using philz to be sure I got a clean start. Also, if u wanna try it, the leaked NC1 firmware that dropped right before the official OTA's came out, I think that was a 'full restore' fw as it came in 4 sections.
---------- Post added at 03:15 PM ---------- Previous post was at 03:10 PM ----------
Adizzzle said:
Well it sure didn't work last time I tried..
I can get the phone to boot but Wifi remains
locked in the off position and my baseband
remains at MK6 when I was trying to flash
the 4.4.2 NC1 build..
Could this be due to the KT kernel I
flashed before trying to restore?
I flashed the Kernel before all this
happened, then realized the kernel
dropped my wifi, so that's why I tried
restoring to stock, but the wifi still
drops on me after odin'ing back to
stock…
Click to expand...
Click to collapse
There is a boot.img inside the stock fw if I'm not mistaken, and that should overwrite anything you've done to /boot (where the kernel lives).

So if I understand this correctly I have a couple of options one of them being I do the full firmware update using the 4 files provided from the leak. Or somehow install the boot.img and that should fix the wifi drop issues?

[Q] Few questions on roms / widgets / etc

Hey, so I'm fairly new to the whole rooting and customizing Android, so please forgive me if I come accross "ignorant" or generally childish. I bought a galaxy note 3 the other day and researched what rooting did. After getting convince that rooting was "awesome," I actually managed to root. I also played with some Xposed modules because they were fairly simple and cool. After more research, I found out that Verizon had a locked bootloader which prevented me from using any other roms? I also read that verizon/att users can use safestrap but i couldn't exactly find some specifics for it. So whats the disadvantages of safestrap? Do specific roms have to be used?
Another concern, I'd like to get a faster rom than stock touchwiz, but i'd also like to find a rom that can use ART runtime as well as maintaining a nice multi window feature. I tried XHaloFloatingWindow and another xposed module, and I can't say I was pleased with them compared to the touchwiz one. I'd also like to maintain S-pen features? Does anybody know of any roms that may come close to fitting most of these topics?
Final, completely random question, The lg g3 has this lockscreen widget where when it rains out, drops of water will cover/slide down the entire lock screen on top of your notifications. I thought this was awesome, but wasn't sure if it was possible to get on a note 3.
Anyways, Hope to get some simple answers

ATalkingRock said:
Hey, so I'm fairly new to the whole rooting and customizing Android, so please forgive me if I come accross "ignorant" or generally childish. I bought a galaxy note 3 the other day and researched what rooting did. After getting convince that rooting was "awesome," I actually managed to root. I also played with some Xposed modules because they were fairly simple and cool. After more research, I found out that Verizon had a locked bootloader which prevented me from using any other roms? I also read that verizon/att users can use safestrap but i couldn't exactly find some specifics for it. So whats the disadvantages of safestrap? Do specific roms have to be used?
Click to expand...
Click to collapse
Safestrap is as close to a custom recovery as we'll get, right now. Due to our bootloader, stock based rom are all we can use. However, we are not stuck with one rom. Check in the dev threads for roms compatible with your device. Also check the dev and general threads for more info on rooting, safestrap, and how to flash roms.
Another concern, I'd like to get a faster rom than stock touchwiz, but i'd also like to find a rom that can use ART runtime as well as maintaining a nice multi window feature. I tried XHaloFloatingWindow and another xposed module, and I can't say I was pleased with them compared to the touchwiz one. I'd also like to maintain S-pen features? Does anybody know of any roms that may come close to fitting most of these topics?
Click to expand...
Click to collapse
Art not available for us. Only stock based. See my recommendation above for other roms. There are a few with some pretty cool features and add-ons!
Final, completely random question, The lg g3 has this lockscreen widget where when it rains out, drops of water will cover/slide down the entire lock screen on top of your notifications. I thought this was awesome, but wasn't sure if it was possible to get on a note 3.
Anyways, Hope to get some simple answers
Click to expand...
Click to collapse
Not sure about this one...

Not sure about your specific questions, as I don't use multiwindow or the other features you listed. But I thought I would point out, what method of root did you use? Make sure of what system your running at this point. beans or kitkat? You will have to select a rom based on that. Or vice versa, re-root if you find a rom that you prefer thats running different android version. Either one will run safestrap obviously, since there are roms for each. You will find pros and cons to each. The con that I'm currently experiencing on kitkat that has me thinking about going back is I can't seem to find a modem that will get me decent reception so I'm assuming at this point that its kitkat thats causing it. Just something more for you to research. Being new to it, you've got ALOT of material to read about. But if you've already rooted, sounds like you've got a decent idea of the process. For me, tutorial videos were a life saver

LeftyGR said:
Safestrap is as close to a custom recovery as we'll get, right now. Due to our bootloader, stock based rom are all we can use. However, we are not stuck with one rom. Check in the dev threads for roms compatible with your device. Also check the dev and general threads for more info on rooting, safestrap, and how to flash roms.
Art not available for us. Only stock based. See my recommendation above for other roms. There are a few with some pretty cool features and add-ons!
Not sure about this one...
Click to expand...
Click to collapse
Alright so perhaps you can help me with just a few more concerns. I researched roms and such. I successfully downloaded safestrap, made a backup of my stock rom and put it on mycomputer. I also made a backup with titanium backup before that and it is also on the computer. I am looking at hyperdrive or jasminerom for the note 3. On there, it explains normal directions to install, but then it says to flash with odin, but when I read something about a tutorial how to install cutom roms on a website "Galaxynote3root" (I can't post the URL yet, says i'll be spamming) , it explained nothing of odin. What is odin? is it mandatory? Does my phone have it by default? hm.... Also i have a build number of NC4, does that build not work with NC2? sorry for inconvenience or annoying noobish questions. Thanks if you respond

So being on Kitkat, did you use the beans method that installed a rom with root basically built in already? And by saying you downloaded safestrap, is it successfully installed? When you boot the phone, do you get the safestrap bootup screen allowing to go into recovery?
If you've already gotten that far, your pretty well set to install either of those roms.

LeftyGR said:
Safestrap is as close to a custom recovery as we'll get, right now. Due to our bootloader, stock based rom are all we can use. However, we are not stuck with one rom. Check in the dev threads for roms compatible with your device. Also check the dev and general threads for more info on rooting, safestrap, and how to flash roms.
Art not available for us. Only stock based. See my recommendation above for other roms. There are a few with some pretty cool features and add-ons!
Not sure about this one...
Click to expand...
Click to collapse
scott_65 said:
So being on Kitkat, did you use the beans method that installed a rom with root basically built in already? And by saying you downloaded safestrap, is it successfully installed? When you boot the phone, do you get the safestrap bootup screen allowing to go into recovery?
If you've already gotten that far, your pretty well set to install either of those roms.
Click to expand...
Click to collapse
Well i rooted my phone via towelroot. I got safestrap hooked up and installed, so in other words when i reboot, yes it does have the splash screen. I am on kitkat as well. but do i need to install some sort of odin or something? sorry

I think as long as the rom's op says it's based on nc2 or nc4, you should be good. You should not need to worry about odin, since you're already on kk.
Since you're new, I'd suggest not touching the stock slot. It gives you a fall back if something goes wrong. Make sure you understand using safestrap, and start trying some stuff out.
---------- Post added 30th July 2014 at 12:00 AM ---------- Previous post was 29th July 2014 at 11:58 PM ----------
scott_65 said:
So being on Kitkat, did you use the beans method that installed a rom with root basically built in already? And by saying you downloaded safestrap, is it successfully installed? When you boot the phone, do you get the safestrap bootup screen allowing to go into recovery?
If you've already gotten that far, your pretty well set to install either of those roms.
Click to expand...
Click to collapse
Sounds like he rooted the nc4 with towelroot, cuz he started on nc4. And sounds like ss is working for him, if he's made a backup.

LeftyGR said:
I think as long as the rom's op says it's based on nc2 or nc4, you should be good. You should not need to worry about odin, since you're already on kk.
Since you're new, I'd suggest not touching the stock slot. It gives you a fall back if something goes wrong. Make sure you understand using safestrap, and start trying some stuff out.
Click to expand...
Click to collapse
Okay thanks, that boosts my confidence a bit! I'm just afraid of bricking my phone, as any noobie should be.

ATalkingRock said:
Okay thanks, that boosts my confidence a bit! I'm just afraid of bricking my phone, as any noobie should be.
Click to expand...
Click to collapse
Good man.
If you find something that you don't know or understand, search that thread for an answer. Then ask if you don't find an answer. And always try to give any other details you think might help.
As long as you remember search is your friend first...then ask...you will almost always find people to help you out!

LeftyGR said:
Good man.
If you find something that you don't know or understand, search that thread for an answer. Then ask if you don't find an answer. And always try to give any other details you think might help.
As long as you remember search is your friend first...then ask...you will almost always find people to help you out!
Click to expand...
Click to collapse
alright alright I'm very sorry for this final question as I actually have tried to search for this but only got comparisons between titanium backup and safestrap. So, if I were to make a titanium backup right now, after the fact that i made a safestrap backup or installation, will that effect anything? I'm really really sorry if these questions are beyond beginner, I just like to play it safe.

ATalkingRock said:
alright alright I'm very sorry for this final question as I actually have tried to search for this but only got comparisons between titanium backup and safestrap. So, if I were to make a titanium backup right now, after the fact that i made a safestrap backup or installation, will that effect anything? I'm really really sorry if these questions are beyond beginner, I just like to play it safe.
Click to expand...
Click to collapse
Nope. Tibu backs up specific apps and it's associated data and stores it on sd. When you open tibu, it gets it's info from files it stores on sd. Recovery backs up your entire rom environment, but doesn't actually touch sd card user space.
This is why tibu is so helpful. Everything pops up that you had backed up, even on a new rom.

I'm not familiar with the towelroot method. Only the old Kingo for jb, or the beans method for kk. Sounds like your good to go for any KK roms, and Lefty seems familiar, good deal. Not sure how old you are or how far back your computer knowledge goes, so this may do you no good. Odin doesn't go on your phone, it goes on your computer. I always think of it as the old school DOS, or like now when you boot to command prompt if windows isn't working. Its like a back door when your phone operating system isn't working, or if you need to make changes to part of the system that would otherwise need to be running to make those changes FROM the phone. Its flashes the changes TO the phone from your computer instead.
I'm rambling. Its too early. Anyhow, glad your getting things moving along. You can try roms in various rom slots, but you may have issues. I had some roms work well, others not well at all. The ones that have problems, they seem to work better in the stock slot. So you have to wipe the stock slot and flash it there. No big deal, just don't goof up, flash it all at once. If you pause, take a potty break and the battery dies, whatever, don't forget, you have no operating system at that point. Thats when Odin would come into play

LeftyGR said:
Nope. Tibu backs up specific apps and it's associated data and stores it on sd. When you open tibu, it gets it's info from files it stores on sd. Recovery backs up your entire rom environment, but doesn't actually touch sd card user space.
This is why tibu is so helpful. Everything pops up that you had backed up, even on a new rom.
Click to expand...
Click to collapse
Alright so quick update. I successfully installed both roms into slots 1 and 2 respectively. Everything went okay, I rebooted system, but the screen just stayed black. They aren't loading, i still can go back to stock rom. But uhm any idea as to why this is occuring? Could it be the NC4/NC2 build things?
In the hyperdrive rom for the note 3, it says it will work with verizon and also states that after the initial reboot after flashing the rom, there will be a 10 minute wait until it actually boots up. I'd say i've waited 15 minutes and nothing has shown up. So I'm assuming something went wrong. Perhaps i should try to reflash it?
EDIT: I read the directions further ahead and managed to flash a file via odin for the first time, now im getting a rom's boot animation which is good. I hope this'll work !
Edit 2: I successfully installed it and booted it up, everything went okay, I restored my titanium backup and then titanium prompted me to restart. I restarted, and now its bootlooping android.process.acore or something like that is crashing everything =/

ATalkingRock said:
Alright so quick update. I successfully installed both roms into slots 1 and 2 respectively. Everything went okay, I rebooted system, but the screen just stayed black. They aren't loading, i still can go back to stock rom. But uhm any idea as to why this is occuring? Could it be the NC4/NC2 build things?
In the hyperdrive rom for the note 3, it says it will work with verizon and also states that after the initial reboot after flashing the rom, there will be a 10 minute wait until it actually boots up. I'd say i've waited 15 minutes and nothing has shown up. So I'm assuming something went wrong. Perhaps i should try to reflash it?
EDIT: I read the directions further ahead and managed to flash a file via odin for the first time, now im getting a rom's boot animation which is good. I hope this'll work !
Edit 2: I successfully installed it and booted it up, everything went okay, I restored my titanium backup and then titanium prompted me to restart. I restarted, and now its bootlooping android.process.acore or something like that is crashing everything =/
Click to expand...
Click to collapse
uh oh now my stock rom is bootlooping as well. i in trouble

ATalkingRock said:
uh oh now my stock rom is bootlooping as well. i in trouble
Click to expand...
Click to collapse
What did you flash in odin?

LeftyGR said:
What did you flash in odin?
Click to expand...
Click to collapse
In JasmineRom's instructions it says to flash a file called unified_KK_Firmware_RE.tar.md5. After flashing it, it booted up to the new rom.But seemingly once i restarted after titanium backup restored everything it crashed. I then cleared all the cache and data through a factory reset in the safestrap settings and it started up normally. Am I not going to be able to restore my things through titanium? I would send you a link to the odin flash file, but I can't until I have a certain number of posts

ATalkingRock said:
In JasmineRom's instructions it says to flash a file called unified_KK_Firmware_RE.tar.md5. After flashing it, it booted up to the new rom.But seemingly once i restarted after titanium backup restored everything it crashed. I then cleared all the cache and data through a factory reset in the safestrap settings and it started up normally. Am I not going to be able to restore my things through titanium? I would send you a link to the odin flash file, but I can't until I have a certain number of posts
Click to expand...
Click to collapse
No need. I know what you're saying. So flashing that file shouldn't have been really necessary, given you're already on nc4. But it doesn't hurt and should not have caused what you described. So you have roms in stock, slot 1, and slot 2? Which ones bootloop?
For tibu, I would uninstall, reboot, reinstall. Somehow it didn't like you doing that.

LeftyGR said:
No need. I know what you're saying. So flashing that file shouldn't have been really necessary, given you're already on nc4. But it doesn't hurt and should not have caused what you described. So you have roms in stock, slot 1, and slot 2? Which ones bootloop?
For tibu, I would uninstall, reboot, reinstall. Somehow it didn't like you doing that.
Click to expand...
Click to collapse
Alright so as we speak right now, I have slot 1 with jasminerom and stock which should be the untouched stock rom of course. I have a backup through safestrap of that. I will uninstall titaniumbackup and reinstall and see if that works?
edit: sorry I feel as though I'm being unclear as I can hardly comprehend my own messages. Before, both slot 1 and stock were bootlooping. This bootloop came after titanium backup promted me to restart. But when i cleared the cache through the factory reset, the slot1 rom started to work agin (jasminerom), I haven't tried stock rom to see if it works yet. I'm currently on jasminerom about to re-restore my apps through titanium backup like you said.

LeftyGR said:
No need. I know what you're saying. So flashing that file shouldn't have been really necessary, given you're already on nc4. But it doesn't hurt and should not have caused what you described. So you have roms in stock, slot 1, and slot 2? Which ones bootloop?
For tibu, I would uninstall, reboot, reinstall. Somehow it didn't like you doing that.
Click to expand...
Click to collapse
alright i finished re-restoring through titanium backup. Once it finished it provided a notification saying "batch complete, 66 elements failed" Right now all my apps are here and everything is seeming to work. Should I restart to see if it bootloops again?

ATalkingRock said:
alright i finished re-restoring through titanium backup. Once it finished it provided a notification saying "batch complete, 66 elements failed" Right now all my apps are here and everything is seeming to work. Should I restart to see if it bootloops again?
Click to expand...
Click to collapse
You should be ok. How many apps did you try to restore, if 66 failed?