Related
i had root per odin + cwm + x-note v5.1 rom. had mj1, but knoxed it 01.
since i wanted to return the device, i wanted to get the original branded firmware. instead of reading a lot of pages (took me quite some
reading to flash a different rom as a noob), i thought i take a short cut and went ahead and pressed reset on the regular settings menu
(thinking, that somewhere on the device the original fw should be stored). i wiped everything off. so after that, while booting up only the
x-logo appeared and nothing else happend. i had to take the battery away to stop it spinning perpetually. i have no clue, but i suppose i
took root away while erasing everything and that's why i can't start the device or pass the booting process.
so here's my question: how to get root again? how to start the device w/o it beeing in this perpetual x-note 5.1 cross? and where to get
the original fw? how to proceed to get back to the original fw? is it definitely bricked? things are getting over my head and i have till tomorrow to fix this problem.
hadn't made a backup. the only backup i have is an efs backup (14mb file). how do i proceed to get back to a branded firmware ? and where
to get it.
any help is appreciated. thx
zenorth said:
i had root per odin + cwm + x-note v5.1 rom. had mj1, but knoxed it 01.
since i wanted to return the device, i wanted to get the original branded firmware. instead of reading a lot of pages (took me quite some
reading to flash a different rom as a noob), i thought i take a short cut and went ahead and pressed reset on the regular settings menu
(thinking, that somewhere on the device the original fw should be stored). i wiped everything off. so after that, while booting up only the
x-logo appeared and nothing else happend. i had to take the battery away to stop it spinning perpetually. i have no clue, but i suppose i
took root away while erasing everything and that's why i can't start the device or pass the booting process.
so here's my question: how to get root again? how to start the device w/o it beeing in this perpetual x-note 5.1 cross? and where to get
the original fw? how to proceed to get back to the original fw? is it definitely bricked? things are getting over my head and i have till tomorrow to fix this problem.
hadn't made a backup. the only backup i have is an efs backup (14mb file). how do i proceed to get back to a branded firmware ? and where
to get it.
any help is appreciated. thx
Click to expand...
Click to collapse
get it from www.sammobile.com
the problem is the download links there are down have a look and see if it works you might be lucky
hi jaythenut,
thanx for your answer, i heard of sammobile. is there another place? and i'm still not aware how to solve my prob> reinstall cwm + the rom
or bypass that and go directly to the other original rom? as of right now, there's just a constant boot. any ideas? in case i would be able
to install a new rom and the device is not bricked, how to unroot after installing the original fw? via supersu? it says permanently
unroot. how permanently is that?
zenorth said:
hi jaythenut,
thanx for your answer, i heard of sammobile. is there another place? and i'm still not aware how to solve my prob> reinstall cwm + the rom
or bypass that and go directly to the other original rom? as of right now, there's just a constant boot. any ideas? in case i would be able
to install a new rom and the device is not bricked, how to unroot after installing the original fw? via supersu? it says permanently
unroot. how permanently is that?
Click to expand...
Click to collapse
It's not permanently unroot you can root it any time you want
Have you got Cwm on the phone if so just flash a new rom if you want stock this one is stock http://forum.xda-developers.com/showthread.php?t=2461929
hi jaythenut, i hit the thx button this time.
i've got the fw now. not via sammobile since they had a rapidgator link and it wasn't free. i went into cwm recovery mode and re-installed the x-note 5.1 rom, so now the device is alive and running. good. now, that i got the branded mj1 fw, do i install it via odin or via cwm recovery? as a zip or extracted? and afterwards, when the fw branded rom is back on, how do i unroot the device? with supersu? and how do i delete the cwm itself as i don't want to leave a trace or obvious trace when i go into the shop and try to return it? thx for any input
Hello all,
I have had my S4 for awhile now and need some help. When I first received it, I did some reading, rooted, did something that removed a triangle or a padlock, can't remember which one and made sure the AT&T software update was unable to run. At the time, custom recovery wasn't possible so I stopped there. So here I am now, rooted with MDL and I have no idea where to go from here to get the latest 4.3, although apparently I have the holy grail of firmware.
I've read as much as I possibly can, subscribed to the forums, GOOGLED, SEARCHED, RTFM and waited for someone else to come along and ask the very same question. Some did but those threads never really gave me the info I need to SAFELY flash my phone up to 4.3. So what do I do? All I need is some guidance, I follow directions well. Teach me! Please and Thank You
Doug
DO NOT UPDATE YOUR FIRMWARE IF YOU STILL HAVE MDL. ....U JUST NEED INSTALL CWM RECOVERY OR TWRP RECOVERY. .... AND THEN INSTALL CUSTOM 4.3 ROM. .... EVEN 4.4 KITKAT ROM. ..... BUT IF U DO UPDATE TO NEWEST MK2 FIRMWARE THEN U WOULD LOSE THE PRIVILEGE OF MDL..... WHICH IS RARE. ..... GOODLUCK
Swyped from MK2 Deadly Venom SS
Right! One of the things I have learned is that I want to keep the MDL baseband. What I really want are all the improvements that 4.3 or 4.4 offer. Also, I'm hoping my Pebble and my S4 play better together than they do now.
Do I just pick a recovery? Are they the same? Guess I need to read some more.
Sent from somewhere...
DRRies said:
Right! One of the things I have learned is that I want to keep the MDL baseband. What I really want are all the improvements that 4.3 or 4.4 offer. Also, I'm hoping my Pebble and my S4 play better together than they do now.
Do I just pick a recovery? Are they the same? Guess I need to read some more.
Sent from somewhere...
Click to expand...
Click to collapse
This one click tool is pretty awesome. http://forum.xda-developers.com/showthread.php?t=2297033... .. Super easy as 1.2.3.... and have everything u need. ......root....CWM or TWRP recovery and even flash to stock via Odin. ... Hope this work for u and hit THANK button If someone helped you. ...
Swyped from MK2 Deadly Venom SS
DRRies said:
Hello all,
I have had my S4 for awhile now and need some help. When I first received it, I did some reading, rooted, did something that removed a triangle or a padlock, can't remember which one and made sure the AT&T software update was unable to run. At the time, custom recovery wasn't possible so I stopped there. So here I am now, rooted with MDL and I have no idea where to go from here to get the latest 4.3, although apparently I have the holy grail of firmware.
I've read as much as I possibly can, subscribed to the forums, GOOGLED, SEARCHED, RTFM and waited for someone else to come along and ask the very same question. Some did but those threads never really gave me the info I need to SAFELY flash my phone up to 4.3. So what do I do? All I need is some guidance, I follow directions well. Teach me! Please and Thank You
Doug
Click to expand...
Click to collapse
As ted said, upgrading is bad. You can change modems and such to the MK2 baseband, it's the bootloader that's the issue. As long as you don't try to take any OTA's and don't ODIN any newer version you'll be fine. If you want to run the official AT&T 4.3, your closest bet is StockUp MK2 and the rebloat addon. Otherwise, you can choose either CWM or TWRP and flash away as long as you remember to use the loki patch for things that aren't patched already.
I've read the info at the link you provided before and wondered if I'm already rooted, what would happen? Is that safe to use if currently rooted?
Also, since I'm currently on MDL, would a factory reset return me to a fresh MDL or would it force me to update to current software?
Start here. http://forum.xda-developers.com/showthread.php?p=42320391
Ok so I strated with the thread posted. I now have TWRP installed, nandroid backed up and all sorts of zips on my ext card. Also made Kies backups. My first ROM flash, Stockup_MK2 went fine until reboot and I had no mobile data or cell signal. What did i do wrong? I immediately did a restore from the nandroid backup to return to where was before.
DRRies said:
Ok so I strated with the thread posted. I now have TWRP installed, nandroid backed up and all sorts of zips on my ext card. Also made Kies backups. My first ROM flash, Stockup_MK2 went fine until reboot and I had no mobile data or cell signal. What did i do wrong? I immediately did a restore from the nandroid backup to return to where was before.
Click to expand...
Click to collapse
Did you wipe before installing the rom? Just use the slider toggle in wipe. If so, check that the apn is setup correctly.
DRRies said:
Ok so I strated with the thread posted. I now have TWRP installed, nandroid backed up and all sorts of zips on my ext card. Also made Kies backups. My first ROM flash, Stockup_MK2 went fine until reboot and I had no mobile data or cell signal. What did i do wrong? I immediately did a restore from the nandroid backup to return to where was before.
Click to expand...
Click to collapse
In stead of a stcok MK2 rom might I suggest a fairly stock but cleaned up rom like MDOB or any other close to stock rom's
http://forum.xda-developers.com/showthread.php?t=2280556
Not advocating any one person but he does good stuff and it based on the actual AT&T update to 4.3.. Make sure you do as the guy above me stated and do the simple swipe to wipe in TWRP
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.
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.