Hello,
I'm trying to flash a custom ROM. I'm at the point of installing 3e recovery. The issue is after I put 3e recovery in /system/bin I cannot boot into recovery (it is stuck at the Samsung screen) and when I boot into my phone I have no WiFi access even though WiFi is successfully connected.
Help please?
Thanks!
Scratch that. I did a factory reset and used Root Explorer instead of ES File Explorer this time and everything is working as intended.
Root explorer is always recommended glad things worked out!
Sent from my Infuse running Malvarious v1.5(coming soon)
Related
I was running 3.0.1 unlocked/rooted, Tiamat's 1.4.1 kernel. I followed the steps to update to 3.1 from here, and had no issues what so ever. This was earlier this week, and today I was going to run fix permissions in recovery. I used Quick Boot (also tried Reboot to Recovery in ROM Manager) to boot to recovery, and I got to the Android with the exclamation point...
I tried sending the modified 3.0.2.8 recovery listed in the Dev Forums using fastboot commands, and everything went smooth with no errors, but still got the Android/exclamation point.
I tried reflashing recovery via ROM Manager, and it wouldn't pop up anything, so I uninstalled/reinstalled, and the flash of recovery worked. Boom! Recovery is back! So I can do what I need (run fix permissions), and rebooted the device.
I try to reboot into Recovery again, back to Android with exclamation point. Any thoughts here as to why I must do this, and thoughts to what I can try to make Recovery "stay"?
Thanks!
RMarkwald said:
I was running 3.0.1 unlocked/rooted, Tiamat's 1.4.1 kernel. I followed the steps to update to 3.1 from here, and had no issues what so ever. This was earlier this week, and today I was going to run fix permissions in recovery. I used Quick Boot (also tried Reboot to Recovery in ROM Manager) to boot to recovery, and I got to the Android with the exclamation point...
I tried sending the modified 3.0.2.8 recovery listed in the Dev Forums using fastboot commands, and everything went smooth with no errors, but still got the Android/exclamation point.
I tried reflashing recovery via ROM Manager, and it wouldn't pop up anything, so I uninstalled/reinstalled, and the flash of recovery worked. Boom! Recovery is back! So I can do what I need (run fix permissions), and rebooted the device.
I try to reboot into Recovery again, back to Android with exclamation point. Any thoughts here as to why I must do this, and thoughts to what I can try to make Recovery "stay"?
Reflash cmw afterward and it should stay.
Thanks!
Click to expand...
Click to collapse
Use your computer to do this:
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
or alternately, you can use a root file manager such as root explorer to remove the files (I personally just renamed mine so they wouldn't be recognized. I don't like burning bridges).
Re-flash cmw afterward and it should stay.
Thanks! That worked, you the man! I renamed them as well, as I don't want to burn bridges either.
Rooted with SuperOneClick
Copied krylon's recovery to /system/bin/
Used ROM Manager to flash CWM
Stuck at boot screen
Tried removing SD. No difference.
No combination of buttons boots into recovery.
Replaced update.zip on SD with krylon's update.zip. No difference.
Can anyone help me fix this?
Kuzar said:
Rooted with SuperOneClick
Copied krylon's recovery to /system/bin/
Used ROM Manager to flash CWM
Stuck at boot screen
Tried removing SD. No difference.
No combination of buttons boots into recovery.
Replaced update.zip on SD with krylon's update.zip. No difference.
Can anyone help me fix this?
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=wU2nzNC_Cvs&list=UU2-cnU5RP_yQ
Follow that video & ODIN your phone back to default .
Download Link = http://www.megaupload.com/?d=KLDZATSY
It take's phone back to default , reroot with oneclick , CWM again , Check Mount's before flashing .
UNMOUNT CACHE
MOUNT DATA
MOUNT SDCARD
UNMOUNT SYSTEM
Then you can flash .
If you still need help shoot me a PM
Im trying to flash the Clockwork Recovery mod to my sidekick but every time I boot in recovery I keep getting the stock recovery screen. First of all I rooted my phone using the latest version of SuperOneclick Root. Once the phone was rooted I installed both root explorer and rom manager.
I downloaded the modified binary recovery file and replaced it in system/bin using Root Explorer. I used Rom manager to flash the CWM and it supposedly intalled it (it says version 4.0.0.2). I tried to reboot on recovery but it doesnt boot the CWM recovery screen. I the tried donwloading the CWM and placing the update.zip file in the root of my SD card. I then rebooted into recovery and selecte reintall packages and i get the following:
E: signature verification failed.. installation aborted?
Im guessing its the binary recovery file that's causing the problem but I've tried replacing the file again and it wont work. Anyway, does anyone have any idea whats going on and how I can successfully install the clockwork recovery mod??
Yes that would say that it isn't using the correct modded recovery binary. use my modded oneclickroot script to push the correct recovery and update, and it should work.
http://forum.xda-developers.com/showpost.php?p=15831175&postcount=124
Thank you so much it worked like a charm!! One question, every time I boot in recovery now, it boots in the stock recovery. In order to boot CWM i have to select reinstall packages every time is this normal??
Currently that's normal. I've got the same thing on mine.
sly_fox said:
Thank you so much it worked like a charm!! One question, every time I boot in recovery now, it boots in the stock recovery. In order to boot CWM i have to select reinstall packages every time is this normal??
Click to expand...
Click to collapse
Yes that CWM is a fake flash and doesn't actually replace your stock recovery so you would have to reinstall packages everytime, unless you flash bali kernel which has the red CWM that replaces the stock recovery when you boot into recovery mode
Sent from my SGH-T839 using XDA App
EDIT: sniped by ayoteddy.
That is normal, as that script uses the "fake flash" instead of having CWM built into the kernel.
A fake flash technique uses a modded recovery binary that doesn't check for signature verification, allowing us to boot into CWM from a stock looking recovery, even on a stock kernel.
In order to have recovery boot straight to CWM, you need to have it built into the kernel, which currently only exists on the Bali kernel (as there's no need to build it for another kernel).
I've now flashed the recovery using both rom manager and fastboot 4 times, and each time it works fine the very first time after, but then the 2nd and succeeding times after lead to the little android and then the triangle and exclamation point. This is with the latest clockwork 3.1.0.1 on a Nexus S 4G. I have no idea what the problem could be and I'm hella frustrated.
Thanks for any help you can provide in advance.
http://forum.xda-developers.com/showthread.php?t=856999
Trying this, will update with results after I just try flashing cyanogen.
EDIT: UPDATE problem solved after flashing cyanogen. Sorry for taking up extra space. Here's the fix incase others were searching.
-Flash recovery
-Enter recovery while it's still working, nandroid backup, wipe, flash cyanogen.
-Done
If that doesn't work use the commands from that link.
The problem is solved cause CM fixed it for you.
If you don't have a ROM fixing it for you (eg stock Android), you need to rename the install-recovery.sh inside /system/etc to something else to make a recovery stick through reboots. Renaming system data requires root/super user.
The order would be:
Flash recovery
Flash su.zip
Boot into Android
Use a root explorer (eg Super Manager or Root explorer) to rename the file above
Flash recovery again
Hello,
I installed a custom ROM on my samsung infuse some months ago.
I wanted to install a new one and in the process, I bricked my phone.
I used ODIN3 v1.7 software to unbrick my phone but now I am not able to install the CWM recovery.
I tried following things:
1. Used ROM Manger app to install CWM recovery but no success. It does
not pass the SAMSUNG screen
2. Deleted the file /system/bin/recovery and then started the process but
no success. It does not pass the SAMSUNG screen
3. Copied the CWM recovery onto /sdcard and tried to install it but it
errors out with some permission issue.
Please let me know how do I fix this problem?
Try this it has always got me out of this type of situation.
http://forum.xda-developers.com/showthread.php?t=1116251
Thank you very much for the help.
I have tried this but did not help me.
I will try it again and see if I am able to flash ClockworkMod Recovery.
This is what I did:
I unbricked my phone using the link.
http://forum.xda-developers.com/show....php?t=1116251
Then, I rooted my phone using SuperOneClick.
Then, using the ROM manager, I downloaded the CWM recovery.
While I was trying to install it, I got "Signature invalid" error.
Hence, I 3e modded my phone by deleting the recovery file /system/bin and copying the recovery file from the following location into /system/bin
http://forum.xda-developers.com/showthread.php?t=909213
Now, when I tried to reboot my phone and enter into 3e recovery, the phone starts and it does not pass after SAMSUNG black screen.
Am I doing some wrong?
http://www.youtube.com/watch?v=Y09p-J_g_Rg&feature=youtube_gdata_player do these
Sent from my SGH-I997 using xda premium