Hi everyone,
I've been trying to figure out for a few days on other threads, hows I can rollback my phone, lock the phone, and update to Pie. I need to take it in for warranty service tomorrow morning (camera often won't focus) and haven't been able to find out how to do this safely. I am unlocked, rooted, and running on version 385 which I downloaded from FF and flashed using HuR in TWRP.
If anyone could provide me with instructions for how to get this phone to where I need it to be to give it to the warranty shop, I would very much appreciated it. Any help is very much appreciated.
Just a bump to explain:
Hey guys, sorry to be a broken record, I just really want to get my phone fixed under warranty before my brother's wedding (there is a problem with the camera). If someone could please tell me how to go back to stock and lock the bootloader so I can update to PIE that would be great. I have been told by the warranty service people that I need to have the newest update on the phone and wipe the phone of my personal data before bringing it in.
Instructions would be great, and any help is appreciated!
shiboby said:
Just a bump to explain:
Hey guys, sorry to be a broken record, I just really want to get my phone fixed under warranty before my brother's wedding (there is a problem with the camera). If someone could please tell me how to go back to stock and lock the bootloader so I can update to PIE that would be great. I have been told by the warranty service people that I need to have the newest update on the phone and wipe the phone of my personal data before bringing it in.
Instructions would be great, and any help is appreciated!
Click to expand...
Click to collapse
who told you that you MUST have the latest update for the warranty to be honored? Just reinstall stock B385 with HuRU and relock the bootloader. Something like
Code:
fastboot oem lock
or
Code:
fastboot oem lock
Should work.
EDIT: sorry, here you have exact info: https://forum.xda-developers.com/honor-9/help/lock-honor-9-bootloader-t3676444
enban said:
who told you that you MUST have the latest update for the warranty to be honored? Just reinstall stock B385 with HuRU and relock the bootloader. Something like
Code:
fastboot oem lock
or
Code:
fastboot oem lock
Should work.
EDIT: sorry, here you have exact info: https://forum.xda-developers.com/honor-9/help/lock-honor-9-bootloader-t3676444
Click to expand...
Click to collapse
thanks for the message. The guy I spoke with on the phone at the location I have to take the phone told me that. If I reflash 385 stock unrooted and relock, could I then allow the PIE update to install?
shiboby said:
thanks for the message. The guy I spoke with on the phone at the location I have to take the phone told me that. If I reflash 385 stock unrooted and relock, could I then allow the PIE update to install?
Click to expand...
Click to collapse
I guess so.
enban said:
I guess so.
Click to expand...
Click to collapse
and I could do this HuR updater?
shiboby said:
and I could do this HuR updater?
Click to expand...
Click to collapse
I guess you can... But last time I used HuRu I was able to (very) hard brick my phone...
Related
As the tittle says, stay away from SE official FW updates OTA or through pc, it will brick your phone when you have unlocked your bootloader and modified your firmware.
As of now there's no fix that will bring your phone completely back. The fix will brake your radio and your phone functions wont work, sms, calls etc.
Blagus is working on a fix that also restores the radio (a full fix).
See links below for help and Blagus progress.
Made this thread cause I see more and more people bricking there phones after an update with unlocked bootloaders and modified firmware.
http://forum.xda-developers.com/showthread.php?t=1056094 (Help)
http://forum.xda-developers.com/showthread.php?t=1085184 ([dev]Blagus)
Read this first if you haven't unlocked your bootloader, but planning to. It's how to backup your phone before a BL unlock.
http://forum.xda-developers.com/showthread.php?t=1105425 ([backup]blagus)
Regards Dousan..
e: it's safe to update if you rooted using gingerbreak.
If only I saw this topic this morning ...
for now I give a try to wotanclient ... hope it will work
Add this thread too: http://forum.xda-developers.com/showthread.php?t=1105425
Dousan said:
As the tittle says, stay away from SE official FW updates OTA or through pc, it will brick your phone when you have unlocked your bootloader and modified your firmware.
As of now there's no fix that will bring your phone completely back. The fix will brake your radio and your phone functions wont work, sms, calls etc.
Blagus is working on a fix that also restores the radio (a full fix).
See links below for help and Blagus progress.
Made this thread cause I see more and more people bricking there phones after an update with unlocked bootloaders and modified firmware.
http://forum.xda-developers.com/showthread.php?t=1056094 (Help)
http://forum.xda-developers.com/showthread.php?t=1085184 ([dev]Blagus)
Regards Dousan...
(maybe it could be a sticky?)
Click to expand...
Click to collapse
How about if it is only rooted?
jenkidom said:
How about if it is only rooted?
Click to expand...
Click to collapse
In that case you're safe to update. But OTA won't work in that case, only SEUS. This issue is happening only on BL unlocked phones.
Blagus said:
Add this thread too: http://forum.xda-developers.com/showthread.php?t=1105425
Click to expand...
Click to collapse
Added
Regards Dousan...
Has anyone tried to go in this menu *#*#4636#*#* and use the turn off/on radio option?
Hi guys ill be getting a unlocked rogers play soon. My question is how would i know if the phone is rooted? Is there a way to find out? thank you.
bongajushe said:
Hi guys ill be getting a unlocked rogers play soon. My question is how would i know if the phone is rooted? Is there a way to find out? thank you.
Click to expand...
Click to collapse
Download terminal emu and open it an type:
su (hit enter) and if it comes back with this:
# it's rooted
If not it might still be rooted but if superuser and busybox is not installed it won't work. If it's a used device and the previous owner rooted it those programs should be installed unless the that person reflashed the phone with a generic FW then it won't be rooted unless it was with a modded/rooted .img.
Regards Dousan...
I recovered from a complete brick when I inadvertently did an OTA update with an unlocked and rooted rom. (Brick as in: when trying to power on the phone, it just vibrates.. if you continue to hold the power button it just vibrates randomly and it resembles the phone being dead, there is no activity at all)
Basically just flashed the bootloader relock then flashed the generic UK firmware. Took maybe 2 minutes and I was back in business.
Any ideas on how to fix my Xperia Ray? HELP..
Quick backstory - my Xperia Ray won't read my SIM card anymore. It doesn't even ask for my PIN number, it just boots as normal (after asking me to pick a language) but I have no connection to any network. I've tried using the SIM card in another phone and it works fine, therefore the problem is with the phone itself.
I'd recently had my phone network & bootloader unlocked by wotanserver using the test point method - because of this I thought the DRM keys would be fine (e.g. TrackId & Timescape still worked). However, when I was updating from GB .42 to .62 OTA (to flash a GB ROM) my phone bricked! (Does this mean the DRM keys weren't intact? Confused.)
So, I searched for a solution and ended up using s1tool to relock the bootloader. Then I used flashtool to flash a stock ICS ftf file. It seemed to work (the phone rebooted) but it was then I noticed that the SIM card wasn't being recognised. Also, in the Flashtool log I noticed that a blue line was there saying 'this file is ignored simlock.ta'.
Anyway, my real dilemma is - which of the Available Omnius Operations for the Xperia Ray (see link: http://www.omnius-server.com/phone?id=20… should I pick to fix this?
Backup TA
Flash
Identify
Live boot
Repair S1-boot
Restore TA
Revive phone after OTA flash
Unlock bootloader
Unlock network lock by certificate replacement
Repair S1boot? Restore TA? I really don't know. Would really. really appreciate someone's help - I need my phone back urgently!
Updating via OTA on an unlocked bootloader does lead to a bricked Phone, which just requires THIS to fix it.
XperienceD said:
Updating via OTA on an unlocked bootloader does lead to a bricked Phone, which just requires THIS to fix it.
Click to expand...
Click to collapse
Hi, thanks for your reply! I'm not sure what you mean though - the link provided in the first post on that thread took me to a dodgy website to download a file called 'downloadmanager
_setup' All that did was install crap like 'Zoomdownloader' and other non-android related rubbish on my computer. So I'm not best pleased about that...
Anyhoo, my phone isn't really bricked - it works fine apart from the SIM problem. I was asking what fix in the Omnius list of options applied to my situation. Do I need to Repair S1-boot? Do I need to 'Restore TA?' I really don't know to be honest.
All I really need to know is what option from Omnius's list applies to my situation...
seamo123 said:
Hi, thanks for your reply! I'm not sure what you mean though - the link provided in the first post on that thread took me to a dodgy website to download a file called 'downloadmanager
_setup' All that did was install crap like 'Zoomdownloader' and other non-android related rubbish on my computer. So I'm not best pleased about that...
Click to expand...
Click to collapse
Just checked the link myself, as it didn't skip the ad and asked you to download something else instead, that should have rang alarm bells. This is what you should have downloaded - FlashTool_0.2.9.1_FOTAUnbrick
seamo123 said:
Anyhoo, my phone isn't really bricked - it works fine apart from the SIM problem.
Click to expand...
Click to collapse
Your Phone was bricked in the first place due to an OTA update, and should actually state in what ever thread you used to unlock not to use the OTA feature after doing so, the attachment normally fixes that, given that you've re-locked using S1Tool then you may have done more harm than good. If I knew what option to suggest I would have done so, so unless anyone else does then it's trial and error I'm afraid.
Is it too late for me to give the link you gave me a shot then? Or might it do more harm than good at this stage? Thanks for your help btw, I appreciate it.
seamo123 said:
Is it too late for me to give the link you gave me a shot then? Or might it do more harm than good at this stage? Thanks for your help btw, I appreciate it.
Click to expand...
Click to collapse
You could try to unlock the boot loader again, flash stock ICS and kernel and try again to connect the sim card...
Or have you tried PC companion to fix your phone? Try this first!
But I can't promise anything, maybe you will end up in a bigger problem than now
Sent from my Nexus 7 running Android 4.2.1
Hello everyone, this is my first post, the one issue that made me register
Ill be as short as i can :
I have a sony xperia P t-mobile locked so:
-Bootloader locked,
-root goes up no problem, works,
-CWM goes up this one,works:
http://forum.xda-developers.com/showthread.php?t=2020895
-i copy the rom on the phone, factory reset all that junk, i start to flash i get the "getprop nypon" aka Status 7 error code(tried several roms, all do the same)
-i go and modify the upgrade script via this method http://forum.xda-developers.com/showthread.php?t=2302599
The rom installs, i install the gapps and whatnot and when i go to reboot it goes brick, i can get it to vibrate for hard reset but thats all(luckily the xperia updater software recovers so its not bricked out atm) but thats all, no other response no sony logo no nothing.
I was trying to flash the CM11 nightly to my phone, and i dont have a clue what have gone wrong... any ideas? should i try another one? did i mess up the flashscript modifying?(i checked for space) Any input and suggestion is highly appreciated, thank you in advance!!
TheGregButcher said:
Hello everyone, this is my first post, the one issue that made me register
Ill be as short as i can :
I have a sony xperia P t-mobile locked so:
-Bootloader locked,
-root goes up no problem, works,
-CWM goes up this one,works:
http://forum.xda-developers.com/showthread.php?t=2020895
-i copy the rom on the phone, factory reset all that junk, i start to flash i get the "getprop nypon" aka Status 7 error code(tried several roms, all do the same)
-i go and modify the upgrade script via this method http://forum.xda-developers.com/showthread.php?t=2302599
The rom installs, i install the gapps and whatnot and when i go to reboot it goes brick, i can get it to vibrate for hard reset but thats all(luckily the xperia updater software recovers so its not bricked out atm) but thats all, no other response no sony logo no nothing.
I was trying to flash the CM11 nightly to my phone, and i dont have a clue what have gone wrong... any ideas? should i try another one? did i mess up the flashscript modifying?(i checked for space) Any input and suggestion is highly appreciated, thank you in advance!!
Click to expand...
Click to collapse
And why exactly are you trying to flash a rom that is for unlocked bootloader only?
No CMs for you., stock based ROMs only..
ChikeD said:
And why exactly are you trying to flash a rom that is for unlocked bootloader only?
No CMs for you., stock based ROMs only..
Click to expand...
Click to collapse
Thanks i knew i was overlooking something... i didnt even know you cant flash "random" stuff with a locked bootloader.
By the way is there a method around this? i failed to find any.
TheGregButcher said:
Thanks i knew i was overlooking something... i didnt even know you cant flash "random" stuff with a locked bootloader.
By the way is there a method around this? i failed to find any.
Click to expand...
Click to collapse
You can't "flash", as this feature in the BIOS, but you can do virtually anything you want with your phone once you have root permission.
Is your bootloader unlockable?
ChikeD said:
You can't "flash", as this feature in the BIOS, but you can do virtually anything you want with your phone once you have root permission.
Is your bootloader unlockable?
Click to expand...
Click to collapse
Sadly no, mine is carrier locked so its bootloader locked as well( if i could i would have did it already) thats what im asking, is there even a method to unlock a not unlockable bootloader? some nifty dark alleyway backdoor etc... way?
TheGregButcher said:
Sadly no, mine is carrier locked so its bootloader locked as well( if i could i would have did it already) thats what im asking, is there even a method to unlock a not unlockable bootloader? some nifty dark alleyway backdoor etc... way?
Click to expand...
Click to collapse
Hmmmm, have you checked in service menu?
There might be unofficial method, I don't know if it's for unlockable bootloader.
Luckily, here it's not allowed bind users to service anymore, and carriers must unlock it if the owner of the phone request it.
ChikeD said:
Hmmmm, have you checked in service menu?
There might be unofficial method, I don't know if it's for unlockable bootloader.
Luckily, here it's not allowed bind users to service anymore, and carriers must unlock it if the owner of the phone request it.
Click to expand...
Click to collapse
yep i checked the service menu thats why i know its not unlockable. i might try to get in touch with t-mobile support and ask them for an unlock code... the only ones i found on the internet, costed quite a sum of money. anyway, i wouldnt even bother with it that much, the speed is acceptable and im okay with the default sony interface, but the phone app freaking out and freezing a lot makes me a bit angry about it...
TheGregButcher said:
yep i checked the service menu thats why i know its not unlockable. i might try to get in touch with t-mobile support and ask them for an unlock code... the only ones i found on the internet, costed quite a sum of money. anyway, i wouldnt even bother with it that much, the speed is acceptable and im okay with the default sony interface, but the phone app freaking out and freezing a lot makes me a bit angry about it...
Click to expand...
Click to collapse
You mean the phone lag issue with incoming/outgoing calls?
It's not too bad in firmware 6.2.A.1.100.
ChikeD said:
You mean the phone lag issue with incoming/outgoing calls?
It's not too bad in firmware 6.2.A.1.100.
Click to expand...
Click to collapse
Yes i mean that. Its not that bad and a complete off/on solves it for a while, still it cripples the main usage of a phone...it can be quite annoying when it ballses up when you need to make an urgent phonecall...
TheGregButcher said:
Yes i mean that. Its not that bad and a complete off/on solves it for a while, still it cripples the main usage of a phone...it can be quite annoying when it ballses up when you need to make an urgent phonecall...
Click to expand...
Click to collapse
Yes that's true, I realy wonder why sony did not fix that yet.
For me it's first of all a phone, the rest is just etras.
Dear all,
I am asking for the solutions to solve this issue.
The device goes into bootloop after updating to 5.0.2.
It was known that the device has not enable OEM Unlock through development options. (and cannot get into setting page at this moment.)
Therefore, i cannot unlock the device by using
"fastboot oem unlock" in the fastboot mode of the device.
I have tried wipe data and perform factory reset in recovery mode.
but the device still get into bootloop.
May i ask for any possible solution for flashing back stock rom?
I'm in the same situation. I believe the only solution is to return the device for "repair".
Go to recovery, wipe cache, making sure to give it a full hour to finish. Then reboot. You'll probably still be on 5.0.1.
GrillMouster said:
Go to recovery, wipe cache, making sure to give it a full hour to finish. Then reboot. You'll probably still be on 5.0.1.
Click to expand...
Click to collapse
I am having the same problem. I tried wiping the cache from recovery as well as doing a full reset, and still stuck. HTC is suggesting sending them the device.
FWIW, I am locked/unrooted and running stock.
Have the same problem. Recovery said, that update has been installed, errors reported on tzdata read.
Additional problem: bougth from Amazon and use at russia… Delivery cost is ~insane.
penguinolog said:
Have the same problem. Recovery said, that update has been installed, errors reported on tzdata read.
Additional problem: bougth from Amazon and use at russia… Delivery cost is ~insane.
Click to expand...
Click to collapse
Were you able to fix it? I'm having the same problem, I just can't believe it's not possible to unlock the bootloader any other way.
if im stock 5.01 and i try to do an OTA update to 5.1.1, will that make a bootloop? or its only via 'bad flashing' in adb that causes loop?
i don't want to void my warranty untill im sure im going to keep my n9 LTE
thx
cobyman7035 said:
if im stock 5.01 and i try to do an OTA update to 5.1.1, will that make a bootloop? or its only via 'bad flashing' in adb that causes loop?
i don't want to void my warranty untill im sure im going to keep my n9 LTE
thx
Click to expand...
Click to collapse
It appears from feedback from other users, that sometimes the OTA can just "go wrong". So it's best to unlock your bootloader prior to installing the OTA. That way, if something does go wrong, you can easily recover from it.
cam30era said:
It appears from feedback from other users, that sometimes the OTA can just "go wrong". So it's best to unlock your bootloader prior to installing the OTA. That way, if something does go wrong, you can easily recover from it.
Click to expand...
Click to collapse
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
cobyman7035 said:
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
Click to expand...
Click to collapse
That's good news. Glad to hear it.
cobyman7035 said:
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
Click to expand...
Click to collapse
Simply switching "Enable OEM unlock" doesn't void your warranty, and it covers your butt in case something happens.
Hello everyone:
So that everyone will have a crystal clear status:
Got answer (email) from Xiaomi for warranty question with bootloader unlock AND rooting:
"...With respect to your concern, I would like to inform you that rooting of your device does not affect the warranty. However, the warranty may vary from seller to seller so would request you to coordinate with the respective point of purchase."
Hope that helps many of you
Edit:
Even if you are flashing custom roms, your warranty is NOT void:
https://www.bintooshoots.com/xiaomi-phone-warranty-when-rooted-custom-rom-or-unlocked-bootloader/
Best to attach the screenshot
ronald_loulan said:
Best to attach the screenshot
Click to expand...
Click to collapse
Sure, here it is
I'm guessing it'll be the same answer if the device is purchased from an official Xiaomi store? I never got around to asking my local dealer unfortunately.
It shouldn't matter if the company that supplies the phone is OK with it..
Essentially you return the phone to the reseller and they then forward it on to Xiaomi for repairs/replacement...
The answer they have given is a cop out to make it sound like they are developer friendly but then stand behind the immunity of the reseller's refusal....
ultramag69 said:
It shouldn't matter if the company that supplies the phone is OK with it..
Essentially you return the phone to the reseller and they then forward it on to Xiaomi for repairs/replacement...
The answer they have given is a cop out to make it sound like they are developer friendly but then stand behind the immunity of the reseller's refusal....
Click to expand...
Click to collapse
Don't think they mean that, it may be legal parlance for saying as long as u buy from an official reseller we will provide warranty.
And no we don't return the product to the reseller but always approach a service centre for warranty with a valid proof of purchase.
from my experience in the past, rooting or ubl doesn't affect the warranty as long as the device warranty seal is not damaged or broken. Because I've claimed a warranty a long time ago, I did some mistake and my xiaomi device is heavily bricked so I return the device to service center for repairment. Lucky me, it got covered by the warranty. But yeah, "the warranty may vary from seller to seller so would request you to coordinate with the respective point of purchase".
but my advice, try to relock the bootloader, unroot and revert back to official rom if possible before you claim the warranty.
Guys, if I root my Poco F1, can I OTA update it after that?
GrecoNeoV said:
Guys, if I root my Poco F1, can I OTA update it after that?
Click to expand...
Click to collapse
i could be wrong on this, so hopefully someone more knowledgable will assist...
but, i believe you must remove root first, OTA update, then re-root
And what if we flash a custom rom??
THEN? There will be warranty or not?
GrecoNeoV said:
Guys, if I root my Poco F1, can I OTA update it after that?
Click to expand...
Click to collapse
No. You need to first unroot your device. But if you have flashed twrp or have played with System partition, then forget about OTA update. You need to first flash fastboot rom through MiFlash tool.
Srijan007 said:
And what if we flash a custom rom??
THEN? There will be warranty or not?
Click to expand...
Click to collapse
If you flash back to miui using mi flash tool, locking device again, they'll not know anyway
GrecoNeoV said:
Guys, if I root my Poco F1, can I OTA update it after that?
Click to expand...
Click to collapse
Depends on the TWRP you used if it has features to support OTA Update, like the Batik TWRP for Pocophone, or OrangeFox.
I use Magisk for rooting. I prefer to download the OTA update file, then go to TWRP and flash it myself. I first wipe the Dalvik-cache and cache before flashing, just to be clean. After flashing, I am still in TWRP. I wipe the Dalvik cache and cache again, I am overkill here. I then flash Magisk again, since the OTA update would have removed it. Then reboot, and all ok, like nothing happened except that the OTA has been applied.
hyborian said:
Depends on the TWRP you used if it has features to support OTA Update, like the Batik TWRP for Pocophone, or OrangeFox.
I use Magisk for rooting. I prefer to download the OTA update file, then go to TWRP and flash it myself. I first wipe the Dalvik-cache and cache before flashing, just to be clean. After flashing, I am still in TWRP. I wipe the Dalvik cache and cache again, I am overkill here. I then flash Magisk again, since the OTA update would have removed it. Then reboot, and all ok, like nothing happened except that the OTA has been applied.
Click to expand...
Click to collapse
When you say that you 'prefer to download the OTA update file', do you mean the smaller OTA update file or the full ROM? If you mean the smaller file, does it get downloaded even after finding that you have rooted and are with TWRP?
tnsmani said:
When you say that you 'prefer to download the OTA update file', do you mean the smaller OTA update file or the full ROM? If you mean the smaller file, does it get downloaded even after finding that you have rooted and are with TWRP?
Click to expand...
Click to collapse
Oh, to clarify, I download the full one. That's what always appears anyway when Xiaomi pushes an update to my phone, the full one.
I use apps2Sd pro to link some apps to the SD card. If I let the phone automatically update the ota, it does so, then root is removed, and then it is rebooted back to the system. Since root was removed, all root apps don't work and apps2Sd pro cannot show the apps that were linked and I have to root it and reboot again, then remount SD card.
By doing it manually, I update ota and root and flash whatever needs to be flashed while in recovery all in one go, it's just simpler for me, YMMV.
P.s. I always do a nandroid backup too, I forgot to mention. All done with the above in one session of recovery.
CM-Tester said:
Hello everyone:
So that everyone will have a crystal clear status:
Got answer (email) from Xiaomi for warranty question with bootloader unlock AND rooting:
"...With respect to your concern, I would like to inform you that rooting of your device does not affect the warranty. However, the warranty may vary from seller to seller so would request you to coordinate with the respective point of purchase."
Hope that helps many of you
Click to expand...
Click to collapse
who cares for warranty if u broke screen u not gonna get free replacement.... and if u brick it u can fix it if u r tech guy if u cant u shouldnt have tried that far.... else there is no nee of warranty..... its not that the screen will pop out automatically.... i may ignorant of facts and some severe situations..... u can educate me .... in this and if i m being rude i m sorry peace
OP with new imformations completed:
unlock bootloader, root AND custom rom will NOT void your warranty!!!
Srijan007 said:
And what if we flash a custom rom??
THEN? There will be warranty or not?
Click to expand...
Click to collapse
Even with flashing custom roms, warranty is NOT void.
Have a look at my updated OP
[email protected] said:
who cares for warranty if u broke screen u not gonna get free replacement.... and if u brick it u can fix it if u r tech guy if u cant u shouldnt have tried that far.... else there is no nee of warranty..... its not that the screen will pop out automatically.... i may ignorant of facts and some severe situations..... u can educate me .... in this and if i m being rude i m sorry peace
Click to expand...
Click to collapse
I know its a bit of a necro but this is so true in case of phones.
MOBO goes, no ones gonna know it was rooted.
Screen cracks, no warranty anyway.
Battery issues are hard to prove unless totally bonkers.
Whats left is buttons, mic/speaker and display anomalies like amoled yellow/purple tint. Most of these things wont happen in the warranty period anyway.
F-ed up situation is when a screen "pop out" and youre rooted on a phone that limits root in warranty. Happened to me on Samsung S3. After minor drop, ~20cm onto shaggy carpet, screen just turned off, no crack but no picture either. Warranty was rejected cuz of root.