Anyone willing to help out? The solution should be a sticky!
Basically like a lot of you guys I flashed the 6.16.217 ICS. But I need to send in my phone for warranty. Is it possible to flash back to 6.13.219 or 6.13.215?
yaemes said:
Anyone willing to help out? The solution should be a sticky!
Basically like a lot of you guys I flashed the 6.16.217 ICS. But I need to send in my phone for warranty. Is it possible to flash back to 6.13.219 or 6.13.215?
Click to expand...
Click to collapse
I don't believe there is a solution at this point in time. The phone will not allow an older boot image on for whatever reason. You might be better off just running SBF on the phone and sending it in without boot. They should repair it anyways and will flash the original software on it...
The actual reason is that the touchscreen went bad. So I could flash an SBF then it would look like just a dead phone, they'd flash it, then realize the touchscreen didnt work and authorize me a new Droid 4. That should do the trick! Thanks danifunker!
the power button broke on mine, i called and said it was bricked, they sent me a new one and i bricked the one to send it in
You have to send it in before you get a new one? With mine on Verizon, my phone would boot, but had lost SIM card function so I had no service, etc, and a new Sim card didn't work. I just took it in to the store, and the guy looked at it, tried a new Sim, and it didn't work, so he just ordered a new one to be shipped to me. It was running the ICS leak as well. I sent my old one back and didn't have any issues with VZW.
Sent from my Nexus 7 using Tapatalk 2
There is now a retail/stock GB fastboot thanks to Eternity.
http://forum.xda-developers.com/showthread.php?t=1622256
InfiniteIce said:
There is now a retail/stock GB fastboot thanks to Eternity.
http://forum.xda-developers.com/showthread.php?t=1622256
Click to expand...
Click to collapse
Unfortunately these don't work with the ICS Leaks. There is no way back to GB from ICS. I'd just brick it with trying to roll it back and let them deal with it. They can't tell anything more. I'd first factory wipe it though before doing the soft brick on it though.
Related
I'm returning the phone and I had it rooted with Fresh 1.0 on it.
I tried flashing the 1.29 RUU but its giving me a "ERROR[140]: BOOTLOADER VERSION ERROR"
I don't know what to do now.
I created an update.zip style update that was modeled after the RUU. However a few days later I realized that I didn't create the proper permissions for the /data folder, leaving it unwriteable from adb. If you are just returning your phone then it will work fine for you. However you will still need to manually push the old recovery image back.
PM me if you want the update.zip.
Or if you feel like you can pull it off you can try the goldcard method to remove the update that Sprint put on there to prevent you from using the RUU.
http://forum.xda-developers.com/showpost.php?p=5163950&postcount=2
do u really have to reflash it to stock?i just exchanged 2 of my htc heroes 1 was rooted and flashed to fresh 1.0 and looked nothing like the original, the other one was just rooted. they replaced both of them very fast with no problems, but ive only had the phone a week, and it was obvious that it was a manufacturers defect. just wanna know a definite answer so i know in the future.
Edit- also the employee who was exchanging my phones for new ones was really nice, she let me keep my charger my other battery and my other sd card. she said they were just going to ship them back anyway. so i returned my phones for defect and got 2 extra sd cards,chargers,and batterys. ive always had good luck with sprint lol.
flipzmode said:
Or if you feel like you can pull it off you can try the goldcard method to remove the update that Sprint put on there to prevent you from using the RUU.
http://forum.xda-developers.com/showpost.php?p=5163950&postcount=2
Click to expand...
Click to collapse
I made the goldcard and it still wont flash back to stock. It says ERROR[140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Any ideas?
pntballer1413 said:
do u really have to reflash it to stock?i just exchanged 2 of my htc heroes 1 was rooted and flashed to fresh 1.0 and looked nothing like the original, the other one was just rooted. they replaced both of them very fast with no problems, but ive only had the phone a week, and it was obvious that it was a manufacturers defect. just wanna know a definite answer so i know in the future.
Edit- also the employee who was exchanging my phones for new ones was really nice, she let me keep my charger my other battery and my other sd card. she said they were just going to ship them back anyway. so i returned my phones for defect and got 2 extra sd cards,chargers,and batterys. ive always had good luck with sprint lol.
Click to expand...
Click to collapse
A friend actually wants to buy it now and I wanted to put it back to stock. If I can't get this done, I may have to go back to bestbuy and try to get them to exchange one for me.
I never imagined that getting it back to stock would be so difficult.
I nandroid'd back to my stock shipped state. Is there any problem with leaving it rooted?
threeFiftyLi said:
I nandroid'd back to my stock shipped state. Is there any problem with leaving it rooted?
Click to expand...
Click to collapse
Shouldnt be any problem at all. If you're doubting it just take it back and swap it out.
First off there is no section to Continuum so I'm simply posting in here rather than android development. I have read up and am going out later today to buy some resistors in order to test if I can get into download mode that way.
Okay so I 1 click odin'd back to stock from firefly 2.8. I then tried to use the button combinations to get back into download mode after flashing stock. I lost the button combinations after using odin. So I one click rooted, installed terminal emulator and was able to get into recovery and download mode using that method. I began the process of flashing continuum and flashed the gingerbread bootloaders. It went fine. I9000 flash screen popped up and it booted into eclair. Stupidly I used an older update .zip to flash cwm and then flashed a 3 button fix .zip in order to get the 3 button combo back before moving forward. After I choose to reboot in cwm. Nothing happened. Phone is completely unresponsive (button combos, power, won't charge). Complete paper weight right? I already have a replacement coming from att but I just wanted some input as to how much I messed it up and if ATT can go through my files after they jtag the phone I send them back.
Bricked!! You DID NOT need the button fix on the new bootloaders, you had a working combo with the new ones its contained in the secondary bootloader its just a different series of buttons flashing the button fix mixed a gb primary bootloader and a eclair/froyo secondary= completely ****ed. No jig in the universe can save it.
Att won't be able to tell, they have to take it apart and flash it, thus erasing all evidence.
studacris said:
Bricked!! You DID NOT need the button fix on the new bootloaders, you had a working combo with the new ones its contained in the secondary bootloader its just a different series of buttons flashing the button fix mixed a gb primary bootloader and a eclair/froyo secondary= completely ****ed. No jig in the universe can save it.
Att won't be able to tell, they have to take it apart and flash it, thus erasing all evidence.
Click to expand...
Click to collapse
lol anything out of the universe that could fix it?... OH YEAH I KNOW, I KNOW! A JTAG
Then again, go for waranty 1st. Studa is right, once you mess up with the bootloaders, there's nothing you can do about it. Your phone is bricked.
studacris said:
Bricked!! You DID NOT need the button fix on the new bootloaders, you had a working combo with the new ones its contained in the secondary bootloader its just a different series of buttons flashing the button fix mixed a gb primary bootloader and a eclair/froyo secondary= completely ****ed. No jig in the universe can save it.
Att won't be able to tell, they have to take it apart and flash it, thus erasing all evidence.
Click to expand...
Click to collapse
Sent from my GT-I9100 using XDA App
Studacris,
I'm not a noob. I am running continuum on my other captivate and have flashed many times. I did try the other key combinations NOT the standard ones. They still would not work. I understand that is bricked. I figured as much. The jig was in case any of you asked if I at least tried. AlI needed to know.
I sort of did the same thing
http://forum.xda-developers.com/showthread.php?t=944418&page=63
The last post here, the guy said he used the All-in-one tool to load Continuum 5, so I tried it. Woops. At least my contract is up, may look into the Inspire.
I have not tried a jig, since ever post I've seen, if it don't even flicker with the buttons, it's a waste of time.
Later
I recently bricked mine as well. I believe you can walk into an att device repair center located in your town and let them play with it for a few minutes. After they figure they cannot fix it they will give you a replacement.
Least thats what they did years back with my htc kaiser (at&t variant). I even took apart that kaiser and messed with the internals. They said "you know it's out of warranty cause the void sticker is damaged?" I said "What? No I didn't know I didn't do that." They replaced it anyway. They are pretty nice when it comes to these things.
I currently have a bricked cappy. Gonna take it in friday.
Where in any of the GB bootloader instructions on any of the ROMS does it say flash 3 button fix. Its says read over and over how to flash and follow to the T. You failed nice job. That is why the dev write the instructions so that you can read and follow.
Sent from my GT-I9000 using XDA Premium App
BWolf56 said:
lol anything out of the universe that could fix it?... OH YEAH I KNOW, I KNOW! A JTAG
Then again, go for waranty 1st. Studa is right, once you mess up with the bootloaders, there's nothing you can do about it. Your phone is bricked.
Click to expand...
Click to collapse
HEY STUDA!!! doesnt this sound familiar??? lol dumb ass!
didnt i say what you did?
and you said what bwolf did?
couple days ago...
teach you for making me look dumb!
and +1 for dingokevin!!
keepin an eye on you!
TRusselo said:
HEY STUDA!!! doesnt this sound familiar??? lol dumb ass!
didnt i say what you did?
and you said what bwolf did?
couple days ago...
teach you for making me look dumb!
and +1 for dingokevin!!
keepin an eye on you!
Click to expand...
Click to collapse
wait what?
oops nevermind that was bwolf doing that to me the other day... lol
damn short term memory...
wait what?
Since nobody can read. I ALREADY HAVE a replacement coming. I DID read the instructions and have successfully installed roms since cognition. Mods please lock thread because everyone likes to jump down peoples throats and assume rather than reading my explanation and how I knew it was bricked already. Thanks for nothing.
Sent from my GT-I9100 using XDA App
thread locked by op request.
I need some ideas on how to fix my phone. I used to flash new roms all the time but a few weeks ago I started having problems.
When trying to load a new rom my phone would get hung at the multi colored X. Then once I got a rom to stick I would get lots of force closes when I hit the settings button.
I'm tired of dealing with it but I'm not sure how to fix it. Here are two Logcats of the phone stuck at the mulit colored X.
I would appreciate the help at getting my phone back to normal.
Logcat 1
Logcat 2
im not a expert but try unlocking ur bootloader and uploading all the update files from 2.2 froyo or something that helped me unbrick my almost brick
I would try passimg before fastboot flashing anything. If you want to know how to passimg it's in the wiki under unroot restore.
hitmanre said:
im not a expert but try unlocking ur bootloader and uploading all the update files from 2.2 froyo or something that helped me unbrick my almost brick
Click to expand...
Click to collapse
Thanks a ton! Your suggestion lead me to this thread.
http://forum.xda-developers.com/showthread.php?t=717870
I've spent hours trying everything I could to fix it. My phones been half busted for about 2 months.
I didn't think it would but it did. It brought my phone back to stock 2.1. I grabbed z4root to root it, then reflashed hboot, radio and went back to CM7 nightly. All is well with the world again.
Dude Random21 said:
I would try passimg before fastboot flashing anything. If you want to know how to passimg it's in the wiki under unroot restore.
Click to expand...
Click to collapse
Thank you, I just got it fixed using the method you described.
no problem, it sucks to have that feeling in ur stomach that u broke a 500$ device, thats why i like helping around while i can
I figured i ask here I bought a phone from a friend and he told me the phone is locked and the users gmail account option will not respond. Not sure what he did but its mine now and im not sure what to do. This is a known glitch ive heard but I just cannot get the work around it. Can someone help what steps do i need to take? He also told me "This is what my friend told me about this phone as i dont have it yet. "If you can get it out of the lock screen from the password yes it is fully functional. You can still get incoming calls and the display is damaged but does not mess with the function of the screen". My question is will factory restore help this? Or what would i need to do? I dont have the phone yet its being shipped. Is this fixable?
Once you get it, you can flash a stock rom and it will wipe everything on it, restoring to like new
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Thats grt can you send me a link to the stock rom? Also so if it is locked right now this stock rom would solve that problem? Also the password issue and gmail user account issue? I dont think its rooted does it need to be to flash the stock rom? Im new at all this with this type of phone. Since its already 2.2 does that help. And should it be 2.3.3 now?
Wait. Wait wait, before you go flashing things that could soft brick your phone. What's the build#
Sent from my SAMSUNG-SGH-I897 using xda premium
I dont have it yet im not even sure i know my friend that had it i think its just the way it is out of box dont know. All i lknow is what he told me the gmail user password issue and being locked. But can get incoming calls and if password was unlocked it would be fully functional and display damaged but doesnt mess with the function of the screen what ever that means. I just would like to think i can get this to work when i get it. I dont care if i have to start over meaning whatever is it at now just reset the whole phone from boot i guess
cell2011 said:
I dont have it yet im not even sure i know my friend that had it i think its just the way it is out of box dont know. All i lknow is what he told me the gmail user password issue and being locked. But can get incoming calls and if password was unlocked it would be fully functional and display damaged but doesnt mess with the function of the screen what ever that means. I just would like to think i can get this to work when i get it. I dont care if i have to start over meaning whatever is it at now just reset the whole phone from boot i guess
Click to expand...
Click to collapse
But it would soft brick your phone if your phone is not compatible.
Sent from my SAMSUNG-SGH-I897 using xda premium
I dont have it yet i should Tues or Wed its being shipped its an ATT phone i just dont know much about it except for what he has told me. ill try to get more info. Can this be fixed either way?
cell2011 said:
Thats grt can you send me a link to the stock rom? Also so if it is locked right now this stock rom would solve that problem? Also the password issue and gmail user account issue? I dont think its rooted does it need to be to flash the stock rom? Im new at all this with this type of phone. Since its already 2.2 does that help. And should it be 2.3.3 now?
Click to expand...
Click to collapse
b-eock said:
Wait. Wait wait, before you go flashing things that could soft brick your phone. What's the build#
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Before you start flashing, get yourself a JIG. It will fix a soft brick if it should happen. For the stock rom go into the development section and look for the KB2 thread. And make sure you read some of the stickies around here so you know the risks of flashing/modding your phone. Good luck.
Try to flash KI2 the latest gingerbread leak for the captivate!
Sent from my SAMSUNG-SGH-I897 using xda premium
How do i flash something without being rooted what if clockwork is not there? Ive done these before roms and flashing kernels all that with Hero and Droid on here. If its the same thing im sure ill get you to this development. Is the K2 the beginning right?
cell2011 said:
How do i flash something without being rooted what if clockwork is not there? Ive done these before roms and flashing kernels all that with Hero and Droid on here. If its the same thing im sure ill get you to this development. Is the K2 the beginning right?
Click to expand...
Click to collapse
Have to know. How to use odin
Sent from my SAMSUNG-SGH-I897 using xda premium
This is the latest i have heard about the phone. "You can get it unlocked. I got it to where I needed to get it unlocked by using the calling technique then going to notepad but every time I got there I messed up the steps. Is this an easy fix? Dont know build # yet but im working on trying to get that too.
Ok yes its sounds like when for hero or droid we use RSD lite and the phones drivers. Im sure i can pick up on this to get it to recovery.
No recovery just download mode.
Sent from my SAMSUNG-SGH-I897 using xda premium
I will help you.
Just let me get out my my computer so it will be easier.
Sent from my SAMSUNG-SGH-I897 using xda premium
Can we try this later this week ill PM you when i have my phone ok. I should have it by Tues Wed next week. Im just trying to get some input on what to do and link to what rom would be best for me and battery life i heard Mosiac was good and some others and Serendipity was too much battery usage. Ill learn im sure. Ill be on tommrrow
You can put the phone in DL mode with the help of volume and power buttons.
Press both volume and plug in usb= DL mode.
Just check what build is your phone and what current rom you have on it. Post more details
Instructions!
PLEASE UNDERSTAND THAT I TAKE NO RESPONSIBILITY FOR THE BRICKING OF YOUR DEVICE OR ANY OTHER UNRELATED EVENT!!!!!
IF YOU ACCEPT, GO ON AND DO THIS GUIDE!!!!
Files needed
http://forum.xda-developers.com/showthread.php?t=1129821
http://forum.xda-developers.com/showpost.php?p=17966615&postcount=214 (this is to get CWM on a stock kernel with init.d support)
http://fugumod.org/Samsung_galaxys/zImage-root.tar
http://forum.xda-developers.com/showthread.php?t=1282369
http://www.multiupload.com/8O9NYS8DE7
With phone off and not connected to the computer
Open odin KF1 ATT GB bootloaders as ADMINISTRATOR and B4 you connect phone(VERY important)
While holding volume + and - plug in USB that is connected to back of computer. That will get you download mode.
Hit start on Odin KF1 BL flasher. Let it finish and reboot you. (will boot into samsung recovery)then delete all user data.
Pull battery and disconnect phone. Close Odin BL flasher.
Open Odin3 v1.85 and place the KI2 tar.md5 in the PDA slot.(which is in a .rar file and the password is sampro.pl You have to extract it to flash with odin.) Start and wait. Let reboot and boot all the way up.
Let me know when its done and I will help you with root, cuz this post is way too long.
Ok ty yes i know the thread is long here is the latest ive heard maybe this might help a little bit. My friend told me after asking about the build #. "You can not get to that menu as the phone is locked on the password screen. Gmail will not kick it out of the screen as it is suppose to". Does this help ?
Wait till you get the phone.
Build number is inside the battery compartment, usually on a white label. It should be 4 digits, which interpret as yymm, the year and month of the time the phone was made by Samsung. Older builds came with Android 2.1 Eclair, referred to sometimes as JF6 software from Samsung. J is 2010, F is June, 6 is the 6th complete compile of the ROM.
After February, 2011, Captivates were upgraded to Android 2.2 Froyo, typically software build KB1, or KB2, 2011 February.
In May, Releases of Gingerbread, specifically for Captivate started being leaked by Samsung, nothing is official yet.
KEx is Gingerbread 2.3.3
KHx is Gingerbread 2.3.4
KIx is Gingerbread 2.3.5
Newer phones seem not to like going to older releases of Android for some reason.
Be careful, take out the SIM card and any SD card before you do anything like flashing.
Pick one of the stock ROM's first, and try to reset the phone with that. In the DEV section there are threads for each of the above. Be careful if the thread mentions flashing bootloaders, and read the directions.
I have a note here...its bricked, the owner tried flashing angelrom ICS, and bricked it.
It gets stuck when it starts writing factoryfs.img.
I have tried properly repartitioning it, installed a stock bootloader from a gt-n7000 stock rom, and that at least allowed me to get back into android system recovery. I wiped the data and cache and tried again.
I tried a stock rom that had multiple parts, and one that had the individual parts. I can flash all of the individual parts successfully but the PDA.
Anybody encounter this, and know a fix? I would really appreciate any tips or suggestions.
Just wanted to give some more information. I followed Ketan's guide to flash to stock rom, and tried multiple stock roms with the same results.
So I also tried repartioning with the proper pit file (the 16gb n7000) and that didn't work.
The only bootloader I could seem to find (because that was the next logical step to me) was "KERNEL_N7000XXKJ1_CL627135_REV02_eng_mid_ship.tar.md5" , would that be compatible with all stock roms or just a specific one?
I am sorry bro. You fried your flash drive, there is no way to revive it. The motherboard has to be replaced.
There isn't anything one can do if you flashed that kernel. If you have warranty head to Samsung service.
Yep, anilisanil is right. People who had found themselves in the same predicament tried absolutely everything, but there was no cure whatsoever. Data partition corrupted beyond repair, not even JTAG could help.
Motherboard replacement is the only thing that can be done.
anilisanil said:
I am sorry bro. You fried your flash drive, there is no way to revive it. The motherboard has to be replaced.
Click to expand...
Click to collapse
chasmodo said:
Motherboard replacement is the only thing that can be done.
Click to expand...
Click to collapse
+1
Sorry, it seems You have no option but to go service centre.
chasmodo said:
Yep, anilisanil is right. People who had found themselves in the same predicament tried absolutely everything, but there was no cure whatsoever. Data partition corrupted beyond repair, not even JTAG could help.
Motherboard replacement is the only thing that can be done.
Click to expand...
Click to collapse
How the duck is that physically possible? What an enormous embarrassment for angelom. I doubt hell ever post another kernel again...
Sent from my superior GT-N7000 using Tapatalk
Yeah...I figured it was beyond hope after reading through a lot of the threads....
I did reset the counter with a jig, and took away the yellow triangle...but I was told samsung won't warranty this model in the USA.
Thanks for your replies!
Just a little query. Whats the actual physics behind this? Like how can some software fry the drive? Just a little interested and wondered how it actually physically happened. Because my assumption before all this was that it cant be truly completely bricked (obviously i was wrong). but wondering how!
Sent from my GT-N7000 using Tapatalk