Hi,
I have big problem, I was trying to update my OP6 to Android 10 beta and phone can't turn on, only spin round on logo and can't go further. I'm on stock, no root. Please advise what can I do ? I can't lost my data.
How did you update? Share the instructions?
vs4vijay said:
How did you update? Share the instructions?
Click to expand...
Click to collapse
by OTA.
gianni_zambrotta said:
Hi,
I have big problem, I was trying to update my OP6 to Android 10 beta and phone can't turn on, only spin round on logo and can't go further. I'm on stock, no root. Please advise what can I do ? I can't lost my data.
Click to expand...
Click to collapse
You didn't backup your data like everyone advised including OnePlus themselves?
From the looks of your situation, no, you can't fix your phone without losing data.
remewer said:
You didn't backup your data like everyone as advised including OnePlus themselves?
From the looks of your situation, no, you can't fix your phone without losing data.
Click to expand...
Click to collapse
I haven't got any of case like this that update by OTA can do bootloop on normal stock. That's strange. What is your advise in that case ?
gianni_zambrotta said:
I haven't got any of case like this that update by OTA can do bootloop on normal stock. That's strange. What is your advise in that case ?
Click to expand...
Click to collapse
Yeah, sure. But this is a different case. This is a major update, not to mention it's a beta. Anyway, you could try wiping your cache partition first. You can do that on recovery mode. This won't wipe your data.
If it doesn't work, I don't know any other solution to fix your device while keeping data. If you're ready to let go of your data, the easiest way to surely recover is using MSM Download Tool.
EDIT: I just remembered there's no cache partition anymore. You'll need to wipe cache AND data. I can't check the stock recovery because I'm on TWRP myself.
gianni_zambrotta said:
Hi,
I have big problem, I was trying to update my OP6 to Android 10 beta and phone can't turn on, only spin round on logo and can't go further. I'm on stock, no root. Please advise what can I do ? I can't lost my data.
Click to expand...
Click to collapse
My wouldn't boot after updating a magisk module, I salvaged it by flashing stock boot img again, it's not the same situation but worth a shot.
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
As a last resort before wiping try changing the active partition from fastboot:
fastboot --set-active=a
fastboot --set-active=b
Good luck.
gianni_zambrotta said:
Hi,
I have big problem, I was trying to update my OP6 to Android 10 beta and phone can't turn on, only spin round on logo and can't go further. I'm on stock, no root. Please advise what can I do ? I can't lost my data.
Click to expand...
Click to collapse
your chances of keeping your data without a backup recovering from a bootloop is very slim. the simplest solution would be to wipe your data and cache from the stock recovery. If that doesn't work, you might have to go towards using the msm download tool to unbrick your oneplus 6. Here's the link to the thread with the msm download tool: https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Edit: Shoutout to r/xdacirclejerk for making me see this
Were you full stock or rooted? Were you using Swift installer?
Related
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:
Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...
Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.
No worries
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood
rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?
Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.
Yup. RMA
Sent from my Nexus 5 using Tapatalk
Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. Problem is, Odin gets stuck at cache.img, then fails after a couple of minutes. Phone then displays BSOD whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer, still doesn't work.
My first concern is not to lose any data as I didn't back anything up. Any help would be greatly appreciated. Feel free to ask about any missing info.
Thanks!
I see. It didn't say on the XDA thread it was only for Lollipop, but I checked in CF's website and you're right. I've wanted to update to LL ages ago but I didn't get it through OTA. The only LL release that's available for SM-N900 in SamMobile is Russian :/ I don't know if I should flash that one...
Would it be safe to flash back my stock 4.2.2 to at least get my phone back working? Or would the Russian release work for me (assuming it has language choice)?
Also, once I choose which ROM to use, would I loose my data when I flash it? I assume it is flashed the same way than root.
Thanks!
Hi, thank you for using XDA Assist. I assume you've seen this,http://forum.xda-developers.com/showthread.php?t=2466423. In regards to flashing a Rom you should always clear data, dalvic cache and cache before flashing. That will erase data so backup first. You should look into titanium backup on the play store.
jd1639 said:
Hi, thank you for using XDA Assist. I assume you've seen this,http://forum.xda-developers.com/showthread.php?t=2466423. In regards to flashing a Rom you should always clear data, dalvic cache and cache before flashing. That will erase data so backup first. You should look into titanium backup on the play store.
Click to expand...
Click to collapse
Yes, that is the thread I've used to flash the root. Now I have a BSOD phone and need to fix it without losing data :/ I didn't back up so I guess flashing ROM is out of the question. Any suggestions ?
GST_Diandre said:
Yes, that is the thread I've used to flash the root. Now I have a BSOD phone and need to fix it without losing data :/ I didn't back up so I guess flashing ROM is out of the question. Any suggestions ?
Click to expand...
Click to collapse
You're not going to like it, but you need to flash the stock firmware in Odin and lose your data. It's the only way to get your device working again.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're not going to like it, but you need to flash the stock firmware in Odin and lose your data. It's the only way to get your device working again.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I'm surprised. Can you at least explain why the root didn't work? I did everything as stated in the tutorial. I didn't expect a simple root operation would result in me losing everything on my phone; some data I cannot afford to lose.
Also, the phone says that using Kies in recovery mode is what should be done. Kies doesn't recognize the phone as needing repair. Any info?
Thanks !
GST_Diandre said:
I'm surprised. Can you at least explain why the root didn't work? I did everything as stated in the tutorial. I didn't expect a simple root operation would result in me losing everything on my phone; some data I cannot afford to lose.
Also, the phone says that using Kies in recovery mode is what should be done. Kies doesn't recognize the phone as needing repair. Any info?
Thanks !
Click to expand...
Click to collapse
Sorry, but live and learn. Always backup before doing any thing new on your phone. Especially rooting and flashing roms as they sometimes go wrong and rooting bypasses some of the safe guards the manufacture builds into the phone to avoid problems. Kies is crap. Learn to use Odin, if your rooting and roming you'll need it sooner or later. And you're at the sooner stage.
Edit, I'd really try asking your question here, http://forum.xda-developers.com/galaxy-note-3/help. I'm not sure on your device if you can go back to nb1, 4.4.4, firmware. I'm assuming there is no 5.x firmware for your device at this time. You can check at sammobile.com. But Samsung has updated the bootloader with each update and you have to flash the firmware with the same bootloader version. You can't go backwards.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Sorry, but live and learn. Always backup before doing any thing new on your phone. Especially rooting and flashing roms as they sometimes go wrong and rooting bypasses some of the safe guards the manufacture builds into the phone to avoid problems. Kies is crap. Learn to use Odin, if your rooting and roming you'll need it sooner or later. And you're at the sooner stage.
Edit, I'd really try asking your question here, http://forum.xda-developers.com/galaxy-note-3/help. I'm not sure on your device if you can go back to nb1, 4.4.4, firmware. I'm assuming there is no 5.x firmware for your device at this time. You can check at sammobile.com. But Samsung has updated the bootloader with each update and you have to flash the firmware with the same bootloader version. You can't go backwards.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I will, thank you. I can't afford losing anything as of now. Really hope there's a way of getting it to boot back up.
GST_Diandre said:
I will, thank you. I can't afford losing anything as of now. Really hope there's a way of getting it to boot back up.
Click to expand...
Click to collapse
SOLVED. I can't believe how easy it was. I was about to flash it over from scratch but then it struck me.
Chainfire ships Odin with all its root bundles, a version where you cannot untick "Auto Reboot". Because of Auto Reboot being ticked, Odin freezes at "cache.img". It might not freeze for some people but for me, having Auto Reboot activated causes the freeze
Downloading a different version of Odin (any version, I used 3.09) that allows changing parameters and LEAVING EVERYTHING UNTICKED BUT F. RESET TIME works like a charm.
Don't forget to reboot your phone after Odin displays PASS or RESET (Long press power).
I'm going to PM Chainfire about this, and tell a max of people about it.
Thank you for your support
EDIT: Also going to NANDroid my phone. I'm tired of panicking over failed roots
Hello guys, yesterday I sold my phone. Now im trying to factory reset my Oneplus one in the menu. But when I do that it reboots and gets in a TWRP bootloop. I already backedup my data on my new phone, so I just want to get rid of everything. When I reboot the phone nothing has changed and all my apps and data are still there. Anyone have an idea what I should do? Thanks in advance.
Iniesta89 said:
Hello guys, yesterday I sold my phone. Now im trying to factory reset my Oneplus one in the menu. But when I do that it reboots and gets in a TWRP bootloop. I already backedup my data on my new phone, so I just want to get rid of everything. When I reboot the phone nothing has changed and all my apps and data are still there. Anyone have an idea what I should do? Thanks in advance.
Click to expand...
Click to collapse
Simply boot into Recovery, tap Wipe and swipe to begin the process. Doing so will perform a regular Factory Reset.
Sent from my Nexus 4 using XDA Free mobile app
Iniesta89 said:
Hello guys, yesterday I sold my phone. Now im trying to factory reset my Oneplus one in the menu. But when I do that it reboots and gets in a TWRP bootloop. I already backedup my data on my new phone, so I just want to get rid of everything. When I reboot the phone nothing has changed and all my apps and data are still there. Anyone have an idea what I should do? Thanks in advance.
Click to expand...
Click to collapse
The best way to ensure that the device is ready for sale is by flashing the stock images with fastboot. See section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
The best way to ensure that the device is ready for sale is by flashing the stock images with fastboot. See section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Guys thanks for the tips . Whats the actual difference with sitins method? Cause that seem tot have worked.
Iniesta89 said:
Guys thanks for the tips . Whats the actual difference with sitins method? Cause that seem tot have worked.
Click to expand...
Click to collapse
Well the method that I suggested will ensure that the phone is back to a 100% stock state, exactly as it came out of the box.
Hey guys. I really messed up. I was running 7.1 from launch, and have had the systemless root basically since the beginning. I attempted to mount /system as /r/rw (for the stupidest reason) and my phone booted into a "no command" bootloop. Is there any hope for me? I can access recovery (I think). I can get into adb and fastboot and get the device recognized by the computer.
I will donate, buy coffee, anything for some love. Thank you so much for your time!
junkshot9112 said:
Hey guys. I really messed up. I was running 7.1 from launch, and have had the systemless root basically since the beginning. I attempted to mount /system as /r/rw (for the stupidest reason) and my phone booted into a "no command" bootloop. Is there any hope for me? I can access recovery (I think). I can get into adb and fastboot and get the device recognized by the computer.
I will donate, buy coffee, anything for some love. Thank you so much for your time!
Click to expand...
Click to collapse
Well if you have an unlocked bootloader you can simple flash the stock images.
NBreunig3 said:
Well if you have an unlocked bootloader you can simple flash the stock images.
Click to expand...
Click to collapse
Thank you so much for the reply. I think I could even do a factory reset from recovery, but I'm not sure. I'm pretty new at this. I was really hoping there may be a way I could backup my data first, or even fix the issue, as I'm pretty sure I know what happened. I think my permissions are set wrong, but I could be entirely wrong. I found this guide that sounds like my issue, but it is for a different device. I've tried adapting it to the best of my ability, but I can't get the phone in ADB mode from recovery. http://www.gizbeat.com/2103/how-to-change-file-permissions-through-adb/
Wouldn't hurt to try knowing you can also just flash stock images.
NBreunig3 said:
Wouldn't hurt to try knowing you can also just flash stock images.
Click to expand...
Click to collapse
Can you point me in the direction of someone who may be able to help me do just that? I've tried just about all I can think to do. I really am new at this and feel I am in over my head. I really appreciate any and all help and would gladly donate to this site or any individual user who is able to help me solve my problems (I hope it isn't against your rules to say things like that).
Thanks again.
This site straight from Google has all the files and instructions. https://developers.google.com/android/images
Follow directions but don't lock bootloader.
NBreunig3 said:
This site straight from Google has all the files and instructions. https://developers.google.com/android/images
Follow directions but don't lock bootloader.
Click to expand...
Click to collapse
Sorry, I was unclear, that was my fault. I believe I know how to flash stock images. That is something I have done since the OG Droid. I was asking if you may know anyone who may be able to help me attempt to backup my data, reset my permissions, or even get the phone into ADB mode before I resort to losing everything. Again, apologies for being unclear.
No worries. I would just look online and possibly post another thread here or just wait for replies.
Flash the stock image but remove the -w from the script to keep from losing data. Search around here for instructions. It's been described a zillion times.
cntryby429 said:
Flash the stock image but remove the -w from the script to keep from losing data. Search around here for instructions. It's been described a zillion times.
Click to expand...
Click to collapse
Is this what is referred to as a "dirty flash"?
junkshot9112 said:
Is this what is referred to as a "dirty flash"?
Click to expand...
Click to collapse
I suppose one could think of it that way but it really isn't. Everything other than data will be wiped and flashed. It'll all be new with the exception of your data partition. Removing the w allows you to keep all your apps and their settings in tact. The rest will all be new though. It can't hurt to try it. If it doesn't fix your problem (which it should) you can always run it again and wipe data along with everything else.
robocuff said:
I suppose one could think of it that way but it really isn't. Everything other than data will be wiped and flashed. It'll all be new with the exception of your data partition. Removing the w allows you to keep all your apps and their settings in tact. The rest will all be new though. It can't hurt to try it. If it doesn't fix your problem (which it should) you can always run it again and wipe data along with everything else.
Click to expand...
Click to collapse
I was successful. Thank you so much. What can I do for you to show thanks?
junkshot9112 said:
Is this what is referred to as a "dirty flash"?
Click to expand...
Click to collapse
Yes. But in reality it is not much different than taking an OTA. That never wipes data. I only clean flash if I am having issues after a dirty flash and I can't remember the last time that happened.
Sent from my Pixel XL using XDA Labs
junkshot9112 said:
I was successful. Thank you so much. What can I do for you to show thanks?
Click to expand...
Click to collapse
Your thanks is more than enough.?
I flashed TWRP and unlocked bootloader, I am on mha-l29c636b158. How can I return to completely stock? I want to receive updates via ota because I read that there is a new update to fix the touch screen not being responsive. Or is there a flashable stock zip update I can flash?
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page31
Jaimesco12 said:
I flashed TWRP and unlocked bootloader, I am on mha-l29c636b158. How can I return to completely stock? I want to receive updates via ota because I read that there is a new update to fix the touch screen not being responsive. Or is there a flashable stock zip update I can flash?
Click to expand...
Click to collapse
I spent that past two days rooting and flashing the one rom I could. Had to ignore some Chinese. I am USA 567B167. Got into trouble a number of times. This phone is funky compared to all the rooting I have done. I booted into erocovery, downloaded stock 2GB, wiped and was back to current stock without issue. It bootlooped if I didn't hard reset and wipe cache.
gm007 said:
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page31
Click to expand...
Click to collapse
Will I be able to receive otas?
rndchef said:
I spent that past two days rooting and flashing the one rom I could. Had to ignore some Chinese. I am USA 567B167. Got into trouble a number of times. This phone is funky compared to all the rooting I have done. I booted into erocovery, downloaded stock 2GB, wiped and was back to current stock without issue. It bootlooped if I didn't hard reset and wipe cache.
Click to expand...
Click to collapse
So you just booted to erecovery and from there it automatically downloaded the stock firmware?
You can return stock by use dload update.
Jaimesco12 said:
So you just booted to erecovery and from there it automatically downloaded the stock firmware?
Click to expand...
Click to collapse
yes. I did it twice. that is how many times I got into trouble and was the only solution. It worked great as it gives you the ability to log into wifi with a keyboard present to put in the password, then downloads the stock current rom and flashes it. You have to format data and wipe cache yourself.
Miss Wugfresh root tool. Get you out of any trouble.
It says getting package info failed in erecovery
rndchef said:
yes. I did it twice. that is how many times I got into trouble and was the only solution. It worked great as it gives you the ability to log into wifi with a keyboard present to put in the password, then downloads the stock current rom and flashes it. You have to format data and wipe cache yourself.
Miss Wugfresh root tool. Get you out of any trouble.
Click to expand...
Click to collapse
any ideas?
Jaimesco12 said:
any ideas?
Click to expand...
Click to collapse
Erecovery only work for Chinese firmware.
Use the guide above and yes you can receive ota.
I also received the same message. Getting into recovery was inconsistent for me even with TWRP. Sometimes it would do the auto downloaded and fail thing and other times it would go into TWRP. You need to get where you have three choices and pick erocovery and push the start button. This brings up the restore ability. Worked perfect on the USA model.
rndchef said:
I also received the same message. Getting into recovery was inconsistent for me even with TWRP. Sometimes it would do the auto downloaded and fail thing and other times it would go into TWRP. You need to get where you have three choices and pick erocovery and push the start button. This brings up the restore ability. Worked perfect on the USA model.
Click to expand...
Click to collapse
Do you say that you recovered your phone from erecovery? For usa model?
gm007 said:
Do you say that you recovered your phone from erecovery? For usa model?
Click to expand...
Click to collapse
Yes. Twice. Once to get off of HRT rom that was wonky and another to remove root because I lost Google apps. All accidents and was grateful to discover erecovery put me back on the current B167 version stock.
rndchef said:
Yes. Twice. Once to get off of HRT rom that was wonky and another to remove root because I lost Google apps. All accidents and was grateful to discover erecovery put me back on the current B167 version stock.
Click to expand...
Click to collapse
Are you sure ur not using a paid service?
That's a good news, that was only possible for Chinese firmware,hope they extend it to all regions.
gm007 said:
Are you sure ur not using a paid service?
That's a good news, that was only possible for Chinese firmware,hope they extend it to all regions.
Click to expand...
Click to collapse
Completely positive. It happened by accident because I got in a bad place with HRT rom. Came out completely stock and current when no upgrade need. Then I rooted stock and somehow lost gapps including keyboard. Did it again and back to stock. All in erecovery. No other programs or files. It did a 2.5GB download, flashed in Emui and rebooted like when I bought it.
rndchef said:
Completely positive. It happened by accident because I got in a bad place with HRT rom. Came out completely stock and current when no upgrade need. Then I rooted stock and somehow lost gapps including keyboard. Did it again and back to stock. All in erecovery. No other programs or files. It did a 2.5GB download, flashed in Emui and rebooted like when I bought it.
Click to expand...
Click to collapse
Sorry for the no noob question: I just got my mate 9 and unlocked bootloader and rooted it. Recovery is TWRP 3.0.2-2.
Where do i find this erecovery? Couldn't see any download option in TWRP and even Google didn't know that term. Could anybody please explain step by step how to revert to stock (for the only sake of getting OTAs) once the phone has unlocked bootloader and is rooted using the method from xda with modified boot.img?
Or is it even possible to take OTAs while being rooted with system read only? On my previous phone, the Asus Zenfone 2 this was possible.
Thanks a lot
itenos said:
Sorry for the no noob question: I just got my mate 9 and unlocked bootloader and rooted it. Recovery is TWRP 3.0.2-2.
Where do i find this erecovery? Couldn't see any download option in TWRP and even Google didn't know that term. Could anybody please explain step by step how to revert to stock (for the only sake of getting OTAs) once the phone has unlocked bootloader and is rooted using the method from xda with modified boot.img?
Or is it even possible to take OTAs while being rooted with system read only? On my previous phone, the Asus Zenfone 2 this was possible.
Thanks a lot
Click to expand...
Click to collapse
Connect ur phone to usb,and boot ur phone while holding volume up.
Please report back if erecovery recovered ur phone.
gm007 said:
Connect ur phone to usb,and boot ur phone while holding volume up.
Please report back if erecovery recovered ur phone.
Click to expand...
Click to collapse
Thanks for the quick answer. Let me clearify what I understood : this erecovery is available only on the PC?
So basically I wait in rooted state until I receive the next OTA, don't take it but switch off the phone.
Then connect it to the PC and boot it up by holding the volume up + power key.
Then what happens exactly?
Sent from my MHA-L29 using Tapatalk
itenos said:
Thanks for the quick answer. Let me clearify what I understood : this erecovery is available only on the PC?
So basically I wait in rooted state until I receive the next OTA, don't take it but switch off the phone.
Then connect it to the PC and boot it up by holding the volume up + power key.
Then what happens exactly?
Click to expand...
Click to collapse
Booting the phone while plugged and with volume up will take you to erecovery on ur phone.
There you connect to wifi and the firmware get downloaded into ur phone
gm007 said:
Booting the phone while plugged and with volume up will take you to erecovery on ur phone.
There you connect to wifi and the firmware get downloaded into ur phone
Click to expand...
Click to collapse
Ah ok, this erecovery is still available on my phone even if I already flashed a custom recovery, right?
Then after downloading the firmware, erecovery will flash it and overwrite root and lock my bootloader again, correct?
Sent from my MHA-L29 using Tapatalk