Database Users

[Guide] Flash 6.0, root, and no-forceencrypt from stock (easy method)

Hope this helps.
1. Install android sdk and use the included install manager in the sdk to install the latest google usb drivers and platform tools (platform tools include fastboot and adb). Make sure adb and fastboot directory is in your Path variable as well.
2.Download latest stock image for Nexus 9 from google: https://developers.google.com/android/nexus/images?hl=en
3.Download latest twrp (here is the latest right now 10/6/2015): http://forum.xda-developers.com/nex...recovery-twrp-2-8-2-0-touch-recovery-t2944788
4.Download either a stock boot image with the no- forceencrypt flag set or a kernel with the no-forceencrypt flag set
a.I use the elementalx kernel (10/6/2015): http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657
b.A stock kernel for the MRA58K build with the no-forceencrypt flag set can be found here (boot.zip): http://forum.xda-developers.com/nexus-9/general/marshmallow-factory-images-available-t3218290/page3
5.Download the latest supersu that works with nexus (beta now) : http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
6.Make sure you have usb debugging enabled and ability to unlock bootloader (android developer options menu on nexus).
7.Unzip the 6.0 stock image into a folder and open a command window in the folder.
8.Type the following:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot oem unlock
c.flash-all, now wait a few minutes while the stock image flashes
9.At this point your nexus will reboot. Once you’re started, up you need to again enable usb debugging and the ability to unlock your bootloader in the android developer options menu. Now type the following to flash TWRP:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot flash recovery twrp.img (or whatever the image filename is from the twrp download).
10.Important: now make sure you boot DIRECTLY into TWRP via the button combination (power and volume down), a fastboot command, or the fastboot menu. If you don’t TWRP will be deleted and you’ll need to reflash using the last step.
11.Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
12.Now type adb push supersufile.zip /sdcard/supersufile.zip, make sure you’re typing from the correct directory.
13.Install supersu via the install menu on TWRP.
14.You now need to install a kernel with the no-forceencrypt flag set:
a.If you want to install a custom kernel (like elementalx), type adb push elementalxfile.zip /sdcard/elementalxfile.zip, make sure you’re typing from the correct directory. Then use TWRP to install the zip from your sdcard.
b.If you want to install the modified stock boot.img then unzip the boot.zip, boot back into the bootloader and type: fastboot flash boot boot.img. Make sure you do NOT boot back into the android OS before doing this step or you'll have to reflash twrp.
Reboot and you’re good to go.

Didnt work for me.

Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img

typo
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you

Fda979 said:
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Click to expand...
Click to collapse
Fixed. Thanks.
Sent from my Nexus 9 using Tapatalk

You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
I flashed the latest supersu and the latest elementalx kernel.... been running it since about an hour after elementalx kernel for 6.0 final was posted....... everything seems to be working fine. Are you sure? Maybe i'm having no problems with supersu because i'm using elementalx? let me know the reason, i'll check it out on my tablet and see if i can reproduce, and if so i'll modify the guide. But after about a day and a half use, i've had no issues. thx for quality checking.
gt

Am I missing something?
can I not just do a wipe and flash the img with twrp like a custom rom? Edit: Got it working. For me it was much easier to use this as opposed to the android sdk, because it would not detect my version of java. From there I followed your instructions, mostly. Putting the files you posted inside the directory the mini adb client allowed the flash-all command to work. From there I followed chainfire's instructions on the latest SU. Everything seems to be running smoothly. Thanks for the initiative, OP :good:

i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.

dkryder said:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
Click to expand...
Click to collapse
Of course update binaries. Choose normal method.

Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
I was facing same issue, then updated fastboot(android-sdk) and flash-all script worked fine for me.

That should work as well. That sequence of commands should work with any fastboot version. Just make sure to flash the vendor.img, some scripts don't use that as it's only used for the Nexus 9.

Why so complicated? I just installed @wug's NRT toolkit(on a Venue8 pro) and it did everything for me. Now im on rooted stock 6.0 with disabled encryption. Only thing i needed to do is to flash latest super su beta 2.52, that's it.

Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
i did all this, no worries and no error messages
i did fastboot reboot
now I am in a weird loop of
- google screen
- your device is corrupt
- google screen
- twrp (it flashes quite quickly, error messages on mounting everything and last line says something about renaming and something about stock rom)
loop
any ideas ?

Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.

Verttex said:
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Click to expand...
Click to collapse
yes, that seems to have been it
flashing TWRP seems to have been the problem so I have left everything as stock until root etc works on the stovk kernel
thanks for your help

Nice guide.

I install Busybox from Play, I assume that's needed? Everyone else doing this?

- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
added link to the latest beta supersu. thx.

All of these steps worked for me, but my battery doesn't charge right I don't think. It says battery life is at 3,745%. It runs out somewhere around 3,000%. Any ideas on how to fix that?

May Factory Image now available MXC89F

For those in custom recovery land just flash the system and vendor img to upgrade
now in May flavor!
https://developers.google.com/android/nexus/images#instructions

Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine

redukt said:
Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine
Click to expand...
Click to collapse
The value of this posting would increase exponentially if you took it upon yourself to share what and how you flashed the files with ADB.

Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
No chance of losing root either, is that correct?

Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP

redukt said:
Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP
Click to expand...
Click to collapse
Yes, I will need to reflash both, too (I have TWRP).
Thanks!

Than you´re device is rooted again. With this method you lose no data or wipe anything (ok.... some cache *g)
And... we have a thanks button in XDA So you don´t have to thank mate

Change log ? Or its just a security update

Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.

After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...

rambobo said:
After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...
Click to expand...
Click to collapse
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk

houtx2 said:
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?

rambobo said:
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?
Click to expand...
Click to collapse
Pleas try to reinstall right drivers, change the cable / USB ports. I think your main problem is your system configuration. Good luck

m8... so glad I wasn't too tired to listen to your tip. Awesome! Redid all the steps on my freshly installed laptop, and voila!
Seems either my main PCs USB-connection is flunky or I am damned to reinstall my Windows soon. Scary...
I used the following software to revive the Pixel:
official Google USB Drivers
You have to unzip the file and right-click and install it
then you have to go to your device manager in windows and after connecting the tablet with the PC and getting into fastboot
Find the Android device on the top, select to change driver and go straight to manual selection of the driver, select android and bootloader driver
unpack the official Factory Image with 7Zip until you get to the folder with the flash-all.bat
get the minimal adb fastboot and unpack it in the same folder as the flash-all file
wait until you see the sweet booting animation
I think I didn't forget anything important. My Pixel is alive and ready for prime time.
Big thanks redukt, may the warp speed not pass you!

rambobo said:
Big thanks redukt, may the warp speed not pass you!
Click to expand...
Click to collapse
Enjoy your device
Next time simply hit the thanks button

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
rambobo said:
Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.
Click to expand...
Click to collapse
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!

hugehead83 said:
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!
Click to expand...
Click to collapse
You didn't have to apply root again via ADB or TWRP?

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Mates, the may-factory-image is available. Same procedure as ever
https://developers.google.com/android/nexus/images#instructions
Happy flashing

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Correct
But judging from others' experiences here, YMMV. I tried the latest FlashFire build too, but that got me nowhere.

ROOT Lg K10 MTK Chipset (95% working method)

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?

Rooted with twrp and supersu,not able to boot into system,infinite loop while booting

Hi friends, i have followed instructions as per youtube video (official oneplus),struck on rebooting ..now i am able to fastboot,twrp recovery menu,have backed up using twrp backup.But not able to reboot to system.The boot logo after one plus symbol kept on rotating infinitely.Please help me.

Do a factory reset
Sent from my ONE A2005 using Tapatalk

My phone is not getting power on,though i have done factory reset from twrp 3.000 recovery.Still no go struck in boot menu with rotating logo after 1+ symbol..

Hello . Firstly try get your phone into fastboot mode. Once you have get up adb. (if you don't have adb, or find it really confusing to install, get wugfreshs root tool kit has built in adb terminal)
Open up your terminal plug in your phone and type
Code:
fastboot devices
Something should come up .
Once you done that grab the latest twrp for your device. Then FLASH! AAHHHHHHH, PROTECTOR OF THE UNIVERSE. In fastboot
Code:
fastboot flash recovery twrp.img
Once that's done type
Code:
fastboot boot recovery twrp.img
The it should boot into recovery from. Here your computer should recognize your device . You should be able to easily drag and drop a new rom and gaps on to your device
---------- Post added at 08:52 AM ---------- Previous post was at 08:50 AM ----------
Brandon Indar said:
Do a factory reset
Click to expand...
Click to collapse
Also factory reset only works on a rom level. So if roms wrong. It won't do anything

So, I had the same problem and here is my fix for it.
I am not sure, but I think you will lost all your data on this way :/
You can Skip the first 2 lines, because when you installed TWRP you already done this
1. Go to a Computer and install Adb
2. Download Minimal Adb and Fastboot
3. Download the offical Rom on the OP2 Site and copy the .zip file into the Fastboot folder
4. Rename the .zip into rom.zip
5.Connect your phone to the Computer
6. Start into Twrp, go to advanced, click on adb Sideload
6. Now go to your computer, into the Fastboot Folder and start the command line and type: adb sideload /path/to/rom.zip
7. It should now take some minutes to install the Rom, you will see how many percentages on the Screen (It will only show until 50%, don't worry about that)
8. Voila, your Phone should now work again
To root it again, there are some modified UpdateSu-Files specially for your current Rom.Version. When you are on 3.5.6 you can use the attached file

New way to flash stock rom without miflash!! (easy way) will work on any mi device

I have developed this process by mistake
TRIED AND TESTED
Requirements -1)Download the miui 9 beta rom or stable rom (ie miui 8) from officical miui page.
It has to be fastboot rom
2)Download adb tools from androiddatahost
Procedure
*extract the rom file and then move the files from the image folder to Minimal ADB and Fastboot(which is located in c/program files)
*reboot ur phone into fasboot mode.
*open the command window in Minimal ADB and Fastboot folder and type the following commands
1) fastboot -w
2) fastboot flash system system.img
3) fastboot flash boot boot.img
4) fastboot flash recovery recovery.img
*after completing the above process type the command
5) fastboot oem lock ( it's optional this will lock ur bootloader)
6) fastboot reboot
THATS ALL ITS VERY EASY PROCESS:laugh:
AND WILL WORK ON ANY MI DEVICE WHEN EVER U WANT TO ROLL BACK TO STOCK ROM:good:
?If u want proof let me know in the comments

That re-locking bootloader step is 'optional', right?

lscambo13 said:
That re-locking bootloader step is 'optional', right?
Click to expand...
Click to collapse
Yes it depends upon u
Whether u want to remain in unlocked bootloader or u want to lock it?

Adi.s said:
Yes it depends upon u
Whether u want to remain in unlocked bootloader or u want to lock it
Click to expand...
Click to collapse
i guess you better add some explanation for that step just in case someone really did all the step without knowing it was optional
thank you for this thread, useful
---------- Post added at 02:17 PM ---------- Previous post was at 02:12 PM ----------
i think you have some typos on your last words too
cheers