Hello,
Sorry if this has been posted already , but i couldnt find anything similar.
When i flash something, from cwm, it does not make any changes.
When i flash a other rom, the old rom boots,
Kernel, the old kernel remains
I had the new Cwm 5.5.0.4? With the reboot problem.
So i installed a rom, which i found in dev section wthat included a older cwm 3.3.0.4 or something.
The reboot problem still remains, so i can only start with holding volume down and do a cold boot.
So if i try to flash the new fixed cwm, trough cwm or rom manager, still the old cwm shows up.
(Rom manager actually sais the new version is installed :S )
Also i tried alot of wipes, clear cache and dalvik before flashing, but this makes no difference.
When flashing i dont get any errors, just normal, like everything goes well.
Can someone help me out?
Thanks
Go here
http://forum.xda-developers.com/showthread.php?p=23256536
Yes i readed that thread, but has this anything to do with my rom and kernel not changing after flashing?
Firstly : is it even showing the flashing being done in the recovery? Should show loading bar and tell you what its doing.
Second : baseballfan is showing that thread because there's probably issue with your recovery.
Also, maybe you can just use gnufabios app in app thread " recovery installer ". It flashes roaches working cwm recovery for you, real easy. Download apk, open and hit install
Sent from my SGH-T959 using xda premium
Yeah you have a bad recovery, after flashing a "good" recovery you still need to
use terminal to remove the "bad" recovery or you will still be at square one.
Yes, the flashing of a rom or anything else goes like usual.
I will try to fix the cwm and see if it helps the problems with my tf stuck on a rom and kernel.
Hello guys,
I made some progress,
If i flash a kernel , it does successfully flash it.
When i go to recovery, it now sais : ClockworkMod Recovery v5.5.0.4
So thats better then before,
But now i have the following problem.
It still boots to the recovery if i dont hold vol. down.
I readed the instruction from the thread : http://forum.xda-developers.com/show...php?p=23256536
I flash the zip : cwm_recovery-5504_roach-tf101-r2.zip
Then when i try to ADB : adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
it gives me the error : Write error : No space left on device
I searched all threads on XDA, and i found that this error is normal because there is no space defined.
But after a reboot, it still doesnt boot the R2 recovery.
Just the old one
Anyone that has a solution?
Related
Hi guys,
For the last 2 nights I´ve been trying to get a CG Mod 6.1 on my HTC Magic 32B.
I have rooted it with onclick-root method and tried a bunch of things like ROM Manager and flashing via fastboot (brings up "remote not allow" error). Nothing worked out.
Here are the facts:
HTC Magic with OTA upgrade to 2.2.1
hboot: 1.33.0013
radio: 2.22.28.25
Rooted with Oneclick method
Do I need a goldcard? How do I do that? What hboot Version do I need? What Radio do I need? What do I have to do first?
Are you certain the Root took? Are you seeing the Superuser icon in your app drawer?
When you were using Rom Manager did you flash, or attempt to flash a custom recovery, and if so did it install ok?
What happened when you tried to flash a ROM using Rom Manager?
I'm sure we'll get to the bottom of this
Yes, rooting has worked...Icon is there everything looks fine.
With the Rom Manager i tried to install "update-cm-6.1.0-DS-2708port_S" aswell as the "update-cm-6.1.0-DS-signed". Both did not work.
I still can boot to my standard OTA 2.2.1
Try wiping your phone in recovery and then install the rom
hang on a minute...
it sounds like you haven't installed a custom recovery before trying to flash the rom. Can you clarify...have you actually done this yet?
The process should go root/recovery/nandroid backup/rom in that order.
yeah you re right...i dont have a custom recovery
i just tried to load "recovery-RA-sapphire-v1.7.0G.img" on the console
su
# flash_image recovery /sdcard/recovery.img
does not work, i get: flash_image: not found
USB debugging is enabelde
3rd party software is enabeled
is there another way to get flash the recovery ?
Rom Manager!
At the top you should have the option to flash clockworkmod recovery. Select that; it will run and then the phone should reboot. I usually do it again to confirm. If it installed correctly the first time you'll get a pop up saying that it is installed.
If all goes to plan select 'backup current rom' from within Rom Manager. This is a nandroid backup and can be re-installed from recovery any time you wish to return to stock.
NOW you are free to install a custom ROM of your choice
Post back if you encounter any issues.
I have tried that. It flashes, gives my a popup that it installed correctly.
But it does not reboot.
When i choose restart in recovery mode it boots up the phone an gets stuck on the vodafone logo. BatteryOut reboot and i am back at the good old 2.2.1 OTA
do i have to wait long?!? cant be, right? do i need to hold down any buttons?
If you try the backup option now you'll soon find out if the recovery did indeed install ok. (it won't backup if the recovery isn't installed)
i restarted...flashed the recovery again. got popup confirmation. then chose backup rom and got stuck at the vodafone logo
You must be pretty frustrated by now. It might be time to start asking for more help in the dev section of the Magic forum HERE.
I hope that somebody has the answer!
Thanks for your help...i ll see if someone else has any ideas.
roodee said:
yeah you re right...i dont have a custom recovery
i just tried to load "recovery-RA-sapphire-v1.7.0G.img" on the console
su
# flash_image recovery /sdcard/recovery.img
does not work, i get: flash_image: not found
USB debugging is enabelde
3rd party software is enabeled
is there another way to get flash the recovery ?
Click to expand...
Click to collapse
Are you are aware that the command you need to type will be
flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img
The command points to the exact file name on your sd card so if you just wrote flash_image recovery /sdcard/recovery.img and the recovery file was not called "recovery.img" it would not know what to look for.
I'm not sure if this is what you have or whether you just copied and pasted from a guide, but I just thought I'd put it out there in case that is the case.
Hope this helps.
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
hi there
when i try to install the new recovery with:
1.: Rommanager it makes the update but i cant boot into recovery
2.: i tryed to install it with: "flash_image recovery /sdcard/name-of-recovery.img"
but both ways are not working ..
so what to do?
thx
flo
There is now 5.0.1.0 update posted on koush's page (Google Nexus S):
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
You can open Android Terminal app and type the following commands:
su
flash_image recovery /sdcard/recovery-clockwork-5.0.0.0-crespo.img
reboot recovery
Click to expand...
Click to collapse
I was able to update via ROM Manager successfully though (it will take quite awhile to switch from Google logo to boot animation on your first reboot).
i allready tryed that terminal thing .. last time it worked (3.0.0.5 to 3.0.2.4) but this time .. no chance ..
the update with rom manager dindnt work on my Nexus S anyways .. i dont know why ..
i tryed that with different roms ..
i had such a problem on my Desire like a year ago and than i had to delete a file .. i cant remember but is it possible that i have to delete the file here too?
thx
flo
ok .. in this Thread:
http://forum.xda-developers.com/showthread.php?t=1039584&page=5
i found this:
"anyone having issues with recovery flashing open rom manager and press menu and go to settings. now check erase recovery. this will wipe the recovery partition prior to flashing. this makes the recovery img flash correctly 99% of the time. if not on the main page in rom manager press menu and clear your download cache. this will remove all the files and folders inside /sdcard/clockworkmod/ so you will los e any roms downloaded. then click to flash the recovery again. it will redownload the recovery and reflash. you should still keep the erase option in settings checked. if it still does not flash correctly try flashign twice in a row. if that doesnt work fastboot erase recovery . and fastboot flash recovery \path\to\recovery\here.img"
delete recovery BEFOR flashing a new is working here ...
Flash_image gui by Joeykrim will work great for you
I did an update to v5 and couldn't boot into recovery too, but that was because i did it by the usual hardware buttons Power + VolumeUp.
Then by accident, i was able to boot into recovery, and that is by the "Reboot into Recovery" menu in ROM Manager itself.
Have you tried this method of rebooting yet?
the new cwm flashed fine for me no issues.
I can no longer reboot into recovery after updating to CWM5.01. Tried using rom manager and terminal emulator with no luck. Also tried reverting back to my old recovery and still nothing. The above steps posted didn't work either. Someone please help. I can't restore any backups because I can't boot into recovery.
Edit: Working and fixed by pushing it through adb
Hi guys!
Yesterday I successfully rooted my NS (it is a European SLCD model with stock 2.3.6 on it) following the newest guide on nexusshacks.com. So I ended up with TWRP recovery.
Then I thought the easiest to install CM is via Rom Manager. Therefore I had to change recovery for CWM. (I flashed the latest one.)
And here comes my question: why am I unable to flash CM?
First I tried it in Rom Manager, after wiping everything and rebooting system nothing happens, except for a big yellow exclamation mark.
Then I downloaded the proper CM myself and I tried to do the whole process manually in recovery menu. After wiping and choosing update from SD card I get a message like the process is aborted.
I also tried with an older CWM and with other ROM.
Any suggestions?
Thanks a lot
Sent from my Nexus S using XDA App
Boot into bootloader, then flash recovery via fastboot.
fastboot flash recovery recovery.img
stock firmware will rewrite your recovery after each boot. flash recovery then flash this right after.
Follow what SEAN SAys..............He is a Master in all these , and he helped me with details to root, flash cwm, make it sticky and flash custom ROMS.
It took me 5 minutes to do all those , and Now I am switching Roms like I switch my underwears every day twice.
I must say, Sean has the best possible way which is like a finger click.
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
ackerchez said:
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
Click to expand...
Click to collapse
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
thejosh86 said:
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
Click to expand...
Click to collapse
Hey!
Thanks a ton for your reply! I managed to get the phone to install a new ROM (AOKP V5) and it seems to boot up. Now when I get into that rom, I see all kinds of things crashing on me. The "Settings" app crashes, the keyboard crashes..any idea?
Did you wipe system, factory reset, davlik and cache from within TWRP before flashing?
Try that otherwise if you're still running into issues post in the thread.
You flashed the 11/10 JB gapps?
Sent from my Nexus 7 using xda premium
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
ackerchez said:
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
Click to expand...
Click to collapse
Did u wipe everything? (davlik, cache)
Sent from my HTC One XL using xda premium