Decided to create an insecure boot.img for the new release. The boot.img was pulled from the official factory images and ro.secure has been set to 0.
So now you can obtain ADB root priviledges.
Please do not attempt to flash this if you don't know what you are doing! I am not responsible for any misuse of flashing this.
Flash using fastboot:
boot.img - MD5: 589885EC34A95735F924501A8548D891 - fastboot flash boot boot.img
Kind Regards,
Revoked
DL-Link: boot.img
If you can, please add the boot img as an attachment. We have seen DropBox links go 404 with files like these.
You can upload an Img file up to 8MB on here
worked fine
EDIT: it has a bug where it stuck in the charging animation while the phone is powered off, probably a bad repack of the img..back to the stock kernel
Related
Hi!
I have FW .62 and i want to ROOT... I have
[KERNEL][PLAY][GSM] Advanced Stock (with Recovery) [Rel:v01][Dt:1/JAN][FW:.42/58/62]
So how i can use this Kernel to make a ROOT. I see this post: Post 11 so this is possible
Thaks for advance!
Kucharskov
P.S Sorry for my English.
the kernel is prerooted
and if you want to install it
first of all unlock your bootloader http://unlockbootloader.sonymobile.com/instructions
after that follow the instructions
DooMLoRD said:
[ how to install this kernel ]
download the boot.img
save the boot.img in the folder with fastboot binaries (fastboot.exe files)
power down device
start device in fastboot mode
use the following command to flash the boot.img
Code:
fastboot flash boot boot.img
reboot phone and enjoy the kernel
Click to expand...
Click to collapse
OR
use the flashtool fastboot mode HOW!!
I am trying to get Arch to run on my zf2 and I got both and unmkbootimg and a mkbootimg binary. I tried to unpack the stock boot.img, replace the kernel and initramfs with those from Arch, change the command line and boot that image using `fastboot boot new_boot.img` but nothing happened (no I did not expect it to be this easy, but gotta try still!)
So my question is: once I have a booting boot.img I can populate the /system partition with Arch and then see if everything will start up properly, so how can I make a boot.img using the kernel and initramfs from Arch?
I am rooted, have TWRP and my bootloader is unlocked btw
fastboot boot command isn't supported on ZF2.
You have to flash boot and then boot it as usual.
Hi guys,
I was getting boot loop every time I tried to factory flash mdb08i from https://developers.google.com/android/nexus/images?hl=en on my Nexus 5X. I flashed this build more than 5 times and let the device run 20+ minutes during boot animation.
I generally used method 2 from Nexus 5 tutorial since that was the tutorial I used on my Nexus 5:
Code:
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
fastboot erase cache
fastboot flash cache C:\androidimage\cache.img
However, the missing piece that solved my boot loop was to also run this command at the very end
Code:
fastboot flash vendor vendor.img
I normally have a batch script that runs all the commands for me.
How I found out about flashing vendor.img:
I found this issue only after I factory flashed mdb08i that I accidentally immediately flashed chainfire's modified mdb08i boot image for enabling root. After flashing chainfire's modified mdb08i, my Nexus 5X passed the boot animation but gave "Internal device error". So I looked up the error and found this thread: http://forum.xda-developers.com/nexus-9/help/internal-problem-device-nexus-9-t3112827
I also tried other methods as mentioned in this thread but no luck with it on my end but perhaps will help others: http://forum.xda-developers.com/nexus-4/help/stuck-bootloop-flashing-factory-image-t2527382
Hope this help others who are also stuck on boot loop after flashing mdb08i on their Nexus 5X.
Im glad that you fixed your bootloop but im not exactly sure why you didn't just run the flash-all.bat file that is included in every firmware image (after you upack the tgz file) and gives you the exact procedure you need to follow for that device, or at least use it as a base for your commands. I guess you learned this the hard way but for future devices you might want to check that file first to see exactly what you need to do.
Anyway well done for fixing it yourself
Mark.
Sometimes the flash-all doesn't work properly. If you look at guides to flashing factory images, many of them even note that issue, suggesting it is fairly common. The fix? Manually flashing each file rather than using flash-all.
Sent from my E5823 using Tapatalk
phositadc said:
Sometimes the flash-all doesn't work properly. If you look at guides to flashing factory images, many of them even note that issue, suggesting it is fairly common. The fix? Manually flashing each file rather than using flash-all.
Sent from my E5823 using Tapatalk
Click to expand...
Click to collapse
Ok my mistake on that one lol I forgot the vendor image is inside the zip file. I set the Unified Android Toolkit a long time ago to automatically extract all images and flash each one individually when flashing a stock firmware image. That was the only way to successfully fix certain system problems on earlier nexus devices.
Mark.
phositadc said:
Sometimes the flash-all doesn't work properly. If you look at guides to flashing factory images, many of them even note that issue, suggesting it is fairly common. The fix? Manually flashing each file rather than using flash-all.
Sent from my E5823 using Tapatalk
Click to expand...
Click to collapse
Correct.
mskip said:
Ok my mistake on that one lol I forgot the vendor image is inside the zip file. I set the Unified Android Toolkit a long time ago to automatically extract all images and flash each one individually when flashing a stock firmware image. That was the only way to successfully fix certain system problems on earlier nexus devices.
Mark.
Click to expand...
Click to collapse
To give a glimpse of the modified batch file I did is as follow, notice how the fastboot -w update bullhead.zip line is commented out since it has trouble sending massive data transfer to the phone.
Modified "flash-all.bat" from bullhead-mdb08i-factory-64536fcf.tar
Code:
@ECHO OFF
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-bullhead-bhz10i.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-bullhead-m8994f-2.6.28.0.65.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
::fastboot -w update image-bullhead-mdb08i.zip
:: Modified by haremmon below
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash vendor vendor.img
echo Press any key to exit...
pause >nul
exit
haremmon said:
Hi guys,
I was getting boot loop every time I tried to factory flash mdb08i from https://developers.google.com/android/nexus/images?hl=en on my Nexus 5X. I flashed this build more than 5 times and let the device run 20+ minutes during boot animation.
I generally used method 2 from Nexus 5 tutorial since that was the tutorial I used on my Nexus 5:
Code:
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
fastboot erase cache
fastboot flash cache C:\androidimage\cache.img
However, the missing piece that solved my boot loop was to also run this command at the very end
Code:
fastboot flash vendor vendor.img
I normally have a batch script that runs all the commands for me.
How I found out about flashing vendor.img:
I found this issue only after I factory flashed mdb08i that I accidentally immediately flashed chainfire's modified mdb08i boot image for enabling root. After flashing chainfire's modified mdb08i, my Nexus 5X passed the boot animation but gave "Internal device error". So I looked up the error and found this thread: http://forum.xda-developers.com/nexus-9/help/internal-problem-device-nexus-9-t3112827
I also tried other methods as mentioned in this thread but no luck with it on my end but perhaps will help others: http://forum.xda-developers.com/nexus-4/help/stuck-bootloop-flashing-factory-image-t2527382
Hope this help others who are also stuck on boot loop after flashing mdb08i on their Nexus 5X.
Click to expand...
Click to collapse
You are a life saver. Thank you for everything
Thanks man! Was sitting here scratching my head for a bit. N was giving me issues and I am on vacation and only have access to a MacBook and getting ADB on that was a headache itself!
Flashed vendor and good to go though.
Deleted
mathsz said:
Dude, I could kiss you right now.
big huge thanks. I went to the flash-all.bat and modified the text, the vendor is not even specified. HEADACHE
Big thanks
Click to expand...
Click to collapse
There is no reason to specify vendor in flash-all.bat. It is in the zip file and will get flashed by "fastboot update"
Deleted, because xda
best regards
mathsz said:
thank you for that useful information
:good:
and when the zip file flash doesn't work, we go back to message #1.
Click to expand...
Click to collapse
Message #1 wasn't about the zip file not working. It was about using a script to flash each section separately but forgetting to include vendor.img
fail to flash system.img
[SOLVED (can be ignored)]
I've got the exact same problem you have, however when I followed the code you posted, for some reason the system.img fails to flash
Code:
target didn't report max-download-size
error cannot load 'system.img'
I also noticed the normal FlashAll.bat sends the system in 4 packets, while the custom code I believe tries to do it all at once. Did you run into this problem? All the other things (radio, bootloader, etc) report the max-download-size without an issue
CAUSE: I was running the code in message #1
SOLUTION: run the code in message #5
I ran the code that
It Worked for me.
Thanks for your efforts.:good:
My Nexus 5x just Resurrected.
In my case, after rooting I have installed ex kernel and set up threshold as 90. Then now stable device status keep going.
Can anyone pls tell me where I can download stock rom for (lenovo) p2 preferable in zip format . And is there any unbricking tutorial .
I want this too...? if anyone can help...
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Then share it no
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
aleleo87 said:
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
Click to expand...
Click to collapse
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
itsjustbilly said:
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
Click to expand...
Click to collapse
Ah ok i didnt understand that you have this modem issue. I don't kno how to help you...you phone is bricked so you can test few solutions without more risks .
before flash the original recovery , boot and system by fastboot, you can try to install TWRP again and flash only the bootloader from TWRP (should support .zip and .img files). Then you turn the phone in fastboot mode and flash other stuff .
Taken from post 4 of the TWRP page on lenovo P2 forum
smaranramesh said:
Then share it no
Click to expand...
Click to collapse
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
itsjustbilly said:
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Click to expand...
Click to collapse
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
veimus said:
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
Click to expand...
Click to collapse
Witaj. Mozesz napisać jak wgrałeś czysty soft do Lenovo p2. Tez mam rom z t.mobile a nigdzie nie ma poradnika jak wgrać czysty soft.Pozdrawiam
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
Is there an alternative download link? What is Mega? I want to avoid these third party download utility if I can...
I put the following into a BAT file and placed it into ADB / Fastboot directory:
Code:
fastboot flash partition gpt_both0.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
pause
Extract all the files listed in the BAT file or simply extract the entire archive to ADB / Fastboot and launch the BAT file.
Does this work?? @Undesirable
the above post
Oh yeah, it unbricked me and put me back to stock so I could get OTA updates for Nougat. You need the archive posted earlier in the thread though.
@Undesirable Nice and elegant solution man! Typing all this stuff was so annoying.
For those who need an alternative download source, I offer this magnet link:
Code:
magnet:?xt=urn:btih:ef05ea3af4da8a0cbb137c10621942f3ae16d46f&dn=P2a42_S048_161111_ROW_fastboot.7z
It's slow unless lots of people help to seed it.
Is it possible to flash this firmware 2a42_S048_161111_ROW_fastboot.7z on the P2c72 with firmware build number: V3.5_1652_5.1342.1_ST_p2c72 ???
I bought this phone 4GB Ram/64GB from china, but I want to put the international firmware on it.
Thanks!
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
how can I replace my data partition? It's not getting formatted due to an encryption error
If fastboot erase userdata doesn't work, then use TWRP to change user data file system to EXT4 then change it back to F2FS again.
Need help...
I flashed back the stock ROM (due to encryption error in custom 7.0 ROM) using fastboot commands, but my SIGNAL WON'T WORK after I started d phone . I've tried reflashing the stock firmware (and also custom ROMs) but my phone won't detect the signal. "About phone" settings show unknown baseband and IMEI... how to get it back
---------- Post added at 08:58 AM ---------- Previous post was at 08:06 AM ----------
I've flashed 'ROW' variant of stock ROM. Is there a different version for Indian variant?
After moving my Mi6 from EU ROM to Global Stable 8.2.2.0, I realised that MIUI has now programmed either the boot.img or system.img to overwrite recovery partition on every "normal"/system boot.
So much for unlocking the bootloader...
Although the source system.img has a recovery-from-boot.p file, but it appears to be different from the stock recovery.img file. Attempting to replace it with the TWRP image or removing it entirely (and flashing the rebuilt system.img) results in boot failure (see below for more information).
Does anyone know:
where the "protected" recovery image may be found? and/or
how to repack/rebuild a system.img which will not cause a boot hang?
Note that I have rebuilt it "correctly" (as "correct" as I know) using the properly extracted file_contexts (as extracted from the file_contexts.bin) from the initrd.img from inside the boot.img using the command:
Code:
make_ext4fs -s -T -1 -S file_contents -L system -l <size of partition> -a system system.img <mount point>
I have tried both a blind fastboot flash system system.img, and also a standard "clean" flash using the MiFlash tool (after ensuring that the correct MD5, CRC and sparse CRC strings are edited in the various files, of course).
Thanks!
fastboot flash recovery TWRP.img
That's the solution.
And if you flash a MIUI rom with TWRP simply flash twrp.img without Reboot under TWRP, after rom.zip flash. That's all
reb00tz said:
After moving my Mi6 from EU ROM to Global Stable 8.2.2.0, I realised that MIUI has now programmed either the boot.img or system.img to overwrite recovery partition on every "normal"/system boot.
Click to expand...
Click to collapse
dennis46419 said:
fastboot flash recovery TWRP.img
That's the solution.
And if you flash a MIUI rom with TWRP simply flash twrp.img without Reboot under TWRP, after rom.zip flash. That's all
Click to expand...
Click to collapse
Hi @dennis46419,
Thanks for replying. I have always done that upon forced reboot by the MiFlash tool (i.e. the moment it powers off for a reboot, I put it right back into fastboot mode to flash TWRP again, then directly boot with the TWRP.img).
As mentioned, I believe the new global stable ROM actually overwrites recovery on every boot.
Have you experienced this (i.e. when using the global stable ROM)?
OK, seems I missed the solution as already provided by @TheStrix:
https://forum.xda-developers.com/showpost.php?p=72620133&postcount=2
But the instruction (which I missed because I downloaded directly from the TWRP site) was already here: https://forum.xda-developers.com/showpost.php?p=72620133&postcount=2