Here's all the steps that lead to the unfortunate early demise:
1) was on stock 2.2, updated using Kies to 2.3.3 = works
2) used SuperOneClick to root = works
3) installed Rom Manager from market, but flashing cwm didn't seem to do anything (recovery kept being original one)
4) used Odin to flash a Kernel (bhundven-blastoff-v2.5) with CWM = current "dead" state
- Phone boot loops (i'm seeing all the logos starting with Samsung 4G+, this is a 3G+ phone)
- I can go into Download Mode, but phone is unrecognizable on any PC, using any cable on any port
- I can go to CWM (v5.0) but i have no nandroid, i can't access SD card, PC still doesn't see the phone
Is there ANYTHING i can do to recover this phone ?
Thank you in advance!
Sefy said:
Here's all the steps that lead to the unfortunate early demise:
1) was on stock 2.2, updated using Kies to 2.3.3 = works
2) used SuperOneClick to root = works
3) installed Rom Manager from market, but flashing cwm didn't seem to do anything (recovery kept being original one)
4) used Odin to flash a Kernel (bhundven-blastoff-v2.5) with CWM = current "dead" state
- Phone boot loops (i'm seeing all the logos starting with Samsung 4G+, this is a 3G+ phone)
- I can go into Download Mode, but phone is unrecognizable on any PC, using any cable on any port
- I can go to CWM (v5.0) but i have no nandroid, i can't access SD card, PC still doesn't see the phone
Is there ANYTHING i can do to recover this phone ?
Thank you in advance!
Click to expand...
Click to collapse
You are all kinds of messed up.
First, this is the SGH-T959 and not the T959V. The V denotes the Vibrant 4g which this phone is not.
Second, the phone was abandoned on 2.2 and never got an "official" update to 2.3.3. That again was the 959V.
Third, Not sure where you got bhundven-blastoff-v2.5 kernel from (I know who bhundven is though), but I would think that it is also from the 959V section
All is not lost though. What I need for you to do is pop open your phone and look at the sticker under your battery. Does it say SGH-T959 or SGH-T959V. Another way to tell is that the 959V has a front facing camera, wheras the 959 doesn't natively.
If you do have the 959, then all you have to do is go into my Repo thread in the Dev section and download the stock JFD package and flash that via Odin. As long as you can get into Download Mode, you are not bricked. This will put you on a clean 2.1 eclair and you can use this method to root.
I'll check back in a day or so. Good luck.
Edit: Not sure if you still have your TF101, but you can update that to KatKISS and run KitKat like a baws.
Woody said:
You are all kinds of messed up.
First, this is the SGH-T959 and not the T959V. The V denotes the Vibrant 4g which this phone is not.
Second, the phone was abandoned on 2.2 and never got an "official" update to 2.3.3. That again was the 959V.
Third, Not sure where you got bhundven-blastoff-v2.5 kernel from (I know who bhundven is though), but I would think that it is also from the 959V section
All is not lost though. What I need for you to do is pop open your phone and look at the sticker under your battery. Does it say SGH-T959 or SGH-T959V. Another way to tell is that the 959V has a front facing camera, wheras the 959 doesn't natively.
If you do have the 959, then all you have to do is go into my Repo thread in the Dev section and download the stock JFD package and flash that via Odin. As long as you can get into Download Mode, you are not bricked. This will put you on a clean 2.1 eclair and you can use this method to root.
I'll check back in a day or so. Good luck.
Edit: Not sure if you still have your TF101, but you can update that to KatKISS and run KitKat like a baws.
Click to expand...
Click to collapse
Thank you for the help, regarding your question it's a D, not a V
Either way, i bought a USB Jig off ebay and managed to get Download Mode and fixed the phone up!
Related
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Rovah said:
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Click to expand...
Click to collapse
Same problem. anyone?
Vincho said:
Same problem. anyone?
Click to expand...
Click to collapse
Did you read the answer ???
jje
Look online (samfirmware), ask friends or on forums for anyone who has the SGS2 w/ the same carrier in the same country and try to find the firmware version (I9100***** - the stars are letter codes). Then just download that firmware and use Odin to install it.
If you can't find it,you presumably could just flash any stock firmware and it might work (or it might make things worse, try at your own risk)
Rovah said:
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Click to expand...
Click to collapse
The progress bar not moving is a known issue with the CM7 Recovery. All you need to do is wait for it to say that it's finished. There is nothing wrong with your phone and no need to return it. You just cancelled the CM7 install part way through which meant not all required files were installed on the phone, causing it to not boot.
As for it taking longer to boot into android after the odin reflash. That's because it has to build up it's dalvik-cache again. This is completely normal any time you install a new rom. It only happens on first boot of a rom.
So again, no need to return your device and feel free to try CM7 again. Just remember to let it finish even if the progress bar isn't moving.
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Rovah said:
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes, as long as the firmware you're flashing is the same as the stock version that came on the phone. And even if not, you'll get the kies updates for whatever region firmware you did flash onto the phone.
I see. Thanks a lot!
Is there any danger to flashing firmware from a different region than the one youre from?
Sent from my GT-I9100 using XDA App
Sorry for the read, thanks if you do though.
I'm a total noob, but I've been reading/using many many threads and searches on XDA. I am just Not Sure of the condition of my phone and how to get it to where I want it without getting "stuck/crash/errors/bootloop" again.
Here's my condition, ADB Devices stopped listing my phone, I have a Yellow exclamation at bootup, and trying to flash a kernel or push a zImage left me in bootloop (eventually got the phone to Restore through CWM - It didn't want to at first! different error types like Can't mount SD card, No recovery mode, can't read SD Card, or Can't write due to R/O (then I learned Remount command)) Now I got some weird kernel (Either ZedomaxOC or Siyah kernel)
[email protected] <-- current.
I bought a Jig off amazon incase I mess something up worse.
So I got a SG2 AT&T last Sunday, and immediately I started messing with it. I came from prepaid phones and metro PCS, this is my first smart phone and actual "Phone Contract"
After messing with the phone and exploring themes, settings etc. Stock, By Tuesday I was reading many threads and guides to installing Roms, kernals, and rooting.
(I mess with my own PC alot so I got right on w/ the phone.)
Unfortunately they way I first installed my Root/CWM/Rom added +2 to the counter, and left the Binary at Official or Custom. using these FAQ's http://galaxys2root.com/att-galaxy-s2-faq/
Then I came across XDA forums and followed this: http://forum.xda-developers.com/showthread.php?t=1311081
Then I did steps: 2a, 3a, then 3b (not sure if I did 3a or 3b first) anyway it removed the Yellow "!" and installed CWM 5.0.2.3.
I have Samsung Kies and installed those drivers, I started with this Kernel:
GalaxyS2ATTRootZedomax.zip
http://downloadandroidrom.com/file/GalaxyS2ATT/rooting/GalaxyS2ATTRootZedomax.zip
And this Rom: Galnet Miui ICS Android 4.0.1 v1.11.9
http://galaxys2root.com/att-galaxy-...id-4-0-rom-for-rooted-att-galaxy-s2-sgh-i777/
Here's my GOAL: Stock or Rom/ Official binary / No yellow exclamation or Custom counts/ 5.0.2.3 CWM / 1.6 OC Speed
Taking my phone from where I'm at w/ unbrick kernel brought me to bootloop. (Do I wipe/factory reset before doing unbrick kernel flash?)
History:
Stock?
Device: SG2 AT&T
Android v: 2.3.4
Baseband: I77UCKH7 (current, but I started at UCKJ1)
- Yes I started at UCKJ1 but the Unbrick kernel brought me to UCKH7
Stock Kernel? Not sure
Thank you for everyone who's looked on my thread, I figured I'd clarify my main issue I can't seem to fix:
ADB Devices no longer lists my device. (Debugging is on in the phone, and USB connection doesn't "Mount" my card to computer)
Samsung kies reinstalled its driver, and
my device manager continues listing my phone as "Unkown device" since yesterday. I've tried enable/disable, uninstall/reinstall etc. etc. nothing makes the PC remember it again. Even microsoft solutions didn't help.
Have you checked out the thread about recovering from an i9100 flash?
http://forum.xda-developers.com/showthread.php?t=1294574
I know that's not your issue but it helps 'rebuild' the software for your phone step by step.
And more importantly for your question, the order to do each step.
As for your computer problems, try a different computer. Get your phone up and running and done with. It's alot less stressful when you're only dealing with one issue at a time.
Sent from my páhhōniē
I am just throwing this out there. What you posted it sounds like you flashed the siyah 2.2 kernal. There have been documented mounting issues with that kernal. Try to flash entropy's kernal. It might help.
moustro said:
I am just throwing this out there. What you posted it sounds like you flashed the siyah 2.2 kernal. There have been documented mounting issues with that kernal. Try to flash entropy's kernal. It might help.
Click to expand...
Click to collapse
I tried to go from the "Siyah" 2.2 that was posted here somewhere to Entropy's Stock +Root and it caused crash/bootloop.
I think I downloaded my current kernel from here: http://forum.xda-developers.com/showthread.php?t=1367800
I would like simply a 5.0.2.3 CWM kernel that can do 1.6Ghz
(What else does a kernel do?)
I'm using MIUI rom but I'm wondering if I should go back to stock or try another.
- concerns of: Unable to change ROM/kernel, and phone being called "UNKnown device" and not connecting to PC.
I got my jig in the mail today, it removed the yellow ! triangle and reset the counter/official etc. cost 1.25$ + shipping
I'm getting force close a lot on everything since using "restore" from CWM.
I just plugged my phone into the PC, and using the JIG made the "Unknown device" go away, but my phone still will not list/connect via ADB DEVICES
in debug bridge. Pic: http://img818.imageshack.us/img818/7104/buhuhuhuhuhuh.png
Also when I flash/backup my phone, all the old stuff stays on there, its piling up (I did this like 3 times, down to 8gb space left)
How do I clean it all out, and what files Don't get deleted?
Wipe cache? Wipe delvik cache? factory wipe? + Factory reset? (Do I do these before "restoring"? Do I do these before flashing a new kernel?)
NEW update... My device was "recognized" in Download mode (not recovery mode), and is still UNKNOWN DEVICE when plugged into computer with phone turned on..... man this is lame. How do I get ADB Device to recognize my phone again? I also want to get rid of siyah 2.2 kernel and go back to Zedomax kernel or Entropy kernel w/ root/cwm (previous try to go back cause bootloop)
Solved I think. Restored a backup and it had an older kernel. Siyah 2.2i was causing all my problems/fc's/crashing/bootloop. ADB works now. Just need to get my apps back. How does: Titanium work?
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
This is what happens when you have too much info with waaaay too little experience.
Bought an unlocked Vibrant from Amazon a year ago after the original tmobile one got stolen. It had issues like freezing up, tons of apps running all of time, etc. I finally tried installing froyo and it made the phone SO MUCH BETTER! Everything ran 1000% faster. I should have stopped there. But, it was pretty addictive I started reading about the new ice cream roms and somewhere, before I even got into it, I messed up the internal sd card. I have been working on this for a week, reading, downloading, flashing, etc. I feel like I have tried everything and have gone around in circles.
I can get into download mode with no problem. The furthest I have gotten after that was getting the "pass" in Odin. The phone does the boot up, then stay on the Galaxy S screen. Now, my computer won't recognize the phone (which has already happened) but now I am soooo confused and frustrated about where to go next. I have used AIO toolbox, Eugene's no brick, installing new drivers, new usb cord, etc.
Sorry so long. Thanks again.
bump...hope someone can help.
Could you give a clearer explanation/timeline of what you did? How did you mess internal sd?
Did you Odin stock jfd?
Sent from my GT-I9000 using XDA App
nolamom said:
bump...hope someone can help.
Click to expand...
Click to collapse
Is Clockworkmod recovery installed? If not, google: Samsung_Vibrant:_Full_Update_Guide and go to the Cyanogenmod wiki entry. Read through the "Installing Clockworkmod recovery" section.
In addition, from Addictivetips, to start recovery mode using the hardware buttons:
"Using hardware button combination on most Android devices:
On most Android devices including ones by HTC, you can enter recovery by powering your device off and then powering it back on while keeping either the ‘Volume Down’ or the ‘Volume-Up’ button pressed, depending on the device. This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
Sorry, but I'm not allowed to post links yet.
On most Samsung devices specifically Samsung Galaxy S series devices, you must keep both the ‘Volume-Up’ and ‘Home’ keys pressed while powering on the device, to directly enter recovery."
Thanks so much for the help. Ascallop: I tried to run Heimdall suite 1.3.1. The first time the drivers installed but I could not get passed the "run as administrator" on the next step. I have Windows XP professional even though I am on a home computer. It is automatically checked off to do so. When I tried again later that day, my computer again only recognized the vibrant as an unknown device. I just followed your link to Cyanogenmod's wiki and downloaded the older version and the same thing happened with the unknown device. I can't get passed that. Trailblazerz11, I think when I got to clockwork mod recovery, I hit repartition (if I am explaining that right). I was able to get into download mode and use Odin to get to the bootloader loop. I can't get into recovery. I was getting the message about the internal sd error. Now, I am stuck with the unknown device issue. I have tried a couple of different versions of Odin, the AIO toolbox, different usb ports, a new samsung cord, etc. Thanks again for helping this noob.
update: Used heimdall frontloader and installed cmenard overstock. Now I am stuck at the overstock screen. I am searching through different posts to find out more. But if you have any advice or can point me in the right direction, I'd appreciate it. Thanks again.
Have you tried repartition on odin?
sent from the xda app on my android smartphone.
Do you have an external SD card installed? If so, then remove it during the entire recovery process. I had lots of trouble recovering and flashing new kernels/roms while it was installed. Probably should have mentioned this earlier... sry.
No. It was already taken out. I am having trouble still with the vibrant not being recognized. I used the zadig, it recognized the samsung, did the next step, frozen at overstock screen. Now, after unplugging cable, Vibrant pops up as unknown device. Can't do zadig again.
I'm travelling until Friday, when I get back to my home PC, I'll odin my Vibrant back to stock Eclair and will list the steps that I took some months ago to install CWM/CM7. I once was at the same point as you are now, I just can't remember the steps verbatim regarding the recovery process. One question though: have you updated your phone via Kies at any point? If so, was the last update to Froyo?
BTW, I'm currently running (quite happily) ICS Passion V12 on my T-Mobile Vibrant.
The Vibrant is a pretty hard device to truly brick. Don't worry too much, yet.
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
nolamom said:
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Let's get your phone back to Stock first. I just did this to my own Vibrant
I am officially back to stock!!! Thanks so, so much. After all of the reading and researching, you actually jumpstarted my recovery! Thanks again!!!
You're welcome
BTW, I flashed ICS V12r1 with Nelson's new kernel today. I love it. GPS works great for me, although others have reported problems. Same old deep sleep issue for them.
I wonder if flashing back to stock first is the key to fixing the prob. Don't really know though...
After the stock flash, the steps I took were:
copied kernel and rom to the internal sd card
One-click rooted the phone
odin (1.3) the Overstock kernel just to get cwm installed (instructions on the cm7 wiki)
reboot to cwm
wipe data/factory reset
wipe cache/dalvik
flash rom
reboot, let settle
reboot to cwm
flash kernel (I used: ICS_Passion_sunset_with_nova)
reboot, let settle
---------- Post added at 05:29 PM ---------- Previous post was at 05:24 PM ----------
One more thing: I flashed the Gingerbread bootloader as well. After you do this the key combo for cwm is: Vol-up + power. Let go when you see the boot splash.
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
You shouldn't need an external card to root. Try One click root:
http://forum.xda-developers.com/showthread.php?t=1125414
nolamom said:
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
Click to expand...
Click to collapse
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
cashmundy said:
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
Click to expand...
Click to collapse
And of course the stock recovery won't work with anything else. Different partitioning, different filesystems.
Okay. I was able to root with the one click root app. Now, I need to figure out what to do next. Ascallop, I was reading about your latest updates. I have to go through it a few times so that I can understand it all. I had froyo before and it blew away stock. I can't imagine what ICS is like Thanks again for all of the help. I HATE being back to stock.
The only reason I'm not running ICS is that I'm waiting for CyanogenMod permissions management to appear in anyone ICS rom. I'm really tempted to try Passion. ICS is markedly better than the best GB in various ways. Just remember to take a nandroid backup before upgrading, and that if something doesn't work and you need to downgrade, you will have to get the downgrade done successfully before you can nandroid-restore. Good luck!
Thanks Cashmundy. I saw the video for the root and install ice cream sandwich by Eddie West (I think that is his name.) He is a dj also. It looks like everything I would need so I may go with that.
I've been running rooted with Alliance Rom build 32 for about a year with zero problems. The phone battery ran low last night and the phone turned off. When I turn it on it stops at the first logo. I can't get into Philz
recovery. It will go into downloader mode. I tried using Odin to revert to the stock MJ9 I started from when I used Casual. It flashed successfully (stock pit and MJ9) but still gets stuck at the the first logo and won't go into recovery.
SD card is removed. I haven't made any modifications to the phone for the past six months except adding a few well known apps from the store.
Any advice on how to get back to where I can load recovery and proceed to reinstall would be greatly appreciated.
PS.
I would have bought a new phone last year but it seems all the ones I like are bootloader locked. I can live without the stylus (would love a new note though...). Any recommendation on a replacement for the Note 2 would be much appreciated.
dsteinschneider said:
I've been running rooted with Alliance Rom build 32 for about a year with zero problems. The phone battery ran low last night and the phone turned off. When I turn it on it stops at the first logo. I can't get into Philz
recovery. It will go into downloader mode. I tried using Odin to revert to the stock MJ9 I started from when I used Casual. It flashed successfully (stock pit and MJ9) but still gets stuck at the the first logo and won't go into recovery.
SD card is removed. I haven't made any modifications to the phone for the past six months except adding a few well known apps from the store.
Any advice on how to get back to where I can load recovery and proceed to reinstall would be greatly appreciated.
PS.
I would have bought a new phone last year but it seems all the ones I like are bootloader locked. I can live without the stylus (would love a new note though...). Any recommendation on a replacement for the Note 2 would be much appreciated.
Click to expand...
Click to collapse
If you're looking for a newer phone that lets you unlock the bootloader, you might want to check out last year's Nexus 6 or the newer Moto X Pure Edition. The Nexus 6P from Huawei also looks nice and I'm keeping an eye on it as my next potential phone. The Nexus 5x from LG should also have a boo that can be unlocked.
-----------
Hopefully, you didn't flash the stock Verizon MJ9 4.3 firmware back onto your phone. If so, then you have locked your bootloader with no way to unlock it.
I'm thinking that you're probably getting confused with needing to flash Beanstown106’s modified MJ9 firmware (which doesn't return the phone to stock or contain the 4.3 bootloader). See one of my previous posts ( http://forum.xda-developers.com/showthread.php?p=58541771 ), which discusses a similar issue and has a link on how to flash the stock recovery back onto the phone if you'd like to try that rather than restoring the phone back to stock 4.1.2.
You could also just Odin restore the phone back to Verizon factory stock 4.1.2 and run Casual again to start fresh. See Droidstyle's restore guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ) to get instructions on how to flash back to 4.1.2.
Once back on 4.1.2, you need to go into the stock recovery and wipe cache /factory reset to make sure everything is wiped off the device for a fresh start. (Odin doesn't wipe everything in it's flashing process).
If you restore back to stock 4.1.2, then be careful not to let your phone take an OTA because if it gets updated to 4.3+, then you won't be able to unlock the bootloader any longer.
I usually remove my Sim card when restoring to stock 4.1.2... just to ensure I don't accidentally take an OTA update before I get it rooted again. (You can skip the initial phone Setup screen with the method in this YouTube video - https://youtu.be/qekEpn1Bufc ). It says it's for the S3 but works on the Note II as well. Once you get back into the phone and enable USB debugging in Developer options, you should be able to run Casual again. The phone doesn't have to be activated or on wifi to do this.
Once Casual is successful, it's safe to put the Sim card back in because I don't believe an OTA can install successfully with a custom recovery installed.
Good luck.
mattnmag said:
I
Hopefully, you didn't flash the stock Verizon MJ9 4.3 firmware back onto your phone. If so, then you have locked your bootloader with no way to unlock it.
Click to expand...
Click to collapse
All the ROM's and tools are from threads here so pretty sure I'm using Bean's modified MJ9. I was on Beans 4.3 for over a year before I went to the Alliance ROM.
You could also just Odin restore the phone back to Verizon factory stock 4.1.2 and run Casual again to start fresh. See Droidstyle's restore guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ) to get instructions on how to flash back to 4.1.2.
Once back on 4.1.2, you need to go into the stock recovery and wipe cache /factory reset to make sure everything is wiped off the device for a fresh start. (Odin doesn't wipe everything in it's flashing process).
If you restore back to stock 4.1.2, then be careful not to let your phone take an OTA because if it gets updated to 4.3+, then you won't be able to unlock the bootloader any longer.
Click to expand...
Click to collapse
4.1.2 sounds like a better idea - I have that also.
Thanks your advice here is just what I was looking for in my effort to get this phone running again.
Update: I can still go into Download mode but cannot get a computer to recognize the phone now.
Not one of three computers, numerous cables including one out of the Galaxy Note 2 box and all the tricks I could find like pulling the battery while connected helped.
The first day of this problem (stuck at first logo) I was able to connect to the phone with Odin. I flashed the following:
1. sch-i605-16gb.pit
2. CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
Would something like http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 help?
Should I look into the JTag guys on ebay?
Thanks,
dsteinschneider said:
Update: I can still go into Download mode but cannot get a computer to recognize the phone now.
Not one of three computers, numerous cables including one out of the Galaxy Note 2 box and all the tricks I could find like pulling the battery while connected helped.
The first day of this problem (stuck at first logo) I was able to connect to the phone with Odin. I flashed the following:
1. sch-i605-16gb.pit
2. CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
Would something like http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 help?
Should I look into the JTag guys on ebay?
Thanks,
Click to expand...
Click to collapse
I don't know if a USB jig would help the computer recognize the phone again.
Since you tried 3 different computers and still couldn't get it recognized... I'm wondering if something got fubared when you Odin flashed the VRLJB stock Rom. So when you go to Device Manager in the computer, the computer doesn't even show anything connected at all?
I don't know that it would be worth the time, but (on the computer that last worked for your phone), you could try uninstalling the Samsung Drivers, and then use a program like DevManView to totally uninstall all Android related drivers. Restart the computer afterwards and then reinstall the Samsung USB Drivers (from here: http://www.samsung.com/us/support/owners/product/SCH-I605) . Then connect your phone back to the computer in Download Mode to see if it will reinstall the drivers and recognize it.
If the computer still doesn't recognize the phone after all that, then I'm out of ideas.
I'll try the devmanview driver cleanup (love nirsoft utils!) and install the driver in your link on the orginal pc which I use for flashing ROMs. If that doesn't work I'm going to look into sending it out to a JTag guy although they claim if you can get into download mode after they perform their magic that they were successful.
Went with the LG G4 which I'm very happy with. As far as getting the Note 2 running again I've been thinking l might buy a used Verizon Galaxy Note 2 motherboard on ebay rather than sinking a lot of time into trying to... should I say "unbrick" it.
If you ran casual first, it will not connect to the samsung driver, until you uninstall the USB services from the device manager, and then run find new hardware.
But maybe this will not help considering you already tried 3 machines?
I may have had the Samsung driver on all 3 machines. Good suggestion - I'll post back if it works.
Related question. I see you are running CM 12.1 - do you have standby battery drain issues? My 4.4.2 Alliance 32 would drain the battery down to 0 if I didn't plug it in at night even though I might still have 1/3 charge.
dsteinschneider said:
I may have had the Samsung driver on all 3 machines. Good suggestion - I'll post back if it works.
Related question. I see you are running CM 12.1 - do you have standby battery drain issues? My 4.4.2 Alliance 32 would drain the battery down to 0 if I didn't plug it in at night even though I might still have 1/3 charge.
Click to expand...
Click to collapse
Right, it was in the Adam Antler video, for casual. Once you use the casual on USB, the samsung driver will not work until you uninstall and reinstall USB system.
I can get almost 3 days out of a phone battery with little or no use. The one I am using could make it a day and 1/2, but I charge that one every night because I do not need and down time just in case.
I am using the nightly build, 12.1-20151222 12/22/15, I am not sure how the other builds are, or even the stable build for that matter?