Related
You can remove the unlocked bootloader message as well as make some good stuff with a new logo.
Prerequisites :
Unlocked Bootloader
Adb and Fastboot
Some Faith
Steps(ADB/Fastboot Method)
Download the required attachement and unzip it
Copy the logo.bin found inside to the adb root folder
Open terminal in the folder
Enter fastboot mode in phone and plugin the device
Enter fastboot flash logo logo.bin in terminal
Enter fastboot reboot
UPDATED:
V1.Initial Release
Attachement 1
Simple logo with powered by android on it.
Attachement 2
Logo with powered by cyanogenmod on it.
V2. Changelog:
N/A REMOVED
If you have any new ideas to be put in logo. Please tell me....
There's no attachment on the post
Sent from my Moto G (4) using Tapatalk
Fixed...
I tried both both in twrp an got error 6
Sent from my Moto G (4) using XDA-Developers mobile app
Deleted
hazmatkid said:
I tried both both in twrp an got error 6
Sent from my Moto G (4) using XDA-Developers mobile app
Click to expand...
Click to collapse
some fix is to be done on script. meanwhile use adb method. I ve updated the thread.
Thanks for making the custom logos and this thread in particular.
But I'm pretty convinced that changing the logo on xt1644 doesn't do anything other than leave the "N/A" text on a black screen.
Actually nevermind, I was trying to flash the .zip not the .bin like in previous places I've read to do this
How did you made this?
I've tried it before with the same method, but that didn't work!.
This is....
Just want to make my own screens.
The adb method worked great! Thank you. That screen bothered the hell out of me for some reason.
Thanks so much for doing this! One thing I noticed is that there is still the n/a visible when I boot the phone. Is this just me?
ax.xu said:
Thanks so much for doing this! One thing I noticed is that there is still the n/a visible when I boot the phone. Is this just me?
Click to expand...
Click to collapse
Not just you, I can still see it as well.
Anyone got the logo with the warning? I know it may sound weird... but N/A overlaid on the logo bothers me even more than the warning did. Didn't think it would of course, so my bad
Thread updated. N/A Removed.
could you provide us more custom logos? or tutorial of making it?
Could you make it with a black background, eyes burn at night
Thanks for this. But, is there also a way to eliminate the 5 seconds wait during boot due to unlocked bootloader?
I tried this. But still NA is not going. Is there any other alternative??
askreddy2 said:
I tried this. But still NA is not going. Is there any other alternative??
Click to expand...
Click to collapse
try v2
@rahulsnair
You only move the "Moto" a little to the top, didn't you? ^^
So the NA is still there but no longer visible.
Bender1987 said:
@rahulsnair
You only move the "Moto" a little to the top, didn't you? ^^
So the NA is still there but no longer visible.
Click to expand...
Click to collapse
yep. for now.
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Dielahn said:
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Click to expand...
Click to collapse
That simple thread actually gave me an idea. I grabbed the latest SDK tools. Presto!
Note to anyone else with this issue...
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
By the way, the dead Droid is recovery, from that screen, hold power and press up for recovery menu, in case you ever get stuck again
And just for future reference for others who may be in a similar issue and stumble across this thread...
As long as you've successfully unlocked your bootloader and "fastboot devices" successfully pulls up your device, you'll be just fine. You just gotta take a step back, breath and then make sure your SDK tools are updated before moving forward.
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
Make sure you try a different cable to connect your phone to your PC.. I had the same issue, and I try two different cable before my device accepted the flash-all
Okay, so somehow fortunately I was able to get back into my TWRP 1 last time and able to push my files I needed to boot it back up...
Raistline said:
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
Click to expand...
Click to collapse
The funny thing is I was able to and was in bootloader but I couldn't use any commands from my computer (as far as I know) which is why I was freaking out.
I should've but I didn't actually try using other cables. I did try other usb ports but that didn't do anything.
I still kind of believe that my phone (somehow) got messed up from loading TWRP. I don't know if it's because it is still beta or what but I am like 99% sure it was from that as I can't see anything else being the problem.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
Something similar for me but with different reason for starting all this. When I did sideload of 8.1 all went well but my camera wasn't working (I saw the same thing in 8.1 DP) so I needed to go back to 8.0 but you can't sideload downgrade. I went to Google to get replacement sent and figure I might try to sort things out with this one in the meantime. I had to unlock to be able to just flash the factory 8.0 image so did that with both the unlock commands, then after that and after update I just got hung on the white screen with google logo. I was able to get back to bootloader with the power button + volume from off and from there I would get to the screen with the android and the exclamation point - I think you hold volume up and then power to go to sideload. Once there I just sideloaded 8.0 and all was good. I do still get the warning about corrupt whatever and have to hit power on reboot or fresh power up but I could redo the locks and whatnot and all seems fine now with camera working.
At the least I got camera back while waiting for replacement.
b4db0ys said:
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
This cleaned things up for me - still no camera in 8.1 but I got the replacement coming.
So I'm in the same boat as the OP but my bootloader is locked. Am I totally screwed? Is there a way to do any of this when the device won't show up in ADB?
Deuces said:
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
can you just develop some scripts that working on locked bootloader ?
i have a bricked Pixel xl with locked bootloader and oem locked
If you can boot twrp but can't connect to a pc, a type c flash drive comes in handy. Load it with the needed ota, twrp installer zip and Just mount it and you're good to go.
I received my Mi A2 Lite yesterday (yay!). I have unlocked the bootloader and have rooted. I opted not to install TWRP since backups can't be restored. The only issue I have is with the unlocked bootloader...when I boot up I get the warning message that the system has been unlocked. Is it possible to edit the logo.bin with a different image so I (we) don't need to see that anymore? I am coming from a long use of several Moto phones where I could easily create a new logo.bin with a custom picture to hide the unlocked bootloader warning. I used a program called Moto Boot Logo Maker. It appears to be catered to the Moto line but may work with the Xiaomi. If anyone can provide the stock logo.bin I can try editing it. Or at least tell me how to extract the logo.bin from my phone. I tried extracting it with Terminal Emulator but it failed saying the location didn't exist. So what I need to find is the location.
Thanks!
inside stock rom there's a file called splash.img, that i think is the bootimage, but i'm not sure the warning can be removed, i think only the bootimage could be modified.
Also take care of what you are doing because flashing splash may brick your phone in a way that only edl mode can fix.
Let me know if you find a way
I found this for the Xiaomi Mi A1. I replaced image #5 with the same Android One image that starts off the boot animation. I then resized all the images to 1080x2280 to match our device, and had to compress image #2 smaller for the program to run...but it completed without errors and gave me a splash image! I am hesitant to flash it though - the path for most devices appears to be:
/dev/block/bootdevice/by-name/splash
The path for splash image I found is:
/dev/block/platform/soc/7824900.sdhci/by-name/splash
I have included the resulting splash image for anyone brave enough to try. It is NOT flashable. It will have to be done manually through adb or Terminal Emulator.
I haven't been brave enough to flash my "new" splash.img yet. I have extracted the stock splash.img from the stock firmware download and am hoping/trying to find a way to extract/view the files/pictures on it before proceeding. I haven't had any luck using winiamge or other similar programs. Anyone have an idea to open/view the splash.img?
Success...kind of. I flashed the splash.img I posted in post #3. I no longer get the warning to lock the bootloader. Instead it boots up with a dark screen and a small linux penguin...which is really weird because I don't know where that image even came from. I used a white background that said Android One. It's better than the warning image though.
mn1968 said:
Success...kind of. I flashed the splash.img I posted in post #3. I no longer get the warning to lock the bootloader. Instead it boots up with a dark screen and a small linux penguin...which is really weird because I don't know where that image even came from. I used a white background that said Android One. It's better than the warning image though.
Click to expand...
Click to collapse
Lol success!?
mn1968 said:
Success...kind of. I flashed the splash.img I posted in post #3. I no longer get the warning to lock the bootloader. Instead it boots up with a dark screen and a small linux penguin...which is really weird because I don't know where that image even came from. I used a white background that said Android One. It's better than the warning image though.
Click to expand...
Click to collapse
I have already seen that, it happens when spash image is wrong(i think on all qualcomm devices).
ncar123 said:
Lol success!?
Click to expand...
Click to collapse
I said "Kind of"
mac12m99 said:
I have already seen that, it happens when spash image is wrong(i think on all qualcomm devices).
Click to expand...
Click to collapse
Wrong how? What would be needed to make it right?
I have replaced many logo.bin on Moto phones (qualcomm variants). It is easier though with Moto though since there is tool designed specifically for editing Moto logos. The tool I used from the Mi A1 may need to be tailored for the Mi A2 Lite but that is beyond my capability.
Does anyone know any more about how to do this? I found that when I flashed the splash.img from post #3, aside from booting with a black screen with the Linux penguin, it also messes up the image on the fastboot screen (which is nothing special as it is). That being said, fastboot still functions with ADB, just the image on the phone is messed up. I wound up reflashing the stock spash.img and am dealing with the unlocked bootloader message.
mn1968 said:
Does anyone know any more about how to do this? I found that when I flashed the splash.img from post #3, aside from booting with a black screen with the Linux penguin, it also messes up the image on the fastboot screen (which is nothing special as it is). That being said, fastboot still functions with ADB, just the image on the phone is messed up. I wound up reflashing the stock spash.img and am dealing with the unlocked bootloader message.
Click to expand...
Click to collapse
Did you manage to get any further on this? I'm considering to flash your image and get the Linux pinguin, it's better than the warning screen.
Embeeweezer said:
Did you manage to get any further on this? I'm considering to flash your image and get the Linux pinguin, it's better than the warning screen.
Click to expand...
Click to collapse
No. I kind of gave up on this. Maybe one day I'll try again.
mn1968 said:
No. I kind of gave up on this. Maybe one day I'll try again.
Click to expand...
Click to collapse
Yeah, its very annoying. I dont like that super bright white boot animation screen. I would just prefer and easily color invert :good:
I found this on Motorola One forum, it should work with A2 Lite. I didn't test it tho, I don't have unlocked bootloader.
I am using splash.img from
https://translate.googleusercontent...JrhgOvxxsyFr7imjXOCYKUEm6Y9lTRw#entry83388689
Flashed via fastboot, works on Oreo as well.
locovibe said:
I found this on Motorola One forum, it should work with A2 Lite. I didn't test it tho, I don't have unlocked bootloader.
Click to expand...
Click to collapse
I am 99.9% certain that won't work. Moto phones use a logo.bin. The Xiaomi uses a splash.img. FInding a program to edit the splash.img is the problem.
Chrono Leggionaire said:
I am using splash.img from
https://translate.googleusercontent...JrhgOvxxsyFr7imjXOCYKUEm6Y9lTRw#entry83388689[/url]
Flashed via fastboot, works on Oreo as well.
Click to expand...
Click to collapse
Your link goes to a 400 error.
Sorry, it should be fixed now.
Check post #83
Chrono Leggionaire said:
I am using splash.img from
https://translate.googleusercontent...JrhgOvxxsyFr7imjXOCYKUEm6Y9lTRw#entry83388689
Flashed via fastboot, works on Oreo as well.
Click to expand...
Click to collapse
Could you upload it here please ?
Can't download (4PDA 404 error)
No problem, credits to search0123 from 4pda.ru
deleted
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Perchy35 said:
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Click to expand...
Click to collapse
Just use my guide, at the bottom of it it has everything you need to reflash stock firmware hold the power and volume down button until you get to the fastboot/ bootloader screen, also since you replaced the battery and did your own repair we still might not be able to help you because there's to many variables of user interference now, and yes Google kind of has made it a bit more complicated to root devices now unfortunately
Thanks for the reply, please can you put a link to your guide?
Perchy35 said:
Thanks for the reply, please can you put a link to your guide?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Perchy35 said:
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Click to expand...
Click to collapse
Yes. Hold power and volume down, it'll look a few times and catch, you'll see fastboot. The Android guy and red and white text. May take a few loops
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Perchy35 said:
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Click to expand...
Click to collapse
Whats the carrier?
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Here you go. Amazon Jeter Firmware. That's the main folder.
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Spaceminer is correct, once you catch that sweet spot with the phone to get it in bootloader/fastboot mode just flash the firmware and you should hopefully be good to go, if you want it rooted my guide covers that to but let's just get you a working phone first before you try to root lol
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
You can either flash 8 or 9, what I would do is flash 8 then update it to 9 then if you want it rooted root it
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hey so out of curiosity did you get it fixed and working?
ninjakira said:
Hey so out of curiosity did you get it fixed and working?
Click to expand...
Click to collapse
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
Also can I check that without USB debugging selected this method will override and flash still?
Perchy35 said:
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
I am having issue with the last part, getting "The credentials you provided cannot be determined to be authentic" ?
Also can I check that without USB debugging selected this method will override and flash still?
Click to expand...
Click to collapse
Wait what are you needing your Moto id for? The links for the stock firmware are in my guide, just follow the bottom section of it
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Perchy35 said:
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
Click to expand...
Click to collapse
If you don't have the bootloader unlocked then that is something you can do if you want the phone rooted if not you don't have to unlock the bootloader to flash stock firmware
Perchy35 said:
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Click to expand...
Click to collapse
You either didn't install adb minimal or you have a bad cord, type fastboot devices and if nothing pops up saying you have a device in fastboot then it's one of the 2 things I said, extract the contents from the rar or zip file you got from adb minimal download, then install what you extracted
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Perchy35 said:
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Click to expand...
Click to collapse
Sorry been at work and I'm ona break, I totally forgot though you can use Moto smart Assistant for pc to fix this more than likely, so download and useMoto smart Assistant
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.