Got my Note a few hours ago. Charged it up. Downloaded Odin. Rebooted to download mode. Used Odin to flash some pda.tar that I got from a thread here which said it would install root.
My phone rebooted, and it has been stuck at "Samsung" ever since. Reboots and pulling battery do nothing. Reboots to a stuck samsung logo. I've also, since, flashed CWM successfully, and I'm able to boot to CWM.
I attempted to flash the CM10 builds from these boards, and it errors out with a build.prop thing and refuses to install the package.
Am I bricked without ever making even 1 phone call on my new phone? ..
You are not bricked. If you were bricked you would not be able to get into CWM.
What ROM did you try to install and can you still see it from CWM?
Also which CWM did you install? I think the version of CWM is probably the issue with CM10, just a guess.
Can you get in to download mode?
Also, what version of the Galaxy Note do you have? I717 or what?
From what I've seen all cmw versions posted on the board are too old to flash cm10.
Flashing cmw and then booting up to install/download/flash ROM manager and the latest version of cmw will fix the cm10 problem. But if you attempted to flash a cmw tar and it got stuck at the boot screen you likely flashed the wrong version for your os.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
kinghorsey said:
From what I've seen all cmw versions posted on the board are too old to flash cm10.
Flashing cmw and then booting up to install/download/flash ROM manager and the latest version of cmw will fix the cm10 problem. But if you attempted to flash a cmw tar and it got stuck at the boot screen you likely flashed the wrong version for your os.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I flashed a factor(?) build. It's an old gingerbread. Booted up. Tried to run Kies. It, of course, told me to fly a kite. Ran the pda.tar again and it installed a kernel, succesfully, that then allowed me to install superuser. Then I flashed my CWM again. It works. Just did a backup.
When I try to use it to install CM10, i get a status 7 error. I'm using the 4-14-2012 touch recover found at http://forum.xda-developers.com/showthread.php?t=1584576
From what I'm gathering from your post, if I install ROM Manager, it will update me to a better CWM, and that CWM will flash CM10 without status 7ing on me?
Thanks for the quick responses guys. I've done a number of Droid's, nexus 7, and my Acer a500, but I'm new to Odin. The thought of bricking a phone without owning it 3 hours had me in a panic.
edit: installed ROM manager. It doesn't give me the option to download CWM for a note. Not sure what to do there.
I don't believe your Note is bricked. This thing seems to be bullet proof.
Anthony820 said:
I flashed a factor(?) build. It's an old gingerbread. Booted up. Tried to run Kies. It, of course, told me to fly a kite. Ran the pda.tar again and it installed a kernel, succesfully, that then allowed me to install superuser. Then I flashed my CWM again. It works. Just did a backup.
When I try to use it to install CM10, i get a status 7 error. I'm using the 4-14-2012 touch recover found at http://forum.xda-developers.com/showthread.php?t=1584576
From what I'm gathering from your post, if I install ROM Manager, it will update me to a better CWM, and that CWM will flash CM10 without status 7ing on me?
Thanks for the quick responses guys. I've done a number of Droid's, nexus 7, and my Acer a500, but I'm new to Odin. The thought of bricking a phone without owning it 3 hours had me in a panic.
edit: installed ROM manager. It doesn't give me the option to download CWM for a note. Not sure what to do there.
Click to expand...
Click to collapse
First don't use rom manager it is crap software caused me more headaches than help. Use twrp here http://forum.xda-developers.com/showthread.php?t=1647575. Wipe your Note than flash cm10 than flash jb google apps and you will be up and running.
Anthony820 said:
I flashed a factor(?) build. It's an old gingerbread. Booted up. Tried to run Kies. It, of course, told me to fly a kite. Ran the pda.tar again and it installed a kernel, succesfully, that then allowed me to install superuser. Then I flashed my CWM again. It works. Just did a backup.
When I try to use it to install CM10, i get a status 7 error. I'm using the 4-14-2012 touch recover found at http://forum.xda-developers.com/showthread.php?t=1584576
From what I'm gathering from your post, if I install ROM Manager, it will update me to a better CWM, and that CWM will flash CM10 without status 7ing on me?
Thanks for the quick responses guys. I've done a number of Droid's, nexus 7, and my Acer a500, but I'm new to Odin. The thought of bricking a phone without owning it 3 hours had me in a panic.
edit: installed ROM manager. It doesn't give me the option to download CWM for a note. Not sure what to do there.
Click to expand...
Click to collapse
first things first
GET RID OF CWM. it will just cause more issues then it needs to.
second
INSTALL TWRP2.2.1.1
third
enjoy your day. *and make a new backup in twrp2.*
Anthony820 said:
I flashed a factor(?) build. It's an old gingerbread. Booted up. Tried to run Kies. It, of course, told me to fly a kite. Ran the pda.tar again and it installed a kernel, succesfully, that then allowed me to install superuser. Then I flashed my CWM again. It works. Just did a backup.
When I try to use it to install CM10, i get a status 7 error. I'm using the 4-14-2012 touch recover found at http://forum.xda-developers.com/showthread.php?t=1584576
From what I'm gathering from your post, if I install ROM Manager, it will update me to a better CWM, and that CWM will flash CM10 without status 7ing on me?
Thanks for the quick responses guys. I've done a number of Droid's, nexus 7, and my Acer a500, but I'm new to Odin. The thought of bricking a phone without owning it 3 hours had me in a panic.
edit: installed ROM manager. It doesn't give me the option to download CWM for a note. Not sure what to do there.
Click to expand...
Click to collapse
First don't use rom manager it is crap software caused me more headaches than help. Use twrp here http://forum.xda-developers.com/showthread.php?t=1647575. Wipe your Note than flash cm10 than flash jb google apps and you will be up and running.
One last thing if you want Adobe flash to work in your browser (i.e. Dolphin) you have to stay with ICS builds. Adobe stop supporting Android after 4.0.X releases.
Thanks guys. I swear I'm only a completely flustered noob with the note. I've got a custom ROM'd nexus 7 on one side of me and I'm using my sdcard from my CM10'd acer a500.
I can't thank you all enough. Everything is now running -- cm10 and booting -- and I'm live.
@ Anthony820.....
I have edited your topic to show [Solved] so that other users can see the status.
@ everyone else.....
Thank you for assisting the OP. This is what XDA is all about.
JamieD81 said:
first things first
GET RID OF CWM. it will just cause more issues then it needs to.
second
INSTALL TWRP2.2.1.1
third
enjoy your day. *and make a new backup in twrp2.*
Click to expand...
Click to collapse
Nothing wrong with ROM manager and I've never had an issue with it on the note. It does only flash newer cwm on ICS and doesn't seem to support gb well but that is easily bypassed.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Related
gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Did you try to wipe data/factory reset/ wip cachd and wipe dalvik?
all of it. follow directions for each rom exactly. i always end up in the same spot
burnitdown said:
all of it. follow directions for each rom exactly. i always end up in the same spot
Click to expand...
Click to collapse
How much you wait? After I flashed the Galaxy Task 14 room earlier this day it took several minutes to load.
Certain ROMS require an older version of CWM, such as CM9. If that is the latest version you have installed it may not work. Maybe try using ODIN to flash the recommended version (you can easily find that in the CM9 Nightly threads or simply by searching around)?
bar_rodoy
Click to expand...
Click to collapse
i let it sit long enough.
this_is_nick6
Click to expand...
Click to collapse
i'm using the most up to date cwm. right now i'm trying to flash aokp m4
burnitdown said:
gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Click to expand...
Click to collapse
Can you link us to the CWM 5.8.3.1 recovery your using???
As far as I know this is the latest version of CWM http://droidbasement.com/db-blog/?p=2655 as of 6/30 and it's only 5.5.0.4.
As far as Googling is telling me...
1. It may be a touch recovery?
2. I couldn't find a many search returns that mentioned it being for Tab10.1s
3. The search returns I did find that mentioned Galaxy Tabs were in languages I don't read.
Just curious don't ya know...
Sent From My Galaxy10.1 Class Starship....
Questions go in the Q&A section
my recovery is listed on the cwm site under rom manager. it's not touch
now i'm curious as to what version everyone else is using
okay. so i flashed 5.5.0.4 through odin then flashed aokp m4 plus gapps. all seemed to go well until boot time. i've been sitting at the samsung screen for a full 20 minutes now. i suppose my next course of action would be to revert to stock via odin and start the process over? i'd really like to use this thing but absolutely can't stand tw
you may have gotten a corrupt partition somewhere. I'd odin back to stock and start fresh. fwiw, I wouldn't trust ROM Manager for the latest recovery, it doesn't always have the correct file for your device. For example, for may particular phone Rom Manager had never worked properly and soft-bricks the phone every time.
Always check here on XDA for the proper recovery files for this device first.
that's all i needed to hear. now, can anyone point me in the direction of the file i need? my searches all point to S0ckM0nk3y's link which results in a 404 error
disregard my last post. i flashed sam's ics via odin. i'll play with it and try to like it. thank you sir
huh. still can't flash a custom rom...
Well, I don't know what I did but i was able to get MapleSyrup's CM10 preview to run. I'm happy for now
Are you doing a factory reset and wiping the cache in CWM before you flash? I always do that and then use titanium backup to restore my apps.
Also, what version of recovery are you using? I'm on CWM 5.5.0.4 which I've used to flash a couple of different roms, including the latest stock ICS from Toldo I think.
you can get it here and use ODIN to flash. Just make sure you download the correct version for your device:
http://droidbasement.com/db-blog/?p=2668
i had the same problem. i flash stock ics rom for my 7510. at first it looks fine until i try to reboot my tab. it starts to hang at the bootscreen. i try to reflash the rom via recovery but fail. try to install nandroid backup and also fail. the last resort is to do clean flash from odin. this thing happened 5 times in 3 days. one time after i install all the apps and try to restart my tab then it happened again, stuck at bootcscreen.
My phone wont boot now.
It stays stuck at the 2nd Samsung during the boot up.
What happen was I updated today to offical ICS from my rooted gingerbread.
I updated via kias today to get official ICS, got it working and I noticed I didn't have cwm install anymore, so I followed this http://forum.xda-developers.com/showthread.php?t=1504218
It is pass it did it reboot thing, and never got past the 2nd "samsung" loading screen.
Anyone know how to get my phone booting again?
Flash the latest ICS kernel
I am not sure how to do that without cwm.
Before I updated to ICS when I press power + up down, it booted into CWM. Now when I do that I boots into Android System Recovery <3e>
EDIT: Good news.
Got CWM through installed though odin and then I restored to my gingerbread backup I made earlier.
Flash your roms via clockwork recovery mod from now on.
Drop the ROM .zip on sd card and then enter recovery. Wipe everything three times each then flash a uclf6 based ROM. Never touch Odin or kies again. Be happy. Ice cream sandwich is way better than ginger bread
Sent from my SAMSUNG-SGH-I717 using xda premium
Had the same exact problem. I "believe" the problem was that the CWM I flashed was perhaps incompatible with the official ICS?
I used Odin to flash cwm 5.5.0.4 as suggested and the fone was shut down with the hanging Samsung screen as you mentioned. I used the DL screen with Odin to the 600mb Team Objection ROM, which at least got me up and running again. I found out that CWM did in fact flash once the ROM was compatible with it. Updated CWM, then to finally get full stability, I had to do a factory reset after clearing both caches, then install the CM9 official.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Update: I installed official ICS again last night, looks like I lost my root and CWM.
I don't want to mess anything up again, so could you tell me exactly what CWM file you used to flash so it doesn't hang at samsung again?
I was having the same problems but I think I was doing it wrong. How are you flashing the root files? I upgraded from Kies, then used Odin to flash cwm touch (5.5.0.4 I think), make sure to let the reboot and that it's actually turned on and you can see your homescreen. Once you do that, THEN flash the superuser 3.0.7 in cwm. Let the phone reboot properly and it should be okay.
I was doing the same without the reboots and that's what caused me to hang at the logo, but after the above it worked well. Give it a try. For anyone who needs to flash the T-Mobile radios also let the phone reboot and then flash it because I was having issues with that which was fixed by letting the phone reboot.
Make nandroids at every step in case it does hang so you can just restore and try again instead of flashing everything all over again.
Sent from my SGH-I717R using xda app-developers app
I've also tried rooting my AT&T Galaxy Note I717 which had recently upgraded to ICS via AT&T/Kies and my phone is stuck at the Samsung boot screen. While I'm no expert with rooting phones, I had no problem rooting it when it had GB installed so I figured I wouldn't have any problems rooting it again. Is flashing the ICS kernel the best way to fix this? Where do I get the ICS kernel from and how do I flash it?
Details: After my phone upgraded to ICS 4.0.4 kernel 3.0.8 (IMM76D.UCLF6), I followed some instructions to root it using Odin3-v1.85 and PDA->pda.tar. Other instructions used cwm-touch-i717-120414.tar.md5 and odin_n1717_cwm_recovery_b4.tar and I tried those but to no avail. So I have CWM v5.5.0.4 installed but I don't know what to do next.
Any help is greatly appreciated. Thanks!
dcdtrax said:
I've also tried rooting my AT&T Galaxy Note I717 which had recently upgraded to ICS via AT&T/Kies and my phone is stuck at the Samsung boot screen. While I'm no expert with rooting phones, I had no problem rooting it when it had GB installed so I figured I wouldn't have any problems rooting it again. Is flashing the ICS kernel the best way to fix this? Where do I get the ICS kernel from and how do I flash it?
Details: After my phone upgraded to ICS 4.0.4 kernel 3.0.8 (IMM76D.UCLF6), I followed some instructions to root it using Odin3-v1.85 and PDA->pda.tar. Other instructions used cwm-touch-i717-120414.tar.md5 and odin_n1717_cwm_recovery_b4.tar and I tried those but to no avail. So I have CWM v5.5.0.4 installed but I don't know what to do next.
Any help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
Update: I restored my phone back to a non-rooted working Android 4.0.4 by downloading the stock ROM for my phone (I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5) and uploading it using Odin3-v1.85/PDA. I didn't even lose any of my settings or data. Now I need to figure out how to successfully root it. But at least I'm not worried about getting stuck on the Samsung screen anymore.
Open odin , PDA cwm file, Droid in dl mode, plug in start unplug, reboot, go to cwm recovery mode and backup onto sd card.
Im learning more, as i soft bricked mine last time
dcdtrax said:
Update: I restored my phone back to a non-rooted working Android 4.0.4 by downloading the stock ROM for my phone (I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5) and uploading it using Odin3-v1.85/PDA. I didn't even lose any of my settings or data. Now I need to figure out how to successfully root it. But at least I'm not worried about getting stuck on the Samsung screen anymore.
Click to expand...
Click to collapse
Odin....to get touch cwm, then download the super user zip and flash it, you will have root....
All can be found in "My links" see it in red...go to GNote page....
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
what about su binaries
Can i put both on my sd card and put it in my phone, cmw recovery and install from there?
liftedzuki said:
what about su binaries
Can i put both on my sd card and put it in my phone, cmw recovery and install from there?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1740367
ok look for the green arrow...and use those threads....to root...k
odin for touch cwm
flash super user
your rooted
You realize the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Rooted.
erad1 said:
You realize you the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
so correct...you nailed it...so many are trying to root with gb kernal....
I hope they go to the page I made and follow the green arrowed how to root ics...it is very super simple process to root the official ics...but ....
This happened to me after misreading a comment.
If you put your phone into download mode, plug it in, run kies, and do an emergency firmware recovery. You'll need the serial number. My phone is stock ICS again. Works fine.
erad1 said:
You realize the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
so cwm 5.5.0.4 touch is a GB kernel? Because that's all I flashed after the KIES update to ICS and I got the hanging Samsung logo.
I believe some people are trying to get ICS rooted with this cwm and are getting stuck. Of course there are ways out of it, but it'll help the learning process if we can find the problem.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
romeojunior said:
so cwm 5.5.0.4 touch is a GB kernel? Because that's all I flashed after the KIES update to ICS and I got the hanging Samsung logo.
I believe some people are trying to get ICS rooted with this cwm and are getting stuck. Of course there are ways out of it, but it'll help the learning process if we can find the problem.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Wait what??!!??!!
you need to read read read read and PLEASE read
Because CMW is not a kernel
Its a recovery
People wouldn't have these issues if they read.
Please refer to the stickies before you really damage your phone.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
The OP had posted that he flashed Da_g's GB kernel trying to get root...your issue if flashing CWM may be different. Hopefully you use the steps outlined by bigjoe in his post.
Sent from my SAMSUNG-SGH-I717 using xda premium
Problem Solved. Found the correct version of recovery and bootloader. 4.2.2 roms will now install. Thank you to those who were willing to help. Now that I have educated myself on this tablet, I will begin developing for it.
-Neo
IAmTheOneTheyCallNeo said:
Good morning everyone
Just yesterday, I chose to update my tablet to one of the xda posted JB roms. I'm coming from an ics build 38 AOKP that I've been on for several months.
After I'd confirmed a successful download, I performed all the necessary cleaning procedures pre-flash, flashed the rom, and was stuck at the splash screen.
So I went back to the ics build and attempted the same with a cm-10.1 build with the same effect. Upon asking the first developer for advice flashing his rom, I was advised to update my recovery which was an older 5.x version of CWM to which another member directed me to the latest version.
Prior to this, I had attempted to use rommanager to update the recovery. During that process something happened in which the device rebooted and froze at the splash screen. I attempted a reboot into recovery via power+volume down and when selecting recovery, I only got a black screen.
So I took the Odin route and dropped the latest cwm tar.md5 through pda in download mode which allowed me to freely re-enter the rom and reboot without issues. However I still only have a black screen when attempting to get into recovery.
Any advice on how I would be able to restore my custom recovery without returning everything to factory images and starting over?
Thank you to those willing to spend the time and effort to help me solve this problem.
-Neo
Click to expand...
Click to collapse
You need to flash a new recovery. Grab a copy and install it using ODIN and you should be all set.
Re: [Q] 7510 (p4wifi) CWM Recovery assistance needed
k1mu said:
You need to flash a new recovery. Grab a copy and install it using ODIN and you should be all set.
Click to expand...
Click to collapse
Thanks for your response. Are you suggesting that I flash an older version of ClockworkMod recovery? I already flashed the latest version through Odin which gives me the same black screen.
Sent from my HTC One X using xda premium
IAmTheOneTheyCallNeo said:
Thanks for your response. Are you suggesting that I flash an older version of ClockworkMod recovery? I already flashed the latest version through Odin which gives me the same black screen.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I misread what you said. Apparently you've got your rom installed but recovery isn't working, correct?
I had no problems on my 7510 using CWM v5.5.0.4 and with CWM Touch 5.8.3.1 - either of those should work if you flash them with ODIN or Mobile ODIN.
Re: [Q] 7510 (p4wifi) CWM Recovery assistance needed
k1mu said:
I misread what you said. Apparently you've got your rom installed but recovery isn't working, correct?
I had no problems on my 7510 using CWM v5.5.0.4 and with CWM Touch 5.8.3.1 - either of those should work if you flash them with ODIN or Mobile ODIN.
Click to expand...
Click to collapse
Ok cool I'll give 5.8.3.1 a try if I can find it. So, in my reading I was under the assumption that cwm recovery needed to be above 6.x.x for use with 4.2.2 jb roms. Are you currently or have been on a 4.2.2 rom with your tablet using the recoveries that work for you?
Sent from my Rezound using xda premium
IAmTheOneTheyCallNeo said:
Ok cool I'll give 5.8.3.1 a try if I can find it. So, in my reading I was under the assumption that cwm recovery needed to be above 6.x.x for use with 4.2.2 jb roms. Are you currently or have been on a 4.2.2 rom with your tablet using the recoveries that work for you?
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
No, I've never tried any JB roms, so I didn't need the latest CWM. If nothing else, trying a different known-working CWM will at least prove that you're able to flash recovery and have it working.. then you can go find a 6.x recovery for the Tab 10.1.
Progress Report
So I managed to shell instal a version of TWRP and the recovery works perfectly! However, I am unable to use any roms except aokp ics (milestone6) lol
Could this be a recovery issue? Still somewhat unfamiliar with the Tab 10.1, I assumed there was an hboot that I could access to flash a recovery image but all reboot attempts into hboot (4.0.4) ended in a simple reboot.
Back to recoveries however, I attempted to flash different versions of CWM tars through Odin3 v1.85 and they all ended in solid black screens. Somewhat at a loss as only the Milestone 6 aokp build is accepted to my tablet and no other ics or jb builds. Somewhat off topic, is there no requirement to RUU upgrade the firmware to something later in order for the table to accept newer recoveries and hboots?
-Neo
Problem Solved. Found the correct version of recovery and bootloader. I apparently have an unlocked p4tmo that runs a few p4wifi roms.. Anyway, 4.2.2 roms will now install. Thank you to those who were willing to help. Now that I have educated myself on this tablet, I will most likely begin developing for it.
-Neo
Welcome man! This device has a fantastic community and another developer willing to put work into it really does help to breathe new life into an aging device. Enjoy your time here
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.
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.