This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
lonoguge said:
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
Click to expand...
Click to collapse
Where did you get twrp?
lonoguge said:
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
Click to expand...
Click to collapse
What is "another rom"?
lonoguge said:
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
Click to expand...
Click to collapse
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
bhundven said:
Where did you get twrp?
What is "another rom"?
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
Click to expand...
Click to collapse
I got it from what I thought was the official XDA TWRP thread but I'm not sure if it was official or not
at first I tried reinstalling codename but now I'm trying Beam (Tuk edition) and it seems to be working
TWRP Major Boot Loop
hey guys, im new here and i desperately need help with my phone!
the other day i was flashing a rom on my samsung galaxy s 4g. Things were turning out fine, until i had some complications on my phone.. so, i removed the rom. when i rebooted my phone, it went directly into the team win recovery project boot loop and every time i try to reboot my phone, it goes into the twrp. I also can't wipe anything and i can't delete anything! Does anybody know how I can solve this or is my phone basically bricked
more details would be helpful..
As in what rom, or what kernel.... etc... and make sure you have the corret phone.
Same problem with t959p
Looks like I'm not alone.......here's my story
the other day I wanted to switch from a stock rom to a custom, so I flashed redux 1.3 which was actually a froyo rom, and it started draining my batt like crazy so I flashed another rom on top of the froyo rom not realizing what I was doing and somehow messed it up cuz now it will only boot into recovery.
Now just to be clear I know this was my fault, I know I should have odin'd back to stock first, but I wasn't thinking at the time.....Ohh and just so you know I've flashed this sucker hundreds of times and was always able to get out of any mess I got in.
So here is the situation as it stands now, 3 button combo to enter download does not work. I can only get it into download with the jig I made. the problem is even in download mode none of my pc's will detect the device as a Samsung composite device, so odin will not see it. I've installed every possible 32 n 64 bit driver I could find including reinstalling kies. Kies wont even see it. I've tried flashing a few roms that I know worked and still it just boots into recovery. Now one thing I'll tell you is that depending on which rom I flash I can get recovery to switch from cwm to twrp. right now I left it with cwm 6.x.
what I need is a cwm flashable stock telus t959p rom complete with bootloaders or at the very least a cwm flashable zip file containing the bootloaders to see if I can recover the phone.
ohh and if your thinking about telling me to google search for the answer then don't bother.......I've spent the last 4 days reading posts and going to different websites and repositories trying to find something that would help me and so far nothing has.
the only thing that might work as a last resort is pushing the bootloaders as per one of raver's or whitehawks posts but it's a little more complicated for me as I would have to set up a laptop with Linux as I don't think i'll be able to pull it off with any of my windows pc's, win7 and win 8 only.
so if anyone has the files I need or can make them please let me know....or if you think you have another solution I could try i'm all ears err eyes.
thanks
Jedi
Have you tried heimdall one-clicks? Maybe it's showing up as gadget or something like that. I've had luck using zadig and heimdall to bring it back from the brink of death.
http://forum.xda-developers.com/showthread.php?t=1358498
EDIT
Woops replied to the wrong thread .
Nothing to see here, move along
Would like to revive a slightly dead thread.
I upgraded to a Galaxy S3 and no longer use my SGS4G for daily use. I had AOKP and disliked it, FC's and didn't like the feel. I have been trying to install a new rom ( old rom, VH Black Ed. ). Every time It loads into TWRP I have the ability to select the zip, install, it says complete, but reboots right back to TWRP menu. I've tried flashing CWM and it will install, flash the rom, reboot, and right back to this TWRP B.S... what am I doing wrong? I want to continue to use this SGS4g for music and internet duties.
How can I install CWM and have it stay even after a reboot? This TWRP is starting to me off
Did you happen to one click to stock before you went ham at the recovery?
Sent from my SGH-T959V using Tapatalk 4
Related
I tried to flash a aokp rom and before flashing made a back up. Now when I flashed the rom and rebooted the phone im stuck at samsung boot. I can get into recovery. At first it was a messed up recovery i tried to get to an old rom and reinstalled inimitable on reboot still stuck at samsung but can get into red recovery. Backup when reinstalling says cant mount system/! please help me asap I cant do anything I need my phone I am in panic mode.
Have tried reflashing The ROM again...or if you just want to go back to stock see my signature for links to the one click method
...btw your in the wrong section to post this...
The OP for aokp does state to flash twice...did you?...first time with wipes, then you can pull battery ...go back to cwm and reflash...again.
going back to stock is your way. clear all that crap out
http://forum.xda-developers.com/showthread.php?t=1524081
Post one to stock.....
Post two to put cwm back on....
Read with detail...the thread I provided....
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
soulysephiroth said:
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
Click to expand...
Click to collapse
We have no ics boot loaders...froyo boot loaders make the recovery look funky...gingerbread boot loaders fix that problem and can be used with froyo, gingerbread and ics ...not trying to be rude or a jerk just informing you
Sent from my SGH-I997 using XDA
Actually the "messed up" or rainbow recovery is from the lack of gingerbread boot loaders, just figured this out this morning when I attempted to flash aokp uniporn. Once I did the heimdall one click with bootloaders checked (gingerbread boot loaders) I was able to successfully flash the aokp rom and recovery works perfectly. Its really better not to reply when one does not know what they are talking about oh and I was still able to reflash a gingerbread rom as well although I probably won't go back to gingerbread again since aokp is the **** and runs super smooth
Sent from my SGH-I997 using xda premium
Please move this thread from the Development Section.
edit- Thanks for moving it.
Sorry about posting so quickly in wrong section. I just know the guys who post in here are pros. I used heimdall and everything is back to stock, no superuser. Should that be right, am I now not rooted? I havent tried to boot into recovery, but I think I have it still. Can I just follow root methods if I want to go back to root? Thanks again.
I my experiences, I've noticed our phones use a form of "Cumulative" Upgrade system, where You have to essentially go from Froyo to GB to ICS or things go haywire when you actually start using your ICS Rom..
I've tried using Heimdall to flash back to stock, but it doesn't seem to fix all my files from time to time, so I still use GTGs Ultimate Unbrick, and once it starts up as you're in Recovery Mode do a Factory Reset/Wipe Cache Partitions, it helps with not having the "Google Authentication Failed".
It's a long process from start to finish either way, so i figure save yourself the hassle for the long run and wipe it fresh...
I used heimdall without clicking the GB bootloaders checkbox. Upon reboot after sucessfully flashing everything, my phone shows the rainbow color thing then boots normally. I have no seen any issues other than that, however I only got it back up and running about an hour ago. I will see as the day progresses what happens. I just would like to know where I go from here to reacquire root priveleges. When I try to boot into recovery with the button combo I get a rainbow colored screen and nothing else showing, should I re-run heimdall with gb bootloaders box checked?
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
drnecropolis said:
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
Click to expand...
Click to collapse
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Cjohns8792 said:
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
bigjoe2675 said:
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
Click to expand...
Click to collapse
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Cjohns8792 said:
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Click to expand...
Click to collapse
Aft your 1st flash...dont close program...but put your phone back into download mode again and then it should allow you to check the box...then..
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Axiomkid said:
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Click to expand...
Click to collapse
Can't access recovery, it just shows a full rainbow screen.
Cjohns8792 said:
Can't access recovery, it just shows a full rainbow screen.
Click to expand...
Click to collapse
my suggestion is do the method i mentioned..
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
volume up/home/power button is recovery try that
and you used rom manger to flash rom?
j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.
not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.
I'm stuck on the fuzzy samsung logo right after the sharp one, and right before the colorful boot animation.
Not vibrating repeatedly, but I checked and cleaned the power button.
It was acting buggy after having embryo 7 for a long time with no problems.....Then things started happening a lot, so I changed back to 6. Then one day recently embryo 6 locked up on boot and here I am!
I don't know what caused all this, but I can't get in to recovery either. It looks like it's going to, but then it freezes on the CWM start up screen. Never could get it in to recovery, but I was able to get it in to download mode, AND it looked like I successfully flashed the stock firmware according to Odin. BUT then it froze on at&t screen during start up. AND THEN went back to being frozen on mohans fuzzy samsung screen.
I really was trying to search, but I can't find it.... Help? Anyone....?
Dogs you do factory reset after Odin?
jd1639 said:
Dogs you do factory reset after Odin?
Click to expand...
Click to collapse
It looked like it was trying to restart after Odin finished the install, and the phone never made it past the water drop. Froze in the middle of that part. After a long time I finally unplugged it, and touched the power button. Then it went back to the original screen I was stuck on, and I could never get it to go in to CWM. It starts to, and then gets stuck.
I'm guessing you flashed cymbaline 3.8 on embryo 6. That kernel has issues. Reflash with 3.5 and see what happens. Should be stable then
icenight89 said:
I'm guessing you flashed cymbaline 3.8 on embryo 6. That kernel has issues. Reflash with 3.5 and see what happens. Should be stable then
Click to expand...
Click to collapse
I was just trying to go back to stock. Are you saying that the kernel will still be different even though I was going back to stock through Odin?
I liked mohan's ROM's, but I guess he got a different phone. I never had problems before, but if it's a kernel I can flash will that work through Odin?
Sorry if my questions are annoying, but I just want to make sure I can do it through Odin, AND I don't want to flash it if I'm too far gone for it since I can't even get in to recovery.
jwtruth35 said:
I was just trying to go back to stock. Are you saying that the kernel will still be different even though I was going back to stock through Odin?
I liked mohan's ROM's, but I guess he got a different phone. I never had problems before, but if it's a kernel I can flash will that work through Odin?
Sorry if my questions are annoying, but I just want to make sure I can do it through Odin, AND I don't want to flash it if I'm too far gone for it since I can't even get in to recovery.
Click to expand...
Click to collapse
I dont know whats the problem, but why you no try embryo 7?, i installed it yesterday with cymbaline 3.8 and not issues at the moment. I flashed it with CWM, i dont know why you are talking about odin, but if im wrong its ok, i installed embryo 7 with cwm.
Hope you understand me, english its not my first language.
-LuVaN- said:
I dont know whats the problem, but why you no try embryo 7?, i installed it yesterday with cymbaline 3.8 and not issues at the moment. I flashed it with CWM, i dont know why you are talking about odin, but if im wrong its ok, i installed embryo 7 with cwm.
Hope you understand me, english its not my first language.
Click to expand...
Click to collapse
I can't get in to recovery mode. Only recovery mode.
That's what I'm trying to figure out is just how to get to recovery, or anything else besides download mode.
And yes. I liked embryo 7 a lot. But something started happening about 2 1/2 months after I flashed it with no problem before that.
I love the arms at boot up..
jwtruth35 said:
I can't get in to recovery mode. Only recovery mode.
That's what I'm trying to figure out is just how to get to recovery, or anything else besides download mode.
And yes. I liked embryo 7 a lot. But something started happening about 2 1/2 months after I flashed it with no problem before that.
I love the arms at boot up..
Click to expand...
Click to collapse
You can have "the arms at boot up" without that rom.
To get into recovery, which seems like it's damaged for you, flash TWRP from odin.
http://forum.xda-developers.com/showthread.php?t=1773659
jwtruth35 said:
I can't get in to recovery mode. Only recovery mode.
That's what I'm trying to figure out is just how to get to recovery, or anything else besides download mode.
And yes. I liked embryo 7 a lot. But something started happening about 2 1/2 months after I flashed it with no problem before that.
I love the arms at boot up..
Click to expand...
Click to collapse
Ok, maybe a solution could be install TWRP, or my solution could be installing the oficial android 4.1.2 from odin and then download the CWM recovery and proceed to flash Embryo.
-LuVaN- said:
Ok, maybe a solution could be install TWRP, or my solution could be installing the oficial android 4.1.2 from odin and then download the CWM recovery and proceed to flash Embryo.
Click to expand...
Click to collapse
I appreciate the help, and I did try to install the official 4.1.2 from Odin. Twice. Both times the screen from odin looked exactly like it was supposed to if it was successful. It then tried to restart my phone as part of the install process, and then the phone freezes on start up screen......and done.
CANNOT get the phone in to recovery mode every time I try, but it goes in to download mode no problem.
That's why I'm here and still scratching my head. I'm stuck using a fusion I usually just have for my kid as a toy around the house.
lingowistico said:
You can have "the arms at boot up" without that rom.
To get into recovery, which seems like it's damaged for you, flash TWRP from odin.
http://forum.xda-developers.com/showthread.php?t=1773659
Click to expand...
Click to collapse
I just saw this. Time to try it, thanks.
jwtruth35 said:
I appreciate the help, and I did try to install the official 4.1.2 from Odin. Twice. Both times the screen from odin looked exactly like it was supposed to if it was successful. It then tried to restart my phone as part of the install process, and then the phone freezes on start up screen......and done.
CANNOT get the phone in to recovery mode every time I try, but it goes in to download mode no problem.
That's why I'm here and still scratching my head. I'm stuck using a fusion I usually just have for my kid as a toy around the house.
Click to expand...
Click to collapse
So u need to use Odin and flash a stock image back on the phone, go to sammobile.com and DL the firmware for ur device then place the phone in download mode load the tar file in Odin and click start, when it's done DL the latest twrp as its a little better than cwm because its updated more regularly, then use Odin to flash the recovery to the device and now u are back to stock rooted and from there with twrp, all is possible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
lingowistico said:
You can have "the arms at boot up" without that rom.
To get into recovery, which seems like it's damaged for you, flash TWRP from odin.
http://forum.xda-developers.com/showthread.php?t=1773659
Click to expand...
Click to collapse
Thank you so much!!! It's been a miserable 4 or 5 days, but I was able to get my phone back up and running!
soupysoup said:
So u need to use Odin and flash a stock image back on the phone, go to sammobile.com and DL the firmware for ur device then place the phone in download mode load the tar file in Odin and click start, when it's done DL the latest twrp as its a little better than cwm because its updated more regularly, then use Odin to flash the recovery to the device and now u are back to stock rooted and from there with twrp, all is possible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks to you also. Everything's right with the world again.
So I rooted my brother's infuse 4G because it was slow as sin and needed A. a data/cache wipe and B, I wanted to give him Jellybean
I followed all the instructions I could; rooted, installed the modded 3e (or thought I did), got a CWM installed afterwards, and then set about installing first CM9 (as the Jellybean ROM post says I should) followed by the actual ROM and its Gapps. Well, I installed CM9 (although it seemed to take all of 30 seconds, rather fast...) when I tried to wipe data/factory reset, CWM froze. I rebooted and from then on I had it softbricked. Stuck booting at the samsung logo, and when I tried to return to the recovery, the recovery was a garbled mess that looked like a scrambled TV channel. I used Heimdall and did the one-click reset to stock, and here I am. The phone boots to stock just fine, but my recovery is still completely boned.
Do I re-root? How do I install CWM again without being able to install 3e? (can't install 3e without a working recovery in the first place, after all..)
One anomaly of note - when I was going about all this, booting the phone into recovery always got me 3e, even after installing CWM. I had to manually install CWM by using an update.zip and "reinstall packages" every time I wanted to use CWM. ROM manager would boot me to CWM, but it took several reboots and a flashable CWM zip before I could even get CWM installed in the first place - ROM manager refused to do it the easy way.
What did I do wrong, and more importantly, how do I get back on track? What do I do to put a fixed recovery back on this thing? Odin? ADB?
Today was the first time I ever used Heimdall, I've been a fair weather flasher since the beginning, I've never had to ADB or Odin.
It sounds like you didn't install cwm recovery properly, but I'm not sure I've never ran into this problem before. If you go here
http://forum.xda-developers.com/showthread.php?t=1524081 and carefully read over the first and second post you should end up with gb and red cwm recovery. The way I've done it was to put the phone in dl mode and flash the first package (the stock gingerbread att rom). After it is installed and booted up, I then power it off and go back into dl mode. Then flash the second package, which is just the kernel and red cwm recovery, (be patient because it takes awhile). Once that is done then go into recovery and wipe data/factory reset, wipe dalvik cache, wipe system, and install cm9. I think it only installs the kernel and recovery the first installation after formatting and creating the partitions, but after its done you have to go through the menus and tell it to reboot. After it reboots it will be stuck at the cyanogenmod galaxy s logo, so you will have to go into recovery once more. When you're there you should have blue cwm (only continue if you do) and install jb, without actually having to install the full cm9. When you navigate to which ever jb rom you want to install, a prompt will appear stating that there is incompatible partition layout and to confirm installation you will have to reselect the jb zip again to install. It will flash pretty quick because at this point its doing the same thing as when you went from gb to cm9 and only installs the kernel, recovery, and reformat/creates the partitions, (I think). It will reboot on its own but it will take you back into recovery. At this point all you have to do is navigate to the same jb zip you want to install and flash it, followed by gapps, and then reboot system. This process has worked for me but I highly recommend reading and following the instructions given in the post above.
Use goo.I'm app. Also you need to flash GB bootloaders in Odin . is recovery all colorful? If you see recovery fine just get goo app on play store and install a recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I would go the ODIN route, I have bricked so many times because i try to make the impossible possible. Just search for a already rooted pda,mdr file. I skipped the cm9 part idk if that would make things better or not but as my post says im a risk-taker
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
UnhoIy said:
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
but if don't have any problems i'm good right or should i go back and do it
MajorLeagueROM said:
but if don't have any problems i'm good right or should i go back and do it
Click to expand...
Click to collapse
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
UnhoIy said:
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
MajorLeagueROM said:
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
Click to expand...
Click to collapse
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
UnhoIy said:
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
Click to expand...
Click to collapse
lol it happens to the best of us
I have a Galaxy Tab 2 7.0 gt3113. It is rooted,and I want to install a rom. The factory rom/kernel lags...get stuck ....and with all I have read the roms out there make a big difference. But I'm having a problem....I'm using rom manager and rom toolbox and I cant seem to install a rom. It load the rom whether from the computer or the download option but when it boot into recovery I get an error saying that the sd card is not found and I just end up manually re-booting the device....Ive tried this a few times choosing different things at the screen...a(abd....cashe....external storage....) it all ends up the same.....anyone have any idea what this means? I'm learning as I go....and was thinking about un-rooting my device then rooting it again.....maybe I did something wrong?
Complety bewildered....
Speedy8311 said:
I have a Galaxy Tab 2 7.0 gt3113. It is rooted,and I want to install a rom. The factory rom/kernel lags...get stuck ....and with all I have read the roms out there make a big difference. But I'm having a problem....I'm using rom manager and rom toolbox and I cant seem to install a rom. It load the rom whether from the computer or the download option but when it boot into recovery I get an error saying that the sd card is not found and I just end up manually re-booting the device....Ive tried this a few times choosing different things at the screen...a(abd....cashe....external storage....) it all ends up the same.....anyone have any idea what this means? I'm learning as I go....and was thinking about un-rooting my device then rooting it again.....maybe I did something wrong?
Complety bewildered....
Click to expand...
Click to collapse
if you are able to boot into recovery then please wipe cache partition and do a factory reset and then try to revert to stock rom
Speedy8311 said:
But I'm having a problem....I'm using rom manager and rom toolbox
Click to expand...
Click to collapse
For starters, stay away from ROM Manager! It's known to cause different sorts of problems on different devices while installing CWM and ROMs. I have only good things to say about ROM Toolbox in terms of tweaks and utilities, but never used it for ROM installation, and would suggest not to. Just download the ROM you want from its original source, put it on internal or external storage, and flash using your recovery (my personal all-time favourite is PhilZ Touch CWM, not sure what you are using). Do the proper wipes before flashing (full wipe is always recommended, especially between stock and CM/AOSP ROMs. Make sure you also flash other possibly applicable components (depends on the ROM and your preferences) -- gapps, kernel, etc. See if it works that way. I just don't see any reason to use 3rd-party apps for "ROM management" -- the simpler the process, the better.
I'm going to try to put a new rom on the tab tonight without using a program,i have a question though...I have to press power and the up volume or power and the down volume when i flash the new rom
Speedy8311 said:
I'm going to try to put a new rom on the tab tonight without using a program,i have a question though...I have to press power and the up volume or power and the down volume when i flash the new rom
Click to expand...
Click to collapse
Power+Volume up
This is the screen I get....what do I press? I know its a silly question but this IS where I was at and getting the could not find sd card error
Speedy8311 said:
i have a question though...I have to press power and the up volume or power and the down volume when i flash the new rom
Click to expand...
Click to collapse
Speedy8311 said:
This is the screen I get....what do I press? I know its a silly question but this IS where I was at and getting the could not find sd card error
Click to expand...
Click to collapse
You are in recovery... To get to download mode on P31xx for using Odin you need to press and hold Volume DOWN + Power.
ok.....so I need to be in the download mode to download anything including roms and kernels....so I have to use odin to download stuff then?
Speedy8311 said:
ok.....so I need to be in the download mode to download anything including roms and kernels....so I have to use odin to download stuff then?
Click to expand...
Click to collapse
I think you need to do some research.
http://forum.xda-developers.com/showthread.php?t=1900055
Speedy8311 said:
ok.....so I need to be in the download mode to download anything including roms and kernels....so I have to use odin to download stuff then?
Click to expand...
Click to collapse
Man, that sounds scary! You really need to do some reading on the basics, before you screw something up.
You can flash ZIP files from recovery, including ROMs, kernels, recoveries, and apps. However, you need Odin, a PC connection, and a download mode on your tab in order to flash things like official ROM packages (typically in tar.md5 format).
If you want to flash the ROM in zip format, you can do that in recovery. In general, if you have problems doing that, your other option is Odin and a stock ROM; then you can start over.
Looking closely at your photo, you have a stock recovery. You can only flash signed zips from it, which means you won't be able to flash custom ROMs or kernels. I would suggest to start with flashing a custom recovery (look up PhilZ Touch CWM, it's the best). This will make things easier for you.
P.S.: Sorry, didn't mean to sound harsh... It seems things got a bit confusing in the process, so questions and answers didn't really line up...
well ....I have been doin a lot of research,maybe too much lol....but the only thing I can get outta all of it is that to flash a kernel or rom or both I need to go into recovery(power and up volume) and do a wipe of the cashe and install.....then it seems to trail off there with a ok now your done go enjoy....
I cant seem to find any kinda description of what happens in between the wiping of the cashe/devlick and the install...I keep ending up in the recovey section wheather I use rom manager rom toolbox or just me following directions. I will say this though.....I do not see the cwm logo in the recovery....I stiil have the android and he lays there dead then does a quick flash to an error message then I get the menu....but there is no "mount and storage" and "backup and restore" option for me to choose from I put the tab into recovery mode and took a picture....its in the previous post.
I am still using the stock rom and kernel btw....Im not sure if I have mentioned that. I havnt been able to flash anything.
Speedy8311 said:
I am still using the stock rom and kernel btw....Im not sure if I have mentioned that. I havnt been able to flash anything.
Click to expand...
Click to collapse
Yeah, I got that. Sorry for the confusion! I updated my previous post, take a look. Stock recovery seems to be your problem here.
No harm done lol I appreciate all the help.....I'm a bit new at this,but I learn quick. Ok....I may be putting CWM or pfilze wrong way on my tab I loaded it from the play store,along but when I rooted tab I'm 99% positive that I installed CWM also . when I plug it into the computer I can see a clockwork folder.do I neeed to use odin to install philz?
is there a specific PhilZ Touch for the tab 2? or can I just download it to the computer and send it to my tab via odin?
Speedy8311 said:
when I rooted tab I'm 99% positive that I installed CWM also . when I plug it into the computer I can see a clockwork folder.do I neeed to use odin to install philz?
Click to expand...
Click to collapse
Not sure exactly what and how you did previously, but the fact is that you've got a stock recovery now. You need a custom recovery - it doesn't have to be PhilZ, even though I strongly recommend it. You can install standard CWM, too, no problem with that. To install PhilZ, you either need CWM to be already installed, or you need to use Odin.
For details and install instructions on PhilZ CWM, look here:
http://forum.xda-developers.com/showthread.php?t=2202667
Oh, BTW, as an alternative to Odin, look up the Mobile Odin by Chainfire on Play Store. It allows you to flash Odin packages from your device directly. Very useful tool! Free version will do, but the paid one has more features.
Speedy8311 said:
is there a specific PhilZ Touch for the tab 2? or can I just download it to the computer and send it to my tab via odin?
Click to expand...
Click to collapse
Yes, there is. Look in the thread I linked above.
Yep.....i got it stuck in forever boot using mobile odin.... Uugggh....I'm gonna return everything to stock and re-root it.....what ever I did the first time rooting and installing cwm I must a missed a step or something. I'll repost my progress when I'm back to stock and rooted properly
MERRY CHRISTMAS EVERYONE!!!!
YAY!!! Merry Christmas to me!!! I unrooted and repaired my tab 2 7.0 . I also re-rooted it and installed philztouch and everything is installed properly this time. Funny thing though.....after I got the tab working and before I re-rooted it...I tried to do the factory update to 4.2.2 ,since now I'm only on 4.1.1,it said that I had the latest updates available and my apps and phone list didn't auto load like when I first got my tab....hhhmmmm...anyways it works now and all root stuff and twrp is properly :highfive::highfive: only one more question...now that TWRP is working....when I want to download a kernel or rom do I leave it in Zipped form when I put it on the tab and the tab unzips it and flashs it or do I unzip it? .....sorry for all the basic questions but ya cant learn unless you ask questions
Thanks for every ones help with my Tab 2!!!
Speedy8311 said:
YAY!!! Merry Christmas to me!!! I unrooted and repaired my tab 2 7.0 .
Click to expand...
Click to collapse
Well, congrats, and merry Christmas! A bit confused - are you using PhilZ CWM, or TWRP?
As for zip files, leave them as they are, don't unzip - the recovery will install them. Just a suggestion - whenever possible, especially for large files like complete ROMs, verify the MD5 checksum to make sure your file is not corrupt during download.
just went into recovery and it says Philz touch 6