Related
I rooted the watch successfully and then attempted to revert to stock using the instructions here: http://forum.xda-developers.com/huawei-watch/development/guide-return-to-stock-huawei-watch-t3219596
. Midway through the restore of the system.img, my computer crashed and now the watch is stuck at the Huwaei logo. I can no longer connect to the watch over adb - attemps to do so show that the watch is "offline." Is all hope lost or is there anything I can try?
No one has figured out a way to boot directly to the boot loader yet...there has to be a way, just need to find it.
Edit...if it shows connected but offline, just try unplugging it and plugging it back in again.
Sent from my Nexus 6 using Tapatalk
brizey said:
No one has figured out a way to boot directly to the boot loader yet...there has to be a way, just need to find it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Okay. I'll keep checking back. BTW, I looked back at the terminal window which reopened when my computer restarted and the last thing posted there was "restored" so it may not have been my computer restarting which caused the issue. For this reason, I would strongly caution anyone who is thinking about using the system restore files in the linked thread. Better safe than sorry.
davpel said:
Okay. I'll keep checking back. BTW, I looked back at the terminal window which reopened when my computer restarted and the last thing posted there was "restored" so it may not have been my computer restarting which caused the issue. For this reason, I would strongly caution anyone who is thinking about using the system restore files in the linked thread. Better safe than sorry.
Click to expand...
Click to collapse
Hey man, try unplugging and plugging it back in, then quickly doing an adb reboot bootloader. I have found that adb goes offline when in ambient mode, so you may get a brief chance to get it to the bootloader.
Edit:
Ah hah! You have to adb root to get it to work in ambient mode.
Man, we need a mechanical way to boot to bootloader.
brizey said:
Hey man, try unplugging and plugging it back in, then quickly doing an adb reboot bootloader. I have found that adb goes offline when in ambient mode, so you may get a brief chance to get it to the bootloader.
Edit:
Ah hah! You have to adb root to get it to work in ambient mode.
Man, we need a mechanical way to boot to bootloader.
Click to expand...
Click to collapse
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
If you can get into the bootloader, maybe try restoring these instead? http://forum.xda-developers.com/huawei-watch/general/huawei-watch-stock-rooted-images-t3224930
davpel said:
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
Click to expand...
Click to collapse
I have my TWRP backup if you need it. I looked at it and it looks OK...typical image with the folders and SELinux context files. But...it is a rooted image.
brizey said:
I have my TWRP backup if you need it. I looked at it and it looks OK...typical image with the folders and SELinux context files. But...it is a rooted image.
Click to expand...
Click to collapse
Thanks, but unless/until I can get into the bootloader, I'm stuck. Right?
davpel said:
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
Click to expand...
Click to collapse
Hmmm...just noticed that tiny's and skin's system images are not the same. Different sizes.
davpel said:
Thanks, but unless/until I can get into the bootloader, I'm stuck. Right?
Click to expand...
Click to collapse
If if's anything like the Moto 360, you should be able to power the watch off, and then hold the power button for ~30 seconds to achieve boot to bootloader.
1/4 Life said:
If if's anything like the Moto 360, you should be able to power the watch off, and then hold the power button for ~30 seconds to achieve boot to bootloader.
Click to expand...
Click to collapse
Tried that. I get the double vibration, but no bootloader.
FWIW, I just looked at a few of the 5.1 OTAs for other watches. I think the OTAs will work even if rooted. I looked at skin1980's init autoroot script, and I don't think it really touches any of the base system files...it only adds in the binaries. The updater script does a hash on all of the files that it is going to patch, then patches them if the hashes are OK. Given that we are not really touching the system files by flashing a custom ROM, I think we can make the OTA zips work. The kernel will likely not flash, but we can always build a new one from source if needed.
brizey said:
Hmmm...just noticed that tiny's and skin's system images are not the same. Different sizes.
Click to expand...
Click to collapse
And i dont know why. I dd them like i said and they are completely stock.
davpel said:
Tried that. I get the double vibration, but no bootloader.
Click to expand...
Click to collapse
http://forum.xda-developers.com/g-watch-r/development/fastboot-mode-lg-g-watch-r-t2946955 (?)
1/4 Life said:
http://forum.xda-developers.com/g-watch-r/development/fastboot-mode-lg-g-watch-r-t2946955 (?)
Click to expand...
Click to collapse
Thanks, but tried the LG method as well (both the swipe and the tap) and had the same results -- or lack thereof.
Has anyone else tried restoring to stock with success from Skin's files?
myke66 said:
Has anyone else tried restoring to stock with success from Skin's files?
Click to expand...
Click to collapse
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Skin1980 said:
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Click to expand...
Click to collapse
Yes, my watch is working great, thanks to Skin1980. This community is very lucky to have him!
Skin1980 said:
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Click to expand...
Click to collapse
davpel said:
Yes, my watch is working great, thanks to Skin1980. This community is very lucky to have him!
Click to expand...
Click to collapse
Agree 100%. I am returning my first watch, and flashed it back to stock and relocked the bootloader with no issues using the revised instructions. Going to keep my new one stock I think...got to cut down on the toys (Nexus 6, Nexus 7, iPhone 5s, custom PC, G37, surveillance system, house LED lighting conversion, etc. etc. Momma ain't happy, and I really want to spend more time with the kiddos.)
Who the hell needs to ROOT a damn smart watch?! I could see when it was 2 years ago with the first Samsung smart watch to sideload Android apps but this.... This is just stupid. Congrats
Sent from my SM-N910T using Tapatalk
Hello XDA!
I have a Verizon Pixel XL that is stuck in a boot-loop after the 7.1.2 firmware update. The boot-loop did not begin immediately after the update which confuses me. I have never attempted to unlock the bootloader, root, or flash the firmware. I have thousands of pictures I am attempting to recover (I did not have coverage to backup the pictures in Google Photos) before I work on the boot-loop issue (or warranty replacement). I can access fastboot & recovery but these modes do not provide a backup option or backup command from ADB. When I boot to safe-mode the phone will stay on for about 10 seconds which has allowed me to disable a LOT of apps and enable USB debug.
As I see it, there are only two options available to me...
1) Find a way to 'halt' the system after start-up or find the mysterious app causing the issue and disable it.
2) Forensic (physical) data recovery for $500-$900
I have tried to research as much as possible (please correct me if I'm wrong): unlocking Verizon bootloader is not currently possible, installing custom recovery is either not possible or will wipe the device, and pushing a firmware update will also wipe the device.
If anyone has any suggestions or would like more information please let me know.
I will keep an eye on this thread to provide timely responses.
Thank you,
Matthew
w144mjb said:
Hello XDA!
I have a Verizon Pixel XL that is stuck in a boot-loop after the 7.1.2 firmware update. The boot-loop did not begin immediately after the update which confuses me. I have never attempted to unlock the bootloader, root, or flash the firmware. I have thousands of pictures I am attempting to recover (I did not have coverage to backup the pictures in Google Photos) before I work on the boot-loop issue (or warranty replacement). I can access fastboot & recovery but these modes do not provide a backup option or backup command from ADB. When I boot to safe-mode the phone will stay on for about 10 seconds which has allowed me to disable a LOT of apps and enable USB debug.
As I see it, there are only two options available to me...
1) Find a way to 'halt' the system after start-up or find the mysterious app causing the issue and disable it.
2) Forensic (physical) data recovery for $500-$900
I have tried to research as much as possible (please correct me if I'm wrong): unlocking Verizon bootloader is not currently possible, installing custom recovery is either not possible or will wipe the device, and pushing a firmware update will also wipe the device.
If anyone has any suggestions or would like more information please let me know.
I will keep an eye on this thread to provide timely responses.
Thank you,
Matthew
Click to expand...
Click to collapse
Flashing updates do not wipe your data. Download firmware of choice. Unzip it, place latest fastboot drivers in where update zip is. Rename it to something easy. fastboot update update.zip
Edit: enclosed fastboot drivers
Tulsadiver said:
Flashing updates do not wipe your data. Download firmware of choice. Unzip it, place latest fastboot drivers in where update zip is. Rename it to something easy. fastboot update update.zip
Edit: enclosed fastboot drivers
Click to expand...
Click to collapse
Thank you Tulsadiver!
Do you think the firmware update will also fix the boot loop?
w144mjb said:
Thank you Tulsadiver!
Do you think the firmware update will also fix the boot loop?
Click to expand...
Click to collapse
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.
Tulsadiver said:
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.
Click to expand...
Click to collapse
Being the noob that I am, I have a few more questions.
Do I have to unlock the bootloader to update the firmware?
I'm currently on NHG470 firmware, should I choose NHG47N or NHG47K or a different one?
I'd like to keep the phone on a factory image unless you suggest otherwise.
Thank you for your time and patience,
Matthew
w144mjb said:
Being the noob that I am, I have a few more questions.
Do I have to unlock the bootloader to update the firmware?
I'm currently on NHG470 firmware, should I choose NHG47N or NHG47K or a different one?
I'd like to keep the phone on a factory image unless you suggest otherwise.
Thank you for your time and patience,
Matthew
Click to expand...
Click to collapse
Yes, you must unlock the bootloader...you are on Verizon and I am unfamiliar with their procedure and even if the bootloader is unlockable. You had better talk to someone on a Verizon phone.
Tulsadiver said:
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.
Click to expand...
Click to collapse
Tulsadiver said:
Yes, you must unlock the bootloader...you are on Verizon and I am unfamiliar with their procedure and even if the bootloader is unlockable. You had better talk to someone on a Verizon phone.
Click to expand...
Click to collapse
On Android source I am reading that unlocking the bootloader requires a full wipe.
https://source.android.com/source/running#unlocking-the-bootloader
Please advise.
Thank you,
Matthew
w144mjb said:
On Android source I am reading that unlocking the bootloader requires a full wipe.
https://source.android.com/source/running#unlocking-the-bootloader
Please advise.
Thank you,
Matthew
Click to expand...
Click to collapse
That is true.
If you take it to a Verizon store and explain the situation they might be able to help.
Tulsadiver said:
That is true.
Click to expand...
Click to collapse
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew
w144mjb said:
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew
Click to expand...
Click to collapse
I understand but my stepson has worked for every Carrier and they have access to software that might help. You already have a phone coming in so no skin off their nose.
w144mjb said:
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew
Click to expand...
Click to collapse
I'm pretty sure you're SOL if you can't get it to boot to system. I don't think you can pull the data off the device without being in system. Even if you can it would be encrypted. So you wouldn't be able to do anything with it. Have you tried to boot in safe mode. If you get it to boot up in safe mode then you can pull the data off with no issues.
Tulsadiver said:
I understand but my stepson has worked for every Carrier and they have access to software that might help. You already have a phone coming in so no skin off their nose.
Click to expand...
Click to collapse
I'll give Verizon technical support a call tonight (or a few, as necessary) and update you after.
Thank you,
Matthew
toknitup420 said:
I'm pretty sure you're SOL if you can't get it to boot to system. I don't think you can pull the data off the device without being in system. Even if you can it would be encrypted. So you wouldn't be able to do anything with it. Have you tried to boot in safe mode. If you get it to boot up in safe mode then you can pull the data off with no issues.
Click to expand...
Click to collapse
It will stay on for about 10 seconds in Safe mode.
w144mjb said:
It will stay on for about 10 seconds in Safe mode.
Click to expand...
Click to collapse
Safe mode only runs stock apps so if you are still boot looping in safe mode it's unlikely an app is causing your problem. I'm not sure what you mean when you say you didn't have coverage to back up your photos in Google Photos --i thought all Pixel phones came with unlimited original quality photo backup as long as the photos were uploaded from your phone. At this point I don't think you can recover your photos unless you find a way to fix the boot loop. Your boot loop where it didn't happen immediately after the update and it allows you into safe mode briefly sounds kind of unusual and might be the result of a hardware problem on your phone rather than a software issue. Have you tried booting the phone up while it is plugged into a wall outlet to see if that makes any difference? Some people with boot loop issues on the Pixels have reported that allowing the battery to completely run down until the phone is dead and then plugging the phone into a wall outlet allowed them to boot up normally. If you try that maybe you will get lucky but your options are very limited at this point.
I have a unlocked bootloader EVR-AL00 that has been bricked for awhile now. TWRP is stuck on load screen on erecovery and recovery. I have tried everything to get it to work. I can get to the bootloader screen and flash from Hstool, Funkyhuawei, ADB and Hisuite but it always goes back to the TWRP load screen and stays there. TWRP crashed on me back then and now it seems EMUI is gone forever. Any new tricks out there that might work? Please help if you can! Thank you!
can flash stock recovery via adb?
Which Firmware version is on it?
letschky said:
can flash stock recovery via adb?
Which Firmware version is on it?
Click to expand...
Click to collapse
910120. I've tried that. It seems to flash without errors then boots to the TWRP load screen and freezes...
Steamer2499 said:
910120. I've tried that. It seems to flash without errors then boots to the TWRP load screen and freezes...
Click to expand...
Click to collapse
After flash Stock Recovery can boot into Erecovery?
Power off wait for 10 seconds
Press and hold Volume up and put in the usb cable.
Hold Volume up until you start the Erecovery
letschky said:
After flash Stock Recovery can boot into Erecovery?
Power off wait for 10 seconds
Press and hold Volume up and put in the usb cable.
Hold Volume up until you start the Erecovery
Click to expand...
Click to collapse
That doesn't work either
There is only one wat I came back from the TWRP cycle of death.
I followed the steps for the side load in the OP of this thread. The bottom of the first post.
https://forum.xda-developers.com/mate-20-x/how-to/fw-emui-9-1-0-123-evr-al00-t3935995
The update is listed and can be renamed (I used the 123 update_full_base.zip)
The nocheck.img was a challenge, but I found one in a TWRP backup I had done and save off. Doing a search of XDA later I see that there is also versions in the Mate 20 pro and Mate 10 forums.
Now I have a normal eRecovery, but I cannot obtain root and the recovery StockAL00, magiskAL00 amd newer images changed in bootloader don't seem to make a difference.
Rudolpht said:
There is only one wat I came back from the TWRP cycle of death.
I followed the steps for the side load in the OP of this thread. The bottom of the first post.
https://forum.xda-developers.com/mate-20-x/how-to/fw-emui-9-1-0-123-evr-al00-t3935995
The update is listed and can be renamed (I used the 123 update_full_base.zip)
The nocheck.img was a challenge, but I found one in a TWRP backup I had done and save off. Doing a search of XDA later I see that there is also versions in the Mate 20 pro and Mate 10 forums.
Now I have a normal eRecovery, but I cannot obtain root and the recovery StockAL00, magiskAL00 amd newer images changed in bootloader don't seem to make a difference.
Click to expand...
Click to collapse
I can't get into TWRP. It is frozen on load screen
Steamer2499 said:
I can't get into TWRP. It is frozen on load screen
Click to expand...
Click to collapse
Damn, that's worse than I had it. I don't know if there is a way to HStool or modified HiSuite take a ROM update, which would return you to regular eRecovery.
I'm hoping that can work if you can Fastboot from bootloader through those steps or HiSuite recovery.
With my crazy sideload I cannot root, I get prompted for updates constantly (with updates set off) and HStool & HiSuite didn't work. Since I don't have root cannot do ENMUI flasher.
Rudolpht said:
Damn, that's worse than I had it. I don't know if there is a way to HStool or modified HiSuite take a ROM update, which would return you to regular eRecovery.
I'm hoping that can work if you can Fastboot from bootloader through those steps or HiSuite recovery.
With my crazy sideload I cannot root, I get prompted for updates constantly (with updates set off) and HStool & HiSuite didn't work. Since I don't have root cannot do ENMUI flasher.
Click to expand...
Click to collapse
To bad there's not a patch for TWRP...
I know there are some smart people out there that could tell me how to un-brick my phone
@ajsmsg78 is the smartest one I know on here. He has flashed stock, RR, etc... I bought his phone so he doesn't have one anymore but maybe he knows how to help you.
CCJ22 said:
@ajsmsg78 is the smartest one I know on here. He has flashed stock, RR, etc... I bought his phone so he doesn't have one anymore but maybe he knows how to help you.
Click to expand...
Click to collapse
I spent some time in pm trying to help him but the phone still won't do what it's supposed to. I think he needs to do a data format but he can't get into twrp to do it and Huawei blocks a lot of adb commands.
ajsmsg78 said:
I spent some time in pm trying to help him but the phone still won't do what it's supposed to. I think he needs to do a data format but he can't get into twrp to do it and Huawei blocks a lot of adb commands.
Click to expand...
Click to collapse
Sh*t if you can't help him it's not looking good.
So here's the story, TL;DR at bottom.
So I have been checking out gaming phones for a little bit and saw the RedMagic 6 Pro and was captivated by its glowing RGB, 16GB of RAM, high refresh screen, a delicate and strange but mighty internal fan and A BATTERY THAT WOULD LAST ME ALL DAY.
So naturally I ordered the phone as soon as it launched in NA and waited about a week and before I got it. Once I did, it was like Willy Wonka and I was Charlie with a golden ticket.
At first I didn't notice anything wrong, maybe these glitches were there all along and I just never noticed it. After some steady usage, I started noticing little things here and there that were annoying, like the app switcher not opening sometimes, not closing apps, notifications not showing, misspelled words in the Settings app. You know, annoying stuff like that.
Obviously I tried to do factory resets a couple times to see if it would help but nothing fixed it so my conclusion was that something was wrong with the software itself.
My next idea was to download and try to I guess manually update the phone in hopes that that would also reload part of the system...¯\_(ツ)_/¯
Went to the global rom page on redmagic.gg>downloaded the rom to my computer that matched my phone model>factory reset the phone>copied update over>manual install through settings>phone says installing... whatever>then reboots to the RedMagic boot logo and never goes from there.
So now I'm sitting here, clearly devastated by the loss of my little pocket heater, my side table light show, my phone I use to cheat on Apple and iPhone with (shh don't tell Siri).
Things I've already tried>
1) More factory resets through the recovery
2) Letting the battery die and then charging it.... ¯\_(ツ)_/¯
3) extracting .img from payload update file and flashing through fastboot (always fails due to locked bootloader)
4) Reaching out to Nubia support, I don't think they like me because they haven't answered back yet.
TL;DR -- Is there a way to unbrick/reflash the 6 or 6 Pro with a locked bootloader yet?
waiting for same thing.... quite sad that i can't use my phone just from an update
Yeah, there is a number of us in the same position. We could start a club. The really expensive paperweight club or something. I've also reached out to support. They asked a couple of questions, I promptly answered, and thin it's been crickets since.
Are you unable to unlock the bootloader?
chocolote4444 said:
Are you unable to unlock the bootloader?
Click to expand...
Click to collapse
yes my phone open bootlooder
chocolote4444 said:
Are you unable to unlock the bootloader?
Click to expand...
Click to collapse
No I never really got a chance to do it and now since I can't boot, I can't unlock it.
my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file
shakhawat1993 said:
my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file
Click to expand...
Click to collapse
Are you unlocked? Did you flash anything?
CyberWolf92 said:
So here's the story, TL;DR at bottom.
So I have been checking out gaming phones for a little bit and saw the RedMagic 6 Pro and was captivated by its glowing RGB, 16GB of RAM, high refresh screen, a delicate and strange but mighty internal fan and A BATTERY THAT WOULD LAST ME ALL DAY.
So naturally I ordered the phone as soon as it launched in NA and waited about a week and before I got it. Once I did, it was like Willy Wonka and I was Charlie with a golden ticket.
At first I didn't notice anything wrong, maybe these glitches were there all along and I just never noticed it. After some steady usage, I started noticing little things here and there that were annoying, like the app switcher not opening sometimes, not closing apps, notifications not showing, misspelled words in the Settings app. You know, annoying stuff like that.
Obviously I tried to do factory resets a couple times to see if it would help but nothing fixed it so my conclusion was that something was wrong with the software itself.
My next idea was to download and try to I guess manually update the phone in hopes that that would also reload part of the system...¯\_(ツ)_/¯
Went to the global rom page on redmagic.gg>downloaded the rom to my computer that matched my phone model>factory reset the phone>copied update over>manual install through settings>phone says installing... whatever>then reboots to the RedMagic boot logo and never goes from there.
So now I'm sitting here, clearly devastated by the loss of my little pocket heater, my side table light show, my phone I use to cheat on Apple and iPhone with (shh don't tell Siri).
Things I've already tried>
1) More factory resets through the recovery
2) Letting the battery die and then charging it.... ¯\_(ツ)_/¯
3) extracting .img from payload update file and flashing through fastboot (always fails due to locked bootloader)
4) Reaching out to Nubia support, I don't think they like me because they haven't answered back yet.
TL;DR -- Is there a way to unbrick/reflash the 6 or 6 Pro with a locked bootloader yet?
Click to expand...
Click to collapse
could you please tell me your process, how did you try to flash ? my bootloader is unlocked even though I could not flash with .img file, everytime it's showing - FAILED (no such partition)
numbawon said:
Are you unlocked? Did you flash anything?
Click to expand...
Click to collapse
yes ,phone is unlocked, when i go for flashing with miflash, no .img file showing, or /and to install twrp,its showing no such partition
numbawon said:
Are you unlocked? Did you flash anything?i
Click to expand...
Click to collapse
i unlocked bootloader. i flash twrp after that it stuck on fastboot mode
shakhawat1993 said:
i unlocked bootloader. i flash twrp after that it stuck on fastboot mode
Click to expand...
Click to collapse
Where is everybody getting TWRP? I don't think there is one yet for the 6 yet. Not till there is kernel source available.
I have the rom extracted here for both the EU and NA/Asia releases. In each is an output folder. You need to flash the boot.img.
in Treble based roms the boot and recovery are in the boot.img. So you flashed over the whole boot image with TWRP that isn't working for the 6 yet, so it defaults to fastboot.
numbawon said:
Where is everybody getting TWRP? I don't think there is one yet for the 6 yet. Not till there is kernel source available.
I have the rom extracted here for both the EU and NA/Asia releases. In each is an output folder. You need to flash the boot.img.
in Treble based roms the boot and recovery are in the boot.img. So you flashed over the whole boot image with TWRP that isn't working for the 6 yet, so it defaults to fastboot.
Click to expand...
Click to collapse
i flashed with redmagic 5g twrp on my redmagic 6 pro. my bad
shakhawat1993 said:
i flashed with redmagic 5g twrp on my redmagic 6 pro. my bad
Click to expand...
Click to collapse
You have been very bad. You will be punished. *invites in the scary nurse with the big paddle*
@shakhawat1993 see this other post as it explains some more in it just in case it's helpful.
shakhawat1993 said:
my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file
Click to expand...
Click to collapse
i was in same situation like you,,start RM6 only on fastboot but thie works ,download you rom from this page https://drive.google.com/drive/mobile/folders/1BE4FSGDcfXavYoJ3Kw3toGMiPHgCGakC?usp=sharing
extract boot.img to your folder with fastboot
start mobile in fastboot
and open cmd.
fastboot device
if you see your device try next command
fastboot flash boot boot.img
restart your phone and you have stock recovery,,wipe data and you have unbricked device
i download latest twrp but not working and after install twrp i was stucked in fast boot like you
I pulled apart the RM5 unbrick tool to see if I can learn anything that might help us that are stuck at the logo screen. So obviously this contains the RM5 rom right now.
It contains all the firehose files and script and such and obviously the image to the RM5. I was looking into if it could be used to recover the RM6. I've been slammed at work and not been able to dig into it as I'd like, but i have it located here if anybody wants to dig into it too.
numbawon said:
I pulled apart the RM5 unbrick tool to see if I can learn anything that might help us that are stuck at the logo screen. So obviously this contains the RM5 rom right now.
It contains all the firehose files and script and such and obviously the image to the RM5. I was looking into if it could be used to recover the RM6. I've been slammed at work and not been able to dig into it as I'd like, but i have it located here if anybody wants to dig into it too.
Click to expand...
Click to collapse
It would great if can just replace those system, recovery, boot etc in folder, then boom it works lol...
Nocturne Seigneur said:
It would great if can just replace those system, recovery, boot etc in folder, then boom it works lol...
Click to expand...
Click to collapse
That's what I was hoping for but worried it's going to take more than just that, like the GPT layout and some other things.
For sure you will need the partition table, rawprogram, & a firehose for the SD888; I'd be surprised if the one for the RM5 would work on the RM6.
Hello,
In the rush of flashing the january update I've flashed by mistake the Pixel 5 image bootloader (my wife's phone)
Yest that's stupid, I've done this every months for years with several Pixel phones, but I was listening to music at the same time and did dl the wrong image...
Anyway my phone is now hard bricked but I'm sure there must be a way to enter the other bootlader slot and/or entering a special recovery tool.
I cannot enter bootloader anymore
Requesting some help as I'd avoid to send it for a reflash...
Thanks !
Try: https://pixelrepair.withgoogle.com/carrier_selection
(I've never personally used this)
foobar66 said:
Try: https://pixelrepair.withgoogle.com/carrier_selection
(I've never personally used this)
Click to expand...
Click to collapse
Unfortunately the phone is supposed to have a working bootloader
Thibale said:
Unfortunately the phone is supposed to have a working bootloader
Click to expand...
Click to collapse
Ouch ...
Thibale said:
Unfortunately the phone is supposed to have a working bootloader
Click to expand...
Click to collapse
Android Flash Tool
flash.android.com
Also doesn't work?
Morgrain said:
Android Flash Tool
flash.android.com
Also doesn't work?
Click to expand...
Click to collapse
Nope...
Thibale said:
Nope...
Click to expand...
Click to collapse
Can you still access Fastboot Mode?
(pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back)
Morgrain said:
Can you still access Fastboot Mode?
(pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back)
Click to expand...
Click to collapse
No that's the problem.
But there are 2 bootloader slots (a and b) and I'm pretty sure there is way to switch from one to another with a special tool or button sequence.
I've already tried many button combinaison with no luck.
This kind of error is so stupid that I hope there is a way to force a rescue bootloader or something on boot.
yes but you need to be able to communicate with your phone from your pc.....if you cant access fastboot then how will you change partition?
Thibale said:
No that's the problem.
But there are 2 bootloader slots (a and b) and I'm pretty sure there is way to switch from one to another with a special tool or button sequence.
I've already tried many button combinaison with no luck.
This kind of error is so stupid that I hope there is a way to force a rescue bootloader or something on boot.
Click to expand...
Click to collapse
The only special tools we have are either the pixel repair tool or the android flash tool. If both can't get you fastboot / firmware flashing, that's it. Hardbrick. Google Pixels don't have "special" hardbrick solving tools, like older OnePlus had. You need to contact Google.
Ok I'll get in touch with my local reseller on Monday then...
Thibale said:
Ok I'll get in touch with my local reseller on Monday then...
Click to expand...
Click to collapse
Do you remember what went wrong?
EDIT: Uh, never mind. So you accidentally used the P5 fw. Why on hell would the device accept the P5 fw at all?!
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
WOW. So even holding volume down and power until you see the fastboot screen wont work? sometimes you have to hold it for a while. I say that because when the December firmware came out I accidentally flashed the wrong region but was able to access bootloader and so was able to rescue myself. So sorry dude. That really sucks.
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
Yes worst case we'll have for repair but they could have implemented a simple device id check on their script prior flashing anything, especially for the bootloader.
Anyway, I'm alive, in a good health and it's just a phone
niko26 said:
Do you remember what went wrong?
EDIT: Uh, never mind. So you accidentally used the P5 fw. Why on hell would the device accept the P5 fw at all?!
Click to expand...
Click to collapse
You can flash gobbledygook to your phone if you're not careful. You can flash a non-Google phone's image. Flashing just flashes what you tell it to flash.
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
That sucks. I'm sure you know now, always go straight to the source for everything if possible, firmware, platform tools, drivers, BIOS / UEFI (for computer).
SDK Platform Tools
Get the Google USB Driver
Pixel 6 Pro Factory Images
You can also Google for official pixel firmware and the top search result is what the want. I know it doesn't help you now. Good luck with your phone!
Morgrain said:
After having played around with the January patch (came from December Europe A4 firmware that was pulled), it seems that the FP scanner got even faster and more reliable, even though it's not stated in the patchnotes. Maybe it's just placebo.
Click to expand...
Click to collapse
So many folks have reported the exact same thing, I'm really, really curious just how much faster it will seem when I get around to updating.
roirraW edor ehT said:
So many folks have reported the exact same thing, I'm really, really curious just how much faster it will seem when I get around to updating.
Click to expand...
Click to collapse
I noticed how faster it was before I saw everyone else posting about it, so at least no placebo on my end. Hope you find the same.
I know that you tried to get into Fastboot. Pixel 6/6P also has a Recovery mode. I can get to it from a working phone.
I would think that there is someway to boot into Recovery mode from a dead phone via button combos.
Thibale said:
Hello,
In the rush of flashing the january update I've flashed by mistake the Pixel 5 image bootloader (my wife's phone)
Yest that's stupid, I've done this every months for years with several Pixel phones, but I was listening to music at the same time and did dl the wrong image...
Anyway my phone is now hard bricked but I'm sure there must be a way to enter the other bootlader slot and/or entering a special recovery tool.
I cannot enter bootloader anymore
Requesting some help as I'd avoid to send it for a reflash...
Thanks !
Click to expand...
Click to collapse
Hy, how did you flashed? Via adb sideload or?
vrda08 said:
Hy, how did you flashed? Via adb sideload or?
Click to expand...
Click to collapse
factory image with modified flash-all.bat
I'll do the exact same process when I'll get my phone back but this time I'll check the image name at least 3 times