Does anyone have a copy of teamwin recovery 1.1.1 I've tried getting it from the site but no go I don't know if it matters but i have hboot1.5
Sent from my PG86100 using XDA App
Have you tried this link on the site?
Under: PROJECTS (Tab) -> TWRP -> TWRP 1.x
http://teamw.in/project/twrp/67
Why wouldn't you want the latest one or latest with Dumlock?
I heard bad things about the newest is it ok ,dies flash GUI do a good job flashing recoverys
Sent from my PG86100 using XDA App
Flashimage works well for flashing recoveries and kernels before a ROM. I've used it and it works well & as advertised, but u can't just enter recovery to restore a backup with it (need fastboot). I've used Cwm 4.0.1.4, Cwm Touch 5.0.8.2 (no usb mount/charging), and TWRP 2.0RC1 (with & w/o Dumlock).
Now, imo, I don't prefer to rely on FlashImage with S-On and think that all new HTC Unlocked/S-On users need to get experience flashing & booting to recovery via fastboot command prompt. This avoids most of the issues people experience like "my phone boot loops" & "flashed rom, now my phone stuck at white screen" etc. If ur using the correct fastboot commands all the recoveries I mentioned work pretty much the same minus the Touch features.
People run into problems not fully understanding these "workaround apps" (flashimage & Dumlock) even though the directions are well written. I just think some newcomers jump on these shortcuts and end up back to using fastboot anyway.
Currently I am using the TWRP 2 w/Dumlock and like that I can flash w/o fastboot (& restore nand backups too). If u don't follow steps correctly u can screw ur boot and have to use fastboot to reload recovery & restore backup. Other than fastbooting to recovery its the only way to fully restore a nand backup (b/c kernel flash). Note: u don't have to use Dumlock, but its part of the newer version if u want to.
I personally like the Touch screen version of Cwm & haven't had any issues other than the Usb issues I mentioned. I may give the Universal Dumlock option a go since it can be used with Cwm, but it won't be baked into the recovery. Also, I read that Agrabren left Team Win so future development of TWRP may be limited.
There's a lot of opinion in my post, but I hope I answered your question.
I'll also point out my guide/flashing notes & ROM/recovery issue (scenarios) in my signature have some detailed examples of what I did when using / flashing roms etc.
Sent from my PG86100 using Tapatalk
Related
I recently rooted my phone and flashed the TWRP recovery for it as it was recommended on IRC. One of my favorite apps when I had my rooted 4G was Rom Manager. It allowed me to easily backup and flash roms whenever I pleased.
Is there something similar to that for TWRP? Rom Manager requires having Clockwork Mod recovery to use. Also what are the advantages / disadvantages if any to either recovery?
Sent from my Evo 3D using XDA Premium App
I like doing everything manually from recovery myself. The advantages of TWRP of CWM is the ease of access of certain options in the menus. I love having the wipe cache and dalvik cache as an option in the install zip menu. You can also change the theme easily. I like the backup options in the Nandroid menu and the fact that it backs up your wimax partition. There are many advantages in TWRP over CWM imo. It is designed for the Evo 3D natively and CWM is a port, so it's options are not designed for the Evo 3D. TWRP is just laid out better and you don't have to scroll through the work no 8 times just to wipe cache. Rom Manager is nice, but even when I did use CWM on my NS4G, I never, ever used the app because I just feel safer doing things manually.
All this is a matter of opinion, so it ultimately is up to you. Maybe the ultimate and best reason to shoose TWRP over CWM is because when you go into the Wipe Menu there is a roll of toilet paper in the background.
There working on something similar to rom manager
Instead of making a new thread ill go ahead and ask here. I'm currently doing a Titanium Backup of my apps / data. I'm also going to do a nandroid backup using TWRP since I've decided to dive into a rom. Are there any other recommended steps I should take before I flash? I hear talk of kernals but know nothing about them.
*Edit
To be more de specific this is the rom I plan on using.
[ROM][8-21-11][2.3.4] gbsense-e3d-deck [0.5]
I read in his thread there was only 2 kernals for 2.3.4, stock and another custom that's floating around.
Sent from my Evo 3D using XDA Premium App
If you are going to a 2.3.4 Rom I would stick with the stock kernel that comes with the Rom for now. Until HTC releases the source for the 2.3.4 kernel we won't have any custom kernels to flash. I would suggest searching here and on Google what is a Linux kernel and what benefits a custom kernel can give you in Android.
Also, if you flash an incompatible kernel it will at least break things like wifi, sms, mms and other functions of the phone and at most completely make your phone unbootable and you will have to nandroid restore.
housry23 said:
If you are going to a 2.3.4 Rom I would stick with the stock kernel that comes with the Rom for now. Until HTC releases the source for the 2.3.4 kernel we won't have any custom kernels to flash. I would suggest searching here and on Google what is a Linux kernel and what benefits a custom kernel can give you in Android.
Also, if you flash an incompatible kernel it will at least break things like wifi, sms, mms and other functions of the phone and at most completely make your phone unbootable and you will have to nandroid restore.
Click to expand...
Click to collapse
So in other words i can just flash this Rom and i'm good to go.
Yep. The Rom's always include a kernel. If you want a custom kernel, that is a separate flash. Some Rom's include a custom kernel and some include stock kernels. I will say that I am using a Rom based off the HTC 2.3.4 update and has the stock kernel and it is actually very smooth and runs fast. I really am not sure overclocking is necessary on this phone, especially after all of the Sprint and HTC bloat are taken out. Though I can understand why people want and do overclock, but seriously benchmarks don't mean shiz to me. How the phone runs in real time use and how the battery performs are my greatest concerns.
I had the same question as the OP. It looks like i won't be using rom manager. Can you point me to a step-by-step on rom flashing using TWRP? Thanks. All google searches seem to return flashing "how to's" using CWM Rec.
meccadon123 said:
I had the same question as the OP. It looks like i won't be using rom manager. Can you point me to a step-by-step on rom flashing using TWRP? Thanks. All google searches seem to return flashing "how to's" using CWM Rec.
Click to expand...
Click to collapse
curious about this too, i've searched here and googled with no luck. everything i find only explains step by step with rom manager/clockwork
i'm assuming you just enter recovery, select install zip -> choose zip to flash -> select your custom rom.zip from the list and then let it do it's thing.
just want to be sure so hopefully someone can confirm or post proper steps.
meccadon123 said:
Can you point me to a step-by-step on rom flashing using TWRP? Thanks. All google searches seem to return flashing "how to's" using CWM Rec.
Click to expand...
Click to collapse
finally found someone who would actually respond. not step by step per say, but i you read this post you should get the idea
http://forum.xda-developers.com/showpost.php?p=16982135&postcount=4402
meccadon123 said:
I had the same question as the OP. It looks like i won't be using rom manager. Can you point me to a step-by-step on rom flashing using TWRP? Thanks. All google searches seem to return flashing "how to's" using CWM Rec.
Click to expand...
Click to collapse
jorts said:
curious about this too, i've searched here and googled with no luck. everything i find only explains step by step with rom manager/clockwork
i'm assuming you just enter recovery, select install zip -> choose zip to flash -> select your custom rom.zip from the list and then let it do it's thing.
just want to be sure so hopefully someone can confirm or post proper steps.
Click to expand...
Click to collapse
Assuming you already have S-OFF you just need this file http://www.techerrata.com/android/twrp/PG86IMG-twrp-shooter-1.0.3.zip
*Download flashable zip from the OP and rename it "PG86IMG.zip" (without the quotes)
*Place in the root of the sdcard
*Power off phone (make sure you turn off hot boot or pull the battery when it's off)
*Power on the phone holding power and volume down
*Follow the prompts to flash it
*Delete .zip (PG86IMG.zip) after booting
*Enjoy
(Credit to ViViDboarder)
If you have any other questions head to
http://forum.xda-developers.com/showthread.php?t=1192077
What is the best method to use to update Kernels and ROMs?
I'm using Flash Image to flash the Kernel and TWRP to flash the ROM but I see alot of other methods out there not sure what the best is to use?
Just and FYI I use the HTC unlock method with S-on
I've been using ClockwordMod for 6 months now and have had no issues. It always works just fine for me. I see other people who say that TWRP is the best, but have yet to understand or see anyone give a good reason as to why it is better. I've thought about installing TWRP, but since Clockwork has worked great for me, I don't see the benefit unless someone can enlighten me?
I use twrp 1.1.1 its my favorite one of all and I tried all of them. You can flash multiple zips all at 1 time. Im on hboot 1.5 so I always fastboot into recovery so I know kernel will stick. Some roms out there will not flash unless you use twrp 2.0 you just have to read devs OP's thoroughly.
Jabawockee said:
I use twrp 1.1.1 its my favorite one of all and I tried all of them. You can flash multiple zips all at 1 time. Im on hboot 1.5 so I always fastboot into recovery so I know kernel will stick. Some roms out there will not flash unless you use twrp 2.0 you just have to read devs OP's thoroughly.
Click to expand...
Click to collapse
I agree with Jabawockee. I've tried them all and 1.1.1 is great but for just flashing a different kernel i use gui and to just flash mods I was gui to flash my recovery then reboot into recovery and flash my mods.
Dear all
i have a droid eris with 1.5 firmware i root it and did a backup withe clock work mode
the i tried to install a cyanogenmod custom rom it went fine then when i boot my phone it stuck on the logo screen so i turned it off and went to the recovery mode and i try to do a restore for my backup what i get is the following message
"erasing boot before restore...
restoring boot image...
Error while flashing boot image "
and return me to previous selection
and then i tried to download a custom rom and it goes with the following error
assert failed: write_raw_image("/tmp/boot.img", "boot"
so my phone is stuck in the logo screen can you help me please.
Did you get the rom from xda? Also, you should try to flash different rom's that contain Cyanogen (ex: GSB). I may not know much but hope this helped.
P.S I would incite you to Wipe data/cache before flashing a rom; from my personal perspective, I think when you flash a rom and don't wipe, it piles up; and well the phone may not work as expected(ex: glitches). Good luck
i tried but nothing work i don't know what to do i have a guy who has a box to do reflash is it going to work shall i try it
Find and flash an RUU, then install amon ra recovery. Clockwork rom cause trouble on Eris.
Sent from my Galaxy Nexus using xda premium
I may not very adept in these things, however, there is a rom that restores everything back to OTA 2.1 from my knowledge. I admonish you to use that, I presume that it might fix it. In such a grievous state; that would perhaps be an essential option to you.
Sent from my ERIS using xda premium
Find and flash an RUU, then install amon ra recovery. Clockwork rom cause trouble on Eris.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Good thing you pointed this out, as I am too discordant with the use of ClockworkMod in the Eris; as it has proved to promote some minor complications when running.
Sent from my ERIS using xda premium
I will try it and letnu know
ramses77 said:
I will try it and letnu know
Click to expand...
Click to collapse
One more thing, from what I am aware of; there is an application on the Market that actually installs a custom recovery. It's issued as HTC Eris One Click, look it up, I would admonish you to use it; it works more efficiently on the Eris than ClockwordMod does.
Hope this actually benefits
If his phone won't boot an app won't do any good..
There is an ruu or pb img file with an unlocked boot loader. Or try unrevoked to unlock the boot loader. Then you can fast boot flash your recovery.
Its been a while since I retired my Eris, but I'm sure there are still tutorials out there.
Google search is your friend.
Good luck.
Sent from my Galaxy Nexus using xda premium
As far as I know, an Eris flashed with Clockwork as the default recovery that tries to flash an RUU is a quick method to leaving yourself with a brick.
If the OP can restart in Recovery (hold down VolUp while starting the phone), then I would try a wipe data/factory reset. Also, if you can start in Recovery, flash the Flashback_21 ROM (which restores the stock recovery and stock Eris 2.1 software as of the March 2011 OTA) and then re-root with the 1-click Eris root app in the market. Leaving Clockwork as the default Recovery has tended to be a recipe for disaster.
Flashback is here; the non-radio version should be fine: http://forum.xda-developers.com/showthread.php?t=792026
I will try and hope it works cause all the previous tried did not but thanks to you all anyway
There may be a solution: see this thread: http://forum.xda-developers.com/showthread.php?p=22725909#post22725909
ramses77 said:
Dear all
i have a droid eris with 1.5 firmware i root it and did a backup withe clock work mode
the i tried to install a cyanogenmod custom rom it went fine then when i boot my phone it stuck on the logo screen so i turned it off and went to the recovery mode and i try to do a restore for my backup what i get is the following message
"erasing boot before restore...
restoring boot image...
Error while flashing boot image "
and return me to previous selection
and then i tried to download a custom rom and it goes with the following error
assert failed: write_raw_image("/tmp/boot.img", "boot"
so my phone is stuck in the logo screen can you help me please.
Click to expand...
Click to collapse
The two most likely scenarios that you are encountering are one of these two:
(1) Lack of sufficient good NAND memory pages in the "boot" partition to be able to write the boot image due to a few bad pages. (A small number of bad memory pages can be a normal condition)
(2) An extreme lack of good NAND memory pages in the "boot" partition caused by a mysterious and not well-understood phenomenon when using CWM recovery on Eris handsets.
The first thing I would try is flashing an Eris ROM with relatively smaller boot partition utilization to see if it succeeds. For instance, the "March2011 OTA Reference" ROM - it only needs about 86.3% of the space in the boot partition. If it succeeds, then your issue is likely syndrome (1). If it also fails due to a failure writing the boot partition, then it is somewhat more likely you have syndrome (2). There is a solution available for that problem; but let's first find out where your problem lies.
Here's some examples sizes of the boot images sizes of various ROMs:
Evervolv-Eligo-2.1.0b2: 2,478,080 (94.5% of full)
xtrSENSE5.0.1: 2,265,088 bytes (86.41% of full)
March2011_OTA_ReferenceROM_v1: 2,260,992 (86.25% of full)
As strange as it may seem, it is possible to lose 10% of the space available in the NAND boot partition if only two individual (2048-byte) pages go bad - because pages are lumped together into "eraseblocks" of 64 pages (= 128 kB), and there are only 20 "eraseblocks" in the Eris boot partition. (It turns out that when you lose a single Nand memory basic page of 2048 bytes, you effectively lose the entire eraseblock that it lives in - 128 kB !)
So - while I realize your end goal is not some other ROM - we need to find out what the nature of the problem is, and the fastest way to do that is a test flash. ( You'll have to figure out how to get the ROM onto your SD card - card reader, MS/USB toggle in Amon_RA recovery, or via adb with CWM running on the phone. )
Some of the older Eris ROMs also have small boot partition utiliization - unfortunately nearly all of the early Eris dev ROMs are now missing from the internet due to various sites going offline. If you have an early ROM file lying around, you can unpack it (or inspect it with 7-zip) to find out how big the "boot.img" file is. If it is small enough, feel free to use that as a flash test.
bftb0
So has CWM Recovery been fixed? The whole not being able to charge the phone if the battery died. I would like as many people to chime in so I feel assured that it either has, or has not been fixed. The latest CWM Recovery that I am inquiring about is 5.8.1.4.
I still consider myself a n00b with this stuff, but it seems like I'm still having the same issues with CWM that everyone else is describing.
Most importantly for me, CWM freezes every time it tries to make a nandroid backup. I had the amon recovery, but I guess I installed CWM through the ROM Manager app, not realizing what I was doing. No matter, though, since I couldn't get amonto make a nandroid backup of my Rezound either.
So if anyone can help me figure out how to make a nandroid backup, that would be great ...
bloodymurderlive said:
I still consider myself a n00b with this stuff, but it seems like I'm still having the same issues with CWM that everyone else is describing.
Most importantly for me, CWM freezes every time it tries to make a nandroid backup. I had the amon recovery, but I guess I installed CWM through the ROM Manager app, not realizing what I was doing. No matter, though, since I couldn't get amonto make a nandroid backup of my Rezound either.
So if anyone can help me figure out how to make a nandroid backup, that would be great ...
Click to expand...
Click to collapse
I am not sure what version of Amon Ra you tried to flash or how, but are you on the new firmware or old ? Regardless, download the newest Amon ra recovery img and place it in the same folder as you used to unlock with.
Bring up a command prompt , and change directory if needed to the folder containing your image. Have phone connected in hboot so that it says fastbootusb ... then type in fastboot flash recovery "nameofrecovery".img
This will flash the recovery ...
In recovery just choose backup/restore...nand backup ..press power to confirm and it will make a backup.
mjh68,
Thanks for the info. I will probably try again when I get home. But since I had problems with amon last time, do you know where I can get the version of amon that I should be using for my Rezound?
Here's my software info:
Android version 2.3.4
HTC Sense version 3.5
Software number 2.01.605.11
If amon works better than CWM currently does, at least for nandroid/B], I will definitely let you know. Too bad CWM doesn't just work, though ...
Use 3.15, use scotts clean flashtool. It taked the adb commands out. You can find it on his website
Sent from my INCREDIBLE, faster than a THUNDERBOLT, REZOUND!
Alright, I followed Scotty's "temporary recovery" instructions here: (darn, link not allowed for n00b's ... the title is "Scottys noob friendly root guide-start to finish" at androidforums)
These are the same instructions I used to root my phone in the first place.
I went into Amon.
I selected "Nand backup".
There were several options on the next screen. It looked like this:
- [X] boot
- [X] system
- [X] data
- [X] cache
- [] recovery
- [] sd-ext
- [] .android_secure
- [] .android_secure_internalsd
- [] compress_backup
- Perform Backup
- Return
I left the selections as they were, then selected "Perform Backup".
Before confirming my selection, it said:
Use Other\recoverylog2sd for errors.
I confirmed my selection. It gave me the following messages:
Performing backup : ..
Oops... something went wrong!
Please check the recovery log!
So now I'm stuck, and it looks like Amon is not working as an alternative to CWM.
I looked for Scott's clean flash tool, but I couldn't find it anywhere. Would that even make a difference?
Did you flash the ics ruu leak..if you did and are going back to gb there's a sd card patch he made. Also amon ra has a version 3.15.
Not sure if anything I said may help....just some ideas/thoughts.
Sent from my ADR6425LVW using XDA
I just realized, you're right ... I'm using Amon 3.14, not 3.15 ... But I don't see the download for 3.15 on the link that Scotty provided ... Anyone know where I can get it from?
Here you go....
http://forum.xda-developers.com/showthread.php?p=23781936
from my ADR6425LVW using XDA
Thanks. Again, I followed Scotty's "temporary recovery" instructions. This time, however, the md5 in the command window did not match the md5 at the link you gave me ... ?
This is probably a big no-no, but I flashed it anyway ... Nothing bad happened to my phone, but it gave me exactly the same message I described earlier.
Still no CWM alternative for nand backups.
Thanks for helping me with this, everyone ... mega thanks.
Guess I'm going to move my questions to another thread, since they're becoming more about nandroid than CWM (or finding an alternative to CWM).
bloodymurderlive said:
Guess I'm going to move my questions to another thread, since they're becoming more about nandroid than CWM (or finding an alternative to CWM).
Click to expand...
Click to collapse
CWM does have some problems but all of them are fixable from what I understand. The alternative to CWM is AmonRa. There really isn't anything else.
i choose the cwm route.... i am now flashing back....cwm will NOT charge a dead battery or let you turn it on.....u have to keep messing with it or boot into bootloader to charge...its a pain in the butt
I can't find clear cut instructions anywhere but I am sure there is a post on it already... I looked through the CM10 thread in original development but didn't see anything. I am totally stock on 1.22.651.3.
Well, you root using regawmod, you flash the ROM, and then you fastboot flash the kernel
Instructions for each of those are strewn about the forums
My write-up for Installing kernels with H-boot 1.15
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-wip.html
Rooter:
http://forum.xda-developers.com/showthread.php?t=1690919
Sent from my EVO using Tapatalk 2
Skullmonkey said:
I can't find clear cut instructions anywhere but I am sure there is a post on it already... I looked through the CM10 thread in original development but didn't see anything. I am totally stock on 1.22.651.3.
Click to expand...
Click to collapse
The process is fairly similar to most other devices, with the one unusual quirk being HTC's unlock method does not allow the kernel portion of a ROM to be loaded from the custom recovery.
Assuming you have to use the HTC unlock method, this quirk will apply to your process.
There are multiple ways to approach working around the quirk, but I'll provide two common methods.
1) After unlocking the device, which can be done with packaged up software or by directly using HTC's software at htcdev.com, you'll want to make sure you have the RUU (method to revert back to stock) handy in case of any issues.
2) At a high level, a ROM consists of two portions, the kernel and the system. The system will almost always be loaded through the custom recovery and the kernel, due to HTC's quirk in their unlock method, can be loaded via the command line using the fastboot command, or through the phone using my app, Flash Image GUI.
If a mistake is made or something does not load properly, a computer and the command line will be the only option, thanks to HTC's quirk.
3) The order of loading the ROM depends on the method. I would recommend either one of two methods:
1) Flash Image GUI, select the ROM .zip from the sdcard, and FIG will flash the kernel portion.
2) Reboot into the custom recovery, select the same ROM .zip from the sdcard, and the custom recovery will load the system portion.
3) Reboot and everything should work.
Another available method:
1) Reboot into the custom recovery, load the ROM .zip from the sdcard, the custom recovery will load the system portion.
2) Reboot into the bootloader/fastboot mode, extract the kernel file from the ROM .zip, and using fastboot and this command: fastboot flash boot c:\downloads\boot.img, load the kernel.
3) Reboot and everything should work.
If something doesnt work, you'll gain some experience in troubleshooting, which isn't too difficult, but takes more time. If you're new to the process, I'd plan for more time learning the ins/outs.
Hope that helps!
Thanks Joey! Not new to the game but I like to know the process before actually going through with it. I had to flash 2 times and unlock manually but I an now running Jelly Bean! Now to figure out why my WiFi is nothing even being 2 feet away from the router...
Don't forget to wipe dalvic, cache and factory reset before flashing a new ROM or you will have problems.
Sent from my EVO using xda premium
I did. Wiped cache x2, dalvik x2, factory x2, superwipe x5. Should be squeaky clean!