I wanted to download the new update for our phone, so last night, I backed up with Titanium Backup and ROM Manager. Then, I used SL4A to undo the ext4 lagfix, as I was told that I had to do. Now, my phone won't boot. It gets to the S screen, pulses for while, and goes dark.
This is what I backed up for, right? But I can't seem to boot into ClockworkMod recovery. Pressing power+volume keys just gets me into the normal Android recovery screen. And since I don't want to reinstall packages, try another reboot in vain, or delete all user data, I'm kind of at a loss.
Can anyone help me?
If i've understood correctly, Clockwork doesn't play well with ext4, so that may be what you're running into. Shouldn't be too big of a deal, just use ODIN3 to reflash JF6 (DON'T MASTER CLEAR- just flash JF6). You should be able to do this by 1. Starting ODIN3, 2. Get your phone to the stock recovery screen and then hooking up your USB cable, 3. Start up an ADB Command Line and type in 'adb shell' (enter) and then 'reboot download' (enter). Your phone should reboot into download mode (big yellow triangle) and be picked up by ODIN3. Click 'start' on ODIN3 and wait for it to reflash JF6. When it's done, try downloading the update again. If it doesn't take (don't be surprised) just download it from the development forum and flash it using Clockwork. (You'll have to re-root, re-download and install Clockwork). Once you have JH7, re-root, re-download and install Clockwork and Titanium again, and then use the batch method to put your apps and settings back on. Let me know if you run into anything and I'll see if I can help.
-ok, just double checked, and you'll run into permission issues if you try to type 'adb shell' and then 'reboot download'. Instead, just type in 'adb reboot download' at the C:\...\tools> prompt. It gave an 'error: protocol fault <no status>' message in the command window, but the phone went into download mode 3 out of 3 tries.
had a similar issue last night. went from cog 2.1 back to JH7 and didnt fix the voodoo issue which left me in the same position. you just have to reflash to JF6 with Odin and you'll be set.
1. make sure you have the usb drivers installed
2. open odin
3. turn phone off (pull battery if needed, and replace)
4. hold both volume keys while inserting usb cable to phone (will put phone into download mode, huge yellow triangle on screen)
5. odin should now recognize the phone/com port.
6. hit 'Start', not Master Wipe or w/e the other button is.
after all said and done you'll have flashed JF6. Now re-root phone, download rom manager and restore one of your backups and you're back in business. good luck.
I just found myself in this same position, but I removed the EXT2 lagfix via SL4A and ended up with a phone that had to be reflashed - it went dead, wouldn't get past the glowing S, then black screen. Reflashed, I then recovered later via Titanium backups.
Then get this... once I flashed with Odin, I got hit with an OTA update... which I cancelled. Then I was dealing with an almost bricked phone. So I had to finagle my way into getting to where Odin would reflash the phone (I was lucky) and then I went straight to Cognition 2.1 to avoid the OTA, and I've been setting up everything else since. I've recovered my apps, et al... and tweaked it like I once had it.
There should be a way to avoid this in the future - I hate setting everything back up - but I got hit with a SL4A issue too.
Thanks a lot, guys. I'm going to use Odin3 as soon as I get home from work! Then, should I just try SL4A again to un-lagfix, or what? It's my understanding that the update doesn't play well with ext4.
Nope, once you've reflashed JF6 with ODIN3, you should be back to stock with no SL4A if i'm not mistaken. If your goal was to just have JH7, i'd make sure to delete any folders SL4A might have put on your INTERNAL SD card storage (don't know if it does, never used it), and don't do a nandroid restore- that will put you back to where you were right before the problems started. Your apps and settings should be ok, just get to JH7, reload your apps and settings, THEN do a nandroid backup before you try anything else so that you basically have a fresh JH7 install with all your apps and settings as a starting point for future tinkering.
-Ok, just read a post from Rajendra82 in the Development forums discussing this type of thing. It's the "Noob needs your help to understand" thread, and on page 2 he discusses this same situation in pretty good detail. I'm pretty sure I read that SL4A gives you two choices to lagfix- ext2 and ext4. If you chose ext2 you'll probably be ok, but if you chose ext4 you may infact still have issues with trying to use ODIN3. Go read that thread for more info, maybe even PM Rajendra82 since he seems to have a pretty good understanding about this. Good Luck.
Thank you, samoled! It's all fixed. Good lord, what a pain in the backside.
I (eventually) managed to flash a fresh JF6 install with Odin3. Tried the update the regular way; it failed. So I rooted, then used ClockworkMod to load the update from my SD card. Rooted again, got Busybox, enabled app sideloading, got Titanium backup, and finally ran the batch and restored everything. Phew.
I hear voodoo's a much less buggy way to do the lagfix (I used the Tayatumi update.zip last time). I think I'll use that - after backing up, of course!
No problem at all man, just glad I could help. Happy Modding!!!
Sent from my SAMSUNG-SGH-I897 using XDA App
Related
I am very new to this - my first time rooting a phone. I followed the guide and everything seemed to work perfectly until I got to the step to make a Nandroid backup. I get an error: "Error : Run nandroid-mobile.sh via adb!"
I then tried re-booting without making a backup but my phone just hangs at the white HTC screen. I tried cleaning off my 2GB sd card via USB-MS toggle and deleted everything except for the files put there at the beginning of the process. But had the same error when I attempted a Nandriod backup.
Next, I tried running the backup via adb but got an error that the Device or Resource is Busy.
I really need a working phone fairly quickly and am ok without having an original backup if that is what I have to do.
Could someone please give me a hand?
jasonnelms said:
I am very new to this - my first time rooting a phone. I followed the guide and everything seemed to work perfectly until I got to the step to make a Nandroid backup. I get an error: "Error : Run nandroid-mobile.sh via adb!"
I then tried re-booting without making a backup but my phone just hangs at the white HTC screen. I tried cleaning off my 2GB sd card via USB-MS toggle and deleted everything except for the files put there at the beginning of the process. But had the same error when I attempted a Nandriod backup.
Next, I tried running the backup via adb but got an error that the Device or Resource is Busy.
I really need a working phone fairly quickly and am ok without having an original backup if that is what I have to do.
Could someone please give me a hand?
Click to expand...
Click to collapse
How much free space is on your SD card?
Kcarpenter said:
How much free space is on your SD card?
Click to expand...
Click to collapse
1.81 GB currently. I have even tried flashing a couple of ROMS but when they finish, I choose Reboot and it still sits on the White and Green HTC screen.
Have I bricked it?
jasonnelms said:
Have I bricked it?
Click to expand...
Click to collapse
Highly doubtful.
1. Reflash your recovery image
Code:
flash_image recovery /sdcard/recoveryfilename.img
2. Try a Nandroid (if it fails oh well, too late now)
3. Wipe everything under the Wipe menu when you get into it.
4. Reflash your rom
5. Reboot - It really could take up to 20 minutes some times.
if it still wont reboot:
6. Power off
7. Take the SD card out.
8. Reboot.
If it still doesn't boot post back.
Kcarpenter said:
Highly doubtful.
1. Reflash your recovery image
Code:
flash_image recovery /sdcard/recoveryfilename.img
2. Try a Nandroid (if it fails oh well, too late now)
3. Wipe everything under the Wipe menu when you get into it.
4. Reflash your rom
5. Reboot - It really could take up to 20 minutes some times.
if it still wont reboot:
6. Power off
7. Take the SD card out.
8. Reboot.
If it still doesn't boot post back.
Click to expand...
Click to collapse
-Ok, tried reflashing recovery but it said header is same, not flashing recovery.
-is the rom I need to reflash the boot-patched.zip file?
Thanks for all of your help. I don't know what happened on this one but it got hosed somewhere in the process!
Hoping I can get it running again soon as it is my only phone and I have 2 kids at home.
UPDATE
Ok-
Loaded the 1.6.2 Recovery. It allowed me to run a NAND Backup.
However, after loading the ROM I still end up locked on the White background with the Green HTC letters on it?
Any other ideas? I have not seen anything like this googling and reading forums.
Try taking the battery out for a minute. I would just reroot from scratch and follow the directions step by step.
-------------------------------------
Sent via the XDA Tapatalk App
How would I reroot from scratch? I can only get into recovery mode. Is there a way to do it that way?
Try this thread.
http://forum.xda-developers.com/showthread.php?t=657086
Me personally, I would unroot, then root all over again.
-------------------------------------
Sent via the XDA Tapatalk App
This phone had 2.1. That is a guide for older versions. Plus, I can't get into the OS to make the changes to debugging and such. I only have access to Android System Recovery.
I should also mention that the command adb devices returns a
000000000000 Recovery
Is this normal? It is in recovery mode so, I am not sure.
I am starting to think it is a brick.
Hi guys...
First off, i'm somewhat of a noob. Got my N1 already rooted a few months back but i've tried many different ROM's since. I'm using Clockworkmod Recovery.
I was running Cyanogen 6.1 yesterday and wanted to create a backup of stock froyo for gingerbread's release.
So, i did a backup of Cyan 6.1 and followed the following steps off Android Central's forum.
Step One
Download this file. It's the flashable, stand alone version of FRG33.
You can't go straight back to FRG83 using this method. Just trust us.
Place the PASSIMG.zip file on the root of your SD card.
Power off your Nexus One, then hold volume down while pressing the power button.
Your phone will spend a minute or so looking for an update file (the PASSIMG.zip file).
When it has the info it needs, it will ask if you would like to install it. Press the volume up key to choose to install the file.
Your Nexus One will take another few minutes installing the update, then it will reboot.
Let it reboot the whole way, then go on to step two.
Step two is for the update to FRG83 which i did.
The phone boots and runs fine...
But ever since I did all that, my N1 looks like its unrooted. I can't use ROM manager, Titanium backup to restore since they all tell me they don't have su rights. I installed Superuser from the market. It opens but does nothing with my app's rights.
adb can't find my device when I try to list it (adb devices). Neither can Fastboot (fastboot devices), in fastboot mode.
I see the padlock at boot
I can't go into recovery. I get the robot with an exclamation mark. If i hit the power and vol-up I get the android system recovery menu (in blue) with only 4 options; reboot, apply sdcard:update.zip, wipe data/factory reset and wipe cache partition.
I've tried rooting it with Universal Androot but it failed.
I've no idea where to go from there...
Please help!
You have to root again. Use the rageagainstthecage exploit.
Sent from my Nexus One using XDA App
Ok... N1 is rooted using VISIONary.
However, I can't boot into recovery mode (clockworkmod). I still get the exclamation mark.
If I try to use adb, i always get an error: device not found.
If I try to unlock with fastboot oem unlock, i get a waiting for device message but it never finds anything....
Almost there... i think!
Ok... using Clockworkmod, flashed recovery and all is good!
Thanks for your help!
i had network problems (3g stopped working, don't know why), and had an old version of doc's. so i figured i'd install the new version after a wipe, see if that'd fix it.
just to be safe, i went in recovery (clockwork) and restored an earlier backup. it worked, but still no internet. upon remembering that this was the backup i made just after installing docs, i went back to my previous backup, stock rom, i think 2.1.
this is where stuff went wrong. i hadn't disabled the lagfix (forgot which one, i remember i had ext4 as filesystem), and now, no matter what i do, my phone won't go past the boot screen. big lettering galaxy s, smaller gt-i9000 and at the bottom samsung, you know the one.
i tried everything i could imagine. wipe data/factory reset, wipe cache partition, re-restore to the oldest backup. only then did i remember the lagfix and remove it. retried all of those, still no dice.
i can get into recovery mode, both clockwork and 2e, and i can get into download mode.
when i connect my phone to my pc, it doesn't notice. when selecting mount in clockwork, it mounts, and shows the two drives in my computer, but when i try to open one of the drives, i get nothing.
i installed docs rom a while back, and have wiped my pc since then, so i have no files from that. i have installed the android sdk, but don't know how to use it, let alone how to use it with a phone that doesn't show.
all i want is to get back to stock, for now. try again from there.
can i? or have i ruined my phone?
edit:
wow... take about relief.
i used odin to flash xxjpu, 2.2.1, and it seems to have worked!
in case anyone else is stuck on a boot screen, download mode with odin means you're safe.
anyone with more sense than i showed in my stupidity, sorry for adding another semi useless topic.
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Titerepayaso said:
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Click to expand...
Click to collapse
Sounds pretty accurate. You'll have to get a jig to get in download mode, flash stock Odin KK4 to fix w/e happened during your testing.
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Titerepayaso said:
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Click to expand...
Click to collapse
Make a backup with ADB.
Once that's done, push download mode with it and get Odin KK4 (without bootloaders). You'll have to start from there to fix w/e went wrong.
You don't have to wipe your sd doing so but you will lose your apps and such. If you backed up your phone with your Play Store account, it will re-download your apps as you're done booting up.
To get back up where you were, grab Corn Kernel, flash it with Odin 1.87 and then follow the full instructions of the ROM you wanna use.
Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.
ktvanhorne said:
Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.
Click to expand...
Click to collapse
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.
BWolf56 said:
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.
Click to expand...
Click to collapse
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT
ktvanhorne said:
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT
Click to expand...
Click to collapse
My guess is that something got corrupted, so yes, software issue. Find the required Odin and 2.3 kernel for the I9000 and flash them in download mode. It should run fine after that.
Got things resolved
Thanks for the help. I tried to follow your steps, but I could never get the phone connected to the PC. It would charge, but not connect to let Odin in. (It will connect to another PC without issues. I uninstalled and reinstalled the drivers, but no dice). However, in the process of putting the phone into download mode and rebooting it back somehow got me into the recovery screen. I did a factory reset through there and it worked.
Thanks for the help of all the contributers to the site.
K