Related
I firstly rooted my phone, then unlocked bootloader.
after unlocking of bootloader, my phone doesn't boot again. (blocked on the boot animation)
then I flashed Extened stock kernel v5, installed kitkat, phone couldn't turn on wifi.
I format system and all datas, i tried to install jb, wifi came back, but can't connect. (only save id and password)
Now I flashed back CM11 from son fxp website, all works except wifi...
what should i do for get back wifi? please help me... :crying:
Anyone can help me please...
:crying:
hebarakisun said:
I firstly rooted my phone, then unlocked bootloader.
after unlocking of bootloader, my phone doesn't boot again. (blocked on the boot animation)
then I flashed Extened stock kernel v5, installed kitkat, phone couldn't turn on wifi.
I format system and all datas, i tried to install jb, wifi came back, but can't connect. (only save id and password)
Now I flashed back CM11 from son fxp website, all works except wifi...
what should i do for get back wifi? please help me... :crying:
Click to expand...
Click to collapse
hebarakisun said:
Anyone can help me please...
:crying:
Click to expand...
Click to collapse
I suppose you should do the following. Considering you have unlocked your bootloader via Sony/flashtool. (Sony preferable)
Flash latest stock using Flashtool. 15.3.A.1.17
I found this Download here
The wifi should work after that.
Then you should download any custom ROM. Extract the zip and find boot.img
Flash boot.img via flashtool again. Then flash custom Rom Zip (without extraction) via recovery!
Good Luck
Hnk1 said:
I suppose you should do the following. Considering you have unlocked your bootloader via Sony/flashtool. (Sony preferable)
Flash latest stock using Flashtool. 15.3.A.1.17
I found this Download here
The wifi should work after that.
Then you should download any custom ROM. Extract the zip and find boot.img
Flash boot.img via flashtool again. Then flash custom Rom Zip (without extraction) via recovery!
Good Luck
Click to expand...
Click to collapse
Thank you so much for your reponse..
I see that I must get back stock rom on my phone.
on the download page, there was 2 links, FTF file, part1 and part2,
please can you explain me how to flash it via flashtool?
My phone is unlocked bootloader.
hebarakisun said:
Thank you so much for your reponse..
I see that I must get back stock rom on my phone.
on the download page, there was 2 links, FTF file, part1 and part2,
please can you explain me how to flash it via flashtool?
My phone is unlocked bootloader.
Click to expand...
Click to collapse
I am glad I could be of any help!
Well, you can use any 15.3.A.1.17 ftf file depending on the region. Usually you do not have any problems apart from supported languages on your phone if you flash some other FTF file apart from your region.
Basically, you will need to download both the files and then you will need to extract them both to find one FTF file. from the link i shared. However, you can flash any FTF file with latest version x.x.17. Make sure you flash FTF made for your own device or you may permanently brick your phone for good. The link I am sharing below is for Xperia L
Here is a place where all the FTF files are compiled together by @Joel16
FIND IT HERE
The guide to flash an FTF file is as follows :
Look here
Remember the guide i sent you is for another device but as long as you flash Xperia L (taoshan) FTF file, it would be fine. Also, you would need to flash everything including kernel.
Good Luck and tell me if you need anything more at all!
Hnk1 said:
I suppose you should do the following. Considering you have unlocked your bootloader via Sony/flashtool. (Sony preferable)
Flash latest stock using Flashtool. 15.3.A.1.17
I found this Download here
The wifi should work after that.
Then you should download any custom ROM. Extract the zip and find boot.img
Flash boot.img via flashtool again. Then flash custom Rom Zip (without extraction) via recovery!
Good Luck
Click to expand...
Click to collapse
I see that you helped the OP get through Wifi problem , but I am also having same problems , maybe more.
I clean installed many different ROMs , including Flashing the 15.3.A.1.17 Stock ROM.
I tried even different KK kernels and JB kernels(for Stock ROM) , but no luck.
Plus I have also tried flashing a kernel through Flashtool and reflashing it from recovery , but my Wifi doesn't work and after a hell lot of reboot cycles , I sometimes manage to get it on , which eventually turns off after crashing the phone after some indefinite time.
Please help.
coolhz said:
I see that you helped the OP get through Wifi problem , but I am also having same problems , maybe more.
I clean installed many different ROMs , including Flashing the 15.3.A.1.17 Stock ROM.
I tried even different KK kernels and JB kernels(for Stock ROM) , but no luck.
Plus I have also tried flashing a kernel through Flashtool and reflashing it from recovery , but my Wifi doesn't work and after a hell lot of reboot cycles , I sometimes manage to get it on , which eventually turns off after crashing the phone after some indefinite time.
Please help.
Click to expand...
Click to collapse
First of all, how did you unlock your bootloader?
Secondly, when you are flashing an FTF, have you flashed any FTF for a different variant ?
Like if you have c2105 and you flashed c2104 ?
What about your WiFi bug, tell me details about how it started and what kind of error do you get. The more the details, the more you are helping yourself out .
Lastly, is your device in warranty and can you claim it for an exchange if you relock your bootloader?
Hnk1 said:
First of all, how did you unlock your bootloader?
Secondly, when you are flashing an FTF, have you flashed any FTF for a different variant ?
Like if you have c2105 and you flashed c2104 ?
What about your WiFi bug, tell me details about how it started and what kind of error do you get. The more the details, the more you are helping yourself out .
Lastly, is your device in warranty and can you claim it for an exchange if you relock your bootloader?
Click to expand...
Click to collapse
Bootloader was unlocked through Flashtool from Androxyde.
Wifi problem started when I was using something like FXP 325 , that would be a couple of months ago , but then it was minor , just a reboot would do.
But now I have tried many ROMs(of course clean installed) , kernels(with essentials wiped) , also stock ROMs (.26 ,.12 ,.14 ,.17) all show wifi problems.
By that I know that its a user specific issue. My warranty is over , but I will have no problem paying a bit with relocked bootloader if repairs are needed.
But if there's a way I can fix it at home , please tell. And yeah , I always flash C2104 files as mine is C2104.
coolhz said:
Bootloader was unlocked through Flashtool from Androxyde.
Wifi problem started when I was using something like FXP 325 , that would be a couple of months ago , but then it was minor , just a reboot would do.
But now I have tried many ROMs(of course clean installed) , kernels(with essentials wiped) , also stock ROMs (.26 ,.12 ,.14 ,.17) all show wifi problems.
By that I know that its a user specific issue. My warranty is over , but I will have no problem paying a bit with relocked bootloader if repairs are needed.
But if there's a way I can fix it at home , please tell. And yeah , I always flash C2104 files as mine is C2104.
Click to expand...
Click to collapse
I think you should boot into recovery and do a full wipe including internal/ dalvik/everything including SD card. Don't just factory reset but do a complete wipe. (Twrp has that option. In other recoveries usually you have to do it individually.) So go in recovery and wipe everything you can see that could be wiped.
If that doesn't work,
I suggest you relock your bootlader and see if that helps.
Also try to relock bootloader and unlock it via Sony official way. See that works for you or not.
Seems like a software issue most probably because I'm afraid you didn't backup TA while unlocking bootloader and sometimes the keys are lost and it causes some problems like WiFi. Also, the reason is more likely because of the fact that you didn't do it officially. it could be hardware as well but that's very rare. I would suggest that only give it to someone who knows hardware quite well.
Update me what happens!
Hnk1 said:
I think you should boot into recovery and do a full wipe including internal/ dalvik/everything including SD card. Don't just factory reset but do a complete wipe. (Twrp has that option. In other recoveries usually you have to do it individually.) So go in recovery and wipe everything you can see that could be wiped.
If that doesn't work,
I suggest you relock your bootlader and see if that helps.
Also try to relock bootloader and unlock it via Sony official way. See that works for you or not.
Seems like a software issue most probably because I'm afraid you didn't backup TA while unlocking bootloader and sometimes the keys are lost and it causes some problems like WiFi. Also, the reason is more likely because of the fact that you didn't do it officially. it could be hardware as well but that's very rare. I would suggest that only give it to someone who knows hardware quite well.
Update me what happens!
Click to expand...
Click to collapse
nothing worked , issue still persists , also I would like to tell that Bluetooth also doesn't work along with Wifi.
I cleaned everthing , went back to stock , locked bootloader also. but no luck.
coolhz said:
nothing worked , issue still persists , also I would like to tell that Bluetooth also doesn't work along with Wifi.
I cleaned everthing , went back to stock , locked bootloader also. but no luck.
Click to expand...
Click to collapse
Well, I would say that this happened due to unlocking your bootloader without a TA backup. I am afraid there isnot much you can do as every device has a specific TA code and I am not sure if someone would be interested to share TA backup with you. Even if they do, I am not sure if it would be helpful.
I would share you with all the options you have got :
Go to question/answer and ask for TA backup from someone, this wouldnot work mostly and I would tell you to do everything with caution and on your own risk but that all that could help you out for now at home really. Try someone else TA and see if it is accepted and the WIFI starts to work again. (But use it as a last resort)
If I may add, if you can get a Jtag guy, he might be able to fix your device for a cost but I am not sure of that either.
Another option for you would be asking an expert to repair your phone and telling him all about TA/ unlocking bootloader. If he understands what you are talking about, it just means he knows what you want him to do. If he doesnot, it probably is a bad idea to pay him. You can add it could be a hardware issue as well just in case. However, some times those people use different sort of cables tools to flash FTF so maybe that could be helpful. You can say, you would only pay if WIFI and bluetooth starts to work again! (Second best option ??? )
I honestly do not know how to solve issues related to TA I also suggest write in Xperia Z1 / Z / Z2 forums about your problem as I remember that many of them had many issues due to unlocking bootloader. Sometimes unrooting solves the problem as well. I think that forum users be able to help you much better! Make sure you add all the details about how it happened, what you did and which device are you using and how everything you tried so far hasnot worked. Make sure you mention all tips you got and those that didnot work for you!
Good Luck!
Hnk1 said:
Well, I would say that this happened due to unlocking your bootloader without a TA backup. I am afraid there isnot much you can do as every device has a specific TA code and I am not sure if someone would be interested to share TA backup with you. Even if they do, I am not sure if it would be helpful.
I would share you with all the options you have got :
Go to question/answer and ask for TA backup from someone, this wouldnot work mostly and I would tell you to do everything with caution and on your own risk but that all that could help you out for now at home really. Try someone else TA and see if it is accepted and the WIFI starts to work again. (But use it as a last resort)
If I may add, if you can get a Jtag guy, he might be able to fix your device for a cost but I am not sure of that either.
Another option for you would be asking an expert to repair your phone and telling him all about TA/ unlocking bootloader. If he understands what you are talking about, it just means he knows what you want him to do. If he doesnot, it probably is a bad idea to pay him. You can add it could be a hardware issue as well just in case. However, some times those people use different sort of cables tools to flash FTF so maybe that could be helpful. You can say, you would only pay if WIFI and bluetooth starts to work again! (Second best option ??? )
I honestly do not know how to solve issues related to TA I also suggest write in Xperia Z1 / Z / Z2 forums about your problem as I remember that many of them had many issues due to unlocking bootloader. Sometimes unrooting solves the problem as well. I think that forum users be able to help you much better! Make sure you add all the details about how it happened, what you did and which device are you using and how everything you tried so far hasnot worked. Make sure you mention all tips you got and those that didnot work for you!
Good Luck!
Click to expand...
Click to collapse
bro I think I got it , I absent mindedly relocked bootloader through Flashtool , as I was going back to stock after months . I do have my TA backup.And I will restore it and see what happens. Thanks you just made me remeber that
I have an unlocked xperia z3 d6603 I bought brand new in january I believe. I just today rooted and installed recovery but am stuck on the 23.0A.2.93 tft rom which it shippped with. It would have normally been running unrooted the latest rom from sony which was just pushed out a couple months ago. I'm in california and need a rooted d6603 generic global rom, or even unrooted, and I can't seem to find the down link here. In xpreifirm 3.6a latest, I keep getting a java error so can't use that and I've already uninstalled and installed the latest 64bit java8 update 40. I was going to just flash it with the moonwalker rom but it days I need to be on a different tft altogether. Any help here would be appreciated. I have installed a firewall, changed dns servers, and uninstalled a few things using rom toolbox. Hoping to just update it to the recent tft or even better, a working custom rom which won't mess up the default phone capabilities. I'm on kitkat 4.4.4, at&t lte, rom 23.0.A.2.93
Again I need a rooted global generic 577 tft for a z3, a nonrooted one, or even better, a custom one I can just flash to it so I can get back to my life.
since you have a working recovery just flash this one 23-0-1-5-77-deodexed-zipaligned it's the latest KK
ps: I'm on AT&T in CA as well and running that firmware just fine for a while now, it's generic global so no worries...
awesome. THANKS. Gonna try it now. Been at it all day from like 10am to about 5 when I had to break
How do you flash a zip file
tweker said:
awesome. THANKS. Gonna try it now. Been at it all day from like 10am to about 5 when I had to break
Click to expand...
Click to collapse
I rebooted with TWRP in recovery mode, reset device (Wipe Data, Cache and Dalvik Cache), saw no way of flashing from recovery mode. Shut phone off. Plugged in in flash mode with the zip file in the firmwares folder and it was not recognized by flash tool. Where are the directions for flashing a zip?
Choose the second option in recovery
Install custom zip
I used NDR to reboot into recovery. The zip was on both internal and external at root. First time I selected the one from internal and it gave no errors. Wiped cache and rebooted and still on stock 93. Did the exact same thing again choosing zip on sd card and it still says 93. Third time I did it from sd card but no cache wipe. Still on23.0.A.2.93. WTF???
Where can I find a working ftf. NDR doesn't work for ****. BTW, phone is setup in dev mode with mock, airplane mode etc with supersu free working. I think
BTW, why in the hell does the thread with all the roms not have any current ones???? rooted or not
What for are you trying to flash? Please provide a link.
What does the recovery log say? It really helps if you tell us this.
FTF files are geberally not uploaded anymore as it is very easy to download any you want from the sony servers and create your own FTF using flashtool and Xperia firm.
Ps, it may be nice to watch your language. The issue is not NDR, it works fine.
I'm using D6603_23.0.1.A.5.77_deodex.zip from here: http://forum.xda-developers.com/z3/development/deodex-23-0-1-5-77-deodexed-zipaligned-t3015178 on top of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf which was rooted and dual recovered. I have flashed the above 5.77 zip file like 5 times from recovery mode and still on 93. This last time I noticed I had no file mgr. Installed es, mounted system rw like it says to do after root, reflashed the 77 deodexed zip, wiped dalvik and cache, reupdated supersu zip in recovery, rebooted, and stil on93. What am I doing wrong? Is there not a dern ftf file I can use instead? OR, should and could I just wait for another official update?
tweker said:
I'm using D6603_23.0.1.A.5.77_deodex.zip from here: http://forum.xda-developers.com/z3/development/deodex-23-0-1-5-77-deodexed-zipaligned-t3015178 on top of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf which was rooted and dual recovered. I have flashed the above 5.77 zip file like 5 times from recovery mode and still on 93. This last time I noticed I had no file mgr. Installed es, mounted system rw like it says to do after root, reflashed the 77 deodexed zip, wiped dalvik and cache, reupdated supersu zip in recovery, rebooted, and stil on93. What am I doing wrong? Is there not a dern ftf file I can use instead? OR, should and could I just wait for another official update?
Click to expand...
Click to collapse
That is not a ROM file, it does not contain a ROM. It just deodex's your system files if you are on that firmware.
And, No, there is not a FTF you can flash that is rooted. FTF files have to be completely stock as we cannot sign them with Sony's keys as we do not know them. The only way to flash something rooted is via recovery
Post#2 told me I could flash the zip over and it would work. No wonder it doesn't work because it doesn't do anything. I don't want to unlock boot because I may fail official updates. I really just want to update to a working global generic 77 rooted dual recovered system. So basically even if I had the official 77, unrooted, I still couldn't use (nor root) it right? Thanks for the help. I at least know to go another route.
tweker said:
Post#2 told me I could flash the zip over and it would work. No wonder it doesn't work because it doesn't do anything. I don't want to unlock boot because I may fail official updates. I really just want to update to a working global generic 77 rooted dual recovered system. So basically even if I had the official 77, unrooted, I still couldn't use (nor root) it right? Thanks for the help. I at least know to go another route.
Click to expand...
Click to collapse
Post #2 is wrong. Also the thread stated in the first line that a requirement for that to work is that you are already on .77 firmware.
There is no need to unlock your boot.
Just flash a .77 prerooted ROM.
If you cannot find one then make one yourself. Follow the guide in the thread called PRFCreator (Just google it)
Once you have the files downloaded it takes 7 minutes and it is all automated for you
Thank You Very Much. At present I have access to two pc's. One is my roomies (win8.1) and mine (win7). My roomies has some sort of java issue and xperifirm fails right when you click the file you want. Tried fixing java didn't work. Mine is wireless, dns disabled, mac changed, hosts file, and tiny wall fw. Experifrm says no net access even though it works fine. Tried a cable and for the life of me got the same error (couldn't quite reconfigure it to work correctly-pita). If I ever get the file I will do the prfcreator magic, and I'm assuming, flash it through ndr tools in recovery mode. In the mean, I might request an xda user in another thread to grab one for me and post it. Should help lots of people not just me. Again, thank you for your help, saved a lot of hair pulling.
tweker said:
Thank You Very Much. At present I have access to two pc's. One is my roomies (win8.1) and mine (win7). My roomies has some sort of java issue and xperifirm fails right when you click the file you want. Tried fixing java didn't work. Mine is wireless, dns disabled, mac changed, hosts file, and tiny wall fw. Experifrm says no net access even though it works fine. Tried a cable and for the life of me got the same error (couldn't quite reconfigure it to work correctly-pita). If I ever get the file I will do the prfcreator magic, and I'm assuming, flash it through ndr tools in recovery mode. In the mean, I might request an xda user in another thread to grab one for me and post it. Should help lots of people not just me. Again, thank you for your help, saved a lot of hair pulling.
Click to expand...
Click to collapse
Sorry about the confusion, indeed the first link that I provided was just a patch to deodex your room (I always use deodex so I can mod my rom)....anyway you can use this one it's a generic prerooted .77 from the z3 android development section in this forum, then you can patch it with the other one if you have the need to...just follow the instructions in this link and you should be on your way
Again sorry about that first post, I rooted my phone the minute root was available on locked bootloader so it's been some time now
I have been to that link. The only one I can see that says generic global is the 23.0.A.2.93 one. The others say, Generic_DE, Generic_NCB, or Generic_AU. Which looks to me like Deutch, Generic Nordic?, and Australian? Since I speak english and am nowhere near any of those places, I did not touch them. Which one is safe to use and will there be any post config for my locale and radios?? Plus I have no clue what the purpose is of de-odexing the file system (flashing that zip) does. I still have read write issues with apk's I install when I tell them to use my 128gb sd card. I did recover my setup prior to the zip flash you pointed me to which I still have-thank you.
tweker said:
I have been to that link. The only one I can see that says generic global is the 23.0.A.2.93 one. The others say, Generic_DE, Generic_NCB, or Generic_AU. Which looks to me like Deutch, Generic Nordic?, and Australian? Since I speak english and am nowhere near any of those places, I did not touch them. Which one is safe to use and will there be any post config for my locale and radios?? Plus I have no clue what the purpose is of de-odexing the file system (flashing that zip) does. I still have read write issues with apk's I install when I tell them to use my 128gb sd card. I did recover my setup prior to the zip flash you pointed me to which I still have-thank you.
Click to expand...
Click to collapse
1) its called a FTF file not a TFT file. It's a FlashTool File.
2) your sd write card issues are a feature of KK, and nothing to do with any error or bug to do with your phone. Just Google KK write to sd card to read more about it and how to circumnavigate this issue that was deliberately introduced by Google.
3) i have read some of the advice you have banded about in several of the thread here. Some of it is just plain wrong. Although not dangerous to anyones device it may be worth reading and learning a bit more first.
4) please stick to asking questions in just one thread, there is no need to ask in several thread because the first time you did not get an immediate answer
5) you can safely flash a FTF from any region as long as it is for the same model you have. Especially as you are only going to be on that version for a few minutes whilst you root them immediately upgrade.
Ok, great. I'll grab the de one. As for not trying to help; I put down what worked for me. If I don't know everything I can still give input with the little I know. That's how people learn, myself incl. I just got my pc running not two weeks ago so a little overwhelmed with having just rooted as well. Thanks very much for all your help.
tweker said:
Ok, great. I'll grab the de one. As for not trying to help; I put down what worked for me. If I don't know everything I can still give input with the little I know. That's how people learn, myself incl. I just got my pc running not two weeks ago so a little overwhelmed with having just rooted as well. Thanks very much for all your help.
Click to expand...
Click to collapse
No worries. I did not mean to imply that you should not help, only that you should be sure that what you are saying is in fact correct information.
We do all have to learn, but its hard to learn when incorrect information is posted and stated as "fact"
Greg
From install to booted took 4 min. Just had to update supersu and remove a few things. This is awesome! NDR Utils is worth paying for. Now I can finally encrypt my phone. TYSM
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
I've run into a huge problem that I hope someone here can help me with. I currently have a USA model XZ that is on Nougat 7.0. Completely stock, bootloader locked and everything. I've been reading and researching all the necessary steps to flash a custom rom on the XZ and am prepared. Have all the files I need, am following the steps in order and making sure I don't skip or overlook anything, but my problem is at the first few steps.
I am trying to backup my TA partition, but the problem is when I flash a 6.0 FTF. I flashed a European FTF, flashtool said successful, but when my phone booted, I reached a screen that said "To start Android, enter Password". I did not have a password on my phone to unlock, a pin, nor a pattern. I had it at swipe to unlock and made sure of it before I flashed the .FTF file. I googled, tried reading some threads here, but no luck. I entered my Google account password that was associated with my phone, nothing. It gave me 20 tries and if I got it wrong 20 times, it would factory reset I believe. Out of fear an panic, I flashed the newest USA FTF from Xperifirm and everything worked like normal. All my files, apps, and settings were there as if nothing ever happened.
Has anyone ever seen that screen? I wished I would've taken a picture, but I was completely afraid that I softbricked or did something wrong with my phone. I would love to try out a custom rom, but would prefer that I still have all my DRM keys intact. Could anyone help out? Thanks in advanced for reading and helping!
desperately trying to un brick my note 5. I've been trying for weeks now to recover my phone after a rooting mishap had caused loss of imei and baseband. in the process of attempting to repair that issue I have managed to completely soft brick the damn thing. I have been to the deepest corners of google in search of this specific 4 file repair download and can not find anything that is free. I've even signed up for accounts on gsm flash and the like only to be disappointed that signing up wasn't enough to get the files I need... if anyone has a link or the files themselves I would be very thankful for there help. to be clear I can not flash standard stock rom through Odin. the process completes and the phone boots but than erases at 32 percent and will only boot to recovery with dm verity error or download mode. I've tried a few different official stock roms. I've tried flashing the one file home.tar as well as un packing and flashing boot, system, modem, cache neither of which have worked. I can't find a hidden image file to remove before flashing so unless I'm missing something im out of ideas.. the repair. firmware seems to be my last hope... also to hell out anyone trying to assist. I flashed a. efs file when trying to restore imei and that in turn re enabled frp lock.. so I believe both frp lock and oem lock are enabled. so any combination file or modified at all is out of the question... I believe it's repair or nothing. there are a few free 4 file repair downloads out there but they aren't the same number im not sure if there are any compatible enough that I could flash one of them and they work? so if any one knows of other models compatible. with the SM-N920TUVU4EQJ3 let me know so I can try to get this mess sorted out. I apologize if this has been asked somewhere els or if I'm in the wrong forum. but this seemed the most suited for my case. thank you to anyone who may be able to help
anybody?
is anyone able to help me out?
thatspideyguy said:
desperately trying to un brick my note 5. I've been trying for weeks now to recover my phone after a rooting mishap had caused loss of imei and baseband. in the process of attempting to repair that issue I have managed to completely soft brick the damn thing. I have been to the deepest corners of google in search of this specific 4 file repair download and can not find anything that is free. I've even signed up for accounts on gsm flash and the like only to be disappointed that signing up wasn't enough to get the files I need... if anyone has a link or the files themselves I would be very thankful for there help. to be clear I can not flash standard stock rom through Odin. the process completes and the phone boots but than erases at 32 percent and will only boot to recovery with dm verity error or download mode. I've tried a few different official stock roms. I've tried flashing the one file home.tar as well as un packing and flashing boot, system, modem, cache neither of which have worked. I can't find a hidden image file to remove before flashing so unless I'm missing something im out of ideas.. the repair. firmware seems to be my last hope... also to hell out anyone trying to assist. I flashed a. efs file when trying to restore imei and that in turn re enabled frp lock.. so I believe both frp lock and oem lock are enabled. so any combination file or modified at all is out of the question... I believe it's repair or nothing. there are a few free 4 file repair downloads out there but they aren't the same number im not sure if there are any compatible enough that I could flash one of them and they work? so if any one knows of other models compatible. with the SM-N920TUVU4EQJ3 let me know so I can try to get this mess sorted out. I apologize if this has been asked somewhere els or if I'm in the wrong forum. but this seemed the most suited for my case. thank you to anyone who may be able to help
Click to expand...
Click to collapse
thatspideyguy said:
is anyone able to help me out?
Click to expand...
Click to collapse
Hi I had the same issue with my note 5 SM-N920T I managed to fix it by downloading a pre rooted with SU rom from xda I also had the twrp custom bootloader installed first for some reason my pc still picked up my phone and I was still able to upload the rom to the twrp location on the device. having done that I was the able to copy the zip file over to my device and flash it.
When I had the rom installed I was then able to download the original android rom (android 5 in my case) from sam mobile they also had the most up-to-date android 7 rom as well for the device then it was just a case of using android repair to un root the bootloader and install the original android bootloader this was also on sam mobile.
Then make sure the phone has a full battery as flash the stock firmware as you would normally with odin and have the latest Samsung drivers installed on yore system or it will fail.
After the flash has taken place the first boot will take some time my note 5 took around 45 min's and then when fully back up and running I had to spend a good 2 hours reinstalling and updating all my software and OTA updates.