Related
I am not sure why, but suddenly everyone is calling everything 'rooting' when talking about the evo... this makes things very confusing in guides, etc.
Installing an engineering SPL is not the same as rooting! (but does require root level access in the OS)
The boot loading of android devices (esp HTC devices) generally goes:
SPL (secondary program loader) (can be stock or engineering build)
White skateboarding androids.
Recovery (RA Mon, stock, clockworkmod, etc)
Green/Orange on Black menu which allows flashing images and wiping data.
Android (can be rooted) (cyanogenmod, stock, etc)
The running android operating system
Not trying to make troll bait... just got sick of very confusing guides telling me to 'root' the SPL
Who (exactly) is everyone?
I've been reading $h!t everyday for 2-3 weeks now and haven't seen this issue (or at least been confused by anything relating to it)... At least not from any thread/guide that really matters.
I understand you think this applies to Dev's (and hence posted in the Dev section)... but I'm not seeing it.
ok, maybe *everyone* wasn't a fair justification. still though.. not a single one of the posts I see in the dev section use the SPL identifier.
Keep in mind I definitely appreciate the hard work of guide writers.. I just think that the terminology should stay consistent to what has been outlined by android/google/the G1/etc
http://forum.xda-developers.com/showthread.php?t=690762
http://forum.xda-developers.com/showthread.php?t=701835
http://forum.xda-developers.com/showthread.php?t=706411
http://forum.xda-developers.com/showthread.php?t=741294
http://forum.xda-developers.com/showthread.php?t=715915 (at least HBOOT/engineering is mentioned in this one)
etc.
Me neither. Plus posting this wouldn't change anything anyway. Are you the kind of person that likes to correct people's spelling mistakes too? Love those types!
Sent from my PC36100 using XDA App
kallisti5 said:
ok, maybe *everyone* wasn't a fair justification. still though.. not a single one of the posts I see in the dev section use the SPL identifier.
Keep in mind I definitely appreciate the hard work of guide writers.. I just think that the terminology should stay consistent to what has been outlined by android/google/the G1/etc
http://forum.xda-developers.com/showthread.php?t=690762
http://forum.xda-developers.com/showthread.php?t=701835
http://forum.xda-developers.com/showthread.php?t=706411
http://forum.xda-developers.com/showthread.php?t=741294
http://forum.xda-developers.com/showthread.php?t=715915 (at least HBOOT/engineering is mentioned in this one)
etc.
Click to expand...
Click to collapse
I think most of those guides mention gaining root AND unlocking NAND/loading a custom recovery?
And toasts guide (the 2nd link) specifically mentions via an engineering SPL build.
I'm not a dev... but it has been referred to as root, nand unlock and custom recovery for quite some time (since I've been rooting my Hero/Evo).
gmanvbva said:
Who (exactly) is everyone?
I've been reading $h!t everyday for 2-3 weeks now and haven't seen this issue (or at least been confused by anything relating to it)... At least not from any thread/guide that really matters.
I understand you think this applies to Dev's (and hence posted in the Dev section)... but I'm not seeing it.
Click to expand...
Click to collapse
I didn't notice either.
kallisti5 said:
The boot loading of android devices (esp HTC devices) generally goes:
Click to expand...
Click to collapse
"Android" should be capitialized.. I hate it when people don't capitalize it right.
I thought we were going to use 'jailbreaking' as the new term!
sigh...
kallisti5 said:
sigh...
Click to expand...
Click to collapse
That's what I did when I read this waste of forum space.
12MaNy said:
That's what I did when I read this waste of forum space.
Click to expand...
Click to collapse
QFT.
Don't get your knickers in a twist over terminology. Learn the new terminology if you're coming to a new phone/OS and be content.
so my recovery isn't rooted? how do i do that? I want my recovery to have full access to my roots!
12MaNy said:
That's what I did when I read this waste of forum space.
Click to expand...
Click to collapse
Really? Wow. Sorry to hear your so limited on bandwidth. You disable images in IE6? I hear that helps lower the bandwidth usage.
smw6180 said:
Don't get your knickers in a twist over terminology. Learn the new terminology if you're coming to a new phone/OS and be content.
Click to expand...
Click to collapse
Yeah, Fair enough. As nothing has really changed with the different stages of Android boot with the Evo I didn't think the terms for did either.
Didn't think my 1 cent worth thoughts would cause that big of an uproar.
I am aware that the questions i am about to ask might have been asked 1000 times, but the search feature didnt help this time, so i am sorry if i am bugging out somebody. So here is what happened.
I got a mytouch 4g phone today, and i rooted it using gfree as it was the first sticky on the forum. i did a bit of research about bricks on mt4g (have been playing with androids since a long time) and didnt find anything about the emmc problem. then i tried gfree and it was easier than i thought. so i unlocked it (s-off), changed cid and unlocked sim (all using gfree -f). and i installed cwm and installed a rom. everything is working perfect.
but i discovered all the threads about bad emmc and bricks and stuffs like that. so i checked my emmc name and it came out to be the bad one. and i figured out that i did a big mistake. so i thought about restoring gfree backup and using the other root method (hboot s-off not radio). i was just about to restore the backup using gfree, then i noticed that my backup file (.bin file) was not present on my sd. i was shocked at first. then i found that i could s-on the phone using gfree without using backup bin file. but if i do that, will my phone not get emmc bricked like others? or do i need my backup file? can i use someone else's bin backup file? if yes, can you give me yours? any help would be really appreciated. i am worried that i might get a brick anytime. i was planning to make some tools for mytouch 4g (like i did for hd2) but i guss i will not be able to do that anymore cuz i might get a brick anytime. thanks for reading.
Edit: do all bad emmc phones using gfree get bricked? and what is the average period before it gets bricked (yea im too worried ) and is there anythign i could do now? (except for sending it for replacement since i bought it off craigslist)
This gfree and bad eMMC is just a correlation. Nothing has been proven to be a fact just yet. I've rooted my phone via gfree about 3 months ago now and I flash at least 2-3 times a week and nothing happened so far (I have the bad eMMC by the way). Everything seems fine for now.
I've also came across people that have the bad eMMC and have bee rooting and flashed hundreds of time for 6 months and going, so it's not a definite that your phone with the bad chip will die soon, so just keep that in mind.
But yes, it has happened to numerous people with the bad chip. Honestly, I would just ride it out and see what happens. If it dies just exchange it through T-Mobile.
You can't root the phone with "bad" eMMC by root.sh method, so you shouldn't even bother trying.
Jack_R1 said:
You can't root the phone with "bad" eMMC by root.sh method, so you shouldn't even bother trying.
Click to expand...
Click to collapse
I used this method on mine with the "bad chip" and had no problems.
tooter1 said:
I used this method on mine with the "bad chip" and had no problems.
Click to expand...
Click to collapse
You used g-free previously.. or root.sh wouldn't work on bad eMMc.
Please refer to the guides.
root.sh is guaranteed not to work on bad eMMc's unless g-free had previously been used.
Also not all "can't open /cache/recovery/log" errors in recovery are due to a dead eMMC chip. It can happen if your cache partition gets corrupted. Earlier this week, I had a bad flash--forgot to verify the md5sum before flashing, and after things started messing up, wifi not working, force-closes, etc...
So I went back to restore a nandroid backup I had made prior to the bad flash and got the dreaded "can't open /cache/recovery/log" error. I plopped the PD15IMG.zip on my sdcard and flashed it through hboot without any fail-PU errors.
So no, a M4G2DE eMMC chip doesn't always mean you'll have a brick. And cache partition errors in recovery don't always mean the eMMC chip died. What it means is that the "bad" eMMC chip has a much higher failure rate than the "good" chip. So if you have a "bad" chip, judging by the numbers, you have a much higher chance of ending up with a brick at some point.
might sound silly but where would I get the PD15IMG.zip file??
I thought PD15IMG.zip was the RADIO file.. but i think am pretty clueless...any enlightenment ?
3p4145 said:
might sound silly but where would I get the PD15IMG.zip file??
I thought PD15IMG.zip was the RADIO file.. but i think am pretty clueless...any enlightenment ?
Click to expand...
Click to collapse
Any file that has to be flashed through the bootloader (such as the stock RUU, radio files, etc) has to be named PD15IMG.zip for the bootloader to recognize it. There are two threads in the dev section that have the stock RUU you're looking for. A little searching should locate them.
Hi,
I'm a newb, and was thinking about rooting my phone and installing a different rom, but I read about this bad eMMC problem. I was wondering, if I have the bad eMMC and I don't root and install roms, will I still have the same problem that my phone might just die? Or is it only if I flash roms onto my phone?
Thanks,
Andy
Yes, if the "bad" eMMC in your phone is really bad - it'll die no matter if you flash ROMs or not. Just slower if you don't.
For what it's worth, I've had my phone with the bad emmc since December ... rooted since January & flashing roms ever since... no dead emmc. (Yet, if ever).
Sent from my HTC Glacier using XDA App
So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?
DashBlacK said:
So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?
Click to expand...
Click to collapse
+1
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
good question. i don't have an answer to that. i've warrantied my phone, got another bad emmc around april? & have rooted & been flashing roms. phone hasn't died.
M4G2DE is just a regular chip. It's used for at least 3 other phones (G2, DHD, DS). I have one in my wife's Desire S, and it's rooted and running VU.
All the hype of the "bad" chip has gone WAY out of proportions.
DashBlacK said:
So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?
Click to expand...
Click to collapse
Yes, there is a good and a bad batch like most things in the world. My mytouch had the bad emmc from march to now and it's been fine. I flash like a maniac and it's been fine.
But like someone mentioned before if you really do have the bad bad chip; eventually your phone will just crap out. There are several cases on it from people who has never rooted before.
What people usually don't talk about is that some "good" chips are also bad and will eventually go bad overtime. Someone made a poll and discovered that the bad emmc chip showed a higher susceptibility of the phone failing. But remember it is only a poll. The poll also said that blacks are more susceptible than other colors... Why? because more blacks were distributed. It is possible that more bad chips were distributed. who knows?
Hope that clears some things up for everyone.
Teo032 said:
Yes, there is a good and a bad batch like most things in the world. My mytouch had the bad emmc from march to now and it's been fine. I flash like a maniac and it's been fine.
But like someone mentioned before if you really do have the bad bad chip; eventually your phone will just crap out. There are several cases on it from people who has never rooted before.
What people usually don't talk about is that some "good" chips are also bad and will eventually go bad overtime. Someone made a poll and discovered that the bad emmc chip showed a higher susceptibility of the phone failing. But remember it is only a poll. The poll also said that blacks are more susceptible than other colors... Why? because more blacks were distributed. It is possible that more bad chips were distributed. who knows?
Hope that clears some things up for everyone.
Click to expand...
Click to collapse
Interesting info...
Sent from my HTC Glacier using xda premium
HTC Mytouch 4G EMMC
I sent in my lifeless HTC Mytouch 4G to have 'Jtag Service' done to it as thats what I thought it needed, but instead they performed this 'EMMC Repairs Service' which was what they diagnosed the problem to be. An it fixed it, before sending it in, all my phone did was to charge batteries. checkout their website they even send the bad EMMC chip with the phone :good: hope I helped someone be blessed :angel: here is the URL---> mobiletechvideos.mybigcommerce .com/htc-mytouch-4g-emmc-chip-repair-replacement/
Nice how much was that
Sent from my HTC Glacier using xda app-developers app
bramz said:
I sent in my lifeless HTC Mytouch 4G to have 'Jtag Service' done to it as thats what I thought it needed, but instead they performed this 'EMMC Repairs Service' which was what they diagnosed the problem to be. An it fixed it, before sending it in, all my phone did was to charge batteries. checkout their website they even send the bad EMMC chip with the phone :good: hope I helped someone be blessed :angel: here is the URL---> mobiletechvideos.mybigcommerce .com/htc-mytouch-4g-emmc-chip-repair-replacement/
Click to expand...
Click to collapse
I almost had the JTAG service done too. Before I did I did my research and come to find out that when I explained my situation to one of their techs I was emailing, he said that my situation was folly and there was nothing they could do. He stated it was the dreaded "bad eMMC chip problem" yet all i had was cache and recovery errors just like what was mentioned above. Formatted my sdcard, put the stock T-Mobile GB PD15IMG.zip on there, flashed, and booted right up. Lost root of course, but able to get it back to rooted state and been flashing custom roms ever since. Pretty sure just like what was stated above... Blown WAY out of proportion. Hope this helps some people with their anxiety about this issue.
I recently updated to Royalginger 3.0 and it seems like to me that I'm experiencing less signal on my wifi connection sitting at my desk downstairs than I was before, on the stock rom. Also my cell bars are dramatically lower. Is there anything that can be recommended? I'm kind of hesitant to change radios after reading about the eMMC chip problem (i've got the bad one).. Any info would be appreciated by the vet's of these forums..
Thanks
Changing the radio is not as big of as ordeal as you would think. Just follow the directions on the radio thread and verify your md5sum before flashing. It really is easier than flashing a rom.
eqjunkie829 said:
Changing the radio is not as big of as ordeal as you would think. Just follow the directions on the radio thread and verify your md5sum before flashing. It really is easier than flashing a rom.
Click to expand...
Click to collapse
What I was concerned about is the eMMC chip (the bad one) and flashing radio, any idea if one can break the other?
cballard37 said:
What I was concerned about is the eMMC chip (the bad one) and flashing radio, any idea if one can break the other?
Click to expand...
Click to collapse
It can but just cause you have a bad chip doesn't necessarily mean it will go bad. Then again you never know. Its kind of like playing Russian roulette
Sent from my Google Nexus 12! yup I'm from the future
Rooted a friend's phone using visionary, put root folder on SD card, followed Prompts in terminal emulator, reboot and S still show's on.. any suggestions.. I never had this problem rooting my own mytouch.. & The phone hasn't been updated, still running 2.2.1
Check out the Post Your eMMC thread in the general section, it will tell you how to check which one the phone has using terminal emulator. Phones with the "bad" eMMC cannot be rooted using the root.sh method, but can be with g-free.
King350z said:
Rooted a friend's phone using visionary, put root folder on SD card, followed Prompts in terminal emulator, reboot and S still show's on.. any suggestions.. I never had this problem rooting my own mytouch.. & The phone hasn't been updated, still running 2.2.1
Click to expand...
Click to collapse
Root via gfree method...
Sent from my HTC Glacier Sense 3.0 using XDA app
King350z said:
Rooted a friend's phone using visionary, put root folder on SD card, followed Prompts in terminal emulator, reboot and S still show's on.. any suggestions.. I never had this problem rooting my own mytouch.. & The phone hasn't been updated, still running 2.2.1
Click to expand...
Click to collapse
Before I learned about this website I had rooted my phone using the tutorial from the unlockr's website, gfree method.. Worked great.
saranhai said:
Root via gfree method...
Sent from my HTC Glacier Sense 3.0 using XDA app
Click to expand...
Click to collapse
you need to be careful before throwing out the idea that ./gfree is a fix all. It's not. It's a huge problem on phones that have bad eMMC chipset.
neidlinger said:
you need to be careful before throwing out the idea that ./gfree is a fix all. It's not. It's a huge problem on phones that have bad eMMC chipset.
Click to expand...
Click to collapse
Yea... That's what happened to my old MT4G
Best suggestion is to just keep stock.
Sent from my HTC Glacier Sense 3.0 using XDA app
Does that mean I shouldn't put custom roms on my phone? What if I get bored?
U can also use launchers and home replacements if u get bored wit stock
McSurge45 said:
Does that mean I shouldn't put custom roms on my phone? What if I get bored?
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
McSurge45 said:
Does that mean I shouldn't put custom roms on my phone? What if I get bored?
Click to expand...
Click to collapse
I wouldn't say don't put roms on your phone EVER.... but before you do make sure you check what emmc chip you have. If you have the bad one you're sort of giving your phone a death sentence by rooting with gfree. It might last a good while, but most likely your phone will brick itself at some point. And considering the root.sh method doesn't work with the bad chip, gfree is your only option.
Basically, if you have the good chip feel free to flash roms to your delight, AFTER YOU INFORM YOURSELF HOW. But if you have the bad chip just know that your phone is at risk of dying if you root it.
AlanB412 said:
I wouldn't say don't put roms on your phone EVER.... but before you do make sure you check what emmc chip you have. If you have the bad one you're sort of giving your phone a death sentence by rooting with gfree. It might last a good while, but most likely your phone will brick itself at some point. And considering the root.sh method doesn't work with the bad chip, gfree is your only option.
Basically, if you have the good chip feel free to flash roms to your delight, AFTER YOU INFORM YOURSELF HOW. But if you have the bad chip just know that your phone is at risk of dying if you root it.
Click to expand...
Click to collapse
I have rooted and unrooted my phone(with the bad chip) many times, which writes to the emmc and power cycles it and flash at least 5 ROMS a week and flash back to nandroid backups as well during the week, so saying the bad chip and gfree combine is the issue is not true... There are cases of the root.sh emmc failure as well just not as many.... There is something more at bay with the bad emmc that has to be a common fail point not known yet. Cause as much as my chip has been power cycles and written to, it should be the first to fail! Just my two cents...
Sent from my HTC Glacier using XDA Premium App
irrelephant said:
I have rooted and unrooted my phone(with the bad chip) many times, which writes to the emmc and power cycles it and flash at least 5 ROMS a week and flash back to nandroid backups as well during the week, so saying the bad chip and gfree combine is the issue is not true... There are cases of the root.sh emmc failure as well just not as many.... There is something more at bay with the bad emmc that has to be a common fail point not known yet. Cause as much as my chip has been power cycles and written to, it should be the first to fail! Just my two cents...
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
+1 I have heard more horror stories about root.sh and visionary method failures then gfree method there's got to be more to the story then just the bad emmc chip and using Gfree to root. I used Greer to root as well and have bad emmc but good display and I'm a crack flasher, tho I've slowed down a bit after finding my 3 favorite roms.
Sent from my HTC Glacier using XDA Premium App
@Irrelephant & DrunkBastard
I don't intend to discount your experiences with what I said. Like I posted before, I have read about plenty of people with bad chips who have spent a long time flashing and reflashing their phones, so I can totally believe that you guys haven't had any problems with it or gfree. And considering the nature of rooting I can also believe that people have messed their phones up with the visionary method as well, especially since I actually was one of those people. However, I was fortunate enough and informed enough to fix it without any lasting damage.
As you said, the emmc chip problem is something that nobody is entirely sure about, but the general consensus seems to be that they are much more likely to fail when you have the bad model, whether or not you have rooted your phone or flashed roms or anything. I've even read some cases where people with entirely stock phones have had it fail on them.
On top of that, the gfree method, while very reliable, relies heavily on that chip. I can't honestly say that I know the exact processes that are different between the visionary method of rooting and the gfree method, but from what I've read gfree is more of a hardware oriented approach to achieving s off while visionary is more software oriented. Feel free to correct me if I'm wrong, I'm here to learn just like everyone else.
I guess it was sort of bold(and grim) for me to say that having a bad chip and then rooting it was a death sentence for your phone. What I was trying to get across was that the bad chips definitely do have a worst reputation. And while anybody who wants to root their phone should try and be as well informed of the risks and processes as possible, I think that if you have a product with a bad reputation you should read up about the problem and what extra risks it may cause.
ALL of the evidence doesn't point towards death sentences for bad chipped phones, but a lot definitely points to major problems with the bad chips, and that's something people should know about, particularly if they are one of the people who have it.
So in the end, people just need to try and make well informed decisions about what they will do with their phones(and the same can be applied to life I guess). That's what I was trying to get across. Sorry if I bothered you guys with my strongly worded post before, I just wanted to make sure people knew what they were getting into before they jumped into the pool.
____________________________________
Sent from the AFB Corporation's Main Communication Portal
AlanB412 said:
As you said, the emmc chip problem is something that nobody is entirely sure about, but the general consensus seems to be that they are much more likely to fail when you have the bad model, whether or not you have rooted your phone or flashed roms or anything. I've even read some cases where people with entirely stock phones have had it fail on them.
Click to expand...
Click to collapse
That.
Moreover, I had an experience with Desire S (HTC Saga) with the aforementioned "bad" chip, and I can confirm it's prone to failure even in completely stock form. The "bad" chip seems to have a bad production run or post-silicon verification issues, since there are many perfectly fine specimens, yet more than enough reports of failing devices, not necessarily rooted. Of course, vast majority of reports on XDA would be of rooted devices, since this is what XDA is about.
Judging by the time-to-failure reports for those chips, it's probably safe to say that 2-3 weeks of heavy use would be a good checkpoint - if a chip is prone to failure, it'll fail within 2-3 weeks of heavy use, and if it didn't fail - it'll most likely serve the regular lifetime of eMMC (which isn't eternal either).
There was an interesting hypothesis for this chip's failures in one of the threads at Desire S section, which might be worth checking. It was said that the chip is most likely to fail when it has power failure (intentional or not) during write cycle. Which means, pulling the battery while installing the app, for example, has a high chance of bricking a completely stock device.
i totally agree with both of you guys!!! and as jack stated, i think there was just a bad production run, or lot run for that matter... but all in all, rooting your phone is taking a chance since there are always unknown variables that could come to play. i have noticed that my phone with the bad chip has always been a bit more wonky that the one with the good chip, but i continue to use the bad one to flash away with because it was the one i started all the crack flashing on and if it fails, then it fails! i kinda wish it would fail so that i can start poking around at it to see what craziness i can find in there... i am all about troubleshooting things and if all else fails then i can send it in under insurance!
i think people should read and know what could happen and make a choice based on that, but i see too many ppl trying to scare off users because they have the so-called bad chip... but the bad chip has been good to me over a yr now and i continue to abuse this bad boy more than the average user!
and nothing anyone says on here is going to get me BUTT HURT, i am always open to a good debate on a controversial topic... so long as it is civil that is, cause if it gets ignorant, then i just leave it at that... to in the end, thank yall for holding open debate with me as it keeps me informed and thinking!!!
I wish you could buy the phone and pick the rom it comes with......
Hey everyone!
So I have searched high and low for an answer to this problem. I hope I am posting in the correct place. I just got a VitalASC ST1011 tablet and I am looking for a way to put a custom ROM on it. I was able to root it and it did root correctly, but there is absolutely nothing on this exact tablet for ROMs. My question is, are most RK 3188 tablets in the same category? Like will my tablet work with most 3188 ROMs?
Thanks guys!
toonwar said:
Hey everyone!
So I have searched high and low for an answer to this problem. I hope I am posting in the correct place. I just got a VitalASC ST1011 tablet and I am looking for a way to put a custom ROM on it. I was able to root it and it did root correctly, but there is absolutely nothing on this exact tablet for ROMs. My question is, are most RK 3188 tablets in the same category? Like will my tablet work with most 3188 ROMs?
Thanks guys!
Click to expand...
Click to collapse
The answer is NO, since the hardware is different like bluetooth/wifi/bootloader/file structure etc... for example a 3188 with ap6120 wifi chip is not the same as 3188 with MTK wifi chip.
buhohitr said:
The answer is NO, since the hardware is different like bluetooth/wifi/bootloader/file structure etc... for example a 3188 with ap6120 wifi chip is not the same as 3188 with MTK wifi chip.
Click to expand...
Click to collapse
I had thought so. The thing is I am used to rooting and messing with big brand devices like my S3 and such. Is there any way for me to find out what ROMs will work on my device?
toonwar said:
I had thought so. The thing is I am used to rooting and messing with big brand devices like my S3 and such. Is there any way for me to find out what ROMs will work on my device?
Click to expand...
Click to collapse
I'm sorry but there are none custom rom support for this device or very very limited. Just a suggestion for future reference, if you like custom rom and such, you should investigate for rom support first before purchase the device. Maybe someone out there who would know some forum that can support this, please chime in. In the mean time you just have to wait and see....
buhohitr said:
I'm sorry but there are none custom rom support for this device or very very limited. Just a suggestion for future reference, if you like custom rom and such, you should investigate for rom support first before purchase the device. Maybe someone out there who would know some forum that can support this, please chime in. In the mean time you just have to wait and see....
Click to expand...
Click to collapse
Sadly I had no choice. It was a surprise birthday gift from my parents. It's all good though! It's not a bad tablet, I just like custom ROMs. I appreciate the help though!
Nice of you to be nice to him. Maybe there is a humble pie in his fridge..lol
Sent from my A200 using xda app-developers app
How were you able to root it? i have the same tablet and have been trying to root it but do not want to lock it up..... I put a bigger class 10 32gb sd card and am trying to run everything of that instead of nad flash....
toonwar said:
Hey everyone!
So I have searched high and low for an answer to this problem. I hope I am posting in the correct place. I just got a VitalASC ST1011 tablet and I am looking for a way to put a custom ROM on it. I was able to root it and it did root correctly, but there is absolutely nothing on this exact tablet for ROMs. My question is, are most RK 3188 tablets in the same category? Like will my tablet work with most 3188 ROMs?
Thanks guys!
Click to expand...
Click to collapse