S.O.S!!! - Honor 6X Questions & Answers

Hi guys, good evening from the Philippines.
This is my first time making a thread here at xda but ever since, I have been visiting this site for the past years and the guides here are pretty helpful. Let me cut the chase. Guys, I really need your help.
I just rooted my huawei gr5 2017 and installed twrp to downgrade the firmware. I wiped all the partitions as usual and started flashing the firmware. Installing firmware is really time consuming and I fell asleep during the process (Well I am just a normal college student so i assume you know how tiring the whole day is) so I was really upset when I booted my phone in the morning and got stuck to your device is unlocked and can't be trusted. I tried reviving my phone by reflashing the firmware but it wont go to twrp. eRecovery only pops up with the download and restore recovery option. I tried fastboot but then it wont engage. I think everything was literally wiped, the whole system gone and my phone is like in a coma state. Please respond asap if you have any ideas regarding this matter.
*apologies if I can't send a picture of it but please do share your ideas if you have one

charles.darryl said:
Hi guys, good evening from the Philippines.
This is my first time making a thread here at xda but ever since, I have been visiting this site for the past years and the guides here are pretty helpful. Let me cut the chase. Guys, I really need your help.
I just rooted my huawei gr5 2017 and installed twrp to downgrade the firmware. I wiped all the partitions as usual and started flashing the firmware. Installing firmware is really time consuming and I fell asleep during the process (Well I am just a normal college student so i assume you know how tiring the whole day is) so I was really upset when I booted my phone in the morning and got stuck to your device is unlocked and can't be trusted. I tried reviving my phone by reflashing the firmware but it wont go to twrp. eRecovery only pops up with the download and restore recovery option. I tried fastboot but then it wont engage. I think everything was literally wiped, the whole system gone and my phone is like in a coma state. Please respond asap if you have any ideas regarding this matter.
*apologies if I can't send a picture of it but please do share your ideas if you have one
Click to expand...
Click to collapse
Can you boot into fastboot? To do so plug the USB into the phone and computer. Then hold power and volume down. As soon as screen goes black let go of power but keep holding volume down. It should boot into fastboot. From there tell me the status of Phone and FRP. Is it locked or unlocked. Next, was your phone in EMUI 8 before or 5? And to which version were you trying to downgrade to?

Related

[Q] Boot Loop with no recovery mode

Ok so I'm new to the thread and basically to android tablets, so please forgive my ignorance if it should become prevalent.
I bought a Galaxy Note Pro 12.2 32GB wifi and had it for about one day. I performed a factory restore on the device in which it froze for about 2 hours. (this is probably the stupid part) I turned it off since it was not progressing after a long time and it booted up as a new device. After about 5 minutes of use, it randomly restarted and went into a boot loop. About every 15 or so boot screens, it sometimes boots up, then freezes and goes back into a boot loop. The longest it stayed active without resetting was about 10 minutes. After hours of research, I have done the following
Tried to boot into recovery to no avail. It just continuously pops up the device name screen
I have tried to flash the device with a stock rom in odin 3.9.
It recognizes the device but hangs at the Initialization stage. Sometimes it will give me a fail notice saying that it couldn't open the COM port
I've tried it on another computer, changed usb ports, powered on and off multiple times and nothing changes.
please let me know if i've forgotten anything. Any help will be appreciated.
Also I live in Japan, so if I can fix it myself that would be nice since this device isn't sold here yet, I'm not able to get support from a store. I'd like to avoid waiting a month sending it back to america, replacing it, and getting it sent back. Thanks in advance ^_^
Make sure you have the correct and latest Samsung drivers for your tablet.
If you have an SD card installed, try removing it and see if you can boot up and get it stable.
roninb30 said:
Ok so I'm new to the thread and basically to android tablets, so please forgive my ignorance if it should become prevalent.
I bought a Galaxy Note Pro 12.2 32GB wifi and had it for about one day. I performed a factory restore on the device in which it froze for about 2 hours. (this is probably the stupid part) I turned it off since it was not progressing after a long time and it booted up as a new device. After about 5 minutes of use, it randomly restarted and went into a boot loop. About every 15 or so boot screens, it sometimes boots up, then freezes and goes back into a boot loop. The longest it stayed active without resetting was about 10 minutes. After hours of research, I have done the following
Tried to boot into recovery to no avail. It just continuously pops up the device name screen
I have tried to flash the device with a stock rom in odin 3.9.
It recognizes the device but hangs at the Initialization stage. Sometimes it will give me a fail notice saying that it couldn't open the COM port
I've tried it on another computer, changed usb ports, powered on and off multiple times and nothing changes.
please let me know if i've forgotten anything. Any help will be appreciated.
Also I live in Japan, so if I can fix it myself that would be nice since this device isn't sold here yet, I'm not able to get support from a store. I'd like to avoid waiting a month sending it back to america, replacing it, and getting it sent back. Thanks in advance ^_^
Click to expand...
Click to collapse
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root. Don't get me wrong, I have a list of things I want that require root and it will be happening but I figured I should at least run it for a couple weeks to make sure no defects pop up before I void the warranty. Good luck to you!
Russbad said:
Make sure you have the correct and latest Samsung drivers for your tablet.
If you have an SD card installed, try removing it and see if you can boot up and get it stable.
Click to expand...
Click to collapse
I've installed drivers a few times. No go.
I'm on it now and the boot loop seems to have stopped, but I still get random restarts. But each time it restarts, it's from factory, so it doesn't save anything I download or any settings such as enabling debugging in the developer settings.
rkirmeier said:
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root. Don't get me wrong, I have a list of things I want that require root and it will be happening but I figured I should at least run it for a couple weeks to make sure no defects pop up before I void the warranty. Good luck to you!
Click to expand...
Click to collapse
I didn't root, and I haven't voided my warranty. I can still get into download mode and my flash counter is still at 0. I never tried to root, I simply wanted to flash to stock, from stock.
[Edit] I'd also like to mention that Odin has not successfully done anything, Every time I tried to flash it was done with a stock ROM, and everything that has gone wrong has occurred on nothing but the stock ROM
Is it possible that I need a pit file for the device since no version of Odin will get past initialization? ....if so where can I get one for the this model?
roninb30 said:
I've installed drivers a few times. No go.
I'm on it now and the boot loop seems to have stopped, but I still get random restarts. But each time it restarts, it's from factory, so it doesn't save anything I download or any settings such as enabling debugging in the developer settings.
I didn't root, and I haven't voided my warranty. I can still get into download mode and my flash counter is still at 0. I never tried to root, I simply wanted to flash to stock, from stock.
[Edit] I'd also like to mention that Odin has not successfully done anything, Every time I tried to flash it was done with a stock ROM, and everything that has gone wrong has occurred on nothing but the stock ROM
Click to expand...
Click to collapse
If you are not rooted and you have a boot loop I'd be returning the device for a new one...
rkirmeier said:
If you are not rooted and you have a boot loop I'd be returning the device for a new one...
Click to expand...
Click to collapse
I hate to agree since you would have to wait for a while to get the replacement, however the device sounds to be defective. just my two cents as a developer, if you flash anything to the device, root, a new image, or even the factory software, Knox will be tripped and the counter will go from zero to a one. My advice would be to get a replacement for the defective one.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Huge 3rd.
Device should just plain WORK out of the box. There shouldn't have been a need to flash stock to begin with.
One last suggestion, factory reset from recovery. From complete power off, hold volume up+home button+power and after a few seconds let go until it boots into recovery. From there wipe cache, wipe davlik, and factory restore. Good luck!
Android.Ninja said:
I hate to agree since you would have to wait for a while to get the replacement, however the device sounds to be defective. just my two cents as a developer, if you flash anything to the device, root, a new image, or even the factory software, Knox will be tripped and the counter will go from zero to a one. My advice would be to get a replacement for the defective one.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Click to expand...
Click to collapse
Yeah, it's unfortunate, but I have to suck it up and just pay the shipping back to Ameica....then again for it to come back. Just wanted to do everything I could before I had to send it. Thanks for the input though. I guess I learned quite a bit researching processes and terminology which will be helpful in the future. ^-^
Russbad said:
One last suggestion, factory reset from recovery. From complete power off, hold volume up+home button+power and after a few seconds let go until it boots into recovery. From there wipe cache, wipe davlik, and factory restore. Good luck!
Click to expand...
Click to collapse
Tried many times. The device pretty much gives me the finger by going blank and repeatedly showing the boot up logo when I hold the buttons down.
rkirmeier said:
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root.
Click to expand...
Click to collapse
I voided my warrant after having mine for about an hour (though not new to Android). I did all my random "OCD does it work as I expect/want" tests and it passed, so I rooted. Had it for one week now, and I absolutely love everything about this tablet.
roninb30 said:
Yeah, it's unfortunate, but I have to suck it up and just pay the shipping back to Ameica
Click to expand...
Click to collapse
IMO, it will be worth it. This is my fourth tablet, and is the first one I've not had buyer's remorse with. Luckily with the gift credit for Google I was able to get the non-Tegra equivalents of some of my favorite games, too.
ExtremeRyno said:
I voided my warrant after having mine for about an hour (though not new to Android). I did all my random "OCD does it work as I expect/want" tests and it passed, so I rooted. Had it for one week now, and I absolutely love everything about this tablet.
IMO, it will be worth it. This is my fourth tablet, and is the first one I've not had buyer's remorse with. Luckily with the gift credit for Google I was able to get the non-Tegra equivalents of some of my favorite games, too.
Click to expand...
Click to collapse
After doing research, I think that even if I get a new one, I want to root it. With the problems I've read about for kitkat 4.4.2 I need to know how to fix problems, and start with a fresh install of roms and know how to use custom recovery. I haven't done anything yet, but I was wondering...
Since I'm stuck in a boot loop with no stock recovery, can I flash a custom recovery to fix my issues, flash the stock rom that is on sammobile.com and then root after that? From what I understand this is a soft brick since I can still sometimes access the device. I worked out why I couldn't access the device with adb and now it shows the device as listed. It stays on long enough to where I could flash a recovery before it restarts itself. I'm not trying to do anything stupid, just getting information before I pay the shipping for it back to the states. I've checked the knox counter in download mode, and it is still set to 0, so I haven't voided the warranty yet.
Any input would be greatly appreciated.
It's odd that a new device would not have recovery. I don't want to insult you, but just making sure we covered the basics, volume up+home+power gets you to recovery. The boot logo will flash about three times, make sure you're still pressing all three buttons, then let go after the 3rd flash of the boot logo then you should be in recovery. Volume down+home+power takes you to download mode, this is where you flash roms and recovery. I read in another post about someone not being able to get in recovery after numerous times, it turned out that he was hitting the volume down button instead of volume up. Just to be clear, if you do flash recovery, you will definitely trip knox, at this time there is no way around that.
Russbad said:
It's odd that a new device would not have recovery. I don't want to insult you, but just making sure we covered the basics, volume up+home+power gets you to recovery. The boot logo will flash about three times, make sure you're still pressing all three buttons, then let go after the 3rd flash of the boot logo then you should be in recovery. Volume down+home+power takes you to download mode, this is where you flash roms and recovery. I read in another post about someone not being able to get in recovery after numerous times, it turned out that he was hitting the volume down button instead of volume up. Just to be clear, if you do flash recovery, you will definitely trip knox, at this time there is no way around that.
Click to expand...
Click to collapse
I understand the skepticism. Yeah, I tried the button combination, usb in, usb out. I can power off the device completely only when it is plugged into power. When I hold the recovery combo from power on, the screen goes black with no flashing of the boot logo, looks as if it wants to go to recovery, and then then the boot logo comes up again, but just continues to the boot animation and continues the boot loop, even if i'm still holding down volume up and home buttons. It will sometimes boot up, then freeze after a couple of seconds, and return to boot loop. On rare occasions it will boot up, but turns me to setup like it's a brand new device. I can access everything for about 10 minutes, and then it will randomly restart and continue to boot loop again after that. I tried update/initialization in kies, but it would restart before the downloading and decompressing of binary could finish. It finished one time and then switch to a downloading screen (although it didn't say odin since you have to manually go there) but the update would freeze at 0 percent no matter how long I left the device there. It's all pretty lame ><

[Completed] corrupted boot partition in vodafone smart prime 6

hi! im new here, but all of the members at xda never let me down in unbricking my two previous smart phones (i brick all of my smartphones ), though im having a little bit of a problem in my most recent phone, a vodafone smart prime 6 from portugal.
hereĀ“s what happened:
my previous two phones didnt run pokemon go, and i wanted to give it a try, see what all the fuss was about. unfortunately, i bought the phone second handed, and it was rooted, so i had to unroot it. but then i remembered all the good things about rooted android smartphones so i decided to try to install magisk, without success unfortunately. but magisk and supersu messed up my phone, and i was having a pain in the ass unrooting it, so i tried to install an original rom with TWRP, but it turns out i got a corrupted rom, and i know for a fact the boot partition is completely ****ed.
it wont go to recovery, it wont boot into the system, just stays there on the "powered by android" screen. i know for a fact (and this might help) that my computer detects the bootloader interface, but no ADB. if i connect my phone to the computer with the volume up and down buttons, it goes into download mode, but those are the only things that work.
it doesnt do anything, and i really dont wanna take it to a store, because i cant afford it (which is why i bought it second handed).
i hope you guys can help me,
thanks in advance,
vectonic
Hello
Try asking in the link below
http://forum.xda-developers.com/android/help
Good luck

Think i bricked my Huawei flashing an update via Hisuite. Wont boot or charge. HELP!?

I think i wanted a pie update so badly i bricked my Huawei Y9 2019( runs kirin 710). please read this, ill try to be as detailed as possible about my problem
So this what happened, i installed and made patch changes to a Hisuite version i found online which was meant to force an emui 9 update for my phone. i had already tried the firmware finder method but it wasnt woking. so after following the instructions and plugging in my phone, Hisuite provided me with an update. funny thing is that the update had no name or description or even changelog (i know this shouldve been a warning sign) but i still downloaded and after 20-30 minutes it was done, phone went into erocovery, verified update and started updating to completion. afterwards my phone was supposed to boot but it never booted up, wont charge (battery was about 90% innitially though) or even get to recovery mode or anything. The screen remains off; black. My phone is not rooted or anything, bootloader is still locked. when i plug it into my computer i can hear the plugging noises that windows makes but it doesnt show up anywhere(i believe this might be a good sign its not completely dead idk)
I've already visited their service centre in my country and they said they need to change the motherboard cuz i flashed wrong software but im supposed to wait for a month so they can get me a new board. i cant wait that long. im just suprised since if it was an mtk device or some other i would just reflash the stock rom. My phone was in perfect physical condition. ive searched all over the place for help but nothing, someone please help me:crying::crying:

G970F bootloop after upgrade to Android 10

Yesterday I got my knew phone and unlocked the bootloader. I did this, because I want to root it (when I have more time). But today the phone downloaded Android 10 update and I installed it. After installing, the phone is "bricked" and in boot loop. I cannot turn it off. Volume down and power keys won't help. I cannot get into recovery mode either. The only option is download mode. But in download mode, the USB is not recognized by my PC. Already downloaded the newest Samsung USB driver. I flashed my old phone (Samsung S7) by Odin several times, with the same PC.
Is it in bootloop, because I installed the Android 10 update with an unlocked bootloader?
Any advice?
No advice, but I did exactly the same thing, and mine also bricked, so yeah, it seems like upgrading to Android 10 on an unlocked phone causes a bootloop. I returned mine, didn't want to deal with this on a brand new device.
Somehow I managed to make a good USB connection and flashed the Android 10 firmware by Odin. Tried the CSC_home option, but then after boot it was stuck at "SAMSUNG" screen for more than 30 minutes. Killed the phone by using volume down + power buttons. After this I could enter recovery mode and did a factory reset.
Best thing is, like you said, to return the phone. But I didn't want to wait that long
So people, be warned. Do not update from Android 9 to 10 with an unlocked bootloader!
hi everybody. there was the same situation, friends, please tell me what to do? what can I do to bring my phone back to life?
acid umbrella said:
hi everybody. there was the same situation, friends, please tell me what to do? what can I do to bring my phone back to life?
Click to expand...
Click to collapse
Read the comment above

Samsung s20FE somehow bricked

Hello
my sister's phone somehow broke down. It's not rooted or anything, was use for mainly day to day use. She called me yesterday that her phone randomly resets (like 1x per hour).
I plugged phone to computer, wanted to transfer pictures and "important" data to pc and during the transformation phone closed and I am unable to open it again. I managed to transfer around 60% of pictures but mostly important ones so the loss is not that big.
-phone started "looping" at start screen logo to samsung for like 30minutes. After a while it somehow booted into the system and I tried to do software update. Downloaded the update and then installed it but at some point phone closed down and started looping loading screen again. Since then im unable to boot it into the system....
-I entered recovery mode and did Factory reset. Doesnt help. Wiped cache, doesnt help.
-i know little to nothing about android but my guess is that i somehow bricked the system when i did factory reset just when the phone was updating?
is there any solution to somehow "install" fresh android on the phone via PC? Phone is not rooted but it has activated USB debugging options.
****EDIT***
I was thinking that it could be hardware issue but phone can stay open in recovery mode for hours so I suppose it is software problem?
Phone is still under warranty but i cba dealing with services and would rather fix it myself.
Thank you for any help
You should simply done a factory reset.
It will need reflashed. In the long run it may be best to let Samsung hash it out.
Yeah i should've done factory reset while phone was still usable. But I wanted to recover all of the photoa, thats why i tried to do system update first....
dehumless said:
Yeah i should've done factory reset while phone was still usable. But I wanted to recover all of the photoa, thats why i tried to do system update first....
Click to expand...
Click to collapse
Updates don't help especially in this case where the OS was teeter toddling on the abyss. Safe mode. The first mistake was not having the critical data redundantly backed up. All you can do is learn from the mistakes.
blackhawk said:
Updates don't help especially in this case where the OS was teeter toddling on the abyss. Safe mode. The first mistake was not having the critical data redundantly backed up. All you can do is learn from the mistakes.
Click to expand...
Click to collapse
well, right now im trying to find android firmware images and will try to flash them on with Odin later.
But I am sure that i will face several problems on the way
dehumless said:
well, right now im trying to find android firmware images and will try to flash them on with Odin later.
But I am sure that i will face several problems on the way
Click to expand...
Click to collapse
You can use SmartSwitch to do that, but I'm a total novice at flashing Androids and the best method. Pick and use the safest method...
A Samsung Experience center at Best Buy can also do it. They might be able to give you more insight as to why it failed.

Categories

Resources