I have seen some people suffering this issue like I did before and Other guys just offering the advice of " Use LG flash tools to flash to stock"
Yes, it could solve the problem. But it takes so much effort and hustle to fix such a easy issues.
There is always a easy way to solve a problem. Keep reading.
This method should work for LG Optimus G Pro using the same recovery. Like E980, E985, E986. I only try this on my phone (AT&T E980)
Issue:
Your phone keep boot into CWM or TWRP all the time, no mater what you did- factory reset, wipe system, install new rom. It just keep going into recovery all the time.
What might cause this:
You install recovery in your phone and when you are in stock rom, you accidently hit "check update" and " install update".
You might not remmeber you did that , and the system just pop up showing " update available", and you click it....That is how the nightmare starts.
How to fix
If you are using CWM, try this method: http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70 But I personally like the TWRP method below ( just flash TWRP over CWM and use the TWRP method bellow)
remember hit thanks to @chappatti
Following these steps:
1.a. If you are stuck on CWM OR TWRP boot loop DO NOT DO ANYTHING YET to the phone or anything. All you need to do is delete the "fota" file. keep reading
1.b. YOU MUST HAVE ADB INSTALLED AND WORKING.
1.c. Open cmd prompt as admin and run "adb devices". If you get
"List of devices attached
XXXXXXXX recovery" GO TO STEP 7.
If you HAVE adb installed and get no device output....continue from 2.
Otherwise, INSTALL ADB.
2. With the phone in CWM plug it into the computer.
3. Your computer MAY not see the phone. i.e you will get the ping noise for USB cnnection, but if you look under
COntrolPanel>>>>DeviceManager you will see a yellow exclamation mark. The next part I figured by trial and error.
If your phone is seen properly go to step 5.
4. If 3: although I installed the drivers again, if you had the phone working on adb before try this step:
4.b. Press and hold the Volume DOWN (volume decrease) button and hold the power button.
NOTE: I am not 1000% whether volume up or down did it. Try each one.
HOLD until the phone goes off and reboots. After the LG logo release the power. You will see black and white text as the phone tries to go into factory reset. It will ask if you want to factory reset...... SAY NO by pressing volume down button. During reboot my computer saw my phone and installed the driver. Phone was still on CWM recovery now.
4.c. If 4.b. did not work reinstall following drivers (attached rar): I do not know which worked, if any
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.1 0.1
minimal_adb_fastboot_v1.1.3_setup
UniversalAdbDriverSetup
LGPCSuite_Setup
http://www.mediafire.com/download/1j...nd STUFF.rar
5. These steps I got from this forum post here: I DO NOT CLAIM ANY CREDIT http://forums.androidcentral.com/t-l...ot-loop-2.html
6. Open cmd promt as administrator.
7. Run "adb devices"
You will get
"List of devices attached
XXXXXXXX recovery" Now you are good to proceed
Enter the following one by one
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
it will say xxxx info in and out or soemthing each time.
Type "exit" to leave adb shell.
Then "adb reboot". This will reboot your phone and all is great !!
If you are using TWRP, or the method above did not work for you, flash TWRP as your recovery, then using this TWRP method.
remember to hit thanks to @thecubed here is the post: http://forum.xda-developers.com/showthread.php?t=2451696
you can simply use TWRP's awesome "terminal command" option to run the following code
go to "Advance" " Terminal Command", select the current folder( root folder), and type the following code:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
I took no credit for these method, they are work of other XDA members.
Hit thanks if any of us help you solve your problem.
This is VERY good work! THANK YOU!
Sent from my LG-D415 using XDA Free mobile app
Hi there, this is my first post i think so please be kind.
I am tearing my hair out over my LG G4, because for the life of me I cannot root or install TWRP recovery.
here is the information i think you'll need to help me:
- LG H815 International version (bought in the UK)
- Official Android 6.0 update
- Bootloader unlocked with official LG tool
I have downloaded TWRP and placed it in the folder along with my 'adb fastboot win' tools.
I type: "adb reboot bootloader" and i get the 'Welcome to fastboot mode' message and quick guide.
then i type "fastboot boot twrp.img" and press enter i simply get "cannot load 'twrp.img' : No error"
and that's it. It seems I need TWRP installed to root using SuperSU, but i need root access to install TWRP any other way. I've spent hours and hours trawling through forums for an answer but can't find it anywere.
Any help will be greatly appreciated as I am almost at the end with this phone... :crying:
Thanks!
SirJackington said:
Hi there, this is my first post i think so please be kind.
I am tearing my hair out over my LG G4, because for the life of me I cannot root or install TWRP recovery.
here is the information i think you'll need to help me:
- LG H815 International version (bought in the UK)
- Official Android 6.0 update
- Bootloader unlocked with official LG tool
I have downloaded TWRP and placed it in the folder along with my 'adb fastboot win' tools.
I type: "adb reboot bootloader" and i get the 'Welcome to fastboot mode' message and quick guide.
then i type "fastboot boot twrp.img" and press enter i simply get "cannot load 'twrp.img' : No error"
and that's it. It seems I need TWRP installed to root using SuperSU, but i need root access to install TWRP any other way. I've spent hours and hours trawling through forums for an answer but can't find it anywere.
Any help will be greatly appreciated as I am almost at the end with this phone... :crying:
Thanks!
Click to expand...
Click to collapse
1. So do you have renamed the twrp file to twrp.img?
2. Give the link where you taken the twrp image from
3. Attach a screenshot of the error message
4. When in download mode type
fastboot devices
And make a screenshot of that output, too
.
Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...
oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)
Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .
Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?
TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work
in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?
So I have hit a wall.
I have an old HTC One M8 - I want to root it and play with it.
I have Mint 19 installed on my old Thinkpad, I want to start learning Python and GO and doing things with Android.
So I successfully unlocked the bootloader last night I can't even remember how but I followed instructions and did it.
Now I am trying to root using TWRP and running into issues.
I have platform-tools on my desktop (I found it somewhere via these XDA Forums)
I have (I believe) a good TWRP HTC One M8 recovery image in that folder, named recovery.img
i got that through a link on here somewhere too.
I can successfully boot to the white text menu by restarting and holding power and volume down, and it says Fastboot USB
From there on my PC I open a command prompt in the platform-tools folder and put in the recommended command line:
fastboot flash recovery recovery.img (I have renamed it recovery.img)
It says it successfully flashed, but after this I cannot figure it out, it keeps booting to regular HTC start up screen.
I have SuperSU on the phone ready go to - I understand this would be the next step.
I also have the TWRP program on the phone but it doesn't do anything, the only thing I can do with it is download the iso for One M8 again.
Any ideas?
I am missing something here, I cannot boot into TWRP after its flashed.
Thanks
I tried countless methods to download TWRP on my Nokia 6.1 (TA-1043), but the closest I got was getting stuck on the TWRP logo. The phone has the stock rom btw.
epicAndroid08 said:
I tried countless methods to download TWRP on my Nokia 6.1 (TA-1043), but the closest I got was getting stuck on the TWRP logo. The phone has the stock rom btw.
Click to expand...
Click to collapse
Hi,
If your intent to use TWRP is to Root Nokia 6.1 device, please avoid flashing the TWRP as it can brick your device. I too tried 'n' number of TWRP images, but nothing worked and ultimately every time, I had to flash my STOCK ROM to get back into my device and the recovery.
However, if you're using it to simply obtain root, follow the below-mentioned steps that helped me root my device after struggling for nearly 2-days.
Here's how I did it:
NOTE: I used Magisk instead of TWRP to obtain Root.
The actual steps that you need to follow are:
Install adb & fastboot" + "Nokia USB" & other relevant drivers on your system.
Unlock the Nokia Bootloader using adb (Follow this Techmesto Guide for exact steps.)
Use this another Techmesto guide to download the latest version of Magisk apk on your system. Then, install it on your device.
Check your device settings to know which version is patched (Follow the guide link in the previous step).
Download the relevant magisk_patched image file and paste it within the adb folder.
Now, run the following two commands in your command prompt:
Code:
fastboot flash recovery <magisk_patched_filename.img
fastboot boot <magisk _patched_filename.img
Wait for the device to boot up normally. Once done, fire up the pre-installed Magisk apk and hit the "Install" button. [Install >> Install >> Direct Install]
Let the flash process complete, & once its done, simply reboot your device.
You have now successfully Rooted your Nokia 6.1 device.
Let know if the above steps helped you.
Cheers,
Manu