Related
Hello all,
I think I may have bricked my nexus one. It is completely my fault for attempting things that I knew little about, so flame away But after the flaming, if anyone is willing to help I would be sooooo thankfull...
I successfully rooted my phone following the instructions on this page: (all links edited with a double asterisk as I don't believe I can post links)
h**p://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Then successfully installed cyanogenmod (which is awesome!) following this page:
h**p://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
All was well, I even got the modaco desire rom up and running, and was happily switching back and forth using the recovery screen. I had nand backups for specific setups, etc.
Then I decided it would be good to know how to go back to stock, and found this page:
h**p://**w.androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
I followed the instructions to the letter (I think) except for erasing userdata (it said "failed: remote not allowed"). I thought that things would be ok, since I'd recently wiped, so I followed the page till the end.
The phone rebooted, and I got the original nexus boot animation - but it's in an endless loop! What's worse, it that now when I try to go to the bootloader or recovery mode, I get the exclamation triangle with the little android.
Is there any way through a command prompt (or other method) that I can fix this? I tried to re-flash the RA recovery image through the command prompt, but the response was, "waiting for device."
ANYTHING that anyone can suggest to help, I would be so thankful! I've been loving the nexus, and hate to think that I crippled it
Thanks in advance,
Randy
I doubt its bricked.
Noticed you didnt mention that fast boot doesnt work? (power button+trackball) try it.
Once you get to fastboot you can flash any ROM back. (fastboot flash **** commands from a command shell)
Did you ever perform a Nand Backup from Recovery?
It's not bricked, the only way to brick is to interrupt power when flashing a Radio image
Connect phone to PC. Open command prompt.
adb reboot recovery
Wipe, reflash.
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
nexus5894 said:
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
Click to expand...
Click to collapse
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Paul22000 said:
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Click to expand...
Click to collapse
............................
It worked!!!!!
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Randy Malkoski said:
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Click to expand...
Click to collapse
Glad to hear it. You learn the most by trial and error.
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
revonomics said:
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
Click to expand...
Click to collapse
Tell me what i need to download again and how to go about it...i really need my phone working again ((((
I decided to go ahead with the TW firmware upgrade. Everything seemed to be going fine until I tried to install it and it told me there was an error and I needed to hook it up to Kies first. I had already been using Kies with it on my Macbook for a couple weeks now so I went ahead and plugged it in. Kies recognized it as usual and all the information came up.
So I went on and tried to install again and it said it needed to reboot.
It reboots and comes to the Samsung Galaxy Tab 10.1 screen like normal (right before it starts the galaxy animation). Next thing I know it comes to a screen that looks like the attached images! I immediately unplugged it from Kies and shut it down. Every time I start it back up it does the same thing. I honestly have NO idea what to do. I can't even return it as it's past the 14 day period and I (stupidly) didn't buy Staples' bogus $160 insurance.
I was not rooted before. This was a stock tab that I bought at staples. It had the firmware 4.24 when I bought it, I think.
Please, any help is appreciated. I tried doing firmware recovery in Kies but the pop up comes up in Korean and I have no idea what it says...
Edit: More info. I'm not the only one with this problem. Two other people have posted on AndroidPolice about this. http://www.androidpolice.com/2011/08/04/samsung-galaxy-tab-10-1-wifi-touchwiz-ux-update-is-now-live/
The software is definitely running underneath all that mess but it's literally impossible to see what is going or to touch anything.
I guess this thread is about the same issue
http://forum.xda-developers.com/showthread.php?t=1203610
Thanks, I'm checking the thread out now. I probably should have searched more than just Google before posting but I freaked out when it happened.
No need to freak out . we have xda and dev to solve all our problems
i have exactly the same problem as you... what should i do now?
I get the same screen but after rebooting! pfft it's making me really sad :\
I'm sorry but I tried reading this http://forum.xda-developers.com/showthread.php?t=1171089 and couldnt understanding what should I do!
What CWM + my device is not rooted, all I could understand is that the thread contains instructions on how to root your device..
I just want my normal screen back!
Please tell me what to do in simple english :\
And now I did a wipe and the stripes are gone, but the screen is black instead :\ still not working. Please help me!
Are you sure you didnt sit on it?
Amal Kadi said:
I'm sorry but I tried reading this http://forum.xda-developers.com/showthread.php?t=1171089 and couldnt understanding what should I do!
What CWM + my device is not rooted, all I could understand is that the thread contains instructions on how to root your device..
I just want my normal screen back!
Please tell me what to do in simple english :\
Click to expand...
Click to collapse
haha i had the same problem go look at my threat that was posted above. in thier someone posted instructions on what to do the link you posted contains the download to the things needed heres a basic rundown of what you need to do
install clockwork recovery mod "CWM" to replace your bootloader.
download and install stock 3.1 and you should have your tab back to normal.
my help thread has the instructions to instal CWM
tonyurquiza said:
haha i had the same problem go look at my threat that was posted above. in thier someone posted instructions on what to do the link you posted contains the download to the things needed heres a basic rundown of what you need to do
install clockwork recovery mod "CWM" to replace your bootloader.
download and install stock 3.1 and you should have your tab back to normal.
my help thread has the instructions to instal CWM
Click to expand...
Click to collapse
So I need to follow all the steps for rooting except the last one which is the actual rooting? Great thanx! Do I need to use Kies? My current computer is Mac but I guess I need to download those things to a Windows machine to make it work, right?
Thank you very much
I had the same problem. I upgraded the update on my non-rooted tablet and got the funked up video mess. Per instructions from Samsung support, I hard booted to the recovery menu (power+vol down, then power up, down on download screen) and did the factory wipe. After that I ended up with the black screen. I could tell things were working in the back but couldnt see a thing. I figured I would throw it on the Kies and it saw that there was a factory upgrade so I let the Kies run through it and it works fine now.
Dont know if this will help w/other but it worked for me.
Hello All,
I have run into a problem with my Heroc not wanting to boot. Some background:
ROM: CM7
Kernal: Jaybob's recent Kernal
Mods: Firerats
All was fine and dandy until yesterday, when I decided to reboot the phone (with a full battery charge). The phone shutoff and when restarted was stuck at the HTC screen. I've tried several times to get into recovery but it hangs at the HTC Screen.
I can enter Fastboot/Hboot. I did some digging and tried to unroot by using this method: http://forum.xda-developers.com/showthread.php?t=988741
Method 1, loading the imaging on the sd root and loading. Everything loaded fine but when I reboot it still hangs at the HTC screen. I have not tried to RUU being that I am on a Mac and don't have access to a PC at the moment. So RUU will be done later tonight hopefully, but I don't expect different results.
It seems like I have some messed up memory and its not allowing me to boot. Does anyone know of a fix? I'm not desperate because its time for an upgrade. I just wanted to hold off on using it until January when Sprint holds their press conference, assuming its an Android device. I'd like to see what I could get versus the phones on the market now.
Any help is appreciated, thanks in advance
srkmagnus said:
Hello All,
I have run into a problem with my Heroc not wanting to boot. Some background:
ROM: CM7
Kernal: Jaybob's recent Kernal
Mods: Firerats
All was fine and dandy until yesterday, when I decided to reboot the phone (with a full battery charge). The phone shutoff and when restarted was stuck at the HTC screen. I've tried several times to get into recovery but it hangs at the HTC Screen.
I can enter Fastboot/Hboot. I did some digging and tried to unroot by using this method: http://forum.xda-developers.com/showthread.php?t=988741
Method 1, loading the imaging on the sd root and loading. Everything loaded fine but when I reboot it still hangs at the HTC screen. I have not tried to RUU being that I am on a Mac and don't have access to a PC at the moment. So RUU will be done later tonight hopefully, but I don't expect different results.
It seems like I have some messed up memory and its not allowing me to boot. Does anyone know of a fix? I'm not desperate because its time for an upgrade. I just wanted to hold off on using it until January when Sprint holds their press conference, assuming its an Android device. I'd like to see what I could get versus the phones on the market now.
Any help is appreciated, thanks in advance
Click to expand...
Click to collapse
You definitely need to do an RUU. No way around it. know it sucks starting fresh again but it'll solve all these problems you have. If your s-off you can also do the RUU from Hboot but it's better to do it from PC as I have learned. Good luck man.
thanks a lot! om going to give it a try later tonight when i have access to a pc. Im not so much worried about starting fresh than I am losing the phone and using my upgrade now... I have a curve laying around and started to thing about using that for a while until I see something I like.
i will report back tonight or tomorrow when i am up and running again.
I had the same problem awhile back and it took me forever to get it fixed but I finally got it fixed. Search the forum for " stuck at HTC screen and look for the threads I started for as possible fix. I will try to find it and post the link here.
http://forum.xda-developers.com/showthread.php?t=1305479&page=3
My last post describes how I finally fixed my Hero, but you should read the whole thread.
williams1978 said:
I had the same problem awhile back and it took me forever to get it fixed but I finally got it fixed. Search the forum for " stuck at HTC screen and look for the threads I started for as possible fix. I will try to find it and post the link here.
http://forum.xda-developers.com/showthread.php?t=1305479&page=3
My last post describes how I finally fixed my Hero, but you should read the whole thread.
Click to expand...
Click to collapse
Thanks. I will give it a look.
I read through the thread and it looks like you passed the black htc screen and got to the white one. I can't get passed the black and adb doesn't pick up the phone at this point. I'm still waiting to try the RUU and see if HTC sync picks up the device.
Very resourceful thread and I'll be sure to give all the suggestions a try before giving up.
HTC sync won't pick up the device and I don't think any other option will work since I don't have ADB access. I'm just gonna bite the bullet and look into a replacement.
Ok to verify your phone does boot at least to the bootloader? If so I have a doffeemr approach for you to take
私のEVO 3Dから送信される。
dastin1015 said:
Ok to verify your phone does boot at least to the bootloader? If so I have a doffeemr approach for you to take
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
yeah. I can get into bootloader and fastboot. whatcha got?
I have a new phone on the way. Amazon has ET4G for $79, too good to pass up so I used my upgrade. Ill still be curious to know how I can get the Hero up and running.
srkmagnus said:
yeah. I can get into bootloader and fastboot. whatcha got?
I have a new phone on the way. Amazon has ET4G for $79, too good to pass up so I used my upgrade. Ill still be curious to know how I can get the Hero up and running.
Click to expand...
Click to collapse
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=804692
I used a flashable RUU based off Flipz source and still no luck. I will give your RUU a try later tonight... Thanks
No luck. The phone freezes at the HTC screen and fails to go any further. :-(
srkmagnus said:
No luck. The phone freezes at the HTC screen and fails to go any further. :-(
Click to expand...
Click to collapse
i had same kinda deal from a bad radio flash
if you still have fastboot do
"fastboot erase system -w"
"fastboot oem boot heroc.hboot-1.46.2000.zip"
you may need to rename the file to HBOOT.
if that dose not work unzip the file take the hboot img and place on sdcard and place where your fastboot files are like in android/platform-tools.
this made a deference for me.
then try fastboot flash img hboot.img
this is what i went through here
http://forum.xda-developers.com/showthread.php?t=1086125
good luck if i can help let me know.
Thanks for the help oostah. I haven't been able to get ADB to recognize the device. When I get home I'll try it again and remove the hboot as suggested and give that a try.
Now that ICS is in beta for the Heroc my phone decides to crap out on me and I can't enjoy the hard work put in by the developers. Nonetheless, I am much appreciative of all the support put into the Heroc and have learned a lot from this community
I'll report back tonight with my results.
srkmagnus said:
Thanks for the help oostah. I haven't been able to get ADB to recognize the device. When I get home I'll try it again and remove the hboot as suggested and give that a try.
Now that ICS is in beta for the Heroc my phone decides to crap out on me and I can't enjoy the hard work put in by the developers. Nonetheless, I am much appreciative of all the support put into the Heroc and have learned a lot from this community
I'll report back tonight with my results.
Click to expand...
Click to collapse
you are welcome i have been there before.
your phone may not recognize ADB but it may still take fastboot commands. that was one thing that drove me crazy is that i could fastboot but not adb. let us all know how it goes.
I did "fastboot-mac devices" and got my device to show up, so it registered. however, when I go to erase system I get an error, "remote: not allowed". The same occurred when trying to flash the .zip and img files separately as suggested . At one point the devices started vibrating like crazy and shut off, the led started to blink green. I did get it back into Fastboot, but now it won't turn on.
Thanks for the help though It was already replaced and the new phone should be here tomorrow. I'm just going to miss the Hero since it was my first Android device and I learned a lot in this forum.
Thanks!
srkmagnus said:
I did "fastboot-mac devices" and got my device to show up, so it registered. however, when I go to erase system I get an error, "remote: not allowed". The same occurred when trying to flash the .zip and img files separately as suggested . At one point the devices started vibrating like crazy and shut off, the led started to blink green. I did get it back into Fastboot, but now it won't turn on.
Thanks for the help though It was already replaced and the new phone should be here tomorrow. I'm just going to miss the Hero since it was my first Android device and I learned a lot in this forum.
Thanks!
Click to expand...
Click to collapse
i still have one of my hero's that i let people play with when the come over. it still runs off wifi so they can play games yous gtalk what ever be nice to get it up and running for experience and fun lol now that your not in a have to mode.
do you have a nan back up from a sd card any place like on your pc if so look for your clockworkmod folder look for backups and you should see your backups open one of them you will see
boot
system
data
recovery
sd-ext
cache
they will be img files you can place them on your sd card and fastboot them back to the phone
"fastboot flash img boot.img"
"fastboot flash img system.img"
and so on
or
"fastboot boot img boot.img"
"fastboot boot img system.img"
and so on
or you can let it RIP
good to know. I'll give that a try if I can get it booted. I'm thinking its dead and needs a charge to get back into fastboot. I'd love to get it back up and running as a learning experience more than anything. I wont have time until tomorrow or Thursday . I will report back when I give it a try.
srkmagnus said:
good to know. I'll give that a try if I can get it booted. I'm thinking its dead and needs a charge to get back into fastboot. I'd love to get it back up and running as a learning experience more than anything. I wont have time until tomorrow or Thursday . I will report back when I give it a try.
Click to expand...
Click to collapse
will the charge light come on when plugged in if not there is a trick take a old usb cable cut one end off on the battery there are
= and - becare full connect the red wire to + and black to - tap them down so they dont move. let it set for 2 1/2 hrs should be good to go.
I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.
live_free said:
I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.
Click to expand...
Click to collapse
what sbf did you flash? is it att bell etc? need some more info to help you out.
aideneisley3 said:
what sbf did you flash? is it att bell etc? need some more info to help you out.
Click to expand...
Click to collapse
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204
live_free said:
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204
Click to expand...
Click to collapse
STEPS:
1) Have the correct Motorola drivers installed for your PC (i.e. x32-bit or x64-bit).
2) Download RSD Lite (Links above) & install on your PC.
3) Choose a sbf file to download and flash from Motorola Atrix Firmware Super Thread: http://forum.xda-developers.com/showthread.php?t=1125944
If you are currently running firmware 4.5.91, I suggest that you only flash back to this firmware version. Flashing back to a eariler sbf/firmware version may have unintended consequences, the most serious of which is bricking your device.
*Note: U.S. AT&T users should only flash AT&T sbfs, internationl users should only flash their particular sbf versions.
4) Read the above sbf hints, trick, etc. to help prevent RSD Lite problems/errors.
5) Open RSD Lite and load the sbf file that you downloaded.
6) Put your device in RSD Protocol Mode by powering OFF, and upon powering back ON, hold both the power button and the volume UP button. Device should now say "Entering RSD Protocol Mode."
7) Connect your device to your computer via the usb cable, and select your device by clicking/highlighting it in RSD Lite.
8) Select START in RSD Lite and let the sbf flash process fully complete before disconnecting the device from the PC. There will be several reboots and the process make take 5 - 10 minutes to complete a FULL sbf flash.
9) If you have any errors or problems as a question, prefably in the Q&A section.
this is what i have done and worked for me! good luck
i copied this from the noob guide found here http://forum.xda-developers.com/showthread.php?t=1154600
Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.
live_free said:
Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.
Click to expand...
Click to collapse
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!
aideneisley3 said:
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!
Click to expand...
Click to collapse
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.
live_free said:
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.
Click to expand...
Click to collapse
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
aideneisley3 said:
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
Click to expand...
Click to collapse
Yes. Same exact problem.
live_free said:
Yes. Same exact problem.
Click to expand...
Click to collapse
oh ok well then i'd have to agree with you then maybe it is a hardware problem... sorry i wasn't much help.
it wouldn't hurt as a last ditch effort to use motorola's software update program that you can download from their site it will tell you that there is no update and ask if you want to use it to restore your phone basically it reflashes it...
haha thats all i got. maybe someone else could offer more help.
good luck! =]
live_free said:
I did everything properly and now am in a boot loop, and I've done a battery pull.
Click to expand...
Click to collapse
apparently not.
in his defense replacement phones are refurbished (cough... broken and maybe fixed to like new). motorola gave me a replacement with broken senor so the screen didn't turn off when i was in a call and that was out of the box and when they replaced that one the screen was messed up it had super bright spots all over the screen so it is possible that it is moto's fault.
not saying it is moto's fault but that it is possible lol
My vibrant is stuck on a boot loop, i was in the middle of installing ics and now it is in a boot loop. What can i do, if you want i can post of video of this boot loop for any advice.
lovenokia said:
My vibrant is stuck on a boot loop, i was in the middle of installing ics and now it is in a boot loop. What can i do, if you want i can post of video of this boot loop for any advice.
Click to expand...
Click to collapse
Just because you didn't care to read ANY of the stickies around... I'll make sure you do, i'll give you instructions but lets see if you can go back a page and click the stickies to learn how to do all of this:
you will need to get into download mode, and odin - this is the safest and recommended route
if you want to take a bit of a risk you can try to go into recovery and flash the ROM you were in before - this can lead to more bootloops/brick
here is the video
http://www.youtube.com/watch?v=cwNzHqezAuU&feature=youtu.be
If only there was a guide that explained what to do when you get a bootloop while installing ICS. Hmmm. (Hint: see my sig).
If that doesn't work, rider's is the way to go.
Edit:: saw that you posted your video. That is a fast ass bootloop. Hit your thanks button by accident. Anyways try pulling your battery and booting into recovery and reflashing ICS again over itself. Did you wipe and factory reset?
i am a dumbass that followed a youtube video tutorial congratulations to me(pissed >(, i went straight from eclair to ics. wopdee do. I got odin in a ".rar" file and cant open it, but i prob have the wrong odin then right?
Not sure about your Odin file but check my guide for clear instructions. Need to go from 2.1 to CM7 to ICS flavor.
Alright i am lost and pissed? what should i do now, (i did my touchpad just fine to ics) to let you know that i am not a complete n00b about this, but the vibrant is not liking me...
ok, now that i've seen the video this is not any normal BOOT LOOP.
What exactly did you do to get this? Which flashing procedures did you look at?
Can you at all get into recovery/download mode?* most important question*
Do you have Froyo Bootloaders or GB bootloaders? (if you don't know what these are and have not messed with bootloaders you are on Froyo.)
I have just read what the recovery says through the video
It pretty much says that it is trying to flash ICS PASSION, but it cannot because your sdcard is either a) wiped b) not mounted c) the ICS PASSION file is corrupted and/or ics passion has been deleted somehow.
-after reading some latest posts from you, i'm sorry for making you feel like a dumbass but you did not read the instructions, mainly the stickies, and did not follow the instructions on how to get to ICS from eclair. That is why. Many do not and I prefer not to give any help at all to people who can't help themselves, but I understand your situation and i'll try to help. Sorry for offending you if I did, its just that some people need to be treated that way so they open their eyes and start reading around.
i understand that, but i did a battery pull and the samsung vibrant is still doing the same thing, when i hold power and volume down it stays at the "vibrant" thing but that is it, i can do anything else but watch it boot loop.
okay, i did a wipe on my sd card before installing, let me try to find the youtube guide
here is the guide that i followed, i just went from step three onward because it was rooted but nothing else
http://www.youtube.com/watch?v=iryi3TzylN4
Rider, see if you can help him out. My boy just woke up. Let me get him back to sleep and ill be back after these messages.
PS I just PM'd him the CM7 Rom.
thanks, i hope someone can help me out.
lovenokia said:
thanks, i hope someone can help me out.
Click to expand...
Click to collapse
read this post, i think you missed it, answer the questions while i watch the video guide and see if theres anything wrong in there.
xriderx66 said:
ok, now that i've seen the video this is not any normal BOOT LOOP.
What exactly did you do to get this? Which flashing procedures did you look at?
Can you at all get into recovery/download mode?* most important question*
Do you have Froyo Bootloaders or GB bootloaders? (if you don't know what these are and have not messed with bootloaders you are on Froyo.)
I have just read what the recovery says through the video
It pretty much says that it is trying to flash ICS PASSION, but it cannot because your sdcard is either a) wiped b) not mounted c) the ICS PASSION file is corrupted and/or ics passion has been deleted somehow.
-after reading some latest posts from you, i'm sorry for making you feel like a dumbass but you did not read the instructions, mainly the stickies, and did not follow the instructions on how to get to ICS from eclair. That is why. Many do not and I prefer not to give any help at all to people who can't help themselves, but I understand your situation and i'll try to help. Sorry for offending you if I did, its just that some people need to be treated that way so they open their eyes and start reading around.
Click to expand...
Click to collapse
----
Okay..... so after watching that guide. I have never seen ANYONE using that method, mainly because he didn't flash ANY kind of CM7 kernel etc.
Most of his instructions were right, but he just did something on his phone that seemed unusual, but i guess worked for him...
xriderx66 said:
ok, now that i've seen the video this is not any normal BOOT LOOP.
What exactly did you do to get this? Which flashing procedures did you look at?
Can you at all get into recovery/download mode?* most important question*
Do you have Froyo Bootloaders or GB bootloaders? (if you don't know what these are and have not messed with bootloaders you are on Froyo.)
I have just read what the recovery says through the video
It pretty much says that it is trying to flash ICS PASSION, but it cannot because your sdcard is either a) wiped b) not mounted c) the ICS PASSION file is corrupted and/or ics passion has been deleted somehow.
-after reading some latest posts from you, i'm sorry for making you feel like a dumbass but you did not read the instructions, mainly the stickies, and did not follow the instructions on how to get to ICS from eclair. That is why. Many do not and I prefer not to give any help at all to people who can't help themselves, but I understand your situation and i'll try to help. Sorry for offending you if I did, its just that some people need to be treated that way so they open their eyes and start reading around.
Click to expand...
Click to collapse
no i cant get into recovery mode
i did not mess with any bootloaders
i wiped, unmounted as in not plugged in then yes, i installed zip from phone unmounted
Dude that video is wack. He pirates one version of CWR but once it boots up is a completely different version. Check out the numbers on top. The edits are terrible. Cuts out some pretty huge points. Plus he starts out with Passion beta 1 on his settings screen before he edits back to show you how to do it, but ends up with RC1.
so am i screwed? if i am than thanks for trying to help me though.
No you are not screwed. Odin back to stock 2.1 and then follow the instructions. Don't sweat getting Gingerbread bootloaders for now. Get your phone in download mode.
You probably won't know this but even if you phone doesn't show download mode on its screen, you want that yellow COM box to light up in Odin. Once you see that, profit.
Woodrube said:
Dude that video is wack. He pirates one version of CWR but once it boots up is a completely different version. Check out the numbers on top. The edits are terrible. Cuts out some pretty huge points. Plus he starts out with Passion beta 1 on his settings screen before he edits back to show you how to do it, but ends up with RC1.
Click to expand...
Click to collapse
Yeah i'm completely confused from the video as well...
lovenokia said:
so am i screwed? if i am than thanks for trying to help me though.
Click to expand...
Click to collapse
First read the post above this and try to get odin to light up yellow, if it does, no JIG needed, odin and you should be good. If that does not happen, then you will need a JIG.
Since you cannot get into recovery or download mode, I would try a JIG before claiming that your phone is a brick.
does the odin and stock rom from the video that i used work? or where should i get the odin and stock rom this time without effing up?