Hi friends,
So here's a thing:
I was trying to update my Nexus 9 to the latest Slimrom build , and I used Chainfire's flashfire app. It didn't work and sent the tablet in a boot loop. But it also wiped my recovery so I couldn't even select my recovery.
So no issues, I used the Wugfresh nexus toolkit to flash it back to stock and unroot. Bootloader is still unlocked, so I just root it again and go ahead and try to install the update using Wugfresh. It works, but says the vendor.img is wrong. So I downloaded the correct vendor.img and tried to flash it, but of course because the tablet is encrypted TWRP asked for a password. I hit cancel and tried to continue, but Wugfresh just hung at that step.
So I tried to manually flash the ROM, but now it gives me a vendor.img error and will not flash anything. Trying to flash anything sends the device in a bootloop.
TLDR; I can restore to stock and root, and also access the bootloader and recovery (TWRP) but can't flash anything without sending the device in a bootloop.
I've currently restored the tablet to stock via wugfresh's tool and rooted. So I'm back at the beginning, except with this vendor.img issue when I'm trying to flash a ROM.
Anyone have any ideas?
Related
So I just unlocked my bootloader and flashed CM12 with TWRP. TWRP refused to flash Gapps and just kept restarting, after I flashed CM12. I booted into CM12 and then into recovery and it was replaced with the CyanogenRecovery, which can't flash anything. When I tried with fastboot to flash TWRP, it said successful, but kept the Cyanogen one. How do I change it?
EDIT - Flashed it again with ADB and it worked. Now Gapps restarts TWRP.
Hey buddy
just install [ROOT] Rashr - Flash Tool by DsLNeXuS (Aschot Mkrtchyan) from the Play Store.
The App lets you decide wich recovery you want to flash
I really don't know what is left to do, I always end up with a bootloop and have to repair my phone with flashtool. I have tried flashing twrp by adb/fastboot, temporarily booting to twrp, flashing different twrp files after repair.... I always get boot loop. Help please :/
Once I had my phone rooted by oneclickroot support, then I started to get play store crashed constantly. Once I booted to recovery and when try to reboot, got a bootloop. I tried to flash a new rom, so found a stock rom for Z5C and flashed it by twrp. But after a reboot I lost the twrp recovery this time. Then I tried to flash the recovery myself using abd, following the basics; fastboot flash boot boot.img/recovery recovery.img But I again stuck into a bootloop. Repaired again... I thought flashing a custom recovery breaks the phone, so I decided to just boot the recovery and install supersu. but again a bootloop in the end.
Is your bootloader already unlocked?
Gewiz said:
Is your bootloader already unlocked?
Click to expand...
Click to collapse
yes sir, already.
flash complete stock, no modifications.
confirm if it loads to usermode
NeoBeum said:
flash complete stock, no modifications.
confirm if it loads to usermode
Click to expand...
Click to collapse
I have flashed the lastest stock ftf by flashtool, that is what I do after everytime I brick it while trying to obtain root. And if you mean switching to another user, yes it does.
that's good. it means hardware is fine.
it's your root method.
try this
https://forum.xda-developers.com/showthread.php?t=3609358
Hi, I am using P600 (note 10.1 2014 Wifi) XAR one
Yesterday I was trying to install magisk all day, but failed all
When I rooted device and instaled TWRP, in TWRP it made error number 1 and it says something like turn to stock boot, so I tried to reinstall stock firmware via Odin, but it didn’t change anything.
I guess it’s a problem with boot.img or the autoroot method I used.
So I tried to use fastboot to install TWRP without rooting, but this time it didn’t boot into bootloader from fastboot, it just restarted the tablet all the time.
So I tried to manually reboot into the download mode, but fastboot didn’t recognize the device then.
When I did it, I turnned on the USB debugging with no mistake since it’s just samsung.
So I booted into recovery mode(It can go into recovery mode without problem)
Then tried option “reboot to boorloader” and it just restarts the tablet again.
I guess something corrupted boot.img or bootloader somehow, while I was rooting or something.
Can I get factory boot.img and solve it? Or when I install stock firmware via Odin does it also fix boot.img and boot loader?
I tried to install stock firmwares and factory reset several times. It didn’t help anything. It did unroot or turn the recovery to stock recovery, but couldn’t get into bootloader.
Can anyone please help me or give me advice to solve this problem?
Bump
Hi everybody,
I got my Swift 2 8 months ago and have finally decided to root it using TWRP. So I unlocked my bootloader and then installed TWRP using the official guide at https://twrp.me/devices/wileyfoxswift2.html. I also wiped my cache and dalvik cache.
However, now I have done this, whenever I try to boot, I receive both the amber and red warnings about corruption and then get stuck in a bootloop on the first black and white boot image.
Please can someone help me get back into android; if possible I would like root but in the end just a working phone.
Thanks.
As far as I know it's a dm-verity issue. There might be several ways to fix it but the only one I know is to flash Magisk from TWRP. I still run version 12 because 13.x won't install for me.
From my expierience, unlocking and locking bootloader will wipe your userdata , so backup! How I root mine is, first unlock through fastboot, than fastboot boot twrp, instead of flashing, flash magisk through twrp, than lock the bootloader again through fastboot. This keeps you from getting messages about corruption and has you rooted. Whenever I need twrp I just boot it instead of flashing it. I also made a backup using twrp, just to keep things safe and easy to restore...
Edit: To get out of bootloop you either do a factory reset or flash the image found in this forum using fastboot update...
You should have a look at this thread: https://forum.xda-developers.com/swift-2/how-to/marmite-wileyfox-ota-nougat-android-7-1-t3654999
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!