Ohh, where to start. Ok so first off let me apologize in advance if this has already
been posted but I’m a noob when it comes top posting in the forums. Been using
them for years to fix my problems just new to posting. Anyway, a few nights ago I
tried to flash the newest version of the T-Mobile AOKP rom (Kit Kat 4.2.2) onto my
AT&T I337 Samsung Galaxy S4 via the latest version of TWRP recovery. After
attempting to flash AOKP, TWRP failed the flash and had an error message that said
something about the phone not being able to flash a T-Mobile rom on an AT&T
phone. I then tried to flash the AOKP rom again and mistakenly flashed the Loki
kernel instead. I was currently running Cyanogenmod 11. After the Loki kernel
attempted to flash, it once again said failed and gave me a message that said
something about me losing root and asking if I wanted to reinstall superuser. I
agreed to reinstall superuser and used the option to reboot my phone once it was
complete. But….once the phone attempted to reboot my screen went black and all
my phone would do is vibrate every two to three seconds with a blank screen. I
pulled the battery, tried to put it in recovery mode, and download mode but nothing
worked at all. It wouldn’t charge, no battery icon, no LED. After messing with it for a
few hours and randomly pushing buttons I finally got it to go into download mode. I
was so happy. I decided I would flash (Odin) a stock firmware that I had already had
and used plenty of times. But…after flashing Odin would say complete and pass but
when my phone would reboot it done the same thing as before. Black screen and
vibrates every two to three seconds wont charge, no battery icon, no LED, still won’t
go into recovery mode but will still go into download mode. I’ve used every version
of Odin, used different USB ports, different USB cords, reflashed the stock at least
20 times now and still nothing. What have I done and how could I fix this issue. :crying:
Ohhh and before I forget, It may be worth mentioning that when I finally got it in
download mode I noticed it said that I had the stock Samsung firmware, where it
usually says custom when rooted.
I'm assuming you're on MDL firmware. If so Odin flash the stock firmware. You can get it at sammobile.com
You're probably hosed though, sounds like you've tried all this.
Doesn't work
jd1639 said:
I'm assuming you're on MDL firmware. If so Odin flash the stock firmware. You can get it at sammobile.com
Click to expand...
Click to collapse
Like i said in the post. Odin didnt work. It will say pass every time but doesnt fix anything. Screen still stays black and just vibrates every two to three seconds and still cant access recovery mode.
signature
lukethaduke88 said:
Like i said in the post. Odin didnt work. It will say pass every time but doesnt fix anything. Screen still stays black and just vibrates every two to three seconds and still cant access recovery mode.
Click to expand...
Click to collapse
just try whats in my signature
lukethaduke88 said:
Like i said in the post. Odin didnt work. It will say pass every time but doesnt fix anything. Screen still stays black and just vibrates every two to three seconds and still cant access recovery mode.
Click to expand...
Click to collapse
so my gs4 does the same thing how did you fix it ?
juggalo1978 said:
so my gs4 does the same thing how did you fix it ?
Click to expand...
Click to collapse
First observation: nothing here says that he fixed it. If he did, which may not have happened, then he obviously didn't tell us.
I wonder if you really have the same issue. Did you read through the OP? Did your phone get where it is by doing the exact same sequence that he did? If not, and you want someone to help, you will need to give a detailed description of everything that led up to the issue you have, from the time the phone was operating normally. It would also be helpful to know what your phone was running before this happened.
creepyncrawly said:
First observation: nothing here says that he fixed it. If he did, which may not have happened, then he obviously didn't tell us.
I wonder if you really have the same issue. Did you read through the OP? Did your phone get where it is by doing the exact same sequence that he did? If not, and you want someone to help, you will need to give a detailed description of everything that led up to the issue you have, from the time the phone was operating normally. It would also be helpful to know what your phone was running before this happened.
Click to expand...
Click to collapse
I have an i337 and i flashed the AOSP Kt kernel like june or before intern it rebooted and was stock on boot black screen and vibrating trying to turn on or or recovery does the same thing i can get in dl mode and odin says pass nothing stays the same kies wont read it and it dont come up in device manger it is on ether the mdb boot loader or mdl it was running liquid smooth it never got to stock recovery because when it would not boot i tried odin
3.2 ive seem some where it can be fixed with an sd card but i need the debrick image if anyone could help id appreciate it thank you
---------- Post added at 02:17 AM ---------- Previous post was at 01:58 AM ----------
creepyncrawly said:
First observation: nothing here says that he fixed it. If he did, which may not have happened, then he obviously didn't tell us.
I wonder if you really have the same issue. Did you read through the OP? Did your phone get where it is by doing the exact same sequence that he did? If not, and you want someone to help, you will need to give a detailed description of everything that led up to the issue you have, from the time the phone was operating normally. It would also be helpful to know what your phone was running before this happened.
Click to expand...
Click to collapse
I have an i337 and i flashed the AOSP Kt kernel intern it rebooted and was stock on boot black screen and vibrating trying to turn on or or recovery does the same thing i can get in dl mode and odin says pass nothing stays the same kies wont read it and it dont come up in device manger it is on ether the mdb boot loader or mdl it was running liquid smooth 3.2 ive seem some where it can be fixed with an sd card but i need the debrick image if anyone could help id appreciate it thank you
Related
Well first off, ive been at this for 2 days and its frustrating. I am new to this flashing and rooting business and ended up bricking my phone from using the wrong files in metamorph and never backing my stock files up. It would give me a blank screen with the red LED lit up and all my home buttons on the bottom lit up. I followed the Odin directions and actually got my phone to stock. But it was extremely laggy and and i had no service and my SD card just kept connecting and reconnecting. Well i followed the flashing kernel threat because someone told me to try that so i can get the stock kernel or whatever on the phone. That failed and now im sitting here with my phone displaying a phone icon and a computer icon, then a caution symbol in the middle. Someone pleaseeee help me fix this.
l2,
I've been there 3 times this morning already as I hadn't flashed a new zImage to this particular device yet until this morning. What you need to do is get the stock files from http://rapidshare.com/files/415661977/SPH-D700-DG27-8Gb-REL.tar.html and s1_odin_20100513.pit (it must be 13, not 12). Boot into Download mode (hold 1 when powering on). Start Odin 3, check Auto Reboot and Debug En. Choose your PIT file, and under PDA choose the SPH-D700-DG27-8Gb-REL.tar. Plug in your phone, once it is recognized in Odin click Start. This takes about 10 minutes, I know it looks like it hangs up a couple of times but it should keep going. Let me know if that helps.
khalaan said:
l2,
I've been there 3 times this morning already as I hadn't flashed a new zImage to this particular device yet until this morning. What you need to do is get the stock files from http://rapidshare.com/files/415661977/SPH-D700-DG27-8Gb-REL.tar.html and s1_odin_20100513.pit (it must be 13, not 12). Boot into Download mode (hold 1 when powering on). Start Odin 3, check Auto Reboot and Debug En. Choose your PIT file, and under PDA choose the SPH-D700-DG27-8Gb-REL.tar. Plug in your phone, once it is recognized in Odin click Start. This takes about 10 minutes, I know it looks like it hangs up a couple of times but it should keep going. Let me know if that helps.
Click to expand...
Click to collapse
okay ill try all of that but Where can i get the 13 pit file?
It can be downloaded from this link.
http://www.4shared.com/get/6aSCPmEf/s1_odin_20100513.html
khalaan said:
It can be downloaded from this link.
http://www.4shared.com/get/6aSCPmEf/s1_odin_20100513.html
Click to expand...
Click to collapse
thanks so much man ill try it out. One question though. I already started this odin thing and its doing its thing. its about half way done but its using the 12...can i just shut my phone off and put it in download again when its done and use the 13 and it will work?
If you have it going with the 12 already I'd give that a try, if it doesn't work you can always get back into download mode and do it with 13. I couldn't get 12 to ever start it would always sit for 20m and do nothing.
khalaan said:
If you have it going with the 12 already I'd give that a try, if it doesn't work you can always get back into download mode and do it with 13. I couldn't get 12 to ever start it would always sit for 20m and do nothing.
Click to expand...
Click to collapse
okay yeah ill try. but its been sitting for like 10 min at half way on the status bar...
That is way the devil too long, go ahead and unplug your phone, hit reset in odin, set it up like I instructed, reboot your phone to download mode, and give it another go.
yeah lol okay i thought so. haha
Alllll fixed. Thank you guys soooo much for helping out. Im going to root again but i'm not gunna mess with metamorph this time lol, whats a good root? Im learning all this stuff and idk what one i should do.
http://forum.xda-developers.com/showthread.php?p=8628341#post8628341
>_>
Please Modify Title of Thread add
" Solved - Bricked Epic - tried everything "
I bricked my Epic last weekend and am feelin' ya on all the stuff you did to unbrick it. Glad to hear that all is well~
I screwed my setup up and had to do the Odin method yesterday. I didn't read this post before hand, and I used the ****12.pit instead of the 13. What is the difference in the two? My phone seems to be working just fine with the 12. One problem I found I don't believe I had before is theming the dialer_tab_activity.apk FCs the phone on hangup, but when I put another one in unthemed, it works fine.
help
I cannot get phone to load any tar completely.. they all stop and phone's screen goes purple. Most the time it hangs in odin at the zImage and then sometimes it gets a few bars going .. and hangs at factoryfs.rfs. Any help
You don't need the pit file when flashing a tar rom. It's only for modems and kernals. I have used Odin and haven't used the pit. Works just fine.
Okay, i just joined. Sorry if i sound ignorant (most likely cause I am) but i am fairly certain i semi-bricked my Epic, okay so it started when i flashed the CyanogenMod it was very laggy so i figured i did it wrong, quickly using clockwork i flashed VIPERrom (FRoZeN) DK28 all looked fine but then my phone's service started acting up, so i tried to re-flash CyanogenMod. This ***** it up worse it got stuck at the Samsung boot logo, now i am trying to revert to Stock but Odin nor my Cpu recognize the Device.
Extra info that might help, I have the Stock Tar, Odin 1.6 with Pit, can get into both download and CW recovery...
Help this ignorant fool please T_T
The Boxinator said:
Okay, i just joined. Sorry if i sound ignorant (most likely cause I am) but i am fairly certain i semi-bricked my Epic, okay so it started when i flashed the CyanogenMod it was very laggy so i figured i did it wrong, quickly using clockwork i flashed VIPERrom (FRoZeN) DK28 all looked fine but then my phone's service started acting up, so i tried to re-flash CyanogenMod. This ***** it up worse it got stuck at the Samsung boot logo, now i am trying to revert to Stock but Odin nor my Cpu recognize the Device.
Extra info that might help, I have the Stock Tar, Odin 1.6 with Pit, can get into both download and CW recovery...
Help this ignorant fool please T_T
Click to expand...
Click to collapse
You forgot to flash the EXT4 or RFS Kernel
http://android.stolenrobot.com/Epic4G/epic.htm
that comes with cyanogen it looks like just put either on your sd card then flash after you flash cyanogen in Cwm
Here is some more info
http://forum.xda-developers.com/showthread.php?t=935060&highlight=tutorial
iSaint said:
You forgot to flash the EXT4 or RFS Kernel
http://android.stolenrobot.com/Epic4G/epic.htm
that comes with cyanogen it looks like just put either on your sd card then flash after you flash cyanogen in Cwm
Here is some more info
http://forum.xda-developers.com/showthread.php?t=935060&highlight=tutorial
Click to expand...
Click to collapse
I did flash EXT4 "CM6EXT4kernel-1-2-2011" this one to be specific.
The Boxinator said:
I did flash EXT4 "CM6EXT4kernel-1-2-2011" this one to be specific.
Click to expand...
Click to collapse
did you wipe x3 ?
Okay,
There is a growing number of us XDA members on the Vibrant platform who have just bricked out phones. Save for other DEV tools, which I have not used, do not have access, and do not know how to use, for all intensive purposes, this phone is Br'iKTed ! ! !
Here are the series of events
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
4. worked great for 2 days.
5. then on night 2, the phone was stuck on the DOW Green robot screen
6. could not get into Recovery mode (none of the recovery modes)
7. Phone would not boot
8. ODIN back to stock
9. After Vibrant screen, the phone turns off. No soft keys, Nada!
10. Flashed JI5, Ji6, Eugene's Non Bricking Froyo (ODIN Files)
11. Same result, Turned off after Vibrant
and
12. still cant' get into recovery
I am having problems with the phone starting up and loading what I flashed.
I flashed JI5 Ji6, and Eugene's non bricking Froyo Rom
These 3 are the only ones I was able to find that is ODIN flashable
Why you ask?
I cannot get into Recovery, but I can get into Download mode. I can't get into any recovery at all. NOTHING. This is why ODIN seems to be my only option.
But regardless of any ROM i flash, my phone shuts off right after the Vibrant screen. No splash screen, no loading, no booting. .Nothing. It just shuts off.
I can't charge it either.
i get a Charging bootloop. HOurglass - battery shows up for a bit, then restarts over and over.
So in other words. it's ****ed.
Hope that explains it sufficiently. if you have any more questions or suggestions, Im open man, Im open.
Help me
So I'm not sure how DEVs would like to proceed on this.
TW (I've always loved your roms. Been following you since the first BIONIX 1.8)
Morific (If it's the Kernel, i'd like to know about it)
Thanks for reading guys. I wanted to give everybody a heads up.
I don't know what the problem is, but I do know that the phone does not work.
I'd appreciate some suggestions or anything.
And to inform the community that this problem is out there. I hope there aren't any more bricked phones.
Cheers,
have you tried using odin with the repartition checked
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
a4 moda said:
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
Click to expand...
Click to collapse
have you tried to odin to ka6 or ka7? something with a bootloader
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
STiGLOGiC said:
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
Click to expand...
Click to collapse
Completely reasonable. This pertains to development because if there is an endemic problem with one of our ROMS or KERNELS (not pointing fingers, just pointing out the possibilities that I know of, there could be more), people in our community need to know. Hence, I titled it "PUBLIC SERVICE ANNOUNCEMENT"
Thanks. I hear you about Tmobile. I'd rather not have to dump my problem on Tmobile if I can fix it, because I flashed the rom. Despite the fact that Tmobile JFS leaves something to be desired, they did deliver me a working phone. So i'd like to exhaust all possibilities before calling it quits.
hackman17 said:
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
Click to expand...
Click to collapse
Exactly.
jaetm83 said:
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Click to expand...
Click to collapse
Thanks for the heads up. I've gone through this myself many times. And i'm sure your post will help others out there. My problem (as well as many others on here with the same ROM and KERNEL I used) seems to be different and unique. Something that ODIN won't cure.
vibrant2010 said:
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Yes, tried that too. Same result. Vibrant.. then shut off.
Thanks anyway.
I had actually just had Bionix-v 1.2.1 and the new DoW combo to try out Voodoo Sound. I really loved the sound quality, but battery drain was not adequate as being my daily driver, even though I set it to run at 1ghz and used a sleep profile. After just over 2 days of use, I backed out by ODIN'ing to JFD and I installed Bionix-v 1.2.1 again. Only thing I have noticed so far is GPS not initiating immediately after it's turned on. I would go into GPS Test app, and turn on GPS after the app is started, but I get no satellites for at least 1 min. I used to get a lock within seconds, not minutes. I will try ODIN again tomorrow and see if it fixes. I guess I was lucky enough not to get a bootloop again though.
But I can't see why you and I would have any issues after the Bionix+Dow combo. Wouldn't ODIN just clear everything up? I even repartitioned when flashing, so my guess is that my system, data, datadata, etc., are all reformatted completely? Am I missing something?
I had the same problem. I flashed DoW and then the next day my phone didn't want to turn on. I pulled the battery and restarted it. It didn't want to start up all the way. It got to the vibrant screen and shut off. luckily for me, my replacement phone that I ordered a week ago came in the same day. I sent off my old phone letting samsung/tmo take care of it.
This exact same thing happened to me.
I too had the phoen bricked after flashing the DOW after Bionix 1.2.1
I have been flashing since the G1. This is the first time I've ever bricked a phone.
Hoping to get it fixed this weekend
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
black spirit said:
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
Click to expand...
Click to collapse
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
If you have not already done this, I recommend doing this: http://forum.xda-developers.com/showthread.php?t=954509
Bay Wolf made a nice software for the computer that pretty much shows you a step-by-step instruction on how to flash to stock, reroot, and flash the new ROM of your choice. This program will push you into download mode, clockwork recovery, etc. There is a video on that link that will also show you a step-by-step instruction. Try that out if you haven't, and let us know how it goes.
That program comes with a PIT and TAR file for you to use as well.
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
drewdude007 said:
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
Click to expand...
Click to collapse
I thought the same when it happen to me.
Nothing would work, but went that approach and happy days.
s1_odin_20100512.pit
and
T959UVJFD.tar
are the only ones you need, and if your good with your flashing, just do a pit first, no pda.
And if your still getting to download mode, ect, and dont have the computer /!\ phone icon on the screen, sounds like a soft brick.
jellette said:
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
Click to expand...
Click to collapse
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
SamVib said:
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
Click to expand...
Click to collapse
Because he started off with his problem stated as:
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
Your phone probably IS charging.
Your /efs nodes may be messed up. Do you have a backup of your /efs?
Try reading here: http://forum.xda-developers.com/showthread.php?t=859914
Hi guys,
I have a T-Mobile Note 3 running 4.4.2 and I'm having the hardest time installing a custom recovery such as CWM or even TWRP. I was having problems the last few days with my older phone and decided to get a free replacement because I thought it was the phone. Anyways I open my phone, boot it up, install latest software, and restart to download mode. I root it with ODIN and restart. Then I restart it again and install CWM recovery. Everything goes smoothly, everything is in the green. Then I hold volume UP, menu, and power keys and it says "Could not do normal boot. What is this? It was happening on my older Note 3 and now this one.
Everything works fine when I try to boot it normally and I can use the phone but cannot seem to install a custom recovery. Instead of booting to the recovery screen, it goes to Odin/downloading mode with a message above 'Odin Mode' that reads 'Could not do normal boot'.
I am not new to this. I have done this before many times but for some reason it is not working for me anymore. Is it the new firmware and/or the updated software that is preventing me from doing this? I have researched this night and day last 72 hours but can't find a solution.
Please help, and thanks in advance!!
Figured I'd give it a bump. Any thoughts guys?
the_real_vlad said:
Figured I'd give it a bump. Any thoughts guys?
Click to expand...
Click to collapse
Which bootloader is the phone on, and which CWM/TWRP versions are you using? You sure you downloaded the right ones for your model?
jisoo said:
Which bootloader is the phone on, and which CWM/TWRP versions are you using? You sure you downloaded the right ones for your model?
Click to expand...
Click to collapse
Hi,
Firmware on my phone: N900TUVUENK3
Recovery: n900s-cwm-recovery-6.0.4.4(1011).tar, openrecovery-twrp-2.6.3.2-hltetmo.tar
As for the bootloader, I have no idea. It is stock however, I know that.
Solved!
What I did was download the VERY LATEST twrp from the official website and flash with odin. Then I wiped EVERYTHING and reinstalled the firmware. Last, reinstalled TWRP.
All is well
So, I was going to install a Lollipop rom and I thought I followed directions correctly but it gets stuck at the "Powered by Android" very first screen. Booting into recovery gets me into the simple manual recovery mode and not safestrap. Odin also doesn't seem to recognize that I've connected my phone - although maybe there's a special way to do it?
I basically need help getting my phone working again. I've dug around but everything seems focused around using Odin and I don't know how to get that to see my phone in the state that it's in.
Help!
So, reasons I am dumb #1: I had no idea what the key combo to boot into Odin was (volume down+home+power) So, now I can get to Odin and I'll try to figure it out from here unless someone jumps in with something before I do.
Sheesh. Sigh.
im in need of help myself as I went to root my sm-g900v and now am stuck in bootloop.. how do i fix this? no matter what I do to get it to restart, same result....
rlo5ca said:
im in need of help myself as I went to root my sm-g900v and now am stuck in bootloop.. how do i fix this? no matter what I do to get it to restart, same result....
Click to expand...
Click to collapse
From Download Mode, just flash a stock ROM. If you hadn't rooted yet, you can use Kies 3, from Samsung, to reset your phone to newest ROM, correcting any issues. Verizon also has a Software Repair tool you can try, but I like Kies better. All the info you need is in the stickies.
Hi so first of all im kind of a noob when it comes to this so please explain any technical jargon
It all started a few days ago when my note 4 started rebooting on its own, it did occasionally get stuck in bootloop but a battery pull fixed every time, I hadn't rooted it or did anything that could break it that way just normal media consumption. About 2 days later it started to get stuck on bootloop more than half the times it rebooted (again all without a reason) Currently it doesnt even show the boot animation and i can't access recovery mode, I can access odin mode tho but i flashing it twice didn't help
I have the uk O2 version (SM-N910F) with a powerbear battery that doesn't show any signs of wear down
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience
Did you flash stock rom(latest) successfully through odin? Did odin show 'success' message after finishing flashing?
Mufrad said:
Did you flash stock rom(latest) successfully through odin? Did odin show 'success' message after finishing flashing?
Click to expand...
Click to collapse
yes and yes, I used the latest stock rom from sammobile and it did successfully flash but when it tries to go to recovery mode after that it just goes to bootloop again (it shows the "recovery booting..." in blue at the top)
Altrath said:
yes and yes, I used the latest stock rom from sammobile and it did successfully flash but when it tries to go to recovery mode after that it just goes to bootloop again (it shows the "recovery booting..." in blue at the top)
Click to expand...
Click to collapse
I am not sure what's wrong, but I would install a custom recovery and try and install a custom rom to check if everything works right, if it does then maybe try and flash stock through odin again.
Altrath said:
Hi so first of all im kind of a noob when it comes to this so please explain any technical jargon
It all started a few days ago when my note 4 started rebooting on its own, it did occasionally get stuck in bootloop but a battery pull fixed every time, I hadn't rooted it or did anything that could break it that way just normal media consumption. About 2 days later it started to get stuck on bootloop more than half the times it rebooted (again all without a reason) Currently it doesnt even show the boot animation and i can't access recovery mode, I can access odin mode tho but i flashing it twice didn't help
I have the uk O2 version (SM-N910F) with a powerbear battery that doesn't show any signs of wear down
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience
Click to expand...
Click to collapse
Mate, the 910F is a Snapdragon - famous for it's eMMc problem. You may search about this and get more info.
In short, there's a big chance it's not going to get to work again.
Sorry for your loss.
The problem seems to be caused by the eMMc chip
Is there a way to fix or replace it without expensive equiepement?
Mufrad said:
I am not sure what's wrong, but I would install a custom recovery and try and install a custom rom to check if everything works right, if it does then maybe try and flash stock through odin again.
Click to expand...
Click to collapse
btw flashing TWRP or any recovery doesn't work so i'm pretty sure it's the eMMc chip
If it really is your eMMC chip, you are better off trying to get a new device. The eMMC chip isn't removable without a lot of time, effort and risks. Also you'll need a head Gun or something and a new identical chip that will cost you a new device worth.
Altrath said:
The problem seems to be caused by the eMMc chip
Is there a way to fix or replace it without expensive equiepement?
Click to expand...
Click to collapse
try
https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448