Database Info

Bricked ZM609 (xybaord) READ THIS

ok so here is a quick question,
i have not had a locked device that has fastboot before
but here is the scenario and the question
i copied my recover, as well as a few other imgs with this command
dd if=/dev/block/mmcblk1p12 of=/sdcard/recovery.img
and for ****s and giggles i decided that iwould see if it would let me flash the img back.
so with device in fastboot mode
i entered
fastboot flash recovery recovery.img
and it flashed....
so i guess my question is... would it flash a custom recovery???
heres the read out
Code:
C:\Users\zach\Desktop\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (9216 KB)...
OKAY [ 0.454s]
writing 'recovery'...
OKAY [ 1.677s]
finished. total time: 2.132s
C:\Users\zach\Desktop\platform-tools>reboot
'reboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\zach\Desktop\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.007s
C:\Users\zach\Desktop\platform-tools>

if any one has brick their xyboard 4g 8.2
please contact me
for more proof of concept i have two mz609
on the one that i flashed recovery it loads and will preform resets and wipe cache, which is ECXATLY what the mz609 tab that is stock + root does and on the stock one i have not fastbooted any recovery,
so this leads me to believe that we can in fact flash imgs, at least stock imgs that is
well if anyone has bricked there ZM609-32
here are some imgs that may or may not work to fastboot img
and before i get flamed with "its a locked bootloader blah blah blah"
if u look at the above code u will see that i successfully fastboot flashed the recovery and the stock recovery still loads, and works with all intensive purposes
i have not however flashed the system.img or the boot.img
but if you have already bricked your tablet,,,whats the worse that could happen right...
if you do use this please report back here and let me know the outcome, and dont just say it didnt work, i want the cmd copied so that i can read where it fails
https://dl.dropbox.com/0/view/n5rll0c7lk7b0ap/my roms/xybaord dump/MZ609_fastboot_images.zip

Sounds interesting

Never mind.....

Can't enter TWRP

I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?

BoredDude said:
I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?
Click to expand...
Click to collapse
You can try to boot directly into twrp with "fastboot boot TWRP.img"

zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s

zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
BoredDude said:
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s
Click to expand...
Click to collapse
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!

ChazzMatt said:
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!
Click to expand...
Click to collapse
I fixed it erasing the TWRP folder in my internal storage

Trying to root with Android 8.0

So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?

Kew01 said:
So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?
Click to expand...
Click to collapse
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images

Kew01 said:
So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?
Click to expand...
Click to collapse
You skipped a step. You also need to issue the fastboot command to unlock it.
This will WIPE your phone. No way around that.
fastboot flashing unlock

TonikJDK said:
You skipped a step. You also need to issue the fastboot command to unlock it.
This will WIPE your phone. No way around that.
fastboot flashing unlock
Click to expand...
Click to collapse
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.

Kew01 said:
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.
Click to expand...
Click to collapse
This is why you should unlock the phone as soon as you buy it.

So maybe a dumb question but I'm new to all this. Is there any way I could completely backup a clone of my phone's data, and then restore it after root, so that everything is just as it was, except now I have root privileges?

Kew01 said:
So maybe a dumb question but I'm new to all this. Is there any way I could completely backup a clone of my phone's data, and then restore it after root, so that everything is just as it was, except now I have root privileges?
Click to expand...
Click to collapse
No. You can do this once you are rooted and have TWRP but not before. Just back up your important data and go for it.

Kew01 said:
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.
Click to expand...
Click to collapse
Isn't app data automatically backed up on Google servers? Or am I recalling it wrongly?

Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Whenever I click "Acknowledge" on the page, the page just reloads?

Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Kew01 said:
Whenever I click "Acknowledge" on the page, the page just reloads?
Click to expand...
Click to collapse
**** nevermind I figured it out.

Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Sorry for spamming you, but it looks like the official instructions only show you how to re-flash the system OS without root privileges? My goal is to re-flash with root.

Kew01 said:
Sorry for spamming you, but it looks like the official instructions only show you how to re-flash the system OS without root privileges? My goal is to re-flash with root.
Click to expand...
Click to collapse
1. Flash factory image
2. Boot system
3. Reboot bootloader
4. Fastboot Twrp 3.1.1.1
5. Flash Twrp 3.1.1.1 installer zip or not if you don't want permanent Twrp
6. Flash SuperSU or Magisk
7. Reboot system

[Guide] Unlock Bootloader, Get Root and Flash TWRP Recovery

Warning: This guide is a WiP and is NOT complete. DO NOT FOLLOW THIS GUIDE UNTIL THIS MESSAGE IS REMOVED.
You will require ADB and Fastboot installed on your computer.
First you will need to send a private message to the_lazer with your IMEI and Serial Number and they will give you a key to unlock the bootloader.
Wherever you see KEY in this guide replace that with the key you got given.
Second you will need to download Magisk from here, rename that file to
Code:
magisk.zip
Then download the TWRP.img from here.
If the touch screen doesn't work on TWRP then press the power button so the screen sleeps and then press it again so it wakes up and it should work.
Make sure your device has "Enable OEM Bootloader Unlocking" enabled in settings.
Plug your device into your computer and turn the device off.
Hold the power and volume up buttons, if it has a menu where reboot to bootloader or fastboot is a option then do that.
Once in fastboot mode on your computer run:
Code:
fastboot oem key KEY
fastboot oem unlock
Press the volume up button on the phone and it should unlock successfuly.
Once that is done you will need to run:
Code:
fastboot boot TWRP.img
Note that you should NOT flash twrp yet as it will give "red state" error and prevent your device from booting.
Then once in TWRP if it asks for a password then click cancel. If that doesn't work then press the power button and then press it again so the screen sleeps and wakes up then swipe to unlock and click cancel again.
Swipe to allow modifications then click Advanced and then ADB Sideload and swipe.
Next run
Code:
adb sideload magisk.zip
and it will flash magisk.
Magisk will provide root and patch the bootloader so it will still boot past the "orange state" screen.
Next go back twice and click Reboot and then Bootloader.
Then on your computer run
Code:
fastboot flash recovery TWRP.img
That will now flash TWRP.
The reason you need to flash TWRP after you have flashed magisk is because magisk is required to patch the bootloader so that it will actualy boot.
Then run
Code:
fastboot reboot
and you should eventualy reboot to android, give it about 30mins to boot just to be safe.
Then install Magisk Manager from
Code:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
.
You should now have a working rooted Nokia 3 which uses Magisk.
TODO: Add troubleshooting section and steps to follow if something goes wrong.

Any feedback? Does anyone want to pm me and try it safely?

JakesDen said:
Any feedback? Does anyone want to pm me and try it safely?
Click to expand...
Click to collapse
Don't worry, then next time someone asks about rooting their Nokia 3 I will be sure to point them to this thread, and I like how you described the process. It's very easy to understand. I already have my phone rooted and i'm sticking with my stock recovery because of updates

redweaver said:
Don't worry, then next time someone asks about rooting their Nokia 3 I will be sure to point them to this thread, and I like how you described the process. It's very easy to understand. I already have my phone rooted and i'm sticking with my stock recovery because of updates
Click to expand...
Click to collapse
Thanks :3

nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?

SkaboXD said:
nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?
Click to expand...
Click to collapse
Runs flawlessly and doesn't crash or bootloop.
However if you enable a magisk module which causes a bootloop then you would have to factory reset the device unless /data is decrypted in which case you can just delete the folder the magisk module is located in. I will add to the guide instructions on how to have a decrypted /data partitionlater.

SkaboXD said:
nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?
Click to expand...
Click to collapse
QUOTE=virenhp;75052054]I have Unlocked bootloader in Nokia 3 TA 1032
I flashed Trwp Successfully but Still Getting Stock Recovery when entered to Recovery Mode. Please Help Me .. How Can I get Twrp Recovery. Thank Yo

virenhp said:
QUOTE=virenhp;75052054]I have Unlocked bootloader in Nokia 3 TA 1032
I flashed Trwp Successfully but Still Getting Stock Recovery when entered to Recovery Mode. Please Help Me .. How Can I get Twrp Recovery. Thank Yo
Click to expand...
Click to collapse
if flashing doesn't work, use this command: fastboot boot recovery.img
You will boot to twrp successfully but you need to do this every time when you want twrp.

I followed your guide step by step but when rebooting after TWRP flash, the phone does not boot into system. No matter how i try to reboot the android logo pop up with orange state and the next thing is TWRP loading. I can boot into bootloader, so i tried flashing magisk and TWRP again, but no success. Any help would be appreciated

I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed

I recommend not using SuperSu.
You can however install magisk and then use magisk manager to install a systemless xposed.
Just don't use the official regular xposed or your device won't boot.

redweaver said:
I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed
Click to expand...
Click to collapse
I recommend not using SuperSu.
You can however install magisk and then use magisk manager to install a systemless xposed.
Just don't use the official regular xposed or your device won't boot.

Please make sure to quote me so I get notified if you respond.

it's good and easy guide, i got my nokia 3 rooted in 30mins

Send me the adress where i'm sending private messege

Tayyabmadina said:
Send me the adress where i'm sending private messege
Click to expand...
Click to collapse
Just click "New Private Message" and enter "the_lazer" in the "Recipient Username" field.
Or message them from https://forum.xda-developers.com/member.php?u=3665957

Thank you

i did everything like on tutorial but when i finish it. it boot to TWRP

redweaver said:
I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed
Click to expand...
Click to collapse
My Nokia3 roadacts:
- Developper mode OK
- Unlocked OK
- Install magisk & TWRP
fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.047s]
finished. total time: 0.484s
adb sideload magisk.zip
Total xfer: 1.59x
fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (13916 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.734s]
finished. total time: 1.188s
- Install SuperSU
fastboot reboot
rebooting...
finished. total time: 0.016s
fastboot reboot
adb sideload SuperSU-v2.82-201705271822.zip
That's the only way I found to install SuperSU, cause I don't succed to put the zip in my phone: All mounts in TWRP failed : USB (a R1 warning PC appears), internal... I had transfert the zip in the Nokia before doing all but I don't know where it's located when I browse in TWRP.
According to the trace I saw on the phone when I did the adb sideload, SuperSU install and config seems to be OK, but I'm no sure.
When I open a term on the phone, navigate in the filesystem, I can't do su but see a SuperSU path with an install shell that failed...
My 2 problems:
1/ is SuperSU OK ?
2/ I'm block : how to go back to Andoid to execute root checker or SuperSU, always boot on TWRP ?
Need Help.

JBData said:
My Nokia3 roadacts:
- Developper mode OK
- Unlocked OK
- Install magisk & TWRP
fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.047s]
finished. total time: 0.484s
adb sideload magisk.zip
Total xfer: 1.59x
fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (13916 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.734s]
finished. total time: 1.188s
- Install SuperSU
fastboot reboot
rebooting...
finished. total time: 0.016s
fastboot reboot
adb sideload SuperSU-v2.82-201705271822.zip
That's the only way I found to install SuperSU, cause I don't succed to put the zip in my phone: All mounts in TWRP failed : USB (a R1 warning PC appears), internal... I had transfert the zip in the Nokia before doing all but I don't know where it's located when I browse in TWRP.
According to the trace I saw on the phone when I did the adb sideload, SuperSU install and config seems to be OK, but I'm no sure.
When I open a term on the phone, navigate in the filesystem, I can't do su but see a SuperSU path with an install shell that failed...
My 2 problems:
1/ is SuperSU OK ?
2/ I'm block : how to go back to Andoid to execute root checker or SuperSU, always boot on TWRP ?
Need Help.
Click to expand...
Click to collapse
I haven't used magisk before, but I was under the opinion that you didn't need to sideload or flash supersu once you've sideloaded magisk. Maybe you need to read up on activating root with magisk

Pixel 3a - stuck on BootLoader with: error boot prepar

Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked

DarthLuch said:
Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked
Click to expand...
Click to collapse
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.

adm1jtg said:
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.
Click to expand...
Click to collapse
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!

DarthLuch said:
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!
Click to expand...
Click to collapse
If 21 worked but 22 didn't... Going from my faltering memory that means your not on March security, your on feb or earlier. 22 only worked on March, i am running it myself.

I got stuck here, too... I used the flash tool (flash.android.com) and it put me back to stock after about a 20 minute progress bar crawl

I have the same problem can someone help me?

YYa solucionaste ?