Related
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Dr. Light said:
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Click to expand...
Click to collapse
first of all you can't flash anything on a stock recovery hence the need of a custom recovery. Second you don't accept the OTA when rooted as it can cause the exact issue that you have. Last there isn't a way to fix your problem via another android device that I know of.
U are going to need a pc and then u will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery. Then you can access your backups.
Always_Jonezen said:
U will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery.
Click to expand...
Click to collapse
He doesn't have access to his PC PLUS he already knows what to do on that end.
jmxc23 said:
He doesn't have access to his PC PLUS he already knows what to do on that end.
Click to expand...
Click to collapse
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Thanks for all of advice guys. I'll prob just wait it out till Monday. Thanks again.
Always_Jonezen said:
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Click to expand...
Click to collapse
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
jmxc23 said:
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
Click to expand...
Click to collapse
hey all, I've been reading , downloading etc for hours trying to get back into my GS3.. i was as usual roaming around and saw a post that said something to this effect "do ya need to get back to stock?" and figured yes i need to so i jumped in with both feet ..i had my boot loader unlocked and for some reason locked the darned thing remembering it was locked before i rooted and then i get the screen that says ie: "System software not authorized ~~~~~~~~~~~~" with a yellow triangle over it with an "!" mark in it..
all would have been ok except the line up of the way to do things was kinda outta line.. after i had locked bootloader "which is the way the GS3 came" i thought. at any rate i am now where i said i was and if i can be helped it would be appreciated.. and no repeated.. next time i'll read their whole line up first.. so help me if ya can and i am game right now for about anything ..
So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?
Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium
Any ideas?
Sent from my LG-LS970 using xda premium
Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.
No one can help?
Sent from my LG-LS970 using xda premium
Well that sucks...
Sent from my LG-LS970 using xda premium
Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.
I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.
I am currently running 4.4.4 but I want to go back to 4.2.2 stock rom that came with the phone and I want to root it. My bootloader is unlocked. And I did a recovery and wiped the phone within Android and it just went back to 4.4.4 not 4.2.2 like it did before. I went to fastboot and tried to go into recovery and wipe the cache but the phone just rebooted. I was able to wipe the cache before...maybe I did something wrong...I am very new to this and have downloaded so much stuff to do this but im sooooooo lost
Also Fastboot says that device is UNLOCKED, Status Code 3
Knight71 said:
I am currently running 4.4.4 but I want to go back to 4.2.2 stock rom that came with the phone and I want to root it. My bootloader is unlocked. And I did a recovery and wiped the phone within Android and it just went back to 4.4.4 not 4.2.2 like it did before. I went to fastboot and tried to go into recovery and wipe the cache but the phone just rebooted. I was able to wipe the cache before...maybe I did something wrong...I am very new to this and have downloaded so much stuff to do this but im sooooooo lost
Click to expand...
Click to collapse
factory resetting and wiping does nothing but remove data.
to get back to an older version, you will need to get the factory firmware file and flash it to the phone with rsd lite (tutorials can be found through google). afterwards, find a custom recovery that is compatible with the version you installed, install it, then grab the superuser flashable zip and flash in recovery to get your root back.
Sorry it took me so long to reply back. I drive truck OTR and I put in some long days. Ok I have some time to get this down and understood I will be going for my hometime at the end of this month for about 4 days because my phone is the only way that I can get online out here.
So I have a XT1080 Dev Ed. And I have a copy of a factory image from Motorola for my phone TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_1FF.xml.zip. Now how do I flash it do I have to unzip it or put it in a folder or??? And also (custom recovery that is compatible with the version you installed) do you mean using TWRP. Also what does Status code 3 mean and do I have to turn of Write Protection and if so how.
I am so sorry for being a noob at all of this. My old phone was a Droid Global 2. It was ok until it got old and unresponsive I used FoxFi to get online while I was out on the road. Then I decided to go and get me a new phone and I hear about the Droid Maxx and the awesome battery life on it so I decided to get it...But I had to Pay full price for it. 650 plus 50 for tax 700 total. The reason behind that is that I have unlimited data and I did not want to lose it.
Knight71 said:
Sorry it took me so long to reply back. I drive truck OTR and I put in some long days. Ok I have some time to get this down and understood I will be going for my hometime at the end of this month for about 4 days because my phone is the only way that I can get online out here.
So I have a XT1080 Dev Ed. And I have a copy of a factory image from Motorola for my phone TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_1FF.xml.zip. Now how do I flash it do I have to unzip it or put it in a folder or??? And also (custom recovery that is compatible with the version you installed) do you mean using TWRP. Also what does Status code 3 mean and do I have to turn of Write Protection and if so how.
I am so sorry for being a noob at all of this. My old phone was a Droid Global 2. It was ok until it got old and unresponsive I used FoxFi to get online while I was out on the road. Then I decided to go and get me a new phone and I hear about the Droid Maxx and the awesome battery life on it so I decided to get it...But I had to Pay full price for it. 650 plus 50 for tax 700 total. The reason behind that is that I have unlimited data and I did not want to lose it.
Click to expand...
Click to collapse
unzip the factory file to a folder, inside there is a "xml" file, that is the target file you load into rsd lite.
before you start with rsd you will likely have to edit the xml first. right click it and choose edit. you are looking for any lines that contain "getvar". if you see that, delete the hole line from end to end (may be more than 1), then close and save when prompted.
now you can flash with rsd as usual.
yes twrp or cwm
status code 3 just means that the bootloader is unlocked.
as far as i know that should be all there is to it, i dont have this device so im just stating general moto flash procedures. if you found something about write protection that im not aware of, post a link and ill have a look at it.
here is the su zip you will need to install root after you install twrp or cwm http://www.mediafire.com/download/nwxoj8b3k1u8xtv/UPDATE-SuperSU-v2.01.zip just flash as is in recovery.
btw, i have unlimited data too
Got to love Verizon. My bill would be so expensive if I got on there 10GB Tier plan...I would go way over that. But the things that we do to keep it...like buying a 700 dollar phone...LOL
What is getvar and also how do I see the partitions on my phone?
Well I have to hit the road but will be back on here tonight.
Knight71 said:
Got to love Verizon. My bill would be so expensive if I got on there 10GB Tier plan...I would go way over that. But the things that we do to keep it...like buying a 700 dollar phone...LOL
What is getvar and also how do I see the partitions on my phone?
Well I have to hit the road but will be back on here tonight.
Click to expand...
Click to collapse
i dont know what getvar is really, but if its there (occasionally not) and you dont remove it, rsd will fail. its nothing needed to flash, thats all i know.
not sure how you would look at the partitions. you can wipe them in recovery, but you really dont want to mess with anything you dont understand. if you wipe the wrong thing, you will be in big trouble, and a factory file cant fix it.
Ok...I downloaded the files. I did not know if there is more then one partition on my phone or not. I have never done this on a phone before...Its a learning curve for me. I cant do this now it will have to wait until I get home so that way I can get online and you can walk me threw all of the steps and commands I need to send to my phone.
Knight71 said:
Ok...I downloaded the files. I did not know if there is more then one partition on my phone or not. I have never done this on a phone before...Its a learning curve for me. I cant do this now it will have to wait until I get home so that way I can get online and you can walk me threw all of the steps and commands I need to send to my phone.
Click to expand...
Click to collapse
In the future, please quote me or I may miss your post like I just did.
Thanks
Sent from my G2 running SlimKat
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/