Related
I just got a Moto X on Sprint, and after successfully unlocking the bootloader, I do not seem to be able to flash TWRP. The flash seems to go ok, but when I boot the device into recovery, its still the stock recovery. Im attempting to use the official openrecovery-twrp-2.7.1.1-ghost.img image. Ive tried using the standard fastboot on OSX and WIn7-64bit, and in both situations I get this output:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.749s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.629s
The variable not supported seems to be the 'getvar partition-type:recovery' command (based on the output on the phone).
I have also tried using the fastboot provided by Motorola with the same output and result. On the forums somewhere I found a link to an older moto-fastboot-osx command, which has slightly different output, but the same results:
Code:
moto-fastboot-osx64 flash recovery openrecovery-twrp-2.7.1.1-ghost.img
sending 'recovery' (8220 KB)... OKAY [ 0.787s]
writing 'recovery'... OKAY [ 0.909s]
What am I doing wrong?
Have you double checked that your oprnrecovery-twrp...img file is not corrupt? Make sure to check it against the md5 checksum.
Yes, I verified the MD5, it is correct.
slushpupie said:
I just got a Moto X on Sprint, and after successfully unlocking the bootloader, I do not seem to be able to flash TWRP. The flash seems to go ok, but when I boot the device into recovery, its still the stock recovery. Im attempting to use the official openrecovery-twrp-2.7.1.1-ghost.img image. Ive tried using the standard fastboot on OSX and WIn7-64bit, and in both situations I get this output:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.749s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.629s
The variable not supported seems to be the 'getvar partition-type:recovery' command (based on the output on the phone).
I have also tried using the fastboot provided by Motorola with the same output and result. On the forums somewhere I found a link to an older moto-fastboot-osx command, which has slightly different output, but the same results:
Code:
moto-fastboot-osx64 flash recovery openrecovery-twrp-2.7.1.1-ghost.img
sending 'recovery' (8220 KB)... OKAY [ 0.787s]
writing 'recovery'... OKAY [ 0.909s]
What am I doing wrong?
Click to expand...
Click to collapse
Just a few thoughts...forgive me if any of this sounds redundant, or obvious....
Just reading your initial post, I would assume that you had used one of the previous root exploits and/or Safestrap BEFORE you got the BL unlocked. If so, it would be necessary to flash the entire stock SBF, before you would be able to successfully flash TWRP recovery........but your OP says you JUST got the phone, which would lead me to believe you didn't use a previous root exploit. Did you receive it NEW? Because the original owner could certainly have used exploit/safestrap.
If any of this is possible, you should follow the "Return to Stock" thread (manual method is suggested - easier and faster) and flash the entire Sprint 4.4.2 SBF. THEN you should be able to successfully flash TWRP. As I have often stated, a full SBF to stock can actually REPAIR a corrupted / modified (exploit / safestrap) filesystem. A "Factory Reset" does not repair any corruption that may be present.
2nd thought: I've seen some people confuse the "bootloader" screen (AP Fastboot Mode) for recovery. From the bootloader screen, you have to arrow down to highlight recovery, and press volume up to boot into recovery.
Alternatively, you can do it from fastboot: just type fastboot reboot-recovery
Let us know if any of this is relevant or solves your issue. If everything else fails, doing a full SBF back to stock fixes all issues nearly 100% of the time.
Good Luck
samwathegreat said:
Just a few thoughts...forgive me if any of this sounds redundant, or obvious....
Just reading your initial post, I would assume that you had used one of the previous root exploits and/or Safestrap BEFORE you got the BL unlocked. If so, it would be necessary to flash the entire stock SBF, before you would be able to successfully flash TWRP recovery........but your OP says you JUST got the phone, which would lead me to believe you didn't use a previous root exploit. Did you receive it NEW? Because the original owner could certainly have used exploit/safestrap.
Click to expand...
Click to collapse
It was purchased used, and the original owner was not very tech savy, so I assumed it was fully stock (it appeared so at first glance, anyway).
samwathegreat said:
If any of this is possible, you should follow the "Return to Stock" thread (manual method is suggested - easier and faster) and flash the entire Sprint 4.4.2 SBF. THEN you should be able to successfully flash TWRP. As I have often stated, a full SBF to stock can actually REPAIR a corrupted / modified (exploit / safestrap) filesystem. A "Factory Reset" does not repair any corruption that may be present.
Click to expand...
Click to collapse
Ill give this a try and report back. Perhaps there is something weird going on in there...
samwathegreat said:
2nd thought: I've seen some people confuse the "bootloader" screen (AP Fastboot Mode) for recovery. From the bootloader screen, you have to arrow down to highlight recovery, and press volume up to boot into recovery.
Alternatively, you can do it from fastboot: just type fastboot reboot-recovery
Let us know if any of this is relevant or solves your issue. If everything else fails, doing a full SBF back to stock fixes all issues nearly 100% of the time.
Good Luck
Click to expand...
Click to collapse
Im familiar with Android enough to know the difference between the bootloader and recovery, but thanks for making sure.
slushpupie said:
It was purchased used, and the original owner was not very tech savy, so I assumed it was fully stock (it appeared so at first glance, anyway).
Ill give this a try and report back. Perhaps there is something weird going on in there...
Im familiar with Android enough to know the difference between the bootloader and recovery, but thanks for making sure.
Click to expand...
Click to collapse
Haha, yes, I was hesitant to suggest there may be confusion between bootloader and recovery.... Glad you were on top of that one...
The return to stock thread is located here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Again, manual method is easier and faster.
You will flash the 4.4.2 Sprint SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
If my first theory was correct, you wouldn't be the first person who received a used phone that had an exploit used on it. The devs make it pretty easy even for not-so-tech-savvy people with all the "one-click" rooting scripts and the like. Often times, the seller just assumes that a "factory reset" will un-do the modifications, but in the case of the Moto X (with all the Write Protect-disable exploits and safestrap), the modifications actually persist through a factory reset.
samwathegreat said:
Haha, yes, I was hesitant to suggest there may be confusion between bootloader and recovery.... Glad you were on top of that one...
The return to stock thread is located here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Again, manual method is easier and faster.
You will flash the 4.4.2 Sprint SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
Well, I followed the directions and it seemed to flash ok. Booted it up, wanted to activate (I canceled that- I dont have service on the phone yet), everything seemed normal. Went back to flash TWRP, same behavior as before. Any other ideas?
slushpupie said:
Well, I followed the directions and it seemed to flash ok. Booted it up, wanted to activate (I canceled that- I dont have service on the phone yet), everything seemed normal. Went back to flash TWRP, same behavior as before. Any other ideas?
Click to expand...
Click to collapse
A couple more: some individuals have reported that they had issues using a USB 3.0 port. If possible, use a USB 2.0 port to flash the recovery.
If you flashed ALL the partitions in the SBF file starting with gpt.bin (basically manually executed the commands in the XML file, IN ORDER), it -should- have worked.
You might also try flashing twrp from a different PC...
OR
You can try flashing TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
This version is confirmed to work on all versions up to and including 4.4.2, so as long as you aren't on 4.4.3 yet, you can give this a shot.
And lastly, since I don't know exactly where you got the mfastboot binary, be sure to try the mfastboot binary linked in the 'return to stock' thread. That one is confirmed to work.
2 suggestions:
- try a different TWRP - I'm using a 2.7 that is referred to in one of the threads here
- after flashing > use the volume down button to highlight boot to recovery, and the volume up button to select (execute) that command ... my first time I tried the power button to select it and that doesn't work. I experienced some strange issues when trying to flash recovery if I didn't immediately boot into recovery (don't power down).
jasoraso said:
2 suggestions:
- try a different TWRP - I'm using a 2.7 that is referred to in one of the threads here
Click to expand...
Click to collapse
Ive tried a few, but will see if I can find some more to try. There seems to be no negative to trying them at this point.
jasoraso said:
- after flashing > use the volume down button to highlight boot to recovery, and the volume up button to select (execute) that command ... my first time I tried the power button to select it and that doesn't work. I experienced some strange issues when trying to flash recovery if I didn't immediately boot into recovery (don't power down).
Click to expand...
Click to collapse
The volume-key navigation is familiar to me (Ive had Android devices going back to the Samsung Moment), and I wasnt sure if I was getting into recovery or not since it just booted normally when I select recovery from the boot menu. However, when I specifically boot to recovery with 'adb reboot recovery' I get the tell-tale "No command" screen indicating I still have stock recovery.
slushpupie said:
Ive tried a few, but will see if I can find some more to try. There seems to be no negative to trying them at this point.
The volume-key navigation is familiar to me (Ive had Android devices going back to the Samsung Moment), and I wasnt sure if I was getting into recovery or not since it just booted normally when I select recovery from the boot menu. However, when I specifically boot to recovery with 'adb reboot recovery' I get the tell-tale "No command" screen indicating I still have stock recovery.
Click to expand...
Click to collapse
If you boot into stock recovery on Moto X, it shouldn't say "No command".... It should show "Dead Andy" - the broken android with the exclaimation point.
Are you trying to do this while android is booted? If so, unplug the USB, turn off the phone. Now hold down VOL DOWN and turn it back on. You should be on the bootloader screen (AP Fastboot mode). Plug the USB back in now
(^ I realize you probably already know the procedure, but good to have it here for others that might visit this thread)
Now VOL DOWN to recovery and VOL UP to boot it
What happens? Do you see Dead Andy?
I just tested the procedure on my phone (after flashing stock recovery back). After I select recovery and VOL UP to boot it, it takes less than 10 seconds for Dead Andy to appear. Pressing VOL UP + POWER brings up the stock recovery menu: reboot, apply update, wipe cache, etc. etc.
EDIT: I also just tried rebooting from within android as you stated you had done. After typing adb reboot bootloader, the phone promptly booted to the Dead Andy Stock Recovery screen.
Nowhere did it say "no command" on either the device itself, or the command prompt from which the adb command was executed...
samwathegreat said:
A couple more: some individuals have reported that they had issues using a USB 3.0 port. If possible, use a USB 2.0 port to flash the recovery.
Click to expand...
Click to collapse
My MacBook Pro only has USB3.0 ports. I would expect an issue to show some error, though (like in the transfer). It seems everything transfers just fine; it just doesn't seem to take.
samwathegreat said:
If you flashed ALL the partitions in the SBF file starting with gpt.bin (basically manually executed the commands in the XML file, IN ORDER), it -should- have worked.
Click to expand...
Click to collapse
It appeared the full SBF flashing process worked. It reset everything and prompted me for activation.
samwathegreat said:
You might also try flashing twrp from a different PC...
Click to expand...
Click to collapse
I dont really have anything different to try. Ive got another MBP, but its pretty much identical, and I get the same results when I try there. I have several VMs I can try- Ive tried with Win7-64bit (as mentioned in the original post) but that was the same too. I could try Linux too, if I get the time to set one up, but my gut says it wont be any different.
samwathegreat said:
You can try flashing TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
This version is confirmed to work on all versions up to and including 4.4.2, so as long as you aren't on 4.4.3 yet, you can give this a shot.
Click to expand...
Click to collapse
Since I just reflashed back to the stock image, it is 4.4.2. Ive tried this version as well, with the same result.
samwathegreat said:
And lastly, since I don't know exactly where you got the mfastboot binary, be sure to try the mfastboot binary linked in the 'return to stock' thread. That one is confirmed to work.
Click to expand...
Click to collapse
Being on a Mac makes this a bit more challenging, but yes, I did try this in my Win7 virtual machine with the same results.
samwathegreat said:
If you boot into stock recovery on Moto X, it shouldn't say "No command".... It should show "Dead Andy" - the broken android with the exclaimation point.
Are you trying to do this while android is booted? If so, unplug the USB, turn off the phone. Now hold down VOL DOWN and turn it back on. You should be on the bootloader screen (AP Fastboot mode). Plug the USB back in now
(^ I realize you probably already know the procedure, but good to have it here for others that might visit this thread)
Now VOL DOWN to recovery and VOL UP to boot it
What happens? Do you see Dead Andy?
Click to expand...
Click to collapse
Yes, I see the dead andy image, with the no command message below him.
No, I am doing this from the bootloader. When I attempt to load recovery from the bootloader, I see the white unlocked warning image, then it goes and boots normally. Once into Android, I can issue 'adb reboot recovery' and that's when I see dead andy with the no command message. Confused yet? Cause I am.
samwathegreat said:
I just tested the procedure on my phone (after flashing stock recovery back). After I select recovery and VOL UP to boot it, it takes less than 10 seconds for Dead Andy to appear. Pressing VOL UP + POWER brings up the stock recovery menu: reboot, apply update, wipe cache, etc. etc.
EDIT: I also just tried rebooting from within android as you stated you had done. After typing adb reboot bootloader, the phone promptly booted to the Dead Andy Stock Recovery screen.
Nowhere did it say "no command" on either the device itself, or the command prompt from which the adb command was executed...
Click to expand...
Click to collapse
Im really at a loss then.. Ill try to restore the stock images again. Maybe I missed something the first go around.
slushpupie said:
Im really at a loss then.. Ill try to restore the stock images again. Maybe I missed something the first go around.
Click to expand...
Click to collapse
I suggest a slight variation:
After you extract the entire SBF file to the same folder where mfastboot resides:
First, boot to bootloader. Next, issue the following commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Device should reboot right back to bootloader. Now issue these commands (we are going to use mfastboot for ALL commands, and YES, we are repeating gpt and motoboot again. this is intentional):
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem config carrier sprint
mfastboot oem fb_mode_clear
mfastboot reboot
Lets see if we can flash TWRP now. I helped another user on a MAC with a similar issue, and this resolved it for him. I'm hopeful we will fix your issue as well.
samwathegreat said:
I suggest a slight variation:
After you extract the entire SBF file to the same folder where mfastboot resides:
First, boot to bootloader. Next, issue the following commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Device should reboot right back to bootloader. Now issue these commands (we are going to use mfastboot for ALL commands, and YES, we are repeating gpt and motoboot again. this is intentional):
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
<...>
Lets see if we can flash TWRP now. I helped another user on a MAC with a similar issue, and this resolved it for him. I'm hopeful we will fix your issue as well.
Click to expand...
Click to collapse
That did it, thanks! I wonder what is going on that I had to flash partition and motoboot twice. In any event, Im off and running. Thanks again!
slushpupie said:
That did it, thanks! I wonder what is going on that I had to flash partition and motoboot twice. In any event, Im off and running. Thanks again!
Click to expand...
Click to collapse
GPT stands for GUID Partition Table.
We aren't quite sure why this method works with stubborn flashes, but this is the theory:
We think that if the partition table somehow gets corrupted, the bootloader enforces write protection (on some or all partitions) even if you are unlocked...
The trick is to just flash the partition table, and the bootloader images, then immediately reboot, so the bootloader can load the NON-Corrupt partition table. Once the system reboots, all subsequent partition flashes seem to 'stick' without issue. It seems to involve some sort of 'bug' in the write protection implementation.
Regardless, once it is fixed, so is the issue. You shouldn't need to double-flash any partitions after rebooting like we did this time. AFAIK, all the users who got fixed using the above procedure have reported no further problems.
Just remember to never flash a previous version of android without checking here first. Most users who have to undergo the above procedure tried to downgrade for some reason, and many of them ended up having to do the procedures listed in the "Unbrick" thread (Not fun...)
Glad it all worked out.
samwathegreat said:
GPT stands for GUID Partition Table.
We aren't quite sure why this method works with stubborn flashes, but this is the theory:
We think that if the partition table somehow gets corrupted, the bootloader enforces write protection even if you are unlocked...
The trick is to just flash the partition table, and the bootloader images, then immediately reboot, so the bootloader can load the NON-Corrupt partition table. Once the system reboots, all subsequent partition flashes seem to 'stick' without issue. It seems to involve some sort of 'bug' in the write protection implementation.
Click to expand...
Click to collapse
Makes sense. Given that the bootloader is the one area you cant easily fix if you screw up, I would add as much protection as possible too. Of course, I would also add error messages... Makes me wonder if there is some hard coded entries in the event the GTP gets screwed up. Has anyone attempted to inspect the gpt.bin file?
samwathegreat said:
Regardless, once it is fixed, so is the issue. You shouldn't need to double-flash any partitions after rebooting like we did this time. AFAIK, all the users who got fixed using the above procedure have reported no further problems.
Just remember to never flash a previous version of android without checking here first. Most users who have to undergo the above procedure tried to downgrade for some reason, and many of them ended up having to do the procedures listed in the "Unbrick" thread (Not fun...)
Glad it all worked out.
Click to expand...
Click to collapse
Good to know. I dont plan on doing anything fancy, just want root for TI backups, really. I guess Ill see how well flashing the bootloader works again when the 4.4.3 OTA comes around to my phone.
Bricked. Red "Your device is corrupt. It can't be trusted and may not work properly"
Following this guide I ended up bricking my Nexus 6. Please ask questions as this is my first time rooting a device.
http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
After typing "fastboot reboot" my phone begun rebooting, stopped and went to the red "Your device is corrupt. It can't be trusted and may not work properly". Now I am able to get to the fastboot menu. I am also able to get to the android recovery menu. Can anyone point me in the direction to get my phone working again?
Thank you in advance
You can get into fastboot. So restore to stock image. Or since you have custom recovery restore your working backup.
Then read the thread on root. Not just the first post. Read the most recent ones... They are the ones with the most up to date info. Never flash stuff or follow guides with out reading like the last 3-4 pages of the thread as well as the full OP AT A MINIMUM.
1)download google factory image
2)Extract everything in one folder.
3)Delete userdata.img from folder(because once i left it in folder and started flashing images one by one and ended up with empty internal storage.lost everything)
4)use these commands to flash
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
5)reboot
You don't have to delete userdata.img... Just dont flash it, and don't use flashall
Your manually typing these commands. Just don't type it. Understand what the partitions are and don't flash the ones you don't want.
And on that point, rather then flash the stock recovery, flash something like TWRP since your trying to root.
Wow. Thank you guys. I really appreciate it. Great group here.
Got it back up and running with 6.0.1 with your help. Since I have gotten this far I think I'll try out some ROM's.
Thanks again.
Can anyone tell me what this (remote: Flashing is not allowed in Lock State).
What exactly is locked? Is my cell OEM unlocked?
I flashed the wrong TWRP (for the 2017 Red Magic-NX209J) and even though I have been able to unlock my cell via CMD commands; it remains permanently in fastboot mode?
If I send a CMD command to reboot it reboots straight back to fastboot mode.
No form of ADB connect seems to work an my windows PC cannot see/show the cell?
How the hell do I fix this? It's been in this state for a week.
Can anyone help?
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
xronaldx said:
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
Click to expand...
Click to collapse
Thanks for the suggestion. I have no recovery back up Is it possible to get past TWRP being locked and use CMD to flash the International or chinese ROM? Or recovery image?
Unless tools are developed to unbrick this device I am scared this problem might be permanent
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Secretcow said:
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Click to expand...
Click to collapse
Thanks but what do i do with it? Its all in an asain language?
Link not open bro
The TWRP does not work
Sorry. That link to the twrp does not result in a bootable twrp recovery for me.
I am starting to think my cell is not fixable.
I did not do that much wrong I just flashed the twrp for 2 models of red magic earlier. It only has a fastboot mode. I either get a boot screen then fastboot mode or a warning about the bootloader being unlocked.
Whatever is wrong with my cell prevents ADB connect an the cell is not able to be seen by windows.
This $1100 New Zealand dollar cellphone may be permanently bricked by my mistake.
I might just need to bin it an buy another one.
Lesson learned.
It confusing....
My cell acts like it has a softbrick (can turn off an on an has fastboot options and I have erased it an OEm an bootloader unlocked it)
And also behaves like a hard brick (resists every method of repair).
I just do not understand it or Nubia products. I am unfamiliar with this phone.
Does anyone have any clue how I can see this cell on my windows pc or ADB connect it an boot into TWRP?
Are there any Nubia repair software tools?
I already share nubia red magic 3 twrp check my all post
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Thanks for that. I'm talking about using CMD to totally wipe everything in the cell an reflash the Chinese ROM that came with it. Repair software. Might take months to develop software like that.
sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Also it isn't a zip. It's some other kind of file. And does not boot into TWRP on my unit
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Sent from my NX629J using Tapatalk
terrapin4 said:
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Click to expand...
Click to collapse
Terrapin. Absolutely nothing worked. I am the 3rd person who has had this issue I know of. 2 other xda members had the same issue. One with TWRP like me an the other got stuck in fastboot mode after trying g to flash an apk of Gapps? I think these cells do not like tinkering. But your advice enabled me to be OEM and bootloader unlocked. But always.....straight back to fastboot mode no matter what I flash? My red magic 3 device is currently at a service center with a technician trying to solve the problem. I have 3 repayments left on my Xiaomi Mi9 that has zero flashing issues. O admit i.may be ignorant of the ways of Nubia ?
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
emmegitony said:
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
Click to expand...
Click to collapse
Thank God. Maybe the Chinese service guy I'm paying will get on xda an try your idea. I'm being lazy saying that lol. Thanks very very much. I will show your post to the service guy who has my red magic 3 or try it myself.
There's no way your a junior member working all this out. I'm a junior member listed as a senior member who makes rookie flashing errors with Chinese cellphones lol.
I will share if I can implement your ideas successfully. Thanks buddy my missus really loved this phone I felt really bad when I incapacitated it.
Fingers crossed.....
I have no idea how did you managed to flash the system.img
C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
LE: After this error, somehow it manages to continue and flash all partitions of the system, but after above tutorial, the phone still reboots in fastboot mode and cannot access recovery
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
sakilxda said:
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
Click to expand...
Click to collapse
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Bryceicle1971 said:
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Click to expand...
Click to collapse
Hane you fixed the phone or not?
JerryYin said:
Hane you fixed the phone or not?
Click to expand...
Click to collapse
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Bryceicle1971 said:
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Click to expand...
Click to collapse
My suggestions is, download a full sd card update package, unlock the bootloader temporarily,extract the update file and flash the vbmeta.img to vbmeta partion, then flash the recovery.img to recovery partition, after that, try to boot into recovery through bootloader. You have to make sure that you use all the same file from same package, if you are use a low version vbmeta file to boot a high version system (or recovery ) it will not boot. the vbmeta is very important on this phone.
Can't even fastboot flash boot recovery system...and thats all folks...waste of money.
Failed attempt to unlock the bootloader and instal TWRP ?
Hi guys, visit this link. We had similar problems and we could solved that.
Read all and you would get the solution
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
roadworker said:
Failed attempt to unlock the bootloader and instal TWRP ?
Click to expand...
Click to collapse
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.
Just flash the ROM again..It will be back lm
mhex said:
Just flash the ROM again..It will be back lm
Click to expand...
Click to collapse
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked
SuperDroidMe said:
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked
Click to expand...
Click to collapse
Every time you restart back to the bootloader you need to do: "fastboot oem nubia_unlock NUBIA_NX629J" first
SuperDroidMe said:
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.
Click to expand...
Click to collapse
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.
xphyle1971 said:
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.
Click to expand...
Click to collapse
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.
SuperDroidMe said:
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.
Click to expand...
Click to collapse
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot
mswl04 said:
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.
SuperDroidMe said:
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.
Click to expand...
Click to collapse
btw did you rooted the phone?
mswl04 said:
btw did you rooted the phone?
Click to expand...
Click to collapse
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.
SuperDroidMe said:
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.
Click to expand...
Click to collapse
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick
mswl04 said:
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick
Click to expand...
Click to collapse
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?
SuperDroidMe said:
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?
Click to expand...
Click to collapse
all you need to do is to fix the corrupt image so later once you finish the first step of booting to the phone then you can flash to global rom. if you have the cn version 2.27 boot.img then you can download the adb and use the command to fix the phone
Shouldn't have messed with something that wasn't broken. Now you have a nice brick to use as a paperweight. Hope you get it fixed tho. Good luck.
Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.
SuperDroidMe said:
Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.
Click to expand...
Click to collapse
Congrat you finally fix it
Hows your phone?..Did it work.
So i have Korean Version V40 (SKT_KR) on android 10 Q, tried to unlock my bootloader.
First thing i tried was flashing abl_a with V35abl using QFIL, but it got soft-bricked and couldn't get into fastboot mode.
Then i installed stock ROM (android 10Q) using LGUP, after that i redid everything, but i flashed abl_b and it got into fastboot mode on V35 bootloader.
So i thought everything was fine and installed ablpiestock.iso thinking it would work. as you know it was for Android pie and i was on Android 10.
Now im stuck on Fastboot, no download mode, not booting into system, and on the bootloader it only shows power off and restart.
Im just very confused were do i go from here.
Model number LM-v4059N (jydypn)
SKT_KR (Korean version)
Android 10
Device State - Unlocked
Also i know my IMEI if that helps
Cookies_crumbly said:
So i have Korean Version V40 (SKT_KR) on android 10 Q, tried to unlock my bootloader.
First thing i tried was flashing abl_a with V35abl using QFIL, but it got soft-bricked and couldn't get into fastboot mode.
Then i installed stock ROM (android 10Q) using LGUP, after that i redid everything, but i flashed abl_b and it got into fastboot mode on V35 bootloader.
So i thought everything was fine and installed ablpiestock.iso thinking it would work. as you know it was for Android pie and i was on Android 10.
Now im stuck on Fastboot, no download mode, not booting into system, and on the bootloader it only shows power off and restart.
Im just very confused were do i go from here.
Model number LM-v4059N (jydypn)
SKT_KR (Korean version)
Android 10
Device State - Unlocked
Also i know my IMEI if that helps
Click to expand...
Click to collapse
So no, it won't work with ablpiestock on Q. It's unfortunate but the directions, they were written when the person was on Pie, so they wrote it kind of like everyone else would be on Pie.
But what you should have done, before flashing any partition, is to save off the original of what's in that partition. So, you would have abl Q for whatever Q firmware you used lgup to install.
The v35 eng abl will not boot your device. That's because it's Oreo based, it won't boot anything but Oreo roms. But it can be used to unlock the bootloader, then, you flash YOUR original abl back with it, then reboot, and it should be all set.
If you didn't save your newly flashed (lgup) abl partition, then what did u flash? Kr Open 30f ? If so, I have the abl for that. But mention what u flashed and maybe someone will have it.
cheers
AsItLies said:
So no, it won't work with ablpiestock on Q. It's unfortunate but the directions, they were written when the person was on Pie, so they wrote it kind of like everyone else would be on Pie.
But what you should have done, before flashing any partition, is to save off the original of what's in that partition. So, you would have abl Q for whatever Q firmware you used lgup to install.
The v35 eng abl will not boot your device. That's because it's Oreo based, it won't boot anything but Oreo roms. But it can be used to unlock the bootloader, then, you flash YOUR original abl back with it, then reboot, and it should be all set.
If you didn't save your newly flashed (lgup) abl partition, then what did u flash? Kr Open 30f ? If so, I have the abl for that. But mention what u flashed and maybe someone will have it.
cheers
Click to expand...
Click to collapse
thank you for your quick reply, yes its V409N30f_00_LGU_KR_OP_0126.
I managed to install v35 eng abl back.
Also, can you sideload download mode from Bootloader?
Cookies_crumbly said:
thank you for your quick reply, yes its V409N30f_00_LGU_KR_OP_0126.
I managed to install v35 eng abl back.
Also, can you sideload download mode from Bootloader?
Click to expand...
Click to collapse
ahhh good, then follow this link and you'll find the boot+twrp image you need.
So with fastboot, flash this to your current slot boot partition. Then flash this abl to the abl partition. Then, boot to recovery, hold appropriate keys to do that.
follow steps to get recovery / now twrp. If it asks for pw, just cancel. Format data, then reboot recovery. Then flash magisk and dm_verity and you should be all set.
this is abl attached.
AsItLies said:
ahhh good, then follow this link and you'll find the boot+twrp image you need.
So with fastboot, flash this to your current slot boot partition. Then flash this abl to the abl partition. Then, boot to recovery, hold appropriate keys to do that.
follow steps to get recovery / now twrp. If it asks for pw, just cancel. Format data, then reboot recovery. Then flash magisk and dm_verity and you should be all set.
this is abl attached.
Click to expand...
Click to collapse
Okay so im trying to understand
First i fastboot flash abl_b kor_30f (im on b part)
Then i fastboot boot twrp
Them Resart into TWRP using power down + volume down
Then go from here?
Because i get error like this should i also flash to abl_b only?
I renamed abl_b to new, and twrp to boot for easier usage
Cookies_crumbly said:
Okay so im trying to understand
First i fastboot flash abl_b kor_30f (im on b part)
Then i fastboot boot twrp
Them Resart into TWRP using power down + volume down
Then go from here?
Because i get error like this should i also flash to abl_b only?
I renamed abl_b to new, and twrp to boot for easier usage
Click to expand...
Click to collapse
So, no. First and foremost, don't flash anything to anywhere if you don't know what yer doing. That can result in trying to flash too big of an image to a partition that is too small, and you'll the overwrite the images near it, which could (soft) brick the device.
any abl image is only suppose to be flashed to an abl partition. Any Boot image is only suppose to be flashed to a boot partition, etc.
I'd suggest read the directions in the guide again, do ea step one at a time, if yer unsure what to do at any step, post in here, and one of us can clear it up.
cheers
AsItLies said:
So, no. First and foremost, don't flash anything to anywhere if you don't know what yer doing. That can result in trying to flash too big of an image to a partition that is too small, and you'll the overwrite the images near it, which could (soft) brick the device.
any abl image is only suppose to be flashed to an abl partition. Any Boot image is only suppose to be flashed to a boot partition, etc.
I'd suggest read the directions in the guide again, do ea step one at a time, if yer unsure what to do at any step, post in here, and one of us can clear it up.
cheers
Click to expand...
Click to collapse
I first tried loading 30f abl and got this (My active abl was in b):
C:\Users\User\Desktop\adb>fastboot flash abl_b kor_30f_abl_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (1024 KB)...
OKAY [ 0.024s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 0.027s
then i tried with twrp and got the same error:
C:\Users\User\Desktop\adb>fastboot flash abl_b boot-twrp-30f_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (65536 KB)...
OKAY [ 1.384s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 1.386s
im new to this, i really need help
Cookies_crumbly said:
I first tried loading 30f abl and got this (My active abl was in b):
C:\Users\User\Desktop\adb>fastboot flash abl_b kor_30f_abl_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (1024 KB)...
OKAY [ 0.024s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 0.027s
then i tried with twrp and got the same error:
C:\Users\User\Desktop\adb>fastboot flash abl_b boot-twrp-30f_a.img
target reported max download size of 805306368 bytes
sending 'abl_b' (65536 KB)...
OKAY [ 1.384s]
writing 'abl_b'...
FAILED (remote: unknown command)
finished. total time: 1.386s
im new to this, i really need help
Click to expand...
Click to collapse
So, I already told you... DO NOT FLASH WRONG PARTITION IMAGES TO WRONG PARTITIONS!!!
You just indicated trying to do exactly what I told you not to do!! You tried to flash the boot+twrp image (that's a BOOT image) to the abl partition!! THE ONLY THING you flash to an abl partition is an ABL IMAGE! NOT A BOOT IMAGE!!
I understand yer new to this, but don't make the mistake of hacking around doing anything u think **might** work. That's the wrong approach, because it could easily make things much worse than they are.
So again, what are you trying to do? One STEP AT A TIME, tell me the state of the device and what your goal is, I'll try to help you get there, but you have to have patience, don't try to run before u can walk.
cheers
AsItLies said:
So, I already told you... DO NOT FLASH WRONG PARTITION IMAGES TO WRONG PARTITIONS!!!
You just indicated trying to do exactly what I told you not to do!! You tried to flash the boot+twrp image (that's a BOOT image) to the abl partition!! THE ONLY THING you flash to an abl partition is an ABL IMAGE! NOT A BOOT IMAGE!!
I understand yer new to this, but don't make the mistake of hacking around doing anything u think **might** work. That's the wrong approach, because it could easily make things much worse than they are.
So again, what are you trying to do? One STEP AT A TIME, tell me the state of the device and what your goal is, I'll try to help you get there, but you have to have patience, don't try to run before u can walk.
cheers
Click to expand...
Click to collapse
Okay my goal is installing TWRP + CUSTOM ROM
Only thing working now is v35 bootloader, and download mode shows "no command" dialog.
I don't know what i done to the system at this point. Maybe if its better if i install dmz and start from there? im really in deep water now.
please help me, step by step
greatly appreciated
Cookies_crumbly said:
Okay my goal is installing TWRP + CUSTOM ROM
Only thing working now is v35 bootloader, and download mode shows "no command" dialog.
I don't know what i done to the system at this point. Maybe if its better if i install dmz and start from there? im really in deep water now.
please help me, step by step
greatly appreciated
Click to expand...
Click to collapse
okay. So from what you're saying, your current slot (be it a or b, I don't think we know), has the v35 eng abl flashed to the abl partition, that's why all you get when you try to boot is FastBoot.
To install a kdz (not dmz) and start over, you need to have download mode working, as I think you know. To get download mode to work there are some partitions that have to have the same variant and version, they can't be 'mismatched' for it to work.
And since you don't seem to have backups of the files your flashed over, the best I can recommend is to follow this link. In that link are the files needed to get lgup to work. They should ONLY be flashed to the exact partition they are for! Boot to boot, laf to laf, etc etc. (the only one in there not to use is the one with twrp in the name).
They would have to be flashed with qfil, which I think u have set up and used already. So once you've flashed them in qfil, exit out of qfil by holding pwr button and vol dn button. Then, when u hear windows chime (meaning exit), release pwr and vol dn buttons but then press vol up button. That should take u to lgup (download mode) and you can flash a kdz and start over.
Do that, and we'll go from there. cheers
AsItLies said:
okay. So from what you're saying, your current slot (be it a or b, I don't think we know), has the v35 eng abl flashed to the abl partition, that's why all you get when you try to boot is FastBoot.
To install a kdz (not dmz) and start over, you need to have download mode working, as I think you know. To get download mode to work there are some partitions that have to have the same variant and version, they can't be 'mismatched' for it to work.
And since you don't seem to have backups of the files your flashed over, the best I can recommend is to follow this link. In that link are the files needed to get lgup to work. They should ONLY be flashed to the exact partition they are for! Boot to boot, laf to laf, etc etc. (the only one in there not to use is the one with twrp in the name).
They would have to be flashed with qfil, which I think u have set up and used already. So once you've flashed them in qfil, exit out of qfil by holding pwr button and vol dn button. Then, when u hear windows chime (meaning exit), release pwr and vol dn buttons but then press vol up button. That should take u to lgup (download mode) and you can flash a kdz and start over.
Do that, and we'll go from there. cheers
Click to expand...
Click to collapse
They files you shared is for 30c, mine is 30f (Korean version).
Is it okay to use it?
Also is there a certain order do i have to go through? like boot first etc?
cheers for the helps
Cookies_crumbly said:
They files you shared is for 30c, mine is 30f (Korean version).
Is it okay to use it?
Also is there a certain order do i have to go through? like boot first etc?
cheers for the helps
Click to expand...
Click to collapse
yes, I know they are not what you currently have. But it will work to get to lgup, not to boot the device, only to get to lgup.
there's no order, I would have told you an order if there was one.
just re-read what I said. This allows you to go directly from qfil to lgup, use the key combo I mentioned.
It's at that point you can re-flash kor 30f, and start fresh.
Im still getting the same error.
C:\adb>fastboot flash abl abl_30c.img
target reported max download size of 805306368 bytes
sending 'abl' (1024 KB)...
OKAY [ 0.031s]
writing 'abl'...
FAILED (remote: unknown command)
finished. total time: 0.031s
Cookies_crumbly said:
Im still getting the same error.
C:\adb>fastboot flash abl abl_30c.img
target reported max download size of 805306368 bytes
sending 'abl' (1024 KB)...
OKAY [ 0.031s]
writing 'abl'...
FAILED (remote: unknown command)
finished. total time: 0.031s
Click to expand...
Click to collapse
you're suppose to be using qfil, not fastboot.
But how would i enter QFIL if i cannot enter 9008 mode?
why are u unable to enter 9008 mode?
AsItLies said:
why are u unable to enter 9008 mode?
Click to expand...
Click to collapse
I did now, thank you
I was just having problem clicking volume up down button so i thought it was only possible if the phone is booted.
Successfully installed the recovery files and booted into download mode.
Downloading original kdz and hopefully do all this all over again, this time backing up the files
Thank you for all your troubles, you single handedly helped me save my phone.
AsItLies said:
why are u unable to enter 9008 mode?
Click to expand...
Click to collapse
Another surprise, when i tried to install kdz on the phone, it says:
Error: 0x6004, CrossDL
judypn_lao_eea>@judypn_la
Both refurbish and upgrade options show same result.
This is the same version that i successfully flashed before
edit: shoot, i downloaded the wrong version
Cookies_crumbly said:
Another surprise, when i tried to install kdz on the phone, it says:
Error: 0x6004, CrossDL
judypn_lao_eea>@judypn_la
Both refurbish and upgrade options show same result
Click to expand...
Click to collapse
Look in the thread on unlocking in the guides forum, you'll find the information in there to deal with that problem. cheers
AsItLies said:
Look in the thread on unlocking in the guides forum, you'll find the information in there to deal with that problem. cheers
Click to expand...
Click to collapse
Great news, i flashed kdz using patched LGUP with custom cmd line. Now its working as intended, it shows OEM already unlocked in dev options. i patched abl_a to get magisk working ( i think my active slot is A now).
So i got root and magisk, but my goal is still have TWRP and install custom ROM.
So from what i gathered, i install v35 on abl_a, boot into fastboot, flash twrp to boot and flash orignal abl back and restard bootloader.
Or can i just flash twrp into boot_a in QFIL?
cheers