This thread might be a warning not to install CWM through ROM Manager until it's fixed. Aplogies to koush if it isn't broke and it was just my incompetence.
So... I got my TF101 on Saturday and after checking everything worked on it I rooted it with ViperMOD PrimeTime v4.5, installed Team Rogue recovery using the recovery installer apk and flashed Revolution HD ROM.
(I had to use ViperMOD for the rooting becasue I had already done the ASUS ICS update via Wifi)
Anyway, a few hours ago I saw on Twitter that ClockworkMOD recovery for the TF101 was now available. I thought great and installed ROM Manager from the market, clicked on flash CWM recovery and selected my device. It flashed CWM and rebooted into CWM.
Only problem is my device now boots up to CWM recovery every time I turn it on. Also I was expecting CWM to be better than the Team Rogue one but it turns out that the Team Rogue one lets you select a zip from your MicroSD card where CWM does not.
If I want to boot into the OS on my EeePad I have to hold the Vol Down on startup, wait 5 seconds at the recovery prompt and then I get the screen which allows you to wipe data or cold boot into Linux/Android. So I choose boot into linux and the OS starts loading.
This is a bit of a pain in the arse, and not what the device was designed to do so I'd like to get it back to nornal, preferably with Team Rogue recovery due to the better options it has.
I've tried running the Team Rogue recovery installer apk and also reflashing Revolution HD and it always boots up with ClockworkMOD!
My guess is that ROM Manager has placed CWM in an area of memory that it isn't supposed to go in, ahead of where the EeePad recovery should be.
Is there a hardcore recovery/kernel flashing utility I could use?
I've done a lot of flashing with phones but this is my first tablet so I'm a bit of a noob with the TF101.
I've been thinking: would flashing a stock ASUS ROM, complete with ASUS kernel and recovery, fix this?
I can't use nvflash because it's one of the SBKv2 models.
Is there a complete package I could flash with ADB/Fastboot?
Try wiping everything and install the rom again?...
Or.. download an older rom version from asus website and follow their instructions to load perhaps ?
I found out even though I've got a B70KAS serial device I'm lucky to be able to NVFlash. I've flashed a complete, stock Honeycomb image on there and it's sorted out my recovery sector.
It had me scratching my head as I thought I would be able to NVFlash, but I tried and it worked.
where did u find file?
Had same problem ,went to Asus site wouldn'tlet me downloads us version
Here is the page for the NVFlash of the Worldwide/UK version of the file mate:
http://www.wupload.co.uk/file/2628149097/Revolver_TF_3.11_nvflash_gnufabio.zip
I ended up finding out which file I needed and just did a google search for 'Revolver_TF_3.11_nvflash_gnufabio.zip'.
Then when I flashed that I had a brand new installation of Revolver Honeycomb which was rooted and an older version of ClockworkMod installed.
Make sure that you have the NVflash/APK drivers on your PC and you should be OK. I used Windows 7 64 bit and the flash went fine.
I then rebooted Revolver and used CWM to wipe and install the latest Revolution HD zip file from my microSD card. I'm back to Ice Cream Sandwich now and it's running OK.
Related
So I'm trying to update my rooted 3.0.1 euro 3G xoom to the 3.2 Hammerhead ROM, and here's something that is really confusing me:
I've installed ROM Manager 4.3.3.0 from the Market. Then I downloaded and flashed ClockworkMod Recovery 3.2.0.0 R4c via this thread: http://forum.xda-developers.com/showthread.php?t=1074979
So far so good: I can boot to recovery and it looks that everything is working nicely... with the exception of the following:
1) Even though I have CWM installed, ROM Manager won't recognize it. It keeps asking to install it. I haven't done that though because I don't want to overwrite the one I flashed... how can I get ROM Manager to recognize CWM? Or, if I install a different CWM version through the ROM Manager interface, will that overwrite the existing install, or even break something?
2) I can't find Nandroid in the recovery menu of 3.2.0.0 R4c. It says that it should be there in the Wiki (http://forum.xda-developers.com/wiki/index.php?title=How_to_backup_or_recover_via_Nandroid), but no sir. I only have the options Backup and Advanced Backup in recovery; it doesn't say Nandroid anywhere.
The thing is - I made a normal backup and it created a folder with .img files in it, along with a nandroid.md5 file. So is this a full Nandroid backup or not? And should it not be a zip file? Meaning - will I be able to revert to this backup through ROM Manager or CWM later if it's not a zip?
3) Lastly, I want to install the Tiamat 2.1 Hammerhead ROM. solarnz writes in the instructions in step 6 to "install the rom". So do I do that from recovery? Or from ROM Manager? Which brings me back to my first problem, that ROM Manager won't recognize CWM and won't let me install a ROM without it.
Also - can I install the Hammerhead ROM from my rooted 3.0.1 device at all, or should I install 3.1 first?
I know these are a lot of questions all at once, but after hours and hours of searching and reading (and learning a lot!), I still can't figure this part out.
Many thanks to anyone who can help me make sense of this!
bobblack said:
So I'm trying to update my rooted 3.0.1 euro 3G xoom to the 3.2 Hammerhead ROM, and here's something that is really confusing me:
I've installed ROM Manager 4.3.3.0 from the Market. Then I downloaded and flashed ClockworkMod Recovery 3.2.0.0 R4c via this thread: http://forum.xda-developers.com/showthread.php?t=1074979
So far so good: I can boot to recovery and it looks that everything is working nicely... with the exception of the following:
1) Even though I have CWM installed, ROM Manager won't recognize it. It keeps asking to install it. I haven't done that though because I don't want to overwrite the one I flashed... how can I get ROM Manager to recognize CWM? Or, if I install a different CWM version through the ROM Manager interface, will that overwrite the existing install, or even break something?
2) I can't find Nandroid in the recovery menu of 3.2.0.0 R4c. It says that it should be there in the Wiki (http://forum.xda-developers.com/wiki/index.php?title=How_to_backup_or_recover_via_Nandroid), but no sir. I only have the options Backup and Advanced Backup in recovery; it doesn't say Nandroid anywhere.
The thing is - I made a normal backup and it created a folder with .img files in it, along with a nandroid.md5 file. So is this a full Nandroid backup or not? And should it not be a zip file? Meaning - will I be able to revert to this backup through ROM Manager or CWM later if it's not a zip?
3) Lastly, I want to install the Tiamat 2.1 Hammerhead ROM. solarnz writes in the instructions in step 6 to "install the rom". So do I do that from recovery? Or from ROM Manager? Which brings me back to my first problem, that ROM Manager won't recognize CWM and won't let me install a ROM without it.
Also - can I install the Hammerhead ROM from my rooted 3.0.1 device at all, or should I install 3.1 first?
I know these are a lot of questions all at once, but after hours and hours of searching and reading (and learning a lot!), I still can't figure this part out.
Many thanks to anyone who can help me make sense of this!
Click to expand...
Click to collapse
Forget about Rom Manager. You have the correct recovery installed and you have made a "nandroid" backup when you used the backup option in CWM recovery 3.2.0.0 R4c. The Rom you want to flash needs to be on your MicroSD card and that needs to be in your Xoom when you boot into recovery. It is from the CWM recovery menu that you will choose to flash the zip file that will install the Rom. You will need to be able to boot into recovery and you can do it by pressing volume up and power to get to dual core screen, then after 3 seconds, press volume down then volume up and you should be in recovery. Or you could download Quick Boot from the market and use its boot into recovery option (that's what I do).
About the version you need to be on to flash Hammerhead...what does it say? I think you may need to be on 3.1 but just read the OP on the Hammerhead thread...it will tell you the requirements.
Good luck!
Thanks a lot for explaining that okantomi, that's very helpful and reassuring!
The only thing I'm left with now is to figure out the version part... the rom OP doesn't say anything about a required version. Here's the thread btw: http://forum.xda-developers.com/showthread.php?t=1203635
I made my way through the first 18 or so pages of the 434 total pages in that thread, but still couldn't find any info on that. I'll keep looking - not giving up
Quick update... I decided to just go for it. I flashed the 3.2 ROM onto 3.0.1 - it worked perfectly without any hiccups whatsoever. I'm now running Androud 3.2 with 3G and it works beautifully. Can you see that I'm smiling?
bobblack said:
Quick update... I decided to just go for it. I flashed the 3.2 ROM onto 3.0.1 - it worked perfectly without any hiccups whatsoever. I'm now running Androud 3.2 with 3G and it works beautifully. Can you see that I'm smiling?
Click to expand...
Click to collapse
Me too! ;^ )
Enjoy your shiny new Rom!
Hi all
I am stuck on an older cm9 nightly from March and desperately want to flash the newer cm9 released a couple of days ago
My problem is that I cant boot into recovery, rom manager doesnt work and the various other apps that I have found people recommending dont work either.
Could some kind soul tell me how to get rom manager back to working order so I can reboot to recovery so I can install the latest nightly? Or suggest another/better way to go?
Thanks in advance!
Try turning off your Tf, and holding the Volume-Down key Before and While you hold the power key to turn it back on. This should boot to your cwm recovery if you have one, if it gives you nothing or the stock recovery download the Recovery Installer.apk in the development section and (You MUST have root, I assume yes on cm9) open it and flash 3.2.0.1 cwm recovery. Once that's done you can flash the newest nightly. Keep in mind that 3.2.0.1 ONLY reads from External SD card (MicroSD) so be sure to get one or NVflash a newer recovery with internal.
Also a tip: Rom manager has had a host of problems for the Transformer, and while it's really good for some supported phones, it's not so good for the tf (just look around Q+A and the dev you see all sorts of ROM manager related problems)
Good luck
Recovery installer apk is actually in apps n themes section. And it read both internal SDcard and the microSd as well.
Sent from my awesome rooted Defy: 2.3.6
farsight73 said:
Recovery installer apk is actually in apps n themes section. And it read both internal SDcard and the microSd as well.
Sent from my awesome rooted Defy: 2.3.6
Click to expand...
Click to collapse
Actually if you use Gnufabio's version it will flash Roach's CWM 3.2.0.1
It only read from external micro sd card.
There's a modified version of RecoveryInstaller that flash Team Rouge's recovery, that version read from internal and external sd.
http://forum.xda-developers.com/showpost.php?p=22359727&postcount=218
After you have install recovery do the manual button method as posted above by Thing O Doom
or use this app
https://play.google.com/store/apps/...sMSwxLDEsImNvbS50cmFuc2Zvcm1lci5yZWNvdmVyeSJd
It's highly recommended you know the manual button method for when you're in a bootloop or your TF is stuck at the Asus page.
Resolved
Excellent, thanks so much for the help all, ended up getting team rogue's recovery....I had tried Gnufabio's one before and it hadnt worked when I installed and used the power & Vol down button(as the recovery image would not boot ever and froze after the first nightly I had installed)
Just a word of warning on the 4ext boot to recovery option, and this could just be me with Rom manager on previously when I tried to fix myself, when I installed 4ext it would freeze on boot totally...only way I got it to work was cold booting linux so just so you know it does seem to have its problems too
But I am now downloading the latest nightly to flash
Cheers!
Hello everyone,
My problem is this: I wanted to install a CM10 nightly on the device, so I root using the DebugfsRoot method, install rom manager, flash a recovery, try to install a ROM and it did not work. Rebooting into recovery got me the red triangle, but using the volume buttons allowed me to get in (only it did not have the option to install updates or anything. I think it was just he mounting and partition options)
Since I did not unlock the device before doing this, I chose to do so using ASUS's unlock utility. Once done, I tried booting into recovery, but the device would be stuck at "booting recovery kernel image" and won't budge. I tried flashing different version of CW but it did not seem to work.
Finally, for some reason, I chose the "wipe data" option from the bootloader and the device was stuck, again, at "booting recovery kernel image", only this time I can't boot into a ROM nor can I boot back into bootloader.
What happens when I boot using power and volume down is this:-
The device is Unlocked
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Checking for android ota recovery
Booting recovery kernel image
and then everything's stuck.
Booting normally makes the device stop at "the device is unlocked" message because, I assume, there is no ROM flashed into the device.
Thanks for helping in advance.
It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)
ShiroiKage said:
It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)
Click to expand...
Click to collapse
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.
buhohitr said:
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.
Click to expand...
Click to collapse
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.
ShiroiKage said:
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.
Click to expand...
Click to collapse
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.
okantomi said:
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.
Click to expand...
Click to collapse
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.
ShiroiKage said:
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.
Click to expand...
Click to collapse
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.
buhohitr said:
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.
Click to expand...
Click to collapse
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.
ShiroiKage said:
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.
Click to expand...
Click to collapse
You can't install the ASUS firmware through custom recovery. It has to be stock. I believe there are signature checks that prevent it from installing otherwise.
Sent from my ASUS Transformer Pad TF700T
did you unzip the file? should be a zip within a zip. you flash the zip inside
lafester said:
did you unzip the file? should be a zip within a zip. you flash the zip inside
Click to expand...
Click to collapse
You know, I unzipped the file the first time I installed it to get Clean ROM to flash, I had the unzipped folder there yet I managed to forget to use the unzipped file. /InfiniteFacePalm
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The stock Asus firmware includes bootloader, kernel, recovery and apps. You have flashed the stock recovery. Head over to the twrp thread or my ROM thread in my sig to see how to get twrp 2.5 onto your tab.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
Yes, you did. Everytime you install stock file of any version, it will update your bootloader, rom, and kernel. Just use Motochopper to root your device and reinstall your custom recovery with goomanager.
No, it is stock recovery. Just reroot with motochopper and install custom recovery with goomanager. Have fun. :good:
Right, thanks! If I want to stay completely stock I just need to figure out why the newer update is failing. Could be the file name now I think about it.
Otherwise I'll re-root and re-TWRP...
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The Android on his back is your stock recovery and it does not find a valid update file.
Weird is, that your system seems to see the 10.6.1.14 file (I assume you get an automatic notification and click "install" or "update" ) and then the recovery does not seem to install it...?
You could have a bad download, so try that first if you want to get the latest stock rom, or you can try to rename the downloaded file to EP201_768_SDUPDATE.zip, put it on your microSD card and reboot into recovery. The recovery should recognize the update file and start flashing it.
But since you are unlocked anyway - why don't you give CromiX a try? It runs so much better than the stock rom!
And for that, yes you would have to root again using the Motochopper tool and then install TWRP 2.5 with Goo Manager.
If you go that route make sure you flash the latest bootloader from the OP of the CROMiX thread first, boot back into your old rom once before you flash CROMiX.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Anatosuchus said:
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Click to expand...
Click to collapse
It's based on the stock rom, cleaned up and tweaked and optimized. Everything works - and better than on stock! I recommend selecting the option to disable fsync during installation. It boosts performance considerably, and since the rom is totally stable, the "risk" is neglible.
You will love it!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
OK, ChromiX installed! Looks interesting already, will tinker with it over the next couple of days.
My old phone got lost so I am using my Infuse again. I decided to update it since it is still on the old version from when it first came out. I was trying forever to update through the kies software until I realized I rooted it and so this won't work. So then I found out there are roms for way better versions anyways. So I found the Cyanfox rom and I wanted to do that, but I needed to first upgrade to cm9 so I went and downloaded the cm9 file and got the clockworkrecovery, and I installed it.
Now my phone will not turn on, it sits as samsung screen. And if you try to go to recovery it is just a messed up screen with all different colors as if the screen was broken. So now my only option to bea ble to install anything on it is through odin. I can get to download mode fine.
But this damn odin software will not detect my phone for the life of me. It literally will not work. I don't understand. I have spent hours upon hours on this between the past few days. I just want to update my damn phone.
Now I have to leave for work in 30 minutes and my phone doesn't work. This is just great.
How did you install CWM?
Sent from my Asus MeMO Pad 8"
Well I tried clockworkmod through the rom manager app, but I was running the android recovery 3e and it said I needed a modified version of that to be able to install 3e. So I replaced the recovery file with the one I was given, and then I manually installed cwm by naming it update.zip and running it on the recovery
The only problem was that every time I wanted to use cwm, it would go back to android recovery 3e, and I would have to click install again to get it to go into cwm.
Either way, it doesn't work anymore and I just need the damn thing to connect to Odin so I can flash it back.
Are you using a desktop or laptop? If desktop, are you using the USB ports in the back? If laptop, have you tried different USB ports? Maybe try a different computer? I've heard that USB 3.0 doesn't play nicely with ODIN so it's good to find some 2.0 connections. What Windows version? I've heard that Win8 can cause problems. Could also try Heimdall instead of Odin.
Unless I think of anything else, is the cable in good working order (recent successful file transfer)?
Alright. I got things working somewhat. I had to use different drivers for each program for it to be able to detect it. I don't know, its annoying as hell, but it worked when I went back and forth between drivers.
Anyways, I got my device restored. But the whole point of this was that I was trying to get to the KitKat rom(Cyanfox). I am still quite a few steps away from that. I am actually further away than when I started,
This is what originally happened: I had my device rooted(from when I last used it, 1-2 years ago) and had the 3e recovery. So I found out I needed a modified 3e so I could install Clockworkmod. Got that, all was well, and the thing basically got bricked when I went to update to a new rom. It wasn't the kitkat rom, but a CM9 rom that I needed to go to first so that I could then update to kitkat.
Now I got it unbricked, and I updated it using kies. So now I am on gingerbread. So then I rooted it again. So now I have the 3e recovery again, the only problem is when I go to system/bin/ there is no file called recovery, and I can put one there but it does not affect the recovery, it still looks for signed files, meaning I cannot install Clockworkmod.
Not sure what to do...
Seems everyone follows this process (looks like you already did step one) now....
1. Either use Odin or Heimdall One-Click. Follow instruction on how to do it.
2. While phone running install sgs kernel flasher from Market/Google Play.
2a. Copy/transfer Synthesis GB Kernel to your Internal SD card.
2b. Start up sgs kernel flasher and choose it from your Internal SD card. Phone will auto-reboot after done flashing.
2c. Wait a bit while your phone convert to new partition format and activate lagfix. Your CWM recovery version should be 2.5.1.3
3. Reboot phone into CWM Recovery and DISABLE vodoo lagfix and /system lagfix. Reboot once done. Phone will convert partition to old format. If you don't turn the lagfix off the phone will hang at Samsung logo when you install new rom.
4. Prepare your flavor rom/gapp for installation by copying them to your Internal SD card.
4a. Go into CWM Recovery mode and install the rom. You will need to do this twice since the 1st time was just a warning about partition format being different.
4b. Reboot once done. You will need to REMOVE the battery to power down the booting process and put it back in.
4c. Go into the New CWM Recovery and install the rom again since the previous attempt only install the new CWM Recovery.
5. Install Gapp.
6. a. Wipe: Cache / Factory Reset <--- Probably don't need it since it's new install from stock unless you installed stuff. Just to be safe.
b. Wipe: Cache Partition
c. Wipe: Dalvik Cache
7. Reboot
Click to expand...
Click to collapse
I never tried step two myself, as I found a flashable download for ODIN that did this for me. But mine is a Rogers phone (not AT&T) so that would not work for you. Hope this helps.
Thanks you so much man. I know that is just copy/paste but I didn't see it, and it works. I was looking in Cyanfox thread, never looked at the Beanstalk thread.
Anyways I am in the process of doing this and it seems like it will work. Appreciate all your help!
Edit: Boom. Worked like a charm. Thanks so much. I am very happy now The funny thing is, half the reason I wanted this is cause everyone was group messaging, and I didn't have that capability anymore when I lost my phone(I was on such an old version). Again thanks so much.