Related
Hello everybody this is my first post on this site but it has be invaluable to me in the past for getting phones up and running.
I have a photon q that received a forced update to JB i rooted the phone put CWM on and flashed a stock 4.0.4 ROM to it (asanti_c-user-4.0.4-7.7.1Q-6_SPR-125_ASA-10-11-release-keys-Sprint-US )
Everything appeared to have worked correctly (IE it boots, i can access the internet/youtube app, receive gmail .etc) however the play store wasn’t working.
Fast forward 2 days of debugging and I realized that somehow my IMEI and MEID are messed up ( 0 and 00000000000000 respectively)
I have been looking at ways to restore the IMEI to the phone (i have to original number as it came on the screen protector when I bought the phone), however I cannot seem to find a method that will work with the photon Q.
Tried the terminal emulator method, After reboot nothing has changed.
Can’t find the /EFS folder (after looking that one up i do not believe it exists on this phone) so the method of manipulating the files within won’t work.
So the meat and potatoes of my question is how do i put my IMEI number back into my phone so I can use it again?
thank you in advance
Arckonicon
Did you try using RSD Lite to flash the phone back to factory?
RSD lite
I Used RSD lite to flash the ROM.
As far as I know that rom is a factory/stock ROM.
If it is not where would I go about finding a factory ROM?
Arckonicon said:
I Used RSD lite to flash the ROM.
As far as I know that rom is a factory/stock ROM.
If it is not where would I go about finding a factory ROM?
Click to expand...
Click to collapse
Ah, OK I was mistaken about how you flashed the device...
I'm not sure why that would or how it could erase your IMEI, I have used it many times.
That is why I am confused i have done this for other peoples phones prolly 20 or 30 times and I have never had an issue with it.
untill i go to do my own
So i need to figure out a way to put my IMEI back onto the phone. like i said i have the number i just dont know how to get it back into the device... :/
Still unable to find information on how to fix this.
I have however found out that there are three differant versions of the "stock" firmware for the same version and same model.
I am going to attempt to try them all and I will post results here.
FIXED
After looking the problem over i determined that my phone must have shipped with a different firmware than the "stock" one I had flashed. I found 2 other 4.0.4 firmware "stock" ROMS. they are all stock but some of them shipped on different devices. I guess with this phone you have to have the exact same "stock" firmware that came with it.
what I did
found and downloaded the other ROMS (will post the site to get them if I am allowed)
re-flashed the ROMS until one automagicaly had my IMEI number populated (i double checked against the number I had written down from when I got the phone and they are the same so it is not a "fake" IMEI)
I hope others who have this problem will find this helpful.
Arckonicon said:
After looking the problem over i determined that my phone must have shipped with a different firmware than the "stock" one I had flashed. I found 2 other 4.0.4 firmware "stock" ROMS. they are all stock but some of them shipped on different devices. I guess with this phone you have to have the exact same "stock" firmware that came with it.
what I did
found and downloaded the other ROMS (will post the site to get them if I am allowed)
re-flashed the ROMS until one automagicaly had my IMEI number populated (i double checked against the number I had written down from when I got the phone and they are the same so it is not a "fake" IMEI)
I hope others who have this problem will find this helpful.
Click to expand...
Click to collapse
i mean that erasing imei is impossible on photon...simple question...is your phone switched to gsm mode?
Arckonicon said:
After looking the problem over i determined that my phone must have shipped with a different firmware than the "stock" one I had flashed. I found 2 other 4.0.4 firmware "stock" ROMS. they are all stock but some of them shipped on different devices. I guess with this phone you have to have the exact same "stock" firmware that came with it.
what I did
found and downloaded the other ROMS (will post the site to get them if I am allowed)
re-flashed the ROMS until one automagicaly had my IMEI number populated (i double checked against the number I had written down from when I got the phone and they are the same so it is not a "fake" IMEI)
I hope others who have this problem will find this helpful.
Click to expand...
Click to collapse
Hi dude
I faced the same problem
Could you post the site to download roms?
Please help me
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 haven't been able to find anything specific in the threads, so this may be an odd request.
I recently needed to pull some texts from an old backup from CWM. I can see it saved on my external storage, but something messed up in the memory(?) and I kept getting error messages in Odin mode telling me I needed to use the Software Repair Assistant.
Everything I found and tried on here would fail in Odin, no matter what file I was trying to install or which directions I followed.
The phone ended up not booting at all, just going to the repair assistant screen whether it was a normal or download mode boot.
I got frustrated the other night and just used the Samsung emergency repair tool. Now it is back to working properly, but everything I read on here is saying nothing is really going to work on 4.4.2 with the VRUDNE1 baseband.
Before I mess it up again and try rooting and restoring back to an older version (4.3 I think) which will probably mess up, is there any way I can go in to the save files and pull the texts?
nebbernoo said:
I haven't been able to find anything specific in the threads, so this may be an odd request.
I recently needed to pull some texts from an old backup from CWM. I can see it saved on my external storage, but something messed up in the memory(?) and I kept getting error messages in Odin mode telling me I needed to use the Software Repair Assistant.
Everything I found and tried on here would fail in Odin, no matter what file I was trying to install or which directions I followed.
The phone ended up not booting at all, just going to the repair assistant screen whether it was a normal or download mode boot.
I got frustrated the other night and just used the Samsung emergency repair tool. Now it is back to working properly, but everything I read on here is saying nothing is really going to work on 4.4.2 with the VRUDNE1 baseband.
Before I mess it up again and try rooting and restoring back to an older version (4.3 I think) which will probably mess up, is there any way I can go in to the save files and pull the texts?
Click to expand...
Click to collapse
I haven't seen a way to do it yet. If your already on 4.4.2 you can't revert back to an older version. Doing so will cause a soft brick
Sent from my Nexus 5
ShapesBlue said:
I haven't seen a way to do it yet. If your already on 4.4.2 you can't revert back to an older version. Doing so will cause a soft brick
Sent from my Nexus 5
Click to expand...
Click to collapse
Would I be able to flash it onto another device that hasn't been updated to 4.4.2? On say a Motorola RAZR M? Or would it have to be a pre 4.4.2 Galaxy S3?
nebbernoo said:
Would I be able to flash it onto another device that hasn't been updated to 4.4.2? On say a Motorola RAZR M? Or would it have to be a pre 4.4.2 Galaxy S3?
Click to expand...
Click to collapse
It would have to be a S3. Flashing the software intended for an S3 to another device won't work, I am not saying that this will 100% work
Sent from my Nexus 5
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
I know more about Motorola Droid phones. This is phone is new to me. I did do a lot of research out there and mainly on XDA. I have the option to return the phone for a full refund. I would like to see if I can fix the phone before hand. I have till this weekend to send it back.
Claps1775 said:
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
Click to expand...
Click to collapse
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Droidriven said:
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes and yes. Okay. I know with droids when I was bootloader locked and rooted. I was fine updating. There was a change on loosing root. It's all about learning. I will try to find out how to unblock my phone. Thank you for the response.
Have you came across the ota .IMG file?
I was able to power my phone off. I connected the phone to my computer, installed the software, and tried the repair part. Failed on downloading. Version on my phone is 1.102VZ.
I found more info on xda refuring to the http://4pda.ru/forum/index.php?showtopic=597313&st=3680 site. I am not able to do anything with my phone now. Cannot get it to boot in recovery or even have my pc see it. The verizon apk sees it where I can still try to repair or update. That is it. I am going to send it back for a full refund and be done with this phone. Cannot spend weeks trying to fix this right now. Thanks all for the help.
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
I was able to flash the Rom_5.1.1_3153LR_Modem_3153LR_E6782 and my phone booted up and went into the optimizing but it is in Russian. I am further than I was. Need to find out if this is changeable to English and it all works. Yes, I do know that I will not flash anything than 5.0 now since the bootloader is locked or it can be unlocked with a code. Phone is up and running. I need a 5.1.1 US now.
It is not in Russian. It is in vietnamese. But I still need a clean 5.0 full rom.
Claps1775 said:
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
Click to expand...
Click to collapse
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I will try that. I have to get it into fastboot and that can take a few tries. The firmware I have on it has no verizon apps. It is a mod by someone. I am going to try original firmware 5.1.1 firmware. Downloading right now. it is a .rar file. Making head way witch is good. I am learning for sure.
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Claps1775 said:
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Click to expand...
Click to collapse
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Claps1775 said:
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Click to expand...
Click to collapse
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Claps1775 said:
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Click to expand...
Click to collapse
When some, lose some.
For future reference, when you want to update or modify a device, try doing some research into what NOT to do or what can go wrong with that particular device and how to fix it if it does BEFORE you focus on what CAN be done on that device and before you actually do anything to the device. Cover the bases, ask questions, search for issues others might have had when they modified their device.
Remember, just because something is available for that device, doesn't mean you can use it. Things change from android version to android version and this stock firmware to that stock firmware for a device, such as whether the bootloader is locked or unlocked, among other possible differences that can turn things into a train wreck.
Android devices are all different and are not all done the same. What and how it is done on "this" device is not the same on "that" device.
Sent from my SM-S903VL using Tapatalk
Edit: I got it back to proper firmware, but now have an issue with re-locking the bootloader so that I can install an OTA and make my sim card recognizable again. "Still waiting for signed boot.img"; can anybody provide a DL link to a signed boot.img for my specific model? [PCO29.114-54-2]
I'll try to keep this short and simple. It's my first post to these forums (hi), so sorry if I say stuff that sounds really simple or silly.
So, for a while now, I was dealing with a lot of really minor issues on my phone that I was told by those I asked was corruption in the android stock firmware. It wasn't anything major, but the issues were building up, and factory resets weren't fixing any of them. So, with my phone already out of warranty, I decided there wouldn't be any harm in trying to fix it myself. After reading up on it a little, I unlocked my bootloader, then I decided I would try flashing a custom ROM.
Well... I didn't even get that far. I was trying really hard to use the TWRP to back up my phone, but it kept getting errors. Looking it up, people said you just have to delete corrupted files to make it work, so I went back and forth wiping the files that gave it issues, until eventually I just decided to give up because there were so many corrupted files, just in the boot folder alone. When I went to turn the phone on and throw in the towel... I got the dreaded bootloop.
I freaked out, and decided that since I could still get into fastboot mode, I would try to stock the flash firmware to fix it. So, I went online, just found stock firmware, ran a batch file that did it all automatically, and...
When I turned my phone on, it was for the complete wrong carrier. Previously, it was a device I bought from T-Mobile, and thus, I was using a sim card and all that from them. Now the device is tied to Cricket, and so, of course, that stuff doesn't work.
Weirdly, there's other issues on the device now too, like when trying to add a Google account, the phone just closes out of everything...
Well.
I do know there's a guide here for how to flash the phone back to original firmware (although they don't have my firmware (M3DE6) listed), but there's other issues now, too. Stuff like the IMEI are totally wiped from the phone's memory now, just being listed as "Unknown" in the phone's settings. Not to mention, everytime I turn on the phone, I get text that says "bad ID" and it takes an additional 10-15 seconds to turn on. Is there any way to fix all this stuff? I don't mind if I have to restore it to OG stockware or if flashing a custom ROM will fix the problem- I just really need my phone to be able to work with my sim card again so I can take and make calls/texts.
I've still got to pay on my phone for a year still via the contract I made with T-Mobile, so it'd really suck if my phone got stuck in an unusable condition like this. If there's anybody who could just help me get it back to WORKING condition (calls/texts, google accounts, etc.), then I would greatly appreciate that. Thanks.
Tsukomasi said:
I'll try to keep this short and simple. It's my first post to these forums (hi), so sorry if I say stuff that sounds really simple or silly.
So, for a while now, I was dealing with a lot of really minor issues on my phone that I was told by those I asked was corruption in the android stock firmware. It wasn't anything major, but the issues were building up, and factory resets weren't fixing any of them. So, with my phone already out of warranty, I decided there wouldn't be any harm in trying to fix it myself. After reading up on it a little, I unlocked my bootloader, then I decided I would try flashing a custom ROM.
Well... I didn't even get that far. I was trying really hard to use the TWRP to back up my phone, but it kept getting errors. Looking it up, people said you just have to delete corrupted files to make it work, so I went back and forth wiping the files that gave it issues, until eventually I just decided to give up because there were so many corrupted files, just in the boot folder alone. When I went to turn the phone on and throw in the towel... I got the dreaded bootloop.
I freaked out, and decided that since I could still get into fastboot mode, I would try to stock the flash firmware to fix it. So, I went online, just found stock firmware, ran a batch file that did it all automatically, and...
When I turned my phone on, it was for the complete wrong carrier. Previously, it was a device I bought from T-Mobile, and thus, I was using a sim card and all that from them. Now the device is tied to Cricket, and so, of course, that stuff doesn't work.
Weirdly, there's other issues on the device now too, like when trying to add a Google account, the phone just closes out of everything...
Well.
I do know there's a guide here for how to flash the phone back to original firmware (although they don't have my firmware (M3DE6) listed), but there's other issues now, too. Stuff like the IMEI are totally wiped from the phone's memory now, just being listed as "Unknown" in the phone's settings. Not to mention, everytime I turn on the phone, I get text that says "bad ID" and it takes an additional 10-15 seconds to turn on. Is there any way to fix all this stuff? I don't mind if I have to restore it to OG stockware or if flashing a custom ROM will fix the problem- I just really need my phone to be able to work with my sim card again so I can take and make calls/texts.
I've still got to pay on my phone for a year still via the contract I made with T-Mobile, so it'd really suck if my phone got stuck in an unusable condition like this. If there's anybody who could just help me get it back to WORKING condition (calls/texts, google accounts, etc.), then I would greatly appreciate that. Thanks.
Click to expand...
Click to collapse
U in USA if so I could try the reuts think that's how it spelled TMobile is same as crickit if I member right so u can flash the retail firm where if u in the states.I on cc but not the firmware for them I'm in the retail version works great no added junk ware either
roadkill42 said:
U in USA if so I could try the reuts think that's how it spelled TMobile is same as crickit if I member right so u can flash the retail firm where if u in the states.I on cc but not the firmware for them I'm in the retail version works great no added junk ware either
Click to expand...
Click to collapse
I did find my device's actual stock firmware from another website and installed it, but now the sim card doesn't work. I've heard that if I perform an OTA update, it'll make it work again, but... I can't perform an OTA update because the bootloader is unlocked. I can't re-lock it, because everytime I try, it gives me a message that says "Still waiting for signed boot.img".
Someone said to use the rescue and smart assistant app, but it doesn't recognize my phone, so that's a no-go.
Tsukomasi said:
I did find my device's actual stock firmware from another website and installed it, but now the sim card doesn't work. I've heard that if I perform an OTA update, it'll make it work again, but... I can't perform an OTA update because the bootloader is unlocked. I can't re-lock it, because everytime I try, it gives me a message that says "Still waiting for signed boot.img".
Someone said to use the rescue and smart assistant app, but it doesn't recognize my phone, so that's a no-go.
Click to expand...
Click to collapse
Have u done the factory reset after flashing the software? U might have to reflash the modem look through this sight or tellagram for how to
roadkill42 said:
Have u done the factory reset after flashing the software? U might have to reflash the modem look through this sight or tellagram for how to
Click to expand...
Click to collapse
I tried a ton of different fixes and approaches, and I still can't get it to work. I'm gonna make a new thread now since I've got a new main issue to deal with. This is... a mess.
Tsukomasi said:
I tried a ton of different fixes and approaches, and I still can't get it to work. I'm gonna make a new thread now since I've got a new main issue to deal with. This is... a mess.
Click to expand...
Click to collapse
Sorry
roadkill42 said:
Sorry
Click to expand...
Click to collapse
Nah, don't worry about it. I'm the one who messed up my phone.
Tsukomasi said:
Nah, don't worry about it. I'm the one who messed up my phone.
Click to expand...
Click to collapse
Here is the bat fille just change the zip to bat then get the retus file I'm looking for the link of the software I used it is lol. https://www.lolinet.com/. Pm me I can tell u how to set it up. https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/