hey all. recently i tried to use hwota 8 to go from emui 8 china to emui 8 india. during the processs where it askd for bootloader unlock code (i used change location) it failed (remote password wrong). so i disconnected and manually booted to fastboot and unlocked my bootloader. but now the device wont boot, its stuck on your device is booting screen. i cant enter fastboot, erecovery or bootloader, however when i connect it to my pc sound plays. please help me anyone i am worried i cant also use dload
@Ramesh006 can you help me out?
Fixed. A while ago actually. Posting so that anyone in the same situation can ask
Good idea is writing Solution whitout waiting another in same condition...
Fixed. A while ago actually. Posting so that anyone in the same situation can ask
Click to expand...
Click to collapse
I have the same situation . what Solution ????
When you say same do you mean exactly same like no fastboot, recovery etc. And did it happen after HWOTA 8. Please tell me exactly what happened so I can guide you better
MadDog.76 said:
Good idea is writing Solution whitout waiting another in same condition...
Click to expand...
Click to collapse
+1
Oh well. If you want guide then sure. Here you go.
First of all let your battery drain completely. Once battery is dead. Plug your phone into charging and as soon as it shows three options boot screen quickly press Volume Up to boot into recovery. It will boot TWRP. Only if you tried via HWOTA 8. Read OP to know complete story. Now once in TWRP keep your phone on charging and don't let it shutdown. In TWRP go to Wipe and Format Data. Do it one to two times. Now go to Advanced Wipe and individually select each of the following one by one.
Cache
Dalvik Cache
Data
Internal
System.
First select repair file system and then after it repair wipe it individually. Then do a collective wipe. One or two Swipe to factory reset. After this cleansing flash firmware for Oreo of the build you were trying to go-to via Hurupdater. Search for it and follow exact guide. After that select Reboot Phone and when it's powering on, you should get three options menu. Press Volume Up to enter erecovery. This time you will boot normal recovery. Factory reset and then Format cache. Reboot system. First boot will take time. Be patient.
After you reboot you will notice several apps missing and themes not working as well as pinkish wallpaper instead of purple one. To fix flash any Oreo Compatible TWRP or the TWRP form Elemental ROM thread. Go-to wipe and format data. Then advanced wipe and select Data Internal System Cache and Dalvik. Wipe and then reflash Firmware via Hurupdater. After it finishes, reboot system and then reboot into stock recovery. Perform factory reset and then format cache. Reboot.
Related
I am a relatively new android user but do enjoy flashing roms, kernels etc
My problems began when i was trying to flash a new rom on my Nexus 5
I was trying to flash this rom http://forum.xda-developers.com/showthread.php?t=2655722 but despite doing a factory reset and wiping the dalvik cache and cache it refused to boot in to the new rom
I tried to flash the rom multiple times but without success, eventually when trying to boot into recovery to try again i was greeted with an unthemed TWRP recovery asking for a password despite the fact that i had a custom theme and multirom installed I tried to proceed anyways but was greeted with E: unable to mount storage
In desperation i tried to solve this problem and found this
UsoftTech :: WwW.UsoftTech.CoM ::
TWRP asking for password
After unboxing my Nexus 5, here's what I did:
1. Booted into bootloader
2. fastboot oem unlock
3. Flashed TWRP v2.6.3.0
4. Booted to recovery
The screen that greeted me says "Please Enter Your Password".
I can hit the cancel button below this which takes me to the normal TWRP screen. I then pushed SuperSU to /sdcard, but when I flash it it fails because it's unable to mount /cache or storage.
When I reboot to the system, it takes an awfully long time (approximately 30s) to progress past the "Google" screen, and then it just seems to sit on the booting animation forever.
Any help?
EDIT: Solved my own problem.
Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
TWRP asking for password
Click to expand...
Click to collapse
I now fear that i maybe without both a rom and all my files such as my music that was stored on my phone.
Is there any way for me to undo the damage i may have done to to my phone?
You can't recover the data. But you can push files over with ADB.
Sent from my Nexus 7 using Tapatalk
JoJostar said:
I am a relatively new android user but do enjoy flashing roms, kernels etc
My problems began when i was trying to flash a new rom on my Nexus 5
I was trying to flash this rom http://forum.xda-developers.com/showthread.php?t=2655722 but despite doing a factory reset and wiping the dalvik cache and cache it refused to boot in to the new rom
I tried to flash the rom multiple times but without success, eventually when trying to boot into recovery to try again i was greeted with an unthemed TWRP recovery asking for a password despite the fact that i had a custom theme and multirom installed I tried to proceed anyways but was greeted with E: unable to mount storage
In desperation i tried to solve this problem and found this
Wrong thread.
d
Click to expand...
Click to collapse
About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.
Hi guys. I recently rebranded my Honor 6X from BLN L22 (oreo) to BLN AL10. I used HuRUpdater method to flash the system via TWRP. However, after booting, I noticed that the clock on the lockscreen went on top instead on the bottom,which looks weird. Also, I noticed that the Themes app doesnt show customizqtion options (only fonts).
Why am I getting this? And how can I fix this? It seemd that the system Is not also working properly. I think there might be some problems on flashing on the system because TWRP couldnt mount the data partition.
Please guys. I need your HELP. Thank you very much!
It's an incomplete flash pretty easy to fix. For this you need an external Micro SD card. About 8 GB should do. You also need the three firmware archives you originally downloaded to go to Oreo. And rename them as you did before. Now search for Hurupdater and download latest. You can also get more instructions there over the archives. Place the three archives as well as Hurupdater in the same folder. Instructions in above mentioned thread.
Now flash TWRP. Oy Oreo Compatible TWRP is the one from Elemental ROM thread for the Honor 6x. Grab it and flash it using the command:
fastboot flash recovery_ramdisk RECOVERY-V2.img
Now boot into TWRP. Go to Wipe -> Format Data -> Yes.
Once it completes press back Twice and now select Advanced Wipe. Select Dalvik/Art Cache, Cache, Data, Internal & System. Swipe to Wipe. Now go to install and select only Hurupdater to flash. Press Volume Down when prompted. Flashing will take 5-8 mins. Now once flash complete press Wipe Cache Dalvik and after wiping press Reboot System Now. As device boots up and shows three warning screen, press and hold Volume Up. Boot into recovery and do a factory reset. Then format Cache and reboot. First boot will take 10 mins. Good luck. Ask for more help.
Hi everyone!
Yesterday after entering boot loops after trying to install the Xposed module from Magisk, I reinstalled the latest Oxygen OS zip via TWRP's "Wipe / Swipe to Factory Reset". When the phone booted in "hello, new user" mode, I saw there were still files from before under sdcard/, so, to be sure, I also tried to do a Factory reset from within OOS Settings / System. When the phone booted in "hello, new user" mode, I noticed there were still files from before under sdcard.
I re-flashed Magisk, installed a few things, did a backup via TWRP. Worked on setting up the phone for two more hours (didn't install any Magisk module, only software from the Play store), rebooted the phone to check everything was okay… boot loop!
Using the backup, I was able to reset the phone to the state of before wasting these two hours… But these boot loops seem so fickle, so random, that I wonder if I'm missing something with the factory reset, if maybe there is a more brutal reset that would erase all trace of activity after the state where the phone was after unlocking the bootloader.
Is there a way to do a more complete "factory reset" than what I've done? I see that Magisk has an "Advanced Wipe", if I checked all the box would that do it? Or is that a bad idea because some important OOS recovery files would vanish. Which "Advanced Wipe" options should I check? If I follow that procedure, will I be able to reinstall TWRP and Magisk via ADB?
Really needing some expert insight, I feel very lost!
Thanks in advance!
who ah way said:
Hi everyone!
Yesterday after entering boot loops after trying to install the Xposed module from Magisk, I reinstalled the latest Oxygen OS zip via TWRP's "Wipe / Swipe to Factory Reset". When the phone booted in "hello, new user" mode, I saw there were still files from before under sdcard/, so, to be sure, I also tried to do a Factory reset from within OOS Settings / System. When the phone booted in "hello, new user" mode, I noticed there were still files from before under sdcard.
I re-flashed Magisk, installed a few things, did a backup via TWRP. Worked on setting up the phone for two more hours (didn't install any Magisk module, only software from the Play store), rebooted the phone to check everything was okay… boot loop!
Using the backup, I was able to reset the phone to the state of before wasting these two hours… But these boot loops seem so fickle, so random, that I wonder if I'm missing something with the factory reset, if maybe there is a more brutal reset that would erase all trace of activity after the state where the phone was after unlocking the bootloader.
Is there a way to do a more complete "factory reset" than what I've done? I see that Magisk has an "Advanced Wipe", if I checked all the box would that do it? Or is that a bad idea because some important OOS recovery files would vanish. Which "Advanced Wipe" options should I check? If I follow that procedure, will I be able to reinstall TWRP and Magisk via ADB?
Really needing some expert insight, I feel very lost!
Thanks in advance!
Click to expand...
Click to collapse
Hello, format internal storage within twrp deletes everything off your /sdcard but does not touch system, data, vendor for example.
You're still able to use fastboot/adb cause you do not delete the bootloader:good:
strongst said:
Hello, format internal storage within twrp deletes everything off your /sdcard but does not touch system, data, vendor for example.
You're still able to use fastboot/adb cause you do not delete the bootloader:good:
Click to expand...
Click to collapse
Thank you for your reply!
Just to be sure I understand, are you suggesting that a strong way of getting a good Factory Reset would be:
TWRP / Wipe
[ ] Dalvik / ART Cache
[ ] System
[ ] Vendor
[ ] Data
[x] Internal Storage
[ ] USB Storage
then (if TWRP is gone):
adb devices
adb reboot bootloader
fastboot boot twrp-3.3.1-52-guacamole-unified.img
In TWRP, install twrp-3.3.1-52-guacamole-unified-installer.zip
In TWRP, install OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
Do the phone's "Welcome, user" setup
Flash Magisk
Does that sound right?
who ah way said:
Thank you for your reply!
Just to be sure I understand, are you suggesting that a strong way of getting a good Factory Reset would be:
TWRP / Wipe
[ ] Dalvik / ART Cache
[ ] System
[ ] Vendor
[ ] Data
[x] Internal Storage
[ ] USB Storage
then (if TWRP is gone):
adb devices
adb reboot bootloader
fastboot boot twrp-3.3.1-52-guacamole-unified.img
In TWRP, install twrp-3.3.1-52-guacamole-unified-installer.zip
In TWRP, install OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
Do the phone's "Welcome, user" setup
Flash Magisk
Does that sound right?
Click to expand...
Click to collapse
Generally the factory reset does all too need(from android settings). Why theres something left of your device I don't know.
But I meant format internal storage, not wipe internal storage.
So reboot to twrp - wipe - format and follow the instructions reading the hints.
Again: that does not wipe your twrp, system, system data only the internal storage like music, photos etc.
For installation, it's OK what you wrote
Thank you very much, @strongst.
If I understand, that "Format" option that you suggested is what gets rid of all the personal files. Then to Factory Reset, I can either flash via TWRP, or use adb.
At the moment I am thinking that like you suggested the phone is actually okay after the standard Factory Reset — and that the earlier boot loop was created by one specific piece of "bad software". So I am reinstalling things little by little, and doing TWRP backups after every 15 minutes of set-up. That way if the phone enters a boot loop, I will be able to restore and to narrow it down, and check on the forum if others have the same problem. Does this make sense to you?
Wishing you a great week!
who ah way said:
Thank you very much, @strongst.
If I understand, that "Format" option that you suggested is what gets rid of all the personal files. Then to Factory Reset, I can either flash via TWRP, or use adb.
At the moment I am thinking that like you suggested the phone is actually okay after the standard Factory Reset — and that the earlier boot loop was created by one specific piece of "bad software". So I am reinstalling things little by little, and doing TWRP backups after every 15 minutes of set-up. That way if the phone enters a boot loop, I will be able to restore and to narrow it down, and check on the forum if others have the same problem. Does this make sense to you?
Wishing you a great week!
Click to expand...
Click to collapse
It's a good way to break a potential boot loop issue down, time consuming, but worth the effort in case it boot loops
Hello, I was using my phone normally and then I decided to turn it off because I was having a bug with an application, then I turned it on but in that process I accidentaly push one of the volume bottons and end up on what it seems a boot menu, I went for the english option and then to "exit" and "power off" so I can exit this boot menu, but it comes back again to this menu over and over I don't know why,.
I go to boot reason and appears this: fs_mgr_mount_all
Unable to parse kernel log.
I need help, don't know why I can't exit this menu because I entered by mistake and did nothing else than trying to exit. I have never root my phone or anything related to that, please help me to not lose my data!
Try booting in Recovery and clear Cache (only wipe Cache not Wipe all) and then reboot
Maybe this help you
GraveDigger176 said:
Try booting in Recovery and clear Cache (only wipe Cache not Wipe all) and then reboot
Maybe this help you
Click to expand...
Click to collapse
Ok just done that but it is still stuck on boot, maybe there is another solution to this problem?
Hmm looks like your 8T is caught in bootloop. As far as i know there is only to try in Recovery the Wipe All step which deleted all on your Phone. If that also not works then MSN Tool which has the same result as the Wipe All, the only differnce is that MSN Tool sets up your Partitions fresh and complete clean.
But i can be wrong with that what i Knowing, maybe a more smarter guy can help you out with your problem.
If your phone bootloader not unlocked, the only way i know is fastboot flash .img file from official full update.zip
If that not work, wipe or MSM, but they all causing data loss.