Related
okay i'll preface this by saying i read all the way through the Vibrick thread and any others i could find on this subject.
i was running NeroV3, decided to try CM7. made a dumb move (apparently?) by restoring back to my stock 2.2 backup via CWM, then flashing to CM7 and THEN trying to flash the Overstock kernel (these steps should be reversed?). i wiped the cache and dalvik cache, but then the kernel flash failed ("installation aborted"), so i rebooted, which went fine. i used ROM Manager to get back to recovery, tried flashing the kernel again, failed again, hit reboot, and then my phone got stuck on the Vibrant screen.
I tried every 3-button combo (also with battery pulls) to get to Download mode but nothing works. when i plug in the USB the spinny-working-hourglass thing pops up but freezes, the green charging bar does not come up, and it does not go to download mode.
when not plugged in, it just keeps returning to the Vibrant screen. i can't even get it to turn off without pulling the battery. i'm definitely not comfortable trying the solder method.
any help is appreciated - i'm not giving it long til i take it to t-mobile and play dumb, worst comes to worst i'll just get a cheapo replacement from the store and find another vibrant (or similar) used on craigslist.
thanks!
UPDATE:::
got the phone into download mode thanks to a thread by Dolphinwigs. had to do have odin open when replacing the battery/holding volume up/down.
waiting on the stock rom download now (internet is slow). hopefully all goes well from here...
The biggest issue I find is that people give up on ODIN to easily. Getting into download mode is not that hard but also not that easy eiither. This is why everyone should purchase a jig, never give up on ODIN try it a thousand times and then once more. Always have ODIN up and ready with the proper files on hand, and as soon as it connects to ODIN be ready to make shyt happen.
In your case an ODIN flash should get you where you need to be and after you root again flashing to CM7 should not be an issue. Keep in mind if you use the .tar in ODIN as well as the .pit you will lose everything on both internal/exteral SD. At this point unless you made a backup prior to your issue its really a lost cost.
Good luck!
i am now back up and running, i just didn't realize i needed Odin running when i tried to go to download mode. so simple, but so frustrating.
one thing though, the ROM i got is Eclair. do i need to update to FroYo before flashing CM7?
and also, so i do it right this time, do i flash the Overstock kernel BEFORE i flash CM7? or does it matter?
Ok...I'm at a point where I had no other choice but to get another replacement. I looked just about everywhere my patience would take me, and decided to give up. I hope someone could/would have a solution for me or others like me.
I had EH03 deoxed rom and decided I wanted ICS build5. So I installed CM7, I whiped cache, DLVK, and system data. Then flashed ICSb5 and GAPPS, Rebooted and stuck on ICS splash screen.
At this point USB ports wouldn't recognize fascinate. Downloaded all Fascinate drivers from Samsung, drivers for Nexus S, ADB, Android SK. You name it I got it. Nothing worked for USB detection. I even followed YT videos on turning Vista/PC off and unplug. Nothing.
After messing with data cords,(numerous ones,trying another PC), PC ports, I happened to pull plug and battery out of Fascinate at the same time, not sure what version of CWM, it was blue, came on. Luckily I had two Nandroid backups on SD.
I flashed Nandroid back to CM7 successfully. Rebooted fine and hooked to USB but still not recognized. At this point I was able to get into recovery using ROM. So, I did something stupid...lol...I tried to flash earliest Nandroid which was performed when on EH03 deoxed. Once I did this, I wiped all needed data and rebooted. Now Fascinate shows Samsung logo. It doesnt reboot, just that the logo stays until I pull battery. Now if I have battery in wth phone off and plug in, the charging battery comes on but doesn't show battery level. Doesn't go away till I pull battery.
The funny thing is that I can get into Download mode but USB is still unrecognized/malfunction on PC/Vista. I only wish that I was able to link phone and PC just to use Odin with PIT file and stock EDO5 or EH03.
Any advice?
dssheeley1 said:
Ok...I'm at a point where I had no other choice but to get another replacement. I looked just about everywhere my patience would take me, and decided to give up. I hope someone could/would have a solution for me or others like me.
I had EH03 deoxed rom and decided I wanted ICS build5. So I installed CM7, I whiped cache, DLVK, and system data. Then flashed ICSb5 and GAPPS, Rebooted and stuck on ICS splash screen.
At this point USB ports wouldn't recognize fascinate. Downloaded all Fascinate drivers from Samsung, drivers for Nexus S, ADB, Android SK. You name it I got it. Nothing worked for USB detection. I even followed YT videos on turning Vista/PC off and unplug. Nothing.
After messing with data cords,(numerous ones,trying another PC), PC ports, I happened to pull plug and battery out of Fascinate at the same time, not sure what version of CWM, it was blue, came on. Luckily I had two Nandroid backups on SD.
I flashed Nandroid back to CM7 successfully. Rebooted fine and hooked to USB but still not recognized. At this point I was able to get into recovery using ROM. So, I did something stupid...lol...I tried to flash earliest Nandroid which was performed when on EH03 deoxed. Once I did this, I wiped all needed data and rebooted. Now Fascinate shows Samsung logo. It doesnt reboot, just that the logo stays until I pull battery. Now if I have battery in wth phone off and plug in, the charging battery comes on but doesn't show battery level. Doesn't go away till I pull battery.
The funny thing is that I can get into Download mode but USB is still unrecognized/malfunction on PC/Vista. I only wish that I was able to link phone and PC just to use Odin with PIT file and stock EDO5 or EH03.
Any advice?
Click to expand...
Click to collapse
In the op of ics and also droidstyles guide you have to flash build 1 before you can flash build 5
Sent from my SCH-I500 using XDA App
I've never flashed version 1 before flashing.build 5. In fact I've had the least amount of problems going back to stock (ED05) then flashing ICS.
I bootlooped when i went from stock EH03 to Build 5 so i did 3 first then 5.
But this doesn't help our poster here.
OP:
you get into DL mode but odin wont see your phone?
What i suggest is to try: Move the usb cable to a different port. see if your pc can see it then. Second thing try a totally different computer. Chances are your PC is trying to use borked up drivers.
Once you get odin going flash a stock image [i recommend eh03] then cwm then build 3 and now the new build 6. good luck!
if you need any links or a more detailed guide I STRONGLY suggest Droidstyles guild, it is by far the best and most up to date for the fassy!
OhioYJ said:
I've never flashed version 1 before flashing.build 5. In fact I've had the least amount of problems going back to stock (ED05) then flashing ICS.
Click to expand...
Click to collapse
Consider yourself lucky....going from stock to build 6 causes me problems and many others. Going from stock, to build 1, then build 6 works flawless.
MOD please close thread due to lapsed timeline and no longer support of this model.Ty
Sent from my SGH-i717/GT-N7005 w/phMOD_beta2
dssheeley1 said:
MOD please close thread due to lapsed timeline and no longer support of this model.Ty
Sent from my SGH-i717/GT-N7005 w/phMOD_beta2
Click to expand...
Click to collapse
You realised you just bring a a old thread back yourself and no longer support of this model wtf you realise people.still use this phone everyday Right?
Sent from my SCH-I500 using Tapatalk 2
Alright So I am new to this forum but Im not new to the scene. I cant figure this problem out after days of searching and restoring. So I just got my note last week been loving it coming from my old 4s. Anyways My problem is I did a fresh factory restore rooted with dags kernel (tried both stock root and Oc kernel). I have clockwork recovery installed btw. So usually everything goes smooth. I clear all caches phone boots up runs smooth, I install root then my basic apps. Now I was doing them one by one and restarting.
Well long story short. At random any one of these times I reboot the device I come back into the lock screen Ill unlock and it force closes everything and just keeps rerunning media scanner looping. (force close twlauncher calenders google sync etc like really anything usually its twlauncher thats first I click ok it goes back to lock screen freezes for a second then reboots media scanner. It doesnt find service or even attempt it. The only thing I can do is restore and try again. I have done this over 10 times just this past week. I have fixed permissions in both rom manager and clockwork. Though it was good until last night it just completely restarted on its own and when I booted back up it was force closing.
I even did a fresh format wiped everything reinstalled stock att unrooted Rom then rooted and I have to be afraid of my phone dying or just randomly crashing and that when I restart its not gonna make it back into gingerbread without a restore. Now this will happen whether I have no apps or some apps. I can seem to find anything triggering it. Is this a defect in the phone maybe? Should I restore to stock and exchange at at&t or am I missing something? Please help guys. Ive only been able to get about a day before everything force closes. And that is unacceptable for an 700 dollar phone when all these others are running smooth.
Did you happen to mess with any overclock values? I had the problem you explain only after I overclocked to much and it was unstable
Solution: put into download mode and flash back to total stock with odin and start over. It worked for me. Restoring backup did not work
Sent from my SGH-I717R using Tapatalk
It is a problem with CWM. You should look for and download darkside super wipe. If I were you I would probably flash the stock Odin tar and start fresh. Make sure you install the latest CWM.. I believe beta4. You should not have to reboot your phone after every new app install.
Use the super wipe from in CWM (install from zip) and then use Odin to get back to stock.
You most likely have an older version of the CWM, I don't think anyone has reported any problems with beta 4 and force closing issues.
I have CWM 5.0.2.7 on here. I dont have to restart everytime I install. I was doing it to see if there was a certain app triggering it thats all. Cuz if the phone goes off and reboots to lockscreen thats when the FC happens. It never happens while Im actually in use. First time this happened it was stock clock speed and its happened whether its 1.83 or 1.56 or stock rooted rom. And I had tried both restarting stock att rom with bloat and from my first backup after odin root.
Where do i find beta 4? I originally got this cwm from rootgalaxynote.com
Nevermind I found it I pulled a n00b. Ok Imma give that a try right now I see this is older version so HOPEFULLY thats it. Thanks a bunch Ill check back in after to let you know. Pretty crazy in the back of my mind I felt like CWM was the only thing I didnt check out.
Stuck in firmware upgrade encountered an issue. I cant do anything Odin wont write the stock firmware back on after wipe. What do I do? No cwm or anything phone just boots to telling me to restore with kies?
h3r3tic said:
I have CWM 5.0.2.7 on here. I dont have to restart everytime I install. I was doing it to see if there was a certain app triggering it thats all. Cuz if the phone goes off and reboots to lockscreen thats when the FC happens. It never happens while Im actually in use. First time this happened it was stock clock speed and its happened whether its 1.83 or 1.56 or stock rooted rom. And I had tried both restarting stock att rom with bloat and from my first backup after odin root.
Where do i find beta 4? I originally got this cwm from rootgalaxynote.com
Nevermind I found it I pulled a n00b. Ok Imma give that a try right now I see this is older version so HOPEFULLY thats it. Thanks a bunch Ill check back in after to let you know. Pretty crazy in the back of my mind I felt like CWM was the only thing I didnt check out.
Click to expand...
Click to collapse
The version of CWM you were using was most likely for the international Note and therefore incompatible with the Note you have.
---------- Post added at 09:03 PM ---------- Previous post was at 09:00 PM ----------
h3r3tic said:
Stuck in firmware upgrade encountered an issue. I cant do anything Odin wont write the stock firmware back on after wipe. What do I do? No cwm or anything phone just boots to telling me to restore with kies?
Click to expand...
Click to collapse
You may want to join the IRC channel and see if anyone there can offer you a solution.
irc.irondust.net
#attgalaxynote
Just for Clarification
I too had the TwLauncher issue and tried clearing the Dalvik cache, cache, etc. This then sent me into a boot loop into recovery. (My CWM is the 5.0...version too). Tried the restore, no luck, wipe, no luck etc.
My PC doesn't see the phone, so I need to basically start the root process over again and install the Beta4 CWM. Am I understanding correctly?
I have the same problem and its driving me crazy. Can some one please help me out step by step Im new to this any help would be gratefully appreciated
this is what i get for oding late at night but i managed to do something very very stupid I odined my phone with a one click package for my captivate
I've been able to get the phone back in mostly working order now though.. but i feel in my gut something still may not be right.
here is where i got the package
http://forum.xda-developers.com/showthread.php?t=1300843
This below is what version i accidently installed.
I897UCKI2 Android 2.3.5 Gingerbread
With Bootloaders - Link to thread - Second Post [With CWM Injected Kernel from Boog]
so after i made this mistake.. (noticed my phone had a at&t bootscreen an wouldn't load) I went forth an flashed stock firmware avail for aiotools for the vibrant an then installed the stock froyo bootloader
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
help sugestions banter calling me a noob I just want to make sure i did possibly everything to fix this mistake.
pintek said:
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
Click to expand...
Click to collapse
You,my friend, dodged a bullet here.
pintek said:
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
Click to expand...
Click to collapse
Well, when you say you are not able to get CM7 to install, what exactly is it doing?
Are you getting thrown into a bootloop (caused by CWR mismatch and pretty common)? If so, pull battery and boot into recovery and re-flash CM7 over itself again. No wipe. Then reboot.
You may have to flash a different kernel, like glitch or something like that. But try the above first. Should work for you. Does it still say ATT when you boot up?
Lucky for you, everything is good, but if you want to flash a GB or higher ROM, i would suggest you flash the bootloaders in this thread: http://forum.xda-developers.com/showthread.php?t=1117990
After that just flash CM9, and you *should* be good, if not, try flashing it again with wiping data, cache, and dalvik cache. I guarantee that will work.
I ended up having to format both SD cards an retrying install custom rom via aio tool an with luck was able to get cm7 installed then cm10 an i dno't have the ime error everyone else seams to have . I did before this flash the gb bootloader over this cause it was the only thing that managed to remove the at&t splash screen before the kernal.
Lesson I learned....
remember that the vibrant you use aio tool not a premade pack >.<
an ya i do own both phones so this does complicate things now an then <,<
I also have both devices. Set up two different folders on your pc, one marked i897 and the other t959. I also add i897 or t959 to any files that could possibly get mixed up in Odin.
Its peanut butter jelly(bean) time...
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737