I rooted phone unlocked the phone and i am getting an error 7 message!
Tried to flash 2.3.6 still getting error.Wiped data off still getting error!
I have been searchine over 5 hours to find a clear solution but i am confused!
Can anyone give a hint!
Nexus s 4g
I even tried to install pixel rom 1.7 and i get the same problem error status 7??
WTF???
Also i flashed the cwm recory and every time i reboot it get me the ics recovery which gets me a blank screen.I even flashed cwm touch worked the first time rebooted and then the default ics recovery menu with the blank screen.Its seem that my phone cant hold the cwm recovery menu?
Any suggestions?
Distro123 said:
Also i flashed the cwm recory and every time i reboot it get me the ics recovery which gets me a blank screen.I even flashed cwm touch worked the first time rebooted and then the default ics recovery menu with the blank screen.Its seem that my phone cant hold the cwm recovery menu?
Any suggestions?
Click to expand...
Click to collapse
if you have stock ics then it will automaticly disapear. you have to have a custom rom if you want it to stay
Sent from my sandwich using a Nexus S
tjackbjorn said:
if you have stock ics then it will automaticly disapear. you have to have a custom rom if you want it to stay
Sent from my sandwich using a Nexus S
Click to expand...
Click to collapse
But how can i install a custom rom it i end up with a error 7 ??I tried beside 4.0.4 ,Gingerbread and 4.0.3. to instal pixel 1.7 but i end up with the same error 7 !
Distro123 said:
Also i flashed the cwm recory and every time i reboot it get me the ics recovery which gets me a blank screen.I even flashed cwm touch worked the first time rebooted and then the default ics recovery menu with the blank screen.Its seem that my phone cant hold the cwm recovery menu?
Any suggestions?
Click to expand...
Click to collapse
To boot up from CWM Recovery with Active Stock recovery(Stock script not modified)
From CWM app
1) Click flash CWM image one more time, regardless previous recovery image
2) Click Reboot to recovery, you will see CWM recovery screen..the identify for CWM recovery is the cool man with hat icon.
I have used above steps to go to CWM Recovery for long compared to those recommendation of modifying stock recovery script..the problem of modifying the stock script is overtime you have forgotten what have been changed from stock..the next Manual update of Google Official patch which will give error.
Distro123 said:
Also i flashed the cwm recory and every time i reboot it get me the ics recovery which gets me a blank screen.I even flashed cwm touch worked the first time rebooted and then the default ics recovery menu with the blank screen.Its seem that my phone cant hold the cwm recovery menu?
Any suggestions?
Click to expand...
Click to collapse
1) update to 4.0.4 you can use these instructions: http://andwise.net/?p=275.
Once you update that you will have another recovery image anyway.
2) the recovery image is coming back becuase you probably have this:
Code:
service flash_recovery /system/etc/install-recovery.sh
in your init.rc(in boot image)
you cn either change your boot image and comment this line or just rename or replace the /system/etc/install-recovery.sh.
For any of these you need root access.
I advise not to do that as you may need the stock recovery to get updates.
Related
Hey everyone,
Basically I was trying to flash a new ROM onto an old Nexus S of mine and when I tried to boot into recovery there was just a black screen. I pressed the power button and a single line saying "Clockwork mod Recovery" and the version number popped up. I assumed that the recovery must've been corrupted so I erased it and installed the latest version using fastboot which seemed to work fine.
Now whenever I try to boot into recovery I just get a blank screen with nothing else. I've tried using other recovery images such as twrp but the same problem happened, I just get the background wallpaper/image and nothing else.
I searched the forums and apparently people were having this issue earlier on when the i9023 was first released but now most custom recoveries are supposed to work with both i9020 and i9023.
Also the touch buttons light up and vibrate whenever I touch them when I'm in recovery mode.
Any help to this problem would be greatly appreciated as atm I have an old ROM which is buggy as hell and I need to get rid of it.
Cheers!
I had the same Issue. If you can boot into the rom, you can try to download the rommanager-app and install the recovery from there.
Hey I tried that already that and instead of booting into recovery it just went into the bootloader and said "No Recovery or Bootloader found".
Any other ideas?
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Hey
I have the i9023 and I install rom manager. install CWM and if I reboot into recovery it works and I get in to CWM recovery.. but after reboot into os.. if I go into Rom manager and reboot to recovery it dont work? I just get the android figur and a "!".. then I just can Power + vol up and I'm in bootloader recovery..
Do I have to install CWM every time i want to use it? and can't I access CWM on boot op ?
sorry for my bad English
Normaly you have to flash the recovery only once.
Try to flash the newer clockwork-recovery with fastboot.
http://forum.xda-developers.com/showthread.php?t=988686
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
bedalus said:
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
Click to expand...
Click to collapse
I havent unlock my phone, but I can get in to bootloader is it then necessary to unlock ?
I try to delete the /install-recovery.sh
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Xziped said:
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Then it must be unlock as default.. I havent unlock it.. just delete the install install-recovery.sh and it works every time now.
now I just have to find a ROM to try..
Xziped said:
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Simultaneity said:
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Click to expand...
Click to collapse
what happens when you try to temporary boot into the recovery?
instead of "fastboot flash recovery recovery.img", try to "fastboot boot recovery.img"
Just look for an recovery.img that works temporary and then try to flash it permanently.
I'll try it and get back to you Xziped. If anyone else can think of any other ideas please just throw'em at me, I'm willing to try anything!
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Simultaneity said:
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Click to expand...
Click to collapse
Sorry but if not even the temporary recovery boots up, i dont know what else we can do
did you try some of the older recoverys? is your bootloader unlocked?
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Simultaneity said:
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Click to expand...
Click to collapse
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
khartaras said:
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
Click to expand...
Click to collapse
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Simultaneity said:
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Click to expand...
Click to collapse
Just look @ http://www.samfirmware.com/ .
There you should find all you need
Sent from my Full Android on Crespo using XDA App
Recently, i upgraded my nexus s I9023 from 2.3.6 to 4.0.3 . But i did that with the fault of upgrading it with a different OTA version as suggested for my phone. The problem is that i cannot load into the boot recovery mode , can i install any recovery modes nor can i downgrade my phone to 2.3.6 without the boot loader .
Any answer would be helpful ...
Btw thanks for ur help.
if possible suggest me how to boot into the correct version or just help me downgrade to gingerbread.
How is the file called, you installed?
Overall I think you have the right version, if everything except the recovery mode is working.
All i9023 have this problem with the official OTA update (look in those threads).
If you really need it for wiping or so on, you could use a bright (LED) flashlight and illuminate the screen from the top then you can hardly see the menu points.
If you have an open bootloader you can flash a custom recovery as well.
I have the exact same problem. Even if flashing CWM recovery and superuser, once the OTA 4.0.3 boots it cripples the custom recovery. Very annoying!
It is like in Gingerbread...
you have to rename "/system/etc/install-recovery.sh" to "/system/etc/install-recovery.sh.old" for example
coolfranz said:
How is the file called, you installed?
Overall I think you have the right version, if everything except the recovery mode is working.
All i9023 have this problem with the official OTA update (look in those threads).
If you really need it for wiping or so on, you could use a bright (LED) flashlight and illuminate the screen from the top then you can hardly see the menu points.
If you have an open bootloader you can flash a custom recovery as well.
Click to expand...
Click to collapse
thanks for the post buddy . but i really think i ve booted with the wrong unofficial OTA update for my phone . I actually have downloaded the version for my phone but the problem still remains is that i can boot into my recovery mode nor can i go for CWM recovery on my phone. it is as if i m stuck with the 4.0.3 version. on the added problem is that i dont have any roms installed on my phone ..
Thanks for the reply
I actually have downloaded the version for my phone but the problem still remains is that i can boot into my recovery mode nor can i go for CWM recovery on my phone. it is as if i m stuck with the 4.0.3 version.
Click to expand...
Click to collapse
Does the phone boot, so you can use it?
Can you boot in the bootloader mode (power on the phone while holding the vol+ button)? When yes what says it about its version?
i can boot into the boot loader but cant boot into the stock recovery mode
It's already been answered in this thread. New recovery turns off the backlight for the SCLCD on the i9023. Strong flashlight at the right angle will show you whats on the screen. To install a new recovery you need an unlocked bootloader and you need to rename /etc/install-recovery.sh to something else (which requires root).
i tried with the strong flash light but it cant be seen . I ve the unlocked and rooted nexus phone . I tried renaming the file with the file ("/system/etc/install-recovery.sh) via the root explorer but it seems it cannot be renamed bcoz it is read only and i cannt change it to read\write option in the root explorer app.
can u suggest any other way of doin so where i can get back to the android 2.3.6 version
Reboot into bootloader and use fastboot to flash cwm, then install your rom of choice without rebooting.
It's much more convenient to remove the recovery from stockrom's zip before flashing it. It's in its own folder, just delete that. And if you really want it perfect, remove the corresponding lines from update-script (optional). No new recovery, no script.
But I guess you need bootloader unlocked for this (to flash a then wrongfully signed rom in this case).
I have a new Transformer TF101 that I rooted with vipermod.
I tried installing CWM using the recovery installer at http://forum.xda-developers.com/showthread.php?t=1346180, but it kept giving me parsing errors when I tried to run the apk. This happened when I copied over the su from bin to xbin.
So I tried Rom Manager to install the CWM there, but when I try to boot into it, it would get stuck saying Booting recovery kernel image.
If I try to use the Transformer Reboot to Recovery app, it gets stuck at the boot screen and goes into a semi reboot loop where If I try powering it off, it automatically powers on again and I had to do a data wipe to recover.
Does anyone have any idea how I can solve this? I really don't want to be stuck on Android 3.1 forever since it won't update to ICS with the stock update either now.
The android version is 3.1, Build is 8.4.4.11.
Thanks!
I know you already tried this installer, but check out this link.
You could also try using ADB to install the CWM recovery: link.
Read through there and follow the instructions around step 6 since you're already rooted.
If this doesn't work:
Does the ASUS recovery not work at all? As in holding vol-down while powering on then pressing vol-up to enter recovery? If it does you could try an update.zip to flash back to the old stock version that supports old razorclaw and use that to flash recovery reroot and pop a ROM on there (stock rooted ICS or otherwise) I'll give further help if you have to resort to this. ToD
xelloss12 said:
I have a new Transformer TF101 that I rooted with vipermod.
I tried installing CWM using the recovery installer at http://forum.xda-developers.com/showthread.php?t=1346180, but it kept giving me parsing errors when I tried to run the apk. This happened when I copied over the su from bin to xbin.
So I tried Rom Manager to install the CWM there, but when I try to boot into it, it would get stuck saying Booting recovery kernel image.
If I try to use the Transformer Reboot to Recovery app, it gets stuck at the boot screen and goes into a semi reboot loop where If I try powering it off, it automatically powers on again and I had to do a data wipe to recover.
Does anyone have any idea how I can solve this? I really don't want to be stuck on Android 3.1 forever since it won't update to ICS with the stock update either now.
The android version is 3.1, Build is 8.4.4.11.
Thanks!
Click to expand...
Click to collapse
Your firmware is to old for RecoveryInstaller to work. Manually update to latest ICS, root with ViperMod and use RecoveryInstaller for CWM.
Thing O Doom said:
You could also try using ADB to install the CWM recovery:.
Read through there and follow the instructions around step 6 since you're already rooted.
Click to expand...
Click to collapse
This worked! Thank you very much!
Hey guys,
I recently rooted my Galaxy Tab 2 P3110 , then installed CWM, and then went on to install the Cyanogen Mod 10.1.3. Installation was succesful .I then used the tablet for about 5-6 hrs before i restarted it. Now the tablet is stuck showing the Cyanogen logo. I have waited for an hour and still nothing happened.
When i tried to enter the CWM recovery mode, i end up getting the ODIN screen or the stock recovery mode.
Any ideas as to how i can resolve this issue.
Thanks in advance
Does it bootloop or just stick at boot animation?
If it's stuck at animation you may be able to adb push recovery.
sent using logic and reason from a device forged of witchcraft.
tokenpoke said:
Does it bootloop or just stick at boot animation?
If it's stuck at animation you may be able to adb push recovery.
sent using logic and reason from a device forged of witchcraft.
Click to expand...
Click to collapse
It just stuck at animation.
I don't know the Windows process of an adb flash of recovery.
You can also try to flash it with odin
sent using logic and reason from a device forged of witchcraft.
tokenpoke said:
I don't know the Windows process of an adb flash of recovery.
You can also try to flash it with odin
sent using logic and reason from a device forged of witchcraft.
Click to expand...
Click to collapse
I tried the ODIN method. I first downloaded the stock rom and then used ODIN to flash it. It says Pass in the ODIN App but when the device reboots, i still get the cyanogen logo which goes on forever..!!
I had the same issue with being stuck at the cyanogenmod boot animation. I went back into recovery, did a wipe data/factory reset. Once I did that, I flashed the .zip file from my sdcard and it worked fine. As far as your installation of CWM, you must have not installed it correctly. I use Philz Touch Recovery for my P5113.
Hi,
My wife just got a new phone and gave up her old XT925 so I thought I would try to put CM or SlimKat on it and let my daughter play around with it. But I'm having trouble putting a custom recovery on it. I've unlocked the bootloader. I've used fastboot to write the recovery image...but when I try to reboot directly into recovery so the binary update can complete, it pauses for a couple of minutes and then reboots the OS normally. If I try entering reovery after that, I end up with the dead android with a red exclamation point in him and "no command" written below.
The phone currently has 4.4.2 and System 181.46.3.XT925.RCI.en.CA. Am I out of luck with this device and stuck on 4.4.2?
Thanks!
What recovery did you try to flash ?
Use this one, it worked for me :
http://forum.xda-developers.com/showthread.php?t=2747535
Thanks. That one worked. I wonder why I had trouble with twrp.
Orionbell37 said:
What recovery did you try to flash ?
Use this one, it worked for me :
http://forum.xda-developers.com/showthread.php?t=2747535
Click to expand...
Click to collapse
pls update the link pls
Pausky said:
pls update the link pls
Click to expand...
Click to collapse
Its because you need to rename the stock recovery to .bak at the end of the file name. The stock recovery is getting in the way of you rebooting to TWRP or what ever custom recovery you are trying to use.
If you cant figure out how to do that or don't know where in system the stock recovery is just hit me up and ill give you the path to the file. After you rename the file just go back into fastboot and reflash the custom recovery and you should be able to reboot into TWRP or what ever custom recovery you want.