So I acquired a GTablet last night... and am looking to change the rom that's on it - however, the previous owner can't remember for certain which BL was originally listed and I want to figure it out before I do anything (granted, so long as I have my APX and such taken care of I can always go from soft brick back to working and will know which I have at that point)
My Question is:
Is it "safe" to assume it has the 1.1 bootloader since it has Cyanogenmod 7 (harmony) on it? Or is there another way to sort out what was originally on the device?
Yes, if it's running CM7 then you would be on the 1.1 bootloader. Might wanna give this thread and various other stickies a read through.
http://forum.xda-developers.com/showthread.php?t=1035983
Jboxmods said:
My Question is:
Is it "safe" to assume it has the 1.1 bootloader since it has Cyanogenmod 7 (harmony) on it? Or is there another way to sort out what was originally on the device?
Click to expand...
Click to collapse
See this thread.
rajeevvp said:
See this thread.
Click to expand...
Click to collapse
I get:
fgrep: permission denied
write: broken pipe
CM7 can be on BL 1.1 or BL 1.2, best way to burn a new ROM is to flash the tablet back to factory using Code Detox which will bring the tablet to BL 1.2, then you can use any of the nice BL 1.2 based ROMs.
http://viewsonic-gtablet-for-dummies.webs.com/
Read the Code Detox section.
Good luck.
tsukaza said:
CM7 can be on BL 1.1 or BL 1.2, best way to burn a new ROM is to flash the tablet back to factory using Code Detox which will bring the tablet to BL 1.2, then you can use any of the nice BL 1.2 based ROMs.
http://viewsonic-gtablet-for-dummies.webs.com/
Read the Code Detox section.
Good luck.
Click to expand...
Click to collapse
Thx... I love the nvflash devices (have the g2x).
So you recommend BL 1.2 over 1.1? I read in the BL thread that 1.2 was pulled and 1.1 was the more stable/preferred choice... with the newer roms is BL a moot point?
Most new ROMs are now based on BL (Boot Loader) version 1.2, so you will have a much larger choice on which ROM to try IMO.
This is the file I have been using the last few months.
gtab.nvflash.1.2.branch.20110508 with cwmv3028.zip
www.mediafire.com/?brd9u48iefdqcc7
Follow the gtablet for dummies instructions.
Good luck.
tsukaza said:
Most new ROMs are now based on BL (Boot Loader) version 1.2, so you will have a much larger choice on which ROM to try IMO.
This is the file I have been using the last few months.
gtab.nvflash.1.2.branch.20110508 with cwmv3028.zip
www.mediafire.com/?brd9u48iefdqcc7
Follow the gtablet for dummies instructions.
Good luck.
Click to expand...
Click to collapse
Yeah, I'm running Flashback 10.1 now... this tablet is sooooo much nicer now.
Thx everyone!
Jboxmods said:
I get:
fgrep: permission denied
write: broken pipe
Click to expand...
Click to collapse
Hmm--didn't the fgrep binary (ie. busybox) have the correct permissions on CM7?. You're now the second person who's reported that error. Can you run the same command on the current ROM and post the results?
rajeevvp said:
Hmm--didn't the fgrep binary (ie. busybox) have the correct permissions on CM7?. You're now the second person who's reported that error. Can you run the same command on the current ROM and post the results?
Click to expand...
Click to collapse
it doesn't do anything on my current rom (Flashback 10.1)
Jboxmods said:
it doesn't do anything on my current rom (Flashback 10.1)
Click to expand...
Click to collapse
You have to run the command line soon after you boot the tablet; if you wait longer the required line will get overwritten.
Related
Hi All,
I searched and searched, but can't figure out how to identify the bootloader. I bought this gtab off of craigslist and it has already been rooted to VEGAn-TAB-v1.0.0B5.1
I want to install VEGAn-GE-7.0.0-RC1, but I before I do I want to be sure I'm on the right bootloader. Any Idea how to Identify the bootloader after the Gtablet has already been rooted?
Go to Settings, About Tablet & look at Tap UI Version. If it starts with 1.1, you're on 1.1 the bootloader (b/l). If it starts with 1.2, you're on the 1.2 b/l.
Thanks for the response! I tried that before, but I dont seem to have a Tap UI Version because I am presently rooted and have the VEGAn-TAB-v1.0.0B5.1 installed. It gives me a build number, kernal version and Model number
DjRashonal said:
Hi All,
I searched and searched, but can't figure out how to identify the bootloader. I bought this gtab off of craigslist and it has already been rooted to VEGAn-TAB-v1.0.0B5.1
I want to install VEGAn-GE-7.0.0-RC1, but I before I do I want to be sure I'm on the right bootloader. Any Idea how to Identify the bootloader after the Gtablet has already been rooted?
Click to expand...
Click to collapse
1VegaTab 1.0.0B5.1 is a b/l 1.1 branch
aabbondanza said:
1VegaTab 1.0.0B5.1 is a b/l 1.1 branch
Click to expand...
Click to collapse
Thanks! I was searchin around for which branch! You definitely saved me a bunch of greif!
DjRashonal said:
Thanks! I was searchin around for which branch! You definitely saved me a bunch of greif!
Click to expand...
Click to collapse
Google "Gtablet for dummies", it's hte only place you'll need ot look for just about anything. under start here, there is a drop down, wiht a "rom" entry, click on that and there is a convenient table that illustrates what roms are available and on what bootloaders.
TJEvans said:
Google "Gtablet for dummies", it's hte only place you'll need ot look for just about anything. under start here, there is a drop down, wiht a "rom" entry, click on that and there is a convenient table that illustrates what roms are available and on what bootloaders.
Click to expand...
Click to collapse
I second this.
The tutorials on that site are second to none.
You will probably end up nvflashing back to a stock version anyway.
"I second this.
The tutorials on that site are second to none.
You will probably end up nvflashing back to a stock version anyway."
Ditto that, before you try to flash any other ROM. do a clean flash
using the Bl 1.2 with CWM.
How do I check which version of my firmware I have, i see stuff referencing 1.1 / 1.2 all the time.
Also, I'd like to install the most stable HC rom for browsing / youtube / video playback. Any recommendations.
Fyi, i am noob when it comes to rooting on androids.
firmware version in setting
apps then setting
good luck
I am in settings and I do not see firmware anywhere.
Ive checked about tablet / status etc..
supperman2k said:
How do I check which version of my firmware I have, i see stuff referencing 1.1 / 1.2 all the time.
Click to expand...
Click to collapse
If you have the stock rom, then see this thread.
Take some time to read the sticky threads that are there here.
Wow i am on 1.0
Is this bad? Or do I need to do an over the air update?
supperman2k said:
Or do I need to do an over the air update?
Click to expand...
Click to collapse
Yes, do the update--either OTA or manually.
I recently bought a USED GTablet which has already been Rooted. I am unsure which bootloader is/was on the device. Currently the following info is available:
Android Version 3.0.1
Kernel Version 2.6.32.41-cyanogenmod [email protected] #1
Build: GtabComb_a1.6
When booting into Recovery--> ClockworkMod Recovery v2.5.1.1-bekit-0.8
OK. When rooting a new ROM (and associated Kernel), do I use one for 1.1 or 1.2? Thanks in advance for an answer to this very basic question!
I'd like to update the Kernal and perhaps go to a 3.3 ROM-- but even with extensive research and my very limited knowledge, I have not determined which BL is applicable.
Rick-F said:
I have not determined which BL is applicable.
Click to expand...
Click to collapse
If you're able to boot into CWM-2.5.1.1, then you most likely have a 1.1 bootloader. However, there is a precise way to identify which bootloader you have if you run a Pershoot kernel. See this thread.
Hi there everyone. Was just looking up guides and tutorials on unlocking my tf201.
I went to the asus website to download the unlock tool http://support.asus.com/download.aspx?SLanguage=en&p=20&m=Eee+Pad+Transformer+Prime+TF201&hashedid=FqCKMQDqgvSncfFM
And I noticed it says: Unlock Device Boot Loader (only works with tf201 ICS OS)
So my question is: Do I have to wait for asus to update their bootloader? or what do you guys recommend I'd do?
Thanks in Advance.
Rhendera said:
Hi there everyone. Was just looking up guides and tutorials on unlocking my tf201.
I went to the asus website to download the unlock tool http://support.asus.com/download.as...sformer+Prime+TF201&hashedid=FqCKMQDqgvSncfFM
And I noticed it says: Unlock Device Boot Loader (only works with tf201 ICS OS)
So my question is: Do I have to wait for asus to update their bootloader? or what do you guys recommend I'd do?
Thanks in Advance.
Click to expand...
Click to collapse
officialy its only working with ics, due to changed bootloader. but some users reported successfull unlock even on JB. but i also read about one guy bricking his prime when trying to unlock on JB...dont know what went wrong in his case...
so everything on your own risk
Sent from my GT-I9100 using xda premium
Rhendera said:
Hi there everyone. Was just looking up guides and tutorials on unlocking my tf201
Click to expand...
Click to collapse
I unlocked my Prime using the Asus Unlock Tool V6 after I upgraded to JB. It worked perfectly for me.
But like beckzz said, one person reportedly bricked his prime trying to unlock it. YMMV
Hi guys
i want to unlock my prime but when i download unlock tool i run this and he said problem with connection or can't unlock something like this. What can i do? HELP
Matteo1497 said:
Hi guys
i want to unlock my prime but when i download unlock tool i run this and he said problem with connection or can't unlock something like this. What can i do? HELP
Click to expand...
Click to collapse
Hey, first of all pls check, if you have a serial number:
Settings->About Tablet -> Status
if S/N is empty, your device doesnt know its S/N. you can add it manually with a tool called "ratchet",
here are the instructions: http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/
credits to the author.
(you find your serial number on a sticker on the bottom of your tablet, or on the package in which it was shipped..)
After that, when you can see your S/N in Settings->About Tablet -> Status, you can try again.
if this fails to, you can try the following:
Some users reported, that they where able to unlock, after a factory reset. but remember: you loose root with factory reset and there is no root-method atm for JB.
If all the stuff didnt work: you are one of the "lucky" guys: there will be no unlock for your device and asus refuses support. (you are not alone, me and many others are with you)
atm there is an official asus employee named Tien, who is trying to help us. no success so far, but lets hope..
check these threads for more info:
http://forum.xda-developers.com/showthread.php?t=1764917
http://forum.xda-developers.com/showthread.php?t=1511195
beckzz said:
Hey, first of all pls check, if you have a serial number:
Settings->About Tablet -> Status
if S/N is empty, your device doesnt know its S/N. you can add it manually with a tool called "ratchet",
here are the instructions: http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/
credits to the author.
(you find your serial number on a sticker on the bottom of your tablet, or on the package in which it was shipped..)
After that, when you can see your S/N in Settings->About Tablet -> Status, you can try again.
if this fails to, you can try the following:
Some users reported, that they where able to unlock, after a factory reset. but remember: you loose root with factory reset and there is no root-method atm for JB.
If all the stuff didnt work: you are one of the "lucky" guys: there will be no unlock for your device and asus refuses support. (you are not alone, me and many others are with you)
atm there is an official asus employee named Tien, who is trying to help us. no success so far, but lets hope..
check these threads for more info:
http://forum.xda-developers.com/showthread.php?t=1764917
http://forum.xda-developers.com/showthread.php?t=1511195
Click to expand...
Click to collapse
Okay i have the serial number. I run again the unlock tool but he said a unknown error.
I have a similar issue...any ideas for me?
beckzz said:
Hey, first of all pls check, if you have a serial number:
Settings->About Tablet -> Status
if S/N is empty, your device doesnt know its S/N. you can add it manually with a tool called "ratchet",
here are the instructions: http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/
credits to the author.
(you find your serial number on a sticker on the bottom of your tablet, or on the package in which it was shipped..)
After that, when you can see your S/N in Settings->About Tablet -> Status, you can try again.
if this fails to, you can try the following:
Some users reported, that they where able to unlock, after a factory reset. but remember: you loose root with factory reset and there is no root-method atm for JB.
If all the stuff didnt work: you are one of the "lucky" guys: there will be no unlock for your device and asus refuses support. (you are not alone, me and many others are with you)
atm there is an official asus employee named Tien, who is trying to help us. no success so far, but lets hope..
check these threads for more info:
http://forum.xda-developers.com/showthread.php?t=1764917
http://forum.xda-developers.com/showthread.php?t=1511195
Click to expand...
Click to collapse
At the current moment my prime is being used as a daily driver. It is my college life all bundled in to one awesome device. Android version 4.0.3 ICS. It is rooted it has IML74. US_epad-9.4.2.28.2-20120529 It has latest superuser it has been backed up Voodoo OTA root keeper shows 100% The device is NOT UNLOCKED, it does not say that it is unlocked on start-up, ITS LOCKED but It has CWM 5.5.0.4 My first method of rooting was done though vipermods exploits Last time I updated I just flashed the proper/suitable stock .28 build that I have now through CWM from a rooted .21 stock
I can flash custom roms for unlocked devices but I am worried about a possible brick if I update to JB.
SpeedV said:
At the current moment my prime is being used as a daily driver. It is my college life all bundled in to one awesome device. Android version 4.0.3 ICS. It is rooted it has IML74. US_epad-9.4.2.28.2-20120529 It has latest superuser it has been backed up Voodoo OTA root keeper shows 100% The device is NOT UNLOCKED, it does not say that it is unlocked on start-up, ITS LOCKED but It has CWM 5.5.0.4 My first method of rooting was done though vipermods exploits Last time I updated I just flashed the proper/suitable stock .28 build that I have now through CWM from a rooted .21 stock
I can flash custom roms for unlocked devices but I am worried about a possible brick if I update to JB.
Click to expand...
Click to collapse
ahmm...wait...
"The device is NOT UNLOCKED", it has "CWM 5.5.0.4" running and you "can flash custom roms for unlocked devices"?
so thats sounds like impossible...really...did you already try to flash CM 10 or something? was it working? no offense man, but im really interested in what is going on with your tablet...cause im unable to unlock and think about selling this piece of s*** ...its unusable for me with this script-kiddie-stock-fw running on it...
Grz
Look at my post...
beckzz said:
ahmm...wait...
"The device is NOT UNLOCKED", it has "CWM 5.5.0.4" running and you "can flash custom roms for unlocked devices"?
so thats sounds like impossible...really...did you already try to flash CM 10 or something? was it working? no offense man, but im really interested in what is going on with your tablet...cause im unable to unlock and think about selling this piece of s*** ...its unusable for me with this script-kiddie-stock-fw running on it...
Grz
Click to expand...
Click to collapse
Thats correct. Look over at my post by searching ".28 to JB help" here on xda for more info on my situation...I have a video if people want proof and a bunch of detail on my issue. Help me out if you can.
Thank you.
SpeedV
okay..going to check this...crazy..
unfortunatly i was hoping, that you can help me get into the same situation as you are ^^
(cause unlocked with not showing "the unlock" is much better that no unlock ^^)
lets call it "the invisible unlock"
SpeedV said:
Thats correct. Look over at my post by searching ".28 to JB help" here on xda for more info on my situation...I have a video if people want proof and a bunch of detail on my issue. Help me out if you can.
Thank you.
SpeedV
Click to expand...
Click to collapse
guyd said:
I unlocked my Prime using the Asus Unlock Tool V6 after I upgraded to JB. It worked perfectly for me.
Click to expand...
Click to collapse
+1
Sent from my Transformer Prime TF201 using xda premium
i did it!
a little scared but worked in jelly bean. thanks
ricardo1976 said:
a little scared but worked in jelly bean. thanks
Click to expand...
Click to collapse
did it too today...worked perfectly in my second prime (my first prime was unable to be unlocked).
but what now? i installed twrp jb via fastboot, worked perfectly too.
But cm10 wont boot...any ideas?
Grz
beckzz said:
did it too today...worked perfectly in my second prime (my first prime was unable to be unlocked).
but what now? i installed twrp jb via fastboot, worked perfectly too.
But cm10 wont boot...any ideas?
Grz
Click to expand...
Click to collapse
I haven't used CM10 since the early Craig builds, but reading around it looks like at least one version of CM10 here in the development area doesn't use the newer JB bootloader so if you had already upgraded ota to JB then you have the latest JB bootloader and CM10 won't work unless you use one that has been built based on the new bootloader.
In my opinion, don't get hung up on thinking CM10 is the end all be all for our Primes. Either Craigs stock JB Rom or Hairybean 1.3 give a very nice JB experience with lots of tweaks.
Good luck
Fireplug said:
I haven't used CM10 since the early Craig builds, but reading around it looks like at least one version of CM10 here in the development area doesn't use the newer JB bootloader so if you had already upgraded ota to JB then you have the latest JB bootloader and CM10 won't work unless you use one that has been built based on the new bootloader.
In my opinion, don't get hung up on thinking CM10 is the end all be all for our Primes. Either Craigs stock JB Rom or Hairybean 1.3 give a very nice JB experience with lots of tweaks.
Good luck
Click to expand...
Click to collapse
hey,
running the cm10 nightly port of craig now...at least its working ^^
ill try other roms too, no question!
and hairybean is running on jb bootloader?
Grz
beckzz said:
hey,
running the cm10 nightly port of craig now...at least its working ^^
ill try other roms too, no question!
and hairybean is running on jb bootloader?
Grz
Click to expand...
Click to collapse
Yup, latest Hairybean is using the actual JB boot loader for t201
I cant seem to download the unlock tool from the jellybean website, the select OS box has no items for me to choose from (im on Windows8)
Postal Psycho said:
I cant seem to download the unlock tool from the jellybean website, the select OS box has no items for me to choose from (im on Windows8)
Click to expand...
Click to collapse
I first saw this behaviour about 2 weeks ago. I think you get this situation if you go direct to the download page/tab. If you navigate off the download page to another page on the site and then return (not by using the browser's back button but using links on the page) you find the drop down list is populated.
Postal Psycho said:
I cant seem to download the unlock tool from the jellybean website, the select OS box has no items for me to choose from (im on Windows8)
Click to expand...
Click to collapse
I had the same problem. Try using the stock browser on yr prime
Apparently Voodoo OTA doesn't keep root now with the official JB update?
(I've been using my Nexus7 for a while hence why I am just now coming back to my TF201)
Now I guess it's time to unlock /re-root and flash a custom ROM.
So before I continue on with any unlocking / rooting, I want to make sure I have the correct file (http://techerrata.com/file/twrp2/tf2...1.1-tf201.blob) for my device so I don't brick it.
My Build number on my device is JR030c.US_epad-10.4.2.18-20121122
Is the above TWRP file the correct image for my build#?
Thanks all.
usafle said:
Apparently Voodoo OTA doesn't keep root now with the official JB update?
(I've been using my Nexus7 for a while hence why I am just now coming back to my TF201)
Now I guess it's time to unlock /re-root and flash a custom ROM.
So before I continue on with any unlocking / rooting, I want to make sure I have the correct file (http://techerrata.com/file/twrp2/tf2...1.1-tf201.blob) for my device so I don't brick it.
My Build number on my device is JR030c.US_epad-10.4.2.18-20121122
Is the above TWRP file the correct image for my build#?
Thanks all.
Click to expand...
Click to collapse
Your link isn't complete.
I can tell you tho that you are on the Jellybean Bootloader so get this http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.4.1.0-tf201-JB.blob
So the TWRP build number doesn't have to match the build number of my device?
I think that is where I was getting confused..... The build number of the TWRP is just the "version number" of the TWRP file?
flumpster said:
Your link isn't complete.
I can tell you tho that you are on the Jellybean Bootloader so get this http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.4.1.0-tf201-JB.blob
Click to expand...
Click to collapse
usafle said:
So the TWRP build number doesn't have to match the build number of my device?
I think that is where I was getting confused..... The build number of the TWRP is just the "version number" of the TWRP file?
Click to expand...
Click to collapse
Yes, you want the newest version of TWRP but for the correct bootloader. You are on Jellybean bootloader so I have linked you to the newest version for that.
Thanks. Huge help. I posted this same exact question on numerous threads for the past few days and you are the first one to answer.
Appreciate it.
flumpster said:
Yes, you want the newest version of TWRP but for the correct bootloader. You are on Jellybean bootloader so I have linked you to the newest version for that.
Click to expand...
Click to collapse
usafle said:
Thanks. Huge help. I posted this same exact question on numerous threads for the past few days and you are the first one to answer.
Appreciate it.
Click to expand...
Click to collapse
That's unusual that I missed it. I read most of the new threads. You must have been posting on old threads that I thought were dead.
No worries.... that's why I started a new thread in case anyone missed the new post on the older threads.
I've unlocked, attempting to install the TWRP now. If I brick it, I have a Nexus7 on standby. lol
flumpster said:
That's unusual that I missed it. I read most of the new threads. You must have been posting on old threads that I thought were dead.
Click to expand...
Click to collapse
usafle said:
No worries.... that's why I started a new thread in case anyone missed the new post on the older threads.
I've unlocked, attempting to install the TWRP now. If I brick it, I have a Nexus7 on standby. lol
Click to expand...
Click to collapse
You should be fine..
When you go into fastboot mode it will freeze on the prime screen. That is normal.
You will probably have to install universal naked drivers from the Dev section then in device manager if you have an unknown device before continuing.
I've successfully installed TWRP.
I had no freezing issues and the driver got installed by windows update (of all things?)
Running a backup now in TWRP and placing it on SDCard before I go any further.
Again, huge thanks.
flumpster said:
You should be fine..
When you go into fastboot mode it will freeze on the prime screen. That is normal.
You will probably have to install universal naked drivers from the Dev section then in device manager if you have an unknown device before continuing.
Click to expand...
Click to collapse
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.