Hi. Does anyone know what the status of clockwork recovery is for our devices???
I'm just starting to work on that myself.
Starting with this post from Koush:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Unfortunately, I'm stuck at dumping the stock recovery with no idea how to proceed. It seems that on other devices, one would start by typing
Code:
cat /proc/mtd
but unfortunately, that doesn't work on our A7 (or at least not on mine). It returns, "cat: can't open '/proc/mtd': No such file or directory"
So, I guess "dump_image" is another option, but Koush says that it only works on devices running MDT. Anybody know how to tell if the A7 runs MDT? Or what MDT is?
After that, it looks pretty straight forward.
Billy
I've run "cat /proc/___" on just about everything else there hoping to find that "mtd" was just renamed on our devices, but no luck.
Billy
well....one of us could send our tablet to him for a week or so...
"My" tablet, technically became my wife's as of 12/25. She let's me play with it but I'm not even going to ask if I can send it to some guy from teh intarweb for a week
Billy
Sent from my Nexus One using XDA App
Elementix said:
well....one of us could send our tablet to him for a week or so...
Click to expand...
Click to collapse
sounds like you volunteered
i believe were dealing w/ a mmc device, not MDT. So DD (dalvik debug) which is emulated in android sdk will have to be used. ive been messing with it but time is hard to come by during the holidays!
Sent from my A7-040 using Tapatalk
hashbrown said:
i believe were dealing w/ a mmc device, not MDT. So DD (dalvik debug) which is emulated in android sdk will have to be used.
Click to expand...
Click to collapse
LOL, A couple hours of research brought me to this conclusion as well.
Billy
hashbrown said:
i believe were dealing w/ a mmc device, not MDT. So DD (dalvik debug) which is emulated in android sdk will have to be used. ive been messing with it but time is hard to come by during the holidays!
Sent from my A7-040 using Tapatalk
Click to expand...
Click to collapse
the memory in the elocity is 4GB eMMC Module via HSMMC Interface for System Boot and Storage it is listed in the specs
Ok guys, I've been talking to Koush a bit in IRC and will be sending him my A7 soon to hopefully get Clockwork ported to it. Maybe then we can get some actual development going for this little guy. I hope someone is able to possibly get true multitouch working for it. Anyway, we'll see what happens.....
Elementix said:
Ok guys, I've been talking to Koush a bit in IRC and will be sending him my A7 soon to hopefully get Clockwork ported to it. Maybe then we can get some actual development going for this little guy. I hope someone is able to possibly get true multitouch working for it. Anyway, we'll see what happens.....
Click to expand...
Click to collapse
Thanks for taking the time and trouble in getting CW ported to our devices!!!!!
Whats the main website for clockwork? I googled it and so many websites came up that i don't know what it is.
rfisher1968 said:
Whats the main website for clockwork? I googled it and so many websites came up that i don't know what it is.
Click to expand...
Click to collapse
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Related
I know. This is the hero forum. But if anyone has a droid or knows someone with one maybe we can get a dump?
Forgot to, post the link
Http://alldroid.org/viewtopic.php?f=210&t=567
awesome! i'd expect you goons to have vanilla 2.0 ready for the mass sprint crowd by tomorrow right? lol isn't a dump all we'd need? pardon for my ignorance but what changes would be made to be compatible to the cdma hero?
Excellent! Now we just need a full rom dump (not just the /system folder which is all that's available right now).
flipzmode said:
Excellent! Now we just need a full rom dump (not just the /system folder which is all that's available right now).
Click to expand...
Click to collapse
+1
I could use those apk's to build a "fuller" AOSP... that is assuming data can be made to work.
Thats what I'm hoping for. So please everyone who has access to a droif, root it and get a dump for us. Please
I was excited for droid users to find out it had been rooted. Now I am really excited because I didn't even think of the benefits it would bring to us!
flipzmode said:
Excellent! Now we just need a full rom dump (not just the /system folder which is all that's available right now).
Click to expand...
Click to collapse
Request made @ AllDroid
http://alldroid.org/viewtopic.php?f=210&t=570
WhiteWidows said:
Request made @ AllDroid
http://alldroid.org/viewtopic.php?f=210&t=570
Click to expand...
Click to collapse
Sweet. Post back here if they provide it please. I can only watch so many forums. heh.
So let me get this straight, a full dump from the Droid will help us get 2.0? If so AWESOME! I have a friend who has one, I'm sure he'll be rooting tonight I can get a dump tomorrow if you don't get one sooner.
NCX001 said:
So let me get this straight, a full dump from the Droid will help us get 2.0? If so AWESOME! I have a friend who has one, I'm sure he'll be rooting tonight I can get a dump tomorrow if you don't get one sooner.
Click to expand...
Click to collapse
It's more of a theory than anything. But if we can get their rom booting on our phone then we have a much better chance of getting things working rather than the gsm version we've been hacking up to try and work.
If anyone has access to a rooted droid then let me know. Although it will be much better once they have access to nandroid because pulling these files while the phone is booted up doesn't always work.
flipzmode said:
It's more of a theory than anything. But if we can get their rom booting on our phone then we have a much better chance of getting things working rather than the gsm version we've been hacking up to try and work.
If anyone has access to a rooted droid then let me know. Although it will be much better once they have access to nandroid because pulling these files while the phone is booted up doesn't always work.
Click to expand...
Click to collapse
I don't think that's true.. our kernel/drivers are way different than theirs.. we will be about the exact same point that we are now, and there are full rips out of the droid now on alldroid.org
nelson8403 said:
I don't think that's true.. our kernel/drivers are way different than theirs.. we will be about the exact same point that we are now, and there are full rips out of the droid now on alldroid.org
Click to expand...
Click to collapse
I agree but it's a lot easier to make a trackball work, to make leds work, and to make wifi work rather than trying to make it work on a radio that it wasn't designed for.
The image that the guy posted on alldroid is corrupted. It won't unyaffs. And based on the file size I would say it's just a system dump anyways.
Thanks to whitewidow I was able to get my hands on the boot.img by copying it off of /dev/mtd. The build went smoothly however it reboots instantly after the HTC logo. It is never recognized by the debugger. So this is either caused by corruption from how we obtained the boot.img, or the architecture / processor are just too different to work on ours at all. I am not the type that can build kernels from scratch though so maybe someone out there better than me will get it soon.
flipzmode said:
I agree but it's a lot easier to make a trackball work, to make leds work, and to make wifi work rather than trying to make it work on a radio that it wasn't designed for.
The image that the guy posted on alldroid is corrupted. It won't unyaffs. And based on the file size I would say it's just a system dump anyways.
Thanks to whitewidow I was able to get my hands on the boot.img by copying it off of /dev/mtd. The build went smoothly however it reboots instantly after the HTC logo. It is never recognized by the debugger. So this is either caused by corruption from how we obtained the boot.img, or the architecture / processor are just too different to work on ours at all. I am not the type that can build kernels from scratch though so maybe someone out there better than me will get it soon.
Click to expand...
Click to collapse
I'm pretty sure stuff compiled for the OMAP arch. Droid is not going to work in our Qualcomm arch. Heroes. I tried using "chat-ril" executable from Droid on my Hero and that doesn't work at all. OMAP and MSM have their own kernel trees as well, so their kernel probably won't boot on the Hero.
It's OMAP alright.
You wont get any of the normal binaries to run.
You can however grab some apks from it.
There is a dump out already btw, has been for almost a month now.
There has been a system dump yes but we are talking about a full dump including the boot.img file.
Boot image contains nothing useful for our purposes.
If you absolutely have to have the boot image someone posted it over on alldroid.org.
is it possible to get the new lockscreen from newly updated droid as verizon has spreaded 2.01 update for droid? cheers
So, so far with every OC Rom I've tried (both versions of FreshToast and all recent versions of DarchDroid) I'm getting the same problem: the phone will hang up at the first HTC screen at boot.
I wiped, partitioned the sdcard as 32mb swap, 512mb ext2 and remainder fat32. Then converted ext2 -> ext3. I've tried just about everything, from reflashing the ROM, to repairing sd:ext, to re-partitioning. Nothing works.
ADB doesn't detect the phone, so I can't do a logcat. I did manage to get the last 2 last_kmsgs though, so they're both linked below.
First:
http://pastebin.com/1NNnffps
Second:
http://pastebin.com/aEbzJFKi
If a dev could take a look at these and tell me what the problem is I'd really appreciate it! I'd LOVE to try one of the OC roms but I haven't been able to
Thanks for your help in advance.
Gregalous said:
So, so far with every OC Rom I've tried (both versions of FreshToast and all recent versions of DarchDroid) I'm getting the same problem: the phone will hang up at the first HTC screen at boot.
I wiped, partitioned the sdcard as 32mb swap, 512mb ext2 and remainder fat32. Then converted ext2 -> ext3. I've tried just about everything, from reflashing the ROM, to repairing sd:ext, to re-partitioning. Nothing works.
ADB doesn't detect the phone, so I can't do a logcat. I did manage to get the last 2 last_kmsgs though, so they're both linked below.
First:
http://pastebin.com/1NNnffps
Second:
http://pastebin.com/aEbzJFKi
If a dev could take a look at these and tell me what the problem is I'd really appreciate it! I'd LOVE to try one of the OC roms but I haven't been able to
Thanks for your help in advance.
Click to expand...
Click to collapse
Mind posting what version of radio your using, as that may affect things perhaps. (i really don't know, but radio does control alot)
Btw, i think this more belongs in the general section than development, but hey, lets have the mods be the judge of that.
I have the exact same issue, just posted in the fresh toast thread. Tried with partitions and without, ext2, 3, and 4. Multiple downloads. No luck...
edit: I have the latest sprint radio, 2.42.00.03.10
Baseband version: 2.42.00.03.10
Gregalous said:
Baseband version: 2.42.00.03.10
Click to expand...
Click to collapse
ok, so thats not the issue as we have the same version. Umm, how about taking out your sd card and booting?
darchstar said:
ok, so thats not the issue as we have the same version. Umm, how about taking out your sd card and booting?
Click to expand...
Click to collapse
K so I flashed an older radio and tried booting without the sd card and neither helped. Got stuck at boot again both times.
same here...
In the settings> about phone> hardware version
Do people have different versions? Or are all cdma heros version 2?
Jus10o said:
In the settings> about phone> hardware version
Do people have different versions? Or are all cdma heros version 2?
Click to expand...
Click to collapse
Hardware version: 0002
Gregalous said:
Hardware version: 0002
Click to expand...
Click to collapse
Oh i was just adding it has a thought. Maybe there was the chance of it being different. I dont know if anyone actaully has a different version.
And im from dfw, texas.. I think you are the first texas person iv seen.
version 2 as well for hardware
This affects me too... I really want to get this issue sorted out so that I can use DarchDroid :3
Hey, I'm from Fort Worth.
I have nothing to say about the topic, buy saw that so I had to let you know .
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Hardware version: 0002
Click to expand...
Click to collapse
Oh i was just adding it has a thought. Maybe there was the chance of it being different. I dont know if anyone actaully has a different version.
And im from dfw, texas.. I think you are the first texas person iv seen.
Click to expand...
Click to collapse
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Do you have any issues with a non-OC ROM?
It looks like your phone is failing at various different points in the kernel (which could be the result of the OC...not really sure.)
Gregalous said:
So, so far with every OC Rom I've tried (both versions of FreshToast and all recent versions of DarchDroid) I'm getting the same problem: the phone will hang up at the first HTC screen at boot.
I wiped, partitioned the sdcard as 32mb swap, 512mb ext2 and remainder fat32. Then converted ext2 -> ext3. I've tried just about everything, from reflashing the ROM, to repairing sd:ext, to re-partitioning. Nothing works.
ADB doesn't detect the phone, so I can't do a logcat. I did manage to get the last 2 last_kmsgs though, so they're both linked below.
First:
http://pastebin.com/1NNnffps
Second:
http://pastebin.com/aEbzJFKi
If a dev could take a look at these and tell me what the problem is I'd really appreciate it! I'd LOVE to try one of the OC roms but I haven't been able to
Thanks for your help in advance.
Click to expand...
Click to collapse
Don't know if this helps at all but I'm using a 1.5 rom with a kernel based on toast's latest release I had this same issue multiple times and I got it working by not pushing any files to /data/app or /system/app and restoring with the 1.56 RUU before hand. I don't think they support ext3, 4 either so I went with a ext2 partition. My hero is flying!
Jus10o said:
l
And im from dfw, texas.. I think you are the first texas person iv seen.
Click to expand...
Click to collapse
Really? Cause I coulda sworn we had had a conversation before.
tejasrichard said:
Really? Cause I coulda sworn we had had a conversation before.
Click to expand...
Click to collapse
I got stranded in dallas day before yestarday.
&RoidRage said:
Hey, I'm from Fort Worth.
I have nothing to say about the topic, buy saw that so I had to let you know .
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Hey I live in Fort Worth too!! Around the hulen mall area!!! 817 baby!!
Today Toast said he would post a lower clocked kernel in the fresh toast thread, although that didn't help me in darch's thread. I think I will try the ruu later suggested a few posts up, just for the hell of it, but it will probably be late tonight. I'll keep ya updated.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
shahrukh817 said:
Hey I live in Fort Worth too!! Around the hulen mall area!!! 817 baby!!
Click to expand...
Click to collapse
im in mansfield.. Im 817 also
Hey there,
since I have no clue about Android development, is it possible to access the USB on a rooted phone and simulate a USB Hub? Reason for this is a possible port to android phones of the open source jailbreak PSGroove found here:
github.com/psgroove/psgroove
Coffeinchen said:
Hey there,
since I have no clue about Android development, is it possible to access the USB on a rooted phone and simulate a USB Hub? Reason for this is a possible port to android phones of the open source jailbreak PSGroove found here:
github.com/psgroove/psgroove
Click to expand...
Click to collapse
well it is, but it's a small mixup especially if you have no clue about android.
instructions can be found here (tested and working on N1)
Thanks for that, that already helps a lot!
well i was going write a topic about it .... the Teensy++ USB Development Board and AT90USBKEY are sold out we will have to wait 2 weeks.
android seems to have the required hardware
the Teensy++ usb is sold for $24
so a psjailbreak app in the market for a $10 is great deal
any developer interested ?
edit:
further info on the exploit
ps3wiki.lan.st/index.php?title=PSJailbreak_Exploit_Reverse_Engineering
cheers
can someone try it?PLSS
This would be awesome! I'll donate.
hope there is a possibility, because all are sold out usbkey
Here the github code of the open source version
github.com/psgroove/psgroove
WOw THIS WOULD BE AMAZING IF WE COULD get this fully working just flash into kernals etc.. soo from then on all you'd have to do is plug in your usb and have access to keyboards. mouse. flash disks. etc..
Would be great if we could have an apk that does it..
I would surely buy it.. maybe someone with some good knowledge of porting apps wants to get some money from it...
found this in a comment on maxconsole.
Stage 2 done. Thinking If I should use PSGroove or OpenPSJailbreak as a base. for stage 3 about 7 hours ago via TweetDeck
Lol I just got my Android to mimic the 6 port hub. Stage 1 Complete
http://twitter.com/qberty1337
This dude is looking for beta testers of his android port netzke.blogspot.com
http://twitter.com/qberty1337/status/22834648971
As per the Android port status. I have successfully emulated the WHOLE procedure of fake usbs and jigs. Time for descriptors.
Click to expand...
Click to collapse
Sounds good I knew someone was doing it I'm currently using a Blackcat JTAG, if there sold out of the Teensy grab one of them and use Flip to load the binary. I'll most likely use a device dedicated to this but I'm sure tons of people will enjoy this. It will be cool to be able to run the exploit on the go, to show friends or something.
jamiejones85 said:
This dude is looking forfools to be scammedof his android port netzke.blogspot.com
Click to expand...
Click to collapse
fix ............
netzke seems legit time will tell he said beta by the end of the week. Im just glad I keep my Palm Pre around after I upgraded to the Evo I just used the Pre to jailbreak my ps3 crazy stuff
Just curious, the scrubby nub I am wonders what form this 'jailbreak' will take for android, an installable apk that just requires (or not - no way) root, some full fledged ROM?
I'm a bit scared too after reading netzke's blog seeing how he mentioned 1 or 2 phones blew up cause they got shorted or something but I can't help but look forward to it.
Netzke is a scammer. Everything on his blog is pure bull****.
The guys over the Desire forums already ported psfreedom to it. Go check if its compatible with your device.
Sent from my Milestone using XDA App
This message was deleted by its author
t4tav said:
Here we go...
This should work on the nexus and desire...
Thanks to whoever built the psfreedom.ko
----------
Here you go, Instructions too...
Download this
http://www.mediafire.com/?cgst1aw26i26b60
and place it's contents onto the root of your SD-card.
Then download my flashable boot.img
http://cl.ly/83b21dd1818a791d857e
Place that on the root of your card, Reboot into recovery and flash the PS3-signed.zip
Reboot your phone.
Launch terminal emulator...
Then type the following...
Code:
#cd sdcard
#su
#insmod psfreedom.ko
Now turn your PS3 off at the wall, and plug in your phone.
Turn the PS3 back on at the wall.
Press the PS3 power button followed by the eject key in quick succession...
Profit ??
Click to expand...
Click to collapse
Get Ready for the newbish questions.
I'll start:
What are the requirements for those instructions to work? I understood initially that you would need a particular ROM. From reading the post on the Desire forums it appears as if you need to unlock your bootloader (true/false) So what ROM are you using?
Lastly <3 tyvm for the instructions
Edited cause I can't read..
any chances of us getting it?
Contact KOUSH from the forums here. He made it and ported it to the galaxy s phones so he might be able to help..
Sent from my SGH-T959 using XDA App
so after getting in the irc room for koush i was directed to http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
i must say that his blog is very appropraitely named.
I'm trying to get my ubuntu box setup to do the stuff he's asking but my phone isn't here yet it's in the mail. (i'm hoping this one has a clean esn.............)
i do however have my Sylvania Tablet that i would love a custom recovery for and am a little lost on the guide as well. I'm completely new to any kind of android dev work at all. and have very little programming background.
I'm enough of a nerd though that i feel i should be able to tackle anything i set my mind to. so when my interecept gets here tomorrow i'll be headed down this road and seeing where i end up.
bigwooly said:
any chances of us getting it?
Click to expand...
Click to collapse
get rom manager from the market
StaticMaal said:
get rom manager from the market
Click to expand...
Click to collapse
i thought rom manager needed CWR to function properly
bigwooly said:
i thought rom manager needed CWR to function properly
Click to expand...
Click to collapse
I have tried Rom Manager, and there is no Clockwork option for the intercept in it.
CM01 Custom Recovery
CM01 Custom Recovery by Inxane works well for our Intercepts.
This is compiled from Nvidia's source using instructions found on this page Link
You need to have an unlocked bootloader and adb/fastboot.
Be aware this does not include any of nvidia's apps or google's frameworks/play store and is just plain android with no extras. (If someone can pull from their /system it may be helpful). I will try to add more later, but this should at least get any bricked tablets going until nvidia released a factory image.
______________Downloads_________________________________________________
Preinstalled
OTA0
_______________Directions___________________________________________________
Run flash.bat while unlocked/ screen on(if your computer hasn't been approved for adb yet), or while in bootloader.
Or flash each file in fastboot, instructions are in the nvidia link if you need more.
Keithn said:
This is compiled from Nvidia's source using instructions found on this page Link
You need to have an unlocked bootloader and adb/fastboot.
Be aware this does not include any of nvidia's apps or google's frameworks/play store and is just plain android with no extras. (If someone can pull from their /system it may be helpful). I will try to add more later, but this should at least get any bricked tablets going until nvidia released a factory image.
______________Downloads_________________________________________________
Preinstalled
OTA0
_______________Directions___________________________________________________
Run flash.bat while unlocked/ screen on(if your computer hasn't been approved for adb yet), or while in bootloader.
Or flash each file in fastboot, instructions are in the nvidia link if you need more.
Click to expand...
Click to collapse
Fixed my problem with WIFI not turning on at all, but is there an easy way for me to install gapps? Playing the waiting game for the factory img sucks....but Without even the playstore this tablets a lemon! hahaha any help would be awesome
Gytole said:
Fixed my problem with WIFI not turning on at all, but is there an easy way for me to install gapps? Playing the waiting game for the factory img sucks....but Without even the playstore this tablets a lemon! hahaha any help would be awesome
Click to expand...
Click to collapse
You'll have to root and push a gapps package into your root directory. We don't have a recovery unfortunately.
precisely...
yeah I normally just slap it in the sd card then boot into twrp and flash away but it's kinda hard at the moment. and even stock recovery is upside down and wont get past the android icon no matter the button combo. lol im SOL.
Pretty sure I received a Lemon Tablet though out of the box. Wifi Was really choppy, but then I factory reset it and wifi was just completely gone. but this reenabled the wifi...thank god. but no playstore/google account is a huge bummer! lmao
I appreciate the fast response though man! I'm not stupid with android, but dummy stock makes me scratch my head. I can throw adb commands all day but I just cant push install them for some reason...maybe im just rtarded
I had some issues just pushing too, try using these commands.
Code:
adb root
adb remount
(from inside the extracted gapps folder)
adb push system /system
WORKED!
Thanks man! Went perfectly smooth! I forogot about pushing the full folder like that. Havent had to do it inna while but yeah man it went smooth as day! Thanks! now to just wait for the factory img...lol
BTW do you know what I have to rename the tablet under about device to make it look as the shield tablet to the playstore? I was using grid when the wifi crapped but I cant use grid as it says my device isnt supported.
Gytole said:
Thanks man! Went perfectly smooth! I forogot about pushing the full folder like that. Havent had to do it inna while but yeah man it went smooth as day! Thanks! now to just wait for the factory img...lol
BTW do you know what I have to rename the tablet under about device to make it look as the shield tablet to the playstore? I was using grid when the wifi crapped but I cant use grid as it says my device isnt supported.
Click to expand...
Click to collapse
I'm not sure exactly what it needs to be changed to, if someone could get a dump of the stock rom it would help. I tried to see if someone could get me a dump, but I've had no luck yet.
I hear yuh. Yeah I'm no help onna dump at the moment. If somebody could post even a screen shot of their about tablet I can rename the stuff directly. I use ROM Toolbox Pro and use the build prop editor. You just rename the builds to the stock nvidia one and you should be golden as the play store reads it as stock nvidia android...I think...I had to do it with the kindle fire back in the day to make it look like a Nexus 7.
Gytole said:
I hear yuh. Yeah I'm no help onna dump at the moment. If somebody could post even a screen shot of their about tablet I can rename the stuff directly. I use ROM Toolbox Pro and use the build prop editor. You just rename the builds to the stock nvidia one and you should be golden as the play store reads it as stock nvidia android...I think...I had to do it with the kindle fire back in the day to make it look like a Nexus 7.
Click to expand...
Click to collapse
Yes, you should be able to change a few things to make it work. I think most of what you can se is cosmetic and you'll have to change the ro.build.fingerprint too if I'm not mistaken.
shield tabletiers
Hopefully someone who is rooted/stock is willing to send us some screen shots. I actually kinda prefer this build over the stock nvidia one...its a lot faster. Theres absolutely no lag...granted I use sd maid/unlocker, fstrim, and nova. But so far this rom has been great. And you cant beat that barebone feel of android! Although the nvidia optimizer is there its unavailable through the settings menu. You can tell how stuff is like in there but hidden. Theres pros and cons to both. I just need to get the right build props to make the playstore see this as the shield tablet. Youve been a great help bub btw I appreciate it.
It just sucks that my first experience with the shield tablet was a bad install of android out of the box? Thats the first time ive ever had a software related wifi failure. The only other time was eith my droid 2 back in the day. LOL
Btw Other Shield Tablet owners, this is the screenshot I need from YOU so i know what to change my props too. Im using rom toolbox pro, but the lite version allows adjustments too. All I need is the screenshot! Much appreciated!
Gytole said:
Hopefully someone who is rooted/stock is willing to send us some screen shots. I actually kinda prefer this build over the stock nvidia one...its a lot faster. Theres absolutely no lag...granted I use sd maid/unlocker, fstrim, and nova. But so far this rom has been great. And you cant beat that barebone feel of android! Although the nvidia optimizer is there its unavailable through the settings menu. You can tell how stuff is like in there but hidden. Theres pros and cons to both. I just need to get the right build props to make the playstore see this as the shield tablet. Youve been a great help bub btw I appreciate it.
It just sucks that my first experience with the shield tablet was a bad install of android out of the box? Thats the first time ive ever had a software related wifi failure. The only other time was eith my droid 2 back in the day. LOL
Btw Other Shield Tablet owners, this is the screenshot I need from YOU so i know what to change my props too. Im using rom toolbox pro, but the lite version allows adjustments too. All I need is the screenshot! Much appreciated!
Click to expand...
Click to collapse
thanks bud!
dcaplinger76 said:
Click to expand...
Click to collapse
Thats what I needed! I'll punch it in and see what the playstore thinks!
dcaplinger76 said:
Click to expand...
Click to collapse
Can you send me this one too? And youre on stock right? Like the Tablet came out of the box and you rooted?
Gytole said:
Can you send me this one too? And youre on stock right? Like the Tablet came out of the box and you rooted?
Click to expand...
Click to collapse
Yep, stock and rooted
Thanks man!
Your awesome for the shots! So far no luck but ill cha ge the prkps from your next 2 also and ill post back!
---------- Post added at 12:57 AM ---------- Previous post was at 12:46 AM ----------
dcaplinger76 said:
Yep, stock and rooted
Click to expand...
Click to collapse
I noticed what was wrong, after changing like 20 lines, including the fingerprint which SUCKED! The one that I needed to change was the ro.product.build!
I had it, just by guessing at SHIELD TABLET, and while my gf and I were lookingat it I randomnly noticed that it was SHIELD Tablet, and not SHIELD TABLET! I REBOOTED AND IT WORKED!! YOU SIR, ARE AWESOME!! I appreciate the help!! And Keith, when you built the img's I noticed you put your name in them? You should just change that one line to SHIELD Tablet, and you'll basically have you're own rom with the playstaore recognizing your tablet as the Shield Tablet! Thanks guys, a million!
Gytole said:
Your awesome for the shots! So far no luck but ill cha ge the prkps from your next 2 also and ill post back!
---------- Post added at 12:57 AM ---------- Previous post was at 12:46 AM ----------
I noticed what was wrong, after changing like 20 lines, including the fingerprint which SUCKED! The one that I needed to change was the ro.product.build!
I had it, just by guessing at SHIELD TABLET, and while my gf and I were lookingat it I randomnly noticed that it was SHIELD Tablet, and not SHIELD TABLET! I REBOOTED AND IT WORKED!! YOU SIR, ARE AWESOME!! I appreciate the help!! And Keith, when you built the img's I noticed you put your name in them? You should just change that one line to SHIELD Tablet, and you'll basically have you're own rom with the playstaore recognizing your tablet as the Shield Tablet! Thanks guys, a million!
Click to expand...
Click to collapse
It automatically uses the user name @ PC name when you build from source. Good to know
Sent from my wx_na_wf using XDA Free mobile app
Keithn said:
It automatically uses the user name @ PC name when you build from source. Good to know
Sent from my wx_na_wf using XDA Free mobile app
Click to expand...
Click to collapse
Oh! No big deal! Your name is still all in it. Its just the one line, I assume, thats seperating the playstore from recgonizing it as the shield tablet! Lol
This build has external sdcard issues. My 128 GB SD card shows as damaged, every other ROM with sdcard support (including stock) works fine. I'd love to be able to use a pure android build on the tab, any chance of making another build?
EDIT: seems to have issues with exfat formatted cards, works fine with sdcards formatted as fat32 ?