So, i had my gtab working fine then i tried to go to BL 1.2, had a rom running for a while then decided i wanted to go back to a 1.1 rom, I nvflashed to 1.1 stock image and now my tablet wont boot on any rom that isnt NVflashed, regardless of if i use CWM or stock recovery, what am i doing wrong? It only runs stock Viewsonic roms
What rom were you trying to flash that you could only use on 1.1 that there isn't a port running for 1.2.?
Let me guess. You never wiped out your data before you flash a new rom.
This is a common mistake made by beginners. Is this the case?
goodintentions said:
Let me guess. You never wiped out your data before you flash a new rom.
This is a common mistake made by beginners. Is this the case?
Click to expand...
Click to collapse
No, this is not the case, i am aware that NVflashing changes partition sizes, is it possible that customs roms are larger than Viewsonics rom and there isnt sufficient space to load a custom rom?
Mantara said:
What rom were you trying to flash that you could only use on 1.1 that there isn't a port running for 1.2.?
Click to expand...
Click to collapse
I was running BOS on 1.2 but i was having isues where if the tablet was powered off after initial boot it would not booot again so i wanted to run the 1.1 honeycomb
Have you used cwm to repartition and then load a rom?
Mantara said:
Have you used cwm to repartition and then load a rom?
Click to expand...
Click to collapse
Yes, but from what i know you can only partition the internal SD from CWM
Did you update using ota from stock brfore trying to flash another rom?
How about this. What version of nvflash are you using? I don't just mean 1.1 or 1.2. I'm talking about the long string of number in the nvflash zip file.
There are some nvflash versions floating out there that are bad.
Try this. Go to my website at
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
Use the code red procedure. Don't use anything you already have. Download everything from my website. Follow the procedure I outlined. See if this changes anything.
goodintentions said:
How about this. What version of nvflash are you using? I don't just mean 1.1 or 1.2. I'm talking about the long string of number in the nvflash zip file.
There are some nvflash versions floating out there that are bad.
Try this. Go to my website at
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
Use the code red procedure. Don't use anything you already have. Download everything from my website. Follow the procedure I outlined. See if this changes anything.
Click to expand...
Click to collapse
my NVflash is not the same extention but the 1.1 file has the same extention as yours, ill try to flash yours anyways.
Mantara said:
Did you update using ota from stock brfore trying to flash another rom?
Click to expand...
Click to collapse
Ive tried ota and NVflash to 1.1 directly neither work
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
Was written for linux you might need to adjust the nvflash commands for windows.
Thanks all of you, I got it to run BOS on 1.2 using goodintentions' NVflash, idk what happened but it appears to be working weirdly though, it wont boot a second time without a factory data reset
whodatxevg said:
Thanks all of you, I got it to run BOS on 1.2 using goodintentions' NVflash, idk what happened but it appears to be working weirdly though, it wont boot without a factory data reset
Click to expand...
Click to collapse
Didn't I tell you to use code red on my start here page? Part of the instructions in code red is to wipe data/factory reset.
You didn't really read my code red did you?
goodintentions said:
Didn't I tell you to use code red on my start here page? Part of the instructions in code red is to wipe data/factory reset.
You didn't really read my code red did you?
Click to expand...
Click to collapse
It wont boot without a data reset AFTER the initial boot. I dont think its normal to have to do a data reset after a rom is already installed but that seems to be a rom issue
Yep. Rom issue. Bos needs to be factory reset after flash. Its odd but what needs to happen to boot initially.
Glad to see you got her up and running
Mantara said:
Yep. Rom issue. Bos needs to be factory reset after flash. Its odd but what needs to happen to boot initially.
Click to expand...
Click to collapse
Oh well, thats why its not a final build.
Thanks again guys.
I suggest that all HC roms have a boot splash screen that simply states "This is an Alpha build, please on't expect everything to work like you want it to"
People keep having these delusions that the HC roms will work perfectly...
whodatxevg said:
It wont boot without a data reset AFTER the initial boot. I dont think its normal to have to do a data reset after a rom is already installed but that seems to be a rom issue
Click to expand...
Click to collapse
No it's not a rom issue.
As I explained on my website, the problem is that nvflash DOES NOT wipe out your data. When you nvflash a new stock rom, the data from the previous rom is still there. Some are not compatible with the stock rom, so the left over data cause an interruption in the normal boot process. Sometimes, it bootloops. Sometimes, you are kicked into permanent apx mode.
That's why in my code red procedure I told you to wipe data/factory reset RIGHT AFTER you nvflash.
There's a purpose to the way I ordered my instructions.
Better read the instructions better next time. Could have saved you hours of frustration.
And yes, it is normal to wipe data before you flash a new rom. Since nvflash doesn't wipe data, you have to wipe data manually after you nvflash. It's the same as wiping data before you flash the stock rom.
There have been cases with bos where full wipes were done (as far as were stated in the posts but we know no one ever lies right?) and it would bootloop untilled full wipes were done again. Who knows.
Personally I wipe and repartition every time I flash a new rom. If its an update I leave it, if its a new rom I start from a clean slate. I use titanium backup almost daily and have copies of my recovery backup on my PC weekly. Its slightly time consuming but unborking takes a hell of a lot longer than being extra cautious when flashing
Related
This ROM has been superceded by MCR 1.5 here.
P
aad4321 said:
Sweet, i might give it a shot. quick question tho... will this wipe the device?
Click to expand...
Click to collapse
Modacp said:
I'm pleased to present my MoDaCo Custom Nexus One ROM! No 'wipe' is required to use this ROM.
Click to expand...
Click to collapse
Reading comprehension much?
aad4321 said:
just to confirm, wavesecure add on is a anti theift program which is a monthly service?
Click to expand...
Click to collapse
No, there is no monthly service charge...at least not yet. I have been using wave secure for a little while now, and for a 3rd party security app its pretty damn good.
I tried to flash and got this:
Code:
E:No space left on device
E:Error writing Boot:
E:Failure at line 369:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
I tried to reboot and it wouldn't boot, so I pulled the battery and went back into recovery and tried to apply the NANDROID backup, seemed to apply fine, but now it always boots into bootloader, no matter what I do. I can still make it into recovery so it isn't all lost, but I can't do anything else from there.
Bizarre, never seen an error like that before!
What happens if you try to re-apply the ROM?
P
ccunningham83 said:
I tried to flash and got this:
Code:
E:No space left on device
E:Error writing Boot:
E:Failure at line 369:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
I tried to reboot and it wouldn't boot, so I pulled the battery and went back into recovery and tried to apply the NANDROID backup, seemed to apply fine, but now it always boots into bootloader, no matter what I do. I can still make it into recovery so it isn't all lost, but I can't do anything else from there.
Click to expand...
Click to collapse
did you wipe then restore nandroid?
anyone get tether working on this rom?
Only wireless tether is supported at the moment. Wired tether coming in a future release.
P
modaco said:
Only wireless tether is supported at the moment. Wired tether coming in a future release.
P
Click to expand...
Click to collapse
neither wireless or wired working for me..
Strange, wireless seems to be working for me I think?
P
wireless tethering say "please wait while starting" but never starts...
any suggestions?
modaco said:
Bizarre, never seen an error like that before!
What happens if you try to re-apply the ROM?
P
Click to expand...
Click to collapse
Re-Applying the ROM gets the same result.
I did Wipe and try to re-apply and also wipe and Nandroid. All got me nowhere. I ended up getting it fixed by applying Cyanogens Bacon1.img. I am really interested in your ROM though. Think maybe I got a bad download or something. I will try again and check the md5 sum this time.
my tether puts a signal out and all but i cant connect to it.. only get local
So after downloading the ROM again after the first one didnt work, I got this for the md5 checksum:
Code:
e04970294888313787d0b9d5cb370a12
Which is entirely different than what is posted on the MoDaCo Forum:
Code:
d537e42372a7239dfaf40846ef0b8b4e
However, I could be doing it wrong. This is the first time I tried using md5 checksums to verify a download. However I used two different utilitys to get the same checksum and I don't want to try to flash it again and have it mess up.
ccunningham83 said:
Re-Applying the ROM gets the same result.
I did Wipe and try to re-apply and also wipe and Nandroid. All got me nowhere. I ended up getting it fixed by applying Cyanogens Bacon1.img. I am really interested in your ROM though. Think maybe I got a bad download or something. I will try again and check the md5 sum this time.
Click to expand...
Click to collapse
I can help fix your problem and it is very simple. READ THE FIRST POST BY PAUL. DO NOT WIPE. Do a Nandriod backup then apply the update. Remember do not extract the rom file with I hope WINRAR, just rename update. Let me know if this solves it for you which it should. Kevin
kevinrirvine said:
I can help fix your problem and it is very simple. READ THE FIRST POST BY PAUL. DO NOT WIPE. Do a Nandriod backup then apply the update. Remember do not extract the rom file with I hope WINRAR, just rename update. Let me know if this solves it for you which it should. Kevin
Click to expand...
Click to collapse
Maybe I should have explained everything I did step by step, I did READ THE FIRST POST BY PAUL AND DIDN'T WIPE. Before I even tried flashing, I performed a Nandroid Backup. I booted into recovery, applied the update, got the error message I listed, tired to reboot, got stuck, pulled the battery, booted back into recovery, performed a wipe, reapplied the update, rebooted, still a no-go, rebooted back into recovery, performed a Nandroid restore, after it completed, rebooted, got stuck on bootloader screen, reloaded the ROM on the SD card, tried flashing again, still no luck, ended up flashing Cyanogens Bacon1.img to fix the problem.
I want to give it another try, but I may wait and find out if my md5 sum is correct or maybe try another link if someone post it up.
ccunningham83 said:
Maybe I should have explained everything I did step by step, I did READ THE FIRST POST BY PAUL AND DIDN'T WIPE. Before I even tried flashing, I performed a Nandroid Backup. I booted into recovery, applied the update, got the error message I listed, tired to reboot, got stuck, pulled the battery, booted back into recovery, performed a wipe, reapplied the update, rebooted, still a no-go, rebooted back into recovery, performed a Nandroid restore, after it completed, rebooted, got stuck on bootloader screen, reloaded the ROM on the SD card, tried flashing again, still no luck, ended up flashing Cyanogens Bacon1.img to fix the problem.
I want to give it another try, but I may wait and find out if my md5 sum is correct or maybe try another link if someone post it up.
Click to expand...
Click to collapse
Paul's rom's are only at modaco and I am pretty sure he does not allow other links for I only use his rom's and have one on my Hero Telus, AT&T 3G, and what I like most about them is he keeps them as close to stock as possible, a good thing, and just optimizes them.
Your not going to brick your n1 so I know your gun-shy now but try the link a few more times even and it will work. Also, delete or format your memory card so it the rom is at the root for this might have something to do with it. Want you to have a happy ending. Kevin
The zips are signed, if a download is corrupt it won't flash.
P
kevinrirvine said:
Paul's rom's are only at modaco and I am pretty sure he does not allow other links for I only use his rom's and have one on my Hero Telus, AT&T 3G, and what I like most about them is he keeps them as close to stock as possible, a good thing, and just optimizes them.
Your not going to brick your n1 so I know your gun-shy now but try the link a few more times even and it will work. Also, delete or format your memory card so it the rom is at the root for this might have something to do with it. Want you to have a happy ending. Kevin
Click to expand...
Click to collapse
I need to re-format my sdcard, I still have the three partitions from my G1. I will give that a try, but I am still unsure about the md5 sum issue. Not too worried about bricking the device after all I put my G1 through.
Thank you for posting here on XDA also
Hi. I was following this guide here wiki.cyanogenmod.<(SPACE)>com/wiki/Viewsonic_G_Tablet:_Full_Update_Guide
(REMOVE <(SPACE)>)
I chose to install the 'update' to internal memory. Upon rebooting while holding the volume up and power buttons, "booting recovery kernel image" is seen but it doesn't progress beyond that point. After pressing the power button the tablet boots normally. I am stuck at Step 3 of the 2nd Method in the guide I had posted. I read somewhere that ROM Manager softbricks the device or something so I avoided it. How can I finish installing Cyanongen or perhaps switch to vegan? I would appreciate any responses
What bootloader are you on? Had you installed clockwork mod at any point?
Mantara said:
What bootloader are you on? Had you installed clockwork mod at any point?
Click to expand...
Click to collapse
How do I know what bootloader im on? I think the clockwork version is .8 or something. I installed it. Again, I followed that guide by the word. Any dl link in there is the one I used. Thank you.
What was your stock rom? Tapntap 3558 or 4389?
You can try here for more info. http://viewsonic-gtablet-for-dummies.webs.com/
Its a handy site
Mantara said:
What was your stock rom? Tapntap 3558 or 4389?
Click to expand...
Click to collapse
Err. Tap UI says 1.2-4349.
I'm having the exact same problem. Just got the tablet and starting from the beginning with CWM. I've tried internalsd, externalsd and nvflash and all three methods result in the same thing. Stuck on the booting recovery kernal image.
I may nvflash the stock recovery and try it again.
EDIT: Go here: http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm
Follow the instructions to download the stock rom with CWM pre-installed. This did the trick for me! Hope it helps.
PyBro said:
Err. Tap UI says 1.2-4349.
Click to expand...
Click to collapse
This means your on bootloader 1.2. Cm7 is made around bl 1.1 so it wont install correctly. You can install a modified version of cm7 that was packaged to run on bl 1.2. There is a thread in development by zyhong that has links to the modified cm7.
Here is the thread
http://forum.xda-developers.com/showthread.php?t=1123836
There are 2 options for kernels. The roms on the linked thread come pre packaged with either pershoots or clemsyns 1.2 compatible kernel.
maxxve said:
I'm having the exact same problem. Just got the tablet and starting from the beginning with CWM. I've tried internalsd, externalsd and nvflash and all three methods result in the same thing. Stuck on the booting recovery kernal image.
I may nvflash the stock recovery and try it again.
EDIT: Go here: _________
Follow the instructions to download the stock rom with CWM pre-installed. This did the trick for me! Hope it helps.
Click to expand...
Click to collapse
Okay, thanks. I followed this completely without any errors...how do I know if Cyanogen is installed? Everything looks the same, has the same settings, nothing was wiped (same apps in same places and still have flash). Nothing says cyanogen in the settings. Thanks!
You guys flashed (installed) the wrong cwm for your branch. You're on 1.2 but you flashed in cwm for 1.1.
goodintentions said:
You guys flashed (installed) the wrong cwm for your branch. You're on 1.2 but you flashed in cwm for 1.1.
Click to expand...
Click to collapse
I suppose I could reinstall CWM. How do I uninstall it so I can reinstall?
Also, if you'll read the above post, how do I know if I'm on Cyanogen? I followed your guide but everything looks the same
PyBro said:
I suppose I could reinstall CWM. How do I uninstall it so I can reinstall?
Also, if you'll read the above post, how do I know if I'm on Cyanogen? I followed your guide but everything looks the same
Click to expand...
Click to collapse
You can't uninstall it. And no you didn't follow my guide. The fact that you put in the wrong cwm says this.
Go to my start here page and impliment code yellow. Make sure you look ahead at the rom page to know which rom you want and what branch its on.
Disregard this, I am an idiot.
PyBro said:
Disregard this, I am an idiot.
Click to expand...
Click to collapse
Not an idiot. An idiot would not have the awareness to call himself an idiot
Your learning and we all started in about the same place you did. Chin up and try again
Mantara said:
Not an idiot. An idiot would not have the awareness to call himself an idiot
Your learning and we all started in about the same place you did. Chin up and try again
Click to expand...
Click to collapse
Well stated! Only thing that I can add is read more and then read again! Then just before you flash re-read
Hi,
I won't give you the long story so here's what happened:
- TouchscreenDigitizer & LCD broke
- Replaced both
- Got a different rev of the Digitizer, result: X-Axis is inverted
- Someone (darksawa) built a patch for this by editing the touchscreen driver but you need nvflash enabled to replace the kernel image the easy way
- Was on JB Stock without root/unlock until now so I'm not able to enable nvflash
- There is a way to get it done anyway: Get the edited kernel image into another rom and install it via TWRP
- Tried to extract the stock rom (unpack blob files etc..) and replaced the kernel image - then pack all together again but wasn't working (flashing procedure abrupted, no brick)
Could someone of you do me and some other guys a big favour by replacing the original kernel image of the stock rom WW-10.4.2.15 with this kernel image?
Thank you!!!
mechadream said:
Hi,
I won't give you the long story so here's what happened:
- TouchscreenDigitizer & LCD broke
- Replaced both
- Got a different rev of the Digitizer, result: X-Axis is inverted
- Someone (darksawa) built a patch for this by editing the touchscreen driver but you need nvflash enabled to replace the kernel image the easy way
- Was on JB Stock without root/unlock until now so I'm not able to enable nvflash
- There is a way to get it done anyway: Get the edited kernel image into another rom and install it via TWRP
- Tried to extract the stock rom (unpack blob files etc..) and replaced the kernel image - then pack all together again but wasn't working (flashing procedure abrupted, no brick)
Could someone of you do me and some other guys a big favour by replacing the original kernel image of the stock rom WW-10.4.2.15 with this kernel image?
Thank you!!!
Click to expand...
Click to collapse
No I can't but I can go one better for you
I have converted it to a blob file and put it into an installable zip. Just flash this in twrp and your good to go.
This is for Jellybean.
flumpster said:
No I can't but I can go one better for you
I have converted it to a blob file and put it into an installable zip. Just flash this in twrp and your good to go.
This is for Jellybean.
Click to expand...
Click to collapse
Thank you very much for you help but I got the following problem:
I flashed the file via TWRP and now I'm stuck at the ASUS Boot-Logo with the tegra logo on the bottom right.
mechadream said:
Thank you very much for you help but I got the following problem:
I flashed the file via TWRP and now I'm stuck at the ASUS Boot-Logo with the tegra logo on the bottom right.
Click to expand...
Click to collapse
I tested the kernel myself before uploading it for you mate.. It worked fine. Everything was reversed for me when I booted back into the rom.
You could try doing a factory reset and a cache and dalvik wipe to see if that is your problem.
I was running hairybean 1.3 on jellybean when I tested it.
What rom are you running ?
flumpster said:
I tested the kernel myself before uploading it for you mate.. It worked fine. Everything was reversed for me when I booted back into the rom.
You could try doing a factory reset and a cache and dalvik wipe to see if that is your problem.
I was running hairybean 1.3 on jellybean when I tested it.
What rom are you running ?
Click to expand...
Click to collapse
I am on Stock. Installed Stock from Asus website, installed TWRP via fastboot and then flashed your file.
EDIT: factory reset, cache and dalvik wipe does not help, you suggest I install hairybean too?
mechadream said:
I am on Stock. Installed Stock from Asus website, installed TWRP via fastboot and then flashed your file.
EDIT: factory reset, cache and dalvik wipe does not help, you suggest I install hairybean too?
Click to expand...
Click to collapse
After you flashed my zip did you see a blue progress bar go along after you restarted the prime. If you did then the kernel definately flashed.
You can also try holding down the power button and volume down button until you get to the place where there are 4 icons and then going over to the wipe data icon and selecting that. That should factory reset your machine.
If that doesn't work let me know.
flumpster said:
After you flashed my zip did you see a blue progress bar go along after you restarted the prime. If you did then the kernel definately flashed.
You can also try holding down the power button and volume down button until you get to the place where there are 4 icons and then going over to the wipe data icon and selecting that. That should factory reset your machine.
If that doesn't work let me know.
Click to expand...
Click to collapse
Got that blue progress bar the first time after I flashed your file, then it went away and thats all.
Just did the wipe the way you told me, no change, still stuck @ splash screen. I think I have to install another complete rom to get over the splash screen again.
mechadream said:
Got that blue progress bar the first time after I flashed your file, then it went away and thats all.
Just did the wipe the way you told me, no change, still stuck @ splash screen. I think I have to install another complete rom to get over the splash screen again.
Click to expand...
Click to collapse
Well you're definitely not bricked so don't panic.
I think the next step would be to install a rom like you say. Try installing Hairybean 1.3 and follow all the steps in the original post. If you are still stuck after that I think the next step will be to run a full wipe script on your prime and then install a rom.
Try the rom first and let me know how you get on. We will get this sorted soon enough
Also before you install the rom, factory reset, wipe cache, dalvik and system then install.
flumpster said:
Well you're definitely not bricked so don't panic.
I think the next step would be to install a rom like you say. Try installing Hairybean 1.3 and follow all the steps in the original post. If you are still stuck after that I think the next step will be to run a full wipe script on your prime and then install a rom.
Try the rom first and let me know how you get on. We will get this sorted soon enough
Also before you install the rom, factory reset, wipe cache, dalvik and system then install.
Click to expand...
Click to collapse
Installed like you said and it's WORKING!!!
Thank you very much, after all these frustrating months it's working now, thank you thank you thank you!!
And thanks to sawa of course :good:
mechadream said:
Installed like you said and it's WORKING!!!
Thank you very much, after all these frustrating months it's working now, thank you thank you thank you!!
And thanks to sawa of course :good:
Click to expand...
Click to collapse
Glad you got it all fixed mate. I have no idea what went wrong for you as it worked first time for me but as long as it's all done now
flumpster said:
Glad you got it all fixed mate. I have no idea what went wrong for you as it worked first time for me but as long as it's all done now
Click to expand...
Click to collapse
Can I use this with Hairy Bean 1.4 too?
mechadream said:
Can I use this with Hairy Bean 1.4 too?
Click to expand...
Click to collapse
Yea, it should be okay on any stock based jellybean rom.
same problem
I have the same problem as the original treath.
I am not rooted, not unlocked under jelly bean.
Beginner question but is it also possible to install without root. how i understood TWRP needs root.
you can help me soo much ...
oremy said:
I have the same problem as the original treath.
I am not rooted, not unlocked under jelly bean.
Beginner question but is it also possible to install without root. how i understood TWRP needs root.
you can help me soo much ...
Click to expand...
Click to collapse
You need to be unlocked to install TWRP. Once installed you can flash the zip. Root is not required to install TWRP.
Thank you all!! i managed ... fully operational prime again ...
i was getting used to the mirrored clicking
Stuck at the ASUS Boot-Logo. FW US
My problem started two month ago when the repair assistance sent me back my tf201 with reverse axis. I broke the glass and they this but the didn't do the reversed axis. They wasted my time and money. I realy need help.
I am on Stock US-10.4.2.15 unlocked bootloader with TWRP and I have same problem that "!mechadream" had. I'm stuck at the ASUS Boot-Logo.
Maybe I shouldn't flash this WW(I don't know if this make some difference honestly) but I had some hope that finally solve my problem and fix it.
Now I am stuck. What should I do now? I can I do? Can you help me please? Thank you for your help.
fabianogalaxy said:
My problem started two month ago when the repair assistance sent me back my tf201 with reverse axis. I broke the glass and they this but the didn't do the reversed axis. They wasted my time and money. I realy need help.
I am on Stock US-10.4.2.15 unlocked bootloader with TWRP and I have same problem that "!mechadream" had. I'm stuck at the ASUS Boot-Logo.
Maybe I shouldn't flash this WW(I don't know if this make some difference honestly) but I had some hope that finally solve my problem and fix it.
Now I am stuck. What should I do now? I can I do? Can you help me please? Thank you for your help.
Click to expand...
Click to collapse
Can you tell me where you can get to please? can you get into TWRP? can you get to fastboot?
TWRP
flumpster said:
Can you tell me where you can get to please? can you get into TWRP? can you get to fastboot?
Click to expand...
Click to collapse
I am not sure about fastboot BUT the TWRP is working well. I can get into TWRP.
Thanks a lot.
fabianogalaxy said:
I am not sure about fastboot BUT the TWRP is working well. I can get into TWRP.
Thanks a lot.
Click to expand...
Click to collapse
Can you try installing hairybean 1.51 following all the instructions to install it including doing the wipes it tells you to.
TF201
flumpster said:
Can you try installing hairybean 1.51 following all the instructions to install it including doing the wipes it tells you to.
Click to expand...
Click to collapse
Thank you. I did what you asked me. THIS IS PERFECT!! Glad to have people like you in the world. Your help has saved my TF201. thank you :laugh::good:
I followed a post on here from malloneem - http://forum.xda-developers.com/showthread.php?t=2037368 - but I ran into an issue. I have CM7 running just fine on NT (thanks by the way ) but I'm trying up "upgrade" to CM10. I can boot into recovery and then into TWRP but it hangs after selecting the acclaim.zip file and gapps file. It states "Flashing file 1 of 2 /sdcard/sgt7-10-20121124-UNOFFICIAL-acclaim.zip" I let it run for 2 hours, but no luck.
Thanks in advance!
SuicidalSoldier said:
I followed a post on here from malloneem - http://forum.xda-developers.com/showthread.php?t=2037368 - but I ran into an issue. I have CM7 running just fine on NT (thanks by the way ) but I'm trying up "upgrade" to CM10. I can boot into recovery and then into TWRP but it hangs after selecting the acclaim.zip file and gapps file. It states "Flashing file 1 of 2 /sdcard/sgt7-10-20121124-UNOFFICIAL-acclaim.zip" I let it run for 2 hours, but no luck.
Thanks in advance!
Click to expand...
Click to collapse
The method you're using is rather old. Before you try anything else I will interrupt your possibly long strenuous process of flashing CM10.
Before you attempt anything else, restore your tablet. You might be mad at me for saying this, but it makes things easier using the newer methods for flashing ROMs. You can restore your tablet by writing this repart.img to an SD card and putting it in your nook. It will write stock BN ROM to your tablet. Use this:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
A lot of people have problems with TWRP. I could never get it to stop freezing up. Assuming you want to internally flash CM10 I'll give you this link to follow:
http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
If you are new to flashing ROMs there is a very simple way of using CM10 from an SD card. Just write it to your SD card and you're good! You can use a partitioning tool such as MiniTool to expand the different partitions of your SD card. Use this method if you want run from an SD card.
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
If you run into any problems along the way, just ask!
I appreciate the reply. I was able to flash back to factory, but I'm a bit perplexed on the second link. I do want to run CM10 internally. I was able to grab the file, but the link isn't exactly noob friendly on a "how to". Could you point me in the right direction to get started on this?
Thanks
SuicidalSoldier said:
I appreciate the reply. I was able to flash back to factory, but I'm a bit perplexed on the second link. I do want to run CM10 internally. I was able to grab the file, but the link isn't exactly noob friendly on a "how to". Could you point me in the right direction to get started on this?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2056626
Try this out.
Mega simple super duper easy way where you don't have to set up any partitions at all:
1. Download one of the ready-made CM10 sd-card images on Iamafanof website. Doesn't matter which! These images contain Cyanoboot.
2. Burn this image
3. Put your CM10 and gApps on this or another sd card.
4. Boot into Cyanoboot by holdninh "n" during bootup. Choose "sd recovery"
5. Clear cache and dalvik
6. Choose your zips and flash them
Once CM10 is installed you'll have Cyanboboot and CWM installed internally so if you need to reflass you just boot into Cyanoboot by holding the "n" at bootup.
datallboy said:
http://forum.xda-developers.com/showthread.php?t=2056626
Try this out.
Click to expand...
Click to collapse
@SuicidalSoldier:
I'd also suggest taking a look at http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more info/pointers -- especially w.r.t. making backup in case you make mistakes in flashing.
Thank you for the info. I'll give these a try and post back my results.
Somehow after installing I keep stuck at the CyanogenMod splash screen.
I have already re-installed but to no avail.
Any hints?
shadowhumper said:
Somehow after installing I keep stuck at the CyanogenMod splash screen.
I have already re-installed but to no avail.
Any hints?
Click to expand...
Click to collapse
Takes a while for the initial boot to start. Just wait 2 or 3 minutes and it should boot.
datallboy said:
Takes a while for the initial boot to start. Just wait 2 or 3 minutes and it should boot.
Click to expand...
Click to collapse
It indeed takes 2-3 minutes but then it just flashes the Android home screen and goes back to the cyanogenmod boot splash screen.
I am guessing I should install another build perhaps?
shadowhumper said:
It indeed takes 2-3 minutes but then it just flashes the Android home screen and goes back to the cyanogenmod boot splash screen.
I am guessing I should install another build perhaps?
Click to expand...
Click to collapse
Go to recovery and do a factory rest/total wipe, wipe cache, wipe dalvik cache. Then install the ROM again. If it still doesn't work try a different ROM.
shadowhumper said:
It indeed takes 2-3 minutes but then it just flashes the Android home screen and goes back to the cyanogenmod boot splash screen.
I am guessing I should install another build perhaps?
Click to expand...
Click to collapse
By "cyanogenmod boot splash" do you means "Cyanoboot splash" or "Cyanogenmod boot-animation"?
You need to say more on what you did to "flash the ROM" so that we can discern what you might have done wrong.
datallboy said:
Go to recovery and do a factory rest/total wipe, wipe cache, wipe dalvik cache. Then install the ROM again. If it still doesn't work try a different ROM.
Click to expand...
Click to collapse
Thanks dude, that did the trick. I guess the problem I had was with a corrupt image that I have downloaded.
I'm left clueless here. I just can't get it to boot, no matter what ROM/Kernel i'd flash. It was originally running OOS 2.3.1 but flashing it now won't work anymore. It worked briefly for 1 hour with that AOSP 8.1 but then after trying to flash gapps it stuck again in a bootloop. Sometimes it also freezes and reboots while i am flashing sometimes. I really have no idea what should i do next, hope you can help me.
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Kéno40 said:
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Click to expand...
Click to collapse
I updated the bootloader like over a year ago or so. I also tried 2 different versions of TWRP, now i am using the latest one.
ALSO, very sorry it actually is OOS 3.1.4, not 2.3.1, i just typed briefly what i could remember, i haven't been using this phone for months now but i would like to give it to a relative so there's that. Hope you can help me out, i have no clue why is it acting up like that.
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Try to flash official ROM after having wiped everything
Kéno40 said:
Try to flash official ROM after having wiped everything
Click to expand...
Click to collapse
That's what i first tried, mentioned it in the main post.
yayakuya said:
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Click to expand...
Click to collapse
I don't know what to make of this, thought maybe anyone else encountered this problem and has a clue.
gabytzu338 said:
That's what i first tried, mentioned it in the main post.
Click to expand...
Click to collapse
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Kéno40 said:
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Click to expand...
Click to collapse
I don't really understand what you are trying to say. I did wipe everything and the only way to flash anything is through adb sideload anyway since the device is not recognized as storage while in TWRP. I think I am gonna give up on it, I was gonna sell it but I can't risk having it act up days/weeks after i sold it.