I tried rooting my Swift and I ended up being stuck in TWRP 2.8.7.1.
All I did was fastboot the TWRP 28.7.1 Image.
I then decided not to do it, so I tried to reboot device.
It keeps putting me into twrp.
Could someone tell me how i get rid of this.
Sorry if the answer is obvious I'm a noob to this.
Greets Louis
ztva said:
I tried rooting my Swift and I ended up being stuck in TWRP 2.8.7.1.
All I did was fastboot the TWRP 28.7.1 Image.
I then decided not to do it, so I tried to reboot device.
It keeps putting me into twrp.
Could someone tell me how i get rid of this.
Sorry if the answer is obvious I'm a noob to this.
Greets Louis
Click to expand...
Click to collapse
- on which firmware were you (COS12.1 or COS13.0)?
- how exactly did you flash twrp?
You can always revert back to stock by flashing from
cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip
or
cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip
as folows:
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Thanks for the response.
I flashed back to the original recovery and everything works fine.
I'm currently on COS 13.0.
Is there a safe way to root my Swift or get CM running safely.
I've tried a couple of methods on here, but they didn't seem to work.
I also reallly don't want to brick my phone since it's the first decent smartphone I have.
I know the basics like how to use adb and fastboot, but I'd really appreciate some advice on this.
Greets Louis
ztva said:
Thanks for the response.
I flashed back to the original recovery and everything works fine.
I'm currently on COS 13.0.
Is there a safe way to root my Swift or get CM running safely.
I've tried a couple of methods on here, but they didn't seem to work.
I also reallly don't want to brick my phone since it's the first decent smartphone I have.
I know the basics like how to use adb and fastboot, but I'd really appreciate some advice on this.
Greets Louis
Click to expand...
Click to collapse
There is a separate thread about preparing for and rooting.
Being on COS13 you may want to use TWRP_3.0.2 (to be found separate thread) and flash UPDATE-SuperSU-v2.76 ZIP (to be found in SuperSU trhead) from TWRP.
You can even boot TWRP without the need to flash it with e.g.:
Code:
fastboot boot twrp-3.0.2-0.img
Hi, I have the same problem. My Swift is blocked on TWRP and it doesn't go into bootloader. How I can to do?
Related
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!
Hey guys, I think i screwed up big time. I have just received my Htc one M8 from rogers (with no bloatware on it .. weird lol ) And i wanted to root it in order to use titanium back up.
So i followed a guide to root the phone everything went well execpt that now my phone boots straight into philz custom recovery....
When i was entering the fastboot commands to flash the recovery to the phone i made a mistake i wrote :
fastboot flash boot recovery.img
instead of
fastboot flash boot recovery recovery.img
....
So my guess is that i have overwritten the boot.img of the phone with the custom recovery which is bad... now i can't use the phone...
Is there a way to flash the stock boot image back? of to restore the phone like it was brand new?
Thanks for you help
Reflash the both with the correct commands !!!
Fastboot flash recovery recovery.img
and
Fastboot flash boot boot.img
Mr Hofs said:
Reflash the both with the correct commands !!!
Fastboot flash recovery recovery.img
and
Fastboot flash boot boot.img
Click to expand...
Click to collapse
Yeah this is what i wanted to do but i couldn't find a boot.img. I did find it eventually. here it is in case anyone needs it
Straight, just saying.
The boot.img is always in the rom....Most roms contain the stock boot.img. or check my backup collection and download the stock rom. It has the stock boot.img inside
Thanks a lot.
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
Hi,
My phone is rooted and the DPI was customized. I tried to manually flash the OTA but the installation got stuck so I cannot boot into Android anymore. I tried those restore tutorials but when I try to flash using fastboot I get a "FAILED (remote: Permission denied). I tried to clear the cache in the recovery and then it got also stuck and now I can't access recovery.
This is what I can read in the bootloader
---------------------------
FASTBOOT MODE
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI - 0094.0177
SERIAL NUMBER - Xxxxx....
SIGNING - ?
SECURE_BOOT - ?
continue fastboot process
-----------------------------
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
manlord said:
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
Click to expand...
Click to collapse
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
ultramag69 said:
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
Click to expand...
Click to collapse
Thanks for your help. I did that earlier with the latest pre-rooted OTA and now it gets stuck on the splashscreen. I tried going to recovery (stock now) and doing a factory reset after flashing system.img and it still the splashscreen after I reboot. I know the 1st boot after flahing a ROM can be long, but now it's been an hour and I'm still on the splash screen...
The only other thing I can recommend is to flash a RAW rom image. As I have never needed to do this I can't say how this works but if you do a search you should find out the procedure...
This may relock your bootloader so just be aware....
Hey guys I think i have a problem
I was trying to flash v4a, and realized that I needed to downgrade twrp from RC2 to RC1. My phone had been rooted by SU.
I proceeded to do the flash and then flashed the v4a mod but now my phone can't get out of TWRP. When I click reboot, it boots into the recovery mode.
Any ideas on how to solve this? I cannot use my phone now
Use fastboot to flash stock boot on both slots
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Fastboot boot twrp.img
Then flash twrp and all should be fine
mikaole said:
Use fastboot to flash stock boot on both slots
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Fastboot boot twrp.img
Then flash twrp and all should be fine
Click to expand...
Click to collapse
Just wanted to chime in so people in the future can see that this worked, at least for me on my Pixel 2 XL.
hey, I tried this method to boot back into system but lost TWRP recovery... any way to install TWRP without flashing boot.img again? or which boot.img should I be flashing back to slot A and B.. i extracted the boot.img from factory images but i lose TWRP recovery