mtc19x modified image required - Nexus 6P Q&A, Help & Troubleshooting

hope this is the right place to post this thread
just wanting to root stock mtc19x using systemless root but looking for the modified boot image. is it too early for that still? thanks for any inputs

No , its the wrong Place http://forum.xda-developers.com/showthread.php?t=2731129.
Your Posting belongs in Quest / Answer but here is what you are looking for
Modified Boot Img
http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684

that's what i get now

RockyAJ said:
that's what i get now
Click to expand...
Click to collapse
Have you unlocked the bootloader first?

ravinder0003 said:
Have you unlocked the bootloader first?
Click to expand...
Click to collapse
yes it is already unlocked previously. i just did a new clean wipe for the phone and flashed the mtc19x factory image

Try this:
fastboot oem device-info
It will confirm if it is unlocked...
Also try to boot twrp by:
fastboot boot recovery_name.img
Both commands will confirm the same.

Related

Fastboot - Partition table doesn't exist

I've been trying to push the bootloader and radio from the 4.2.2 factory image using fastboot using the commands below
fastboot flash radio "filename.img"
fastboot flash hboot "filename.img"
The radio works just fine, but while flashing the bootloader it gives me an error saying "partition table doesn't exist".
Any idea what this means and how it can be fixed?
AW: Fastboot - Partition table doesn't exist
Hboot is HTC. On Nexus 4 it is
Code:
fastboot flash bootloader bootloader.img
Sent from my Nexus 4 using xda premium
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
siddjazz said:
fastboot flash hboot "filename.img"
The radio works just fine, but while flashing the bootloader it gives me an error saying "partition table doesn't exist".
Any idea what this means and how it can be fixed?
Click to expand...
Click to collapse
Sent from my Nexus 4 in a Faraday cage
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
No
boot is the kernel.
bootloader is the bootloader.
There is no "bootloader" partition. Good luck flashing on that. Nexus 4 mount point thread:
http://forum.xda-developers.com/showpost.php?p=34141701&postcount=1
Nuu~ said:
No
boot is the kernel.
bootloader is the bootloader.
Click to expand...
Click to collapse
Sent from my Nexus 4 in a Faraday cage
Nuu~ said:
No
boot is the kernel.
bootloader is the bootloader.
Click to expand...
Click to collapse
So the command would be fastboot flash bootloader "boot.img" ?
This is a bit confusing
siddjazz said:
So the command would be fastboot flash bootloader "boot.img" ?
This is a bit confusing
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-mako-makoz10o.img
and for the radio:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
KyraOfFire said:
There is no "bootloader" partition. Good luck flashing on that. Nexus 4 mount point thread:
http://forum.xda-developers.com/showpost.php?p=34141701&postcount=1
Click to expand...
Click to collapse
is that so? =)
even if there is no "bootloader" partition, fastboot still flashes the right partition when used with "flash bootloader".
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
You're gonna make someone brick their device. Do us all a favor and stick to toolkits. Please.
It's definitely most ****ing definitely:
Code:
fastboot flash bootloader bootloader.img
KyraOfFire said:
hboot is HTC. for N4 you use
fastboot flash boot boot.img
boot.img is whatever your bootloader image is. Please note:flashing wrong/corrupted boot.img is difficult to recover.
Click to expand...
Click to collapse
NO!
Your advice above is totally wrong, and will brick a phone if it is followed. Boot is the kernel, NOT the bootloader.
Sent from my Nexus 4
starscream92 said:
You're gonna make someone brick their device. Do us all a favor and stick to toolkits. Please.
It's definitely most ****ing definitely:
Code:
fastboot flash bootloader bootloader.img
[/QUOTe
Lmfao
I guess toolkits do have a purpose
i gave you a thanks for the laugh
Click to expand...
Click to collapse
I followed his instructions
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
qsylalyn said:
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
Click to expand...
Click to collapse
boot = kernel
bootloader = bootloader
radio = modem
userdata = nand´s user data storage(/data)
system = system
cid = not used on n4
so for god sake
just install stock images
its pretty straitgh forward, just double click on .bat
qsylalyn said:
I followed his instructions and used fastboot flash boot boot.img
Is it hopeless and I need to buy a new phone or is their still hope?
Oddly, it seemed to allow me to use the correct method fastboot flash bootloader boot.img, bu I get stuck in a bootloop.
If anyone could help me that would be greatly appreciated.
Click to expand...
Click to collapse
Of course you're in a boot loop. You still have the bootloader image in your kernel because that's where you flashed it to!
Wouldn't the solution be to get a KERNEL image and flash that to the BOOT partition before you flash your bootloader image to its correct partition (bootloader) which is what you now doing?
You never posted back on where you ended up with your phone.

Strange problem with Re-Locking bootloader

Hi guyz, i've a little problem here.
I've to Lock my bootloader. Now i did it several times, with different tools too. Now:
If i use correct droidboot version (lollipop one) and flash it, the bootloader is not (secure), so not locked.
But if i try with a tool and it flashes the KK fastboot, it works, it's relocked.
Can you tell me why? Thanks!
steakhutzeee said:
Hi guyz, i've a little problem here.
I've to Lock my bootloader. Now i did it several times, with different tools too. Now:
If i use correct droidboot version (lollipop one) and flash it, the bootloader is not (secure), so not locked.
But if i try with a tool and it flashes the KK fastboot, it works, it's relocked.
Can you tell me why? Thanks!
Click to expand...
Click to collapse
Seems the Lollipop fastboot doesn't have the signature check that kitkat fastboot has.
But, even you can flash custom files with locked bootloader and lollipop fastboot, the system don't boot, stucks at USB logo, so it means the bootloader is locked.
leonardohenrique10 said:
Seems the Lollipop fastboot doesn't have the signature check that kitkat fastboot has.
But, even you can flash custom files with locked bootloader and lollipop fastboot, the system don't boot, stucks at USB logo, so it means the bootloader is locked.
Click to expand...
Click to collapse
Thanks! You sure about this? I've to return the phone to amazon, and i would to be sure of this :silly:
steakhutzeee said:
Thanks! You sure about this? I've to return the phone to amazon, and i would to be sure of this :silly:
Click to expand...
Click to collapse
Yes, I tested in my phone, flashed custom kernel with locked bootloader and fastboot from Lollipop .87, flash sucessfully, but when I try to boot... USB logo.
Only KitKat fastboot has signature check.
leonardohenrique10 said:
Yes, I tested in my phone, flashed custom kernel with locked bootloader and fastboot from Lollipop .87, flash sucessfully, but when I try to boot... USB logo.
Only KitKat fastboot has signature check.
Click to expand...
Click to collapse
Ok, thank you
In fastboot (lollipop) i've an (?) next to signature and other values i don't remeber. You too?
steakhutzeee said:
Ok, thank you
In fastboot (lollipop) i've an (?) next to signature and other values i don't remeber. You too?
Click to expand...
Click to collapse
Yes, same on my device. I think it's normal.
Yes, fastboot mode of lollipop firmware on ZenFone 5 / 6 is able to flash custom kernel / recovery, but it won't boot until bootloader unlocked.

Meizu PRO 5 bootloop no recovery locked bootloader

Hi all,
I am in trouble with the PRO 5.
Actual situation:
No recovery mode available
The phone boots but when is time to go in the home screen, the screen becomes black and only the power button response so I only turn it off or restart.
Fastboot mode available but the bootloader is locked
I tried many time with the Multiupgrade tool and TestPCTool but the answer is "Token sign failed"
Could someone help me before to put the phone in the trash
Upppppp!!!!!
You could try to unlock it using "fastboot oem unlock", but if it works it probably wipes the userdata partition, and it may fail. If you manage to unlock it, just reflash the stock image, but without the bootloader.
If this doesn't work, there is a similar thread in a different forum which may help you:
https://forum.meizufans.eu/topic/5376/meizu-pro-5-have-rooted-rom-but-lost-recovery-phone-can-boot-pls-help
Daniel Abrecht said:
You could try to unlock it using "fastboot oem unlock", but if it works it probably wipes the userdata partition, and it may fail. If you manage to unlock it, just reflash the stock image, but without the bootloader.
If this doesn't work, there is a similar thread in a different forum which may help you:
https://forum.meizufans.eu/topic/53...rom-but-lost-recovery-phone-can-boot-pls-help
Click to expand...
Click to collapse
I know the italian guy of this 3D and I can tell u, "fastboot oem unlock" doesn't work unfortunately :crying:
Thanks Pycon.
He is right, no way to unlock the bootloader, at the moment
just try this. good luck man. http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678
tzzzz said:
just try this. good luck man. http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678
Click to expand...
Click to collapse
Thanks but tried many times: Token signature fail...
Have you tried flashing the whole system (20150923195421_demo_prd_stable) as described in the M86 firmware upgrade tutorial.pdf ?
st0rm77 said:
Have you tried flashing the whole system (20150923195421_demo_prd_stable) as described in the M86 firmware upgrade tutorial.pdf ?
Click to expand...
Click to collapse
Where is that tutorial?
DarginMahkum said:
Where is that tutorial?
Click to expand...
Click to collapse
It resides in the Meizu Tools post, but never mind that. I dove into the security and fastboot uses secure boot so unless there is an exploit your stuck.
Are you able to flash the boot partition ?
If so, you might be able to flash the recovery.img onto the boot (bootimg) partition. Then drop an update.zip into the root of userdata and reboot.
Good luck.
Hey Grumpy,
I extracted the kernel and ramdisk from the recovery image (flyme_5.6.1.19_daily). Unpack these files into a directory, then run
# fastboot boot kernel ramdisk
If it boots you can:
- erase to factory default
- maybe ?? flash /sdcard/update.zip ??
Good luck :good:
st0rm77 said:
Hey Grumpy,
I extracted the kernel and ramdisk from the recovery image (flyme_5.6.1.19_daily). Unpack these files into a directory, then run
# fastboot boot kernel ramdisk
If it boots you can:
- erase to factory default
- maybe ?? flash /sdcard/update.zip ??
Good luck :good:
Click to expand...
Click to collapse
Nope...
creating boot image...
creating boot image - 15699968 bytes
downloading 'boot.img'...
FAILED (remote: permission denied!)
finished. total time: 0.000s

Bootloop cant access twrp recovery

I was at work when i entered a bootloop. I was doing nothing special maybe using the camera. I was bootloader unlocked rooted on latest twrp and on the latest official dirty unicorn I think 10.4 and everything was fine.
After the bootloop started I tried entering recovery in which it only boot loops. I can only access the bootloader screen. I Can see my device in fastboot devices.
I think my next step is to flash some Google factory images in fastboot. But I was wondering if my device be encrypted with fingerprints and a pin will affect it because I've ran into a problem last year when flashing a new version of TWRP it asked for passcode when one was not set.
I'd love to be able to recover some of my data but I guess if it's Encrypted that is not a chance, so I guess I will fastboot Flash the original images.
Is there going to be any problems when I try to flash Nexus images while it is encrypted with a passcode, Any suggestions?
Yeah, standard answer here is to flash the fastboot images. It'll be wiping/overwriting system and vendor so you shouldn't have any issues with the previous fingerprints. It'd be a good idea to wipe data once you get into TWRP afterwards but I wouldn't worry about wiping/formatting userdata.
Heisenberg said:
Yeah, standard answer here is to flash the fastboot images. It'll be wiping/overwriting system and vendor so you shouldn't have any issues with the previous fingerprints. It'd be a good idea to wipe data once you get into TWRP afterwards but I wouldn't worry about wiping/formatting userdata.
Click to expand...
Click to collapse
Thanks... I was just re reading your huge thread for the 4th time this year.
Heisenberg said:
Yeah, standard answer here is to flash the fastboot images. It'll be wiping/overwriting system and vendor so you shouldn't have any issues with the previous fingerprints. It'd be a good idea to wipe data once you get into TWRP afterwards but I wouldn't worry about wiping/formatting userdata.
Click to expand...
Click to collapse
I flashed the stock images mtc19x and its bootlooping to hell. Is it time for me to call Google? To see if I can get a new one I bought it in November when it came out
dontbeweakvato said:
I flashed the stock images mtc19x and its bootlooping to hell. Is it time for me to call Google? To see if I can get a new one I bought it in November when it came out
Click to expand...
Click to collapse
It's worth trying the latest (MTC20F) images first. And if that doesn't work I'd try formatting userdata too.
Heisenberg said:
It's worth trying the latest (MTC20F) images first. And if that doesn't work I'd try formatting userdata too.
Click to expand...
Click to collapse
Hey man, you think i can relock the bootloader with only access to the bootloader screen. I can't access anything accept for bootloader.... It won't boot up or go into recovery.
I'm returning it for rma
dontbeweakvato said:
Hey man, you think i can relock the bootloader with only access to the bootloader screen. I can't access anything accept for bootloader.... It won't boot up or go into recovery.
I'm returning it for rma
Click to expand...
Click to collapse
Yeah, relocking the bootloader is easy, just put it in bootloader mode and issue this command:
Code:
fastboot flashing lock
Heisenberg said:
Yeah, relocking the bootloader is easy, just put it in bootloader mode and issue this command:
Code:
fastboot flashing lock
Click to expand...
Click to collapse
I did that exactly. It returned with the list of commands
Fastboot flashing lock
I think it can't. When I type devices it comes back with a serial number and I could even flash boot system and all that from the system image. But when I type fastboot flashing lock it acts like it can't complete that request. Hopefully Huawei or Google won't care if my bootloader is unlocked although i did Flash the factory images and unrooted it
dontbeweakvato said:
I did that exactly. It returned with the list of commands
Fastboot flashing lock
I think it can't. When I type devices it comes back with a serial number and I could even flash boot system and all that from the system image. But when I type fastboot flashing lock it acts like it can't complete that request. Hopefully Huawei or Google won't care if my bootloader is unlocked although i did Flash the factory images and unrooted it
Click to expand...
Click to collapse
That usually means your fastboot isn't up to date.
Heisenberg said:
That usually means your fastboot isn't up to date.
Click to expand...
Click to collapse
Yea that dawned on me and yea it worked. I was thinking there was an error because the board is fried.
Thanks

delete guide

delete guide
--reserved--
I have a question i used a all in one and unlocked the boot never did the critical comand but says my boot is unlocked
rob420p said:
I have a question i used a all in one and unlocked the boot never did the critical comand but says my boot is unlocked
Click to expand...
Click to collapse
Unlock and Unlock_critical are not the same. Unlock itself change nothing, need critical to flash things...
Matteo
It's possible to remove warning ?
It's possible in Moto device
mbangi said:
It's possible to remove warning ?
It's possible in Moto device
Click to expand...
Click to collapse
Nope. Sorry
Matteo
Matteo said:
Nope. Sorry
Matteo
Click to expand...
Click to collapse
What if I install
Custom ROM
Custom recovery
Without unlocking _critical
mbangi said:
What if I install
Custom ROM
Custom recovery
Without unlocking _critical
Click to expand...
Click to collapse
Still nope
mbangi said:
What if I install
Custom ROM
Custom recovery
Without unlocking _critical
Click to expand...
Click to collapse
You need to unlock critical to flash things. So you can't.
Matteo
fastboot flashing unlock
fastboot flashing unlock_critical
when I enter this in terminal then it starts the first command but not the second, what to do?
Thread closed on OP request

Categories

Resources