Related
EDIT:
SOLVED! Thanks for the support!
In the end I decided to flash back to stock factory image from Google downloaded at the following link (https://developers.google.com/android/nexus/images) and installed using the very easy method of inputting a single command. Exactly the kind of solution I needed after pulling hair out.
Hopefully this post is of assistance to others in need.
In the end I used the Chain Fire auto root. Worked a treat - so now running stock Nexus 5 image with root, just the way I wanted it.
http://forum.xda-developers.com/showthread.php?t=2507211
Original question:
Need help - I think I bricked my Nexus 5 (was running KOT49H stock ROM). And would really appreciate some sage advice now to get me out of trouble.
Not my first root, custom ROM experience - have done on 3 previous devices, but first Nexus 5 and first stuff up for me. Not a complete noob, but please be clear in your advice. Thanks.
I "followed" this guide (http://www.teamandroid.com/2013/12/10/root-nexus-5-android-442-kot49h-kitkat-install-cwm-recovery/2/)
However, at Step 13-15 I was unable to mount an SD card (Nexus 5 is all internal), and I then opted to sideload the UPDATE-SuperSU-v1.80.zip file using "adb sideload". It is now stuck in a boot animation loop (say 10mins of waiting?). So what has gone wrong here?
I also guides from the same site to unlock bootloader and install CWM - that all worked.
I am able to get back to the bootloader and can get into CWM still, just cannot boot.
Not sure if my phone is charging, but I believe I still have some juice so looking for a solution. Have I somehow replaced all of the ROM software with just the SuperSU file? Is that possible? This is my first outing with the Nexus 5 but I have rooted and custom ROMed many phones before, but this is my first with no external SD card.
I could not mount any / partition from what I could tell.... such as /data (not sure if this helps your advice?)
In another thread, someone mentioned a catch all solution might be this : http://forum.xda-developers.com/showthread.php?t=2513701
As I said, I can get into the bootloader and CWM and phone is still recognised by PC.
If I am not mistaken, this would basically sideload everything back to factory?
Would this matter if my phone was at KOT49H before everything went wrong, or will that just come down via OTA later anyway (I was getting OTA updates just fine).
I think I should still have about 50% battery charge, but I don't know if it is charging (nothing shows) and the battery is completely internal on these.
Your help = much appreciated! Please - its Christmas afterall...
Cheers Adriaan
Sorry to hear about your troubles! I know how frustrating it can be when you softbrick for no apparent reason. However, the fact the phone still boots into recovery and all that means that there shouldn't be anything we can't recover from. The link you provided would work. You might also check out one of the toolkits that helps automate most of the stuff you are looking for, like this: http://forum.xda-developers.com/showthread.php?t=2525026 .
That being said, me personally, I would attempt some fixes via CWM first (though I much prefer TWRP). It could be something as simple as wiping the caches and fixing permissions. Possibly a factory reset could help, though I suspect probably not at this stage. Are you comfortable with manual ADB and fastboot commands? I would download a rom zip and adb push it to /sdcard, perform resets and reboot. Should be fine at that point and rooted to boot. If you're all about the stock root experience (never really understood that, but to each their own ) then try this: http://forum.xda-developers.com/showthread.php?t=2557523
Once you would download that, and are able to get ADB access in recovery (should work if you have the right drivers and all - if not, would recommend switching to TWRP) then you would use this command:
adb push rom.zip /sdcard/ - where rom.zip is the name of whatever that one downloads as...
Then wipe factory reset and caches (system too if you want to be thorough) then install the rom and reboot. Should be back to where you want.
If you would like some more 1 on 1 type help, feel free to hit me up on Hangouts with this username. Good luck!
You can flash the factory images directly from Google which should get you back up and running again.
Download and extract them.
Boot your phone to the bootloader and plug into your PC.
Run the flashall.bat
Note that this will fully wipe your phone
Sent from my Nexus 4 using xda app-developers app
First reboot recovery and factory reset the phone. If it boots your good. If not install the google factory image.
Everyone, thank you for your input. My phone is back alive and well.
In the end, I decided to flash all back to a stock factory image from Google. Only had 1% battery left by the time it booted into the fresh flash. Figured this was the best place to recommence my efforts to gain root again, and hopefully this time with a better outcome.
I will probably give the chain fire auto method a shot this time, after a bit more research.
Thank you again for your help and for the very quick responses. Great community.
In the end I used the Chain Fire auto root. Worked a treat - so now running stock Nexus 5 image with root, just the way I wanted it.
http://forum.xda-developers.com/showthread.php?t=2507211
Today when I decided to update to the latest android (5.1.1) with rooted nexus 5. I rebooted
my phone and it started installing when suddenly a picture of the android robot with a red triangle sign on top appears and under it it says error so I restarted my phone by holding down the power button for several seconds and when I get in to my phone it says that I'm updated to 5.1. But what I understand that's correct so now I'm wondering how to deal with future updates because I can't afford to brick my phone and I thought I could just download OTA updates normally after root so my question is, can I normally install OTA updates, if not How?
[Edit]Later today I got the update to 5.1.1 message again and its really annoying and I want the update now so how do I get it?
Thanks for reading.
Hi, thank you for using XDA Assist. No, you can't use the OTA if your rooted with 5.x and above. To update you'll most likely need to flash the stock frimware. but you never let us know what your device is so i can't point you in the right direction.
jd1639 said:
Hi, thank you for using XDA Assist. No, you can't use the OTA if your rooted with 5.x and above. To update you'll most likely need to flash the stock frimware. but you never let us know what your device is so i can't point you in the right direction.
Click to expand...
Click to collapse
Thank you for answering, I have a nexus 5 but I guess I´ll have to flash the stock firmware if there is no other way that isn´t too complicated.
All right. You'll want to see these, http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 , http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 It's possible to update by only flashing the system, boot, and radio images files with fastboot. You'll lose root but you can easily regain it by flashing supersu in your custom recovery.
Also don't forget there's a complete forum for the Nexus 5 here, http://forum.xda-developers.com/google-nexus-5
jd1639 said:
All right. You'll want to see these, http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 , http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 It's possible to update by only flashing the system, boot, and radio images files with fastboot. You'll lose root but you can easily regain it by flashing supersu in your custom recovery.
Also don't forget there's a complete forum for the Nexus 5 here, http://forum.xda-developers.com/google-nexus-5
Click to expand...
Click to collapse
I just spent 2 hours trying to flash the system but all i ended up with was a factory reset after following this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 so all i want to do now is just getting rid of root so I can update but the guides that i understand doesn´t work because when I tried to flash the hammerhead bootloader it said the my device requires another version. The i took the version that my nexus is in right now 5.1.0 and it appeared to be working so when it was finished I followed the guide and i wiped my system for about 5 minutes and then i chose reboot system from the recovery mode menu. And now im back at where i started.
(Edit) Now I´m installing SDK and following another guide online http://www.talkandroid.com/guides/b...-lollipop-factory-image-on-your-nexus-device/
It turns out all i had to do was to unlock my phone and then I installed 5.1.1 just fine
Yep, that's the first step. Glad you got it working. I'll close this thread.
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!
Totally new to xda forum, and pretty much a noob. Nexus 5 (US model). I was trying to unroot my Nexus 5. I bought it from a friend who had rooted it using TWRP, and it was running CM. Anyway, I managed to completely wipe the operating system ... completely. It will boot using the power/volume down configuration, but when I try to start the phone, it says, "No operating system found." All the threads I have been reading (yes, I have done a lot of reading), assume a couple of things: 1) that the phone can get into Settings/Developer Mode; and, 2) that my PC finds my phone when I plug it in. I have tried the adb and fastboot driver downloads, and wound up with some weird app that was almost impossible to uninstall off my PC. Ten-something or other. I tried doing the flash-all thing, but got a message that there was no such command. Can anyone help me, either directly, or by links to what I need? Once again, I have no operating system on this phone. Thanks.
There's a cool tool kit called wugs nexus toolkit that will help some http://forum.xda-developers.com/showthread.php?t=1766475
Sent from my Nexus 5 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:59 AM ----------
Also, here's mostly all the roms stock & custom here: http://forum.xda-developers.com/goo...dex-google-nexus-5-roms-kernels-mods-t2475401
Did you say you can still get into recovery? Because there's an unroot rom thats flashable somewhere... Itd take you to stock everything.....
Sent from my Nexus 5 using Tapatalk
I second that recommendation. With a caveat. Wugfresh's Nexus Root Toolkit is a superb piece of programming which should enable you to set up your PC with all the necessary drivers and also let you specify the ROM you want to install, download it for you, and install it. You should obviously take the latest MMB29V.
But...
I see that you've done a lot of reading, and I understand that Android is initlally hard to grasp, but please don't (a) think you'll never understand it and (b) think that NRT is the answer to all your problems - it isn't. There are lots of reports of people saying "NRT has broken my phone" either because the've used it incorrectly or because they've used it before Wug has had a chance to update it to cater for all the latest tweaks that Google have introduced (particularly on Marshmallow root). If you're careful, set up your drivers properly, and install the correct version for your phone (Hammerhead MMB29V), NRT should give you back a working phone. But after that, read more, and investigate manual update methods, which are particularly useful for installing the monthly security updates without losing your data or waiting for the OTA (over-the-air) rollout from Google.
In fastboot, but can't flash operating system
dahawthorne said:
I second that recommendation. With a caveat. Wugfresh's Nexus Root Toolkit is a superb piece of programming which should enable you to set up your PC with all the necessary drivers and also let you specify the ROM you want to install, download it for you, and install it. You should obviously take the latest MMB29V.
But...
I see that you've done a lot of reading, and I understand that Android is initlally hard to grasp, but please don't (a) think you'll never understand it and (b) think that NRT is the answer to all your problems - it isn't. There are lots of reports of people saying "NRT has broken my phone" either because the've used it incorrectly or because they've used it before Wug has had a chance to update it to cater for all the latest tweaks that Google have introduced (particularly on Marshmallow root). If you're careful, set up your drivers properly, and install the correct version for your phone (Hammerhead MMB29V), NRT should give you back a working phone. But after that, read more, and investigate manual update methods, which are particularly useful for installing the monthly security updates without losing your data or waiting for the OTA (over-the-air) rollout from Google.
Click to expand...
Click to collapse
I'm in the fastboot mode, and I can get into TWRP, but I can't get my PC to recognize the phone. I've followed every rabbit trail I can find, but the phone doesn't show up. The USB ports are fine, and all the USB drivers are up to date. This is what is on my phone screen:
FASTBOOT MODE
PRODUCT NAME - hammerhead
VARIANT - hammerhead D820(E) 32GB
HW VERSION - rev. 11
BOOTLOADER VERSION - HHZ12k
The rest is serial number and so forth. I can get into TWRP, but can't ADB Sideload because the phone is not showing up. Giving me an error 43.
" I've followed every rabbit trail"
Have you followed this one?
"Wugfresh's Nexus Root Toolkit"
kakid56 said:
Totally new to xda forum, and pretty much a noob. Nexus 5 (US model). I was trying to unroot my Nexus 5. I bought it from a friend who had rooted it using TWRP, and it was running CM. Anyway, I managed to completely wipe the operating system ... completely. It will boot using the power/volume down configuration, but when I try to start the phone, it says, "No operating system found." All the threads I have been reading (yes, I have done a lot of reading), assume a couple of things: 1) that the phone can get into Settings/Developer Mode; and, 2) that my PC finds my phone when I plug it in. I have tried the adb and fastboot driver downloads, and wound up with some weird app that was almost impossible to uninstall off my PC. Ten-something or other. I tried doing the flash-all thing, but got a message that there was no such command. Can anyone help me, either directly, or by links to what I need? Once again, I have no operating system on this phone. Thanks.
Click to expand...
Click to collapse
Yup use wugfresh toolkit ... download the factory image https://developers.google.com/android/nexus/images#hammerhead
and boot into bootloader.. then u knw what to do
kakid56 said:
I'm in the fastboot mode, and I can get into TWRP, but I can't get my PC to recognize the phone. I've followed every rabbit trail I can find, but the phone doesn't show up. The USB ports are fine, and all the USB drivers are up to date. This is what is on my phone screen:
FASTBOOT MODE
PRODUCT NAME - hammerhead
VARIANT - hammerhead D820(E) 32GB
HW VERSION - rev. 11
BOOTLOADER VERSION - HHZ12k
The rest is serial number and so forth. I can get into TWRP, but can't ADB Sideload because the phone is not showing up. Giving me an error 43.
Click to expand...
Click to collapse
I don't disagree with the NRT suggestion but am confused. Sorry if I'm missing something obvious. When you are in the bootloader, do you get a cmd response from "fastboot devices" (no quotes in the command)? ADB doesn't work from the bootloader as you probably know, but since you identify as a noob, thought I'd throw it out there. You can flash the system using fastboot commands if your PC recognizes (part of the confusion) the device in fastboot. If not, then you do need to get the drivers set up. If you just need adb/fastboot drivers, I recommend this which I used recently when NRT didn't seem to have the SDK version I needed for my N9 to sideload the latest OTA. Since it installs at the system level, you can place flashable files at the root of C rather than in a specific platform-tools folder. I'm on Windows 10; don't know if that makes any difference for this minimal install. As far as the flash-all. bat not working, that's not uncommon; the files can be extracted and flashed separately.
Sent from my Nexus 9 using Tapatalk
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