Related
i am extremely new to the rom/flashing/rooting scene. i recently used a "back door" rooting process, which worked great and i did all the recomended actions and apps: supersu titanium backup, root browser, etc. then i wanted to change my boot animation->samsung device-> flash a zip file to allow bootanimation.zip->samsung requires signature verification from stock recovery mode->cwm recovery(which flashes itself to the phone... curious why a custom recovery...or any recovery for that matter is even required if it isnt necessary...) -> recovery menu no longer accesible. i cant flash anything to my phone i tried changing the recovery to twrp but no dice. its giving me this dialog along with caution sign:"system software not authorized by verizon wireless has been found on your phone...etc" the phone is a samsung galaxy legend on verizon prepaid plan it is the jasper version of the samsung galaxy stellar. now for the question... What do i do so that i can flash files to my device?
i dont know much about unlocking the bootloader except that doing so with the wrong program will brick your phone and since im doing this recreationally on my primary phone i dont want to buy a new one. how can i regain access to my recovery menu/ unlock my bootloader?
its not a popular phone so i doubt anyone is going to be able to offer a one touch application to unlock the bootloader but any information would be helpful.if youre still reading this i thank you for any advice and i apologize if i : posted in the wrong section, offended anyone, or came off as a cheap experience-less n00b
EDIT: my phone is running 4.1.2 jellybean, baseband:i200ppvramh1, kernel: 3.0.31, build: jzo54k.i200ppvramh1, dont know if that will help any and before anyone criticizes me remember i am completely new to this forum posting thing but i guarentee i have scrounged this site the world over trying to get help but there just seems to be noone working on this problem the same as me...
So...
I'm coming from a Fascinate running CM10. Pretty easy install, etc. etc.
Finally got some info from the S3 I'm restoring, and trolling around trying to find info (or finding too much).
This is what I have:
Android Version - 4.3
Baseband version - I535VRUCML1
Kernel Version - 3.0.31
Build - JSSI5J.I535VRUCML1
So I'm basically looking for the RTFM replies.
How do I find if the the bootloader is locked (I have been able to avoid installing ADB on my PC, but would have no troubles running basic linux command line stuff)?
I think I can install either TWRP or CWM, because it doesn't actually touch the bootloader, correct?
Can I install any ROM (I have read threads that I can install any "4.3 compatible ROM")? Is that all I need to look for?
What is the purpose of "safestrap" ? is it needed, and why (didn't need this on the Fascinate).
I am familiar with ODIN, and used CWM to install CM10, but with all the warning about "YOU WILL BRICK YOUR PHONE" have got me to a point of such confusion, I feel like a deer stuck in the headlights (or even worse, a Q-Beam).
Thanks in advance for any RTFM replies.
Eric
ejaf said:
So...
I'm coming from a Fascinate running CM10. Pretty easy install, etc. etc.
Finally got some info from the S3 I'm restoring, and trolling around trying to find info (or finding too much).
This is what I have:
Android Version - 4.3
Baseband version - I535VRUCML1
Kernel Version - 3.0.31
Build - JSSI5J.I535VRUCML1
So I'm basically looking for the RTFM replies.
How do I find if the the bootloader is locked (I have been able to avoid installing ADB on my PC, but would have no troubles running basic linux command line stuff)?
I think I can install either TWRP or CWM, because it doesn't actually touch the bootloader, correct?
Can I install any ROM (I have read threads that I can install any "4.3 compatible ROM")? Is that all I need to look for?
What is the purpose of "safestrap" ? is it needed, and why (didn't need this on the Fascinate).
I am familiar with ODIN, and used CWM to install CM10, but with all the warning about "YOU WILL BRICK YOUR PHONE" have got me to a point of such confusion, I feel like a deer stuck in the headlights (or even worse, a Q-Beam).
Thanks in advance for any RTFM replies.
Eric
Click to expand...
Click to collapse
You ain't in Kansas anymore.
your bootloader is locked. your stuck with safestrap and roms compatible with a locked bootloader
ejaf said:
So...
I'm coming from a Fascinate running CM10. Pretty easy install, etc. etc.
Finally got some info from the S3 I'm restoring, and trolling around trying to find info (or finding too much).
This is what I have:
Android Version - 4.3
Baseband version - I535VRUCML1
Kernel Version - 3.0.31
Build - JSSI5J.I535VRUCML1
So I'm basically looking for the RTFM replies.
How do I find if the the bootloader is locked (I have been able to avoid installing ADB on my PC, but would have no troubles running basic linux command line stuff)?
I think I can install either TWRP or CWM, because it doesn't actually touch the bootloader, correct?
Can I install any ROM (I have read threads that I can install any "4.3 compatible ROM")? Is that all I need to look for?
What is the purpose of "safestrap" ? is it needed, and why (didn't need this on the Fascinate).
I am familiar with ODIN, and used CWM to install CM10, but with all the warning about "YOU WILL BRICK YOUR PHONE" have got me to a point of such confusion, I feel like a deer stuck in the headlights (or even worse, a Q-Beam).
Thanks in advance for any RTFM replies.
Eric
Click to expand...
Click to collapse
To add to the above, no you cannot install TWRP or CWM. You didn't need safestrap on the Fascinate because the bootloader was unlocked on it. You need to read this thread and the links that are contained in the OP of the thread to get your answers:
http://forum.xda-developers.com/showthread.php?t=2639337
Thanks...I would have expected that sticky thread to be in this forum...hadn't even started searching the dev forums yet.
I'll read up on safestrap...sounds as if it allows other ROMS to run on a locked bootloader.
No, I am definitely not in Kansas anymore. Can I click my heels together three times, and have CM11 running :silly:
Eric
I think I screwed up big time.
I fist got my GS3 Verizon and rooted with Towelroot. Then I tried installing TWRP. I was unaware of the locked bootloader, and found out about SafeStrap. I never actually uninstalled TWRP. From there, I installed SafeStrap, then I tried installing CM 12.1 and I messed up. My phone won't boot up in any mode other than download mode. When I try to boot in to recovery I will get the "System Software not authorized by Verizon Wireless has been found on your phone." Message. I need to wipe and install stock ROM. Someone please help! (And if possible, maybe someone can walk me through having CM 12.1 on here? I really want it on, but I need a walkthrough)
Thanks guys!
P.S. I am running Android 4.4.2.
TacoTank said:
I think I screwed up big time.
I fist got my GS3 Verizon and rooted with Towelroot. Then I tried installing TWRP. I was unaware of the locked bootloader, and found out about SafeStrap. I never actually uninstalled TWRP. From there, I installed SafeStrap, then I tried installing CM 12.1 and I messed up. My phone won't boot up in any mode other than download mode. When I try to boot in to recovery I will get the "System Software not authorized by Verizon Wireless has been found on your phone." Message. I need to wipe and install stock ROM. Someone please help! (And if possible, maybe someone can walk me through having CM 12.1 on here? I really want it on, but I need a walkthrough)
Thanks guys!
P.S. I am running Android 4.4.2.
Click to expand...
Click to collapse
Your best bet may be using Odin to flash the stock 4.4.2 ROM.
I bought my i535 (Verizon SGS3/d2vzw) used as a device to develop modding skills. It came with the 4.4.2 rom already installed. I have learned from reading in this forum that options for you and I are very limited. Once your device is restored you can use SafeStrap but not TWRP, CWM, or Philz Recovery. There are only three roms available to us: Stock, SuperLiteRom, and PaulPizz ROM.
@ShapesBlue may have better advice, he actually used this device as a phone and has much more experience with what can be done with the i535 on the 4.4.2 bootloader (NE1)
First of all, thank you for ALL your help! I REALLY appreciate it! You are a lifesaver. Now, my question is, can I flash android 4.2 so the bootloader isn't locked? I know I am being a little picky, but this is the ONLY reason I bought it. But I was thinking, put my phone in download mode, flash 4.2 > root > install TWRP > wipe > Flash CM12.1 > and voila! Would that work, and if so, could you help?
TacoTank said:
First of all, thank you for ALL your help! I REALLY appreciate it! You are a lifesaver. Now, my question is, can I flash android 4.2 so the bootloader isn't locked? I know I am being a little picky, but this is the ONLY reason I bought it. But I was thinking, put my phone in download mode, flash 4.2 > root > install TWRP > wipe > Flash CM12.1 > and voila! Would that work, and if so, could you help?
Click to expand...
Click to collapse
Everything I have read indicates that we are stuck at 4.4.2 and can not downgrade. I didn't read the forums before purchasing mine and have not seen anything saying anyone has safely downgraded, or used any rom other than the three I mentioned.
I guess we could wish for Verizon to release a security update because of stagefright issues. I can dream, but I'm not holding my breath.
Okay, guys, I am starting to lose it.
I am having 0 luck fixing this damn thing. I have tried flshing every android version that exists for this phone and it won't work at all. KIES won't recognize so I used ODIN. ODIN never feels like working so IDK what to do. I used Safestrap to try and install CM 12.1, but it was stuck in a boot cycle, and since I had to use the Safestrap app to launch recovery, I am screwed. There is no way for me to get into my phone, I only have download mode, I need some help guys. What can I do!?!?! I just want anything that will work at this point. Even if I can't get CM12. I think I want to get android working on it and sell it. Pls help!!!
TacoTank said:
Okay, guys, I am starting to lose it.
I am having 0 luck fixing this damn thing. I have tried flshing every android version that exists for this phone and it won't work at all. KIES won't recognize so I used ODIN. ODIN never feels like working so IDK what to do. I used Safestrap to try and install CM 12.1, but it was stuck in a boot cycle, and since I had to use the Safestrap app to launch recovery, I am screwed. There is no way for me to get into my phone, I only have download mode, I need some help guys. What can I do!?!?! I just want anything that will work at this point. Even if I can't get CM12. I think I want to get android working on it and sell it. Pls help!!!
Click to expand...
Click to collapse
If your device was ever on 4.4.2 you may as well give up on the idea of installing CM 12.1, or any ROM other than the three I mentioned. (If you have found something stating differently please share.)
Some of these threads may be of help:
[GUIDE] Debrick your bricked SCH-I535! [BOOTLOADER/HARDBRICK]
[GUIDE][ML1/NC1/NE1] TW 4.4 and 4.3 Sticky Roll-Up Thread (7-10-14)
[INDEX] TW 4.4 Download List (7-10-14)
That last one is a bit dated but still worthwhile. The second is not quite as dated. The first may be what helps you.
So, I need like, a tutorial or a link on how to fix this. I want to fix my recovery as well if that's possible. Just so I can have stock recovery. If I flash Android 4.4.2 it should fix that though. Plus, a working download link would be MUCH appreciated.
Alright. So, I followed the instructions on this http://forum.xda-developers.com/showthread.php?t=2581166&nocache=1 and had no luck, when I flash on ODIN, it gets the error when flashing the "aboot". That's when it fails. Any suggestions? I tried deleting it, but 7zip won't let me.
TacoTank said:
Alright. So, I followed the instructions on this http://forum.xda-developers.com/showthread.php?t=2581166&nocache=1 and had no luck, when I flash on ODIN, it gets the error when flashing the "aboot". That's when it fails. Any suggestions? I tried deleting it, but 7zip won't let me.
Click to expand...
Click to collapse
Odin gives an error at that point when you are trying to flash an incompatible bootloader. If you used any rom with a bootloader older than 4.4.2 (NE1) it prevents you from flashing to avoid a bricked device.
Which image did you use from the site you linked?
None of the images from the OP of that thread are for flashing with Odin. They are to burn to an external micro sdcard from which you boot the device and then restore your bootloader, and recovery if necessary.
Please detail the exact steps you performed.
Oh, I flashed an image from something else, my bad on that one. Uh, so I tried putting that thing on my SD card with Win32DiskImager, and every time I do it, after multiple writes and phone boot-ups, I had no luck. It always tells me "Firmware upgrade encountered an error. Please use Software Repair Assistant & try again." So, I don't know what to do. Ad I also wanted to thank you for your speedy replies, I know mine are always delayed, I have finals and stuff, it's hectic. But, I need my phone back already so I'll jump back to reply ASAP! Thanks!
TacoTank said:
Oh, I flashed an image from something else, my bad on that one. Uh, so I tried putting that thing on my SD card with Win32DiskImager, and every time I do it, after multiple writes and phone boot-ups, I had no luck. It always tells me "Firmware upgrade encountered an error. Please use Software Repair Assistant & try again." So, I don't know what to do. Ad I also wanted to thank you for your speedy replies, I know mine are always delayed, I have finals and stuff, it's hectic. But, I need my phone back already so I'll jump back to reply ASAP! Thanks!
Click to expand...
Click to collapse
I am not in the least familiar with "Software Repair Assistant." I do know it is a Verizon process. You can give it a try if you wish.
Other than that you are back to the debrick image process. That process can take a number of attempts. You should use either a 16 or 32 GB class 10 card. It sometimes works with a slower card, but best bet is with a class 10. It would be an oddity for something samller than 16 GB to work. Also, you may need to try several cards. A card that works for this in one phone at times does not work in a different SGS3.
Alright, here's what I just did. I needed a new SD Card anyay so I bought a Kingston Digital 16 GB microSDHC Class 10 UHS-1 Memory Card 30MB/s with Adapter (SDC10/16GB) off of Amazon and it should be here by Thursday. And then, I'll tell you how things go. I am praying this works, because, even though I am getting a HTC One M9 (I'd like your thought on that, if you think it's a good phone to run CM 12.1 off of) I need a phone for now.
TacoTank said:
Alright, here's what I just did. I needed a new SD Card anyay so I bought a Kingston Digital 16 GB microSDHC Class 10 UHS-1 Memory Card 30MB/s with Adapter (SDC10/16GB) off of Amazon and it should be here by Thursday. And then, I'll tell you how things go. I am praying this works, because, even though I am getting a HTC One M9 (I'd like your thought on that, if you think it's a good phone to run CM 12.1 off of) I need a phone for now.
Click to expand...
Click to collapse
A quick check at the VZW development thread for the M9 shows they have root and custom recoveries. A quick glance at a number of the custom ROMs their had all of them based on stock, either saying stock or sense.
Another check at CM shoes development open for the himaul HTC One M9. I don't know which carrier that is for, but it is a GSM device instead of cdma. The AT&T M9 is code named hima so I am not convinced it is theirs.
Otherwise, I don't know much about the M9 outside of what I see in the reviews. Being that my daily driver is still my SGS3, I would think I would be satisfied with the M9 performance.
Well, I am screwed. I tried using my 16GB SD and it didn't work. I did everything right, I don't know what to do. I kinda think flashing something via ODIN would work, but I don't know what to flash. Help?
TacoTank said:
Well, I am screwed. I tried using my 16GB SD and it didn't work. I did everything right, I don't know what to do. I kinda think flashing something via ODIN would work, but I don't know what to flash. Help?
Click to expand...
Click to collapse
From what I have read in the debrick threads, you may have to try several cards to find one that works in your phone. Also, it is 16 and 32 Gb class 10/U1 cards that are most likely to work.
So I tried this process with a 64GB Samsung Class 10 SD, and it didn't work. Should I just go with a 32GB or am I going to need a Jtag?
TacoTank said:
So I tried this process with a 64GB Samsung Class 10 SD, and it didn't work. Should I just go with a 32GB or am I going to need a Jtag?
Click to expand...
Click to collapse
I don't recall seeing anyone report attempting to do this with a 64GB card, not to say it wouldn't work, I just haven't seen anyone saying they tried one.
TacoTank said:
So I tried this process with a 64GB Samsung Class 10 SD, and it didn't work. Should I just go with a 32GB or am I going to need a Jtag?
Click to expand...
Click to collapse
dawgdoc said:
I don't recall seeing anyone report attempting to do this with a 64GB card, not to say it wouldn't work, I just haven't seen anyone saying they tried one.
Click to expand...
Click to collapse
You may just need a SanDisk version versus the Samsung one. I have ran across threads with people having success with them. Definitely try a 32gb sd card as dawgdoc suggested
Nexus 6 running SSHD or Cataclysm
http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Sent from my Nexus 5 using Tapatalk
Please what's the confirmed rooting method for Samsung galaxy s3 Verizon i-535 running 4.4.2 I tried rooting with towelroot & kingroot, also flashed cwm recovery from rom manager respectively then rebooted to recovery but got black screen with yellow triangle error. I have a friend at the Samsung store in bestbuy that have reflashed the phone twice & is still willing to restore the phone again but I wanna know the working root method for this device without screwing up recovery?
Hi there,
My phone has android 6.0.1 and i want it downgraded to android lollipop because ive got problems with android 6.0.1.
Im a total noob with all this stuff, so can someone please advise step by step how i can do this? I have the MOTO G 3rd Gen, SKU is "XT1541", Ram is 1GB and ROM 8GB. My current system version is 24.61.55.osprey_reteu.reteu.en.EU reteu. Build number is MPI24. 107-55. This phone will accept any phone network. Can someone please help? thanks in advance!
There are multiple threads discussing downgrading, it can be done if your device has the bootloader unlocked (which wipes data and voids the warranty)... There are some inherent dangers in doing so, some immediate and some long-term dealing with future updates which have the potential to brick the device.
What are the issues you are having, many times it is better to solve those then to downgrade.
acejavelin said:
There are multiple threads discussing downgrading, it can be done if your device has the bootloader unlocked (which wipes data and voids the warranty)... There are some inherent dangers in doing so, some immediate and some long-term dealing with future updates which have the potential to brick the device.
What are the issues you are having, many times it is better to solve those then to downgrade.
Click to expand...
Click to collapse
Some apps wont run well on android 6.0.1 such as facebook etc (personal and buisness use) and my phone generally ran better with the previous android version. The phone does not have a warranty on it anyway so that does not matter. Trust me, it really cudnt be much worse than it is atm, ive factory reset it and its just not up to standard as it was with android 5. I did have android 6.0 which i didnt like and then i got 6.0.1, which was putting ice on the cake, (in a bad way!). I am 1000% sure i want to downgrade my device. Can you help?
Ryanm353 said:
Some apps wont run well on android 6.0.1 such as facebook etc (personal and buisness use) and my phone generally ran better with the previous android version. The phone does not have a warranty on it anyway so that does not matter. Trust me, it really cudnt be much worse than it is atm, ive factory reset it and its just not up to standard as it was with android 5. I did have android 6.0 which i didnt like and then i got 6.0.1, which was putting ice on the cake, (in a bad way!). I am 1000% sure i want to downgrade my device. Can you help?
Click to expand...
Click to collapse
Not much to it... Unlock the bootloader, factory reset, then use the lollipop factory image from the factory images thread, gpt.bin will fail, just continue to flash everything all the way through. Follow the instructions in how to flash factory images, it's all done in fastboot.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Not much to it... Unlock the bootloader, factory reset, then use the lollipop factory image from the factory images thread, gpt.bin will fail, just continue to flash everything all the way through. Follow the instructions in how to flash factory images, it's all done in fastboot.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Thanks. But can you explain all that in more detail step by step? I need clear instructions on how to do all that as ive literally no idea about anything.
Ryanm353 said:
Thanks. But can you explain all that in more detail step by step? I need clear instructions on how to do all that as ive literally no idea about anything.
Click to expand...
Click to collapse
No offense, but this is not something to be taken lightly... there are many steps.
First, backup all your data... it will be lost.
Start by reading the first few posts in this thread... This will give the basics of what is needed to be done, what tools you need, how to do it, and the factory firmware images (you will need the correct one for your device, all the ones available are in this thread.
Next, read the first two posts in this thread... this is the instructions in detail of exactly how to flash a firmware image. Pay attention to the warnings and follow the linked threads with more information and make sure you understand all of it.
Once you have read and understand this part, you need to get fastboot working... this tool is essential to making all this work. Both of the threads I mentioned above have links to the drivers and Minimal ADB & Fastboot you will need. Install them and make sure they are working.
Now you can unlock the bootloader, this will wipe all data on your device. The instructions and process are done directly with Moto here.
Once you have unlocked the bootloader, reboot and start the bootloader and follow the instructions in the threads above, noting that the part where enter the command "fastboot flash partition gpt.bin" will likely fail because you are downgrading, but no other pieces should fail, if they do enter them again (radios are known to need to be done 2-3 times sometimes before taking), and continue all the way to the end. Pay attention to the number of sparcechunks in your image, it can will vary and you need to flash all pieces in order for your device, there could be anywhere from 5-9 pieces.
Keep a log of everything, it is much easier to tell what happened if something goes wrong by looking at the terminal log (scroll back of the terminal window) than just guessing.
TBH... I am not endorsing this method, but it generally does work, and although it is difficult to brick the Moto G 2015 it is not impossible. After you are done, you will need to root the device and freeze the updater service so you are not constantly prompted to update, and taking an OTA update can be problematic since your bootloader and/or partition table will not match the rest of the ROM correctly.
Personally I think since you have to unlock the bootloader anyway, you are probably better off just looking for a custom ROM like CM13, Resurrection Remix, or something like that since there are lots of rock solid Marshmallow aftermarket ROMs. Or if you are dead set on Lollipop, using CyanogenMod 12.1 instead of downgrading.
I know there is a downgrade utility out there, and not to take away from the developers work but I would suggest avoiding it.
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