Related
I have saved myself from many weird bricks.. but I have never Had anything like this happen. So I wanted to get darkys rom 10 on my phone so I opened it up and replaced some files with ones that I stole from the edt gingerbread rom, but then I remembered that I had to flash some i9k thing from Odin for the bootloaders
So I stupidly i did, and. The flash failed. so then I decided to Flash just the bootloaders (I'm useing heimdall so I could do that) and then I would flash a vibrant kernel and install darkys rom from recovery so. Flashed the bootloaders, and it rebooted showing the i9000 splash screen an didn't even who the vibrant one! And the weird part is that I can still boot into the on I was using before (edt gingerbread) and it works fine. BUT I cat get into download mode using 3 buttons only using reboot download command
So here Is my question, should I flash back to stock vibrant software useing reboot download command or should I leave it as it is and stop flashing (that would be sad) because if I brick my phone I can't get into download mode?
Thanks
UPDATE: I can reboot into recovery and I see it I dont need to use android screencast
Download mode is 2 buttons plus use cable.
Sent from my SGH-T959 using XDA App
bbm21 said:
I have saved myself from many weird bricks.. but I have never Had anything like this happen. So I wanted to get darkys rom 10 on my phone so I opened it up and replaced some files with ones that I stole from the edt gingerbread rom, but then I remembered that I had to flash some i9k thing from Odin for the bootloaders
So I stupidly i did, and. The flash failed. so then I decided to Flash just the bootloaders (I'm useing heimdall so I could do that) and then I would flash a vibrant kernel and install darkys rom from recovery so. Flashed the bootloaders, and it rebooted showing the i9000 splash screen an didn't even who the vibrant one! And the weird part is that I can still boot into the on I was using before (edt gingerbread) and it works fine. BUT I cat get into download mode using 3 buttons only using reboot download command
So here Is my question, should I flash back to stock vibrant software useing reboot download command or should I leave it as it is and stop flashing (that would be sad) because if I brick my phone I can't get into download mode?
Thanks
UPDATE: I can reboot into recovery and I see it I dont need to use android screencast
Click to expand...
Click to collapse
Odin back to stock and start over. Try using the toolbox
http://forum.xda-developers.com/showthread.php?t=954509
But If I g back to Eyck bandit fails am I screwed cuz I can't go inorganic download mode?
Sent from my GT-I9000 using XDA App
Download mode: vol+ and vol- at the same time and then usb cable. There is no 3 button combo to get into download mode
Sent from my SGH-T959 using XDA App
Ya that's what I did I meant 3 buttons for When you turn it off
Sent from my GT-I9000 using XDA App
did you do the remove battery method? or no?
If you didn't, say you didn't, and i'll list instructions on how to do so.
If you can't get into Download mode, idk how you'll be able to get to stock, without flashing other roms or something?
So j was trying to get it to where it had gingerbread and lockscreen mods on it now its on eclair and has 2 bootloaders on it , its on 2.1 update 1 baseband t959uvjfd and kernal 2.6.29 this was awhile ago now and I remember I was trying to install gingerbread and I got an error on startup that said something like creating system partition , not enough space for partition , and the background was bullets or something ... I REALLY NEED SOMEONE WHOSE HAD THIS PHONE FOR AWHILD TO HELP WITH DIRECTIONS TO FIX MY GIRLS PHONE its on eclair now anc runs like **** , it freezes and just runs bad , I think im experienced with odin and flashing , ive made themes for my old epic 4g and my new galaxy 2 but when I picked up her phone and looked around I was lost ... I hope someone can help me
Sent from my SPH-D710 using xda premium
Digglez said:
So j was trying to get it to where it had gingerbread and lockscreen mods on it now its on eclair and has 2 bootloaders on it , its on 2.1 update 1 baseband t959uvjfd and kernal 2.6.29 this was awhile ago now and I remember I was trying to install gingerbread and I got an error on startup that said something like creating system partition , not enough space for partition , and the background was bullets or something ... I REALLY NEED SOMEONE WHOSE HAD THIS PHONE FOR AWHILD TO HELP WITH DIRECTIONS TO FIX MY GIRLS PHONE its on eclair now anc runs like **** , it freezes and just runs bad , I think im experienced with odin and flashing , ive made themes for my old epic 4g and my new galaxy 2 but when I picked up her phone and looked around I was lost ... I hope someone can help me
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I assume thet the phone is rooted. You should flash a 2.2 Rom from the vibrant forum first. Bionix, Trigger etc. Once you flash a 2.2 froyo rom, it should be smooth. I like Zendroid located here
http://forum.xda-developers.com/showthread.php?t=1079517
If you can get into CWM you should be golden ..good luck
Haha Lapdog hit the Thanks instead of the Quote.
Ok then. Here us what you can do. Hit my signature and download CWR. Open the folder and put the Update.zip on her internal SD. Go here and download this ROM (Derange9). Put it on her internal SDcard.
Boot into recovery (either volume up AND down and power OR volume up + power [depending on whatever bootloader you have]). It will show up Blue.
Tab down to Reinstall Packages and hit it. It will cycle through and come back to the blue screen. Hit Reinstall Packages again and the recovery will go from blue (stock) to green (CWR).
Scroll down to Wipe cache, factory reset/data and advanced->wipe Dalvik. Then scroll to Install from SD and find the above ROM and flash it.
Once done Reboot and profit, you are on Deranged9. If you want to flash a different ROM, just replace D9 with whatever one you want. After it boots up and she is no longer pissed at you, you should get some kisses. Tell er' Wood sent you.
really she wants it to just be stock , it was ten times smoother when i got it then after i tried to put the lockscreens on it , is there any way i can get rid of the 2 bootloaders and just have one and have it be all stock
Try Odin if u want it back dtock
Sent from my SGH-T959 using XDA App
If you just want to Odin to the latest stock, it appears to be KB5:
http://www.google.com/search?hl=en&sky=mrdr&q=t959uvkb5&oq=t959uvk&aq=1&aqi=s1g4&aql=&gs_sm=c&gs_upl=2935l15089l0l18525l11l10l0l1l1l0l531l1319l0.6.5-1l9l0&mvs=0
That doesnt solve my dual bootloader problem though
Sent from my SPH-D710 using xda premium
I don't know what you mean by dual bootloader. You might want to Odin back to the froyo bootloader before installing a stock rom.
i mean when it first turns on you see it go through 2 bootloaders the froyo one and the gingerbread one First is Galaxy S i9000 logo , then Vibrant logo, finally is T-mobile bootscreen.
i would like to get it back to how it was where it only says the vibrant logo when loading then i would like to odin it to the most rexent stock version
like if i hook it up to samsung kies for vibrant that will fix it right ?
At least two of the recent hard-brickings I've read about recently have involved Kies. I wouldn't touch it. Odin or Heimdall for me.
Info about kb5:
http://duckduckgo.com/?q=t959uvkb5
I'm a little concerned about your initial "i9000". If there is any possibility you changed the SBL, you might want to Odin back to a stock Froyo SBL before loading kb5. Do it in the same session: uncheck "reboot" in Odin before loading the SBL, then after it loads, load kb5. Probably the initial "i9000" just means you somehow got an i9000 kernel.
I think you need to go back to odin3 flash the stock jfd to stock then go in phone dailer press *2767*3855# to format the system to wipe out the old folder then go back to odin3 again and flash the VIBRANT STOCK (FROYO) BOOTLOADER. I hope that help. I did have 2 bootloader like seeing i9000 and the Vibrant logo before
bootloader
http://forum.xda-developers.com/showthread.php?t=1117990
Sbl and jdf , no comprendas , I get most of what your saying just not those terms , and whats odin3 I know what odin is just never heard of odin3 unless thats the version
Sent from my SPH-D710 using xda premium
Dude quit asking redundant questions about the help and just read a guide on Odin, know How to use it and fix the phone.
You shouldnt be flashing if you can't get back to stock.
Sent from my SGH-T959 using XDA App
ok im assuming sbl is samsung boot loader but like i said in the beginning i dont have a vibrant , i was just trying to help my girl deck out her phone , you can catch me in the og epic or the epic touch threads and im pretty much on the ball there and im pretty well versed in using odin to get MY phone back to stock . as for redundant questions ... i dont really see where i asked any ? i just know last time i started messing with my girls phone it went all bad so i guess i was just trying to make sure i understood what people were talking about ... also i guess i could have just googled odin3 (which i just did and im pretty sure i got the idea of it) but i was on the go and had really horrible service , its the Q&A section so i guess dont read it if you dont wanna hear people asking question
Use the AIO Vibrant toolbox 2.5
http://forum.xda-developers.com/showthread.php?t=954509
Kies won't fix anything. If you don't have much experience, use Heimdall One-Click. http://forum.xda-developers.com/showthread.php?t=1278683
It will flash the stock bootloaders and the stock Vibrant ROM. It will be back to the way it was when you (or she) first got it.
Note: It won't let you flash bootloaders until you've flashed it once, so just reflash it with bootloaders checked. If it fails, just keep doing it. It will flash it eventually. I used this when I bricked my Vibrant.
I have tmobile's vibrant t959 and I had Nero w/voodoo on there and all I did was odin back to stock because I wanted to get ICS on the phone. well I knew I had a problem before I had dropped my phone and the service cut out it doesnt do anything since then but bootloop unless I have a ROM on there then it works PERFECTLY fine, So I assume it's an internal issue? Well I had used odin to go back to stock and the terrible bootloop started again. I tried to install a new rom after i installed the update.zip file but it WILL not go into clockwork recovery. The other day when I put Nero on there I didn't need rom manager or ANYTHING it was completely stock and all I did was do update.zip through install packages and then it brought me right to the Clockwork screen. Now after I hit install packages it just reboots to the loading screen and starts up the phone..then bootloops. I'm not too sure what to do I've installed every odin 1.7 1.3 everything every single JDF and pit file I can possibly find nothing works. I can't get into clockwork even though I have superuser and all that can anyone PLEASE give me some kind of advice? I just can't figure out how i got it to work the other day.. but I know it will work. Also I did put some kind of....clockwork thing through odin? brought me to a red clockwork but when I go to install the rom it doesn't so my SD Card just my internal phone one and I even tried putting the rom on there but it doesnt show up...Mind you I can't keep the phone on for very long before it restarts...maybe if i'm lucky i can put osmething on the SD card...I also have been using my other phone to put things onthe SD card then put the SD card back into my vibrant..please someone help I want to let my boyfriend use the phone.. I'm starting to feel like I should have just left Nero on there and never tried to put ICS on there...
You try the nobrick PDA tar first?
Sent from my SGH-T959 using xda premium
Remove your SD and power, when u flash
Sent from my SGH-T959 using xda premium
Also did you try to check reparatition , when you flashed??
Sent from my SGH-T959 using xda premium
I literally tried everything you know what I just got it to work by odin. PIt and tar and then another tar.md5 file in PHONE and it workeD! I'm not sure how or why but i'm really even more confused now LOL
okay so now when i try to put roms on it just says installation aborted.... so...i dont know what else to do.... Maybe it was how i did the odin thing? but i do odin any other way and i get bootloops?
Md5.tar?
Sent from my SGH-T959 using xda premium
512.pit and ur supposed be using
T959UVJFD.tar
Sent from my SGH-T959 using xda premium
You have to root it after you used Odin. You can't flash custom roms without that and custom recovery. Follow the sticky guides.
Sent from samsung Vibrant
I am completely and fully aware that I have to root after i use odin......LOL i've been rooting and using roms for the last two years I just am currently having this problem...yeah it was a md5 tar and the pit and then the jfd tar. i dont know where i found it but now i cant apply roms. I dont know if i odin back with just the pit and jfd tar then i get a bootloop....and i know what i'm suppose to be using. i do understand how to do it that's not the problem at all so no I don't need to follow the stickys.. it's the fact that when I do it RIGHT i get the bootloop.
BeautifulTrauma said:
I am completely and fully aware that I have to root after i use odin......LOL i've been rooting and using roms for the last two years I just am currently having this problem...yeah it was a md5 tar and the pit and then the jfd tar. i dont know where i found it but now i cant apply roms. I dont know if i odin back with just the pit and jfd tar then i get a bootloop....and i know what i'm suppose to be using. i do understand how to do it that's not the problem at all so no I don't need to follow the stickys.. it's the fact that when I do it RIGHT i get the bootloop.
Click to expand...
Click to collapse
Try this, and please do it even if you already have.
Delete any update.zip you have on your sdcard and put this one on your internal sdcard. http://db.tt/5FWb4wT8
Odin jfd w/ repartition clicked (must be jfd, not ji4/5/6 or anything else).
No, boot into recovery, select "real install packages". And then the phone will reboot back to recovery. Select it again.
Now you *should* be able to install the rom you want, assuming you have a vibrant 3g (t959) and not a galaxy s 4g (t959v) or a t959d.
Also, what's the error number you are given when the flash fails?
Sent from my Sensation using Tapatalk 2
Alright thank you i'm trying all this now and I'll let you know what happens. I'm just a little nervous because whenever i odin back to stock without doing it the other way I get the bootloop from hell. hopefully it doesn't happen.... The error that appears is error in sd/romname installation aborted. that's all it says.
Alright well I did odin, the same way I always do it. This time without the tar.md5 file just the regular JFD. This is such a pain in the butt with no service connection...even through wifi I cannot use the market so anything i need i have to download the APK until I get this rom working. -.- OH BAM! ur update.zip worked! butttt roms still are aborted and i'm back into a bootloop.
wait a minute...can I not go directly to ICS or any other rom if i'm coming from stock?...I barely remember not being able to do that....okay so i tried putting cm7 on there and same thing... installing:sdcard:update-cm-7ect.zip finding update package opening update package installing update checking state of BMLMTD assert failed:run_program("/tmp/updater.sh") == 0 e?:error in sdcard/update-cm-7.1.01-vibrant-sig-ned. (1).zip status 7 installation aborted.......wtf D: i am about to give up... i dont know how I had nero w/voodoo on here... i know i odin back to stock then through clockwork installed the zip.. i tried to get nero back but the website is gone and no other downloads for nero are anywhere...
My phone wont boot now.
It stays stuck at the 2nd Samsung during the boot up.
What happen was I updated today to offical ICS from my rooted gingerbread.
I updated via kias today to get official ICS, got it working and I noticed I didn't have cwm install anymore, so I followed this http://forum.xda-developers.com/showthread.php?t=1504218
It is pass it did it reboot thing, and never got past the 2nd "samsung" loading screen.
Anyone know how to get my phone booting again?
Flash the latest ICS kernel
I am not sure how to do that without cwm.
Before I updated to ICS when I press power + up down, it booted into CWM. Now when I do that I boots into Android System Recovery <3e>
EDIT: Good news.
Got CWM through installed though odin and then I restored to my gingerbread backup I made earlier.
Flash your roms via clockwork recovery mod from now on.
Drop the ROM .zip on sd card and then enter recovery. Wipe everything three times each then flash a uclf6 based ROM. Never touch Odin or kies again. Be happy. Ice cream sandwich is way better than ginger bread
Sent from my SAMSUNG-SGH-I717 using xda premium
Had the same exact problem. I "believe" the problem was that the CWM I flashed was perhaps incompatible with the official ICS?
I used Odin to flash cwm 5.5.0.4 as suggested and the fone was shut down with the hanging Samsung screen as you mentioned. I used the DL screen with Odin to the 600mb Team Objection ROM, which at least got me up and running again. I found out that CWM did in fact flash once the ROM was compatible with it. Updated CWM, then to finally get full stability, I had to do a factory reset after clearing both caches, then install the CM9 official.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Update: I installed official ICS again last night, looks like I lost my root and CWM.
I don't want to mess anything up again, so could you tell me exactly what CWM file you used to flash so it doesn't hang at samsung again?
I was having the same problems but I think I was doing it wrong. How are you flashing the root files? I upgraded from Kies, then used Odin to flash cwm touch (5.5.0.4 I think), make sure to let the reboot and that it's actually turned on and you can see your homescreen. Once you do that, THEN flash the superuser 3.0.7 in cwm. Let the phone reboot properly and it should be okay.
I was doing the same without the reboots and that's what caused me to hang at the logo, but after the above it worked well. Give it a try. For anyone who needs to flash the T-Mobile radios also let the phone reboot and then flash it because I was having issues with that which was fixed by letting the phone reboot.
Make nandroids at every step in case it does hang so you can just restore and try again instead of flashing everything all over again.
Sent from my SGH-I717R using xda app-developers app
I've also tried rooting my AT&T Galaxy Note I717 which had recently upgraded to ICS via AT&T/Kies and my phone is stuck at the Samsung boot screen. While I'm no expert with rooting phones, I had no problem rooting it when it had GB installed so I figured I wouldn't have any problems rooting it again. Is flashing the ICS kernel the best way to fix this? Where do I get the ICS kernel from and how do I flash it?
Details: After my phone upgraded to ICS 4.0.4 kernel 3.0.8 (IMM76D.UCLF6), I followed some instructions to root it using Odin3-v1.85 and PDA->pda.tar. Other instructions used cwm-touch-i717-120414.tar.md5 and odin_n1717_cwm_recovery_b4.tar and I tried those but to no avail. So I have CWM v5.5.0.4 installed but I don't know what to do next.
Any help is greatly appreciated. Thanks!
dcdtrax said:
I've also tried rooting my AT&T Galaxy Note I717 which had recently upgraded to ICS via AT&T/Kies and my phone is stuck at the Samsung boot screen. While I'm no expert with rooting phones, I had no problem rooting it when it had GB installed so I figured I wouldn't have any problems rooting it again. Is flashing the ICS kernel the best way to fix this? Where do I get the ICS kernel from and how do I flash it?
Details: After my phone upgraded to ICS 4.0.4 kernel 3.0.8 (IMM76D.UCLF6), I followed some instructions to root it using Odin3-v1.85 and PDA->pda.tar. Other instructions used cwm-touch-i717-120414.tar.md5 and odin_n1717_cwm_recovery_b4.tar and I tried those but to no avail. So I have CWM v5.5.0.4 installed but I don't know what to do next.
Any help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
Update: I restored my phone back to a non-rooted working Android 4.0.4 by downloading the stock ROM for my phone (I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5) and uploading it using Odin3-v1.85/PDA. I didn't even lose any of my settings or data. Now I need to figure out how to successfully root it. But at least I'm not worried about getting stuck on the Samsung screen anymore.
Open odin , PDA cwm file, Droid in dl mode, plug in start unplug, reboot, go to cwm recovery mode and backup onto sd card.
Im learning more, as i soft bricked mine last time
dcdtrax said:
Update: I restored my phone back to a non-rooted working Android 4.0.4 by downloading the stock ROM for my phone (I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5) and uploading it using Odin3-v1.85/PDA. I didn't even lose any of my settings or data. Now I need to figure out how to successfully root it. But at least I'm not worried about getting stuck on the Samsung screen anymore.
Click to expand...
Click to collapse
Odin....to get touch cwm, then download the super user zip and flash it, you will have root....
All can be found in "My links" see it in red...go to GNote page....
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
what about su binaries
Can i put both on my sd card and put it in my phone, cmw recovery and install from there?
liftedzuki said:
what about su binaries
Can i put both on my sd card and put it in my phone, cmw recovery and install from there?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1740367
ok look for the green arrow...and use those threads....to root...k
odin for touch cwm
flash super user
your rooted
You realize the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Rooted.
erad1 said:
You realize you the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
so correct...you nailed it...so many are trying to root with gb kernal....
I hope they go to the page I made and follow the green arrowed how to root ics...it is very super simple process to root the official ics...but ....
This happened to me after misreading a comment.
If you put your phone into download mode, plug it in, run kies, and do an emergency firmware recovery. You'll need the serial number. My phone is stock ICS again. Works fine.
erad1 said:
You realize the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
so cwm 5.5.0.4 touch is a GB kernel? Because that's all I flashed after the KIES update to ICS and I got the hanging Samsung logo.
I believe some people are trying to get ICS rooted with this cwm and are getting stuck. Of course there are ways out of it, but it'll help the learning process if we can find the problem.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
romeojunior said:
so cwm 5.5.0.4 touch is a GB kernel? Because that's all I flashed after the KIES update to ICS and I got the hanging Samsung logo.
I believe some people are trying to get ICS rooted with this cwm and are getting stuck. Of course there are ways out of it, but it'll help the learning process if we can find the problem.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Wait what??!!??!!
you need to read read read read and PLEASE read
Because CMW is not a kernel
Its a recovery
People wouldn't have these issues if they read.
Please refer to the stickies before you really damage your phone.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
The OP had posted that he flashed Da_g's GB kernel trying to get root...your issue if flashing CWM may be different. Hopefully you use the steps outlined by bigjoe in his post.
Sent from my SAMSUNG-SGH-I717 using xda premium
Here goes, hopefully someone can help!
Ive installed a fair few roms on my phone and never had any issue, maybe this explains the complacency.
After updating to CWM recovery -6.0.4.7 I get stuck on my bootscreen, only seeing "Samsung galaxy I9100P" , ive been putting I9100 roms on it and losing NFC functionality for a while.
I went to update to the newest CM-11 nightly and read I needed to update CWM-recovery first. So did that, rebooted phone as instructed after installing new CWMr and nothing. Just stuck on I9100 screen.
No way to get into recovery mode, the only bright side I have found is I can boot into ODIN download mode. So what would be my next steps anyone?
Flash stock rom. or flash a kernel to get a working recovery bk with odin.
Sent from my GT-I9300 using xda premium
andrewwright said:
Flash stock rom. or flash a kernel to get a working recovery bk with odin.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
From a dig through the forums it sounds like NAND rw corruption?
I wouldn't be calling it that just yet. Unless you'd like to pay for a motherboard replacement ? Most of these are recoverable.
Used ODIN and flashed a new kernel, still on the boot screen, except now I have the yellow exclamation mark. Now to, Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.. this day is not going well..
Fingers crossed, flashed 3 or 4 kernels before one worked and allowed me into recovery mode. Trying to restore back to my backup from this morning. Heres hoping! :good:
Worked perfectly, the first thing I did was retry the initial task which was what got me stuck, currently waiting on CM-11's initial boot up after a successful install Thanks for the calming responses!