Hello there,
I have had this issue for some time now and hence not used the phone since then.
Now I see that the device is supported by LOS 16.0 and this has awaken my interest to see whether the device is salvageable or not.
Is there any guide or any information on how I can wake the radio up?
Thanks for anything you can offer
axolotl98 said:
Hello there,
I have had this issue for some time now and hence not used the phone since then.
Now I see that the device is supported by LOS 16.0 and this has awaken my interest to see whether the device is salvageable or not.
Is there any guide or any information on how I can wake the radio up?
Thanks for anything you can offer
Click to expand...
Click to collapse
Is there any error message? What device firmware is running? Is it bootloader unlocked? Rom version?
It is really simple. The phone cannot be used as the radio seems to be permanently off. It is as if the flight mode is activated, but the flight mode is not activated. As soon as I enter the SIM card, it asks for the PIN code and the radio remains off. As the bootloader is unlocked I have tried several months back to install other OS, but was not successful in getting the radio to work . At the moment it is on Cyanogen oS 12.1-YOG4PAS3AJ on Android 5.1.1
axolotl98 said:
It is really simple. The phone cannot be used as the radio seems to be permanently off. It is as if the flight mode is activated, but the flight mode is not activated. As soon as I enter the SIM card, it asks for the PIN code and the radio remains off. As the bootloader is unlocked I have tried several months back to install other OS, but was not successful in getting the radio to work . At the moment it is on Cyanogen oS 12.1-YOG4PAS3AJ on Android 5.1.1
Click to expand...
Click to collapse
What other roms did you tried? Latest available ZUI?
strongst said:
What other roms did you tried? Latest available ZUI?
Click to expand...
Click to collapse
I will try today with ZUi 2.5.414 and repost
Well, after some time I managed to install ZUI 2.5.414 and then LOS 15.1-20190225-Nightly.
The phone works like a charm...but the radio seems tostill be off. It recognizes the SIM, it asks for the PIN, but signal is zero, no data connection. As soon as I try to place a call, the message "Turn off he airplane mode to make a call" pops up, even though the airplane mode is not on...what a shame...
axolotl98 said:
Well, after some time I managed to install ZUI 2.5.414 and then LOS 15.1-20190225-Nightly.
The phone works like a charm...but the radio seems tostill be off. It recognizes the SIM, it asks for the PIN, but signal is zero, no data connection. As soon as I try to place a call, the message "Turn off he airplane mode to make a call" pops up, even though the airplane mode is not on...what a shame...
Click to expand...
Click to collapse
You can try the qpst/qfil rom https://forum.xda-developers.com/zuk-z1/help/zui-rom-qpst-qfil-fastboot-issue-t3632025/post74256368 maybe this helps you
Thanks. Actually the ZUI was installed using QFIL. Unfortunately the radio remains inactive
Related
anyone experience this, anyone can help?
Hi, I have the same problems with the dynamics v2 rom, can someone help us? :cyclops:
Problem
KzL said:
anyone experience this, anyone can help?
Click to expand...
Click to collapse
Im experiencing the same problem after I flashed my lumia 800 with a rom. The zune software doesnt recognize the phone and sometimes the phone even does reboot, after i plugged it to the pc.
Did you get some more information with the ZENDESK?
Id be glad if you would answer my comment, thanks
After flashing, have you ever run the usb mode switch?
I've had this problem. but by using this software and selecting zune mode, it has been fixed.
Try ##634# first, and turn off the auto diag mode if it is on.
It doesn't seem to let me update the radio through zune...
I had a similar problem. Have you tried this?
jt
Astron said:
Try ##634# first, and turn off the auto diag mode if it is on.
It doesn't seem to let me update the radio through zune...
Click to expand...
Click to collapse
I am behind the times, but I just got this phone cheap and decided to try it. I could NOT get anything to recognize it. Zune would not see it and I could do no updates. There was a yellow exclamation mark in the device manager on Windows 7. Turning off diag mode fixed it all! THANK YOU! I have been fighting this for many hours!
Hi,
I was using CM13 based Nuclea OS. Tried to Lock the bootloader using the tool provided in this forum. But after that, the phone kep on starting on and off continuously and showing only Zuk Z1 logo after each boot. Then I pressed Vol UP + Vol Down + Power button for some time and the phone switched off. Now I am not able to switch it on. Tried by holding all 3 buttons and power button alone as well. Battery was 90% when I did this. Any clue?
Thanks,
Sarin
Somehow I turned the phone on (tried multiple key combinations and one of them worked). But now the Phone is in a boot loop again, ie. The Logo and 'Powered by Android' message appears after a vibration and then it switches off. This is being coontinued for the past 8 hours.
That is because u have wiped all of ur phones data and phone is bricked now
..Try connecting to pc and install Twrp recovery by going to fastboot
Harijayan994_ said:
That is because u have wiped all of ur phones data and phone is bricked now
..Try connecting to pc and install Twrp recovery by going to fastboot
Click to expand...
Click to collapse
Fastboot was not detecting the phone as it's restarting continuously. Some how I switched off the phone (I Guess I pressed and hold Power button for a very very long time and then released). Then installed ZUI Version using QFIL. Did lot of search to get the Diag Port drivers and after that it detected and installed software.
Now trying to install Original CM 12.1 OS.
Coming to the real problem why I tried to lock boot loader - Now a days all apps started checking whether phone is rooted or not I guess. It's not allowing me to install the SBI Pay App or the new IRCTC App in India. (Though Root is disabled in settings). So is there a way to install CM13/CM14 without rooting the phone.
You can go to developmee option and there is an optiom for enabling root
.. enable it and enjoy apps
I guess you got me wrong. Apps gives error that 'Your phone is rooted, Please un-root to continue'. This shows up irrespective of Root is enabled or disabled in Developer options.
sarincv said:
Fastboot was not detecting the phone as it's restarting continuously. Some how I switched off the phone (I Guess I pressed and hold Power button for a very very long time and then released). Then installed ZUI Version using QFIL. Did lot of search to get the Diag Port drivers and after that it detected and installed software.
Now trying to install Original CM 12.1 OS.
Coming to the real problem why I tried to lock boot loader - Now a days all apps started checking whether phone is rooted or not I guess. It's not allowing me to install the SBI Pay App or the new IRCTC App in India. (Though Root is disabled in settings). So is there a way to install CM13/CM14 without rooting the phone.
Click to expand...
Click to collapse
Brother! There are a lot of Noobs here! (Myself one of them!). Now somehow you got saved! You took the time and toil to find a method. So I request you to kindly specify how you did that coz if anyone else get the same problem your post will be a life saver!
Hope you'll take the trouble to explain, type and provide links! But definitely if you do, one or the other guy will thank you with all this heart!
---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------
sarincv said:
I guess you got me wrong. Apps gives error that 'Your phone is rooted, Please un-root to continue'. This shows up irrespective of Root is enabled or disabled in Developer options.
Click to expand...
Click to collapse
And yes... There is a way for that... Install Xposed. And try RootCloak... It's a root hider app. If it works then great. If not, let me know. There is another workaround.
Followed this tutorial to Flash ZUI Version. But for the Drivers I forgot which link I used. I can upload it to Google Drive and post it here.
http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
sarincv said:
Followed this tutorial to Flash ZUI Version. But for the Drivers I forgot which link I used. I can upload it to Google Drive and post it here.
http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
Click to expand...
Click to collapse
Alright bro... Then upload it and share the link please...
Please Help! I flashed my phone to Lineage OS and everything was working great except android pay. I read online to re lock the bootloader for android pay to work. I did and the phone suddenly died on me. If I try to switch on it wont switch on. It just shows ZTE logo and dies and the red notification light flashes once immediately. If I try to charge, the red notification light wont come up. Its all black. Please help if anybody knows any solution! Thank you!
It's because LOS needs unlocked bootloader. What you're experiencing is it booting into EDL. If you connect it to your computer you should near that chime that something is connected. You'll need to flash the b20 bootloader to unlock it again. Once you do that flash the nougat bootstacks and you'll be back in business.
nolimit78 said:
It's because LOS needs unlocked bootloader. What you're experiencing is it booting into EDL. If you connect it to your computer you should near that chime that something is connected. You'll need to flash the b20 bootloader to unlock it again. Once you do that flash the nougat bootstacks and you'll be back in business.
Click to expand...
Click to collapse
Thanks a lot for the reply. computer doesn't do any chime when I connect it. I dont see any drivers related to that also. I dont know what to do.
ar4m7 said:
Thanks a lot for the reply. computer doesn't do any chime when I connect it. I dont see any drivers related to that also. I dont know what to do.
Click to expand...
Click to collapse
With the phone connected to the pc, post a screen shot of the device manager screen.
hello
i got a problem with my nokia 6 im hoping someone here is able and willing to help me with.
The phone started doing a system update, but went dead and afterwards it just says that the phone has ever been rooted and that may lead to security risks and malware and instability or something like that. the phone wont even enter the revocery mode or anything, just keeps flashing the same text.
Looking forward to any help offered. since i dont know much about this kind of things id appreciate a thorough and simply put guide on how to fix it.
I reckon it's the same security patch that messed up my phone. What device do you have TA-10?? It's on the back of the device at the bottom. What version of android were you running?
Sent from my MHA-L09 using Tapatalk
imediax said:
I reckon it's the same security patch that messed up my phone. What device do you have TA-10?? It's on the back of the device at the bottom. What version of android were you running?
Sent from my MHA-L09 using Tapatalk
Click to expand...
Click to collapse
yeah its ta-1021. unfortunately i dont know what version of android was i running.
janekkkk said:
yeah its ta-1021. unfortunately i dont know what version of android was i running.
Click to expand...
Click to collapse
Hold down power and volume up until the device powers off. Now, plug the phone into your PC while holding voldown and pwr. It should now say "Download mode" in the bottom right. You can now flash MENA firmware with ost 6.0.4
Let me know if the problem persists.
quagsirus said:
Hold down power and volume up until the device powers off. Now, plug the phone into your PC while holding voldown and pwr. It should now say "Download mode" in the bottom right. You can now flash MENA firmware with ost 6.0.4
Let me know if the problem persists.
Click to expand...
Click to collapse
thank you for answering. the phone is always shut off so i cant do the first step. Neither will the phone go to download mode, simpli says the root stuff again. Only time it does something else is when trying to do a hard reset, then it will also say shutdown device: under the root stuff.
janekkkk said:
thank you for answering. the phone is always shut off so i cant do the first step. Neither will the phone go to download mode, simpli says the root stuff again. Only time it does something else is when trying to do a hard reset, then it will also say shutdown device: under the root stuff.
Click to expand...
Click to collapse
When turned off, open OST and connect your phone when it tells you to do so. It will boot into download mode automatically. (Mine did, so I assume yours will do the same)
ZeroPointMax said:
When turned off, open OST and connect your phone when it tells you to do so. It will boot into download mode automatically. (Mine did, so I assume yours will do the same)
Click to expand...
Click to collapse
got the phone into download mode now i think, atleast it says so on the bottom left corner, but when i try to do the ost la thing it gives an error everytime.
the update process failed !
error code 0xc6da
error: download fails
error=se_err_adb_cmd_GET_FAIL_result(0xc6da)
janekkkk said:
got the phone into download mode now i think, atleast it says so on the bottom left corner, but when i try to do the ost la thing it gives an error everytime.
the update process failed !
error code 0xc6da
error: download fails
error=se_err_adb_cmd_GET_FAIL_result(0xc6da)
Click to expand...
Click to collapse
Can you go into recovery? Grab the dec 2017 update and Flash it from there. This is for downgrading some mechanics that changed with Android Oreo. OST should work again. For more detail, you can look around the many threads and answers on xda.
nokia products
janekkkk said:
hello
i got a problem with my nokia 6 im hoping someone here is able and willing to help me with.
The phone started doing a system update, but went dead and afterwards it just says that the phone has ever been rooted and that may lead to security risks and malware and instability or something like that. the phone wont even enter the revocery mode or anything, just keeps flashing the same text.
Looking forward to any help offered. since i dont know much about this kind of things id appreciate a thorough and simply put guide on how to fix it.
Click to expand...
Click to collapse
I used the nokia products and realized the quality of the product. There is really a special magic in the products that attract the customer. I suggest you use nokia products. I have a site that I've introduced about the popular nokia products. Visit my blog :
@yarimehdi33 this is spam
nokia 6 dead during update Orio to Pie
imediax said:
I reckon it's the same security patch that messed up my phone. What device do you have TA-10?? It's on the back of the device at the bottom. What version of android were you running?
Sent from my MHA-L09 using Tapatalk
Click to expand...
Click to collapse
same problem with my mobile plz help how to fix this problem
Bilal Rehman said:
same problem with my mobile plz help how to fix this problem
Click to expand...
Click to collapse
Boot to download mode by pressing volume down and power button continuously when phone is off.
Download OST 6.0.4 and flash nb0 firmware.
It'll only work if you're max on Dec update.. if later then that than first flash ota from recovery to downgrade bootloader.
Hello...
I am looking for a working way to root my SM-T555
The device is running android 7.1.1;
base ver. "T555XXU1CQHA";
build ver. "NMF26X.T555XXU1CRG1";
Samsung experience 8.5;
Android security patch August 2017.
So far, the several attempts I made using every T55X related software I found in this website have been unsuccessful.
It would seem that the rooting software available is for "Marshmallow only", thus not Nougat specific,
though I read some comments stating that the TWRP made for MM worked on Nougat too and, after that, Magisk would/could do the job...
So I gave it a try but, after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again.
On top of that, the "OEM unlock" key is not present in the developer mode list: none of the "date changing tricks" I found around the web seems to fit this model.
I am inclined to believe this "might" be the mother of my problems in rooting the device though, supposedly, the patches were not for Nougat, anyway...
The developer options page, once activated, can only be "turned off" ("greyed out") but cannot be deactivated;
while, on other devices, if you turn it off the page usually disappears after rebooting then you have to tap 7 times the build version, again, in order to make it appear.
I never had problems in rooting any of the phones and tablets I have /had, including an SM-T819 running Nougat 7.1.1,
thanks to the great job done by the coders in this community to whom I would like to express my appreciation for what they do for the benefit of us all.
But this thing seems to reject everything I throw at it and it's been the most stubborn "phone like object" I ever fought with.
So far I am the one loosing the fight... I wish some of you guys could give me the means to defeat it.
Thanks in advance to whoever may be available to help me out.
Flash TWRP, then install Magisk in TWRP.
V0latyle said:
Flash TWRP, then install Magisk in TWRP.
Click to expand...
Click to collapse
thanks for your reply.
maybe my post was too long and boring so you didn't read it all
Of course I already tried the solutions posted in the page you suggested but they did not work.
not the autoroot files, not the recovery, etc...
I quote: "after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again."
If there is a TWRP file specific for my Nougat version available I'd be happy to give it a shot
endlessquest said:
thanks for your reply.
maybe my post was too long and boring so you didn't read it all
Of course I already tried the solutions posted in the page you suggested but they did not work.
not the autoroot files, not the recovery, etc...
I quote: "after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again."
If there is a TWRP file specific for my Nougat version available I'd be happy to give it a shot
Click to expand...
Click to collapse
Did you follow a guide when flashing TWRP? Did you unlock your bootloader?
You need to be clear and concise in your posts as yo what you did and how.
V0latyle said:
Did you follow a guide when flashing TWRP? Did you unlock your bootloader?
You need to be clear and concise in your posts as yo what you did and how.
Click to expand...
Click to collapse
of course I did follow the guide by the book. also, the recovery appears to be installed properly, Odin showing a nice green PASS sign, but it doesn't work anyway
now about unlocking the bootloader, as I mentioned in my first post:
"the "OEM unlock" key is not present in the developer mode list: none of the "date changing tricks" I found around the web seems to fit this model.
I am inclined to believe this "might" be the mother of my problems in rooting the device"
every time I had to re install the system, so there clock want back to zero. Maybe I should be waiting for the allotted number of days to pass on order for the OEM unlock key to appear...
but before my first attempt to root the device, almost one month was past and the OEM unlock key wasn't there, notwithstanding...
I hope there was a chance that the bootloader was already unlocked...
to be concise (schematic):
tablet in download mode
untick auto reboot in Odin
AP loaded with "smt550_cf-autoroot.tar"
flash with Odin, OK, green sign PASS
reboot manually home+volume down+power,
then switch to volume up when screen becomes black
the Samsung logo appears and stays there indefinitely
So I turn the device off, long pressing the power key
then I try and turn on the tablet but does not turn on anymore,
not even pressing the power button for 30 second
then I press home+volume down+power again
to enter download mode and reinstall stock rom
(the same happens with
sm-t550_p550_p555_cf-autoroot.tar
or twrp_3.0.2-1_sm-t550_mm_7816.tar,
I also tried
twrp_3.1.1-1_sm-t355_251117
remark: none of them mentions T555 nougat)
Put your tablet in Download Mode and take a picture of the text at the upper left of the screen.
V0latyle said:
Put your tablet in Download Mode and take a picture of the text at the upper left of the screen.
Click to expand...
Click to collapse
What process did you follow to unlock your bootloader?
Stop trying to use Autoroot. Let's figure out what we need to do to get TWRP on your device. Once we do that, you can flash Magisk in TWRP for root.
Please read this guide, sections 1 through 4 (don't worry about the GSI stuff) and tell me what you have or have not done.
ok, I wasn't able to do this:
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
OEM Unlocking is missing in the list, as I mentioned in my previous posts
I tried the date change trick but it didn't work
endlessquest said:
ok, I wasn't able to do this:
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
OEM Unlocking is missing in the list, as I mentioned in my previous posts
I tried the date change trick but it didn't work
Click to expand...
Click to collapse
This is the first step. You cannot flash custom or modified images if the bootloader is locked.
Connect to the Internet and check for updates in system options, then check Developer Options again.
I did that step too, several times:
the system found an update available
the first times I cancelled the download
then I downloaded the update without installing it
then I tried and installed it
no result at all the attempts: the OEM Unlock key does not appear in developer options
endlessquest said:
I did that step too, several times:
the system found an update available
the first times I cancelled the download
then I downloaded the update without installing it
then I tried and installed it
no result at all the attempts: the OEM Unlock key does not appear in developer options
Click to expand...
Click to collapse
Has it ever appeared before?
V0latyle said:
Has it ever appeared before?
Click to expand...
Click to collapse
it is the first time I work on this specific device, so I couldn't tell: so far I couldn't find the OEM unlock option in the list
it never happened before on any of the several devices I have rooted in my life,
included another Samsung tablet SM-T819 running Nougat 7.1.1: the option was right there and all I had to do is tick it.
I used fastboot for other brands
I wish there was a way to use fastboot to unlock the bootloader on Samsung
if there is any I don't know it
adb is working, but when I give the "adb reboot fastboot" command, the tablet enters the download mode and fastboot does not see the tablet anymore from the computer
endlessquest said:
it is the first time I work on this specific device, so I couldn't tell: so far I couldn't find the OEM unlock option in the list
it never happened before on any of the several devices I have rooted in my life,
included another Samsung tablet SM-T819 running Nougat 7.1.1: the option was right there and all I had to do is tick it.
I used fastboot for other brands
I wish there was a way to use fastboot to unlock the bootloader on Samsung
if there is any I don't know it
adb is working, but when I give the "adb reboot fastboot" command, the tablet enters the download mode and fastboot does not see the tablet anymore from the computer
Click to expand...
Click to collapse
Samsung devices do not have a fastboot mode.
Since this is a Snapdragon device, it probably cannot be unlocked, especially if it was marketed in the US.
Only Exynos and international Snapdragon devices can be unlocked, unfortunately.
V0latyle said:
Samsung devices do not have a fastboot mode.
Since this is a Snapdragon device, it probably cannot be unlocked, especially if it was marketed in the US.
Only Exynos and international Snapdragon devices can be unlocked, unfortunately.
Click to expand...
Click to collapse
actually I am in Rome, Italy so I am quite positive it was marketed here...
is there a way to know for sure whether or not it is international?
the Samsung SM-T819 I am writing from has a snapdragon chip
but I had no problem unlocking/rooting it,
I bought both the devices here in Rome
now that's a mystery...
endlessquest said:
actually I am in Rome, Italy so I am quite positive it was marketed here...
is there a way to know for sure whether or not it is international?
Click to expand...
Click to collapse
Usually the model number is a good indication with phones - the G908U vs G908N for example, but I don't see that being the case here
Have you tried signing into a Samsung or Google account on the device before checking for updates and looking for OEM Unlocking?
V0latyle said:
Usually the model number is a good indication with phones - the G908U vs G908N for example, but I don't see that being the case here
Have you tried signing into a Samsung or Google account on the device before checking for updates and looking for OEM Unlocking?
Click to expand...
Click to collapse
I did that too...
on a freshly installed rom:
I connected the internet thru wireless
signed into my Google account
completed the tablet configuration, etc
then I went and enable the developer options
no OEM Unlocking yet again...
endlessquest said:
I did that too...
on a freshly installed rom:
I connected the internet thru wireless
signed into my Google account
completed the tablet configuration, etc
then I went and enable the developer options
no OEM Unlocking yet again...
Click to expand...
Click to collapse
You manually checked for an update too?
Did you try disconnecting from the Internet, disabling network time, and manually setting the time ahead 1 week?