As you may or may not be aware Samsung in their wisdom have decided to blacklist old sboot.bin files from being installed when a customer has installed the XXELLA sboot, this may or may not be for a valid reason, but enforcement such as this is not nice and its always nice to be able to do what we want with our phones.
Attached is a small util which will check the sboot.bin file and give you some info, such as if it appears on the Samsung blacklist, if it's new which means boot downgrade will not be possible or if it does not appear in the blacklist which means it can be used for bootloader downgrade and you should PM me with details :laugh:
I have checked all the sboot.bin files I have and they are all blacklisted, some of these sboot.bin files are ones which have never appeared in the internet and I have gotten from my various sources, these include engineering boots and debug versions.
The blacklist is built on the date the EBL was compiled and its possible no older sboot.bin files will be missing from the blacklist, but we have to try
It's also worth noting here that this boot enforcement is also in the latest boots on the M440s, N7100 (XXDLL7), N7102, E210s (KSJLL6) and will probably spread to other models in the near future.
Enjoy and happying hunting the nice sboot.
SBOOT_CHECK.zip
How to downgrade boots on XXELLA or XXELLC and bypass the blacklist (or any other boot in existence as of this post)
(USE THESE COMMANDS AT YOUR OWN RISK)
> adb push sboot.bin /sdcard/sboot.bin
> adb push tz.img /sdcard/tz.img
> adb push param.bin /sdcard/param.bin
> adb shell
$ su
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4
# rm /sdcard/sboot.bin
# rm /sdcard/tz.img
# rm /sdcard/param.bin
# reboot fota_bl
tz.img and param.bin are not required, but since they are part of AP_BOOT I included them for completeness.
You will not lose any data, since no wipe is performed or needs to be performed using this method.
Its tested method and no, I will not release any automated method.
APBOOT_I9300XXALE8.zip
APBOOT_I9300XXALEF.zip
APBOOT_I9300XXBLFB.zip
nice
as you said, my old ICS bootloader is blacklisted, ELLA is ok.
Hopefully somedy can make downgrading happen. I regret i flashed the new bootloader
Maybe it was the cause of the mythical sudden dead...
And they wanted to be sure...
And all the previous bootloaders are blacklisted, because they ALL were dangerous...
Maybe...just a wishful thinking...but till anyone proves otherwise...
Sent from my washing machine using its tumbler.
sebarkh said:
Maybe it was the cause of the mythical sudden dead...
And they wanted to be sure...
And all the previous bootloaders are blacklisted, because they ALL were dangerous...
Maybe...just a wishful thinking...but till anyone proves otherwise...
Sent from my washing machine using its tumbler.
Click to expand...
Click to collapse
NOthing mythical about sudden death.. better to be quite and look stupid then open your mouth and confirm it.
read what tons of people have faced in your mythical sudden death.
http://forum.xda-developers.com/showthread.php?t=1993044&page=207
treare said:
Hopefully somedy can make downgrading happen. I regret i flashed the new bootloader
Click to expand...
Click to collapse
Why?
LenAsh said:
Why?
Click to expand...
Click to collapse
Cuz you cant lol
I don't get it. It's good or bad to have the new sboot?
pros: some report it fixes sudden deaths; updated
cons: can't flash older sboots; ?
marcellocord said:
I don't get it. It's good or bad to have the new sboot?
pros: some report it fixes sudden deaths; updated
cons: can't flash older sboots; ?
Click to expand...
Click to collapse
Until new sources come out and we can actually check the kernel and what was changed, it's too early to say anything.
The bootloader changes might be completely unrelated to the sudden death bug and just Samsung increasing their warranty enforcement.
Mate Odia, your file is one heavy virus attached on some system dll on my laptop. Check with Avira Amtivirus.
Regards
sak500 said:
NOthing mythical about sudden death.. better to be quite and look stupid then open your mouth and confirm it.
read what tons of people have faced in your mythical sudden death.
http://forum.xda-developers.com/showthread.php?t=1993044&page=207
Click to expand...
Click to collapse
...and better to understand my words than not.
It' not the point of my post. The point is that we blame Sammy for blacklisting, but maybe they did it on purpose for users' good, as the previous bootloaders were dangerous - affected by this sudden death syndrome.
And replying to your answer: until Samsung confirms its existance we can not be sure all those brick cases have one cause:SD.
AndreiLux said:
Until new sources come out and we can actually check the kernel and what was changed, it's too early to say anything.
The bootloader changes might be completely unrelated to the sudden death bug and just Samsung increasing their warranty enforcement.
Click to expand...
Click to collapse
yeah, I can now see a red ! at the top-left of the screen, on the SGSIII logo part.
Samsung don't want you to downgrade because if you do and you get sudden death, they'll have to replace your S3 for a new one... and for FREE.
miro666 said:
Mate Odia, your file is one heavy virus attached on some system dll on my laptop. Check with Avira Amtivirus.
Regards
Click to expand...
Click to collapse
Virus Total Scan
Bit suspicious...
Tovagulet said:
Samsung don't want you to downgrade because if you do and you get sudden death, they'll have to replace your S3 for a new one... and for FREE.
Click to expand...
Click to collapse
We still have zero evidence that the bootloader has anything to do with sudden death issue, please don't go spreading nonsense around.
AndreiLux said:
We still have zero evidence that the bootloader has anything to do with sudden death issue, please don't go spreading nonsense around.
Click to expand...
Click to collapse
Theory 1: Samsung included a new method to validate the warranty
Theory 2: Samsung fixed those random bricks
Theory 3: Samsung fixed some bugs, but not that major bug from the point 2
Theory 4: Warranty and Random bricks
Theory 5: Another non-sence crap from Samsung, just like many
And the only theory regarding blacklisting old sboots, to prevent you downgrading to a warranty-friendly sboot. I doubt Samsung just wants users to be safe, away from faulty stuff, oh boy, I know how all the episodes begin and continue... but never end. Same plot: new thing - everybody goes nuts - this is awesome - (the f word) you Samsung - stay away
so not blacklisted then? Or does the program tell me when it is?
Code:
File: C:\cygwin1\home\tar\sboot.bin
Samsung S-Boot 4.0 -500022 for GT-I9300 (Dec 25 2012 19:52:01) Rev I9300ZSDLL1
Sboot is New
File: C:\ROM_Working\ROM_files\bootloader_check\sboot.bin
Samsung S-Boot 4.0 -742798 for GT-I9300 (Dec 22 2012 17:03:17) Rev I9300XXELLA
Sboot is New
Nvm
Code:
File: C:\ROM_Working\ROM_files\bootloader_check\sboot.bin
Samsung S-Boot 4.0 -928452 for GT-I9300 (Aug 21 2012 17:03:14) Rev I9300XXBLH3
Sboot is BlackListed
Perka said:
so not blacklisted then? Or does the program tell me when it is?
Click to expand...
Click to collapse
from OP
Odia said:
if it's new which means boot downgrade will not be possible
Click to expand...
Click to collapse
To say I9300ZSDLL1 is new and will install but contains its own blacklist.
I read somewhere that it is possible to downgrade if we receive an ota with an older bootloader, because system cannot check in these situations. But in the other hand I never saw a firmware upgrade with a new bootloader, only ELLA.
Sent from my GT-I9300 using Tapatalk 2
Mothatt said:
Virus Total Scan
Bit suspicious...
Click to expand...
Click to collapse
Its because of Execryptor, AV software not like files they cannot check, I am here to help, not spread virus infected software.
Seems only Agnitum has the correct result.
Related
The AlphaRev team has successfully unlocked NAND on several devices in just the last few days using the same technique. Some of the devices are very similar spec-wise to the Espresso and some of the devices are the same devices that Dumfuq's kernels work for universally with our phone. Has anyone played with this for the Espresso yet? (Devs). I wouldn't play with it unless you are sure what you are doing due to the page having a disclaimer about it being possible to brick your device.
http://alpharev.shadowchild.nl/
http://forum.xda-developers.com/showthread.php?t=794314
nikol4s said:
The AlphaRev team has successfully unlocked NAND on several devices in just the last few days using the same technique. Some of the devices are very similar spec-wise to the Espresso and some of the devices are the same devices that Dumfuq's kernels work for universally with our phone. Has anyone played with this for the Espresso yet? (Devs). I wouldn't play with it unless you are sure what you are doing due to the page having a disclaimer about it being possible to brick your device.
http://alpharev.shadowchild.nl/
http://forum.xda-developers.com/showthread.php?t=794314
Click to expand...
Click to collapse
Initial testing shows that it's very likely it will work.
Now I need to put some stuff together for a full manual test.
ieftm said:
Initial testing shows that it's very likely it will work.
Now I need to put some stuff together for a full manual test.
Click to expand...
Click to collapse
Get in touch with ChiefzReloaded, he's working on it as well.
I smell unlocked NAND incoming soon.
Hmmm i smell s-off sooner then later..
at 935 pm est on chiefsreloaded twitter page he states he has clockwork reinstalled with no need for the update.zip bs. =>
Damn i am syked !!
I am working with AlphaRev to help port this over to Espresso. As IEF said, initial testing shows promise. We'll keep you in the loop when we know more.
I hope this works. Finally some great progress,
Sent from my T-Mobile myTouch 3G Slide using XDA App
Good job guys this is amazing! Thank you
Thanks for your help everyone. I don't need anymore model ID's! See my photo of S-OFF in this thread!
[FONT="]
[/FONT]
[FONT="]If I can all ask you a favor - I need a lot of sample data in order to help IEF automate the process in AlphaRev, specifically your model ID numbers for your Slides. This is not phone-specific like the serial number, but I want to make sure different revisions of our phone aren't out there or that they didn't give them different model IDs depending on manufacturing conditions.
Here's how to help:[/FONT]
[FONT="]Run: adb pull /proc/cmdline.[/FONT]
[FONT="]Open (using Notepad, etc) the 'cmdline' file that you just downloaded using adb pull /proc/cmdline (it defaults downloading to the directory where you ran adb from).[/FONT]
[FONT="]I need the letters and numbers after the equals sign of "androidboot.mid=".[/FONT]
[FONT="]Post those letters and numbers here, in a reply to this thread (please do not quote this post).[/FONT]
[FONT="]Please do NOT reply with your androidboot.cid or androidboot.serialno![/FONT][FONT="]
Please understand that this post does not imply that we have S-OFF yet. I will let you know if/when that happens.
Thanks everyone![/FONT]
Deleted. As totally off topic.
Here You Go Man....
androidboot.mid=PB6510000
Deleted...
I've got the same:
androidboot.mid=PB6510000
MrThePlague said:
I've got the same:
androidboot.mid=PB6510000
Click to expand...
Click to collapse
Same here to
androidboot.mid=PB6510000
androidboot.mid=PB6510000
nbetcher said:
If I can all ask you a favor - I need a lot of sample data in order to help IEF automate the process in AlphaRev, specifically your model ID numbers for your Slides. This is not phone-specific like the serial number, but I want to make sure different revisions of our phone aren't out there or that they didn't give them different model IDs depending on manufacturing conditions.
Here's how to help:
Run: adb pull /proc/cmdline.
Open (using Notepad, etc) the 'cmdline' file that you just downloaded using adb pull /proc/cmdline (it defaults downloading to the directory where you ran adb from).
I need the letters and numbers after the equals sign of "androidboot.mid=".
Post those letters and numbers here, in a reply to this thread (please do not quote this post).
Please do NOT reply with your androidboot.cid or androidboot.serialno!
Please understand that this post does not imply that we have S-OFF yet. I will let you know if/when that happens.
Thanks everyone!
Click to expand...
Click to collapse
Not to sound stupid i read the.. link but wtf is.. S-OFF and what does this do exactly? can someone dumb it down for me
Virus1x said:
Not to sound stupid i read the.. link but wtf is.. S-OFF and what does this do exactly? can someone dumb it down for me
Click to expand...
Click to collapse
S-off makes your phone fully rooted. The S stands for security which locks your NAND, HBOOT, system, and recovery. Right now we our phones are soft modded so we have to get into recovery from the update.zip. With S-off all we have to do is flash the recovery once then it boots up without the update.zip. You can read about it more at this link http://alpharev.shadowchild.nl/
Sent from my T-Mobile myTouch 3G Slide
lstevens86 said:
S-off makes your phone fully rooted. The S stands for security which locks your NAND, HBOOT, system, and recovery. Right now we our phones are soft modded so we have to get into recovery from the update.zip. With S-off all we have to do is flash the recovery once then it boots up without the update.zip. You can read about it more at this link http://alpharev.shadowchild.nl/
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
Anyone pull this off yet
Sent from my T-Mobile myTouch 3G Slide using XDA App
Virus1x said:
Anyone pull this off yet
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
There are people working on it
Sent from my T-Mobile myTouch 3G Slide
same as well
.mid=PB6510000
About The ROM
Revision is based on I605VRALJB. Also, it's been specifically designed to be the most stable image to fall back on before or after flashing kernels, recoveries or ROMs. It will put your device into the MOST working condition possible currently. The only more possibly stable image would be the one your device came with and we don't have that.
What is Revision?
Revision is a stepping stone. It puts your device into a relatively stock, and known working condition.
Tweaks
I added the following tweaks to the ROM for usability and hackability.
Carrier Unlocked for AT&T network.
Rooted with ERD Chainfire's SuperSU
Bash
Busybox
i2cdetect, i2cdump, i2cget, i2cset
ipctool
strace
tcmpdump
viewmem
PARAMS: UART Logging Increased
PARAMS: UART Root Prompt at battery charging
PARAMS: UART Shell terminal during normal operations
The PARAMS will be available in a future CASUAL application for testing.
Download Revision3 ROM repacked
Troubleshooting
Windows users: First uninstall PDANET drivers, then install Samsung Kies.
Here's some notes I wanted to record:
Uncompressing a Samsung System image
Code:
./ext4_utils/simg2img ./originalsystem.img ./working.img
Compressing a Samsung Image
Code:
sync; sudo ./ext4_utils/make_ext4fs -s -l 1792M -a ./temp ./system.img /path/to/mounted image
Create a tar.md5.gz file from a set of images..
Code:
tar -H ustar -c boot.img hidden.img modem.bin param.bin recovery.img system.img tz.img sboot.bin>./Revision1.tar;sync md5sum Revision1.tar >> Revision1.tar; mv Revision1.tar Revision1.tar.md5; sync; gzip Revision1.tar.md5 -c -v >Revision1.tar.md5.gz;
the tools are available on the internet.
Revision1: initial release
Revision2: Fixed Baseband issue. The PARAMS were to blame for this. Removed features to add functionality.
Revision3: Carrier Unlock for AT&T.. needs more work to get rid of Verizon warning. Thanks Joder for the APN info.
Revision3 repacked: apparently there was an issue with the uploaded Revision3. Repacked is a properly repackaged version of Revision3.
thx
downloading now... cant wait for the unlocked bootloader hack to be released!
Great Work!
Nice, can't wait for the bootloader unlock tool to be released!
Thanks Adam for all your hard work. You and Beans are the first devs I ever donated to, and you wont be the last. I really appreciate the all the hard work devs put into this.
So what's the next step? Does this help you understand the bootloader?
So just flash this via Odin?
Sent from my SCH-I605 using Tapatalk 2
Thanks very Much
I really appreciate all you have done
I'll download it and put it in a folder locked with a code.
Sent from my rooted galaxy note 2... U mad?
nnnnr14 said:
I'll download it and put it in a folder locked with a code.
Sent from my rooted galaxy note 2... U mad?
Click to expand...
Click to collapse
Make sure you encript it as well
drumdestroyer said:
Make sure you encript it as well
Click to expand...
Click to collapse
Pshh that's too advanced! I'll probably have to leave a .txt file on the desktop reminding me what the code was!
Sent from my rooted galaxy note 2... U mad?
i flashed in odin and now i have no service nor 4g it is simply stuck at the activation screen in setup wizard......any ideas. thanks in advance.
oh well aint it grand
thunderbread said:
i flashed in odin and now i have no service nor 4g it is simply stuck at the activation screen in setup wizard......any ideas. thanks in advance.
Click to expand...
Click to collapse
Flash back to what u were on before. Seems like a common problem. Beans had that prob with his rom. Before he released it.
mine too
mine is tryn to activate but still stuck at activation screen
nnnnr14 said:
Pshh that's too advanced! I'll probably have to leave a .txt file on the desktop reminding me what the code was!
Sent from my rooted galaxy note 2... U mad?
Click to expand...
Click to collapse
That's me! Lol. I have to write it on my hand next to my grocery list.
welp dont know
welp Adam yours kept saying tryn to activate,so I went back odin the others and now the other 2 does also is saying tryn to activate,sounds like I am gonna have to call and see if my sim card has to be reactivated,but I am gonna let it set overnite just to make sure...........
Yeah mine isnt doing anything. Tried to Odin back and still nothing. Just sits at activation screen. Anybody have any ideas.
Sent from my SCH-I535 using xda app-developers app
thunderbread said:
Yeah mine isnt doing anything. Tried to Odin back and still nothing. Just sits at activation screen. Anybody have any ideas.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Can you check Settings>About>And status to see if you have an IMEI or any info?
Nope. Won't let me leave activation screen.
Sent from my SCH-I535 using xda app-developers app
Has any one tried the bypass activation like we did on the s3?
on select a language screen, press lower left corner, lower right corner, lower left corner, lower right then volume up
Sent from my SCH-I605 using Tapatalk 2
Mine finally just stopped tryn to activate and gave me a number to call and i have wifi,, but the answer to question on imei is there is no imei number, no baseband, all says unknown
T-Mobile SM-N900T
Verizon SM-N900V
Sprint SM-N900P
Root de la Vega
By @designgears & @Chainfire
First off, a big huge thanks to Chainfire for his SuperSU app and help getting root setup manually.
Warning: This will wipe your data and internal sdcard, this will show custom system status. I cannot be held responsible for anything you do to your phone, rooting is optional, I am not forcing you to do it.
DO NOTE TAKE OTA UPDATES OR UPDATE WITH STOCK ODIN FILES THAT CONTAIN BOOTLOADER UPDATES!!
How To Enter Download Mode
Method 1: adb reboot download
Method 2: Pull the battery out, unplug the usb cable, reinsert the battery. Hold Volume Down + Home + Power. Follow the instructions on the screen.
IF YOU HAVE REACTIVATION LOCK ON, TURN IT OFF!
Go to Security Settings and turn the reactivation lock OFF, this is just a precaution.
Rooting Instructions
Remove the external sdcard (if you have one)
Boot into bootloader mode (see methods above)
Load the correct AP file into the AP slot in Odin (find your AP version in post #2)
Load the correct CSC file into the CSC slot in Odin (find your CSC version in post #2)
Click start in Odin, wait for it to fully flash
Let your device fully boot after flashing has completed
Copy the contents of Root_de_la_Vega.zip to the root of the internal storage
/My Computer/[Phone Name]/Phone/
root_de_la_vega.sh
root_files (folder)
Reboot (very important!)
After fully booting delete the files from the internal storage that were added previously
/My Computer/[Phone Name]/Phone/
root_de_la_vega.sh
root_files (folder)
Reboot (extremely important!)
Reinsert the external sdcard (if you have one)
That's all! Enjoy Root!
Bounty Pledges and Donations can be sent via Paypal:
Click Here (please include your xda username in the comments)
Bitcoin: 1F2FfTNnaXzFrGhUaB4iBD7EBegR5gh3qF
If you haven't already, pick up a copy of SuperSU Pro to support @Chainfire! Well worth the $2.49!
Root_de_la_Vega.zip / Odin v3.09
Root_de_la_Vega.7z
Get your version information:
Dial *#1234# (If SuperSU opens, press the back button)
Find your AP version below, Download the tar file
Find your CSC version below, Download the tar file
Find Your AP Version, Download Tar File
--------------------------------------------------------------------------------
Sprint N900PVPUBMI3_VEGA
N9005VJUBMI7_VEGA
N9005VJUBMJ1_VEGA
N9005XXUBMI7_VEGA
N9005XXUBMJ1_VEGA
N9005XXUBMJ3_VEGA
N9005ZHUBMI7_VEGA
N9006ZCUBMJ3_VEGA
N9008ZMUBMJ7_VEGA
N900SKSUBMJ1_VEGA
N900SKSUBMJ5_VEGA
N900W8UBUBMJ1_VEGA
N900W8VLUBMJ1_VEGA
N900W8VLUBMI5_VEGA
--------------------------------------------------------------------------------
DO NOT mix and match AP and CSC files! Doing so will trip KNOX Warranty!
Find Your CSC Version, Download Tar File
REQUEST THE CSC FILE IF YOURS IS NOT LISTED!! Failure to comply will may leave your warranty voided.
Sprint N900PSPTBMI3_CSC.tar.md5
CSC FOLDER <-- get your csc files here
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Question & Answer
"Root de la Vega" What kind of name is that?
It's named after Ralph de la Vega, CEO of AT&T Mobility.
Can I flash custom recovery/kernel without tripping KNOX flags?
No.
Will this set a tripped KNOX flag 0x1 back to 0x0?
No.
Can you help me with the drivers?
No, but you can head over here for help with drivers.
How do I get into download mode?
Method 1: adb reboot download
Method 2: Pull the battery out, unplug the usb cable, reinsert the battery. Hold Volume Down + Home + Power. Follow the instructions on the screen.
Will rooting or downgrading or flashing stock trip the Knox flags?
No, KNOX flags will not be tripped!
Will root survive a factory reset?
Yes, it does.
Do I need have to fully wipe my phone when rooting?
Yes. If you don't you will get lots of nasty force closes. I have yet to find a way around it.
Does Xposed Framework work?
Yes, it has been updated to work fully with the Note 3.
Will rooting report system as custom and display an unlocked lock on the initial boot screen?
Yes. It can be removed by installing Xposed Framework with Wanam Xposed and enabling Security hacks > Fake system status.
Titanium Backup is giving me problems, how can I fix it?
Check out this thread. If you are still having issues, please take your concerns to the dev, they are not related to rooting.
How do I open a 7z file?
With 7zip or IZArc!
Can I do this on OS X/Linux?
No, not until heimdall is updated to support the Note 3.
Can I unroot?
Yes, use SuperSU full unroot option or flash stock.
I am getting a "Prevention Information" popup after running a root app, how do I disable it?
From terminal emulator or adb shell as root, run; pm disable com.sec.knox.seandroid
Or freeze the Knox apps with Titanium Backup.
I am getting Force Closes after flashing, how can I fix it?
Make sure you are flashing the CSC file! If you are, try flashing AP and CSC separately.
HELP! I flashed N9005XXUBMJ3_N9005OXABMJ1 and now I am stuck in download mode! What do I do?!
You are mostly going to trip the KNOX Warranty at this point.
Flash this AP N9005XXUBMJ3_N9005OXABMJ1_BTU_RECOVER.tar.md5 (2.05 GB) and this CSC N9005OXABMJ3_CSC.tar.md5 (38.0 MB)
Whats stopping this being used for the N9005?
vinokirk said:
Whats stopping this being used for the N9005?
Click to expand...
Click to collapse
The method? Nothing, I am working on it
Don't use these files for it tho.
designgears said:
The method? Nothing, I am working on it
Don't use these files for it tho.
Click to expand...
Click to collapse
Good stuff!
Getting root whilst keepin know at 0x00 would be fantastic
OMG! I didn't believe someone could find a solution to root and maintain Knox on 0x0!
Please do the same for SM-9005 and a donation will arrive
Galaxy Note 3 | SM-9005 | Tapatalk
mouse100 said:
OMG! I didn't believe someone could find a solution to root and maintain Knox on 0x0!
Please do the same for SM-9005 and a donation will arrive
Galaxy Note 3 | SM-9005 | Tapatalk
Click to expand...
Click to collapse
What is your current build number and what carrier is the phone for?
settings > general tab > about phone > build number
JSS15J.N9005XXUBMJ1
I use Vodafone Italy but phone is no brand.
Awesome! That was fast! Thank you for this! sorry I used up all my Thanks for the day :laugh:
designgears said:
What is your current build number and what carrier is the phone for?
settings > general tab > about phone > build number
Click to expand...
Click to collapse
I havewritten on the othertopic but for N900 models i think here is better to write
Hey @designgears i see that you are really so talented developer here on xda. You really made this root quick for the friend who has asked you right now.
My paypal is not active yet but nowadays i want to activate it and send you donation for your hard works. Actually i dont own the at&t or roger version but i am sure that you deserve it and i also hope that maybe i can get your great root support on my device too (N9000Q).
As i said i will donate you as soon as my paypal has been activated because i think that you really deserve it.
And i can also tell you that lots of people from the Turkish forum website are also waiting for a root method like yours. Everyone would be so happy if you can do sth for us.
I also want to send you our firmware link and details:
N9000QXXUBMI5_N9000QTURBMI3_TUR
http://www.hotfile.com/dl/250045625/af09deb/N9000QXXUBMI5_N9000QTURBMI3_TUR.zip.html
Build number:
JSS15J.N9000QXXUBMI5
If you could do sth and help us about rooting our phones with knox 0x0 it would be really so appreciated.
Thank you very much for all you effort for this great community
I read something about CSCs of GN3, and i saw that you can flash any region and it wont trigger know but it doesnt change CSC, maybe its an option to use a single firm to all of them.
Can someone mirror the file? It seems to not be available..
DDRFAN said:
Can someone mirror the file? It seems to not be available..
Click to expand...
Click to collapse
Rebuilding it, tar'd the files wrong. It will be back in a bit.
designgears said:
Rebuilding it, tar'd the files wrong. It will be back in a bit.
Click to expand...
Click to collapse
Thanks for the speedy reply I'll be waiting.
Glad I waited to root! Thanks OP. Maybe you can enlighten us on how this works versus every other method?
Sent from my SM-N9005 using XDA Premium 4 mobile app
jetbruceli said:
Glad I waited to root! Thanks OP. Maybe you can enlighten us on how this works versus every other method?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hex editing the system img to call to a script on the sdcard
designgears said:
Hex editing the system img to call to a script on the sdcard
Click to expand...
Click to collapse
Ok great lol! I am no dev or anything but this is just plainly great news for the note 3 users and for anyone worried Knox.
Also it's an awesome "Haha look what I did Mr. Manufacturer!"
Sent from my SM-N9005 using XDA Premium 4 mobile app
TheRecRuiT89 said:
I havewritten on the othertopic but for N900 models i think here is better to write
Hey @designgears i see that you are really so talented developer here on xda. You really made this root quick for the friend who has asked you right now.
My paypal is not active yet but nowadays i want to activate it and send you donation for your hard works. Actually i dont own the at&t or roger version but i am sure that you deserve it and i also hope that maybe i can get your great root support on my device too (N9000Q).
As i said i will donate you as soon as my paypal has been activated because i think that you really deserve it.
And i can also tell you that lots of people from the Turkish forum website are also waiting for a root method like yours. Everyone would be so happy if you can do sth for us.
I also want to send you our firmware link and details:
N9000QXXUBMI5_N9000QTURBMI3_TUR
http://www.hotfile.com/dl/250045625/af09deb/N9000QXXUBMI5_N9000QTURBMI3_TUR.zip.html
Build number:
JSS15J.N9000QXXUBMI5
If you could do sth and help us about rooting our phones with knox 0x0 it would be really so appreciated.
Thank you very much for all you effort for this great community
Click to expand...
Click to collapse
Uploaded!
Other files are back up to!
Can you please make this work for wind mobile n900w8! I will post the build number when I get home
Sent from my Nexus 4 using XDA Premium 4 mobile app
Please for n9005!!! :thumbup::thumbup::thumbup:
Enviado desde mi SM-N9005 usando Tapatalk 2
Sprint Moto X [XT1056] Stock ROMS
By using any of these you agree that I am not responsible for ANYTHING that can or may happen to your phone
Click to expand...
Click to collapse
Like this guy said:
iKrYpToNiTe said:
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please!
Click to expand...
Click to collapse
-----------------------------------------------------------------
KIT KAT 4.4.4
System Version: 212.44.28
Software update 08/2014
Code:
[B]DETAILED ENHANCEMENTS:[/B]
Android™ 4.4.4, KitKat® - Android 4.4.4, KitKat, is the latest release of the Android platform. This release includes several stability, framework and security fixes in addition to accuracy improvements to the power profile.
Camera - Improved image quality - Improved camera image quality including better consistency of exposure, more realistic flash coloring, improved photos in low light conditions using front camera.
Camera - Pause video recording - Added the ability to pause video recording with a convenient pause/resume button on the viewfinder.
Updated Phone dialer - Updated Phone dialer with a new graphical layout and colors to improve consistency and usability.
Motorola Alert application - New Motorola Alert application sends periodic alerts with your location to your selected contacts. Now available for download from the Google Play Store.
ROM LINK
212.44.28
md5: d1fb4c2259855abf74dfadbad5ccdbc2
FIRMWARE LINK
LINK
-----------------------------------------------------------------
BIG thanks to:
iKrYpToNiTe
chad.goodman
NineInchNails
Rizal Lovins
ibanez7
motofirmware.center
JustCMH
HOT-SPOT UNLOCK:
iKrYpToNiTe said:
All you have to do is add net.tethering.noprovisioning=true to your build.prop file and then you can remove or freeze the entitlement check app if you want to. Sprint model requires ro.mot.tether_dun_required to change from 1 to 0.
For people who don't want to mess with modifying their build.prop file or use xposed. I made an app which requires Root, that will run a setprop command to bypass the check until you reboot. If you want it to last after a reboot you can select apply of boot to run the command after every reboot. This was tested and confirmed by cvhovey thanks to him for testing it for me, since I have free tethering. This is my first app so I hope you Enjoy it! I want to say thanks to jcase's slapmymoto and the developer of adaway, I used their github sources as references when I couldn't get something working. Also androidicons for the icon template, and Poliva for setpropex, and jduck for getting setpropex working on KitKat.
Download Links
v1.2 http://www.androidfilehost.com/?fid=23501681358557764(v1.2 is signed with a different key than v1.0/v1.1 so it will display a msg box telling you this just click okay)
Click to expand...
Click to collapse
RECOVERY LINKS
CWM Advanced Edition- PhilZ Touch
TWRP
SUPERUSER LINKS
SuperSU
CWM Superuser (Koush)
DID YOU MAKE AN EXPENSIVE BRICK?
[HOW-TO] Resurrecting A Bricked Moto X
FEW WAYS TO GET BACK TO STOCK
Easy Guide to Restore Stock Firmware on Moto X using RSD Lite
Moto X Toolkit v1.4.3 [Backup/Restore,Drivers,Return to stock,Root,Bootani]
Script FlashFirmware (simple and safe method to flash firmware)
Getting a moto x back to stock on mac os x
BAD BATTERY DRAIN LATELY? TRY THIS
hardware reset of the processor and terminates all running commands
LEAVING THIS HERE IN CASE I FORGET HOW TO TAKE A DUMP
Code:
[B]dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/System.img.ext4
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/Boot.img[/B]
Thanks for this! Thanks soo much for the hard work!
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
They are both up. md5's should be posted right, they were manually entered. I'm carving pumpkins with the boys, so........hopefully all is good. If not, let me know and I'll attack it when able to.
AbstractXart said:
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
Click to expand...
Click to collapse
pfft, and mine was what?
looks good gokart
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
gokart2 said:
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
Click to expand...
Click to collapse
nah, the last big script i did for people was teh first nexus toolkit, nowadays i hop around trying to help out unloved devices (hence teh name of the team i made Official Unloved Devices Hit Squad ). people needed this anyways, my stock rom was based on the pre-ota camera fix apparently. i had considered getting this phone on republic wireless so i wanted to scope out how development was coming, saw nothing was going on and figured id help out .
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Wha?! I never saw it Shabby. My bad, let me rephrase,
FINALLY! The second rom for the Sprint variant :').... I Love you! haha.
Hey guys, I just wanted to update and say it won't boot on the Verizon dev edition like the T-mobile rom will. It freezes for me on the Moto Earth boot animation. Noo! Well darn, I was wanting to try the sprint rom to see if I could get google wallet tap to pay working on my vzw dev phone since no one has figured out how to make tap to pay work on the non-sprint variants.
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
gokart2 said:
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
Click to expand...
Click to collapse
what command are you using to pack the boot.img?
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
shabbypenguin said:
what command are you using to pack the boot.img?
Click to expand...
Click to collapse
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
jimmypop13 said:
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
Click to expand...
Click to collapse
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
Click to expand...
Click to collapse
i take it then you arent packing the Device tree file to the boot.img.
http://pastebin.com/tSGxTmYq save this script, run it against stock boot.img. youll get a DTB.img, extract your boot.img, edit what you want in ramdisk or swap zimages. then use a modified mkbootimg to include the dtb file as part of it all
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
Click to expand...
Click to collapse
I got the sprint deodex rom booting on my vzw dev edition doing like you said. But sadly I found google wallet would not work. It just sat saying "finishing up a few things." So I guess unfortunately there is a hardware issue preventing wallet from working on the non-sprint variants. That sucks!!!
I don't understand why but I noticed between the t-mobile, verizon, and sprint roms that the signal bars are slightly different on every one. Sprint's seems to be stretched out a little more and have an extra bar or two. I hate all of them though because the grey has some funky white lines through it where the separations are instead of being solid grey. I don't know what was wrong with the stock android signal bars that none of the carriers wanted them
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
d4mi3n said:
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
Click to expand...
Click to collapse
Honestly have no clue about SS. I would have to say no. No sure what needs to be done for it to be SS flashable.
Added 4.4 links. Thank abiezer for letting me link to his deodex 4.4 build HERE!
I plan on adding the SPRINT specific firmwares, and more in due time.
Good morning guys, as the tittle says, I got some questions about patched files. I own a S3 (i9300) but I had the problem of "not registered in network" when I updated to 4.3 (It was fine at 4.1.2) so I fixed this using these files:
My questions are:
- Do I really have to patch those files everytime I wanna try any custom rom? (Only on roms based 4.4.4 I don't have to patch them and btw, I tried just patching the modem file and it fixed the network problem, I didn't have to use the kernel one)
- I don't know If installing stock kernels will fix the problem.
- Is there any other way to have network working fine?
crfahecr said:
Good morning guys, as the tittle says, I got some questions about patched files. I own a S3 (i9300) but I had the problem of "not registered in network" when I updated to 4.3 (It was fine at 4.1.2) so I fixed this using these files:
My questions are:
- Do I really have to patch those files everytime I wanna try any custom rom? (Only on roms based 4.4.4 I don't have to patch them and btw, I tried just patching the modem file and it fixed the network problem, I didn't have to use the kernel one)
- I don't know If installing stock kernels will fix the problem.
- Is there any other way to have network working fine?
Click to expand...
Click to collapse
You will just have to try a rom and see. Maybe sometimes yes maybe sometimes no.
If you don't want to do this all the time go get the imei repaired properly.
Darke5tShad0w said:
You will just have to try a rom and see. Maybe sometimes yes maybe sometimes no.
If you don't want to do this all the time go get the imei repaired properly.
Click to expand...
Click to collapse
What do you mean with "repaired properly"? I was talking about customs and stock. It always happen, that's why I uploaded the files.
crfahecr said:
What do you mean with "repaired properly"? I was talking about customs and stock. It always happen, that's why I uploaded the files.
Click to expand...
Click to collapse
You require those files because you or someone else has "upset" your efs, causing either or both of you imei or serial number to go to a generic one causng you to lose calling etc.
If you got the imei and serial number fixed properly at a service center this would no longer be necessary.
Darke5tShad0w said:
You require those files because you or someone else has "upset" your efs, causing either or both of you imei or serial number to go to a generic one causng you to lose calling etc.
If you got the imei and serial number fixed properly at a service center this would no longer be necessary.
Click to expand...
Click to collapse
Edit: Sorry, my wrong. But... Really? I read that I'm not the only one having this problem.
crfahecr said:
Edit: Sorry, my wrong. But... Really? I read that I'm not the only one having this problem.
Click to expand...
Click to collapse
No you are not, you can either continue to flash the files after each rom flash like you have been which honestly doesn't take long to simply flash it again or choose option b which is to get it repaired by samsung which will cost $.
Personally if the patched files are working fine I would stick to them.
http://forum.xda-developers.com/showthread.php?t=2393289
Darke5tShad0w said:
No you are not, you can either continue to flash the files after each rom flash like you have been which honestly doesn't take long to simply flash it again or choose option b which is to get it repaired by samsung which will cost $.
Personally if the patched files are working fine I would stick to them.
http://forum.xda-developers.com/showthread.php?t=2393289
Click to expand...
Click to collapse
Thanks for taking your time!