So guys basically, I wanted to give F2FS a shot, I downloaded the recoveries that the thread told me to, flashed either of them using the fastboot flash boot filename.img
With both of them, and even the latest official TWRP I get this:
sending 'boot' (8182 KB)... OKAY [ 1.056s]
writing 'boot'... OKAY [ 0.182s]
finished. total time: 1.238s
and on my Bootloader screen I get the message FASTBOOT STATUS OKAY
So, you'd think all went fine.
Rebooting into recovery reveals that I have the exact same recovery as before, I've tried like 10 times and the result is always the same one
Are you sure the one you flashed is different to the previous one? Which recovery do you have now and which do you want to flash?
XxM4tzexX said:
Are you sure the one you flashed is different to the previous one? Which recovery do you have now and which do you want to flash?
Click to expand...
Click to collapse
I have TWRP 2.7.0.1 and I'm trying to flash either KT recovery or the latest TWRP 2.7.1.0, I'll try flashing CWM and then change back to one of those to see if I can manage to do that
fastboot boot filename.img worked and I managed to change my filesystems, I'll try creating the zip as the recovery keeps going reverting and 2.7.0.1 isn't able to read my partitions now, I'll update with the results and so far I just booted up and everything seems to be going well.
Edit: Ok, I DL'ed an official TWRP 2.7.1.0 zip and flashed it, my recovery updated successfully, however it isn't able to read my /cache or /data partitions, next, I replaced the recovery.img with the exact same img I used to convert to F2FS (the one provided here) and again booted into the functional recovery through fastboot boot filename.img, I flashed the new zip file and everything seemed to be fine, rebooting to recovery shows that the original TWRP 2.7.1.0 wasn't replaced as I'm unable to mount the data or cache partitions.
Also worth mentioning that using the TWRP manager from the playstore to try to flash .imgs does not work either
The fastboot method listed above is to flash a kernel not recovery, if your trying to flash a new recovery you run
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Fidelator said:
So guys basically, I wanted to give F2FS a shot, I downloaded the recoveries that the thread told me to, flashed either of them using the fastboot flash boot filename.img
Click to expand...
Click to collapse
fastboot flash recovery filename.img
uDude
Related
Hello guys, i've been trying to install a custom recovery on my Nexus 4 but it has been unsuccessful all the time.
The problem is just that I can't get to boot into the custom recovery, When i flash or temporarily boot a custom recovery with fast boot (fastboot flash recovery.IMG or fastboot boot recovery.IMG) it goes without any errors, but the problem comes when its time boot into the recovery, it just stays frozen at the Google screen and then i have to do a battery pull to get out of there.
I hope you can help me guys because i cant even root my phone without a custom recovery. Ive tried rooting using the Nexus roottoolkit but it doesnt work... Apparently my phone also cant boot a custom boot.img because it also stays frozen at the google screen. My phone is unlocked...
Thanks!:laugh:
Guillermo095 said:
Hello guys, i've been trying to install a custom recovery on my Nexus 4 but it has been unsuccessful all the time.
The problem is just that I can't get to boot into the custom recovery, When i flash or temporarily boot a custom recovery with fast boot (fastboot flash recovery.IMG or fastboot boot recovery.IMG) it goes without any errors, but the problem comes when its time boot into the recovery, it just stays frozen at the Google screen and then i have to do a battery pull to get out of there.
I hope you can help me guys because i cant even root my phone without a custom recovery. Ive tried rooting using the Nexus roottoolkit but it doesnt work... Apparently my phone also cant boot a custom boot.img because it also stays frozen at the google screen. My phone is unlocked...
Thanks!:laugh:
Click to expand...
Click to collapse
fastboot flash recovery recoveryname.img not fastboot flash recoveryname.img. you have to tell it which partition it goes into.
simms22 said:
fastboot flash recovery recoveryname.img not fastboot flash recoveryname.img. you have to tell it which partition it goes into.
Click to expand...
Click to collapse
OK. I just tried that and still nothing it hangs up on the Google screen... But that can't be the problem because booting it temporarily would have worked anyways...
fastboot oem unlock
Guillermo095 said:
OK. I just tried that and still nothing it hangs up on the Google screen... But that can't be the problem because booting it temporarily would have worked anyways...
Click to expand...
Click to collapse
try it 2 or 3 times in a row
fastboot oem unlock
Sent from my Nexus 4 using xda premium
androidtoy09 said:
fastboot oem unlock
Click to expand...
Click to collapse
this, if you havent done it yet.
simms22 said:
this, if you havent done it yet.
Click to expand...
Click to collapse
It says failed because i´m already unlocked, and also tried flashing multiple times but it still stays at the google screen...
Are you getting the boot loader screen? You should see the word start in green letters at the top.
If so then you may be flashing the wrong recovery.
If you have the right one try flashing the bootloader
Sent from my Nexus 4 using xda premium
kthejoker20 said:
Are you getting the boot loader screen? You should see the word start in green letters at the top.
If so then you may be flashing the wrong recovery.
If you have the right one try flashing the bootloader
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes, the bootloader works perfectly... I´m flashing the recovery through there... I don´t think I have the wrong recovery, I downloaded it from clockworkmod.com/rommanager and I have the latest Jelly Bean 4.2.2
Guillermo095 said:
Yes, the bootloader works perfectly... I´m flashing the recovery through there... I don´t think I have the wrong recovery, I downloaded it from clockworkmod.com/rommanager and I have the latest Jelly Bean 4.2.2
Click to expand...
Click to collapse
Could you try another custom recovery like TWRP. Might be an incomplete or corrupted download as well (Check md5sum before flashing).
I would download it directly from clockworkmod. Google it.
The make sure you put it in the same folder that your fast boot is in. Rename the file to recovery.img
Then at boot loader type fastboot flash recovery recovery.img
Sent from my Nexus 4 using xda premium
I tried both of your solutions but still nothing, I really don't understand why it doesn't allow custom recoveries :S
Guillermo095 said:
I tried both of your solutions but still nothing, I really don't understand why it doesn't allow custom recoveries :S
Click to expand...
Click to collapse
Make sure your SDK/ADB is up to date. Older versions have issues with flashing files to the Nexus 4 that can cause your phone to get stuck at boot. If your N4 isn't booting at all, you might want to reflash the entire stock software using the download from Google's Nexus build page, after you've updated your SDK/ADB suite, just to make sure your partition tables haven't gotten messed up.
you could try downloadong the stock rom from google then flashall file.
then try to install the custom recovery after it reset
Sent from my Nexus 4 using xda premium
Guillermo095 said:
I tried both of your solutions but still nothing, I really don't understand why it doesn't allow custom recoveries :S
Click to expand...
Click to collapse
hello,
I have exactly the same problem .... what finally made?
My device now is Rooted with superSU but with no custom recovery.
I return to stock recovery (after downloading the stock rom and flash only the recovery)
bbsnick said:
hello,
I have exactly the same problem .... what finally made?
My device now is Rooted with superSU but with no custom recovery.
I return to stock recovery (after downloading the stock rom and flash only the recovery)
Click to expand...
Click to collapse
I have same problem, when i install custom recovery it goes as follows(completes without error)
boot flash recovery recovery-clockwork-touch-6.0.3.1-mako.img
sending 'recovery' (7560 KB)...
OKAY [ 0.475s]
writing 'recovery'...
OKAY [ 0.402s]
finished. total time: 0.877s
but when I try to go into custom recovery, it shoes android bot icon with back open and exclamation mark.
Then when i ran
boot boot recovery-clockwork-touch-6.0.3.1-mako.img
downloading 'boot.img'...
OKAY [ 0.475s]
booting...
OKAY [ 0.021s]
finished. total time: 0.498s
It booted into custom recovery, but custom recovery was never installed. Any help?
1. Rename CWM to recovery.img (not recovery.img.img)
2. fastboot flash recovery recovery.img
3. fastboot reboot-bootloader
4. Done
EddyOS said:
1. Rename CWM to recovery.img (not recovery.img.img)
2. fastboot flash recovery recovery.img
3. fastboot reboot-bootloader
4. Done
Click to expand...
Click to collapse
It worked, thanks
I used the WonderHowTo site incorrectly to flash a nexus 5 version of twrp unto my nexus 4.
My device at this point booted to a blank screen. It could still boot the boot loader at this point.
To "fix" this I found the correct version of twrp for my device and proceeded to flash that unto my device.
This has appeared to work since I can access twrp on my device but it is only thing I can access on the phone. When I attempt to boot to system through twrp I am sent back into twrp.
I have attempted to use the wugfresh root tool kit to unroot and return to stock using both soft bricked and phone is still working normally options with no success.
It can still boot to the boot loader currently.
I have logs from the toolkit if these can shed more light on my issue.
Is there anyway I can return my device to stock? Thanks for any response
Flash factory image
https://developers.google.com/android/nexus/images#occam
attempted
attempted to flash stock and got the following error message
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
codebam said:
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
Click to expand...
Click to collapse
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
MrTalk said:
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
Click to expand...
Click to collapse
Okay adb push a cyanogenmod zip from here and flash it in recovery. It should automatically install a working boot image. You should also flash the latest bootloader in the factory image with "fastboot flash bootloader bootloader.img" if you're using an outdated bootloader.
used the advice
I pushed the zip file using cmd and it appears to have been successful since I was given the summary of data transferred and how long it took once the process was finished.
I can't find the zip file in twrp to attempt to flash it.. Is there any reason the file name would change inside the device once it has been pushed?
Is there a way to flash the zip in question without pushing it unto the device?
When I try to flash TWRP (via "fastboot flash recovery twrp.img" then "fastboot boot twrp.img") I receive the following error:
Downloading 'boot.img'
OKAY [1.477s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.534s
I've tried manually booting it into recovery with power button and volume down but it just freezes on the oneplus logo where I have to turn off and on again.
Any help is greatly appreciated!
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
that link just saved me!
I tried this recovery (I had the same problem as the OP) but although I can boot into twrp, I get stuck on the oneplus logo if I try a normal boot?
Sent from my Nexus 9 using XDA-Developers mobile app
I managed to get it working by flashing CM after flashing the recovery.
Sent from my Nexus 9 using XDA-Developers mobile app
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
pitrus- said:
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
Click to expand...
Click to collapse
Actually, fastboot boot twrp.img boots the TWRP image without flashing it.
fastboot flash recovery twrp.img flashes the TWRP image to the recovery partition.
Both are valid commands and have their uses.
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Spannaa said:
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Click to expand...
Click to collapse
That's exactly what I meant to convey.
Similar problem while flashing recovery
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
bhanuodin said:
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
Click to expand...
Click to collapse
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
pitrus- said:
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
Click to expand...
Click to collapse
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
bhanuodin said:
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
Click to expand...
Click to collapse
The bootloader (also called fastboot) comes with the original ROM. In your case you're already on the newer bootloader since you flashed OOS3 which means you will have to flash recoverys and ROMs compatible with this newer bootloader.
This TWRP should be compatible
https://dl.twrp.me/oneplus2/twrp-3.0.2-1-oneplus2.img.html
Also you can't run ROMs not compatible with this newer bootloader (which means pretty much any ROM that's not using the official Cyanogenmod source tree for building). That is except for OOS3 or newest HOS of course since these are made for the newer bootloader.
However I would say the error message you get might be caused by bad cable, faulty driver setup, faulty fastboot tool version or in worst case damaged partition layout on phone. The last one can be fixed by the Qualcomm OOS2 factory restore solution.
Hi, i am having the same problem.
some background: I was on Oxygen OS 2.x.x, i wanted to upgrade to Exodus 6. I had the older version of TWRP. So I tryed to install the new twrp image within twrp. When i rebooted i couldnt boot into twrp, receiving the same error message as in OP title, when using fastboot.
Using the tool all in one toolkit I was able to flash stock recovery.
But I still cant flash Twrp.
I can still boot into system though.
Any advice? Thanks.
That explains why you're having problems. You're doing it the wrong way.
First you must upgrade the bootloader by either flashing the convert to Marshmallow zip file which also installs the correct TWRP for the new bootloader (easiest way). Or you could flash the latest official OOS3, then fastboot flash the latest TWRP and from there format system and flash the ROM that's using the newer bootloader.
Does that Link work with oneplus x also? Having same problem as Higgings when trying to install twrp and cyanogenmod.
thnx a lot for sharing
:good:
Higgings said:
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
Click to expand...
Click to collapse
Hello,
I've decided to install the Beta version of Oxygenos 3.0. Since my phone came from the OnePlus support, I've unlocked the oem, installed TWRP and flashed the Oxygen zip.
However, a day later I've spotted important touchscreen issues (I can't use the touchscreen sometimes).
To see if it is a software problem, I've decided to go to the recovery to reflash a backup. When I try to go to recovery mode, nothing Happen! (Just the oneplus logo ).
So, i've decided to reinstall TWRP by flashing it with fastboot.
"fastboot flash recovery recovery.img" -> OK
"fastboot boot recovery.img"
downloading 'boot.img' ...
OKAY [0.702s]
booting...
FAILED (remote: dtb not found)
Click to expand...
Click to collapse
I've tried to install the stock recovery but I've the same error.
PLEEEASE HELP. I've waited a week to receive my phone because it had a problem but it's broke again :crying:
Note: I can go in Android normally (but with the touchscreen problem)
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.
This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.
AndroidBeginNinja said:
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.
Click to expand...
Click to collapse
Thank you,
I've done this and I had a working recovery, (bootloop if I try to boot up normaly but it's not a problem I just have to flash a rom)
Trey22200 said:
This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.
Click to expand...
Click to collapse
I've tested your manipulation and it worked well too.
For those having the same problem OR want to install Oxygen OS the CLEAN WAY, read this post before: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
It is very important to read the faq before flashing and doing **** like me.
http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713 flash this first before you flash oos3
Hi, I'm having issues with booting recovery.
I've successfully rooted my phone before, but because of an OTA update, had to revert back to the flashing of recovery (TWRP), booting recovery, then flashing Magisk steps.
So, I have my recovery.img file which I renamed to "twrp.img" (no double twrp.img.img file extensions). It looks like I'm able to flash it successfully, giving something that looks like this when I run "fastboot flash recovery twrp.img" (in the directory where the recovery image is located):
target reported max download size of 536870912 bytes
sending 'recovery' (24496 KB)...
OKAY [ 0.530s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.691s
Click to expand...
Click to collapse
However, after I try the "fastboot boot recovery twrp.img" command, it gives me:
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
When I try to restart into recovery, it just boots into stock recovery, and not TWRP.
Any help would be super useful, I'm really not able to figure this out. I've done a lot of research, even going through disabling/uninstalling the Kedacom USB drivers and turning airplane mode on and installing adb/fastboot drivers from XDA.
Thanks!
Why are you flashing two recovery images? Maybe I'm missing something but I'm not understanding what it is that you are doing.
Your problems could also be related to whatever version of TWRP you are flashing on whatever OS you are running. Maybe there is a compatibility issue between the two but without more specific information it's pretty much impossible to say.
I'm just flashing one recovery.img file (TWRP), which doesn't display any errors in the flashing in command line. But when I try to boot it in command line, it gives me the above error that the recovery doesn't exist. When I try to boot it by advanced restart -> recovery, it just takes me to the stock recovery.
I'm on Oxygen 4.5.14. Let me know if there's anything else I can provide.
Rename your Recovery file to twrp.img
Seems like you forgot to do that according to your command
k0byf1ch said:
Hi, I'm having issues with booting recovery.
I've successfully rooted my phone before, but because of an OTA update, had to revert back to the flashing of recovery (TWRP), booting recovery, then flashing Magisk steps.
So, I have my recovery.img file which I renamed to "twrp.img" (no double twrp.img.img file extensions). It looks like I'm able to flash it successfully, giving something that looks like this when I run "fastboot flash recovery twrp.img" (in the directory where the recovery image is located):
However, after I try the "fastboot boot recovery twrp.img" command, it gives me:
When I try to restart into recovery, it just boots into stock recovery, and not TWRP.
Any help would be super useful, I'm really not able to figure this out. I've done a lot of research, even going through disabling/uninstalling the Kedacom USB drivers and turning airplane mode on and installing adb/fastboot drivers from XDA.
Thanks!
Click to expand...
Click to collapse
Edit:Sorry I kind of Missed that its already Done
Please Ignore My Upper Message
Possible another Solution:
Download Another Recovery File and Do the Same again
I've renamed the file since, and it still has been a problem.
Both recovery.img and twrp.img and the original name of the file "twrp-3.1.1-cheeseburger-84-20170820-194433-CEST.img" wouldn't take.
The file name is irrelevant. But it seems like your command to boot into recovery is the problem: fastboot boot only takes one argument (the file to boot into) whereas the fastboot flash command takes two arguments (partition and file to flash).
fastboot flash recovery twrp.img
fastboot boot twrp.img
Okay, I'll give that a shot but I'm still booting into the stock recovery when I advance restart into recovery.