Sorry about the files being split, if somebody wants to get them and mirror an unsplit version I would appreciate it.
It looks like you may be able to get both pieces at once by checking the check box once you get to the site, I guess that make it a little more convenient.
These are for UNLOCKED devices only.
Here is the US stock .28 rom from Asus, repackaged for unlocked devices. - MD5: 305346D0CC4C20F37C13085E02B29F8B
Piece 1 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!211
Piece 2 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!210
Here is the same US, except pre-rooted - MD5: C5DF23E2A3E848EE190D1F66EA52E26C
Piece 1 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!216
Piece 2 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!215
Here is the US kernel - MD5: EFF266D90BE3E228DC182A3F36C32C06
https://skydrive.live.com/redir?resid=DC89975E3CE960E5!207
Here is WW stock .28 rom - MD5: B197410861EBC67CFD6D64748F575267
Piece 1 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!214
Piece 2 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!213
Here is the same WW, except pre-rooted - MD5: AD3F563AB796C73DF11597D33EEB8283
Piece 1 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!218
Piece 2 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!217
Here is the WW kernel - MD5: 0F4316AA1CB043D463E57438279649F2
https://skydrive.live.com/redir?resid=DC89975E3CE960E5!212
If you have already flashed one without root and would like to use CWM to flash just the root piece, here is a link to that:
http://goo-inside.me/superuser/Superuser-3.0.7-efghi-signed.zip
Would you be able to tell me the kernel version that shipped with .28? I'm on AndroWook 1.31 which comes with Motley's kernel and was just curious to see if any changes have been made to the stock source.
Deathbyfugu said:
Would you be able to tell me the kernel version that shipped with .28? I'm on AndroWook 1.31 which comes with Motley's kernel and was just curious to see if any changes have been made to the stock source.
Click to expand...
Click to collapse
I'm not sure how technical you are, but the kernel is mostly the same. There is 1 update to 1 file in the ramdisk. File "init.cardhu.rc" has this added at the very bottom:
service BtService /system/bin/sh /system/etc/BtService.sh
user root
group root
disabled
oneshot
sparkym3 said:
I'm not sure how technical you are, but the kernel is mostly the same. There is 1 update to 1 file in the ramdisk. File "init.cardhu.rc" has this added at the very bottom:
service BtService /system/bin/sh /system/etc/BtService.sh
user root
group root
disabled
oneshot
Click to expand...
Click to collapse
Thanks for the reply. I guess ASUS is attempting to improve Bluetooth at the kernel level. I was also just wondering what the version of the linux kernel is (i.e. 2.6.39.4)
Deathbyfugu said:
Thanks for the reply. I guess ASUS is attempting to improve Bluetooth at the kernel level. I was also just wondering what the version of the linux kernel is (i.e. 2.6.39.4)
Click to expand...
Click to collapse
Kernel version number did not change.
sparkym3 said:
Sorry about the files being split, if somebody wants to get them and mirror an unsplit version I would appreciate it.
It looks like you may be able to get both pieces at once by checking the check box once you get to the site, I guess that make it a little more convenient.
Here is the US stock .28 rom from Asus, repackaged for unlocked devices.
Piece 1 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!211
Piece 2 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!210
Here is the same, except pre-rooted
Piece 1 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!208
Piece 2 = https://skydrive.live.com/redir?resid=DC89975E3CE960E5!209
Here is the kernel
https://skydrive.live.com/redir?resid=DC89975E3CE960E5!207
Click to expand...
Click to collapse
I really appreciate this. You were the one who mentioned you would do it when the update was released and you held true to your word. I admire that immensely. Anyways, couple Q's: Can you do the WW version as well? And I am assuming these are odexed, correct?
pinky059 said:
I really appreciate this. You were the one who mentioned you would do it when the update was released and you held true to your word. I admire that immensely. Anyways, couple Q's: Can you do the WW version as well? And I am assuming these are odexed, correct?
Click to expand...
Click to collapse
Yeah, I will do a WW version as well, but I am not set up to do the pre-rooted version on this computer. So, I will have to do that later tonight when I get home.
Yay, .28 pre rooted for my lazy self ;D
WW version is up, pre-rooted WW will be up later.
I purchased my Asus Transformer Prime from eBay and it came with the boot loader unlocked (and not described as such) so I'm being forced into learning a little more than I'd like to.... ;-)
I was waiting for the update and wasn't getting it so I did some reading. Is it correct that since the boot loader is unlocked I won't get OTA updates? How do I install the update from the files provided above?
Thanks for your time, I appreciate the help!
I'm installing it now. Had some issues with CWM disappearing off my Prime, had to reinstall it and now I'm rolling.
I'll let you know how it goes.
ATTENTION
Anybody who has downloaded the US pre-rooted version. I added the su files to the image but forgot to set the permissions. I am currently rebuilding it with the corrected permissions. If you flash this version it will not hurt your device, but you will not have root by default. Sorry for the inconvenience.
Its telling me that your pre-rooted ROM isn't rooted.
edit : I guess that's why lol. Hope it gets fixed soon, wife is yelling at the kids working her way to me.
bleclair said:
I was waiting for the update and wasn't getting it so I did some reading. Is it correct that since the boot loader is unlocked I won't get OTA updates? How do I install the update from the files provided above?
Thanks for your time, I appreciate the help!
Click to expand...
Click to collapse
That is correct. No OTA update with an unlocked bootloader. The eBay seller misrepresented the item and you certainly have grounds to demand a refund if you're not happy about it. On the other hand life here (on the dark side) sure is wonderful. ;-)
Can't wait to get the stock pre rooted. Thanks for doing this mate.
sbdags said:
Can't wait to get the stock pre rooted. Thanks for doing this mate.
Click to expand...
Click to collapse
US pre-rooted is back up and it should have to correct permissions this time.
Thank you for your work on this. Much appreciated.
Got it figured out. Thanks, sparkym3.
bleclair said:
Got it figured out. Thanks, sparkym3.
Click to expand...
Click to collapse
Sorry I didn't respond. I must have missed your post.
sparkym3 said:
Sorry I didn't respond. I must have missed your post.
Click to expand...
Click to collapse
Thanks for doing the WW version. I am waiting patiently for the rooted version even though I could probably just flash it and then flash superuser apk and binary. I will wait....
Related
This Rom is no longer available at XDA due to XDA moderator double standards.
been waiting for something like this. Ever since I unlocked my prime, I thought I would be getting CM9 but since they arent that stable I am actually wishing I waited!
But since there are awesome devs out there keeping my device up to date, i cant complain.
Anyways, thanks again!
Sent from my Transformer Prime TF201 using xda premium
jetbruceli said:
been waiting for something like this. Ever since I unlocked my prime, I thought I would be getting CM9 but since they arent that stable I am actually wishing I waited!
But since there are awesome devs out there keeping my device up to date, i cant complain.
Anyways, thanks again!
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
YW bro!
WW or US
Looking at your screenshots i notice it states:
IML74K.WW_epad-9.4.2.21-20120323
I noticed that because i would like such a ROM but then the WW version.
Which is this one? US as the thread states?
Is it deodexed?
If not, to be fair, this is no different to the blob version in then other thread. How the payload is delivered is irrelevant, it's still the same result.
Can't theme it if it's odexed, perhaps you could differentiate on that?
djmcnz said:
Is it deodexed?
If not, to be fair, this is no different to the blob version in then other thread. How the payload is delivered is irrelevant, it's still the same result.
Can't theme it if it's odexed, perhaps you could differentiate on that?
Click to expand...
Click to collapse
Not the exact same result (already Rooted and Busybox installed) but in a more standardized-CWM manner.
And I think you should read about deodex/odex ROM here:
http://forum.xda-developers.com/showpost.php?p=24450807&postcount=275
Striatum_bdr said:
Not the exact same result (already Rooted and Busybox installed) but in a more standardized-CWM manner.
And I think you should read about deodex/odex ROM here:
http://forum.xda-developers.com/showpost.php?p=24450807&postcount=275
Click to expand...
Click to collapse
Thanks for the link, assuming it's true I learnt something there.
The point I'm making is that the other ROM is ALSO rooted with busybox, with CWM install. How are they different, that's what I'm asking?
djmcnz said:
Is it deodexed?
If not, to be fair, this is no different to the blob version in then other thread. How the payload is delivered is irrelevant, it's still the same result.
Can't theme it if it's odexed, perhaps you could differentiate on that?
Click to expand...
Click to collapse
As stated in the post above, you really should read up on odexed vs. deodexed. No offense intended bro.
You can theme Odex very easily.
Here is a case in point.
http://forum.xda-developers.com/showthread.php?t=1532640
Five ROMs, all themed, one is deodexed, four are odexed.
You can't theme or modify a blob until you unpack the blob itself.
rveupen said:
Looking at your screenshots i notice it states:
IML74K.WW_epad-9.4.2.21-20120323
I noticed that because i would like such a ROM but then the WW version.
Which is this one? US as the thread states?
Click to expand...
Click to collapse
checking right now to see how the build.prop from the ww version made it into the US version. I was working with 6 different ROMs. Give me just a few more to check it out
djmcnz said:
Thanks for the link, assuming it's true I learnt something there.
The point I'm making is that the other ROM is ALSO rooted with busybox, with CWM install. How are they different, that's what I'm asking?
Click to expand...
Click to collapse
Sorry, I was in the middle of checking up on a build.prop issue while typing a response, and you responded yet again.
See my previous post on the subject.
They're different in that this ROM is still in blob format, which can't be modified until unpacked. This ROM is here for others to use as a base for their builds if they so wish, or for those that want a completely stock ROM, nothing more.
But with this ROM (once again), no unpacking from blob format is needed
rveupen said:
Looking at your screenshots i notice it states:
IML74K.WW_epad-9.4.2.21-20120323
I noticed that because i would like such a ROM but then the WW version.
Which is this one? US as the thread states?
Click to expand...
Click to collapse
Sorry it took so long. THANK YOU for catching that. It is indeed the WW version that I uploaded by mistake. US Version is being uploaded this very minute and will post link in this thread as soon as it's done. Once again, my apologies!
04/10/12
Uploading US Version NOW
Re Uploading WW Version Now
Guys,I have a question,I bought my prime in the USA.I upgraded it to the latest original software from ASUS ofcourse.Since I really like custom roms,I decided to unlock and root my prime.Installed primalicious (not the USA version),which is a great rom.However since than it seems that I cannot use my VPN anymore.Also I noticed that not all networks are reachable anymore for me.I have the feeling that something got stuck in the modem(wifi)software.Do any of you guys know what the problem might be?I would very much appreciate some pointers.
This was too good to be true
"This file is either removed due to copyright claim or is deleted by the uploader."
says mine
Sent from my Transformer Prime TF201 using Tapatalk 2
Vanto said:
This was too good to be true
"This file is either removed due to copyright claim or is deleted by the uploader."
says mine
Sent from my Transformer Prime TF201 using Tapatalk 2
Click to expand...
Click to collapse
Re uploading now. Sorry for the inconvenience
04/10/12
US Version is uploaded and link updated!
Re Uploading WW Version Now
ATGAdmin said:
Sorry it took so long. THANK YOU for catching that. It is indeed the WW version that I uploaded by mistake. US Version is being uploaded this very minute and will post link in this thread as soon as it's done. Once again, my apologies!
Click to expand...
Click to collapse
Dude...no need to apologize...i appreciate your work.
Thx for clearing it up anyway....and with the speed most parcel deliveries are jealous of.
IF you need a mirror i can give you sapce...just dont have a counter or anything...space and speed...thats all.
rveupen said:
Dude...no need to apologize...i appreciate your work.
Thx for clearing it up anyway....and with the speed most parcel deliveries are jealous of.
IF you need a mirror i can give you sapce...just dont have a counter or anything...space and speed...thats all.
Click to expand...
Click to collapse
That would be great bro!
I could use some mirrors for this ROM anyway, and I don't need counters on this ROM (it's just a bone stock ROM for others to install or modify for creating ROMs).
PM me the details if you would please? And thank you!
04/10/12
US Version is uploaded and link updated!
WW Version is uploaded and link updated!
When people say to not try to go back to stock after unlocking/flashing a custom ROM, I assume they mean don't install Asus official firmware. Will I be OK to flash this? I've tried all the custom ROMS and they're all great but all have some sort of problems. I'd like to try this stock ROM with just over clock.
Could somebody with the TW ROM post the JB dlpkgfile?
Many thanks!
Fizzerr said:
Could somebody with the TW ROM post the JB dlpkgfile
Many thanks!
Click to expand...
Click to collapse
I couldn't find anyone with it, but here's the solution http://forum.xda-developers.com/showthread.php?p=32156572#post32156572
First you're supposed to flash an official blob (either WW or US version,it doesn't matter), then proceed to download the corresponding JB update and you're good to go!
Notes;
You don't need to be unlocked but you need root and busy box installed
There's always a risk of bricking your device following anyone of these procedures
Remember to have your root backed up using Voodoo
justcookiesncream said:
I couldn't find anyone with it, but here's the solution http://forum.xda-developers.com/showthread.php?p=32156572#post32156572
First you're supposed to flash an official blob (either WW or US version,it doesn't matter), then proceed to download the corresponding JB update and you're good to go!
Notes;
You don't need to be unlocked but you need root and busy box installed
There's always a risk of bricking your device following anyone of these procedures
Remember to have your root backed up using Voodoo
Click to expand...
Click to collapse
The only problem with flashing a different SKU is that you'll never be able to receive OTA updates again...
If ASUS doesn't do anything about the update problem in the next few days, though, I'll switch anyway. I've tried re-flashing the TW .28 ROM, data wipe, rerooting and unrooting after backing up SU, and clearing DMClient and CMClient caches, all to no effect. I always end up with the "Failed to download the file" error.
Danforth said:
The only problem with flashing a different SKU is that you'll never be able to receive OTA updates again...
If ASUS doesn't do anything about the update problem in the next few days, though, I'll switch anyway. I've tried re-flashing the TW .28 ROM, data wipe, rerooting and unrooting after backing up SU, and clearing DMClient and CMClient caches, all to no effect. I always end up with the "Failed to download the file" error.
Click to expand...
Click to collapse
Well... That's what came to mind but whenever an update comes someone would probably have it posted up on xda (mostly WW and US) and changing the SKU would just mean that we'd get better compatible support since the WW and US versions are more widespread
On a side note I got the dock update as soon as I docked my keyboard after 4.1 :fingers-crossed: so that doesn't completely rule out the possibility that we wouldn't be supported with anymore Asus updates
Fizzerr said:
Could somebody with the TW ROM post the JB dlpkgfile?
Many thanks!
Click to expand...
Click to collapse
Here you are:
TW JB dlpkgfile
CRC32: 7C828B02
MD5: 9259363BC2A20558ABB635515E979076
SHA-1: FC339F2FB67693D642BC5425E2B0940E152D7D17
I have downloaded once and ensure the file is identical to my local file
Hey thanks! In the meantime I flashed the US JB ROM. All working well so far.
Cheers.
update fail
sh: cp: not found after typing cp /mnt/sdcard/dexdump /system/xbin/dexdump
please help me:crying:
ChungWingKeung said:
sh: cp: not found after typing cp /mnt/sdcard/dexdump /system/xbin/dexdump
please help me:crying:
Click to expand...
Click to collapse
Install BusyBox using BusyBox Installer from the market
lineager said:
Here you are:
TW JB dlpkgfile
CRC32: 7C828B02
MD5: 9259363BC2A20558ABB635515E979076
SHA-1: FC339F2FB67693D642BC5425E2B0940E152D7D17
I have downloaded once and ensure the file is identical to my local file
Click to expand...
Click to collapse
Thanks lineager. Unfortunately for me, my Prime started to download the OTA update hours earlier, and thinking based on other users' posts that OTA Root Keeper would be up to the task, I just let the regular update process proceed. Found out the hard way that it only could restore partial root. So I actually got punished for doing it the Asus way, instead of using dlpkgfile... I have seen the thread of restoring full root, but I don't have the knowledge to understand it. I'd just be parroting it step by step, hoping I didn't make a mistake...
Sucks because I pretty much need root to use apps like Facebook or Twitter here in China (because I need to use a VPN app to get around the Great Firewall). Ah well, at least I can use this dlpkgfile to help one of my Chinese Prime-owning friends.
lineager said:
Here you are:
TW JB dlpkgfile
CRC32: 7C828B02
MD5: 9259363BC2A20558ABB635515E979076
SHA-1: FC339F2FB67693D642BC5425E2B0940E152D7D17
I have downloaded once and ensure the file is identical to my local file
Click to expand...
Click to collapse
OMG! You just saved me a heap of time.
Was planning to go through the SKU change.
Thanks mate.
lineager said:
Here you are:
TW JB dlpkgfile
CRC32: 7C828B02
MD5: 9259363BC2A20558ABB635515E979076
SHA-1: FC339F2FB67693D642BC5425E2B0940E152D7D17
I have downloaded once and ensure the file is identical to my local file
Click to expand...
Click to collapse
Lineager, THANK YOU VERY MUCH!!!! Have successfully upgraded to 4.1.1 with your dlpkgfile!
Danforth said:
Thanks lineager. Unfortunately for me, my Prime started to download the OTA update hours earlier, and thinking based on other users' posts that OTA Root Keeper would be up to the task, I just let the regular update process proceed. Found out the hard way that it only could restore partial root. So I actually got punished for doing it the Asus way, instead of using dlpkgfile... I have seen the thread of restoring full root, but I don't have the knowledge to understand it. I'd just be parroting it step by step, hoping I didn't make a mistake...
Sucks because I pretty much need root to use apps like Facebook or Twitter here in China (because I need to use a VPN app to get around the Great Firewall). Ah well, at least I can use this dlpkgfile to help one of my Chinese Prime-owning friends.
Click to expand...
Click to collapse
About the VPN, I see there is an option under the Setting -> Wireless & Network -> More...
I also lost my root after following the way someone posted. :crying:
I hope a new way for Root the JellyBean Prime will come Soon!
can someone re-up the file. looks like the dropbox link exceed bandwidth..!! thanks
lineager said:
Here you are:
TW JB dlpkgfile
CRC32: 7C828B02
MD5: 9259363BC2A20558ABB635515E979076
SHA-1: FC339F2FB67693D642BC5425E2B0940E152D7D17
I have downloaded once and ensure the file is identical to my local file
Click to expand...
Click to collapse
Lineager,
would it be possible for you to re-up the TW JB DLPKGFILE?
Thanks
lineager said:
About the VPN, I see there is an option under the Setting -> Wireless & Network -> More...
I also lost my root after following the way someone posted. :crying:
I hope a new way for Root the JellyBean Prime will come Soon!
Click to expand...
Click to collapse
You might be lucky like me if you used OTA Root Keeper before the update. I used the method described by member thenrz in his thread "For those with 'partial root after JB update - regain root!", and it worked fine (though I had a heart attack at step 18a, which turned out not to be necessary for my machine). Now my Prime is fully rooted and should still be able to receive any future OTA updates. I hope that method works for you.
What a tech nightmare this has been, though. Not only did it take me days to download the OTA update, I spent a whole day trying to get root back -- the thenrz method wasn't the first one I tried. I tried repeatedly to downgrade back to .28 so that I could root/backup and use the dlpkgfile, but always failed. My mind was blown when manually pushing files worked on my first try -- it was like Murphy's Law was being violated.
I was using Android's built-in VPN support last year, but the government started blocking the commonly used PPTP and L2TP protocols, and so I have been using a free VPN app (DroidVPN) for a year now. Thanks for reminding me though, I just checked and JB has some new VPN settings that I will give a try.
shuweee said:
Lineager,
would it be possible for you to re-up the TW JB DLPKGFILE?
Thanks
Click to expand...
Click to collapse
2nd link.
http://d-h.st/kks
lineager said:
2nd link.
http://d-h.st/kks
Click to expand...
Click to collapse
thx a lot! will be added to Trekest's Method too..
Grz
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.
http://www.androidpolice.com/2014/0...droid-incredible-4g-lte-casio-gzone-commando/
http://support.verizonwireless.com/dam/support/pdf/system_update/droidincredible4glte.pdf
pmcall said:
http://www.androidpolice.com/2014/0...droid-incredible-4g-lte-casio-gzone-commando/
http://support.verizonwireless.com/dam/support/pdf/system_update/droidincredible4glte.pdf
Click to expand...
Click to collapse
pretty interesting ... so next will be: 2.19.605.2 710RD ... which is of course newer than our previous 2.17.605.2, but it doesn't give much hope for the expected JB release (3.16.605.1)
main changes (as per changelog dec-2013): ISIS support, Software Update and Software Repair Tools are now compatible (?? whatever that means!!), reduced power cycling, improved bluetooth clarity and ... security patches added
that's about it. will be interesting if ANY new custom roms are going to be based on the new release (a new Viper? ) ... but i suppose we still won't get any newer kernel, any JB love and/or updated Sense(4.5) ... as nothing of that is listed in the update announcement
EDIT: checked http://support.verizonwireless.com/support/system_update/droidincredible4glte.html for "benefits" (which is already updated to 2.19.605.2) and "instructions" for a hint on the size of the (this time for _real_ new OTA 2013/2014!) ... but as instructions are still based on our prev 2.17.605.2 update with its 155mb size, there isn't _any_ info yet on the size of the upcoming OTA. ........... and it seems that it was just less than 24hrs ago, when the news about the 2.19.605.2 update started to make its round in the net (and on the verizon page).
I run Viper rom and it keeps downloading and trying to install. Is there anyway to stop OTA from happening?
The viper OTA (about the faked illegal rom) has nothing to do with this
This info above is finally some news about an official OTA from Verizon! (albeit not the bigger JB update we are all still waiting for, but rather only a smaller Bugfix for our current ICS)
update size
according to my phone, the update is only 43.8MB.
I have now lost faith in seeing any real updates for this phone. I am ready to root and try a new ROM. What I'd like to know is if this update will break any of the methods for rooting this phone.
I know this phone isn't much, but for HTC to totally forget it like they have is rotten. I guess I'll have to follow the bandwagon to Samsung or Motorola.
DanPFW said:
according to my phone, the update is only 43.8MB.
I have now lost faith in seeing any real updates for this phone. I am ready to root and try a new ROM. What I'd like to know is if this update will break any of the methods for rooting this phone.
I know this phone isn't much, but for HTC to totally forget it like they have is rotten. I guess I'll have to follow the bandwagon to Samsung or Motorola.
Click to expand...
Click to collapse
it's HIGHLY LIKELY that ANY previous rooting method will not be working any more AFTER you agree to the new OTA.
@DanPFW: as for HTC, they had prepared a JB update and send it to Verizon ... it's just that Verizon didn't approve it (for some unknown to us reason!!!) ... even the release-number is known, just the actual ROM has not surfaced (yet?!) to the community.
as for rooting and a new custom-ROM ... it's a great and fun device and fairly easy to root & unlock. just that the fully working custom-roms _with_ HTC Sense are ALL only ICS4.0.4 with Sense4.1. Overclocking is easy and stable and a sweet kernel (from user: jose) is available. the newer JB-based custom-roms with Sense5 or Sense4.5 are all ported from different devices and are only partially working, as camera and bluetooth are _completely broken_ due to non-existing (Sense-kernel) drivers for JB. most ppl here are running either ViperLTE2.2.0 (best ICS with Sense4.1 imho) or some AOSP-based custom roms like CM, PacMan, Avatar etc, which are upto at least JB4.3.1 available and nicely working)
EDIT: I hope someone can capture this new OTA for 2.19.605.2 and provide the file here on xda ... for further "analysis"
new OTA package on my drop box
https://dl.dropboxusercontent.com/u/5271399/OTAPkg.zip
dcooterfrog said:
new OTA package on my drop box
https://dl.dropboxusercontent.com/u/5271399/OTAPkg.zip
Click to expand...
Click to collapse
thanks for the upload ... i just checked its content, but as it's mainly patchfiles (which i dun know how to apply manually to see what's changed) i can only confirm a couple of things for now:
* according to the updater script, it's still ICS4.0.4 ... but now "fireball:4.0.4/IMM76D/278117.2" (prev was: "fireball:4.0.4/IMM76D/111397.2")
* the actual patch-content size is only 15MB!
* whole new firmware package (32MB) ... incl a slightly newer radio: 1.53.06.1009 (was: 1.53.06.0919)
waiting for some more details about the actual OTA changes from others for now :fingers-crossed:
kimba99 said:
thanks for the upload ... i just checked its content, but as it's mainly patchfiles (which i dun know how to apply manually to see what's changed) i can only confirm a couple of things for now:
* according to the updater script, it's still ICS4.0.4 ... but now "fireball:4.0.4/IMM76D/278117.2" (prev was: "fireball:4.0.4/IMM76D/111397.2")
* the actual patch-content size is only 15MB!
* whole new firmware package (32MB) ... incl a slightly newer radio: 1.53.06.1009 (was: 1.53.06.0919)
waiting for some more details about the actual OTA changes from others for now :fingers-crossed:
Click to expand...
Click to collapse
yah I looked the update script
so the hfirware includes the radio. that mihgt make it worhthteh update IF WE CAN ROOT.
dcooterfrog said:
yah I looked the update script
so the hfirware includes the radio. that mihgt make it worhthteh update IF WE CAN ROOT.
Click to expand...
Click to collapse
yeah and additionally one needs the (previous) 2.17.605.2 installed ... and unmodified stock-rom to apply the patches (or is there a "offline" way, like on linux or so to apply them safely w/o needing to run it on a Dinc4G). but plz correct me if i'm wrong ^^
we just shouldn't execute/load the whole firmware.zip at once as it is (right now) ... as it might re-lock the bootloader and/or in the worst case even bricks _currently_ rooted/unlocked Dinc4Gs ... that's why I said, let's wait for "the specialists" to decompose the OTA and tell the "common ppl" what can be safely applied and what better shouldn't
kimba99 said:
yeah and additionally one needs the (previous) 2.17.605.2 installed ... and unmodified stock-rom to apply the patches (or is there a "offline" way, like on linux or so to apply them safely w/o needing to run it on a Dinc4G). but plz correct me if i'm wrong ^^
we just shouldn't execute/load the whole firmware.zip at once as it is (right now) ... as it might re-lock the bootloader and/or in the worst case even bricks _currently_ rooted/unlocked Dinc4Gs ... that's why I said, let's wait for "the specialists" to decompose the OTA and tell the "common ppl" what can be safely applied and what better shouldn't
Click to expand...
Click to collapse
i know I cant do it. that's why i posted it.
i know that the asserts nt eh script check each file (and odex) for the right hash before applying the patch.
kimba99 said:
The viper OTA (about the faked illegal rom) has nothing to do with this
This info above is finally some news about an official OTA from Verizon! (albeit not the bigger JB update we are all still waiting for, but rather only a smaller Bugfix for our current ICS)
Click to expand...
Click to collapse
I'm not that stupid. I run the Viper run and keep getting the download for the Verzion OTA. I thought the Viper rom was suppose to stop Vertizon OTA's, but I guess it hasn't. I just deferred it for now. Wait to see what happens with it, and if its worth while.
articzap said:
I'm not that stupid. I run the Viper run and keep getting the download for the Verzion OTA. I thought the Viper rom was suppose to stop Vertizon OTA's, but I guess it hasn't. I just deferred it for now. Wait to see what happens with it, and if its worth while.
Click to expand...
Click to collapse
afaik only ViperLTE2.2.0 removed the real Verizon OTA stuff ... it still is present in Viper2.1.1
kimba99 said:
afaik only ViperLTE2.2.0 removed the real Verizon OTA stuff ... it still is present in Viper2.1.1
Click to expand...
Click to collapse
damn, thanks!! :good:
Can we install it if running viper 211? I just got the message and deferred it for now... How can I cancel it if running viper 211?
j13smiley said:
Can we install it if running viper 211? I just got the message and deferred it for now... How can I cancel it if running viper 211?
Click to expand...
Click to collapse
I'm pretty certain it will mess up the ROM if you run the OTA. Viper 2.2 lets you turn off the check/reminder.
j13smiley said:
Can we install it if running viper 211? I just got the message and deferred it for now... How can I cancel it if running viper 211?
Click to expand...
Click to collapse
you probably wont be able to install it anyway. im pretty sure it needs a stock recovery to install it. if youre running viper youre more than likely running custom recovery.
Correct... I didn't think ota updates would actually install on phones running custom rom / recoveries
to get rid of the notifications... does the old trick of changing your build.prop work? i can just use this...
* according to the updater script, it's still ICS4.0.4 ... but now "fireball:4.0.4/IMM76D/278117.2" (prev was: "fireball:4.0.4/IMM76D/111397.2")
Click to expand...
Click to collapse
also looks like viper rom has a section in build.prop...
"ro.config.venum.enableCOTA=1"... if i change that to zero i wonder if it will stop the viper illegal rom nag (that thread got closed) (and yes i'm still on viper 211 so i don't have the option in settings to disable ota updates).
j13smiley said:
to get rid of the notifications... does the old trick of changing your build.prop work? i can just use this...
<snip>
also looks like viper rom has a section in build.prop...
"ro.config.venum.enableCOTA=1"... if i change that to zero i wonder if it will stop the viper illegal rom nag (that thread got closed) (and yes i'm still on viper 211 so i don't have the option in settings to disable ota updates).
Click to expand...
Click to collapse
I decided to just take this as an opportunity to finally upgrade to Viper 2.2.0. I wasn't looking forward to the full ROM install and the PITA that goes with it. Hooray for Nandroid backups and TiB!
If anyone else it thinking of doing the same, make sure you're using TWRP recovery. (Full Nandroid and full TiB backup first before doing anything!). The Aroma installer appeared to work when installing with a CWM-based recovery, but the phone hung up good upon reboot. I looked at the nice white HTC screen for quite a while :laugh:
This rom is deodexed, busybox and rooted (although root may need to be updated).
I made this with a kit kat kitchen I found. I did not intend this to be a "ROM" But a base that Dev's can make roms from.
https://www.androidfilehost.com/?fid=95916177934553556
FEEL FREE TO USE.
EDIT I JUST TESTED THIS WITH THE TWRP and it faild because of the script. I do not know how to fix but if someone else wants to try go for it
tjsooley said:
This rom is deodexed, busybox and rooted (although root may need to be updated).
I made this with a kit kat kitchen I found. I did not intend this to be a "ROM" But a base that Dev's can make roms from.
https://www.dropbox.com/s/fk0j7u7hinxxa8s/ASUS-T00D_signed_ATT_11.10.8.7.zip?dl=0
FEEL FREE TO USE.
Click to expand...
Click to collapse
BTW forgot to mention. This has the Padfone s bootanimation
I just wanted to say thank you for working on this device. I haven't decided if i will keep mine as the fried LTE radio thing has me worried, but I love the device and think more developers could have taken it to another level.
crash447 said:
I just wanted to say thank you for working on this device. I haven't decided if i will keep mine as the fried LTE radio thing has me worried, but I love the device and think more developers could have taken it to another level.
Click to expand...
Click to collapse
Welcome, Mine just needs to last till the Modular Phone from google is released and I can get my hands on it
Link seems to be broken. Can you kindly update? Thanks
magiconthetire said:
Link seems to be broken. Can you kindly update? Thanks
Click to expand...
Click to collapse
I will reupload. But warning. have a nandroid backup first. it may not work.
asus padfon x can not load invlid boot image
Hello I want to help My Asus Padfone x says :
Error: can not load invlid boot image
If you can help me
Thank you in advance