Hi, tried to install a 4.4 ROM but it failed and then went downhill. Does anyone have the latest image file for the bootloader? Now I am soft bricked trying to go back to stock but all I can find are the old bootloaders and they do not work with the kitkat image file from google. Thanks for the help!
http://forum.xda-developers.com/showthread.php?t=2383146
See post#2
I flashed it from recovery.
hyperxguy said:
http://forum.xda-developers.com/showthread.php?t=2383146
See post#2
I flashed it from recovery.
Click to expand...
Click to collapse
Hi, thanks for that but I already have it. The thing is it's a .zip i need the .img and inside that zip there are multiple files i don't exactly know which one is the bootloader.
Thanks!
th3xeroeagle said:
Hi, tried to install a 4.4 ROM but it failed and then went downhill. Does anyone have the latest image file for the bootloader? Now I am soft bricked trying to go back to stock but all I can find are the old bootloaders and they do not work with the kitkat image file from google. Thanks for the help!
Click to expand...
Click to collapse
You can find many of the kernels/recoveries/bootloaders in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2534698
The problem is it might not get you to where you want to be.
What exactly are you calling a "brick"?
If you have a bootloader issue, you won't even see the Google during boot. It is rare to be bricked in that way.
You are probably stuck on the X or bouncing balls animation.
You can get out of that by going to recovery and performing wipe data factory reset.
If you are stuck at "Google", then you need to reflash the factory image (you can choose the nowipe option and possibly keep your user data)
sfhub said:
You can find many of the kernels/recoveries/bootloaders in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2534698
The problem is it might not get you to where you want to be.
What exactly are you calling a "brick"?
If you have a bootloader issue, you won't even see the Google during boot. It is rare to be bricked in that way.
You are probably stuck on the X or bouncing balls animation.
You can get out of that by going to recovery and performing wipe data factory reset.
If you are stuck at "Google", then you need to reflash the factory image (you can choose the nowipe option and possibly keep your user data)
Click to expand...
Click to collapse
hey, thanks for the reply. I'm trying to get my tablet to kitkat with the stock image from google. but I hear that with kitkat there is a new bootloader so I want to update that through fastboot (my device is recognized so I call it a soft boot) but the problem is when I erase the boot and reflash the boot.img and try to flash the new .img it doesn't load up. im using these commands
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash boot
fastboot flash recovery
fastboot flash system
fastboot reboot-bootloader
my current bootloader version says FLO 4.01 not sure how to update it.
th3xeroeagle said:
hey, thanks for the reply. I'm trying to get my tablet to kitkat with the stock image from google. but I hear that with kitkat there is a new bootloader so I want to update that through fastboot (my device is recognized so I call it a soft boot) but the problem is when I erase the boot and reflash the boot.img and try to flash the new .img it doesn't load up. im using these commands
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash boot
fastboot flash recovery
fastboot flash system
fastboot reboot-bootloader
my current bootloader version says FLO 4.01 not sure how to update it.
Click to expand...
Click to collapse
4.01 is the bootloader that came with kitkat.
you can't just say
fastboot flash boot
you need to say
fastboot flash boot boot.img
and have the boot.img in place.
I suggest you just follow the instructions in this post:
http://forum.xda-developers.com/showthread.php?p=47640458#post47640458
Use the nowipe option and you should be able to keep your user data unless you erased or messed it up earlier.
sfhub said:
4.01 is the bootloader that came with kitkat.
you can't just say
fastboot flash boot
you need to say
fastboot flash boot boot.img
and have the boot.img in place.
I suggest you just follow the instructions in this post:
http://forum.xda-developers.com/showthread.php?p=47640458#post47640458
Use the nowipe option and you should be able to keep your user data unless you erased or messed it up earlier.
Click to expand...
Click to collapse
AH! It was in the general section, I looked everywhere in the development sections. Thank you very much!
hi
i have ordroid 15 on my htc one x
i need to flash a new rom (with new android)
and how i flash it????
volio said:
hi
i have ordroid 15 on my htc one x
i need to flash a new rom (with new android)
and how i flash it????
Click to expand...
Click to collapse
%i'm not responsible for any harm%
Just backup the rom trough a custom recovery, backup userdata on the pc.
download the new rom (zip) and place it on your phone, unpack the boot.img on your pc,
go in to bootloader (fastboot), and check if you can connect to it using the fastboot toolchain. (fastboot devices)
only if the commandline returns your device, continue
go in your custom recovery, and wipe system, data and cache.
then install the zip with the new rom.
then return to the bootloader, and flash the unpacked boot image by running the command: fastboot flash boot boot.img(path to your boot.img)
good luck
Hello fellows.
I have some problems with my find 7a, which have been a stable friend the past 2 years. I updated to the latest ColorOS yesterday, 2.1.5i. I started rooting my phone using the OPPO tool in the forums, and it worked fine. I then experienced the "insufficient space" problem and solved that by changing the partition method in developer options. This is where everything went nuts. All programs does of cause not work anymore because of the partition change, but I am no longer able to boot in to recovery, only fastboot, no matter if i power + up / down. I can no longer roll back or update to a newer ROM, and everything is gone on my SD and internal storage besides the absolute needed files to ColorOS 2.1.5i, but very slow. I have tried everything which I can think of: installing stock ROM and recovery, new ROM and recovery. No matter how I try to recover, nothing works. Now I just have a slow find 7a.
What can I do?
Best Regards
Devial
I have fixed this problem myself with some research.
Install stock ColorOS 1.2.7i recovery using adb/fastboot:
Code:
fastboot flash boot boot.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash LOGO logo.bin
fastboot flash reserve4 reserve4.img
Thanks to darrenpauli.
I was now able to boot in to the stock recovery, but still had problems with installing any ROM, any custom or stock ROM.
I then rebooted into fastboot again, to see the "smiley" thing is gone, and the only thing on the screen was "Fastboot..." - progress!
So far I haven't been able to install any custom ROM or recovery, but this time I was able to install GUMMY TWRP 2.7.1.0 using the recovery installer for oppo find 7. I was now past the "failed" in fastboot/adb.
Since i completely wiped the phone, I no longer had any ROM installed, but I was now able to install the newest rom from CM using TWRP.
My phone is now rocking with the newest CM!
Software used.
Recovory_installer from OPPO
AndroidSDKSlim
ColorOS 1.2.7i
Newest CM
Wanted to just stay on the stock releases. Is there an easy way to flash them without wiping storage? I'm used to flashing everything in recovery, not used to getting stuff straight from Google.
jackdubl said:
Wanted to just stay on the stock releases. Is there an easy way to flash them without wiping storage? I'm used to flashing everything in recovery, not used to getting stuff straight from Google.
Click to expand...
Click to collapse
You can follow this guide for the original N5: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Follow method 2 but make sure you SKIP this step:
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
Click to expand...
Click to collapse
Flashing userdata.img overwrites your personal data and writes the stock one. Also, don't "Wipe data/factory data reset"
Should do the trick Also, be aware that flashing the boot.img and recovery.img will break root and flash the stock recovery. You'll have to manually flash a custom recovery and re-root :good:
zepeters said:
You can follow this guide for the original N5: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Follow method 2 but make sure you SKIP this step:
Flashing userdata.img overwrites your personal data and writes the stock one. Also, don't "Wipe data/factory data reset"
Should do the trick Also, be aware that flashing the boot.img and recovery.img will break root and flash the stock recovery. You'll have to manually flash a custom recovery and re-root :good:
Click to expand...
Click to collapse
If you already have root and twrp can you skip flashing the boot and recovery img?
Sent from my Nexus 5X using XDA Free mobile app
kbbeer said:
If you already have root and twrp can you skip flashing the boot and recovery img?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Not sure about that, I'd have to test it first. But I think twrp is version specific, so instead of flashing the stock recovery you can just flash the correct twrp version for the android version you're upgrading to. As for the boot.img, since rooting in marshmallow involves messing with the boot.img itself, I don't think it will work.
Again, this is me thinking out loud. I'd have to test it in order to give you a certain answer on this.
zepeters said:
You can follow this guide for the original N5: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Follow method 2 but make sure you SKIP this step:
Flashing userdata.img overwrites your personal data and writes the stock one. Also, don't "Wipe data/factory data reset"
Should do the trick Also, be aware that flashing the boot.img and recovery.img will break root and flash the stock recovery. You'll have to manually flash a custom recovery and re-root :good:
Click to expand...
Click to collapse
Basically this I believe. Make sure to flash vendor.img too though, or you will get some errors on boot. And ensure the rooted boot.img is compatible with the latest Nexus image via Chainfire's thread. So assuming it is, and recovery is as well:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
Tried with the latest Nexus image, and all seems well. Cheers
Edit: Don't forget to re-flash SuperSU in twrp if you are not using the systemless root
itzweber said:
Basically this I believe. Make sure to flash vendor.img too though, or you will get some errors on boot. And ensure the rooted boot.img is compatible with the latest Nexus image via Chainfire's thread. So assuming it is, and recovery is as well:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
Tried with the latest Nexus image, and all seems well. Cheers
Edit: Don't forget to re-flash SuperSU in twrp if you are not using the systemless root
Click to expand...
Click to collapse
Cool, so just flash those three, then I'm guessing reboot ensure everything is working and reboot to recovery and flash supersu again.
itzweber said:
Basically this I believe. Make sure to flash vendor.img too though, or you will get some errors on boot. And ensure the rooted boot.img is compatible with the latest Nexus image via Chainfire's thread. So assuming it is, and recovery is as well:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
Tried with the latest Nexus image, and all seems well. Cheers
Edit: Don't forget to re-flash SuperSU in twrp if you are not using the systemless root
Click to expand...
Click to collapse
What exactly is vendor.img? I don't think I ever flashed this file... not it is present in the factory images
EDIT: I've seen it in some flashing guides but it was only related to tablets somehow...
vendor.img is new in 6.0 i believe that contain vendor proprietary info.
you also don't need to flash cache.img either (i never do and it have yet to experience any problems).
So assuming the boot.img, radio.img, and recovery.img is still compatible with the newer version...all you must flash is system.img and vendor.img, SuperSU.zip, wipe cache/dalvic in TWRP when upgrading these minor updates. Making a custom zip to do this in TWRP would be the easiest way.
Everything seems to be working! Here is what I did to summarize -
I was on MDB08I and had twrp and root working properly. I downloaded the factory images for MDB08L and MDB08M, extracted until I had the img files.
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
wipe cache/dalvic in TWRP
rebooted
flashed SuperSu in recovery
Done!
Did this first for L then repeated for M.
Followed those steps except flashing Superuser, (I use systemless) data, root, and Elemental kernel are still in tact.
Sent from my Nexus 5X
kbbeer said:
Everything seems to be working! Here is what I did to summarize -
I was on MDB08I and had twrp and root working properly. I downloaded the factory images for MDB08L and MDB08M, extracted until I had the img files.
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
wipe cache/dalvic in TWRP
rebooted
flashed SuperSu in recovery
Done!
Did this first for L then repeated for M.
Click to expand...
Click to collapse
Why did you do this for L and then for M? I am currently on MDB08I and was planning to flash system.img and vendor.img for M, skipping L. Then flash Supersu in TWRP. Would this work for me to be on the newest update and keep root?
neuroval said:
Why did you do this for L and then for M? I am currently on MDB08I and was planning to flash system.img and vendor.img for M, skipping L. Then flash Supersu in TWRP. Would this work for me to be on the newest update and keep root?
Click to expand...
Click to collapse
I was on "I" and flashed the .imgs for M and everything went well so it should work for you.
Sent from my Nexus 5X
neuroval said:
Why did you do this for L and then for M? I am currently on MDB08I and was planning to flash system.img and vendor.img for M, skipping L. Then flash Supersu in TWRP. Would this work for me to be on the newest update and keep root?
Click to expand...
Click to collapse
Another thread mentioned doing it in order so I was just being cautious. In reality only takes 5 more minutes to flash both. System didn't go through refreshing all apps after the L security update.
i followed the steps above as well but went straight from i to m. everything works fine
Just went from I to M and everything seems to be working
Do we have to reflash modified boot image with this method?
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
Do we have to reflash modified boot image with this method?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
I didnt.
Sent from my SM-G920F
dave2775 said:
Do we have to reflash modified boot image with this method?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Same here, only reflashed the original modified i img. During the first root.
kbbeer said:
Everything seems to be working! Here is what I did to summarize -
I was on MDB08I and had twrp and root working properly. I downloaded the factory images for MDB08L and MDB08M, extracted until I had the img files.
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
wipe cache/dalvic in TWRP
rebooted
flashed SuperSu in recovery
Done!
Did this first for L then repeated for M.
Click to expand...
Click to collapse
Did this straight from I to M and worked a treat, thanks!
How does one get back to stock recovery for the Mate SE BND-L34?
My phone is rooted with TWRP/Magisk but would like to try AOSP to see if it will fix my issues but AOSP says it won't work with twrp. Thanks
teatimecrumpet said:
How does one get back to stock recovery for the Mate SE BND-L34?
My phone is rooted with TWRP/Magisk but would like to try AOSP to see if it will fix my issues but AOSP says it won't work with twrp. Thanks
Click to expand...
Click to collapse
ASOP will work with both TWRP and Magisk. The install is different as you flash just a system image from fastboot instead of through TWRP. The only other issue that I know of is with a factory reset/wipe which is needed when installing a GSI like most of the ASOP stuff. If you do a factory wipe through TWRP, you will brick your device. The factory wipe has to be done through the stock recovery. Basically, download the firmware for your phone and extract either 'recovery' or 'recovery_ramdisk' depending on if you are on Oreo or Pie. Flash that file through fastboot "fastboot flash (name of reovery partition on your device) (name of recovery file in the fast boot folder) for mine it looks like this "fastboot flash recovery recovery.img"
You will have to reinstall magisk after you install your choosen GSI