Idell
cool nice to see no one has gave up on this yet hopefully you can get some devs to chime in on this
Thank you for continuing to work on this and hopefully someone will step up and assist. This is my first locked phone.
Sent from my SM-N900V using XDA Premium 4 mobile app
Nice! good work, hopefully someone like hash can chime in. I love to see devices that are locked down get hacked into freedom. F U Samsung!
dhufford81 said:
Nice! good work, hopefully someone like hash can chime in. I love to see devices that are locked down get hacked into freedom. F U Samsung!
Click to expand...
Click to collapse
no its FU verizon
krazy_smokezalot said:
no its FU verizon
Click to expand...
Click to collapse
Exactly! T-mobile and Sprint are unlocked.
Friend
* not flood.
* communicate only topic
Has anyone contacted Hashcode on this
I wonder perhaps if there is some kind of security check on at least MJ9 or even MJE retail that verifies the kernel in use which is causing the issue. Especially since it's seeing its the dev edition kernel. Just guessing here. This is huge progress however and hopefully we'll be able to get it unlocked soon. Way to go hobbit19!
AngryManMLS said:
I wonder perhaps if there is some kind of security check on at least MJ9 or even MJE retail that verifies the kernel in use which is causing the issue. Especially since it's seeing its the dev edition kernel. Just guessing here. This is huge progress however and hopefully we'll be able to get it unlocked soon. Way to go hobbit19!
Click to expand...
Click to collapse
Tomorrow I will try to flash the firmware engineering
http://forum.xda-developers.com/showthread.php?t=2567394
and try to apply it loki
http://forum.xda-developers.com/showthread.php?t=2292157
although it seems to me that the hole uses Loki already fixed there
Hopefully another dev can help you out. This would be amazing progress and would finally allow us to have the phone we deserve, I really wish VZW would knock this crap off. Looks like I'll be holding out on upgrading and rerooting MJE. I'll just hang out on MI9 and see where this goes.
I believe
* while those who have older versions of the firmware is worth staying on them
because I could not sew dev bootloaders where there was the latest firmware.
* possible for them will then flash dev bootloaders from 4.4 dev firmware
* which we do not have.
hobbit19 said:
Hello everyone .
I have long been engaged in an attempt to break the bootloader and it seems to me found a way .
Recently I got the retail version of the note 3 with the old firmware MI9.
And I was able to correctly flash it with testbit
, then dev version bootloaders
https://dl.dropboxusercontent.com/u/59757245/Step2_DevEdition_Bootchain.tar.md5
https://dl.dropboxusercontent.com/u/59757245/Step1_TestBoot.tar.md5
that I gave one a developer xda and at the end of firmware MJE for dev version
( before on recent firmware on another note3 it was not possible to flash dev bootloader ) .
At the same time I did not get any errors and phone worked .
But when trying to flash a custom recovery through Odin - it produce errors .
I did root and installed Safestrap Recovery , they managed to flash recovery and modifying kernel and no errors. But after restarting the phone won't work with them pointing me to the kernel error .
But I have no problem I can roll back to dev version of the firmware and the phone works . I believe that retail version has some other protection, than those in boot.
And I would like to ask the advice to other developers that I can do now to try to break other protection from boot and firmware.
Click to expand...
Click to collapse
You should reach out to Designgears, and Hashcode. Although Designgears no longer has an note 3, he did a lot of work trying to break the bootloader, if anything he can point you to the right direction. Hashcode has a note 3 (retail).
Everyone else please keep this thread clean, I know you have good intentions but it makes it very hard to read through 100's of post.
2swizzle said:
You should reach out to Designgears, and Hashcode. Although Designgears no longer has an note 3, he did a lot of work trying to break the bootloader, if anything he can point you into the right direction. Hashcode has a note 3 (retail).
Everyone else please keep this thread clean, I know you have good intentions but it makes it very hard to read through 100's of threads.
Click to expand...
Click to collapse
Actually..... Hashcode sold his retail Note 3 on swappa, and now has a Dev Edition Note 3 :good:
2swizzle said:
You should reach out to Designgears, and Hashcode. Although Designgears no longer has an note 3, he did a lot of work trying to break the bootloader, if anything he can point you into the right direction. Hashcode has a note 3 (retail).
Everyone else please keep this thread clean, I know you have good intentions but it makes it very hard to read through 100's of threads.
Click to expand...
Click to collapse
He was able to flash the leaked engineering firmware. It was only a debugging bootloader. Although if you are still on MI9 I have some ideas. The engineering aboot I believe did not have security checks, which means Loki may be possible. I'm going to try to patch the old aboot and see if it works. Even if it did, we have no way of getting back to MI9 at the moment.
Sent from my SM-N900V using Tapatalk
you MI9?
you're kind of wrote in another topic that pierced the new firmware
* and you are unable to flash dev bootloader
Hello @hobbit19,
I want to sort of walk through your process and clarify with questions:
hobbit19 said:
And I was able to correctly flash it with testbit
Click to expand...
Click to collapse
1. Using this file https://dl.dropboxusercontent.com/u/59757245/Step1_TestBoot.tar.md5 (which contains engineering versions of sbl1, aboot, tz. rpm and sdi partitions) you were able to set testbit? Can you go into download mode and print out the values shown there for me?
hobbit19 said:
, then dev version bootloaders
https://dl.dropboxusercontent.com/u/59757245/Step2_DevEdition_Bootchain.tar.md5
Click to expand...
Click to collapse
2. On step 2 here, you are flashing the dev ed. partitions which match up to the previous files + NON-HLOS.bin (for the firmware partition).
hobbit19 said:
I did root and installed Safestrap Recovery , they managed to flash recovery and modifying kernel and no errors. But after restarting the phone won't work with them pointing me to the kernel error .
Click to expand...
Click to collapse
And for this last bit: Which recovery file did you try? I believe there's nothing to stop you from actually flashing the partitions, but the signature checks will fail during the next boot (as you've seen) Did you try booting into recovery mode? (Like don't flash boot.img yet)
Yes, I now can flash testbit and phone starts with it.
You want what flashed boot writes?
Yes, I understand in structure of firmware and understand how it works. I flashed MJE_insecure_Kernel.zip http://d-h.st/AR6
and http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltevzw/philz_touch_6.08.9-hltevzw.zip
After flash and phone won't start I roll back to full dev firmware.
Tomorrow I can try to re-flash and try to open recovery.
Also I have idea - try to flash old dev build what exist in other thread and use loki exploit on it.
But I afraid that flash of dev build may brick phone and require jtag.
Now in boot mode I see
odin mode
POroduct Name SN-900V
Current binary Samsung Official
System status Official
KNOX Kernel Lock 0x0
knox warranty void 0x1
qualcomm secure boot Enable csb
RP swrev s1 , t1 ,r1, a1, p1
Write protection Enable
You have dev version? Can you show what your bootloader says?
Dev Ed. Download Mode:
ODIN MODE
PRODUCT NAME: SM-N900V
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
WRITE PROTECTION: Enable
MODE: Developer
(NOTE: I'm currently testing / debugging CM11 which explains the "Custom" items)
Related
A few of us purchased the Dev Edition and it appears there are some things where clarification is required concerning the three "R's":
1. Rooting: I understand this wonderful rooting exercise is successful: http://forum.xda-developers.com/showthread.php?t=2290798. I would think since the Dev Edition is unlocked, an owner would only utilize Step 3, and NOT the kernel exchange section. Correct?
2. ROMing: Since the ROMS were created using the Loki enabled system, does this affect ROMing the Dev Edition since it is already unlocked? What does a user need to do? Or, does it not matter? Do the Loki enabled ROMS work on a Dev Edition?
3. Recovery: Again, it appears TWRP and CWM are Loki adjusted, so does this affect recovery on the Dev Edition and restoring? Also, is there a Stock Factory Image which will NOT turn the phone back to a locked bootloader? Or, does the one which exists OK to use?
I only ask these questions since a few of us are somewhat confused.
Thanking you in advance!
markwebb said:
A few of us purchased the Dev Edition and it appears there are some things where clarification is required concerning the three "R's":
Click to expand...
Click to collapse
I've been thinking about buying the Verizon S4 Dev Edition phone, but have been hesitant due to not knowing how simple it would be to root. Is it as simple as just running MotoChopper? Or is there a better way?
Being that the bootloader on this phone is truly unlocked, can you install the current versions of CWM or TWRP that are LOKI enabled, and will it work on this phone? I haven't seen any compiled versions that were non-loki (standard).
Same question goes for kernels too.
The first batch of Dev phones sold out in less than 24 hours, so I'd expect some of the people that have them would start posting their experience with it here soon. At least, I hope so!
Root failed when just applying the Motochopper step! It says it installs correctly and then it reboots and SuperSu is installed and then I checked for an upgrade which it took. However, it says it cannot install binary, there is a problem and closes.
I uninstalled SuperSu and tried a few times to root again but it doesn't work.
My phone states:
Kernel Version: 3.4.0-562219 dated May 15th
Build Number: JDQ439.I545OYUAMDK
Baseband: I545OYUAMDK
Must be something we can do....
markwebb said:
Root failed when just applying the Motochopper step! It says it installs correctly and then it reboots and SuperSu is installed and then I checked for an upgrade which it took. However, it says it cannot install binary, there is a problem and closes.
I uninstalled SuperSu and tried a few times to root again but it doesn't work.
My phone states:
Kernel Version: 3.4.0-562219 dated May 15th
Build Number: JDQ439.I545OYUAMDK
Baseband: I545OYUAMDK
Must be something we can do....
Click to expand...
Click to collapse
I wonder if step 2 and 4 are still required? (swapping kernels)
Even though the bootloader is unlocked, the kernel may still have root blocked?
guyd said:
I wonder if step 2 and 4 are still required? (swapping kernels)
Even though the bootloader is unlocked, the kernel may still have root blocked?
Click to expand...
Click to collapse
It sounds like it. But wouldn't swapping kernels render the Dev Edition to a retail version? Kinda defeats the purpose, no? Or, am I missing something?
The question is: Does the Dev Edition have the same kernel as the Retail Edition? If so, then it would make sense to swap kernels. I think we need the devs to weigh in.
markwebb said:
It sounds like it. But wouldn't swapping kernels render the Dev Edition to a retail version? Kinda defeats the purpose, no? Or, am I missing something?
The question is: Does the Dev Edition have the same kernel as the Retail Edition? If so, then it would make sense to swap kernels. I think we need the devs to weigh in.
Click to expand...
Click to collapse
From what I've been able to gather, Samsung has put in place a SetUID restriction on the stock release kernel via CONFIG_SEC_RESTRICT_SETUID. Apparently the D2 prerelease kernel doesn't have this restriction in place. That seems to be why flashing that is required prior to using MotoChopper to gain root. What I can't figure out is why you can flash the release DK afterwards and still keep root?
On the T-Mobile and Sprint S4 they've been able to remove the SetUID restriction on their latest DL release kernel by recompiling the kernel source with the SetUID restriction commented out
Thanks for the thoughts and analysis. Hopefully someone will find an alternate
root method for the dev edition since it has been available for a week and it sold out in less than twenty four hours, somebody with know how must have purchased it and is tinkering as we speak.
I would hate to render it back to a retail version otherwise.
Sent from my SCH-I545 using xda app-developers app
markwebb said:
Thanks for the thoughts and analysis. Hopefully someone will find an alternate
root method for the dev edition since it has been available for a week and it sold out in less than twenty four hours, somebody with know how must have purchased it and is tinkering as we speak.
I would hate to render it back to a retail version otherwise.
Click to expand...
Click to collapse
I think I may have found a solution. With the Developer Edition we have an unlocked bootloader, so there is no need to use loki. I was looking for a non-loki patched (normal) recovery that could be flashed in Odin. I think I found one here http://forum.xda-developers.com/showthread.php?t=2322675. Look for the "Latest version can be found here" link, not the "loki patched" link. The filename is : Philz_touch_5.06.6-jfltevzw.tar.md5
If this works like it did in previous unlocked Samsung devices, then we should be able to flash the custom recovery in Odin, and then boot into recovery afterwards to flash SuperUser. From there, we're rooted.
If I had my dev edition S4, I'd test it out myself. But I'm still waiting for them to get back in stock!
Great..am somewhat game to try. Well report back. Thanks!!
Sent from my SCH-I545 using xda app-developers app
IT WORKED...somewhat!!! When it boots, I now get Samsung Custom and unlocked symbol and I am in Philz Touch Recovery backing up the image.
As expected, the backup image is 4GB+ (saved on external card of course).
However, I can't update binary for root.
You, sir, are a genius...thanks so much..almost there!
Not really rooted though. Can't update binary and when in Root Explorer I can explore most folders but Root checker says I am not rooted.
Now what do I do? LOL
markwebb said:
IT WORKED...somewhat!!! When it boots, I nLet me know how it goes ow get Samsung Custom and unlocked symbol and I am in Philz Touch Recovery backing up the image.
As expected, the backup image is 4GB+ (saved on external card of course).
However, I can't update binary for root.
You, sir, are a genius...thanks so much..almost there!
Click to expand...
Click to collapse
Did you flash SuperSU from recovery via the zip file? (from this thread) http://forum.xda-developers.com/showthread.php?t=1538053. Look for the UPDATE-SuperSU-v1.41.zip file in the download section.
This should give you root after flashing in recovery! If you can't get root in a root app after flashing this file, then the kernel is blocking root. You can thank Samsung for adding that in the DK kernel.
You can easily work around this by flashing a custom kernel!
Let me know how it goes.
guyd said:
Did you flash SuperSU from recovery via the zip file? (from this thread) http://forum.xda-developers.com/showthread.php?t=1538053. Look for the UPDATE-SuperSU-v1.41.zip file in the download section.
This should give you root after flashing in recovery! If you can't get root in a root app after flashing this file, then the kernel is blocking root. You can thank Samsung for adding that in the DK kernel.
You can easily work around this by flashing a custom kernel!
Let me know how it goes.
Click to expand...
Click to collapse
BINGO!!!!!!!!!!!! THANKS!!!!
Now we need a thread/tutorial started for the Dev Edition Owners on how to do this!!
markwebb said:
BINGO!!!!!!!!!!!! THANKS!!!!
Now we need a thread/tutorial started for the Dev Edition Owners on how to do this!!
Click to expand...
Click to collapse
Do you now have root with the stock DK kernel, or did you flash a custom kernel?
Root with stock kernel.
Sent from my SCH-I545 using xda app-developers app
markwebb said:
Root with stock kernel.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Now I know exactly what I need to do when I get mine!
Thanks for testing it out on your device
guyd said:
Now I know exactly what I need to do when I get mine!
Thanks for testing it out on your device
Click to expand...
Click to collapse
You are welcome. Now, the next question: Can we flash the ROM's which are Loki adjusted?
markwebb said:
You are welcome. Now, the next question: Can we flash the ROM's which are Loki adjusted?
Click to expand...
Click to collapse
Good question. From what I have seen thus far, the recovery is the piece that has to be Loki adjusted to allow it to be flashed on a locked bootloader. I don't think the ROM cares one way or the other. The only thing I still have questions about is the kernel. Is the kernel in the Developer Edition different than the carrier version?
guyd said:
Good question. The only thing I still have questions about is the kernel. Is the kernel in the Developer Edition different than the carrier version?
Click to expand...
Click to collapse
How do I/we find out? If you have any suggestions, let me know. I have gone this far and sweated.
markwebb said:
How do I/we find out? If you have any suggestions, let me know. I have gone this far and sweated.
Click to expand...
Click to collapse
If we could get an MD5 of the Developer DK kernel (boot.img), and compare it to the MD5 of a completely stock DK kernel (boot.img). Or maybe compare the kernel build numbers? I dunno, just throwing some ideas out.
As the title states, I'm new to the S4, but not to flashing. I had the Fascinate (S1) for the past 3 years and did EVERYTHING with it! I picked up the S4 yesterday and have some questions.
I saw Shane's (DroidModderX) video on how to Root the S4 (ME7) and also his video on how to LOKI bootloader hack, but this all warns against not working after the l latest OTA. When I got the phone, the VZW tech made sure my phone was totally updated and so I'm sure I'm in that stuck area.
I'm working on backing up my SD card before I try formatting to extFAT, so I haven't done anything yet. But do I have any options available to me in terms of rooting/custom ROMs?
Not sure what the relevant information is for the S4, but I've attached my phone info.
You can root only currently. Hopefully SafeStrap wil be available soon to give you other options.
Sent from my SCH-I545 using xda app-developers app
Thanks for the news. What, exactly, is SafeStrap? A new way to flash customs, a recovery method or something altogether new to me?
adamklo said:
Thanks for the news. What, exactly, is SafeStrap? A new way to flash customs, a recovery method or something altogether new to me?
Click to expand...
Click to collapse
Safestrap is a very similar way to flash roms as phones that have UNLOCKED bootloaders. The main difference is that the bootloader is locked currently on S4. safestrap doesnt go around bootloader but it does give people the option to flash so custom roms, but you dont get the wide variety as you would on a unlocked bootloader phone.
Also I don't mean to ruin the fun, but the bootloader each year becomes tougher. The developer that did the LOKI mentioned once on a post that this would probably one of the last option he will be able to find a way to unlock bootloaders.
Mod Edit: You have a very probable brick if you successfully flash these ENG images. Dont do it.
These are the files that were leaked to me for the Verizon Note 3, I don't have anymore Notes, maybe someone else can do something with these.
ALL_N900VVREBMHV_N900VVZWBMHV_1554921_REV03_eng_mid_noship_MULTI_CERT.tar.7z 1.45 GB
https://mega.co.nz/#!H4pAGb5B!awVu4SGnvHRt19g19gxfh0NHzR0MeGG_b0JLzoHYuWg
ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.7z 1.27 GB
https://mega.co.nz/#!3gAwQZgL!BL-kZkfWn5HpiwES36kjBk8DCsw8IozG03dTQ_-9_VA
BOOTLOADER_HLTE_VZW_TestBit_1525763_REV03_user_mid_noship_MULTI_CERT.7z 957 KB
These allow you to down grade the bootloader
https://mega.co.nz/#!7wJzyCYD!Zo3Hv2EfQFPcPiCrMvfgtC_mT0Y98UCwz35DZXQrSP0
COMBINATION_N900VVREAMG3_N900VVZWAMG3_1031711_REV03_eng_mid_noship.tar.7z 1.62 GB
These seem to only work on dev devices, never got any of it working on retail
https://mega.co.nz/#!Wkx3lS4K!SEbUulbz2HAVmL0NJAZofluN4pxGlIjlDyyoqBagEo8
Thanks again!
Okay:
Flashing bootloader through ODIN failed, I knew this was going to happen, just because it's a user release and a downgrade, just wanted to try. Recovered soft-brick to all my data intact by flashing MJ7 radio. Going to try the first engineering build next.
Nice thanks.
Sent from my SM-N900V using Tapatalk
lets hope the bootloader download will save us in the future
OP,
Thank you for these!
2swizzle said:
lets hope the bootloader download will save us in the future
Click to expand...
Click to collapse
I almost wonder in a way if this could be used towards some kind of bootloader unlock method.
AngryManMLS said:
I almost wonder in a way if this could be used towards some kind of bootloader unlock method.
Click to expand...
Click to collapse
That would be awesome. Enough to downgrade to be able to use loki maybe. If it's possible .
Sent from my SM-N900V using Tapatalk
This could be a breakthrough with the right person or people working on it.
The aboot from the unsigned engineering build is significantly smaller than the rest... I wonder... Not to mention the SM-N900 boot recovery guide leak from Samsung. If we could get an old sboot.bin we might have a shot.
Sent from my SM-N900V using Tapatalk
ryanbg said:
The aboot from the unsigned engineering build is significantly smaller than the rest... I wonder... Not to mention the SM-N900 boot recovery guide leak from Samsung. If we could get an old sboot.bin we might have a shot.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
blahh.. i wish you guys the best of luck. However, I am sick of verizon locking down our dang devices. I'm taking my 4 lines over to sprint today where i can be worry free . With that said I have a new shinny note 3 (retail) and a note 2 and galaxy nexus for sale
kwkw480 said:
blahh.. i wish you guys the best of luck. However, I am sick of verizon locking down our dang devices. I'm taking my 4 lines over to sprint today where i can be worry free . With that said I have a new shinny note 3 (retail) and a note 2 and galaxy nexus for sale
Click to expand...
Click to collapse
enjoy your .5mb download speeds hahaha jk
kwkw480 said:
blahh.. i wish you guys the best of luck. However, I am sick of verizon locking down our dang devices. I'm taking my 4 lines over to sprint today where i can be worry free . With that said I have a new shinny note 3 (retail) and a note 2 and galaxy nexus for sale
Click to expand...
Click to collapse
Its not worth bring on a Sprint connection, that's junk man. Been there done that. TMobile, Sprint and ATT are all second seat to VZW in regards to service. Besides, what do you gain from getting an unlocked bootloader? AOSP? Junk too. Move to AOSP and not only will you have a phone on a junky network, you will have a less capable device in terms of reception. Been there done that.
These are ENG builds, not developer builds. The best you would get from flashing the bootloaderes would be more detailed information during the boot process, and it would not unlock your device's bootloader. Worst case, you will end up with a brick since these predate the SBLs you are running now, and a fuse has been blown to prevent the older bootloaders from functioning.
My word of advice is, unless you like bricking phones leave them alone.
I know it.
* therefore asked the firmware version from dev
with engineering Bootloader phone is not start...
but it does not die and then be impeccably renovated.
jcase said:
These are ENG builds, not developer builds. The best you would get from flashing the bootloaderes would be more detailed information during the boot process, and it would not unlock your device's bootloader. Worst case, you will end up with a brick since these predate the SBLs you are running now, and a fuse has been blown to prevent the older bootloaders from functioning.
My word of advice is, unless you like bricking phones leave them alone.
Click to expand...
Click to collapse
I was looking for an older sboot so I could attempt the leaked SM-N900 SD Boot Recovery process to see if I could downgrade my radio (step 14 in leaked article. Have you seen the leaked documentation? I could avoid the SW rev error and possibly have a loki-able aboot from an older pre-patch bootloader, which I might have found. I'm not sure though.
Sent from my SM-N900V using Tapatalk
ryanbg said:
I was looking for an older sboot so I could attempt the leaked SM-N900 SD Boot Recovery process to see if I could downgrade my radio (step 14 in leaked article. Have you seen the leaked documentation? I could avoid the SW rev error and possibly have a loki-able aboot from an older pre-patch bootloader, which I might have found. I'm not sure though.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Link me to the documentation please
jcase said:
Link me to the documentation please
Click to expand...
Click to collapse
I'm at a friends house now. I can't remember where I found it but it was brand new. It's like 13-58 SM-N900 Boot Recovery and released by Samsung Global CS HQ. They revealed the short needed to boot SDCARD mode with the sboot, and the last step is to flash everything back including BP and AP, after you've restored boot process which makes me think it's possible. I'll link you immediately when I'm home. Also it was a mediafire link. I'll keep looking.
Sent from my SM-N900V using Tapatalk
While safestrap is a great accomplishment I hope there are devs here that are not as content to call that a complete victory and manage to follow a crumb trail to an open bootloader.
Here you go
jcase said:
Link me to the documentation please
Click to expand...
Click to collapse
*Fingers crossed* I'm no expert but this pdf looks promising. YAYAY
http://www.mediafire.com/view/jkw1vv95ub8596h/13-58_SM-N900_Boot_Recovery_Guide_rev1.0.pdf
Here are few more things..but for Galaxy Gear
http://www.mediafire.com/view/i3q3yiefvc24ytx/Galaxy_Gear_Boot_Recovery_V01.pptx
http://www.mediafire.com/download/ji397waz5j945qs/SM-V700_USB_Recovery_V0.2.zip
Walter.White said:
*Fingers crossed* I'm no expert but this pdf looks promising. YAYAY
http://www.mediafire.com/view/jkw1vv95ub8596h/13-58_SM-N900_Boot_Recovery_Guide_rev1.0.pdf
Here are few more things..but for Galaxy Gear
http://www.mediafire.com/view/i3q3yiefvc24ytx/Galaxy_Gear_Boot_Recovery_V01.pptx
http://www.mediafire.com/download/ji397waz5j945qs/SM-V700_USB_Recovery_V0.2.zip
Click to expand...
Click to collapse
Confirming first link is the documentation I am referencing.
Sent from my SM-N900V using Tapatalk
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
GlitchMob said:
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
Click to expand...
Click to collapse
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
decaturbob said:
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
Click to expand...
Click to collapse
Okay maybe my understanding on the purpose of unlocking the bootloader is incorrect.
I thought the bootloader has to be unlocked in order to install a custom rom?
On my S3 if the bootloader wasn't unlocked the phone would brick.
Safestrap is a custom recovery so how is that relevant to bootloader? I can't seem to draw the connection.
Thanks!
GlitchMob said:
Okay maybe my understanding on the purpose of unlocking the bootloader is incorrect.
I thought the bootloader has to be unlocked in order to install a custom rom?
On my S3 if the bootloader wasn't unlocked the phone would brick.
Safestrap is a custom recovery so how is that relevant to bootloader? I can't seem to draw the connection.
Thanks!
Click to expand...
Click to collapse
plenty of threads here to read to educate yourself.
S4 bootloader is locked since mdk firmware. MDK had an exploit that Loki process allowed custom recovery
safestrap uses an exploit to work around it so its the only custom recovery for the locked bootloader.
Each subsequent firmware release locks the bootloader and exploits down further. Anyone taking the next round of kit kat OTA's will likely loose root as well.
GlitchMob said:
I'm currently on a Galaxy S3, but I have an S4 coming in on Friday.
I saw a thread for rooting the S4, but do I need to unlock the bootloader like I did in the S3 to install a rom?
Basically, where is the thread that has all the info I need to root, unlock, and install a custom recovery for the S4?
I have one for the S3, but can't find it for the S4.
Click to expand...
Click to collapse
More then likely the device you get will come with the new baseband MJ7 or MK2. You need to check this before you start messing with anything. That said the bootloader is locked up tight and you will be very limited with what you can do with it. You can root, and install safestrap(a custom recovery by Hashcode that bypasses the bootloader). This will allow you to install certain touchwiz based roms but you have to be sure they are compatible with safestrap.
Root for 4.3 baseband:
http://forum.xda-developers.com/showthread.php?t=2565758
Safestrap:
http://forum.xda-developers.com/showthread.php?t=2441441
Both these links are in the android devlopment section. It is very difficult with this device because there are multiple root methods and recovery methods depending on baseband version. If by some chance you get the phone and the baseband is MDK, DO NOT UPDATE!!!! This will allow you to install loki'ed recovery and flash any rom you want. Chances are that won"t happen though. Good luck
decaturbob said:
you cant find thread? How hard did you look? There is a stickie can't be missed in the general section.
BTW, the bootloader is locked for all versions of firmware since mdk.
only option is safetrap.
Click to expand...
Click to collapse
decaturbob said:
plenty of threads here to read to educate yourself.
S4 bootloader is locked since mdk firmware. MDK had an exploit that Loki process allowed custom recovery
safestrap uses an exploit to work around it so its the only custom recovery for the locked bootloader.
Each subsequent firmware release locks the bootloader and exploits down further. Anyone taking the next round of kit kat OTA's will likely loose root as well.
Click to expand...
Click to collapse
I understand that I need to look into it, but the way things are organized is different. I've been on an S3 for almost two years now and the forums in the S4 are just overwhelming with information that is scattered. Here is an example of what I was hoping for when I came to the S4 section.
http://forum.xda-developers.com/showthread.php?t=1762709
onemeila said:
More then likely the device you get will come with the new baseband MJ7 or MK2. You need to check this before you start messing with anything. That said the bootloader is locked up tight and you will be very limited with what you can do with it. You can root, and install safestrap(a custom recovery by Hashcode that bypasses the bootloader). This will allow you to install certain touchwiz based roms but you have to be sure they are compatible with safestrap.
Root for 4.3 baseband:
http://forum.xda-developers.com/showthread.php?t=2565758
Safestrap:
http://forum.xda-developers.com/showthread.php?t=2441441
Both these links are in the android devlopment section. It is very difficult with this device because there are multiple root methods and recovery methods depending on baseband version. If by some chance you get the phone and the baseband is MDK, DO NOT UPDATE!!!! This will allow you to install loki'ed recovery and flash any rom you want. Chances are that won"t happen though. Good luck
Click to expand...
Click to collapse
Thank you. This is the response I was looking for. As you said there are many stipulations with each baseband. This is something I am not used to coming for an S3, which is far simpler to deal with. Thanks again!
GlitchMob said:
Thank you. This is the response I was looking for. As you said there are many stipulations with each baseband. This is something I am not used to coming for an S3, which is far simpler to deal with. Thanks again!
Click to expand...
Click to collapse
The difference isn't in the baseband, it's in the bootloader. You can run a newer baseband than your bootloader, for example, especially if you have the MDK bootloader.
Since you're starting from stock, the baseband and the bootloader revisions are the same and can be found from Settings/More/About phone.
Before you flash anything, please read the what you need to know thread in the General section. Also, there's my thread in this forum.
The S4 is more complicated than the S3 largely because Samsung has really locked it down much more effectively than the S3. Consequently, there's lots of ways to go wrong. Reading first can save you a lot of grief.
k1mu said:
The difference isn't in the baseband, it's in the bootloader. You can run a newer baseband than your bootloader, for example, especially if you have the MDK bootloader.
Since you're starting from stock, the baseband and the bootloader revisions are the same and can be found from Settings/More/About phone.
Before you flash anything, please read the what you need to know thread in the General section. Also, there's my thread in this forum.
The S4 is more complicated than the S3 largely because Samsung has really locked it down much more effectively than the S3. Consequently, there's lots of ways to go wrong. Reading first can save you a lot of grief.
Click to expand...
Click to collapse
One more question. Is there a way to flash the s4 back to stock? I'll find the info on how, but going into the whole rooting and coming phase it would be nice to know that I could flash back to stock with odin. As I have with my s3.
GlitchMob said:
One more question. Is there a way to flash the s4 back to stock? I'll find the info on how, but going into the whole rooting and coming phase it would be nice to know that I could flash back to stock with odin. As I have with my s3.
Click to expand...
Click to collapse
Yes. Read the second link in my reply above - it tells you how to identify what build you're on and has links to the downloadable Odin images for each build.
k1mu said:
Yes. Read the second link in my reply above - it tells you how to identify what build you're on and has links to the downloadable Odin images for each build.
Click to expand...
Click to collapse
Thanks for your help. Turns out I'm on MJ7. I'm going to let this puppy charge while I hit the gym. I'll root it and see what rom I can install later tonight. Thanks again!! :victory:
GlitchMob said:
Thanks for your help. Turns out I'm on MJ7. I'm going to let this puppy charge while I hit the gym. I'll root it and see what rom I can install later tonight. Thanks again!! :victory:
Click to expand...
Click to collapse
Mind as well update to mk2. You can do the same as mj7 but are most up to date. Just my 2 pennies. Btw I'm on bonestock 2.1 in SS romslot 1.
Sent from my SCH-I545 using xda app-developers app
Slowbalt said:
Mind as well update to mk2. You can do the same as mj7 but are most up to date. Just my 2 pennies. Btw I'm on bonestock 2.1 in SS romslot 1.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Is there a noticeable difference? If its the same, why upgrade?
I am coming from a similar situation as you. I cracked my screen on my S3 and Asurion replaced it with an S4, which I received on Monday. I thought that I was going to be able to load SlimKat and pick up where I left off, but no.
The posts that k1mu linked are a great starting point. A few of my thoughts that I came to realize this week. These are my ways of looking at it and may not be totally correct.
The bootloader is locked and there isn't a total unlock (yet). Safestrap allows you to crack the door open a little and reach your arm in to grab a few things.
You will need to stick with ROMs that work with the TouchWiz kernel. The post that k1mu referenced has a link to compatible ROMs. You will not be able to load SlimKat, CM, Carbon, etc. Basically any ROM you choose will have TW underneath. Some of the ROMs will try to look like an ASOP, but it is still a TW base.
Safestrap will allow you to create ROM slots where you can try out the ROM to see if you like it. I am still trying to decide what I want to use. Currently I have Hyperdrive as the leader. Everything that I do continues to work. The Eclipse ROM looks good but it is not quite there yet, but he is working on a build in the next couple days. Here is a link to their website with more up to date status. Eclipse . I also looked at the Foxhound ROM and it is good also. For me support and future upgrades are the most important. I am starting to think that i will embrace TW instead of trying to cover it up and will go with Hyperdrive.
If you use TiBu, read this post, especially with Hyperdrive http://forum.xda-developers.com/showthread.php?t=2653044.
The other realization that hit me was that while Safestrap can create partitions for loading different ROMs, each one is restricted to a maximum of a 3GB /data partition. When I tried to restore all of my apps this was quickly used up. It isn't supported by Safestrap to flash to the stock location, but it can and has been done. Since Safestrap isn't doing a flash there are more risks and I think that this should probably be kept to a minimum. This is where you want to test all the candidate ROMs first and then decide which one to use and then flash to the stock location. Obviously this could cause problems with the phone and would use ODIN as a fallback. Unless something get totally hosed and then you are out of a phone.
One thing that I realized a long time ago is that when you change devices you may want to do everything exactly the way it was before. On the phone or even when looking for information. But in most cases it is better to change your processes or work flow to work with the new device than it is to change the device to work in your previous work flow.
I was curious if this still works on ND7 of the Verizon Galaxy Note 2? Thanks.
RTR
https://www.youtube.com/watch?v=n9u11EyOaBY
Published on Dec 12, 2012
WARNING: DO NOT FLASH ANYTHING WITH a sboot.bin!! This will either
relock your device or render it inoperable.
Recently, resident hardware hacker, XDA Elite Recognized Developer and XDA Developer TV Producer AdamOutler got his hands on a Verizon variant of the new Samsung Galaxy Note II. He assembled a team of experts including Recognized Developer Ralekdev and fellow Elite Recognized Developer Rebellos. With a group this talented they had the bootloader unlocked in no time. Why does Verizon even try?
This exploit involves installing Revision ROM as an Odin package. Running the CASUAL to exploit. Then flashing the custom bootloader and TWRP recovery. It ends by booting back into the ROM. Remember to boot back into the ROM, this is important because you wont get LTE back until CASUAL completes and tells you that you are unlocked. So grab a
chair and check out this video.
Step 1: Install Revision ROM Odin Package by AdamOutler: http://d-h.st/ouo
Step 2: CASUAL Exploit by Ralekdev and AdamOutler: http://d-h.st/dma
Step 3: Install Insecure Bootloaders by Ralekdev and Rebellos:http://d-h.st/DQG
Tools:
Odin Tool: http://d-h.st/s6I
Pit Tool for use in every odin flash: http://d-h.st/mKu
XDA Thread: http://forum.xda-developers.com/showt...
XDA Portal: http://www.xda-developers.com
XDA Forums: http://forum.xda-developers.com
XDA TV: http://www.xda-tv/
I'm sorry but the answer is no. If you are on ND7 and have a locked bootloader right now, than you are stuck with a locked bootloader. I think your only 3 options are to root and use Xposed mods to customize, or to root and use Safestrap to flash a touchwiz rom with the same kernel as the stock kernel, or send your phone out to Mobile Tech Videos in Texas to do a downgrade service on your phone.
Those are the only options that I am aware of for phones on MJ9 or higher with locked bootloader.
Please don't take this the wrong way but this is not where you create a new thread. This section is for android development. You should have asked this in the "Q&A help and troubleshooting" section of this forum. Just for future references.
"Chance Favors the Prepared"
glockman4519 said:
I'm sorry but the answer is no. If you are on ND7 and have a locked bootloader right now, than you are stuck with a locked bootloader. I think your only 3 options are to root and use Xposed mods to customize, or to root and use Safestrap to flash a touchwiz rom with the same kernel as the stock kernel, or send your phone out to Mobile Tech Videos in Texas to do a downgrade service on your phone.
Those are the only options that I am aware of for phones on MJ9 or higher with locked bootloader.
Please don't take this the wrong way but this is not where you create a new thread. This section is for android development. You should have asked this in the "Q&A help and troubleshooting" section of this forum. Just for future references.
"Chance Favors the Prepared"
Click to expand...
Click to collapse
Oh ok. Thank you for the response. I'll do that in the future. Do you think sending it to Mobile Tech is worth the trouble personally?
Absolutely. My granddaughter got hold of my phone while I was in TWRP recovery mode and screwed my phone up bad. It ended up with the boot loader updated and locked (my fault for that one) and all I could do from then on out was use Safestrap and flash Safestrap compatible roms.
I heard about Mobile Tech Video and thought it couldn't hurt to try and 2 weeks later I was back in the"flashing saddle"again. I highly recommend their services.
"Chance Favors the Prepared"
Galaxy note 2 schi605 nd7
Please someone help me find a touchwiz rom using safestrap i tried installing alliance rom and i installed on a rom slot but when i rebooted phone it jus went back in a bootloop to stock recovery i was able to get ba k into safestrap and restored my back up im wondering why rom never loaded tia!
ricosf415 said:
Please someone help me find a touchwiz rom using safestrap i tried installing alliance rom and i installed on a rom slot but when i rebooted phone it jus went back in a bootloop to stock recovery i was able to get ba k into safestrap and restored my back up im wondering why rom never loaded tia!
Click to expand...
Click to collapse
Same thing happened to me...Did you have any luck getting it working. I am sitting here with an unusable phone and was hoping to get it running.
note 2 nd7 rom
yes what i did was i installed safestrap 4.0 and i of course did a back up and instead of flashing in the rom slot i wiped my stock slot and installed alliance rom and had no issues at all..it was a risk but i took it cause i can and/or could of just used odin to flash stock back so yes phone works flawless..got a note 4 coming today so im tossing my note 2 as a backup phone goodluck
Good day
So after you wiped the stock slot and installed the rom , it worked out okay?