Related
okay i really need some help.
ive tried all the steps to recover my phone.
i get to the g1 screen when i power it up.
i can still get in to recovery menu.
ive tried to do a wipe.
please i need help.
ive also tried reinstalling rc29 with the original spl
but my radio is still 2_22_19_26I
PLEASE I NEED HELP!
or if there is a way that i can make it look like i never touched it then im still able to return it
so anything would help. links also
if you put the DREAIMG.nbh on your phone via bootloader it will reset the radio and spl to stock and everything else will be stock so that you can return the phone as though you never did anything to it
sweet. i guess i cant fix my phone. good thing i only got it 3 days ago.
whats a good thing to tell them when returning my phone?
G-Fetus6 said:
sweet. i guess i cant fix my phone. good thing i only got it 3 days ago.
whats a good thing to tell them when returning my phone?
Click to expand...
Click to collapse
if your phone is not messed up then there is no reason to return it. if you keep it at stock rc29 then it will update to 1.5 firmware within 72 hours supposedly or if you still want root follow these steps in this thread. this is the probably the most reliable way to root your phone, and since it is not as automated as some of the other threads, you might learn some things about your phone in the process http://forum.xda-developers.com/showthread.php?t=442480
david1171 said:
if your phone is not messed up then there is no reason to return it. if you keep it at stock rc29 then it will update to 1.5 firmware within 72 hours supposedly or if you still want root follow these steps in this thread. this is the probably the most reliable way to root your phone, and since it is not as automated as some of the other threads, you might learn some things about your phone in the process http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
well the thing is im stuck at the G1 boot screen.
and cant get it to do anything after that.
so i might as well save me time and just return it tomorrow
G-Fetus6 said:
well the thing is im stuck at the G1 boot screen.
and cant get it to do anything after that.
so i might as well save me time and just return it tomorrow
Click to expand...
Click to collapse
do you have a modified recovery image on the phone or were you able to get that far. if not just take it by where you got it and tell them you got an ota update then wouldn't boot up past the g1 screen
david1171 said:
do you have a modified recovery image on the phone or were you able to get that far. if not just take it by where you got it and tell them you got an ota update then wouldn't boot up past the g1 screen
Click to expand...
Click to collapse
i got that it back to looking stock. so that is better if they try to do a hard reset for me.
yeah ill just tell them that an ota did it. cuz the phone is only 3 days old so im sure theyll say "oh yeah it must of been cupcake"
thanks
Ok so I think I've bricked my Nexus One. Everything was working perfect until I re-rooted it (to have SetCPU to work). I am now stuck at the loading animation screen (Google Nexus One "X"). It just keeps going and going and going. I've even tried loading my Nandroid backup and still does the same and won't work. Also I've wiped to factory default settings and tried to reinstall Modaco's 1.3 rom.
Someone please help me out...
Flash bacon add-on on top
bye!
So reinstall Modaco's 1.3, then install Bacon Add-On, and then reboot?
Yep That's the solution for some users
ok cool I'll give it a shot right now... I really appreciate it
ok at this moment it's still stuck on the animated screen... now I really don't know what to do...
Try flashing the stock rom
if u have the sdk installed, the run ddms. power on the phone usb connected to pc and see the log in ddms, paste-bin here
I have no idea on how to do that... I'm pretty much stuck at this point
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
shmigao said:
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
Click to expand...
Click to collapse
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
if you can get into bootloader mode (this is the lowest level mode you can boot into), you can not brick. Even more so if you can get into recovery (which is usually always possible if you can get to bootloader)
Good you found a way to get out of your situation.
Like i said in Android 101, you CAN NOT brick the phone unless you are updating SPL and Radio. All other stuff is just a minor inconvenience.
risterdid said:
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
Click to expand...
Click to collapse
haha, i am glad it worked! I don't even have my Nexus One in my hands (my biz trip to the States has been delayed again ), but i spend the waiting time doing my research... it's a bit like the Holiday Season, just that the gift giving day gets pushed out further and further...
glad it worked and it confirmed my research - so i can go at it with ease once i can
This is good news. OP, you should update your thread titled with the prefix [SOLVED].
ahh how'd I miss that 101 sticky... thanks for the heads up again guys.
Edited title =)
Am I bricked?
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
DrBlast33 said:
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
Click to expand...
Click to collapse
First of all, if your phone boots at all, it isn't bricked. A brick is a paperweight - it doesn't do anything. Second, this thread of 5 months old. Third, people have talked A TON about sending phones in to HTC with an unlocked bootloader, do a bit of searching.
And finally, it is very peculiar that your phone doesn't boot into bootloader or recovery. Try plugging your phone into your computer, opening your command prompt, navigate to your adb install direction, typing "adb wait-for-device reboot bootloader", and turning on your phone. Best of luck!
People should be banned for bumping 5 month old threads with posts not even related to the OP's post. Ridiculous.
@rcxquake: thanks for your suggestion. That didnt work, it just rebooted the OS. Ill keep searching for my solution and how to send to HTC if I cant find the solution.
@GldRush98: Sorry for ruining your day. I put in a google search for what I was experiencing and this was one of the top result of anyone remotely close to my issue. Yes, this is an old post, but maybe someone had this issue months ago, and had a solution I wasnt aware of.
And like I said, I found this post, although not exactly my same issue, was as related as Ive been able to find. I didn't find it so ridiculous.
If you can find my same issue on another post, then please help by pointing me to it so I can find my solution. I didn't mean to cause any issues.
Thanks
I for one am glad you posted. I don't know whether this is a solution for you or not, but I'm sometimes only able to get to the bootloader after I've had the phone off the charges, with the battery out, for some time. It varies for me between a few minutes and many minutes. It is hard to say because when I try and it doesn't work, I don't know if I've reset the time by having tried.
Anyhow, I found this thread because I'm having trouble with an N1, and one of the earlier posts may help me. Thanks for bumping the thread for my benefit.
So, the only thing holding me back was voiding the warranty and the fact I have a rogers phone (build EPE54B).... so I think I have to flash the build to the one that matches the update?
Sooooo if anyone wants to point me in the safest, easiest direction... I would appreciate it... and dos and don't would be appreciated as well. I am new to the phone an android, so feel free to dumb it down.
Does the build actually mean anything? What happens once I change it... and official updates come out? I am going to cut the grass... and then root, so help me out (preferably someone that is on rogers and has done this)
thx in advance! Froyo or Brick, here I come!
had a long day with chores and family day.... but I am back at it, first tutorial down and it seems solid...
Uploaded with ImageShack.us
onward!
Let me know how you make out. I'm on Rogers as well and am debating rooting.
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Let me know how it goes for you.
I am on Rogers and experienced EXTREME instability the moment I flashed the Froyo radio. My phone would crash randomly and frequently.
I suspect it was a problem with my hardware and have returned the phone and am waiting for a new one.
Jack_R1 said:
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Click to expand...
Click to collapse
thx jack, I appreciate it.... sorry for the thread... but in my experience... it is easier having your hand held by someone experienced.... then assuming I am following the right one, lol.... so I follow that entire thread to go from rogers to whatever build I need? heh
I will try this in approx 2 hours.... when the yard work is done!
early quick question, when I go to "CyanogenMod"
it takes me to a thread, but I do not see the download, what am I not seeing? heh
I am at this part
Type: fastboot flash recovery recovery-RA-nexus-v1.7.0.img
it says cannot load image recovery? thx
well everything was working great up until this point, tried it 100 times, heh... so now I sit and wait for guidance? thx
Mr.Kakarot, have you put the .img in the same folder as fastboot? Or, alternatively, if fastboot is in your PATH, you won't have this problem.
i renamed the image to recovery.img and that seemed to work? I will continue after supper!
Jack_R1 said:
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Click to expand...
Click to collapse
followed that first thread to a T and it worked out... had 2 minor stalls but I got through it... I am doing this stuff off and on, thx for that thread... this is going to be a STUPID question I am sure... but following that first thread, what have I done? unlocked, rooted and installed google add ons? phone looks awesome, I will do the rest after supper!
hmmm, got it, lol
done, running 2.2.... so tomorrow at work, i guess I will see if I have any issues....
now that this is done, can I re install that sense ui? What should I do or try now that I have done those 2 tutorials? thx
first off there are no 2.2 froyo/sense roms available as of yet.. so if you want to use a desire rom youre more than likely going to want to downgrade to the latest 2.1 radio that works well with your carrier/area, as froyo has its own radio and needs it to run properly.. once you downgrade.. nandroid>wipe>flash
yea, I did not know it would put me back to 2.1, lol.... went back and then back again to 2.2, lol... sense sure looked good!
Any ideas, suggestions, tips for 2.2? I installed flash! thx
How stable is your phone with the Froyo radio? Any unexplained reboots yet?
well it was quite late by the time I did it, I was playing with it, went to a few flash websites.... and no reboots or shutdowns, I also just woke up.... so I will know today after a full day work/playing, thx
one of the bugs is my camera does not work for video... so I have to update the radio, any suggestions! thx
Nope thats pretty much what you need to do is update the radio
thanks, but I am not gonna lie... still not sure which are radios, roms, senses, lol.... could you point me to the one I need.... or does it matter? thx, I just do not want to brick, obviously!
Also, I did not do this step.... is this what I need to do, or is it unrelated?
11) You should still have root, but if you want BusyBox (or lost root somehow), Cyanogen has done it again! Go back into Recovery and flash froyo-rooter-signed.zip. Then Titanium Backup will work once again.
does not sound like something I need or use, so I did not do it....
as far as stability... my 3g signal looked low all day... but I never had a dropped call, instability or any reboots/crashes.... all is well! thx
go here:
http://forum.xda-developers.com/showpost.php?p=6734240&postcount=9532
havent had problems with the older one, but am going to try the new one just to see.
anyone around?
I tried these 3 things
Step_One_Froyo_Radio_Update.zip
step-two-RoDrIgUeZsTyLe-FroYo-MCR-R16-MOD-V1.8-FIX.zip
and then i ran
2.6.34_AVS-925mV_CFS_1113Mhz_061210.zip
anytime I run setcpu, I get this error
the application process com.mhuang.overclocking has stopped unexpectedly, please try again?
"uninstalled and reinstalled, worked. thx"
I have been looking through the threads, and havent seen what I am looking for. So hopefully i will not get flamed to bad. I tried to install mikeymikes GR12, I got through the first stage of downloading the gingerbread rom to the phone through odin, but then it went south. I lost root and was unable to get back to the download screen. I then tried to use the all in one tool to root the phone, and that put me to the recovery screen where i could not use the ok button, just the volume up and down buttons. I just managed to get the download screen to come back, but i cant get anything else to work. Any suggestions on what to do, where to go from here.
Thank you for your help
I would go back to stock first. I believe your problem lies in the bootloaders. There are two bootloaders in the beginning and if you don't have the gingerbread ones installed, you won't install gingerbread properly.
I would use DesignGears One Click Odin to go back to stock and load the Froyo drivers. http://forum.xda-developers.com/showthread.php?t=731989. Make sure you open up Odin first before plugging in your phone, then hit the Start button.
Once that is done, you can try again, but read about getting the GB bootloaders installed properly before you try to flash a GB ROM. Any of the GB ROM instructions should get you there. Just make sure you know all the steps before you try it again.
Good Luck!!
I don't see why you would be flamed for your question. That is what Q&A is for and you are in a bad spot. The biggest thing to remember is to be as specific as possible when you post a question. This includes what you were trying to do, what steps you took, what was the result, when did the problem occur (which step) and what you have tried to do, if anything to fix it.
One more thing. It is always possible that the USB cable is bad or that the USB port you are plugging into (on the computer) isn't working properly. You might also want to plug into a different USB port.
Sorry these posts are broken up, but as I'm coming up with ideas, I'm posting.
Here's something you should try:
(I wrote this for Team Phoenix, hence the sig.. But it works the same with every ROM. There's a link to a very nice tutorial I suggest you follow).
http://forum.xda-developers.com/showpost.php?p=13503747&postcount=2
Hope it helps
You guys are awesome, Odin one click worked, It's on eclair, but it works! Thank you again
donkeyboy said:
You guys are awesome, Odin one click worked, It's on eclair, but it works! Thank you again
Click to expand...
Click to collapse
Glad it worked!
Make sure you read and understand before going forward with flashing
Otherwise... well.. I'll still be in here ready to help lol
BWolf56 said:
Glad it worked!
Make sure you read and understand before going forward with flashing
Otherwise... well.. I'll still be in here ready to help lol
Click to expand...
Click to collapse
Me too. If we can ... Remember not all things can be recovered from so please read everything twice before ever touching your phone.
10-4. My next question is: where do I get froyo from. Kies sees my eclair version as unregistered, so it wont update. And my ota sees an update is needed, but when i tried, the area im in has crappy signal, so the update failed and now i have to wait 24 hours to do it.
Any suggestions?
Thanks again
are you planning on flashing a custom rom?
if so updating to official froyo is A HUGE WASTE OF TIME
EDIT:are you Canadian by chance? if so check this thread:http://forum.xda-developers.com/showthread.php?t=979133
I only plan to root the official froyo right now, that is what I had before I jacked it up. I am not Canadian.
donkeyboy said:
I only plan to root the official froyo right now, that is what I had before I jacked it up. I am not Canadian.
Click to expand...
Click to collapse
Going on official froyo will get you the signature failed error (which you need the 3e recovery fix if you ever want to flash a custom ROM).
So, basically, if you want more than 2.2 official release. We suggest you don't update. If you're perfectly fine staying on 2.2 Froyo, then there's no problem lol
As for Kies, you shouldn't have any problem using Kies mini. Other than that, there is a 2.2 flash around here. I'm sure you'll find it doing a little search
I had root on my official froyo for a couple of months without a problem. Right now i cant get my phone to go into download mode, it only goes to the battery screen. If i can get to download i can make some headway
donkeyboy said:
I had root on my official froyo for a couple of months without a problem. Right now i cant get my phone to go into download mode, it only goes to the battery screen. If i can get to download i can make some headway
Click to expand...
Click to collapse
If the battery pull way isn't working. You could always go read on abd. It send SU commands and you could get your phone in downlaod mode that way.
Is there an easy way to get adb without getting the sdk. I downloaded the sdk and it keeps saying i need java, when i download the java crap it says the same thing.
donkeyboy said:
Is there an easy way to get adb without getting the sdk. I downloaded the sdk and it keeps saying i need java, when i download the java crap it says the same thing.
Click to expand...
Click to collapse
Did you reboot your pc?
Yes i did, no change
i believe you need microsoft .net framework installed also...
easy adb setup link in my sig.
files and everything needed to get going.
you may want to build a jig yourself or buy one online just in case:
MOD EDIT: No links to commercial products please.
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