Related
So i thought i'd start with cooked roms since the internal memory is kinda low.
So i started by upgrading the current stock rom 2.73(sigh) and everything works sweet,
next i partition the memory card (4gb) like said in this guide Partition Guide
All good so far!
Next step was to ofc flash the recovery part with flashrec since i have hboot and all,
and that worked well while going after the guide Flashrec guide for noobs like me
boots wonderfully into Cyanogens recovery mode.
Meanwhile i prep the memory card with MoDaCo Custom ROM 2.4
and make sure the phone is rooted by this guide root guide. after i reboot to recovery. made a backup first!(thank god for that option), and after that installed the custom rom.
So far so good eh ?
Once in the phone i started appstosd just to see if it works at all
(remind you that i can login by adb shell with su so should work ?)
and all i get is "your memcard is not partitioned lets do that" well okey then,
I drag the meter so it gets 500mb for ext2, press apply and then new screen comes with a reboot button,
I press it and nothing at all happens.(also pressed the "always allow")
Well maybe it's auto since it should be with MoDaCo lastest rom. but nope nothing goes to the sdcard.
tried doing latest stock rom with root instead of custom rom, and still appstosd gives me the same thing,
refuses to boot. even tried to reinstall the custom rom 3 times, where one of those just rebooted all the time.
Any idea what's going on here ? should be more out there with the same problem ?
cepet said:
Any idea what's going on here ?
Click to expand...
Click to collapse
Yup, you didn't read the release notes for the MoDaCo ROM carefully enough.... Apps2SD works automatically. So long as your card has a second ext2/3 partition it will be recognised and your apps moved to it. No user interaction is required.
On another note, try using Amon Ra recoery image. It's the latest.
cepet said:
So i thought i'd start with cooked roms since the internal memory is kinda low.
[...]
I drag the meter so it gets 500mb for ext2, press apply and then new screen comes with a reboot button,
[...]
Click to expand...
Click to collapse
Maybe the problem is with the ext2 partition. Modaco's works with ext3. If you have a ext2 instead of a ext3 you shouldt upgrade the partition. You can do that from the recovery-image from AMON_Ra
thanks a lot for the tips about amon_ra and all! worked flawlessly , still had to go by flashrec tho.
But what still bothers me is appstosd, both first and second release.
Fully confirmed that root is working both through the phone and adb shell, but still appstosd won't work manually,
don't want the monaco rom tbh, wanna go with stock rom.
Doesn't bother me a bit that i have to do it manually everytime(appstosd that is).
So i'm rooted and appstosd installed, but still appstosd1 tells me that my card is wrongly formatted(did it in amon_ra) then i wiped it clean in amon_ra and tried appstosd2 so it can partition it for me, after i press apply i get the "reboot" button that doesn't work.
Any ideas ?
Thanks in advance!
Ok, I give (well sort of) stuck at 3 birds screen for gingerbread roms.
Need one of the better brains on this one. I'm not sure if solvable without one of the big guys having one of these troublesome woot tablets.
Story up till now.
I have a G tablet, I have had one since November 2010. (black friday sears).
On my tablet I have never had any issues installing any rom/kernel and it at least booting (ones designed for gtablet)
I impressed work with them so much that during the Woot sale a few weeks back, the university bought 11 of these tablet for other techs.
So I stepped up and decided to flash them all (since tap n tap doesn't support several things such as WPA2 enterprise).
Now on the first 2 tablets I got ahold of they would not load any gingerbread rom on this forum, not vegan experementals, not either one of the asops, nor cm7 .... etc..
But they will run TNT lite and vegan 1 5b11.....
One of the units came to me with fc issues out of the box... that one loaded and ran gingerbread just fine..... (vegan experementals + pershot kernal + gapps)
The one my step father purchased from woot runs gingerbread asop + pershot + gapps fine as well
Got to work today tried a few things on another one of these tablets and it gets stuck at the veiwsonic 3 birds screen.
So these are all the methods broken down by tablet.
Tablet 1 -
Boot to stock
Mount tablet as usb
extract CW internal to device
mount usb
Reboot recovery
Reboot CW recovery
Copy over GB Asop
Copy over gapps
Flash said above
stuck at "viewsonic" screen
Ok...
Partition memory 2048/0
mount
Copy over gb asop, gb experementals, gapps
Try all of them...
Viewsonic screen..
ok
partition
mount
Copy over vegan 5.1 5.11 and pershot kernal
flash
Bingo we have vegan tab....
Hmmm..
2nd tablet
Ok lets try this again
Boot to stock
Mount tablet as usb
extract CW internal to device
mount usb
Reboot recovery
Reboot CW recovery
Copy over GB experementals
flash
stuck at viewsonc screen
partition 2048/0
mount
copy over experementals
flash
stuck at viewsonic
copy over vegan 5.1 / 5.11
flash (no kernal this time)
bingo we have froyo .... still no gb
Tablet 3- Troubled begginings
Set time zone - Force crash here....
Copy over micro sd and extract to micro sd card
Flash CW
lets try again
Copy over asop + gapps + pershot
Bam reboot and were in---- ran perfectly.
So I go... AHHA.. Must be micro SD is the key...
Tablet 4 ---
Bring over same micro sd card with me.
Use it to install CW
Install asop +gapps+pershot
froze at "Viewsonic"
WTF....
hmmmmm
Repartiton 2048/0
stuck
repartition 4096/0
stuck
repartition 4096/32
stuck
etc...
Repartitioned 2048/0
Installed vegan 5.1 / 5.11
bingo we have a live tab....
So I really don't know what is causing this. any thoughts on any of it would be greatly appreciated.
Only thought is hardware revision.. *shrug*
Did you do the stock OTA update before flashing any roms?
Pnuts said:
Did you do the stock OTA update before flashing any roms?
Click to expand...
Click to collapse
On tablet 4 I did.
I got cm7 on my woot gtab finally.
I repartitioned to 4096/256.
NVFlash
booted in to stock > plugged in to pc > usb transferred cm .8
installed cm .8
booted back to stock > usb transferred rom + gapps
boot recovery > formated boot,system,cache,data and wipe davlik cache
mount system & data
install rom then gapps
mount system ( it unmounts after rom install, cache was still mounted)
“wipe data/factory reset”
reboot
on mine- it took 30-60 secs to go from viewsonic screen to the cm boot animation and 1-2 mins it loaded up
bill1253 said:
I got cm7 on my woot gtab finally.
I repartitioned to 4096/256.
NVFlash
booted in to stock > plugged in to pc > usb transferred cm .8
installed cm .8
booted back to stock > usb transferred rom + gapps
boot recovery > formated boot,system,cache,data and wipe davlik cache
mount system & data
install rom then gapps
mount system ( it unmounts after rom install, cache was still mounted)
“wipe data/factory reset”
reboot
on mine- it took 30-60 secs to go from viewsonic screen to the cm boot animation and 1-2 mins it loaded up
Click to expand...
Click to collapse
I'll have to give this a try.
bill1253 said:
mount system ( it unmounts after rom install, cache was still mounted)
Click to expand...
Click to collapse
Hmmm.... May have something on this line. Have to check it out.
Gentlemen -- and others reading this thread:
Please don't get people started re-partitioning the way you have just posted!!!???!!!
I can't pull the reason off the top of my head -- but the 2048 and 0 has been the
standard since last November. I do remember that it will foul things up.
If you want to experiment with it, fine. But if you keep posting and pushing it you
may start another round of problems for folks that don't need problems.
IMHO.
Rev
EDIT, HERE'S THE ANSWER: The 2048 figure has been set for a long time because other values
(particularly 4096) caused issues with the Market. Wouldn't allow downloads.
The second value is a cache and the the understanding is that Android doesn't use it, so
it's just a waste of space.
Android is not well-documented, but that is the wisdom behind 2048/0.
bc
I would agree with butchconner. I am not a developer, but I am a UNIX systems administrator.
In the "old days" when RAM was hideously expensive ($7,000 for 16MB of RAM), we used a rule of thumb that swap should be 1-2.5 times the physical RAM. Disk was cheaper than RAM, hence virtual memory.
Now, memory generally exceeds requirements. I can understand why one would want not to have your swap go to flash nvram, since nvram is slow and has limited write cycles. But, letting the system swap to nvram _and_ to less swap than you have memory for just seems counter productive.
I partitioned mine to 2048/0 and it runs great.
My Archos 70 has only 256MB RAM, and I could see a benefit from 256mb - 512mb of configured swap space, as it appears memory constrained in 256MB RAM.
Hope this helps.
butchconner said:
Gentlemen -- and others reading this thread:
Please don't get people started re-partitioning the way you have just posted!!!???!!!
I can't pull the reason off the top of my head -- but the 2048 and 0 has been the
standard since last November. I do remember that it will foul things up.
If you want to experiment with it, fine. But if you keep posting and pushing it you
may start another round of problems for folks that don't need problems.
IMHO.
Rev
EDIT, HERE'S THE ANSWER: The 2048 figure has been set for a long time because other values
(particularly 4096) caused issues with the Market. Wouldn't allow downloads.
The second value is a cache and the the understanding is that Android doesn't use it, so
it's just a waste of space.
Android is not well-documented, but that is the wisdom behind 2048/0.
bc
Click to expand...
Click to collapse
fine and good and all, but red hering all the same. still can't get gingerbread to work on a large majoity of the woot tablet i have come across.
That's the best I can offer. Sorry I can't help you.
Please remember that Gingerbread is not out for the
G-Tablet and what you are using is experimental.
It may not be perfect!
Good Luck.
Rev
butchconner said:
That's the best I can offer. Sorry I can't help you.
Please remember that Gingerbread is not out for the
G-Tablet and what you are using is experimental.
It may not be perfect!
Good Luck.
Rev
Click to expand...
Click to collapse
Yea I don't think this has to do with experimental some of the bootloaders or something are fowled up on some tabs why does it work on some and not others?
My coworker and I both bought the tabs at the same time and his flash ginger no problem and mine sticks at the birds.
My Woot tablet works great, no problem with Gingerbread. I DID let it do the OTA update before I started hacking - not sure if that made a difference.
chadness said:
My Woot tablet works great, no problem with Gingerbread. I DID let it do the OTA update before I started hacking - not sure if that made a difference.
Click to expand...
Click to collapse
Wish that it did. I tried this on both tablet 4 and tablet 5 (last night) with no effect.
I rolled tablet 3 to stock 3588 from roebeet's recovery mod
Only thing I haven't tried is skipping CW all together and do it all from update.zip s .
May give that a shot today.
It's alive!
bill1253 said:
I got cm7 on my woot gtab finally.
I repartitioned to 4096/256.
NVFlash
booted in to stock > plugged in to pc > usb transferred cm .8
installed cm .8
booted back to stock > usb transferred rom + gapps
boot recovery > formated boot,system,cache,data and wipe davlik cache
mount system & data
install rom then gapps
mount system ( it unmounts after rom install, cache was still mounted)
“wipe data/factory reset”
reboot
on mine- it took 30-60 secs to go from viewsonic screen to the cm boot animation and 1-2 mins it loaded up
Click to expand...
Click to collapse
I skipped the repartition (left it at default), but I was actually able to boot into a Gingerbread ROM! I followed your instructions to the T.
An additional note for the NVFlash, I followed roebeet's instructions to do a restore via NVFlash, although, I did not update to 3588 (it said it was already up-to-date?): http://forum.xda-developers.com/showthread.php?t=861950
Thanks!
EDIT: the Tap UI version that is installed from the NVFlash I performed is 2638. I have completed the steps above again with a different ROM (CM7) and it worked like a champ again.
Do NOT partition to anything other than 2048 and 0. You WILL have market problems otherwise. If you load a Gingerbread rom and it stops at the birds you must nvflash to stock and then you will okay. I have walked about 20 people through this in the last 2 weeks and it works everytime. Something is different in the partitioning on these newer tabs and Gingerbread dont like it. It's not the bootloader and not clockwork
Yeah, I left it at 2048/0; you actually shouldn't have to repartition it with the default settings anyway. I haven't had a problem and haven't needed to repartition it when going between Gingerbread ROMs.
thebadfrog said:
Do NOT partition to anything other than 2048 and 0. You WILL have market problems otherwise. If you load a Gingerbread rom and it stops at the birds you must nvflash to stock and then you will okay. I have walked about 20 people through this in the last 2 weeks and it works everytime. Something is different in the partitioning on these newer tabs and Gingerbread dont like it. It's not the bootloader and not clockwork
Click to expand...
Click to collapse
Any chance you could walk me through it? I'm not quite sure what I'm doing wrong otherwise.
You can join irc but the first thing that will be asked is do you have the drivers installed and can you see the tab from a pc.
Freenode channel #tegratab
Hi guys,
I just got a Woot replacement for my old Gtab and noticed a new version of Vegan tab was out. I followed the install instructions but when I reboot, it wont get past the Viewsonic screen. The older version is working fine (installed it just now).
I'm concerned that it is my build version causing it to (soft brick?). How do I check the build version? Thanks!
Or if it's not a build issue, anyone know a fix?
Did you clear data and cache? Also what version of cwm are you using?
Sent from my VEGAn-TAB using Tapatalk
deathcipris said:
Did you clear data and cache? Also what version of cwm are you using?
Sent from my VEGAn-TAB using Tapatalk
Click to expand...
Click to collapse
Installed using CWM .8 (or whatever is in the FAQ guide), then cleared data/cache and that other thing recommended to clear on the vegan tab download site.
So I partitioned -> installed -> cleared everything -> rebooted. Hung for 30+ minutes
Bascotie said:
Installed using CWM .8 (or whatever is in the FAQ guide), then cleared data/cache and that other thing recommended to clear on the vegan tab download site.
So I partitioned -> installed -> cleared everything -> rebooted. Hung for 30+ minutes
Click to expand...
Click to collapse
nvFlash back to stock. There are some tablets with partition tables swapped. Doesn't seem to hurt Froyo ROMS, but it hangs all of the GB Roms.
nvFlash will fix the tables (partitioning SD card won't).
Zaphod-Beeblebrox said:
nvFlash back to stock. There are some tablets with partition tables swapped. Doesn't seem to hurt Froyo ROMS, but it hangs all of the GB Roms.
nvFlash will fix the tables (partitioning SD card won't).
Click to expand...
Click to collapse
I will second this post. I had the same issue of no boot and being stuck at the birds screen. I almost gave up on flashing to vegan ginger. I nvflashed, then installed vegan ginger rc1 and the tablet booted right up.
jetguy35 said:
I will second this post. I had the same issue of no boot and being stuck at the birds screen. I almost gave up on flashing to vegan ginger. I nvflashed, then installed vegan ginger rc1 and the tablet booted right up.
Click to expand...
Click to collapse
Nvflash is available from cwm?
Also, can i backup my apps with titanium to use on ginger? Thx
Bascotie said:
Nvflash is available from cwm?
Also, can i backup my apps with titanium to use on ginger? Thx
Click to expand...
Click to collapse
If you refer to this link http://forum.xda-developers.com/showthread.php?t=861950
Roebeet posted this link in the development forum. It gives you the procedure for nvflash. You have to download a few items for nvflash and a usb driver. All of the links are in his document and it tells you exactly what you need to download. When you download the nvflash files make sure you dump all of the files into a central folder like the document says. I was unable to nvflash keeping the folders seperate. So all of the files from each folder that you download should go into one central folder so that the nvflash process can access all of the files. So for example, you have to download nvflash_windows_20100500.zip and nvflash_gtablet_2010110500.zip. I downloaded those and then transferred the internal files of those zips into one folder I created called Nvflash. Also, the usb driver worked for me. Some people were saying that it wasn't working on their windows 7 64 bit machines but I had no problem with it.
I figured out how to use nvflash by trial and error from reading the document in the link provided above. Hopefully this helps you out. Once you do it the first time, it's a piece of cake. Just follow the document and you'll be fine.
PS: make sure you follow the "windows" directions or the "linux" directions. There are different files depending on your computer OS and different procedures but they are pretty clearly outline in his link. Good luck.
Thanks. I tried the instructions on WIndows 7 32 bit (from Clockwork mod, not the "black screen"). I got the driver installed fine but when I ran the .bat it says USB device not found. Any idea?
Got it working! Long story short, I was pressing Power+Volume+ instead of Volume-.
Also, for anyone who does this in the future, when you try to run the .bat file, if it doesn't go, try re-powering the gtab with power+volume- again.
Hi
Trying to root my table tand get it to work, I have not succeeded something operational yet. I have made a root & CWD sd card, and in the process had backed up my tablet. I copied thgis backup to my PC as I had to try different things with the sd card.
So now I d like to restore (to start afresh) but... I google it around, and dont find any procedure!?
I am sure it is known... and am dummy... but can't invent neither.
I need use those files, because I still can't read .apks and try the apk based nook restore.
How should I go?
Your help appreciated
Thanks, Agnes
Restore method did not work....²
I have found my 3 neurons and realized I could just re do a CWD sd card, do a backup, and then take the card to my PC and add the other backup aside there (they are orgnaized by folders and date)
Then back to the tablet, go CWD / restore... but I only get a MD5 error and it does not want. Same with advanced restore.
I finally found this very simple method from Adam to restore to 1.4.0
http://forum.xda-developers.com/showthread.php?t=1402190
It semt it worked, but then when it starts again... I get the same broken rooted / whatever I have now .
Is your device 16GB or 8GB model? depending on that i can tell you what to do.
16GB model has more development and some modified stock ROMs , i even made 1 of them check here:
http://forum.xda-developers.com/showthread.php?t=1494367
~ Veronica
lavero.burgos said:
Is your device 16GB or 8GB model? depending on that i can tell you what to do.
16GB model has more development and some modified stock ROMs , i even made 1 of them check here:
http://forum.xda-developers.com/showthread.php?t=1494367
~ Veronica
Click to expand...
Click to collapse
Veronica,
You wouldn't happen to have an un-modified stock ROM would you?
LonelyTV said:
Veronica,
You wouldn't happen to have an un-modified stock ROM would you?
Click to expand...
Click to collapse
You want a sotck stock unrooted one? yet you need to reply me if your device is 8GB or 16GB model.
Depending on that i can upload it for you , but later 'cause right now i've got to go.
~ Veronica
lavero.burgos said:
You want a sotck stock unrooted one? yet you need to reply me if your device is 8GB or 16GB model.
Depending on that i can upload it for you , but later 'cause right now i've got to go.
~ Veronica
Click to expand...
Click to collapse
Yeah, an unrooted unmodified stick would be great. I've got a 16gb model.
Thanks.
16Gb device now messed uo....
Hi Veronica, thanks for the reply. I am deseprately in need of expert advice here, instead of guessing and trying...
I have a 16 GB Nook Tablet, that was bought with 1.4.0.
I now seriously again need to make a restore, as I did some bad mismanipulation and my tablet is now out of order:-(
One of my best chance I guess would be use one of the backups I have (I have several copied on my HD), but after I formatted and wrote on my SD card several times (is this the reason?), now when I try restore, I have this MD5 error.
I hope I would not run into other problems, as it seems my prop.build may have changed in the process....!
May I ask you to have a look what I did, and then confirm it would be wise try the restore you provided in the thread?
The history what I did:
- I initially had a 1.4.0 with some tweaks to sideload apps, and could no more sideload with 1.4.2 of course (and that is all I need: be able get Kindle, Le Monde, and few other apps!). I understood I had to root and was ready to try get CM7 on my internal drive, and tried a few things (Rooting with Indirect's method, ...), and could not get it to work, until I got very close:
- I restored 1.4.0 using this thread restore 1.4.0 from Adam Outler. It worked fine and apparently erased some of the problems I had that were previously preventing me to move with rooting etc.
- Then I used Albert Wertz's Backup of a rooted 1.4.0. It worked. It seems it had already OTA bloked (displaying version 9.9.9 or so)
- Then I was to install CM7 using this tutorial from ebook-reader, based on this Celtic XDA thread ("team B") (choosing the internal method) , and used the CWM flasher apk. That is where somewhere I did a mistake: after backing up and erasing all data, I somehow stupidly rebooted and got in trouble, and restored the old B&N I don't know how.
- Willing to go back to stage 1, I tried using the 1.4.0 basic restore from Adam Outler, but that did not work anymore, like if my build.prop had been changed in the process (where?)
It said "assert.failed: getprop ("ro.product.device" = blaze" or something alike.
- Then I got a long powercut (am in Africa) and some sleep
- The worse is, the NOOK does not boot and work anymore at all, it is stuck on "read forever" screen
- The curse is, I cant use other restores I have, it says MD5 mismatch
- I also can't use simple root procedures (with CWM and installing zips), as my basic system seems corrupted.
I guess a proper restore may work if I manage to do it, but I wonder what happened with my prop.build and why it was mentionned up there (was it changed in some of the process) - and whether it will create more trouble.
Your advice will be very precious!
Thanks, Agnes
agnes00777 said:
Hi Veronica, thanks for the reply. I am deseprately in need of expert advice here, instead of guessing and trying...
I have a 16 GB Nook Tablet, that was bought with 1.4.0.
I now seriously again need to make a restore, as I did some bad mismanipulation and my tablet is now out of order:-(
One of my best chance I guess would be use one of the backups I have (I have several copied on my HD), but after I formatted and wrote on my SD card several times (is this the reason?), now when I try restore, I have this MD5 error.
I hope I would not run into other problems, as it seems my prop.build may have changed in the process....!
May I ask you to have a look what I did, and then confirm it would be wise try the restore you provided in the thread?
The history what I did:
- I initially had a 1.4.0 with some tweaks to sideload apps, and could no more sideload with 1.4.2 of course (and that is all I need: be able get Kindle, Le Monde, and few other apps!). I understood I had to root and was ready to try get CM7 on my internal drive, and tried a few things (Rooting with Indirect's method, ...), and could not get it to work, until I got very close:
- I restored 1.4.0 using this thread restore 1.4.0 from Adam Outler. It worked fine and apparently erased some of the problems I had that were previously preventing me to move with rooting etc.
- Then I used Albert Wertz's Backup of a rooted 1.4.0. It worked. It seems it had already OTA bloked (displaying version 9.9.9 or so)
- Then I was to install CM7 using this tutorial from ebook-reader, based on this Celtic XDA thread ("team B"), and used the CWM flasher apk. That is where somewhere I did a mistake: after backing up and erasing all data, I somehow stupidly rebooted and got in trouble, and restored the old B&N I don't know how.
- Wwlling to go back to stage 1, I tried using the 1.4.0 basic restore from Adam Outler, but that did not work anymore, liek if my build.prop had been changed in the process (?)
It said "assert.failed: getprop ("ro.product.device" = blaze" or something alike.
- The worse is, the NOOK does not boot and work anymore at all, it is stuck on "read forever" screen
- The curse is, I cant use other restores I have, it says MD5 mismatch
- I also can't use simple root procedures (with CWM and installing zips), as my basic system seems corrupted.
I guess a proper restore may work if I manage to do it, but I wonder what happened with my prop.build and why it was mentionned up there (was it changed in some of the process) - and whether it will create more trouble.
Your advice will be very precious!
Thanks, Agnes
Click to expand...
Click to collapse
Thanks for post the whole history of what you've done 'cause pfff that saves a lot of time.
Now in this part "after backing up and erasing all data, I somehow stupidly rebooted and got in trouble"
1. Did you get to flash CM7 succesfully
2. When you mention you backed up means you backed up CM7?
3. when you mention erasing all data you mean only wipe data (factory reset) or did you wiped maybe formatted anything else?
4. What method did you use to format your sdcard
Edit: i have a MIUI backup that i made for a guy that could not install it with the other way (install .zip) of the same ROM. So at list try it for now to see what happens, if it works then go ahead and flash back the ROM you want, and always make sure to check the md5 of what you download.
http://minus.com/mwIltnw1I/4f - NT_MIUI_Tweaks_backup.zip | md5: 3518f9a3289ca6e97b569777873b899b
* Uncompress the .zip and put the folder (do not change the name of the folder) in your sdcard and flash in CWM >> backup and restore >> restore
~ Veronica
LonelyTV said:
Yeah, an unrooted unmodified stick would be great. I've got a 16gb model.
Thanks.
Click to expand...
Click to collapse
*This is a flashable .zip:
http://minus.com/mwIltnw1I/5f - NT_stock_1.4.0_B&N_ 16GB.zip | md5: f8ae4f8e88e0ced9f252e9440df3910c
~ Veronica
lavero.burgos said:
Now in this part "after backing up and erasing all data, I somehow stupidly rebooted and got in trouble"
~ Veronica
Click to expand...
Click to collapse
Thanks Veronica. Here is as much as I remember:
1. Did you get to flash CM7 succesfully?
No. While following the procedure, I did some mistake after backing up and before even trying to installing CM7. I did not realize I was in CWM within my existing rooted 1.4.0 (using the .apk), so somewhere I wiped and rebooted... to realize I was rebooting into nothing! Or actually into the original 1.4.0 B&N. And then I did some attempts to go back step by step (like restoring that 1.4.0 from Adam then the rooted 1.4.0 from Albert) and somehow went into more troubles.
2. When you mention you backed up means you backed up CM7?
No, since I did not go so far as to install CM7.
I have a backup of my initial (tweaked) 1.4.2 system, then one of Albert rooted 1.4.0 (not mine), then another one of a Nook normal OS that worked (not sure, I think 1.4.2) at some point later.
These backups were OK, I used at some point, I don't understand why then I got this MD5 errors.
3. when you mention erasing all data you mean only wipe data (factory reset) or did you wiped maybe formatted anything else?
I used the command within CWM, both to wipe data and cache
4. What method did you use to format your sdcard
I usually use Acronis Disk Manager, a quite powerful programme to change partitions on disks and also handle formatting. When I really want to make sure, I first use HP USB formatting tool, and then sometimes check on Acronis to get the partitions I want. I am not sure in what order I did that time, but was not using partitionning in fact.
I will redo it all again as I wonder if it is not a mistake on the disk that lets it misread the MD5, as I think my backups were fine.
I don't undestand:
- why my MD5 are wrong, and is it something I can fix by properly reformatting mys disks
- what is this story with "assert.failed: getprop ("ro.product.device" = blaze" and where I may have changed the build.prop. Is it somehting that will bother me further or should push me into one direction rather than another.
I will try your MUI backup. (What means MUI?). (It may take ma a day or 2 to download this through Lesotho poor internet :-(
Thanks and wil tell you what happens!
agnes00777 said:
Thanks Veronica. Here is as much as I remember:
1. Did you get to flash CM7 succesfully?
No. While following the procedure, I did some mistake after backing up and before even trying to installing CM7. I did not realize I was in CWM within my existing rooted 1.4.0 (using the .apk), so somewhere I wiped and rebooted... to realize I was rebooting into nothing! Or actually into the original 1.4.0 B&N. And then I did some attempts to go back step by step (like restoring that 1.4.0 from Adam then the rooted 1.4.0 from Albert) and somehow went into more troubles.
2. When you mention you backed up means you backed up CM7?
No, since I did not go so far as to install CM7.
I have a backup of my initial (tweaked) 1.4.2 system, then one of Albert rooted 1.4.0 (not mine), then another one of a Nook normal OS that worked (not sure, I think 1.4.2) at some point later.
These backups were OK, I used at some point, I don't understand why then I got this MD5 errors.
3. when you mention erasing all data you mean only wipe data (factory reset) or did you wiped maybe formatted anything else?
I used the command within CWM, both to wipe data and cache
4. What method did you use to format your sdcard
I usually use Acronis Disk Manager, a quite powerful programme to change partitions on disks and also handle formatting. When I really want to make sure, I first use HP USB formatting tool, and then sometimes check on Acronis to get the partitions I want. I am not sure in what order I did that time, but was not using partitionning in fact.
I will redo it all again as I wonder if it is not a mistake on the disk that lets it misread the MD5, as I think my backups were fine.
I don't undestand:
- why my MD5 are wrong, and is it something I can fix by properly reformatting mys disks
- what is this story with "assert.failed: getprop ("ro.product.device" = blaze" and where I may have changed the build.prop. Is it somehting that will bother me further or should push me into one direction rather than another.
I will try your MUI backup. (What means MUI?). (It may take ma a day or 2 to download this through Lesotho poor internet :-(
Thanks and wil tell you what happens!
Click to expand...
Click to collapse
Try formatting your sdcard again, i recommend SDFormatter. Sometimes sdcard can be the cause of many weird errors and issues.
Then copy back one of your backups within clockworkmod >> backup folder
If no go with that then try the following.
* First you need adb working
Here is a tutorial i made about it: http://forum.xda-developers.com/showpost.php?p=22049356&postcount=1
* Plug your NT to your PC using USB cable
* Download the file attached which is 1.4.0 stock build.prop, uncompress it, put it in the same folder adb is located and push it using adb while in CWM
> cd path-of-adb-tools
> adb devices
(verify that you get a code with numbers and letters)
> adb remount
(if this command does not work for you then please mount /system manually from mount&storage > Mount /system in CWM)
> adb push build.prop /system
* Unplug cable
* Try Adams acclaim_update.zip again ( preferably with nothing else in your sdcard only that .zip
* Report back
~ Veronica
OK I now was finally able to download the files.
- I guess I'll try first what you suggested with the MIUI backup after a proper reformat.
(I am just not sure which CWD file to use, as many dont leave any space on the card to put backups....)
- Then the ADB method if the 1st one does not work.
Though, part of the ADB tutorial is this "ADB root hijack" where they say you must already be rooted - that is not my case....
I'll try do tomorrow... and report! So glad to have your help here.
Successfully restored MIUI backup... what next?
YES!
@Veronica, I have been able to restore your MIUI backup!
I am not sure what it is... it looks like for a phone.... but it seems Market is working YEAH! 1st time on this Nook!!!!
Veronica you are a queen !!!
May I ask you what should be my next step now?
As a reminder, I basically want to get here Kindle (because I bought this Nook for Xmas for my Mozambican husband without realizing B&N does not have any Portuguese books, while Amazon does) and a few more apps I like. So this would do! But I d like make sure:
- my system is more or less stable
- I don't get messed up with more OTA updates
So I wonder:
- is this system recommendable? This is rooted, right? Should I prefer Launcher or Zeam Launcher here?
- should I rather use another system? Go into CM7?
Since I dont have even any Nook here behind, I am afraid of more troubles following the normal procedure, should I?
- Do I need at all to set the normal version of Nook behind (like I could use with the Nook button app) - in fact, I don't really care...
HELP PLEASE!!!! Nook 8Gb!
Can somebody help me? I bricked my nook tablet 8Gb!!
This is the whole story:
1) Rooted my NT
2) Used this apk to install CWM
http://forum.xda-developers.com/showthread.php?t=1458630
3) Tried to flash CyanogenMod 7 ROM but while it was flashing the tablet blacked out and rebooted
4) Now the tablet is stuck at the READ FOREVER screen
5) I can boot in CWM holding power+N button, but it can't flash anything, it freezes anytime I try to flash something.
6) I followed these 2 guides to unbrick my NT but they didn't work
http://forum.xda-developers.com/showthread.php?t=1470910
http://forum.xda-developers.com/showthread.php?t=1562130
Can anyone help me restore my NT at least to stock???
Please I'm desperate!!!!
@JohnDorian, Seems you got very similar problem to mine...!
It seems we got the same problem trying to do the same thing... So the same solution may work? (the only difference beeing I have not tried the unbrick mehods you did)
What I just did with Veronica's guidance, and worked for me:
- I created a 50MB sd card to boot into CWD, using this
- booted into CWM with it
- copied onto another SD card the MIUI backup Veronica provided earlier in this thread:
http://minus.com/mwIltnw1I/4f - NT_MIUI_Tweaks_backup.zip | md5: 3518f9a3289ca6e97b569777873b899b
- inserted it and did restore. It just worked and provided something that seems acceptable!
And at least, next steps may be possible...
I hope it works with you too!
Thank you for your answer!
Will this work also with my 8Gb NT?
agnes00777 said:
YES!
@Veronica, I have been able to restore your MIUI backup!
I am not sure what it is... it looks like for a phone.... but it seems Market is working YEAH! 1st time on this Nook!!!!
Veronica you are a queen !!!
May I ask you what should be my next step now?
As a reminder, I basically want to get here Kindle (because I bought this Nook for Xmas for my Mozambican husband without realizing B&N does not have any Portuguese books, while Amazon does) and a few more apps I like. So this would do! But I d like make sure:
- my system is more or less stable
- I don't get messed up with more OTA updates
So I wonder:
- is this system recommendable? This is rooted, right? Should I prefer Launcher or Zeam Launcher here?
- should I rather use another system? Go into CM7?
Since I dont have even any Nook here behind, I am afraid of more troubles following the normal procedure, should I?
- Do I need at all to set the normal version of Nook behind (like I could use with the Nook button app) - in fact, I don't really care...
Click to expand...
Click to collapse
Hello im glad to see you're back, about launchers, addons & apps it all depends of your likes.
What i gave you is MIUI ROM (operative system) without major modification (as-is) and yes it has zeam launcher but all can be modified.
I'm personally not a fan of gingerbread CM7 because i really like the eye candy of MIUI and even stock (which the buttons and menus are very similar to MIUI) so i use MIUI.
About stock i didn't mind using it even though i don't use B&N application and buy books from them buy i enjoyed the eye candy (interface/GUI), now that @cobrato released MIUI i immediately switched to that as im a huge fan of MIUI.
I have always used GO launcher as my main launcher but now im starting to use ADB in MIUI because it manages better the grid feature.
All systems you're going to find already come rooted which is standard and is the feature #1 of custom and stock ROMs, without root there is no fun. If you're in this community is because eather you have a rooted device or you came to learn how to root it and other stuffs.
If you like B&N stock ROM but don't use their apps and services you can bypass the registration and forget about the OTA updates, you can also apply on top of that the OTA block with titanium backup if you want to make sure. That is the methods i used and never ever had a problem. I also recommend you that when you flash a stock ROM do the whole procedure of OTA block and don't guess is already blocked, nothing better than do it yourself manually.
If you decide you want to make use of B&N services then you can eather go back to stock for a complete B&N experience or just install their app from the market if you're on CM7, CM9 or MIUI that is, nothing fancy but it does the job.
I have mentioned days ago that i was going to make a thread for MIUI users with how-tos and info about set it up but i've got very busy with many bricked devices around lol, but i eventually will do.
~ Veronica
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
JohnDorian said:
Thank you for your answer!
Will this work also with my 8Gb NT?
Click to expand...
Click to collapse
no, it is only for 16GB tablet, let me read your problem
~ Veronica
---------- Post added at 03:06 PM ---------- Previous post was at 02:58 PM ----------
JohnDorian said:
Can somebody help me? I bricked my nook tablet 8Gb!!
This is the whole story:
1) Rooted my NT
2) Used this apk to install CWM
http://forum.xda-developers.com/showthread.php?t=1458630
3) Tried to flash CyanogenMod 7 ROM but while it was flashing the tablet blacked out and rebooted
4) Now the tablet is stuck at the READ FOREVER screen
5) I can boot in CWM holding power+N button, but it can't flash anything, it freezes anytime I try to flash something.
6) I followed these 2 guides to unbrick my NT but they didn't work
http://forum.xda-developers.com/showthread.php?t=1470910
http://forum.xda-developers.com/showthread.php?t=1562130
Can anyone help me restore my NT at least to stock???
Please I'm desperate!!!!
Click to expand...
Click to collapse
I don't have a 8GB nook tablet to upload a backup of stock ROM and actually is very important to have nobody has been nice to upload it and post it in development section. Anyway let me give you the link of the official update to see if that helps, i was checking yesterday and they provide one for both i think there is not a separate section for the 8GB model so i assume that update is for both models containing 1.4.2
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/
under -Get Version 1.4.2 Today
~ Veronica
How can I flash this update?
JohnDorian said:
How can I flash this update?
Click to expand...
Click to collapse
right you dont know how, ok let me download the file and see if i make a kind of acclaim_update.zip for you to try.
can't flash any rom as a flashable.zip and backup folder? have you tried both?
~ Veronica
No, I can't flash anything from CWM...
I've basically spent my entire day off from work trying to root my Nook Tablet 8GB to get CM10.1 put on it, and I'm ready to yank my hair out. A while back I successfully got CM10 on an sdcard and have been running that from the sdcard while my warranty was still active (just in case). Now my warranty's run out, and CM10 had been running sluggish for a while, in spite of my cleaning off all unnecessary files regularly. So I figured I'd try an internal ROM install. After hunting around for some really good detailed instructions for noobs (because I totally am one), I found this post (http://forum.xda-developers.com/showthread.php?t=2037368) and decided that even though it looked inefficient to go from CM7 to CM10, it broke the steps down enough for me to follow along.
However, I'm now stuck with CWM not reading the sdcard once it's time to install CM7 and gapps from the zip files. I keep getting the message, "No files found." I've tried unmounting the sdcard (and mounting "sd-ext," just for kicks), and it says, "Error unmounting /sdcard." If I try choosing "format /sdcard," it says, "E:format_volume failed to unmount '/sdcard.'" I've tried popping it out and back in multiple times. I've tried formatting in SDFormatter over again (even did a full overwrite erase, which takes forever, b/c I got a message saying the device doesn't support flash erase). I've been using Minitool to ensure that the partition is always FAT32, primary, set to active. I've gone into the stock OS and used a workaround I found to ensure that it will install apps from unknown sources. I've tried doing the root again from the beginning (which is a pain in the butt because I only have 1 sdcard to use for both the root and the ROM, so I have to keep switching the files out). I have no idea what I could be doing wrong, but I fear that it's something really basic.
Does it matter that I'm leaving the partition labeled "boot" for the ROM install? Is there a better way to put the files on the sdcard besides just with a Windows drag and drop? Is there a way for me to reboot the Nook from within CWM to maybe force it to read the sdcard fresh (keeping in mind that the sdcard no longer has the CWM files on it by that point)? I've seen some info online about people having issues with this class of sdcard, but I really don't want to spend the money on a new one until I rule out the possibility of a stupid user error. I'm also loathe to give up and go back to running a ROM from the sdcard because I've already put over 8 hours into trying to make use of the full Nook memory... If anyone has suggestions, I'd greatly appreciate it. Please keep in mind that any instructions will need to be very, very basic, though.
CWM version 5.0.2.8
sdcard type: SanDisk 8GB Class 4
Files on the sdcard: cm-7-TEAM-B-BETA1-signed.zip and gapps-jb-20130301-signed.zip
MidnightFrost1701 said:
I've basically spent my entire day off from work trying to root my Nook Tablet 8GB to get CM10.1 put on it, and I'm ready to yank my hair out.
...
Click to expand...
Click to collapse
There is no point in flashing CM7 if you're aiming to immediately flash CM10 on top of it.
To flash CM10.x, I'd suggest you try the process outlined at http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1. See http://forum.xda-developers.com/showpost.php?p=42985699&postcount=117 if you'd like to use a more recent CM10.1 build.
...
Files on the sdcard: cm-7-TEAM-B-BETA1-signed.zip and gapps-jb-20130301-signed.zip
Click to expand...
Click to collapse
You'll need an older version of gapps to go with CM7, see http://goo.im/gapps.
digixmax said:
There is no point in flashing CM7 if you're aiming to immediately flash CM10 on top of it.
To flash CM10.x, I'd suggest you try the process outlined at http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1. See http://forum.xda-developers.com/showpost.php?p=42985699&postcount=117 if you'd like to use a more recent CM10.1 build.
You'll need an older version of gapps to go with CM7, see http://goo.im/gapps.
Click to expand...
Click to collapse
Thank you, I'll try that tonight after work! After having been through the steps in the original instructions so many times, I'm familiar enough with things like Minitool Partition Wizard that I can get by with slightly less noobish instructions now. So that's one silver lining... [crosses fingers]
It seems to have worked! The first time I tried to turn it on after the install, the screen went and stayed black after the initial Cyanoboot screen. So I forced a reboot, but it appears to be running just fine! Thanks for the help!