Database Info

[Q] Boot custom image without flashing it

This may seem an already (10 times) solved question, but I'm unable to boot my Mogo G with a custom boot.img instead of the one flashed on the device.
The phone is an XT1032, currently running KitKat 4.4.4, and I use the latest SDK tools.
I download the stock firmware from sbf.droid-developers.org/phone.php, where I choose RETAIL-FR_FALCON_KLB20.9-1.10-1.24-1.1_cid7_CFC_1FF_SVC.xml.zip
I extract the boot.img file using standard unzip tools, and the zImage and initrd.img files using abootimg
Code:
adb reboot-bootloader
The phone reboots and gets to the fastboot menu
Code:
fastboot boot zImage initrd.img
The console output seems right:
Code:
creating boot image...
creating boot image - 6975488 bytes
downloading 'boot.img'...
OKAY [ 0.336s]
booting...
OKAY [ 0.244s]
finished. total time: 0.580s
The device tries to reboot, but stops at the first "M Powered by Android" splash screen
I wait one minute
I hard reboot the device by holding the power button
The device reboots, but has to pass an unusual step, "Updating Android/Optimization application ..."
I'm quite sure the same method was successful a few months ago, so what has since changed:
The device's firmware was upgraded from 4.4.3 to 4.4.4
The SDK tools were upgraded from ? to 23.0.2
I don't remember whether the firmware was available as a tar.gz or a xml.zip file, but I think it was a tar.gz, and I'm near certain I then used the SDK provided fastboot tool. Today, the firmware is available as an xml.zip file, and I think I have to use the Motorola specific fastboot tool (anyway I've tried both, for identical results)
Could anyone point me toward what I'm missing or doing wrong ?
Thanks.

Why did u extract the boot.img?
Maybe wrong kernel?
And whats about the kernel modules of your custom kernel?

sub77 said:
Why did u extract the boot.img?
Click to expand...
Click to collapse
I simply want a basic way to boot a custom initial ramdisk, without flashing it to the device. So I download the stock firmware archive, unzip it, extract the initial ramdisk (initrd.img) from the boot image, modify it, and repack it using abootimg.
And then:
Code:
fastboot boot zImage initrd.img
For me, this command conform to both the SDK provided fastboot and the Motorola specific one shows in it's help message:
Code:
boot <kernel> [ <ramdisk> ]
I'm not sure anymore of the above command's correctness:
Some information may be missing, as when you expand the boot image (boot.img) you get three files : a kernel (zImage), an initial ramdisk (initrd.img), but also some metadata (in bootimg.cfg); and this metadata is lost when I use "fastboot boot zImage initrd.img". I may try to give this information using additional fastboot options
I even suspect that a few months ago, I used fastboot with a full boot.img image as parameter, though this does not seem to fit the help message above
sub77 said:
Maybe wrong kernel?
And whats about the kernel modules of your custom kernel?
Click to expand...
Click to collapse
As I told you, I'm not currently working on the kernel, and I'm testing with _unmodified_ kernel image (zImage) and initial ramdisk (initird.img), as extracted by "abootimg -x".
Again, any idea is welcome.

Back to Stockrom (Recovery/System) Mediapad X2 703L

Ok,i found a Way back to Stock for Mediapad X2 703L
i test this and works fine.
If your Mediapad X2 Rooted and have install Custom Recovery and will go back to Stock.(Also your Pad is Rooted,Unlocked Bootloader and Twrp installed)
Backup your Data Before Flash this Firmeware!!!
Download the Huawei Extractor App unpack and install it (Download from Attachment).
Download the Huawei Firmware from here and unpack it.
Installing Mediapad X2 Driver (Hi Suite) and must have fastboot ADB installed.
Copy the Update.app in dload Folder in Internal or external Storage.(For later)
Open the Huawei Extractor and extract Recovery and or System and copy Recovery and or System in your ABB Folder.
Reboot your Mediapad in Fastboot/Bootloader Power Off - Connect to Pc and Press and hold Power and Volume Down to boot in Fastboot Mode or CMD Command adb reboot bootloader.(USB Debugging must be enabled)
Open CMD and Navigate to your ADB Folder (cd C:\ADB)
For Recovery to Update for Local Update
fastboot flash recovery RECOVERY.img
For System (If you have delete Apps from System and not wipe your Data))
fastboot flash System SYSTEM.img
wait to finish this Procedur.
The X2 Reboot and go in Setting to Update Program-Menu-Local Update and Flash your Original Firmware for GEM 703L
Wait to Reboot and you have Original Stockrom/Firmware without Root and Twrp.This wipe your Data,please Backup your Data before you make this Procedur!
I am not responsible for damage to the unit or other!!!
Sorry for my bad English.

thank you. now my phone gets bootloop.I will try this method !

I can't flash system.img.Error messaging : can't load system.img

Bootloader unlocked

I have 702L, will the 703L firmware work for my Mediapad? I couldn't find the specific firmware for it on Huawei's web-site.

It worked! Oh my god, thank you! I was close to tears, being up all night trying to fix my failed root attempt. Time to start again from scratch hahahaha!

what if in fastboot when flashing it says : " write : command not allowed " ...

How do I get USB debugging if I have no ROM installed and TWRP won't flash D: (only thing I can get is erecovery)
EDIT: Well TWRP wouldn't flash because I had to reunlock my bootloader, yes....reunlock.

letschky said:
For System (If you have delete Apps from System and not wipe your Data))
fastboot flash System SYSTEM.img
Click to expand...
Click to collapse
Code:
platform-tools>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (32354 KB)...
OKAY [ 1.010s]
writing 'recovery'...
OKAY [ 1.050s]
finished. total time: 2.060s
platform-tools>fastboot flash System SYSTEM.img
[COLOR="Red"]error: cannot load 'SYSTEM.img'[/COLOR]

xdxdxd33 said:
Code:
platform-tools>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (32354 KB)...
OKAY [ 1.010s]
writing 'recovery'...
OKAY [ 1.050s]
finished. total time: 2.060s
platform-tools>fastboot flash System SYSTEM.img
[COLOR="Red"]error: cannot load 'SYSTEM.img'[/COLOR]
Click to expand...
Click to collapse
Extract the SYSTEM.img again,i had the same Problem,then it worked

letschky said:
Extract the SYSTEM.img again,i had the same Problem,then it worked
Click to expand...
Click to collapse
Nope still does not work, I tried with GEM-703L_EMUI3.0.5_Android5.0_V100R001C233B015 and GEM-703L_EMUI3.1_Android5.1_V100R001C233B112
What is the sha1 or md5 hash for your SYSTEM.img?
My fastboot / platform-tools were outdated, so I downloaded newer ones that fixed the issue.

I'm pulling out my hair trying to get this to work.
When I try to run the local update using the UPDATE.APP file, I get an incompatible error.... I definitely downloaded the 703L stock ROM FOR MY 703L...... so wtf is the problem?

I've followed your instructions and the local update always fails with this error message i.imgur.com/Gb7P9Ks.jpg
So what could I be doing wrong...?
I've tried all these ROMs
Code:
GEM-703L_EMUI3.0.5_Android5.0_V100R001C233B015
GEM-703L_EMUI3.1_Android5.1_V100R001C233B112
GEM-703L_EMUI3.1_Android5.1_V100
GEM-703LT_EMUI3.1_Android5.1_V10

[Completed] Error "Can't Allocate Region" - Reverting Nexus 6 to Stock 6.0.1

I am currently running CM12 and want to revert to stock 6.0.1 on my Nexus 6. I use a Mac.
The bootloader and radio image files flash with no problems. But the shamu file gives me the following error every time. My phone boots up with CM12 no matter what I do. I even tried wiping TWRP with system, but still no luck flashing. I have a Nandroid backup and used it to restore for the time being.
fastboot -w update image-shamu-mmb29k.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(5475,0xa0e8f1a8) malloc: *** mach_vm_map(size=2100051968) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 2097952524 bytes
error: update package missing system.img
Any advice is appreciated!

bretttinla said:
I am currently running CM12 and want to revert to stock 6.0.1 on my Nexus 6. I use a Mac.
The bootloader and radio image files flash with no problems. But the shamu file gives me the following error every time. My phone boots up with CM12 no matter what I do. I even tried wiping TWRP with system, but still no luck flashing. I have a Nandroid backup and used it to restore for the time being.
fastboot -w update image-shamu-mmb29k.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(5475,0xa0e8f1a8) malloc: *** mach_vm_map(size=2100051968) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 2097952524 bytes
error: update package missing system.img
Any advice is appreciated!
Click to expand...
Click to collapse
Hello,
I would recommend you to read this thoroughly,
Also you may try asking here, the experts there maybe able to assist you.
-Vatsal

Vatsal said:
Hello,
I would recommend you to read this thoroughly,
Also you may try asking here, the experts there maybe able to assist you.
-Vatsal
Click to expand...
Click to collapse
Thanks for the response. My bootloader is properly unlocked (Status Code 3) and OEM is checked in developer options. I am flashing the images separately, but can't get the shamu image to flash without the error. Nothing in the thread applies to my situation since everyone seems to be successful flashing the images separately. Not me.
I'll ask in the Noob section you recommend. Although I am not a developer, I have been running a rooted device for 9 months and I have successfully flashed several custom roms. I think this is a unique problem since I have not found others who cannot flash the images separately.

Nexus 5 D821 (h) Soft Brick Fastboot Erro

Hey guys,
I need help!
A model LG Nexus 5 D821 (h) 16GB has bricked.
I downloaded 3 firmwares on https://developers.google.com/android/nexus/images#instructions for this device and execute the instructions folow:
1- extract adb minimal and fastboot on new paste
2- extract file compacted of firmware at same new paste
3- execute commands fastboot
(now is the problem)
when i execute "fastboot flash system system.img
an error appears:
REMOTE FAILED: (size too larger)
I think that file system.img it´s than larger. File´s size is 1961709KB. But a device information for max download size supported is 1073741824B, or aproximatted 1073741KB.
an others firmwares it was split a chunk files, exemple:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.3
etc etc
Its make file minors.
Please, any solution???

"I downloaded 3 firmwares" - which firmwares?
Which system.img are you trying to flash? Which tutorial are you following?
Did you check that the firmware was good by verifying the checksum? You can do this with a free Windows program called Checksum Utility - http://download.cnet.com/MD5-SHA-Checksum-Utility/3000-2092_4-10911445.html
Is your device bootloader unlocked? Did you have "Enable OEM unlock" ticked in developer options?
Did you manage to flash any partitions? Are you flashing manually or via a toolkit or flash-all.bat?
Too many questions - you need to provide more detail about exactly what you've done.

Fastboot and Multiple <system_xx.img>

Within stock rom it has multiple system image files:
system_1.img
system_2.img
...
If i wanted to flash this to system do i simply:
fastboot flash system system_1.img
fastboot flash system system_2.img
fastboot flash system system_30.img
Or must i join them first?
Thanks