***How To ROOT 4.3 & NC4 OTA, Install Recovery & Roms - Verizon RETAIL Note 3***

[jrmckinn]

Weird Issue

So, I was rooted, safestrapped and flashed to JB. Then ran out of space trying to update apps. So backed up using titanium pro, created a new slot with max space in safestrap, flashed the JB I had already downloaded and rebooted. Phone boots up, safestrap screen shows, then black screen with nothing else happening. Ok, that's odd I thought. I pulled the battery, restarted, same thing. No bueno. So I go back in to safestrap and set the boot back to slot 1, the working JB slot. Same thing. Uh-oh. Back in to safestrap, set the Factory slot to be the active. Almost the same result, except I don't even get the safestrap window. Just black screen.

No panic yet, something just got corrupted. Crack open Odin and do a full restore. Everything comes up like it just came out of the box. I then root via Kingo, fresh downloads of everything, install Chanfire, safestrap, restart...

black screen and nothing else.

I figured it had locked up, but while I'm searching for an answer I look down and see that I'm at the safestrap recovery screen, 20 minutes after I powered up the phone. At that point I try to flash to JB, and it just sits and sits and sits. I restart at that point and Odin it back to stock. Even at stock this is an amazing phone, but with the latest updates my battery life is dreadful, so I'd like to get back to JB or another ROM. Any ideas what may be causing this to occur? Thanks in advance!

jrmckinn

 

[Az Biker]

So, I was rooted, safestrapped and flashed to JB. Then ran out of space trying to update apps. So backed up using titanium pro, created a new slot with max space in safestrap, flashed the JB I had already downloaded and rebooted. Phone boots up, safestrap screen shows, then black screen with nothing else happening. Ok, that's odd I thought. I pulled the battery, restarted, same thing. No bueno. So I go back in to safestrap and set the boot back to slot 1, the working JB slot. Same thing. Uh-oh. Back in to safestrap, set the Factory slot to be the active. Almost the same result, except I don't even get the safestrap window. Just black screen.

No panic yet, something just got corrupted. Crack open Odin and do a full restore. Everything comes up like it just came out of the box. I then root via Kingo, fresh downloads of everything, install Chanfire, safestrap, restart...

black screen and nothing else.

I figured it had locked up, but while I'm searching for an answer I look down and see that I'm at the safestrap recovery screen, 20 minutes after I powered up the phone. At that point I try to flash to JB, and it just sits and sits and sits. I restart at that point and Odin it back to stock. Even at stock this is an amazing phone, but with the latest updates my battery life is dreadful, so I'd like to get back to JB or another ROM. Any ideas what may be causing this to occur? Thanks in advance!

jrmckinn

There's another user that experienced similar issues flashing roms. I'm waiting to hear what he did to finally get up and running.

Are you using SafeStrap 3.65?


Notorious 3

 

[jrmckinn]

There's another user that experienced similar issues flashing roms. I'm waiting to hear what he did to finally get up and running.

Are you using SafeStrap 3.65?


Notorious 3

Yes, 3.65. I'm going to take another shot with a brand new SD card to see if that helps. The one that's in there now is a bit long in tooth and on the smaller side. Amazon should be delivering tonight.

 

[KOKJ]

Yes, 3.65. I'm going to take another shot with a brand new SD card to see if that helps. The one that's in there now is a bit long in tooth and on the smaller side. Amazon should be delivering tonight.

If you ODIN'd back to a stock software, then followed the proper steps, then man. Is your USB cable bad that you transfer the files to your phone?

I downloaded multiple ROMs, checked all MD5 checksums, downloaded and loaded SafeStrap multiple times, everything was appearing fine until I'd create the ROM slots, load the ROM, reboot and nothing. I'd have to pull the battery, go into recovery and select the stock rom slot to boot up. I'm really not sure what my issue was. I was able to successfully install the JellyBeans ROM but nothing else yet.

On every ROM I try to load now, it says "Unable to mount internal storage." Very odd, but JellyBeans loaded just fine.

 

[jrmckinn]

That would be a possibility, except that the initial problem began after I had already rooted and installed a new rom. I hadn't connected to anything when the problem started. Great suggestion though. Bad cables can create ridiculous problems.

Sent from my SM-N900V using Tapatalk

 

[KOKJ]

Hey az_biker,
What do you think about this? On every ROM I try to load now, it says "Unable to mount internal storage." Very odd, but JellyBeans loaded just fine.

---------- Post added 30th January 2014 at 12:00 AM ---------- Previous post was 29th January 2014 at 11:49 PM ----------

Not sure if you're still around, but what do you think about this?
I was able to successfully load JellyBeans ROM. But, on every other ROM I try to load now, it says "Unable to mount internal storage." Very odd, but JellyBeans loaded just fine.

 

[Az Biker]

Hey az_biker,
What do you think about this? On every ROM I try to load now, it says "Unable to mount internal storage." Very odd, but JellyBeans loaded just fine.

---------- Post added 30th January 2014 at 12:00 AM ---------- Previous post was 29th January 2014 at 11:49 PM ----------


Not sure if you're still around, but what do you think about this?
I was able to successfully load JellyBeans ROM. But, on every other ROM I try to load now, it says "Unable to mount internal storage." Very odd, but JellyBeans loaded just fine.

At this point, Dutch is gonna be your best bet, I've exhausted my small amount of knowledge already

Notorious 3

 

[DutchDogg54]

Not sure if you're still around, but what do you think about this?
I was able to successfully load JellyBeans ROM. But, on every other ROM I try to load now, it says "Unable to mount internal storage." Very odd, but JellyBeans loaded just fine.

Honestly, I'm pretty confused by your whole situation as well but let me ask you this - When you flashed Jellybeans you must have created a clean slot and installed to it since it was the first rom you installed. When you are trying to install others are you creating new slots to install them on or are you trying to install to the same slot as jellybeans was on?

If you can't get new slots to work you might be able to use the same slot jellybeans is on or try using the stock slot. Beyond those things, I really don't know what else you could try.

 

[bftb0]

So ... created a new slot with max space in safestrap...

Does this use up all remaining free (filesystem) storage on mmcblk0p25, or is it just a really big slot with some free space still left in the host filesytem?

 

[KOKJ]

Honestly, I'm pretty confused by your whole situation as well but let me ask you this - When you flashed Jellybeans you must have created a clean slot and installed to it since it was the first rom you installed. When you are trying to install others are you creating new slots to install them on or are you trying to install to the same slot as jellybeans was on?

If you can't get new slots to work you might be able to use the same slot jellybeans is on or try using the stock slot. Beyond those things, I really don't know what else you could try.

I created a slot on slot 1, and installed Jellybeans ROM. I tried loading others on slot 2 with no success. I can load Jellybeans ROM on slot 2, but no other ROM on any other slot. So, I'm only able to install Jellybeans ROM on all slots, but nothing else on any slots. I'm getting an error that says "failure to mount internal memory." Jellybeans doesn't give me that error.

 

[KOKJ]

I created a slot on slot 1, and installed Jellybeans ROM. I tried loading others on slot 2 with no success. I can load Jellybeans ROM on slot 2, but no other ROM on any other slot. So, I'm only able to install Jellybeans ROM on all slots, but nothing else on any slots. I'm getting an error that says "failure to mount internal memory." Jellybeans doesn't give me that error.

I've tried again loading various ROMs on various slots and I'm not getting the same "failure to mount internal memory" message, but ROM installations are failing within seconds of starting, without any real message but only saying they were successful.

 

[Az Biker]

I've tried again loading various ROMs on various slots and I'm not getting the same "failure to mount internal memory" message, but ROM installations are failing within seconds of starting, without any real message but only saying they were successful.

I'm stumped. Well I sure hope you like Beans Rom...

Notorious 3

 

[Az Biker]

I've tried again loading various ROMs on various slots and I'm not getting the same "failure to mount internal memory" message, but ROM installations are failing within seconds of starting, without any real message but only saying they were successful.

I'm working with another guy that is having issues flashing roms to a specific rom slot, if we come up with anything, I'll get at you!

 

[KOKJ]

Meant to tell you, I found the problem. I was validating the MD5 on the files after they were downloaded to my PC. However, I never checked them after I transferred them to the handset. Either my cable has gone bad, or my USB controller for the USB port I've been using is acting up, but I transferred them to my handset from my primary computer, checked the MD5 and it failed. I used another machine and transferred the files to my handset and validated MD5 successfully and was able to load all the ROMs.

 

[Az Biker]

Meant to tell you, I found the problem. I was validating the MD5 on the files after they were downloaded to my PC. However, I never checked them after I transferred them to the handset. Either my cable has gone bad, or my USB controller for the USB port I've been using is acting up, but I transferred them to my handset from my primary computer, checked the MD5 and it failed. I used another machine and transferred the files to my handset and validated MD5 successfully and was able to load all the ROMs.

So the MD5 got corrupted somehow between the transfer from PC to device? That's really weird, but I am GLAD you got it figured out!

Enjoy your freedom JI know you know about Beans, but in case you haven't heard of these roms; I suggest giving Baja, and Eclipse a try.

All three are really top notch Roms!

 

[KOKJ]

So the MD5 got corrupted somehow between the transfer from PC to device? That's really weird, but I am GLAD you got it figured out!

Enjoy your freedom JI know you know about Beans, but in case you haven't heard of these roms; I suggest giving Baja, and Eclipse a try.

All three are really top notch Roms!

I've got both of those loaded up and have been comparing them all. Just need to decide on one. Thanks for your willingness to help, by the way.

 

[Az Biker]

I've got both of those loaded up and have been comparing them all. Just need to decide on one. Thanks for your willingness to help, by the way.

No problem. If I were stuck like you were, I would want someone to help me out!

 

[KOKJ]

No problem. If I were stuck like you were, I would want someone to help me out!

But something like this, I should've caught. Oh well, my oversight.

 

[jrmckinn]

Got my new sd card in and attempted tried to start the process, but it seems I'm completely unable to root at all now. Kingo just constantly reports back Fail: NotSupport. I've tried at least 3 dozen times with different cables, slots, cables etc. It also look like Kingo's twitter feed has gone silent. Anyone else having issues rooting with Kingo over the last day or so?

jrmckinn

 

[Az Biker]

Got my new sd card in and attempted tried to start the process, but it seems I'm completely unable to root at all now. Kingo just constantly reports back Fail: NotSupport. I've tried at least 3 dozen times with different cables, slots, cables etc. It also look like Kingo's twitter feed has gone silent. Anyone else having issues rooting with Kingo over the last day or so?

jrmckinn

Download "Root Checker" and see if you are actually rooted even though it reported FAILED. This has happened a few times.