Related
I am trying to go through the process of flashing a custom recovery so that I can get off of stock and on to a custom rom. I have gone through the following steps:
1) downloaded the latest drivers
2) downloaded the latest version of fastboot
3) downloaded twrp 2.8.1.0 and checked the MD5 for the program
4) enabled the usb debugging, signed on as an administrator in my pc, and am using a 2.0 usb port
5) have verified the conenction between tablet and PC.
I get the following result:
C:\>fastboot devices
15C3E100910000000XXXXXXXX fastboot (I edited out a few numbers and replaced them with with x's, but got a pure result)
C:\>fastboot -i 0x0B05 flash recovery twrp.blob
target reported max download size of 643825664 bytes
sending 'recovery' (7024 KB)...
OKAY [ 0.964s]
writing 'recovery'...
OKAY [ 0.241s]
finished. total time: 1.213s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
The recovery is not actually flashing over to the device. When I attempt the flash I do a fastboot reboot and power down afterwards, then try to boot back up to the recovery and instead I get the bried vision of the android and the blue bar underneath before it's promptly replaced by the dead android. The twrp.blob file is in the same directory as fastboot. I have tried deleting and re-downloading both the blob file and the drivers. I have tried using 2.8.0.1 and 2.8.1.0. Because TWRP wasn't working I tried flashing CWM and got exactly the same result. There doesn't seem to be an issue with the cable, since I can move other forms of data between the devices with no issue. I'm beating my head against the wall here, and am hoping that you guys might be able to provide me with some direction as to what else I might try/look for. Thanks all.
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Sleeepy2 said:
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Click to expand...
Click to collapse
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
talion777 said:
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
Click to expand...
Click to collapse
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Sleeepy2 said:
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Click to expand...
Click to collapse
Thanks Sleeepy, but as I mentioned in the OP I did the flash for the CWM recovery already, using exactly the link you sent me, with the exact same commands, and with the same results. No go.
P.P.S. - also tried juggling around the MTP and PTP modes (plug/unplug while on/off) to ensure recognition and it seems fine both ways. Someone else had said they freed up their drivers that way but it made no difference on my end.
P.S. - Here, just so that you see, here are the command window results for th CWM recovery, just for clarity's sake:
C:\adb 2>fastboot devices
15C3E100910000000XXXXXXXX fastboot
C:\adb 2>fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (6646 KB)...
OKAY [ 0.910s]
writing 'recovery'...
OKAY [ 0.230s]
finished. total time: 1.140s
C:\adb 2>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb 2>
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Sleeepy2 said:
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Click to expand...
Click to collapse
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
talion777 said:
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
Click to expand...
Click to collapse
The temp image will work just like normal.
Sleeepy2 said:
The temp image will work just like normal.
Click to expand...
Click to collapse
except that I will always need to be connected to my PC to use it. How do I actually make that the default recovery in my tablet? It just seems bizarre to me that I can boot the image but that I can't flash it. Also, assuming I used the image to flash a custom ROM what happens when the temp image is shut off and the recovery reverts to stock? Would the ROM work with a stock recovery?
Was able to use the CWM image to install SuperSU and root the tablet. Still can't get the recovery to flash over.
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Sleeepy2 said:
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Click to expand...
Click to collapse
I'm on 11.4.1.17, and yes I'm on the latest ASUS update.
Damn... that was my last guess. You need to get the attention of someone smarter than me like pershoot or berndblb
Sorry I can't help any better.
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
talion777 said:
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
Click to expand...
Click to collapse
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
You sir, would appear to be a genius. CWN successfully flashed to the tab. Excellent! Thanks so very much to both you and Sleeepy for your help. This was driving me absolutely bananas!
berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Sleeepy2 said:
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Click to expand...
Click to collapse
A lucky guess.. LOL
Actually I worked with talion on the Transformer forums on his problem, so it was not quite as magical as it may sound. [emoji56]
Long story short, woke up with my N6 stuck at the bootloader screen and cannot do anything at it. I can only see my serial number and if I try anything else, it reloads bootloader. I am trying to flash back to a stock 6.0.1 image, however I keep getting this error while trying to do so.
C:\Program Files (x86)\Android\android-sdk\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.332s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 11.542s
I have tried Nexus Root Toolkit, tried flashing all and tried flashing each image one by one but I still get this "(bootloader) Failed to flash partition FAILED (remote failure)" on all attempts. Phone does show up if I try fastboot devices, and I have tried this on two different computers. Device is also unlocked as well, and I even tried flashing older versions of Lolipop but they all give me the same error. Drivers work fine, and I have everything up to date in terms of bootloader and Andriod SDK. I am starting to think that there is physical damage inside the phone, however I do not know how or why this occurred randomly. Any help would be awesome, as I am very new to flashing images onto my phone and frankly I am 99% sure that my warranty is out, and I really don't want to pay $175 cost .
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
coremania said:
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
Click to expand...
Click to collapse
I've already tried method 2 before so I tried method 1 with the program, and it gives me the same exact error as before. Thanks for the help though, it was worth a shot!
Are you able to enter twrp ? Try to reflash Bootloader through twrp
coremania said:
Are you able to enter twrp ? Try to reflash Bootloader through twrp
Click to expand...
Click to collapse
I did not have TWRP installed on my phone since I had it completely stock and unrooted, so I tried installing it in the hopes of that some chance it would work and I could access it. Still getting the same error as before (grumble grumble). It is starting to look like more of a physical problem to me, but thanks for the advice. Here is what I got...
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11585 KB)...
OKAY [ 0.468s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 6.380s
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
This was going to be my suggestion!!
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Click to expand...
Click to collapse
Any image I even try to flash I get the error with, no matter what order or which one I pick. I redownloaded the image again and still nothing, so I don't think it's a corrupt download. What is the unlock command? Sorry for being a noob, never heard of it since all my knowledge is from reading tons of flashing guides on the internet lol.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
Alright, I downloaded the OTA file and got the process to about 47% when suddenly I keep running into the error of "E:Can't open /cache/recovery/log" then followed by more things it can't open. I tried the OTA twice and it gets stuck on that same exact spot. I tried the wipe data/factory reset option from the recovery mode and I get a similar error of "Can't mount", "Can't open", "failed to mount" the recovery log. It seems like there is a problem with the recovery log files (or the folder) on my phone, but I have no idea what that means. I will mess around with some more and try Googling the source of error, but thank you for the help.
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Click to expand...
Click to collapse
Oh yes, my device has already been unlocked from the start so that wasn't a problem. I still get the same error when I try to flash anything, including TWRP which means I have to install the OTA. The problem is a get a separate error when I try to install the OTA, which the only solution being to flash my device (or at least that is what most people have been saying when I googled the can't open cache recovery error) so this is a giant goose chase which leads me back to the start :/. I will keep trying however, I refuse to give up after going this far!
holeindalip said:
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Should I try fastboot erase cache and then fastboot format cache? Would refresh the cache on there? I only just learned the erase command so I am not exactly sure what I should try.
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
holeindalip said:
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I get the same failure error while trying to format and erase, so I am guessing something is really wrong with my phone or the bootloader is messed up beyond repair. I guess it could be the cable I am using as well, that is one thing I did not take into factor so I will try with another cable if I find a spare. Flashing might be beyond my solution at this rate though... Thanks anyways for the help.
blanco2701 said:
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
Click to expand...
Click to collapse
I really should have had TWRP installed before I guess lol, but I still get the same failure error. My phone has more problems than a teenager going through puberty I swear, thanks for the help though.
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
coremania said:
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
Click to expand...
Click to collapse
I tried it with another wire and nothing changed, and then I tried taking out my sim card and trying it.... and it worked! It flashed everything normally and loaded up just fine. I don't know whether I should be furious or happy but thank you and everyone who helped. Who would have known just taking out the sim card could have saved me 2+ days of stressing and trail and error. Once again thanks, you really saved me lol.
You're welcome, nice your phone works again !
Don't forget to activate oem unlock and debugging in the Developer options, and flash twrp, so maybe more save for upcoming problems
skipsoft android toolkit maybe help you in future
Hello. So, I got my Moto G5s Plus around the last week of October or beginning of November. It is a great device, but I learned about the camera flaws by Motorola and unlocked the bootloader to fix it by following this XDA thread here for camera fixing and the Chromatix mod. I learned that I could edit build.prop without flashing the TWRP recovery but using it temporarily following the guide here. build.prop edit would enable cam2api for third party cam apps. The Chromatix mod threads/posts were for the G5 Plus, which I didn't realize at the time and didn't backup original Chromatix files. However, That went successfully and I could still use my phone with better camera quality. Note that prior to doing this fix and before unlocking the bootloader (I believe) I had updated my device from Nougat to Oreo. My bootloader is indeed unlocked.
Now, when the 1 October OTA Update came I was hesitent because I had came across some rooting/custom rom/custom recovery/mod articles while learning about unlocking the bootloader. Yet and before reading more to get educated on this, I applied the update to my phone. I was hoping it wouldn't brick it or that it would fail if it didn't work. It failed (because of the modification on the stock ROM) at the last bit of the update and rebooted my phone. My phone worked and it let me know nothing was changed by the failed update. However, my phone since then has shown as if it is up-to-date in system updates.
So, basically I have been trying to flash TWRP for my Moto G5s Plus after that was done. I want to see about backing up my stock ROM (or the most important parts) possibly getting a good custom ROM installed (which I believe they have their own official Android security updates from Google?). However flashing TWRP hasn't worked. I get the following in PowerShell (cmd):
PS C:\Android SDK\platform-tools> fastboot flash recovery twrp.img
Sending 'recovery' (10236 KB) OKAY [ 0.407s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.172s]
Finished. Total time: 0.594s
Note that I renamed twrp-3.1.1-sanders.img to twrp.img as it was a suggestion I followed at the time. This I heard is normal, but when I go to Recovery Mode on my phone I see this:
Start Up Failed:
Repair message stuff
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
~~~
Error: failed to load kernel!
~~~
I also tried to find the latest stock ROM to flash because I believe I read I may need to do that. I found SANDERS_RETAIL_8.1.0_OPSS28.65-36-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and tried to use "Apply update from ADB" from the stock Recovery (when it was working normally after powering off and not with kernel errors because of this). It failed.
I couldn't find the right answer(s). Thank you to anyone that can help me or others who have done the same!!
EDIT (11/19/2018):
So, last night I tried wiping my data in stock recovery and then I tried to do this again. It still didn't work. I also tried to apply the same stock zip as well as boot_magisk.img from this thread here https://forum.xda-developers.com/moto-g5s-plus/development/stock-kernel-prerooted-8-1-0-t3863301.
PS C:\Android SDK\platform-tools> fastboot flash boot boot_magisk.img
Sending 'boot' (10702 KB) OKAY [ 0.391s]
Writing 'boot' (bootloader) Image not signed or corrupt
OKAY [ 0.141s]
Finished. Total time: 0.563s
It all still fails. However, now when I boot up my phone it goes straight to the bootloader instead of loading the OS right away. I can select START to start the phone normally from there.
I got all this resolved through XDA's Telegram group (& specific group for G5s Plus/sanders)! I have TWRP (Treble) and custom rom working after getting an official stock rom from them flashed using fastboot commands!
I don't know if I should or a mod can close/erase this thread now?
Try typing fastboot oem fb_mode_clear while in bootloader
Coala990 said:
Try typing fastboot oem fb_mode_clear while in bootloader
Click to expand...
Click to collapse
Thanks for the suggestion/tip. I will probably try that if I reflash twrp treble (or another version of twrp for Sanders) again. This has been resolved.
I managed to brick a moto G7 plus to the point of not being able to recover from it (locked bootloader, no twrp, boots to fastboot)
I wanted to go back to 100% stock but failed badly.
My device is odd one. RETLA stream with XT1965-T hardware. Lenovo Rescue apparently don't work on these devices.
1) I flashed stock RETLA latest rom from Lolinet using a flash.bat I made
2) worked and booted fine.....twrp was still intact
3) I did factory reset when booted in.
4) To relock I flashed boot.img and sent lock command a few times
5) Bootloader is now locked but only boots to fastboot and get (YOUR DEVICE HAS LOADED A DIFFERENT OPERATING SYSTEM.
6) I cannot unlock with code because adb says says I need developer option etc.
To repeat: this is BOOTLOADER LOCKED, JUST BOOTS TO FASTBOOT and gives "your device loaded a different operating system) which is not the issue and I expected that.
Bankflash didn't do anything. I mostly get oermission denied with mostly flashing anythiine else.
Any suggestions on how to just get this thing at least bootable again to use?
Thanks.
I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.
Anrito Kun said:
I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.
Click to expand...
Click to collapse
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/
Anrito Kun said:
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/
Click to expand...
Click to collapse
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s
PROBLEM SOLVED. See my post.
https://forum.xda-developers.com/t/moto-g7-plus-no-service.4201229/post-84335207
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