So thanks to RA and Haykuro, I have my Magic rooted. But I'm still unable to tether. I get this message in the log of the app:
Code:
Tearing down firewall rules...
iptables v1.3.7: can't initialize iptables
table 'filter': iptables who? (do you need
to insmod?)
Perhaps iptables or your kernel needs to
be upgraded.
failed
What can I do to make it work?
from wot i gather, the iptables on the Rogers rom dont allow you to tether and therefore you have to load a custom ROM for it to work aka the ION5 rom for example. It already comes with a tethering app. I cant try it since im overseas on a paygo sim card with no data plan.
Someone correct me if im wrong please.
My best guess is that the Rogers kernel isn't supporting netfilter/iptables , you'll have to replace the kernel with a "netfilter-enabled" kernel or compile one yourself.
Ive had the same problem the only way i could teather was to use PdaNet.....
hers the link enjoy..... http://www.junefabrics.com/android/
Killadude said:
Ive had the same problem the only way i could teather was to use PdaNet.....
hers the link enjoy..... http://www.junefabrics.com/android/
Click to expand...
Click to collapse
I know of PDANet and I have no intention of using it.
Amon_RA, tell me more.
Im as noob as you get with linux stuff, but is it extremely had to recompile the original rogers kernel with IPtables?
Birnie
Anyone made any progress on this?
From what I have read, you with 1.5 cupcake, deep root access was blocked and to attain that level, got to apply this "su" to enable it. hey warn that it leaves phone security wide open. Google search. Will post
link I found shortly.
http://android-dls.com/wiki/index.php?title=Magic_Root_Access
That's the link!
jfive74 said:
From what I have read, you with 1.5 cupcake, deep root access was blocked and to attain that level, got to apply this "su" to enable it. hey warn that it leaves phone security wide open. Google search. Will post
link I found shortly.
Click to expand...
Click to collapse
It's not a matter of root access. As Amon_RA said you'll have to replace your kernel in the boot.img or recompile one yourself.
To answer the next question "how does it work"...... google is your friend: http://www.google.com/search?hl=en&q=compile+android+kernel&btnG=Google-Suche&meta=&aq=f&oq
allla said:
It's not a matter of root access. As Amon_RA said you'll have to replace your kernel in the boot.img or recompile one yourself.
To answer the next question "how does it work"...... google is your friend: http://www.google.com/search?hl=en&q=compile+android+kernel&btnG=Google-Suche&meta=&aq=f&oq
Click to expand...
Click to collapse
Yeah, I confirmed it with the wifi-tether devs and they confirmed what Amon_RA said. The rom doesn't have netfilter support. Need to flash a ROM that has it to use it.
tribalmunky said:
Yeah, I confirmed it with the wifi-tether devs and they confirmed what Amon_RA said. The rom doesn't have netfilter support. Need to flash a ROM that has it to use it.
Click to expand...
Click to collapse
Cool. I was just rtying to help based on what i read.
It's not a matter of root access. As Amon_RA said you'll have to replace your kernel in the boot.img or recompile one yourself.
To answer the next question "how does it work"...... google is your friend: http://www.google.com/search?hl=en&q...&meta=&aq=f&oq
Click to expand...
Click to collapse
Well thats out of my ability range If anyone has a rogers kernal that will work with wifi can you post the link to DL.
Thanks
Birnie
do you think its possible to swap the nandroid backup data.img from daldroids rom that i have with the nandroid backup data.img from rogers rom and then flash to device? just because i find the daldroid rom not really customised for rogers 7.2mbps data connection. i could be wrong. Please advise. Thanks.
Related
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
is busy box installed?
is SU working?
feefeeboomboom said:
is busy box installed?
is SU working?
Click to expand...
Click to collapse
I haven't done anything since flashing the 2.1 RUU. What steps do I need to do to get busybox and su working?
if you installed the RUU that was just 'leaked' (from what i understood our 2.1 builds are based off this ruu already). The build does not include busy box or anything for that matter that is required for wireless tether-
damageless said:
Here is a link to the latest RUU from Sprint.
You cannot simply extract it. This still has root since it is a test release. I recommend just doing an adb pull of your system directory after you flash it. Don't do this when the final one comes out or else you might be stuck without root.
You will need to add busybox, patch sh and su, and make sure that you do another recovery image and such. I also recommend adding Superuser.apk and stuff. If you use the Desire build.prop, you can get most of the protected apps working.
Enjoy.
http://dl.damagedroms.com/2.0/RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe
Leak, I know who you are.
Click to expand...
Click to collapse
http://benno.id.au/blog/2007/11/14/android-busybox
Busy Box link for you, I'm not really sure how to get it working but it's a start, alot of results come up if you google "busybox for android", so I hope that helps ya out bud
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.
dwertz said:
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.
Click to expand...
Click to collapse
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.
mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root
Click to expand...
Click to collapse
Who told you that the RUU was rooted already? It's not. Why would it be? Sprint has no interest in you being root.
As for why do you have to install busybox? Because the application requires it.
It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed
mobilehavoc said:
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.
Click to expand...
Click to collapse
Here is the superuser.apk You have to have root.
Put superuser.apk in your C:\AndroidSDK\Tools\
adb remount
adb push superuser.apk /system/app/
mobilehavoc said:
It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed
Click to expand...
Click to collapse
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
Not sure what you mean but I was able to push a new build prop onto the phone using adb with no issues.
posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
The leak actually is rooted. It's an engineering leak, so root can work his magic- but only from the adb shell.
why do you need superuser?
superuser requires root, if you had root, you wouldnt need it.
you can just dl the wifi tether for root from the market
program and it would work right?
10 chars and a poke
This is the latest Sprint Rom based on the latest RUU leak with A2SD support (I used Darktremor A2SD 2.7 since it was easy to add it).
I have verified that A2SD is working as I downloaded and installed a couple of programs from the market. The programs are being stored in /system/sd/app.
Here's the link: http://www.darktremor.info/files/2.1/2.1-ruu-a2sd-signed.ziphttp://www.darktremor.info/files/2.1/sprintstock-21-a2sd-b-signed.zip
This one now has adb rooted (thanks to nfinitefx45 for his assistance) and does flash (heard complaints on the symlink issue...never sure what causes that, but ended up starting over and porting the files from the previous build).
This is for those people who want to keep with the stock installation but want the addition of A2SD. If you want a customized look, faster performance and A2SD support, I suggest a custom rom. Fresh 2.1.2 or FreshToast is a good one to use.
Note: It will not affect recovery.
Enjoy and I'll answer any questions you may have (if I can answer them).
did you manually edit the init.rc? and you should mention that this is a ROM, not an RUU
tkirton said:
This is the latest Sprint RUU leak with A2SD support (I used Darktremor A2SD 2.7 since it was easy to add it).
This is definitely an RUU as when I go into adb shell, I get the dollar sign as a prompt rather than the pound sign...I'm pretty certain it is not rooted.
.
Click to expand...
Click to collapse
<<<snip>>>
This makes no sense at all.
Good point about the Rom vs RUU. Edited to correct.
As for the init.rc. Mainly it was init.rc edit.
regaw_leinad said:
did you manually edit the init.rc? and you should mention that this is a ROM, not an RUU
Click to expand...
Click to collapse
Don't look at me...that's what I'm getting. Doesn't make much sense to me, either. I just know if I do adb shell, I don't have root access. But A2SD works fine.
I went ahead and released it since the goal was to get A2SD working...and I did that. Everything else is for a Rom developer.
wctom said:
<<<snip>>>
This makes no sense at all.
Click to expand...
Click to collapse
tkirton said:
Don't look at me...that's what I'm getting. Doesn't make much sense to me, either. I just know if I do adb shell, I don't have root access. But A2SD works fine.
I went ahead and released it since the goal was to get A2SD working...and I did that. Everything else is for a Rom developer.
Click to expand...
Click to collapse
Thanks, I'll just use your boot image for RegawMOD 2.5. saves me a few minutes
working perfectly all apps installed and 132 megs still open internal
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
sandboxlove said:
is it a general consensus that if you want to run a2sd successfully you should use a class6? i currently have a class4
Click to expand...
Click to collapse
right now, I switched back to my class 4 and its working great
nvmchars....
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
sandboxlove said:
i just want to be clear...this is the latest sprint leak? you seriously deodexed the whole thing?
i thought vince was crazy for trying, your completely BANANNAS
Click to expand...
Click to collapse
yeah, i thought I'd post it in here. Didn't think since it's the same thing as he posted but deodexed that I should make another thread.
and yes, the latest sprint leak. you should test this. I can't right now.
Oooh...cool. Enhancements. I like enhancements.
regaw_leinad said:
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
Click to expand...
Click to collapse
tkirton said:
Oooh...cool. Enhancements. I like enhancements.
Click to expand...
Click to collapse
Well, I like your work, so that's for you
did anyone test it out to make sure it boots?
Sorry to be such a noob, but what is "deodexed" a ROM mean?
regaw_leinad said:
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
Click to expand...
Click to collapse
Well I flashed it and stuck on the HTC screen. Flashed the non deodexed version and loads fine.
So apparently i f***ed up deodexing lol. I guess that ROM that I did wont work..
well just loving this rom, but one question, can we get a updated boot.img with the adb enabled for access as root?
Now that the A2SD stuff is behind me, I'll take a look at that. Flipzmode or Toastcfh may be able to shed some light on how you get this image rooted correctly, especially Flipz since he's using the latest leak for Fresh 2.1.1.
The original goal was to get A2SD working on a stock rom, which I did....but it is rather annoying that it isn't rooted (or fully rooted).
Damage said in his point that it was rooted, but I got the same thing you did...no root when doing adb.
I'll talk to Flipz or Toast and see if they can point me in a direction to go.
nfinitefx45 said:
well just loving this rom, but one question, can we get a updated boot.img with the adb enabled for access as root?
Click to expand...
Click to collapse
well this is a piece from some of the reading I've been doing I beleice this needs to be done with in the boot image. I dont know if this will help in your research,
-------------------------
You also need to modify the ROM update script to change the default permissions for /system/bin/su so it can be used to elevate privileges to root. The script is in $WKD/dst/META-INF/com/google/android/update-script. Open it in your favorite editor and find the line starting with set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh and after it add the following set_perm 0 0 04755 SYSTEM:bin/su
=======================
Hi tkirton,
Nice job on this and thanks for all your hard work on everything! I am also wondering what dedoxed means? Is it like where application data is also stored on the SD card instead of on the phone itself?
Thanks!
Amon_RA/Koush,
Would it be possible for you to integrate PSFreedom into your recovery image as a selectable option?
So theoretically you can have all the recovery features with the option to run PSFreedom.
Anyone else please feel free to post your thoughts and comments.
Thanks
N0ble
n0ble said:
Amon_RA,
Would it be possible for you to integrate PSFreedom into your AmonRA recovery image as a selectable option?
So theoretically you can have all the recovery features with the option to run PSFreedom.
Anyone else please feel free to post your thoughts and comments.
Thanks
N0ble
Click to expand...
Click to collapse
I'm pretty much sure that's possible. Guess we should ask Koush too
Sent from my HTC Desire using XDA App
I'm waiting for this great feature too.
Sent from my HTC Desire
If someone could get this working it would be great.
I've never used USB mount in recovery. If this feature is lost its a worthy sacrifice.
as far as it looks like , he stoped the support for his recovery image ...
mercianary said:
If someone could get this working it would be great.
I've never used USB mount in recovery. If this feature is lost its a worthy sacrifice.
Click to expand...
Click to collapse
AFAIK, you also lose ADB
I would really like this too.
I can understand that we would lose ADB and USB mount when in recovery but it would be allot more convenient. I imagine it won't be too much further down the line until someone figures out a mod in the kernal of the ps3 itself to boot unsigned code, now we have the ability to dump and write it.
Sent from my HTC Desire using XDA App
You do loose ADB & Mass Storage in the recovery image, also a toggle between PSFreedom & ADB etc is not possible, as ADB... can not be built into a kernel module.
Fake-Flash will also not re-enable these features for you as it does not contain a kernel in itself.
It would be a nice feature, but after talking with AmonRa and exploring the possible routes to doing this, it simply is not possible as it is.
Later today or early tomorrow I will release a updated pack that does not have the OD 4.0.4 requirement, it will however still have AOSP as a requirement until HTC release kernel source.
Is a dual boot not possible? mount an img file as a virtual drive and boot from it?
can be a stripped down kernel with just psfreedom in it!!!
AmunRA already did this with his, you have to permanently flash it but it works.
neoKushan said:
AmunRA already did this with his, you have to permanently flash it but it works.
Click to expand...
Click to collapse
No, the question was for a recovery with a toggle, that's not possible.
Nice so it now seems that AmunRA and Klutsh have both made recovery images with ADB and USB working with a PSFreedom toggle.
Thats excellent work!
yyou guys are way too late google amon ra recovories google might just have a gift 4 you
turtleiscool said:
yyou guys are way too late google amon ra recovories google might just have a gift 4 you
Click to expand...
Click to collapse
Did you even bother to notice that this thread was month's old!!!
Had quite the night. ANYWAY, you need to be rooted in order to flash this (it's meant to be flashed through CWM)
This the stock Inspire 4G ROM with su and busybox installed. Basically, I took attn1's Inspired DHD AFR zip package, and replaced all the files in the system directory with the system files stripped out of the RUU that was posted here earlier this week.
Sound quality is back to normal!
One problem with this build is that ro.secure is still set to 1 (you can't use adb remount). I was originally going to include a batch file that would pull settings.db off the phone and update install_non_market_apps with a value of 1 (for sideloading). Without adb remount, it's a bit more complex to enable sideloading.
Version 2 with sideloading enabled will be coming soon! Hopefully.
DOWNLOAD HERE: http://www.multiupload.com/7867ZQNEM4
Off to bed!
You and attn1 are marvelous. I really should have been more patient
All this figured out in less than one week. I'm torn now, my current setup is awesome.
Inspire (rooted)
Leedroid v2.0.0
TELUS kernel
With this rom are we able to install non market downloads straight from the phone since sideloading wont?
davwman said:
All this figured out in less than one week. I'm torn now, my current setup is awesome.
Inspire (rooted)
Leedroid v2.0.0
TELUS kernel
Click to expand...
Click to collapse
Next we'll have CM7
booty hater said:
With this rom are we able to install non market downloads straight from the phone since sideloading wont?
Click to expand...
Click to collapse
Not yet, there is a workaround but it takes about 5-10 min
If I can figure out how to set ro.secure = 0, enabling sideloading would take under 20 seconds
booty hater said:
With this rom are we able to install non market downloads straight from the phone since sideloading wont?
Click to expand...
Click to collapse
No, because the option to install non market apps is not in this rom. Thus the need for sideloading.
I posted in your other original thread but ill post it here too...
Couldnt you use the method described here to do the "temproot" in order to get the adb root prompt and change it that way?
r34p3rex said:
Not yet, there is a workaround but it takes about 5-10 min
If I can figure out how to set ro.secure = 0, enabling sideloading would take under 20 seconds
Click to expand...
Click to collapse
How about if I take the .apk file from my SD card with root explorer and move it to the /data folder, would it work? Or perhaps move it to /system/app, change permissions and reboot?
emarsha said:
How about if I take the .apk file from my SD card with root explorer and move it to the /data folder, would it work? Or perhaps move it to /system/app, change permissions and reboot?
Click to expand...
Click to collapse
That's a good question, especially since we already have root with r/w access.
Don't see why that wouldn't work.
Inspire (rooted)
Leedroid v2.0.0
TELUS kernel
r34p3rex said:
Not yet, there is a workaround but it takes about 5-10 min
If I can figure out how to set ro.secure = 0, enabling sideloading would take under 20 seconds
Click to expand...
Click to collapse
You would need to unpack the boot.img, change the default.prop file (I think) and then repack the img. I know that's oversimplified, especially if you don't know the parameters for repacking the img, but does that help?
Another thing for v2 would be to swap out the WifiRouter on the AT&T stock rom for the one that was on the desire so we can tether ;D
JetBlk said:
Another thing for v2 would be to swap out the WifiRouter on the AT&T stock rom for the one that was on the desire so we can tether ;D
Click to expand...
Click to collapse
That would be nice indeed
lrs421 said:
That would be nice indeed
Click to expand...
Click to collapse
Maybe later after I actually root and get this setup (tonight or tomorrow after class) I'll look into it if he hasnt already
JetBlk said:
Another thing for v2 would be to swap out the WifiRouter on the AT&T stock rom for the one that was on the desire so we can tether ;D
Click to expand...
Click to collapse
+1
Once sideloading and tethering/hotspot are enabled in this ROM, I'll be all over it like a fat kid on a cupcake Looking forward to v2!
It wasn't stated in the OP, but is HSUPA enabled?
Also, this should help you with unpacking the boot.img to edit ro.secure http://android-dls.com/wiki/index.p...t,_and_Re-Pack_Boot_Images#Alternative_Method
yg17 said:
+1
Once sideloading and tethering/hotspot are enabled in this ROM, I'll be all over it like a fat kid on a cupcake Looking forward to v2!
Click to expand...
Click to collapse
+1 for me too
I'll be happier than a fat kid in the chocolate factory . You guys are awesome
Sent from my Desire HD using XDA App
JetBlk said:
Another thing for v2 would be to swap out the WifiRouter on the AT&T stock rom for the one that was on the desire so we can tether ;D
Click to expand...
Click to collapse
Which files would you need to change? Should not be that hard...
yzlvr said:
Which files would you need to change? Should not be that hard...
Click to expand...
Click to collapse
Im just guessing WifiRouter.apk but i havent looked into it too much. will do more research when I root later tonight/tomorrow
DOWNLOAD LINKS REMOVED - MOVED TO THE DEV SECTION!!! YAY!!
LINK : http://forum.xda-developers.com/tab...ooted-odexed-2015-04-11-t3079083#post60044636
Thanks for all the support
MOVED -
Looking forward to trying this out. Thank you for the work.
VerneVerne said:
Looking forward to trying this out. Thank you for the work.
Click to expand...
Click to collapse
Check your PM
Stock rooted boots but WiFi appears to be broken. This was with a clean install. I will try stock debloated either tonight or tomorrow.
VerneVerne said:
Stock rooted boots but WiFi appears to be broken. This was with a clean install. I will try stock debloated either tonight or tomorrow.
Click to expand...
Click to collapse
I forgot to ask on PM. Did you try forget and try your WiFi connection again? Like I said might be kernel related or system/etc/wifi files.
Root access / 3G/4G LTE work?
Can someone pull a logcat while trying to connect to WiFi.
g_ding84 said:
I forgot to ask on PM. Did you try forget and try your WiFi connection again? Like I said might be kernel related or system/etc/wifi files.
Root access / 3G/4G LTE work?
Click to expand...
Click to collapse
I'm sorry but I already went back to stock. I did try the forget Wi-Fi password trick but still didn't help.
The limited time I was using it everything checked out good...root, 3g, 4g(very spotty for me, but it did connect).
My data is very limited so Wi-Fi is important for me. I will try the debloated tomorrow though. Do you think it will have the same Wi-Fi issue? If so, I will grab a logcat if no one else gets to it before me. I'm going to have to wait until tomorrow afternoon unfortunately though.
@VerneVerne sounds good. It might have the same issues.....also see if you can pull /cache/recovery/last_log after you flash the ROM. That can give me some insight on if I messed up the updater-script. (Invalid arguments)
g_ding84 said:
@VerneVerne sounds good. It might have the same issues.....also see if you can pull /cache/recovery/last_log after you flash the ROM. That can give me some insight on if I messed up the updater-script. (Invalid arguments)
Click to expand...
Click to collapse
Ahhh, you say updater script. Come to think of it there was something mentioned of a script being outdated and needing to be updated while flashing the rom. I'll be sure to find out what that says exactly when I can get back to testing later.
VerneVerne said:
Ahhh, you say updater script. Come to think of it there was something mentioned of a script being outdated and needing to be updated while flashing the rom. I'll be sure to find out what that says exactly when I can get back to testing later.
Click to expand...
Click to collapse
I need a new update-binary. It is legacy but still should work. Philz switches to a legacy environment for compatibility..... That a huge plus with using philz recovery.
Its outdated because it uses set_perm command. Newer binaries use set_metadata (for selinux support). I might have too cook up a newer script with a newer binary.
Huge thanks to @moonbutt74 - it was an updater-script issue. I missed a symlink command. I added that in and WiFi should work now. Just need the stock kernel pulled from the T237P if someone would be so kind.
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
and send me the kernel img....please.
if not - drop /msm_sdcc.1/by-name/boot and use the mmcblk0p(xx) use xx as the block number
G,
https://www.androidfilehost.com/?fid=95916177934549973
:good:
m
@moonbutt74. The man. Ty
@VerneVerne - lead tester
@mysticjp - tester
@dave5777 - tester
@trevortf - tester
@amphillips82277 - tester
@moonbutt74 - custom recovery (philz) and support (various tips and help)
Guys check your PM. I uploaded a fixed version to you guys for testing. If all is well, this thread can be moved to the Dev section and public download links.
Everyone else following this thread, please thank the testers above, without them there wouldn't be a ROM. :highfive::good:
Thank you! I was about to throw this thing in my box of shame next to my gtab2 ;p
Download links available for public release.
Just need someone to confirm init.d is working correctly.?
After that we can call this stable and move this thread to the Dev section.
g_ding84 said:
Download links available for public release.
Click to expand...
Click to collapse
:good:
Good to hear that we have recovery and custom rom for T237P!
I flash recovery, and download firmware now.
Rooted yesterday so far so good... Just need that free Hotspot going.
There are a few 3rd party apps that will do the job in the mean time.