I am lost.
I had FireFly 2.05 on my SGS (ATT US version) and was going to update to 2.1. I followed the procedure as I aways do; ODIN 1 click to stock rom, master clear, copy update.zip and rom file and reboot into recovery. This time however I get the following error
E:Can't symlink /system/xbin/su SYSTEM:bin/su
E:Failure at line 14
I checked some notes on this and found out that it might be a currupt file. So I re-downloaded FireFly2.1 again and transfered the file to the internal SD card. The outcome was the same.
Then I copied the original 2.05 version back which I know was fine and I still get the same error. Even after a full stock 1-click and master clear the above error will not go away.
Is my internal SD card messed up? Or am I missing something else?
It's running stock right now and all seems to work fine, but I cannot stand all the bloatware and other crap ATT puts on the phone and really want to try FireFly2.1.
Any help is greatly appreciated.
Thanks.
Did you flash clockwork recovery
Did you root the phone after you flashed back to stock?
Sent from my SAMSUNG-SGH-I897 using XDA App
Agree with DaveyBB - sounds like you are not rooted.
Sent from my SAMSUNG-SGH-I897 using XDA App
You do not need to root on stock just flash clockwork with update zip
The update.zip i use is the current clockwork recovery.
I boot into the stock e2 recovery, then apply cw recovery and update the rom. Never had to root stock before when i update via cw recovery.
I will try to root stock first this time and then apply rom via recovery.
Thx
Sent from my SAMSUNG-SGH-I897 using XDA App
anosis said:
The update.zip i use is the current clockwork recovery.
I boot into the stock e2 recovery, then apply cw recovery and update the rom. Never had to root stock before when i update via cw recovery.
I will try to root stock first this time and then apply rom via recovery.
Thx
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
To install clockwork select reinstall packages twice
The issue is not with cw recovery. I am already in it, but the error that i get is after i click "yes apply this zip"... The script starts to format the system, data, datadata, etc. And then this error shows up after files ate copied
Sent from my SAMSUNG-SGH-I897 using XDA App
Have you tried re download of rom package?
My only guess is that clockwork and the rom are not working well. I would try downloading a different clockwork
Sent from my SAMSUNG-SGH-I897 using XDA App
mcord11758 said:
Have you tried re download of rom package?
Click to expand...
Click to collapse
Done that too.
So just to reiterate...
I had FireFly2.05 running and many other cooked Android 2.1 and 2.2 roms before this. I follow the instrution of the cooks to the 't' on how to update to the newest rom and never had any issue.
This time I downloaded FireFly2.1 and also Phoenix4.5 from the respective cooks and followed the instructions as usual. The issues does not show up until the 'copy files' part of the script is running (formating of the filesystem already passed).
All I can imagine are these:
1) The transfer from the PC to the Phone is corrupt (ruled out the download from the net as even the existing FireFly2.05 rom no longer loads)
2) The internal SD card is messes up
3) There is some configuration change I am not aware off that prevents the install of the cooked rom.
Maybe try to reformat sd through clockwork
Problem solved, kind of.
My desktop PC, which I always use to transfer the files is somehow responsible for the error I get in CWM recovery. I ended up using my laptop to transfer the ROM to the phone and it worked again.
Something is messing up the USB transfer? That seems very odd but I am glad it's not the phone that caused the issue.
If I find out what the issue is with my Desktop I will post again just in case this rather rare issue might happen to someone else.
anosis said:
Done that too.
So just to reiterate...
I had FireFly2.05 running and many other cooked Android 2.1 and 2.2 roms before this. I follow the instrution of the cooks to the 't' on how to update to the newest rom and never had any issue.
This time I downloaded FireFly2.1 and also Phoenix4.5 from the respective cooks and followed the instructions as usual. The issues does not show up until the 'copy files' part of the script is running (formating of the filesystem already passed).
All I can imagine are these:
1) The transfer from the PC to the Phone is corrupt (ruled out the download from the net as even the existing FireFly2.05 rom no longer loads)
2) The internal SD card is messes up
3) There is some configuration change I am not aware off that prevents the install of the cooked rom.
Click to expand...
Click to collapse
One Question:
What method are you using to enter recovery method when you attempt to flash the rom? And what color is your recovery menu (should be green)?
(Don't go into recovery via rom manager. Try entering recovery via your advanced power menu)
bames said:
One Question:
What method are you using to enter recovery method when you attempt to flash the rom? And what color is your recovery menu (should be green)?
(Don't go into recovery via rom manager. Try entering recovery via your advanced power menu)
Click to expand...
Click to collapse
I don't think he's getting into Clockwork via ROM Manager, as he's said multiple times he's using the CWM update.zip; reinstalling packages in 2e recovery to get to CWM.
He's also said he doesn't believe this to be an issue with Clockwork (and I don't either). And I'm also pretty sure we're not dealing with newbie mistakes of Android Recovery vs. Clockwork Recovery.
any chance you're leaving your usb plugged into your cappy while you're trying to flash it?
Related
hey guys i had andromeda installed but messed the flash up by disabling lots of system stuff so i one clicked back to stock, rooted, installed rom manager like normal but every time i try to flash clockwork recovery mod it keeps telling me "An error occurred while downloading your recovery." and i cant install it so i can re-flash the rom plz help me i dont know what to do thx ahead of time
praramis said:
hey guys i had andromeda installed but messed the flash up by disabling lots of system stuff so i one clicked back to stock, rooted, installed rom manager like normal but every time i try to flash clockwork recovery mod it keeps telling me "An error occurred while downloading your recovery." and i cant install it so i can re-flash the rom plz help me i dont know what to do thx ahead of time
Click to expand...
Click to collapse
Put this on your internal SD card along with your ROM of choice. Reboot in to recovery and install packages 2 times. The second time it will be in clockwork recovery and you can flash your ROM.
I just had the same problem after doing countless ROM flashes in the past. Perhaps its something in their server preventing the download of CWM? Anyways, thanks for the .zip. Worked like a charm!
yes thank you very much for that zip u saved my life well appreciated
Keep that .zip on your HDD and you can bypass Rom Manager (and all the associated problems) altogether.
I have my phone rooted and unlocked. It's the AT&T Captivate but I'm using it on T-Mobile. I've had no problems so far with it.
I downloaded Clockwork's Rom Manager (v3.0.0.7) and tried to Flash ClockworkMod Recovery to begin experimenting with ROMs.
When I click on that it tells me "An error occurred while downloading your recovery."
I have over 4 gigs of memory left and I have 3 bars on 3g and WiFi going. No internet connection problems (i checked the net using market and using the browser, it works fine.)
What else could be causing the problems.
I'm just wanting to get a good stable rom going which ditches all the junk AT&T put on the phone.
Jonathan
lanternslight456 said:
I have my phone rooted and unlocked. It's the AT&T Captivate but I'm using it on T-Mobile. I've had no problems so far with it.
I downloaded Clockwork's Rom Manager (v3.0.0.7) and tried to Flash ClockworkMod Recovery to begin experimenting with ROMs.
When I click on that it tells me "An error occurred while downloading your recovery."
I have over 4 gigs of memory left and I have 3 bars on 3g and WiFi going. No internet connection problems (i checked the net using market and using the browser, it works fine.)
What else could be causing the problems.
I'm just wanting to get a good stable rom going which ditches all the junk AT&T put on the phone.
Jonathan
Click to expand...
Click to collapse
Read the above solution...
I Can't get the update.zip file to work. After I reinstall packages is says E:Can't open /sdcard/update.zip (No such file or derectory) Installation aborted. I've tried it probably 20 times today with no luck.
Thank You
Nothing like flashing to find out it wasn't working. Thanks for making my day go better.
Noobie Mistakes
Just like everyone in this forum I'm having the same problem, I followed your instructions posted, but every time I reinstall packages in recovery mode a whole list of new problems comes up..... see below.
---Install from sdcard---
Finding update package...
Opening update package....
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
PLZ Help.......
Thanks
i have been fight this same thing for 2 days. im going to try the update.zip he posted i hope it works
npe didnt work. still says error downloading
tat2messiah said:
npe didnt work. still says error downloading
Click to expand...
Click to collapse
if the update.zip is already on your /sdcard/ then there is no reason to try and download/flash clockwork recovery.....thats what the update.zip IS
thats what i thuoght but not true. even goin in normal recovery and selecting to install packages gets a error some about no such directory or something even though updat.zip is there even fix permissions gives a error
I'm having the exact same problem. After reading the development section I have decided to flash a custom rom from my stock rom. Installed "Rom manger" from market, then tried to run the "recovery" got the same error msg. Also uploaded the update.zip to my /sdcard the I got the below errors:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
tat2messiah said:
thats what i thuoght but not true. even goin in normal recovery and selecting to install packages gets a error some about no such directory or something even though updat.zip is there even fix permissions gives a error
Click to expand...
Click to collapse
Did you flash back to stock JF6 first not JI6?
try this cuz this is what i did and the update.zip worked just fine for me
1. one click back to stock jf6
2. master clear
3. root with galaxy s one click root
(after the root there should be an update.zip in your sdcard)
4. replace the update.zip in the root of your sd card with the one here posted which is the clockwork recovery one and if you want while u do that you can throw in the rom that you want to flash in there as well to kill 2 birds with one stone
(i will re post the update.zip for cwm just in case)
5. power off the phone and boot into stock recovery and hit reinstall packages two times
6. you should now be in clockwork mod recovery and can now flash the rom of your choice
this is what i did and everything went smoothly but this is just me if this helps someone else plz let me know if this works for you
p.s. i will make a video if needed just ask
Try This
After flashing back to stock do a master clear from Odin3
Put update.zip onto internal sd
Boot into recovery
Reinstall packages
After boot enable USB debugging and mock locations
Get Rom Manager from market
Start Rom Manager
Flash ClockworkMod Recovery
Flash away
jhernand1102 said:
Put this on your internal SD card along with your ROM of choice. Reboot in to recovery and install packages 2 times. The second time it will be in clockwork recovery and you can flash your ROM.
Click to expand...
Click to collapse
You guys are making it harder then necessary, the update zip I posted is the clockwork recovery MOD, just flash stock, reboot into recovery and reinstall packages 2 times and you will be in the green clockwork recovery then you can install zip from sd and choose your ROM you placed on your internal sd card. No need to root every again as long as you keep this update zip handy.
I too am having problems with Rom Manager. I just wanted to change modems. No go. So I used the power button to go into Recovery mode, picked the modem file, flashed it then told the menu to reboot system.
Sent from my Samsung Captivate with Perception 10.3, Firebird2 v0.8 #77 Kernel, Firmware 2.2.1, Modem T9000UGJL2 using XDA App
Ok guys so I have managed to root my i9023 and flash clockwork recovery which was all good, I set about flashing some new roms via rom manager, again, all good.
So now I settle on this cm7 based rom which I love, used anim mod to get some nice transitions, then I used font changer.
All was good, then I decided that the font I was using was a bit ott so I decided to change it again, upon reboot it starts boot looping, bollocks !!!
So I try to get into clockwork recovery, and it seems to have gone back to the stock bootloader, grrrrr
I re flash clockwork, wipe / clear etc... then flash the rom again, but it would not flash, so I went to my backup of stock n flashed that, all good.
I then install rom manager again and flash the rom I liked again, this time no problem, but when it loads up the home button and search button are not working
So i decide on a factory reset, I select wipe everything including sd just to be sure but it comes up "error null"???
So now I wipe the sd manually and then do the reset and it works, ok, I re load everything on from scratch and all is good, but when I installed rom manager it says that clockwork recovery IS NOT installed again
Can anyone here work out from my ramblings WTF is going on???
I dont get why the font changer all of a sudden caused a boot loop, as I had changed font about 15 times with it without issue, also why clockwork recovery will not stick anymore after a reboot, when before it did and I have not changed a thing!
Cheers!!!
Rename install-recovery.sh in system/etc to something else, flash cwm recovery again, this time it'll stick until you install a stock rom again.
Rom manager is causing more problems than it's saving time, hence I don't use it.
Sent from my Nexus S using XDA App
Thanks for the reply, can you go into detail on what exactly I need to do to get clockwork to stick? I still hold noob status!
Thanks!
Also rom manager seems fine, I flashed loads of roms with it with no issue, I also rebooted a few time at least between flashes so I dont get why clockwork suddenly decided to jump ship.
It was the font changer that f&%ked it all up for me, or anim mod (which I wont touch now even tho I miss the wicked transitions).
When using Font Changer, it's better to do a reboot manually instead of selecting Reboot from within the program. That sometimes cause me a boot loop too. But after turning the phone off / on a.k.a. "reboot manually", the phone boots fine.
To elaborate what rentaric said, use Root Explorer and go to /system/etc/, there should be a file named install-recovery.sh. This file is responsible for flashing the stock recovery every time the phone boots. If you rename it to something else e.g. install-recovery.sh.bak then CWM will stick on reboot.
Thanks, but when I get into the /system/etc/ there is not file called install-recovery.sh.
The only .sh in there is init.goldfish.sh
Any ideas???
bump...............
Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App
I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.
athani said:
I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.
Click to expand...
Click to collapse
LINK: http://forum.xda-developers.com/showthread.php?t=1007782
Please read the whole thread, if I had it would have saved me half a night scratching my head...lol
rentaric said:
Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yeah I have a custom rom installed, supercm7, but the install-recovery.sh. that I have been told is causing the problem of clockwork disappearing is not in the /system/etc/ folder, so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?
I will tell you exactly what happens.
1. I go into rom manager
2. download a rom and choose flash rom from sd card
3. it asked if I want to wipe etc, i select yes
4. phone re boots and I get ! with an android
5. I pull the battery, hold volume up n power and boot / connect to my pc
6. re flash clockwork via SDK
7.the phone then load the new rom on its own
Before it would just flash the rom without me having to install clockwork again.
install-recovery.sh is only there if you're using a stock android rom.
"so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?"
ROM Manager.
It's not a reliable working tool for ME as I'm changing ROMs/kernels on a regular basis and it might not work reliable the one time you need it.
Thanks for that, I may just sack rom manager then.
Its a shame as I flashed several roms with it without issue.
Oh well, loving this supercm7 so gonna stick with it untill an update comes out.
Many thanks to all who have replied, clicking the thanks buttons now!
I had the same problem but i installed a previus recovery and works fine formeforme
Sent from my Nexus S 4G using XDA Premium App
I soft bricked my phone playing with ICS, I got a JIG and solved the problem
I can now ODIN back to any version and once rooted I can install any samsung based rom, the problem comes when I try to flash aosp both CM7 and any ICS beta
What happens is I select the zip, it runs a script and the phone reboots, I see the AT&T logo and then it mounts the sd card, it says it can't find the zip file.
I've tried Froyo, Eclair, even gingerbread (I know your not supposed to flash cm7 from gingerbread, I'm just running outta ideas) I have froyo bootloaders, I reinstalled them with heimdal. I've also done a master clear and erased the internal sd card
Does anyone have an idea of why this is happening?
Are you trying to install the zip from ClockworkMod?
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Another problem
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?
kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
I can't flash cm7 either
movielover76 said:
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?
Click to expand...
Click to collapse
I'll go over my method of installing(I've had ZERO issues flashing from/to any ROM)
1. I FTS/MC using Odin 1 Click. My phone build is 1008
2. Root with 1 click root(I have to do steps 2 and 3 because I do not have 3 button recovery)
3. Sideload and install ROM Manager(Rom manager, and CWM update.zip are in the Sideload zip that's attached)
4. Copy CWM Update.zip and ROM to device. Reboot and install CWM
5. Reboot into recovery and install ROM
Odin 1 Click(If you can use it)
http://dl.dropbox.com/u/12100225/Odin I897UCJF6-final-OCD-REV0.zip
Root 1 Click
http://dl.dropbox.com/u/12100225/Root.zip
Sideload Wonder Machine and ROM Manager
http://dl.dropbox.com/u/12100225/Sideloading.zip
Edit** What is the build number of your phone?
Here's what you need
Just download this rom
http://download.cyanogenmod.com/get/cm_captivatemtd_full-181.zip
And then watch this video!
http://www.youtube.com/watch?v=iBPu-GqM9RE
Flash CM7 using odin
then flash ICS using clockwork mod using the instructions I gave you before.
That's the easiest way I found to do it and that's how I went from stock rom to CM7 rom and then finally to ICS
kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
Tried this to the letter still doesn't work, could it be because of rom manager not finding a recovery for captivatemtd, some pages say I need that recovery but it isn't available in rom manager.
Finnally
Finnally got CM7 installed the problem was I had to do the three button boot into recovery twice, the first time updates clockworkmod to version 5.x
Now to try ICS again, wish me luck
Thanks
Thanks for all the suggestions, the tip in the video about flashing the speedmod kernel did help I think, I've successfully flashed
teamhacksung's ICS Port for Captivate (BUILD 9) again.
A couple notes here:
1 when your flashing cm7 from cwm( NOT 3e RECOVERY THOUGH) you need to flash the. Zip file, then reboot system, IT WILL PROBABLY BOOT LOOP, three button back to recovery and flash again, then while in recovery still flash gapps. Reboot and it will install fine. You should ONLY need to do the two time flash the first time going to cm7.
2. When you go to rom manager and choose manual flash overide from hitting the menu button you will get the unsupported recovery, DON'T WORRY about it and hit ok. Then another popup will come up and choose 3.x and it will work.
Sent From My KickAss ATT SGS2 SPORTING CM7
I searched this forum a bit and I can't find a nice guide. I am currently running rooted .19 on my TF101, B70KAS. Is it as simple as dropping the ROM on my internal SD and letting it update to the latest Revolver release (based on .21)? Or can I do it with booting into recovery mode? This is my first tablet and I have no clowworkmod on my tablet... do I need to flash that somehow? Where's a guide?
thanks!
ninjai117 said:
I searched this forum a bit and I can't find a nice guide. I am currently running rooted .19 on my TF101, B70KAS. Is it as simple as dropping the ROM on my internal SD and letting it update to the latest Revolver release (based on .21)? Or can I do it with booting into recovery mode? This is my first tablet and I have no clowworkmod on my tablet... do I need to flash that somehow? Where's a guide?
thanks!
Click to expand...
Click to collapse
Since i am firm believer you need to learn what you are doing i will lay down the basics from there you are on your own.
1) read and study SU access
2) read and study SU access
3) read and study SU access
4) root
5) install clockwork recovery
6)download Revolver
7)verify the MD5SUM
8)boot into recovery
9)do a nandroid back up
10) do a factor reset via CWRI
11) flash the OS you want
12) reboot
13) enjoy
neidlinger said:
Since i am firm believer you need to learn what you are doing i will lay down the basics from there you are on your own.
1) read and study SU access
2) read and study SU access
3) read and study SU access
4) root
5) install clockwork recovery
6)download Revolver
7)verify the MD5SUM
8)boot into recovery
9)do a nandroid back up
10) do a factor reset via CWRI
11) flash the OS you want
12) reboot
13) enjoy
Click to expand...
Click to collapse
I am very familiar with CWM, flashing, nandroid backups, etc. I've had a nexus one for a long long time. I just can't find any good stickies on how to install CWM on my tablet, which I assume is my first step, though I find it odd there are no stickies. On the Nexus One forum there are lots! Where can I learn about installing CWM on my tablet with stock (but rooted) .19 FW?
ninjai117 said:
I am very familiar with CWM, flashing, nandroid backups, etc. I've had a nexus one for a long long time. I just can't find any good stickies on how to install CWM on my tablet, which I assume is my first step, though I find it odd there are no stickies. On the Nexus One forum there are lots! Where can I learn about installing CWM on my tablet with stock (but rooted) .19 FW?
Click to expand...
Click to collapse
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
I had the Same issue coming from the nexus s. the tricky bit is that rom manager does not support the transformer. I've got a galaxy tab 10.1 as well and flashing over a custom recovery was easy as pie.
anyway, what you have to do is this: http://forum.xda-developers.com/showthread.php?t=1213723
(http://forum.xda-developers.com/showthread.php?t=1093818)
then you need to install an app (i use reboot2recovery) from the marketplace to get into the custom recovery. i've tried quickboot or rom manager but all it does it take me to a black screen or reboot the device. reboot2recovery will actually drop you into clockworkmod recovery. from there, do your nandroid backup. you'll need an SD card in your transformer for it to actually go ahead with the backup.
aside: from my reading, the backup should backup to internal storage with that modded clockwork. i've never been able to get it to work though. anyway, just use an SD card for now so you can get through the difficult stuff.
so at this point uve done the following:
installed clockwordmod using the first 2 links and installed the reboot2recovery APK to get into recovery.
now you have an SD card in your transformer and you are doing a nandroid backup.
once completed, put the 200+mb revolver rom on the root of your SD card. you may also want to put another kernel. i use the one recommended by revolver.
now just wipe the cache, data, etc as usual. now flash the rom, reboot the system when completed. plug in your gmail account, wifi password etc. and then reinstall the reboot2recovery apk. now reboot to recovery and then flash the kernel. reboot and ure good to go. install revolver parts to allow for additional tweaking and OTA updating.
i got my transformer from bestbuy this thanksgiving and went to revolver 3.9.5 immediately. last night i actually flashed revolver 3.11 right over it. not a single problem.
edit: reading the above post, i remember that my FIRST recovery installation was using that one-click tool and, as was said, it works flawlessly. you still need the reboot2recovery though. and recoveryinstaller WILL NOT install the modified for internal storage version of clockwork. i'm thinking maybe i just havent tried backing up since updating to the internal storage version, which is why i think i've "never gotten it to work"
baseballfanz said:
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
Click to expand...
Click to collapse
Awesome, I had tried it earlier and it didn't do anything. Then I realized that my superuser app was FCing, however I could still use adb shell and su just fine! After I realized there was an update for the superuser app, I installed it. Everything is perfect now.
kramer987 said:
I had the Same issue coming from the nexus s. the tricky bit is that rom manager does not support the transformer. I've got a galaxy tab 10.1 as well and flashing over a custom recovery was easy as pie.
anyway, what you have to do is this: http://forum.xda-developers.com/showthread.php?t=1213723
(http://forum.xda-developers.com/showthread.php?t=1093818)
then you need to install an app (i use reboot2recovery) from the marketplace to get into the custom recovery. i've tried quickboot or rom manager but all it does it take me to a black screen or reboot the device. reboot2recovery will actually drop you into clockworkmod recovery. from there, do your nandroid backup. you'll need an SD card in your transformer for it to actually go ahead with the backup.
aside: from my reading, the backup should backup to internal storage with that modded clockwork. i've never been able to get it to work though. anyway, just use an SD card for now so you can get through the difficult stuff.
so at this point uve done the following:
installed clockwordmod using the first 2 links and installed the reboot2recovery APK to get into recovery.
now you have an SD card in your transformer and you are doing a nandroid backup.
once completed, put the 200+mb revolver rom on the root of your SD card. you may also want to put another kernel. i use the one recommended by revolver.
now just wipe the cache, data, etc as usual. now flash the rom, reboot the system when completed. plug in your gmail account, wifi password etc. and then reinstall the reboot2recovery apk. now reboot to recovery and then flash the kernel. reboot and ure good to go. install revolver parts to allow for additional tweaking and OTA updating.
i got my transformer from bestbuy this thanksgiving and went to revolver 3.9.5 immediately. last night i actually flashed revolver 3.11 right over it. not a single problem.
edit: reading the above post, i remember that my FIRST recovery installation was using that one-click tool and, as was said, it works flawlessly. you still need the reboot2recovery though. and recoveryinstaller WILL NOT install the modified for internal storage version of clockwork. i'm thinking maybe i just havent tried backing up since updating to the internal storage version, which is why i think i've "never gotten it to work"
Click to expand...
Click to collapse
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
It mean open your command prompt in your computer fire up the ADB server and type
Code:
adb reboot recovery
Why why not download the reboot recovery app from the market?
https://market.android.com/details?id=com.transformer.recovery
Sent from my Transformer TF101 using Tapatalk
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
Have you installed CWM recovery?
Rooting alone does not install CWM recovery.
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
thank you guyz i just needed to install cwm recovery, its just that those steps are not on any step by step , i can access now in to cwm recovery
Once in recovery it cant mount sd
SGS Dutchie said:
Once in recovery it cant mount sd
Click to expand...
Click to collapse
You have a micro sd card insert into the slot?
baseballfanz said:
You have a micro sd card insert into the slot?
Click to expand...
Click to collapse
Nope,thought it was the internal sd just like is shown in file explorer.
SGS Dutchie said:
Nope,thought it was the internal sd just like is shown in file explorer.
Click to expand...
Click to collapse
CWM only work with external card for now
Removable/MicroSD
baseballfanz said:
CWM only work with external card for now
Removable/MicroSD
Click to expand...
Click to collapse
Ah, I must go and search for one then.
baseballfanz said:
CWM only work with external card for now
Removable/MicroSD
Click to expand...
Click to collapse
Thx man, you really helped me out today. First with my root/cwm problem and now with this rom.
You really are a great help. Thx again!
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
The problem with ROM Manager is that it messes up the files when flashing a ROM or any file. It is more advised to use CMW Recovery.
yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
Rom Manager should not be used on the G2x. If you flash a rom and something goes wrong and you can not boot you are dead in the water. Use Nvidia CWM instead.
http://forum.xda-developers.com/showthread.php?t=1056847
Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...
yuma80 said:
Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...
Click to expand...
Click to collapse
I've always been curious about the details of a 'fake flash' too.. please let us know if you figure out any details.
Rom manager has been around since the original Droid from Verizon. The fake flash you refer to isn't actually a fake flash. It actually flashes CWM recovery. It just doesn't work on this particular phone. I may be wrong on the exact details but the G2x partitions and drivers require the use of NVflAsh to install the CWM. However, there are many phones that once they have been rooted, the user can install Rom Manager and use the Flash Recovery option to install their CWM recovery. There are also times when a particular recovery version (ie.. 5.0.5. Or 4.6.3) works better than another on one particular phone. Rom manager allows users an easy way of flashing between those CWM versions by simply pushing the flash button.
So in summary of a long response... it is only called a fake flash because it looks like it worked on our phone , but in fact it does not. We have to use NVflash to flash our recovery.
If it looks like I'm remotely right ( which I think I am..) hit that thanks button. (Shameless request, I know)
From my understanding, the "fake flash" that ROM Manager does is that it doesn't actually flash CWM like NVFlash does (on the recovery partition) but still puts the CWM files on your SD card saying that you do have it installed (sdcard/clockworkmod) so when you try to flash/install a ROM, it can't put it anywhere. I don't think it will flash anything, but people mess up their devices by wiping data/system and such...
OR...
Maybe it does flash CWM to your device but it has the partition tables all messed up?
One or the other lol, it's just a guess for both options but I believe the first one is right.
I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this
DorisTheHeavy said:
I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this
Click to expand...
Click to collapse
To rename your nandroid backups .
buru898 said:
To rename your nandroid backups .
Click to expand...
Click to collapse
I never thought about that. I was always unsure what flashing CWM with ROM Manager would do when it's already on my phone using NVFlash.
Since our phones have a dual partition in it. I think it flashes to the internal 1 gig memory so then loading another rom writes over it.
Sent from my LG-P999 using xda premium
OK, I finally had some time to do some poking around. Some of this is guess-work since I was too lazy to verify 100% exactly what it does when you specify that you're running a G2X.
Anyway, in it's settings DB it says this phone's recovery partition is read-only, and there's no flash command set, so I guess it doesn't try to flash it directly. It looks like it's relying on the Google stock recovery image to do the flashing instead, so it downloads a recovery-update.zip to the SD card and writes a script to /cache/recovery and reboots the phone into recovery mode. Google stock recovery would execute the script in /cache/recovery, which says to apply recovery-update.zip, but the actual stock recovery on the phone is either not Google stock, or has been modified; it doesn't bother to execute scripts, it just does a factory-reset (clear /cache, /data, etc) so that's why it doesn't work.
Meanwhile, ROM Manager writes to it's DB that it just flashed CWM version X.Y.Z and happily displays that every time it runs, even though that's not true.
I used NVFlash and moved on with my life.