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.....

Stucked at "Rom Logo"

Hey guys..
I made a search on google for the best rom for a Moto G, and found a website with links for Paranoid, CNM, and Slim.. and i picked SLIMKAT
But after dong the process of installing twrp or CWM Recovery.. ended up sticking with CWM recovery cause of the buggy touch on the TWRP
so i was able to flash the rom and did it in this order
Flash Rom
Flash Gapps
Flash SU
reboot.. and got stucked at "slimkat logo"
then i decided maybe there was something wrong with the rom so i tried flashing Paranoid.. same deal.. stucked at logo.
Would anyoen please point me in the right direction fo what i need to do to fix this?
Thank you

SD card
Xcarab said:
Hey guys..
I made a search on google for the best rom for a Moto G, and found a website with links for Paranoid, CNM, and Slim.. and i picked SLIMKAT
But after dong the process of installing twrp or CWM Recovery.. ended up sticking with CWM recovery cause of the buggy touch on the TWRP
so i was able to flash the rom and did it in this order
Flash Rom
Flash Gapps
Flash SU
reboot.. and got stucked at "slimkat logo"
then i decided maybe there was something wrong with the rom so i tried flashing Paranoid.. same deal.. stucked at logo.
Would anyoen please point me in the right direction fo what i need to do to fix this?
Thank you
Click to expand...
Click to collapse
Genius me, seems at some point i deleted or formatted the sdcard now when i go to install zip on cwm recovery i get "Can't mount sd card

Xcarab said:
Genius me, seems at some point i deleted or formatted the sdcard now when i go to install zip on cwm recovery i get "Can't mount sd card
Click to expand...
Click to collapse
I'd restore stock firmware (that should get rid of those "sd card" errors) and then flash the custom recovery again.
I'd try the philZ recovery instead of CMW. And finally flash the Rom you want to.

Thank you
Landrea said:
I'd restore stock firmware (that should get rid of those "sd card" errors) and then flash the custom recovery again.
I'd try the philZ recovery instead of CMW. And finally flash the Rom you want to.
Click to expand...
Click to collapse
Ty Landrea.. in the process of doing exactly that now.. struggling on the "bootloader permission denied"
going trought the steps of unlocking bootloader again... will post how it goes

But are you sure that bootloader is unlocked?

Well i guess
denzel09 said:
But are you sure that bootloader is unlocked?
Click to expand...
Click to collapse
This is prove enough that it was
E:\Kindle Fire Utility\tools\Firmware restore lock and more 4.4.2>fastboot oem u
nlock UNIQUE_KEY
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.013s
E:\Kindle Fire Utility\tools\Firmware restore lock and more 4.4.2>

Xcarab said:
Ty Landrea.. in the process of doing exactly that now.. struggling on the "bootloader permission denied"
going trought the steps of unlocking bootloader again... will post how it goes
Click to expand...
Click to collapse
Omg that's strange. Unlocked bootloader once = unlocked bootloader forever, it's impossible you somehow re-lock it.
Did you follow the instructions on Motorola webiste to unlock?

Returning to stock process
Landrea said:
Omg that's strange. Unlocked bootloader once = unlocked bootloader forever, it's impossible you somehow re-lock it.
Did you follow the instructions on Motorola webiste to unlock?
Click to expand...
Click to collapse
Yes i think the problem is in the way i am returning to stock.
I found a thread with here in XDA last night were called "Firmware restock and more 4.4.2
but instead of using the batch file i oped them up in a text editor and run every line manually to see what the console answers after each command.
i downloaded the stock rom according to my country and carrie and simply rpelaced the files but i think the checksum did not match and thats why i was getting the denied message when doing this
%fastboot% flash system system.img_sparsechunk1
%fastboot% flash system system.img_sparsechunk2
%fastboot% flash system system.img_sparsechunk3
I'm going to rename my country stock rom xml file to match the original xml file and see

Xcarab said:
Yes i think the problem is in the way i am returning to stock.
I found a thread with here in XDA last night were called "Firmware restock and more 4.4.2
but instead of using the batch file i oped them up in a text editor and run every line manually to see what the console answers after each command.
i downloaded the stock rom according to my country and carrie and simply rpelaced the files but i think the checksum did not match and thats why i was getting the denied message when doing this
%fastboot% flash system system.img_sparsechunk1
%fastboot% flash system system.img_sparsechunk2
%fastboot% flash system system.img_sparsechunk3
I'm going to rename my country stock rom xml file to match the original xml file and see
Click to expand...
Click to collapse
Buddy be careful when you go to do all this "stuff" :good:
Try to help you with Moto Tool by Alonosoch in Android Original Development section

Thank you Denzel
denzel09 said:
Buddy be careful when you go to do all this "stuff" :good:
Try to help you with Moto Tool by Alonosoch in Android Original Development section
Click to expand...
Click to collapse
"Man on Fire"
I called in sick for work already.. have to be at this all day.. so i will try everything and wont stop untill it is fixed.
Following the step by step instructions at: http://forum.xda-developers.com/showthread.php?t=2542219&highlight=sparsechunk

Xcarab said:
"Man on Fire"
I called in sick for work already.. have to be at this all day.. so i will try everything and wont stop untill it is fixed.
Following the step by step instructions at: http://forum.xda-developers.com/showthread.php?p=51155548
Click to expand...
Click to collapse
When I restored Stock, in the zip file I downloaded (en version) instead of:
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
there were
system.img_sparsechunk0
system.img_sparsechunk1
system.img_sparsechunk2
so I had to edit the prompt commands to match the file names.
May you're facing the same issue?
Try to auto-complete commands witht the tab key, it helps you not to give the wrong imputs

Ok, do you tried the Alonsoch tool? Read carefully the op, there is your "sparsechunk" problem and how fix it.
http://forum.xda-developers.com/showthread.php?t=2635706

Thank you Landrea and Denzel
Yes Landrea, you were absolutely right the file names did not match.. i typed in the propper names and i was able to finish the whole process
Now i'm waiting for it to boot...
Finger crossed.
Thanks a lot to both of you.. You Rock!

:victory: :victory: :victory: :victory: :victory: :victory: :victory:

Xcarab said:
Yes Landrea, you were absolutely right the file names did not match.. i typed in the propper names and i was able to finish the whole process
Now i'm waiting for it to boot...
Finger crossed.
Thanks a lot to both of you.. You Rock!
Click to expand...
Click to collapse
You're very welcome
Keep us updated!
P.S. you could hit the thanks button sometimes <3

Original Post
The original Post was about being stucked at CUSTOM ROM LOGO... since this happened with different roms i decided to go back to stock rom and then the post went in this direction.. will try again tonigh to install a custom rom.. SLIM kat looks just like my style so will go for that again
Thanlk you everyone for the quick responses and this will continue...

Xcarab said:
The original Post was about being stucked at CUSTOM ROM LOGO... since this happened with different roms i decided to go back to stock rom and then the post went in this direction.. will try again tonigh to install a custom rom.. SLIM kat looks just like my style so will go for that again
Thanlk you everyone for the quick responses and this will continue...
Click to expand...
Click to collapse
I think the reason you were being stuck at the ROM logo is because you didn't unlock your phone before you tried all this..
So.. hopefully you can restore your phone back to stock rom and start over..
good luck

neozen21 said:
I think the reason you were being stuck at the ROM logo is because you didn't unlock your phone before you tried all this..
So.. hopefully you can restore your phone back to stock rom and start over..
good luck
Click to expand...
Click to collapse
My boost mobile phone is unlock but I still can't pass the cm logo or PAC man logo or the slimkat logo ... I done try 3 recoveries but I still get the same problem. I'm currently using philz recovery BC its the only one it would let me make a complete back up without any issues.. I try twrp and cwm but I get back up failed when it gets to the "backing up data section". Anyone else get the same issue? And about the ROM getting stuck at the logo any one have any idea what could it be????? I hate stock Roms even though its not that bad since its rooted lol...
Sent from my XT1031 using XDA Premium 4 mobile app

jglm4u said:
My boost mobile phone is unlock but I still can't pass the cm logo or PAC man logo or the slimkat logo ... I done try 3 recoveries but I still get the same problem. I'm currently using philz recovery BC its the only one it would let me make a complete back up without any issues.. I try twrp and cwm but I get back up failed when it gets to the "backing up data section". Anyone else get the same issue? And about the ROM getting stuck at the logo any one have any idea what could it be????? I hate stock Roms even though its not that bad since its rooted lol...
Sent from my XT1031 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Going to post all the commands i used to get it to work
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot boot TWRP-2.6.3.3-falcon.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
OKAY [ 0.508s]
finished. total time: 0.807s
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot flash recovery TWRP-2.6.3.3-falcon.i
mg
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.306s]
writing 'recovery'...
OKAY [ 0.522s]
This i used to send the rom, gapps and superuser to the media card so it was available to choose on twrp
E:\Moto G\Minimal ADB and Fastboot>adb push slim_unofficial_falcon_02-02-2014.zi
p /data/media/0
3769 KB/s (193672391 bytes in 50.180s)
E:\Moto G\Minimal ADB and Fastboot>adb push Slim_minimal_gapps.4.4.2.build.3.x.z
ip /data/media/0
3576 KB/s (62215309 bytes in 16.986s)
After that.. did
.- Do the wipes (cache/data/dalvik cache).
4.- Format system.
5.- Install the rom.
6.- Enjoy!
now on step 4, you will have to
Touch Wipe
Advanced Wipe
Check System
Then Swipe

Xcarab said:
Going to post all the commands i used to get it to work
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot boot TWRP-2.6.3.3-falcon.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
OKAY [ 0.508s]
finished. total time: 0.807s
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot flash recovery TWRP-2.6.3.3-falcon.i
mg
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.306s]
writing 'recovery'...
OKAY [ 0.522s]
This i used to send the rom, gapps and superuser to the media card so it was available to choose on twrp
E:\Moto G\Minimal ADB and Fastboot>adb push slim_unofficial_falcon_02-02-2014.zi
p /data/media/0
3769 KB/s (193672391 bytes in 50.180s)
E:\Moto G\Minimal ADB and Fastboot>adb push Slim_minimal_gapps.4.4.2.build.3.x.z
ip /data/media/0
3576 KB/s (62215309 bytes in 16.986s)
After that.. did
.- Do the wipes (cache/data/dalvik cache).
4.- Format system.
5.- Install the rom.
6.- Enjoy!
now on step 4, you will have to
Touch Wipe
Advanced Wipe
Check System
Then Swipe
Click to expand...
Click to collapse
I will try this after work man thanks tho..hopefully it works for me 2
Sent from my XT1031 using XDA Premium 4 mobile app

[Q] OnePlus One - Unable to unlock bootloader again after relocking

Hi Guys,
Hope to get some help here.
So i unlocked the bootloader of my one plus one and installed supersu + Twrp recovery. All worked fine until i decided to relock the bootloader.
I've put the device into fastboot mode and executed "fastboot oem lock" with twrp recovery still in there.
Now i am trying to unlock the bootloader again using "fastboot oem unlock" to be able to flash the stock recovery and having issues.
output of commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>
After this it boots straight to twrp recovery. I then hit reboot system and go back to fastboot mode and run the below:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (12260 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.404s
Anyone has an idea how i can unlock the bootloader again ?
Thanks
Vik

Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out

I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.

lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
Thanks i'll give that a try as soon as am home..

YrrchSebor said:
Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out
Click to expand...
Click to collapse
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks

Vikmeister said:
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks
Click to expand...
Click to collapse
Be careful if you updated your phone to XNPH30O OTA,
!!! Warning !!!
In the NEW OTA CM11S XNPH30O, the bootloader (aboot) img size changed....
We request all not to apply the unlocker scripts on the new bootloader , until we confirm/find the new bit position.
It might brick your phone and corrupt bootloader...
Click to expand...
Click to collapse
It won't work.. do not try it if you updated to XNPH30O using the OTA.

zephiK said:
Be careful if you updated your phone to XNPH30O OTA,
It won't work.. do not try it if you updated to XNPH30O using the OTA.
Click to expand...
Click to collapse
Thanks for letting me know ZephiK i haven't updated to that version yet. I still have XNPH25R. I should all good.

Fantastic.. Thanks a lot guys.. That worked like a treat.. Bootloader is now unlocked.
:laugh::good:

lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
I ran this command:
Code:
fastboot.exe boot TWRP-2.7.1.0.img
But the next step does not work:
Code:
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or from sdcard...
I got:
downloading 'boot.img'...
OKAY [ 0.484s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.487s

That's because you can't boot a recovery with the recent bootloader unless you're unlocked.
Transmitted via Bacon

Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo

Im have the same issue but I have no recovery installed..Anyway to do this

i have same issue plz give me any solution if you found any???plz let me know plzzzzz
​
piriri007 said:
Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo
Click to expand...
Click to collapse
plz help same issue

[Q] Rooting Issues with Moto G

Hi,
I'm trying to root my Moto G. Was able to unlock it but can't flash recovery or boot superboot with fastboot.
On trying to push twrp with: fastboot flash recovery twrp.img
I get the error:
target reported max download size of 536870912 bytes
sending 'recovery' (8090 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.021s
On trying to boot superboot with: fastboot boot boot.superboot.img
Iget the error:
downloading 'boot.img' ...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
I can't seem to find a solution online, does someone know how to fix these errors?

Uncannytable said:
Hi,
I'm trying to root my Moto G. Was able to unlock it but can't flash recovery or boot superboot with fastboot.
On trying to push twrp with: fastboot flash recovery twrp.img
I get the error:
target reported max download size of 536870912 bytes
sending 'recovery' (8090 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.021s
On trying to boot superboot with: fastboot boot boot.superboot.img
Iget the error:
downloading 'boot.img' ...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
I can't seem to find a solution online, does someone know how to fix these errors?
Click to expand...
Click to collapse
just install flashify from the playstore and flash a recovery from there its very easy and i think a large number of people had the same problem anyhow thats how i fixed it after further reading in xda cheers,martin

I am actually a fan of rooting without changing the recovery
just use
fastboot boot YourRecovery.img
Click to expand...
Click to collapse
and then flash e.g. latest supersu zip http://download.chainfire.eu/supersu you can even do this by adb sideload in CWM (for the recovery i used CWMrecovery)
i like this method because it will leave your recovery untouched and just root :highfive:

Why dont you flash just Philz Touch recovery? Then go to recovery option on Fastboot mode, once Philz has booted, touch REBOOT SYSTEM, then the recovery will tell you "Your device is not rooted or SU is missing, do you want to apply SU?" Then scroll to YES option and phone will reboot.. DONE, rooted! Now go to Play Store and grab SuperSU app.. Then you can flash to stock recovery....

All I had to do was change the usb port. Now everything is working fine.

martindar said:
just install flashify from the playstore and flash a recovery from there its very easy and i think a large number of people had the same problem anyhow thats how i fixed it after further reading in xda cheers,martin
Click to expand...
Click to collapse
The OP is trying to root his device. AFAIK Flashify requires the device to be rooted to work. What am I missing?

Trying to boot to twrp

Everytime I try to boot twrp i get this message.
PS C:\adb> fastboot boot twrp-3.3.1-4-guacamole.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.324s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.331s
I am bootloader unlocked so I dont know why I am getting that message. Any help would be appreciated. Thanks

Try "fastboot flash boot [img name]".

The correct command is
Fastboot boot [drag and drop the img]

phenomenalblaze said:
Everytime I try to boot twrp i get this message.
PS C:\adb> fastboot boot twrp-3.3.1-4-guacamole.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.324s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.331s
I am bootloader unlocked so I dont know why I am getting that message. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Are you on Beta1, if so, you can't boot into recovery that way, you need to flash recovery using Magisk first.

No I'm not. I'm on 9.5.11

phenomenalblaze said:
No I'm not. I'm on 9.5.11
Click to expand...
Click to collapse
If you have root, try flashing the recovery installer with Magisk

smo69 said:
Try "fastboot flash boot [img name]".
Click to expand...
Click to collapse
This command is useless it won't work. Download the latest oxygen OS zip(full rom package not the incremental one), place it in your internal storage and update it via the local updater.
After the update is complete you can boot to fastboot and then the command will work i.e. fastboot boot imagefilename.img
Hope this helps