Related
I need help fast...
I got my Htc Incredible replace today and as soon I got it I rooted the phone and I use a custom recovery image to root.. everything went well but when I got the Rom manager from the market and now its asking me to flash a recovery but I dont want to flash to the v3.. I wanna stay with the 2.5 version is there any way I can flash a image with rom manager instead of flashing the new version..
thanks .
EDIT: re-read post.
If you rooted with the latest unrevoked, you should be on 2.5 anyway. The latest ROM Manager only works with the 3.x recoveries. So, either don't use rom manager, (Flash stuff manually) or upgrade.
-----------------------------------------------------------------------------------------------------------------
All the CWM recoverie are here. http://mirrorbrain.cyanogenmod.com/cm/recoveries/
2.5.1.2 here, RM should be able to flash it.
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-2.5.1.2-inc.zip
And there's always 2.5.0.5 PB31IMG.zip, via unrevoked forever.
http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
If you want the older version of CWM to persist, don't update it in rommanager. Note that when flashing stuff, you do it through recovery, not rommanager.
I have the older CWM, rommanager v 3.0.7, works to create backups. Use recovery to flash and restore.
Sent from my ADR6300 using XDA Premium App
Welp
Personally, I stay away from RomManager. Have never seen something work in RomManager that didn't also work (better) straight out of CWM Recovery.
I am still on 2.5.x.x as well; 3.0.0.5 and 3.0.0.8 seem to cause WAY too much trouble, and there is no clarification from Koush that he is resolving those bugs.
I would love to see an answer on this. I can go back to 2.5 but...
Some of the newer roms require you to use 3.xx.xx Most say to use 3.0.0.7. I would love to but when I set to this version my phone shows no recovery. Just a black screen. I can still push the buttons and get the actions to work, from memory, but this is not a solution. Is anyone else have the "black screen" issue?
Great Offender said:
I would love to see an answer on this. I can go back to 2.5 but...
Some of the newer roms require you to use 3.xx.xx Most say to use 3.0.0.7. I would love to but when I set to this version my phone shows no recovery. Just a black screen. I can still push the buttons and get the actions to work, from memory, but this is not a solution. Is anyone else have the "black screen" issue?
Click to expand...
Click to collapse
I think 3.0.0.7 had an SLCD issue. You must have an SLCD Incredible. You might try 3.0.0.8, I believe it works fine with the newer Incredibles.
Hi All,
I have a question about cmw's recovery and the rom manager. In the dev forum, theres cmw 3.1.0.1, which i've downloaded. However, rom manager keeps telling me the latest is 2.5.0.7. So im curious which one i should actually be using?
Reason I ask is because i've been getting a few odd problems flashing rcmix on my phone. Generally it will work properly (coming from a stock 2.2 rom), though from any other rom it wont. I know that if i flash something like insertcoin, reboot to recovery, wipe/reset, install rcmix it never works. Same goes for when i come from rcmix 1.5 to 1.6 (and 1.7). I assume its got something to do with the a2sd partition, but im not sure what or why cmw recovery is not wiping that jumping between versions of rcmix end with a total failure (stuck at boot logo forever). Quite often this happens with other roms too (like going from rcmix -> insertcoin or oxygen).
Mines a desire lcd, often running stock 2.2 at the moment (rooted, s-off'd) and the standard hboot.
Officially the Desire had the latest recovery version of 2.5.0.7 or what ever it is. 3.1.0.1 is a build built from the source unofficially. V3 has a new type of script and so might help with your issues.
Tbh I hate rom manager because it doesn't work well. Try manually flashing roms. It might help even more.
Swyped...
Same here. RomManager doesn't offer 3.x.x.x versions. You'll habe to flash it manually via Fastboot (for S-OFF) or with Unrevoked (for S-ON).
I actually dont use rom manager for flashing roms and the only reason i went to it was cause I couldnt find a consistent way of finding the lastest clockworkmod recovery image (theres alot of conflicting info out there).
Thanks for the info though, was handy to know. Interestingly, the version rom manager booted me into (boots off update.zip from the sdcard?) was older then the one i had.
Shihan said:
I actually dont use rom manager for flashing roms and the only reason i went to it was cause I couldnt find a consistent way of finding the lastest clockworkmod recovery image (theres alot of conflicting info out there).
Thanks for the info though, was handy to know. Interestingly, the version rom manager booted me into (boots off update.zip from the sdcard?) was older then the one i had.
Click to expand...
Click to collapse
I have always stuck with CWM 2.5.0.7 - it seems to be the latest version that nobody reports problems with. I don't think there's any good reason to update to the newer versions.
Looked urgent huh? That's because it is. I see that most people that have their phones bricked is from using ROM manager to install a rom that they downloaded onto their phone.
LISTEN TO ME WHEN I TELL YOU....
Do not use ROM manager to install a custom ROM that is not listed in the application.
I too have bricked my phone this way and I never made a back up. The quickest solution is to actually re-root your phone again by putting it back into download mode.
Look in the forums for instructions. I'm sure others can explain it better than me.
Only use ROM Manager to install clockwork mod recovery.
From there, do it the manual way. It may be more labor, but it is better than bricking your phone.
There are instructions to do that too. If you can't find it just throw me a PM.
Lol I use it all the time to flash roms never bricked
Sent from my SAMSUNG-SGH-T989 using xda premium
same here. can you elaborate why you think or provide proof that cwm is bricking peoples phones.
I have used cwm on several phones and never had any problems getting to recovery and flashing roms.
you didn't read his post. he is saying not to use Rom manager to get/install roms
Probably because rom manager only wipes data and cache at most. Most of these roms work best with a super wipe
The touch cwm is the worst. Have to toggle signature verification every time, and point it to the internal sd card. Only one brick (soft), though.
That v5 one is notoriously bad on many phones. Just buggy. Not a dealbreaker for me. Is the other touch one better?
Sent from my SAMSUNG-SGH-T989 using xda premium
He's probably referring to the roms listed in ROM manager that are not for our phone.I think there is two of them now
I think we're confusing Rom Manager with Clockwork Mod...
Rom Manager is an app made by koush, its a downloadable market app thats included with Cyanogenmod and other roms (on other phones) that makes it easy to install a ROM without bothering with booting into recovery. I used it extensively during my Nexus days, though on the t989 many roms you have to super wipe or do a lot of advanced things you can only do inside clockwork mod.
ClockworkMod is a recovery manager for your android phone, also made by Koush. The classic version that has been on all phones is the non-touch type, latest version is 5.0.2.7. You use the power button and volume rocker to navigate. There is another version dubbed ClockworkMod Touch, latest version is 5.8 something...you can actually navigate with touchscreen in this.
Many people's problems, I've experienced it too, is that CWM touch likes to reboot randomly during crucial moments (during a backup, MD5 creation, flashing a ROM...), leaving the potential for (and in some cases it actually has) bricked phones. Plus the touchscreen navigation is tempermental, its just not very responsive or accurate. Very dangerous bugs for such a sensitive area on the phone.
So do yourself a favor...use ClockworkMod, the originial. Its not going to kill you to navigate with the volume rocker and power button...it actually makes you pay attention and go slower so you don't make mistakes and push the wrong thing. Its easy to install...with Rom Manager! Download it from the market, when you open it near the top there will be a button to flash the latest ClockworkMod. It will be the non touch type.
As stated above, I wouldn't use the ROM flashing functions of Rom Manager with our phone, but it does have an easy button to reboot into recovery for roms without the option in the shutdown menu. It's the easiest way to flash CWM though.
Hope this helps.
You guys can stop "trippin" there are 2 roms under the dl section in rom manager for our phone DO NOT IN ANY WAY SHAPE OR FORM FLASH THIS TO YOUR SGH-T989!!! it WILL BRICK YOUR DEVICE!!! Somebody just needs to email koush about it so they can be removed. IMHO dl to your phone or pc and then flash away a superwipe is recommended. I for one am iffy with rom manager because it errors out on restores sometimes.
Sent from MY Juggernaut!!!
zander21510 said:
I think we're confusing Rom Manager with Clockwork Mod...
Rom Manager is an app made by koush, its a downloadable market app thats included with Cyanogenmod and other roms (on other phones) that makes it easy to install a ROM without bothering with booting into recovery. I used it extensively during my Nexus days, though on the t989 many roms you have to super wipe or do a lot of advanced things you can only do inside clockwork mod.
ClockworkMod is a recovery manager for your android phone, also made by Koush. The classic version that has been on all phones is the non-touch type, latest version is 5.0.2.7. You use the power button and volume rocker to navigate. There is another version dubbed ClockworkMod Touch, latest version is 5.8 something...you can actually navigate with touchscreen in this.
Many people's problems, I've experienced it too, is that CWM touch likes to reboot randomly during crucial moments (during a backup, MD5 creation, flashing a ROM...), leaving the potential for (and in some cases it actually has) bricked phones. Plus the touchscreen navigation is tempermental, its just not very responsive or accurate. Very dangerous bugs for such a sensitive area on the phone.
So do yourself a favor...use ClockworkMod, the originial. Its not going to kill you to navigate with the volume rocker and power button...it actually makes you pay attention and go slower so you don't make mistakes and push the wrong thing. Its easy to install...with Rom Manager! Download it from the market, when you open it near the top there will be a button to flash the latest ClockworkMod. It will be the non touch type.
As stated above, I wouldn't use the ROM flashing functions of Rom Manager with our phone, but it does have an easy button to reboot into recovery for roms without the option in the shutdown menu. It's the easiest way to flash CWM though.
Hope this helps.
Click to expand...
Click to collapse
Holy christ time to flash back to original clockworkmod. Later touch recovery.
Sent from my SAMSUNG-SGH-I727 using xda premium
Still rockin the original CWM, never saw all the fuss about the touch stuff. Manually toggling is much safer and reliable IMO
I see that people have mistaken that I was talking about not using CMW. Let me explain. CMW (Clockwork Mod Recovery) and ROM Manager are two different things. You get CMW from ROM Manager. You use CMW to flash ROMs. Some people use ROM Manager to flash ROMs instead of CMW. That's the way you get bricked. By flashing ROM's that aren't on ROM Manager. I hope this clears it up.
I was unaware people still used Rom Manager.....
Thought we upgraded to ODIN, ADB and Heimdall
ROM manager will not brick your phone! If it does get bricked it was user error! Please close this thread
the OP says it bricked his phone, yet then says he flashed back to stock LOL. If your phone is a BRICK it's dead and does NOTHING.
rsfaze said:
the OP says it bricked his phone, yet then says he flashed back to stock LOL. If your phone is a BRICK it's dead and does NOTHING.
Click to expand...
Click to collapse
There's also soft brick which can be saved. He was most likely referring to that.
Sharpie603 said:
I was unaware people still used Rom Manager.....
Thought we upgraded to ODIN, ADB and Heimdall
Click to expand...
Click to collapse
ODIN is really crappy software IMO.. Despite its uses.
Even rom manager has its uses...I wouldn't use it to flash ROMS, because often with our phones you need more wiping than just data & cache, which is all it can do before it flashes a rom. It however it can be used to easily flash CWM and for phones without the option in the shutdown menu, you can use rom manager to reboot straight into CWM.
Guy's, what he is trying to tell you is that there are 2 ROMS that can be dowloaded and installed by ROM MANAGER that WILL BRICK YOUR PHONE. They are listed as T989 roms but they are actually for the International SGS2....
sbell7105 said:
ROM manager will not brick your phone! If it does get bricked it was user error! Please close this thread
Click to expand...
Click to collapse
He's accurate about what he described in this thread. I created a similar thread (probably got deleted) yesterday about the same issue. Just because you haven't experienced bricking yours doesn't mean he shouldn't warn others.
I hard-bricked my T989 just simply trying to boot into recovery (non-touch CWM) from the Rom Manager app...and I have read similar issues. The phone goes fcuking dead.
UPS just dropped off my replacement phone today...ready to be rooted for an ICS AOSP ROM if I can find one. Done with CM7 for now.
bluepenny65 said:
H
UPS just dropped off my replacement phone today...ready to be rooted for an ICS AOSP ROM if I can find one. Done with CM7 for now.
Click to expand...
Click to collapse
There isn't one that fully works with data and audio
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse
Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....
Shot you a PM.
Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse
Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk
motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse
Ok, so I've been flashing Roms since I first had the G1 but my step sons Galaxy S II is giving me fits as of late.
I've been working on it for over 2 days now and can not figure the problem even after reading through all the how to's and individual rom threads. I initialy rooted his phone back in April/May and had a early ICS phandroid rom on it. However I wanted to move him to JB. I've done the customary wipe data/cache but no matter what JB rom I flash it goes into what I believe is a bootloop. I've read several places it been said to let sit after flashing for 10 minutes so I let sit for 20 and it was still on boot (but no obvious point where you can tell it's looping).
When I went to restore his backup that would no longer boot at all, just a blank screen. So long story short I restored everything to stock then updated to ICS through keis. and tried the process again thinking it might need updated firmware/radio. Same thing happened and I had to restore stock and update through keis again. I am now at a complete loss as I update my phone (One S) and wifes (GSIII) atleast once a week on nightlies.
The one thing that I thought was odd is both on the original 2.3.6 and now 4.0.4 when I go into settings at search for update i get a message saying "no firmware". Not sure if that means anything but it didn't sound right to me.
Any help or suggestions would be overwhelmingly appreciated.
You will get different methods on here but for starters what recovery are you running. Thats problem 1 I guarantee for your bootloop. I use TWRP 2.3 which can be found by downloading goo.im and flashing it from the menu screen. You can also go to the forum here in development for the zip file.
When using TWRP or any touch recovery do not use the wipe scripts. Lets start there.... Since the method to flashing is basically the same all over its just the wiping procedure with the wrong recovery can be tricky
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
jhenson496 said:
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
Click to expand...
Click to collapse
I personally prefer that recovery and I'm running a cm 10 on my phone with no issues at never had anything. Yes it's rather simple to put on an even if you want to try the CWM touch recovery by all means go ahead
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
jhenson496 said:
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
Click to expand...
Click to collapse
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
abesgs2 said:
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
Click to expand...
Click to collapse
My friend I linked the zips in the post right above yours
playya said:
CHANGELOG for 2.3.0.0:
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
Click to expand...
Click to collapse
Just saw that last part by Playa, sorry didnt mean to kang you haha... but hes got it down ^^^