Related
I bought this tablet 2 months ago in our local t-mobile. And everything was fine until 2 weeks ago when it suddenly started loosing gsm signal.
At first i thought it had something to do with me rooting it. So i tried repairing it 2 times but with no luck. After that i tried downgrading to 4.1.2 and that didn't work either.
So basically i can be online (surfing,downloading etc.) for few minutes before it drops gsm signal (no signal icon in statusbar) and after few minutes it comes back and then it drops again...
I'd like to know if it can be fixed without taking it to nearest sony repair service. Did anyone encounter similar problem and manage to fix it?
btw bootloader is locked (unlock allowed: no) so flashin another kernel/ROM is out of the question...
wh15tler said:
I bought this tablet 2 months ago in our local t-mobile. And everything was fine until 2 weeks ago when it suddenly started loosing gsm signal.
At first i thought it had something to do with me rooting it. So i tried repairing it 2 times but with no luck. After that i tried downgrading to 4.1.2 and that didn't work either.
So basically i can be online (surfing,downloading etc.) for few minutes before it drops gsm signal (no signal icon in statusbar) and after few minutes it comes back and then it drops again...
I'd like to know if it can be fixed without taking it to nearest sony repair service. Did anyone encounter similar problem and manage to fix it?
btw bootloader is locked (unlock allowed: no) so flashin another kernel/ROM is out of the question...
Click to expand...
Click to collapse
Have you tried factory resting it ? Also you can unlock the boot loader just search xda im sure ive seen a guide somewhere ? i was going to say take it back to Sony as it might be a hardware problem but since you have rooted it your warranty has been voided...
N1NJATH3ORY said:
Have you tried factory resting it ? Also you can unlock the boot loader just search xda im sure ive seen a guide somewhere ? i was going to say take it back to Sony as it might be a hardware problem but since you have rooted it your warranty has been voided...
Click to expand...
Click to collapse
Well firmware flashing via SUS repair option usually does that for me.. but yeah, i tried factory reset as well. And about bootloader unlocking i've been searching for a guide ever since i bought it. No such luck... Apparently if it's "bootloader unlock allowed: NO", it's meant to stay that way. At least until someone finds a way around it.
I've got a vague idea about how does rooting work and that tells me if i did a complete wipe and flashed my tablet, how can they detect it?
I mean.. it's a complete reinstall, how are they supposed to know that the tablet was rooted on previous firmware if it currently isn't?
wh15tler said:
Well firmware flashing via SUS repair option usually does that for me.. but yeah, i tried factory reset as well. And about bootloader unlocking i've been searching for a guide ever since i bought it. No such luck... Apparently if it's "bootloader unlock allowed: NO", it's meant to stay that way. At least until someone finds a way around it.
I've got a vague idea about how does rooting work and that tells me if i did a complete wipe and flashed my tablet, how can they detect it?
I mean.. it's a complete reinstall, how are they supposed to know that the tablet was rooted on previous firmware if it currently isn't?
Click to expand...
Click to collapse
Well im no pro, but don't they have some kind of binary counter witch tells the manufactures the devices has been rooted ? i know that's how Samsung goes about identifying if the devices has been rooted... But Sony im not too sure, Also your theory does hold ground, if you clean install from the ground up then Sony shouldn't be able to tell, if the device has been rooted, also you do know that Sony have a guide on there website on how to unlock the boot loader ? Here check it out http://developer.sonymobile.com/services/unlock-bootloader/
N1NJATH3ORY said:
Well im no pro, but don't they have some kind of binary counter witch tells the manufactures the devices has been rooted ? i know that's how Samsung goes about identifying if the devices has been rooted... But Sony im not too sure, Also your theory does hold ground, if you clean install from the ground up then Sony shouldn't be able to tell, if the device has been rooted, also you do know that Sony have a guide on there website on how to unlock the boot loader ? Here check it out...
Click to expand...
Click to collapse
I know about that website. That's how i unlock every sony i come across that needs unlocking :laugh:
But it also says if the "Bootloader unlock allowed" is NO in service menu, then there is no hope for unlocking the bootloader. At least not officially.. until someone comes with a solution for that..
So i managed to get some extra details on that problem.
Apparently i can't get LTE signal anywhere. And when i get LTE, connection automatically drops.
Could it be that the LTE chip is faulty? Does that mean that i'll probably get another device... because somehow i doubt that theyll try to replace the motherboard
Hi all,
I've just unlocked my H850 bootloader "successfully" if I may say. why ? Because once it's was done, I get warnings on boot.
The first one says: "Your device software can’t be checked for corruption." with an Orange triangle.
The I got a second one with a red triangle which says "Your device is corrupt. It can’t be trusted and may not work properly"
The first message appears for about 3 seconds then the second for about 8sec then the LG logo and it boots normally...
I still didn't flash the SuperSU zip file to root since I don't have an external storage.
What might be the effects of those warnings ? Should I be worried ? My phone is still working normally however...
How can I erase them ?
Should I keep going with the rooting process ?
Thanks in advance for your answers.
dbaOCP said:
Hi all,
I've just unlocked my H850 bootloader "successfully" if I may say. why ? Because once it's was done, I get warnings on boot.
The first one says: "Your device software can’t be checked for corruption." with an Orange triangle.
The I got a second one with a red triangle which says "Your device is corrupt. It can’t be trusted and may not work properly"
The first message appears for about 3 seconds then the second for about 8sec then the LG logo and it boots normally...
I still didn't flash the SuperSU zip file to root since I don't have an external storage.
What might be the effects of those warnings ? Should I be worried ? My phone is still working normally however...
How can I erase them ?
Should I keep going with the rooting process ?
Thanks in advance for your answers.
Click to expand...
Click to collapse
This has already been asked many times, just search in the bootloader unlock thread or in TWRP thread...
Back to the "problem", well, it's NORMAL, starting from Android Marshmallow on ALL devices with an unlocked bootloader will boot with those warning, so nope, nothing to worry about, and nope, at the moment is not possibile to remove those warnings
Thanks for your answer. I've seen such threads but no one is talking about the second warning in red. I'm asking specially for that one..
Isn't this just the same as the warning that you get on Samsung devices where it pops up the alert to say "This device is not SE enforcing."
If you're unlocking the Bootloader, you're opening up something that logically (since you're opening the door to rooting the device), you can more easily compromise the device security - only fair that they warn you and stop the warnings from being suppressed, my devices have always worn that "branding" as a badge of honour
BahnStormer said:
Isn't this just the same as the warning that you get on Samsung devices where it pops up the alert to say "This device is not SE enforcing."
If you're unlocking the Bootloader, you're opening up something that logically (since you're opening the door to rooting the device), you can more easily compromise the device security - only fair that they warn you and stop the warnings from being suppressed, my devices have always worn that "branding" as a badge of honour
Click to expand...
Click to collapse
Thanks you make me sure of my device again
Did you root it ? Is it mandatory to use an SD card or you could do it without it ?
After more than 6 months, I'd like to know if there is anything available to remove those message?
dsr250p said:
After more than 6 months, I'd like to know if there is anything available to remove those message?
Click to expand...
Click to collapse
Afaik no
dsr250p said:
After more than 6 months, I'd like to know if there is anything available to remove those message?
Click to expand...
Click to collapse
Alas, not without a custom kernel for the stock firmware. I also have a bootloader unlocked rooted Nexus 6 running MM that doesn't display the warning. Why not? To root the Nexus 6 with MM you had to flash a custom kernel. The developers of the Nexus 6 kernels were somehow able to eliminate the unlocked bootloader warning, but I haven't a clue as to what was needed for them to accomplish its removal.
dbaOCP said:
Thanks you make me sure of my device again
Did you root it ? Is it mandatory to use an SD card or you could do it without it ?
Click to expand...
Click to collapse
You don't need an SD card to root.
Abort said:
To root the Nexus 6 with MM you had to flash a custom kernel. The developers of the Nexus 6 kernels were somehow able to eliminate the unlocked bootloader warning, but I haven't a clue as to what was needed for them to accomplish its removal.
Click to expand...
Click to collapse
But the Nexus 6 is a different device than the LG G5, for some reasons it seems impossible to get rid off the warning message with the LG.
dsr250p said:
But the Nexus 6 is a different device than the LG G5, for some reasons it seems impossible to get rid off the warning message with the LG.
Click to expand...
Click to collapse
You are absolutely correct, and I share your lament that no H850 developer has appeared on the scene with a simple solution for the stock G5. Honestly Annoying has done some very slick work to install a userdebug kernel that permits the disabling of dm-verity, which might therefore eliminate dm-verity warnings. But as you will see at the following link, it is anything but simple. https://forum.xda-developers.com/lg-g5/how-to/guide-adb-root-rw-dm-verity-off-sprint-t3523499
Alright, I see. At this time I will take a distance of using this exploit called "dirtysanta", but hopefully some simple load still coming up.
dsr250p said:
Alright, I see. At this time I will take a distance of using this exploit called "dirtysanta", but hopefully some simple load still coming up.
Click to expand...
Click to collapse
You may want to think twice about DirtySanta. The OP states the following:
Working Devices:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
You'll note the H850 is not listed. Honestly Annoying's work is the only way I've seen to disable dm-verity on the H850, but there are too many drawbacks associated with it for me to try it simply to eliminate the "Your device software cannot be checked for corruption" warning.
I'll get back to this topic during the next 6 months to see if there is a better solution available. I am not in a hurry.
I have never read the about the red triangle warning
Welcome to DM-VERITY
Still_living714 said:
I have never read the about the red triangle warning
Click to expand...
Click to collapse
Here is an article that will tell you about dm-verity and the warnings it presents, including the very familiar orange triangle due to an unlocked bootloader. The red warning is different, and also discussed in the article.
https://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
Hello All,
Hope you and yours are doing fine in these worldwide complicated days.
Regarding the subject, I have a Xiaomi Mi Play mobile that was working fine, with official MIUI, never rooted, never done something else than usual "office" daily usage.
One day, came the famous Security Update notification and as usual, I've confirmed.
Since then big headaches...
Next morning I found the phone in the loop reboot, Fastboot being the only available feature, no more recovery, no more OS, no more personal stuff... Everything has been deleted by the update.
When trying to go to recovery only the magnificent message with the red triangle, saying "The system has been destroyed. Press the power button to shutdown" stays for 10-15 secs and then the whole crap reboots again and again.
No, Developer Settings haven't been enabled, OEM Unlock has not been enabled, USB Debugger neither, bootloader has not been unlocked, MIUI account has not been added in Developer Settings or elsewhere... and no I haven't wrote to Xiaomi support yet.
I've tried around 60-80 different methods to unlock whatever could be unlocked on Xiaomi phone, EDL, bootloader, with dozens and dozens of methods proposed, so far nothing worked. Impossible to install anything, impossible to unlock anything, impossible to do anything.
I've applied for the phone unlock, but since 2 months, impossible to finish the process, it says "Couldn't Unlock - Please add your account in MIUI's Settings > Developer options > Mi Unlock Status"
But I CANNOT access the system anymore at all....
This is it...
Thank you for reading and if you have any other ideas out of everything I've tried, feel free to let me know about.
Take care of you and yours
Kind Regards,
SK
ooophhh no. did you ever get a solution? i had my mi play brick just oputta the blue.. its on communist lockdown fighting the war on capitalism ..... well the hardware wasnt bad for the price and it ran well.,but im not buying a phone from them ever again.
It's very sad. Did you get any update?
Hello All,
No update since March, still looking and trying to unbrick the device....
I'll keep you posted if I find anything that could be called a solution.
Thanks for your support.
Be safe all, you and yours.
Kind Regards,
SK
Same here, bricked device since March by the same update, "The System has been destroyed", fastboot doesn't load.
I guess i've lost 150$.
Produkt87 said:
Same here, bricked device since March by the same update, "The System has been destroyed", fastboot doesn't load.
I guess i've lost 150$.
Click to expand...
Click to collapse
There are many thread for issues like this, for example:
https://forum.xda-developers.com/mi-9-se/help/lock-bootloader-destroyed-help-t3965825
It seems that in some way, same issue was fixed on a different model, but most likely it will work also with Mi Play.
Af far as I have understood, basically the solution is to download the official firmware and flash it back. The main issue is that by default the bootloader is locked so nothing can be written. The point here is how to unlock the phone, and there is an official procedure from Xiaomi:
https://forum.xda-developers.com/mi-9t/how-to/guide-unlock-bootloader-flash-xiaomi-eu-t3952443
I have the same issue for a couple of hours and I am struggling now, so as first step I am trying to unlock the bootloader, but the problem is that per Xiaomi instructions it may take up to 7 days.
So, I will apply for that, while in the meantime I will look for any alternative solutions (if any).
Regards,
Thanks a lot!
But, the're now way to get my phone into fastboot mode.
I've tried all button combinations and there's no response, just the same loop "your system has been destroyed"
Produkt87 said:
Thanks a lot!
But, the're now way to get my phone into fastboot mode.
I've tried all button combinations and there's no response, just the same loop "your system has been destroyed"
Click to expand...
Click to collapse
After some tests on my device, I have found out that it's not easy as I have believed, but if you don't get even in Fastboot mode it's more complicated.
However, can you please clarify what's your cellphone model?
Regards,
I have exactly the same problem since early May, if I just unlock the boot loader before they fall down :c
hello .... I have a sister redmi note 4 who has a bootloop ... on the screen with the MI logo it keeps restarting .... it goes to fastboot but not to recovery ... the bootloader is locked and I still can't unlock it because what I looked so unlocked in the system by logging into my MI account ... but I can't get to the system ... I tried my flash but it says that it did something for 4 seconds and nothing still the same .... I tried to put it into download mode - by connecting contacts on the board and miflash download ROM to the phone but bootloop still continues
do you have any ideas?
the phone was so stupid that it kept restarting but always after several restarts it started but now even after two days of restart it didn't start ...
thanks sorry for my english
I had a stroke reading this.
Unlocked bootloader is the basic requirement of flashing. If you don't have it, then sorry you're out of options.
Your only option is to flash stock ROM through test-point method. DO IT ON YOUR OWN RISK.
You can find Xiaomi stock ROMs of your device here (MTK) or here (MIDO).
Of course you can always just send your device to a repair center and change it there.
Goodluck.
test point method is lint two pins od board and run mobile to download mode? I try it ... flashing was succesfull but mobile ist still bootloop
johnyfly1 said:
test point method is lint two pins od board and run mobile to download mode? I try it ... flashing was succesfull but mobile ist still bootloop
Click to expand...
Click to collapse
You need to flash stock ROM not any other ROM.
As in the same ROM you had before any issue. Because your bootloader is locked it will refuse to run any boot image that isn't registered in it.
If you have a backup maybe you can flash it through download mode.
I try ROMs from your link and not working...always bootloop I try a lot of ROMs - global, china, stable, weekly and not working....flash is succesfull around 190seconds.... but still bootloop
johnyfly1 said:
I try ROMs from your link and not working...always bootloop I try a lot of ROMs - global, china, stable, weekly and not working....flash is succesfull around 190seconds.... but still bootloop
Click to expand...
Click to collapse
Do you know what ROM you had before the issue started?
I dont know is sister phone... but she have original stock rom... i think global because phone was buy on slovakia
johnyfly1 said:
I dont know is sister phone... but she have original stock rom... i think global because phone was buy on slovakia
Click to expand...
Click to collapse
I Can't help you there mate.
Maybe there is a way to get system info from bricked phone. Maybe through a hex editor or something. That way you know exact version of the ROM you had.
So instead of that maybe you can unlock your bootloader, just request from Xiaomi unlock code with your XIaomi account and unlock it. It usually takes 30-60 days for the request to go through.
Where I find old way to unlock bootloader? because in new unlocker I unlock phone butt I must log in to my account in system... thanks
johnyfly1 said:
Where I find old way to unlock bootloader? because in new unlocker I unlock phone butt I must log in to my account in system... thanks
Click to expand...
Click to collapse
There is no other way to unlock bootloader. Unless you know a guy, know what I'm sayin?