As the title states...can we flash just the bootloader from 25R onto 30O using fastboot? And if so, therefore allow for the temporary boot of a custom recovery. Until now, I've only owned/flashed Samsung devices so still learning the fastboot idioms. Any ideas or nah?
You can boot a recovery without flash it .. fastboot boot recovery.img
Why are you wanting to downgrade a bootloader to 25R? There aren't any restrictions.
If you want to temporarily boot a recovery, then just type what nneves said.
Theres no need to downgrade your bootloader.
Since the firmware has been updated to 30O, this cannot be done. I used the 'boot recovery' method while on 25R, but for some reason (security?) they have blocked that exploit, hence the question at hand.
I had even tried this method I found in a Nexus forum:
Here's some instructions I compiled for doing useful things with your Nexus. Also includes instruction to root nexus 4 without installing a custom recovery. Basically, you save the customrecovery.zip file then fastboot boot into it (NOT install, and notice you have to type the full command specified below, not just "fastboot boot customrecovery.img") and then install using the custom recovery, install SuperSU.zip for unrooting:
1) Install all STOCK files:
./fastboot flash bootloader bootloader-XXX.img ./fastboot reboot-bootloader ./fastboot flash radio radio-XXX-XXX.img ./fastboot reboot-bootloader ./fastboot -w update image-XXX-XXX.zip ./fastboot oem unlock (to unlock bootloader)
2) If you want to keep stock recovery, fast boot BOOT into custom recovery and install SuperSu.zip: 3) Install SuperSu.zip file (to root)
./fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
there used to be a 'fastboot boot recovery recovery.img' command, but Google removed it in 4.3, so now to simply boot into your custom recovery you can type 'fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img' instead and it'll do the same thing as the 'fastboot boot' command. Meaning it will revert to your stock recovery once you reboot. So boot into custom recovery, flash superuser (Koush or Chainfire's) and reboot. done.
It didn't work but maybe another code for our device is needed?
Just going to give this a little bump...
there is a stock 25R ROM zip floating around here somewhere. you should just be able to flash it via recovery using twrp, if you're just wanting to go back to flat stock. let me know if you can't find it, i think i may have it somewhere.
Wouldn't you need to unlock the bootloader to downgrade to 25R? I think that there would be some sort of check in the signed 25R OTA update that would prevent you from flashing it.
Hi, my son's oneplus one mobile will not start up. When we press the "on" button, we see the first "1+ powered by android" screen, then the word "cyanogen" is written across the screen. This word continues to slowly blur and un-blur slightly, but the system never comes any further. (The phone is fully charged).
We can also boot to a "cyanogen recovery" screen, where there are several options - where I guess a "factory reset" could be worth a try. If we do a factory reset, is there any way to maintain installed apps, and especially "progress" in these apps?
Thanks for any help,
Peter
You could try to use adb to backup the data, but you wont be able to save the progress in the apps I think, some apps have their progress stored online with your google account(Clash of clans for example)
ok, thanks (I don't know what "adb" is, but I'll google it).
Otherwise, has anyone seen this startup problem before, and are there any good solutions?
Thanks.
Hmm, seems that "adb" requires installation and/or enabling on the phone - as I can't start the phone, I don't think I can use this unfortunately.
You don't have access to adb unless it was previously enabled. Can you shed some light on what caused this situation please? It makes it a lot easier to troubleshoot. Do you know what build of Cyanogen OS was installed on the phone before this happened?
Hi, thanks for the reply. The phone's battery run out and the phone shut down. The power supply was attached, and it was attempted to turn the phone on - but this resulted in the current state where the phone stops at the "cyanogen" screen. The phone has since been charged over night, but will still not start. As to the current OS version - we are unfortunately not sure. My son says he last performed an OS update a few weeks ago.
xdzgor said:
Hi, thanks for the reply. The phone's battery run out and the phone shut down. The power supply was attached, and it was attempted to turn the phone on - but this resulted in the current state where the phone stops at the "cyanogen" screen. The phone has since been charged over night, but will still not start. As to the current OS version - we are unfortunately not sure. My son says he last performed an OS update a few weeks ago.
Click to expand...
Click to collapse
Ok, thanks. If you can get into the stock recovery you should try flashing the latest build from here, then reboot the phone.
Thanks for the suggestion - but what do you mean with "stock recovery"? We can get to a menu with these options:
reboot system now
apply update
wipe data/factory reset
wipe cache partition
wipe media
reboot to bootloader
power down
view recovery logs
Can we use one of these to upload a new OS to the phone?
"Apply update" gives the options:
apply from ADB (does this mean adb *is* running on the phone?)
choose from internal storage
"Reboot to bootloader" results in a screen where it says "fastboot mode", but gets no further than this screen.
xdzgor said:
Thanks for the suggestion - but what do you mean with "stock recovery"? We can get to a menu with these options:
reboot system now
apply update
wipe data/factory reset
wipe cache partition
wipe media
reboot to bootloader
power down
view recovery logs
Can we use one of these to upload a new OS to the phone?
"Apply update" gives the options:
apply from ADB (does this mean adb *is* running on the phone?)
choose from internal storage
"Reboot to bootloader" results in a screen where it says "fastboot mode", but gets no further than this screen.
Click to expand...
Click to collapse
That's the stock recovery. The "apply from adb' option is present whether you have adb enabled or not, so that's a no-go. I've just realised that you won't be able to use the recovery to flash the zip anyway, because there's no way to transfer the zip to the device without adb.. I think your only option will be to unlock the bootloader and flash the stock images with fastboot. Unfortunately this will erase all data on the phone, but right now you don't really have any other option. So what you'll need to do is this:
1. Install adb/fastboot onto your PC, the 15 seconds adb installer is probably the easiest option for this.
2. Use the reboot to bootloader option in recovery to put the phone in fastboot mode.
3. Navigate to where adb.exe and fastboot.exe are located on your PC, hold shift and right-click, then select open command prompt here.
4. Make sure your phone is connected to the PC via usb cable and (in the terminal window that popped up after the previous step) issue this command:
Code:
fastboot devices
It should return the serial number of the device, if it does you have a working fastboot connection. If it doesn't return the serial number you might have to play around with drivers.
5. Once you know you've confirmed that you have a working fastboot connection you can check the status of the bootloader with this command:
Code:
fastboot oem device-info
There will be a few lines of text. One of the lines will be 'bootloader unlocked: true/false". If it says true you can move on to step 6, if it says false you will need to unlock it with step 5a.
5a. Unlock the bootloader with this command:
Code:
fastboot oem unlock
The phone will automatically go through the unlock process, and will probably try to boot into the OS. Get back into fastboot mode by using the option in recovery, or by shutting the device off by holding the power button and then using the fastboot mode button combo (hold power + volume up).
6. Once you know you have an unlocked bootloader you can now flash the stock images to the device:
-Download the latest stock images to your PC from here. If you don't want the latest build you can find all stock images mirrored here thanks to @Spannaa.
-Unzip the file you downloaded and put its contents into your fastboot folder (the same folder that you have adb.exe and fastboot.exe located in on your PC).
-Open a command prompt from within your adb/fastboot folder (shift + right click, select open command prompt here).
-Issue these fastboot commands:
Code:
fastboot flash modem NON-HLOS.bin
Code:
fastboot flash sbl1 sbl1.mbn
Code:
fastboot flash dbi sdi.mbn
Code:
fastboot flash aboot emmc_appsboot.mbn
Code:
fastboot flash rpm rpm.mbn
Code:
fastboot flash tz tz.mbn
Code:
fastboot flash LOGO logo.bin
Code:
fastboot flash oppostanvbk static_nvbk.bin
Code:
fastboot flash boot boot.img
Code:
fastboot flash cache cache.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata_64G.img
or fastboot flash userdata userdata.img if you have the 16gb model)
Please note: flashing the userdata will wipe your internal storage (your virtual sd card). It's possible to flash these images without that command if a full wipe isn't completely necessary in your situation.
-Reboot your device with this command:
Code:
fastboot reboot
-It's now safe to disconnect your usb cable.
Click to expand...
Click to collapse
Hopefully the phone will boot up now.
Thanks heaps for the info. My son has now re-established his telephone - though he lost all his data/progress/photos etc.. Is there a recommended backup mechanism for the OnePlus One? (Maybe he can run a backup application on his PC once a week which takes a snapshot of his phone?)
xdzgor said:
Thanks heaps for the info. My son has now re-established his telephone - though he lost all his data/progress/photos etc.. Is there a recommended backup mechanism for the OnePlus One? (Maybe he can run a backup application on his PC once a week which takes a snapshot of his phone?)
Click to expand...
Click to collapse
The best way is by creating a backup with TWRP recovery. You'll find instructions on how to flash it (and how to make a backup) in my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
It's very, very, unfortunate that this happened so early in the life of my new Pixel 2. Here's what I did:
fastboot oem unlock
Device erases and boots normally, power off and boot into bootloader using volume and power.
Flash Android 8.1 beta using flash-all.bat
<Device is stuck in bootloader>
Flash factory Android 8.0 image, same thing
Try "fastboot --set-active=a" followed by "fastboot continue" and "fastboot --set-active b" followed by "fastboot continue", neither worked.
Try entering recovery or download mode from bootloader, neither worked.
I contacted Google support, and they didn't have any suggestions other than an RMA, so a new device should be on the way soon. Given the comments in this thread about using the wrong version of fastboot, I'll point out that I do have the latest version of platform-tools, and my fastboot version is:
Code:
C:\>fastboot --version
fastboot version 3db08f2c6889-android
Installed as C:\android-platform-tools\fastboot.exe
Anyone else have this experience? (I hope not.)
Edit: Okay, thanks to this post, I learned that I flash-all.bat, which uses "fastboot -w update image-*.zip", leads to this condition. However, flashing each img file in the zip archive individually gets the device back to health. Phew.
can you share the .bat file please?
I didn't use a bat script to recover the device, I typed each "fastboot flash <partition> <partition>.img" command by hand. Not the most efficient, but I wasn't expecting to do this more than once.
It's possible you had a bad download, did you attempt to redownload the stock image?
Hello everyone,
this is about the Nexus 5 16gb.
It has been completely erased and no backup has been done by the previous owner :silly: and he asked for help. I am a complete noob myself and could only do the below listed things thanks to this forum.
It was completely empty when I received it (as far as I can tell), but I can access the bootloader. I put a costum recovery on it with the help of this forum. When in costum recovery mode my computer identifies it as the Nexus 5 with the help of the Google Drivers and the SDK-Android (I presume) I installed previously.
I went to Google and was able to put a factory image on it from their collection of "hammerhead" for Nexus 5 (GSM/LTE).
I tried the 6.0.1 (MOB31E) and installed it via the flash-all.bat via CMD since this version was, according to the owner, installed before. It worked, as far as I could tell - data got copied on the phone.
When I restart the phone, the Google Logo with an opened lock blinks very slowly. The swirly loading screen I have seen on some Youtube videos for this model's OS does not appear. I presume that the phone does not recognize the flashed factory image?
My question is:
Do I need to try all of the factory images from Google until one works? Or is something so fundamentally lost (maybe somewhere in the booting process), that the phone cannot be repaired since the swirly loading screen does not appear?
Do I need to copy something else on the phone besides the factory image for it to start the booting process for the OS that I have installed via the flash-all.bat?
I am very lost - if someone could point me toward the right direction or even just toward the right kind of tutorial, I'd be very grateful.
You can flash the factory image using the following fastboot commands (subtitute file names to match the file names from the unzipped factory image):
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?
well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this
ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing
If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.