Develop Bugs

Need urgent help

I just tried flashing the new wimax update and it went through and succeeded, but now my phone reboots after a minute or 2 once it's fully booted. If I'm in recovery mode it doesn't have that problem at all. I'm using baked 1.5.

michaelm718 said:
I just tried flashing the new wimax update and it went through and succeeded, but now my phone reboots after a minute or 2 once it's fully booted. If I'm in recovery mode it doesn't have that problem at all. I'm using baked 1.5.
Click to expand...
Click to collapse
Have you tried the standard "wipe cache and data, then reflash your ROM"?

Noxious Ninja said:
Have you tried the standard "wipe cache and data, then reflash your ROM"?
Click to expand...
Click to collapse
I have re-flashed the wimax radio and wiped the dalvik/regular chache and did a factory reset.

did you wipe? that will solve most of your problems with out the need of a thread being made.

DomSim said:
did you wipe? that will solve most of your problems with out the need of a thread being made.
Click to expand...
Click to collapse
First of all, mods please move my topic to Q&A. I did not mean to post this in this forum. Also yes I've wiped everything about a million times.

michaelm718 said:
First of all, mods please move my topic to Q&A. I did not mean to post this in this forum. Also yes I've wiped everything about a million times.
Click to expand...
Click to collapse
Did you try flashing an older version or a nandroid? If you are using clockwork make sure signature checking is turned on too, you could have a corrupted file.

xHausx said:
Did you try flashing an older version or a nandroid? If you are using clockwork make sure signature checking is turned on too, you could have a corrupted file.
Click to expand...
Click to collapse
I tried flashing an older version and that didn't work either. What is this thing about nandroid? How do I go about that?
Edit: I fixed it by restoring google proprietary stuff(forgot the name) and restored nand. Which one fixed it? I have no idea, but it basically restored me to factory 2.1, but with root access. Mods please lock/ delete this. It's in the wrong forum and I apologize. Thank you

michaelm718 said:
I tried flashing an older version and that didn't work either. What is this thing about nandroid? How do I go about that?
Click to expand...
Click to collapse
A nandroid is a backup of your system you can make from the recovery, it's always a good idea to make one before you flash anything. I'm not sure if that covers your radios though.
Do you use titanium backup or anything? Without knowing how your phone is set up (what recovery you are using, etc) the only thing I can think of would be to flash the engineering bootloader. That should fix it but you would have to reinstall your ROM afterwards.

xHausx said:
A nandroid is a backup of your system you can make from the recovery, it's always a good idea to make one before you flash anything. I'm not sure if that covers your radios though.
Do you use titanium backup or anything? Without knowing how your phone is set up (what recovery you are using, etc) the only thing I can think of would be to flash the engineering bootloader. That should fix it but you would have to reinstall your ROM afterwards.
Click to expand...
Click to collapse
The nandroid restore worked because I had a backup I made while following the guide. I fixed it doing that, but while trying to update the radio to the current one again figuring if it messed up I can restore it and again the same problem came up, but this time nandroid restore wont work and it's telling me to use adb restore, but adb says your device is not found.
BTW all of my phones stuff come directly from the idiot proof guide(recovery etc)

bump... I'm sorry I'm sitting here with a semi broken phone. Is it possible to download someone else's nandroid back up and install it on mine? I know it will fix my problem as it already did, but for some reason now it's telling me to do it with adb, but my usb seems to not be working either.

Doing a clockwork backup/restore, getting a weird msg???

When i restore or make a new backup in clockwork i get this:
No 1.26507E-306ame 3.54993E-308rip
I get this 5 times...
What is this? Anybody Know?
It doesn't seem to effect anything, just never got it before???
Thanks

Weird. At what point during the process do you get the error?
Do you get it if you advanced restore the various partitions?

I get it when I do a full back up and restore and data I think, I don't know what it is I'm think I'm going to start fresh and reroot my epic and put clockwork on again.

Yes, I know it is during backup or restore, but CWM tells you which partition is being backed up or restored, does it not?
It is going to be hard to get help if you can't provide some context on the error.

DiGi760 said:
Yes, I know it is during backup or restore, but CWM tells you which partition is being backed up or restored, does it not?
It is going to be hard to get help if you can't provide some context on the error.
Click to expand...
Click to collapse
Where does it tell me that and ill find it for you.

davidrules7778 said:
Where does it tell me that and ill find it for you.
Click to expand...
Click to collapse
Watch what it does during backup and restore. It should tell you whether it is backing up system, data, etc. What is it doing when it errors?

HELP NEEDED with CWM "error while restoring /data!"

Hey guys,
I have kind of a serious issue right now. I used Touch Recovery 5.8.0.2 and made a full backup today of my whole ROM (2.5GB) before trying out some mods which eventually didn't work. So I decided to wipe and restore the backup I made. No matter what I do I cannot get it to restore my data partition properly. I keep getting "Error while restoring /data!" message, however it does the boot image and system fine but doesn't continue to cache and sd-ext because of the failed data. Whenever I boot it up, some of my apps are missing from the home screen and practically all of them are not working when I launch them (force close). I also get boot up error of Google+ force close, among a bunch of other issues. This is happening even when I try to restore an older backup as well. My device is not working state right now and although I can just restore the stock images to get it working again, it is urgent that I restore my data ASAP! I tried wiping several times and even using the non-touch 5.5.0.4 recovery to restore and same thing keeps happening.
Any help would be highly appreciated!
Please don't tell me my backup is corrupt
Update 1: Eventually I gave up and started from scratch but I have confirmed already this happened on a fresh backup as well, at this time we are trying to figure out what is causing this so I can go back to safely backing up and restoring backups.
Update 2: We have test builds of TWRP Recovery that may have resolved this issue! We need testers!
Please see this post: Link Here
Update 3: We have test builds of ClockworkMod Recovery 6 that may have resolved this issue as well! We need testers!
Please see this post: Link Here
***Always see last few posts on the thread for updates on what we discovered just in case I don't update the OP***

Unfortunately I also have the same error today!
Please help us out.

JayantSparda said:
Unfortunately I also have the same error today!
Please help us out.
Click to expand...
Click to collapse
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?

Hi Spectre85,
My phone did fine yesterday, I was running AOPK Milestone 3 with FAUX123 kernel.
But when I woke up, my phone looked like it's battery was emtpy.
- When I plugged the phone with the charger, I started the phone again.
- Unfortunately my phone keep looping at the Google screen over and over.
So I pulled the battery and put the battery back again in the phone.
- I went to the bootloader and went to CWM recovery.
Deleted Data, Cache and Dalvike cache.
- Tried to retrieve my backup rom, but keep getting this "Error while restoring /data!" message.
I've tried to install other roms as well, but I still keep getting the bootloop at the Google screen.
Have you guys have any advice for me?

spectre85 said:
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Click to expand...
Click to collapse
For me, no, no (CWM Touch 5.8.0.2), yes (stock rooted 4.0.4), no but my goal is to restore my data not erase it.

I had this happen to me before, what I did was flash a factory image through fast boot and it was fine after.
Sent from my Galaxy Nexus using xda premium

Thanks guys..I flashed the factory image through Fastboot mode and the phone works perfectly again! Too bad I lost all my data, but I'm happier that I have my phone fully functional again

You can't access your backup right? There's no way you can copy the file to your desktop?

mohitrocks said:
You can't access your backup right? There's no way you can copy the file to your desktop?
Click to expand...
Click to collapse
I did copy it. I have full access to the file. Also, just fyi my goal here is not just to get to working state (I'm aware of the stock images) but to actually recover my data. My phone is currently on stock images completely blank and working now.

Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus

bwcorvus said:
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Nanadroid files can be flashed in fastboot? Are you sure? First time I'm hearing this. Doesn't fastboot need .img files? These are .tar files.

Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus

bwcorvus said:
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I guess it depends on the recovery version you use. I remember older versions actually had .img files. However 5.5.0.4 and Touch 5.8.0.2 both have ext4.tar files.
Which version of recovery do you use?

If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore

Immix said:
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Click to expand...
Click to collapse
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?

open1your1eyes0 said:
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
Click to expand...
Click to collapse
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.

Immix said:
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Click to expand...
Click to collapse
You're right. This works great for restore data to select apps (got my notes and game saves back). I think the icon layout is held in the launcher settings, I'm about to try and restore the data to the launcher app and see what happens. I'm making a CWM backup of first of my current state (that's assuming this backup will actually work).
EDIT: Yes! That did it! Widgets position weren't saved but it's ok I only had a few so I manually put them back. Thank you! I never knew TB had the ability to work with nandroid backups.

I guess this now just leaves me figuring out what went wrong with the CWM backup. It happened twice (I have two backups from the same day that won't restore). Does anyone else use CWM Touch 5.8.0.2 and have successful backups? I would experiment to see if it works now but I don't want to end up with a corrupt backup and redo everything again.

Yes with me its the same thing my data its corrupt is even worse every time I do a nanobackup and restarted my phone the phone freezes on the boot logo and I have to go back to recovery trying to use my backups but I can't so I have to flash a new from again and start from the beginning again!!!! Anybody here has the same experience with that ???

So AGAIN, I'm having the same issue. This time on a recovery 5.5.0.4 that used to work for me when I originally got my phone. I think either my data partition might be too big or something but this really needs to fixed pronto. Anyone know how to contact Koush directly in regards to this matter?

[Q] Cannot install from zip

Hi,
I have a problem. i currently have Codename ROM and I tried to flash new clock app from 4.2. I kept doing force close, so I wanted to restore my backup and it does not work - it says "MD5 mismatch", I cannot even make another backup, it looks like recover reboots. When I wanted to flash Codename again it said to me "Installation aborted, symlink: some symlinks failed (status 7)". Any idea how to get it all back to work?
Thank you!
EDIT: Great! Now I cannot even boot the system.

devcager said:
Hi,
I have a problem. i currently have Codename ROM and I tried to flash new clock app from 4.2. I kept doing force close, so I wanted to restore my backup and it does not work - it says "MD5 mismatch", I cannot even make another backup, it looks like recover reboots. When I wanted to flash Codename again it said to me "Installation aborted, symlink: some symlinks failed (status 7)". Any idea how to get it all back to work?
Thank you!
EDIT: Great! Now I cannot even boot the system.
Click to expand...
Click to collapse
Do you have a working Nandroid on your computer that you can push back into your phone and then restore (after wiping and formatting everything)?

dirtygoldfish said:
Do you have a working Nandroid on your computer that you can push back into your phone and then restore (after wiping and formatting everything)?
Click to expand...
Click to collapse
I managed to flash Codename ROM again but it seems that my recovery has problem with backuping and restoring. In fact my backups has around 25MB. It is a problem with backing up. I found this thread but I absolutely don't understand how to fix it. http://forum.xda-developers.com/showthread.php?t=714114

devcager said:
I managed to flash Codename ROM again but it seems that my recovery has problem with backuping and restoring. In fact my backups has around 25MB. It is a problem with backing up. I found this thread but I absolutely don't understand how to fix it. http://forum.xda-developers.com/showthread.php?t=714114
Click to expand...
Click to collapse
this has been covered in several threads.
the newer version of CWM (6.x +) create BLOBS and use a combination of BLOBS and your backup data to perform backups and restores.
if you deleted the BLOB folder from clockworkmod directory, that would be your problem. stating that you think the reason your backups are broken because of the filesize is just plain wrong.
also, md5 mismatch usually has to do with having invalid spaces or characters in the backup name.

Pirateghost said:
this has been covered in several threads.
the newer version of CWM (6.x +) create BLOBS and use a combination of BLOBS and your backup data to perform backups and restores.
if you deleted the BLOB folder from clockworkmod directory, that would be your problem. stating that you think the reason your backups are broken because of the filesize is just plain wrong.
also, md5 mismatch usually has to do with having invalid spaces or characters in the backup name.
Click to expand...
Click to collapse
In fact I do not know what BLOB folder is so I suppose I did not delete it. i did not even give my names to the backups. Sooo... what shall I do? I mean, I have wiped out the ROM and now getting everything back from scratch but I think I won't be able to make backups Thanks

Try the non touch versions of cwm or twrp.
Sent from my i9250

bk201doesntexist said:
Try the non touch versions of cwm or twrp.
Sent from my i9250
Click to expand...
Click to collapse
Thanks, man! That helps. Pushing thanks button

Note II Stuck on samsung logo possibly /efs issue?

Hi there,
I have spent hours trying to fix my issue that i am trying to fix and i was wondering if you guys could help me out?
A few weeks ago i went to go and plug my phone in as it was completely flat but for some reason it began some kind of boot loop where it would reach the lock screen for a few seconds and then power off again because it did not have enough power.
I left this on over night in the hope that it would charge my phone but when i tried to power it on in the morning it just got stuck at the Samsung logo. I did a quick web search and they suggested leaving your phone at the Samsung logo, clearing you cache/dalvic cache and finally resetting it. After all of the above failed i thought that maybe a a full restore in odin would work, the same thing happened when i tried to power it on.
I then went back into the stock recovery after the reset to find the error "E: failed to mount /efs (invalid argument)".
After quite some research into this i found a possible zip that may fix the issue from people having a similar issue but of coarse it diddn't work.
It seems as if the /efs folder/partition may be corrupted in some way.
I am really stuck on this now and i am reluctant to pay lots of money to someone to fix it
Do you have any ideas?
Many thanks,
Shenstone
EDIT: The phone has CWM recovery installed and i have attemped to flash the stock firmware with both Kies and Odin

Bro, maybe flash stock firmware will solve the prolem

exorcistz said:
Bro, maybe flash stock firmware will solve the prolem
Click to expand...
Click to collapse
Sorry forgot to mention that, i have flashed stock firmware with both odin and kies but both do not work, same process still occurs
Any other ideas? :/

Do you have the original EFS folder backed up? If so, then try restoring it and flashing a stock ROM... If you don't have your EFS backed from earlier you might have some problems, I don't know if it's possible to fix it then...

librapt said:
Do you have the original EFS folder backed up? If so, then try restoring it and flashing a stock ROM... If you don't have your EFS backed from earlier you might have some problems, I don't know if it's possible to fix it then...
Click to expand...
Click to collapse
I didn't specifically backup the EFS folder, however I performed a full backup in CWM recovery. Do you know if there is a backup of the EFS folder there?
Just a quick question, is it possible to re-create a EFS folder or not?
Many thanks!

shenstone said:
I didn't specifically backup the EFS folder, however I performed a full backup in CWM recovery. Do you know if there is a backup of the EFS folder there?
Just a quick question, is it possible to re-create a EFS folder or not?
Many thanks!
Click to expand...
Click to collapse
See this, http://forum.xda-developers.com/showthread.php?t=2420881

shenstone said:
I didn't specifically backup the EFS folder, however I performed a full backup in CWM recovery. Do you know if there is a backup of the EFS folder there?
Just a quick question, is it possible to re-create a EFS folder or not?
Many thanks!
Click to expand...
Click to collapse
I use this,
http://forum.xda-developers.com/showthread.php?t=2269318