[q] cwm fail - T-Mobile, Samsung Galaxy SIII

I have done this a number of times and I know it works. I got a new phone GS3-T999. I want to insatll CWM and add a custom ROM. I go to Odin, I find my CWM.tar file, I run it and the phone reboots. NO Custom recovery, but stock recovery
The custom binary counter shows 3 (cause I ran it three times BECAUSE IT WASN'T WORKING)... and custom for Binary and Status.
I'm frustrated and have no idea what to do. This phone is new and did the OTA JB update.
Does the JB Stock ROM have something to do with this?
My question, what do I have to do the get my Custom Recovery so I can install .zip from SD card and get my custom ROM on the phone.

You need root first. Go the the link. Follow the root66 method using the odin instructions. After that download rom manager and load cwm recovery.
http://forum.xda-developers.com/showthread.php?t=1949687

Related

I can't seem to root

I went back to odin to get a fresh of my gs3. I did the 4.1.1 update and now i have an issue.
I can't seem to install any recovery on my samsung galaxy s3 in order to root it.
I have tried just about all the downloadable clockworks out there and even tried twrp...its no go. I do not know why this is happening because I never had this problem before when rerooting my gs3.
Any one faced this before? suggestion?
You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.
Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).
bikrame said:
You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.
Click to expand...
Click to collapse
I do, personally I only flash via odin....root66...is that a rom? how do I flash that without rooting?
Aerowinder said:
Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).
Click to expand...
Click to collapse
I am not quite sure what you are saying here about needing to access recovery mode after I flash...I flash the clockwork recovery mode and when i go to access it, i only see the stock.
I i reflashed odin again and decided to root using 4.0.4 ics...now it worked..I guess we can't flash over 4.1.1 anymore?
anyway, thank you both ^.^
The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?
Aerowinder said:
The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?
Click to expand...
Click to collapse
Oh now that make a lot of sense. So I was not suppose to reboot before going into recovery with 4.1.1...will keep that in mind next time!
Even though you're rooted, flash the 4.1 root66 in Odin. You don't want to go from ICS to JB via recovery, it doesn't flash all partitions. After you flash root66 in Odin, you will already be rooted. Then you can just flash a custom recovery.
Sent from my SGH-T999 using Tapatalk 2
If I remember correctly you can still root normally on the later builds, you just have to pop out you battery after you flash, don't let it auto-reboot, then you can put the battery back in and get to clockwork recovery.

[Q] Won't boot rom or cwm recovery - only download mode

Hi! I have encountered a problem, and really hope someone can help me!
Two days ago i flashed Omnirom Nightly on my n7105 to get Android 4.4. I was running cmw recovery but couldnt get the ota updates to work, so i was trying to flash open recovery instead. I used an apk that was supposed to install a script.
When i rebootet my phone, all i could get was the Note 2 boot image. It wont boot into recovery mode, or the rom. I am however able to boot into download mode.
Custom Binary download: Yes (4 counts).
Current binary: Custom
System Status: Custom.
How should i proceed? I've already tried to reflash cwm recovery, which did work, but didnt solve the problem. I am currently downloading stock firmware, but the file is 1.2 GB so it will take i while. Figured i should ask here in the meanwhile.
I'm not an expert at Android at all, im just a guy enjoying having custom roms and playing around a little. I do know that there are a lot of very talented people in this forum, and i really hope someone can help me find a solution. I've been googling for hours, but cant find anything that seems to work for me / or i dont fully understand and wont risk try before someone approves it.
Thank you, Vetle
EDIT: Is it correct that i cant flash any custom rom trough Odin? Or could i just flash omnirom again trough Odin?
If i manage to flash the stock rom and the bootloop goes away, will everything go back to normal, so i can flash cmw again and then a custom rom again?
No custom rom can be flashed through odin, as most of them are zip cwm/twrp base.
When u can only go to download mode, an official firmware only can help u through odin.
Sent from SM-N9005 with xda-app
Thanks for the answer!
Yup, i have flashed a stock rom now and i got the stock recovery. Everything was working fine.
Then i proceeded to do a factory reset in the stock recovery and flashed cwm trough Odin. When it was done, it wouldnt let me into recovery again! I can still boot up the phone tough.
I've also tried Open recovery. CWM via Rom manager. Open Recovery trough Goo Manager... Still cant get recovery to work, the stock rom works tough.
Any ideas?
Okay, i tried to flash the stock rom again and installed Rom Manger.
It still showes TWRP and CWM under installed recovery and i guess these its these two who makes the problem.
My plan now is to figure out how to completely remove them. I've never done anything related to adb before, so i hope it possible to remove them in another way?
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
vetle666 said:
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
Click to expand...
Click to collapse
I had recovery problems in the last few days also.
Installed DN3 rom using philz recovery, because its capable of prepare the phone to a new rom in a easy way.
It all went fine until first reboot.
I had a recovery boot loop. All I could see were some buttons and then reboot again.
Like you I had download access and flashed philz with Odin, but no luck.
Installed twrp via Odin and all was fine, and flashed philz new version.
Then I had to flash a new kernel (to be able to access wifi) and it all started again. Now I'm back on twrp.
Let's see what happens on my next flash.
My suggestion is to flash the recovery, and if that's OK flash the rom and use it
Next time you need recovery get Odin to help, but not all the way from an original rom. Just the custom recovery.
But if you want to get rid of your strange recovery configuration, and you are not already on new 4.3 recovery(which in your case could explain some of the problems you had) , with knox, install an older original rom, 4.1, and make all the steps, root it, install a custom recovery, and from there the room you want.
Reading your path sorting this problem, that was what would do next
Best regards

[Q] already installed stock firmware, can't install stock kernels or recovery

I tried to unroot my phone after getting stuck in a cyanogen bootloop a while back. I managed to get into recovery and install stock firmware via Odin. I did not however install the stock kernel or stock recovery. I am now in a stock t-mobile bootloop. I'm not sure what to do, I have been unable to get into recovery thus far, but I can keep trying. What can I do?
lasabrjotur said:
I tried to unroot my phone after getting stuck in a cyanogen bootloop a while back. I managed to get into recovery and install stock firmware via Odin. I did not however install the stock kernel or stock recovery. I am now in a stock t-mobile bootloop. I'm not sure what to do, I have been unable to get into recovery thus far, but I can keep trying. What can I do?
Click to expand...
Click to collapse
Can you get in Download mode? To work with Odin you must be in Download mode, not recovery.
If you can get in Download mode, then start Odin and flash a TWRP Odin flashable recovery:
http://teamw.in/project/twrp2/101
Then at least you should have a functional recovery. From there you could either try to flash your stock ROM again, or any another ROM.
Are you 100% sure what you flashed was a good stock ROM for the T989 ?
Dont you have a nandroid you could restore?

Cant Flash ROM using TWRP

Hey guys.
Little review of what happen:
Woke up today and my phone wasn't able to use any of my apps. So, I though no problem let me flash my rom. ( I use SlimKAT)
When I downloaded latest stable ROM I was ready to flash. I come across error while flashing "Executing update binary in <zip name>".
Things I tried:
Wiping:
davlik cache
cahe
system
Rebooting and flashing again. gave me same error.
Any suggestions?
UPDATE:
Now I cant even enter TWRP.
I don't know what went wrong, but at this point there is really no downside to just starting over. You could use odin to return your phone to stock then install TWRP or CWM then flash supersu then flash your rom again.
qwerty3656 said:
I don't know what went wrong, but at this point there is really no downside to just starting over. You could use odin to return your phone to stock then install TWRP or CWM then flash supersu then flash your rom again.
Click to expand...
Click to collapse
Honestly im not sure what I am doing at this point.
My ODIN MODE setting are followed:
Product Name: SGH T999
Custom Binary Download: Yes(4 count)
Current Binary : Custom
System Status: Custom
Qualcol Secure boot: Enabled
Warranty Bit: 1
Boot-loader RP SWREV:1
Im not sure how can i flash my stock rom.
Can you suggest where to start.
Thank you.
I'm no expert so do your own research - I think you can skip a step and get the route 66 version of your ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
IT should be the NC2 rom. follow the instructions there to use odin and install the route 66 rom onto your phone - you should then have a rooted stock phone. Then you can install cwm or twrp and flash your rom
qwerty3656 said:
I'm no expert so do your own research - I think you can skip a step and get the route 66 version of your ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
IT should be the NC2 rom. follow the instructions there to use odin and install the route 66 rom onto your phone - you should then have a rooted stock phone. Then you can install cwm or twrp and flash your rom
Click to expand...
Click to collapse
My problem is that i cant boot in TWRP mode at all. It wont let me enter there.
When i try to flash via ODIN it wont pass.
Any other suggestions?
I got a feeling it have something to do with Custom Binary.
UPDATE:
I was able to get TWRP to boot from ODIN and it passes.
When I try to enter my TWRP it wont let me enter it will skip and go to loading screen of my rom and that's when it get stuck.
To use ODIN, you don't boot into TWRP. You put your phone into Download mode (hold the DOWN volume along with home and hit the power button - when the screen comes up hit the UP volume). You need to be running odin on your PC.

how to install i317 UCU Stock Recovery without using CWM or TWRP

I am am trying to take my Samsung i317 AT&T Note 2 back to stock.
Installed 4.4.2 NJ1 stock rom using ODIN. Reset/ cleared and started phone and went to OTA upgrade the latest patch from AT&T to make it to NJ2. However, when the phone reboots, the Samsung Note II logo shows up and the screen does dark. When I try to enter recovery, it starts to reinstall the OTA patch all over again and says updated. Tried turning the phone back on and the same thing happens again.
I was able to get the phone to work by reflashing the NJ1 stock rom and installed the ZIP stock recovery file using CWM. However, I am trying to get back to the original stock configuration as possible without having CWM installed on the phone and was hoping I can install the stock recovery so that when I go to download mode, everything shows Samsung Official. Knox Warranty Void is at 1, so I guess there is nothing I can do to fix that at this point.
Would installing this be the simple fix by downloading 4.3 Param.bin and Tz.img
Another would be to install the stock recovery ZIP file using CWM as I have already successfully done and maybe someone can point me to find a way to uninstall the CWM afterwards. I've searched online to remove CWM but couldn't find the md5.tar file that would do that from ODIN.

Categories

Resources