to make a long story short I had to go back to stock after something happened when I tried to flash the new Carbon ROM. Anyway, the screen works and the buttons, but touch is gone. Not sure what to do .. don't have root, don't have CMW, can't navigate.
Any ideas?
You can run recovery (CWM) from sd card, on any OS.
About touch screen, have you run the 10 touch firmware at any time from a cm10 or newer ROM?
Sent with my Dinc4G
You know, I didn't even think of that... I'm so used to just installing it after a reflash. As far as the 10 touch mod, I believe I did that quite a while ago, but I have wiped/reflashed quite a few times since then. Would that still affect the system?
Yeah, as far as I know re-installing the stock ROM does not flash you back to 2-touch; you'd have to do that if you want to use stock ROM again. However, there's no need if you plan to go straight back to Carbon (or any other full android ROM that supports 10-touch) via a bootable SD card.
I am planning on running carbon, but I was trying to get back to a stock state because it was hanging at the carbon logo and no matter what I tried, it didn't work. I figured that starting from scratch would work... I didn't count on losing touch lok
criscross79 said:
I am planning on running carbon, but I was trying to get back to a stock state because it was hanging at the carbon logo and no matter what I tried, it didn't work. I figured that starting from scratch would work... I didn't count on losing touch lok
Click to expand...
Click to collapse
All you really need to do is flash a cm10/cm10.1 based ROM - they all have the 10 touch firmware app pre-installed. Then just run the app to go back to 2 touch. You can then go back to stock no problem.
Look around though, I think Succulent has a newer SD CWM file, you may have some issues flashing CM10/CM10.1 with an older version of CWM.
Good Luck
Same issue
Man my nook tablet was running great. but a few days ago my daughter was playing with it and I have no idea if she pushed the touch app on purpose. I have a feeling she did. Now its not working, it just stays on locked screen. Someone help.
centenj said:
Man my nook tablet was running great. but a few days ago my daughter was playing with it and I have no idea if she pushed the touch app on purpose. I have a feeling she did. Now its not working, it just stays on locked screen. Someone help.
Click to expand...
Click to collapse
If your NT is running a recent CM10.x build it should work with either 2-touch or multi-touch. So your problem might not be Touch-FW related. But if you suspect it is, as @DavDoc suggested above, burn one of Succulent's CM10 SD image to SDcard, boot that SDcard then use the Touch FW Flasher app to flash back to 2-touch.
Oh No
Well I guess its not the problem. I did a complete factory reset and still the problem exsist. I rooted it again and flashed cm7 with the gapps and still the same problem. I guess it decided to really give up. Any suggestions anyone.
centenj said:
Well I guess its not the problem. I did a complete factory reset and still the problem exsist. I rooted it again and flashed cm7 with the gapps and still the same problem. I guess it decided to really give up. Any suggestions anyone.
Click to expand...
Click to collapse
Were you running CM10 when this happened? Have you tried burning the CM10 card suggested and run it? I suspect there is a hardware error, but I just want confirmation that you actually have tried what's already suggested. CM7 will not work woth multitouch. You need to try CM10 if you haven't!
right
Yeah when this happened I was running CM10. I haven't tried the SD card method but I'll do it when I get home. Any place where I can find a CM10version in SD.
centenj said:
Yeah when this happened I was running CM10. I haven't tried the SD card method but I'll do it when I get home. Any place where I can find a CM10version in SD.
Click to expand...
Click to collapse
It's worth a try, but if you were running CM10 when it happened it probably won't help. But it's worth a try anyway!
try reflashing a compatible kernel. it should do the trick
Kernel?
rafiur said:
try reflashing a compatible kernel. it should do the trick
Click to expand...
Click to collapse
Hey where can I find that.
centenj said:
Hey where can I find that.
Click to expand...
Click to collapse
http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Weird
OK something weird is going on. I returned back to stock and the touch was not working. So I Rooted it and flashed CM7 and it still didnt work. So I went to CWM and flashed CM10.2 and still didnt work. I gave up and left the nook off for a while. I turned it back on and it started working. WTF. The next day I turned it on from sleep mode and it didnt work again. I did the same procedure the next day and it did the same thing. Someone help!
DavDoc said:
You can run recovery (CWM) from sd card, on any OS.
About touch screen, have you run the 10 touch firmware at any time from a cm10 or newer ROM?
Sent with my Dinc4G
Click to expand...
Click to collapse
exactly what i was thinking , did this myself , even made a post about it last week , stock doesnt support it so it ends up non responsive ,
but from your last post , that sounds like it was working then not working then working and not working , it might be a hardware failure ....
if its out of warranty crack it open , inspect the cables to the screen under a microscope
Do you have problem with whole touch screen or a part. I have unresponsive problem of touch screen on the top then bottom until it happened with whole touch screen.
That's hardware problem. My friend has the same. Nook Table has low quality touch screen, so after 1 years or more, the touch screen becomming unresponsive!
The best solution is replace touch screen with new one but I recommend you change from Nook Table to another like Nexus 7
Related
I recently installed the nightly build of ICS on my samsung vibrant. Today the phone had a error that said encryption cannot be completed phone must be erased. I let it do a factory reset . Then I got stuck in a endless boot cycle showing the vibrant logo and then the cynogen guy for a few seconds then reboot. I could still access the recovery menu but it refused to flash any roms I threw at it. I downloaded and ran odin 1 click recovery and it changed my tmobile phone to a att phone. And it lost the recovery mode. It just shows att screen first then samsung vibrant second and just reboots. I can still get into download mode and flash roms using odin 3 but no matter what rom I select or if I choose repartion or not the flash will go through successfully but then the phone reboots into same problem as before. I suspect the recovery files are gone since no button combination anymore gets me into recovery. Is there anything else I can do?
Man I am having the exact same problem. I really hope someone can figure something out soon. Did yours randomly get that error? Or did you actually try to encrypt your phone?
Sounds like you used the wrong Odin 1 Click. If it installed Captivate bootloaders, that would cause a problem.
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
It just happened
It happened on its own. Was working fine all day walked in my house as as soon as it hit wifi it started going crazy. I had the data plan turned off months ago. Maybe theres something to it connecting up to the net. I have found out if you install your sim you get a reduced menu of recovery options but without sim it just constantly reboots. it only gives option of reboot, reinstall packages,delete all user data, delete cache data. If you try reinstalling the packages theres nothing there. Deleting caches made no differance. ADB does work and responds while in this lesser form of recovery is there a easy way to use adb to force a full system flash?
Thanks
That link was perfect had a link to eugenes no brick froyo rom which fixed my problem. Dloaded that used its pit and tar files and repartioned and im back to stock. Going back to team whiskeys mod. If all ICS roms has bugs like that is unusable.
bfranklin1986 said:
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Do you have access to BOTH your internal and external SD cards? The Encryption Bug is totally and completely random and does not discriminate. There is currently no known reason or solution. Several of us across a few different devices have been working on this for months.
Consider yourself luck if you have access to both SDs as you are the 2nd person to get in and out today. Many, many others have not been as fortunate.
If you could please pull up this thread and put as much information in there as possible, it would be greatly appreciated. Are you unlocked, what happened right before, what bootloaders are you on, what ROM were you trying to flash, what ROM did you end up getting booted,....those types of things. As much detail as you can muster together, after you catch your breath and relax a minute.
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Update
I think I might have pulled the trigger to quick. While the link above did give me Eugenes rom which at least got me out of the boot cycle both internal and external sd shows 0 and I am unable to load anything on either card. I have tried differant microsd cards all of them show the same thing. So eugenes rom got me working kind of but cant store anything at all. That sucks loved my vibrant and its almost out of contract and planned on using on prepay.
Agreed 100 %
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Moped_Ryder said:
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Click to expand...
Click to collapse
chickenmon said:
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Click to expand...
Click to collapse
I got tagged on a Nook Color with it. BUT, since the Nook Color has a feature that no others I think do (you can boot a ROM straight from an SD card and not mess with the oringinal OS at all), I was able to just pull my Microsd out and reformat it and then put CM7 on it for my wife.
So far from what I have seen and been working on:
Vibrant, Captivate, My wife's Nook Color, A few Transformers, SGSII,...
Anything I can do?
Anything I can do to get my partions right again? I can flash the twm 5.2.2 but none of the roms i throw at it including ics passion stays in a boot cycle. Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
chickenmon said:
... Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
Click to expand...
Click to collapse
You may want to bring up this issue directly in Merio90's thread. I believe Alex9090 went thru possibly similar issues and may be able to help you in that thread (unless she happens to pop in here).
I'm assuming you were trying to mount sdcard and emmc within recovery first (storage and mounts)? If you do have access to recovery again and can mount the external sdcard, maybe try repartitioning the card within recovery (using the parameters in Merio90's instructions)? Then transfer your rom zip and re-flash.
People have actually flashed Eugene's Froyo post-EU ... but without an ext sdcard. Quite an oddity. It's the only one (AFAIK) that'll fully boot up (even after losing int sdcard access due to EU) yet without an external sdcard in place.
Your assumptions are correct. I cannot mount emmc. I cannot flash any rom via 2.5 or 5.2 recovery only through odin and only eugenes rom still allows phone to boot but no mounting of internal or external sds. Ive spent about 3 days on this. There must be some hardcore adb commands to force a true factory reset partioning and all. Very annoying. Thanks for the help if I find any ways to fix it I will repost it here.
Might be bricked?
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Not related at all to my original problem.
tenantrep said:
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Click to expand...
Click to collapse
First of all, not to sound like a ****; but it's rude to hijack someone elses thread. You should've created your own thread for this.
Second; you might have fried your bootloader which in turn, yeah, that's bad and you might have bricked your phone.
Did you try to boot into recovery via the battery pull method. If not, try that and see how it works. I would link you to the instructions but I'm too lazy and tired right now to search for it and again, this is someone else's thread. Just do a search for it and you should find it.
If you need more help or guidance, create your own thread and start there.
Noticed your running Ice Cream Zenwich rc1.3. How do you like it. Ive installed slim 3 times today and twice I have gotten the encryption error within a hour. Needless to say not impressed major pain in the ass to have to do a million and half tricks with awm, adb, popping sd cards in and out etc.
Update
Also the current build of ics slim does not allow the imei information to be retrieved from sim for tmobile requiring a reflash of the modem. You have to download and install a new modem. I used csm5. The guide on the link in this post dow work but its a real pain and requires lots of trial and error. Wondering if google intentionally bricking these things knowing we all got gadget lust for the sIII now.
chickenmon said:
Noticed your running Ice Cream Zenwich rc1.3. How do you like it ...
Click to expand...
Click to collapse
ICZen_rc1.8.3 (AOKP #39, ICS 4.0.4) + subZero #144 (New Test Kernel just released in mr_pyscho's RootzWiki kernel thread) is Linaro infused ... and I've got to say the combo is THE fastest rom experience I've ever had on my Vibe. Whatever MP did in his new test kernel just blows the doors off the previous performance limits.
Btw .. you keep encountering EU again. Really odd unless possibly your external card wasn't partitioned correctly. Not a knock directly on you, but it is a common occurrence lately. FYI, I repartitioned mine directly from recovery.
Also ... Br1cK'd (ICZen) and mr_psycho (subZero) are aware of the EU situation and try to include safeguards in their builds. However, until we know the exact root cause of EU, we're all just shooting in the dark. Imo, it's at least comforting to use a rom & kernel where the dev's are at least mindful of EU.
so my gtab will only show the three birds, i took the cover of the back and held down the reset button and it turned off then back on to the same screen. I even tried to nv flash it and it says that it currently update. Im not even able to get into recovery mode. Am i screwed or did i miss something, im sorta new to this stuff....thanks
1. What rom were you using?
2. Which version of CWM are you using?
3. What were you doing to the tablet when it froze like that?
There's a lot of things that can go wrong and which NVflash you use (250m partition or 350m partition) is going to be determined by which rom you wish to run.
The Gtablet for dummies site really helped me out while I was starting off, but it appears its no longer online.
Going to need some more info and I'll try to help as best and as fast as possible, but real life keeps me pretty busy most of the time.
tobalaz said:
1. What rom were you using?
2. Which version of CWM are you using?
3. What were you doing to the tablet when it froze like that?
There's a lot of things that can go wrong and which NVflash you use (250m partition or 350m partition) is going to be determined by which rom you wish to run.
The Gtablet for dummies site really helped me out while I was starting off, but it appears its no longer online.
Going to need some more info and I'll try to help as best and as fast as possible, but real life keeps me pretty busy most of the time.
Click to expand...
Click to collapse
i had ics, not sure what version, clock i think was 5. something. i know that this dont help much. i was able to get it working,
what i was trying to do was get it back to the way it came new so i could start all over with a new rom. Now i found what i thought was the stock rom but all it will do is sit on the screen where it says gtablet, i even let it sit over night,while i was at work and still the same screen.
Nobe (has some kick ass roms) has already done the legwork in another thread, try this:
http://forum.xda-developers.com/showthread.php?t=2070655
first download, should but you back at stock with a 1.2 branch ready to go.
I know it sucks, I've NVflashed dozens of times to work off of stock, I still get a little jittery every time I load another rom.
tobalaz said:
Nobe (has some kick ass roms) has already done the legwork in another thread, try this:
http://forum.xda-developers.com/showthread.php?t=2070655
first download, should but you back at stock with a 1.2 branch ready to go.
I know it sucks, I've NVflashed dozens of times to work off of stock, I still get a little jittery every time I load another rom.
Click to expand...
Click to collapse
so i tried reloading ics 4 beta that i had, after it said everything was installed and went to reboot it and just sat on the screen with birds. im able to turn off, go into recovery, and apx. So my father in law installed the 350 zip and jellybean 5.3 on his with no issues. i followed the same video he did and it said that everything installed good until i went to reboot, there it got stuck on the bird screen but im still able to do nvflash, apx and power down....Am i screwed ??
racefan82 said:
Am i screwed ??
Click to expand...
Click to collapse
We'll have to see.
See this thread, run the commands there and post the output.
Originally Posted by racefan82
Am i screwed ??
You may also try the detailed instructions by Raywaldo (Google Raywaldo for his site) on installing new ROMs on GTablet. In my opinion Smoother Bean v 1.5 (by nobe1976) is the best/fast ROM for this device.
I am in charge of several nook tablet (16gb) devices, these devices all run on the cyanogenmod nightlies. I fixed a problem with one of them recently, After fixing the problem I noticed it needed an update. After performing the update the tablet refused to boot (either shutting down before or sometimes during the bootloader).
Rather than flash back to the previous update my genius mind decided to try flashing the acclam_update zip and then flashing back to cm. The first half of this worked out well enough and I got the tablet on stock B&N software. However when I loaded the device I realised my error. some time ago I had flashed the updated touchscreen firmware that was included with the rom. Before flashing acclaim I should have flashed stock touchscreen firmware but did not, rendering the nook's touchscreen useless on the current software. Additionally (though I was aware this would happen) I now have the stock recovery mode instead of CWM.
I have struggles with adb as it is (I originally used a bootable CWM sd card for these devices but have since cleared that sd card) and I'm fairly certain I need access to the screen to use it on this device (I believe I need to activate something in the developer settings.)
So that's my problem. If anyone knows what I should do please help me out. If you need more info tell me what you need and I'll do my best to put it up here.
Run CM10 from sd card and flash the original firmware whle running it. Ready-made image tthat you can just download and burn http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Thank you
asawi said:
Run CM10 from sd card and flash the original firmware whle running it. Ready-made image tthat you can just download and burn http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Click to expand...
Click to collapse
That should work excellently, thank you very much.
Nookuser19 said:
I am in charge of several nook tablet (16gb) devices, these devices all run on the cyanogenmod nightlies. I fixed a problem with one of them recently, After fixing the problem I noticed it needed an update. After performing the update the tablet refused to boot (either shutting down before or sometimes during the bootloader).
Rather than flash back to the previous update my genius mind decided to try flashing the acclam_update zip and then flashing back to cm. The first half of this worked out well enough and I got the tablet on stock B&N software. However when I loaded the device I realised my error. some time ago I had flashed the updated touchscreen firmware that was included with the rom. Before flashing acclaim I should have flashed stock touchscreen firmware but did not, rendering the nook's touchscreen useless on the current software. Additionally (though I was aware this would happen) I now have the stock recovery mode instead of CWM.
I have struggles with adb as it is (I originally used a bootable CWM sd card for these devices but have since cleared that sd card) and I'm fairly certain I need access to the screen to use it on this device (I believe I need to activate something in the developer settings.)
So that's my problem. If anyone knows what I should do please help me out. If you need more info tell me what you need and I'll do my best to put it up here.
Click to expand...
Click to collapse
Just now experienced the same problem. I've been trying to get my nook to boot from SD for the last couple hours and nothing. Tried booting tethered to my laptop, the factory wall charger, etc. It's a stock Nook Table with the 10point touch driver...meaning completely unusable. Could you post what tools you used if you get it working?
topdawg7793 said:
Just now experienced the same problem. I've been trying to get my nook to boot from SD for the last couple hours and nothing. Tried booting tethered to my laptop, the factory wall charger, etc. It's a stock Nook Table with the 10point touch driver...meaning completely unusable. Could you post what tools you used if you get it working?
Click to expand...
Click to collapse
What sd card are you using? Do you have another one to try? Are you using the image I linked to or something else?
Sent from my BNTV400 using Tapatalk 2
asawi said:
What sd card are you using? Do you have another one to try? Are you using the image I linked to or something else?
Sent from my BNTV400 using Tapatalk 2
Click to expand...
Click to collapse
Just used a 4gb class4 through a memory stick reader. It's working beautifully now, except I need to repartition it.
Interesting bug though, the home button won't take it out of sleep any more. Only the power button..?
Hello,
I have an old HTC Hero (GSM) with a very old VillainROM on it, I haven't touched the phone for years. I now wanted to update with this ICS ROM (or potentially another one), however, I was unsure where to start, e.g. update my bootloader or whatever.
I tried copying the linked ROMs zipfile to the SD card, booting into my loader, wipe everything, and then "Install from zip". However, that fails while verifying the zip package.
I then also tried the newest official CM7 nightly for the hero, and that didn't produce above verify error.
Should I update my bootloader or something, or is just the ROM I tried broken? (for other people in that thread it seems to work).
What recovery do you use (CWM, AmonRA)?
Maybe you should try a newer one from here:
http://forum.xda-developers.com/showthread.php?t=1797626
derproblembaer said:
What recovery do you use (CWM, AmonRA)?
Maybe you should try a newer one from here:
http://forum.xda-developers.com/showthread.php?t=1797626
Click to expand...
Click to collapse
@derproblembaer Thanks for getting back to me! Just to close this, the phone wasn't really usable anymore, the touch was not working or acting weird on half the screen.
Elador said:
@derproblembaer Thanks for getting back to me! Just to close this, the phone wasn't really usable anymore, the touch was not working or acting weird on half the screen.
Click to expand...
Click to collapse
Yes exactly, why in the world does this happen? My friends HTC hero also, most of the times the bottom half of the phone does not work (touch). Thought a ROM problem so Flashed different ROM's and still the problem remains. He bought a new phone but he still has it, we could still try and see if we can do anything about that phone.
What can we use it for?
driverless said:
Yes exactly, why in the world does this happen? My friends HTC hero also, most of the times the bottom half of the phone does not work (touch). Thought a ROM problem so Flashed different ROM's and still the problem remains. He bought a new phone but he still has it, we could still try and see if we can do anything about that phone.
What can we use it for?
Click to expand...
Click to collapse
That's interesting! I assumed it was because I haven't been cleaning the screen for years and it was sticky etc., and even after proper cleaning it didn't work anymore. So I thought it was me and I should've taken more care And also, I mean it's really old.
However, maybe it's a Hero problem after all. And after thinking about it, it's not that old - it's from summer 2009 which makes is 5 years old. Hmm.
I had the same problem few years ago... two times with the same phone.
I lost my Nook Tablet for a while and just recently found it again. I'd like to update the recovery tool and put a new ROM on it so I'm looking for suggestions.
I had previously rooted it and installed ClockWorkMod and then it is running some version of an Android ROM. I'm looking to update the ROM to something newer so I can make use of new apps etc. Also I know newer ROMs need newer recovery tools to install. Is CWM still the go to for that?
Thanks for any help!
OMGitsShan said:
I lost my Nook Tablet for a while and just recently found it again. I'd like to update the recovery tool and put a new ROM on it so I'm looking for suggestions.
I had previously rooted it and installed ClockWorkMod and then it is running some version of an Android ROM. I'm looking to update the ROM to something newer so I can make use of new apps etc. Also I know newer ROMs need newer recovery tools to install. Is CWM still the go to for that?
Thanks for any help!
Click to expand...
Click to collapse
I'm running CM 10.2 and have been very happy with it. This excellent post by digixmax should get you on your way. It's what I used to get up and running, and yes, the recovery is CWM-based.
nmyshkin said:
I'm running CM 10.2 and have been very happy with it. This excellent post by digixmax should get you on your way. It's what I used to get up and running, and yes, the recovery is CWM-based.
Click to expand...
Click to collapse
Thanks for that! Honestly i'm not sure what is going on. I managed to get Cyanoboot on it, installed CWM 6.0.4.8, yet every single 10.1~10.2 CM ROM I get from the official directory seems to cause it to go into a weird state where the screen goes blank, then flashes white, then goes blank again and repeat etc. Eventually the tablet just restarts. I've yet to find a single ROM that I can successfully load via SD card or internal and install it through CWM. For such an old tablet, I'm surprised things are this difficult! I've spent the last few days flashing back to stock on so many occasions when things have gone wrong. I wish I could try some other ROMs that aren't on the official CM repository however most ROMs have been hosted on Goo.im and while the site works, it is so slow you aren't even sure if the file is downloading. I wish there was more custom ROMs I could try because every official CM from 10.1 to 12.1 is bricking or failing to install! I'm honestly at my wits end.
OMGitsShan said:
Thanks for that! Honestly i'm not sure what is going on. I managed to get Cyanoboot on it, installed CWM 6.0.4.8, yet every single 10.1~10.2 CM ROM I get from the official directory seems to cause it to go into a weird state where the screen goes blank, then flashes white, then goes blank again and repeat etc. Eventually the tablet just restarts. I've yet to find a single ROM that I can successfully load via SD card or internal and install it through CWM. For such an old tablet, I'm surprised things are this difficult! I've spent the last few days flashing back to stock on so many occasions when things have gone wrong. I wish I could try some other ROMs that aren't on the official CM repository however most ROMs have been hosted on Goo.im and while the site works, it is so slow you aren't even sure if the file is downloading. I wish there was more custom ROMs I could try because every official CM from 10.1 to 12.1 is bricking or failing to install! I'm honestly at my wits end.
Click to expand...
Click to collapse
I'm not skilled enough to give advice relative to your problem, but I might suggest you go for 10.0. Many people seem to think that this is the most stable of the lot, although it does seem there is something else going on with the problems you describe--maybe the SD card?