This method is only for devices with MTK chipset. CONFIRMED WORKING ON K430T, K430DSY and K430dsE
It is based on the gottlasz method published in: http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807"
Required files:
- Carliv Image Kitchen (search in google)
- SuperSU 2.65 available in: http://downloadmirror.co/L2/BETA-SuperSU-v2.65.zip
- TWRP ported by berkantkz at: http://forum.xda-developers.com/lg-k10/development/teamwinrecoveryproject-3-0-0-0-lg-k10-t3404434
- Time and patience (a lot of patience)
Steps:
1. Enable developer options on the lg K10
2. Enable OEM unlocking and USB debugging
3. Copy twrp.img to disk C: /
3. Go to C: / and open command window. Enter: adb reboot bootloader (phone will start in fastboot mode)
4. Once in the fastboot mode enter the command: fastboot boot twrp.img
5. Once inside TWRP press cancel and then slide to allow modifications.
6. Mount System, data and sdcard.
7. Make BOOT-only backup (uncheck all other partitions)
8. Mount MTP
9. Copy BOOT backup from TWRP folder in our SD card (Boot.emmc.win) and rename bootlz4.img
10. Copy to Boot-resources of CARLIV IMAGE KITCHEN
11. Decompress with Carliv
12. Open bootlz4 folder and find the file "boot.img-ramdisk-compress".
13. Edit "boot.img-ramdisk-compress" with notepad ++ and change "lz4" to "gz"
14. Save
15. Recompress bootlz4.img
16. Go to output folder and look for bootlz4xxxxx.img and rename it as bootgz.img
17. Go to TWRP and restart in bootloader mode
18. Write in command window: fastboot flash boot bootgz.img
18. Then write in command window: fastboot boot twrp.img to return to TWRP
19. Install superSU 2.65
20. Backup BOOT (boot partition only)
21. Copy BOOT backup again (Boot.emmc.win) and rename it to bootgzroot.img
22. Copy to Boot-resources of CARLIV IMAGE KITCHEN
23. Unzip with Carliv
24. Open bootgzroot folder and find the file "boot.img-ramdisk-compress".
25. Edit "boot.img-ramdisk-compress" with notepad ++ and change "gz" to "lz4"
26. Save
27. Recompress bootgzroot.img
28. Go to folder output and rename "bootgzrootxxx.img" to "bootlz4root.img"
29. Copy "bootlz4root.img" to disk C: /
30. Copy bootlz4.img from boot-resources folder into C:/ too
31. Go to TWRP and reboot into bootloader
32. Write in command prompt fastboot flash boot bootlz4.img (this is to avoid bootloops)
33. Write in command window fastboot boot bootlz4root.img (there will be a bootloop and then boot normally)
34. Write in command window adb reboot bootloader
35. Write in command window fastboot boot bootlz4root.img, after boot write in command window adb reboot bootloader (fast because the phone will reboot after some seconds)
36. Write in command window fastboot flash boot bootlz4root.img
37. Start normally.
Ready, you have ROOT!
I am not responsible for any damage caused to your phone, your grandma or your hamster. Cheers!
waiting for ramdump
cpatrick3000 said:
This method is only for devices with MTK chipset.
It is based on the gottlasz method published in: http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
Required files:
- Carliv Image Kitchen (search in google)
- SuperSU 2.65 available in: http://downloadmirror.co/L2/BETA-SuperSU-v2.65.zip
- TWRP ported by berkantkz at: https://drive.google.com/open?id=0B0BUe3iVMnzKQnBpeDdTM1plc3c
- Time and patience (a lot of patience)
Steps:
1. Enable developer options on the lg K10
2. Enable OEM unlocking and USB debugging
3. Copy twrp.img to disk C: /
3. Go to C: / and open command window. Enter: adb reboot bootloader (phone will start in fastboot mode)
4. Once in the fastboot mode enter the command: fastboot boot twrp.img
5. Once inside TWRP press cancel and then slide to allow modifications.
6. Mount System, data and sdcard.
7. Make BOOT-only backup (uncheck all other partitions)
8. Mount MTP
9. Copy BOOT backup from TWRP folder in our SD card (Boot.emmc.win) and rename bootlz4.img
10. Copy to Boot-resources of CARLIV IMAGE KITCHEN
11. Decompress with Carliv
12. Open bootlz4 folder and find the file "boot.img-ramdisk-compress".
13. Edit "boot.img-ramdisk-compress" with notepad ++ and change "lz4" to "gz"
14. Save
15. Recompress bootlz4.img
16. Go to output folder and look for bootlz4xxxxx.img and rename it as bootgz.img
17. Go to TWRP and restart in bootloader mode
18. Write in command window: fastboot flash boot bootgz.img
18. Then write in command window: fastboot boot twrp.img to return to TWRP
19. Install superSU 2.65
20. Backup BOOT (boot partition only)
21. Copy BOOT backup again (Boot.emmc.win) and rename it to bootgzroot.bin
22. Copy to Boot-resources of CARLIV IMAGE KITCHEN
23. Unzip with Carliv
24. Open bootgzroot folder and find the file "boot.img-ramdisk-compress".
25. Edit "boot.img-ramdisk-compress" with notepad ++ and change "gz" to "lz4"
26. Save
27. Recompress bootgzroot.img
28. Go to folder output and rename "bootgzrootxxx.img" to "bootlz4root.img"
29. Copy "bootlz4root.img" to disk C: /
30. Copy bootlz4.img from boot-resources folder into C:/ too
31. Go to TWRP and reboot into bootloader
32. Write in command prompt fastboot flash boot bootlz4.img (this is to avoid bootloops)
33. Write in command window fastboot boot bootlz4root.img (there will be a bootloop and then boot normally)
34. Write in command window adb reboot bootloader
35. Write in command window fastboot boot bootlz4root.img (there will be an error related to NFC, accept and allow USB connection)
36. Write in command window adb reboot bootloader
37. Write in command window fastboot flash boot bootlz4root.img
38. Start normally.
Ready, you have ROOT!
I´m not responsible for any damage caused to your phone, your grandma or your hamster. Cheers!
Click to expand...
Click to collapse
sorry for my English. I tried to follow the tutorial, however the Get on the (4. Once in fastboot mode enter the command: fastboot boot twrp.img) The Reset one cell features a Next Message: waiting for ramdump. Is there something I can do to get rid of it? thanks for the help in MTK
MarkiinBRz said:
sorry for my English. I tried to follow the tutorial, however the Get on the (4. Once in fastboot mode enter the command: fastboot boot twrp.img) The Reset one cell features a Next Message: waiting for ramdump. Is there something I can do to get rid of it? thanks for the help in MTK
Click to expand...
Click to collapse
Mmm remove battery and try to turn on again. If It doesnt works reflash stock kdz and before doing the root use adb reboot bootloader and then fastboot oem unlock
MarkiinBRz said:
sorry for my English. I tried to follow the tutorial, however the Get on the (4. Once in fastboot mode enter the command: fastboot boot twrp.img) The Reset one cell features a Next Message: waiting for ramdump. Is there something I can do to get rid of it? thanks for the help in MTK
Click to expand...
Click to collapse
my phone is lg k10 430dsy mtk
I had the same problem
after flash twrp.img
show message: waiting for ramdump
---------- Post added at 08:43 AM ---------- Previous post was at 08:33 AM ----------
cpatrick3000 said:
Mmm remove battery and try to turn on again. If It doesnt works reflash stock kdz and before doing the root use adb reboot bootloader and then fastboot oem unlock
Click to expand...
Click to collapse
remove battery and switch on phone work device without problem
but not work recovery twrp on the 430dsy.
fastboot boot twrp.img in the terminal show message success but show error message: waiting for ramdump in the device
#sorry for my bad english
i got unlocked fastboot
I goto fastboot this command
# adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse
then flash twrp
# fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.596s]
booting...
OKAY [ 0.051s]
finished. total time: 0.648s
Click to expand...
Click to collapse
but show this error waiting for ramdump in the device
i waiting 30 min but nothing happened
please view Attached image
Hi, can you tell us, what is the difference between gottlasz' method and your method? I guess you added a few final flashing and booting steps.
123xdagsm said:
i got unlocked fastboot
I goto fastboot this command
then flash twrp
but show this error waiting for ramdump in the device
i waiting 30 min but nothing happened
please view Attached image
Click to expand...
Click to collapse
This error persists after the fourth step same, I think it must be the twrp or something is passing unperceived. Anyway I'll try another way.
I believe this ramdump thing is TWRP related. There is a 3.0.2 TWRP on berkantkz TWRP thread so the ones who get this error could also try that other one.
Where is that twrp 3.0.2?
wizzardsk said:
Where is that twrp 3.0.2?
Click to expand...
Click to collapse
there
http://forum.xda-developers.com/showpost.php?p=69381986&postcount=126
I still have those bootloop... When I flash with fastboot, the device freezes. When I flashed in TWRP, I got bootloop after restart...
wizzardsk said:
I still have those bootloop... When I flash with fastboot, the device freezes. When I flashed in TWRP, I got bootloop after restart...
Click to expand...
Click to collapse
I believe you need a fresh start... lg up or lg flashtool and full firmware reintall. Lg bridge and hard reset is not enough.
Of course it's just guessing so don't take it for granted.
---------- Post added at 06:46 PM ---------- Previous post was at 06:14 PM ----------
@cpatrick3000, did you manage to make it work after any unsuccesful or succesful attempts on root? I mean if you were rooted before but lost it and you had to make a hard reset or you used lg bridge update error recovery? Or your k10 was fully stock when you rooted it this way, no earlier attempts on root?
wizzardsk said:
Hi, can you tell us, what is the difference between gottlasz' method and your method? I guess you added a few final flashing and booting steps.
Click to expand...
Click to collapse
Hi. The difference is that I found a way to "force" boot of k10. If i don't do these final steps the phone stays on black screen after device corrupt warning (red triangle)
cpatrick3000 said:
Hi. The difference is that I found a way to "force" boot of k10. If i don't do these final steps the phone stays on black screen after device corrupt warning (red triangle)
Click to expand...
Click to collapse
I tried "fastboot flash boot bootlz4.img" and then my phone just freezed. After removing battery I just had something like bootloop. Device corrupt warning, then blank screen. I guess you had not these problems.
wizzardsk said:
I tried "fastboot flash boot bootlz4.img" and then my phone just freezed. After removing battery I just had something like bootloop. Device corrupt warning, then blank screen. I guess you had not these problems.
Click to expand...
Click to collapse
Mmmm thats strange. I think u better flash kdz (ill check my method again)
cpatrick3000 said:
Mmmm thats strange. I think u better flash kdz (ill check my method again)
Click to expand...
Click to collapse
Okay, which kdz do you mean?
wizzardsk said:
Okay, which kdz do you mean?
Click to expand...
Click to collapse
You hace to put your phone into download mode and restore by lg bridge. Here in the forums there's a tutorial. Btw always be sure that u can go back to normal before doing root related stuff (there's always bricking risk)
cpatrick3000 said:
You hace to put your phone into download mode and restore by lg bridge. Here in the forums there's a tutorial. Btw always be sure that u can go back to normal before doing root related stuff (there's always bricking risk)
Click to expand...
Click to collapse
I see. I have no prob going back, thx for your care. I even do not loose my data after restore in lg bridge.
wizzardsk said:
I see. I have no prob going back, thx for your care. I even do not loose my data after restore in lg bridge.
Click to expand...
Click to collapse
Np dude, i was trying to root like during a month, finally i used this method and works always for me (last night i rooted and works fine) hope u find a way to root!
cpatrick3000 said:
Np dude, i was trying to root like during a month, finally i used this method and works always for me (last night i rooted and works fine) hope u find a way to root!
Click to expand...
Click to collapse
You only used lg bridge to recover after root attempts or you tried lg up or lg flashtool?
Related
Just a quick step by step tutorial to get a Custom ROM working on your HTC One or if you just want to unlock and root!
This guide is especially for the new users, experienced HTC users should already be familiar with this process.
Step 1: Unlock
Go on http://www.htcdev.com and create yourself an account on HTCDEV.
Download these adb/fastboot files
Make a new folder on your C:/ drive called fastboot for example.
Extract the zip downloaded in step 2 to the new folder
Go Here http://www.htcdev.com/bootloader/ and select "All Other Supported Models" and "then begin unlock bootloader"
Yes, Tick both Boxes, Proceed
Skip up to step 8 as we have all we need for the first 7 steps
Power off your phone by holding the power button down for 10 seconds
Power your phone on by holding power and volume down
Highlight Fastboot With Volume+or- then press Power
Plug your phone into your PC and open a Command Prompt.
(windows XP - Click Start > Run > type CMD in box then press OK
(Windows 7 - Click Start > type CMD in search box then press Enter)
Change directory to your folder where we put fastboot files cd c:\fastboot
Type this into your command prompt window fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files to in step 2
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol + to accept and power to confirm.
Step 2: Recovery
Download the Android SDK (optional)
Download the recovery of your choice, here a few links:
- CWM
- CWM 2
- TWRP
Place the Recovery file you downloaded where the fastboot.exe is (Either in the location of your downloaded fastboot drivers or in the Android SDK directory)
Now open the cmd and navigate to the folder where the Recovery File is located or just open a cmd with shift and right click at the correct directory
Now type:
fastboot flash recovery name_of_the_recovery.img
For example:
fastboot flash recovery recovery-clockwork-touch-6.0.2.8-m7.img
Now your recovery is installed
Step 3: Root
This step is only needed if you want a stock rooted ROM, if you want a custom ROM, skip this step.
Now root your phone with SuperSU by Chainfire or SuperUser by koush
Download SuperSU from this link or SuperUser from this link
Flash it with the Recovery:
Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader
Navigate with VOL and Power to Recovery
Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
Now you are able to flash any Custom ROM.
Step 4: Custom ROM
With htcdev unlock you need to flash the boot.img after every ROM installation
Note: Most of the custom ROMs have a script which lets the boot.img flash automatically with the ROM, so probably the steps after flashing the ROM are not needed.
If you are in a bootlop though, I recommend you to perform these steps and flash the boot.img with fastboot
Download the ROM you want to flash
Open the ROM zip with an archive manager and extract the boot.img out of it and place it in your fastboot directory
Copy the ROM to your sdcard
Now boot into bootloader again (explained above) and choose recovery with your volume keys and power button
In recovery wipe data and cache aka fullwipe before flashing your ROM if you are moving to a new base (for example from CyanogenMod to a Sense ROM, don't forget to backup your data files, like apps) (Often ROM chefs leave a note in their thread if a fullwipe is needed or not, just follow their advices)
Now flash your ROM by installing zip from sdcard
If this is finished, reboot and reboot into bootloader again
Connect your phone to your PC in fasboot mode (choose in bootloader with power button)
Open a cmd in your fastboot folder with your boot.img and type these two commands:
fastboot flash boot boot.img
fastboot erase cache
Then reboot your phone and wait some minutes to see your ROM booted
Enjoy
Video tutorials (for One S but the steps are the same):
Video-Tutorial by Flow-Wolf:
Bootloader Unlock:
Recovery Installation:
Root:
Custom ROM Installation:
I recommend using SuperUser by koush insted of SuperSU. I also made Super Boot to root stock ROM but I need someone with WWE HTC One...
I added a link for koush's SuperUser
hi
i done everything like its writen here, but i cant boot into recovery.. it cames the screen "entering recovery" and then the device is reboot
noob.fl said:
hi
i done everything like its writen here, but i cant boot into recovery.. it cames the screen "entering recovery" and then the device is reboot
Click to expand...
Click to collapse
Yes currently the recoveries are not working, be patient until they work, I will leave a note in the OP
thanks for responce - i will wait :laugh:
ist there any other opinion to put the su binary into system? maybee with adb?
noob.fl said:
thanks for responce - i will wait :laugh:
ist there any other opinion to put the su binary into system? maybee with adb?
Click to expand...
Click to collapse
adb can't write system on stock, you would need a modified boot.img
noob.fl said:
thanks for responce - i will wait :laugh:
ist there any other opinion to put the su binary into system? maybee with adb?
Click to expand...
Click to collapse
I have modified boot.img but it's from .401 ROM. You want to try?
mike1986. said:
I have modified boot.img but it's from .401 ROM. You want to try?
Click to expand...
Click to collapse
im since a longer time no more so familar with htc... can it harm my device or it does not care and the one will run? if cot my one since to day, and its a damn expensive device to brick it at first time... but if it works - je i will try
its like all other androiddevices to flash? fastboot flash boot boot.img?
noob.fl said:
im since a longer time no more so familar with htc... can it harm my device or it does not care and the one will run? if cot my one since to day, and its a damn expensive device to brick it at first time... but if it works - je i will try
its like all other androiddevices to flash? fastboot flash boot boot.img?
Click to expand...
Click to collapse
There is no chance to brick but there is a chance for bootloop
if got the softwarw nr 1.27.206.1 with kernel [email protected]#1 - will it works with your 401 kernel?
Can you pull the system partition so we can enjoy some stuff from the One on other HTC devices?
tell me how to do and i will share
http://d-h.st/2DO
Unpack and run the runme.bat
Dumping may need a while, upload it to dropbox for example
Imho all devs should work together here instead of trying to be the first guy with a deodexed stock ROM
these are just windowsfiles - does not working on my linux, sorry
torxx said:
http://d-h.st/2DO
Unpack and run the runme.bat
Dumping may need a while, upload it to dropbox for example
Imho all devs should work together here instead of trying to be the first guy with a deodexed stock ROM
Click to expand...
Click to collapse
Do i understand it right i do not need to install recovery to get the system dump?
Simply go to your adb dir and type that in terminal:
adb pull /system ./system
optional:
adb kill-server
7za a -tzip system.zip system\ -r (needs the 7za file)
rmdir system /s /q
to pack a zip
simpelsense said:
Do i understand it right i do not need to install recovery to get the system dump?
Click to expand...
Click to collapse
no, all through adb
noob.fl said:
these are just windowsfiles - does not working on my linux, sorry
Click to expand...
Click to collapse
Using ADB (I assume you already isntalled it)
adb devices
adb pull /system ./system
adb kill-server
It will write it in your ADB folder
torxx said:
no, all through adb
Click to expand...
Click to collapse
thought pulling system is a little more magic.
Had a problem with audio playback (volume always high no matter what). Decide to flash. PAC for my Sprint LS980. I see this:
Seems to be a lot of confusion so I'll clear things up..
ZV7->ZV8->ZVA is how the ota history goes, with ZVB on the way.
If you're on stock ZVA, your aboot (bootloader) may not be downgraded, in that case, use FreeGee from Play Store to install a recovery, it will automatically downgrade your aboot.
if you have the ZVA Radio, just flash furnace or dr87's kernel after you flash an AOSP ROM, all done.
Click to expand...
Click to collapse
Sorce: http://forum.xda-developers.com/showthread.php?t=2669074
Seeing the last sentance, I think that if I flash ZVA Radio, SlimKat ROM (the one that causes me problems) and then dr87's kernel I could try a ZVA experience. I flashed SlimKat again becuase I was going to change anyway, I wanted to try it with ZVA.
Tell myself why not, I do it.
Fails but I didnt pay much attention. I reboot.
Stuck in fastboot mode and cant escape. Recovery is a no-go.
Tried flashing both ZV7aboot.img and twrp2.6.3.0.img into their appropriate partitions (boot and recovery).
Still having problems, but now I cant do any button combination (except DownloadMode. Cant turn off) after ZV7aboot.img flash.
I dont want to erase my memory (~26GB of valuable data). Is there a way to flash a ZV8Radio.zip from fastboot? I think thats my problem, but Im not too sure. Just access to recovery would allow my to fix my problems.
Thanks anyone for any help! I think I really screwed myself over this time. Thanks everyone!
Edit: Anyone know where to get a boot.img and system.img for the Sprint LS980?
zv7_aboot.img isn't a boot.img, it's the bootloader. Use FreeGee to install twrp, it will handle the aboot for you. Then you can take advantage of the last sentence.
Savoca said:
zv7_aboot.img isn't a boot.img, it's the bootloader. Use FreeGee to install twrp, it will handle the aboot for you. Then you can take advantage of the last sentence.
Click to expand...
Click to collapse
I am stuck in fastboot. No recovery. Download mode is also accessable.
Which of the following would help:
* System.img and Boot.img (where to find em?)
* A kernel .img (Do they exist?)
* Flashing the ZV7 or 8 aboot.img oncemore with twrp.img again?
Thanks for coming to help! It means a lot.
RevolcFael4 said:
I am stuck in fastboot. No recovery. Download mode is also accessable.
Which of the following would help:
* System.img and Boot.img (where to find em?)
* A kernel .img (Do they exist?)
* Flashing the ZV7 or 8 aboot.img oncemore with twrp.img again?
Thanks for coming to help! It means a lot.
Click to expand...
Click to collapse
If you can boot into a rom, use FreeGee to install twrp. If you can't boot into rom and recovery, you need to flashtool.
Savoca said:
If you can boot into a rom, use FreeGee to install twrp. If you can't boot into rom and recovery, you need to flashtool.
Click to expand...
Click to collapse
Flashtools is asking for login and password. ?
Does this mean I have to wipe all user data in order to use it?
Edit: Do you know where System.img and Boot.img could be downloaded? I think its my only hope.
RevolcFael4 said:
Flashtools is asking for login and password. ?
Does this mean I have to wipe all user data in order to use it?
Edit: Do you know where System.img and Boot.img could be downloaded? I think its my only hope.
Click to expand...
Click to collapse
You didn't read the tutorial.
http://downloads.codefi.re/autoprime/LG/LG_G2
Savoca said:
You didn't read the tutorial.
http://downloads.codefi.re/autoprime/LG/LG_G2
Click to expand...
Click to collapse
Thanks for the link! That was extremely helpful.
What I did to gain access to twrp again was:
Download boot.img from the link.
Download aboot.img from link.
Download twrp.img (but this isnt necessary, file is already available on phone. No need.)
* Enter command 'fastboot flash boot boot.img'
* (If you hold power it starts showing LG Logo.)
* Go back to Fastboot. Enter command 'fastboot flash aboot aboot.img'
* Now TWRP access is regained! Phone doesnt boot normally, must flash ROM and stuff again.
Thanks a lot! This was an okay first fastboot experience.
Soft Bricked Sprint LS980?
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
---------- Post added at 02:59 AM ---------- Previous post was at 02:06 AM ----------
x_lord said:
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
Click to expand...
Click to collapse
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
x_lord said:
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
Click to expand...
Click to collapse
Sorry for not replying, but I see you managed to fix your problem. All you needed to do was download .img files, then enter commands through fastboot. Although it is slightly more complicated than that, its the rough outline of what needs to be done to fix it. Nice work fixing your problem. I came back to this thread to remind myself of the commands that need to be entered (My comments help myself).
I think I am just going to copy-paste the quoted box above if anyone needs instructions how to do this. Thanks for the quick guide I can use to help others!
bricked , simple fix?
x_lord said:
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
---------- Post added at 02:59 AM ---------- Previous post was at 02:06 AM ----------
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
Click to expand...
Click to collapse
this process (which i got from a different thread originally)
bricked my phone Lg G2 (Ls 980 sprint 32 gb)
i was on remote connection with my friend attempting all kinds of flashes (mostly custom roms and recoveries)
what he did
he FIRST flashboot erase aboot
and then erased all the other files
foolishly he then used fastboot reboot BEFORE reflashing the necessary images
this leaves me with a device that is practically 100% empty all hardware no software
i have no response no life not even a backlight EXCEPT
i can plug into windows and see Qdloader9008 is connected comport 3
and i can communicate with the device on ubuntu terminal although im not too farmiliar with terminal syntax so im not having much luck
im convinced it is as simple as reflashing at least a working recovery or download mode from which i can install everything else i nee
between QPST, Terminal, and or some other method
sorry for Noob ish ness
any help would be appreciated even if just help with a better understanding of what to do next
payment is possible
True2This said:
this process (which i got from a different thread originally)
bricked my phone Lg G2 (Ls 980 sprint 32 gb)
i was on remote connection with my friend attempting all kinds of flashes (mostly custom roms and recoveries)
what he did
he FIRST flashboot erase aboot
and then erased all the other files
foolishly he then used fastboot reboot BEFORE reflashing the necessary images
this leaves me with a device that is practically 100% empty all hardware no software
i have no response no life not even a backlight EXCEPT
i can plug into windows and see Qdloader9008 is connected comport 3
and i can communicate with the device on ubuntu terminal although im not too farmiliar with terminal syntax so im not having much luck
im convinced it is as simple as reflashing at least a working recovery or download mode from which i can install everything else i nee
between QPST, Terminal, and or some other method
sorry for Noob ish ness
any help would be appreciated even if just help with a better understanding of what to do next
payment is possible
Click to expand...
Click to collapse
Sorry, I barely understood what to do originally. What you have to do next is to reflash the aboot/boot/ whatever partitions but getting to that position might be difficult. Maybe some sort of command would allow you to connect to it oncemore?
Sorry, try to look into it more and see if a dev could help. Try posting something in /r/lgg2 but then again I cant be certain anything would happen. Good luck!
Easy guide
Since the problem keeps happening to people heres a quick tutorial I made.
Download and install this (PC only?)
Now go here. (D802) (D800) (LS980) (VS980) (D803) (Device tree/others)Download the images for laf, aboot, boot, and recovery.
Place the 4 .img files in the same folder. Control right click in that folded and open terminal. If this isn't how you open terminal in a folder search"how to open terminal in a folder".
(NOTE: Commands below will differ from the file names. Change the values in the parenthesis to match the files, HOWEVER, do not type the parenthesis into the terminal prompt! It will not work if you do.)
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot (6-boot.img)
fastboot flash aboot (4-aboot.img)
fastboot flash recovery (10-recovery.img)
fastboot flash laf (11-laf.img)
fastboot reboot
You should be fine now!
Unbrick Ls980 formatting partitions
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
RevolcFael4 said:
Since the problem keeps happening to people heres a quick tutorial I made.
Download and install this (PC only?)
Now go here. (D802) (D800) (LS980) (VS980) (D803) (Device tree/others)Download the images for laf, aboot, boot, and recovery.
Place the 4 .img files in the same folder. Control right click in that folded and open terminal. If this isn't how you open terminal in a folder search"how to open terminal in a folder".
(NOTE: Commands below will differ from the file names. Change the values in the parenthesis to match the files, HOWEVER, do not type the parenthesis into the terminal prompt! It will not work if you do.)
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot (6-boot.img)
fastboot flash aboot (4-aboot.img)
fastboot flash recovery (10-recovery.img)
fastboot flash laf (11-laf.img)
fastboot reboot
You should be fine now!
Click to expand...
Click to collapse
i tried this with almost all model files but still on fastboot any other option?>
I want to say thank you so much for this thread. Just got a new (refurb) G2 switching carriers to T-Mo and my idiot self used the wrong root program and soft bricked to fastboot. 4 .img files later and a few commands and I don't think I've ever been so happy to see a download screen on a phone...
juancho8207 said:
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
Click to expand...
Click to collapse
GREAT, You are a life saver :laugh:
juancho8207 said:
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
Click to expand...
Click to collapse
wow.. worked flawlessly... thank you very much :good::good::laugh::laugh:
http://www.datafilehost.com/d/59efbc15mfastboot with custom Recovery Link
http://www.datafilehost.com/d/bf3a2c6d
Super SU
http://www.datafilehost.com/d/bab6821a
insure you have Unlock Bootloader if aren't see the Post by Lucas
http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728
After unlock Bootloader
1. Put Super SU in Internal Storage
2. Extract Rar file in pc
3. In Folder Shift+Right click Of mouse and Start Command Mode
4. Enter Command "mfastboot Devices" And see your serial No. of device
5. Then next Command "mfastboot flash recovery twrp-2.8.3.0-titan.img" Done
6. Next Command "mfastboot reboot"
5. Then Reboot in Recovery and Flash Super Su
done !!! See super Su in Device
My moto g2 stuck on bootloader unlock warning after rooting
My moto g2 stuck on bootloader unlock warning after rooting
Follow the instructions here instead:
www . gammerson . com /2015/11/how-to-root-moto-g2-on-marshmallow. html
(remove spaces from link, as I'm not permitted to post an actual link)
1st boot take time after unlock bootloader .. if take more
then try to reset from recovery when Power off your device
-for recovery first press volume down button during power button
-select recovery in option
-when android logo comes press again both volume button during press power button and wipe data reset and wipe cache partition too
if you want remove unlocked bootloader logo
-Make sure you have setup ADB and mfastboot on your PC. (Download from above)
-Download the logo file and extract the zip file to get the logo.bin file. Transfer the logo.bin file to some place you can track it easily. Its better if you use the folder where you setup the mfastboot.
-Power off your device and keep it unplugged from your PC.
-Boot into bootloader. To do so, press and hold volume down and the power button for 5-6 seconds.
-You will see the bootloader screen. Now plug in your device to the PC.
-Navigate to the location of the logo.bin file. While the folder with the logo file is open, hold shift on keyboard and right-click on an empty space and select “Open command window here” option to launch a cmd window.
Now type the following in the command prompt to get a code
mfastboot flash logo logo.bin
Now type the following in command prompt to reboot.
mfastboot reboot
Once you reboot, you will no longer see the bootloader warning as it has been replaced with the Motorola logo. You can choose a custom image you like but be sure it is in .bin
link for logo file
https://www.datafilehost.com/d/TekaWiCcHE
Root Failed?
I followed your steps and after I flash recovery, It says boot failed when i try to boot in recovery. It says failed to boot?
Rushaan9912 said:
I followed your steps and after I flash recovery, It says boot failed when i try to boot in recovery. It says failed to boot?
Click to expand...
Click to collapse
well make sure that you have unlock bootloader,
are you able to start fastboot ?
then try this commands
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Locker49 said:
well make sure that you have unlock bootloader,
are you able to start fastboot ?
then try this commands
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
Tried it. It formatted my phone, Stilll wont root. WHenever I select REcovery it says "Failed to boot"
Rushaan9912 said:
Tried it. It formatted my phone, Stilll wont root. WHenever I select REcovery it says "Failed to boot"
Click to expand...
Click to collapse
Tried to flash recovery by fastboot ?
still face problem then you need to flash your stock rom
Instruction to Restore Stock Firmware on Moto G 2014
See the Post by @bhu999
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-original-motorola-t3155774
first you needto Flash lollipop(link below) then in recovery you upgrade MM
https://docs.google.com/uc?id=0B665WEdcrNV2dnpDYjdJaTh5aGc
marshmallow (indian) Dual sim
https://drive.google.com/file/d/0B7BRotdWEAc5TXJQc091Vk5RQU0
https://drive.google.com/file/d/0Bw0NmnatfFOxVEotMFZlMkQzZkk
Kit-kat to MarshMallow
https://mega.nz/#F!Q9YHCQzY!dgyvAJ8eNA3t7az4vizwOQ
Locker49 said:
Tried to flash recovery by fastboot ?
still face problem then you need to flash your stock rom
Instruction to Restore Stock Firmware on Moto G 2014
See the Post by @bhu999
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-original-motorola-t3155774
first you needto Flash lollipop(link below) then in recovery you upgrade MM
https://docs.google.com/uc?id=0B665WEdcrNV2dnpDYjdJaTh5aGc
marshmallow (indian) Dual sim
https://drive.google.com/file/d/0B7BRotdWEAc5TXJQc091Vk5RQU0
https://drive.google.com/file/d/0Bw0NmnatfFOxVEotMFZlMkQzZkk
Kit-kat to MarshMallow
https://mega.nz/#F!Q9YHCQzY!dgyvAJ8eNA3t7az4vizwOQ
Click to expand...
Click to collapse
Is it possible that this doesnt work on my phone because I have the 4G-LTE model?
Rushaan9912 said:
Is it possible that this doesnt work on my phone because I have the 4G-LTE model?
Click to expand...
Click to collapse
i uploded for moto g2 2014 (lte)
Rushaan9912 said:
Tried it. It formatted my phone, Stilll wont root. WHenever I select REcovery it says "Failed to boot"
Click to expand...
Click to collapse
Try using this SU as its the only one that has worked for me
http://forum.xda-developers.com/showpost.php?p=67670718&postcount=2
The issue is in the SuperSU updater script, which can't detect the system and is trying to install root in system mode (it should use systemless mode)
For those users who are stuck at bootloader logo after flash supersu, is necesary to reflash stock rom and flash this SuperSU (I've edited the updater-script to force systemless install)
After flash this SuperSU (updated to 2016-09-01), all updates can be installed directly from the store
Stuck at the start page
The root was done,but while rebooting the phone,the phone stuck on the unlock bootloader window and nothing happens.If anybody had the same problem please tell me how to repair it.
Locker49 said:
http://www.datafilehost.com/d/59efbc15mfastboot with custom Recovery Link
http://www.datafilehost.com/d/bf3a2c6d
Super SU
http://www.datafilehost.com/d/bab6821a
insure you have Unlock Bootloader if aren't see the Post by Lucas
http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728
After unlock Bootloader
1. Put Super SU in Internal Storage
2. Extract Rar file in pc
3. In Folder Shift+Right click Of mouse and Start Command Mode
4. Enter Command "mfastboot Devices" And see your serial No. of device
5. Then next Command "mfastboot flash recovery twrp-2.8.3.0-titan.img" Done
6. Next Command "mfastboot reboot"
5. Then Reboot in Recovery and Flash Super Su
done !!! See super Su in Device
Click to expand...
Click to collapse
Does this work on the XT1064?
bootloader is unlocked successfully but it is showing no command while trying to superuser in recovery option with a android bot lying down with an exclamatory mark on it in red background, what does it mean?
can moto g2 support VOLTE?
Facing same issues while trying to flash su. Result: stuck at bootloader screen
After running successful "fastboot flash recovery twrp.IMG " when i select recovery option in my moto g(titan) an error occur that is"boot failed"
How can i fix it please help asap?
So as I saw, there are a lot of users who's afraid of rooting their device, so I decided to make a thread where I write everything down step by step.
I'm not a man of words, so I try to keep it very minimalistic and simple, so newbies can do this too without any issue.
In this thread I'll guide your through on how to flash twrp, root, and use a custom kernel, which is called Hex and can be found here on XDA.
You need to be on September patch, otherwise I cannot guarantee that it will work.
Before we start the process, I need to say that if you brick your device because of something went wrong, don't point your finger at me, I just wrote this to help users who wants to enjoy a better experience on A2.
And one more thing. Bootloader unlocking will wipe every data on your phone so make sure to backup everything!
Let's start then, shall we?
1. Installing drivers & Preparing PC
- Download this and extract it
- Open and install "adb-setup-1.4.3.exe"
- When it is done, go to "Drivers" folder and start "miflash_unlock.exe"
- Click on the gear icon top right corner and click on "Check" next to "Click the button to install the drive"
- Do as the installer says
- Hopefully the drivers has been installed so we're done with it, let's head on the next step.
2. Preparing phone for unlocking
- On your phone navigate to Settings->System->About phone and tap the build number until you see "You are developer"
- Go back once and you'll see a new menu called "Developer options"
- Tap on it and search an option called "OEM Unlocking", enable it
- We're done here. Let's keep going
3. Entering fastboot and unlocking bootloader (MAKE A BACKUP of your data!)
- Hold your power button down, tap on restart and hold your volume DOWN button while it resets until you see the Mi bunny doing its thing
- Now we're in Fastboot mode, hooray:victory:
- Download this zip and extract it on your PC
- Open it and type "cmd" (without the quotations) in the file manager header where you see (This computer>somethingsomething>Mi A2 fastboot), don't be afraid just type it in, and hit enter and you'll enter into command prompt
- Now we are ready for action
- Type these commands one by one:
fastboot flashing unlock
fastboot flashing unlock_critical
After this, you will see a warning message that your bootloader is unlocked and your data is not safe, blah blah... Just ignore it everytime you power on your phone.
- Hope you can keep up with me cause we're done here, let's head to the next step.
4. Installing TWRP and Magisk (and Hex kernel which is optional)
- First we need to know what is our active slot, we can check this in fastboot with "fastboot getvar current-slot"
- Download this recovery by TingyChen and also copy this to the same location
- If you have slot A as active then flash twrp to B partition and vice versa In cmd type "fastboot flash boot_a or boot_b TWRP-3.2.3-jasmine-20180804.img" (Without quotation) - Now we have twrp on our device
- Then type: "fastboot set_active A (or) B " (Also without quotation) - Depending on where you installed TWRP
- Hold down the power button and Volume UP!(This time up) and when the phone resets release the power button and keep pressing the vol up button until you enter twrp
- If you did right, you're in TWRP now, let's start flashing
- Navigate to Reboot and select Slot A (or B) at the bottom - Select the active slot where your system is
- Flash Custom Kernel (we have Hex for now)
- Flash Magisk_a if you have system on A partition or Magisk_b if you have it on B
Reboot your device and we're done with everything. Now you have fully functional Magisk and Hex custom kernel.
Now you can enable CameraAPI2 with magisk module and use google camera and some other sweet things like substraum for example.
Is Twrp permanently or temporary?
aankvian said:
Is Twrp permanently or temporary?
Click to expand...
Click to collapse
It is permanent, but if you want to use twrp unfortunately you need pc for it to set the active slot to B (fastboot set_active b), because your system is on A and you boot on that slot by default. You cannot change the active slot on phone at the moment.
balazs312 said:
After this, you will see a warning message that your bootloader is unlocked and your data is not safe,
Click to expand...
Click to collapse
Hello. Is it possible to remove this annoying screensaver?
Serrega277 said:
Hello. Is it possible to remove this annoying screensaver?
Click to expand...
Click to collapse
I dont know?
Thank you so much. Where i have to start when device is already unlocked?
bavmouse said:
Thank you so much. Where i have to start when device is already unlocked?
Click to expand...
Click to collapse
4. part
don't work for me: https://picload.org/view/dcrolwrl/anmerkung.png.html
bavmouse said:
don't work for me: https://picload.org/view/dcrolwrl/anmerkung.png.html
Click to expand...
Click to collapse
Did you copy the image file to the folder?
Yes I did.
bavmouse said:
Yes I did.
Click to expand...
Click to collapse
it says that the file is not found, try to rename it and flash it like that with your preferred file name
Anyone managed to do it this way?
I had a lot of trouble. Mainly because fastboot won't support the "set_active" command. The second thing is, that not everybody is running on slot A, so the guide might be misleading.
So after I figured the basics (I'm not used to the A/B partitions) I had a bootloop if I installed magisk via recovery.
What I did (I'm on slot B):
- everything till step 4. ofc
- installed magisk (just the apk)
- flash recovery to slot B (the active one) and then "fastboot reboot" holding vol up, to enter recovery
- in recovery I flashed the hex kernel_b and wiped cache, reboot to system
- after completed boot, reboot to fastboot (again) and boot the patched stock boot file
- then tun magisk.apk and "direct install" magisk. after reboot, you have hex kernel and magisk (but no twrp)
if you re able to select active partitions in fastboot, you can have it all
Good evening,
@pecholino I have the same problem like you with the command "fastboot set_active b" but you are on Slot B. Please tell me how do you change the Slot from A to B. I´m still on A. Thank´s in advanced.
servus
It really doesn't matter if you are on A or B. If you're on A, you follow the guide. If you're on B, you still follow the guide, but using the opposite partition.
I ended up on slot B because I flashed the august release stock image (default on slot A) and then I updated via updater to the last release (slot B). So I have the old rom on slot A and the new one on slot B. The only way I'm able to change active slots is in twrp.
I understand. Instead off "fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img" i must write "fastboot flash boot_a TWRP-3.2.3-jasmine-20180804.img", after reboot to recovery i change to B and install magisk. Is this the right way???
servus
4. Installing patched boot image, twrp and Hex
**
- Type "fastboot boot BOOT_PATCHED_V9.6.13.0.ODIMIFE" (Without the quotations) in cmd and your device will restart, don't worry about it
Here u forgot .img in your post =) i mean thah you should type fastboot boot BOOT_PATCHED_V9.6.13.0.ODIMIFE.img
Learginy said:
4. Installing patched boot image, twrp and Hex
**
- Type "fastboot boot BOOT_PATCHED_V9.6.13.0.ODIMIFE" (Without the quotations) in cmd and your device will restart, don't worry about it
Here u forgot .img in your post =) i mean thah you should type fastboot boot BOOT_PATCHED_V9.6.13.0.ODIMIFE.img
Click to expand...
Click to collapse
Thank you, fixed it:highfive:
Hey, thanks for the tutorial!
Is the Magisk.zip customized? If yes could you please upload it to google drive? I don`t have access to mega...
inuZ said:
Hey, thanks for the tutorial!
Is the Magisk.zip customized? If yes could you please upload it to google drive? I don`t have access to mega...
Click to expand...
Click to collapse
https://drive.google.com/file/d/1YXgnJ1yibMdYL4e84OiDnqM4JUWb1K-I/view?usp=sharing
fastboot flash boot_a TWRP-3.2.3-jasmine-20180804.
Code:
target didn't report max-download-size
Sending 'boot_a' (38612 KB)...
FAILED (remote: Requested download size is more than max allowed
)
Finished. Total time: 0.003s
Any help appreciated!!
I'm 63 years old & could do with some help - trying to flash my Moto G4 but no luck
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
https://drive.google.com/open?id=1QZAu9ZrCsKBhUcCofo2bde5aB89v76TB
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does, it disappears from the ADB Diver Installer / APK Installer!
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything.
I don't understand what I am doing wrong and am very stuck sadly.
https://drive.google.com/file/d/1zR361DukYrsc923zD2q6Aml3Xr0DVqlj/view?usp=sharing
Would really appreciate some help from you young clever guys!
Thank you.
George.
George425 said:
Hello folks.
I apologise in advance. I thought something was a good idea, and I said to myself I would give it a try and I won't give up, but I have been at this for about 5 hours now and no progress.
I have a Moto G4 which my wife gave about a year ago. I don't like stock Android and want to install Lineage OS onto it. I understand that first I need to:
1. Unlock my bootloader (done)
2. Install ADB Driver Installer onto my Dell (done)
3. Install Minimal ADB and Fastboot onto my Dell (done)
4. Plug my G4 into my Dell using the correct cable. It seems to work as the ADP Driver Installer / APK Installer recognises it as per the image below
https://drive.google.com/open?id=1QZAu9ZrCsKBhUcCofo2bde5aB89v76TB
5. Open up the command promt in the Minimal ADB and Fastboot folder, type adb devices - the device is recognised
6. Here is where the problems start!
(a) At this stage, as soon as I type adb reboot bootloader, the G4 reboots but as it does, it disappears from the ADB Diver Installer / APK Installer!
(b) Soon after when I type fastboot flash recovery twrp.img then nothing is found, no files or directory or anything.
I don't understand what I am doing wrong and am very stuck sadly.
https://drive.google.com/file/d/1zR361DukYrsc923zD2q6Aml3Xr0DVqlj/view?usp=sharing
Would really appreciate some help from you young clever guys!
Thank you.
George.
Click to expand...
Click to collapse
It says no twrp.img in that folder.
Because You renamed it's name to twrp.img.img ?
Try flash with "fastboot flash recovery twrp.img.img"
common file extensions are not shown in name, or while rename, but you added ".img" at last, so it is doubled..
Hello sir,
Copy the twrp file to the folder where ADB is installed. The folder is located in C drive.
Next you can Shift+right click, open powershell/cmd, whichever is there.
Now type in command
" fastboot flash recovery tw" and click tab button. After tab button, click enter.
This should be done when phone is in bootloader mode and connected to laptop/PC.
after the command execution is over, you can reboot to recovery.
First flash Ex kernel and then flash magisk, in THIS ORDER ONLY, OR YOUR PHONE WILL BRICK!
And voila, you have root! Flash anything!
____Mdd said:
It says no twrp.img in that folder.
Because You renamed it's name to twrp.img.img ?
Try flash with "fastboot flash recovery twrp.img.img"
common file extensions are not shown in name, or while rename, but you added ".img" at last, so it is doubled.
Click to expand...
Click to collapse
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
George425 said:
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
Click to expand...
Click to collapse
You flashed it. Reboot into recovery now.
George425 said:
Thank you for your suggestion. I did exactly as you said, in fact I tried different variations - I changed twrp.img to just twrp, then tried the command fastboot flash recovery twrp.img, nothing and then I changed it back to how it was, twrp.img and tried the command again, this time ending with twrp.img.img and nothing. Result is as shown below (bootloader not found / not signed or corrupted).
https://drive.google.com/open?id=1qMgUDp767Q32c0MmH2Ey17cpEGI75cJS
What shall I try now?
Click to expand...
Click to collapse
You've done it! Reboot to recovery!
Lyuu said:
You flashed it. Reboot into recovery now.
Click to expand...
Click to collapse
DhirajKale789 said:
You've done it! Reboot to recovery!
Click to expand...
Click to collapse
Yes you are both absolutely correct thank you for your help! I didn't think it was working!