Hello fellow XDA users ,
I have a nexus 5x which is running Pixelrom , i am trying to find how to go back to dead stock as of performance issues ( when compared to another nexus 5x the difference is mind boggling )
As you probably know , these devices have bootloop problems so i would like to perform the perfect return to stock if possible to avoid bootloop problems as this is my daily driver
Any help is appreciated, any tips or stock files that are usefool for me to flash my way back to stock
Information will be given if asked so do not hesitate to ask in exchange for help <3
lyonschembri said:
Hello fellow XDA users ,
I have a nexus 5x which is running Pixelrom , i am trying to find how to go back to dead stock as of performance issues ( when compared to another nexus 5x the difference is mind boggling )
As you probably know , these devices have bootloop problems so i would like to perform the perfect return to stock if possible to avoid bootloop problems as this is my daily driver
Any help is appreciated, any tips or stock files that are usefool for me to flash my way back to stock
Information will be given if asked so do not hesitate to ask in exchange for help <3
Click to expand...
Click to collapse
Hi,
Since its a nexus device this is pretty easy. All you have to do is flash the stock factory image and lock the bootloader
A guide can be found here from xda
https://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
The factory images are here (Nexus 5x is bullhead)
https://developers.google.com/android/images
Seeing that you have a custom rom, you have already unlocked the bootloader and presumably have ADB and fastboot installed on your PC
I would recommend following the guide on the google link above. Alternatively you can leave the bootloader unlocked in case you want to flash a custom ROM again
:/
poondog said:
Hi,
Since its a nexus device this is pretty easy. All you have to do is flash the stock factory image and lock the bootloader
A guide can be found here from xda
https://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
The factory images are here (Nexus 5x is bullhead)
https://developers.google.com/android/images
Seeing that you have a custom rom, you have already unlocked the bootloader and presumably have ADB and fastboot installed on your PC
I would recommend following the guide on the google link above. Alternatively you can leave the bootloader unlocked in case you want to flash a custom ROM again
Click to expand...
Click to collapse
sadly , i have done all the necessary steps and to no success... The guide i followed somehow wasn`t the same case i was in, meaning that i , even though i had downloaded everything step by step as provided , the outcome was not the same. My .bat prompted the cmd and had loads of errors for files missing.
Any way on how i can fix this ?
https://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
Follow method 2.
The flash all scripts didn't work for me either. Just extract the images and flash them individually.
Back up your stuff as this will wipe everything!
tory13579 said:
https://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
Follow method 2.
The flash all scripts didn't work for me either. Just extract the images and flash them individually.
Back up your stuff as this will wipe everything!
Click to expand...
Click to collapse
literally have 2 missing files from the shown screen shot , these being userdata and cache
: https://imgur.com/a/wM9E7
lyonschembri said:
literally have 2 missing files from the shown screen shot , these being userdata and cache
: https://imgur.com/a/wM9E7
Click to expand...
Click to collapse
Google stopped including cache and userdata images for 7.1.2 and newer.
Sent from my Nexus 5X using Tapatalk
https://imgur.com/a/KyBv6
now this and it has no system image , meaning it went into brick ... nice
lyonschembri said:
https://imgur.com/a/KyBv6
now this and it has no system image , meaning it went into brick ... nice
Click to expand...
Click to collapse
You wrote "fastboot flash .\system.img" which is not a command. You have to specify the partition to be flashed. I don't use Windows, but the proper command is:
fastboot flash system \path\to\system.img
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You wrote "fastboot flash .\system.img" which is not a command. You have to specify the partition to be flashed. I don't use Windows, but the proper command is:
fastboot flash system \path\to\system.img
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
so dumb sorry for wasting your time man but thanks
How's this going?
Have you experienced the boot loop on your device? If so, first check to see if you are covered by warranty. Call LG, they will confirm.
If you are unsure if you boot loop, test with a factory image
https://developers.google.com/android/images and get 8.1 for Nexus 5x specifically https://dl.google.com/dl/android/aosp/bullhead-opm1.171019.011-factory-3be6fd1c.zip
This should have a flash-all.bat. this will wipe your device and return it to stock.
lock your bootloader
If it boots, congratulations you have a stock Nexus 5x with access to all of the Google play apps including Netflix.
If it doesn't boot fulfill your RMA with LG if still applicable. Otherwise, continue to the BLOD fix laid out here
https://forum.xda-developers.com/nexus-5x/general/nexus-5x-bootloop-death-blod-andorid-t3683926
In summary the BLOD fix
Unlock your bootloader, install TWRP, flash the boot.img from the BLOD page, boot into TWRP, sideload the elementalX tweaks zip, and you'll be up and running.
If you do experience the BLOD, it suggests the largest of your cores have fallen to hardware failure, as have most of ours. You will experience significant performance reductions as you're left without your 2 main processing cores. LG is well aware of this issue, and they have guidelines set to help for free (in my case, no obvious physical/water damage and covered by the extended warranty-- which I believe came about after a class action lawsuit)
Good luck,
And have fun with it
Related
I'm new to the forums and I've been searching and reading all over for help. This was my first time rooting. I was trying to flash a rom in TWRP and somehow erased everything, no OS or anything. Now when I boot up it only says google. It won't load past that. I can get into the fastboot screen but the adb options don't work. And now since trying two different tool kits to flash to stock image, I can't get on TWRP anymore. Any help would be great thanks. I'm not even sure what I did but I can try to add more information. Thanks
You can boot in fastboot and flash it back to stock.
I see Google hasn't posted the factory images out there yet, your tablet is fixable, but you need the image. Maybe someone else can chime in with a image I haven't found yet. BTW, you can fastboot flash the recovery if its a .IMG file to get that back.
Note: you'll need the android SDK because you'll need the fastboot drivers and the fastboot.exe program to flash back.
Sent from my Nexus 7 FHD using Tapatalk 2
trssho91 said:
Can you boot into fastboot mode by holding all three buttons for 5 seconds with the device off? It doesn't need a os or recovery just as long as you didn't kill the bootloader. Once in fastboot just flash it back to stock.
Download your image here: https://developers.google.com/android/nexus/images
Don't freak out yet, its hard to brick a nexus device
Edit, I just saw you said you can get fastboot. Use the link I posted to download your image, if you need the android SDK because you'll need the fastboot drivers and the fastboot.exe program to flash back.
Sent from my Nexus 7 FHD using Tapatalk 2
Click to expand...
Click to collapse
Obviously ADB would not work in fastboot. Erasing your ROM and recovery is no where near being bricked. You get into bootloader by holding Power + Volume down. Google has not released the official image package yet so flash the stock images from these -
http://forum.xda-developers.com/showthread.php?t=2381438
http://forum.xda-developers.com/showthread.php?t=2381582
I'll try this all out in the morning. It's getting late here. Thank you and I'll be back to give you all an update!
You could even skip flashing the stock recovery and reflash TWRP. Rename it "recovery.img" put it in platform-tools... Then:
fastboot flash recovery recovery.img
TWRP should be flashed. Install a stock deodex or odex ROM and wipe data before install. Should be good.
But, everyone else's solutions will also work too (ie you are NOT bricked )
Sent from my Nexus 4 using Tapatalk 4 Beta
I need help also im trying to restore with the images but its hanging when i get to the flash system part it just sits there and i dont have a system to bootup to if i wanted to what can i do ??
Okay i guess i just had to wait a lil bit longer its finally flashing the system
Sent from my Nexus 4 using Tapatalk 4 Beta
I think I'm having some problems trying to download things in the correct folders, seeing as I don't understand most of the lingo. I used a all in one tool to unlock the bootloader and root but when I tried putting things in the folder it wouldn't load properly. I deleted everything off of my pc and I'm going to redownload everything and try again.
Tried http://forum.xda-developers.com/showthread.php?t=2381582 early this morning and it wouldn't load properly. I ran it and it said ?????? fastboot and then said some files were missing. Let me get back at it though.
You're just gonna have to own up and install the SDK. It only takes a few commands once it's downloaded.
http://developer.android.com/sdk/index.html
Sent from my Nexus 4 using Tapatalk 4 Beta
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Geodude074 said:
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Click to expand...
Click to collapse
Yea thats correct zedomax made a zip on here that only has the files u need
Sent from my Nexus 7 using Tapatalk 4 Beta
Geodude074 said:
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Click to expand...
Click to collapse
+1 I didn't know somebody compiled that for the new N7. I was mostly trying to get this fellow to shy away from the toolkits - not that they're bad... But when they mess up, it's a headache to recover.
Sent from my Nexus 4 using Tapatalk 4 Beta
When I post on here I think its better to assume I'm posting to a noob rather assuming they know something they don't and making their situation more stressful. The SDK is a blanket install and you know everything is there. For someone inexperienced its better than: get this driver, and this one, and these files...move them here..you get the idea.
Sent from my SAMSUNG SGH-I747 running CyanogenMod.
Anisak said:
Tried http://forum.xda-developers.com/showthread.php?t=2381582 early this morning and it wouldn't load properly. I ran it and it said ?????? fastboot and then said some files were missing. Let me get back at it though.
Click to expand...
Click to collapse
The guide on that thread should work really well, but I will just point out that for me, ADB wasn't working (yet) while I was still trying to flash TWRP on it, so the 'ADB reboot bootloader' line in the "Recovery_Nexus7.bat" was pointless. In my case, I go to the bootloader/fastboot mode by holding the power button + volume down.
Once in fastboot/bootloader mode, ensure that fastboot can see your N7 2013 by typing 'fastboot devices'. If you see your device there, you are good to proceed with flashing all the files that are in that zip file. It even roots your device. Good luck and let me know if you need any further help.
zeppelin101 said:
The guide on that thread should work really well, but I will just point out that for me, ADB wasn't working (yet) while I was still trying to flash TWRP on it, so the 'ADB reboot bootloader' line in the "Recovery_Nexus7.bat" was pointless. In my case, I go to the bootloader/fastboot mode by holding the power button + volume down.
Once in fastboot/bootloader mode, ensure that fastboot can see your N7 2013 by typing 'fastboot devices'. If you see your device there, you are good to proceed with flashing all the files that are in that zip file. It even roots your device. Good luck and let me know if you need any further help.
Click to expand...
Click to collapse
Oh disregard my last comment. I got it to work! Thank you everyone for the help!
Anisak said:
When I type fastboot devices nothing comes up. And I can't seem to unlock or lock it now. (Was testing that command)
Click to expand...
Click to collapse
Are you logging in from your administrator account and is it windows 8 by any chance ?
Well, Rule is log into from your administrator account and windows 8 will need manual drivers installation for your Nexus 7 (2013). Try downloading USB drivers from SDK.
I am also attaching fastboot drivers which I hope will work
Good luck
Hnk1 said:
Are you logging in from your administrator account and is it windows 8 by any chance ?
Well, Rule is log into from your administrator account and windows 8 will need manual drivers installation for your Nexus 7 (2013). Try downloading USB drivers from SDK.
Good luck
Click to expand...
Click to collapse
I'm on windows 7 but I did read about something about being on admin and that did the trick. Before it wasn't letting me run anything and not warning me to do so either. But I got it! Thanks to everyone for the help and advice. :victory:
Unofficial F2FS-compatible TWRP for the Huawei Watch
Please note that to use this, your bootloader MUST be unlocked.
You can download the modified recovery image from here.
To flash this recovery, make sure that your watch is plugged into your PC, in fastboot mode, with all of the proper drivers installed (if applicable), then run the following command.
Code:
fastboot flash recovery twrp-f2fs-3.0.2-sturgeon.img
Now you should be able to reboot to TWRP recovery and use it like you would on a phone!
Sources:
Kernel source: https://github.com/r3pwn/android_kernel_huawei_sturgeon
Device tree source: https://github.com/r3pwn/android_device_huawei_sturgeon
Devs, please note that the device tree is designed to be built in a CM tree, not an Omni tree. If you are having some trouble getting TWRP into your CM tree, PM me and I'll help you out.
Below, you will find a link to an imgur album full of pictures I've taken of the watch in recovery mode, plus proof that this recovery has f2fs-compatibility.
http://imgur.com/a/UabPb
Wow nice. Flashing asap
Awesome. Been waiting for the 3.0.2 update. Thanks so much.
What are the benefits of f2fs on such a small device? The difference was noticeable on my Nexus 5 way back when... guess I should just try it out and see!
bigdave79 said:
Awesome. Been waiting for the 3.0.2 update. Thanks so much.
What are the benefits of f2fs on such a small device? The difference was noticeable on my Nexus 5 way back when... guess I should just try it out and see!
Click to expand...
Click to collapse
From what I've noticed, any lag that was there before is now gone completely, and eveything seems at least slightly smoother.
My phone gave repeated notifications that watch has disconnected, so I thought I would unpair and pair it. Watch decided to factory reset at Android side, which caused a TWRP boot loop. Ideas, other than flash_all in bootloader? Maybe there is a should-reset flag or similar indicator that Android sets that the recovery should unset?
So when I boot, watch goes to TWRP. No matter what partitions I wipe (excluding system), it will not boot to Android.
jkoljo said:
My phone gave repeated notifications that watch has disconnected, so I thought I would unpair and pair it. Watch decided to factory reset at Android side, which caused a TWRP boot loop. Ideas, other than flash_all in bootloader? Maybe there is a should-reset flag or similar indicator that Android sets that the recovery should unset?
So when I boot, watch goes to TWRP. No matter what partitions I wipe (excluding system), it will not boot to Android.
Click to expand...
Click to collapse
I had a same issue. I reflashed the rom
Sent from my Nexus 5 using XDA Labs
I flashed stock recovery, then rebooted watch and everything is ok. Flashed this TWRP back afterwards.
I don't fully understand the steps to take, but I want to try this because it looks really good.
do I have this right?
1 flash this twrp
2 wipe all partitions and internal storage
3 use this twrp to change all partitions to f2fs, or just data?
4 flash-all.bat the stock images provided by Google
could I flash skin1980's MM kernel afterwards?
thank you
pablo71 said:
I don't fully understand the steps to take, but I want to try this because it looks really good.
do I have this right?
1 flash this twrp
2 wipe all partitions and internal storage
3 use this twrp to change all partitions to f2fs, or just data?
4 flash-all.bat the stock images provided by Google
could I flash skin1980's MM kernel afterwards?
thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/hua...rnel-jpark-kernel-huawei-watch-t3394967/page1
flash N preview
flash kernel flash recovery
boot in to recovery and use the instructions
Sent from my Nexus 5 using XDA Labs
acultr said:
http://forum.xda-developers.com/hua...rnel-jpark-kernel-huawei-watch-t3394967/page1
flash N preview
flash kernel flash recovery
boot in to recovery and use the instructions
Sent from my Nexus 5 using XDA Labs
Click to expand...
Click to collapse
ahhh...for N preview ... I missed that part thanks
huawei Watch china...
Hi,
I bought this watch in China but it is not possible to use with Andr wear europe...
so I'd like to rom and so on... I did the same in the past with a Galaxy note...
the poitn with smartwatch I'm not expert so I don't know how to root and flash...the rom.
sorry to bother you...
thanks in advance,
Claudio
klaus ita said:
Hi,
I bought this watch in China but it is not possible to use with Andr wear europe...
so I'd like to rom and so on... I did the same in the past with a Galaxy note...
the poitn with smartwatch I'm not expert so I don't know how to root and flash...the rom.
sorry to bother you...
thanks in advance,
Claudio
Click to expand...
Click to collapse
This is TWRP recovery, not a ROM. Not sure where to point you as I don't know if watches are exactly the same across countries. There might be a good chance they are all similar, if so u can ask around in the general forums. There's also a developer preview of N with a return to MM link. But you should search around some more b4 doing anything.
Sent from my LG-H901 using XDA-Developers mobile app
klaus ita said:
Hi,
I bought this watch in China but it is not possible to use with Andr wear europe...
so I'd like to rom and so on... I did the same in the past with a Galaxy note...
the poitn with smartwatch I'm not expert so I don't know how to root and flash...the rom.
sorry to bother you...
thanks in advance,
Claudio
Click to expand...
Click to collapse
In the Huawei Watch main forum
http://forum.xda-developers.com/huawei-watch/general/tutorial-complete-guide-how-to-flash-t3307137
I successfully flashed TWRP but cannot mount data. what step did I missed?
---
edit: I reboot the recovery and seems everything is okay
r3pwn said:
Below, you will find a link to an imgur album full of pictures I've taken of the watch in recovery mode, plus proof that this recovery has f2fs-compatibility.
http://imgur.com/a/UabPb
Click to expand...
Click to collapse
Thanks for the recovery! It's all running great and I had no issues installing it. My only issue is I can't figure out how to enable the f2fs file system. I looked at your pictures you posted but I can't find it. Any help would be appreciated. Thanks
I'm on the sturgeon-nvd83h-wear-2.0-preview-2 Build with the Negalite HW+ Kernel
Nvm, I just found your guide in another thread http://forum.xda-developers.com/hua...awei-watch-t3394967/post67266669#post67266669
Going to go and try this now. Thanks again.
Hi, could I request an option to set (increase) the font size? Or can I edit a file in TWRP on my own? Thanks!
--
Edit, I found /twres/ui.xml but changing these numbers doesn't seem to be doing anything. Any ideas?
In particular, I'd like to adjust the font for the file list when selecting a zip to install.
Can I Downgrade Nexus 5x from Android 7.0 to Marshmallow 6.0.1 ?
I Heard users report bricked device by doing so, is that true?
I really want to downgrade because this **** Nougat is soo buggy, Setting Apps crashed and all social media apps lags and sometime irresponsive.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
check this if you want to return to previous version of android
zocex said:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
check this if you want to return to previous version of android
Click to expand...
Click to collapse
with reference to exact same post I said the users report brick device while downgrading.. I want to have more opinions about this issue if anyone tried doing so. Thanks
hasankhan222 said:
with reference to exact same post I said the users report brick device while downgrading.. I want to have more opinions about this issue if anyone tried doing so. Thanks
Click to expand...
Click to collapse
Here is what I did b/c Android N and the lack of notifications blows.
1) I got the Factory images from the normal place.
2) Extracted boot.img, system.img, and vendor.img
3) placed those on the root of my device
4) Booted into TWRP and Wiped everything except internal memory card
5) In TWRP apply those img files
6) booted as normal
7) Booted back into bootloader and flash twrp again ( yes it will wipe it )
8) reboot bootloader using keys, re-flash twrp
9) Boot into TWRP apply whatever you need to apply OR just boot as normal
carm01 said:
Here is what I did b/c Android N and the lack of notifications blows.
1) I got the Factory images from the normal place.
2) Extracted boot.img, system.img, and vendor.img
3) placed those on the root of my device
4) Booted into TWRP and apply those img files
5) Wiped everything except internal memory card
6) booted as normal
7) Booted back into bootloader and flash twrp again ( yes it will wipe it )
8) reboot bootloader using keys, re-flash twrp
9) Boot into TWRP apply whatever you need to apply OR just boot as normal
Click to expand...
Click to collapse
Thanks Sir for your detailed go through but I want to be on stock firmware + settings with no root or TWRP.
I want to do it by fastboot way if there will be no chance then will try this method maybe in future.
hasankhan222 said:
Thanks Sir for your detailed go through but I want to be on stock firmware + settings with no root or TWRP.
I want to do it by fastboot way if there will be no chance then will try this method maybe in future.
Click to expand...
Click to collapse
So your bootloader is locked and no root and you want to downgrade from 7.0 to 6.0.1 ?
carm01 said:
Here is what I did b/c Android N and the lack of notifications blows.
1) I got the Factory images from the normal place.
2) Extracted boot.img, system.img, and vendor.img
3) placed those on the root of my device
4) Booted into TWRP and apply those img files
5) Wiped everything except internal memory card
6) booted as normal
7) Booted back into bootloader and flash twrp again ( yes it will wipe it )
8) reboot bootloader using keys, re-flash twrp
9) Boot into TWRP apply whatever you need to apply OR just boot as normal
Click to expand...
Click to collapse
Did you push the files using /adb?
carm01 said:
So your bootloader is locked and no root and you want to downgrade from 7.0 to 6.0.1 ?
Click to expand...
Click to collapse
Yes... eventually i will unlock bootloader while flashing .imgs but is it safe to downgrade from 7.0 to 6.0.1..? I heard some ppl end up with bricked devices
hasankhan222 said:
Yes... eventually i will unlock bootloader while flashing .imgs but is it safe to downgrade from 7.0 to 6.0.1..? I heard some ppl end up with bricked devices
Click to expand...
Click to collapse
My bootloader is unlocked, and in past experiences ( with HTC devices ) I always thought that your bootloader has to be unlocked to go backwards.
Personally, I would not go backwards without unlocking the bootloader; but that's just me and my experiences.
Yeah you always want an Unlocker bootloader. You gain nothing by having it locked. I went back to 6.0.1 just using flashall and now I'm back to 7.0.0 with also just flash all. No issue on my side.
Sent from my Nexus 5X using Tapatalk
milan187 said:
Yeah you always want an Unlocker bootloader. You gain nothing by having it locked. I went back to 6.0.1 just using flashall and now I'm back to 7.0.0 with also just flash all. No issue on my side.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Out of curiosity, are you complete stock with encryption intact? I'm wondering why the 5X has fewer troubles moving between 7.0 and 6.0.1 but the 6P has a lot if issues with that.
Sent from my Nexus 5X using Tapatalk
milan187 said:
Yeah you always want an Unlocker bootloader. You gain nothing by having it locked. I went back to 6.0.1 just using flashall and now I'm back to 7.0.0 with also just flash all. No issue on my side.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
@milan187
How are your experiences with notifications; meaning lack of notifications aside from calls and text? i have had horrible issues with lack of notifications
carm01 said:
@milan187
How are your experiences with notifications; meaning lack of notifications aside from calls and text? i have had horrible issues with lack of notifications
Click to expand...
Click to collapse
I have no idea what issue you had but all my notifications work just the same as with M. All show up just fine. It's actually better to me.
Did you do a clean factory load? May want to try that?
I just got notified via tapatalk about your message.
Sent from my Nexus 5X using Tapatalk
i was on chroma, flashed dp5 directly,update ota to final nougat. phone works ok. then flash from 7 to factory image MTC20F,phone works ok. then update again to 7 with no problems at all. botloader was unlocked all time. i was just curious is there difference between update to 7 from dp5 and from 6.0.1. when i done it there was no nougat images to factory images site. u unpacked image and execute flash all command
only problem i have is twrp set to stick,and titanium backeup(when i delete some system apk and do clean dalvik,phone cant boot) i think this is problem with tb bcouse apk dalvik on nougat is not at same place as in mm
????
What problems do you have to return to any version of Android? You just have to flash the images (including radio and bootloader from that old version, and the rest of partitions).
To be honest, I am not even sure if returning to old bootloader/radio is even necessary.. I never needed doing that
milan187 said:
I have no idea what issue you had but all my notifications work just the same as with M. All show up just fine. It's actually better to me.
Did you do a clean factory load? May want to try that?
I just got notified via tapatalk about your message.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Let me elaborate: Phone unplugged, and after it is left alone , not touched for an hour or so, do you get notification alerts from Gmail, and any other app you installed?
I wiped everything except internal Sd card, so system, vendor, cache, app data, boot.
All my notifications except text and calls are suppressed after the phone is not touched for some time and unplugged.
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
RusherDude said:
????
What problems do you have to return to any version of Android? You just have to flash the images (including radio and bootloader from that old version, and the rest of partitions).
To be honest, I am not even sure if returning to old bootloader/radio is even necessary.. I never needed doing that
Click to expand...
Click to collapse
I left the N radio and Bootloader in tact after returning to 6.0.1, no issues
carm01 said:
Let me elaborate: Phone unplugged, and after it is left alone , not touched for an hour or so, do you get notification alerts from Gmail, and any other app you installed?
I wiped everything except internal Sd card, so system, vendor, cache, app data, boot.
All my notifications except text and calls are suppressed after the phone is not touched for some time and unplugged.
---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------
I returned to 6.0.1 and left the N radio and bootloader, no issues
Click to expand...
Click to collapse
They all come in but to be honest I keep my phone on Priority and phone calls only make sound. Everything else comes in and blinks led. That's the way I use all my devices. If it's just the sound that did not work for you I can test it for a few hours to make sure they come in.
Sent from my Nexus 5X using Tapatalk
Here's my fix:
1. Moved Nandroid backup to PC.
2. Download factory image MTC20F from https://developers.google.com/android/nexus/images.
3. Install factory image (This will erase all data on your phone so move your files to your PC).
4. Install TWRP 3.0.2-0 from https://dl.twrp.me/bullhead/twrp-3.0...lhead.img.html via fastboot.
5. Go in TWRP>Wipe>Advanced Wipe and repair all partitions that can be repaired (System, Data, Cache).
6. Restore Nandroid backup.
7. Success.
milan187 said:
They all come in but to be honest I keep my phone on Priority and phone calls only make sound. Everything else comes in and blinks led. That's the way I use all my devices. If it's just the sound that did not work for you I can test it for a few hours to make sure they come in.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for your info Sir, Can I just wipe my device and unlock the bootloader and flash 6.0.1 (MTC20F) images with fastboot including Radio and Bootloader?
hasankhan222 said:
Thanks for your info Sir, Can I just wipe my device and unlock the bootloader and flash 6.0.1 (MTC20F) images with fastboot including Radio and Bootloader?
Click to expand...
Click to collapse
That's what I did though I'm back on N now. Unlocking your bootloader will wipe the device as far as I remember.
Sent from my Nexus 5X using Tapatalk
Hi Friends
pleas help , i wanted install Oreo so i went to lock boat-loader by TOOL_ALL_IN_ONE
and i didnt see the alert message and above message appeared "Your device is corrupt. It can't be trusted and will not boot"
so please advise
If you alter the system in any way you can't lock the bootloader as it will not boot due to possible safety issues by modying the system. In order to use the device with a locked bootloader, you need to flash the original OS.
If you want to use a modified system, keep the bootloader unlocked. Unfortunately, there is no other way.
how can i flash rom please help
MsuatafaKhatab said:
how can i flash rom please help
Click to expand...
Click to collapse
It would be helpful to know what you want to flash.
Is it OxygenOS?
Then flash it in e.g. TWRP and then lock the bootloader again.
Is it something else?
Keep the bootloader unlocked.
Macusercom said:
It would be helpful to know what you want to flash.
Is it OxygenOS?
Then flash it in e.g. TWRP and then lock the bootloader again.
Is it something else?
Keep the bootloader unlocked.
Click to expand...
Click to collapse
Is it OxygenOS?
yes it is
Did you modify it in any way? Root, Magisk, Xposed, Recovery, flashable ZIPs or anything else?
yes, the problem i used tool "TOOL_ALL_IN_ONE" to lock boat-loader
Use "fastboot flashing unlock" to unlock it again, install TWRP, use adb push to copy OxygenOS to it, flash OxygenOS, use "fastboot flashing lock" and it should work just fine again.
not allow to me to unlock again
https://imgur.com/a/fIYqZ
I assume this is due to "Allow OEM Unlock" not being enabled. I don't know if anyone has a workaround.
Otherwise, I suggest contacting OnePlus and getting support by an L2 technician.
Macusercom said:
I assume this is due to "Allow OEM Unlock" not being enabled. I don't know if anyone has a workaround.
Otherwise, I suggest contacting OnePlus and getting support by an L2 technician.
Click to expand...
Click to collapse
Thanks pro
I contacted them and they gave file to downlod and will log in to my pc tommorrow to fix
Really appreciate your help
Sent from my LG-H870S using Tapatalk
MsuatafaKhatab said:
Thanks pro
I contacted them and they gave file to downlod and will log in to my pc tommorrow to fix
Really appreciate your help
Sent from my LG-H870S using Tapatalk
Click to expand...
Click to collapse
thanks pro , the session finished with succeed thanks
but why the delete the files after finish installation
MsuatafaKhatab said:
thanks pro , the session finished with succeed thanks
but why the delete the files after finish installation
Click to expand...
Click to collapse
They keep their tools private. So unless you back them up during the session in the background and use a keylogger to get the password, you will never get your hands on the tools. No one does.
But you can contact them again at any time and they will assist you so just don't do this again and you should be fine
this could be avoided if we had fastboot images of OxygenOS..
you can flash any image from fastboot, even if it's locked.
Seven_of_Nine24 said:
this could be avoided if we had fastboot images of OxygenOS..
you can flash any image from fastboot, even if it's locked.
Click to expand...
Click to collapse
How bro
I already fixed by one plus technical support , but to learn
Sent from my ONEPLUS A5010 using Tapatalk
I didn't do anything in my phone n still I got the device is corrupt.
Tejesh.D said:
I didn't do anything in my phone n still I got the device is corrupt.
Click to expand...
Click to collapse
Open ticket in one plus website
They will fix by logging to your PC
Don't worry
They are very friendly
Sent from my ONEPLUS A5010 using Tapatalk
MsuatafaKhatab said:
Open ticket in one plus website
They will fix by logging to your PC
Don't worry
They are very friendly
Click to expand...
Click to collapse
It's working now....but still ll open a ticket
I also faced similar problem yesterday & following steps worked for me
1. I unlocked the bootloader
2. Flashed TWRP & wiped everything (system data cache, internal) I wiped internal because I was seeing random folders in my internal, you can skip it while trying first time but if it doesn't work. Try again with wiping internal.
3.I flashed stock recovery via fastboot.
4. ADB side loaded oxygen OS (any version) using stock recovery.
I side loaded rom because I was unable to select file from stock recovery option "install from internal"
*don't boot now*
5. Reset everything from stock recovery option and then boot it.
I haven't tried to lock bootloader again but it should lock if you try now without rooting it again (⅛)
(⅛) I think the problem was that I mistakenly tried to lock bootloader with magisk installed which made this issue.
(That's what I was able to notice)
Please report back if this was the case for you too.
Sent from my ONEPLUS A5010 using Tapatalk
Try this
https://r.tapatalk.com/shareLink?ur...share_tid=3733012&share_fid=3793&share_type=t
Sumanyu Sinha said:
I also faced similar problem yesterday & following steps worked for me
1. I unlocked the bootloader
2. Flashed TWRP & wiped everything (system data cache, internal) I wiped internal because I was seeing random folders in my internal, you can skip it while trying first time but if it doesn't work. Try again with wiping internal.
3.I flashed stock recovery via fastboot.
4. ADB side loaded oxygen OS (any version) using stock recovery.
I side loaded rom because I was unable to select file from stock recovery option "install from internal"
*don't boot now*
5. Reset everything from stock recovery option and then boot it.
I haven't tried to lock bootloader again but it should lock if you try now without rooting it again (⅛)
(⅛) I think the problem was that I mistakenly tried to lock bootloader with magisk installed which made this issue.
(That's what I was able to notice)
Please report back if this was the case for you too.
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Sent from my ONEPLUS A5010 using Tapatalk
Hello everyone,
Since I'm facing difficulties connecting my Nexus 5X to my PC (believe me, I have tried nearly everything), I was wondering if it is possible to flash Magisk to my phone without the use of a PC. The bootloader is still unlocked because i've rooted my phone previously (when it still could connect to my PC). All the possibilities I ran into require either root or a PC.
I hope one of you guys knows a way how to handle this without losing all my data.
Thanks in advance!
Assuming you don't have a custom recovery installed either?? What's the "difficulty with trying to hook to a PC?
No, I don't have a custom recovery installed. There are more people facing this problem: https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4. Solution is not working for me for some reason.
To install magisk you need a custom recovery. And to install a custom recovery you need a pc.
Sent from my [device_name] using XDA-Developers Legacy app
I was afraid of that. Maybe i'll go with a factory reset then. Thanks tot the help anyways.
jd1639 said:
To install magisk you need a custom recovery. And to install a custom recovery you need a pc.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
_Hitman47 said:
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
Click to expand...
Click to collapse
So..... The bottom line is..... You still need a PC.
_Hitman47 said:
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
Click to expand...
Click to collapse
You're right. You can flash a boot image with fastboot. Is there a boot image that has magisk as party of it?
Well, I have installed Magisk Manager, and it gives me the option to patch a boot image-file. When I choose this option it askes me to select te original boot image-dump (.img or .img.tar). Since I'm no expert and I don't know where to find this and what this does, I'm afraid of losing my data or bricking my phone.
bluesh4rk said:
Well, I have installed Magisk Manager, and it gives me the option to patch a boot image-file. When I choose this option it askes me to select te original boot image-dump (.img or .img.tar). Since I'm no expert and I don't know where to find this and what this does, I'm afraid of losing my data or bricking my phone.
Click to expand...
Click to collapse
You would use the boot.img from the factory image that your rom is based on. Find your device below and download the 1 GB zip. Inside this zip is another zip you'll need to open to find the boot image (boot.img). Flashing boot images doesn't wipe internal storage, but it does remove root if you had it installed.
Factory images:
https://developers.google.com/android/images?hl=en
There's not really a collection of stock boot images besides what's included in the factory image.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You would use the boot.img from the factory image that your rom is based on. Find your device below and download the 1 GB zip. Inside this zip is another zip you'll need to open to find the boot image (boot.img). Flashing boot images doesn't wipe internal storage, but it does remove root if you had it installed.
Factory images:
https://developers.google.com/android/images?hl=en
There's not really a collection of stock boot images besides what's included in the factory image.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Instead of downloading the entire ROM, you might find what you need here: https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169
bluesh4rk said:
Hello everyone,
Since I'm facing difficulties connecting my Nexus 5X to my PC (believe me, I have tried nearly everything), I was wondering if it is possible to flash Magisk to my phone without the use of a PC. The bootloader is still unlocked because i've rooted my phone previously (when it still could connect to my PC). All the possibilities I ran into require either root or a PC.
I hope one of you guys knows a way how to handle this without losing all my data.
Thanks in advance!
Click to expand...
Click to collapse
Hello there ,
I have same as your issue.
My pixel 2 xl non rooted with unlocked bootloader.
So, Is it possible to flash latest OTA update directly through the phone via stock recovery?
As you aware that with the known and common pixel 2 xl issue which you can't get it connected to PC.
I'm stuck on October update and I'd be glad if someone could help me out on this matter.
Hi I'm new to rooting. I have a ZTE n9137 tempo x looking to root .I can't get this done.no recovery no boot.img no custom recovery none what so ever .the olny I keep reading is that I have to have a PC I don't like I said I'm new to root but I'm trying anything to get this done I unlocked the oem but I don't thing that it is enabled.?.?and I don't think that the phone can do this ota so now what ?? If I'm wrong plzz tell me where at I'm wrong and how to gain root thanks for all the help
Update not got root
hi everybody i wanted to root a samsung a3 2018(idk what version it is because it is still my grandma's phone) and as i know there isn't any twrp version for that phone