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).
I have been doing lots of ROM / Kernel experimentation on my VZW S4, and on attempting to take a backup of my most recent good configuration I received an error from TWRP that there is not enough space available because there is not enough space for my /Data partition which TWRP sees as 2438401MB or 2.4TB!
Since it is impossible that my on device /Data partition is 2.4TB, anyone have any suggestions on how to repair?
Or do I need to do a full install via Odin using the repartition option?
Thx.
Wow, it would be cool if you had 2tb, umm sounds like the recovery is corrupt, if it were me, I would try that first, if it does not work, do the odin flash to stock.
Good luck.
I reinstalled the TWRP recovery, and also reflashed a Verizon stock image file...but TWRP is still reporting my /data partition at 2.4TB.
I'm thinking I need to repartition, but have never done so on an Android device.
Recommendations?
I would try reading the odin features and what it does to re-partition. It has that option, but messing with the partition structure will cause a hard brick if not careful.
good luck.
Okay, I did an complete factory restore using the image from the following thread and now have a properly sized /data partition.
http://forum.xda-developers.com/showthread.php?t=2289325
Whew.
Thx.
morgej said:
Okay, I did an complete factory restore using the image from the following thread and now have a properly sized /data partition.
http://forum.xda-developers.com/showthread.php?t=2289325
Whew.
Thx.
Click to expand...
Click to collapse
hehe you got off easy...good deal.
Can you tell TWRP to do its backups to the SD card rather than internal memory?
Thinking about getting an S4 but w/only 9GB free, would like to keep my backups on the SD card I'm going to get for it. I know I could move them there after creating them, but don't want to deal with having to move them back and forth if I need to restore one.
Redflea said:
Can you tell TWRP to do its backups to the SD card rather than internal memory?
Thinking about getting an S4 but w/only 9GB free, would like to keep my backups on the SD card I'm going to get for it. I know I could move them there after creating them, but don't want to deal with having to move them back and forth if I need to restore one.
Click to expand...
Click to collapse
yes. thats what i do. However, I was using TWRP to backup my aokp rom that i set up and it wouldnt back it up and read the size would be 16gigs. However, my slim rom backup just fine without reporting a huge file size.
Hi all, i just replaced my sd-card so i can make a swap partition and speed up my phone.
any way.. i played with Swapper 2 options (swap and swappiness size).
after reboot my galaxy doesn't boot into the system i did a nandorid backup,moved back to Samsung official release, did a full system format and still i doesn't boot into the system.
when i'm restore to my cm backup it stuck on it writes that the restore succeed but it stuck on ''Samsung Galaxy SIII'' screen.
when the official release installed (from adb) it does a boot loop over and over (factory reset doesn't work).
another thing i noticed is that in the recovery it writes ''E:failed to mount /efs (invalid argument)''
that can i do? i think i did every thing i can
In recovery can you access the efs partition? If not then it probably is corrupt, you'll need to format it and restore your efs backup.
If you don't have an efs backup then you need a service centre.
I wouldn't mess with any partition software on this phone, too risky.
i don't have /efs partition
Ok so i managed to boot into official firmware and i found that i don't have /efs partition.
i figure this out from EFS Professional, EFS pro and the recovery.
im searching for an hours but with no answer.. - can i create /efs partition?
EFS Recovery
RReeD said:
Ok so i managed to boot into official firmware and i found that i don't have /efs partition.
i figure this out from EFS Professional, EFS pro and the recovery.
im searching for an hours but with no answer.. - can i create /efs partition?
Click to expand...
Click to collapse
Do you have any older backup files.
When you try to restore your backup file CVM or TWRP recovery will ask which partitions you want to restore.
If you see EFS partition on any of your old backups you can restore it.
If no the way to service is seen.
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
edwinn said:
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
Click to expand...
Click to collapse
u need to use pit file for repartition your internal memory.flash your phone with pit file
ifhi said:
u need to use pit file for repartition your internal memory.flash your phone with pit file
Click to expand...
Click to collapse
Total Bull-sh-it!
Don't do this, @edwinn
You will restore your backup either with terminal command or within the custom recovery. Is it tar only or tar.gz?
tetakpatalked from Nexus 7 flo
edwinn said:
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
Click to expand...
Click to collapse
hello u should flash the tar file via recovery this should restores ur efs backup
tetakpatak said:
Total Bull-sh-it!
Don't do this, @edwinn
You will restore your backup either with terminal command or within the custom recovery. Is it tar only or tar.gz?
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
The efs.ext4.tar file is in a folder called "clockworkmod", together with files like boot.img, system.ext4.tar, nandroid.md5 etc.
So I took the next steps:
installed CWM Touch 6.0.3.2 via Odin
copied entire "clockworkmod" folder tot ext sd card
tried to restore from external sd card
After checking MD5 sums the error "MD5 mismatch!" is displated.
Deleting all data in nandroid.md5 was not succesfull.
Further help would be appreciated.
edwinn said:
The efs.ext4.tar file is in a folder called "clockworkmod", together with files like boot.img, system.ext4.tar, nandroid.md5 etc.
So I took the next steps:
installed CWM Touch 6.0.3.2 via Odin
copied entire "clockworkmod" folder tot ext sd card
tried to restore from external sd card
After checking MD5 sums the error "MD5 mismatch!" is displated.
Deleting all data in nandroid.md5 was not succesfull.
Further help would be appreciated.
Click to expand...
Click to collapse
There have been major changes done in CWM since early 6xxx versions. Do you remember which recovery version number did you use to create your backup? I had myself some perfect backups done with 6.0.2.7 that weren't restorable with 6.0.4.5 due to md5 mismatch.
The chances are good you'll be able to restore it, mate.
tetakpatalked from N7100
tetakpatak said:
There have been major changes done in CWM since early 6xxx versions. Do you remember which recovery version number did you use to create your backup? I had myself some perfect backups done with 6.0.2.7 that weren't restorable with 6.0.4.5 due to md5 mismatch.
The chances are good you'll be able to restore it, mate.
tetakpatalked from N7100
Click to expand...
Click to collapse
I found out that the backup was made with Online Nandroid v9.51 (The recovery.log file says so :victory. No info on the CWM version number. It may have been a very old recovery which had a bug that created nested /0 folders in the file systems after every data wipe. I didn't discover that issue until recently . More info on this bug:
http://forum.xda-developers.com/galaxy-s3/help/storage-emulated-0-0-0-flashing-roms-t2214356
The backup may include the nested /0 folders. Perhaps that is causing the checksum mismatch?? (Since the system folder was formatted afterwards)
Anyway. I tried a new non-touch cwm recovery, version 6.0.4.3. No success.
Would you recommend to proceed with the terminal thing? Thx
edwinn said:
I found out that the backup was made with Online Nandroid v9.51 (The recovery.log file says so :victory. No info on the CWM version number. It may have been a very old recovery which had a bug that created nested /0 folders in the file systems after every data wipe. I didn't discover that issue until recently . More info on this bug:
http://forum.xda-developers.com/galaxy-s3/help/storage-emulated-0-0-0-flashing-roms-t2214356
The backup may include the nested /0 folders. Perhaps that is causing the checksum mismatch?? (Since the system folder was formatted afterwards)
Anyway. I tried a new non-touch cwm recovery, version 6.0.4.3. No success.
Would you recommend to proceed with the terminal thing? Thx
Click to expand...
Click to collapse
I am sure it is possible to disable md5 check
tetakpatalked from P5110