I flashed the Google assistant some time ago and everything was fine but yesterday I decided to do some minor build prop edits and accidentally bricked my phone. Now that's fine because they have multiple ways of unbricking the T-Mobile LG v20. But when I tried to unbricking it using LGup nothing works because it registers my phone as a pixel and now my phone can't be restored. So take it from me..Don't do it!!! It isn't worth the loss. I have a brick now. An official lg v20 brick. Sigh
EDIT:
IM EDITING THIS TO ADD WHAT I DID.
Here's the story
I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.
Do you not have TWRP you can reboot into, and re-flash a backup or new ROM?
CharlzO_2000 said:
Do you not have TWRP you can reboot into, and re-flash a backup or new ROM?
Click to expand...
Click to collapse
Nope, the only thing my phone does it boot into the mode where it says "Firmware update" mode. I really think I destroyed my phone.
remix435 said:
Nope, the only thing my phone does it boot into the mode where it says "Firmware update" mode. I really think I destroyed my phone.
Click to expand...
Click to collapse
Take it to the store and tell them it happend when the phone was updating.
slayerh4x said:
Take it to the store and tell them it happend when the phone was updating.
Click to expand...
Click to collapse
That's actually a pretty good idea. I'm going as soon as TMobile opens.
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Leonarddale said:
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Click to expand...
Click to collapse
This.
remix435 said:
I flashed the Google assistant some time ago and everything was fine but yesterday I decided to do some minor build prop edits and accidentally bricked my phone. Now that's fine because they have multiple ways of unbricking the T-Mobile LG v20. But when I tried to unbricking it using LGup nothing works because it registers my phone as a pixel and now my phone can't be restored. So take it from me..Don't do it!!! It isn't worth the loss. I have a brick now. An official lg v20 brick. Sigh*
Click to expand...
Click to collapse
That is very strange, I recently bricked my phone to the point where I didn't have a system at all on it. When you boot to firmware update mode (power + volume up) and pluged it in LGUp recognized it instantly. You have the correct DLL for your device right?
shadowxaero said:
That is very strange, I recently bricked my phone to the point where I didn't have a system at all on it. When you boot to firmware update mode (power + volume up) and pluged it in LGUp recognized it instantly. You have the correct DLL for your device right?
Click to expand...
Click to collapse
My issue was that when I flashed the assistant mod it turned my device name into " google pixel" so when I hooked it up to lgup it read it as a pixel and failed the restore every time. That was the issue I couldnt change the name of my devixe back to the v20.
Leonarddale said:
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Click to expand...
Click to collapse
I disnt have anything on my phone. No twrp and I couldnt install it. The assistant mod changed my device name to PIXEL and when id connect it to the pc it read as a pixel and failed every update I LG V20 I pushed to it..that was a new type of brick lol. But I told t mobile that if I what happened and I got another one.
These old assistant mods would be taken down. The only thing needed to enable it without spoofing a phone as a Pixel is adding "ro.opa.eligible_device=true" to build.prop, and the Google app updated via Play Store.
remix435 said:
My issue was that when I flashed the assistant mod it turned my device name into " google pixel" so when I hooked it up to lgup it read it as a pixel and failed the restore every time. That was the issue I couldnt change the name of my devixe back to the v20.
Click to expand...
Click to collapse
That's the thing my phone didn't have a system on it at all and LGUp read it as what it was. When you on the firmware screen it should read based on hardware ID right? Have you tried using LG bridge? Are you on the T-Mobile variant?
This is a contributing factor in why these companies lock bootloaders. People do stupid things because they don't know what they're doing and then others encourage them to just return it and get a new one and lie. Not cool at all. How about don't root your phone if you don't know what you're doing.
markbencze said:
This is a contributing factor in why these companies lock bootloaders. People do stupid things because they don't know what they're doing and then others encourage them to just return it and get a new one and lie. Not cool at all. How about don't root your phone if you don't know what you're doing.
Click to expand...
Click to collapse
WTF! With your logic no one would learn anything.
My phone was rooted just fine. How was I suppose to know that after I flashed the stock build prop my phone was going to stay as a pixel device?? That wasn't stupid of me that was trial and error. Something stupid is if I did it again. No one specified that my phone would stay as a pixel device, go read the instructions and tell me where it says that. Also, I have "Jump on demand" so I used one of my jumps to get a brand new phone..So I paid a price for it. It wasn't just "me lying and getting a free phone" I still paid for it I paid for my mistake and Yes initially I lied but still paid and am still paying for this phone. Plus I have an s7 edge and a Huawei honor note 8 all rooted and have never ran into any issues. Why?? Because I never did what people instructions told me not to do. I always follow instructions. I've been rooting phones since I was a milk drinker all the way back to the G1 days. I'm very careful but if instructions don't cover all the basis then what?? PEOPLE, including me should continue to root and try new things. But you can't blame them if YOU(not you in particular but in general) as a developer make something and can't catch all the bugs(it isn't The developers/modders fault either)..Modding is a giant community of trial and error. The only people at fault are idiots who don't read and do some ****. Other than that we are all out here finding our way with these new devices. So yes, I have a new v20 that I paid for with MY "Jump on demand" plan that is now rooted and unlocked. Now am I going to use the Google assistant mod again?? No, because that would be stupid of me. Now get off my post.
I was just warning people so they wouldn't make the same mistake as me.
Whats the stupid part is how you managed to erase TWRP and lose access to fastboot on your device. Not that your changed something in build.prop. His logic is not flawed, whatever you did to lose access to the two essential parts of having a rooted phone is the flaw here.
Also simply doing build.prop edits should not make you lose access to TWRP nor being able to access fastboot - or did you relock your bootloader?
twistedvip said:
Whats the stupid part is how you managed to erase TWRP and lose access to fastboot on your device. Not that your changed something in build.prop. His logic is not flawed, whatever you did to lose access to the two essential parts of having a rooted phone is the flaw here.
Also simply doing build.prop edits should not make you lose access to TWRP nor being able to access fastboot - or did you relock your bootloader?
Click to expand...
Click to collapse
In stead of assuming what happened with my device how about y'all ask me the details first. But coming off the bat assuming that I just did foolishness is asinine.
I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.
So once again where's the stupidity on my part when I didn't know that my phone was still going to be labeled a a pixel after a factory reset? Please, both of you have several seats in the back.
All I'm doing is warning people about what could possibly happen. Y'all can miss me with your unnecessary opinions and comments.
No I appreciate you wanting to warn the community, but you most certainly did not post that story. You posted saying you got bricked from doing edits to your build.prop and then because of using a Google assitant mod you are hard bricked. Post that entire story as a warning because even having your phone appear as a Pixel won't do any harm - but flashing a .kdz and having it fail midway may indeed cause harm. Lack of details causes much misinformation to spread around quickly
twistedvip said:
No I appreciate you wanting to warn the community, but you most certainly did not post that story. You posted saying you got bricked from doing edits to your build.prop and then because of using a Google assitant mod you are hard bricked. Post that entire story as a warning because even having your phone appear as a Pixel won't do any harm - but flashing a .kdz and having it fail midway may indeed cause harm. Lack of details causes much misinformation to spread around quickly
Click to expand...
Click to collapse
My bad I'll edit it. And apologies for the response tone.
It's called taking responsibility. You had a phone with root and did something stupid. Instead of taking responsibility you lie and tell them the phone is defective. That is 100% your fault. I bet it worked fine before you started messing with it. Whatever man I'm gonna let this be but you can bet that when these companies look at the supposed drfrctive returned phones and see they have been tamperred with and that people are being dishonest to get a new phone when they're the sole reason the phone stopped working, eventually they will all say screw it and just lock everything down.
Hopefully you learned from this.
markbencze said:
It's called taking responsibility. You had a phone with root and did something stupid. Instead of taking responsibility you lie and tell them the phone is defective. That is 100% your fault. I bet it worked fine before you started messing with it. Whatever man I'm gonna let this be but you can bet that when these companies look at the supposed drfrctive returned phones and see they have been tamperred with and that people are being dishonest to get a new phone when they're the sole reason the phone stopped working, eventually they will all say screw it and just lock everything down.
Hopefully you learned from this.
Click to expand...
Click to collapse
Actually the phone had a few random rebootsa and use to freeze on stock. I decided to keep it because of the note 7 fiasco and I was too frustrated and pissed to return it and then they ran out. So this was well over due. But once again you know nothing Jon snow. And yes I did lie but this device already had issues. Soooo???
Related
A day or two ago I unlocked my ChaCha using the HTCDev.com instructions. I then used DooMLoRD_v4_ROOT-zergRush-busybox-su to root it. Everything was going fine until I apparently deleted one too many system apps and now my phone is in extremis.
The problem: As the phone boots up and reaches the HTC logo screen, just when the main interface should appear, an error pops up. It says:
Code:
Sorry!
The process com.htc.bg has stopped unexpectedly. Please try again.
[Force close]
When I close it, the HTC logo appears again as the main GUI is reinitialised, which leads to the same error popping up again, thus entering into an infinite loop.
I can just about manage to connect the phone to my PC as a disk drive, but it's not connected in such a way that RUU or unrooting applications can "find" it from within Windows, so if I'm to fix this it's gotta be from the SD card/Hboot.
Details:
* HTC ChaCha with the latest Android firmware.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
* Factory resets and recovery boots don't seem to have any effect.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Is there any hope of fixing this issue given my obvious lack of critical faculties?
Thank you for reading this.
You can always install clockworkmod recovery and from there a custom rom. Check the relevant thread, it is pinned.
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
Click to expand...
Click to collapse
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
Click to expand...
Click to collapse
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
Click to expand...
Click to collapse
You can't restore a system app if there is a conflict. Try and identify the conflict.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
Click to expand...
Click to collapse
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
* Factory resets and recovery boots don't seem to have any effect.
Click to expand...
Click to collapse
See above about freezing.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
Click to expand...
Click to collapse
Doesn't matter, you'll fix it, guarantee it.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
Click to expand...
Click to collapse
See what I said above.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Click to expand...
Click to collapse
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
For a safe to remove list, check the Themes and Apps section.
skezza said:
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Click to expand...
Click to collapse
Music to my ears!
skezza said:
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
Click to expand...
Click to collapse
In Titanium Backup I tried restoring the backups I made; the "Recovering Backup" notice would just hang indefinitely until I forced TB to close. This only happened with system apps. The backed up files are still on my PC hard drive from when I copied them from my SD card, but I'm not sure they're of any use at this stage.
skezza said:
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
Click to expand...
Click to collapse
Ahhh, this is probably my problem then. I ignored most of the fixes and workarounds listed as [S-OFF] because I didn't think they'd work for my device haha.
skezza said:
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
Click to expand...
Click to collapse
I'm disappointed in myself for being so haphazard in my deleting, I'm usually not that stupid but I think I was a little overexcited to have finally gotten rid of some of the bloatware that'd irritated me for so long haha. I was like "oh boy, I can save even more battery power and internal space if I just remove a little more!". Lesson learnt
skezza said:
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
...
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
Click to expand...
Click to collapse
As I said above I didn't realise I could make use of [S-OFF] materials so I didn't even attempt them for fear of making matters worse. I just now attempted to flash CWM and it hung on "parsing" which is what happened with previous flash attempts. If a flash attempt doesn't hang on "parsing" it parses for a second and then goes back to the main menu, apparently having no effect.
I'd be lying if I said I'm not overwhelmed by all of this; the tutorials I've read seem to assume a fair degree of prior knowledge that I definitely don't have haha. I hope I don't stretch anyone's patience here, but if you could explain it to me like a 6-year-old whose mother drank heavily during pregnancy I think it will help move things along!
Thank you for the thorough reply, much appreciated
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
dapaua said:
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
Click to expand...
Click to collapse
Unfortunately I can't do anything via my computer; my phone isn't "discovered" by the command line, unrooting tools or anything else. It does allow me to access the SD card as a hard drive but that's all it does. Obviously this wasn't the case before my problems started, because I used my PC to root and unlock the phone originally, but now the phone's boot process can't reach a point where it becomes receptive to the PC's commands. I don't know why it lets me access the SD card though.
Is there any way to do this without my PC being involved beyond transferring files to the SD card? If not, am I screwed? haha
Thanks mate!
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
The fastboot binary is here C:\Program Files (x86)\Android\android-sdk\tools , if you installed the android SDK, which I asume you did.
Good luck, I hope this works!
dapaua said:
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
Click to expand...
Click to collapse
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
dapaua said:
Good luck, I hope this works!
Click to expand...
Click to collapse
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
PaddyM said:
Dear CHRIST thank you for that - I didn't...
Click to expand...
Click to collapse
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
PaddyM said:
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
Click to expand...
Click to collapse
I'm happy it worked. Let's hope WiFi technology improves in the future
skezza said:
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
Click to expand...
Click to collapse
I knew about the recovery menu (the stock one, at least) but I didn't realise I could go into the Fastboot option and for the phone to then be recognisable to the PC, thus making it possible to flash via the command line. If I had known that I probably wouldn't have needed to post this thread at all haha.
skezza said:
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
Click to expand...
Click to collapse
Yeah... I think if it happened to one of you guys you probably would have had it sorted in about 6 minutes. 3 days isn't bad for my first attempt though! hahaha
skezza said:
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
Click to expand...
Click to collapse
Thanks for the advice man, I'll definitely be looking into the Nandroid backup option, although I hope I've learnt enough from this experience to have no need for it
Thanks to everyone who posted here, I appreciate the patience and the tolerance of my noobery.
Funnily enough, I tried TitaniumBackup today and the original poster is correct. While you can freeze, remove apps etc, you can't return them. especially system. I've not tried any of the alternative install methods that TB uses, but it's quite interesting.
TB is a bit quirky, I think. The system apps won't restore at all, but sometimes apps that I've downloaded myself will restore and other times they won't (the "Restoring App" notice just hangs there indefinitely). I usually find that forcing TB to close and then trying again does the trick, but I can't figure out why it happens in the first place.
Im wondering if anyone else has worked out a good configuration that will allow it to work every time?
So, my wife decided to buy this phone, and I am to stay away from her phones. She smashed the screen one day, and that was a door open for me. I hastily get some version of TWRP to boot on it and grab a backup, and also do an adb backup (which was crap). Then, I did a full wipe before taking it in to get repaired.
SO, what I want to walk through here boys and girls, is never, never, never, never, put Smartisan OS 2.5.3 on this phone. When my wife got her phone back I harmlessly believed that updating would not disallow me from TWRP again to recover. What this version does to the device is completely disable recovery altogether. You are always pushed to fastboot, and fastboot cannot flash anything After this realization, I borked the phone, I dd'ed out the aboot and the sbl. She had insurance, we live in China it is cheap, and after the difficulties I realized this was happening to lots of people. I figured the local service center could re-write the partitions I had pooped on and they would re-write it with an earlier firmware. My gamble paid off.
Got the phone back with 2.5.0. I immediately followed the guide here http://tinyurl.com/z7ekyxp , Russian site, to revert back. I then, deviating from the guide to be careful, fastboot boot "twrp.img". I used commands the whole way, no flashify or anything (I love flashify on my nexus 5 but I had already borked this phone once. It booted TWRP, I copied all the old SD files over to the phone. Then, the moment of truth, would a restore from my previous backup work. Yes, it did. I even followed the guide through and flashed the 2.3.5 modified update. It worked, the SuperSU and open gapps flashed without issue also.
Not a horrible phone for being extremely cheap, but they messed up an update. For those fooling around with the device, remember the partition table has a bak for all boot related things. I also see on Chinese forums that they use the headphone jack for diagnostics (My Chinese isn't great, but I looked around when I bricked my wife's phone).
One thing of note with this device is there are three versions that appear in build.prop 32, 32_younger, 306_younger, I think, but Smartisan has confirmed they are all the same, just different production batches. If you get errors in the update process, modify this to match.
Don't drink and post children, I was editing to say I ran with what smartlinux on that site said, nothing here is my idea except for running the commands yourself.
Another good dev on the device but Chinese http://blog.cofface.com/archives/1139.html. He has an app that will boot into either (stock or custom) recovery, but like I said, do not take that 2.3.5 thing. I see they have 2.5, so let's see what happens.
wangdaning said:
Another good dev on the device but Chinese http://blog.cofface.com/archives/1139.html. He has an app that will boot into either (stock or custom) recovery, but like I said, do not take that 2.3.5 thing. I see they have 2.5, so let's see what happens.
Click to expand...
Click to collapse
Hey bro, you're a native American working in Chengdu?
xcjchandler said:
Hey bro, you're a native American working in Chengdu?
Click to expand...
Click to collapse
Yep.
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
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. :/
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/