Title says it all I'm having an issue booting into recovery. I went back to stock to get the o.t.a. 4.4.4 I got back to stock my status was official but something went wrong. I downloaded the o.t.a but when i try to install it stops at 27 percent and re boots I can boot into system, download mode fine. But there's no way to get into recovery. I tried flashing stock and philz. . That's the short of it if any has any suggestions let me know. Phone is working just no recovery. I did a search on this issue but never found a fix of any kind.
Goat1378 said:
Title says it all I'm having an issue booting into recovery. I went back to stock to get the o.t.a. 4.4.4 I got back to stock my status was official but something went wrong. I downloaded the o.t.a but when i try to install it stops at 27 percent and re boots I can boot into system, download mode fine. But there's no way to get into recovery. I tried flashing stock and philz. . That's the short of it if any has any suggestions let me know. Phone is working just no recovery. I did a search on this issue but never found a fix of any kind.
Click to expand...
Click to collapse
Hi bud, you are no stranger to flashing !!! Don't know if I can help. Sounds like something isn't sticking on the flash back to stock. This could be if you have an ext sd card or maybe the internal sd card, sometimes the settings that are stored on one of cards keeps getting pushed back on the device. Hence, something was lost when you went back to stock. It's just theory.
Here is what I would try. If you have a ext sd card, and you don't want to erase it, just remove it from the device. Now you know the routine flash a clean fresh copy of NC5 with odin. Or go to micmars post here http://forum.xda-developers.com/showthread.php?t=2712205 and get a copy of NH7 or you can go to Sammoblie here is the link http://www.sammobile.com/firmwares/3/?download=35283 and get the NH7, XAS, CSC copy which eliminates the yellow Sprint logo. ( I run 4.4.2 NC5 XAS stock, rooted, and Philz CWM v16.12.9 )
After you get the stock rom flashed, boot up let it settle down, and do a factory reset. Now try and odin a new recovery. May I suggest Philz CWM hltespr v 6.12.9 I know it's not the latest, but it's the most stable recovery I have used. Trust me I beat that recovery to death every day.
If you get back into recovery great !!! Now get a root file manager like root explorer and delete your delvik cache. Completely power down the device install the sd card and boot it up. Hopefully it will rebuild the delvike cache on the device and sd card on boot up. I run a 32gb class 10
sd card and every once in awhile I format/erase it just for sport. Let me know how it goes ?
jimzweb1 said:
Hi bud, you are no stranger to flashing !!! Don't know if I can help. Sounds like something isn't sticking on the flash back to stock. This could be if you have an ext sd card or maybe the internal sd card, sometimes the settings that are stored on one of cards keeps getting pushed back on the device. Hence, something was lost when you went back to stock. It's just theory.
Here is what I would try. If you have a ext sd card, and you don't want to erase it, just remove it from the device. Now you know the routine flash a clean fresh copy of NC5 with odin. Or go to micmars post here http://forum.xda-developers.com/showthread.php?t=2712205 and get a copy of NH7 or you can go to Sammoblie here is the link http://www.sammobile.com/firmwares/3/?download=35283 and get the NH7, XAS, CSC copy which eliminates the yellow Sprint logo. ( I run 4.4.2 NC5 XAS stock, rooted, and Philz CWM v16.12.9 )
After you get the stock rom flashed, boot up let it settle down, and do a factory reset. Now try and odin a new recovery. May I suggest Philz CWM hltespr v 6.12.9 I know it's not the latest, but it's the most stable recovery I have used. Trust me I beat that recovery to death every day.
If you get back into recovery great !!! Now get a root file manager like root explorer and delete your delvik cache. Completely power down the device install the sd card and boot it up. Hopefully it will rebuild the delvike cache on the device and sd card on boot up. I run a 32gb class 10
sd card and every once in awhile I format/erase it just for sport. Let me know how it goes ?
Click to expand...
Click to collapse
I'm gonna try your suggestions and keep my fingers crossed. But it will be a few hours I'm at work . I will definitely keep you updated on the progress. Thanks for the tips!!! I've never ran into this problem. It F#@&*.n freaking me out!
Goat1378 said:
I'm gonna try your suggestions and keep my fingers crossed. But it will be a few hours I'm at work . I will definitely keep you updated on the progress. Thanks for the tips!!! I've never ran into this problem. It F#@&*.n freaking me out!
Click to expand...
Click to collapse
I feel your pain the same thing happened me I went back to stock unrooted and took the OTA update to 4.4.4 NH7 did not see anything worth having and my radio signal was less than NC5, other people are complaining that reception on the new Baseband on NH7 sucks. So I did a factory reset figuring it would me back to NC5. Nope stayed at 4.4.4, so I tried to odin flash a fresh copy of NC5, and the device boop looped. ( soft brick ). Check out this link http://forum.xda-developers.com/note-3-sprint/help/4-4-4-download-mode-t2877528 to see what a couple us did to get our phones back from the brink !!!
jimzweb1 said:
I feel your pain the same thing happened me I went back to stock unrooted and took the OTA update to 4.4.4 NH7 did not see anything worth having and my radio signal was less than NC5, other people are complaining that reception on the new Baseband on NH7 sucks. So I did a factory reset figuring it would me back to NC5. Nope stayed at 4.4.4, so I tried to odin flash a fresh copy of NC5, and the device boop looped. ( soft brick ). Check out this link http://forum.xda-developers.com/note-3-sprint/help/4-4-4-download-mode-t2877528 to see what a couple us did to get our phones back from the brink !!!
Click to expand...
Click to collapse
Mind me asking what you used to go back with?
Goat1378 said:
Mind me asking what you used to go back with?
Click to expand...
Click to collapse
If your asking was there a magic pill that got me back to stock, sorry no. On your device, you lost the ability to use your recovery. In my case it boot looped which has happened to several people, another guy said he kept losing his network connection. But in all the cases it occurred getting back, or trying to get back to 4.4.2 from 4.4.4.
Once I got the phone to boot up again, used odin v 1.85 to flash a copy of NC5 that was downloaded from Sammobile it's a XAS copy so I don't have the Sprint logo. I rooted with SuperSu v 1.94 and used Philz CWM v 6.12.9 hltespr.
---------- Post added at 11:51 AM ---------- Previous post was at 11:41 AM ----------
One more thing, can you boot into the stock recovery ? If so, try and do a factory reset from there. Remove ext sd card and try to odin a custom recovery.
UPDATE!!!
jimzweb1 said:
If your asking was there a magic pill that got me back to stock, sorry no. On your device, you lost the ability to use your recovery. In my case it boot looped which has happened to several people, another guy said he kept losing his network connection. But in all the cases it occurred getting back, or trying to get back to 4.4.2 from 4.4.4.
Once I got the phone to boot up again, used odin v 1.85 to flash a copy of NC5 that was downloaded from Sammobile it's a XAS copy so I don't have the Sprint logo. I rooted with SuperSu v 1.94 and used Philz CWM v 6.12.9 hltespr.
---------- Post added at 11:51 AM ---------- Previous post was at 11:41 AM ----------
One more thing, can you boot into the stock recovery ? If so, try and do a factory reset from there. Remove ext sd card and try to odin a custom recovery.
Click to expand...
Click to collapse
The guy over top me saved my a$$!!!!! Yeah that guy! Followed your instructions while removing sd card.. i downloaded the Nc5 full restore one click popped that in the old Odin v3.04. Did the restore,booted into stock recovery and did a full wipe x3,battery pulled, booted back DL mode flashed full restore again then booted into system just to see if everything was good back into DL mode chainfire root,back to system,back to Odin Flashed philz 6.12.9 ,battery pulled for 20sec. popped her back in and did the old 3 button combo into recovery and restored my previous backup.THANK YOU SIR! You are a life saver. I did however lose my TB backups but....WHO CARES! My whole set up is back on.
Goat1378 said:
The guy over top me saved my a$$!!!!! Yeah that guy! Followed your instructions while removing sd card (after i messed things up a bit more) can you say (soft brick) ? After i was done playing god and decided to follow some tips cuz i dont know everything, i downloaded the Nc5 full restore one click popped that in the old Odin v3.04. Did the restore,booted back into system back into DL mode chainfire root,back to system,back to Odin Flashed philz 6.12.9 ,battery pulled for 20sec. popped her back in and did the old 3 button combo into recovery and restored my backup at which point i think i wet my pants and all is well other then having to wash clothes now . THANK YOU SIR! You are a life saver. I did however lose my TB backups but....WHO CARES! My whole set up is back on.
Click to expand...
Click to collapse
Awesome !!! First my bad, should have told you to back up your data to a PC. This is just a theory, but here goes. Did you have Philz latest 6.48.7 one size fits all hlte ? For some reason when you switched from the hlte recovery to the hltespr recovery, things started working again. Now I cannot speak from experience because I have always used that recovery. However, check this thread out post #7 http://forum.xda-developers.com/note-3-sprint/help/using-pac-cm-slim-loose-connection-t2883855 he had the same basic problem.
Did you see where Philz no longer updating his thread !!!
jimzweb1 said:
Awesome !!! First my bad, should have told you to back up your data to a PC. This is just a theory, but here goes. Did you have Philz latest 6.48.7 one size fits all hlte ? For some reason when you switched from the hlte recovery to the hltespr recovery, things started working again. Now I cannot speak from experience because I have always used that recovery. However, check this thread out post #7 http://forum.xda-developers.com/note-3-sprint/help/using-pac-cm-slim-loose-connection-t2883855 he had the same basic problem.
Did you see where Philz no longer updating his thread !!!
Click to expand...
Click to collapse
No I used the 6.12.8 or whatever it was and yes I did see that philz is a dead project which is unfortunate cuz its a very reliable recovery. Apparently has got other ongoing projects and sounds to me like he was tired of people posting bash posts about his product not working properly (just a guess) but guarantee atleast 90 percent of those post was cus of user error not his recovery and now we all suffer. Not cool!!! I do hope his recovery holds for future updates and development . Like my mishap…No boot to recovery was all caused by user error cuz I got lazy not cuz I didnt know better and when $#!+ got bad I didn't come on and bash anyones work. . I'm just glad someone such as yourself hit it from a different point of view and saves my @$$ when I couldn't think clearly. Lesson learned. And Thank you again!!! Hope I can lead a hand someday.
Related
Hi there, I'm panicking right now.
I just rooted my phone using a tutorial online and it was no problem and everything worked fine after that.
Then I used another tutorial to flash my ROM to CM7 and that's when I started to have problems.
I booted into ClockworkMod Recovery (holding volume up + home + power) and wiped data and chache partition, then I select "Install zip from sdcard" and chose CM7 zip file which I had put on to my sd card, I get a message that installation was successful.
But now I can't access my phone, it's stuck at the Samsung Galaxy SII logo.
I have wiped data again and used Odin to flash a stock ROM on to my phone but it doesn't work.
I need help guys.
EDIT: This post doesn't matter now, there is a new reply at page 3 with new problems.
Did you use a .pit file a repartition when you flashed a stock ROM with ODIN again? What do you mean the phone doesn't work? Does it bootloop or still stuck on the startup logo?
Prasad007 said:
Did you use a .pit file a repartition when you flashed a stock ROM with ODIN again? What do you mean the phone doesn't work? Does it bootloop or still stuck on the startup logo?
Click to expand...
Click to collapse
Well the phone did bootloop at one time and I fixed that by flashing a stock ROM on the phone with Odin, did not use a PIT file.
Now the phone is just stuck on the white Galaxy SII logo and I was hoping that flashing the phone again with stock ROM would also fix that.
I did not use a PIT file for that either.
Please reflash with a stock ROM that contains DBDATA and use a .pit file for repartitioning... That should fix your phone!
Prasad007 said:
Please reflash with a stock ROM that contains DBDATA and use a .pit file for repartitioning... That should fix your phone!
Click to expand...
Click to collapse
Yep!
@OP Download this package : http://hotfile.com/dl/130600047/b70801e/I9100XXKI3.rar.html
And then, in ODIN, put :
.PIT -> PIT
CODE -> PDA
MODEM -> PHONE
CSC -> CSC
Toggle repartition, and those 2 standard ticks. DO NOT TICK ANYTHING ELSE.
That WILL fix your phone Bootloops means that you soft bricked it. Flashing a new ROM + PIT always fixes a bootlooped device.
Prasad007 said:
Please reflash with a stock ROM that contains DBDATA and use a .pit file for repartitioning... That should fix your phone!
Click to expand...
Click to collapse
Could you link to a ROM with a .pit file, have not found any. Thanks!
Also, I tried flashing to CM7 again with ClockworkMod Recovery and it now said:
E:Error in /sdcard/cmgs.zip
(Status 7)
Installation aborted
Is that bad?
The amount of bad advice in this thread is shocking.
Do you actually have an I9100?
My first thought from your original post is that you didn't flash twice in succession, and the flash you did do was practically instant.
Regarding your last post, status 7 is usually when you're trying to flash something not meant for your device.
oinkylicious said:
The amount of bad advice in this thread is shocking.
Do you actually have an I9100?
My first thought from your original post is that you didn't flash twice in succession, and the flash you did do was practically instant.
Regarding your last post, status 7 is usually when you're trying to flash something not meant for your device.
Click to expand...
Click to collapse
I have an I9100 and I got the CyanogenMod from the official website where I chose my device.
The first flash was pretty fast yes.
oinkylicious said:
The amount of bad advice in this thread is shocking.
Do you actually have an I9100?
My first thought from your original post is that you didn't flash twice in succession, and the flash you did do was practically instant.
Regarding your last post, status 7 is usually when you're trying to flash something not meant for your device.
Click to expand...
Click to collapse
Wrong.
10 chars.
Phistachio said:
Yep!
@OP Download this package :
And then, in ODIN, put :
.PIT -> PIT
CODE -> PDA
MODEM -> PHONE
CSC -> CSC
Toggle repartition, and those 2 standard ticks. DO NOT TICK ANYTHING ELSE.
That WILL fix your phone Bootloops means that you soft bricked it. Flashing a new ROM + PIT always fixes a bootlooped device.
Click to expand...
Click to collapse
Thanks man! You saved me!
I was seriously going to stay up all night trying to fix this and skip school tomorrow...
But I still want a custom ROM
Is there a better way than booting into ClockworkMod Recovery and installing zip file from sd card?
Also, any idea about why all this would happen to me? I got all the tutorials on an Icelandic forum where a person with the same phone did exactly what I was going to do and it worked perfectly for him, and I have gone over the steps many times, I did not screw up.
How to flash CM7
1) Flash a kernel with CWM, CF-root will do
2) Download CM7 zip and put it in your internalSD card
3) Boot into CWM
4) Flash CM7 zip
5) Reboot into CWM
6) Flash CM7 zip again
7) wipe cache/data/dalvik cache
6) reboot and wait for upto 10min for it to boot.
You HAVE to flash the CM7 zip twice.
Also you NEVER need to use the .pit, also never tick repartition, a bad flash with repartition ticked is a one way street to hardbrick land.
himmip said:
Thanks man! You saved me!
I was seriously going to stay up all night trying to fix this and skip school tomorrow...
But I still want a custom ROM
Is there a better way than booting into ClockworkMod Recovery and installing zip file from sd card?
Also, any idea about why all this would happen to me? I got all the tutorials on an Icelandic forum where a person with the same phone did exactly what I was going to do and it worked perfectly for him, and I have gone over the steps many times, I did not screw up.
Click to expand...
Click to collapse
Ideally, you:
1. Flash a stock ROM via ODIN
2. Flash CF-Root via ODIN
3. Flash a custom ROM such as CM9 via CWM Recovery
Ok thanks guys!
And just to be sure, I went here: http://www.cyanogenmod.com/devices/samsung-galaxy-s2 and was going to download nightly, or is their anything else you would recommend more?
himmip said:
Ok thanks guys!
And just to be sure, I went here: http://www.cyanogenmod.com/devices/samsung-galaxy-s2 and was going to download nightly, or is their anything else you would recommend more?
Click to expand...
Click to collapse
Only this: http://forum.xda-developers.com/showthread.php?t=1410400
Prasad007 said:
Only this: http://forum.xda-developers.com/showthread.php?t=1410400
Click to expand...
Click to collapse
Not sure if I want experimental ROM, I would also like to be able to restore my apps with Titanium Backup
himmip said:
Not sure if I want experimental ROM, I would also like to be able to restore my apps with Titanium Backup
Click to expand...
Click to collapse
The stable build is much older and actually less stable than the newest nightly.
Also you can restore user apps with titanium backup, just not system apps.
himmip said:
Not sure if I want experimental ROM, I would also like to be able to restore my apps with Titanium Backup
Click to expand...
Click to collapse
You can restore non-system apps, just not their data.
Prasad007 said:
Ideally, you:
1. Flash a stock ROM via ODIN
2. Flash CF-Root via ODIN
3. Flash a custom ROM such as CM9 via CWM Recovery
Click to expand...
Click to collapse
My phone is really starting to annoy me now.
I put a stock ROM on the phone and then flashed CF-Root and when I boot up in CWM and select something it just displays the loading sign and then I hit the power button and I'm back on the main menu of CMW, doesn't matter what I select it only displays the loading sign and it doesn't go away.
It really sucks, I had put all the CM9 files on the SDcard and was ready to go.
EDIT: Never mind guys, finally got it to work Thanks for your help!
himmip said:
My phone is really starting to annoy me now.
I put a stock ROM on the phone and then flashed CF-Root and when I boot up in CWM and select something it just displays the loading sign and then I hit the power button and I'm back on the main menu of CMW, doesn't matter what I select it only displays the loading sign and it doesn't go away.
It really sucks, I had put all the CM9 files on the SDcard and was ready to go.
Click to expand...
Click to collapse
If the Home button doesn't work for you, try selecting with the power button once inside CWM Recovery..
Phistachio said:
That WILL fix your phone Bootloops means that you soft bricked it. Flashing a new ROM + PIT always fixes a bootlooped device.
Click to expand...
Click to collapse
seconded...
Don't panic dude, it happens sometimes Keeping cool is the key to fixing your phone without making it worse than it already is... I can't count the times this has happened to me already, and there ain't nuffin like a good 'ole repartitioning to set things straight (and show the damn contraption who's boss around these here parts.. I hate those stupid machines to whom nobody has ever taught that Man's genius INVARIABLY always triumphs over dumb and inert matter.. )
(although I almost never flash the whole ROM back on : most times flashing the .PIT file and rebooting the device does the trick -unless it's an installed app which caused the trouble in the first place, in which case you're better off starting over from scratch than wasting time trying to debug the problem)
N.B : don't forget to flash the "old bootloader" too, AFTER you've flashed the PIT and rebooted the device (or at least rebooted the recovvery, to check that it boots off a valid partition), I've noticed the new one can give a lot of weird and unpredictable behaviors when used in conjunction with root and a CMx ROM.
---------- Post added at 01:36 PM ---------- Previous post was at 01:28 PM ----------
himmip said:
My phone is really starting to annoy me now.
I put a stock ROM on the phone and then flashed CF-Root and when I boot up in CWM and select something it just displays the loading sign and then I hit the power button and I'm back on the main menu of CMW, doesn't matter what I select it only displays the loading sign and it doesn't go away.
It really sucks, I had put all the CM9 files on the SDcard and was ready to go.
EDIT: Never mind guys, finally got it to work Thanks for your help!
Click to expand...
Click to collapse
I was going to ask : have you flashed the CM rom twice, and flashed the google apps pack BEFORE even rebooting the phone ? It's almost always mandatory to do this precise sequence, the installation routine of the CM ROM is not quite perfect -far from it, actually..
Right so here is my thing acouple of days ago i tried to go from a rom based on XLPH to one Based on XLPQ. I did the four wipes however on startup it would go into Kernel Panic Mode. I could not access cwm but could get into dl mode so i flashed cf root XLPH and managed to get back to the original rom i started from. It seems that any XLPQ based rom results in the same outcome of Kernel Panic Mode even siyah.Ive tried to go back to stock to start again but the same thing keeps happening.However as a last resort i flashed an original ota based samsung Build i don't now get the Kernel Panic Mode message but a blank screen and it shuts down I've managed to get into dl mode and get back to my original rom any advice.
djseaneq said:
Right so here is my thing acouple of days ago i tried to go from a rom based on XLPH to one Based on XLPQ. I did the four wipes however on startup it would go into Kernel Panic Mode. I could not access cwm but could get into dl mode so i flashed cf root XLPH and managed to get back to the original rom i started from. It seems that any XLPQ based rom results in the same outcome of Kernel Panic Mode even siyah.Ive tried to go back to stock to start again but the same thing keeps happening.However as a last resort i flashed an original ota based samsung Build i don't now get the Kernel Panic Mode message but a blank screen and it shuts down I've managed to get into dl mode and get back to my original rom any advice.
Click to expand...
Click to collapse
unfortunately.. i having same problem..tired of this..please someone help..
i think it maybe hardware i hope not
Been a few people on my forum with the same problem but I seemed to avoid it.
First I made a nandrord backup and passed it to my PC.Then formatted my internalSD(have all important stuff on external anyway)then passed it back to internalSD again with the new ROM.Formated the phone-System,Data,cache in Mounts and Storage and flashed the official ICS from SamMobile.Rooted booted to recovery and then flashed the ROM on a clean device.After that flashed the CF-PROPER kernel cos the CF-Root kernel has the apps to SD and Titanium restore problems.So far all running smooth.
thanks will try that how do i get a nandroid back up to my pc
guys can i install this new XXLPQ ics update manually??...i heard its for the european phones...im in Malaysia...hope it wont effect my carrier phone calls, sms ad 3G network ~~
how did you reformat through cwm and how did you flash the official ics from sammmobile just glad im not the only one with this problem thought it was my fault.
djseaneq said:
how did you reformat through cwm and how did you flash the official ics from sammmobile just glad im not the only one with this problem thought it was my fault.
Click to expand...
Click to collapse
The basics is a must read before any flashing .
FAQ
http://forum.xda-developers.com/showthread.php?t=1065995
NEW HERE
http://forum.xda-developers.com/showthread.php?t=1134290
bible
http://forum.xda-developers.com/showthread.php?t=1473577
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
sorry should have put it better i just want to know whether her reformatted in cwm or any other way ie kies.
CWM only .
jje
Sorry had to go to bed.It was late in the morning here.
1.have your nandroid and custom ROM on the internalSD.The wont be touched by a format.
2.Boot to recovery and go to Mounts and Storage and format System,Data;Cache
3.Go back and wipe battery stats.Go back and do a Factory reset.
4.Reboot your device.
It wont boot properly cos you have formatted the system so pull the battery,put it back in and boot into download mode.Now flash via Odin the Official LPQ firmware that you can download from SamMobile and root with chainfires CF kernel.Now flash your custom ROM.
Tryed find a full "odin-version" of a XLPQ, including bootloader?
it MUST include XLPQ bootloader for this to work.
I had Kernel panic when I needed go from Omega V4 to v5.
Odin image with same kernel as needed, root it,
then try install youre new rom.
Good luck man
Thanx guys will try later maybe the idea of messing with the bootloader scares me im gonna try cooza method first.
djseaneq said:
Thanx guys will try later maybe the idea of messing with the bootloader scares me im gonna try cooza method first.
Click to expand...
Click to collapse
Do you have the link to the ICS download?
No ill have a looksee later
pit
if after flashing xxlpq it stops at start screen you need to flash rom by ext4 pit in pit section of odin to repartion.
djseaneq said:
No ill have a looksee later
Click to expand...
Click to collapse
this is the Poland one.If you want a different area let me know.
http://hotfile.com/dl/149514867/aea2f22/I9100XXLPQ_I9100OXALPQ_XEO.zip.html
i had this exact problem too
i tried various methods to fix it
in the end i flashed the main stock lpq as pda and also the kernal and modem in odin and it worked.
yeay it worked so far so good thanks cooza you are a legend probably shut put a sticky in the omega rom thread thanks a lot for all your help.
So this is me second Galaxy Note. My first one came with Gingerbread and I had no problems rooting that phone. That phone broke and I got sent a new one because my old phone was still under warranty. So I'm trying to find a way to root this phone and everything I keep seeing on how to root it is the same method that I used on Gingerbread, however, my phone came from AT&T with ICS 4.0.4 pre-isntalled. I didn't think that the old way to root it would work but I can't find anything that doesn't involve loading a custom image so I tried using the pda.tar root method and now my phone is bricked, stuck at the splash screen and it won't turn back on. I can get it back into download mode, but I do not want to put a leaked ICS rom back onto the phone. Call me crazy but I think there are differences between the stock ICS ROM and the leaked versions.
The leaked version is actually where my problems came from on my other phone, after having put that on there AT&T tried forcing an update to my phone while I was talking to tech support about an issue and that thing is completely bricked. According to their guy the leaked version had a different kernel that the stock ICS ROM and that's where the problem came from and why my phone was replaced under warranty.
Does anyone have good news for me on this thing?
Read the root information in the "note everything " thread , and find the big green arrow .
Notes have been added to the root method , and are found there also ...
Read them twice and you'll see the battery pull fix you need ..
The problem you have is a script being loaded after root that won't allow recovery to stick ...
The fix is easy ...just read the info in the notes .....g
I will check that out, thank you!
http://forum.xda-developers.com/showpost.php?p=30824863&postcount=1
And no....your not bricked .....not Even close ....g
This link is the fix ....it's that easy ....
gregsarg said:
http://forum.xda-developers.com/showpost.php?p=30824863&postcount=1
And no....your not bricked .....not Even close ....g
This link is the fix ....it's that easy ....
Click to expand...
Click to collapse
That's of no help... I can't get my phone into any recovery, stock or CWM. Seems like he was using a different rooting method than me. I've only ever loaded the one file pda.tar and what he's looking at seems like it wants to load CWM using Odin? I'm so confused, I'm sorry. Thanks for your help so far.
Root is gained by pushing the recovery in DL mode ...
Then the battery trick after that ....
If no download mode exists .....that's a problem .g
Don't think he has the script issue. That was on Canadian Notes that took the OTA update. He is boot looped from the sounds of it.
Gubment Cheeze
Still have DL mode, I've tried running pda.tar again which gave me CWM. I pulled the battery out, still the same problem.
I guess I could try CM9, is there a stable build on that yet? I know I should probably do the research looking for it, but it has to do with this thread in a way.
If you're boot looped but have recovery and dl mode then you can flash a ROM through recovery or Odin back to stock and start over.
Gubment Cheeze
---------- Post added at 01:54 PM ---------- Previous post was at 01:36 PM ----------
..root and custom recovery are 2 different things completely. If you're just going to flash a ROM then you don't need to root. You just need a custom recovery. If you want to keep your stock ROM and attain root, then you need to flash the su binaries zip in a custom recovery.
Gubment Cheeze
Froid said:
If you're boot looped but have recovery and dl mode then you can flash a ROM through recovery or Odin back to stock and start over.
Click to expand...
Click to collapse
I do not have recovery. Looking for a different ROM to use, my question, do I have to have recovery to get a new ROM installed or can I run that from Odin? Thank
davis.ja said:
Still have DL mode, I've tried running pda.tar again which gave me CWM. I pulled the battery out, still the same problem.
Click to expand...
Click to collapse
OK..so when you said this^^^, you meant what? Can you get into recovery at all? Cwm or stock 3e? If not then you can't flash a ROM. You can use Odin to flash back to stock and start over.
Gubment Cheeze
Froid said:
OK..so when you said this^^^, you meant what? Can you get into recovery at all? Cwm or stock 3e? If not then you can't flash a ROM. You can use Odin to flash back to stock and start over.
Gubment Cheeze
Click to expand...
Click to collapse
I just used Odin to get me back to the stock Gingerbread ROM. Then I ran Odin again to get root on the phone using the pda.tar. Before this gave me CWM. I cannot get my phone into any recovery mode at all, CWM or stock. I went back into Odin and loaded a CWM using PDA and I still can't access a recovery menu.
What happens when you try to flash the cwm tar through Odin? Does it say successful and then reboot your phone? How are you trying to enter cwm recovery?
Gubment Cheeze
---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------
Also, I'm not aware of any Odin root tar that you're talking about. You flash cwm through Odin and then install su binaries zip to attain root.
Gubment Cheeze
I'm confused ...
If you Odin flashed the GB.tar, and it completed successfully, then you "in fact " have a 3e recovery, as it's included in the .tar image .
Volume up, volume down , and power button being pushed together will open this version of recovery.
The restore won't complete without it ....
If you have a working GB rom ....then Odin push the recovery and done ....g
When I try to flash CWM through Odin it all goes as expected till I try to get into recovery. I've pushed and held VLup, VLdn, Pwr and I've tried VLup plus power. The phone does nothing, just vibrates over and over again until I let go and then it shuts off. The phone boots no problem into GB, the problem after that is that the phone still thinks it has some remenance of ICS on it. A whole lot of google processes don't work and it tries telling me that it's still in power save mode that I know for sure isn't in the GB ROM. I can restart the phone and attempt recovery and I still get nothing. I've even tried updating the firmware with Kies and that gets me nowhere either. Even after I've got GB back onto the phone I've tried flashing a couple different CWM from Odin with no better result.
The fact that I'm booting into GB shows that Odin is working. I'll be looking into Odin to see if it will wipe the phone clean without going into recovery. Otherwise I have a worthless device and I have to send in my old phone and I know I can get working again....
Both volume up and down plus power. After first vibration, release power, but continue to hold the volume buttons. If that doesn't work, download an app from the play store like Flapps PowerTool to get into recovery.
Gubment Cheeze
I had a similar issue (stuck on the Samsung logo) the other day when I tried to root ICS. I solved it by entering download mode and flashing one of the leaked ICS ROMS using Odin. Once I had done that, I downloaded the full ATT official ICS ROM and using Kies, updated manually.
Good luck.
That's good advice I'll have to try out and I'll let you guys know what happens. Thank you again!
davis.ja said:
That's good advice I'll have to try out and I'll let you guys know what happens. Thank you again!
Click to expand...
Click to collapse
What will happen, is you will see a recovery called 3e...
and then we can start all over again to root your phone...g....:good:
Ok, I flashed the experimental 4.2.1 update from temasek earlier. flashed his custom kernel. all worked fine.
Told me my SD Card was 'damaged', which I now understand just needed a fix which was provided. However I decided to just forget it and restore my nandroid backup i'd taken the previous night.
Checked the folder was there, which it was, so booted to CWM, did all the wipes and chose "restore". much to my horror, it failed to find any files.
stupid mistake part: i decided to flash the perseus kernel back over the top to see if the CWM would recognise my nandroid files and restore them
the screen just went mad - had blue lines all over the place, the samsung logo jumped about and the screen went off.
i booted back to CWM and found the touchscreen was unresponsive. everything else worked - buttons, CWM. The phone is also recognised in ODIN, so I grabbed the latest stock JB leak and flashed it. it flashed fine, but it was a middle eastern rom, which didn't help, and the touchscreen was still dead.
the PC still recognised it, so i coped the temasek files back on to see if i could re-flash those, which i did, but still no luck with the touchscreen.
flashed the JB leak again with ODIN, which worked. plugged it in to the PC and copied across a nandroid backup folder i'd taken earlier in the evening last night, since the other one seems to not work. rebooted and it still wouldn't find it.
Now i've got the latest stock rom for the uk but ODIN just won't flash anything - the phone is recognised, the MD5 sum on the rom checks out but i always get "Complete(Write) operation failed" error each time. I plug the phone in to the PC, and it recognises it just fine, but KIES is sitting on the "connecting" screen and not doing anything - i've reinstalled the latest drivers as well.
I'm starting to be resigned to the fact i've killed it, but if anyone has any ideas, i'd be hugely grateful - thankyou
touchscreen dead is getting more and more common. Not sure what is going on but if u cant flash anything from odin maybe u have dead mmc chip or something. Hopefully you resolve it or a trip to sammy service centre hopefully can fix under warranty for u
Edit close down all kies software whilst using odin
Sent from my GT-I9300 using XDA Premium HD app
i dont have warranty as the phone was bought second hand.
i'm just on the phone to my insurance providers though for accidental damage ..it might mean i have to drop it downstairs though !
ooeerr .. rebooted my PC, reconnected to ODIN and it's flashing the UK Stock ROM i got .. fingers crossed. I really don't want to have to drop it downstairs. The insurers will want to inspect it and if there's a custom rom on it, it might get bounced
hankhandsome said:
Ok, I flashed the experimental 4.2.1 update from temasek earlier. flashed his custom kernel. all worked fine.
Told me my SD Card was 'damaged', which I now understand just needed a fix which was provided. However I decided to just forget it and restore my nandroid backup i'd taken the previous night.
Checked the folder was there, which it was, so booted to CWM, did all the wipes and chose "restore". much to my horror, it failed to find any files.
stupid mistake part: i decided to flash the perseus kernel back over the top to see if the CWM would recognise my nandroid files and restore them
the screen just went mad - had blue lines all over the place, the samsung logo jumped about and the screen went off.
i booted back to CWM and found the touchscreen was unresponsive. everything else worked - buttons, CWM. The phone is also recognised in ODIN, so I grabbed the latest stock JB leak and flashed it. it flashed fine, but it was a middle eastern rom, which didn't help, and the touchscreen was still dead.
the PC still recognised it, so i coped the temasek files back on to see if i could re-flash those, which i did, but still no luck with the touchscreen.
flashed the JB leak again with ODIN, which worked. plugged it in to the PC and copied across a nandroid backup folder i'd taken earlier in the evening last night, since the other one seems to not work. rebooted and it still wouldn't find it.
Now i've got the latest stock rom for the uk but ODIN just won't flash anything - the phone is recognised, the MD5 sum on the rom checks out but i always get "Complete(Write) operation failed" error each time. I plug the phone in to the PC, and it recognises it just fine, but KIES is sitting on the "connecting" screen and not doing anything - i've reinstalled the latest drivers as well.
I'm starting to be resigned to the fact i've killed it, but if anyone has any ideas, i'd be hugely grateful - thankyou
Click to expand...
Click to collapse
unfortunately your touchscreen died and your only option is to bring it for warranty because of the bad flash, if you have warranty i suggest follow my simple guide here.
http://forum.xda-developers.com/showthread.php?t=2074756
---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------
hankhandsome said:
i dont have warranty as the phone was bought second hand.
i'm just on the phone to my insurance providers though for accidental damage ..it might mean i have to drop it downstairs though !
ooeerr .. rebooted my PC, reconnected to ODIN and it's flashing the UK Stock ROM i got .. fingers crossed. I really don't want to have to drop it downstairs. The insurers will want to inspect it and if there's a custom rom on it, it might get bounced
Click to expand...
Click to collapse
still follow the guide so the insurance will not detect that you have been rooted before
chris151722 said:
still follow the guide so the insurance will not detect that you have been rooted before
Click to expand...
Click to collapse
i'll see what i can do but it's now stuck in a bootloop after flashing the rom i grabbed earlier, so will try another one.
i might have to kill it stone dead if none of this works
each rom i try in ODIN never boots - just goes into a bootloop.
i suppose if the insurers do inspect it, they may well not be able to get to see the flash counter if they can't boot it up - so it'll have a stock, unrooted rom on it anyway, so does anyone think i'll be ok ?
hankhandsome said:
i'll see what i can do but it's now stuck in a bootloop after flashing the rom i grabbed earlier, so will try another one.
i might have to kill it stone dead if none of this works
Click to expand...
Click to collapse
after you flash stock firmware go to recovery try to factory reset
---------- Post added at 02:15 PM ---------- Previous post was at 02:11 PM ----------
Ausboy 2011 said:
touchscreen dead is getting more and more common. Not sure what is going on but if u cant flash anything from odin maybe u have dead mmc chip or something. Hopefully you resolve it or a trip to sammy service centre hopefully can fix under warranty for u
Edit close down all kies software whilst using odin
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
its a bad flash from odin and bad flash thru phone the reason why touch is dying.
chris151722 said:
its a bad flash
Click to expand...
Click to collapse
every rom though ?
just tried another one and it's bootlooping ..
hankhandsome said:
every rom though ?
just tried another one and it's bootlooping ..
Click to expand...
Click to collapse
can you access recovery mode? if so try to wipes or factory reset before and after firmware flash
chris151722 said:
can you access recovery mode? if so try to wipes or factory reset before and after firmware flash
Click to expand...
Click to collapse
at the moment i can't access anything - it just sits at the samsung logo now. CWM is now no longer accessible either - i pop the battery, wait a few minutes then put it back in. I hold down Up/Power/Middle button and the Samsung Logo flashes, but nothing happens.
I can still put it in to download mode and flash roms with odin, but nothing happens .. i think i'm going to have to accept it's dead
My last roll of the dice is to grab one of the earlier roms from this thread
http://forum.xda-developers.com/showthread.php?t=1835931
and see what that does in ODIN
FYI:
1. you don't have to wipe anything before restoring a backup, it doesn't make a difference.
2. insurance fraud is a felony
Glebun said:
FYI: 2. insurance fraud is a felony
Click to expand...
Click to collapse
Good job i don't live in the US then ..
I'm pretty sure it's illegal no matter where you live
Well I don't particularly want to get into an argument here, as i'd much prefer a phone that works so i'll just thank you for your input.
i think you have to solve the bootloop issue first by searching in the forum, im not expert so cant give you better advice on bootloop,
chris151722 said:
i think you have to solve the bootloop issue first by searching in the forum, im not expert so cant give you better advice on bootloop,
Click to expand...
Click to collapse
thanks. it doesn't actually bootloop now, it just sits on the glowing samsung logo and doesn't move.
i just want to get a stock rom back on it and i'm going to just let it go. i'm a bit concerned that on the download screen it says "Custom Binary Download: Yes (19 Counts)". I know I did reset the flash counter not too long ago before I flashed the Darky Rom, so if this is indeed the flash counter, then i've obviously not done something right, so it'll show multiple flashes ..
ok, we've had developments ..
i actually got it in to CWM (don't know how..) and did a factory reset. it then did boot up into the OS but - no touchscreen still.
however, i've just tried connecting it to KIES and it's detected it so i'm going to try the emergency recovery thing ..
he says, as he selects the option and KIES then goes back to "connecting" .. *GROAN* .. and then comes back to tell me it's not supported to upgrade firmware via KIES .. *BIGGER GROAN*
Ok, downloaded and flashed an earlier rom for the UK but still no luck with the screen. Kies won't do any kind of emergency firmware upgrade either so that's that. i'll have to try and get one of those OTG USB dongles so i can get the flash counter reset though ..
hankhandsome said:
Ok, downloaded and flashed an earlier rom for the UK but still no luck with the screen. Kies won't do any kind of emergency firmware upgrade either so that's that. i'll have to try and get one of those OTG USB dongles so i can get the flash counter reset though ..
Click to expand...
Click to collapse
Does not reset flash counter only allows access to download mode. Traingle Away to reset flash counter .
jje
JJEgan said:
Does not reset flash counter only allows access to download mode. Traingle Away to reset flash counter .
jje
Click to expand...
Click to collapse
i'm aware of that - that's why I've ordered the OTG dongle so I can use my desktop mouse to go in and install triangle away
Greeting Devs & thanks in advance.
My t959 got bricked where it wouldn't go passed the vibrant screen, found a post called ** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly ** followed instructions on it to take it back to stock with Odin, rigth now my phone is running Android 2.1 eclair, rooted and with CWM Recovery version 2.5.1.2. im trying to flash a custom rom and when i go into recovery mode and try to do it, the progress bar at the bottom comes up and when it is at about 10% the phone reboots back to the vibrant screen and wont go passed it so i have to take the battery out put it back in and get the phone into download mode to retake it back to stock using ODIN, so i guess is safe to say that my phone gets bricked whenever i try to install a custom rom so im stuck with eclair wich blows specially after having 4.2.2
my phone got bricked the first time when i was trying to update the rom from SlimBean 4.2.2 Build 7 to Build 8 (had done the process many times and never had a problem) did the usual, put the Rom and the Gapps .rar files in the sd card and performed wipe data/ factory reset only this time i went into mounts and storage and wiped everything that was under there as well (dont know why) so when went to flash the rom it was no longer on the sd card (cause i wiped it) so rebooted my phone and it got stuck on the vibrant screen with i fixed already and my problem now is the one mentioned above
i have browsed the different forums and have tried many different methods to try to fix it for example: have brought it back to stock with Odin also with AIO Vibrant Toolbox and even tried UVKB5_Stock_Heimdall-One-Click wich is a froyo 2.2 that comes with CWM recovery with voodoo lag fix and root. even though all these methods work as far as bringing the phone back to stock i still get the same problem when trying to flash a rom, i also have installed CWM through Rom manager and also through the update.zip file i think im doing everything right and have tried multiple forums yet havent been able to find a forum about this specific issue so decided to create this thread as a last resource
this is my first post and id really appreciate any assitance and if any additional information is needed ill be happy to provide it, thanks in advance
This worked for me
elpromo01 said:
Greeting Devs & thanks in advance.
My t959 got bricked where it wouldn't go passed the vibrant screen, found a post called ** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly ** followed instructions on it to take it back to stock with Odin, rigth now my phone is running Android 2.1 eclair, rooted and with CWM Recovery version 2.5.1.2. im trying to flash a custom rom and when i go into recovery mode and try to do it, the progress bar at the bottom comes up and when it is at about 10% the phone reboots back to the vibrant screen and wont go passed it so i have to take the battery out put it back in and get the phone into download mode to retake it back to stock using ODIN, so i guess is safe to say that my phone gets bricked whenever i try to install a custom rom so im stuck with eclair wich blows specially after having 4.2.2
this is my first post and id really appreciate any assitance and if any additional information is needed ill be happy to provide it, thanks in advance
Click to expand...
Click to collapse
Mine would remove the root when I rebooted it not allowing me to install a rom also. I used the Super One Click and the root stuck. I suggest you give it a try.
Super One Click
seerenr since
Devil-Dog said:
Mine would remove the root when I rebooted it not allowing me to install a rom also. I used the Super One Click and the root stuck. I suggest you give it a try.
Super One Click
Click to expand...
Click to collapse
my problem is not really with rooting the phone, it is rooted i just cant flash roms. whenever i try to flash a rom it reboots and gets stuck on the vibrant screen (bricked) so i have to take it back to stock
thanks though
elpromo01 said:
Greeting Devs & thanks in advance.
My t959 got bricked where it wouldn't go passed the vibrant screen, found a post called ** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly ** followed instructions on it to take it back to stock with Odin, rigth now my phone is running Android 2.1 eclair, rooted and with CWM Recovery version 2.5.1.2. im trying to flash a custom rom and when i go into recovery mode and try to do it, the progress bar at the bottom comes up and when it is at about 10% the phone reboots back to the vibrant screen and wont go passed it so i have to take the battery out put it back in and get the phone into download mode to retake it back to stock using ODIN, so i guess is safe to say that my phone gets bricked whenever i try to install a custom rom so im stuck with eclair wich blows specially after having 4.2.2
my phone got bricked the first time when i was trying to update the rom from SlimBean 4.2.2 Build 7 to Build 8 (had done the process many times and never had a problem) did the usual, put the Rom and the Gapps .rar files in the sd card and performed wipe data/ factory reset only this time i went into mounts and storage and wiped everything that was under there as well (dont know why) so when went to flash the rom it was no longer on the sd card (cause i wiped it) so rebooted my phone and it got stuck on the vibrant screen with i fixed already and my problem now is the one mentioned above
i have browsed the different forums and have tried many different methods to try to fix it for example: have brought it back to stock with Odin also with AIO Vibrant Toolbox and even tried UVKB5_Stock_Heimdall-One-Click wich is a froyo 2.2 that comes with CWM recovery with voodoo lag fix and root. even though all these methods work as far as bringing the phone back to stock i still get the same problem when trying to flash a rom, i also have installed CWM through Rom manager and also through the update.zip file i think im doing everything right and have tried multiple forums yet havent been able to find a forum about this specific issue so decided to create this thread as a last resource
this is my first post and id really appreciate any assitance and if any additional information is needed ill be happy to provide it, thanks in advance
Click to expand...
Click to collapse
What version of android are the ROMs you are flashing?
are they above or below android 2.3?
and on the same note, do you know what bootloader you have?
some roms 2.3 and above require gingerbread bootloaders.
(an easy way to find out is by figuring out which button combo you have to use to get to recovery)
you might also try re-flashing recovery.
firefly6240 said:
What version of android are the ROMs you are flashing?
are they above or below android 2.3?
and on the same note, do you know what bootloader you have?
some roms 2.3 and above require gingerbread bootloaders.
(an easy way to find out is by figuring out which button combo you have to use to get to recovery)
you might also try re-flashing recovery.
Click to expand...
Click to collapse
i have re-flashed recovery multiple times i wish there was another type of recovery i could install
on another note im trying to install android 4.2.2 SlimBean and 4.3.3 and i dont know what bootloader i have nor how to check it, id appreciate it if u could show me how to check wich one i have and how to up it
thanks
firefly6240 said:
What version of android are the ROMs you are flashing?
are they above or below android 2.3?
and on the same note, do you know what bootloader you have?
some roms 2.3 and above require gingerbread bootloaders.
(an easy way to find out is by figuring out which button combo you have to use to get to recovery)
you might also try re-flashing recovery.
Click to expand...
Click to collapse
the combo i have to do for recovery is volume up and down and the power button simultaniosly
elpromo01 said:
the combo i have to do for recovery is volume up and down and the power button simultaniosly
Click to expand...
Click to collapse
Try flashing a 2.2 rom or below.
if that works you probably just need to flash GB bootloaders before flashing the 4.2 rom (See Below)
if that doesn't work I wouldn't worry about the step below until we figure out why its not working.
To flash GB bootloaders go here: http://forum.xda-developers.com/showthread.php?t=1117990
firefly6240 said:
Try flashing a 2.2 rom or below.
if that works you probably just need to flash GB bootloaders before flashing the 4.2 rom (See Below)
if that doesn't work I wouldn't worry about the step below until we figure out why its not working.
To flash GB bootloaders go here: http://forum.xda-developers.com/showthread.php?t=1117990
Click to expand...
Click to collapse
ok so i installed GB bootloader following the instructiones as shown in the forum, went ahead an tried to flash Slimbean 4.2.2 build 8 and the same thing happened my phone is stock at the boot screen only different is that instead of the vibrant screen im getting a semaphore screen (i guess is because of the gb bootloader) anyway flashed back to stock using Odin and im back where i started so it doesnt seem to be a bootloader related issue
thanks anyway
elpromo01 said:
ok so i installed GB bootloader following the instructiones as shown in the forum, went ahead an tried to flash Slimbean 4.2.2 build 8 and the same thing happened my phone is stock at the boot screen only different is that instead of the vibrant screen im getting a semaphore screen (i guess is because of the gb bootloader) anyway flashed back to stock using Odin and im back where i started so it doesnt seem to be a bootloader related issue
thanks anyway
Click to expand...
Click to collapse
Flash the rom again instead of going back to stock when it hangs. You have to flash JB roms twice most of the time when you are on stock 2.1, the first flash simply upgrades your recovery mode. Pull the battery after the first flash and boot back into recovery (should be blue now) and flash the rom again.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
Flash the rom again instead of going back to stock when it hangs. You have to flash JB roms twice most of the time when you are on stock 2.1, the first flash simply upgrades your recovery mode. Pull the battery after the first flash and boot back into recovery (should be blue now) and flash the rom again.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
i just fixed, i tried to flash CM10.1 and it crashed during the process only this time instead of getting stuck on the Vibrant screen it rebooted back into the recovery mode wich is now blue and version 6.0.2.1 intead of 2.5.1.2.
im running CM10.1 right now and so far everything looks good :laugh: only thing different now is that it say Galaxy S GT-I9000 and is the t959, doesnt really bother me as long as the phone behaves im just sayin
thanks to everyone that took their time to help, never give up on a Vibrant cause it will never give up on you :good:
elpromo01 said:
i just fixed, i tried to flash CM10.1 and it crashed during the process only this time instead of getting stuck on the Vibrant screen it rebooted back into the recovery mode wich is now blue and version 6.0.2.1 intead of 2.5.1.2.
im running CM10.1 right now and so far everything looks good :laugh: only thing different now is that it say Galaxy S GT-I9000 and is the t959, doesnt really bother me as long as the phone behaves im just sayin
thanks to everyone that took their time to help, never give up on a Vibrant cause it will never give up on you :good:
Click to expand...
Click to collapse
Glad you figured it out. Just so you you know, your phone says GT-I9000 because you flashed gingerbread bootloaders. They provide better button combinations to recovery and download modes, much easier than stock combos.
Sent from my SGH-T959 using Tapatalk 2
Good to know, thanks!!
Sent from my SGH-T959 using xda app-developers app