Database Develop

Danger SPl

Hi, guys, maybe i am stupid, but i cant find a link where i can download Death SPL
Please help, thanks.

sssats said:
Hi, guys, maybe i am stupid, but i cant find a link where i can download Death SPL
Please help, thanks.
Click to expand...
Click to collapse
DON'T.
We call it the "deathspl" for a reason.
And there is NO BENEFIT to it.
If you want to use a ROM that wants to use more than about 65MB in the /system partition, just move some files into /cache and symlink to them!!!! There is no reason to risk your hardware for something this pointless.

Where i must wach, if i have enough space?

Could you please rephrase that? I can't understand the question.

Here you go, download links and instructions http://forum.xda-developers.com/showthread.php?t=625886

lbcoder said:
DON'T.
We call it the "deathspl" for a reason.
And there is NO BENEFIT to it.
If you want to use a ROM that wants to use more than about 65MB in the /system partition, just move some files into /cache and symlink to them!!!! There is no reason to risk your hardware for something this pointless.
Click to expand...
Click to collapse
I see using SuperD a huge benefit

Joe333x said:
I see using SuperD a huge benefit
Click to expand...
Click to collapse
And risking a brick doesn't help you run it.
As I said, just move the overflow files into /cache. Fits just fine unless you're a retard.

lbcoder said:
And risking a brick doesn't help you run it.
As I said, just move the overflow files into /cache. Fits just fine unless you're a retard.
Click to expand...
Click to collapse
Or instead of moving anything you can just read this http://forum.xda-developers.com/showthread.php?t=625886 and not have to move files every time you want to flash a ROM. Trust me if you follow the guide you will not brick your phone.

Joe333x said:
Or instead of moving anything you can just read this http://forum.xda-developers.com/showthread.php?t=625886 and not have to move files every time you want to flash a ROM. Trust me if you follow the guide you will not brick your phone.
Click to expand...
Click to collapse
Trust me, sometimes even if you DO follow the guide, you'll STILL brick your phone.
The SPL you are recommending is simply NOT COMPATIBLE.
And no, it does not cause you to need to move files every time you write a different ***SYSTEM IMAGE***.
(Hint: The word "rom" does NOT APPLY)
I curse that stupid kid "haykuro" every time someone recommends this "deathspl". It has had TWO effects, neither of them positive;
1) Creates BRICKS,
2) Creates INCOMPATIBILITY.
*** if the various cookers weren't lazy douches, they would arrange files to be suitable for REGULAR SPL, and therefore there would be no issue of "this system requires XXXX SPL"....
It has been a TERRIBLE DISSERVICE.
Note: It is TRIVIAL to write a script to automatically REPAIR your various ill-conceived "update.zip" archives.
i.e.: (this won't work exactly like this, requires minor debugging, but to give you the idea...)
Code:
#!/bin/bash
unzip update.zip
mkdir -p update/cache/app
mv update/system/app/(a bunch of .apk's) update/cache/app
echo "(a few trivial lines to write /cache and create symlinks" >> update/META-INF/com/google/android/update-script
zip fixedupdate.zip update/*
java /path/to/testsign.jar fixedupdate.zip
Just run that on every update.zip that you feel like installing!!!

Well...
Hey!
Concerning deathspl...
1) Creates BRICKS,
2) Creates INCOMPATIBILITY.
*** if the various cookers weren't lazy douches, they would arrange files to be suitable for REGULAR SPL, and therefore there would be no issue of "this system requires XXXX SPL"....
Click to expand...
Click to collapse
Well said.... and agreed 1000%
So called deathSPl for HTC Dream is nothing more than engineering bootloader 1.33.2005 from HTC Sapphire.
Of course these devices are similar but not the same...
I know that this works out well for some, but it's also obvious that some like to mix it all up
Personnally i would appreciate to use some clever hacks for the original evironment to run modified ROMs.
Regards,
scholbert

lbcoder said:
Trust me, sometimes even if you DO follow the guide, you'll STILL brick your phone.
The SPL you are recommending is simply NOT COMPATIBLE.
And no, it does not cause you to need to move files every time you write a different ***SYSTEM IMAGE***.
(Hint: The word "rom" does NOT APPLY)
I curse that stupid kid "haykuro" every time someone recommends this "deathspl". It has had TWO effects, neither of them positive;
1) Creates BRICKS,
2) Creates INCOMPATIBILITY.
*** if the various cookers weren't lazy douches, they would arrange files to be suitable for REGULAR SPL, and therefore there would be no issue of "this system requires XXXX SPL"....
It has been a TERRIBLE DISSERVICE.
Note: It is TRIVIAL to write a script to automatically REPAIR your various ill-conceived "update.zip" archives.
i.e.: (this won't work exactly like this, requires minor debugging, but to give you the idea...)
Code:
#!/bin/bash
unzip update.zip
mkdir -p update/cache/app
mv update/system/app/(a bunch of .apk's) update/cache/app
echo "(a few trivial lines to write /cache and create symlinks" >> update/META-INF/com/google/android/update-script
zip fixedupdate.zip update/*
java /path/to/testsign.jar fixedupdate.zip
Just run that on every update.zip that you feel like installing!!!
Click to expand...
Click to collapse
Actually not one person that has followed that guide has bricked, I have read every post in the thread seeing as I am the one who made the guide and the brick percentage is at zero. Why call people who make ROMs for others to use lazy? They create ROMs on their own time for free so that others can enjoy them. I really dont see the need to do extra work every time you flash something when you can simply flash the Danger SPL correctly one time and then you will be fine. As far as incompatibility goes I dont really see why that matters its no one right to be able to flash a certain ROM. If they want to use a ROM that requires a different SPL then flash the SPL if you dont want to flash the SPL no one is forcing you to just use a different ROM its as simple as that. The devs on here work for free and they are free to make requirements for their ROMs if people dont like that then they wont use that devs ROM but as you may know many people have been willing to switch SPLs to use a certain ROM.

You are definitely dense.
IT IS NO EXTRA WORK!!! I just PROVED it to you!
And I call them LAZY because they ARE.

lbcoder said:
Just run that on every update.zip that you feel like installing!!!
Click to expand...
Click to collapse
lbcoder said:
You are definitely dense.
IT IS NO EXTRA WORK!!! I just PROVED it to you!
And I call them LAZY because they ARE.
Click to expand...
Click to collapse
I could be wrong but running a script every time you update seems like extra work to me even though it maybe trivial and easy to do so is flashing an SPL one time. If they were lazy they wouldnt be cooking ROMs for anyone. I could say that anyone who doesnt want to simply flash an SPL is also lazy, but its just their choice not to just like its the devs choice to not do extra work to make their ROM not require a certain SPL. Its very simple you dont want want to flash the SPL then dont and dont use any ROMs that require it. If you do want to flash the SPL then just follow the How-To and you will be fine. There is no sense in arguing about it there hasnt been a Haykuro brick from anything besides flashing an old radio, so simply dont flash an old radio and you wont brick, very simple.

z4mod for the Tab

Hi guys.
I know that the z4mod can successfully patch a Tab kernel, without any problems (I did it myself, flashed it, and ran it just fine for a few days).
But when I tried to run one of the zip files to switch the file system, everything went nuts and I had to reflash my Tab from scratch.
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
So if anyone around here knows anything about this sort of business, please take a look at it and let me/us all know, cuz it would be GREAT to get z4mod working on the Tab.
Here's the web site if anyone's interested;
http://www.sgscompilebox.dreamhosters.com/

Hi, did you tell ryanZA what results you got? I'm sure he'll be interested to help.
However, thank you for trying, I was about to do the same.

Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?

knightnz said:
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
Click to expand...
Click to collapse
RFS is Samsung's partition format (FAT + journal) that is supposed to be better for flash devices. Apparently it is not so good, and very laggy. Therefore people are switching partitions to ext2/3 or moving and linking stuff to SD card with ext2/3 or jffs2 partition.

jeebspawnshop said:
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
Click to expand...
Click to collapse
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Fyi: http://forum.xda-developers.com/showthread.php?p=9629477#post9629477

doloop said:
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Click to expand...
Click to collapse
It has been tested by many Galaxy S users. Go to their forum and you will know

evermick said:
It has been tested by many Galaxy S users. Go to their forum and you will know
Click to expand...
Click to collapse
I'm really newb on linux, but i've read a little since last post.
What if we:
1 - dump mount list from a working SGT (terminal or adb shell -> mount ?)
2 - apply Z4mod then SGT won't boot (i assume it creates /etc/.fstab)
3 - edit /etc/fstab to match the dump in step 1
But, how do we read/write /etc/fstab once the sgt is locked ? using some kind of update.zip, or is there some shell service we could connect to, even if some mounts aren't in the right place ?

Unfortunately, everything I could contribute to this idea was in my first post. I know absolutely nothing about Android development, sadly...
But after reading what Deodexed said about volumes not mounting properly during recovery (he's the guy trying to get CWM to work for our Tabs) it seems that maybe that's the reason that z4mod may not work... If the volumes aren't mounted correctly, it can't convert the filesystems.
Maybe what doloop said might work? I hope so. An SGT running on ext2 would rock the socks off anything else out there. God I want it

[Q] Accidentally deleted photos! Need G2 /dev/block userdata partition to recover.

Hey Guys.
Help! I Accidentally deleted my vacation photos I am planning to use the method described here. For that I need to know /dev/block userdata partition.
Any other method too is welcome.
Any help will be massively appreciated :good:
Thanks.

Try this, might still work. http://forum.xda-developers.com/showthread.php?t=1514286

nowetdio said:
Try this, might still work. http://forum.xda-developers.com/showthread.php?t=1514286
Click to expand...
Click to collapse
The link I posted in the OP uses Recuva too..Just that to make it work, u need to make a VHD or a RAW image of ur data partition and I am not sure what the data partition block on the G2 is. If our phones were to appear as a drive letter, not as MTP there are tons of recovery tools I can use but from ICS onwards, this is no longer possible.

[Q]Rooting & File Recovery

Hi,
Trying to help a friend recover files (media) that were accidentally deleted on the sm-g900a. To recover those files, all signs indicate that rooting is necessary.
She tried using towelroot without mod, but it failed. I'm guessing she updated sometime in the past. So I'm guessing to root, she'll need to follow the steps (rather, I'll have to follow the steps since it might be a bit much for said friend) in the Root Guide on the General page.
(https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196)
**Q: Once the steps are complete - ie flashing the experimental firmware/OF3- will the chances of file recovery lessen (media files)? (ie will flashing the new firmware(s) override hard drive space that was occupied by said deleted files?) My first guess is minimal, since I'm guessin that part of the hard drive that'll be re-written are mainly the /system and /data files. I'm thinking about this like a traditional HD. But since this isn't my phone, I'd like to get second opinions.
**Q: She's not a tech person so any hitches w/r/t the new stock will be a hassle. Are there any glitches in the no-ship OF3? If so, I'm guessing flashing firmware from sammobile will remedy the problem. (root after this will not be necessary)
***Q: An afterthought. (It's been a while since I've flashed a phone w/ files I cared about. I'm pretty sure they aren't buuuttt) Will the files in /[user] directory affected with the flashes? (eg /sdcard, /internal (however the nomenclature works on the S5. Not the actual Sdcard)

alljokingaside said:
Hi,
Trying to help a friend recover files (media) that were accidentally deleted on the sm-g900a. To recover those files, all signs indicate that rooting is necessary.
She tried using towelroot without mod, but it failed. I'm guessing she updated sometime in the past. So I'm guessing to root, she'll need to follow the steps (rather, I'll have to follow the steps since it might be a bit much for said friend) in the Root Guide on the General page.
(https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196)
**Q: Once the steps are complete - ie flashing the experimental firmware/OF3- will the chances of file recovery lessen (media files)? (ie will flashing the new firmware(s) override hard drive space that was occupied by said deleted files?) My first guess is minimal, since I'm guessin that part of the hard drive that'll be re-written are mainly the /system and /data files. I'm thinking about this like a traditional HD. But since this isn't my phone, I'd like to get second opinions.
**Q: She's not a tech person so any hitches w/r/t the new stock will be a hassle. Are there any glitches in the no-ship OF3? If so, I'm guessing flashing firmware from sammobile will remedy the problem. (root after this will not be necessary)
***Q: An afterthought. (It's been a while since I've flashed a phone w/ files I cared about. I'm pretty sure they aren't buuuttt) Will the files in /[user] directory affected with the flashes? (eg /sdcard, /internal (however the nomenclature works on the S5. Not the actual Sdcard)
Click to expand...
Click to collapse
Okay I'll try to go in order here.
1. flashing the new firmware might lessen the chances of file recovery. I'm not exactly sure how NAND chips work, so the problem might be that it zeroes all the sectors out (unlikely) or it just uses a file index and the entries are erased. So proceed at your own risk, if the files are already lost there isn't much more to lose at this point anyway.
2. the pre-rooted OF3 is just the entire OF3 stock system but with the su files inside. Everything else is the same, so you shouldn't have any problems.
3. I'd guess no, but take that with a grain of salt since I've never really checked.
Any other questions, feel free to ask. Good luck!

AptLogic said:
Okay I'll try to go in order here.
1. flashing the new firmware might lessen the chances of file recovery. I'm not exactly sure how NAND chips work, so the problem might be that it zeroes all the sectors out (unlikely) or it just uses a file index and the entries are erased. So proceed at your own risk, if the files are already lost there isn't much more to lose at this point anyway.
2. the pre-rooted OF3 is just the entire OF3 stock system but with the su files inside. Everything else is the same, so you shouldn't have any problems.
3. I'd guess no, but take that with a grain of salt since I've never really checked.
Any other questions, feel free to ask. Good luck!
Click to expand...
Click to collapse
Thanks! Said friend got freaked out w the idea if flashing firmware. Boop

Hard bricked my RP2, need some assistance from someone with a working rooted RP2.

I recently hard bricked my Razer Phone 2(bootloader locked, but the OS got corrupted, and can no longer access recovery), and I need some help from a person with a working, rooted RP2. I found this guide for unbricking phones using an SD card(for those that want to see the guide, the link is here), but it requires information from a working version of the RP2.
For anyone interested in helping, here are the steps:
You will need:
Razer Phone 2(obviously)
SD Card(at least 64+ GB)
Root
Terminal Emulator(on the play store)
Busybox(link here)
Steps:
0.) Clean up your files. The finished file will have your entire internal storage within it. I don't wanna see any weird stuff(also clean your SD card and ensure it is exFAT; this file is going to be very big).
1.) Place the SD card into your RP2.
2.) Start up Busybox and install dependencies.
3.) Start up Terminal Emulator, and type this in:
su
Click to expand...
Click to collapse
4.) Then type this in:
ls /storage
Click to expand...
Click to collapse
5.) Find a hexadecimal set of numbers and letters(for example: 7368-9BEE); keep track of that set of numbers for now, as it is the name of your SD card.
6.) Then type this in(fill in [NAME OF YOUR SD CARD] with the set of numbers you found from step 5):
dd if=/dev/block/mmcblk0 of=/storage/[NAME OF YOUR SD CARD]/Loader.img
Click to expand...
Click to collapse
7.) Wait until the process is done(WILL MOST LIKELY TAKE A LONG TIME; BE PATIENT).
8.) If you see a "Loader.img" file in your SD card(may be around 60+ GB), you're done.
9.) Copy the file to your computer. It should be very large.
For those that complete it, I would be grateful if you could share the file(through Google Drive or MEGA) so that I can use it to unbrick my Razer Phone 2. Thanks.

Possible solution
Hey, I also have a bricked RP2. I'm getting in touch with a friend of mine who also has one to see if his is rooted. If it works out, I'll post the files for you. Thanks for the link.

TBurn420 said:
Hey, I also have a bricked RP2. I'm getting in touch with a friend of mine who also has one to see if his is rooted. If it works out, I'll post the files for you. Thanks for the link.
Click to expand...
Click to collapse
I honestly just sold off my RP2 for parts awhile ago and just used the money to buy a cheap flagship. I hope this method does work for you though.

TBurn420 said:
Hey, I also have a bricked RP2. I'm getting in touch with a friend of mine who also has one to see if his is rooted. If it works out, I'll post the files for you. Thanks for the link.
Click to expand...
Click to collapse
I'm still in the same situation Generic123 was in. I'd really appreciate those files, if you can share, Tburn420. I'm back on an older spare phone until I get this RP2 fixed. I'm sure it'll help others too.

I would also be grateful to need these files, otherwise I probably won't get my phone running

I have clean partition files, but rp2 don't have /dev/block/mmcblk0 (is used to sdcard) but he have other name sda, sde, etc.
I tried use theses files to revive my other rp2 (i have two rp2) but this method doesn't work
If someone have method to revive with sda, sde partitions, share please