Alright, so i soft bricked my phone is what the internet is telling me. the phone turns on but stops at the opening samsung screen with the unlock symbol on it. i can get into odin mode, and recovery, but i have a locked recovery. I went to flash a rom to my stock slot which is what the forum said to do so i did it. looking back it was pretty stupid, and now when i tried to recover my back up it came back with an error and then said there was no os system in my stock slot. i tried doing a recovery in rom slot 1 which it recovered but when i restarted my phone everytime it went into a boot loop. so now i have a very expensive paperweight. so my questions are one is there anyway that i could salvage my phone. two is there a way i could get it back to where i was with any of my recoveries that i have. i herd the odin method works but will it work for my phone? i tried the odin before but never could get it to work. also kies is out of the question because neither programs will recognize my phone.
oh yeah my phone. so the last thing i had running on it was the 4.4.2 update I337 NC1 would i have to flash the NC1 os or could i flash an earlier one because all i could find were the 4.2.2's and the NB1 flash.
tshaulis said:
Alright, so i soft bricked my phone is what the internet is telling me. the phone turns on but stops at the opening samsung screen with the unlock symbol on it. i can get into odin mode, and recovery, but i have a locked recovery. I went to flash a rom to my stock slot which is what the forum said to do so i did it. looking back it was pretty stupid, and now when i tried to recover my back up it came back with an error and then said there was no os system in my stock slot. i tried doing a recovery in rom slot 1 which it recovered but when i restarted my phone everytime it went into a boot loop. so now i have a very expensive paperweight. so my questions are one is there anyway that i could salvage my phone. two is there a way i could get it back to where i was with any of my recoveries that i have. i herd the odin method works but will it work for my phone? i tried the odin before but never could get it to work. also kies is out of the question because neither programs will recognize my phone.
oh yeah my phone. so the last thing i had running on it was the 4.4.2 update I337 NC1 would i have to flash the NC1 os or could i flash an earlier one because all i could find were the 4.2.2's and the NB1 flash.
Click to expand...
Click to collapse
1. As long as you can get into Odin mode, you're ok.
2. if you are on NB1 or NC1 base running safestrap 3.72, stock slot is the ONLY slot you can use. ROM slots do not work.
3. it's not really clear what you did to cause the boot loop, but lets get you back to stock...
Check out post 5 in my thread. If you follow these steps, you should be back to stock (and rooted with recovery, if you want) in no time.
http://forum.xda-developers.com/showthread.php?t=2616221
BTW - Post 2 has a list of ROMs that are safe to flash for safetrap users. Read the install notes first then follow the install instructions to install one of the ROMS.
guut13 said:
1. As long as you can get into Odin mode, you're ok.
2. if you are on NB1 or NC1 base running safestrap 3.72, stock slot is the ONLY slot you can use. ROM slots do not work.
3. it's not really clear what you did to cause the boot loop, but lets get you back to stock...
Check out post 5 in my thread. If you follow these steps, you should be back to stock (and rooted with recovery, if you want) in no time.
http://forum.xda-developers.com/showthread.php?t=2616221
BTW - Post 2 has a list of ROMs that are safe to flash for safetrap users. Read the install notes first then follow the install instructions to install one of the ROMS.
Click to expand...
Click to collapse
sir i will tell you that your a genius. its pretty cool to see the creator of the link you posted (which is you) being used on other sites. goes to show you really know what you are doing. for me well i thought i did, and wish i did. it might be awhile before i change roms again or at least until i get more knowledge.
ok so from my understanding safestrap is having difficulties being you and only flash in the stock slot. ok well what i did was flashed the hyperdrive rom (from your link) to the stock slot because in the hyperdrive forum it said only can flash on stock. so i did a full wipe on stock then flashed the hyperdrive and gapps. well my guess is when i did the full wipe it wiped the os. also i didn't grab the supporting modules for the rom so i didnt have wifi or service which made me try to restore from my nandroid and couldnt because it said error loading /system. then tried other things i thought would work and softbricked it so to that.
i think for newbies like myself its a lot of reading and well we could miss some things and screw things up. and plus samsung had to make different freakin models like the i337 or i9505 or the i9000 or something and everything has to be the exact same and perfect. but oh well. i am happy to tell you that my phone is fully restored and working from the day before all this happened. thanks again and sorry for the long message.
Related
Ok, i realize i have a different phone from this thread but it is close and my problems closely reflect the issues ive seen with the Galaxy S.
A little background. Im no perfect i know what im doing when it comes to rooting. I have an HTC Tbolt and rooted many of those, an older touch pro 2, and this is first time doing a samsung. I am getting the hang of ODIN (i wish everyone would just use this program instead of bouncing back and forth between heimdall and ODIn but whatever) Im liking ODIN cause it works well. I was successful at flashing a new rom into this Samsung phone. 95% of it worked, wifi i think didnt but everything else worked. While trying to fix the phones wifi somehow i have stopped the phone from booting into CMW recovery unless forced or booting into a rom. I can get into CMW but i must hold down the Vol Down button to get there, otherwise a clean basic boot takes me to the stock android system recovery screen and will not boot a rom.
I have something backwards or out of order. I am just trying to get the rom to identify the installed CMW and the installed ROM through CMW but it wont do it.
Any help would be appreciated, i dont want my GF to find out i jacked her phone lol
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
annqx said:
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
Click to expand...
Click to collapse
Its a stratosphere. Im using the root and / or stock files in the root method. I use ODIN to flash the StratCWMRecovery.tar.md5 and if i tick "reboot" then it reboots into CWM i install a rom or stock rom and it finishes. I reboot the phone and it instantly goes back to android system recovery. If you like ill make a short video to give you an idea of whats going on.
I will note that im close to making a jig but its not 100% bricked obviously. 3 button method still works (and unecessary at this point since all the phone does is go straight into the stock bootloader) and then after i install CWM i can force it in to CWM but it wont actualy boot into it.
From a programing standpoint i feel the pointers or partitions are incorrect. Its like booting a computer that has a hard drive with windows installed however getting the bios to tell it to boot from the hard drive isnt working. THats the easiest way to explain this.
One thing i want to note is the only errors i am getting are when i try to partition the SD card from CWM. I get an error saying sdparted is not found.
I am not getting a full understanding of how the root system works on this phone.
Again any help is appreciated.
Made a short video. Its uploading now. http://www.youtube.com/watch?v=tFZ5Adm5AdQ
So whatever i did i was able to fix. I think me being a very visual person and normally having access to all files i need or could use in a situation is always nice. Here, i didnt but i found them. Here's the link. Its obviously for stratosphere but i took about 10 minutes and let ODIN install all these files and it worked.
original posting but the link doesnt work for download
http://rootzwiki.com/topic/11183-eh2-full-factory-odin-restore/
where i downloaded it
http://www.fileswap.com/dl/t4D235pUTO/SCH-I405.EH2_rel.md5.html
Again this is for stratosphere. Since it really helped me return to stock and allow me to re root in about 15 minutes this thread should be moved but there is no stratosphere area
I've generally managed to root and/or customize most of my devices with the help from these forums, but this one has me stumped. I picked up an AT&T Galaxy S4 recently, and unfortunately it was already on a locked bootloader. I was able to root and install Safestrap 3.71 with little trouble. After some tweaking of the stock ROM, I decided to have a go with some custom ones.
Until recently, I'd been able to flash just about any SS-compatible ROM to any slot with little to no issue. Some required flashing of GApps, or Kernels, but aside from a few FC's or signal issues, the actual flashing portions always went smoothly. I ended up flashing DarthStalker vX1 to my stock slot with the MK2 kernels and have had zero issues with the ROM functionality. Being curious about recent developments with other ROM's, I decided to try flashing a few. The problem I'm having is that 90% of the ones I try to flash are going into a boot loop. Even those that worked previously (Hyperdrive, SHOstock) are boot looping.
I have tried deleting and recreating various ROM slots and at one point I managed to get SHOstock (SS) 3.0 to boot, but all of the GApps were crashing to the point where it was unusable, regardless of GApps I flashed over it for testing purposes.
I guess I'm wondering if there may be some sort of issue with having a custom ROM in the stock slot? Perhaps some sort of file or data corruption that is stopping these ROM's from working, even though they all worked previously? It just doesn't seem to be making sense because I don't believe I've changed anything since the last time I was able to flash to any SS slot. I've tried searching, but pretty much all of the boot loop issues I've come across were related to something that I've either already ruled out, or simply didn't apply to my configuration. Any hints or tips would be great. Please let me know if anyone needs more information about the config, or steps I've taken so far. Thanks all!
@remedee
I believe for HyperDrive u also need to install Att compatible pack and u also need flash ATT mk2 kernel modules .... check this thread about MK2 INDEX and ROM LISTS by @guut13 http://forum.xda-developers.com/showthread.php?t=2616221 anything u should know about all the compatible roms and instruction. ....u might get better help on that thread since alot of Rom flashaholic there. ...check with @ddubz he is flashaholic Master..... :thumbup::thumbup:.... Goodluck.....
Swyped From MK2 Dark Venom SS Edition
Once you flash a bad ROM on Stock slot and you boot loop, you are cooked. Only way to fix it is to Odin back to stock. Then you can restart the process.
If you flash a bad ROM on a ROM slot, you can just delete the ROM slot, recreate it, and you will be good to go for another try.
That's been my experience, anyways.
ted77usa said:
@remedee
I believe for HyperDrive u also need to install Att compatible pack and u also need flash ATT mk2 kernel modules .... check this thread about MK2 INDEX and ROM LISTS by @guut13 http://forum.xda-developers.com/showthread.php?t=2616221 anything u should know about all the compatible roms and instruction. ....u might get better help on that thread since alot of Rom flashaholic there. ...check with @ddubz he is flashaholic Master..... :thumbup::thumbup:.... Goodluck.....
Swyped From MK2 Dark Venom SS Edition
Click to expand...
Click to collapse
Thanks for the reply. I've read through quite a few of the threads for the individual ROMs, but unfortunately the issue isn't related to any one specific ROM. I do have the compatibility pack and modules for HyperDrive and I was able to successfully get that installed previously. I was using that as an example of a ROM that worked before with this same configuration, which is why it's bugging me. I'll wipe out the existing slot 1 and give it another go, making sure I flash those as well. Unfortunately that doesn't explain why SHOstock (which I tested extensively before), and others go into a boot loop as well.
The only thing I can think of is perhaps I'm not wiping properly. So far, whenever I attempt to install a new ROM, I create a new slot with the default size values, do a factory reset, install ROM and any module/kernel recommended with it, wipe cache, reboot. Not sure what else I could be doing wrong.
guut13 said:
Once you flash a bad ROM on Stock slot and you boot loop, you are cooked. Only way to fix it is to Odin back to stock. Then you can restart the process.
If you flash a bad ROM on a ROM slot, you can just delete the ROM slot, recreate it, and you will be good to go for another try.
That's been my experience, anyways.
Click to expand...
Click to collapse
Thankfully I don't think I've had any truly bad flashes that resulted in a brick, or even a partial brick. My stock slot is running a custom (Darthstalker) ROM that is still fully functional through all of this other testing. I do have backups of my original stock config, as well as a recent backup of the DS ROM in the stock slot, so I'm not sure it's related to a bad ROM in that slot. It's just really strange that ROMs that were working just fine before in any slot are now causing loops. I haven't had to Odin back to stock or anything, but I'm considering doing that just to get back to a clean base. It just seems unnecessary since my stock slot is still 100% functional. No signal drops, all wifi and bluetooth connections work flawlessly, etc.
I'm usually the guy that scours these forums until I find a solution, but this problem is just plain weird. As you can see from my post count, this is the first time I've thrown up my hands and asked for help. I'm not even sure there is anything really broken. It could very easily be something stupid I have or haven't done. It's just frustrating when I flash a ROM that I've verified the MD5 on, and I know for a fact has worked previously. I'll keep plugging away at it and post back if I figure out what's going on. Thanks again!
@remedee If I were u..... Follow my thread to go back to stock MK2 http://forum.xda-developers.com/showthread.php?t=2621279 check post #2 for guide on how to. After u got fresh MK2 firmware ..... root it.... install safestrap v3.71 and then create rom slot 1 first to see if the rom stable enough ....If it does then make your rom slot 1 back up .....then wipe your stock slot..... restore your rom slot 1 back up to stock slot or follow @guut13 instruction noted on every compatible rom lists from his thread. ..... Goodluck....:good:
Swyped From MK2 Dark Venom SS Edition
remedee said:
Thankfully I don't think I've had any truly bad flashes that resulted in a brick, or even a partial brick. My stock slot is running a custom (Darthstalker) ROM that is still fully functional through all of this other testing. I do have backups of my original stock config, as well as a recent backup of the DS ROM in the stock slot, so I'm not sure it's related to a bad ROM in that slot. It's just really strange that ROMs that were working just fine before in any slot are now causing loops. I haven't had to Odin back to stock or anything, but I'm considering doing that just to get back to a clean base. It just seems unnecessary since my stock slot is still 100% functional. No signal drops, all wifi and bluetooth connections work flawlessly, etc.
I'm usually the guy that scours these forums until I find a solution, but this problem is just plain weird. As you can see from my post count, this is the first time I've thrown up my hands and asked for help. I'm not even sure there is anything really broken. It could very easily be something stupid I have or haven't done. It's just frustrating when I flash a ROM that I've verified the MD5 on, and I know for a fact has worked previously. I'll keep plugging away at it and post back if I figure out what's going on. Thanks again!
Click to expand...
Click to collapse
Just to be clear, I didn't necessarily mean bricked when I said cooked, but kind of. I tested a bunch of ROMs for my threads. If i flashed one that didn't work, my phone would usually boot loop...
samsung logo, safestrap menu, black screen, reboot, samsung logo, safestrap menu, black screen, reboot, and so on...
If I stopped the boot loop by going back into safestrap, no matter how many times I wiped or which ever ROM I flashed next (even known working ones), I always went back into a boot loop after rebooting. Only thing that worked was odin back to stock. (Can't remember if I tried restoring, though.)
ROM slot was different. Deleting it and recreating was all it took. That's why I learned my lesson and just test new roms on ROM slot first.
remedee said:
Thanks for the reply. I've read through quite a few of the threads for the individual ROMs, but unfortunately the issue isn't related to any one specific ROM. I do have the compatibility pack and modules for HyperDrive and I was able to successfully get that installed previously. I was using that as an example of a ROM that worked before with this same configuration, which is why it's bugging me. I'll wipe out the existing slot 1 and give it another go, making sure I flash those as well. Unfortunately that doesn't explain why SHOstock (which I tested extensively before), and others go into a boot loop as well.
The only thing I can think of is perhaps I'm not wiping properly. So far, whenever I attempt to install a new ROM, I create a new slot with the default size values, do a factory reset, install ROM and any module/kernel recommended with it, wipe cache, reboot. Not sure what else I could be doing wrong.
Click to expand...
Click to collapse
next time you try to flash one and it fails try making the data partition smaller. Had a guy pm me and couldn't get rom to boot and i had him do this and bam it booted right up. Worth a shot. Also i have switched phones i went to the nexus 5 and i am not as fresh with the s4 stuff as i was a few weeks ago. PM if you need any help
I still plan to Odin back to stock but I didn't have time tonight. I did however grab a ROM from the link provided by ted77usa (thanks man, I can't seem to figure out how to mention at the moment). The Wicked v10 ROM installed to a clean Slot 1. I know that DarthStalker installed using Aroma, and Wicked is one of the few that I've tested that also uses Aroma. I don't know if it makes a difference, but this is the first ROM to install without a boot loop since I started having trouble.
I'm also wondering if the fact that this ROM had never been installed before has anything to do with it. I'm going to back it up since it's functional, then wipe and try to reinstall just to see if I get a boot loop. Thanks again to everyone for all of the input.
Sorry for the delay in getting back on this. My toddler finds new and interesting ways of keeping me from my hobbies Just wanted to say thanks to @ted77usa @guut13 and @ddubz. I tried resizing the partition and that didn't seem to help. I ended up starting from scratch and everything seems to be running properly. I've got DarthStalker back in the stock slot, Wicked in slot 1 and Hyperdrive in slot 2. I'm quite certain it's overkill, but just knowing I can switch between them and tinker makes me happy. Thanks again for all the input. XDA is definitely an awesome community.
Yesterday morning I came on and saw kitkat had finally rolled around. I read through Beans notes watched the tube, and got to where I wanted to be. But I came from a time of old flashing addicted never satisfied HTC thunderbolt so much easier than this Note 3.
So after I was on 4.4.2 kitkat by beans thread I decided to try a rom. I figured lets lighten the load and deleted all my other slots and tried to flash over with biggins rom. I thought I followed the steps correctly installed busybox X , new safestrap and rebooted. well now I cannot get anywhere in any recovery it shows the blue writing but then just reboots and bam back to hanging. I can only get into ODIN so I am assuming this is still a salvageable situation.
Really F#$#[email protected]%@%# frustrated as I try to figure things out on my own reading through other threads but I cant. And I can not have my phone off any longer. Odin recognizes port. Everything I try to put on pit to tar to image are all failures. Kingo not any help 1.2.2
I need someone to reach out and kick my face back in place
grengoblinalway said:
Yesterday morning I came on and saw kitkat had finally rolled around. I read through Beans notes watched the tube, and got to where I wanted to be. But I came from a time of old flashing addicted never satisfied HTC thunderbolt so much easier than this Note 3.
So after I was on 4.4.2 kitkat by beans thread I decided to try a rom. I figured lets lighten the load and deleted all my other slots and tried to flash over with biggins rom. I thought I followed the steps correctly installed busybox X , new safestrap and rebooted. well now I cannot get anywhere in any recovery it shows the blue writing but then just reboots and bam back to hanging. I can only get into ODIN so I am assuming this is still a salvageable situation.
Really F#$#[email protected]%@%# frustrated as I try to figure things out on my own reading through other threads but I cant. And I can not have my phone off any longer. Odin recognizes port. Everything I try to put on pit to tar to image are all failures. Kingo not any help 1.2.2
I need someone to reach out and kick my face back in place
Click to expand...
Click to collapse
Are you sure your selecting the .md5 file and not the unzipped file?
Ok I know this is gonna suck, but you are probably gonna have to find a tar.md5 file for mje baseband and Odin back to 4.3, then reroot and follow beans instruction to go back to 4.4.2 to a T at which point you just need to install the new safe strap 3.72 (I believe beans 4.4.2 leak rom already has busybox, but I might be wrong) to be able to flash a new rom. P.s. make sure when you flash a rom it is 4.4.2 based and that it is done in the stock rom slot and make sure you do a factory reset wipe from within safe strap before flashing the new rom.
Sent from my baja kit kat SM-N900V using XDA app
Hello all, I posted a similar topic a few days back, and cannot seem to find it. I fear it was deleted, but could be wrong. I only looked back a few pages in the history.
My problems have multiplied since that posting. I have nc4, when I bought my phone it was on there. Used towelroot and was able to root, download safestrap 3.75 and was able to add/delete slots, attempted to use hyperdrive, experienced a lot of weird things like my SMS would randomly not send, battery life was not spectacular,and just other misc things. IT seemed like I might have used a rom that could not be used properly for nc4. I then tried bajarom, which completely does not work for my phone, probably because it's nc2 and I didn't realize that?? Tried jellybeanz or whatever the exact name was, my phone won't even boot, says it successfully installed but sticks on the black screen.
Somehow over the past few days I managed to wipe my stock so I do not have the stock, thus I cannot go back.
I am sure I can find or maybe be directed to the stock firmware and reflash it.
I am not sure if it's possible but I'd really love to be able to get nc2, or if someone more knowledgable than myself could point out a solution for me, I would like to have a custom rom if theres one that would work properly on my phone.
Another confusion I have, with the nc4, am I able to use odin to flash a different radio, should I even bother? I would sincerely appreciate someone who would help clear some of this up for me, I'm pretty novice as you can see. Thanks in advance.
update
I guess my question is unclear. I really can use some help if anyone would be so obliged.
I am trying to use ADB to push the file over, it says access denied, I was previously rooted and verified as much. My issue is I need a way to send the roms over to my SD or my regular phone internal mem so I can at least load a rom. Currently my phone is bricked and I am just getting very upset, I really could use someone to give me a bit of guidance.
I opened the cmd with admin and it's still saying access denied. IS there a way to force the phone to open as a media device via cmd? That way I can edit sd card info and push on there what needs to go?
I am currently trying to find a way to get hyperdrive, or another rom over.
I have beanstowns rom on there, it appears as .zip yet when I try to install from safestrap I end up exploring the directory, as opposed to just being an option I can choose.
Baja is the same way, both are still on my sd, yet for whatever reason I cannot select them to install them.
Hope is not lost.
I think your initial problem was that you tried using rom slots. It specifies in the Safestrap OP that rom slots are only supported on NC2 bootloader. Since you are on the NC4 bootloader you cannot go backwards, however you can flash the NC2 kernel if you want to run a custom rom, you simply need to use the stock slot alone.
Since I know very little about ADB & Terminal CMD, I will try to give you directions to get up and running the way I know how.
First you'll need to reflash the stock NC4 tar via odin and reroot. Files can be found here.
Since you've flashed a couple different roms that have probably messed with the system settings I would do a factory reset before rerooting.
After you are up, running and rooted, follow the instructions here to get on the NC2 kernel.
Once you've completed these steps you will be on the NC4 bootloader with the NC2 kernel and be able to flash a custom rom in the stock rom slot. Only a NC2+ rom will function so make sure it is based on NC2/NC4 (i.e. jelly 'beans' will not run on NC2+ firmware as it is based on MJE).
kinstre11 said:
Hope is not lost.
I think your initial problem was that you tried using rom slots. It specifies in the Safestrap OP that rom slots are only supported on NC2 bootloader. Since you are on the NC4 bootloader you cannot go backwards, however you can flash the NC2 kernel if you want to run a custom rom, you simply need to use the stock slot alone.
Since I know very little about ADB & Terminal CMD, I will try to give you directions to get up and running the way I know how.
First you'll need to reflash the stock NC4 tar via odin and reroot. Files can be found here.
Since you've flashed a couple different roms that have probably messed with the system settings I would do a factory reset before rerooting.
After you are up, running and rooted, follow the instructions here to get on the NC2 kernel.
Once you've completed these steps you will be on the NC4 bootloader with the NC2 kernel and be able to flash a custom rom in the stock rom slot. Only a NC2+ rom will function so make sure it is based on NC2/NC4 (i.e. jelly 'beans' will not run on NC2+ firmware as it is based on MJE).
Click to expand...
Click to collapse
firstly, thank you so much for the reply.
I did flash nc2 kernal, but was confused when I still saw nc4 in the about section. I flashed with odin NC2_modem_kk.tar and nc2kernel.tar.
The issue I was having is with hyperdrive, and baja I had some serious issues, so I assumed it was because I was using them incorrectly, ie didn't install one of the above files correctly, or did something else wrong in the process. Just for example, with hyperdrive, my sms would just stop sending/receiving/ double sending. My sim card was not being recognized. And a whole lot of other issues.. So I kept messing around and now im at a point where nothing boots up, I cannot reflash, and I'm just stuck.
I will follow your link and attempt to do as you said, will wipe, and then will try again.
deindichter said:
firstly, thank you so much for the reply.
I did flash nc2 kernal, but was confused when I still saw nc4 in the about section. I flashed with odin NC2_modem_kk.tar and nc2kernel.tar.
The issue I was having is with hyperdrive, and baja I had some serious issues, so I assumed it was because I was using them incorrectly, ie didn't install one of the above files correctly, or did something else wrong in the process. Just for example, with hyperdrive, my sms would just stop sending/receiving/ double sending. My sim card was not being recognized. And a whole lot of other issues.. So I kept messing around and now im at a point where nothing boots up, I cannot reflash, and I'm just stuck.
I will follow your link and attempt to do as you said, will wipe, and then will try again.
Click to expand...
Click to collapse
Alright, I applied to nc4 and did a factory reset, made sure all my slots were deleted (had 2). Then factory reset and rebooted, saw safestrap, pressed continue, and i'm looking at a blank screen now as though there is nothing to boot to. I was under the impression factory reset would undo all and it has not.
Did I do something wrong, or am I missing something?
deindichter said:
Alright, I applied to nc4 and did a factory reset, made sure all my slots were deleted (had 2). Then factory reset and rebooted, saw safestrap, pressed continue, and i'm looking at a blank screen now as though there is nothing to boot to. I was under the impression factory reset would undo all and it has not.
Did I do something wrong, or am I missing something?
Click to expand...
Click to collapse
Did you already boot into download mode and flash the correct files through Odin? If so that should set your phone back to stock. Then you would have to re root.
fsolares said:
Did you already boot into download mode and flash the correct files through Odin? If so that should set your phone back to stock. Then you would have to re root.
Click to expand...
Click to collapse
I did and it did not boot me back into stock. I then found http://forum.xda-developers.com/showthread.php?t=1922461which led me to download the files directly from samsung.
After downloading the official partition table/ modem/ kernal from the verizon website I finally have this back to stock. LOL. wow. Thank you very much for helping, and working with me on this.
deindichter said:
After downloading the official partition table/ modem/ kernal from the verizon website I finally have this back to stock. LOL. wow. Thank you very much for helping, and working with me on this.
Click to expand...
Click to collapse
can u post the link from where u got the official partition table/modem/kernel on verizon website...
deindichter said:
After downloading the official partition table/ modem/ kernal from the verizon website I finally have this back to stock. LOL. wow. Thank you very much for helping, and working with me on this.
Click to expand...
Click to collapse
So are you good to go now?
moin786 said:
can u post the link from where u got the official partition table/modem/kernel on verizon website...
Click to expand...
Click to collapse
could you post where you found all this since im trying to get my phone back to stock.
Paulrybicki83 said:
could you post where you found all this since im trying to get my phone back to stock.
Click to expand...
Click to collapse
Seriously, just Google for the Samsung official firmware. It's on their site. Not Verizon.
Greetings,
I need some help. I purchased OneClickRoot for my Verizon S5. Everything went swimmingly right up until it didn't. I got root after several hours with the oneclick tech team. he gave me instructions on how to flash a ROM, but left out the apparently important step where I should have skipped the signature verification. So I had SafeStrap, wiped everything and tried to flash an unsigned ROM. now the phone is dead wit no OS and seemingly no ability to get back to safestrap. Should I just toss this phone in the rubbish and buy a new one or can it be saved? When I boot to recovery, it is Android recovery and it keeps failing on the verification.
All advice is welcome.
Doug M.
dwmackay said:
Greetings,
I need some help. I purchased OneClickRoot for my Verizon S5. Everything went swimmingly right up until it didn't. I got root after several hours with the oneclick tech team. he gave me instructions on how to flash a ROM, but left out the apparently important step where I should have skipped the signature verification. So I had SafeStrap, wiped everything and tried to flash an unsigned ROM. now the phone is dead wit no OS and seemingly no ability to get back to safestrap. Should I just toss this phone in the rubbish and buy a new one or can it be saved? When I boot to recovery, it is Android recovery and it keeps failing on the verification.
All advice is welcome.
Doug M.
Click to expand...
Click to collapse
I'm unfamiliar with Verizon variants, but have you tried using Odin to flash the original stock?
https://forum.xda-developers.com/showthread.php?t=2784880
Sent from my Samsung SM-G900I using XDA Labs
Yea dude as long as you can get into download mode (or Odin mode whatever you feel like calling it) you're fine just flash whatever version you feel like being on and I would follow these instructions for root and ROMs and possible bootloader unlock since it's Verizon https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
So Close!!
Thanks for the help. I followed this guide ( https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529) and got it back; ...sort-of.
In Step 13, I used the 6.0 firmware.
In Step 14 I used the "latest stock rooted Lollipop Rom" that was recommended.
I have what appears to be a rooted 5.0 factory rom installed. However, when booting, I get process stopped errors for the first 2 minutes. Maybe 15 or 20 of them. After that, they stop.
Current Problems:
1) the radios are dead. Wi-Fi will not turn on and it does not know that my SIM card is installed
2) when the screen times-out I have to pull the battery to get it back.
3) All the error messages (android.process.media)
4) It does not see the SD card
Questions:
A) Can you help me fix the radio problems?
B) Once I get the radios working again, can I flash any G900V ROM with safestrap and it will likely solve 2, 3 &4?
C) Are the custom roms on 6.0 and higher rooted? I was looking at this one (https://forum.xda-developers.com/galaxy-s5/unified-development/rom-cosmic-os-3-1-t3553838)
Thanks for any assistance you can provide.
Idk if i can help bt i can try haha Well first thing first it sounds like you used marshmallow firmware but then flashed a lollipop ROM which yes it will boot up bt stuff like your radio and GPS, etc won't work so first thing is first i would say is do a complete wipe and get your self back to stock through Odin and get everything working first before worrying about ROMs then I have to ask is what is what is your emmc are you 15 (bootloader unlock and can easily root 6.0.1 or higher) or emmc 11 (can only root 5.0)