Related
Hi there,
I have a problem that my LG will not boot the device is stuck at the logo, I've also done a hardware reset but the process also depends on the logo proof and 10min not happened.
In the download mode, I'm not coming.
About the fastboot mode I try to start TWRP, but it appears the TWRP logo and nothing else happens.
How did you manage to get it to this point? What did you do before it didn't boot anymore?
Also, if you manage to get adb access somehow you can just reflash the recovery again
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
So you cant enter download mode or recovery? And you cant turn on phone?
No download mode is not only possible fastboot mode. If I we want to install Recovery in fastboot mode, shown below
Command: fastboot flash recovery recovery .img
Error on LG G3:
Error: Command never completed
Error: Auto CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror:Command completed with errors
Failed to send stop command
Failed Writing block @1
SourceCoder said:
No download mode is not only possible fastboot mode./QUOTE]
Could you please explain this.
Is comma missing somewhere?
Click to expand...
Click to collapse
The following screen appears:
lgg3root.com/wp-content/uploads/2014/08/howto-unroot-unbrick-lgg3-2-690x492.jpg
And then immediately this screen:
android-hilfe.de/attachments/root-custom-roms-modding-fuer-lg-g3/345262d1415303724-lg-g3-kein-download-modus-mehr-img_20141106_093950.jpg
This screen does not appear:
androidheadlines.com/wp-content/uploads/2014/07/LG-G3-Download-Mode-AH-1.jpg
SourceCoder said:
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
Click to expand...
Click to collapse
Something does not compute in this at all. SuperSU should not have caused your phone to brick like that.
Is there something else you are not telling us about how your phone was set up? Were you doing anything before you updated SuperSU? This looks like a case of where you flashed the wrong image on your phone, if you ask me.
SuperSU is not phone specific, so I'm having a hard time believing SuperSU did this.
Something else must have happened that you are not telling us. You need to lay out in order, everything you did to your phone up to the point of updating SuperSU.
Also, SuperSU asks how to update: normal or via recovery. Which way did you choose? Either one shouldn't matter, but it's a start.
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1
SourceCoder said:
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1
Click to expand...
Click to collapse
Did you flash the correct laf.img file for your model of phone? If not, that could be part of it. What model of the G3 are you using and where exactly did you obtain the laf.img file from?
SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
SourceCoder said:
SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
Click to expand...
Click to collapse
Well, there you go. I have NO idea for what version of the G3 that thread was for. The guy never states which version it is. You do not, repeat, do NOT flash anything to system, boot, etc for this phone unless you know for sure it's for YOUR model of the G3. There are various models of the G3. For example, mine is the Verizon model (VZ985). There is an AT&T model (DS855), and numerous others, especially for those overseas. I would not and should not flash the DS855 boot image to my VS985 boot image. It will brick the phone as you have found out the hard way from what I can tell.
You just flashed something you have NO idea which version it was for. You may have completely bricked your phone. I'm not entirely sure, but you need to find the correct stock images for your phone and flash them back.
You need to go here and figure out which model of G3 you have:
http://forum.xda-developers.com/showthread.php?t=2791269
After that, you need to go and find the correct stock image files and flash those back onto your phone. Since this are NOT img files, you cannot fastboot flash them. You muse use either KDZ or TOT files depending on which ones are available for your model of phone:
http://lg-firmware-rom.com/
or
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
Then, you have to use the correct tool to flash these files depending on if they are KDZ or TOT file:
http://forum.xda-developers.com/showthread.php?t=2785089
Hopefully, flashing back to the correct stock image will fix you up. However, you better make darned sure which model of phone you have BEFORE you even attempt it. Once you figure out which model of G3 you have, post here and ask. Otherwise, you could bork your phone up even worse to where it may not be recoverable. Hopefully, it's not at that state right now.
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Again, did you verify with the link you posted for the image file that it was indeed for YOUR model of your phone? If not, you probably have bricked it.
You need to go and follow the links I posted which tell you how to flash back to stock.
There was no reason to go into fastboot mode for SuperSU. I don't know why you felt you had to do that.
Also, the second link you posted has the thread pretty much deleted. The OP said he was incorrect in what he posted (whatever it was I don't know since he deleted it), so it was removed due to it not working as stated.
Go back to the links I posted to flash back to stock on your model. If what you say you have is the European model, then this would be the KDZ file you want:
http://storagecow.eu/Xda/LG G3/Stock/Europe Common 16G D85510A_00.kdz
I would verify for sure that is what your phone is before continuing or else, you'll bork your phone up even worse than it is already.
The boot image you flashed is probably for the Korean version of the phone and that's why everything is messed up.
If you are not sure on how to do this, then you might want to find someone near you who does.
Just remember, just because a post says it's for the G3 doesn't mean it's specifically for YOUR model of the G3. You need to verify for sure that it is. Most have the model number in the thread's title.
LG G3 Fastboot
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
[1700] fastboot mode started
razaaliarain said:
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
Click to expand...
Click to collapse
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
_narisha_ said:
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
Click to expand...
Click to collapse
But now i am stuck again on fastboot mode and this time i was not rooted and did not had twrp installed so now when i try to use the "fastboot boot twrp.img " my device will reboot and then will be stuck on twrp logo on the screen
I have the same problem...
I ran stock OTA update 20f, since a couple of weeks ago. While I had my phone on the table and it was runing voice recorder soft it restarted once and then after a couple of minutes again. This time it never booted but stuck at the LG screen.
Never rooted, never installed anything other than the OTA 20e and 20f updates. I have not flashed anything to the phone other than the official OTA.
Doesn't boot to anything other than fastboot. Recovery starts but after confirming twice it reboots and stuck still.
If I boot to Download Mode it goes to fastboot, if I wait long enough on regular boot that only shows the LG logo it will eventually go to fastboot.
Running "fastboot.exe boot openrecovery-twrp-2.8.4.0-d855.img" gives me the same error messages, stuck at the TWRP logo screen. I found the ADB port is connected but when running "adb devices" it says "LGD855..... offline". I didn't enable ADB before the device crashed and I can't enable it in TWRP because it doesn't start properly.
I have the 32GB D855 European unlocked. I belive this is hardware problem and will send it for repairs.
SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
gee2012 said:
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
Click to expand...
Click to collapse
That's right. I tested to boot Philz recovery and it freezes at the text.
Mine says actually:
Error: Command never completed
Error: Auto CMD12 error
Error: Command never completed
Error: Command timeout error
Failed to send stop command
Failed reading block @ 1
mmc read failure misc 2048
The CMD12 is according to emmc spec a "Stop command".
So this is a hardware fault and not a software one.
My ZE551ML was rooted and I decided to update it being unaware that I was supposed to unroot it before updating. Once I got to the recovery menu, I attempted to sideload the newest firmware but the device was not found despite being able to be found during the bootloop. I then performed a factory reset and now it is stuck on a bootloop and cannot be detected by adb at any point.
U can use fastboot to flash ur device
But be careful with it u can hard brick ur device if done the wrong way
Sent from my Karbonn A1+ Super using XDA Free mobile app
yakub234go said:
U can use fastboot to flash ur device
But be careful with it u can hard brick ur device if done the wrong way
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
But how do I fastboot to flash? Every tutorial I found told me to use adb sideload which I never found possible.
Edit:
I solved my problem by copying the firmware I downloaded into an external sd card under the name MOFD_SDUPDATE.zip and going to recovery mode.
download full firmware according to ur device from here https://mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw give Thanks @shakalaca for this
download (Z00A)2.19.40.18 if u want to unlock ur bootloader cause latest one cause problems with unlocking bootloader
when the device is off press power wait till it vibrates once then immediately press vol up button
u will boot into fastboot mode
there u can use fastboot commands
now form ur pc go to the path where u downloaded the firmware
press & hold shift & right click
select open command window here
now in command prompt give these commands
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
all done ur device will reboot
now u have a rooted device
remember if u want to update than first unroot it reboot than update
where do u get the system.img?
im also in a similar situation where im out of usb debug cause of factory reset
loganj said:
where do u get the system.img?
im also in a similar situation where im out of usb debug cause of factory reset
Click to expand...
Click to collapse
Here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
ultramag69 said:
Here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Click to expand...
Click to collapse
thank you
well i manage to do adb sideload even though my phone was wiped completely clean from recovery and still unable to start the android.... it was a miracle . but thanks to your link i know now how to get the system.img
now if i can only understand what system.img is compare to entire firmware zip.....probably i should try to mount one and have a look
loganj said:
thank you
well i manage to do adb sideload even though my phone was wiped completely clean from recovery and still unable to start the android.... it was a miracle . but thanks to your link i know now how to get the system.img
now if i can only understand what system.img is compare to entire firmware zip.....probably i should try to mount one and have a look
Click to expand...
Click to collapse
System.img is the entire firmware except for boot, droidboot and recovery... These can be flashed separately BUT make sure you use the right commands...
If you get to the usb symbol only displaying on your screen, you've stuffed up and it is a true brick...
yakub234go said:
when the device is off press power wait till it vibrates once then immediately press vol up button
u will boot into fastboot mode
there u can use fastboot commands
now form ur pc go to the path where u downloaded the firmware
press & hold shift & right click
select open command window here
now in command prompt give these commands
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
all done ur device will reboot
now u have a rooted device
remember if u want to update than first unroot it reboot than update
Click to expand...
Click to collapse
Hey the procces struck whe i flash system img, stuck at "sending sparse 'system' (524056 KB)" Can you help me please?
After a long time waiting, probably over 1 hour i touch my phone screen then it just powered off suddenly. I really need help please
EDIT: i figured out that when sending sparse, after 10 second my phone just turned off
Maybe this tutorial works for you: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=12528
Sent from my GT-I9500
krasCGQ said:
Maybe this tutorial works for you:
Sent from my GT-I9500
Click to expand...
Click to collapse
I can't access my phone, how am i gonna turn on USB Debuggin when it's on bootloop ?
okokokokok i meet it
i have done adb side load but cant turn my phone. so, i went fastboot mode to flash it. but the bootloader is locked and cannot unlock it. when i enter the command flashing unlock,there is no response in the command prompt. can you also tell me how can i turn on usb debugging without switch on my android phone
I have the same problem than vinod.katakam!
I try to update my Asus Zenfone 2 Laser (ze601kl), to a recente version of Android, because i'm stuck on a older version of Lollipop.
My system had a SKU WW, so i downloaded the recent version WW (marshmallow) from Asus website, and treid to update, and that gives me an error. But i reboot the phone a it works fine. But still on my old android version.
Then i tried to just update to a more recent version of Lollipop, the process appears to start fine, but then it gives me an error. Now, i tried to reboot and i end up with a endless bootloop.
I tried everithing, update by adb (cant open the file), update by sdcard (E:Error in /sideload/package.zip (Status 1) E: fota_return_code 408), and fastboot boot.img, recovery.img, but on system.img says the file is to big.
I dont have de USB Debbugind activated. Is that a problem?
I dont have important data on the phone, i just want to make it work again.
Please help!!!!
pedrofg said:
I have the same problem than vinod.katakam!
I try to update my Asus Zenfone 2 Laser (ze601kl), to a recente version of Android, because i'm stuck on a older version of Lollipop.
My system had a SKU WW, so i downloaded the recent version WW (marshmallow) from Asus website, and treid to update, and that gives me an error. But i reboot the phone a it works fine. But still on my old android version.
Then i tried to just update to a more recent version of Lollipop, the process appears to start fine, but then it gives me an error. Now, i tried to reboot and i end up with a endless bootloop.
I tried everithing, update by adb (cant open the file), update by sdcard (E:Error in /sideload/package.zip (Status 1) E: fota_return_code 408), and fastboot boot.img, recovery.img, but on system.img says the file is to big.
I dont have de USB Debbugind activated. Is that a problem?
I dont have important data on the phone, i just want to make it work again.
Please help!!!!
Click to expand...
Click to collapse
if you are on 64 bit windows and fastboot flash system system.img gives you error. probably you are not using 64 bit fastboot tool below is the link to 64 bit tool
https://drive.google.com/open?id=0B72QQTXqZSRwUkFRMl81b1pWa0k
The problem still remains!
The problem still remains!
"C:\adb>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.022s]
sending sparse 'system' 1/12 (259338 KB)...
OKAY [ 11.418s]
writing 'system' 1/12...
FAILED (remote: size too large)
finished. total time: 11.471s"
Hello guys!
Well, i manage to understand my problem and solv it!
I bought my phone from Gearbest, and the problem begins there. Why? Because, regarless my phone is a CN device, it came somehow with a WW sku. You must know that a CN device have system partition smaller than the WW device.
So, when i tried to updated it with a more recent WW system there was no room for that, and the instalation stops with a error message.
After many "Trial and error", i understand what my problem is, and tried to install a CN system version by "fastboot flash" with a system.img with root that i find here: "https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw"
To fastboot i used the fastboot tool that sukhwant717 told me to, in the post #15.
Well, that worked, so i now have a phone working. Them i go to Asus website and downloaded the latest CN firmware to my divece, copy it by USB to the internal memory of my device and upgrade it.
So, now i have a phone working with a factory system but with no google apps.
I found this website with google installer: "https://www.digitbin.com/google-installer-apk/" follow the intructions and finaly i have Google play in my phone!
Now everithing works fine!
I hope that my story could help someone with the same problem!
Red error message on boot: "Device Corrupted" (different than bootloader unlock mess)
Was on Qbeta6 and working fine. Wanted to flash complete image of latest pie image PQ3 using fastboot "flash-all.bat" command. After it's done, now we have this. It won't boot into Android. Try to flash an older PIE PQ2 and the same thing. I can still get access to fastboot and stock recovery. TWRP got wiped too. Try OTA side-load rescue but it said that "matrix incompatible" and OTA file won't verify correctly so would not flash. (OTA is higher than current PIE of PQ2 = first PQ3 OTA file). Please help.
HueyT said:
Was on Qbeta6 and working fine. Wanted to flash complete image of latest pie image PQ3 using fastboot "flash-all.bat" command. After it's done, now we have this. It won't boot into Android. Try to flash an older PIE PQ2 and the same thing. I can still get access to fastboot and stock recovery. TWRP got wiped too. Try OTA side-load rescue but it said that "matrix incompatible" and OTA file won't verify correctly so would not flash. (OTA is higher than current PIE of PQ2 = first PQ3 OTA file). Please help.
Click to expand...
Click to collapse
As long as you have access to fastboot you'll be ok
Fastboot flash bootloader, radio and vendor on both slots one by one to August pie, then you can either fastboot update (system.img) or ADB sideload the ota or use a type c thumbdrive with the files you need (ota, TWRP.zip, ROMs) and mount it in TWRP.
Edmontonchef said:
As long as you have access to fastboot you'll be ok
Fastboot flash bootloader, radio and vendor on both slots one by one to August pie, then you can either fastboot update (system.img) or ADB sideload the ota or use a type c thumbdrive with the files you need (ota, TWRP.zip, ROMs) and mount it in TWRP.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Deuces script saved me. Thank you for yourhelp.
I just got this error after unlocking the bootloader and then attempting to flash a clean Factory mage. I just ensured my adb tool set was updated. Downloaded a new factory image and then flashed all. Once it was complete the message was gone. My toolset was old so it wasn't flashing correctly.
Hello everyone! So I have a OP7T 1907 TMobile variant, and I've been following this guide to convert it. I have done it successfully a long time ago. I went to update to android 11 and after a while my flashing stopped working, I finally figured out the problem. I was getting the error. "fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
I was stuck here for a while so I deleted the adb folder and went to bed last night. I woke up and it suddenly was working again. I tried to update to Android 11 and it bootlooped my phone, I tried to reflash but I had already relocked the bootloader, and the command "fastboot flashing unlock_critical" would return the error I had to flip the enable oem unlock switch. So I plugged into the MSM tool and hit start. I am now stuck at the same fastboot error. Any ideas?
After trying a bunch of different stuff, flashing the international rom and it stopped. I guess that put back some files that I was missing. I was then stuck with the tmo splash screen that goes nowhere, I then restarted and I finally go to the fastbootd screen. I wiped all data. After that fastboot reboot fastboot worked, idk if I just once again got lucky or not. But It worked
having same problem, can anyone explain how to enable fastbootd for oneplus 7t indian variant?
You need stock recovery (not twrp, los recovery, etc) for fastboot reboot fastboot to enter fastbootD mode (looks like stock recovery mode with 2 lines of Chinese and 1 line of English)
HueyT said:
You need stock recovery (not twrp, los recovery, etc) for fastboot reboot fastboot to enter fastbootD mode (looks like stock recovery mode with 2 lines of Chinese and 1 line of English)
Click to expand...
Click to collapse
Not entirely true, though.
Both LOS recovery (like the one from StatixOS or Pixel Expierience) and TWRP (the unofficial 3.5.1_10) have working fastbootd.
I don't think the same can be said about the Chinese TWRP, or mauronofrio's version, however.
Good 2 know. Thanks
open platform tools zip (fastboot&adb) place everything you want to flash in same folder as open zip (it can be whole payload extracted) and that will fix fastboot error
ecompton59 said:
open platform tools zip (fastboot&adb) place everything you want to flash in same folder as open zip (it can be whole payload extracted) and that will fix fastboot error
Click to expand...
Click to collapse
I don't think this is true.
Hi Team,
I have an spare Nokia 6.1 (2018) smartphone (Model # - TA -1089)) at my home which I wasn't using since 2-3 years.
Today, I got hands on it, and tried to use it for my development needs.
To begin with, I unlocked its boot-loader using this guide to unlock Nokia 6.1 (2018)
and within "Developer Options", I can see that the "OEM Unlocking" option reads - "Bootloader is already unlocked."
Now, as a next step, I am trying to install TWRP recovery, but nothing seems to be working. No matter which image I try, I get stuck on the TWRP splash screen.
I have tried TWRP Images from the following websites and many more:
TWRP.me
Get Droid Tips - Here when I click on the "Download" option, I get redirected to the "TWRP.me" website only, whose images are not working.
In addition, I have ensured that "ADB and Fastboot" + "Nokia USB Drivers" & other contingencies are properly installed on my system & are not the underlying issue.
I tried running the code
Code:
fastboot flash recovery twrp.img
and my phone got stuck on the TWRP splash screen. Ultimately, I had to use OSA tool and flash the STOCK ROM to get my device working again.
Many websites suggested to simply boot the TWRP and so I used this command:
Code:
fastboot boot twrp.img
in the "Download" mode and then again, nothing happened and I got stuck on the TWRP splash screen.
Note: The only difference between above two commands being - my stock recovery worked fine after executing the 2nd command, and I could boot into my device without much trouble.
Here's my Device Overview:
Device Name - Nokia 6.1
Model & hardware = TA-1089
OS version - Android 10
Security Patch Level - May 1, 2020
Build Number - 00WW_4_15c
Can someone now please suggest where I could be going wrong?
What's my goal:
Root Nokia 6.1 & to be able to install Custom ROM's on Nokia 6.1 and use that device for development purposes
and in case anything goes wrong,
Flash the STOCK ROM again using OSA Tool and bring the device back to its current state.
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
And also not fla#h
It is a/b partition so only boot done your goals and boom
Everytime you need to temporarily boot twrp
White_devil_04200 said:
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
Click to expand...
Click to collapse
Hi @White_devil_04200
Thank you for redirecting me to this Telegram channel.
However, let me share that - On the channel, I found "twrp-3.3.1-1-PL2.img" listed as the TWRP image that works.
The conflict is that - I downloaded this version only from multiple sites & after flashing it, got stuck on TWRP splash screen. I had to use OSA tool to reflash Android OS & restore the stock recovery.
And, when I ran the code -
Code:
fastboot boot twrp.img
, then also I got stuck on the splash screen, but was able to reboot into the OS successfully.
Note: Also, I tried switching the slots too (from 'a' to 'b' or vice versa') but then also, nothing worked for me.
I hope you get my problem, and would now assist me accordingly.
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Bảo Dora said:
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Click to expand...
Click to collapse
Thanks @Bảo Dora for sharing your TWRP file and for the instructions.
I was finally able to boot into TWRP (used another file, of course), and then successfully get "root" access on my device.
Also, I read that if you execute the command:
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
you shall permanently install TWRP on your device, which may or may not be the first preference of many users.
Having said that, am glad that it worked out for you. However, I still prefer to use just the "boot" command to avoid changing my stock recovery.
Thanks for your help again.
Cheers,
Manu
For potential readers of this thread, I would like to explain one thing here.
"fastboot flash recovery twrp.img" does NOT change your stock recovery on Nokia 6.1. Because this phone has "A/B system updates" and due to that the recovery RAM disk is now contained in the boot.img file. So Nokia 6.1 has not recovery partition so if you execute the "fastboot flash recovery twrp.img" command it only shows an error message and nothing is changed on your device.
Common issue on Nokia 6.1 is that when you execute only this one command "fastboot boot twrp.img" then it stucks on androidone logo.
But for some special reason, if you execute "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" it successfully boots into TWRP recovery.
Really there is nothing to worry about. This procedure is safe and really works.
White_devil_04200 said:
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
Click to expand...
Click to collapse
And also wipe data with help of fastboot ! Yes it is important if you facing stuck on twrp logo
mAnN14 said:
Thanks @Bảo Dora for sharing your TWRP file and for the instructions.
I was finally able to boot into TWRP (used another file, of course), and then successfully get "root" access on my device.
Also, I read that if you execute the command:
you shall permanently install TWRP on your device, which may or may not be the first preference of many users.
Having said that, am glad that it worked out for you. However, I still prefer to use just the "boot" command to avoid changing my stock recovery.
Thanks for your help again.
Cheers,
Manu
Click to expand...
Click to collapse
Hi,
which file did you use at the end? i have the same problem..
AndreaMariaBono said:
Hi,
which file did you use at the end? i have the same problem..
Click to expand...
Click to collapse
Let me try and find that file link again bro. It's been time I performed the root process, so I will have to search for it.
Will share it with you at the earliest.
Till then, stay calm and be safe.
Bảo Dora said:
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Click to expand...
Click to collapse
I accidentally found a way to permanently install twrp on nokia 6.1..you don't have to temp boot it every time
sayanmitra753 said:
I accidentally found a way to permanently install twrp on nokia 6.1..you don't have to temp boot it every time
Click to expand...
Click to collapse
I don't think it works...
MricCall said:
I don't think it works...
Click to expand...
Click to collapse
Bro it works in real..i am using it on my device
use comand
adb erase userdata
then
adb erase system
adb arase vendor
then fastboot reboot
Hello,
i have nearly the same problem atm.
I successfully unlocked the device.
When i do to 'fastboot boot twrp.img' in 8 of 10 cases it stucks on Android One screen but sometimes it stucks at twrp boot screen.
I have tried multible twrp versions for Nokia 6.1 PL2.
I also tried 'fastboot flash recovery twrp.img' but here comes a adb error that says:
Sending 'recovery' (38592 KB) OKAY [ 1.064s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
On Galaxy S6 this works fine for installing permanently but here i event cant boot into twrb.
Any advices pls?
N0t3xx_A said:
Hello,
i have nearly the same problem atm.
I successfully unlocked the device.
When i do to 'fastboot boot twrp.img' in 8 of 10 cases it stucks on Android One screen but sometimes it stucks at twrp boot screen.
I have tried multible twrp versions for Nokia 6.1 PL2.
I also tried 'fastboot flash recovery twrp.img' but here comes a adb error that says:
Sending 'recovery' (38592 KB) OKAY [ 1.064s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
On Galaxy S6 this works fine for installing permanently but here i event cant boot into twrb.
Any advices pls?
Click to expand...
Click to collapse
"fastboot flash boot recovery.img" and reboot into recover using Vol+ & Power.