Related
I have a problems with CWM: it has in Advanced menu Format EX partition option
I randomly used that
I chose random values there for external and swap
so, formatted!
but I'm not sure what was formatted, because external sdcard wasn't installed at this time.
After that, I decided to reflash the phone using RSD, but got failed to boot 4
I'm still able to boot the phone after I flash nopudding sbf
Does anybody know, which values should I set in the advanced -> format external sdcard, and please if you can suggest, can it be done by other way to find solution of that problem
thank you very much all. Thanks to Oleg for helping to translate from Russian into English)) you fu....
please help.
http://forum.xda-developers.com/showpost.php?p=23865414&postcount=6
This post describes what I did. but I can not write there.
PavelPerm said:
I have a problems with CWM: it has in Advanced menu Format EX partition option
I randomly used that
I chose random values there for external and swap
so, formatted!
but I'm not sure what was formatted, because external sdcard wasn't installed at this time.
After that, I decided to reflash the phone using RSD, but got failed to boot 4
I'm still able to boot the phone after I flash nopudding sbf
Does anybody know, which values should I set in the advanced -> format external sdcard, and please if you can suggest, can it be done by other way to find solution of that problem
thank you very much all. Thanks to Oleg for helping to translate from Russian into English)) you fu....
Click to expand...
Click to collapse
Did you make a backup? If so, restore that and advance restore your only boot.img and the PDS. I didn't have any problems SBFing to to stock. I think Loki or someone mentioned to NOT SBF the nopudding4u it will give the failed to boot 4 screen you described.
PDS section I have from another phone. I recorded it on your phone. but then, after loading the SBF, the error number 4 left boot.
This menu sector
If you selected to partition your external SD card while it was not in, it should not have done anything. It would have given you this near the of the log. "err: /dev/block/mmcblk1 does not exist," meaning it shouldn'taffect your phone.
there is not formatted EX partition and format a date. see a screenshot
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
I have a Nook Tablet 16GB. It won't even power on to the "n" logo screen unless there is a CWM SD Boot card installed. I get mount errors once inside CWM.
E:Can't mount / cache/recovery/command/
E:Can't mount / cache/recovery/log/
E:Can't open / cache/recovery/log/
E:Can't mount / cache/recovery/last_log/
E:Can't open / cache/recovery/last_log/
I've tried the Factory Restore (repart.img) and it runs through and tells me the device will shutdown in 5 seconds. (The other times I've used this it sits at a green check mark until I shut it down manually) This doesn't resolve the issue or make any changes at all.
I've tried Adam's Ubuntu method and the device boots to the SD card but sits at a blank screen after a few seconds and does nothing, even when left on over night. This doesn't resolve the issue or make any changes at all either.
I can connect to the device in ADB and the plan was to use parted to fix some partitions using Veronica's methods, but when I run the parted /dev/block/mmcblk0 print command no partitions are found at all on the device. I'm never prompted to fix any partitions either. The only thing it sees in the ext sd card partition. In the past when I've done this it shows 11 partitions with some details. This time it shows nothing. I am unable to find any information anywhere as to what to do next.
It is as though the internal SD Card (memory/hard drive whatever you call it) isn't working or detected by the system any longer.
Does anyone have any recommendations on what to try next? Please help!
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
digixmax said:
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
Click to expand...
Click to collapse
I made an SDCard using Succelent's repo and was able to boot to the Cyanoboot Bootloader but a few seconds later it just went to a blank screen. I rebooted and could get into recovery by holding the "n" button and selecting that. When I select to boot from SDC it just goes to Bootloader and then goes blank. It never boots into the OS.
I never mess around with partitions and I'm not sure how this thing got this way. I purchased it from eBay as a tablet for my daughter. It did say the device was bricked but that the hardware was okay. I've seen bricked devices in the past and the repart.img (Factory Reset) has always resolved the problem. I have a Nook Tablet that my son has been using so I've become pretty familiar with the basics of rooting, loading CWM, TWRP, Cyanogenmod, etc. But I've never seen it were I get mounting errors inside of CWM and am unable to flash anything. It won't even mount the external SDCard once inside CWM.
Not sure what to do and I hate to give up on this. Any help would be greatly appreciated.
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
This happened to me last year. There is a post in development section about fixing partition table by So****e. It's the last resort, but worked for me.Also, Adam Outlers Ubuntu method loses your serial number, gone forever. Good luck
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
DEjaVu
Happened to my first nookT not to long ago....It died but the best advice I can give has already been given try not to erase more stuff. Digimax helped me not to long ago. Make sure you format your sdcards correctly and if you can flash a recovery or boot into it you should be able to use one of Succulents cards. Good luck
digixmax said:
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
Click to expand...
Click to collapse
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found. I also tried wiping my cache partition again from inside cwm, but no luck. Still getting the mount errors.
I believe the real issue is that my device doesn't see /dev/block/mmcblk0 (or rather is sees it as the external SD card). there is no /dev/block/mmcblk1 either. I thought perhaps the internal and external were swapped, but that doesn't appear to be the case. So since the device can't recognize the internal SD card I don't think I will be able to get anything to flash until I get that resolved first. I'm certain that is why Adam Ubuntu fix and Meg's reprt.img aren't working.
Probably the only way to do that, if it is even possible, is to do it through ADB. Veronica has a thread that shows how to recreate all of the partitions, but when I attempt to do that it doesn't see the internal storage at all so I can't even get started.
I really hate giving up on anything so I will keep trying as long as it takes if I know it is possible to fix this, but I'm not sure what steps to take next to try and get the internal storage recognized.
For all I know it could be a permission issue.
Do you know any commands I can run from ADB Shell to try and get the internal storage recognized?
When I run a list command from ADB shell I get the following:
~ # ls
ls
boot fstab.acclaim sd-ext
bootdata init sdcard
cache init.rc sys
data internal_sd system
datadata proc tmp
default.prop recovery ueventd.acclaim.rc
dev res ueventd.goldfish.rc
emmc rom ueventd.rc
etc root
external_sd sbin
~ #
So it looks like the internal storage is working after all and I can get into some of these directories and files and CAT or TAIL them. Perhaps the MBR is messed up or something?
skelnik said:
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found.
...
Click to expand...
Click to collapse
You can try one of Succulent's more recent 10.2 builds listed at http://iamafanof.wordpress.com/2013...id-4-3-for-nook-tablet-imgsdc-boot-09aug2013/ which he uploaded onto Media Fire: "cm_acclaim_10.2.0-RC0_13OCT2013_HD_SDC_IMG.7z (mirror)".
You might also want to take a look at Succulent's recovery tools (in particular flash_stock_1.4.2.zip) at https://github.com/succulent/acclaim_recovery_sdcard.
Hi
I'll try to make it brief. Some time ago, my stock Nook slowed down like a mule so I decided to root it, then applied Trimmer to enable trim. Beforehand I'd checked the eMMc with a Brickbug app and it popped up with "sane chip", as I'd read some Nooks had a faulty Samsung eMMc.
It went into a bootloop, and only started showing shredded Nook letters on an abstract background during boot. Then I tried various bootable SD cards to try to flash various stuff, as per available XDA threads, especially - leapinlar's, verygreen's and amaces'. First it would not complete the flashing of a ROM, just froze towards the end, then eventually wouldn't boot up at all.
Here's the weird part. Without an SD card, it doesn't boot up at all.
When I make a bootable SD, it only boots to TWRP 2.6.0.0 (some other versions [amaces] it won't boot to), but doesn't see any zips on the card and won't let me flash anything, even though it previously did, but wouldn't complete the flash.
Whatever else I burn on the card, it either doesn't boot up at all, or boots to whatever it is you can see on the attached printscreens, and won't mount anything. So if I'm guessing right, the eMMc is not borked, as it seems the device boots to some remnants of something that's there, and not on the SD.
Is there a way of fixing that mess? I'd appreciate any ideas.
Best
W.
You can try to flash this flashable_fix_bootdata-ovation.zip which typically should cure corrupted or missing bootdata issues.
Hi, thanks but how? The only thing I tried so far that the Nook boots to is a TWRP 2.6.0.0. bottable card and it won't see the zips on it. So how can I flash the fix bootdata zip?
wojtasys said:
Hi, thanks but how? The only thing I tried so far that the Nook boots to is a TWRP 2.6.0.0. bottable card and it w on't see the zips on it. So how can I flash the fix bootdata zip?
Click to expand...
Click to collapse
Have you tried the verygreen's old SD-based CWM recovery?
If you mean the one from that thread:
https://forum.xda-developers.com/showthread.php?t=2600572
I have. The download links for the initial card image don't work. I looked elsewhere - nowhere to be found.
Sorry about the trouble, guys, forgot to update the dns when the server moved. I just updated it, but it'll take some time to propagate. The actual new ip address is now 178.34.187.142 - you can place it into your hosts file if you don't want to wait.
Nook HD+ Bootloop error
OK, I tried the succulentboot.zip from your folder:
https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook HD+):
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
I tried flashing stock recovery too and it says it's done that, but I guess without the fixed bootfiles it won't work anyway.
wojtasys said:
OK, I tried the succulentboot.zip from your folder:
https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook HD+):
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
I tried flashing stock recovery too and it says it's done that, but I guess without the fixed bootfiles it won't work anyway.
Click to expand...
Click to collapse
Assuming that your flashing of stock recovery was successful (recovery's reports of successful completion can sometimes be erroneous) and also your factory backup partition is still intact, you can try to initiate a factory reset by using the "8 failed boots" method: with the Nook in the power-off state, power it on, then as soon as the boot screen appears hold down the power button until it powers off, do this 8 times, and the Nook should go into stock recovery to revert to factory-fresh state.
Flashing your flashable_restore_stock-recovery-ovation zip ends with the screen I'm attaching.
Then I tried "8 failed boots" but it only boots to CWM SD, without the card - it doesn't power up at all.
Eventually, nothing changes.
Tried putting the stock ROM on the card and flashing that, but the partition size is too small, even though its a 16GB card.
wojtasys said:
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
Click to expand...
Click to collapse
If the issue is about the two files, you could mount /bootdata and copy them manually (ADB shell should be functional with any of these recoveries). You'd extract BCB and BootCnt from ZIP, and copy them onto SD card, then do something like:
Code:
mkdir -p /bootdata
mount -t vfat /dev/block/mmcblk0p6 /bootdata
cd /external_sd or /sdcard or /emmc (wherever SD card root is mounted)
cp BCB BootCnt /bootdata/
Or, you could edit the updater-script inside ZIP to remove the device assert line like in the attachment here. By the way, are the updated images here also failing?
Flashing your flashable_fix_bootdata-ovation-no-assert.zip shows "install from sd card complete" but the device still won't power up without the card.
Trying to mount bootdata results in "error mounting bootdata".
There's no adb command line in that sd recovery, just adb sideload. TWRP 2.6 had it but it didn't access the files on the sd.
Then, I'm not sure I'll know how to edit the updater-script inside ZIP to remove the device assert line.
Chances are your EMMC is hosed, in which case you can try running CM entirely off SD card using the succulent special build available at https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
Helo! I will explain the case.
Device: Samsung Galaxy S Duos S7562
Custom ROM: Lineage 15
I selected to perform device encryption in the default option of the system, after the whole process, the phone got stuck in the Samsung logo and won't start. So I accessed the TWRP and saw that it is not possible to access /data and it is also not possible to clean it.
Through the computer I can't get the device to be recognized by the ADB.
Is there any solution or can I schedule the wake?
TWRP >> Wipe >> format data >> type "yes" .
It appears the ROM does not support encryption/decryption, the phone is indeed encrypted, but the problem is when trying to decrypt the data, it seems to fail.
If you had any important files, there has been some tutorials on decrypting /data in TWRP using the decryption password.
Mohamedkam000Thanks for the tip. I went to research and found this tutorial. It worked for me from step 8.
I found it on another site, I don't know if I can quote the source here, but here are the steps, in case someone else needs it:
1. The first thing to try is whether the internal storage was somehow encrypted using a legacy screen lock method.
2. Go to Settings > Security > Screen lock of your Android device and change screen lock method to Approved or Pin. Create a new one.
3. Reboot into TWRP, and it should ask for a password - enter the pass or pin you just created.
4. TWRP will attempt to decrypt your device's internal storage and, if successful, you should have no further problems. However, if that doesn't solve the “unable to mount data, 0mb internal storage” issue, continue with the rest of this guide.
5. Reboot your device into TWRP again.
6. Navigate to Clean > Next Clean > Data and choose Repair or Change File System.
7. Press Repair File System to see if this resolves the issue. If not, continue.
8. Press Change File System, choose Ext2 and swipe to confirm.
9. Now go back to Ext4 and swipe to confirm.
10. Go back to the TWRP main menu, then to the Mount menu and check if your partitions can be mounted now.
11. If you are still unable to mount your partitions, you will need to repair the internal partition, which will likely clear your internal storage.
There are four points to clear it out:
For /data partition to show 0 MB, or failed to mount, it doesn't mean it has broken its filesystem, it didn't, it's just encrypted, that's how the protection works.
Choosing to repair filesystem or change filesystem may result in a bootable/mountable filesystems, however, you'll lose your data. Not all phones has decryption on TWRP, it needs a modified recovery.
Encryption has different security key than the regular lockscreen, it doesn't use pattern. So it doesn't matter what you've set on your lockscreen.
It seems to be your first time encountering this issue. On modern phones (S6 and above), when you flash TWRP, you won't be able to mount /data, because all phones come with forced encrypting mechanism, so in order to flash custom ROM, you'll have to format data (the option where you write "yes"). And any mount of /system will result in a bootloop haha.
Mohamedkam000 said:
There are four points to clear it out:
For /data partition to show 0 MB, or failed to mount, it doesn't mean it has broken its filesystem, it didn't, it's just encrypted, that's how the protection works.
Choosing to repair filesystem or change filesystem may result in a bootable/mountable filesystems, however, you'll lose your data. Not all phones has decryption on TWRP, it needs a modified recovery.
Encryption has different security key than the regular lockscreen, it doesn't use pattern. So it doesn't matter what you've set on your lockscreen.
It seems to be your first time encountering this issue. On modern phones (S6 and above), when you flash TWRP, you won't be able to mount /data, because all phones come with forced encrypting mechanism, so in order to flash custom ROM, you'll have to format data (the option where you write "yes"). And any mount of /system will result in a bootloop haha.
Click to expand...
Click to collapse
Thanks for the information. Next time I'm going to look for an encryption-compatible TWRP.