Related
The Situation:
I a currently stuck in ClockworkMod Recovery with no backups, no usable flashable ROMs, no ROM installed, a screwed up internal SD, and virtually no way to use the ADB or ODIN in Download, because my phone rarely, if ever, recognizes USB cords for anything but charging (This is a hardware, not software issue. It persists from ROM to ROM.)
Thoughts?
Additional Info
There's a lot, so I will be clear, as concise as possible, and will try to remember everything.
You might ask, "How did this happen?" or even "WTF?"
These are the steps I've taken:
Originally, I used OCLF for rooting + ext2 lag fix, followed by Team Whiskey's latest Bionix ROM. I hadn't removed the lag fix as I was told it should not matter. I was having a multitude of problems, so I wished to revert to Stock. When a standard nandroid restore didn't work, I searched and learned that flashing back to J12 should let my nandroid restore work. This did NOT work, however, and, once again, I was stuck in the boot sequence. I re-flashed the Bionix ROM to see if I could just live with it, and, no, I couldn't. I looked some more and found that, given I could flash a JFD or J16 (I believe) image, I could then perform a restore, then install a 2.1 kernel. I found the image and flashed it. THAT worked, but the nandroid was still refusing to cooperate.
Today, I flashed Team Whiskey's Obsidian V4.2 ULF Kernel ROM, succeeded, and found that my internal SD partition that hosts apps existed, but was 0.00KB. I thought about installing App2SD, but I decided I had too much room internally to want to deal with that. I tried to add a partition via CWM ROM Manager, but did not take into consideration the fact that it would need a ROM to flash once it had wiped and partitioned. I'm not sure how that partition creator is supposed to work, because it wipes the drive that the ROM is on. At that point, I somehow managed to get back in business by formatting w/ backup.
I tried flashing Obsidian V4.2 w/o the lag fixed kernel, thinking this was the issue with my internal partition system, but I never found out because install, post-wipe, failed at line 11. I could not turn the phone back on because it had no complete install, and nandroid was still not restoring, so I went through Recovery and factory reset, wiped cache, tried mounting and unmounting different file systems, including the sd-ext which refuses to mount, citing "E:INFO is WRONG Error mounting SDEXT:!".
I've installed Superuser, messed with the Lagfix and Tweak options, and reset default permissions in the ULF Kernel Menu. All to the effect of allowing the ROM flash to progress to line 85 before failing. I can't remember the errors it gave, and can't flash again, because, in my frenzy, I formatted the system, data, cache, and sdcard. I still have a nandroid available, but it has an md5 sum mismatch. There are three more viable ROMs on my external SD card, but I have no way of moving them to the internal, and the "install zip from sd card" menu won't access the CWM backup folder or the external because it says there aren't any there, which isn't true.
I am completely at a loss as to what to do. Is there any way to move files from external -> internal sd in recovery?
ANY help that isn't "You're screwed" would be appreciated.
Semi_Interested said:
The Situation:
I a currently stuck in ClockworkMod Recovery with no backups, no usable flashable ROMs, no ROM installed, a screwed up internal SD, and virtually no way to use the ADB or ODIN in Download, because my phone rarely, if ever, recognizes USB cords for anything but charging (This is a hardware, not software issue. It persists from ROM to ROM.)
Thoughts?
Click to expand...
Click to collapse
Email me [email protected]
Sent from my SGH-T959 using XDA App
Semi_Interested said:
There's a lot, so I will be clear, as concise as possible, and will try to remember everything.
You might ask, "How did this happen?" or even "WTF?"
These are the steps I've taken:
Originally, I used OCLF for rooting + ext2 lag fix, followed by Team Whiskey's latest Bionix ROM. I hadn't removed the lag fix as I was told it should not matter. I was having a multitude of problems, so I wished to revert to Stock. When a standard nandroid restore didn't work, I searched and learned that flashing back to J12 should let my nandroid restore work. This did NOT work, however, and, once again, I was stuck in the boot sequence. I re-flashed the Bionix ROM to see if I could just live with it, and, no, I couldn't. I looked some more and found that, given I could flash a JFD or J16 (I believe) image, I could then perform a restore, then install a 2.1 kernel. I found the image and flashed it. THAT worked, but the nandroid was still refusing to cooperate.
Today, I flashed Team Whiskey's Obsidian V4.2 ULF Kernel ROM, succeeded, and found that my internal SD partition that hosts apps existed, but was 0.00KB. I thought about installing App2SD, but I decided I had too much room internally to want to deal with that. I tried to add a partition via CWM ROM Manager, but did not take into consideration the fact that it would need a ROM to flash once it had wiped and partitioned. I'm not sure how that partition creator is supposed to work, because it wipes the drive that the ROM is on. At that point, I somehow managed to get back in business by formatting w/ backup.
I tried flashing Obsidian V4.2 w/o the lag fixed kernel, thinking this was the issue with my internal partition system, but I never found out because install, post-wipe, failed at line 11. I could not turn the phone back on because it had no complete install, and nandroid was still not restoring, so I went through Recovery and factory reset, wiped cache, tried mounting and unmounting different file systems, including the sd-ext which refuses to mount, citing "E:INFO is WRONG Error mounting SDEXT:!".
I've installed Superuser, messed with the Lagfix and Tweak options, and reset default permissions in the ULF Kernel Menu. All to the effect of allowing the ROM flash to progress to line 85 before failing. I can't remember the errors it gave, and can't flash again, because, in my frenzy, I formatted the system, data, cache, and sdcard. I still have a nandroid available, but it has an md5 sum mismatch. There are three more viable ROMs on my external SD card, but I have no way of moving them to the internal, and the "install zip from sd card" menu won't access the CWM backup folder or the external because it says there aren't any there, which isn't true.
I am completely at a loss as to what to do. Is there any way to move files from external -> internal sd in recovery?
ANY help that isn't "You're screwed" would be appreciated.
Click to expand...
Click to collapse
Well, adb would be able to move files from external sd card to the internal one but if you don't know how to use it then Odin might be simpler. I'll pm you some instructions but if you cannot get your phone to be recognized in Odin because of USB issues then I'm not sure how to help.
recently i have been having issues with my games and apps that are installed in my phone.........all of them say ether "application not installed" or the force close messege while the day before all was ok... so what can cause this issue
Have you made any changes to you phone recently, tweaked, anything...? Or did it just happen suddenly?
ivanrcks95 said:
recently i have been having issues with my games and apps that are installed in my phone.........all of them say ether "application not installed" or the force close messege while the day before all was ok... so what can cause this issue
Click to expand...
Click to collapse
Hi @ivanrcks95...
After reading your post I sat & scratched my head for a while...
1. do you have any apps etc moved-out to sd...? If so, are there many & what app did you use to move them...?
2. Are you running any ram tweaks or partition managment tweaks...?
The reason I ask these questions is because I have seen this behaviour often when an "Ace" is switching back from USB data transfer mode to Internal & SD memory...
The status of your ram at this point can cause a severe lag with the mounting of the necessary partitions often returning the error messages that you describe... on occasion you will also get "Problem loading widgets" etc. If a particularly bad lag occurs then the data & partitions can become corrupted...
An easy cure to get things running again would be a complete wipe & restore from Nandroid backup (assuming that you have done one...?)... A selective nandroid restore would let you just repair the system partition, which I feel would be adequate.
Have you tried re-installing 1 or 2 apps...? if they install successfully then that tells us that the partition is now functioning but some of the data contained has become corrupt. If the apps fail to install then I think we can safely assume that the partition is corrupt...
Again the simple solution would be a nandroid restore... If you do not have this option then I would suggest the following... :
1. backup all data from your sd card where possible & reformat & partition using CWM 4 or 5 (if ya runnin CM7.2 then you "MUST" use CWM5)...(sd card partitions may be cause of issue)
2. complete a full wipe (system, cache, Dalvik), Wipe battery stats (Always do when installing a new rom so battery can correctly callibrate to new power requirments)...
3. Re-flash rom, modded kernel etc. (always check if system, data partitions need to be mounted before flash from CWM to prevent boot errors & wrong permission assignment)...
4. Re-boot phone after flash to check all is well... Then copy back to sd the backup that you made at the beginning...
You should now have a fully working phone again... Downside is that you may have to re-install ya apps etc...
Nandroid backup recovery...
======================
1. Follow step 1 of my guide above...
2. If doing a "selective" nandroid restore then wipe just the Dalvik cache then just select the needed files and restore them... If doing a "Complete" nandroid restore then do a complete wipe before restore...
3. Re-boot phone after restore to check all is well... Then copy back to sd the backup that you made at the beginning...
You should now have a fully working phone again...
!!! IMPORTANT !!!
==============
If after formatting & partitioning the sd card, CWM has trouble locating the Nandroid backup after you place it in root of sd card then do the following :
1. Open into "Root" of sd card
2. Create a folder called "clockworkmod" all lowercase letters...
3.Create within the above folder another folder called "backup" again all lowercase...
4. now place within this folder your nandroid backup...
5. unmount usb (assuming your phone is connected to pc for folder creation)...
6. now complete the nandroid recovery...(should go without a hitch unless the backup has been altered in any way (MD5 hash file check will fail if file is altered after creation)...
Hope this info is of help to you given that you did;nt really provide many details of your problem...
Stay Breezy n Be Lucky...
Pe"ACE"...
ok i am running my own ROM that i havent published but its a mix with cyanogen and ice cream sunday put into one( so some bits from each rom to make my own) well when i re-install apps they work but ive noticed as soon as i reboot my phone they force close again i can try to reinstall my rom and do a full wipe to solve this but all my apps are in my sd card so it could be that my sd card is a bit mest up or maybe ive mest something up with my rom
Hi all, I built my sdcard per: http://iamafanof.wordpress.com/2012/...r-nook-tablet/ (built by"Succulent")
My kids have two NT's. With two 16GB Sdcards, one class4 the other class 10. I know class4 is recommended, but one poster in forums said he's taken images of CM built on class4's and applied this image to class 10's in several cases and has had no problems. So I thought what the heck, can't hurt to try, so that's what I did (using Winimage). It booted fine 5 or 6 times for me, and I installed several APK's of games from Humble Bundle . I turned over the Nook to my little girl and she brought it back to me later showing she gets errors on boot, after swiping the lock symbol to unlock it. One is "Unfortunately, Talk has stopped". If you click OK on this, you get ""Unfortunately, Trebuchet has stopped". Clicking OK on this does nothing, it keeps popping up indefinitely. I don't know if the sdcard is hot pluggable (can be removed with power to the tablet), but she did admit to doing this. So I'm wondering if some corruption occurred to the CM build on the sdcard. Has anyone seen these errors? I could reflash it from the image I made off the class 4, but want to understand what happened so we don't run into it again. The funny thing is, I don't recall the startup wizard off the 1st class4 card prompting me with several screens regarding Google crap like it did on the 2nd card which was flashed from the same image. That was even after telling it I had no Google acct hoping it would leave me alone.
can anyone explain the boot menu you get when you press the N button? (I'm not including the faded selections) I'm wondering especially about the recovery options. Here's my menu:
INT BOOT ( I assume will boot to B&N native OS?)
INT RECOVERY ?
SDC RECOVERY ?
SDC BOOT (Iassume, boot to CM10 off sdcard?)
SDC ALTBOOT ?
START FASTBOOT ?
baytee said:
...
So my question is, can anyone explain the boot menu you get when you press the N button? (I'm not including the faded selections) I'm wondering especially about the recovery options. Here's my menu:
INT BOOT ( I assume will boot to B&N native OS?)
INT RECOVERY ?
SDC RECOVERY ?
SDC BOOT (Iassume, boot to CM10 off sdcard?)
SDC ALTBOOT ?
START FASTBOOT ?
Click to expand...
Click to collapse
Yes,
internal boot - boots Rom in emmc
Internal recovery - recovery in emmc
Sdcard boot - boots your sdcard Rom.
Sdcard recovery - boots sd card recovery ( keep recovery.img in root of sdcard for it to load recovery)
Sdcard altboot - alternate recovery ( not necessary, unless you want both cwm and twrp at same time)
Fastboot - fastboot mode , fastboot commands to flash .img file etc with this method .
As for your problem, try entering recovery, wipe cache and dalvik cache partition (I've done this on emmc version, never tried sdcard version of any Rom) this may solve the issue. If not try factory reset.
And removing sdcard while device is switched on is called hot swapping , hot plug is a CPU governor. Not sure if sdcard roms are hot swappable, but I think not.
Sent from my ST27i
Thanks.
emmc=internal nook memory I assume?
Oh, and...just to clarify, I haven't modified (rooted) my tablet. (you mention factory reset). I should mention that with the sdcard out, it boots B&N OS just fine.
And the part you say about wiping the two caches, so I should go into SD Card Recovery to do that? Once you get into it, you have various choices like the ones you mention? (I'd read that this choice was to backup your NT to sdcard). And please, I want to be very, very careful not to wipe out the B&N stock OS, so please, any detailed instructions you can give so I don't make that mistake, I'd greatly appreciate it. (I see so many posts on these forums about people bricking their Nook tablets it worries me.)
baytee said:
Thanks.
emmc=internal nook memory I assume?
Oh, and...just to clarify, I haven't modified (rooted) my tablet. (you mention factory reset). I should mention that with the sdcard out, it boots B&N OS just fine.
And the part you say about wiping the two caches, so I should go into SD Card Recovery to do that? I'd read that this choice was to backup your NT to sdcard. But once you get into it, you have various choices like the ones you mention? And please, I want to be very, very careful not to wipe out the B&N stock OS, so please, any detailed instructions you can give so I don't make that mistake, I'd greatly appreciate it. (I see so many posts on these forums about people bricking their Nook tablets it worries me.)
Click to expand...
Click to collapse
Um I don't know much about how it works for sdcard Rom. I've always only used emmc version. I guess if you were to enter recovery, it would access the stock cache partition by default , and we aren't trying to clear that.
Try this - use titanium backup (only talking about your sdcard Rom here, nothing to do with your stock) and in options, you may be able to wipe your cache or dalvik cache.
Or,
boot into your sdcard Rom, in settings > backup and restore > factory reset. This will delete all user data and return Rom to original Cm10 that you flashed on sdcard.
Or if it's only google talk and trebuchet launcher issue, install a new launcher (go launcher, adw etc) , then use titanium backup to uninstall trebuchet and talk.
Sent from my ST27i
From what I see, titanium backup is an android app. If I can't boot to Android (Trebuchet error loops as I said) I don't know how I can install this to do anything? Nor can I install another launcher or go into Settings as the error doesn't let you get any further.
I guess if there was a way to browse files/folders on the sdcard partitions on the sd to manually delete the cache files.....but if they're linux partitions (ext3 or4) you can't do that under windows...
baytee said:
From what I see, titanium backup is an android app. If I can't boot to Android (Trebuchet error loops as I said) I don't know how I can install this to do anything? Nor can I install another launcher or go into Settings as the error doesn't let you get any further.
I guess if there was a way to browse files/folders on the sdcard partitions on the sd to manually delete the cache files.....but if they're linux partitions (ext3 or4) you can't do that under windows...
Click to expand...
Click to collapse
In cwm, enter mounts and backup, then (if) you see /sdcard /cache, mount that and format that ONLY.
Do not format anything else as some options can brick device (Rom, bootdata, factory etc)
Wiping cache is safe (99%)
Again, I have never used sdcard Rom so I don't know what will show up in your recovery. But if you see something like sdcard cache, it can be cleared. If it doesn't specify sdcard, let us assume it refers to stock emmc.
Sent from my ST27i
How do I get into CWM?
baytee said:
How do I get into CWM?
Click to expand...
Click to collapse
Select SDC Recovery on the Cyanoboot boot menu -- see steps 7 & 8 of the post at http://forum.xda-developers.com/showthread.php?t=2061536.
If you want to backup the BN stock ROM just in case, see step 9.
digixmax said:
Select SDC Recovery on the Cyanoboot boot menu -- see steps 7 & 8 of the post at http://forum.xda-developers.com/showthread.php?t=2061536.
If you want to backup the BN stock ROM just in case, see step 9.
Click to expand...
Click to collapse
I chose sd recovery, chose Backup & Restore, then Backup. It started running right away. It said:
SD Card space free: 228MB
Backing up boot image
Backup of boot image completed
Backing up recovery image
Backup of recovery image completed
Backing up system
Error while making a backup image of /system!
I plug sdcard into PC card reader and the FAT partition has 0 bytes free. So, appears it ran out of space. I saw your comment about 600MB space being needed. So I'm redoing the partitions now.
baytee said:
I chose sd recovery, chose Backup & Restore, then Backup. It started running right away. It said:
SD Card space free: 228MB
Backing up boot image
Backup of boot image completed
Backing up recovery image
Backup of recovery image completed
Backing up system
Error while making a backup image of /system!
I plug sdcard into PC card reader and the FAT partition has 0 bytes free. So, appears it ran out of space. I saw your comment about 600MB space being needed. So I'm redoing the partitions now.
Click to expand...
Click to collapse
Why backing up now when it's not working? Fix your issue, then make a backup. So the next time there's a problem you can restore to working condition.
Sent from my ST27i
Well, backing up, I think, was a good suggestion by Digimax. So I'm glad I did it. and now i know how to do it for future. Just in case anything EVER goes wrong, I'll always have that image now on my pc. Bad thing was, apparently B&N nook OS apparently keeps lots of APKs around after installing them. I had to make my 1st fat32 partition over 2GB for the entire backup to process without running out of space. backup size=1.6gb
I ran into lost chains - convert to cluster msgs trying to delete the folder of the first failed backup, but it never would delete even after a chkdsk, so I formatted the card and put the original image back onto it, adjusted the partitions, and then ran into a new probem.....the Cyanomod spinning logo never stopping spinning so it won't boot up. So I give up. I don't know if it's that it's a class 10 card that all these problems are happening. barring any other suggestions, I guess I'll make sure the other NT we have runs stable for a few weeks and if so I'll order another class 4 like that one has.
baytee said:
Well, backing up, I think, was a good suggestion by Digimax. So I'm glad I did it. and now i know how to do it for future. Just in case anything EVER goes wrong, I'll always have that image now on my pc. Bad thing was, apparently B&N nook OS apparently keeps lots of APKs around after installing them. I had to make my 1st fat32 partition over 2GB for the entire backup to process without running out of space. backup size=1.6gb
I ran into lost chains - convert to cluster msgs trying to delete the folder of the first failed backup, but it never would delete even after a chkdsk, so I formatted the card and put the original image back onto it, adjusted the partitions, and then ran into a new probem.....the Cyanomod spinning logo never stopping spinning so it won't boot up. So I give up. I don't know if it's that it's a class 10 card that all these problems are happening. barring any other suggestions, I guess I'll make sure the other NT we have runs stable for a few weeks and if so I'll order another class 4 like that one has.
Click to expand...
Click to collapse
I don't know about your bootloop issue, but I don't think it's a sdcard class issue.
Anyhow, now that you have stock backup, aren't you going to consider flashing cm10 internally? Do you actually use stock?
Sent from my ST27i
I'm a little leery of it, at least while it's under warranty. I don't know how reliable recovery is.? Besides, my daughter wasn't thrilled with it being down for several days with me fussing with it and asked if she could have her "B&N boot" back I admit It is a bit of a pain having to pull it out of it's case, lift the flap, pop-in or out the sdcard to switch between them. (& also to have to remember to always turn it off b4 removing/inserting)
I may do it in the future though. Thanks for the help
FWIW, you don't have to actually remove the card to boot into stock. Just reboot, hold "n" to get into Cyaonoboot menu and choos "int boot" or something like that, and it will boot to stock with the sd-card still inserted.
Great, thanks for that tip!
Card died
I think many of these symptoms could have been caused by a dying card. It did have a corruption error once, and then it finally completely died. Just for anyone else that runs into these.
baytee said:
Well, backing up, I think, was a good suggestion by Digimax. So I'm glad I did it. and now i know how to do it for future. Just in case anything EVER goes wrong, I'll always have that image now on my pc. Bad thing was, apparently B&N nook OS apparently keeps lots of APKs around after installing them. I had to make my 1st fat32 partition over 2GB for the entire backup to process without running out of space. backup size=1.6gb
...
Click to expand...
Click to collapse
FWIW, /cache does not need to be backed up, which should help reduce the backup space requirement.
Hi, I was having some issues on my Nook Tablet 16gb, so I thought I would format everything (actually format every single item 3x) with the goal of having a fresh boot without issues. But then when I installed Slim Rom or any other ROM it installs them and when I hit "reboot system now" on CWM after installing the NEW Rom, it tries to load and goes to the Big N shape boot animation and then back to CWM.
What would you suggest I do?
Thanks a lot!
---
The items I wiped (each 3 times!): ROM, bootdata, factory, system, cache, emmc, data, sdcard, data1.
somerandomname said:
Hi, I was having some issues on my Nook Tablet 16gb, so I thought I would format everything (actually format every single item 3x) with the goal of having a fresh boot without issues. But then when I installed Slim Rom or any other ROM it installs them and when I hit "reboot system now" on CWM after installing the NEW Rom, it tries to load and goes to the Big N shape boot animation and then back to CWM.
What would you suggest I do?
Thanks a lot!
---
The items I wiped (each 3 times!): ROM, bootdata, factory, system, cache, emmc, data, sdcard, data1.
Click to expand...
Click to collapse
Don't press "reboot system now" when you want to exit recovery. Power down system then power it on again. It should boot just fine.
somerandomname said:
Hi, I was having some issues on my Nook Tablet 16gb, so I thought I would format everything (actually format every single item 3x) with the goal of having a fresh boot without issues. But then when I installed Slim Rom or any other ROM it installs them and when I hit "reboot system now" on CWM after installing the NEW Rom, it tries to load and goes to the Big N shape boot animation and then back to CWM.
What would you suggest I do?
Thanks a lot!
---
The items I wiped (each 3 times!): ROM, bootdata, factory, system, cache, emmc, data, sdcard, data1.
Click to expand...
Click to collapse
Your boot-loop problem might be due to invalid or missing data in /bootdata resulted from your having wiped this partition, see http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1. You can try restoring the data by flashing flashable_fix_bootloop.zip from http://goo.im/devs/succulent/acclaim/recovery.
datallboy said:
Don't press "reboot system now" when you want to exit recovery. Power down system then power it on again. It should boot just fine.
Click to expand...
Click to collapse
I tried that didn't work, thanks.
Sent from my SGH-T999 using Tapatalk 2
Wiping ROM seems to have the effect of triggering a recovery every boot, which if you had the stock recovery should recover all the device info stored there. I had to use a repart.img sdcard which loaded stock 1.4.2 or 1.4.3 (Search for files and guides). Then I used a CWM sdcard and put custom recovery and ROM back on.
Sent from my Barnes & Noble Nook Tablet using xda premium
digixmax said:
Your boot-loop problem might be due to invalid or missing data in /bootdata resulted from your having wiped this partition, see http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1. You can try restoring the data by flashing flashable_fix_bootloop.zip from http://goo.im/devs/succulent/acclaim/recovery.
Click to expand...
Click to collapse
This did not work either. thanks
somerandomname said:
This did not work either. thanks
Click to expand...
Click to collapse
The next likely cause of your problem is missing factory-installed device data (e.g., WiFi MAC address, security encryption keys, etc.) that are stored in /rom and /factory partitions which you stated in the OP you had wiped. Unfortunately I am not aware of any way to recover this original set of individual device specific data.
Did you try the stock files like I said before? That got my info back
Sent from my Barnes & Noble Nook Tablet on CM 10.1 using xda premium
dejello said:
Did you try the stock files like I said before? That got my info back
Sent from my Barnes & Noble Nook Tablet on CM 10.1 using xda premium
Click to expand...
Click to collapse
Yeah I was able to use the thread by Adam to redo my tablet with the normal files for Rom through a SD card boot since the touch was not working.
Thank you, this was a great learning experience in my 5 years of playing around first time to cause a brick...
Sent from my SGH-T999 using Tapatalk 2
I'm glad you got it figured out this droid charge i'm on right now used to brick every time i flashed, then started working right one time I've just learned to take it easy and see about fixing things
Sent from my SCH-I510 using xda app-developers app
CWM Bootloop...
Hello all!
It seems I've gotten myself into a bit of trouble with my Nook Tablet. I had been running CM7 for quite some time and finally upgraded to CM10. Very nice! However I landed myself in a CWM boot loop after about a week and have not been able to recover.
First, I attempted to recover back to BN Stock, not knowing that it would not replace CWM with stock recovery. I still have CWM and half of a stock installation (repart.img from bn_142_factory_recovery.zip). From what I understand, the stock BN software is trying to boot to recovery to complete the install, although it was in bootloop before that attempt was made.
Since then, I have tried flashable_fix_bootloop.zip as well as cwm_6.0.2.9_acclaim_recovery_sdcard.img to no avail. I fear that I may have made the mistake of formatting too many things as mentioned at the top of this thread to get into myself here in the first place. What is my next step?
Much appreciated!
-byrd
You could try what I tell the poster in the topic "At wits end". In the beginning of the topic I described an easy way to make a notable COM card. You can then jump to the end of the topic and try to use my backup file. I will remove access to that file later today and I don't know if it will work at all but at least it's worth a try.
asawi said:
You could try what I tell the poster in the topic "At wits end". In the beginning of the topic I described an easy way to make a notable COM card. You can then jump to the end of the topic and try to use my backup file. I will remove access to that file later today and I don't know if it will work at all but at least it's worth a try.
Click to expand...
Click to collapse
Thank you for your reply, asawi!
I've begun the download. From what I understand, this will give me a bootable MicroSD into CM10. If that is correct and it boots as it should, I can then install this image as firmware in some fashion or at least be able to repair the damage done so that I can reinstall CM10?
[Warranty is of no concern. I bought this Nook Tablet in used condition quite some time ago with intent to use CM as primary OS, hence the use of CM7 for well over a year.]
-byrd
If, this works (and that's a HUGE IF), twill leave you with a tablet running CM 1O from internal memory.
It is a two step thing though with two big downloads. The one from Iamafanof will make you a bootable CM10 card. Either you can use it as it's intended, or just use it to get into CWM recovery where you can go to backup and restore and try to restore the backup I made. Unzip my file first, like I tell the other poster.
Edit:I realized I had goofed up when posting the first backup. I have now put up another download of the whole "clockworkmod" folder in my Dropbox. Link in the "at wits end" topic. but I will only leave it up for a very limited time.
asawi said:
If, this works (and that's a HUGE IF), twill leave you with a tablet running CM 1O from internal memory.
It is a two step thing though with two big downloads. The one from Iamafanof will make you a bootable CM10 card. Either you can use it as it's intended, or just use it to get into CWM recovery where you can go to backup and restore and try to restore the backup I made. Unzip my file first, like I tell the other poster.
Edit:I realized I had goofed up when posting the first backup. I have now put up another download of the whole "clockworkmod" folder in my Dropbox. Link in the "at wits end" topic. but I will only leave it up for a very limited time.
Click to expand...
Click to collapse
Using Cyanoboot from the bootable card, I am able to boot into SDC RECOVERY. From there I swap the SD card for another containing your your backup folder, navigate to 'backup and restore'/'restore'/'2013-09-17.16.18.21'. Restore process begins okay, but fails with "Error while restoring /system!"
I then went to 'advanced restore' and attempted restoring /boot, /system, /data, /cache, and /sd-ext individually with these results:
/boot = Restore Complete
/system = Error
/data = Error
/cache = Error
/sd-ext = sd-ext.img not found, Skipping restore...
-byrd
byrdeth said:
Using Cyanoboot from the bootable card, I am able to boot into SDC RECOVERY. From there I swap the SD card for another containing your your backup folder, navigate to 'backup and restore'/'restore'/'2013-09-17.16.18.21'. Restore process begins okay, but fails with "Error while restoring /system!"
I then went to 'advanced restore' and attempted restoring /boot, /system, /data, /cache, and /sd-ext individually with these results:
/boot = Restore Complete
/system = Error
/data = Error
/cache = Error
/sd-ext = sd-ext.img not found, Skipping restore...
-byrd
Click to expand...
Click to collapse
If /boot was successfully restored, that's what matters the most (please, tell me you did NOT erase /rom, because if you did, you're in a really bad situation). You don't need to restore asawi's FULL backup. If the /boot partition is functioning normally now, you should be able to boot into your internally flashed CWM, wipe data/factory reset, wipe dalvik cache, and wipe system, then FLASH the ROM and gapps. You should not be experiencing the bootloops anymore (make sure to take out the SD card BEFORE rebooting to internal CWM).
Hi,
im quite new to rooting and custom roms.
I have rooted (ALLINONE) my device with the S3 ToolKit (http://forum.xda-developers.com/showthread.php?t=1703488)
My device had stock rom and was encrypted. I performed a factory reset from the stock rom (after a nandroid backup from the toolkit.
But the phone failed and booted into TWRP. When i try to wipe Dalvik Cache it sais failed..
I get "cannot mount internal storage" in the logs.
What sould i do?
I want to install the Paranoid Android ROM. But for now, whatever goes. Is there always an possibility to fix the phone as long as i get into the TWRP menu, or can it be permanently bricked now?
Download mode yes no ???
jje
Yes im am able to open download mode. thanks for your quick reply
Could i try to install a ROM from a external card without wiping dalvik? I was able to wipe "cache", but not factory reset or dalvik. havent tried anything else yet.
To my knowledge, you can only access encrypted data with the instance of the ROM you encrypted it with.
I would expect you'd have to decrypt fully before wiping and flashing.
I may be wrong but there is a chance there's nothing you can do to get the data back :/
Everything possibly needs to be formatted.
I just took "format data" - it worked just to confirm i was on the right track, i tried dalvik again - it worked! OH YES. going forward
Whatever doesnt kill your phone makes you stronger, or something But what should i do now..?
sponsen said:
what should i do now..?
Click to expand...
Click to collapse
It depends where you want to be...
rootSU said:
It depends where you want to be...
Click to expand...
Click to collapse
I want to flash the Paranoid Android ROM.
I have downloaded the ROM + gapps from as stated in this link: (remote the [DOT] and replace it with a real dot) tothemobile[DOT]com/install-paranoidandroid-4-2-2-jelly-bean-custom-rom-on-galaxy-s3
but im not sure what steps i should do now. The toolkit dosnt have a feature covering my situation as far as i can see (a formatted phone), since the toolkit want me to boot it as normal to start the flash procedure - if i havent misunderstood this totally
sponsen said:
I want to flash the Paranoid Android ROM.
I have downloaded the ROM + gapps from as stated in this link: (remote the [DOT] and replace it with a real dot) tothemobile[DOT]com/install-paranoidandroid-4-2-2-jelly-bean-custom-rom-on-galaxy-s3
but im not sure what steps i should do now. The toolkit dosnt have a feature covering my situation as far as i can see (a formatted phone), since the toolkit want me to boot it as normal to start the flash procedure - if i havent misunderstood this totally
Click to expand...
Click to collapse
You don't really need the toolkit. Plus, it's really good to learn how to do things manually, in case you get in situations like this.
Sol exactly what state is the phone in?
What recovery has the phone got?
Does the phone now boot?
Is it wiped and internal storage works?
Thanks for your help - really appreciate it
Im not sure how i can describe the phones state more than i have now used "format data" in the TWRP recovery screen, the device is listing in the toolkit and im able to go into download mode. I dont have an external card for the phone now, but if its critical for the ongoing progress, ill get a hold of one.
EDIT:
When i hit "Install" in TWRP i am able to browse the internal memory. I can see:
cache
data
dev
efs
etc
external_sd
extSdCard
preload
proc
res
root
sbin
sdcard
sys
system
tmp
sponsen said:
Thanks for your help - really appreciate it
Im not sure how i can describe the phones state more than i have now used "format data" in the TWRP recovery screen, the device is listing in the toolkit and im able to go into download mode. I dont have an external card for the phone now, but if its critical for the ongoing progress, ill get a hold of one.
EDIT:
When i hit "Install" in TWRP i am able to browse the internal memory. I can see:
cache
data
dev
efs
etc
external_sd
extSdCard
preload
proc
res
root
sbin
sdcard
sys
system
tmp
Click to expand...
Click to collapse
Have a read of the "sticky roll-up thread" in general where there are guides for flashing etc
im not familiar with twrp. usually android sees /extSdCard as your removable sd. But recoveries usually use external_sd for the same location.
Essentially you put the zip on your sd and install via recovery. Have a look through those guides. I cant really help withy your recovery though as i dont know it.
I believe that the case is resloved!
To users experiencing that wipes/factory reset fails on a device that have/had encrypted data, you must "format data" and then mount a SD card with the desired ROM and gapps. If you dont have the option of a external SD - i dont know what you have to do - but im sure the internet do