Greetings Reverb community; As we all know, lately there has been a multitude of issues concerning the inability to flash our trusty CWM 8, a.k.a 6.0.2.3, onto any SGR's recently purchased or replaced, that come o.o.t.b with or immediately update to JB 4.1.2. I am creating this thread AS A WARNING TO ALL SGR OWNERS WHO ROOTED AND FLASHED CWM BEFORE THIS PROBLEM SURFACED... IF YOU FOR ANY REASON FLASH BACK TO ICS 4.0.4; THRU YOUR OWN STOCK BACKUP/RECOVERY OR TYLER1998's METHOD; UNDER NO CIRCUMSTANCES ALLOW THE OTA UPDATE TO INSTALL!! IT WILL INSTALL A DIFFERENT STOCK RECOVERY! I know this because I watched the install line by line, and one of the line commands about 3/4 of the way through the process read "installing new recovery"... On the bright side, I did not totally lose the use of my phone, because it still boots to stock 4.1.2, and SO far, I still have my contacts, pix and other pertinent info So, admittedly, what I was ultimately trying to accomplish ended up costing me the root and custom recovery freedom that a good many are still enjoying; and HOPEFULLY this post will prevent anyone else from making the same mistake that I did!! With any luck, someone will by either skill or blind luck, find a solution for us poor, unfortunate souls! Peace, Sox :frown: EDIT: Well, as quick as this happened, I found my solution! And it was by guess and by golly! I went over to the Rush board and perused around and found this thread: http://androidforums.com/rush-all-things-root/734114-samsung-galaxy-rush-cwm-issue.html Tried Lord Vincent's advice and it worked on the 1st try! I GOT MY CMW 8 BACK WITH ROOT AND ALL MY RECOVERIES!!!! WOOOOOHOOOOO!!! :rock: arty: Maybe this would work for the new/replaced SGR's having the 'no recovery' issue? EDIT: When I posted this, I neglected something that probably needed to be put in here. I DID NOT use the .tar file created for the Rush; ONLY THE METHOD...the CWM test 8 (a.k.a 6.0.2.3) .tar was what I used. EDIT 2: Hello again, everyone. Good news... member mrg666 has put together a new CWM Recovery that is compatible on all Reverbs! BIG THANKS AND PROPS TO YOU, SIR; AND ALSO TO ALL WHO THUS FAR HAVE BEEN CONTRIBUTING TIME AND EFFORT!! So; for all owners of the 'Reverb 2', or 're-issue Reverb' that has rejected previous attempts to put CWM into the device; his thread CWMT 6.0.3.6 is the answer. Check it out, follow the OP instructions, and your good! Now hopefully, we can find an updated root method for this phone's alter ego. EDIT 3: There is evidently (completely overlooked by yours truly) a link to working root method within his link. SO...follow the yellow...YOU know...
Just to be clear, you are not saying this worked for you on a new/replaced reverb with ootb 4.1.2? I have one and cannot get the cwm recovery to boot, even following the 'rush' thread linked above. Must have tried 10 times...
That is correct; it is not the 'new version', I bought it Christmas season, last year. My phone was both, rooted, and 'rommed' BEFORE the issues that the current crop of SGR owners are experiencing. What happened was a subscriber that I was corresponding with was looking for verification on kernel version #'s, and I had some issues of my own that. In my own mind, thought a 'pure back-up' of 4.1.2 created from my phone and not an outside party, would be beneficial for my situation. So I flashed back to bone stock 4.0.4 (provided thry tyler1998)...including the stock recovery thru Odin...and let it follow the OTA update and install. That way, I'm getting MY stuff accomplished, as well as helping someone else with their own thought process, right? LSS, I let him know what he was looking for, and then proceeded to finish MY quest. when I flashed cwm 8 back into the phone thru Odin, I got the same thing as you (new SGR owners) got; correct installation of the recovery, boot up, but no blue flicker/flash-it loaded android os. So I shut down and rebooted into recovery, but it was the <3e> stock. Tried over and over to get cwm to flash, but no-go. After this post I took a step back and thought things thru, and decided to do some digging (mind you, I'm a complete noob, and my digging is moreclosley related to 'light raking'). Came across the post in the Rush community, and figured I had nothing to lose, so I tried it. Turned out great for me, so I figured I'd post the link and see if any new users HAD tried it, or would be willing to try it...couldn't hurt, right? If you already tried it, with no success; then this obviously ISN'T the solution I/we were looking for. I apologize if i got peoples hopes up, I just thought I'd 'stumbled into' something. I'll keep looking and help out with what I can, when I can. Together, I'm sure we'll find something out there! Peace, Sox
soxtober05 THANK YOU FOR SHARING! Gives me some hope for my OutOfBox JB 412 Reverb In short, what was your FIX? Using the CWM-Rush-M830 Recovery? (you said OTA installed a new Recovery) Or just good ol fashioned persistence with the Battery pull Method? I looked over the Rush thread and there's 2 things I'm not clear on. Lordvincent refers to the auto reboot is the problem. The phone has a file inside it that replaces the stock recovery when the phone boots. You need to uncheck that option. -Did you find this file on the phone? or the option to uncheck on the phone? Or simply unchecking Auto-Reboot in Odin is what bypasses or 'disables' the stock recovery write, pull batt, and persistently try to get straight to CWM-test8, ect? Other thing is you had success with which recovery? -CWM-test8 for reverb? or the CWM-Rush-M830-Final.tar? UPDATE: Tried CWM-Rush-M830-Final.tar and Did NOT work. Also, I installed Titanium Backup (no Root) to verify my partition sizes: NOTE this is with all my apps installed referring to free space... OutOfBox JB 412 Galaxy Reverb: SystemROM 825MB (19.4MB free) Internal Media 2.20GB (1.36 GB free) Ext SDcard Can you verify the Partition Sizes of your Old Reverb?
UPDATE: I tried flashing CWM-Rush-M830-Final.tar to my OutOfBox JB412 Reverb via Odin. I got different results than using reverb-cwm-test-8.tar. Here are the differences: -Flashing reverb-cwm-test-8.tar results in Brief Blue Flash on screen, then nothing -Flashing CWM-Rush-M830-Final.tar results in a repeating Blue,Green,Red Flashing screen. I can never seem to get to Recovery until after the first initial Samsung loads, then flashes black, pull batt before it loads 2nd Samsung logo with swirl, then boot into recovery. At first i thought I was not loading CWM quick enough, and possibly interrupting the StockRecovery Write process, leading to corrupted stock Recovery boot attempts... It makes sense the CWM for M830 Rush doesn't work... But is this an indication that I'm properly getting to Recovery, but CWM-test8 doesnt work? Or am i just not getting to the CWM recovery in time before it gets overwritten with stock? Thoughts?
I MAY have overlooked this in one of your previous posts, but when you flash the cwm 8 for the Reverb, are you pulling the battery once it is through flashing the .tar file, and the screen in the lower left-hand corner says 'success 1/failed 0'? Also, MAKE SURE YOU HAVE THE AUTO REBOOT BOX CHECKED... this should 100% assure that you get the battery pulled at the right time.... 1 more thing, I'm admittedly not a developer, but I was always told to install only 'stuff tested specifically for the phone' That being said, I did not use the .tar recovery for the Rush (this probably should have been in the OP, I'm clarifying that today) ...I realize they are similar, but did you look into the 'safety' of flashing the Rush .tar before you flashed it into the Reverb? Peace, Sox Edit: 'MAKE SURE YOU HAVE THE AUTO REBOOT BOX CHECKED'.... Doh! ...meant to say UNchecked....
THANKS FOR REPLY! I've tried BOTH AutoReboot CHECKED + UNCHECKED, Batt Pulled; Same Results Yes mos def waited until I saw success 1/failed 0 I'm admittedly not a developer either, but I have successfully Rooted/Installed custom ROMs on the following Droid Devices: LG Optimus V HTC Wildfire S HTC One V Samsung Galaxy Nexus RAZR MAXX HD XT926 RAZR XT912 HP ZEEN Tablet (from old HP PhotoSmart Printer) TRUE there are risks involved with flashing a recovery designed for another phone, but the way i see it, my recovery was/is broken already. And we'll never find out until we try, and report the results to these Awesome Forums. I took a risk, didn't work, but it didn't softbrick phone either (LUCKY ME) 2 things that stand out to me: -I cannot get to Recovery after Download mode unless it goes past the 1st Samsung logo no matter what. I always pull batt again before it reaches 2nd Samsung logo with swirl. But that's the only way i can get to Recovery. Is the stock Recovery ReWrite occurring sometime in between the 1st and 2nd Samsung logo? -Flashing CMWs made for different phones had different results. Do we just simply need a new CWM recovery for these OutOfBox JB 412 Reverbs?
Yeah, It has been said ...nothing ventured; nothing gained.. This may sound weird to you/some/most here on the forum, but I have never partitioned any of my phone sd cards...int OR ext. Don't know if thats good or bad; just never did it. You mention that your rec. was/is broken...does the phone boot normally to the OS, or not? Stock <3e> rec. or not? '2 things that stand out to me:' -I cannot get to Recovery after Download mode unless it goes past the 1st Samsung logo no matter what. I always pull batt again before it reaches 2nd Samsung logo with swirl. But that's the only way i can get to Recovery. Is the stock Recovery ReWrite occurring sometime in between the 1st and 2nd Samsung logo? Not sure on this...isn't flashing a rec. onto a phone akin to flashing/updating the BIOS in a PC? And if so, wouldn't said re-flash stay in the bios memory until next reflash/update? It is my uneducated two-cent guess, that the present incompatibility problem lies within the script of the recovery itself. Reason I feel that way is that when I ran the initial update in May after getting back to stock, I don't recall the line command 'installing new recovery' going by, as with this latest one I allowed the other day. It is my further, uneducated two-cent guess is yes, we probably do need another v.(CWM) scripted....UNLESS... Another 'already scripted' recovery could work for this phone?...just a thought....
I agree - done! Please use the handy report button next to any post to get our attention for this sort of thing. Ok to report good things too.
I got my Reverb replaced right after the Jellybean update was available, does that indicate i have the "new" ones your talking about?
If you've already got CWM and subsequently root, my guess is no. Because the "new" phones can't even get CWM, or ANY custom recovery to boot.
Yeah, I'm back on Test 8. Not sure why they decided to flash the .tar for the Rush, though. I'm not 100% sure that after these people do attempt to load CWM 8 thru Odin, and get this 'blue flash>>>black screen, if the phones still boot to OS or not...no one has said. I used the method (not the .tar) for the Rush and it worked 1st try. That was the reason I posted that thread that's in the sticky now.
soxtober05 Yes phone still boots to OS superboy4444 Yes, i flashed a CWM Recovery designed for a different phone purposely to see if it made a difference, and it did. This is why i believe we may need a new Recovery... From Reading the Rush Forum, the timing aspect is what most people get stuck on. Getting Recovery to Boot after the Odin Flash but before OS loads was the grey area. I DO get to Recovery before the phone fully boots, but only AFTER the Yellow Triangle appears on the 1st Samsung Boot Screen. (Yes the triangle is there because i flashed more than 3 times) Ive tried all combinations, Auto-reboot on/off. I've tried several different versions of Odin from 1.85-3.07. All successfully Flash. Also, to be clear, I never let the phone fully boot, as I've been told it re-writes the stock recovery. After Odin Flash, i pull USB Cable, then Battery. Then I only let the 1st Samsung screen load, then pull battery again before 2nd Samsung with swirls loads, then replace battery, and viola 'Boot to Recovery by Key' appears, but never fully boots CWM8, or any other Recovery I've tried... This is the only way I've been able to get Recovery to boot after Odin CWM8 Flash.
The reason there are differences in the rush and reverb recoveries is there is a file called graphics.c that helps the recovery adapt to the display. Rush and Reverb have different displays and it's actually a miracle the Rush kernel does anything with the Reverb display. BUT: the phones use the same memory mapping which is why flashing the Rush recovery doesn't brick the Reverb. Aside from that I need a bit of clarity. 1. Is the JBOOB unrootable? 2. If not has anyone pulled any partitions, ie dumps? 3. If there are partitions, where can I get the recovery partition? 4. Is there a pulled UPDATED recovery around? Include links to POSTS and files if possible please. I know this seems like noobish questions, but I don't have time to read through the threads. I'm getting the source from Samsung concurrently and will compile a kernel for the new update, tie in the recovery initramfs and get someone to guinea pig that recovery ASAP. The Galaxy Victory ICS recovery worked after the JB update, so this is really odd. And NO, OUDHS is not dead! I've been working on other devices and the group is actually growing with some newer "understudies" but they are working on LG devices ATM. Cheers and OUT!
1. So Far, it seems that way yes...problem is we cannot get to CWM8. 2. Not the important Partitions... Just what i found on my OutOfBox JB 412 Reverb when I installed TitaniumBackup with NO ROOT, so limited here... -SystemROM 825MB (19.4MB free) -Internal Media 2.20GB (1.36 GB free) 3. Dont' know about that one. 4. I think I killed mine when i tried to flash CWM8 with Odin. Unless normal boot really does re-write stock recovery back. But i know my recovery does nothing when i try, even after normal OS boot. And I have no root yet either so I'm not sure how to pull it. Guinea pig available right here. Let me know when you're finished compiling, and I'll test on my OutOfBox JB 412 Reverb Send Tar file, OR just the .img file and i can make my own Tar file. whatever works... I will flash with Odinv304 and verify results. Soxtober05 had suggested flashing your Stock404 Kernel via Odin, and trying to load CWM8 After that. Makes sense that Flashing a different Kernel would allow the booting of a different Recovery (CWM8). Kinda like when you need to flash a Custom Kernel for a certain Custom ROM to allow Booting of that ROM... If I flash a different Kernel, and break the OS, but can get into CWM, I'm OK with that, because I now have a Recovery to flash ZIPs in. BUT If I flash a different Kernel, and break the OS, and canNOT get into CWM, then I need cross my fingers and Hope that Flashing the Kernel from Stock JB ZJones will at least get the OS to boot. In theory, I should be able to get back to normal running OS condition if all else fails by flashing the stock JB kernel back? ??Thoughts?? Definitely More Risk than just Flashing the Recovery, so I'm proceeding with much caution... If this does work, it has the potential to fix other SoftBricked Reverbs as well, by simply flashing Kernel, and then using CWM8 to fix their partitions they broke in Odin, ect...
lgoptimusv5 When I re-did mine, I pulled the batt AS SOON AS SUCCESS WAS ACKNOWLEDGED (blue download line finished; success 1/failed 0)
Tried that same timing/routine, with AutoReboot CHECKED + UN-CHECKED on my JBOOB Reverb. I remember clearly fumbling the phone around while trying to pull both battery + USB cable at the right time. Just to clarify tho, you're saying that particular timing/routine worked for you on your JBOTA Reverb with AutoReboot CHECKED right? Thank You for being precise about it.
Yeah, it was OTA; but remember; my phone got the root 'n recovery (and roms) before all the present drama...
Hello, new to "Reverb" community...So I gather If my phone is "OOTB JB" I'm SOL on the root thing Huh??? Thanks all the same for any feed back
