Related
Ok, I was restoring my phone to stock with odin following these stpes
Disable Voodoo
Odin to eugenes froyo that wont brick
sticks at vibrant screen
tried odining to JFD
odin completes but still hangs at the vibrant screen
I have tried with and with out repartition checked and I am able to enter and exit download mode freely, I have tried 3 differnt versions of odin and 2 different downloads of the pda and pits. Any help would be great.
EDIT, Odin is finishing at the pass stage when the phone attempts to boot Currently flashing the JI6 seeing if it works.
Still not getting anywhere, I have now tried to odin to eugenes froyo, JFD, JI6, all which end the same with out a boot screen, I can get download but no recovery.
From my understanding when you flash eugenes froyo that wont brick the boot animation should change to the international one, mine has not done that so I am starting to wonder if there is an issue with the flashes themself.
How long did you wait after flashing the stock firmware? The first boot usually takes a while after an Odin. Did Odin finish flashing everything to the point that it said restart in blue?
You can find instructions to revert to stock http://forum.xda-developers.com/showthread.php?t=734475
I've gotten myself out of some pretty bad "bricks" with JFD and ODIN... make sure you also use the stock .pit file and you can check repartition, use JFD and should fix you right up.
I have waited for 10-15 minutes after it says restart and then sometimes after it says pass, and I have done to jfd and stock pit.
left phone at boot fell asleep woke up hr or so later still at vibrant screen, still cannot access recovery but can access download mode.
To OP. What custom rom did you run before flashing back to stock? Have you recovered?
iynfynity said:
To OP. What custom rom did you run before flashing back to stock? Have you recovered?
Click to expand...
Click to collapse
I was on axura the newest one and did not like it that much tbh had tons of processes starting nonstop and was constantly down to 35m of memory while idle. No I have not recoverd, I have flashed every combo I can think of with ODIN but alas have had no luck.
Currently it is being warrantied out for a free replacement.
ionic7 said:
I was on axura the newest one and did not like it that much tbh had tons of processes starting nonstop and was constantly down to 35m of memory while idle. No I have not recoverd, I have flashed every combo I can think of with ODIN but alas have had no luck.
Currently it is being warrantied out for a free replacement.
Click to expand...
Click to collapse
orage
So tired.... I am in the same boat. But I get to flash Eugenes froyo but i have 0 room in app storage. Then When I try to Odin to stock JFD and stock .pit it all goes well untill I get to recovery and it tells me in red text "data wipe failed"
The phone reboots and goes black after the galaxy s animation.
You think samsung will fix it for me? I go the phone in July 2010.
To OP.
have you tried flashing eugenes froyo that doesn't brick? I can't understand why a lot of these bricks are happening right now. Especially when you do flash your phone back to stock.
iynfynity said:
To OP.
have you tried flashing eugenes froyo that doesn't brick? I can't understand why a lot of these bricks are happening right now. Especially when you do flash your phone back to stock.
Click to expand...
Click to collapse
Yes read the first post it says what i have flashed.
Charlie Brown said:
orage
So tired.... I am in the same boat. But I get to flash Eugenes froyo but i have 0 room in app storage. Then When I try to Odin to stock JFD and stock .pit it all goes well untill I get to recovery and it tells me in red text "data wipe failed"
The phone reboots and goes black after the galaxy s animation.
You think samsung will fix it for me? I go the phone in July 2010.
Click to expand...
Click to collapse
How would I know if samsung will fix it.. I called tmobile said it got bricked while doing JI6 boom problem solved. Their support is not that great though he was having me try to access root by calling it a secert master menu, then asked if i tethered my comp to it but his definition of tether was syncing files I was just playing dumb and letting him ask me his questions
ionic7 said:
How would I know if samsung will fix it.. I called tmobile said it got bricked while doing JI6 boom problem solved. Their support is not that great though he was having me try to access root by calling it a secert master menu, then asked if i tethered my comp to it but his definition of tether was syncing files I was just playing dumb and letting him ask me his questions
Click to expand...
Click to collapse
Rooting your device and flashing custom roms onto it voids your warranty from t-mobile. You are wasting your time trying to see if they will help, This is NOT in their job description. They might laugh at you.
@OP Try flashing to a TRUE stock firmware, I personally would not flash from a custom rom to another custom rom, does that make sense? You should go back to t-mobiles legit 2.1. There is a link in the Bible here under the Dev forum. But, The link is broken. So Ive uploaded it here http://www.mediafire.com/?8kw71bx06an0vwg
Don't give up on odin yet, try things like changing your usb ports on the computer, this has worked for me. I also have a video tutorial using odin, it might be of some help to you. http://forum.xda-developers.com/showpost.php?p=10207377&postcount=1
Good luck!
ionic7 said:
Yes read the first post it says what i have flashed.
Click to expand...
Click to collapse
try that again.
Sent from my SGH-T959 using XDA App
Im having the same issue with, "Data Wipe Failed" and have 0.00 space in Application storage but my phone reboots into eugenes 2.2 perfectly fine and works, but the application storage seems to be empty still...very frustrating.
cvibe88 said:
Rooting your device and flashing custom roms onto it voids your warranty from t-mobile. You are wasting your time trying to see if they will help, This is NOT in their job description. They might laugh at you.
@OP Try flashing to a TRUE stock firmware, I personally would not flash from a custom rom to another custom rom, does that make sense? You should go back to t-mobiles legit 2.1. There is a link in the Bible here under the Dev forum. But, The link is broken. So Ive uploaded it here http://www.mediafire.com/?8kw71bx06an0vwg
Don't give up on odin yet, try things like changing your usb ports on the computer, this has worked for me. I also have a video tutorial using odin, it might be of some help to you. http://forum.xda-developers.com/showpost.php?p=10207377&postcount=1
Good luck!
Click to expand...
Click to collapse
have changed usb cord, port, computer, have flashed jfd ji6 froyo that wont brick, 512 pit,513 pit,and they have not laughed at me in anyway they are sending my new phone now and a g2 to try out soo either way I have something soon. I also was going from axura to stock to a custom rom not from one to the other and I do know how to use odin, I know what I am doing just need help figuring this one out has to be something im missing or its just not gonna work. 50 odins and nothing kinda says it all.
I am in the same boat.. tried ODIN + stock ROM from various sources, nothing seems to work.. am I out of luck ??
Okay, so after installing the kang build 25 ICS for the vibrant, everything went fine. Randomly I get a random reboot and my phone says there was an "encryption error" and that I have to do a factory reset. Since I already had everything backed up, I didn't mind the data wipe. When it went rebooted the CWM screen came up and started wiping everything but when it got to the "formatting data" part, it failed. I tried this many times and it kept failing... SO, I decided to ODIN back to JFD. After doing so, all I get is the Vibrant screen, then an instant shut down. I even tried Eugene's old No Brick Froyo PDA, then tried to reinstall the JFD image, but got no luck.
Question is: What should I do now?
Any help will be GREATLY appreciated. Thanks!
Its a little involved but It's all I could find to help buddy
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Perhaps it could be a bootloader problem? If you're sure you are doing Odin right, including repartition with the pit file, you could look at your SBL.
.
Sorry but what is SBL?
lolrus101 said:
Sorry but what is SBL?
Click to expand...
Click to collapse
I dont know how to explain it very well lol but to check if the rom you are trying to odin has the sbl in it. Rename it and put a .zip at the end. Then extract to see if its in there it should be named "sbl". To change it back simply delete the .zip off the original file.
JFD
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Try odining a rom that has the sbl file in it thats probably why its not working.
---------- Post added at 04:14 AM ---------- Previous post was at 04:09 AM ----------
Here http://forum.xda-developers.com/showthread.php?t=1278683 you need to have java installed to open it
Just tried the Heimdall thing. No luck. As soon as it says rebooting, it goes to the vibrant screen, then the battery charging screen, then continues to bootloop. Same thing happened with Odin
why don't you try what I did
http://forum.xda-developers.com/showpost.php?p=23056603&postcount=10
lolrus101 said:
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Click to expand...
Click to collapse
The SBL is the Secondary Boot Loader, which is loaded by the Primary Boot Loader.
I haven't personally encountered any roms which also flash bootloaders.
I did manage to get my phone bootlooped in some weird way which apparently could only be fixed by reflashing the SBL. Note: flashing bootloaders is more dangerous than regular roms.
I am presently running a GB SBL from this thread:
http://forum.xda-developers.com/showthread.php?t=1117990
ian577416 said:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Click to expand...
Click to collapse
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Flashed the GB bootloader and no luck either . Flashed back to the froyo one, and got the data wipe error again, the phone rebooted, and now its at "KERNEL PANIC - UPLOAD MODE"
AdamOutler said:
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Click to expand...
Click to collapse
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
lolrus101 said:
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
Click to expand...
Click to collapse
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
cashmundy said:
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
Click to expand...
Click to collapse
SO the thing is I used the GLITCH kernel with vibrant build 25... I dont think I was supposed to... could that have caused the problem? maybe a voodoo problem?
There are two glitch kernel series that I know of, one for CM7 and one for CM9 and ICS (I think, not sure, that all ICS builds and CM9 use the same basic filesystem scheme).
All stock builds use a Samsung FS scheme which is different from the two above. So there are at least three mutually-incompatible families of FS+kernel pairs.
I used the CM9 kernel I think...
After the installation went fine, I got the encryption error which told me to reboot. as soon as I did, I got the Data wipe fail. Any ideas?
Encryption Error
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
tabthelab said:
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
Click to expand...
Click to collapse
If you are still able to access Clockworkmod Recovery CWM (NOT STOCK RECOVERY) then try this:
http://forum.xda-developers.com/showthread.php?t=1447303
Otherwise just give up. There is currently no fix for this bug as of now.
This is really getting out of hand ICS rom devs should put a big caution sign on their thread(s) stating the following:
WARNING THIS ROM WILL BRICK YOUR DEVICE!!!
Goodluck... in the meantime find yourself a spare phone like i did cuz you certainly ain't fixing this one.
Sent from my Galaxy Nexus using XDA
mother of god
I hope this helps you. I finally, after hours of nothing, tried to use Odin to flash to 2.2 froyo. cha ching. got in.
tar file I used here: http://forum.xda-developers.com/showthread.php?t=833024&page=49
worked for me. I hope it helps you
Good evening,
Thanks for taking the time to read this.
I rooted and unlocked my phone and then tried installing a wrong CM10. Then I installed the stock ROM again so that it would at least work. That succeeded.
However, a popup came offering a OTA update and I hit yes without thinking. It rebooted and stayed at boot loop.
Now when I try using ODIN to reflash the stock ROM it does so, reboots, and stays at the boot screen where the LTE and moving stuff shows up after the Samsung Galaxy Note 2 in white text screen. Please, I need this fixed urgently as that's my work phone.
I've tried flashing the rooted stock rom and that doesn't work either. When I try to re-root/unlock it says "Firmware problem please connect to Klies" or something along those lines. I can't boot into recovery mode either. The android shows up and a bar and then it reboots when it's close to finishing the boot into recovery.
bump
I'm confused, where is your phone now. Boot loop, the firmware upgrade problem or other?
Sent from my SCH-I605 using Tapatalk 2
Really basic question here, how long have you let it sit on the boot animation screen? Sometimes it takes a very long time for first boot, especially if davlik was wiped.
fbernar said:
bump
Click to expand...
Click to collapse
I just read a post about someone in the same situation that said after about 30 attempts!! with Odin it did finally work.
Also, I have no affiliation with these guys but they seem to know what they are doing and doing it for a reasonable price: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-2-jtag-brick-repair/
Good luck.
Geezer Squid said:
I just read a post about someone in the same situation that said after about 30 attempts!! with Odin it did finally work.
Also, I have no affiliation with these guys but they seem to know what they are doing and doing it for a reasonable price: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-2-jtag-brick-repair/
Good luck.
Click to expand...
Click to collapse
They're the people to use if needed
Sent from my SCH-I605 using Tapatalk 2
jacampb2 said:
Really basic question here, how long have you let it sit on the boot animation screen? Sometimes it takes a very long time for first boot, especially if davlik was wiped.
Click to expand...
Click to collapse
I've let it sit for like an hour in a boot loop.
kintwofan said:
I'm confused, where is your phone now. Boot loop, the firmware upgrade problem or other?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Boot loop if I try to go to stock ROM. Firmware warning if I try to use boot unlocker/root ROM.
I can't get into recovery under either. When I try to get into recovery under the boot unlock/root ROM I get the firmware problem.
fbernar said:
Boot loop if I try to go to stock ROM. Firmware warning if I try to use boot unlocker/root ROM.
I can't get into recovery under either. When I try to get into recovery under the boot unlock/root ROM I get the firmware problem.
Click to expand...
Click to collapse
Your phone had to boot up to unlock so again are you boot looping now? I'm thinking you need to use the alternate restore file. It sounds like your boot loader is still locked. If that's the case that's the only image that will actually flash in Odin.
Sent from my SCH-I605 using Tapatalk 2
here is your problem:
1) NEVER ACCEPT OTA'S
2) You didnt research before flashing
3) Since you accepted the ota, the bootloader from the original vraljb odin file is black listed. meaning you cant ever use that file again.
4) To fix your problem follow section 1b of my guide, make sure to use the alternate restore link as it does not contain a bootloader in the file. it will revert you back to vraljb firmwqre while maintaining the L4 bootloader.
droidstyle said:
here is your problem:
1) NEVER ACCEPT OTA'S
2) You didnt research before flashing
3) Since you accepted the ota, the bootloader from the original vraljb odin file is black listed. meaning you cant ever use that file again.
4) To fix your problem follow section 1b of my guide, make sure to use the alternate restore link as it does not contain a bootloader in the file. it will revert you back to vraljb firmwqre while maintaining the L4 bootloader.
Click to expand...
Click to collapse
`^^^ all of this
Sent from my SCH-I605 using Tapatalk 2
Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?
Wrong place to ask but lol if nothing works yer going to have to odin back to stock using download mode wen yer phone booting im not sure but hold da power and volume down while home button and get in odin flash stock den u can try flashing recovery all over again if u want
supy99 said:
Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?
Click to expand...
Click to collapse
same happened to me use kies to restore firmware then re root and that
Thanks for all the help but luckily I was able to fix it. At first I tried to flash a stock rom but it didnt help and it erased by custom recovery so I plugged into odin and flashed the latest cwm recovery, and using that I flashed cm11 and now my phone is flawlessly running cm11! Thanks for all the suggestions though which I did try before this solution
im using cm12 archidroid 3.5.14 and decided to update to 3.5.15 version last night. but the update didnt went well, something went wrong and i got 'recursive' error, and it started to boot loops.
i tried so many solutions, i odin this and that and nothing worked. i downloaded cwm 6.0.0.47 i think, and managed to install the AD rom, but now im stuck at languange selection, i cant select anything because screen support isnt working
what do i do now?
Samsung S3 i9300
You did "odin this and that"? That's never a good idea. Just saying...
I would try to flash latest AD again but with a proper up-to-date recovery e.g. latest TWRP after making a nandroid backup.
Hawaiihemd said:
You did "odin this and that"? That's never a good idea. Just saying...
I would try to flash latest AD again but with a proper up-to-date recovery e.g. latest TWRP after making a nandroid backup.
Click to expand...
Click to collapse
thanks for the reply Hawaiihemd
i downloaded the stock firmware of i9300 and odin that .tar.md5. Now it just stuck at samsung logo
I would try to flash latest AD again but with a proper up-to-date recovery
Click to expand...
Click to collapse
how do i do that? where do i get latest uptodate recovery? at least point me to right directions thanks so much
ricvai7 said:
thanks for the reply Hawaiihemd
i downloaded the stock firmware of i9300 and odin that .tar.md5. Now it just stuck at samsung logo
how do i do that? where do i get latest uptodate recovery? at least point me to right directions thanks so much
Click to expand...
Click to collapse
Well then, if you already flashed stock rom via odin, your data is already gone. Make sure your phone is working on stock first now. Please be aware that the first boot after each rom flash might take up to 15 min or so because the cache has to be built at first boot!
You can find the link to TWRP recovery in my signature (see My Gadgets). I suggest your read the tutorials that are linked there also for more information.
thanks again, glad to hear there's still hope. i will do as you advised.
So, in order to get stock firmware flashed and running, can i use twrp-2.8.6.1-i9300.tar from your signature?
1st i odin the twrp-2.8.6.1-i9300.tar, and then reboot into download mode, and odin firmware stock?
in that order? i havent done this in a long time, i've been using AD for so long without any problem, i dont really exactly remember how. i just concern about the touch screen not functioning, i really hope no hardware failures. i never experience anything like this, even in recovery mode, the touch screen doesnt work, i had to flash entire process using up/down and power button
right now i havent done anything since the last attempt ( flashed stock rom, and stuck at samsung logo )
currently., im charging the battery, will try get it up and running after the battery is full
thanks mate
ricvai7 said:
thanks again, glad to hear there's still hope. i will do as you advised.
So, in order to get stock firmware flashed and running, can i use twrp-2.8.6.1-i9300.tar from your signature?
1st i odin the twrp-2.8.6.1-i9300.tar, and then reboot into download mode, and odin firmware stock?
in that order? i havent done this in a long time, i've been using AD for so long without any problem, i dont really exactly remember how. i just concern about the touch screen not functioning, i really hope no hardware failures. i never experience anything like this, even in recovery mode, the touch screen doesnt work, i had to flash entire process using up/down and power button
right now i havent done anything since the last attempt ( flashed stock rom, and stuck at samsung logo )
currently., im charging the battery, will try get it up and running after the battery is full
thanks mate
Click to expand...
Click to collapse
i've managed to odin stock rom. everything is ok now
the problem remain is no touch screen. how can i fix it?
FYI i sent my phone to replaced the screen 4-5 days ago , but everything was ok, no problem until i failed flashed rom it started to lose touch screen. how can i fix this?
thanks !
ricvai7 said:
i've managed to odin stock rom. everything is ok now
the problem remain is no touch screen. how can i fix it?
FYI i sent my phone to replaced the screen 4-5 days ago , but everything was ok, no problem until i failed flashed rom it started to lose touch screen. how can i fix this?
thanks !
Click to expand...
Click to collapse
i havent solved the problem with touch screen. can anybody help?