Read This
http://forum.xda-developers.com/showpost.php?p=9542514&postcount=662
Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.
Still not that simple for me, since even a "Gtablet Vet" like myself tried the OP method and failed. My second out of box new Gtablet went in perma-loop when simply installing straight to 2.0, via recovery folder & update.zip. Ended up having to get CW on the device by putting on the sd card, remapping command and stopping the loop with power + volume to get CW installed. I then had to install TnT 1.02 and then finally got 2.0 installed after that (cache and data wipe of course).
Cleanest way seems install 1.02 via recovery folder / update.zip method and then install 2.0 the same way. Thats is unless I just had bad luck with second Gtablet. VERY possible.
added:
Frankly, we seem at the stage now where CW seems a survival requirement- IF you want to keep trying new roms & updates.
roebeet said:
Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.
Click to expand...
Click to collapse
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
Installing TnT 1.0 roms appears to zap CW pretty good.
roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
I have found that you can put the stock recovery img (let's call it recovery-stock.img) on the sdcard and get an adb shell while booted into cw recovery. Then it's just a
Code:
flash_image recovery recovery-stock.img
That should get you back to stock recovery.
Sent from my Incredible using XDA App
LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
I had to go back to stock at first because I kept getting status 7 errors with CW. Roebeet's suggestion to partition sdcard with CWR seems to have solved that.
Sent from my Incredible using XDA App
Flashed 2.0.0
I liked TnT 2.0.0 and it really helped performance but the gtab is still full of issues....
Out of the box my Gtab's proprietary email and photo app forced closed before ever loading. the viewsonic update didn't fix it and so I flashed it with TnT 2.0.0.
I got a System UID's warning while I did it and I guess that was the cause of those apps not working. I then did a system reset to factory default or whatever its called and lost everything but after flashing TnT 2.0.0 again it worked a lot better and the email app worked great, photo app still doesn't work. My new problems are that the sound and and flash don't work anymore. I reinstalled flash and the browser just crashes whenever flash is involved with a site. Sound will sometimes work when I first boot up but it quits after a while, especially after waking from sleep. A lot of the time I get crackles and pops when I first boot up or wake it from sleep.
I am returning this Gtab and I am going to buy another one from somewhere else in hopes that I don't get these issues out of the box.....I haven't read anywhere that anyone has experienced these specific problems other than the sound; as this is a TnT error; so I warn all, DON'T BUY FROM STAPLES!!!
Related
Ok guys so here is a little something i have been working on for yall. some of you may know rom manager and all its abilities (download roms and flash them without needing a computer, aka "OTA custom roms") well its done. only one team has the roms up and listed right now. now here is for the issues;
-rom manager does not recognize anything but 2.5.1.0 which is the first version of cwm we had going. afaik there are no plans to let it see cwm3 on teh epic
-any roms put on the list will be under premium, sorry ive tried talking to koush but this means you would need to have rom manager premium
now i am hoping we can get more rom devs up on the list and push for cwm3 to be recognized so that users of a certain rom can get notifications of updates and download them via wifi/4g/3g whenever they want. obviously i dont expect people to pay for the premium rom manager when they cant get the free one working.
if any rom devs wish to have their roms added to the list i will not do it for you but after a couple of hours of screwing with the lists (they are javascript.... >.<) i can offer some help on what may not be working. i am in the irc channels almost all the time, if you cant reach me there then shoot me a pm..
P.S. you may be wondering why i posted this in general eh? because this is partially for devs, but its for the users of the epic.. if this is a feature you want then yall need to speak up cuz as it stands now its pretty useless, im hoping by putting this out there that there will be enough of a cry for it that the situation gets handled and then everyone can use koush's awesome program
shabbypenguin said:
Ok guys so here is a little something i have been working on for yall. some of you may know rom manager and all its abilities (download roms and flash them without needing a computer, aka "OTA custom roms") well its done. only one team has the roms up and listed right now. now here is for the issues;
-rom manager does not recognize anything but 2.5.1.0 which is the first version of cwm we had going. afaik there are no plans to let it see cwm3 on teh epic
-any roms put on the list will be under premium, sorry ive tried talking to koush but this means you would need to have rom manager premium
now i am hoping we can get more rom devs up on the list and push for cwm3 to be recognized so that users of a certain rom can get notifications of updates and download them via wifi/4g/3g whenever they want. obviously i dont expect people to pay for the premium rom manager when they cant get the free one working.
if any rom devs wish to have their roms added to the list i will not do it for you but after a couple of hours of screwing with the lists (they are javascript.... >.<) i can offer some help on what may not be working. i am in the irc channels almost all the time, if you cant reach me there then shoot me a pm..
P.S. you may be wondering why i posted this in general eh? because this is partially for devs, but its for the users of the epic.. if this is a feature you want then yall need to speak up cuz as it stands now its pretty useless, im hoping by putting this out there that there will be enough of a cry for it that the situation gets handled and then everyone can use koush's awesome program
Click to expand...
Click to collapse
I thought this app was a cool idea when I first saw it..... then I realized it didn't work, and I never installed it anymore. if you can get it going, that would be awesome.... you've got my vote!
yogi2010 said:
I thought this app was a cool idea when I first saw it..... then I realized it didn't work, and I never installed it anymore. if you can get it going, that would be awesome.... you've got my vote!
Click to expand...
Click to collapse
He got it working <_<'
Thanks a bunch shabby! This should help with user error issues when it comes to flashing =D
I never see any roms when I go to download roms and I have the premium I thought that was bs.
Epic 4g
jbadboy2007 said:
I never see any roms when I go to download roms and I have the premium I thought that was bs.
Epic 4g
Click to expand...
Click to collapse
tahts because no one ever took the time to post em on there. im hoping to change that
I'm currently running cwm3; but when I open ROM Manager it tell me im running 2.5.1.0...
With that said.. I wonder if it'll work? ;p
wait you get rom manager to work with cwm3???
shabbypenguin said:
wait you get rom manager to work with cwm3???
Click to expand...
Click to collapse
No no no. I'm a moron disregard what I said haha.
All thats happened is ROM Manager thinks I'm running 2.5.1.0 when I'm not.
But; shouldn't this just be a redirector issue?
right but even with it thinking you have 2.5.1.0, what version of cwm do you have? does it pop up and ask you to install cwm version x.x.x.x???
I'm running cwm 3 running ext4.
Rom manager works on the phone; but anytime it needs to go into cwm it fails.
It'll hang at the sammy logo. Pulling the battery and powering the phone up normally does the same.
However..doing the three button recovery boot it attempts to load cwm and fails then gives me the Triangle with an Exclamation point inside it..along with the green android.
so how do you get into recovery? also is it 3.0.0.5 or 3.0.0.6?
shabbypenguin said:
so how do you get into recovery? also is it 3.0.0.5 or 3.0.0.6?
Click to expand...
Click to collapse
3.0.0.6
I'm unable to get into recovery through the manager it self. Once I do the three finger salute..it attempts to load and fails; I pull battery and just hold the power button and it loads into cwm.
ok so sounds like 3.0.0.6 is sorta working but we just need to be able to get into recovery normally now....
3.0.0.5 is confirmed to not be working at all
I would love this... had premium on my hero, but sadly I cannot use it on my epic.
Sent from my Samsung-SPH-D700 using Tapatalk
shabbypenguin said:
ok so sounds like 3.0.0.6 is sorta working but we just need to be able to get into recovery normally now....
3.0.0.5 is confirmed to not be working at all
Click to expand...
Click to collapse
Seems to me like it's just a redirector issue; but I've yet to dig into this too deeply so I could be wrong.
It seems to work fine..it just has issues loading directly into cwm.
Hey peeps hopefully someone here can help with almost similar problem.
I used one click root with cwm recovery 2.5.5 in both 2.1 DI18 and EB13. The recovery installed just fine on both.
When I download Rom manager from clockworkmod it doesnt detect that the recovery is installed. I cant do anything without installing the recovery according to ROM manager.
BUT it is installed! Why doesnt it detect it??
How can I get the rom manager to see that I do have clockworkmod recovery 2.5.5 installed?
Or is it not possible yet? I too am a suckered premium owner.
ErlyD said:
Hey peeps hopefully someone here can help with almost similar problem.
I used one click root with cwm recovery 2.5.5 in both 2.1 DI18 and EB13. The recovery installed just fine on both.
When I download Rom manager from clockworkmod it doesnt detect that the recovery is installed. I cant do anything without installing the recovery according to ROM manager.
BUT it is installed! Why doesnt it detect it??
How can I get the rom manager to see that I do have clockworkmod recovery 2.5.5 installed?
Or is it not possible yet? I too am a suckered premium owner.
Click to expand...
Click to collapse
I don't think that ROM Manager can detect recoveries on the phones partitions. I believe it downloads and installs recovery to the sd card.
I some how managed to get an older recovery installed 2.5.1 But still get "an error occured while downloading your recovery." when I click any option and select samsung epic from the prompted list. In an attempt to install the recovery.
If it doesn't install to the fixed partitions how does it install the recovery to boot from? I thought thats where it had to be? That would mean the current recovery I have is in the SD card? then a simple edit of a file would allow it to be detected?
ErlyD said:
I some how managed to get an older recovery installed 2.5.1 But still get "an error occured while downloading your recovery." when I click any option and select samsung epic from the prompted list. In an attempt to install the recovery.
If it doesn't install to the fixed partitions how does it install the recovery to boot from? I thought thats where it had to be? That would mean the current recovery I have is in the SD card? then a simple edit of a file would allow it to be detected?
Click to expand...
Click to collapse
I believe ROM Manager uses the stock recovery to redirect to a zip file on the sd. If the redirector isn't set up right it won't work. The One-Clicks we use to install CWM install it to fixed partition.
I do see that the ACS team is on board with this, hope to see more support soon. On my buddies Fastinate there is quite a bit to work with in Rom Manager, it is a very cool option.
Thanks to all the Dev's
Sent from DEEZ
This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor
Yes this try to keep this thread open.
Sent From My Evo Killer!
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force
forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.
olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.
Duplicate... Sorry
forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted
Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3
Hi All, maybe someone can help me out with this. I just perm-rooted yesterday and have s=off, but I'm still just running the stock rom, haven't flashed anything other than faux's smartass kernel, I am using Launcher Pro Plus instead of MySense though, if that matters at all.
The only other thing I really want to do at the moment is flash one of pack's cool battery icon mods, and it fails at installation through Clockwork recovery. I was told I need to us Clockwork 2.5.1.x to flash it, and here's my problem: In Rom Manager, under "All ClockworkMod Recoveries" when I try to flash to a 2.5.1.x recovery, it says "An error occurred while flashing your recovery". It allows me to flash both 3.x recoveries smoothly, but neither of the 2.x ones work, and I've been searching and reading and can't seem to find any answers. Does anyone know what I need to do? I want that darn battery mod lol.
You likely have a bad download-verify the file size of the download on the website and compare it to the size of the file you actually downloaded
ronin178 said:
You likely have a bad download-verify the file size of the download on the website and compare it to the size of the file you actually downloaded
Click to expand...
Click to collapse
Thanks for the suggestion - I've tried 2 different versions of the battery mod and the file sizes seem to match what's on the site. Neither one works though
UPDATE: I got it sorted out with some guidance from a helpful poster. Thanks Ronin for offering assistance.
IGNORE THREAD
Glad you got it figured out-do you mind posting what you did in case someone else should run into this issue....
ronin178 said:
Glad you got it figured out-do you mind posting what you did in case someone else should run into this issue....
Click to expand...
Click to collapse
Sure, no problem. The problem was Rom Manager, it wouldn't let me flash 2.1.5.x, which is needed to install the battery mod. What I had to do was download 2.1.5.2 version of clockwork, move to clockwork "recoveries" folder on sd card, rename "2.1.5.4." so that Rom Manager could find it, then I was able to flash the 2.x version of clockwork, after which the battery mod worked fine. The problem was that before I did this, there was no 2.1.5.x recovery to flash.
sunsean said:
Sure, no problem. The problem was Rom Manager, it wouldn't let me flash 2.1.5.x, which is needed to install the battery mod. What I had to do was download 2.1.5.2 version of clockwork, move to clockwork "recoveries" folder on sd card, rename "2.1.5.4." so that Rom Manager could find it, then I was able to flash the 2.x version of clockwork, after which the battery mod worked fine. The problem was that before I did this, there was no 2.1.5.x recovery to flash.
Click to expand...
Click to collapse
Why depend on ROM Manager? You could have used terminal to flash it, then you wouldn't have had to rename the file and could have had it wherever you wanted.
TeeJay3800 said:
Why depend on ROM Manager? You could have used terminal to flash it, then you wouldn't have had to rename the file and could have had it wherever you wanted.
Click to expand...
Click to collapse
I know this is flame-worthy, but I was doing it through Rom Manager because it seemed easier and less prone to user error. I'm a competent guy, and I'm good at following directions and reading, but I'm not a tech whiz, so I guess I used Rom Manager because it's got a nice user friendly interface and streamlines the process.
No flaming man, just a suggestion since so many people seem to have problems with corrupt recoveries and recoveries not "sticking" when flashing with ROM Manager. In your case it would have made life a lot easier as well.
Lol, yeah, I hear you. But once I realized what the problem/obstacle was, fixing it was actually really easy. It was just the issue of why it wasn't flashing. But I get your point - I could've not had to worry about Rom Manager at all.
Thanks, going forward I'll try alternative approaches to figure out what is easiest and what works best.
sunsean said:
Sure, no problem. The problem was Rom Manager, it wouldn't let me flash 2.1.5.x, which is needed to install the battery mod. What I had to do was download 2.1.5.2 version of clockwork, move to clockwork "recoveries" folder on sd card, rename "2.1.5.4." so that Rom Manager could find it, then I was able to flash the 2.x version of clockwork, after which the battery mod worked fine. The problem was that before I did this, there was no 2.1.5.x recovery to flash.
Click to expand...
Click to collapse
Where can I download clockwork 2.1.5.2?
illfxckinqwill said:
Where can I download clockwork 2.1.5.2?
Click to expand...
Click to collapse
use the search button please
illfxckinqwill said:
Where can I download clockwork 2.1.5.2?
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=978038
Lol, I guess you should use the search function, but it would be hypocritical of me to not provide it for you as I came upon it through the help of another poster. I don't see the harm in saving someone the time from having to dig through a pile of threads to find something.
Someone asked if it was possible to flash ClockworkMod Recovery through hboot instead of using RomManager. The answer...yes.
Primary reason something of this nature may be useful, as I see it, is if your recovery is damaged, your ROM is bootlooping, and you don't want to use or have access to ADB.
In that case you would:
remove your sdcard from your phone
place the zip on the root of the sdcard (using an adapter or another phone) and make sure it is named the appropriate "PG05IMG.zip"
place the sdcard back in your phone
boot to bootloader as if you're installing a radio (power+VolDown from powerOff). It will then find the zip, recognize it as recovery and ask if you want to install (if it does not prompt then select "Bootloader" from hboot).
Follow the instructions and after it finishes flashing pull your battery to power off (since the ROM will be bootlooping and hboot will constantly find the zip)
Now remove the sdcard and delete the zip (via adapter or other phone) like you did to put it on the sdcard, then place the card back in the phone.
Boot back to bootloader (Pwr+VolDwn)
Select "Recovery" and use CWR to wipe data/cache, flash a new rom, restore, or whatever you wish.
Obviously not the only reason since some people prefer this method over RM but clearly in that case the whole sdcard switching mess is unnecessary. Just do steps 2 and 4 and reboot when prompted like you do with radios.
Remember to remove any PGO5IMG.zip from your sdcard when done.
If this isn't useful to you, so be it. I just figured I'd throw this out there. Maybe it will help someone.
I will keep this updated as new versions come out for those few that find it useful.
**Credit to Koush and jcase**
All I did was decide to throw them in a zip that was useful in some situations for panicking users.
Updates
8/9/2011: Added latest official stable for mecha (4.0.1.5) released 8/8/2011.
8/30/2011: Added latest official stable for mecha (5.0.0.1) released less than an hour ago. Added mirror.
8/31/2011: Added latest official stable for mecha (5.0.0.8)
9/1/2011: Added latest official stable for mecha (5.0.1.0)
9/5/2011: Added latest official stable for mecha (5.0.2.1)
2/1/2012: Added touch based CWR released this morning (5.8.0.2) *NOTE: Have not personally tested.
If any of these cause problems please let me know immediately.
Latest Official=5.0.2.1
jcase modded=4.0.0.5
Mirror: http://www.mediafire.com/?9zt68cegl6qa3
MD5:
66750618ecfba292c0b0e42c50c2c3ee - (CWR3.1.0.2)PG05IMG.zip
1f390edad7e87310fe80b3264a57b14b - (CWR4.0.0.5)PG05IMG.zip
6aac529cedcd2b22afac7391a4cb7efb - (CWR4.0.1.5)PG05IMG.zip
bf25b2601441b9fffb7d68954c4ff3b5 - (CWR5.0.0.1)PG05IMG.zip
dfe1ddf0c574977ee2c1828735ef2dc0 - (CWR5.0.0.8)PG05IMG.zip
8474c8d607177b0144eec624dea687b7 - (CWR5.0.1.0)PG05IMG.zip
c4c1d9c5e553fd7b151352551b931369 - (CWR5.0.2.1)PG05IMG.zip
58557e1e355c795d748c2e6c66251f0a - (CWR5.8.0.2)PG05IMG.zip
Absolute_Zero said:
Someone asked if it was possible to flash ClockworkMod Recovery through hboot instead of using RomManager. I didn't see the need at the time but I took a few minutes to throw together a test. Let me know if it works for you or not.
I tested flashing the stock recovery from the custom firmware, confirmed it had replaced CWR, then used this to install CWR back.
Primary reason something of this nature may be useful, as I see it, is if your recovery is damaged, your ROM is bootlooping, and you don't want or have access to ADB. In that case you would just pull your sdcard, place this on the root (via adapter or someone else's phone) named the appropriate "PG05IMG.zip", place back in your phone, and boot to bootloader as if you're installing a radio. It should then find it, recognize it as recovery and ask if you want to install.
Additionally, seems if it is as easy as swapping the .img out which is all I did, then the original custom upgrade firmware flashed in the last step of the root guide could include this. Then you'd have CWR immediately after finishing the permaroot guide.
If this doesn't work and doesn't have any use for anyone, so be it. I just figured I'd throw this out there.
BTW, this is ClockworkMod Recovery 3.1.0.2 (latest for mecha at time of posting).
Note1: Only tested on Engr hboot with S-off obviously
Note2: I don't have access to an MD5 generator where I am so people that test this should have a booting ROM with RomManager or at least know how to manually reflash ClockworkMod Recovery if it doesn't work.
Click to expand...
Click to collapse
Good work.on this... A LOT of people are going enjoy it!! It is also a great way to install the modded 4.0.0.5 Clockwork with the boot to bootloader option.
I always had to "flash recovery" in adb.
Props!!
Sent from my ADR6400L using XDA App
good post will definitely come in hand props
DroidTh3ory said:
Good work.on this... A LOT of people are going enjoy it!! It is also a great way to install the modded 4.0.0.5 Clockwork with the boot to bootloader option.
I always had to "flash recovery" in adb.
Props!!
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
There's a modded 4.0.0.5 CWM Recovery out there?? Where can I find the post for this ?
Sword.Zero said:
There's a modded 4.0.0.5 CWM Recovery out there?? Where can I find the post for this ?
Click to expand...
Click to collapse
Post a link to it and I'll make one when I get home. That way I can test again. Hopefully the modded one you speak of is fully stable and functional.
Absolute_Zero said:
Post a link to it and I'll make one when I get home. That way I can test again. Hopefully the modded one you speak of is fully stable and functional.
Click to expand...
Click to collapse
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment (CWR4.0.0.5)PG05IMG.zip
DroidTh3ory said:
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment 661641
Click to expand...
Click to collapse
In your case it would probably be easier to just use flash_image from terminal on the phone (i.e. flash_image recovery /sdcard/recovery.img) assuming your current rom has it (if not just search and download it) or you have RM installed. The main case I saw this being useful was if you didn't have or want to use ADB and your ROM was unusable (e.g. bootlooping). I may add Jcase's modded recovery to the OP as well since it seems useful/wanted by some.
I thought the one JCase made had issues with nandroid backups installing? I could be wrong but for some reason I remember that issue for several people.
Mustang302LX said:
I thought the one JCase made had issues with nandroid backups installing? I could be wrong but for some reason I remember that issue for several people.
Click to expand...
Click to collapse
I have been using for a good month now on 3 different bolts... Never had a issue??
Absolute_Zero said:
Additionally, seems if it is as easy as swapping the .img out which is all I did, then the original custom upgrade firmware flashed in the last step of the root guide could include this. Then you'd have CWR immediately after finishing the permaroot guide.
Click to expand...
Click to collapse
actually,thats allready how it is ive rooted mr2 twice and the mr1 upgrade allready has clockwork installed.
it is that easy,i have done this,and i have also removed the hboot and stock recovery from PG05IMG RUUs so that i could flash without destroying recovery and my eng bootloader.
thanks for putting it together and offering the download, it has many uses, as people will see. the biggest one allready having been mentioned,if something screws up your OS and recovery,its easy to get it back.
did you make up your own android info file? or what did you take it from?
again thanks for posting this,it was commonplace to install inc recoverys in hboot,and ive done it on the eris as well
DroidTh3ory said:
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment 661641
Click to expand...
Click to collapse
thanks for the download. has he put up any posts on it? or is it still being developed?
scotty1223 said:
thanks for the download. has he put up any posts on it? or is it still being developed?
Click to expand...
Click to collapse
I believe he has it posted on rootzwiki
Sent from my ADR6400L using XDA App
cool,thanx... ill go over there and look for it.
edot:
here if anyone else wants it
Thanks for this. Just flashed 4.0.0.5 after being afraid/too lazy to do it through ADB (which is also a pain because I have it on my Windows partition whereas I regularly use Mac).
scotty1223 said:
actually,thats allready how it is ive rooted mr2 twice and the mr1 upgrade allready has clockwork installed.
Click to expand...
Click to collapse
Figures. It was too simple of a concept not to have been done but I didn't see anyone that had done it in Tbolt. I also hadn't seen anyone mention it was in the custom firmware either and I didn't have time to check this morning before I left for work. I guess I can pull that part out of the OP since you say it's already in there.
thanks for putting it together and offering the download, it has many uses, as people will see. the biggest one allready having been mentioned,if something screws up your OS and recovery,its easy to get it back.
Click to expand...
Click to collapse
Exactly my reasoning. I've seen to many people unaware of what to do in that situation
did you make up your own android info file? or what did you take it from?
Click to expand...
Click to collapse
I checked a few from the firmware and radios and they all looked the same so I just pulled one of those.
again thanks for posting this,it was commonplace to install inc recoverys in hboot,and ive done it on the eris as well
Click to expand...
Click to collapse
First HTC android phone I've owned but as I said, makes sense it would have been done a long time ago for other HTC phones.
DroidTh3ory said:
I believe he has it posted on rootzwiki
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Hey get out of here, you've got candy to make! I keeeed I keeeed! Great work on the recovery guys, VERY useful!
Sent from my ADR6400L using XDA Premium App
DroidTh3ory said:
I have been using for a good month now on 3 different bolts... Never had a issue??
Click to expand...
Click to collapse
Yup. Been using it since it's release. Restored many backups with absolutely no issues.
Absolute_Zero said:
Figures. It was too simple of a concept not to have been done but I didn't see anyone that had done it in Tbolt. I also hadn't seen anyone mention it was in the custom firmware either and I didn't have time to check this morning before I left for work. I guess I can pull that part out of the OP since you say it's already in there.
Click to expand...
Click to collapse
id be willing to bet most people dont know,lol.they prolly just blindly downloAd rom manager and flash it. i checked to see if it was there,after seeing this as one of the last statements in the root post: Reboot your phone. You should now have full root permissions, an engineering kernel and recovery.
Absolute_Zero said:
First HTC android phone I've owned but as I said, makes sense it would have been done a long time ago for other HTC phones.
Click to expand...
Click to collapse
its one of the things i really love about htc. i got used to installing recoverys,splash screens,etc. on my incredible,then started experimenting with img files on my eris,and discovered it was quite possible to simply move the images around kinda neat if you want to try a leaked ruu but dont want to wait for someone to post a CWM flashable roms. just pull out the hboot and stock recovery and flash away
it was quite common to manipulate things in hboot on the inc,but never mentioned in the eris forum,where most of the gurus frowned upon the s-off bootloader.kind of a shame... more bricked eris's prolly could have been revived after the clockwork fiasco if s-off was part of the common root process.
thanx for the android info info. when i make them up,it doesnt seem to matter which one i use. i dont think it even checks the text inside,i think you just need a text document titled "android info" lol
Thank you for the updated 5.0.0.1 cement recovery.
cam30era said:
Thank you for the updated 5.0.0.1 cement recovery.
Click to expand...
Click to collapse
Autocorrect fail? or did you have a problem with 5.0.0.1?
im trying to put a recovery on my vibrant that i have and i have root access but when i try to intall rom manager so i can get the recovery i do not find it in the app store. i still have the OLD app store that has lots of green borders. When i look for rom manager, i find te paid version but not the free version and when i try manually installing the apk...
it says parsing error. can i get some help wth the please.
Not sure, but here is the direct downloaded ROM Manager (free)
http://www.mediafire.com/?523y13j76z66lb7
Thanks for the download.
I tried installing it but it did the same thing. It said parsing error
Download cwr from my signature. Put update.zip on your internal and make sure it is only thing labeled that on there. Boot into stock recovery (blue) and hit Reinstall Packages, let it cycle, hit it again and stock (blue) now becomes cwr (green) and flash away
Woodrube said:
Download cwr from my signature. Put update.zip on your internal and make sure it is only thing labeled that on there. Boot into stock recovery (blue) and hit Reinstall Packages, let it cycle, hit it again and stock (blue) now becomes cwr (green) and flash away
Click to expand...
Click to collapse
will do but is it safe to do this if i rooted with zRoot and if i am on stock rom 2.1-update1
Yes that is the best way as a matter of fact. Btw what ROM are you wanting to flash?
i want to get any form of ICS on the vibrant, if yo could also help me with that i would greatly appreciate it.
lol i just saw your sig, you are very prepared in helping noobs xD
WOW i have been trying to install CWM since thursday and with your method i did it within a matter of seconds! Thanks!!
Again see link in my signature for ICS install instruction. I suggest you play with a 2.2 like Fishman 's Bionix and familiarize yourself with handling functions like flashing, restoring, ram tweaks, ....otherwise you might get into more than you can handle. ICS is a pretty advanced flash and could potentially brick your device if something goes wrong. Not as easy as just flashing update.zip, hence my guide. Also see warning at the top of the guide. Very important and the cause/solution is still WIP.
Also you are on your own for finding the needed files. Sorry but my dropbox acct has been getting flexed lately so i am giving it a break. Good luck and make sure you hit Xrider's thanks for posting in two separate threads to helps you with the .apk.
Going to bed. Good luck.
Woodrube said:
Again see link in my signature for ICS install instruction. I suggest you play with a 2.2 like Fishman 's Bionix and familiarize yourself with handling functions like flashing, restoring, ram tweaks, ....otherwise you might get into more than you can handle. ICS is a pretty advanced flash and could potentially brick your device if something goes wrong. Not as easy as just flashing update.zip, hence my guide. Also see warning at the top of the guide. Very important and the cause/solution is still WIP.
Also you are on your own for finding the needed files. Sorry but my dropbox acct has been getting flexed lately so i am giving it a break. Good luck and make sure you hit Xrider's thanks for posting in two separate threads to helps you with the .apk.
Going to bed. Good luck.
Click to expand...
Click to collapse
Thanks you are a big help.
i am just a noob in this phone. i have been flashing and roting ever since the G1, i had the G1, Mytouch3g, Mytouch 4g, and i am currently using my amaze 4g, but i also have a vibrant that i want to root and put ICS on it but thanks!