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 have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.
AAANNNDDDYYY said:
I have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.
Click to expand...
Click to collapse
I have the SM-G920I and it's rooted.
Rooting the G920I is apparently not as straightforward as others but still possible.
I had to flash TWRP via Odin, then flash the [BETA][2015.04.28] SuperSU v2.49 package via recovery.
Details when I get back from work, or some kind soul decides to help.
There is a stock image thread and a few stock roms floating around. Request / search lower down in that thread
Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
AAANNNDDDYYY said:
Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
Click to expand...
Click to collapse
Here is my experience, a fellow kiwi on Spark (with a 2D branded phone). I too have the 920I running on A0D1 via OTA.
It is unlikely Spark firmwares have locked bootloaders.
So long as you can get to download mode (holding volume down, home and the power button for up to 10 seconds), you can bring your phone back to life if something goes wrong . You will want a copy of Spark's firmware handy before you start, you can get it from here . Just in case.
Use the USB cable that come with your phone and make sure you have the drivers installed.
Any ways, first I flashed TWRP via Odin (through download mode Andy), flash was successful, however booting into recovery hung my phone. Managed to get back to download mode from there and flashed CF-Root for 920I. Boot loop.
Back to download mode and flashed CF-Root for 920F. Success, rooted and booted. Andy, if all you are looking for is root, avoiding the TWRP flash may work and going straight to CF-Root. Others have had issues with this, I'm not sure. I'd try the 920I first and if no good try the 920F. Again, as long as you can get to download mode, you can flash Sparks firmware through Odin to restore it to stock. Good luck and remember, attempting any of this WILL trip KNOX. If your using this as a company phone, you will run into issues. Can't imagine we will see Samsung pay any time soon in NZ.
For those interested in TWRP, after the root was obtained, my recovery was still busted. I flashed the TWRP image via Flashify and now I have also have TWRP. Good times.
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY
AAANNNDDDYYY said:
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY
Click to expand...
Click to collapse
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?
AAANNNDDDYYY said:
Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?
Click to expand...
Click to collapse
Nah, don't bother. The process will retain all your settings and data too.
So just confirm that i can root my g920I with build AOD1 with this meathod?
---------- Post added at 05:45 PM ---------- Previous post was at 05:33 PM ----------
d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So just confirm that i can root my g920I with build AOD1 with this meathod?
d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help
s3ct0r said:
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help
Click to expand...
Click to collapse
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off
Kjc99 said:
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off
Click to expand...
Click to collapse
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck
s3ct0r said:
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck
Click to expand...
Click to collapse
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation
Kjc99 said:
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation
Click to expand...
Click to collapse
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success
My carrier is GCI wireless in Alaska, USA... No way to download there firmware...also is twrp it? No more cwm or philz recovery?
Sorry forgot to add current firmware pic
s3ct0r said:
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success
Click to expand...
Click to collapse
Cool thanks for the info!
Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...
Kjc99 said:
Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...
Click to expand...
Click to collapse
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic
s3ct0r said:
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic
Click to expand...
Click to collapse
Is ktoonsez a stable kernel, I remember using it on my S4 but skipped it last year on my S5 because it had to many tweaks... Can I use it with a stock rom? Alliance?
Hello all,
Have rooted my SM-S906L (5.0.2), which is the SM-G920V for Straight Talk.
TWRP recovery is installed and all is well there.
Trying to install the stock VZW Rom 6.0.1 with the file name: "G920VVRU4CPC2_G920VVZW4CPC2_G920VVRU4CPC2_HOME.tar.md5"
Odin finds the com and device gets added, and the rom takes forever loading into the AP field, then its ready to go.
Hit Start and it fails on sboot.bin...
Could someone possibly point me into the right direction, what I could have or been doing to get this error.
My goal is to get Marshmallow on this S6. My stock firmware is backed up using TWRP.
Thanks!
Update:
..
please let me know if you find any solution
S609l vs g920v
Here here...
Been hoping someone would confirm that the G920V is, or not the same hardware as the S906L.
Would be inclined to experiment more if that was indeed the case.
Regardless, installing TWRP through Odin was straight forward, then rooting with SuperSU, again not an issue.
Quite surprised that there is not a custom rom out there yet?
In the meantime, will keep researching
Still no joy on custom rom for s906l?
Sent from my SM-S906L using Tapatalk
Negative
Nothing yet, still hoping that someone will have figured it out and share. I did have the stock G920V rom boot looping at the Samsung logo but since this is my main phone at the moment, I flashed the stock rom back... I am sure the SM-G920 varient is the SAME unit, just would be a drag to hard brick my only phone.
OTA Update Recived
Last night my SM-S906L did indeed receive an OTA update 275mb, and have harvested to ZIP from the cache/fota folder to my GoogleDrive if anyone needs it.
So before I apply said update, who do I see what OS version it is before it is applied?
My phone is rooted and using TWRP which means once this is applied I am back to loading TWRP and SU.
anyone else get this on theirs, thoughts??
I updated it. Still on 5.0.2. Build number now ends with pk4. When I googled the build number there were s7 nougat roms that ended in that. I was really hoping tracfone was gonna give us a real update.
Edit... just tried flashing the s906l twrp in odin and it wouldn't take. Odin said success but it still boots to stock recovery with the power volume up and home press AND I can't go back to the oe3 firmware or whatever the one that's post around is. Now I'm even screweder
Sent from my SM-S906L using Tapatalk
Anyone ever figure anything out with the pk4 firmware with regards to rooting?
Sent from my SM-S906L 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