Related
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Is it a carrier model or a play store
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-ca-bootloader-t3494615
This.
chapelfreak said:
Is it a carrier model or a play store
Click to expand...
Click to collapse
Google store
ASimpleSock said:
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-ca-bootloader-t3494615
This.
Click to expand...
Click to collapse
I see the thread but it doesnt seem like theres a fix in it
tryfont said:
I see the thread but it doesnt seem like theres a fix in it
Click to expand...
Click to collapse
There probably isn't, if you've altered system and relock and toggle OEM unlocking off in dev. options you get bricked.
tryfont said:
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Click to expand...
Click to collapse
Did you try:
fastboot flashing unlock
Since you only relocked, you unlikely toggled "OEM unlock"?!
If it fails, I think you are SOL. Maybe someone with a proper solution will chime in. Otherwise, you have to RMA your device...
Good luck...
5.1 said:
Did you try:
fastboot flashing unlock
Since you only relocked, you unlikely toggled "OEM unlock"?!
If it fails, I think you are SOL. Maybe someone with a proper solution will chime in. Otherwise, you have to RMA your device...
Good luck...
Click to expand...
Click to collapse
It just says waiting for device and hangs there... I don't think it recognizes the phone
EDIT: IT WORKED!!!!!
It wouldnt recognize it and I ran fastboot continue and it just hanged there but I went into the bootloader mode and for like a quarter of a second it recognized it and forced it to boot
tryfont said:
It just says waiting for device and hangs there... I don't think it recognizes the phone
Click to expand...
Click to collapse
Open device manager in windows. Plug your phone and see how is your phone recognized.?!
5.1 said:
Open device manager in windows. Plug your phone and see how is your phone recognized.?!
Click to expand...
Click to collapse
Im on mac but its good now I edited my comment above. Only question is how to I completely clean the OS so I can relock bootloader without running into the same problem
This is whats happening to me- https://goo.gl/photos/2kv9Xo3HM3Mqn8AQ9
tryfont said:
Im on mac but its good now I edited my comment above. Only question is how to I completely clean the OS so I can relock bootloader without running into the same problem
Click to expand...
Click to collapse
Hey... Go into recovery and perform a factory reset.
Reboot bootloader and flash stock firmware. You could flash both slots to be sure your device is completely clean.
I wrote a how-to for someone having another issue. You.can follow this:
https://forum.xda-developers.com/showpost.php?p=71849370&postcount=28
When you are finished with flashing, reboot to be sure your system boot properly and your phone works as it should...
From here you can reboot into bootloader and issue:
fastboot flashing lock
If It was me I'd leave it unlocked though... Or at least OEM unlock enabled and ADB debugging ON. Since Google tend to release messed up OTA, you can always unlock the bootloader if needed.
But if you wish you can also disable the OEM unlock.
Good luck...
5.1 said:
Hey... Go into recovery and perform a factory reset.
Reboot bootloader and flash stock firmware. You could flash both slots to be sure your device is completely clean.
I wrote a how-to for someone having another issue. You.can follow this:
https://forum.xda-developers.com/showpost.php?p=71849370&postcount=28
When you are finished with flashing, reboot to be sure your system boot properly and your phone works as it should...
From here you can reboot into bootloader and issue:
fastboot flashing lock
If It was me I'd leave it unlocked though... Or at least OEM unlock enabled and ADB debugging ON. Since Google tend to release messed up OTA, you can always unlock the bootloader if needed.
But if you wish you can also disable the OEM unlock.
Good luck...
Click to expand...
Click to collapse
I'm pretty inexperienced with this kind of stuff and so you might have to explain it a bit further than what that link says. I did fastboot reboot bootloader in terminal but it can't find my device. Also I couldnt get into recovery when it was bricked so I probably still can't
tryfont said:
I'm pretty inexperienced with this kind of stuff and so you might have to explain it a bit further than what that link says. I did fastboot reboot bootloader in terminal but it can't find my device
Click to expand...
Click to collapse
Hey...
You boot into bootloader when the Device is powered off
Just like in your video: with power + volume down
You can see infos regarding:
Bootloader
Radio
S/N
DRAM
Boot-slot=
Etc...
This is the bootloader :good:
From here, unzip the google image you have downloaded, open the folder and from here run the flash-all script. Let your device reboot. Power it down, boot into bootloader again with power + volume down. Change active slot as I described in the link I gave you previously. Run the same flash-all again... Done!
Just for safety, remove your Google account before you continue. You'll add it again later...
Good luck...
5.1 said:
Hey...
You boot into bootloader when the Device is powered off
Just like in your video: with power + volume down
You can see infos regarding:
Bootloader
Radio
S/N
DRAM
Boot-slot=
Etc...
This is the bootloader :good:
From here, unzip the google image you have downloaded, open the folder and from here run the flash-all script. Let your device reboot. Power it down, boot into bootloader again with power + volume down. Change active slot as I described in the link I gave you previously. Run the same flash-all again... Done!
Just for safety, remove your Google account before you continue. You'll add it again later...
Good luck...
Click to expand...
Click to collapse
Alright thank you so much its doing the flashing right now. I really appreciate you helping...I was worried I'd have to get a replacement through google. Have a great day lad
tryfont said:
Alright thank you so much its doing the flashing right now. I really appreciate you helping...I was worried I'd have to get a replacement through google. Have a great day lad
Click to expand...
Click to collapse
Hey... Flash both slots... Just to be sure both are clean and nothing problematic remains on your device before locking your bootloader!
It could brick installing an OTA or whatever. Better restart 100% clean. :good:
Cheers...
Just flash the flash-all, relock and call it a day. Then you'll be fully stock and locked. I would however recommend rebooting once before locking to make sure its all good.
tryfont said:
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Click to expand...
Click to collapse
Hey man I have the same problem you can try calling Google support they can send you a replacement if you still have a warranty
my warranty has expired so I'm on my own
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
remialfa said:
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
Click to expand...
Click to collapse
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
auceto63 said:
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
Click to expand...
Click to collapse
I did that and yeah it entered this mode but it's not valid bootloader/fastboot mode. It's some service mode to update firmware. Anyway it's not visible in pc as a normal fastboot and I cannot proceed further with unlocking bootloader...
Edit: it's download mode... So as I said it's not fastboot mode.
Anyone can help?
Seriously nobody? I thought this phone has good community and support...
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
charith262 said:
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
You can check out UsU. That is an unofficial bootloader unlock
ThePiGuy said:
You can check out UsU. That is an unofficial bootloader unlock
Click to expand...
Click to collapse
Thanks yeah I checked but that's for ARB<=2 devices. I forgot to mention earlier this godforsaken thing is ARB3.
I have an H811 (T-Mo) running firmware H81120p, ARB3. Doesn't seem to be much that can be done with it as far as rooting. It also has no stock recovery, only boots to system.
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
if you use bank apps, install magisk before installing rom, do not get SU
samadee3 said:
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
Click to expand...
Click to collapse
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
SofaSpud said:
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
Click to expand...
Click to collapse
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
ThePiGuy said:
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
Click to expand...
Click to collapse
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Sent from my SAMSUNG-SM-G935A using Tapatalk
SofaSpud said:
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Click to expand...
Click to collapse
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
ThePiGuy said:
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
Click to expand...
Click to collapse
Got it. Guess that it makes sense. ARB prevents rolling back to earlier release than 20o, I'm ok. Will try the BL unlock today then.
Sent from my SAMSUNG-SM-G935A using Tapatalk
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Florimer said:
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Click to expand...
Click to collapse
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Florimer said:
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Click to expand...
Click to collapse
Do you have more details about this? I seem to be in a similar situation than you and I'm struggling to make it work.
Success is disgusted by some people, and will not share any files for free in the future.
If relock, how about OTA uptdate?
dungnghien said:
If relock, how about OTA uptdate?
Click to expand...
Click to collapse
yes，you can！only support CN firmware，but WW firmware upgrades are not supported. The WW version of the firmware upgrade, you need to download the update package to the root directory, restart the phone to detect the update.
Will this process factory reset or no ???
zinou213 said:
Will this process factory reset or no ???
Click to expand...
Click to collapse
YES！
Damn! I should have waited for this. Too late. I used unlock tool. Now Asus has my unlock info.
One question. Can I relock if I originally unlocked using asus unlock apk tool???
to confirm.......
i have a factory locked, untouched WW 512 unit. If i use this tool, i can unlock WITHOUT Asus knowing? no downsides?
@johnny886,
Thank for this, I waited for something like this, wanted to unlock the bootloader without using that app that gives IMEI to asus, a total offline boot-loader unlock.
although i stuck in step 3 ".update_image_EDL.bat”, dos prompt instantly closes. It may be a driver issue, as im not familiar with drivers for this phone, can you upload the drivers, only thing missing in this pack.
BakaValen said:
to confirm.......
i have a factory locked, untouched WW 512 unit. If i use this tool, i can unlock WITHOUT Asus knowing? no downsides?
Click to expand...
Click to collapse
There are no disadvantages, the only benefit is that you can unlock your phone through EDL mode, no need to install UnlockTool.apk to apply for unlock! The ASUS server will not get your unlocked status, you can get upgrades via OTA later.
Extreme184X said:
@johnny886,
Thank for this, I waited for something like this, wanted to unlock the bootloader without using that app that gives IMEI to asus, a total offline boot-loader unlock.
although i stuck in step 3 ".update_image_EDL.bat”, dos prompt instantly closes. It may be a driver issue, as im not familiar with drivers for this phone, can you upload the drivers, only thing missing in this pack.
Click to expand...
Click to collapse
Oh sorry, I forgot to upload the driver for Qualcomm! You can download and install this tool on your computer, and then follow the steps to unlock it! Download link:https://drive.google.com/open?id=1PRw4jcg0zQKLQnMz7gApMZtCYex1PfJM
How about Burnt Fuses? Does something like this occur? Basically, i want to ensure that the fact that ive unlocked is hidden for warrenty. (I can always re-lock before sending back if i need to)
It would suck for them to tell me, that they wont service it because it was previously unlocked.
BakaValen said:
How about Burnt Fuses? Does something like this occur? Basically, i want to ensure that the fact that ive unlocked is hidden for warrenty. (I can always re-lock before sending back if i need to)
It would suck for them to tell me, that they wont service it because it was previously unlocked.
Click to expand...
Click to collapse
By unlocking this way, you can enjoy the warranty!
had anyone tried this method on previous unlocked device? did it will regain CN FOTA? thanks!
Hi, i tried but stuck on step 3, any way to solve? tried to change the usb port but same thing happened.
on step 3:.Double click to open “1.update_image_EDL.bat”,
it said: {ERROR: WritePort:5164 Could not write to '\\.\COM10', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times
@johnny886,
Hi, I installed the Qualcomm drivers but for step 3 "1.update_image_EDL.bat”, it still prompts and closes immediately and I'm not sure how to QPST or QFIL. Are there ways to fix the bat file or provide a more detaisl on using QPST or QFIL please?
You can root without unlock bootloader?
Deleted, misread, don't think it's relevant...
So I did this and now my headphones jack isn't working. Has this happened to anyone else?
Update: The current workaround is to use the headphone jack of the included cooling fan.
Update 2: So it may have something to do with the bootloader that was flashed during the EDL unlocking process, which seems to be a generic SD855 bootloader. I came to this conclusion after I noticed that I was being limited to 70% battery charge. I flashed the WW 1910.35 OTA from ASUS' site and the battery now charges to 100%, but the headphone jack still remains broken. I will try to flash the WW 1910.44 update through fastboot when I get home, which I'm hoping will have whatever partition that was overwritten during the unlocking process.
Update 3: I figured it out. After using "fastboot flash boot TWRP.img" to boot into TWRP initially, I didn't flash the stock boot image again. This broke the headphone jack. So after booting into TWRP using that command, I had to flash the stock boot image first, then flash the TWRP and Magisk installers in that order. Hope this helps someone.
dennis96411 said:
So I did this and now my headphones jack isn't working. Has this happened to anyone else?
Update: The current workaround is to use the headphone jack of the included cooling fan.
Update 2: So it may have something to do with the bootloader that was flashed during the EDL unlocking process, which seems to be a generic SD855 bootloader. I came to this conclusion after I noticed that I was being limited to 70% battery charge. I flashed the WW 1910.35 OTA from ASUS' site and the battery now charges to 100%, but the headphone jack still remains broken. I will try to flash the WW 1910.44 update through fastboot when I get home, which I'm hoping will have whatever partition that was overwritten during the unlocking process.
Update 3: I figured it out. After using "fastboot flash boot TWRP.img" to boot into TWRP initially, I didn't flash the stock boot image again. This broke the headphone jack. So after booting into TWRP using that command, I had to flash the stock boot image first, then flash the TWRP and Magisk installers in that order. Hope this helps someone.
Click to expand...
Click to collapse
Hey, can you please tell me where to get the stock boot image for 1910.44?
Edit: Okay nevermind got it.
Stuck on step 1.update_image_EDL.bat
Almost all of us are stuck on step 1.update_image_EDL.bat . The CMD window just shows and closes fast, and phone doesnt enter fastboot mode. I installed all drivers. Can you post guide on how to do that step using QPST or Miflash tools?
This Is For those Who Stuck At Android 9 In WW Roms With ZS660KL Model
This Method Will Use Raw Firmware so there is risks if you do something wrong and maybe data loss so always backupBootloader Must Be Unlocked
How To Flash Raw Rom:1-Bootloader Must be Unlocked! (To change fingerprint to ww and relock the bootloader to get OTA) If you are already on WW fingerprint this step aint needed or you want to stay on cn fingerprint just skip)
2-Install adb and fastboot
3-Download and extract the raw version you want i will give some below
4- reboot the phone to fastboot mode and connect it to the pc Use Side Port
5-in the raw firmware folder double click flashall_AFT.cmd This will take sometime and no progress will be shown so all you have to do is to wait till the phone reboot or get black screen if you got black screen just hold vol down and power button for some seconds
6-if your Fingerprint is cn Change it to WW With root explorer you can find posta about this step by step (skip this if you are already on WW Fingerprint)
Downloads:
Android 10:
https://drive.google.com/file/d/1NQI7SyCfPkBA15dVAim2yhEWD_6p0Kta/view
Android 9:
https://drive.google.com/file/d/16uIlYvFuXDEoRmtosqUwgVgM7aMdhaOp/view
Credits:
the custom droid site for the raw Firmwares
Some info:
After this method You will get ota updates if you relock bootloader
or you can install update zips from asus if you want to keep bootloader unlocked :silly:
You don't need to unlock the bootloader to flash the raw firmware. That is stupid to say you do..
joluke said:
You don't need to unlock the bootloader to flash the raw firmware. That is stupid to say you do..
Click to expand...
Click to collapse
The way you say stupid is stupid however mine didn't got flashed just rebooted when tried to flash the raw and couldn't update in system updates or zip files however having some respect ain't bad for your health.
shahram Ali said:
The way you say stupid is stupid however mine didn't got flashed just rebooted when tried to flash the raw and couldn't update in system updates or zip files however having some respect ain't bad for your health.
Click to expand...
Click to collapse
First of all, I just said it was a stupid thing to say because you don't need to unlock the bootloader and you must use the side USB c port to flash via fastboot. Second: learn to interpret proper English because I didn't offend anyone. End of conversation
joluke said:
First of all, I just said it was a stupid thing to say because you don't need to unlock the bootloader and you must use the side USB c port to flash via fastboot. Second: learn to interpret proper English because I didn't offend anyone. End of conversation
Click to expand...
Click to collapse
I mentioned the side port i don't write a paragraph about the phone as homework short and easy fix is the point there is nothing missing in the post so your reply wasn't necessary mate keep it cool :good:
How do I lock the bootloader after this?
I have some apps that wont work, whit the message "This app is not supported in rooted devices, please restore your device"
Thanks
Ricardo55467 said:
How do I lock the bootloader after this?
I have some apps that wont work, whit the message "This app is not supported in rooted devices, please restore your device"
Thanks
Click to expand...
Click to collapse
You will need to enter an command in fastboot mode but be aware backup every necessary things
If you didn't rooted or touched boot.img just use this command in fastboot and the bootloader will be locked again
fastboot oem asus-csc_lk
shahram Ali said:
You will need to enter an command in fastboot mode but be aware backup every necessary things
If you didn't rooted or touched boot.img just use this command in fastboot and the bootloader will be locked again
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .
Ricardo55467 said:
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .
Click to expand...
Click to collapse
You'll need to flash stock boot img if your rom version (to remove root) before locking bootloader
Ricardo55467 said:
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .
Click to expand...
Click to collapse
Just reflash stock boot.img and you can use the command
ROOT RED MAGIC 8 PRO V3.18Your device must be bootloader unlocked
To unlock bootloader enable oem unlock in developer options and usb debugging
Then type the command: adb reboot bootloader
Or access fastboot with hardware key: Power + volume down
Once in fastboot type the following command to unlock:
fastboot flashing unlock
fastboot flashing unlock_critical"
Access fastboot then type the command:
fastboot flash init_boot_a magisk_patched-25200_3.18UN.img
fastboot reboot
Done
You check if the correct active slot is a, if it is b just change the command a with b
Only use for V3.18 version I have not tested other versions
Note: Absolutely do not patch the boot file, you will have a continuous boot error
Root Done
The backups with just ommiting the B slots is 12.7 gb so i cant personally help you with that. Have you tried flashing the OTA's boot.img (might even try boot_a.img) and init_boot.img while slot A is selected? Not the magisk modded files either.
mcfizzlestag said:
The backups with just ommiting the B slots is 12.7 gb so i cant personally help you with that. Have you tried flashing the OTA's boot.img (might even try boot_a.img) and init_boot.img while slot A is selected? Not the magisk modded files either.
Click to expand...
Click to collapse
i flashed those 2 files but still can't boot the phone, go to logo then turn off the screen, can only go to fastboot and recovery, i sideload 47% it gives error
If you are rooted, please help me, I will send you coffee donate, please help me, full backup
I Pm'd you the backups now that i am at home, hopefully they help
Im at a stand still with this. I have already fastboot flashing unlock_critical as you can see in which it states Device already unlocked but whether I am in bootloader and fastboot I get Flashing is not allowed in a lock state. Any help from some else that ran into this or has knowledge on it?
Thanks
Update. Fixed the issue. Add the step of "fastboot flashing unlock" before "fastboot flashing unlock_critical"
If You can flash a GSI, It'd be a decisive factor in getting people to buy this phone. The company should be paying you to do this, but they're probably too greedy to make a bigger profit
I've successfully flashed a few A13 GSIs but screen lock is a still a problem and so far calls and messaging doesn't work normally.
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Muriyata said:
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Click to expand...
Click to collapse
yes, you can return warranty
Muriyata said:
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Click to expand...
Click to collapse
Well once you unlock bootloader it clearly says warranty: void in fastboot so it probably is very easy to detect
edzchen said:
Well once you unlock bootloader it clearly says warranty: void in fastboot so it probably is very easy to detect
Click to expand...
Click to collapse
In that case, why op said that the warranty can still be returned after relocking the bootloader?
As you see, it is very connfusing... Some guys say yes, some others not. :s
edzchen said:
I've successfully flashed a few A13 GSIs but screen lock is a still a problem and so far calls and messaging doesn't work normally.
Click to expand...
Click to collapse
Could you please tell me the steps to flash A13 GSI roms. Thanks.
[email protected] said:
Could you please tell me the steps to flash A13 GSI roms. Thanks.
Click to expand...
Click to collapse
Unlock bootloader
Reboot into fastboot
Flash system with the GSI.img
Mr.PvT said:
i flashed those 2 files but still can't boot the phone, go to logo then turn off the screen, can only go to fastboot and recovery, i sideload 47% it gives error
If you are rooted, please help me, I will send you coffee donate, please help me, full backup
Click to expand...
Click to collapse
I have the same problem with my phone. Could you please tell me if you know find the solution to this. Thanks.
[email protected] said:
I have the same problem with my phone. Could you please tell me if you know find the solution to this. Thanks.
Click to expand...
Click to collapse
inbox me
Mr.PvT said:
inbox me
Click to expand...
Click to collapse
How can I inbox you?
Oh no... Can this be fixed?
Stusick said:
View attachment 5862143View attachment 5862145View attachment 5862147
Click to expand...
Click to collapse
Did you follow the instructions correctly, this error may have you flashed the wrong boot file, right?
Mr.PvT said:
Did you follow the instructions correctly, this error may have you flashed the wrong boot file, right?
Click to expand...
Click to collapse
Yes, I unlocked the bootloader first.
Then I flash boot and an error occurred.
Did I get a brick or is there hope?)