I did a backup in TWRP before flashing the PA alpha ROM, realized I needed CWM, so flashed that over in TWRP. Fine. Installed PAalpha in CWM. Fine. Decided to go back to the ROM I'd backed up (Beans), so attempted to flash TWRP over in CWM. Rebooted recovery. Sent me straight to stock recovery. Still boots into PAalpha fine.
I've tried to install TWRP via goo manager, and it says it's successful, but I'm still on stock recovery. Did I f- something up? How can I get back to custom? Did I screw my unlock somehow (doesn't seem like it would...)?
I've been doing the flashing thing since the Eris, but have been out of the game for a cycle, and am wary of messing around with things now that I'm at a point I don't quite understand. Much thanks.
Unlocked and rooted.
vxkid said:
I did a backup in TWRP before flashing the PA alpha ROM, realized I needed CWM, so flashed that over in TWRP. Fine. Installed PAalpha in CWM. Fine. Decided to go back to the ROM I'd backed up (Beans), so attempted to flash TWRP over in CWM. Rebooted recovery. Sent me straight to stock recovery. Still boots into PAalpha fine.
I've tried to install TWRP via goo manager, and it says it's successful, but I'm still on stock recovery. Did I f- something up? How can I get back to custom? Did I screw my unlock somehow (doesn't seem like it would...)?
I've been doing the flashing thing since the Eris, but have been out of the game for a cycle, and am wary of messing around with things now that I'm at a point I don't quite understand. Much thanks.
Unlocked and rooted.
Click to expand...
Click to collapse
If you used the website in the twrp thread it does not work. I did the same thing. I had to odin the suck it verizon zip again. After that all was good. Hope this helps.
Sent from my SCH-I605
Android_Fr3ak said:
If you used the website in the twrp thread it does not work. I did the same thing. I had to odin the suck it verizon zip again. After that all was good. Hope this helps.
Sent from my SCH-I605
Click to expand...
Click to collapse
EDIT: I held my breath and flashed it over. Everything's great now. Thanks.
That's exactly what I used. Thanks so much. To be clear, flashing suck it verizon through odin is all i need to do (no need to mess with the other unlock steps?)
Best
vxkid said:
That's exactly what I used. Thanks so much. To be clear, flashing suck it verizon through odin is all i need to do (no need to mess with the other unlock steps?)
Best
Click to expand...
Click to collapse
yes...you should never need to relock bootloader.
Related
I flashed my phone with the works. Installed CWM, overclock kernel, and the Saurom rom that's in the Dev's section.
I needed to take it back to stock, so I flashed my phone with the Stock boot from here: http://forum.xda-developers.com/showthread.php?t=1504999 and then I flashed with the stock recovery. I went to install the stock ODIN from here: http://forum.xda-developers.com/showthread.php?t=1506330 and it wouldn't take. It just locked.
I decided to try it again, and it locked again. Its hanging up when it is writing to the NAND. I tried flashing the boot again, and its hanging as well. I JUST got the phone, and I am most likely going to take it back and get an AT&T swap. Anyone have any thoughts on what I can try?
I am not new to flashing phones and working with them, but I can't develop them. My Captivate has been to hell and back, and its still kicking strong. I pulled the SIM card and threw it on there, which currently has ICS on it and is overclocked.
I'm just curious if there's anything I can try before I send it back to AT&T? It has the counters triggered (ironically when I attempted to take it back to stock).
Not sure about the note but on my galaxy s2. To get back to stock I just flashed one .tar file not everything you listed.
Did you do full wipe before?
Sent from the only smartphone designed for Chuck Norris
kevinjgray88 said:
Not sure about the note but on my galaxy s2. To get back to stock I just flashed one .tar file not everything you listed.
Did you do full wipe before?
Sent from the only smartphone designed for Chuck Norris
Click to expand...
Click to collapse
Yep, I did a full wipe both before flashing and when recovery worked.
Also I wanted to note, the NAND can't be written on the boot side from what I can see. I can flash and get into CWM, but that's about it.
I am locking up when flashing the single TAR file that's available for the Note. If I can get the boot NAND to write, I am sure I can finally flash with the stock .tar
keilbaca said:
Yep, I did a full wipe both before flashing and when recovery worked.
Also I wanted to note, the NAND can't be written on the boot side from what I can see. I can flash and get into CWM, but that's about it.
I am locking up when flashing the single TAR file that's available for the Note. If I can get the boot NAND to write, I am sure I can finally flash with the stock .tar
Click to expand...
Click to collapse
take out the battery for a couple hours and try again.
Also, what about using ADB?
orangekid said:
take out the battery for a couple hours and try again.
Also, what about using ADB?
Click to expand...
Click to collapse
I will give that a try. If that doesn't work, I'll see if I can take it back to AT&T.
I can use ADB through CWM but I have no idea what the command is to install the boot.img and I cannot seem to be able to access the SD card at the moment. CWM won't mount it.
Pretty sure that bug has not been fixed
No adb access from cwm
keilbaca said:
I will give that a try. If that doesn't work, I'll see if I can take it back to AT&T.
I can use ADB through CWM but I have no idea what the command is to install the boot.img and I cannot seem to be able to access the SD card at the moment. CWM won't mount it.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I717 using XDA App
00mred00 said:
No adb access from cwm
Click to expand...
Click to collapse
I've dd'd several radios over adb while in cwm on my Note.
So I was pretty determined to get Cm 10.1 running on my Galaxy Note 2 for Verizon. Before hand, I was using TWRP to do all my ROM flashings but when I tried to use CM 10.1, I was told I must use CWM for it to work properly.
Here's my issue, I tried using CWM but it kept on giving me an error and after searching for awhile, it said its because I'm trying to use TWRP instead of CWM. So I flashed CWM and it gave me the same error. Tried both Touch and regular, downgraded and upgraded to the latest CWM but still same error. So I said **** it and installed the lastest TWRP. Then all the ROMs that were giving me issues started to install flawlessly. Then I went to CWM and it gave me the same error.
Am I doing something wrong when I flash CWM? I tried both Odin and APP Update way and both with same results. After using TWRP for awhile, I actually am starting to like the CWM Touch a lot better and I want to switch but not if its going to be giving me problems every flash.
Any insight would be helpful,
and as always to everyone on this forum, thanks
Just make sure you are using the latest version of TWRP 2.5 and you will be fine. You also may need to re-download your ROM file.
Well I am, in a way, stuck using the TWRP right now but I would like to know if I can actually change it to CWM. And if so, how would I go about doing that? because flashing the CWM alone isn't doing anything for me.
wythyntime said:
Well I am, in a way, stuck using the TWRP right now but I would like to know if I can actually change it to CWM. And if so, how would I go about doing that? because flashing the CWM alone isn't doing anything for me.
Click to expand...
Click to collapse
That is the way I have always gone about getting CWM on my phone back when I wanted it. I would just flash over TWRP in TWRP and then reboot system and then reboot back into recovery and it would always be CWM. If it doesnt work for you that way then see if they have a Odin tar and if so follow the instructions to flash it in Odin. They may not have an Odin flashable though, its been a long time since I have used it and on a different phone so....
Sent from my SCH-I605 using XDA Premium HD app
Let me actually rephrase this. (My bad for any confusion)
So if I try to flash a rom using TWRP, it goes through without any issues, even the CM rom. But when I flash CWM and try flashing, it gives me the getdevice-"(t0vzwte)"-not exact".. When researching, I was kept on told its because it is running TWRP. I tell them its CWM and they told me to update my CWM. I actually like CWM a bit better, idk why. but I was just trying to get my phone 100% the way I want it.
To make a long story short, I need to flash the stock recovery image back to my phone.
I am on the me7 build, rooted. I used goomanager to flash the custom twrp recovery. I guess I shouldn't have done that.
But anyway, I want to get a stock recovery back on so that I have a working recovery on my phone. I have looked around and I can't seem to find one.Of course, I can't boot into recovery now with twrp installed.
Any help and guidance on this would be greatly appreciated!!
Flash this in odin and then root me7 again....
http://forum.xda-developers.com/showthread.php?t=2357235
Sent from my SCH-I545 using xda app-developers app
I would use the no wipe me7 image from the dev section, you dont lose any apps/data with those. Like sporty said youll have to re root tho.
Sent from my SCH-I545 using Tapatalk 2
Same exact thing happened to me too. Did this and worked like a charm. Thanks, i've only had the phone two days and thought i was gonna be screwed!
Thanks for this!!! I also tried to flash a custom recovery on ME7.
Got a s4 today, followed the root guide here, using mdk pre release kernel. Did not unlock the boot loader. Loaded hyperdrive and after loading everything did the reboot. left me at the black samsung screen with an unlocked padlock and custom underneath. i can get into recovery and download. but no matter what i do will not progress screens (even tried full cache, dalvic, system, and data wipe and reloaded Hyperdrive. same results)
Should i re flash back to stock and try the entire process over again? if so, links please
also, what did i do to soft brick my phone? for future avoidance
and whats the difference between mdk and me7?
You probably got a bad download of the rom. Its a good idea to verify the md5 after its been downloaded. Once you can get a good download of the rom you dont need to odin back you can flash the rom in recovery and youll be good to go. The me7 ota is the newest firmware, has a few nice changes but it also has a non exploitable boot loader so you cant run a custom recovery on it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
You probably got a bad download of the rom. Its a good idea to verify the md5 after its been downloaded. Once you can get a good download of the rom you dont need to odin back you can flash the rom in recovery and youll be good to go. The me7 ota is the newest firmware, has a few nice changes but it also has a non exploitable boot loader so you cant run a custom recovery on it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
To clarify, your suggesting re downloading rls8, and try flashing that. Then, if that doesn't work, re flash the stock kernel (basically go through the Odin root guide again?)
Thanks!
Redownload rls8 verify the md5 checksum to make sure its not another bad download and then flash. As long as you can get into custom recovery of your choice and the download is good theres no reaaon it shouldnt work.
Sent from my SCH-I545 using Tapatalk 2
correct md5sum, same results.
both odin'd kernels have no effect, same boot problem. anyone know a fix?
Hopefully someone will. Same problem. Putting my phone back to stock rooted MDK works. The minute I try to flash Hyperdrive 8 and 8.1, it boots fine, then hangs on a restart.
Atleast, Will verizon exchange the phone seeing this?
Your mistake, why should Verizon replace something you caused.
Did you make a nandroid of the stock Rom prior to flashing?
Sent from my SCH-I545 using Tapatalk 4
Addiso said:
Your mistake, why should Verizon replace something you caused.
Did you make a nandroid of the stock Rom prior to flashing?
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
and yet no one has yet been able to pinpoint what mistake i made in installing a rom i've used for 12 months (s3) and installing a new version on a new phone while following every instruction to the letter, suddenly ****s on me. so please, enlighten me, what mistake did i make?
You didn't make a mistake. Chances are, you just used the wrong recovery. I spent 7 hours last night trying to fix my phone. I factory reset this morning to the stock MDK and re-rooted and figured out how to use ADB to install the Clockwork Mod Recovery. It's difficult to get started and figure out how to install and use it, but there are resources out there that will help you figure it out. I reinstalled the new 8.1 Hyperdrive with CWM recovery and was delighted when the ROM actually rebooted without fuss. It did hang on the Custom unlock screen long enough to make me nervous though. Figure out ADB and add CWM. It will work.
Edit for your steps: Reinstall the stock MDK with Odin. Reroot as per the instructions in the MDK root thread. Instead of TWRP, use CWM Recovery (which isn't nearly as easy), then reinstall the latest Hyperdrive (or whatever you were trying to install).
Hey guys, I need help.
I consider myself fairly adept at handling rooted devices, but I have not been following development for the GS4 for the last several months and have been running the last release of Synergy before their hiatus.
I was going to try out something different. I always enjoyed Beanstown's Jelly 'Beans', and thought I would try Build 7.
Now I am stuck at the Samsug Galaxy Boot Logo and it never goes to the Custom Boot Screen.
WORSE...I managed to break my recovery...so it will not boot their either.
Only mode I can boot to is Download.
Maybe I am just blind but I searched and could not find any Odin flashable recoveries...does anyone have one? Is there a rooted MDK file out there that I can flash via Odin?
Someone please help
Did you do the proper wipes when flashing the new rom? There arent any odin flashable recoveries for the s4. I would probably use the no wipe mdk image to recover (wont lose any user data) since you have no custom recovery to flash something with. Youll have to start over but youll have a working phone at least.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
jbg25 said:
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
Click to expand...
Click to collapse
Yeah looks like you got everything in order. Rom manager or rom toolbox will auto loki the recoveries. No need to update radios when flashing beans either. Itll already have the radios included unless your wanting to flash the mj7 radio seperately then I believe youll be ok doing that. I havent done alot of reading on the newest radios.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
jbg25 said:
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
Click to expand...
Click to collapse
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
beanstown106 said:
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
Click to expand...
Click to collapse
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
jbg25 said:
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
Click to expand...
Click to collapse
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
jbg25 said:
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
Click to expand...
Click to collapse
Go here. Get 2.5.0.2
http://techerrata.com/browse/twrp2/jfltevzw
Instructions
http://teamw.in/project/twrp2/181
At the bottom of the page.
Edit;
Or flash this in recovery
http://forum.xda-developers.com/showthread.php?p=45006486
I would reboot to recovery after flashing to make you got it on the right version.
Then make sure you can still boot back to your rom.
Then go back to recovery
Wipe
Factory reset.
Advanced
Check system, Data, davlik and cache
Wipe
Go back to main screen
Install
Fund your rom to flash.
Sent from my SCH-I545 using xda app-developers app
Me too. I tried the [ROM][TW4.3]STOCK-ROOTED-MJ7-AROMA-LOKI'd ROM with CWMR. Wiped Dalvik. Cache, Ractory Rest/Data. Seemed to install fine but then hung at "Custom". Fortunately I was able to a Nandroid Restore but not sure where this went wrong. Finally got TWRP to install after several failed GooManager attempts over the past month. May CWMR is the problem.