Database Users

[Please Help] Looping boot screen

Hi all,
A few months ago I rooted my magic and intalled a hero theme one of the JAChero ones, i believe.
Anyway, while in the phone I selected 'Restore factory settings' from within the options menu. The phone reset and now when it boots it just loops the HERO start up screen over and over.
I have still have the update.zip file I used and all the Nandroid backup stuff - but I don't know what to do with them.
Can anyone help?

normally formatting your sd card back to fat/ext/ls is a quick fix for this issue

sondh said:
I have still have the update.zip file I used and all the Nandroid backup stuff - but I don't know what to do with them.
Click to expand...
Click to collapse
update.zip: is just for when you install the rom, once you installed it now it is stored on your device so you no longer need a copy of it on your sd card,
I would personially save that to your computer though incase something like this happens and you dont have a backup but want the same rom then you dont need to search for it, you can simply put it back on your card, wipe, install
nandroid: is the copy of your phone the last time you hit the "backup" button in your recovery screen, you want to leave that on the root of your sd card (where it is now) so that if your phone ever gets messed up you can boot into recovery and do a "restore" (this is why you should always and only do a backup of a rom that is working and that you are happy with )

Hi,
Okay, firstly i've formatted the SD card to FAT/EXT and it's still happening.
I haven't done this in a long time... If I want to restore the phone to the backup do I need to use ADB?
If I boot into recovery mode I get the following options:
reboot system
apply sdcard:update.zip
wipe data/factory reset
Then at the bottom it says E:Can't open /cache/recovery/command
Thanks in advance.

sondh said:
I've formatted the SD card to FAT/EXT and it's still happening.
Click to expand...
Click to collapse
your using a hero rom correct? so I'm hoping you just mistyped that because to start your sd card needs to be partitioned to [ FAT32 / EXT2 / Linux Swap ]
sondh said:
If I want to restore the phone to the backup do I need to use ADB?
Click to expand...
Click to collapse
No as long as you did a backup and still have the nandroid folder on the root of your sd card, you should be able too boot into recovery, then choose "Nandroid Restore" it should be right under "Nandroid Backup" the one you chose to make the backup in the first place
sondh said:
If I boot into recovery mode I get the following options:
reboot system
apply sdcard:update.zip
wipe data/factory reset
Click to expand...
Click to collapse
What recovery img are you using? their normally is a build number somewhere on there [ i.e. Build: RA-magic-v1.2.3H ]
also heres a link to amon's recovery, their s a screen shot at the bottom of the first post of what that recovery looks like and those are the options you should have
RA V1.2.3

Right, I'm going INSANE!
It is a 32A device, so does the card need to be partitioned? Is there a way to partition the card in that way? REMEMBERING i can't do it via an app on the phone as the bloody thing won't get past the Hero boot screen.
I don't have the option to do a 'Nandroid Restore' - I think i used a Daldroid recovery image.
When I plug in the phone via USB, windows recognises it as 'Android 1.0' and won't let me install any USB drivers!!

Right, I can boot the Amon RA recovery image from fastboot.
I've tried fixing the partition of the SD card, but it's still looping.
Can I just flash another ROM now, or would that mess things up?

sondh said:
Right, I can boot the Amon RA recovery image from fastboot.
I've tried fixing the partition of the SD card, but it's still looping.
Can I just flash another ROM now, or would that mess things up?
Click to expand...
Click to collapse
na you can ive had it happen to me a few times the first time re-formatting the partitions worked and second time it didnt so i just flashed again and it works fine...
if you like the rom your using you could try flash the same one maybe something messed up during the install or you could just flash a whole different one
either way the direction i would go would be
first: format the card to fat32/ext2/ls
second: do a wipe
third: flash
hope that works out for ya

sondh said:
does the card need to be partitioned?
Click to expand...
Click to collapse
you def do need to partition it for the hero rom or youll always get that loading screen that will drive you even more nuts then your going now lol
sondh said:
Is there a way to partition the card in that way? REMEMBERING i can't do it via an app on the phone as the bloody thing won't get past the Hero boot screen.
Click to expand...
Click to collapse
you wouldnt be able to use an app to partition anyway so that doesnt really make a difference but if your going to flash another hero i would use these directions to partition your card and also make sure your card is a class 6 (you can tell by the # inside the circle on the card (not the size i.e. 8gb but there will be a circle with a (2),(4),(6) like that))
sondh said:
I don't have the option to do a 'Nandroid Restore' - I think i used a Daldroid recovery image.
Click to expand...
Click to collapse
if you dont have those options i would throw a different recover amons ra is really nice option wise here it is
sondh said:
When I plug in the phone via USB, windows recognises it as 'Android 1.0' and won't let me install any USB drivers!!
Click to expand...
Click to collapse
you can get the drivers from the android sdk which is here
sondh said:
Right, I can boot the Amon RA recovery image from fastboot.
I've tried fixing the partition of the SD card, but it's still looping.
Can I just flash another ROM now, or would that mess things up?
Click to expand...
Click to collapse
na you can ive had it happen to me a few times the first time re-formatting the partitions worked and second time it didnt so i just flashed again and it works fine...
if you like the rom your using you could try flash the same one maybe something messed up during the install or you could just flash a whole different one
either way the direction i would go would be
first: format the card to fat32/ext2/ls
second: do a wipe
third: flash
hope that works out for ya

FINALLY!
Did as you said.
I'm all up and running again!
Thank you so much!

[Q] Can a DFT Rom be backed up & restored with CWM Recovery?

The title pretty much sums it up... im running MDJ's CM7 2.6 (DFT version) and Im happy with it the way it is but i kinda wanna try MIUI, but i wanna be able to restore it if i dont like the new rom

lowrider262 said:
The title pretty much sums it up... im running MDJ's CM7 2.6 (DFT version) and Im happy with it the way it is but i kinda wanna try MIUI, but i wanna be able to restore it if i dont like the new rom
Click to expand...
Click to collapse
I may be mistaken, but I believe MagDLR has its own backup/restore function built-in.

h.nocturna said:
I may be mistaken, but I believe MagDLR has its own backup/restore function built-in.
Click to expand...
Click to collapse
hmmmm... if this is the case can you (or anyone) explain how to use it?

lowrider262 said:
hmmmm... if this is the case can you (or anyone) explain how to use it?
Click to expand...
Click to collapse
My HD2 is in the shop right now, so I can't explain without it here in front of me. From my memory alone, I believe there's an option in the Magdlr menu to backup/restore. It may be under Services. If it's not there, then I totally made up that backup function. The next best thing you can do is to use a backup software like Titanium/MyBackup.

lowrider262 said:
The title pretty much sums it up... im running MDJ's CM7 2.6 (DFT version) and Im happy with it the way it is but i kinda wanna try MIUI, but i wanna be able to restore it if i dont like the new rom
Click to expand...
Click to collapse
No it can't be.
Sent from my HTC HD2

Yes it can be. I used daf roms for a while, and in clockwork, choose backup / restore and it will take an image of the partitions, including the ext if memory serves,, which can then be later restored. But you gotta keep the partitions the same size or bigger else it wont fit when you restore.(or maybe it does re write the partitions,I never tested it)

samsamuel said:
Yes it can be. I used daf roms for a while, and in clockwork, choose backup / restore and it will take an image of the partitions, including the ext if memory serves,, which can then be later restored. But you gotta keep the partitions the same size or bigger else it wont fit when you restore.(or maybe it does re write the partitions,I never tested it)
Click to expand...
Click to collapse
Problem is that he is missing CWM and needs to install it prior to trying new ROMs, which will wipe any ROM he currently has before he has a chance to back it up.

ahhhh hadnt spotted that bit, my oversight. How about the cwm that boots from sd?, suppose that depends whether the nand rom he flashed has the recovery partition,,,

bummer. thanks for the input guys

You could do a full backup using titanium (or whatever its called), then just reflash your current daf rom, but including the recovery.img file from the clockwork files, and using the clockwork flash.cfg, making sure it is creating a system partition big enough for the system.img from the daf rom.
that way you sneakily apply cwm and keep your daf rom, which you restore the backup of, then enter cwm and voila, you can use backup restore.
There is also a converter app to convert daf roms to cwm, you could do it that way,,, backup, wipe, magldr,clockwork,convert daf rom to cwm, flash it, restore backup.
Might also wanna update to latest magldr whilst ya doing that..

samsamuel said:
ahhhh hadnt spotted that bit, my oversight. How about the cwm that boots from sd?, suppose that depends whether the nand rom he flashed has the recovery partition,,,
Click to expand...
Click to collapse
Yes, this will work, even if you don't have the recovery partition. You get an error message when CWM boots, but the backup/restore still works fine. Just setup the CWM files in the SD card and boot AD SD from MAGLDR.

[Q] HTC HD2 from android 2.3.6 to 2.3.7 upgrade

Hi there,
I have the NexusHD2-Gingerbread_V3.1a_NAND_(Android-2.3.6) on my HTC HD2 and I downloaded the TyphooN_CM7_v3.6.8-MAGLDR ROM so I installed it following a video tutorial but there was a slight problem, everything went well up until the moment when the phone boot up which it stayed on the android figure for ever, i have waited maybe 20+ minutes for it to load/boot but there was nothing. I re-flash twice but still nothing was happening, it kept locking at the boot up android figure screen. Also took out the battery twice but still nothing, Do you have any ideas why or any other suggestions? Please if you could help that would be most appreciated.
By the way: this was a clean wipe/flash installation thru Clockworks mod
Thanks
Chris

What cwm partition did you use ?
Sent from my HD2 using xda premium

I am using cwm ver. 3.2 and i installed it on the phones main partition, did not do any ext3 or did not bother with sd, just installed zip from sd on to phone.
Thanks
I hope i find help,

crosis001 said:
I am using cwm ver. 3.2 and i installed it on the phones main partition, did not do any ext3 or did not bother with sd, just installed zip from sd on to phone.
Thanks
I hope i find help,
Click to expand...
Click to collapse
nono
tell me the partition size of system and cache

yz.hd said:
nono
tell me the partition size of system and cache
Click to expand...
Click to collapse
How can i find the parition size and cache?
thanks

twrp recovery

Im trying to go a backup of my rom and when I go into recovery to do the backup it says not enough space . I am backing it up to a 64 gb sd card with obee 39 of gb left. After a couple of times I looked at the data and it was at somthing 750000mb on datawhich is almost 70gb of data which is impossible

scotty25 said:
Im trying to go a backup of my rom and when I go into recovery to do the backup it says not enough space . I am backing it up to a 64 gb sd card with obee 39 of gb left. After a couple of times I looked at the data and it was at somthing 750000mb on datawhich is almost 70gb of data which is impossible
Click to expand...
Click to collapse
this happened to me. Unfortunately i gave up and ended up reflashing the rom i was using.
I originally tried to just flash twrp via odin and the same problem would happen. I ended up just wiping and installing everything from scratch. Weird thing was that it happened again. I did a final wipe and after i would flash one thing i would make a backup. Now i don't have the issue. Originally it said i had 7tb of /data.

scotty25 said:
Im trying to go a backup of my rom and when I go into recovery to do the backup it says not enough space . I am backing it up to a 64 gb sd card with obee 39 of gb left. After a couple of times I looked at the data and it was at somthing 750000mb on datawhich is almost 70gb of data which is impossible
Click to expand...
Click to collapse
And you selected the sdcard as the backup location? It defaults to internal. I know it is reading the data size wrong from what you posted but thought I would check to make sure.

That is correct. But how do I fix the data so I can backup my roms

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

all i know is that TWRP has some major issues...and ill probalby be going back to CWM
even the timestamps are way off

Anyone else have problems with TWRP 2.6.0.0 locking at the splash screen? Its really annoying. I went back to TWRP 2.5.0.2 for the time being until this can get worked out.

raxxid said:
Anyone else have problems with TWRP 2.6.0.0 locking at the splash screen? Its really annoying. I went back to TWRP 2.5.0.2 for the time being until this can get worked out.
Click to expand...
Click to collapse
how did you upgrade to 2.60 ??
try directly from goo manager
or if you are upgrading from twrp zip file then make sure you wipe/dalvik first
i am on 2.6 upgraded from 2.5 works great no problem what so ever

saj070 said:
how did you upgrade to 2.60 ??
try directly from goo manager
or if you are upgrading from twrp zip file then make sure you wipe/dalvik first
i am on 2.6 upgraded from 2.5 works great no problem what so ever
Click to expand...
Click to collapse
I have been trying both methods. Though I never tried wiping dalvik. I figured recovery would be separate from all that stuff but it does seem to happen more when I do a reboot into recovery from cm10.1. I'll give it a shot. While I like the additions in 2.6.0.0 it does lack the polish of 2.5.0.2 so I may end of staying with that release long term until a maintenance release is made for 2.6.0.0.

[Q] Freezing, rebooting, and can't flash stock rom (reverts to previous state)

Okay, so I feel like I've looked everywhere and tried everything for this problem with my Nexus 7. The closest thing I found was this:
(Google: Nexus 7 2012 rebooting reverts back to previous state)(I can't post outside links as I am a new member)
and there was no followup reply, and the thread was closed.
Here's my problem (I want to be very detailed in case I missed something):
I've had Cyanogenmod 11 on my Nexus 7 for a long time (I think I started with M1 release). I recently installed the M7 release after previous nightly and it was working so smooth that I had finally decided there was no need to install nighties anymore. Everything was going fine until the night after when I noticed it kept rebooting, so I reverted it back to the nightly I had before (June 11th?) because I assumed it was probably something bad with the update. Except it did the same thing, rebooting after a couple minutes, which is weird because it never did that with this nightly. There was never enough time to download the nightlies before it reboots so I tried downloading them on my laptop and then just transferring them to my nexus via usb. I put it in the cmupdate folder so that I could quickly go to settings and press install (as it can see the update from there). It rebooted to install, but it went into cwm with what appears that nothing happened, and I usually never see cwm when updating this way. So I figured, while I'm here, I could just "install zip" and find that zip I just transferred and install, right? Nope. The zip mysteriously vanished, yet the other two updates were still there (M7 and the previous nightly). So I just rebooted just to try the process again, maybe the file transfer didn't work. Same thing happened. So I went to cwm and tried wiping cache, nothing. Wiped dalvik cache, nothing. So I went and did it, wiped data/factory reset, that did NOTHING, as in I rebooted and everything was still there.
So I got to the point where I just wanted to see if I could just revert back to stock so I have a place to start from, maybe contemplate on just staying there for a while where there shouldn't be problems. So I got that all set up with fastboot, got the latest 4.4.3 image, unarchived until I could get to the flashall.bat I ran that and it was successful. Okay now I can just boot into that, right? Suddenly I see the cyanogenmod boot graphic. What happened? Even all of my apps are still there. Still freezing and rebooting.
I tried reverting to stock manually by erasing then formating everything that I can, flashed bootloader (grouper 4.23), flashed zip, locked bootloader, unlocked bootloader (trying to erase as much as I can). This did nothing, still cyanogenmod. I tried a third time while rebooting to bootloader with each step. Nothing. I tried doing a factory reset within cyanogenmod, but when I press the "erase everything" button it doesn't lead anywhere, so I could never get that to start the process. I also tried doing the erasing and formatting from cwm (which isn't being overwritten, as it seems, by all the attempts at flashing stock?), nothing.
I was curious. I uninstalled Netflix because it was right there in my dock. Then I rebooted myself. When it came back up, Netflix was still there. I tried various things, also going back to locking the bootloader and rebooting the bootloader, it still said it was unlocked. So I came to the conclusion that literally nothing was being written or committed to the sdcard no matter what I do.
I did some more research and found that article up top. So I tried uninstalling some apps because it said it may have something to do with a third-party app misbehaving (seems a bit extreme, I'll do it anyways), but there's never enough time to erase everything before it reboots. It also said to try to get it into safemode. I think I might have gotten there once but it still rebooted (which makes me think that it didn't get to safemode), the rest of the times it wouldn't even get to the lockscreen.
What I'm currently attempting is to see if I can get it into safemode, or I'm trying to uninstall or stop/clear data for every single app with an intentional reboot each time.
Anyone got any idea what's going on? Is it maybe a bad sector, or worse, bad sdcard?

Gonna bump this. Still no luck on my part.
Anyone have any idea?
Perhaps somehow something got triggered to prevent anything being written to the sdcard? (Kinda like the lock switch on actual sdcards?) Is everything I've been doing going straight to memory since everything reverts back after a reboot? That's the only explanation I can think of.
Perhaps there's more I could try. I'm only moderately knowledgeable with things like fastboot and roms, so maybe someone with more experience might have more insight. Please, chime in.
Thanks in advance,
JM

Same problem here....

Flash factory image

USBhost said:
Flash factory image
Click to expand...
Click to collapse
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.

Amd64bits said:
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Click to expand...
Click to collapse
O ok

Amd64bits said:
Same problem here....
Click to expand...
Click to collapse
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!

Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash

USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.

violoncellemuse said:
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
Click to expand...
Click to collapse
Boot twrp temporary from the bootloader

USBhost said:
Boot twrp temporary from the bootloader
Click to expand...
Click to collapse
I'm unfamiliar with this, how do I boot temporarily?

violoncellemuse said:
I'm unfamiliar with this, how do I boot temporarily?
Click to expand...
Click to collapse
1 set getting on computer

Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.

violoncellemuse said:
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
Click to expand...
Click to collapse
then you did boot twrp temporary

USBhost said:
then you did boot twrp temporary
Click to expand...
Click to collapse
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?

violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem

USBhost said:
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
Click to expand...
Click to collapse
Do you have any more info? Perhaps my sdcard is "softlocked" or something.

violoncellemuse said:
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
Click to expand...
Click to collapse
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it

USBhost said:
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
Click to expand...
Click to collapse
I do thank you for trying to help me out.
I found a thread with someone with the same problem I'd like to direct people towards: http://forum.xda-developers.com/showthread.php?t=2800064

violoncellemuse said:
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Click to expand...
Click to collapse
Well, I have Paranaoid Android 4.4.4, not Cyanogen, and everything seemed ok until I installed Cloudmagic (and maybe Busybox?) that poped up a Play Store error (I don't remember which one), and suddenly all the problems began. It started to reboots, rebooted so many times that I decided to flash another ROM... but this wasn't possible.
My recovery is TWRP, so we can discard Cyanogen, ParanoidAndroid, CMW and TWRP as guilty, I think.
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
Tried that, nothing happened, still with Paranoid Android.
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
Same here.