Related
Is there currently a recovery ROM for the g-Tablet version shipped by woot.com? This is a 3389 ROM with some customizations. Most, or possibly all, of these can be replicated easily since they consist primarily of some home screen setup, links, and a few apps including the Kindle reader, ColorNote, and Pandora.
Following the recommendation to do a data wipe after installing a replacement ROM appears now to mean that even with the backup.zip from my wife's unmolested tablet I'm unable to return the tablet to its actual original state.
If there is not, I currently have one woot.com g-Tablet that is unopened since my wife ordered one for herself after I'd ordered one for each of us. I'm planning to sell it, but if I can create a backup ROM without messing the tablet up for the eventual purchaser I'm willing to try.
I'd like the same thing, if you come across one or make one yourself.
I ended up doing a Format SD Card, thinking it literally meant the external MicroSD Card I had put in the device, because I had read this may help prevent force closes, but it formatted the internal storage which had my stock backup on it and left my MicroSD card alone. I should have copied that over to my PC before wiping anything, just in case, but I'm so used to Android phone hacking that I thought I could get away with it.
I had a ton of force closes with TNT Lite and rebooted, hoping it would help, but then it got stuck in a reboot-loop. So I ended up repartitioning the internal space (thus wiping it AGAIN ::sigh: and using nvflash to restore bekit version 1105 (nvflash_gtablet_2010110500) and OTA updating.
Woot ROM
Going to make one now. Finished charging my "woot" g tab and booted once to make sure it worked. Just installed clockwork. Making backup. Let me know if you still need it.
jm20 said:
Going to make one now. Finished charging my "woot" g tab and booted once to make sure it worked. Just installed clockwork. Making backup. Let me know if you still need it.
Click to expand...
Click to collapse
Yes I do, please.
uploading now....
uploaded
http://www.mediafire.com/?poe59nppdfqhizn
jm20 said:
http://www.mediafire.com/?poe59nppdfqhizn
Click to expand...
Click to collapse
Thank you for doing that. Unfortunately, it doesn't restore the tablet to its shipped state.
Edit: scratch that - I did eventually get it to do exactly that.
mstevens said:
Thank you for doing that. Unfortunately, it doesn't restore the tablet to its shipped state.
Click to expand...
Click to collapse
I'd originally assumed the way to use this would be to rename it to update.zip and use it in recovery. That seemed to flash something, but did not come close to restoring to the shipped state.
Next, I realized it was a clockworkmod backup and figured I could extract it to my clockworkmod backup directory and run a restore from it. This just gave me an MD5 checksum error.
Any more thoughts on how to use this?
Edit: see my later post. I did get it to work.
Do you need the ROM?
My woot Tablet Reset after the 3rd power cycle and restored itself to something besides the original shape I received it in. I thought it was ridiculous as it would not show the "Stock" Videos it was shipped with. Angry Birds also did not work originally. After it Reset things worked. I would return it in the state it is and say it didn't work almost at all when it first arrived.
The original active wallpaper was kind of cool though.
TomRathbun said:
I would return it in the state it is and say it didn't work almost at all when it first arrived.
Click to expand...
Click to collapse
My g-Tablet is working fine. It's just a bit messed up in terms of applications and links after I flashed a few ROMs and now I'm having trouble getting it back to its original state.
TomRathbun said:
My woot Tablet Reset after the 3rd power cycle and restored itself to something besides the original shape I received it in. I thought it was ridiculous as it would not show the "Stock" Videos it was shipped with. Angry Birds also did not work originally. After it Reset things worked. I would return it in the state it is and say it didn't work almost at all when it first arrived.
The original active wallpaper was kind of cool though.
Click to expand...
Click to collapse
Mine was the same way. I didn't wait until it was fully charged until powering it up and it had angrybirds and some other stuff loaded on it. None of it would run though, it would just force close out. After turning it off, waiting for it to fully charge, and then turning it back on did I get put through the new user wizard and everything worked right.
would these work?
Hello, I was curious to know if you had seen (and if it would work) the viewsonic stock Roms that are mentioned on another post in the g tablet section of this site. I can't post links yet but there is a sticky called "viewsonic G-Tablet ROMs frequently asked questions (read this first)" this is posted in the G tablet general section.
The 3rd post down in that sticky has "gtablet recovery firmware images (official viewsonic images)" and there are 3 versions available to download the latest being 3316. Could you flash to this and then do ota updates to get to the current version? I'm sure you'd have to get a few of the apps back yourself (angry birds, Pandora, whatever else came on it) but wouldn't this get you pretty close to how it was when you got the gtab? I'm new to all this and am just throwing this out as a suggestion. I'm curious to know if this is all you'd need though.
barcod21 said:
Hello, I was curious to know if you had seen (and if it would work) the viewsonic stock Roms that are mentioned on another post in the g tablet section of this site.
Click to expand...
Click to collapse
Those work pretty much as expected, but they don't restore the tablet to its state as shipped by Woot. Not having seen any other g-Tablet, I can't be certain but I strongly suspect they do restore the tablet to what it would have been if I'd gotten it from Sears or someplace. I already know I can rebuild it. I'm just looking for the lazy way and, ideally, to get it *completely* back to stock, i.e., any updated drivers or other things that may not be immediately obvious.
So, I did get jm20's file to work for restoring my woot.com g-Tablet to its original shipped state. There may be several ways to do this, but I'll outline what worked for me.
- installed clockworkmod and booted into cwm recovery.
- did a data wipe and formatted all partitions then rebooted, whereupon I naturally got an error.
- rebooted into APX mode.
- performed an NVFlash restore.
- as soon as the tablet rebooted and asked if I wanted to connect via USB, I connected without doing any setup.
- via USB to the tablet, created a directory clockworkmod in the root of sdcard (on the tablet, not the removable SDHC card) and a subdirectory backup within that.
- on my computer, extracted the directory 2009-01-01.00.26.55 from the downloaded .zip file.
- copied that directory via USB into /clockworkmod/backup.
- reinstalled clockworkmod.
- rebooted into cwm and ran a restore of the directory I'd copied.
At this point the tablet now looks and acts mostly like it did when I first opened it. The only problem is that OTA updates no longer work because of clockworkmod. I addressed this via NVFlash using the following in a command window:
- nvflash.exe --bl bootloader.bin --download 9 recovery.img
whew!
Sorry about the lack of instructions
I am really busy with a bunch of other stuff, and I'm just playing with the G-tab when I take a break. The file I uploaded is as you figured out just a direct copy of the folder that clockwork recovery made when I told it to backup the "unused woot g-tab"
Like I said I only booted it up once to make sure it worked and then I immediately made the backup which is why the date says 2009.
After the backup was done, I copied the folder that clockwork made which contained the backup files to my desktop. I then zipped it up and uploaded it to mediafire.
Therefore the zip file is not a file that clockwork can use to restore the ROM, however if you extract the folder/files from the zip file and copy them to the g-tab, clockwork will recognize the folder and will do a full restore from that folder / files.
Sorry for the confusion.
A few other things:
I bought two of these from Sears as soon as they came out (late October 2010). I opened one and tried to use it. The stock ROM barely worked. It was basically useless. I knew the hardware was great but it was crippled by the ROM. I installed clockwork and flashed a few ROMs and found Vegan to be the best of the bunch, however even that left much to be desired as it was still very early on in the whole scheme of things.
After two days of using the one I had opened, things weren't looking good and I returned the unopened second one.
After about 10 days of trying to see the positives, I couldn't take it any longer and the first had to go back also. Unfortunately I had rooted it and installed clockwork and I simply couldn't bring myself to return it in that condition so I spent somewhere around 12+ hours reading various forums (mostly this one, android forums, and android central) figuring out how to completely return the unit to "stock". No traces of clockwork or any other boot manager and I put a clean stock ROM back on it.
Two reasons why I mention all of this:
1. If someone is needing to do this, it can be done unfortunately I have no idea how I did it and didn't bother to keep the files or information because I swore I'd never buy another G-tab (woot made a liar out of me).
2. If you are considering using an older "stock" ROM, don't waste your time. The woot ROM is actually pretty good. Had I known the woot ROM was halfway decent I would have bought two of these. Any of the newer ROMs are probably better than what I initally experienced.
Lastly, if anyone cares; I am currently running Calkulin's ROM with Clemsyn's kernel and I must say I am impressed. The unit is stable and very fast. Those guys have done some great work. Finally some great software that can take advantage of the hardware. Again, had I known things had gotten so much better I'd have ordered two.
If you guys are running something else and you like it let me know, I haven't had time to mess with the other ROMs.
OK, I have got to get back to work. Hope this helps.
Clarification
jm20 said:
Going to make one now. Finished charging my "woot" g tab and booted once to make sure it worked. Just installed clockwork. Making backup. Let me know if you still need it.
Click to expand...
Click to collapse
Brand new Android user here. My Woot gtablet reset itself also after the third reboot to something other than the original. If I figure out how to insert your Woot ROM zip file, this will restore the gtablet to it's orginial state?
Thanks
TomRathbun said:
My woot Tablet Reset after the 3rd power cycle and restored itself to something besides the original shape I received it in. I thought it was ridiculous as it would not show the "Stock" Videos it was shipped with. Angry Birds also did not work originally. After it Reset things worked. I would return it in the state it is and say it didn't work almost at all when it first arrived.
The original active wallpaper was kind of cool though.
Click to expand...
Click to collapse
I had this experience as well. (This Woot tab is my second g-tablet.) I updated it immediately upon the first boot, then rebooted. One or two reboots later, a setup screen magically appeared. After going through the setup process it seems that all of the original woot settings were now gone.
It also seems that Adobe Flash is no longer installed, and has to be re-installed. I haven't tried Angry Birds yet, but I believe that the latest firmware update comes with that pre-installed. Flash can be re-installed by downloading it from the ViewSonic g-tablet "Favorites" page, or use this link and reboot after installation:
http://www.freewarelovers.com/android/download/temp/1291899570_Adobe_Flash_Player_10.1.95.1.apk
As for being able to return to a "stock" firmware, I always save the updates before allowing it to install them. I believe they can be found in the /cache folder after it downloads, and must be copied to external storage before you run the update. I haven't actually tried to use these to restore to a stock firmware, but I believe that you just copy it to /mnt/sdcard and rename it to update.zip.
These are the versions that I saved:
update-smb_a1002-2967-user.zip
update-smb_a1002-3053-user.zip
update-smb_a1002-3588-user.zip
Edit: None of these are the "Woot" version.
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...
Hello,
I've installed CM internal to (2) NT 16GBs without incident, and I got stumbled by the n button not working with 1.4.1 that was on my third. Ultimately - I downgraded to 1.4.0, installed CM7, and then did the dumb thing.
I meant to hit wipe data and cache, and I clicked factory reset in CWM. (And at this point - it is stuck in a state where I can boot to CWM - but cannot get CM7 to boot in any form from the internal rom).
I attempted the following
1) acclaim restore (just tried didn't do anything)
2) backup / restore from alternate nook Tablet 16Gb (man this seemed promising ...)
3) couple of the different unbrick scenarios - but I don't have adb, and it seems like windows 7 is not a happy camper with nook usb devices, (and adb isn't happy either.)
4) meghd00t restores (couple of different variations.)
does anyone have any starter threads that I should start walking down for the same stuff - I have browsed, and it's been a couple of hours and I'm exhausted. will poke back in tommorow, and will get this thing plugged into a linux host.
It didn't seem like adb could be so hard ...
--Adrian
Hmmm interesting... ok first of all doing this "I meant to hit wipe data and cache, and I clicked factory reset in CWM" is not dumb is ok to do but is not good signal the hang actually is very weird. Maybe all you have is a corrupted cwm recovery flash. Now be explicit if you indeed could try some unbrick methods succesfully (the ones running from sdcard) and what methods exactly did you try.
~ Veronica
things I've tried - part 1
1) just try to restore to factory with acclaim_update.zip on non-booting sdcard , (this is the 1.4.0 image) - I get the grey n, a flash of white - (like it's going to boot), and that that "please restart your device and try again..."
(This worked when it was factory), but it seems like the logic to check the sd card and start to recover isn't working.
2) Tried the thread here - http://forum.xda-developers.com/showthread.php?t=1562130 - meghd00tr4-sdimg.zip boots, but first time - get red reverse highlighted line - "booti: bad boot image magic in memory" - s5 in the upper left corner of the cyanoboot screen, and the n button doesn't seem to do anything.
3) same thread different image - repart.img, this runs fine- and after about 30 seconds of boot, I get a green check, (waited a full (2) minutes after that green check before I unplugged it.) - same message after boot.
4) full restore of nook tablet from current good cm7 image (and this is the one that most concerns me) - NT16gbV4_6 based cwm v5.5.04 - attempting restore of backed up alternate nook tablet - and the exact same thing happens at boot - does the image not touch partions that aren't related to the root install -(this seems like maybe there is something the bootloader is looking for in the image that isn't right, and it wedges?)
I am going to work on getting an adb setup going that works and then start working down a couple of fix recovery scenarios today / tonight.
It doesn't seem like this is unrecoverable - and the worst part is -I had cm7 booting fine for a couple of reboots, and then something went awry.
--Adrian
as I think about this ...
I do have (2) differnt backups, and I wonder if that restore was the wrong thing to do.
I got to thinking this as I saw the restore of the .android_secure file, from the ALTERNATE nook. I have the backup from the 1.4.0 "original working" image of this nook before the cm 7 issues- but I put it on an SD card that is safetly out of my reach. (In a friends cell phone.)
I think an easy thing will be to restore that backup as another test.
-Adrian
peril said:
I do have (2) differnt backups, and I wonder if that restore was the wrong thing to do.
I got to thinking this as I saw the restore of the .android_secure file, from the ALTERNATE nook. I have the backup from the 1.4.0 "original working" image of this nook before the cm 7 issues- but I put it on an SD card that is safetly out of my reach. (In a friends cell phone.)
I think an easy thing will be to restore that backup as another test.
-Adrian
Click to expand...
Click to collapse
Right, try that first, dont attempt anything advanced yet. Your problem could be solved easily
Just to make sure you flashed cwm from @Indirect app?
~ Veronica
Sent from my Nook Tablet using xda premium
Wait, can you boot into a CM7 SD ROM? From there you could try reflashing recovery.
Sent from my R800x
FIXED
I used this method - and I was good to go.
http://forum.xda-developers.com/showthread.php?t=1470910
In one of the flashes - must have hit the power prior to something being complete with the recovery.
thanks all for your support - and really appreciate the time in the forum. I'm going to put together a torrent with the recovery stuff in it, and make sure it's available as my little part. (Give me a day or so.)
Thanks again.
--Adrian
The problem with that is that you will lose your original serial ID's and MAC address if you didnt backup your rom partition (mmcblk0p5) first so if you use B&N services you wont be able to register after flash any stock rom.
~ Veronica
Sent from my Nook Tablet using xda premium
I also screwed up...Reverting to 1.4.0
Tried to revert to 1.4.0, and followed all instructions as showned on a youtube video. Unfortunately, as it was reverting back to older version as soon as it finished the process - the tablet wouldn't start back up. Did any one ever have this happen to them.. Fortunately, I had just bought today at WalMart. So, I'm going to replace it...
Was just curious, if it ever happened to any one. If so what did I possibly do wrong....
mr_truevision said:
Tried to revert to 1.4.0, and followed all instructions as showned on a youtube video. Unfortunately, as it was reverting back to older version as soon as it finished the process - the tablet wouldn't start back up. Did any one ever have this happen to them.. Fortunately, I had just bought today at WalMart. So, I'm going to replace it...
Was just curious, if it ever happened to any one. If so what did I possibly do wrong....
Click to expand...
Click to collapse
Hmm i think you have a 8GB Nook Tablet and the acclaim_update.zip is only for 16GB NT.
~ Veronica
ubuntu recovery.
This was strictly for CM7. I have no problem with being locked out of the B&N services. (I use the nook application for that access.)
Wish I would have known the serial number before / after. I was able to login to my B&N account after 1.4.0 was restored from ubuntu.
--Adrian
lavero.burgos said:
The problem with that is that you will lose your original serial ID's and MAC address if you didnt backup your rom partition (mmcblk0p5) first so if you use B&N services you wont be able to register after flash any stock rom.
~ Veronica
Sent from my Nook Tablet using xda premium
Click to expand...
Click to collapse
Hi There
Such a great program is the Nabilab thank you!
Ive tried to serach the forums but am getting burried under so much info that I dont all fully understand, please forgive my ignorance. Im also not even sure if I am posting in the right place (trying to do this at work when boss isnt looking which is hard).
I have a backup and restore question please related to UK version of the nabi2.
I downloaded the full version of the nabilab tools software including the stock condition to my PC. I then ran the full installation (option 1) and all worked brilliantly (little trouble with the drivers but solved).
But now, 4 weeks later, the nabi has lost wifi which I understand from reading is an issue with OTA (which I didnt know about and hadnt realised was turned on).
So from what I can tell, I need to basically blank the nabi2 and then restore it. But I have just had the thought, is the stockbackup file within my internal SD card actually a backup of my own system created when I ran the tools setup/installation (which I think is the case), or is it a copy of the downloaded stockbackup that came with the nabilab tools and was automatically copied across during the tools installation?
The reason for asking is that I just thought, that because my Nabi2 is a UK version (I did update the OS as instructed before running all the nabilab tools installation) then if the stockbackup is from the downloaded pack, and thus not UK, then trying to restore that might cause me problems with the UK version and maybe the uk nabistore??
Would I be better going into Nabi parent-mode and using the option in the settings to reset to factory defaults (will this work to restore nabi to earlier version?) or am I ok to use the stockbackup that is sitting on my internal sd card?
Should I use twrp to "wipe" first before trying any backup or should I just run restore?
Do I use the nabilabs menu to try and do the restore or should I go into TWRP to do the restore?
Id really really appreciate any help please as Im very new at all this and not very knowledgable. The Nabi2 is my sons. He is 4 and has autism and doesnt have any communication or language so doesnt understand that his Nabi ran out of storage space thus I used the root to be able to use an app swapping internal-external sd cards for more space. His Nabi means everything to him and its starting to look like it will help his communication, he doesnt understand why parts of it are now not working which leads to huge upsetments (really huge) and we cant explain to him that it will be fixed soon, and so im desperate to fix it as quick as I can.
Please any help would be wonderful.
many thanks for even taking the time to read my post.
Alex
alexbobspoons said:
Hi There
So from what I can tell, I need to basically blank the nabi2 and then restore it. But I have just had the thought, is the stockbackup file within my internal SD card actually a backup of my own system created when I ran the tools setup/installation (which I think is the case), or is it a copy of the downloaded stockbackup that came with the nabilab tools and was automatically copied across during the tools installation?
Click to expand...
Click to collapse
If you look in the TWRP/BACKUPS/yourserial/ folder the folder called "stockunrooted" should be your Nabi's backup. A folder called "abcdstock123" is the stock backup the Nabilab would create, but it will only create this if you ran the restore "Nabi to stock" from Nabilab. Honestly before you do anything else, if you find the folder stockunrooted COPY THAT TO YOUR COMPUTER. I can't stress that enough, we don't have near as many UK owners here. If something goes wrong we have plenty of north american versions the users here can get for you, but not many if any UK ones.
alexbobspoons said:
The reason for asking is that I just thought, that because my Nabi2 is a UK version (I did update the OS as instructed before running all the nabilab tools installation) then if the stockbackup is from the downloaded pack, and thus not UK, then trying to restore that might cause me problems with the UK version and maybe the uk nabistore??
Click to expand...
Click to collapse
I would definitely try and restore your stock backup if you have one. I have no facts on this matter but the UK store could react negatively to something such as your build.prop being different. Also there might be a difference in WiFi configuration as I think there are some differences between power in channels 12 and 13 outside North America. I would avoid restoring the Nabilab one unless it was a last resort. If you don't have your stockunrooted, someone out there likely has a UK backup. We would be better off seeking them out and seeing if they would upload you one.
alexbobspoons said:
Would I be better going into Nabi parent-mode and using the option in the settings to reset to factory defaults (will this work to restore nabi to earlier version?) or am I ok to use the stockbackup that is sitting on my internal sd card?
Should I use twrp to "wipe" first before trying any backup or should I just run restore?
Do I use the nabilabs menu to try and do the restore or should I go into TWRP to do the restore?
Click to expand...
Click to collapse
-Either a factory reset, or restoring the stock backup of your Nabi(not the stock from Nabilab) should work. A factory reset won't revert you to an older Nabi revision it will simply wipe everything from the tablet, and leave you on whatever version you are currently on. The restoring of your backed up version will more or less result in the same since you upgraded before backing up. However the major difference will be your backup will have the Nabi setup done, where a factory reset will erase it. Also it will WIPE your stockunrooted backup that I talked about at the beginning, we don't want that without you copying it to your computer first. So you skip the step of setting up parent mode, and your wireless password would likely be there so you would save yourself 2 minutes.
-If you restore your stock backup of your tablet, and restore boot, system, and data there would be no reason to wipe first. Although out of habit I always clear cache and dalvik cache anyway, even though it gets wiped by the restore. No need to clear system as TWRP will format that partition before restore anyway.
-Go into TWRP. Select restore tab. Find folder called stockunrooted and select. Restore all. Boot, system, data check. I assume you have gotten into TWRP fine but just in case: From powered off, press and hold both vol+ and power, then select recovery kernel.
-Or you could just do a factory reset. The differences I highlighted above.
-Either option will break root, and gapps. To get them back use options 3 and 4, instead of 1 like you did last time in Nabilab. Gapps only, Root only, since you would already have stockunrooted no need to make a second one.
Thank you so much for your reply the info is invaluable.
Sorry for spelling your name wrong.
Sorry also for posting this in the wrong place (as I have since found from browsing)
Thanks again for the help.
Ill backup the stock to my pc, then will try using twrp to resotre that backup and then use the nabilab again to root. Then I guess its simply logging into the nabi and google store to download any missing apps.
Thanks you so much
Alex
PANIC
Oh no ive gone to the folder on my nabi through the usb cable and the stockunrooted folder appears to be empty.
I did choose option one when I did the nabitools so I just dont understand why theres nothing there.
When I looked into twrp last night it seemed to think there was a backup there for stockunrooted so I dont know if its dissapeared or whether it was never there in the first place.
PANIC
As there is not supposed to be many UK nabi backups out there (and im time limited due to my son relying on the tablet) am I now only left with the factory defalt reset? (not quite sure how to do that really)
I know I cant use the one in the nabilab because that is USA version.
Please help
Alex
alexbobspoons said:
Oh no ive gone to the folder on my nabi through the usb cable and the stockunrooted folder appears to be empty.
I did choose option one when I did the nabitools so I just dont understand why theres nothing there.
When I looked into twrp last night it seemed to think there was a backup there for stockunrooted so I dont know if its dissapeared or whether it was never there in the first place.
PANIC
As there is not supposed to be many UK nabi backups out there (and im time limited due to my son relying on the tablet) am I now only left with the factory defalt reset? (not quite sure how to do that really)
I know I cant use the one in the nabilab because that is USA version.
Please help
Alex
Click to expand...
Click to collapse
I would go into TWRP. Then in the advanced section use the file manager. Navigate to /data/media/TWRP/BACKUPS/serial/stockunrooted and then see if it is blank or if there are files in it. boot.wim boot.wim.md5, etc etc
If it's gone then it will have to be a factory reset.
aicjofs said:
I would go into TWRP. Then in the advanced section use the file manager. Navigate to /data/media/TWRP/BACKUPS/serial/stockunrooted and then see if it is blank or if there are files in it. boot.wim boot.wim.md5, etc etc
If it's gone then it will have to be a factory reset.
Click to expand...
Click to collapse
Hi
Did that, folder empty and no files in it.
Have done a factory reset and YAY all good.
Have re-signed in to nabi account, have redone the root using nabilab, have then installed the ext-to-int sd card app and the big card is now in memory.
So now its just a case of sitting back and slowly reinstalling all the apps from the nabi store and then the google store. Once all thats done ill then go into TWRP and do me a proper full backup.
Phew!
Thank you so much for your help it has been invaluable. My deepest gratitude!
Thank you!
Alex
alexbobspoons said:
Hi
Did that, folder empty and no files in it.
Have done a factory reset and YAY all good.
Have re-signed in to nabi account, have redone the root using nabilab, have then installed the ext-to-int sd card app and the big card is now in memory.
So now its just a case of sitting back and slowly reinstalling all the apps from the nabi store and then the google store. Once all thats done ill then go into TWRP and do me a proper full backup.
Phew!
Thank you so much for your help it has been invaluable. My deepest gratitude!
Thank you!
Alex
Click to expand...
Click to collapse
So glad its working again! Make sure to copy that backup you make to your computer
aicjofs said:
So glad its working again! Make sure to copy that backup you make to your computer
Click to expand...
Click to collapse
I surely surely will (multimple copies)
Thank you again. Its hard to explai how much my son relies on his Nabi so its hard to explain how grateful I am you are a hero!
Alex
UK Nabi 2 Rom
Hello All, I`m looking for a UK version of the 1.9.37 rom after wiping my daughters Nabi, forgetting to make a backup way back when i was rooting it last year. I`ve tried the stock version but when it tries to do the second of the two part ota i get the dead robot and Nabilab doesn`t see it when connected.
Any help would be greatly appreciated.
Hi all,
This is the first time I've tried installing a custom ROM on my VZW S4 (i545) (MDK firmware. Yes, I held out on the OTA since May). I've got a few thoughts and a couple of questions I was hoping could be addressed. I consider myself familiar with flashing ROM's and whatnot, so I won't need hand-holding steps in answer to my questions.
Some info:
VZW S4
MDK Firmware
Recovery: OUDhs CWM Touch Req0very v1.0.3.5
I haven't taken any OTA since I got the phone back in May. This leads me to believe (correct me if I'm wrong) that I'm on Android 4.2.2?
Current ROM: AOKP Nightly Build for 10/31/2013 (MR2)
Thoughts: Holy hell, this ROM is BLAZING fast. I am missing a few features, but none I use regularly (I don't use any of the TouchWiz "smart" features. Damn battery hogs). I was able to flash this over and install GAPPS without any problems. Loading time is incredible, and I love how clean the interface is.
Questions:
Can anyone help me figure out why I cannot install CM10.2? Not sure if that's because I downloaded the wrong version or something, but after flashing it, the screen stays stuck at the Galaxy S4 logo and doesn't move. Maybe I didn't wait long enough, but it surely didn't move in any reasonably expected time (AOKP, by comparison, loaded probably <1 minute). Any thoughts on why this might be? I really want to try CM10.2, so perhaps I should try a different build?
Another question/concern: I downloaded a few different ROMs last night -- CM10.2, AOKP and st0ckdr0id. AOKP installed fine, CM10.2 froze up, but when I installed st0ckdr0id (after wiping out, of course), I got what I think is referred to as a kernel panic. The message was similar to "This phone has software installed on it that Verizon Wireless has determined to be unsafe. Please power off the phone and take to the nearest Verizon Wireless store for help". In the top-left corner, it had in bold RED letters "Kernel secure: FAIL" (or similar wording). I fixed this by booting back into recovery, wiping out, and then installing AOKP again. Can anyone help me understand why this happened?
Why is only ~10GB of space still available when I -thought- I wiped out everything?
What I'm really searching for is an AOSP ROM that is very clean and light, but has SOME of the TouchWiz features. Any recommendations?
My phone only shows me as having a 3G connection, where normally I have 4G LTE. Anything I can do to fix this? Is this an issue with the ROM not detecting the right kind of radio? Bug report, perhaps?
I can't mount my external_sd in my CWM anymore. Yes, I used to be able to do it at one point, because I've done an external nandroid backup to it from within CWM in the past (as of October 29th, if the date on the backups is correct). I've read in other Google searches that it has something to do with the formatting of the SD card, but I haven't removed that SD card from my phone in a few months to have adjusted anything to do with formatting. I plugged the memory card into my Linux laptop this morning while diagnosing this and got an error about an unknown exfat partition. Any advice would be greatly appreciated.
Stupid question: Is there a way to -completely- wipe my internal SD card clean of all my current files? I know when I "wipe" /data I can still see all of my files from the previous installation, and I'm not ballsy enough to wipe /sdcard. I guess the question that then coincides with this is if I were able to completely wipe the phone, I assume that would wipe the recovery as well?
Sorry for some of the novice questions -- I have no problem messing with my old TF300T tablet (because NVFlash will save the day), but this is my only phone, only line of communication and SOLE way for me to answer calls for work (24/7 rotating on-call), so it is VERY important to me to ask questions and not go down for more than 1 hour.
Thanks for all help guys, its much appreciated. I hope to be able to test ROMs regularly and maybe start posting video reviews or something, who knows?
Thanks,
Opethfan89
opethfan89 said:
Hi all,
This is the first time I've tried installing a custom ROM on my VZW S4 (i545) (MDK firmware. Yes, I held out on the OTA since May). I've got a few thoughts and a couple of questions I was hoping could be addressed. I consider myself familiar with flashing ROM's and whatnot, so I won't need hand-holding steps in answer to my questions.
Some info:
VZW S4
MDK Firmware
Recovery: OUDhs CWM Touch Req0very v1.0.3.5
I haven't taken any OTA since I got the phone back in May. This leads me to believe (correct me if I'm wrong) that I'm on Android 4.2.2?
Current ROM: AOKP Nightly Build for 10/31/2013 (MR2)
Thoughts: Holy hell, this ROM is BLAZING fast. I am missing a few features, but none I use regularly (I don't use any of the TouchWiz "smart" features. Damn battery hogs). I was able to flash this over and install GAPPS without any problems. Loading time is incredible, and I love how clean the interface is.
Questions:
Can anyone help me figure out why I cannot install CM10.2? Not sure if that's because I downloaded the wrong version or something, but after flashing it, the screen stays stuck at the Galaxy S4 logo and doesn't move. Maybe I didn't wait long enough, but it surely didn't move in any reasonably expected time (AOKP, by comparison, loaded probably <1 minute). Any thoughts on why this might be? I really want to try CM10.2, so perhaps I should try a different build?
Another question/concern: I downloaded a few different ROMs last night -- CM10.2, AOKP and st0ckdr0id. AOKP installed fine, CM10.2 froze up, but when I installed st0ckdr0id (after wiping out, of course), I got what I think is referred to as a kernel panic. The message was similar to "This phone has software installed on it that Verizon Wireless has determined to be unsafe. Please power off the phone and take to the nearest Verizon Wireless store for help". In the top-left corner, it had in bold RED letters "Kernel secure: FAIL" (or similar wording). I fixed this by booting back into recovery, wiping out, and then installing AOKP again. Can anyone help me understand why this happened?
Why is only ~10GB of space still available when I -thought- I wiped out everything?
What I'm really searching for is an AOSP ROM that is very clean and light, but has SOME of the TouchWiz features. Any recommendations?
My phone only shows me as having a 3G connection, where normally I have 4G LTE. Anything I can do to fix this? Is this an issue with the ROM not detecting the right kind of radio? Bug report, perhaps?
I can't mount my external_sd in my CWM anymore. Yes, I used to be able to do it at one point, because I've done an external nandroid backup to it from within CWM in the past (as of October 29th, if the date on the backups is correct). I've read in other Google searches that it has something to do with the formatting of the SD card, but I haven't removed that SD card from my phone in a few months to have adjusted anything to do with formatting. I plugged the memory card into my Linux laptop this morning while diagnosing this and got an error about an unknown exfat partition. Any advice would be greatly appreciated.
Stupid question: Is there a way to -completely- wipe my internal SD card clean of all my current files? I know when I "wipe" /data I can still see all of my files from the previous installation, and I'm not ballsy enough to wipe /sdcard. I guess the question that then coincides with this is if I were able to completely wipe the phone, I assume that would wipe the recovery as well?
Sorry for some of the novice questions -- I have no problem messing with my old TF300T tablet (because NVFlash will save the day), but this is my only phone, only line of communication and SOLE way for me to answer calls for work (24/7 rotating on-call), so it is VERY important to me to ask questions and not go down for more than 1 hour.
Thanks for all help guys, its much appreciated. I hope to be able to test ROMs regularly and maybe start posting video reviews or something, who knows?
Thanks,
Opethfan89
Click to expand...
Click to collapse
Wow that's a lot. Let's see if we can get you answers.
1. Switch recoveries to twrp 2.5.0.2. I can't stress the importance of the particular version enough. There are others. This is absolutely the most stable. It's what the devs use. I think then your cm issue will be resolved.
Correct way to wipe with twrp.
1.wipe - >factory reset.
2. Advanced wipe - >check system, data, davlik, cache then wipe.
3. The go back to main screen and install rom.
2. Answered by answer one. Lots of people have lots of opinions about the various recoveries. All I can tell you is this is what all the devs use for their recovery. Can't argue with that.
3. Reserved space. It might say you have 16 gigs but a good size chunk is taking merely by formatting. Then the ROM and programs you have installed of course.
4. Honestly they are all freaking great. The aosp roms. You do the answer to number one and you can find out. DU is my fav @ this moment. Followed by beanstalk.
5. Go to mobile networks make sure your network mode is set to cdma +lte/evdo.
6. Answer 1.
7. You don't really want to wipe the entire internal SD card. Sounds good when you think it might screw you if you did it.
Sent from my Nexus 7 using xda app-developers app
Mightycaptain said:
Wow that's a lot. Let's see if we can get you answers.
1. Switch recoveries to twrp 2.5.0.2. I can't stress the importance of the particular version enough. There are others. This is absolutely the most stable. It's what the devs use. I think then your cm issue will be resolved.
Correct way to wipe with twrp.
1.wipe - >factory reset.
2. Advanced wipe - >check system, data, davlik, cache then wipe.
3. The go back to main screen and install rom.
2. Answered by answer one. Lots of people have lots of opinions about the various recoveries. All I can tell you is this is what all the devs use for their recovery. Can't argue with that.
3. Reserved space. It might say you have 16 gigs but a good size chunk is taking merely by formatting. Then the ROM and programs you have installed of course.
4. Honestly they are all freaking great. The aosp roms. You do the answer to number one and you can find out. DU is my fav @ this moment. Followed by beanstalk.
5. Go to mobile networks make sure your network mode is set to cdma +lte/evdo.
6. Answer 1.
7. You don't really want to wipe the entire internal SD card. Sounds good when you think it might screw you if you did it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response Mightycaptain! I used CWM as my first ever recovery and am kinda pressed on it, which is why I use it, but I have no issues going to TWRP if that means fixing my issues. Can you elaborate on how to install TWRP in place of my current CWM? I'll do some Googling in the meantime to try to find the answer myself. (I haven't done any flashing or rooting stuff since I got the phone in May!!)
Thanks for your answer in #5. Fixed the issue I was having.
My reason for wanting to wipe the entire internal SD card is there are still files, folders, logs and backups from when I had my previous ROM. I'm having issues restoring my nandroid backup from the night of the 7th so is it at all possible for me to salvage some of my settings, apps and file backups from those existing files? Once I fix my nandroid, I'm going to keep the nandroid backup in a safe place and I ideally want to have a completely clean phone to start from: That means getting rid of all those old files and other nonsense from before. Is this a possibility?
I'm going to spend my time today trying to extract data from my nandroid backups using ROM Toolbox Pro. If that doesn't work, I have a nandroid backup from the 31st that has 99% of the stuff I need so I'll try to restore that. If THAT doesn't work, then I'm going to cry myself to sleep while trying to remember all of my contacts
Wish me luck, and hopefully I can get some answers to my last few questions!
Thanks,
Opethfan89
opethfan89 said:
Thanks for your response Mightycaptain! I used CWM as my first ever recovery and am kinda pressed on it, which is why I use it, but I have no issues going to TWRP if that means fixing my issues. Can you elaborate on how to install TWRP in place of my current CWM? I'll do some Googling in the meantime to try to find the answer myself. (I haven't done any flashing or rooting stuff since I got the phone in May!!)
Thanks for your answer in #5. Fixed the issue I was having.
My reason for wanting to wipe the entire internal SD card is there are still files, folders, logs and backups from when I had my previous ROM. I'm having issues restoring my nandroid backup from the night of the 7th so is it at all possible for me to salvage some of my settings, apps and file backups from those existing files? Once I fix my nandroid, I'm going to keep the nandroid backup in a safe place and I ideally want to have a completely clean phone to start from: That means getting rid of all those old files and other nonsense from before. Is this a possibility?
I'm going to spend my time today trying to extract data from my nandroid backups using ROM Toolbox Pro. If that doesn't work, I have a nandroid backup from the 31st that has 99% of the stuff I need so I'll try to restore that. If THAT doesn't work, then I'm going to cry myself to sleep while trying to remember all of my contacts
Wish me luck, and hopefully I can get some answers to my last few questions!
Thanks,
Opethfan89
Click to expand...
Click to collapse
Check my post here for twrp 2.5.0.2.
http://forum.xda-developers.com/showthread.php?p=47275165
You can flash it in your current recovery. It overwrites CWM. I would make sure you have a flashable for CWM just in case you need to go back for some reason. Also the backups between those 2 recoveries are not compatible. But I would nandroid with CWM before flashing twrp. I would also change were you recovery is pointing to for storage to the external SD if you haven't already. After you have cut your current backup and past it there. You can use rom toolbox pro to back up your contacts and restore it once you flash a new ROM.
Now as good advice going forward I would add your contacts to your Google account. That way when you flash new stuff or drop your phone in the toilet as soon as you add your Google account to the phone all those contacts will automatically download. But it is always a good idea to use tibu or rom toolbox pro to back up all your apps and seeing and use that after flashing roms to restore apps and settings.
But honestly I'd nandroid, move my contacts to Google, make app backups. Flash twrp. Then start flashing roms. You could be doing it in an hour. After you flash twrp make another nandroid so you have a twrp compatible backup. Then in a day or so of you are happy with everything delete the CWM backups for space.
Edit: as to extracting things from your current nandroid. Not sure if that is possible for one thing it is compressed not sure how that would work unless you are doing a full restore.
Also for future reference with TWRP. When restoring nandroid wipe like your flashing a new rom before restoring.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Check my post here for twrp 2.5.0.2.
http://forum.xda-developers.com/showthread.php?p=47275165
You can flash it in your current recovery. It overwrites CWM. I would make sure you have a flashable for CWM just in case you need to go back for some reason. Also the backups between those 2 recoveries are not compatible. But I would nandroid with CWM before flashing twrp. I would also change were you recovery is pointing to for storage to the external SD if you haven't already. After you have cut your current backup and past it there. You can use rom toolbox pro to back up your contacts and restore it once you flash a new ROM.
Now as good advice going forward I would add your contacts to your Google account. That way when you flash new stuff or drop your phone in the toilet as soon as you add your Google account to the phone all those contacts will automatically download. But it is always a good idea to use tibu or rom toolbox pro to back up all your apps and seeing and use that after flashing roms to restore apps and settings.
But honestly I'd nandroid, move my contacts to Google, make app backups. Flash twrp. Then start flashing roms. You could be doing it in an hour. After you flash twrp make another nandroid so you have a twrp compatible backup. Then in a day or so of you are happy with everything delete the CWM backups for space.
Edit: as to extracting things from your current nandroid. Not sure if that is possible for one thing it is compressed not sure how that would work unless you are doing a full restore.
Also for future reference with TWRP. When restoring nandroid wipe like your flashing a new rom before restoring.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks again for your quick response!! I'm glad I checked this first, because I'm in my ROM Toolbox app atm and it has an option to let me install TWRP 2.5.0.2 from within the app itself. Should I do it this way?
I will be adding all contacts to Google from now on. Unfortunately I saved all my stuff to my Verizon backup assistant so I just need one last shot at my phone to save all those contacts (manually, if I must) and be able to enter them onto the new ROM.
By "flash it in your current recovery" I assume you mean download the .zip, place it on my internal /sdcard, and then "flash" it just like I would flash a ROM, right?
I'm sure I have a "flashable" for CWM somewhere but like I said, I haven't done any of this stuff on this phone since I first bought it, and things have changed so much with everyone having OTA's and being locked out that I'm not sure what process is the same or what has changed. I can't afford to lose this phone so I'm hesitant to go balls to the wall to try things.
I will try the things you've listed here. Seems like a nandroid + TiBu + Google Contacts is my best bet to get up and running each time I decide to try a new ROM.
Thanks again!
opethfan89 said:
Hey thanks again for your quick response!! I'm glad I checked this first, because I'm in my ROM Toolbox app atm and it has an option to let me install TWRP 2.5.0.2 from within the app itself. Should I do it this way?
I will be adding all contacts to Google from now on. Unfortunately I saved all my stuff to my Verizon backup assistant so I just need one last shot at my phone to save all those contacts (manually, if I must) and be able to enter them onto the new ROM.
By "flash it in your current recovery" I assume you mean download the .zip, place it on my internal /sdcard, and then "flash" it just like I would flash a ROM, right?
I'm sure I have a "flashable" for CWM somewhere but like I said, I haven't done any of this stuff on this phone since I first bought it, and things have changed so much with everyone having OTA's and being locked out that I'm not sure what process is the same or what has changed. I can't afford to lose this phone so I'm hesitant to go balls to the wall to try things.
I will try the things you've listed here. Seems like a nandroid + TiBu + Google Contacts is my best bet to get up and running each time I decide to try a new ROM.
Thanks again!
Click to expand...
Click to collapse
Understand the hesitancy completely. But with nodding comes risk. It is always about whether you can accept the worst possible outcome.
Rom toolbox pro flashing recovery? I don't know never tried it.
Yes I would download the recovery. Leave it on SD card reboot to recovery and flash like a rom.
Yes nandroid tibu and saving your contacts to Google is the quickest way to get up and running again.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Understand the hesitancy completely. But with nodding comes risk. It is always about whether you can accept the worst possible outcome.
Rom toolbox pro flashing recovery? I don't know never tried it.
Yes I would download the recovery. Leave it on SD card reboot to recovery and flash like a rom.
Yes nandroid tibu and saving your contacts to Google is the quickest way to get up and running again.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Mighty, just wanted to report that flashing TWRP 2.5.0.2 from within ROM Toolbox Pro worked like a charm. I'm on TWRP as we speak.
Thank you so much for your responses. If anyone else has anything to add, or a different response to my questions, please do so! In the meantime, I'm going to try to figure out how to get my nandroid backup working...
Cheers!
*EDIT* Made a backup with TWRP (whose interface is bloody phenomenal, btw), flashed CWM and its working like a charm!! Going to try the st0ckdr0id one as well. Still working on getting that nandroid working so I can recover my stuff and get to customizing!