Okay, I'll admit that I'm a little OCD, so this probably bugs me more than most. If you unlock the bootloader on the Mi A2 Lite, you get a warning with a typo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, I hate these warning splashes enough without the glaring typo.
Anyone have a suggestion on how to eliminate the warning or add the space between "can'tbe"?
That is all ok. Thay just informed you that your BL is unlocked. Because it's lower security when unlocked.
Magendanz said:
Okay, I'll admit that I'm a little OCD, so this probably bugs me more than most....
Anyone have a suggestion on how to eliminate the warning or add the space between "can'tbe"?
Click to expand...
Click to collapse
Already tried figuring this out here but got nowhere. Apparently nobody but you & me are the only ones that don't like the warning.
You could try this method if you no longer need the OTA support http://4pda.ru/forum/index.php?showtopic=913716&st=1720#entry79136854
You can view the page in English via google translate.
Mi A2 Lite cihazımdan Tapatalk kullanılarak gönderildi
dedebekri said:
You could try this method if you no longer need the OTA support http://4pda.ru/forum/index.php?showtopic=913716&st=1720#entry79136854
You can view the page in English via google translate.
Mi A2 Lite cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
fastboot erase splash does in fact erase splash screen. No more unlock warning, just black screen. I'm sure this voids ota support. Thank you for sharing
Edit
So erasing splash seems to effect fastboot screen, as it is now black, lol... Hopefully it still connects, I did make a backup of splash so maybe I can restore.. I'll post back later, but would not suggest following my lead lol
Edit 2
Flashing stock splash.img restored message and fastboot screen, back to normal. Fastboot commands did work on the black screen
Magendanz said:
Okay, I'll admit that I'm a little OCD, so this probably bugs me more than most. If you unlock the bootloader on the Mi A2 Lite, you get a warning with a typo
Now, I hate these warning splashes enough without the glaring typo.
Anyone have a suggestion on how to eliminate the warning or add the space between "can'tbe"?
Click to expand...
Click to collapse
hossman said:
fastboot erase splash does in fact erase splash screen. No more unlock warning, just black screen. I'm sure this voids ota support. Thank you for sharing
Edit
So erasing splash seems to effect fastboot screen, as it is now black, lol... Hopefully it still connects, I did make a backup of splash so maybe I can restore.. I'll post back later, but would not suggest following my lead lol
Edit 2
Flashing stock splash.img restored message and fastboot screen, back to normal. Fastboot commands did work on the black screen
Click to expand...
Click to collapse
OK
So followed this
https://forum.xda-developers.com/mi-a1/themes/tool-tissot-splash-maker-mod-5-pngs-t3799701
used the tool and the message is gone, there is a short period the screen is just black but there is a nice drop down animation to android one screen and it boots normally. The fastboot/bootloader screen shows linux penguin, fastboot commands working.
I think this may be the best at the moment solution to removing unlock warning
If anyone wants to try, I could try and upload the splash.img i flashed - let me know
hossman said:
OK
So followed this
https://forum.xda-developers.com/mi-a1/themes/tool-tissot-splash-maker-mod-5-pngs-t3799701
used the tool and the message is gone, there is a short period the screen is just black but there is a nice drop down animation to android one screen and it boots normally. The fastboot/bootloader screen shows linux penguin, fastboot commands working.
I think this may be the best at the moment solution to removing unlock warning
If anyone wants to try, I could try and upload the splash.img i flashed - let me know
Click to expand...
Click to collapse
Did you actually try to make your own splash.img, or did you just flash the one provided in the first post you linked to? I previously followed the same link you provided, and tried using my own pictures, but my splash image turned out to be a black screen with the linux penguin. The bootloader image was the STD Xiaomi image but squashed and distorted. I wound up reflashing the stock splash.img.
mn1968 said:
Did you actually try to make your own splash.img, or did you just flash the one provided in the first post you linked to? I previously followed the same link you provided, and tried using my own pictures, but my splash image turned out to be a black screen with the linux penguin. The bootloader image was the STD Xiaomi image but squashed and distorted. I wound up reflashing the stock splash.img.
Click to expand...
Click to collapse
In the files for the tool are included 5 stock png images, I just replaced the one with the warning screen and ran the tool. The splash.img definitely didn't flash the desired images but to me it looks more appropriate than when I just erased splash. I'm guessing someone that actually knows what they are doing can modify that splash.img correctly
@hossman
OK. Thanks. Sounds like pretty much what I tried. Not sure why you got the linux penguin on fastboot when I got it at startup though. What's weirder is that the penguin picture isn't even one of the five pictures included in the tool.
Maybe I'll try agian when I get some free time.
I had the same problem with my unlocked Moto G years back and I just replaced the white unlocked bootloader image with a new animated one. It was pretty easy and didn't effect the fastboot screen at all. Maybe I give it a try as well.
Sent from my Phh-Treble vanilla using Tapatalk
Related
OK so I've looked through the forum (admittedly the Galaxy Nexus specific one only) and tried some searches but may not be able to articulate this problem in clear way. Basically, I'm continuously crashing - started with a stock, but unlocked/rooted install. Now it won't boot and crashes in the boot loader as well after a few seconds (thus not allowing any non-trivial actions to actually complete.)
The first crash was after enabling face unlock for the first time. When I hit the power button to shut things off, the display "tore" and then went totally dark. Phone was completely unresponsive till I pulled the battery for a few minutes (found that one from search.) Couldn't complete a boot sequence though - would go to the animation, then display would go wonky and then shut down. Would usually have to pull battery again to get any response from that.
Went to recovery mode and wiped data - which completed - same problem on boot. Only thing I'd done was unlock and root (for eventual root apps, none of which had been run) so decided to undo that (using "Galaxy Nexus Root Toolkit 1.3.") On the factory restore there are several steps (boot loader, radio, etc.) and I haven't been able to complete that process.
I suspect it might even be bad hardware at this point, but can't go back to VZW with the phone still showing unlocked. Phone is a recent eBay purchase to replace a lost device but seemed fine for the 2-3 days I used before this all started.
Anyone seen something like this before?
So your able to get into recovery still? If it doesn't boot into the os it's probably a compatibility error between the kernel and rom your using (Just clearning data in recovery won't fix this).
So what rom/kernel combination were you using at the time?
Also have you tried flashing a completely different custom rom to the one your having issues with.
And any nandroid backups you have made in the past?
What's weird is that I was in stock kernel / rom at the time. (At least I'm nearly sure - it did come from eBay after all...)
I'll also try changing the ROM, that could be it. The big question is if that can complete before the thing melts. If I boot to recovery and wait, doing nothing, the system crashes in a minute or two.
My current thinking is that I might have a bad recovery / clockwork mod install.
can you still get to the bootloader and is it stable to sit on the bootloader?
I can get to the boot loader but it is not stable there (I think I was conflating the two.)
does your bootloader look like this? i want to make sure you and i are talking about the same thing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yep, that's the one (before it crashes. I have a pic of the amusing video display when it does that I'll put up when I hit the magic 8 posts...)
try using ODIN to restore your phone. instructions are found here: http://forum.xda-developers.com/showthread.php?t=1394051
also, how long can you sit on the bootloader before it crashes?
I'll try that as tonight - thanks!
Varies on time to crash, but no less than 30 seconds and no more than 5 minutes so far. Requires a battery pull and wait to come back after that.
i would like to see the picture of the crash you are talking about.
also, you can relock the bootloader real fast before you take it to VZW. only takes 1 command once you get to the bootloader
fastboot oem lock
Wow, same crash while in download mode. That can't be good...
yeah thats not good at all. i'd lock the bootloader and return it
http://dulinor.smugmug.com/photos/i-XkKWCrg/0/S/i-XkKWCrg-S.jpg
This is the crash I'm seeing
Yeah return to the store and show them this, the board is probably bad.
thats rough, but since you got it on ebay returning it may be a hassle and if the phone is not a north american model samsung might not even accept it for warranty.
did you try to flash the stock google image using fastboot instead of using the toolkit? it will only take a few mins. when you display crash like that does it still take commands from fastboot? you can test it when the display crash like that type in fastboot devices and see if you get the id number in command prompt. if your build was yakju then you can get the factory images from here http://code.google.com/android/nexus/images.html
Just got back from the store - they issued a replacement, none on hand so one should ship out today. (Thanks for the tip on re-locking it - not sure if they checked, but was happier having that.)
So of course, it actually completed booting (for the first time) but crashed during activation. Once they saw it crash on the Odin screen, they were happy to do the swap.
I had been trying to re-flash OEM Google - which it should have been all along.
Thanks everybody for your help.
Hi,
I'm looking for some help with my currently unusable HTC One M8 on EE in the UK. I have done no rooting or making my phone S-OFF to date (and don't have the appetite for it if I'm honest) but it is now stuck in a boot loop and I don't know how to fix it.
On Monday, I accepted an OTA update which seemed to go fine but the reboot then triggered off an update to HTC Lock Screen App. This requested permission to reboot the phone and since then, the phone has been in a constant boot loop. I have tried various options including going into the menu system and selecting 'Recovery' and 'Factory Reset'. None of these options appear to do anything as the screen blanks for a moment and comes back up with the HTC initial screen and then goes into its loop. What does seem odd is that when I go into the recovery area, the menu system is unresponsive to the volume buttons until a series of code lines come up (IMAG1838.jpg)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
which takes some time to cycle through. Once completed, I can then select things like 'FASTBOOT' (IMAG1840.jpg) . Picture IMAG1839.jpg is the only screen I see if i try and reboot/recover anything. I don't know if it means anything to anyone but I also took a pic of the 'IMAGE CRC' (IMAG1841.jpg) .
Can anyone help me resolve this without rooting or voiding my warranty? EE suggested speaking to HTC as they didn't have any ideas or they could send my phone away for repair. This is an option but would rather resolve myself (with help!) if I can.
Although I'm reasonably clued up on general operations of phones, the bare bones of software is a different planet so any assistance will need to be in baby steps and spoon fed (sorry).
Hope the pictures are ok? If not, I can type out the various messages.
Thanks in advance.
Phil
did you Factory Reset while at fastboot mode?
Factory Reboot
aM- said:
did you Factory Reset while at fastboot mode?
Click to expand...
Click to collapse
Hi,
Yes - I did try a factory reset but this didn't resolve the problem and it literally rebooted immediately without appearing to do anything.
Thanks
Phil
PhillipLegg said:
Hi,
I'm looking for some help with my currently unusable HTC One M8 on EE in the UK. I have done no rooting or making my phone S-OFF to date (and don't have the appetite for it if I'm honest) but it is now stuck in a boot loop and I don't know how to fix it.
On Monday, I accepted an OTA update which seemed to go fine but the reboot then triggered off an update to HTC Lock Screen App. This requested permission to reboot the phone and since then, the phone has been in a constant boot loop. I have tried various options including going into the menu system and selecting 'Recovery' and 'Factory Reset'. None of these options appear to do anything as the screen blanks for a moment and comes back up with the HTC initial screen and then goes into its loop. What does seem odd is that when I go into the recovery area, the menu system is unresponsive to the volume buttons until a series of code lines come up (IMAG1838.jpg) View attachment 2966734 which takes some time to cycle through. Once completed, I can then select things like 'FASTBOOT' (IMAG1840.jpg) View attachment 2966736. Picture IMAG1839.jpg View attachment 2966735is the only screen I see if i try and reboot/recover anything. I don't know if it means anything to anyone but I also took a pic of the 'IMAGE CRC' (IMAG1841.jpg) View attachment 2966747.
Can anyone help me resolve this without rooting or voiding my warranty? EE suggested speaking to HTC as they didn't have any ideas or they could send my phone away for repair. This is an option but would rather resolve myself (with help!) if I can.
Although I'm reasonably clued up on general operations of phones, the bare bones of software is a different planet so any assistance will need to be in baby steps and spoon fed (sorry).
Hope the pictures are ok? If not, I can type out the various messages.
Thanks in advance.
Phil
Click to expand...
Click to collapse
Try powering down, then holding power up+power for 20 seconds. This is the equivalent of a battery pull.
Might work, might not. Give it a shot.
Then report back. I/someone might come up with a different solution if it doesn't work for you.
Battery Pull
xunholyx said:
Try powering down, then holding power up+power for 20 seconds. This is the equivalent of a battery pull.
Might work, might not. Give it a shot.
Then report back. I/someone might come up with a different solution if it doesn't work for you.
Click to expand...
Click to collapse
Hi, it was a good idea - but unfortunately this hasn't resolved the problem. Sounds like it's going away for repair unless any other forum users have a stroke of inspiration. It does feel like something has overwritten or corrupted the bootup code somehow!! At least it doesn't feel like anything I've done so warranty is still in place
Thanks for your help.
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
vagifn said:
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
Click to expand...
Click to collapse
See http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203.
Post #16 describes how get into recovery from the 'no command' screen, and my post #12 describes how I managed to get it flashed using the SP Flashtool.
(Note my point no,5 - all I needed to do is press 'Download' first, THEN attach the powered off phone.)
Good luck!
kevvyboy said:
See http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203.
Post #16 describes how get into recovery from the 'no command' screen, and my post #12 describes how I managed to get it flashed using the SP Flashtool.
(Note my point no,5 - all I needed to do is press 'Download' first, THEN attach the powered off phone.)
Good luck!
Click to expand...
Click to collapse
Thanks a lot fot pointing this out.
Managed to get the recovery options menu.
However wiping the cache didn't help.
After doing the "root integrity check" got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
do you think this can be fixed w/o reflashing an entire rom?
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
kevvyboy said:
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
Click to expand...
Click to collapse
Sad... anyway would you please direct me to where I can download the flash tool and stock ROM? Thanks.
kevvyboy said:
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
Click to expand...
Click to collapse
Actually, what you need to do is format the data partition or write the empty data.img file over the data partition which in effect does the same thing. And the later one is also what happens when your download entire rom using sp flash.
pitrus- said:
Actually, what you need to do is format the data partition or write the empty data.img file over the data partition which in effect does the same thing. And the later one is also what happens when your download entire rom using sp flash.
Click to expand...
Click to collapse
I've proceeded with "wipe data/factory reset" option - no effect...or are we talking about different things?
vagifn said:
I've proceeded with "wipe data/factory reset" option - no effect...or are we talking about different things?
Click to expand...
Click to collapse
In that case you probably need to flash the system.img and maybe even the boot.img from the latest rom. Elephone really should stop sending out these broken OTAs...
pitrus- said:
In that case you probably need to flash the system.img and maybe even the boot.img from the latest rom. Elephone really should stop sending out these broken OTAs...
Click to expand...
Click to collapse
I believe the case is that my phone is rooted and this is not the Elephone team's fault...anyways thanks for trying to help me.
vagifn said:
I believe the case is that my phone is rooted and this is not the Elephone team's fault...anyways thanks for trying to help me.
Click to expand...
Click to collapse
You belive this b***** that feed you on official forum? OTA should work on any device software config.
ruonim said:
You belive this b***** that feed you on official forum? OTA should work on any device software config.
Click to expand...
Click to collapse
I didn't read official forum. However you do loose your warranty if device is rooted, thus the device manufacturer owes you nothing. OTA worked fine before I rooted my device.
Btw, I got my phone back to life by re-flashing the entire ROM, just in case.
Hello my friend
vagifn said:
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
Click to expand...
Click to collapse
The only thing you need to do is reinstall the añl the system with spflashtool. Never and remember never you can update any android with a ota if you are a rooted user.
If you speak spanish you can search in the youtube channel AndroidMxL to ser how you can reinstall the original ROM on your android.
allianzcred said:
The only thing you need to do is reinstall the añl the system with spflashtool. Never and remember never you can update any android with a ota if you are a rooted user.
If you speak spanish you can search in the youtube channel AndroidMxL to ser how you can reinstall the original ROM on your android.
Click to expand...
Click to collapse
Already did, thanks. Will never combine Root and OTA together again
Hi all, i have a massive problem. I was using FreedomOS 1.6 [OOS 3.2.7] Rom and went to boot into twrp 3.0.2-0 and now i have no recovery phone doesnt boot, i can boot into fastboot/bootloader mode, i have flashed twrp again and it still dosent boot into recovery.
Please guys this is so frustrating any help is MASSIVELY appreciated
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Follow this:
http://forum.xda-developers.com/showpost.php?p=69141963&postcount=5
kgs1992 said:
Follow this:
http://forum.xda-developers.com/showpost.php?p=69141963&postcount=5
Click to expand...
Click to collapse
still no luck. still boots to a screen saying boot:failed recovery:failed
phonetech101 said:
still no luck. still boots to a screen saying boot:failed recovery:failed
Click to expand...
Click to collapse
I'd the same problem look there, solved by following @kgs1992 instructions !
keviiin38 said:
I'd the same problem look there, solved by following @kgs1992 instructions !
Click to expand...
Click to collapse
still no luck, bootloader is locked and i cant boot phone to enable oem unlock ****kkkkkkkkk
phonetech101 said:
still no luck, bootloader is locked and i cant boot phone to enable oem unlock ****kkkkkkkkk
Click to expand...
Click to collapse
Did you tried @kgs1992 answer ?
kgs1992 said:
Follow this:
http://forum.xda-developers.com/showpost.php?p=69141963&postcount=5
Click to expand...
Click to collapse
i have same problem and my phone now on bootloop how can i fix it
please help us
keviiin38 said:
Did you tried @kgs1992 answer ?
Click to expand...
Click to collapse
nope once bootloader is locked and phone cant boot into system to turm oem unlocking on ur stuffed, so i have a useless phone but open to more suggestions.
phonetech101 said:
nope once bootloader is locked and phone cant boot into system to turm oem unlocking on ur stuffed, so i have a useless phone but open to more suggestions.
Click to expand...
Click to collapse
Relocking was a bad idea, you just ran out of all options.
I'm not sure if there is any way around enabling OEM unlocking.
Try the previous suggestion.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Snapdragons are truly unbrickable. But I'm not sure I know enough to help.
kgs1992 said:
Relocking was a bad idea, you just ran out of all options.
I'm not sure if there is any way around enabling OEM unlocking.
Try the previous suggestion.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Snapdragons are truly unbrickable. But I'm not sure I know enough to help.
Click to expand...
Click to collapse
did it again, cant boot into recovery. tried "fastboot boot recovery.img came back with
error (remote: unlock device to use this command"
this is what it boot loops to and from
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
this is what i see when i boot up
I'm fairly sure fastboot boot <image> doesn't even work if the bootloader is unlocked on the op3.
Also, it looks like recovery did get flashed.
Try rebooting to recovery?
Power off by holding power button, then hold vol down + power.
Then if you are booted into stock recovery, just side load the stock ROM.
kgs1992 said:
I'm fairly sure fastboot boot <image> doesn't even work if the bootloader is unlocked on the op3.
Also, it looks like recovery did get flashed.
Try rebooting to recovery?
Power off by holding volume button, then hold vol down + power.
Then if you are booted into stock recovery, just side load the stock ROM.
Click to expand...
Click to collapse
Na it won't boot into recovery, have flashed stock recovery tried modified recovery tried twrp recovery none off them boot into recovery :/
I wish I could get into recovery then I'm fine from there
Boooommm done it, thanks everyone for your help.
mix-75 said:
i have same problem and my phone now on bootloop how can i fix it
please help us
Click to expand...
Click to collapse
Did you fix yours mate?? I have the fix. Download this https://www.androidfilehost.com/?fid=24591000424942573
Its got the boot.IMG and system.IMG files unlike the others.
This tool can not read my device all tiame no device no device
All drivers is setup on my computer but this tool not read
I have same your screen shoot below
But mype more files is filled, just 3 or 4 file is ok
I hate this problem :crying:
mix-75 said:
This tool can not read my device all tiame no device no device
All drivers is setup on my computer but this tool not read
I have same your screen shoot below
But mype more files is filled, just 3 or 4 file is ok
I hate this problem :crying:
Click to expand...
Click to collapse
My friend I had same problem.
1. Plug phone into computer
2. Turn phone off by holding down power for 40 seconds,
3. Now run unbrick tool with admin.
4. Hold volume up on phone till program reads phone then press start.
So i've been wanting to root this phone for a while now, and i just cant seem to flash twrp, yes its the correct file, yes its the correct command, yes im using SDK developer tools, but i just cant seem to flash it. heres the error btw
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
says its flashing but its not. ive left it on for like an hour or so. please help? anyone?
SzymcioYa said:
So i've been wanting to root this phone for a while now, and i just cant seem to flash twrp, yes its the correct file, yes its the correct command, yes im using SDK developer tools, but i just cant seem to flash it. heres the error btwView attachment 5920083
says its flashing but its not. ive left it on for like an hour or so. please help? anyone?
Click to expand...
Click to collapse
Hi, try using the
Code:
fastboot boot twrp.img
command instead
Jan Skokan said:
Hi, try using the
Code:
fastboot boot twrp.img
command instead
Click to expand...
Click to collapse
oh, i actually solved it actually. im running an amd ryzen 5 5600x and thats the issue. i fixed it using a regedit tweak, thanks tho
Jan Skokan said:
Hi, try using the
Code:
fastboot boot twrp.img
command instead
Click to expand...
Click to collapse
Also, i have a question. So i've rooted my xiaomi note 5 with magisk, and i wanted to do the same with my main phone, and now i cant unlock my phone because i dont want my data lost (the apps are the most important and i have all my other data backed up) and i came across mediatekbootloaderunlock and im just wondering is it patched or does it still work? because if it works then im definitely rooting my phone.
SzymcioYa said:
Also, i have a question. So i've rooted my xiaomi note 5 with magisk, and i wanted to do the same with my main phone, and now i cant unlock my phone because i dont want my data lost (the apps are the most important and i have all my other data backed up) and i came across mediatekbootloaderunlock and im just wondering is it patched or does it still work? because if it works then im definitely rooting my phone.
Click to expand...
Click to collapse
Hi, I'm sorry but I can't confirm or deny this because I don't own a Xioami device anymore You just have to try it 🫤
Jan Skokan said:
Hi, I'm sorry but I can't confirm or deny this because I don't own a Xioami device anymore You just have to try it 🫤
Click to expand...
Click to collapse
It actually worked, and now my phone is unlocked. So i flashed orangefox and i cant seem to boot into it. When i try the combination (power and volume+) it just vibrates and goes back to system. i tried fastboot boot but it didnt work.
SzymcioYa said:
It actually worked, and now my phone is unlocked. So i flashed orangefox and i cant seem to boot into it. When i try the combination (power and volume+) it just vibrates and goes back to system. i tried fastboot boot but it didnt work.
Click to expand...
Click to collapse
This has happened to me too. What I did was that after several attempts I managed to get into twrp and reboot the phone into fastboot via twrp. I know it sounds logical, but try to connect the phone to the computer and hold the power off button and click the volume up button several times. Try it several times, it always works. Via Orange Fox, reboot the phone into fastboot and install the stock rom when you are in fastboot mode. I hope it helps you.. good luck
Jan Skokan said:
This has happened to me too. What I did was that after several attempts I managed to get into twrp and reboot the phone into fastboot via twrp. I know it sounds logical, but try to connect the phone to the computer and hold the power off button and click the volume up button several times. Try it several times, it always works. Via Orange Fox, reboot the phone into fastboot and install the stock rom when you are in fastboot mode. I hope it helps you.. good luck
Click to expand...
Click to collapse
ill try and ill keep you updated
Jan Skokan said:
This has happened to me too. What I did was that after several attempts I managed to get into twrp and reboot the phone into fastboot via twrp. I know it sounds logical, but try to connect the phone to the computer and hold the power off button and click the volume up button several times. Try it several times, it always works. Via Orange Fox, reboot the phone into fastboot and install the stock rom when you are in fastboot mode. I hope it helps you.. good luck
Click to expand...
Click to collapse
nope, doesnt work, tried it tho