i am rooted and have so far enjoyed aloysius v11 and v12, evil eris, zen express. but lately any new roms that i try to flash i get a boot loop. no matter what rom i try now it boot loops.
i did nand and can always restore to my curent stable fave aloysius v11.
any idea why i keep boot looping? is it my sd card? i even tried a diferent card and same thing ( i was trying to flash celbfroyo)
Boot into recovery, and wipe it. Go to wipe, then a full system wipe and after that, whip the dalvik cache. Then flash whatever rom you want, then restore via nand.
thewanton said:
Boot into recovery, and wipe it. Go to wipe, then a full system wipe and after that, whip the dalvik cache. Then flash whatever rom you want, then restore via nand.
Click to expand...
Click to collapse
i wiped and did dalvik before flashing.
what do you mean by restore via nand?
1-f.s. wipe/dalvik wipe
2-flash the new rom
3-restore the new rom via nand?
I mean go to Backup/Restore, and hit Nand Restore. All that does is restore your apps, settings, contacts, etc. It has no affect on your rom, just like how wiping has no affect on your rom. That way, if you want Evil Eris, but have Kaos Froyo, you can wipe, then flash and then restore while still having the new ROM.
If that doesn't work, though.. I'm not sure what to do.
thewanton; said:
I mean go to Backup/Restore, and hit Nand Restore. All that does is restore your apps, settings, contacts, etc. It has no affect on your rom, just like how wiping has no affect on your rom. That way, if you want Evil Eris, but have Kaos Froyo, you can wipe, then flash and then restore while still having the new ROM.
If that doesn't work, though.. I'm not sure what to do.
Click to expand...
Click to collapse
Okay thanks for clearing that up. I'll give it a shot.
thewanton said:
I mean go to Backup/Restore, and hit Nand Restore. All that does is restore your apps, settings, contacts, etc. It has no affect on your rom, just like how wiping has no affect on your rom. That way, if you want Evil Eris, but have Kaos Froyo, you can wipe, then flash and then restore while still having the new ROM.
If that doesn't work, though.. I'm not sure what to do.
Click to expand...
Click to collapse
100% wrong.
A Nand restore on the Eris restores the following partitions:
/system (the O/S or "ROM")
/boot (the kernel, initial ramdisk, and initialization scripting for the "ROM")
/data (settings, application state, your data)
+ SD card /ext{2,3} partition (if you did a Nand+ext backup).
That boils down to pretty much 100% of the OS and the application settings and data.
Some bootloops are caused by ext3- or ext4- partitioned cards, depending on which ROM is involved. You might try seeing if you get a different result using no SD card, or an SD card which only has a single FAT32 partition.
bftb0
Oh ****, sorry then. I was under the impression it only saved your data. :/
My bad man.
bftb0 said:
100% wrong.
A Nand restore on the Eris restores the following partitions:
/system (the O/S or "ROM")
/boot (the kernel, initial ramdisk, and initialization scripting for the "ROM")
/data (settings, application state, your data)
+ SD card /ext{2,3} partition (if you did a Nand+ext backup).
That boils down to pretty much 100% of the OS and the application settings and data.
Some bootloops are caused by ext3- or ext4- partitioned cards, depending on which ROM is involved. You might try seeing if you get a different result using no SD card, or an SD card which only has a single FAT32 partition.
bftb0
Click to expand...
Click to collapse
Thanks!! I'll try the no sd card idea.
bftb0 said:
100% wrong.
A Nand restore on the Eris restores the following partitions:
/system (the O/S or "ROM")
/boot (the kernel, initial ramdisk, and initialization scripting for the "ROM")
/data (settings, application state, your data)
+ SD card /ext{2,3} partition (if you did a Nand+ext backup).
That boils down to pretty much 100% of the OS and the application settings and data.
Some bootloops are caused by ext3- or ext4- partitioned cards, depending on which ROM is involved. You might try seeing if you get a different result using no SD card, or an SD card which only has a single FAT32 partition.
bftb0
Click to expand...
Click to collapse
So I can use the sd card to load the rom. But remove it before I reboot?
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.
Hello.
I just got an HTC Hero, and I've faced the problem of lack of space already.
So I read about this app, unaware I would need it (naive of me), while I was downloading the VillainRom v13, to replace the VillainRom v12 I had.
I flashed it succesfully. I installed the apps I had before. But now, unfortunately, I'm running low on internal space.
How can I move application to the SD card? Is there a tutorial that explains me how to do it for my phone and rom?
How can I determine if my SD card is fast enough?
Thanks for any help you can provide.
to move applications just go to settings>applications>manage applications and click on which ever app you want to move to sd card. Once you click on the app it'll go to a page which will allow you to move your app to the sd. Usually class 4+ SDs are fast enough
The question is that I have tried that... But I don't have that option!
I believe it is because I'm on the 2.1 rom, instead of 2.2, and that option was only introduced in 2.2.
welll, im not sure how to do it without wiping and starting all over again but,
if you make a nandroid.. then backup your sd card onto your computer(including the nandroid backup)
you could go into your recovery image and partition your sd card, swap - 32mb, ext2 - 512mb and fat32 the rest (it takes you through those settings step by step)
then wipe factory reset/all data and wipe your dalvik cache
then flash your rom (double check that the rom has a2sd).. and the rom will do the work for you!
i just did this with wildhero... its the only rom im 100% sure will do the a2sd for you
xsirhc6x said:
welll, im not sure how to do it without wiping and starting all over again but,
if you make a nandroid.. then backup your sd card onto your computer(including the nandroid backup)
you could go into your recovery image and partition your sd card, swap - 32mb, ext2 - 512mb and fat32 the rest (it takes you through those settings step by step)
then wipe factory reset/all data and wipe your dalvik cache
then flash your rom (double check that the rom has a2sd).. and the rom will do the work for you!
i just did this with wildhero... its the only rom im 100% sure will do the a2sd for you
Click to expand...
Click to collapse
Thanks!
I was struggling with this aswell
The thing is my ClockWork Mod doesn't have that formatting option...
Does VR13 support A2SD natively? I believe so.
I use HTC HD2, Android on SD card, don't know how to use A2SD ?
Now i use Swapper2 to set Swap file.
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 want to remove files that have accumulated from other roms. In others words like stock, but with custom rom. I like Beanstown106 with SD swap.
Thats a little tricky with sd swap but you will have to painstakingly go file by file and see if it's something you have deleted to something that you are still using. If you have any apps that created a folder and are gone for good then you are safe to delete. But avoid any system app folders and anything that you are still using like pictures, music and so on avoid.
M.A.D.NoTe.||
thx for help
I'm installing cleanrom ace 4.9 my goto rom next to beanstown106. No SD swap and I was thinking of formating SD card. Now how do I erase what a factory reset won't delete.
I usually wipe EVErYTahING wenever i flash something new sd card and all just to start from scratch but all i got on sd card is pix and music so its easyily backed up
SAPPERJD said:
now how do I erase what a factory reset won't delete.
Click to expand...
Click to collapse
from recovery, format internal and external sd. that will wipe everything out completely.
I did consider formating from recovery. I'm just scare of deleting the OS and my phone ending up being useless. I did research and what I read it won't. Any advise is welcome THX to everyone.
SAPPERJD said:
I did consider formating from recovery. I'm just scare of deleting the OS and my phone ending up being useless. I did research and what I read it won't. Any advise is welcome THX to everyone.
Click to expand...
Click to collapse
How would it end up being useless? Its no different than a pc...your reformatting and installing the OS on a clean slate.
I was thinking if I formated the internal it would delete recovery as well. And had no way of installing a new rom. Thx again really help full.
Wipe Everything
droidstyle said:
from recovery, format internal and external sd. that will wipe everything out completely.
Click to expand...
Click to collapse
I want to clean up my directory structure. If I format the internal and external sd using recovery (TWRP) to wipe everything, what rom will boot? Will my custom rom boot or will the original verizon rom boot? Will I have to unlock the bootloader again? Thanks.
rechbo said:
I want to clean up my directory structure. If I format the internal and external sd using recovery (TWRP) to wipe everything, what rom will boot? Will my custom rom boot or will the original verizon rom boot? Will I have to unlock the bootloader again? Thanks.
Click to expand...
Click to collapse
you will lose all data and need to reflash the rom in recovery...no you will not have to unlock again, nothing performed from recovery will overwrite the boot.img.
I was scared of the losing my OS as well, but it's not that hard. Treat it as two steps. Formatting your sDCard, and then prepping your SdCard by doing a Nandroid backup to your SdCard, and copying a flashable ROM (and kernel if your ROM does not flash a kernel) to your SdCard. Before formatting your SdCard copy anything you want to keep to your computer. I just copy the whole card to my computer.
Reboot and do your data resets and wipes, including internal storage (format data in twrp) Then flash your ROM that you put on your ext SdCard. Your nandroid backup is your insurance. Worst case you boot into recovery and restore your backup.
(But you should still have a working toolkit or ADB on your computer and you can recover from any screw up)
As long as you have what you need on your (ext) SdCard before wiping internal storage, and you only do a data reset and cache wipes and only do 'format data' you will be fine.
Sent from my Nexus 7 using xda premium
Hey Guys,
As an alternative to ROM slots, what you can do is,
1. Boot into 1st ROM, configure and download all the apps you want.
2. Take a Nandroid of; /System and /data and optionally; cache. But I don't use the latter.
3. Wipe Data, System, Cache, and dalvik.
4. Install 2nd ROM, boot, configure, install all the same apps (just for now)
5. Take Nandroid of /system only
To switch to ROM 1, restore the backup of its /system (should only take about 6-10 seconds as opposed to flashing data too.
To switch to ROM 2, restore the backup of its /system ""
The reason you MUST install all the SAME apps on the 2nd ROM is to rebuild the necessary data folders.
In
To install a new app, boot to rom 1 and install it, then switch to ROM 2 and wipe cache and boot or vice versa.
Have fun,
While this may work, be aware there are problems that could arise by doing this. They likely wouldn't effect much but some ROM's are picky. That aside your still partitioning your device and will lose X amount of space even with this method.
NighthawkXL said:
While this may work, be aware there are problems that could arise by doing this. They likely wouldn't effect much but some ROM's are picky. That aside your still partitioning your device and will lose X amount of space even with this method.
Click to expand...
Click to collapse
I agree, especially with Xposed, some problems could definitely arise. But I switch between Hyperdrive and GPE via this method about 2-3 times a week. Over time, constant flashing takes its toll on the Drive, but I don't mind it much.
Actually... you aren't partitioning though... you can just take the backups to your SD Card and it wont take up any internal storage other than what the ROM is taking