Database Users

Only Boots into Recovery

I was having some pretty serious problems with Bionix 1.7 (couldn't download from market, unusably bad GPS, etc), which I thought I had successfully flashed yesterday afternoon. I decided to use Clockwork Mod to restore a backup I made before I flashed Bionix. This hung up for quite a while (upwards of 20 minutes) so I figured something had gone wrong. I held the power button until the screen turned off, and that put me right into Android Recovery, where I get the options to reboot (puts me right back there), reinstall packages (puts me into Clockwork Mod, which I'll get to in a second) or delete user data / cache, which I haven't messed with.
If I go into Clockwork Mod, I can tell it to try to restore one of my previous backups again, but it hangs up indefinitely (upwards of several hours) at "Restoring data..." (with either immvbsd.lck or .pc_syncstream below that). I can also still see the Bionix .zip on my SD card, but when I tell Clockwork Mod to install that .zip it gets this far:
Formatting DATA:...
Copying files...
E:Failure at line 81:
copy_dir PACKAGE:data DATA:
Installation aborted.
Ideas?

Okay, so apparently, the problem may have been that I didn't disable the Voodoo lagfix before I flashed back to my old ROM. I figured you only had to disable the lagfix if you were upgrading, not flashing back. So, I used ADB to push a disable-lagfix file to /sdcard/voodoo and rebooted. I heard Linda say that my file system converted back to RFS, and my phone went back to recovery. From here, I tried two things:
1. Attempted to flash back to a previous Nandroid backup. No matter what backup I pick (and I have several), they all complete successfully. However, when I choose to reboot my phone, it boots into recovery.
2. Attempted to install Bionix 1.7 though Clockwork. It appears to install successfully and gives me an "Installation complete." message, but puts me right back in recovery. Rebooting the phone from here puts me back into recovery again.
Since I'm on a mac right now, I'm really avoiding having to get on a Windows machine just to use ODIN, but I will if that's my only way out. Any alternatives?

opiomorph said:
Okay, so apparently, the problem may have been that I didn't disable the Voodoo lagfix before I flashed back to my old ROM. I figured you only had to disable the lagfix if you were upgrading, not flashing back. So, I used ADB to push a disable-lagfix file to /sdcard/voodoo and rebooted. I heard Linda say that my file system converted back to RFS, and my phone went back to recovery. From here, I tried two things:
1. Attempted to flash back to a previous Nandroid backup. No matter what backup I pick (and I have several), they all complete successfully. However, when I choose to reboot my phone, it boots into recovery.
2. Attempted to install Bionix 1.7 though Clockwork. It appears to install successfully and gives me an "Installation complete." message, but puts me right back in recovery. Rebooting the phone from here puts me back into recovery again.
Since I'm on a mac right now, I'm really avoiding having to get on a Windows machine just to use ODIN, but I will if that's my only way out. Any alternatives?
Click to expand...
Click to collapse
Unfortunately it sounds indeed like you need to use ODIN to flash and re-partition your phone's file system. You're going to need to make sure you use the stock rom (JFD) to do this, other wise you'll be stuck in the recovery loop yet again with a different error message.
So far as being on a Mac goes, I've heard that some people have luck using ODIN through the newer version of parallels. Or you could of course just boot camp your machine if you happen to have a copy of Windows laying around. Parallels sounds like it might be the easier solution if you don't want to go through th hastle of installing a full blown windows load.
Just my .02 cents!

cathardicnotion said:
Unfortunately it sounds indeed like you need to use ODIN to flash and re-partition your phone's file system. You're going to need to make sure you use the stock rom (JFD) to do this, other wise you'll be stuck in the recovery loop yet again with a different error message.
So far as being on a Mac goes, I've heard that some people have luck using ODIN through the newer version of parallels. Or you could of course just boot camp your machine if you happen to have a copy of Windows laying around. Parallels sounds like it might be the easier solution if you don't want to go through th hastle of installing a full blown windows load.
Just my .02 cents!
Click to expand...
Click to collapse
Using ODIN worked. Thanks for the reassurance. :3

Help Please! ROM won't install (nor will backup) Stuck at Fastboot

Hey guys,
I finally decided to root my eris today. I used the revoked method on my mac and everything worked flawlessly. I then downloaded a ROM FroShedYoV7 and followed the installation steps. About half way through I received the error symlink /system/xbin/busybox SYSTEM:xbin/arp. I then tried a few different ROMs and received the same errors. I did a backup beforehand; however, I can not even restore to that. I was going to use the RUU method on my school's PC (I have a mac) but when I tried it, it was unable to recognize that the phone was connected - probably because it stuck at the fastboot screen. I still have access to the recovery though.
I did a little research on the matter and found that chrome sometimes messes up zips so I tried it with firefox and had no success.
Any help would be appreciated, I just want my phone back rooted or not.

what recovery are you using?
first, i'd pull the battery, re-insert and then try booting into recovery (volume up + power)... then, full wipe and try to flash again. are you verifying the md5 of the download to ensure it's not bad?
if you happen to be using clockwork, i think there is a thread that discusses cleaning some things up... i'll see if i can find it.

I'm not sure what you mean by verifying the md5, but I have tried multiple ROMs downloaded by multiple browsers. And also I did full wipes before each attempt.
I also just attempted this fix the RUU ROM rename to PB00IMG.zip fix, but had no luck.
Thanks for your help!

Also, I am using clockwork.

Use RA... CW has issues
Sent from my ERIS using XDA App

Try this thread and good luck.

[solved] need help recovering epic 4g after trying to install a ROM

Sadly, I have goofed up my phone right out of the gate. I do not think it is bricked, but I'm unsure how to proceed and more than a little spooked by how quickly things went from great to non-functioning.
I took my stock Epic 4G and followed a tutorial to install Froyo. That went without a hitch. I then used noobnl's one-click script method to root the phone, and that also seemed to work well.
Then I tried to install the Nebula ROM with DK28 modem and pit, using Odin3 v1.61. Since then, my phone will not boot past the Samsung logo. I can still get into Clockwork, but repeating the ROM installation process has not made any difference. I then noticed that I'm running Clockwork Mod Recovery v2.5.1.0, when Nebula apparently requires v2.5.1.5 or newer.
So can anybody help me fix what I've broken? I've tried searching the forum for this problem, but have not been able to find anyone with my particular form of stupid.
Thanks in advance for suggestions.

Cincinnatux said:
Sadly, I have goofed up my phone right out of the gate. I do not think it is bricked, but I'm unsure how to proceed and more than a little spooked by how quickly things went from great to non-functioning.
I took my stock Epic 4G and followed a tutorial to install Froyo. That went without a hitch. I then used noobnl's one-click script method to root the phone, and that also seemed to work well.
Then I tried to install the Nebula ROM with DK28 modem and pit, using Odin3 v1.61. Since then, my phone will not boot past the Samsung logo. I can still get into Clockwork, but repeating the ROM installation process has not made any difference. I then noticed that I'm running Clockwork Mod Recovery v2.5.1.0, when Nebula apparently requires v2.5.1.5 or newer.
So can anybody help me fix what I've broken? I've tried searching the forum for this problem, but have not been able to find anyone with my particular form of stupid.
Thanks in advance for suggestions.
Click to expand...
Click to collapse
Odin back to this http://forum.xda-developers.com/showthread.php?t=794138 then root using this http://forum.xda-developers.com/showthread.php?t=770388 then install this if you want cw3 and ext4 if not skip it http://forum.xda-developers.com/showthread.php?t=897612 but check on the rom ur flashing because most rom are now using ext4 and cw3. Also if you want and ur rom has the option for no journaling flash this before flashing a rom http://code.google.com/p/bonsai/downloads/detail?name=ext4-format_nojournal-1.1.3.zip&can=2&q= . I know Bonsai and Midnight roms have the option for it. Well best of luck to you and if you have any question or concerns please post them here and ill or one the many helpfull people here at xda will assist you.

Thanks, asj2583, for the quick response. For whatever reason, it did not occur to me to try putting the phone in download mode!
So to get the phone back on-track, I:
1. Started Odin3 v1.61
2. Removed the SD card from the phone
3. Plugged the Samsung USB cable from the phone to the computer (which is running 32-bit Windows Vista)
4. Clicked on 'PDA' in Odin3, then selected the Froyo TAR that had worked before, then I clicked on 'START.'
5. Let Odin3 do its thing, and now my phone is back up and running unrooted Froyo.
Moving forward, I:
1. went here and downloaded One Click Root 2.5.5.
2. On the phone, went into Menu/Settings/Applications and enabled 'Unknown sources,' then unplugged the USB cable and clicked on /Development to enable USB debugging and Stay Awake.
3. I plugged the USB cable back into the phone and ran the 'run.bat' file I extracted from the One Click Root 2.5.5 download. In short order my phone rebooted into rooted Froyo. (confirmed by going into Applications and seeing that 'Superuser' is installed)
Now it's time to set up CW3 and ext4:
1. I went here and downloaded a different One Click Root (anyone know if I could have used this instead of 2.5.5?).
2. Again, with USB debugging enabled and the USB cable plugged in, I clicked on 'run.bat' extracted from the One Click Root CWM3 download. After a brief wait, the phone rebooted. Theoretically, at this point I have Clockwork Mod 3.0.0.5 and my phone can handle ext4 filing. (Speaking of ext4, I thought that was intended for handling LARGE files on teranyte-plus HDDs. How is it the right choice for a smartphone?)
And to try a new ROM:
1. I went here and downloaded CyanogenMod 6.2 prebeta 14 and saved it to the root directory of my phone's SD card.
2. Powered down the phone, and reinserted the SD card.
3. Powered up into ClockworkMod Recovery. The screen showed that it was running v3.0.0.5. ClockworkMod automatically checked for ext4 but failed to mount. ClockworkMod suspected my files are still in rfs (admittedly, I never reformatted my SD card to ext4). ClockworkMod created a backup named 'before-ext4-convert-1296478915' in case I need to restore. At this point, I found myself in ClockworkMod's menu.
4. In ClockworkMod, I ,ped data/factory reset 3 times, cache partition 3 times and, under /Advanced, wiped Dalvik cache 3 times. I then went back to install zip from SD card and chose the CyanoGen Mod I wanted to try, but it failed. ClockworkMod noted that Amend scripting (update-script) is no longer supported and that I need to switch to Edify scripting (updater-script and update-binary) to create working update zip packages. So I went back to my SD card and told ClockworkMod to install gapps-hdpi-20101218-EPICv1.0.3.zip, which completed without error. Then I told ClockworkMod to install NebulaMod. The phone rebooted and all seems well.
Thanks! I sure was stuck last night, and just needed a nudge in the right direction.

Whoah. Whatever you do, don't follow my advice. This just bricked the phone. It will not even power up any more. Damn.
Correction. Not bricked. Just really, really scary. Thanks to Koadic I'm back at unrooted Froyo. I think maybe I'll stay here for a while.

Cincinnatux said:
(Speaking of ext4, I thought that was intended for handling LARGE files on teranyte-plus HDDs. How is it the right choice for a smartphone?)
Click to expand...
Click to collapse
Ext4 wasn't intended solely for handling large files. It made some changed to ext3 that allows handling of larger files and also increases the subdirectory limit, which makes it suitable large files or large disks. Ext4 also added journaling. These are not the reasons we use ext4 on our phones. I think all of our ext4 roms mount the disks with the noatime flag, and many people are running the no-journal mod. This makes ext4 act more like ext2 with the ability to allocate extents instead of individual block.

"Amend scripting (update-script) is no longer supported and that I need to switch to Edify scripting (updater-script and update-binary) to create working update zip packages."
My phone also says this when I try to install the Truly-Epic rom. I'm on DK28 like the rom says to be on, and on CWM3 and EXT4...yet...it doesn't want to install. Anyone know what for or what might be any problems?

how long did it take for your phone to power up after rooting with ext4 and cwm3? mine has been at it for a while now. i flashed back to stock dk28 using odin and did the process over and it gets stuck backing up my information and just keeps creating before ext4 back ups til my memory is gone

Need Stock-i500-VZW-Kernel.tar.md5

Hosed my Fascinate by trying to flash a recovery through Odin -> The recovery also had a kernel in the file that I didn't realize. Phone attempts to boot then reboots into recovery. I would prefer not to do a factory reset until I try reflashing the right kernel.
I am aware of this thread that used to have the file I need, but evidently the guy has removed it from his Dropbox now. Does anyone have a copy they can throw up for me? I think I could use the recovery image, too, but it is a little bit easier to find so don't go to great lengths for the recovery.
Will reflashing the correct kernel even fix my problem? I haven't touched /system. Should all my stuff still be there when I get back in?

Skyroket said:
Hosed my Fascinate by trying to flash a recovery through Odin -> The recovery also had a kernel in the file that I didn't realize. Phone attempts to boot then reboots into recovery. I would prefer not to do a factory reset until I try reflashing the right kernel.
I am aware of this thread that used to have the file I need, but evidently the guy has removed it from his Dropbox now. Does anyone have a copy they can throw up for me? I think I could use the recovery image, too, but it is a little bit easier to find so don't go to great lengths for the recovery.
Will reflashing the correct kernel even fix my problem? I haven't touched /system. Should all my stuff still be there when I get back in?
Click to expand...
Click to collapse
If you have access to your sd card via windows, look for http://forum.xda-developers.com/showthread.php?t=1459905 on kernels. The stock is in post 1 at the bottom with the rest of the links. Download it, copy to your sd card and install it via recovery and it should work. If not, find droidstyle's guide, download the CWM 2.5 flash that in Odin, then install kernel.
Sent from my SCH-I500 using XDA App

Edit: Got it. Thanks!! It's booting up fully!!
Nothing below this line matters anymore, but I am leaving it for Google arrivals. The problem I list in this post was caused by excessive copying of the files. I first downloaded the file from the internet, copied it from Firefox downloads folder to my desktop, copied it up to my LAN server, copied it over to my Motorola Droid Bionic SD card, unmounted the SD card and put it into the Fascinate for installation.
The RIGHT way that worked was removing the network component. I just plugged the Bionic into the PC and mounted USB storage mode, copied files over, unplugged, let the SD card remount on the Bionic, manually unmount on the Bionic, remove the card and put it into the Fascinate.
Thanks for being patient with me. Your thread is obvious at the top of the forum but I ignored that method because it was flashing zips in recovery, which I couldn't get into at the time. I got the CWM 2.5 to work, and I did make a successful nandroid backup (will a factory reset restore the kernel, now that I have a backup?).
I did try to flash both versions of that stock kernel kernel-eh03-GB.zip and kernel-eh03-GB_signed.zip and get the same error on both. I even tried with a different SD card:
-- Installing: SDCARD:kernel-eh03-GB.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/kernel-eh03-GB.zip
(bad)
Installation aborted.​
I've tried downloading the files again, too. I wonder if it's worth noting that I did previously try to mount the SD card to Windows from CWM. It mounted, but when I tried to copy the file over, Windows told me the media was write-protected. WTF? Haven't seen that since floppies.
I think I'm going to call it a night and if I don't hear anything else on this in the morning I'll just do a factory reset and see if that restores the kernel. Then I can reinstall CWM and restore my backup. *long sigh*
Thanks again, man.

Skyroket said:
Thanks for being patient with me. Your thread is obvious at the top of the forum but I ignored that method because it was flashing zips in recovery, which I couldn't get into at the time. I got the CWM 2.5 to work, and I did make a successful nandroid backup (will a factory reset restore the kernel, now that I have a backup?).
I did try to flash both versions of that stock kernel kernel-eh03-GB.zip and kernel-eh03-GB_signed.zip and get the same error on both. I even tried with a different SD card:
-- Installing: SDCARD:kernel-eh03-GB.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/kernel-eh03-GB.zip
(bad)
Installation aborted.​
I've tried downloading the files again, too. I wonder if it's worth noting that I did previously try to mount the SD card in CWM. It mounted, but when I tried to copy the file over, Windows told me the media was write-protected. WTF? Haven't seen that since floppies.
I think I'm going to call it a night and if I don't hear anything else on this in the morning I'll just do a factory reset and see if that restores the kernel. Then I can reinstall CWM and restore my backup. *long sigh*
Thanks again, man.
Click to expand...
Click to collapse
Thats alright, dont worry about it man. Yeah it does sound like you need a factory reset. your phone isnt accepting the download. for ****s and giggles tho, try not using CWM to put the file onto your SD card, and plug it directly into your computer and redownload and transfer that way and see if it takes, if not then you'll definatly have to factory reset. Go here http://forum.xda-developers.com/showthread.php?t=1238070 Follow section 4 to return to stock. That should fix it.

Please note my previous edit. Thanks, again!

Skyroket said:
Please note my previous edit. Thanks, again!
Click to expand...
Click to collapse
Lol didn't see that till after I clicked reply. No problem. Glad you got it working bro
Sent from my SCH-I500 using XDA App

[Q] Defy restoring itself to old ROM automatically!!!

Hi All,
I am new here and this is my first post. But i have been reading this forum for quite sometime and know that u guys are now my final stone. I am a proud owner of a Motorola Defy. And I am having this strange behavior, which is effectively rendered the phone almost useless. The phone is acting like its got a restore point in itself, and every time i restart.. it gets back to that point in time.
This includes app installs, uninstalls, stuff placed in system through adb push, theme, everything in the OS. I tried installing a different ROm through clockworkmod, but its not taking effect. Its saying install success but as soon as it restarts, its going back to the old ROM. (takes time to load, so i guess it reinstall back/restored the old version)
Details of device : I am from India and the phone was manufactured in India in around April/May 2011. Its a red lens Defy and and came with Eclair. I updated it officially to the first Froyo release for SEA region. After that i rooted the phone with superone click, and installed WIUI rom. I have been updating the ROM with newer versions around each month. The last one was 1.11.18 though as i waiting for a good ICS version to flash.
The problem occurred after i started installing some gold apps from getJar. It restated in between and install... and that point is kind of acting like a restore point even now.
Things I did: Tried installing different rom by CWM method. Reinstalling second init and CM, both old and new version. Tried restoring nandroid backup of my official ROM. Tried fixed and full sbf flash through rsdlite 4.9.5.2 and now 5.6. First 3 things reset as soon as i restart. For RSDLite, it gives checksum error for each and every ROM i tried. I tried all SEA releases, JORDN_U3_97.21.51, Defy Plus Rom 2.3.6, 2.21 first eclair rom, everything gives the same error. From the RSDLite logs, i could see that there is something wrong as.. say the last successful CG was 33, and the error came for 34, the log says its expecting the checksum on the sbf to be equal to that of CG 33. Its taking the last successful checksum validation and expecting that for all the CGs henceforth. its not showing what the device actually has.
I atlast could somehow, but trial and error, removed all the CGs which were throwing error, and recompiled the sbf to make it pass the RSDLite flash. The CGs present in the ROM (JRDNEM_U3_3.4.3-36-1.7) were 32, 34, 42, 53, 61, 64, 65. And as soon as it booted, it restored back to the checkpoint. Even after i formatted by card and put it in, the app shortcuts remained on the home screen, but as the apps on the card were gone, they are just junk and doesnt open anything.
Thanks in advance. Please let me know what you need from me to help me resolve this issue.

Any help... Anyone?

Can someone please suggest something?
This is what i got from some people. I am not sure how far this is possible, but somehow the theme i installed just before this all happened, from MIUI market.. somehow managed to change something inside phone's kernel, past the locked bootloader? I am totally a noob in this and just a wild imagination?
Or may be some sort of cache wipe is happening everytime the phone boots up, So even when i install the ROM, when it boots up, it gets back the old ROM.. like what would probably happen if i do a factory reset soon after i instal a rom before the restart..?
I would really appreciate it if anyone could help me out with this...

Checksum errors were for me also.
I tried my office computer for flashing and instantly flash was done. The checksum error occurred 7 times on my good computer before that.
Reflashing froyo must take care of all errors happening

Thanks Kapil fr the response. Are you from india? Which sbf did u flash? And waht all did u install in the office pc? I have a pc of my friend where i can try to reflash if you tell me the exact steps that u took in the fresh pc.
Also, can anybody tell me how to use adb commands in CWM mode? Its recognizing my phone in normal mode but as soon as it boots in Moto recovery of CWM, its not recognizing anymore. Want to use adb format commands from recovery.

Hi I was able to use adb in CWM, but format commands were not working. How can i format the system partition? please help me with this.

Is there anyone here who know how to restore a nandroid backup manually using adb commands for MB525???!!!!!

Sounds weird and impossible. Try this. Wipe everything though cwm and flash new rom. Try ms2ginger.

Thanks darshanonline for the suggestion. I tried to wipe everything.. factory reset+cache+dalvik cache wipe. And then tried to install cyanogenmod 7.1 as well as 3 different wiui builds. Everytime it shows that the install was successful, ut as soon as i restart, it would go back to the old ROM.
Is there any checkpoint system in android, seeing the init.rc, i can see comments on something about saving a checkpoint. Is there any particular condition under which this checkpoint may be getting used on very restart?
Also.. is there any way for RSDLite to skip the chksum validations and get the install anyways?.. Some sort of a hack into it?

Ok.. Found something else thats happening. I dont need to shutdown for the system to revert back. Say i install a few things new after a reboot.. After some time.. 1 day at max, i am not able to open them, and neither am i able to open manage applications or market. Everything force closes. I have Ti Backup installed, and i opened it, and i didnt find the new apps to back up. I connected the device and checked through adb, and they were not present in the app folder. They just vanished... So basically after a certain point of tiime, the new stuff just gets deleted on its own.
Guys i know i may sound dumb and stupid with my questions, but i really couldnt find any solution on the net for this. Please tell me waht i should do, and i'll do it. But tell me something. Dont ignore please!

and you did wipe data from within stock recovery (vol down+power etc.), i presume..
Sent from my MB526 using Tapatalk

Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.

Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834

Soumik84 said:
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Click to expand...
Click to collapse
DL WIUI 1.12.16 ICS > copy to SD card > Boot in CWM > select zip to install > Install WIUI 1.12.16
Hopefully your problem should be solved.
I found 1.12.16 ICS with lesser FC than the 2.21

labsin said:
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Click to expand...
Click to collapse
Thanks for the link. Now i know that i am not the only one having this issue. But even there its not resolved yet.

@ headers.chennai - Thanks. I will try that ROM, along with Pikachu ROM with Aroma installer, might be a different installer can try fix it?!
BTW.. does anyone have the TI OMAP board utility? Any chance that it can be available outsite here?

I tried the arora installer and it supposedly formatted the system partition and remade it.. but as soon as it finishes and i restart.. I get back the same ROM.
Is it some way that the files are not getting deleted, like some hardware lock or fault?

Soumik84 said:
I tried the arora installer and it supposedly formatted the system partition and remade it...
Click to expand...
Click to collapse
Hi, bro! What is "arora"? I should try it asap, and all other chance.
My trouble here, same as your.

Hey man.. looks like we are having same problem...
Sorry abt the typo... its Aroma Installer. Its with the Pikachu ROM in this link :
http://forum.xda-developers.com/showthread.php?t=1498843
Its a new installer that launches from cwm when u try and install this ROM. u got some options to select and on selecting the complete install option,, the log shows that it formats the system partition and then creates it. I saved the log file, but for some reason the file shows up blank now. Might be problem with the launcher.. or my phone.. dont know.

Soumik84 said:
Its a new installer that launches from cwm...
Click to expand...
Click to collapse
Not for me, my checkpoint without cwm