Related
I know there's another thread of mine with the same problem. But no one has helped me yet. I have a lg optimus one for a long time, I installed cm10.1 about 5-6 months ago, I didnt backup anything when I installed custom rom. I factory reset everything on it so I could give it to someone. But now, when I turn it on, checked the about phone. There is no IMEI. I need help from step to step. I dont wanna brick it. I want it back to stock rom 2.2 froyo. And I have been reading threads about people bricking their phone with kdz(dont know what it is). I'm a newb. I live in U.S
Anyone...?
duhvietboy said:
Anyone...?
Click to expand...
Click to collapse
If this mysteriously happened then your SIM card is probably toast. Can you boot into recovery? Have you tried another ROM?
same happend to me, i root the phone and install recovery, an on every single rom i had flashed i didn't had any connection, and there was no IMEI number
kingston951 said:
same happend to me, i root the phone and install recovery, an on every single rom i had flashed i didn't had any connection, and there was no IMEI number
Click to expand...
Click to collapse
If it killed the SIM - try another one - that would quickly prove that theory (although I don't know if I would risk a SIM from an active phone, but if you know anyone who has a phone that died or if you are lucky and can get 10$ SIM cards for pay as you go with no activation fee - it's a cheap way to test and gives you a spare SIM if you ever need it...assuming you have unlocked as well as rooted your phone).
Sounds more like you installed a rom with an incompatible base band if you have no connectivity to your carrier anymore. If you flashed straight to an ICS or JB rom without either upgrading it through the LG app or manually flashing at the time - try it now. (it's not going to hurt it more than it already is, and these phones are tough)
And with my first post I am starting to realize how much I have been digging into what could go wrong so it doesn't go wrong before I tried anything. However if I am wrong, please let me know!!
Hi.
I recently flashed the iNfinity HD V2 rom on my Blu Life Play.
Since then I have not been able to get my sim to be recognize in the sim 2 slot.
It worked before I flashed the rom and I'm at a loss as how to resolve the issue.
Any help would be greatly appreciated.
gunslinger79 said:
Hi.
I recently flashed the iNfinity HD V2 rom on my Blu Life Play.
Since then I have not been able to get my sim to be recognize in the sim 2 slot.
It worked before I flashed the rom and I'm at a loss as how to resolve the issue.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm no expert on this, but here is my guess.
There are 2 versions of the Blu Life Play. One of which supports 850/1900 3G bands, the other working with 850/2100. Both of these versions of your phone have 2 sim card slots. My guess would be (and odds are I am not right) is that you flashed the ROM corresponding to the opposite version of the Life Play that you have, and that caused some sort of issue. Like if you had the L100a, you might have accidentally flashed the L100i ROM, or the other way around.
Check the thread or page that you got the ROM from. That 2nd SIM card slot issue might be a known issue. Usually ROM developers will post a "What's Working" and "What's Not Working" section on the thread or page they made for their ROM. Check to see if the SIM card issue is in the "What's Not Working" section.
Hope this helps!
jasonmerc said:
I'm no expert on this, but here is my guess.
There are 2 versions of the Blu Life Play. One of which supports 850/1900 3G bands, the other working with 850/2100. Both of these versions of your phone have 2 sim card slots. My guess would be (and odds are I am not right) is that you flashed the ROM corresponding to the opposite version of the Life Play that you have, and that caused some sort of issue. Like if you had the L100a, you might have accidentally flashed the L100i ROM, or the other way around.
Check the thread or page that you got the ROM from. That 2nd SIM card slot issue might be a known issue. Usually ROM developers will post a "What's Working" and "What's Not Working" section on the thread or page they made for their ROM. Check to see if the SIM card issue is in the "What's Not Working" section.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the reply.
That could be a possibility.
I have gone through the thread and I don't see anything specific to my problem but something similar.
I should I have been more vigilant before I flashed.
gunslinger79 said:
Thanks for the reply.
That could be a possibility.
I have gone through the thread and I don't see anything specific to my problem but something similar.
I should I have been more vigilant before I flashed.
Click to expand...
Click to collapse
If it is really necessary that you have the 2nd SIM card slot, just go back to the stock version of Android that came with your phone, and then from there try to get another ROM. That way, even if you are unable to find another ROM that doesn't have the 2nd SIM card issue, at least you will be running a version of Android that does support it.
Sent from my SGH-I847 using XDA Free mobile app
jasonmerc said:
If it is really necessary that you have the 2nd SIM card slot, just go back to the stock version of Android that came with your phone, and then from there try to get another ROM. That way, even if you are unable to find another ROM that doesn't have the 2nd SIM card issue, at least you will be running a version of Android that does support it.
Sent from my SGH-I847 using XDA Free mobile app
Click to expand...
Click to collapse
My main issue at the moment is actually getting the phone back to stock; every time I flash it there seems to be remnants of the old rom.
I cant' seem to get it back to stock.
I managed to get the phone back to stock including the recovery.
I still can't get the phone to recognize the sim.
After reading some threads here I think I flashed a rom for L100i instead of L100a.
I think the problem is to do with the modem.
Can anyone help me please?
I think I have the problem narrowed down to not having a IMEI number.
I have no back up of it.
Is there any way I can get a the IMEI back on my phone?
Phone is no longer rooted and having trouble rooting again.
gunslinger79 said:
I think I have the problem narrowed down to not having a IMEI number.
I have no back up of it.
Is there any way I can get a the IMEI back on my phone?
Phone is no longer rooted and having trouble rooting again.
Click to expand...
Click to collapse
If all you did was restore a recovery-made-backup, I don't think that will restore original baseband and stuff. If this is how you got back to stock, that means that although you are running stock BLU-Android, you are still using the broken L100i incompatible baseband.
I am not sure if this phone is compatible with ODIN, but if it is and you can find a tutorial on how to restore your L100a back to stock with ODIN then this is what you want. I am not sure what ODIN stands for, but it's a download tool used for not only restoring a phone's android operating system back to stock, but the other things that a plain old recovery-backup doesn't cover like kernel and baseband. ODIN requires a Windows PC with the correct phone drivers installed. So in this case you need the your phone's drivers from BLU on your computer, so that when you plug the phone in it is recognized as a BLU Life. Again, I am not sure if there even is an ODIN image for your phone since generally BLU phones are not that popular on XDA, but if there is then follow the instructions and use that to restore back to stock instead of just using a recovery backup.
IF YOU DO FIND AN ODIN IMAGE FOR IT, MAKE SURE THAT YOU DO NOT MAKE THE SAME MISTAKE OF INSTALLING THE "I" VERSION INSTEAD OF THE "A" VERSION! MAKE ABSOLUTELY SURE THAT THE ODIN IMAGE IS THE EXACT ONE FOR YOUR PHONE!!!!
EDIT: I just re-read your post and realized I didn't exactly answer your question. Sorry about that.
You should do the ODIN thing I mentioned above, just to make sure that you are on the right baseband. However I do not think this restores your IMEI as well. I Google'd how to restore a lost IMEI on an Android phone and got a couple articles on how to do so. One of these articles tells that CHANGING THE IMEI OF YOUR PHONE IS ILLEGAL!!!!! However It doesn't sound like this applies to you according to what you said, because you are only trying to restore a lost IMEI number, not change an already existing one.
Have a look at this article.
Good luck! :cyclops:
jasonmerc said:
If all you did was restore a recovery-made-backup, I don't think that will restore original baseband and stuff. If this is how you got back to stock, that means that although you are running stock BLU-Android, you are still using the broken L100i incompatible baseband.
I am not sure if this phone is compatible with ODIN, but if it is and you can find a tutorial on how to restore your L100a back to stock with ODIN then this is what you want. I am not sure what ODIN stands for, but it's a download tool used for not only restoring a phone's android operating system back to stock, but the other things that a plain old recovery-backup doesn't cover like kernel and baseband. ODIN requires a Windows PC with the correct phone drivers installed. So in this case you need the your phone's drivers from BLU on your computer, so that when you plug the phone in it is recognized as a BLU Life. Again, I am not sure if there even is an ODIN image for your phone since generally BLU phones are not that popular on XDA, but if there is then follow the instructions and use that to restore back to stock instead of just using a recovery backup.
IF YOU DO FIND AN ODIN IMAGE FOR IT, MAKE SURE THAT YOU DO NOT MAKE THE SAME MISTAKE OF INSTALLING THE "I" VERSION INSTEAD OF THE "A" VERSION! MAKE ABSOLUTELY SURE THAT THE ODIN IMAGE IS THE EXACT ONE FOR YOUR PHONE!!!!
EDIT: I just re-read your post and realized I didn't exactly answer your question. Sorry about that.
You should do the ODIN thing I mentioned above, just to make sure that you are on the right baseband. However I do not think this restores your IMEI as well. I Google'd how to restore a lost IMEI on an Android phone and got a couple articles on how to do so. One of these articles tells that CHANGING THE IMEI OF YOUR PHONE IS ILLEGAL!!!!! However It doesn't sound like this applies to you according to what you said, because you are only trying to restore a lost IMEI number, not change an already existing one.
Have a look at this article.
Good luck! :cyclops:
Click to expand...
Click to collapse
All I'm trying to do is get the IMEI that came with the phone back on it; nothing illegal.
Mobile ODIN is not compatible with my device.
I would like to get back to full stock; can anyone help with that please?
I have seen that SpFlashtool might be useful for me.
The only problem is is that I have no experience with it.
Can anyone give me some pointers on how to use it safely?
I'm not sure if people have any interest in this, but I think I have have the problem resolved.
I flashed octarom_kk_iq4410_v3_fixed which seem to give me a baseband then I used SP_Flash_Tool_v3.1328.0.183 to flash a secro.img.
after all that my imei's were restored.
I think I screwed up big time.
I fist got my GS3 Verizon and rooted with Towelroot. Then I tried installing TWRP. I was unaware of the locked bootloader, and found out about SafeStrap. I never actually uninstalled TWRP. From there, I installed SafeStrap, then I tried installing CM 12.1 and I messed up. My phone won't boot up in any mode other than download mode. When I try to boot in to recovery I will get the "System Software not authorized by Verizon Wireless has been found on your phone." Message. I need to wipe and install stock ROM. Someone please help! (And if possible, maybe someone can walk me through having CM 12.1 on here? I really want it on, but I need a walkthrough)
Thanks guys!
P.S. I am running Android 4.4.2.
TacoTank said:
I think I screwed up big time.
I fist got my GS3 Verizon and rooted with Towelroot. Then I tried installing TWRP. I was unaware of the locked bootloader, and found out about SafeStrap. I never actually uninstalled TWRP. From there, I installed SafeStrap, then I tried installing CM 12.1 and I messed up. My phone won't boot up in any mode other than download mode. When I try to boot in to recovery I will get the "System Software not authorized by Verizon Wireless has been found on your phone." Message. I need to wipe and install stock ROM. Someone please help! (And if possible, maybe someone can walk me through having CM 12.1 on here? I really want it on, but I need a walkthrough)
Thanks guys!
P.S. I am running Android 4.4.2.
Click to expand...
Click to collapse
Your best bet may be using Odin to flash the stock 4.4.2 ROM.
I bought my i535 (Verizon SGS3/d2vzw) used as a device to develop modding skills. It came with the 4.4.2 rom already installed. I have learned from reading in this forum that options for you and I are very limited. Once your device is restored you can use SafeStrap but not TWRP, CWM, or Philz Recovery. There are only three roms available to us: Stock, SuperLiteRom, and PaulPizz ROM.
@ShapesBlue may have better advice, he actually used this device as a phone and has much more experience with what can be done with the i535 on the 4.4.2 bootloader (NE1)
First of all, thank you for ALL your help! I REALLY appreciate it! You are a lifesaver. Now, my question is, can I flash android 4.2 so the bootloader isn't locked? I know I am being a little picky, but this is the ONLY reason I bought it. But I was thinking, put my phone in download mode, flash 4.2 > root > install TWRP > wipe > Flash CM12.1 > and voila! Would that work, and if so, could you help?
TacoTank said:
First of all, thank you for ALL your help! I REALLY appreciate it! You are a lifesaver. Now, my question is, can I flash android 4.2 so the bootloader isn't locked? I know I am being a little picky, but this is the ONLY reason I bought it. But I was thinking, put my phone in download mode, flash 4.2 > root > install TWRP > wipe > Flash CM12.1 > and voila! Would that work, and if so, could you help?
Click to expand...
Click to collapse
Everything I have read indicates that we are stuck at 4.4.2 and can not downgrade. I didn't read the forums before purchasing mine and have not seen anything saying anyone has safely downgraded, or used any rom other than the three I mentioned.
I guess we could wish for Verizon to release a security update because of stagefright issues. I can dream, but I'm not holding my breath.
Okay, guys, I am starting to lose it.
I am having 0 luck fixing this damn thing. I have tried flshing every android version that exists for this phone and it won't work at all. KIES won't recognize so I used ODIN. ODIN never feels like working so IDK what to do. I used Safestrap to try and install CM 12.1, but it was stuck in a boot cycle, and since I had to use the Safestrap app to launch recovery, I am screwed. There is no way for me to get into my phone, I only have download mode, I need some help guys. What can I do!?!?! I just want anything that will work at this point. Even if I can't get CM12. I think I want to get android working on it and sell it. Pls help!!!
TacoTank said:
Okay, guys, I am starting to lose it.
I am having 0 luck fixing this damn thing. I have tried flshing every android version that exists for this phone and it won't work at all. KIES won't recognize so I used ODIN. ODIN never feels like working so IDK what to do. I used Safestrap to try and install CM 12.1, but it was stuck in a boot cycle, and since I had to use the Safestrap app to launch recovery, I am screwed. There is no way for me to get into my phone, I only have download mode, I need some help guys. What can I do!?!?! I just want anything that will work at this point. Even if I can't get CM12. I think I want to get android working on it and sell it. Pls help!!!
Click to expand...
Click to collapse
If your device was ever on 4.4.2 you may as well give up on the idea of installing CM 12.1, or any ROM other than the three I mentioned. (If you have found something stating differently please share.)
Some of these threads may be of help:
[GUIDE] Debrick your bricked SCH-I535! [BOOTLOADER/HARDBRICK]
[GUIDE][ML1/NC1/NE1] TW 4.4 and 4.3 Sticky Roll-Up Thread (7-10-14)
[INDEX] TW 4.4 Download List (7-10-14)
That last one is a bit dated but still worthwhile. The second is not quite as dated. The first may be what helps you.
So, I need like, a tutorial or a link on how to fix this. I want to fix my recovery as well if that's possible. Just so I can have stock recovery. If I flash Android 4.4.2 it should fix that though. Plus, a working download link would be MUCH appreciated.
Alright. So, I followed the instructions on this http://forum.xda-developers.com/showthread.php?t=2581166&nocache=1 and had no luck, when I flash on ODIN, it gets the error when flashing the "aboot". That's when it fails. Any suggestions? I tried deleting it, but 7zip won't let me.
TacoTank said:
Alright. So, I followed the instructions on this http://forum.xda-developers.com/showthread.php?t=2581166&nocache=1 and had no luck, when I flash on ODIN, it gets the error when flashing the "aboot". That's when it fails. Any suggestions? I tried deleting it, but 7zip won't let me.
Click to expand...
Click to collapse
Odin gives an error at that point when you are trying to flash an incompatible bootloader. If you used any rom with a bootloader older than 4.4.2 (NE1) it prevents you from flashing to avoid a bricked device.
Which image did you use from the site you linked?
None of the images from the OP of that thread are for flashing with Odin. They are to burn to an external micro sdcard from which you boot the device and then restore your bootloader, and recovery if necessary.
Please detail the exact steps you performed.
Oh, I flashed an image from something else, my bad on that one. Uh, so I tried putting that thing on my SD card with Win32DiskImager, and every time I do it, after multiple writes and phone boot-ups, I had no luck. It always tells me "Firmware upgrade encountered an error. Please use Software Repair Assistant & try again." So, I don't know what to do. Ad I also wanted to thank you for your speedy replies, I know mine are always delayed, I have finals and stuff, it's hectic. But, I need my phone back already so I'll jump back to reply ASAP! Thanks!
TacoTank said:
Oh, I flashed an image from something else, my bad on that one. Uh, so I tried putting that thing on my SD card with Win32DiskImager, and every time I do it, after multiple writes and phone boot-ups, I had no luck. It always tells me "Firmware upgrade encountered an error. Please use Software Repair Assistant & try again." So, I don't know what to do. Ad I also wanted to thank you for your speedy replies, I know mine are always delayed, I have finals and stuff, it's hectic. But, I need my phone back already so I'll jump back to reply ASAP! Thanks!
Click to expand...
Click to collapse
I am not in the least familiar with "Software Repair Assistant." I do know it is a Verizon process. You can give it a try if you wish.
Other than that you are back to the debrick image process. That process can take a number of attempts. You should use either a 16 or 32 GB class 10 card. It sometimes works with a slower card, but best bet is with a class 10. It would be an oddity for something samller than 16 GB to work. Also, you may need to try several cards. A card that works for this in one phone at times does not work in a different SGS3.
Alright, here's what I just did. I needed a new SD Card anyay so I bought a Kingston Digital 16 GB microSDHC Class 10 UHS-1 Memory Card 30MB/s with Adapter (SDC10/16GB) off of Amazon and it should be here by Thursday. And then, I'll tell you how things go. I am praying this works, because, even though I am getting a HTC One M9 (I'd like your thought on that, if you think it's a good phone to run CM 12.1 off of) I need a phone for now.
TacoTank said:
Alright, here's what I just did. I needed a new SD Card anyay so I bought a Kingston Digital 16 GB microSDHC Class 10 UHS-1 Memory Card 30MB/s with Adapter (SDC10/16GB) off of Amazon and it should be here by Thursday. And then, I'll tell you how things go. I am praying this works, because, even though I am getting a HTC One M9 (I'd like your thought on that, if you think it's a good phone to run CM 12.1 off of) I need a phone for now.
Click to expand...
Click to collapse
A quick check at the VZW development thread for the M9 shows they have root and custom recoveries. A quick glance at a number of the custom ROMs their had all of them based on stock, either saying stock or sense.
Another check at CM shoes development open for the himaul HTC One M9. I don't know which carrier that is for, but it is a GSM device instead of cdma. The AT&T M9 is code named hima so I am not convinced it is theirs.
Otherwise, I don't know much about the M9 outside of what I see in the reviews. Being that my daily driver is still my SGS3, I would think I would be satisfied with the M9 performance.
Well, I am screwed. I tried using my 16GB SD and it didn't work. I did everything right, I don't know what to do. I kinda think flashing something via ODIN would work, but I don't know what to flash. Help?
TacoTank said:
Well, I am screwed. I tried using my 16GB SD and it didn't work. I did everything right, I don't know what to do. I kinda think flashing something via ODIN would work, but I don't know what to flash. Help?
Click to expand...
Click to collapse
From what I have read in the debrick threads, you may have to try several cards to find one that works in your phone. Also, it is 16 and 32 Gb class 10/U1 cards that are most likely to work.
So I tried this process with a 64GB Samsung Class 10 SD, and it didn't work. Should I just go with a 32GB or am I going to need a Jtag?
TacoTank said:
So I tried this process with a 64GB Samsung Class 10 SD, and it didn't work. Should I just go with a 32GB or am I going to need a Jtag?
Click to expand...
Click to collapse
I don't recall seeing anyone report attempting to do this with a 64GB card, not to say it wouldn't work, I just haven't seen anyone saying they tried one.
TacoTank said:
So I tried this process with a 64GB Samsung Class 10 SD, and it didn't work. Should I just go with a 32GB or am I going to need a Jtag?
Click to expand...
Click to collapse
dawgdoc said:
I don't recall seeing anyone report attempting to do this with a 64GB card, not to say it wouldn't work, I just haven't seen anyone saying they tried one.
Click to expand...
Click to collapse
You may just need a SanDisk version versus the Samsung one. I have ran across threads with people having success with them. Definitely try a 32gb sd card as dawgdoc suggested
Nexus 6 running SSHD or Cataclysm
http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Sent from my Nexus 5 using Tapatalk
Please what's the confirmed rooting method for Samsung galaxy s3 Verizon i-535 running 4.4.2 I tried rooting with towelroot & kingroot, also flashed cwm recovery from rom manager respectively then rebooted to recovery but got black screen with yellow triangle error. I have a friend at the Samsung store in bestbuy that have reflashed the phone twice & is still willing to restore the phone again but I wanna know the working root method for this device without screwing up recovery?
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
andrew88 said:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
Click to expand...
Click to collapse
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
TerribleChoices said:
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
Click to expand...
Click to collapse
andrew88 said:
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
Click to expand...
Click to collapse
Oh dear.
Yeah it does sound like something got deeply ****ed up in this case. I had the luck to somehow get past the smart switch error when the phone died of low battery. As I attached it to the charger I quickly boot it into download mode before the screen would become a bootloop again and that's where I was able to reinstall the latest version of TWRP recovery. After that, I was able to flash a stock ROM of Nougat that didn't have a ****ed up bootloader like I had. Specifically the one from this thread: https://forum.xda-developers.com/galaxy-s6/help/device-5-binary-3-s6-sm-g920f-t3706025
by forumber2.
It's the Netherlands stock-ROM. Not sure if you're from the US and the carrier would be wrong with that CSC, but it was a good bet for me. I got my phone back to working normally now.
Worst case scenario I'd say see if you have a phone repair shop nearby and ask them an opinion on what could be wrong. I'm just an amateur like you.
Still, I wish you the best of luck with it. Maybe there's still some hope. :/
Hello,
I did something rather stupid. I downloaded stock firmware from samsung-firmware.org for this build TMB-G930TUVU2APC8_G930TTMB2APC8-20160325.
Using heimdall, I tried to flash all the partitions to my T-Mobile S7. The boot, cache, aboot, recovery, system, and a few other partitions failed during flash due to not passing the checksum. I thought it would be a good idea to remove each partition that failed and just try to flash the partitions that would flash. I believe the partitions that did not flash failed because this firmware build was not the proper baseband version for my phone. I kind of just guessed which firmware build to pick. I guessed because my phone was already softbricked from improper flashing before. I could not obtain the baseband version. That would explain why the locked partitions did not pass checksums.
My half-assed plan to flash only the partitions that would go through worked... kinda. I managed to get a bunch of partitions to flash including modem, keymaster, cmnlib, cmblib64, persist and some others. Immediately after flashing, the device just went black. It is now not responding to any inputs or turning on. I cannot boot to recovery or download. It's completely bricked.
I heard it should be near-impossible to brick due to having a locked bootloader, but this is pretty bricked to me. I have let it sit, not plugged in for half an hour now in hopes that I can get it to turn on after a few hours of discharging or something.
Any way to fix this? Can I take it in to a local repair store to get it unbricked? Any help would be greatly appreciated.
Thanks.
Use Odin3 v3.13.1 It is a windows based program to flash Samsung phones.
ff-racer said:
Use Odin3 v3.13.1 It is a windows based program to flash Samsung phones.
Click to expand...
Click to collapse
Thank you for your reply. It doesn't matter now what tool I use.
At this point, my phone is bricked. No software can pick up the phone now.
I noticed you are trying to flash a Marshmallow OS? Why not try one of the newer roms listed in this forum. I am using Oreo.
Link: https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-g930tuvu4cri2-t3864700
ff-racer said:
I noticed you are trying to flash a Marshmallow OS? Why not try one of the newer roms listed in this forum. I am using Oreo.
Link: https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-g930tuvu4cri2-t3864700
Click to expand...
Click to collapse
Hi again. The stock S7 T-Mobile variant has a locked bootloader so I wouldn't even be able to flash anything except stock...
That's still not the point. My phone is bricked so I would not be able to flash anything at the moment. The point of this thread is to search for an answer about maybe why my phone is bricked and if there's any way to fix it without a JTAG.