Related
DLed the flashrec-20090815.apk
the first time there was no install button using astro
I DLed it again and added it to the SD card and tried again
Installed fine
Backed up fine
I clicked to flash cyanogen recovery 1.4 and its been on the flashing "working do not interrupt screen for about 30 mins
I expected possible problems, just not right away with the auto flasher lol
Its a G1 with 1.5 if it matters
thanks for the help
well its been quite a while now, phone seems to work
Just the flasher is stuck on "flashing do not interrupt"
I guess ill leave it overnight and check back in the AM
I dont want to kill the app if it will screw something up
it probably got stuck doing something because it shouldn't take too long to flash a recovery image.
Thats what i figured
In searching even some of the videos showed how quick
Im just not sure how safe it is to try and close the app
figures
i haven't used the one click before so i honestly couldn't tell you, though you can always power off the phone and hold home and power to boot into recovery
and see if it worked then if it did i can give you the commands to mount your sdcard from recovery
I guess thats worth a shot. I wasnt sure if it would brick if i tried to reboot or anything
figured it was like flashing firmware in other devices
Ill try now
let me know how it works out
Ok, booted to the normal android screen
rebooted and noticed the SD card had the backup
so i guess it stopped half way. trying again now
did you try to boot into recovery? with home and power
Yes. and thats where i saw the normal android recovery screen not the cyanogen I've seen pix of
its been backing up for about 4-5 mins now
i didnt think anyone would be up this late lol
i am usually always on here till 4 or 5 am
Hmm, now it seems to be hanging on backup
If this doesn't work Ill just give up for the night maybe try again tomorrow
So when it got stuck on backup i recovery booted again, no changes so i removed the backup from the SD card (saved to pc just in case)
loaded the app again
now it backed up and flashed in 2 clicks
now for the rom
Also worth noting is this time the phone wasnt plugged in to the USB port
at first i didnt think it would matter since it wasnt mounted
not sure which fixed it.
Just passed the android screen. now i see a black screen.
so far its been booting for 12 mins. Ill give it a few more
Spoo76 said:
Also worth noting is this time the phone wasnt plugged in to the USB port
at first i didnt think it would matter since it wasnt mounted
not sure which fixed it.
Just passed the android screen. now i see a black screen.
so far its been booting for 12 mins. Ill give it a few more
Click to expand...
Click to collapse
if it won't go past the black screen, boot into recovery and wipe and reflash your rom. that fixed it for someone i was helping earlier.
Thats what i was just about to do lol
BTW your Guide is very clear and to the point
I looked around at the older methods and a few other guides just to be sure i knew what to expect
( was still caught off guard a bit lol )
Signing back into google, thanks a bunch!
Spoo76 said:
Signing back into google, thanks a bunch!
Click to expand...
Click to collapse
woot glad you got it to work. welcome to the world of a rooted g1 enjoy
Im already looking forward to trying to brag, then explaining why its cool and then seeing peoples eyes glaze over haha
Recently, I had a very long discussion with some helpful users regarding how my market disappeared in the Android Themes section. After never recovering my stock market application, I finally just flashed to the cognition rom that is built for 2.1.
This was a huge risk for me because for some reason my phone is not found in Odin when it is in download mode. I have already tried everything to get it recognized, but nothing was able to get it recognized. If I were to brick my phone, I don't think I could fix it. I soft bricked it during the problem with the Market, but luckily I was able to get the phone working again through recovery.
I am thinking of flashing to the new cognition so that I can get my phone running on a 2.2 based rom and then quit flashing until I get a better phone or figure out my Odin problems.
I just have a few questions. I know a lot of people recommend flashing to stock first (which I can't do), while others don't flash stock. I should be able to just disable Voodoo and hopefully flash successfully to a new rom, correct? Also, what are the chances of a permanent brick? As long as I could get into recovery I could probably get the phone back up again without the use of Odin, right?
yentlequible said:
Recently, I had a very long discussion with some helpful users regarding how my market disappeared in the Android Themes section. After never recovering my stock market application, I finally just flashed to the cognition rom that is built for 2.1.
This was a huge risk for me because for some reason my phone is not found in Odin when it is in download mode. I have already tried everything to get it recognized, but nothing was able to get it recognized. If I were to brick my phone, I don't think I could fix it. I soft bricked it during the problem with the Market, but luckily I was able to get the phone working again through recovery.
I am thinking of flashing to the new cognition so that I can get my phone running on a 2.2 based rom and then quit flashing until I get a better phone or figure out my Odin problems.
I just have a few questions. I know a lot of people recommend flashing to stock first (which I can't do), while others don't flash stock. I should be able to just disable Voodoo and hopefully flash successfully to a new rom, correct? Also, what are the chances of a permanent brick? As long as I could get into recovery I could probably get the phone back up again without the use of Odin, right?
Click to expand...
Click to collapse
<<< this might not be helpful, but I will tell you my situation... >>>
I have tried to Rom my JI6 (unoffical froyo) version of captivate, with Cog v2.3b8, using ROM manager.
But after installation, my screen went blank and the battery started to heat up...
After that I was lazy to fix it myself, so I went to exchange shop, and changed it...
- if your phone bricks (forever) try this : http://forum.xda-developers.com/showthread.php?t=775911
peurocs4 said:
<<< this might not be helpful, but I will tell you my situation... >>>
I have tried to Rom my JI6 (unoffical froyo) version of captivate, with Cog v2.3b8, using ROM manager.
But after installation, my screen went blank and the battery started to heat up...
After that I was lazy to fix it myself, so I went to exchange shop, and changed it...
- if your phone bricks (forever) try this : http://forum.xda-developers.com/showthread.php?t=775911
Click to expand...
Click to collapse
I tried that same method and it still did not show up in odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
yentlequible said:
I tried that same method and it still did not show up in odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Main problem with your Captivate is that you cannot connect to your PC???
Did you tried using different computer, or using different version of Windows/Mac?
<Sorry, if I'm not really helping you...>
peurocs4 said:
Main problem with your Captivate is that you cannot connect to your PC???
Did you tried using different computer, or using different version of Windows/Mac?
<Sorry, if I'm not really helping you...>
Click to expand...
Click to collapse
Back when I was really trying to figure the problem out (about 2 months ago), I was trying everything mentioned. I tried different versions of odin, 3 separate computers, windows xp/vista/7, front and back usb ports, multiple drivers, etc... The weird thing is that the phone is recognized in odin when it is on, which is how I was able to do a master clear on it. It is just when it is in download mode that it does not recognize it.
I eventually just gave up thinking that it was just a problem my phone has. The only thing I have not been able to test is using a different cable. I have been using the original OEM one, but I guess it could be the problem.
When did you bought the device?
if its within a year... you can exchange it... this looks like easy way out.
Sent from My Captivate
삼성 겔렉시에서 보냄
peurocs4 said:
When did you bought the device?
if its within a year... you can exchange it... this looks like easy way out.
Sent from My Captivate
삼성 겔렉시에서 보냄
Click to expand...
Click to collapse
Unfortunately, It was purchased off contract and used from someone who lived near me. It is less than a year old, I just don't have the receipt for it. I would say that I bought it around the beginning of last August. They guy who sold it said he only used it for 2 weeks.
Ok, im just going to risk it... Phone should be flashed within the next 10 minutes or so.
yentlequible said:
Ok, im just going to risk it... Phone should be flashed within the next 10 minutes or so.
Click to expand...
Click to collapse
I had the same prob at first and what i found is that I had to remove the drivers and then let windows 7 reinstall the drivers on its own again after turning debugging on, then used Odin to activate DL mode and let those drivers install as well
zelendel said:
I had the same prob at first and what i found is that I had to remove the drivers and then let windows 7 reinstall the drivers on its own again after turning debugging on, then used Odin to activate DL mode and let those drivers install as well
Click to expand...
Click to collapse
How do you use Odin to activate DL mode? I was unaware that it could do that...
I recieved a replacement captivate today. It was a 1011 build. Recovery and download worked fine. It was running 2.2.
I used the one click odin to flash to stock 2.1 and now I can no longer get in download mode or recovery with any key combo.
What can I do to fix this? Kinda freaked out, been flashing roms for months and months with zero issues so I am not real sure how to resolve this one.
To clarify, I can use adb to get into download or recovery I am sure and thats what I am going to do. Then flash the 3 button combo fix with Odin that C3P0LOL put together.
My question is I never had this on my 1007 build. What did I do wrong and what can I do to prevent this from every happening in the future? If the fix works and I avoid the one click odin, I should be good to go from now on right? Sucks. I tested everything before I flashed one click to 2.1 which is kinda stupid I guess.
what about holding vol up and down and inserting usb?
maybe your 3button was killed by the odin 1 click... but it still shouldve rebooted...
try the steps in this thread...
http://forum.xda-developers.com/showthread.php?t=775911
B-Naughty said:
what about holding vol up and down and inserting usb?
try the steps in this thread...
http://forum.xda-developers.com/showthread.php?t=775911
Click to expand...
Click to collapse
That is what I was doing and does not work. On my old captivate, I couldnt even count the times I did this so it's not user error. Guess its good I had such good success for so long as this is the time you learn stuff! I really dont want to learn today I just want it to work?!!
gocats7 said:
That is what I was doing and does not work. On my old captivate, I couldnt even count the times I did this so it's not user error. Guess its good I had such good success for so long as this is the time you learn stuff! I really dont want to learn today I just want it to work?!!
Click to expand...
Click to collapse
yea it's a little wierd the odin finsihed and didnt reboot the phone... and now 3button won't work... some phones just wanna act wierd... ive done everything in the world to mine including yank the cord during a bad flash... never lost 3 button or download... 1011 build...
tried holding the vol buttons and hookin usb then insert batt? hope u get it goin... keep us posted...
Flashed back to stock using the loader I referenced earlier and now I have both download and recovery key combinations.
I am speculatiing that coming from 2.2 to 2.1 with the one click was a bad idea. All I had done was root the phone to that point. If anyone knows 100% what the deal was I would like to know. I went from 2.2 to 2.1 because I couldnt get clockwork to work and I read that was an issue on 2.2. I am sure there was a better way but thats what came to me.
I would guess that using the thread below to go back to stock from now on to not risk screwing up my 3 button combos would be the best idea, anyone?
http://forum.xda-developers.com/showthread.php?t=995143
One question, if I want to go back to stock 2.2 as the phone came with is there a thread for that? I looked and so far didnt find it. Probably need to just keep looking but thought what the heck, would ask since I came this far.
Sorry for the long read, this is half rant and half question.
Alright, I got a captivate a long time ago (about a year and 3 months ago), loved it, rooted it and installed cyanogenmod as soon as I got home, changed roms and kernals constantly, did whatever I wanted to do.
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
-Pirate said:
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
Click to expand...
Click to collapse
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
-Pirate said:
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Click to expand...
Click to collapse
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
-Pirate said:
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
Click to expand...
Click to collapse
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
U def don't need a jig. If it's booting it's not bricked. Try removing battery, start Odin, hold down power and down, plug in and put battery in. This should bring u to download mode.
prbassplayer said:
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
Click to expand...
Click to collapse
I did start to see a few people with the problem, however many people do not follow up with what fixes their problem, and I did what a few people had said to do.
prbassplayer said:
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
Click to expand...
Click to collapse
I should of mentioned that I did flash a few times, 3 total I think, it was getting stuck at boot.
prbassplayer said:
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
Click to expand...
Click to collapse
I understand that **** happens but honestly my old captivate could always get into recover mode and download mode no matter what, it's extremely frustrating that something changed with the newer models. One of my questions was what caused the brick? I did nothing wrong from what I see and it was running perfectly until I tried to restart/boot into recovery.
Oh and mbc663, thanks but download mode doesn't work at all, nor does recovery obviously.
I can't say exactly what you are doing. Best advice I can do Re download your .zips Flash back to stock GB and try again.
-Pirate said:
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
Click to expand...
Click to collapse
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Sounds like you got one of the refurbs that is missing the SBL. Have you looked at this thread? http://forum.xda-developers.com/showthread.php?t=1129821
I've not had this problem myself but it sounds like that might help. If I remember reading correctly, once this is flashed it should stick as long as you don't flash any other bootloaders on top of it.
Its not missing the sbl. The sbl it has doesn't respond to key combos. Derpa sherpa moment for samsung I guess?
Rofl yeah...if it was missing the sbl it would be fuggin bricked!
studacris said:
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Click to expand...
Click to collapse
I know, thanks. I'm such a creature of habit, I started doing it like this a bit over a year ago, and has worked flawlessly for me(just jinxed myself!) so I never saw a reason to "fix what aint broke".
I'll take a look at Cezar's thanks!
Yeah, missing SBL was a poor choice of words. My bad.
kangi26 said:
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Click to expand...
Click to collapse
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
kangi26 said:
3buttonFix to my SD, then reboot into recovery
Click to expand...
Click to collapse
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
-Pirate said:
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
Click to expand...
Click to collapse
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
kangi26 said:
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
Click to expand...
Click to collapse
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
-Pirate said:
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
Click to expand...
Click to collapse
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
kangi26 said:
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
Click to expand...
Click to collapse
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: deleted
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
-Pirate said:
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: imgurDOTcom/26sXGl.jpg
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
Click to expand...
Click to collapse
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
kangi26 said:
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
Click to expand...
Click to collapse
Maybe because it's a refurb? and whoops didn't think about that.
-Pirate said:
Maybe because it's a refurb? and whoops didn't think about that.
Click to expand...
Click to collapse
I'm not sure why, mine is a referb, and I have a sticker with mine on it. Ooh well, it is what it is
Sent from a autonomous device
Hey i'm one dumb guy who managed to brick his Galaxy Note...
I received the ICS Update OTA yesterday, i discovered later that i what on the LPY kernel. Then i though it doesn't matter cause i didn't need to flash any rom because the stock gingerbread was perfectly fine for me.
But the update made my phone (had it for only 2weeks) painfull to use. FC all the time etc... Couldn't do a factory reset because of all the warning over here...
So i flashed the franco Kernel wich was to my knowledge a "safe kernel", then i tried to install the Kingdroid Rom, after all 3 wipe. Wich lead me to brick... I've waited 25 minute for the phone to boot up but nothing... So i tried to restore my backup ok ICS that didn't go well either.
After that i tried to flash trough Odin a Gingerbread Rom, before doing so i've read multiple Guides et threads. Odin got stuck at factoryfs.img every time.
So i did some search and achieved to go through this guide: http://forum.xda-developers.com/showthread.php?p=26285877#post26285877
I went through the process. And i tried to flash a CM9 rom through recovery as the guy recommends. But i'm still stuck on the Galaxy Note bootscreen.
I believe you guys can help me, i still have access to recovery et Download mode.
I believed i wasn't a Noob since My HD2 i've had numerous phone and rooted\flashed countless roms on HTC/Samsung/Motorola/Sony Ericsson phones... In the end i'm finally juste one big noob...
Thanks for those who will help me, and even take some time to read this.
First thing you should do is check other threads about that around here.
If you can get it into download mode, you could give flashing with Odin a try. If it doesn't get stuck at factory.fs, then you're not superbricked.
If it does get stuck, then you have 2 more hopes:
- HOPE 1
- HOPE 2
If those don't work either...I'm afraid it's off to the Samsung Service center for a shiny new motherboard.
Best of luck to you and hope you get your Note up and running as soon as possible...
The problem is My flash count is at 3 and i have the big yellow logo...
Atomos33 said:
The problem is My flash count is at 3 and i have the big yellow logo...
Click to expand...
Click to collapse
First try to revive your phone, after that this will fix your triangle/flash counter http://forum.xda-developers.com/showthread.php?t=1354888
Atomos33 said:
The problem is My flash count is at 3 and i have the big yellow logo...
Click to expand...
Click to collapse
If we revive your phone, that's easily sorted.
If we don't, you can make it so that the service center can't really tell.
Right now i am trying to install Rocket Rom after installing, Abyss kernel 4.2 and doing a Full wipe. Waiting for the installation.
Edit: Got through the process after two days. It just took me to write this. And tired the whole process once again desperatly and it worked... Can't believe it...
Android.process just keep crashing what should i do ?
Full wipe? Kinda scared now ^^'
Atomos33 said:
Right now i am trying to install Rocket Rom after installing, Abyss kernel 4.2 and doing a Full wipe. Waiting for the installation.
Edit: Got through the process after two days. It just took me to write this. And tired the whole process once again desperatly and it worked... Can't believe it...
Android.process just keep crashing what should i do ?
Full wipe? Kinda scared now ^^'
Click to expand...
Click to collapse
Wow. You're pretty safe now mate, I guess.
If you're on RocketRom, you can full-wipe, no worries...maybe flash Abyss and reboot recovery and wipe with that, just to be ultra-sure.
You should be clear of any damaging kernels.
------
LE: Did it work...? You're welcome...?
Haha sorry was late yesterday, i didn't do anything went straight to get some sleep ^^'
I really wanted to thank you guys! I'm sorry if you tought i forgot you...
Well i didn't change the rom neither did i wipe anything. Juste went to work this morning so...
I think i am going to change the Rom the battery consumption is to damn high... Was at 100% this morning and i'm already at 30%...
So it worked my Note is saved! I've tried the link in the OP (And your Hope 1 ^^') a second time flashed Abyss kernel, then flashed Rocket Rom.
The flashing took 10minutes so for the people who went through this wait!
And the first boot took 5 minute.
Once again big big thank to Eug3n91 and Gee2012 been around here for long and this has been one of the best response time ever!
HERE is easy way to fix bricked N7000...
http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/
ingbrzy said:
HERE is easy way to fix bricked N7000...
http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/
Click to expand...
Click to collapse
That's not an easy brick fix, that's a tutorial on how to use PCO to flash GB with repartition.
In other words, useless.
In the comment section of the website, quite a few people recovered, so not as useless as it seems!
Sent from my GT-N7000
Atomos33 said:
Haha sorry was late yesterday, i didn't do anything went straight to get some sleep ^^'
I really wanted to thank you guys! I'm sorry if you tought i forgot you...
Well i didn't change the rom neither did i wipe anything. Juste went to work this morning so...
I think i am going to change the Rom the battery consumption is to damn high... Was at 100% this morning and i'm already at 30%...
So it worked my Note is saved! I've tried the link in the OP (And your Hope 1 ^^') a second time flashed Abyss kernel, then flashed Rocket Rom.
The flashing took 10minutes so for the people who went through this wait!
And the first boot took 5 minute.
Once again big big thank to Eug3n91 and Gee2012 been around here for long and this has been one of the best response time ever!
Click to expand...
Click to collapse
So, you are back up and everything I'm gathering, correct?
And, also, from what I gather in your OP, you flashed/wiped with Franco kernel? It shouldn't cause bricks and I'm glad it ended up not "bricking" your phone because so far I don't think it has bricked anything.
Stay clear of anything stock from now on and I highly recommend sticking to CM9 kernel/ROMs. They are smooth, safe, efficient, etc.
Atomos33 said:
Haha sorry was late yesterday, i didn't do anything went straight to get some sleep ^^'
I really wanted to thank you guys! I'm sorry if you tought i forgot you...
Well i didn't change the rom neither did i wipe anything. Juste went to work this morning so...
I think i am going to change the Rom the battery consumption is to damn high... Was at 100% this morning and i'm already at 30%...
So it worked my Note is saved! I've tried the link in the OP (And your Hope 1 ^^') a second time flashed Abyss kernel, then flashed Rocket Rom.
The flashing took 10minutes so for the people who went through this wait!
And the first boot took 5 minute.
Once again big big thank to Eug3n91 and Gee2012 been around here for long and this has been one of the best response time ever!
Click to expand...
Click to collapse
My pleasure! Sorry I got impatient. Was a bit anxious and...well...to be honest...these methods haven't always gone the same for everyone. Glad you were in luck!
Enjoy your Note!
Guess what it worked to recover my note but i tried a Wipe after it died. Once again i flashed abyss kernel and then the abyss kernel just never booted...
So i tried to flash via Odin didn't either... And then it's just dead... I have access to recovery trought pda4 kernel flahed with Odin.
I don't know if i want to re format re partion everything through ADB...
I'm without phone since yesterday... My case seems to be different.
As you said the Franco kernel wasn't supposed to brick my phone but every single move i try to make it seems to kill it...
Had one day without hassle. Worst phone i had.
Edit @Andreww88: i swear it was bricked i wiped everything and installed the Kingdroid Rom never went through. So i just went back to recovery and flashed bac the Stock rom and then nothing. Just nothing Odin, couldn't do anything.
Edit2: So i've done everything again it's working again on paranoid rom! I'm kinda frustrated on CM9 i have no codecs, the lockscreen is not Note-adapted, and the Stylus is of no use...
Edit3: Can anyone help me getting back to a Stock rom without using Odin?
I'm sorry for the double post but can someone tell me if the Odin Mobile will work even if the Odin desktop doesn't work?
Atomos33 said:
I'm sorry for the double post but can someone tell me if the Odin Mobile will work even if the Odin desktop doesn't work?
Click to expand...
Click to collapse
Unfortunately, no.
Congrats for unbricking your note
Its like a Motivational story .
I was also softbricked my Note many times. But managed to unbrick always.
Moral of the story....
Our not is hard to brick if we will not give up..
Because
Winners never quit.... quitters never win
I've sent it back to the repair center. After cyanogen worked, i've used Triangle Away to reset flash counter. Flashed a stock rom. It didn't go well as exepted.
When i sent the phone it had no triangle no flash counter and of course no custom rom!
So as chintamanijaipuri (As Indian i found it very hard to write ^^') said never give up!
Use the link in the OP and flash Cyanogen mod trought recovery. Use the recovery of that thread for me it worked well, Abyss kernel on top didn't work for me. Once you boot cyanogen use triangle away, and Flash a stock rom that will brick your Note in good way, (Without Triangle, flash counter, custom recovery) so it will never be your fault!
Good Luck thanks everybody!