Database Users

[Q] Nandroid Fail!

Hello
I wanted to backup so i ran the backup with ROM Manager and it froze when it was backing up .android secure. I had to pull out the battery so I don't think it was completed has this happened to anyone?

Yeah, it happens to everyone not posting in the right forum.

christiankk said:
Yeah, it happens to everyone not posting in the right forum.
Click to expand...
Click to collapse
You kidding me? If this isn't the place for it then where would he post it? Certainly not in the development section.
Sometimes backups get corrupt man, that sucks.. you'll probably just have to start anew
Sent from my Nexus One

ryanolson7 said:
You kidding me? If this isn't the place for it then where would he post it? Certainly not in the development section.
Click to expand...
Click to collapse
How about the forum called "Nexus One Q&A"?

As fun as it is to "act-a-mod", you both need to stop.
ANYWAYS, OP: If at first you don't succeed, try try again. If it fails again, try flashing a different recovery.

Yeah, just try backing up again. It has happened to me before. Stuck backing up at .android_secure. So I just tried to backup again, then it worked.

if you all want a recovery on which you can trust, then switch to Amon_Ra's recovery (RA-nexus-v1.7.0.1)

i keep having a similar problem. my backups can be created just fine. but when i try to restore them they ALWAYS hang at a certain file, such as event_1626573434.txt or whatever it may happen to be. sometimes i can go to advanced nand and restore each portion individually, which sometimes works. so the backup itself works. i really dont know what the problem could be. using clockwork recovery.

sstang2006 said:
if you all want a recovery on which you can trust, then switch to Amon_Ra's recovery (RA-nexus-v1.7.0.1)
Click to expand...
Click to collapse
That's not entirely true, that's pure opinion.
edit: Sorry, I guess I was too slow in writing my response

wdfowty said:
That's not entirely true, that's pure opinion.
Click to expand...
Click to collapse
You might try the quote button, otherwise, are you doubting the post above yours?

First, Make sure you have enough space on your memory card...

Thank you guys. Its all good now
Sent from my Nexus One using XDA App

I happen to have the same issue. Is pulling the battery the only way to get out of it?

Yes
Sent from my Nexus One using XDA App

wdfowty said:
That's not entirely true, that's pure opinion.
edit: Sorry, I guess I was too slow in writing my response
Click to expand...
Click to collapse
yeap, my opinion may turn out to be a fact.
njiwani said:
Hello
I wanted to backup so i ran the backup with ROM Manager and it froze when it was backing up .android secure. I had to pull out the battery so I don't think it was completed has this happened to anyone?
Click to expand...
Click to collapse
Clarkster said:
Yeah, just try backing up again. It has happened to me before. Stuck backing up at .android_secure. So I just tried to backup again, then it worked.
Click to expand...
Click to collapse
RogerPodacter said:
i keep having a similar problem. my backups can be created just fine. but when i try to restore them they ALWAYS hang at a certain file, such as event_1626573434.txt or whatever it may happen to be. sometimes i can go to advanced nand and restore each portion individually, which sometimes works. so the backup itself works. i really dont know what the problem could be. using clockwork recovery.
Click to expand...
Click to collapse
mailliw320 said:
I happen to have the same issue. Is pulling the battery the only way to get out of it?
Click to expand...
Click to collapse

mailliw320 said:
I happen to have the same issue. Is pulling the battery the only way to get out of it?
Click to expand...
Click to collapse
Nope. I'm not sure what I pressed, but I think trackball + power button. And then the phone restarted. Didn't need to pull the battery.

Quick Question.

I recently bought a MyTouchHD.
Went through the entire s=off process which i did correctly.
But when i boot into Bootloader (HBoot) screen i get a message of "no image or wrong image".
I did flash Clockwork, and i can reboot into Recovery or HBoot. but that "no image or wrong image" kinda has me worried, but everything else works perfectly. ... anyone know anything about it?
I tried using DDMS to screen shot it but it wont work for one reason or another.

where is the error popping up at?
Is it trying to load a.img file in Hboot? Maybe try deleting it?

crypysmoker said:
where is the error popping up at?
Is it trying to load a.img file in Hboot? Maybe try deleting it?
Click to expand...
Click to collapse
The error is at the very beginning of the HBoot start up process. It scrolls through several options then says the error message. I'll have to video and upload it via you tube so you can see.

after you did the s-off were you trying to flash a zimage to do overclocking by chance? if so, you might have removed the stock image for the OS to boot correctly. the stock image needs to match the stock bcm4329.ko file and vise versa for OCing. its just a thought. hope this helps.

Please post questions in Q&A section.

aznpr1de808 said:
after you did the s-off were you trying to flash a zimage to do overclocking by chance? if so, you might have removed the stock image for the OS to boot correctly. the stock image needs to match the stock bcm4329.ko file and vise versa for OCing. its just a thought. hope this helps.
Click to expand...
Click to collapse
No i didn't flash any files. I was just trying to PermaRoot the phone, to be honest about it.

neidlinger said:
No i didn't flash any files. I was just trying to PermaRoot the phone, to be honest about it.
Click to expand...
Click to collapse
hmm thats kinda weird you might have had a corrupted file during the root process then. thats the only explanation i can think of. on the hboot screen you do show s-off on the top correct? if so than technically everything should be fine. if you can fully boot the phone up, download terminal from the market, install it, the there should be a $ sign, then type su then press enter, a message should pop up asking permission, accept it, it should change to a # sign, if it does then you have root access. just to be sure reboot the phone and do it again to make sure that root sticks.

aznpr1de808 said:
hmm thats kinda weird you might have had a corrupted file during the root process then. thats the only explanation i can think of. on the hboot screen you do show s-off on the top correct? if so than technically everything should be fine. if you can fully boot the phone up, download terminal from the market, install it, the there should be a $ sign, then type su then press enter, a message should pop up asking permission, accept it, it should change to a # sign, if it does then you have root access. just to be sure reboot the phone and do it again to make sure that root sticks.
Click to expand...
Click to collapse
Yea. i have full root access. and S=off.
Okay well then i guess i need not to worry about it.... If you guys are thinking everything is okay.

Your phone is searching the sd card for an update image, it is nothing to worry about.
Sent from my Desire HD using XDA App

dbiggss said:
Your phone is searching the sd card for an update image, it is nothing to worry about.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
very possible since the first thing i did was rip out their class 2 card and kept my class 6 card. I guess i'll boot into Linux and look for a file to transfer over.

dbiggss said:
Your phone is searching the sd card for an update image, it is nothing to worry about.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
This is correct. You don't need to worry about finding a file to put on there or anything. Hboot does this everytime you boot into it regardless of you. It is automatically looking for an update or diagnostic file to load and/or flash that isn't needed for the phone to function properly. Its an error but not one that you need to worry about unless you go to manually update through hboot, place a file for the update named PD15IMG.zip on your sd card, and it still gives you the error.
My MyGlacier 4G MINE!!!

Constant Boot Loop and can't get to recovery

I was trying to flash my EVO to Boost mobile and this is where my trouble began. After I had went through the steps of flashing I had to reboot. Upon reboot I get a constant reboot. When I try to go to recovery it goes to the htc screen and then keeps rebooting. I have tried flashing clockwork...I have tried the PC36IMG.zip...I have tried many stock RUU's and none of them work. Has anyone ever heard of this because of flashing? I have a link to a vid I posted on youtube....
http://www.youtube.com/watch?v=5Yszd4CamDs

alnova1 said:
I was trying to flash my EVO to Boost mobile and this is where my trouble began. After I had went through the steps of flashing I had to reboot. Upon reboot I get a constant reboot. When I try to go to recovery it goes to the htc screen and then keeps rebooting. I have tried flashing clockwork...I have tried the PC36IMG.zip...I have tried many stock RUU's and none of them work. Has anyone ever heard of this because of flashing? I have a link to a vid I posted on youtube....
http://www.youtube.com/watch?v=5Yszd4CamDs
Click to expand...
Click to collapse
In your video you said you tried the latest ruu. In your video you state that it is version 3.30. The latest ruu is 3.70. I would try using that ruin first.
Sent from my PC36100 using XDA Premium App

Rem3Dy said:
In your video you said you tried the latest ruu. In your video you state that it is version 3.30. The latest ruu is 3.70. I would try using that ruin first.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I might have said 3.30 but it was 3.70. As a matter of fact I have tried older and new ones and none of them help.

You running the .zip RUU or the .exe?

NewZJ said:
You running the .zip RUU or the .exe?
Click to expand...
Click to collapse
I have tried both and none of them have worked. Is one in your opinion better than the other?

Both good, use one when other won't work, have you tried flashing recovery in bootloader?

NewZJ said:
Both good, use one when other won't work, have you tried flashing recovery in bootloader?
Click to expand...
Click to collapse
Yes I have and after I flash and try to go to recovery it just does the same thing...boot loop..over and over.

Does your bootloader say s- on?

NewZJ said:
Does your bootloader say s- on?
Click to expand...
Click to collapse
No...its off...

Checked the ruu zip md5 match?

NewZJ said:
Checked the ruu zip md5 match?
Click to expand...
Click to collapse
Yes I did...I just can't figure it out.

I'm stumped, you need expert, find xhaus

NewZJ said:
I'm stumped, you need expert, find xhaus
Click to expand...
Click to collapse
I have looked some of his threads that seem to be my problem but I can't get them to work for me. I'm at a loss...

The only thing that comes to mind is to flash stock recovery. Then s-on then the ruu zip

NewZJ said:
The only thing that comes to mind is to flash stock recovery. Then s-on then the ruu zip
Click to expand...
Click to collapse
I just tried to flash a stock recovery...supposedly and it still didn't work. I'm thinking I need to get s-on but can't. I have to admit I'm pretty good at rooting and the whole rom thing but have never had a problem like this so I might be over my head. I thought I found a link to a stock recovery but maybe Im looking in the wrong place.

Can't get my Vibrant rooted, please help!

I am running 2.2 and I have tried One Click Root and Z4root and a few others but when I try to Reinstall the Packages I keep getting an error. On one blog almost all the comments were from people experiencing the same problem but no one would give them an answer. I am not new to rooting Android phones because I started back when the G1 came out and I have rooted other peoples phones over the years but this phone is pissing me off.
Here is the blog that I was talking about: http://www.intomobile.com/2011/02/02/root-samsung-galaxy-s-captivate-and-vibrant/
EDIT: I finally got it rooted. I want to thank everyone who helped me. I installed the Clockwork Recovery and CM7 + Gapps.

If you don't have important stuff on there I would just Odin a pre-rooted stock ROM
Sent from my SGH-T959V using XDA App

Juls317 said:
If you don't have important stuff on there I would just Odin a pre-rooted stock ROM
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
How do I do that. Also I'm using a Mac but I can get to a Windows computer if I have to.

isjr said:
I am running 2.2 and I have tried One Click Root and Z4root and a few others but when I try to Reinstall the Packages I keep getting an error. On one blog almost all the comments were from people experiencing the same problem but no one would give them an answer. I am not new to rooting Android phones because I started back when the G1 came out and I have rooted other peoples phones over the years but this phone is pissing me off.
Here is the blog that I was talking about: http://www.intomobile.com/2011/02/02/root-samsung-galaxy-s-captivate-and-vibrant/
Click to expand...
Click to collapse
do you have root explorer or file manager? if so, I can have you rooted in about 5 min or less
Sent from my phone, not yours.

Smartassassin said:
do you have root explorer or file manager? if so, I can have you rooted in about 5 min or less
Sent from my phone, not yours.
Click to expand...
Click to collapse
I have the Astro file manager.

Place this file in your internal sd.
http://db.tt/er5nBa0B
Hold your vol up /down and power buttons. When vibrant screen comes up, release the power button but keep holding the vol buttons this will put you in recovery. Hit reinstall packages and it should take you to Red recovery screen, this means all text will be red. It may take a couple of times but once you turn red, you will be rooted.
As always, I am not responsible if you brick your phone and don't forget to hit the thanks button.
Edit : make sure the name of the file is Update.zip no other variations will work. You can change the name to read that in case it reads Update.zip.zip . DO NOT UNZIP.
Sent from my phone, not yours.

Duplicate deleted

Smartassassin said:
Place this file in your internal sd.
http://db.tt/er5nBa0B
Hold your vol up /down and power buttons. When vibrant screen comes up, release the power button but keep holding the vol buttons this will put you in recovery. Hit reinstall packages and it should take you to Red recovery screen, this means all text will be red. It may take a couple of times but once you turn red, you will be rooted.
As always, I am not responsible if you brick your phone and don't forget to hit the thanks button.
Edit : make sure the name of the file is Update.zip no other variations will work. You can change the name to read that in case it reads Update.zip.zip . DO NOT UNZIP.
Sent from my phone, not yours.
Click to expand...
Click to collapse
Still getting the same error message as always. It gets about 25% of the way then says that there is an error.

isjr said:
Still getting the same error message as always. It gets about 25% of the way then says that there is an error.
Click to expand...
Click to collapse
and the name of the file is Update.zip and no variation?
Sent from my phone, not yours.

Smartassassin said:
and the name of the file is Update.zip and no variation?
Sent from my phone, not yours.
Click to expand...
Click to collapse
Yes, I learned about the naming trick back with 1.5 on my G1.

isjr said:
Yes, I learned about the naming trick back with 1.5 on my G1.
Click to expand...
Click to collapse
odd it should be near instant. And it's placed somewhere in the internal sd?
What is the error message?
Sent from my phone, not yours.

Smartassassin said:
odd it should be near instant. And it's placed somewhere in the internal sd?
What is the error message?
Sent from my phone, not yours.
Click to expand...
Click to collapse
Yeah its on the root of my sd card. Also I don't have access to the phone right now to tell you the error. The blog that I linked above has the error in the comments.
Sent from my Nexus S

This is getting very frustrating because this isn't my first time rooting a phone.
Sent from my Nexus S

Did you do it my way or the blogs way? And literally just place the update on the internal. Mine is still Located just above my youtube and zedge files.
And... You are getting the same message each time?
I cannot remember if there is a fix permission in stock recovery.
Sent from my phone, not yours.

Smartassassin said:
Did you do it my way or the blogs way? And literally just place the update on the internal. Mine is still Located just above my youtube and zedge files
Sent from my phone, not yours.
Click to expand...
Click to collapse
I did both ways and after I downloaded the file I placed in my internal memory by itself (not in a folder).
Sent from my Nexus S

isjr said:
I did both ways and after I downloaded the file I placed in my internal memory by itself (not in a folder).
Sent from my Nexus S
Click to expand...
Click to collapse
well your problem is you are running into a sig verification error. How many attempts have you made my way. I know that it has taken a few goes to do on occasion.
And I'm not guessing you are dumb but have you rebooted then gone back and did you use the zip I listed or the other pages zip?
Sent from my phone, not yours.

Try this
http://jaxov.com/2010/10/fix-android-no-signature-verification-failed-error/
Same thing about brick and hitting thanks button.
Sent from my phone, not yours.

Smartassassin said:
Try this
http://jaxov.com/2010/10/fix-android-no-signature-verification-failed-error/
Same thing about brick and hitting thanks button.
Sent from my phone, not yours.
Click to expand...
Click to collapse
This fix is for already rooted phones. The first thing it says is that they installed a recovery image but you can't do that unless your phone is rooted.

isjr said:
This fix is for already rooted phones. The first thing it says is that they installed a recovery image but you can't do that unless your phone is rooted.
Click to expand...
Click to collapse
oh. Welp I tried.
Sent from my phone, not yours.

I wondered he could adb push the SGS4G modded recovery so it wouldn't bother with signature verification
Sent from my SGH-T959V using XDA App

[Q] My phone took rom off itself

hi there i have my my touch 4g running jellybean 4.1.1 and some reason today when i went to go in the boot menu and change my splash screen it like restarted itself. Every time i try to click recovery in the boot menu it shows the pd15 files and then shows you need to update it. So basically i guess it went back to its original skin ,but still has everything. I see the s is off. Is there a way to be able to go back or do i have do the whole entire rooting process over again? I really appreciate all your help.

You need to remove the PDxx.img file from your SDcard otherwise evertime you go to the bootloader it will boot the stock ROM.
Sent from my HTC Glacier using xda premium

romuloxiii said:
You need to remove the PDxx.img file from your SDcard otherwise evertime you go to the bootloader it will boot the stock ROM.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Thanks for responding. Umm I'm kinda of confused are you talking about the PD15img.zip? Also, would it be hidden in a folder or just out in the beginning?

alex5p said:
Thanks for responding. Umm I'm kinda of confused are you talking about the PD15img.zip? Also, would it be hidden in a folder or just out in the beginning?
Click to expand...
Click to collapse
Pd15img.zip should be located in the root of your SD card.
Sent from my HTC glacier using xda premium

alex5p said:
Thanks for responding. Umm I'm kinda of confused are you talking about the PD15img.zip? Also, would it be hidden in a folder or just out in the beginning?
Click to expand...
Click to collapse
If you flashed a ROM of some sort using the PD15IMG.ZIP method (such as a stock Froyo or GB ROM), it exists in the root of your SD card (so, under /sdcard). You should see it by hooking up the phone and browsing to the top level of the card, or you could take the SD card out and examine it directly. If you don't rename if after an install, every time you try to boot the bootloader will look for it and try to reinstall it.
Whether you need to reroot again kind of depends on what the PD15IMG was. If you went back down to a stock ROM, then you would probably have to at least go through the rooting steps again (but not the S-off part).

cnote74 said:
Pd15img.zip should be located in the root of your SD card.
Sent from my HTC glacier using xda premium
Click to expand...
Click to collapse
Ok i found it and deleted it was the same thing. It would go back to stock ,but it actually showed a phone with a x on it . Thanks for your help
tuxkamen said:
If you flashed a ROM of some sort using the PD15IMG.ZIP method (such as a stock Froyo or GB ROM), it exists in the root of your SD card (so, under /sdcard). You should see it by hooking up the phone and browsing to the top level of the card, or you could take the SD card out and examine it directly. If you don't rename if after an install, every time you try to boot the bootloader will look for it and try to reinstall it.
Whether you need to reroot again kind of depends on what the PD15IMG was. If you went back down to a stock ROM, then you would probably have to at least go through the rooting steps again (but not the S-off part).
Click to expand...
Click to collapse
Yea i'm guessing ill have to root it again to get jelly bean back on. Thanks for the help

Alright so all day today i have been trying to get my phone working again and i can not get it to work. It still won't let me go into clockwork mod menu when you click recovery. when i click recovery it shows a phone with a red ! on it. I've tried factory reset ,full reset of phone and sd card and still not working. Anyone have any ideas why it won't work?

alex5p said:
Alright so all day today i have been trying to get my phone working again and i can not get it to work. It still won't let me go into clockwork mod menu when you click recovery. when i click recovery it shows a phone with a red ! on it. I've tried factory reset ,full reset of phone and sd card and still not working. Anyone have any ideas why it won't work?
Click to expand...
Click to collapse
I've only had that happen a couple of times when a ROM did not load successfully. Usually it's recoverable, but it sounds like in this case you *might* (I would ask somebody with more experience) need to reflash the CWM recovery via adb in order to get it working once again.

tuxkamen said:
I've only had that happen a couple of times when a ROM did not load successfully. Usually it's recoverable, but it sounds like in this case you *might* (I would ask somebody with more experience) need to reflash the CWM recovery via adb in order to get it working once again.
Click to expand...
Click to collapse
Yeah. The PD15IMG.zip put the stock recovery back on. Just flash the custom recovery of your choice.