Related
Are there any devs working on this? Can we get a dev to do this?
Just for those moments when we need to appear stock & bloated.
Please & thank you.
It's on the developers section. Buried though. It is posted by a drew guy.
Thanks, found his thread:
http://forum.xda-developers.com/showthread.php?t=1192670
(For anyone else looking)
Noiro said:
Thanks, found his thread:
http://forum.xda-developers.com/showthread.php?t=1192670
(For anyone else looking)
Click to expand...
Click to collapse
Cool, glad you found it.
If you s-offed and rooted, don't you already have the stock rooted ROM? Why download it again and overwrite the same thing that you already know works?
Mike
mikeyxda said:
If you s-offed and rooted, don't you already have the stock rooted ROM? Why download it again and overwrite the same thing that you already know works?
Mike
Click to expand...
Click to collapse
assuming you want an odex version, yes. if you want deodex, obviously the apk files in /system/app and some jar files might also be different.
the only other things i added to my stock rooted odex rom on the evo was busybox and a few dev linux arm binaries, like strace, tcpdump, etc.
for those who tinker a lot with their system, they might find themselves far away from the original s-off/rooted stock state and want a quick and easy way to return, hence the rooted stock ROM.
mikeyxda said:
If you s-offed and rooted, don't you already have the stock rooted ROM? Why download it again and overwrite the same thing that you already know works?
Mike
Click to expand...
Click to collapse
Maybe he flashed another Rom and wants to go back!!??
Stock system dump (this is not cwm flashable, this is for devs needing a base rom) all credit goes to drenner99
Deodex'd Version (cwm flashable)
this will allow themeing and your phone should run slightly faster
will someone please tell me what this does?
rj_22 said:
will someone please tell me what this does?
Click to expand...
Click to collapse
Nothing as of right now a dev has to cook a ROM using this as a base
Sent from my MB855 using xda premium
rj_22 said:
will someone please tell me what this does?
Click to expand...
Click to collapse
shabbypenguin said:
Stock system dump (this is not cwm flashable, this is for devs needing a base rom) all credit goes to drenner99
deodex version coming up here shortly
Click to expand...
Click to collapse
and here i thought i did...
It's just a system dump from the Motorola Electrify. It's more or less the same as our stock system dump.
Well let the rom making begin! I wanna root and flash my phone badly....but I dont wanna do it until there is a way I can go back to stock for warranty purposes.
deodex'd uploaded guys
shabbypenguin said:
deodex'd uploaded guys
Click to expand...
Click to collapse
shabbypenguin, the link you posted is password protected - fyi
thanks
shhhh no its not >.>
Thanks for the hard work, guys.
I wish I were able to make roms.
Unfortunately I'm running into an error when attempting to flash via cwm.
Getting status error 0.
:/
superuser in stock dump?
@shabbypenguin,
I was reading through your AIO root thread and it occurred to me that I had rooted prior to extracting the system dump that is posted in op as "Stock". Therefore, there is a version of superuser present in /app that I assume may not have been there as delivered. Of course, I may be making an incorrect assumption.
Is it appropriate then to call this stock, or is it a given that rooting would have been necessary to perform the dump in the first place?
I also don't know if this would affect your deodexed version?
Just wondering if this fact needs to be mentioned somewhere, unless I just did.
b4ifuru18 said:
Unfortunately I'm running into an error when attempting to flash via cwm.
Getting status error 0.
:/
Click to expand...
Click to collapse
It's says in op that you can't flash using cwn
Sent from my MB855 using xda premium
First off, thanks for all your efforts to provide us with this...
Second, root is a requirement for the dump and so even with the Superuser app, what you supplied is most definitely stock.
Unless of course you deleted anything in /system/ prior to the dump...
drenner99 said:
@shabbypenguin,
I was reading through your AIO root thread and it occurred to me that I had rooted prior to extracting the system dump that is posted in op as "Stock". Therefore, there is a version of superuser present in /app that I assume may not have been there as delivered. Of course, I may be making an incorrect assumption.
Is it appropriate then to call this stock, or is it a given that rooting would have been necessary to perform the dump in the first place?
I also don't know if this would affect your deodexed version?
Just wondering if this fact needs to be mentioned somewhere, unless I just did.
Click to expand...
Click to collapse
edward.hidalgo said:
It's says in op that you can't flash using cwn
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
I'm referring to the stock deodex that is cwm flashable according to shabby.
Beach_Head said:
First off, thanks for all your efforts to provide us with this...
Second, root is a requirement for the dump and so even with the Superuser app, what you supplied is most definitely stock.
Unless of course you deleted anything in /system/ prior to the dump...
Click to expand...
Click to collapse
Nothing was deleted
and thank you for your guidance in helping to get this done...
b4ifuru18 said:
I'm referring to the stock deodex that is cwm flashable according to shabby.
Click to expand...
Click to collapse
This is simply a stock from from the Photon's "sister," the Electrify. No one has even identified if there are any benefits/improvements hidden inside this ROM, much less how compatible it is with the Photon.
Just because something IS flashable doesn't mean you SHOULD flash it. OP was very clear - this is for devs only, not public consumption. If you don't know enough, then you're better off exercising some patience and waiting for further announcements.
actually im gunna guess that the man has an electrify and my cwm script is busted
I would venture to guess that you guys will have the same issue we do with the photon roms. As other members on my team verified that root, recovery, kernel and unlock work from the photon. The kernel needed wifi fixed which was pretty simple. In which I pm'd shabby about earlier. The roms also work but some things need fixed to get it working.
I don't know all the details besides what weasel told myself. But mms, 3g I believe works but going back to stock it wouldn't, eri says sprint, blur e-mail fc's and activation for sprint kept popping up to where you have to skip it. Weasel has fixed most of the stuff in the homebase port. I believe e-mail still fc's and mms is still broke.
But here is the first deodex rom weasel and myself did if you want to add it to the first post. http://2fastroms.com/viewtopic.php?f=116&t=265
Then here is the kernel shabby did with wifi fixed ready to install. Only rc-1 since wifi was broke in rc-2. If the electrify people want to install it just grab it from shabby's thread. There was reports of 3000's+ in bench's. Not sure of rom it was on but I would venture to guess our stock rom. http://2fastroms.com/viewtopic.php?f=118&t=334
Then here is the port for homebase weasel is playing with http://2fastroms.com/viewtopic.php?f=116&t=268 if you guys wanted to look at it.
i would gather a lot of frameworks issues, as with services.jar would happen between the phones.
edit: you keep saying you fixed wifi. but the only way to fix it, is by rebuilding the modules using my config file.. which only i have...
unless im missing some other way to replace it?
My Amaze has never been rooted or s=off but I did flash the ICS leak.
My question is if my main want is all the blue in ICS would an AOSP ROM be the only way of achieving that?
As far as I have seen launchers never seem to have any affect on the look of the status icons/notification bar.
Thanks ahead of time for your helpful answers.
http://forum.xda-developers.com/showthread.php?t=1620331
should be updated today with more things themed.
superevilllama said:
http://forum.xda-developers.com/showthread.php?t=1620331
should be updated today with more things themed.
Click to expand...
Click to collapse
Excellent! Is something I can flash while remaining stock or can themes only be flashed on rooted devices?
pavoid said:
Excellent! Is something I can flash while remaining stock or can themes only be flashed on rooted devices?
Click to expand...
Click to collapse
This does requires a rooted device in order to flash it from recovery, but a stock ICS rom is fine. It works on an odexed rom as well since the files are not modifying anything odexed.
superevilllama said:
This does requires a rooted device in order to flash it from recovery, but a stock ICS rom is fine. It works on an odexed rom as well since the files are not modifying anything odexed.
Click to expand...
Click to collapse
superv, you have been quite helpful. I am a bit scared of rooting my phone but I am going to try and take the plunge. I am the type of person that even though binary's "how to" guide might be considered very detailed to most people. For me I have no previous experience with many of the steps that are detailed. I have never "pushed an sdk" used an "all-in-one toolkit" and so on, so I would, out of paranoid instinct, be questioning everything until I got to do it successfully once myself.
Long time lurker, first time poster
Is there a way to stay stock and just do the menu button mod to get rid of that stupid bar at the bottom of the screen? I don't want to flash a new rom just yet.
Thanks in advance......
Evo1979 said:
Long time lurker, first time poster
Is there a way to stay stock and just do the menu button mod to get rid of that stupid bar at the bottom of the screen? I don't want to flash a new rom just yet.
Thanks in advance......
Click to expand...
Click to collapse
Fully stock, meaning unrooted and locked? No.
If you root, unlock, and load twrp recovery, you can flash the deodexed stock rom from this thread, then flash Runandhide05's zip from this thread (the second one down is the one you're looking for, I think). That will still give you the pure stock experience, but with the mod you're looking for.
Thanks. I figured that I would have to root but I wasn't sure if I could just mod the stock rom or if I need to flash another one.
Thanks again for the answer.
I think the issue is the stock rom is not deodex. The mod requires a deodex rom or someone needs to make the mod compatible with odex, which I have no clue if that's possible.
It was 95% of the reason I decided to unlock my phone sooner than I was planning. The mod really does feel like the way HTC designed the phone to work but then was strong armed into going in the direction they ended up.
i thought he could just root the phone.. not unlock the bootloader.. just root and then u can use root explorer.. am i wrong
evo401 said:
i thought he could just root the phone.. not unlock the bootloader.. just root and then u can use root explorer.. am i wrong
Click to expand...
Click to collapse
You are wrong.
Evo_Shift said:
I think the issue is the stock rom is not deodex. The mod requires a deodex rom or someone needs to make the mod compatible with odex, which I have no clue if that's possible.
It was 95% of the reason I decided to unlock my phone sooner than I was planning. The mod really does feel like the way HTC designed the phone to work but then was strong armed into going in the direction they ended up.
Click to expand...
Click to collapse
Is the right answer.
evo401 said:
i thought he could just root the phone.. not unlock the bootloader.. just root and then u can use root explorer.. am i wrong
Click to expand...
Click to collapse
I was kinda thinking the same thing. But while you can put a modded apk like systemUI in an odex ROM, and just delete the associated odex file, and you can edit the keypress in the kl file with root explorer, apparently part of the mod is in android.policy.jar, which , apparently you'll need to be deodexed to use the existing modded one.
sent from a shining jewel 4g LTE
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.