So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Cwm from rom manager hasn't worked in awhile. Use philz touch if you really want cwm. Or use flashify to get twrp
hydeburns said:
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Click to expand...
Click to collapse
Like Josh said just use Flashify https://play.google.com/store/apps/details?id=com.cgollner.flashify
It's still updated and works great. To many have had issues with ROM manager or Goo.
Sent from my SCH-I545 using Tapatalk
hydeburns said:
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Click to expand...
Click to collapse
I was in the same boat all day yesterday - reset to stock using the MDK No wipe tar via Odin, factory restored, flashed MD2, motochopped, flashed MDK, but then could not get any new recoveries to take. Using Flashify I was just able to install CWM 6.0.4.7 (which I had tried doing using ROM Manager, and paid $1.99 for, which didn't work) - halle-frickin-luyah!
sdsurferbob said:
I was in the same boat all day yesterday - reset to stock using the MDK No wipe tar via Odin, factory restored, flashed MD2, motochopped, flashed MDK, but then could not get any new recoveries to take. Using Flashify I was just able to install CWM 6.0.4.7 (which I had tried doing using ROM Manager, and paid $1.99 for, which didn't work) - halle-frickin-luyah!
Click to expand...
Click to collapse
Thanks guys. I tried all of this with the flashify. Even started off freshly reinstalling stock Mdk and then rerooting with the same method I mentioned earlier. Installing cwm through flashify. And though I can make and restore a backup of my stock rooted Rom. I get the same errors I've been getting trying to flash a custom Rom. I'll try to post a screenshot of the error I get in can when flashing.
Related
I have a rooted GT 10.1 LTE with the EH04 update. I have tried flashing via CWM which results in the obvious breakage. I have also tried installing via Recovery and Odin with the attached files and in various combinations with no luck.
Any suggestions or ideas on what I am mucking up to not be able to get CWM only my tablet?
To note: It was working prior to the EH04 update.
Bump.
Any ideas?
try the cwm here:
http://forum.xda-developers.com/showthread.php?t=1090289
to a certain degree it is a lot of trial and error as to what parts of the various 10.1 models are common and which are distinct -- at this juncture what is to loose from flashing a different cwm?
Try this recovery ( flash zip)
http://www.mediafire.com/?w45j8i0fcj0wck0
Then try this rom
http://forum.xda-developers.com/showthread.php?t=1277045
Its been working very well for me.
Mr.Jester said:
I have a rooted GT 10.1 LTE with the EH04 update. I have tried flashing via CWM which results in the obvious breakage. I have also tried installing via Recovery and Odin with the attached files and in various combinations with no luck.
Any suggestions or ideas on what I am mucking up to not be able to get CWM only my tablet?
To note: It was working prior to the EH04 update.
Click to expand...
Click to collapse
I unrooted to get the EH04 updated using this: http://rootzwiki.com/topic/7718-romleakodineg01-factory-stock-odin-image-vzw-lte-tab-101/ , waited for the EH04 update, then re-rooted using this (which I used to root initially): http://rootzwiki.com/topic/2242-root-recovery-galaxy-tab-101-lte/ .
Perhaps you should unroot per the above, take the update, then re-root as above--worked for me.
i ota'd EH04, lost root. downloaded kernel.zip, applied it, got root back, installed cwmod, clicked to reboot into recovery and it's looping since, i can't do anything but get into ODIN but the PC wont recognize it, although i get a pop up saying android.. installed, adb devices doesn't pick up either. can't get into recovery.
---
update
http://forum.xda-developers.com/showpost.php?p=18121666&postcount=53
someone warned in the forums and i didn't read it before i did it, used odin to put recovery.zip, now i'm back in action.
The recovery you provided is the same that I attached. What I discovered however is that if I booted into recovery right after installing the CWM recovery, CWM would load. If I booted into stock EH04 then back into recovery, the stock recovery would load. It seems as if the ROM was restoring stock recovery when it loaded. After installing Lightspeed, CWM recovery stayed in place.
Either way, thank you for the assistance. I hope this thread ends up helping someone else.
My steps to install Lightspeed from Stock ROM EH04:
1. reboot recovery, install either recovery.zips above.
2. When the system automatically reboots, hold volume up to boot into recovery again. This time it should be CWM.
3. Wipe cache and factory reset
4. Install Lightspeed ROM
I
Mr.Jester said:
The recovery you provided is the same that I attached. What I discovered however is that if I booted into recovery right after installing the CWM recovery, CWM would load. If I booted into stock EH04 then back into recovery, the stock recovery would load. It seems as if the ROM was restoring stock recovery when it loaded. After installing Lightspeed, CWM recovery stayed in place.
Either way, thank you for the assistance. I hope this thread ends up helping someone else.
My steps to install Lightspeed from Stock ROM EH04:
1. reboot recovery, install either recovery.zips above.
2. When the system automatically reboots, hold volume up to boot into recovery again. This time it should be CWM.
3. Wipe cache and factory reset
4. Install Lightspeed ROM
Click to expand...
Click to collapse
Thank you. Everytime I tried flashing cwm recovery, I would always end up back at stock recovery. Your fix worked perfect.
So I'd been having some problems lately with my phone hanging on the Samsung screen on boot. Been running CM11 1/1/2014 nightly most recently. Decided to try using TWRP instead of CWM. That didn't seem to help my issue, so I tried installing CWM again. I used an app called Recovery Tools to download the touch version of CWM. After it said it installed, I tried to boot into recovery and got the error "Unauthorized software found. Please contact Verizon." (paraphrased a little).
Doing some research it looks like that error typically comes up when the bootloader is locked. Now, obviously I had my bootloader unlocked (well, Loki'd) because I was running CM11. Any help fixing this? I'm able to bypass the warning screen on boot if I hold down vol up + power like I'm going into download mode, but then hit vol down to cancel to boot up the phone. Once booted everything is ok, but any reboot just brings that up again. Using ROM manager to flash CWM recovery seems to work ok and it says its installed, but same issue. So does trying to flash TWRP from Goo.
If I were to run this tool that I used to root and loki before (http://forum.xda-developers.com/showthread.php?t=2301720) to install a recovery, would I be able to get everything going again? I think that somehow the recovery I installed wasn't Loki'd, although I picked the right one for my device.
Thank you in advance for any replies.
The fix I found was by pure dumb luck. I ended up trying to flash a recovery with Odin. Odin failed but reboot back into the os. I then used the twrp manager app from the playstore (mainly because goomanager wasn't downloading the recovery at the time) to flash the latest twrp recovery and all was good. Even though Odin failed at flashing the recovery I still think it helped somehow. I haven't thought much about why but I might have to now.
Sent from my SCH-I545 using Tapatalk
You could probably try using ODIN to get back to stock MDK and then Re-Root and install a recovery after.
Edit: And then flash CM11 again.
Sent from my SCH-I545 using Tapatalk
Will this one-click stock ROM work?
http://www.rwilco12.com/downloads.p... S4 (Verizon) (SCH-I545)/Stock ROMs/One-Click
or, which of the files on this page are what I would want? (about 1/3 of the way down for SCH-I545)
http://www.droidviews.com/how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models/
I was actually able to reflash TWRP w/ their app from the Play Store. Still get a lot of boot hangs on the Samsung logo though. Seemed to happen less with CWM, but now I'm too scared to try to install a different recovery. I appreciate all your help guys.
So the way I rooted was I flashed CWM via Odin, and then flashed SuperSU zip in CWM. I used the correct versions and i verified I had root with Titanium Backup and even Root Checker. I have tried twice to flash roms and I end up in samsung logo boot loop, don't even get any further than that. I downloaded 2 different roms that are meant for the Sprint Note 3 and work on my build number. Perhaps my root method screwed it up some how? Any ideas what is happening? From reading other posts, I realize I may have to flash another kernel, but on the rom (MiniN3) it said nothing of the sort. So, what gives?
hobokenshmo said:
So the way I rooted was I flashed CWM via Odin, and then flashed SuperSU zip in CWM. I used the correct versions and i verified I had root with Titanium Backup and even Root Checker. I have tried twice to flash roms and I end up in samsung logo boot loop, don't even get any further than that. I downloaded 2 different roms that are meant for the Sprint Note 3 and work on my build number. Perhaps my root method screwed it up some how? Any ideas what is happening? From reading other posts, I realize I may have to flash another kernel, but on the rom (MiniN3) it said nothing of the sort. So, what gives?
Click to expand...
Click to collapse
what rom firmware where you be fore flashing the new rom? did you tried to wipe cache/date after flashing?
Well I restored back to factory 4.3 stock, then use another 4.3 custom rom.
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
So I'm having a bit of an issue flashing a recovery on my NH7 4.4.4 HLTESPR Note 3. I've had it rooted/ROM'd for a few months now without any issues. I used my upgrade to buy an LG G3 for $1 and gave it to someone else, and when they did this, they had to deactivate my Note and activate the G3 for the upgrade to apply. After that, they reactivated my Note 3. I was getting data connection at Best Buy immediately after, but later that night I noticed I had completely lost data connectivity so I went into TWRP, made a backup, and reflashed to a stock/rooted recovery I had made prior so that I could access the profile and PRL updates.
I applied the updates and reestablished data connection. Then I tried to boot into recovery from TWRP to revert to my ROM. No go. I try it with the button method - no go. Then I went to Root Checker and it told me my device no longer had root access. Super User still installed but root was gone. So then I ran it through CF-auto-root again, and tried to flash TWRP from the TWRP manager a few times but it crashed each time. Then I tried to use Flashify to flash TWRP from my SD card. Seemed to work, so I used TWRP manager to reboot into recovery and it went into a boot loop. Odin'd back to NH7 and retried the whole process. Now even when I flash TWRP from odin, I go into TWRP Manager and it doesn't detect a recovery. I've tried a few different versions of TWRP and used Odin, TWRP manager, and Flashify to try and flash a recovery but it just doesn't seem to work. I have no idea what's going on. I've been doing basic rooting/ROM flashing for a few years now, and I'm pretty comfortable with Samsung devices but this is unlike anything I've encountered. Anything will help! Thanks
HarrisY said:
So I'm having a bit of an issue flashing a recovery on my NH7 4.4.4 HLTESPR Note 3. I've had it rooted/ROM'd for a few months now without any issues. I used my upgrade to buy an LG G3 for $1 and gave it to someone else, and when they did this, they had to deactivate my Note and activate the G3 for the upgrade to apply. After that, they reactivated my Note 3. I was getting data connection at Best Buy immediately after, but later that night I noticed I had completely lost data connectivity so I went into TWRP, made a backup, and reflashed to a stock/rooted recovery I had made prior so that I could access the profile and PRL updates.
I applied the updates and reestablished data connection. Then I tried to boot into recovery from TWRP to revert to my ROM. No go. I try it with the button method - no go. Then I went to Root Checker and it told me my device no longer had root access. Super User still installed but root was gone. So then I ran it through CF-auto-root again, and tried to flash TWRP from the TWRP manager a few times but it crashed each time. Then I tried to use Flashify to flash TWRP from my SD card. Seemed to work, so I used TWRP manager to reboot into recovery and it went into a boot loop. Odin'd back to NH7 and retried the whole process. Now even when I flash TWRP from odin, I go into TWRP Manager and it doesn't detect a recovery. I've tried a few different versions of TWRP and used Odin, TWRP manager, and Flashify to try and flash a recovery but it just doesn't seem to work. I have no idea what's going on. I've been doing basic rooting/ROM flashing for a few years now, and I'm pretty comfortable with Samsung devices but this is unlike anything I've encountered. Anything will help! Thanks
Click to expand...
Click to collapse
Have you tried a full revertin? Stock everything including recovery and starting over with the root process?
Have you figured it out if not i can help pm me .