Problems with my HTC one X.
adb devices returns 'no devices found'. fastboot devices works though.
CWM recovery seems to be working.
Can't install CM9 from SD-card, when i do the phone hangs at the loading screen of CM9.
Can't adb push another .zip to the phone since ADB doesn't work.
Fastboot:
c:\Users\user\Desktop\HTC\onexroot>fastboot erase cache
erasing 'cache'...
FAILED (command write failed (Unknown error))
finished. total time: 0.588s
also:
c:\Users\Rik de Vroom\Desktop\HTC\onexroot>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
sending 'recovery' (5732 KB)...
FAILED (unknown status code)
finished. total time: 0.026s
How can I get another .zip file on the sdcard? was hoping to try InsertCoin (since bluetooth isn't working on CM9 and a lot of apps keep crashing).
why isn't adb working? I have updated my JDK and android SDK...
adb devices DOES working in the hanging loading screen of CM9; but unable to do anything "waiting for device" ...
Im stuck :<
CWM
1st flash new CWM that has USB mount, so you can send any file to phone
2dn did you flash the kernel? >> boot.img for the CM9 ROM?
FabioPBX said:
1st flash new CWM that has USB mount, so you can send any file to phone
2dn did you flash the kernel? >> boot.img for the CM9 ROM?
Click to expand...
Click to collapse
looking into the new cwm now; hadn't figured that was so outdated.
i did flash the kernel; used cm9 before but that was behavving strangely; so figured a reinstall might help. tried miui in the meantime but man, i'm used to cm9
maybe you got a corrupted download but if you can access recovery then you should be fine
give TripNDroid's CM9 port a go, he was first to have almost fully functional CM9 port and works quite decently, with just few minor bugs
FabioPBX said:
maybe you got a corrupted download but if you can access recovery then you should be fine
give TripNDroid's CM9 port a go, he was first to have almost fully functional CM9 port and works quite decently, with just few minor bugs
Click to expand...
Click to collapse
Well, what doesn't work is bluetooth and GPS.. both of which i want to use.. Also; a lot of apps seem to 'stop responding' after a while.. Guess im back to stock rom untill a fully working CM9 comes out.
Related
I have been running MIUI flashed via clockwork app/recovery for the past few months. Today, suddenly a bunch of my apps were not working and I was getting a load of force closes. I figured I reboot and I find myself in a bootloop.
At this point, it isn't a huge deal. I figured, I would boot into recovery and load up my backup from CM7. Only problem is I can't seem to get into my recovery, as thought it is gone. Also no big deal, I'll just try to reflash my recovery via fastboot. I load up on hboot and run it with the latest version from clockwork:
Code:
D:\Desktop>fastboot devices
HT08JHJ04373 fastboot
D:\Desktop>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm looking several places for this exact problem, but I can't seem to find anything that works for me. My SD is backed up and while I would like to be able to keep my other stuff and/or just get up and running again without a wipe, any suggestion would be helpful right about now.
Thank you,
Drox
droxpopuli said:
I have been running MIUI flashed via clockwork app/recovery for the past few months. Today, suddenly a bunch of my apps were not working and I was getting a load of force closes. I figured I reboot and I find myself in a bootloop.
At this point, it isn't a huge deal. I figured, I would boot into recovery and load up my backup from CM7. Only problem is I can't seem to get into my recovery, as thought it is gone. Also no big deal, I'll just try to reflash my recovery via fastboot. I load up on hboot and run it with the latest version from clockwork:
Code:
D:\Desktop>fastboot devices
HT08JHJ04373 fastboot
D:\Desktop>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm looking several places for this exact problem, but I can't seem to find anything that works for me. My SD is backed up and while I would like to be able to keep my other stuff and/or just get up and running again without a wipe, any suggestion would be helpful right about now.
Thank you,
Drox
Click to expand...
Click to collapse
Have you tried flashing recovery thru hboot with a PB31IMG.zip? You can get it here http://pvillecomp.com/?page_id=28
I got it installed from there. I loaded up the recovery and it must have done a restore since I booted and it was fresh miui like when i did a backup from before. Nothing to be done there sadly :/ But thanks for the help and the link. I didn't even know this site existed.
I thought I was out of the noob phase but apparently not, just some basic info before I state my problem, Xperia play R800x, unlocked bootloader, running CM9, rooted. Ok so... I'm trying to flash the Doomkernel boot.img here's what I get.
C:\Android>fastboot -i 0x0fce flash boot boot.img
error: cannot load 'boot.img'
C:\Android>fastboot -i 0x0fce flash boot boot.img
error: cannot load 'boot.img'
I have the CDMA Doomkernel V2 in the same folder as fastboot so yeah now I'm stumped. Fastboot HATES me for some reason:crying:
Anything else I can try?
Did you rename it to boot.img? Or is it the actual downloaded name?
savage24x said:
Did you rename it to boot.img? Or is it the actual downloaded name?
Click to expand...
Click to collapse
It's the downloaded name it's something like CDMADoomkernelV2.img
Xperia Player said:
It's the downloaded name it's something like CDMADoomkernelV2.img
Click to expand...
Click to collapse
So, then that's what you should replace "boot.img" with in the command.
savage24x said:
So, then that's what you should replace "boot.img" with in the command.
Click to expand...
Click to collapse
Can't I just re name the doomkernel boot img?
from CDMAdoomkernel.img to boot.img?
Xperia Player said:
Can't I just re name the doomkernel boot img?
from CDMAdoomkernel.img to boot.img?
Click to expand...
Click to collapse
Yes.
savage24x said:
Yes.
Click to expand...
Click to collapse
Thanks for the help man. I re named it successfully, but now I'm getting another error message -.- go figure...
C:\Android>fastboot -i 0x0fce flash boot boot.img
sending 'boot' (8694 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.016s
Xperia Player said:
Thanks for the help man. I re named it successfully, but now I'm getting another error message -.- go figure...
C:\Android>fastboot -i 0x0fce flash boot boot.img
sending 'boot' (8694 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.016s
Click to expand...
Click to collapse
Is your bootloader unlocked? If not you can't install custom kernel.
chery2k said:
Is your bootloader unlocked? If not you can't install custom kernel.
Click to expand...
Click to collapse
yes.
Xperia Player said:
Thanks for the help man. I re named it successfully, but now I'm getting another error message -.- go figure...
C:\Android>fastboot -i 0x0fce flash boot boot.img
sending 'boot' (8694 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.016s
Click to expand...
Click to collapse
Tried different USB cable? Tried different computer? If so, Flash the 2.3.3 ftf file via flashmode and then try the fastboot flashing again. Try it without -i 0x0fce. Mine works without it.
savage24x said:
Tried different USB cable? Tried different computer? If so, Flash the 2.3.3 ftf file via flashmode and then try the fastboot flashing again. Try it without -i 0x0fce. Mine works without it.
Click to expand...
Click to collapse
Even without -i 0x0fce is still does not work... I've flashed FXP kernel with this computer and usb cable before....:crying:
Any other ideas? :crying:
Not sure if this helps but i had a similar problem. I used the latest flashtools and when you go to flash (the lightning bolt button) you can go into flash mode or fastboot mode. Click fastboot mode and then connect your phone to the pc in fastboot then click the option "select kernel to flash". Thats how i flashed Doomlords kernel. Flashtools 9.0. Worth a try? But im a newb my self only just unlocked my bootloader and this is how i managed to flash doomlords kernel.
Finally got fastboot to work. I did the exact same thing I was doing for an hour and it just now decides to work.... I'm trying to flash GB tweaked and OF COURSE I have yet another problem -.- I cleared data and cache, and ran the GB tweaked nandroid backup via cwm & rebooted. now I'm stuck at the doomkernel screen -.- grrrrr...
Delete.
Sent from my R800x using xda premium
i have the same issue sometimes but i fix it by changing usb port
Sent from my R800i using Tapatalk 2
I think you're right about the USB port thing, mine randomly decided to work after like an hour of typing in the same commands lol. Thank guys yall helped me out but I gotta admit this thread was pretty dumb on my part. Mods can go ahead and delete this, unless of course someone wants to help me find a working wifi module for DoomkernelV2, I found one for V1 no problem. Just a suggestion but not necessary.
Cheers
Xperia Player said:
I think you're right about the USB port thing, mine randomly decided to work after like an hour of typing in the same commands lol. Thank guys yall helped me out but I gotta admit this thread was pretty dumb on my part. Mods can go ahead and delete this, unless of course someone wants to help me find a working wifi module for DoomkernelV2, I found one for V1 no problem. Just a suggestion but not necessary.
Cheers
Click to expand...
Click to collapse
If u use GBTweaked v.05 then the wifi modules is pre-loaded...
otonieru said:
If u use GBTweaked v.05 then the wifi modules is pre-loaded...
Click to expand...
Click to collapse
Explain, when I downloaded GB tweaked & was running Doomkernel V2 my wifi would continuously scan, connect, and disable. wtf??
Xperia Player said:
Explain, when I downloaded GB tweaked & was running Doomkernel V2 my wifi would continuously scan, connect, and disable. wtf??
Click to expand...
Click to collapse
this is step that work for me :
-Flash kernel :
fastboot flash boot doom.img
-Erase System & User Data via fastboot :
fastboot erase system
fastboot erase userdata
-Boot to Recovery, Clear Cache & Dalvik Cache
-Restore from Nandroid Backup
-Boot up
-Reboot to Recovery Again, wipe Cache again
-flash Gapps.zip (for working Network Location)
-Boot Up
-Done, everything working well
Hello everyone.
I am having this error while trying to flash the latest factory image.
Adb and fastboot seem propoerly configured as I have adb devices and fastboot devices working.
sending 'bootloader' (3911 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time 5.011s
rebooting into bootloader...
FAILED (status read failed ( Too many links))
finished. Total time: 117.384s
Any help would be appreciated, because I am lost on this one.
SDK is fully updated and doing everything as I did to flash 5.0.1
Thanks in advance.
Can't help with ADB or Fastboot but I can suggest dirty flashing this stock, rooted rom by scrosler found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Worked great for me. Good luck!
Mine failed the first couple of times too, but on the third attempt it went through. However, it turns out that I had failed to turn on the ADB bridge on the first one, and I guess it was still coming up on the second.
Adb has nothing to do with this. Fastboot is what's used when you're in the bootloader.
Have you tried a different cable/USB port?
yosmokinman said:
Adb has nothing to do with this. Fastboot is what's used when you're in the bootloader.
Have you tried a different cable/USB port?
Click to expand...
Click to collapse
Very true, except that it uses adb to initially reboot the tablet into fastboot mode.
It would probably skip that step if you were already in fastboot mode, but if the OS is running, the flash-all script will attempt to restart the device by running adb reboot bootloader.
That said, if ADB isn't working, checking the cable and drivers is the next step.
Getting into the bootloader doesn't require adb. Use the hardware buttons.
hy!
in fastboot i unlocked the nexus 7. I then flashed recovery of clockword mod and twrp but with both i end up on "google" screen with the unlocked lock symbol. After some time it boots in to stock rom. How do i get to run recovery?
i used:
sudo fastboot flash recovery <filename>..
also i cant lock it anymore, it gives me an error.
what i am trying to do? i want to root the device via a recovery rom as towelroot does not work and i dont have a modstring for the nexus 7 for towelroot. i then want to run fstrim as the device is completely nutty slow. maybe install a custom rom- anyone has a source for a good cm?
thx!
versions i tried:
recovery-clockwork-touch-6.0.4.3-flo.img
twrp-2.6.3.1-flo.img
twrp-3.1.1-0-flo.img
update: now i somehow managed to change from the "google with unlocked symbol" screen to the "fallen android" screen. that means no recovery is found.. i dont get it. after booting into stock rom after the unlocking of the bootloader i re-enabled usb debugging of course.
recovery writing ocurs very fast and no info the nexus 7 screen is displayed:
twrp-3.1.1-0-flo.imgsending 'recovery' (8962 KB)...
OKAY [ 1.115s]
writing 'recovery'...
OKAY [ 0.367s]
finished. total time: 1.482s
i tried with v 2.4. of team win recovery, which did install and execute
ok, got it up an running, dont know why it didnt want at first, but its all ok.
used twr3xx
and lineage11
and gapps pica
works
nice tut:
https://cd-rw.org/t/resurrect-a-nexus-7-2012-to-run-as-good-as-new/141
nice rom:
https://forum.xda-developers.com/ne...fficial-build-cyanogenmod-11-0-nexus-t3174831
Hope you guys can give me a hand and get me out of this situation...
What I am using
Xiaomi Redmi Note 5 Pro with:
- Pixel Experience Rom
- TWRP 3.5.2_9
Windows 10 21H1 x64
What happend
- Updating Pixel Experience Rom failed
Downloaded update
Booted into Recovery (battery 85%)
Recovery stuck on Logo
After 30m I tried to reboot to system (thinking update failed or never started)
Reboot in to Recovery
Stuck on Logo
What I tried
- I tried XiaomiFastBootADBTools (latest version)
Device is recognized in Recovery mode
In recovery I can't do anything
Rebooting to System from here results in reboot into Recovery
Booting to fastboot works, but device is not recognized
Re-installed drivers, but no luck
Still recognized in Recovery mode
Still NOT recognized in Fastboot mode
Windows Device Manager > The drivers for this device are not installed. (Code 28)
And turning of phone is not possible, just goes back to Recovery
Don't know what else to do. I have installed all the drivers I could find. Even used Snappy Driver, but nothing seems to do the trick when the phone goes into Fastboot mode. PC just doesn't recognize it.
So can't do anything in Recovery mode; just watching the TWRP logo.
And device is not recognized in fastboot mode; forgot usb debugging?
And can't boot into system to change that, because of bootloop to Recovery.
So, am I **** out of luck and bricked my phone?
While in Recovery mode (when the phone is still recognized) type in adb window the command - adb reboot bootloader. Phone should boot to Fastboot mode and see if it's still recognized.
zaqm said:
While in Recovery mode (when the phone is still recognized) type in adb window the command - adb reboot bootloader. Phone should boot to Fastboot mode and see if it's still recognized.
Click to expand...
Click to collapse
Yeah, that works. Same as with XiaomiADBFastbootTools. But after that the problem starts (remains).
When I get into Fastboot the Device Manager shows the phone as Other Devices > Android with an exclamation mark and the message that the drivers are not installed. I'm missing a driver, but I don't know which one. Guessing Xiaomi USB driver? Finally fixed that issue with another round of googling. I read that you just need net "Mi unlock Tool". So tyring to find that one:
- https://en.miui.com/unlock/download_en.html
results in a download that doesn't contain the files needed.... No driver_install and no miflash_unlock.exe etc.
pretty weird, found another page https://c.mi.com/thread-2262302-1-0.html with previous versions
- 4.5.813.51 won't download... really xiaomi, your site sucks.
- 4.5.707.49 finally downloads and seems to work.
So updated the driver by pointing to that folder. Worked like a charm.
Opening Minimal ADB and Fastboot (XiaomiADBFastboottools didn't recognize phone once in fastboot).
- adb reboot bootloader > success
- fastboot flash recovery 'recovery_file_location' > error
target reported max download size of 536870912 bytes
sending 'recovery' (47140 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried both latest TWRP and Orangefox. Same message each time.
Tried an older/smaller TWRP 3.3.1 and got a different but still similar message
target didn't report max-download-size
sending 'recovery' (38924 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried it with Platform-Tools
- adb reboot bootloader
- fastboot boot 'recovery_file_location'
Which results in
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
OR
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
AND eventually
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
2 hours in, calling it a day for now.
FlashyDuck said:
Yeah, that works. Same as with XiaomiADBFastbootTools. But after that the problem starts (remains).
When I get into Fastboot the Device Manager shows the phone as Other Devices > Android with an exclamation mark and the message that the drivers are not installed. I'm missing a driver, but I don't know which one. Guessing Xiaomi USB driver? Finally fixed that issue with another round of googling. I read that you just need net "Mi unlock Tool". So tyring to find that one:
- https://en.miui.com/unlock/download_en.html
results in a download that doesn't contain the files needed.... No driver_install and no miflash_unlock.exe etc.
pretty weird, found another page https://c.mi.com/thread-2262302-1-0.html with previous versions
- 4.5.813.51 won't download... really xiaomi, your site sucks.
- 4.5.707.49 finally downloads and seems to work.
So updated the driver by pointing to that folder. Worked like a charm.
Opening Minimal ADB and Fastboot (XiaomiADBFastboottools didn't recognize phone once in fastboot).
- adb reboot bootloader > success
- fastboot flash recovery 'recovery_file_location' > error
target reported max download size of 536870912 bytes
sending 'recovery' (47140 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried both latest TWRP and Orangefox. Same message each time.
Tried an older/smaller TWRP 3.3.1 and got a different but still similar message
target didn't report max-download-size
sending 'recovery' (38924 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried it with Platform-Tools
- adb reboot bootloader
- fastboot boot 'recovery_file_location'
Which results in
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
OR
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
AND eventually
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
2 hours in, calling it a day for now.
Click to expand...
Click to collapse
What about trying to flash latest fastboot rom with MiFlash since fastboot now works?
Absolutely awesome! We did it!
I'm no expert in all this, so I had to use a guide to flash a fastboot rom with the Mi Flash Tool. I used this guide: https://www.thecustomdroid.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
That was all straight forward untill I came to step 6; flashing the actual rom with the Mi Flash Tool.
The tool just wouldn't recognize my phone when in Fastboot mode. Even after the driver install popup.
- after pressing refresh phone disconnected.
- tried 3 different usb ports (read online that this could be the issue)
- tried 3 different cables...
The third cable (Ugreen cable) worked! Although it only worked on a usb 3.0 port strangely enough.
I used the "clean all" option and flashed the latest MIUI global fastboot rom for the RMN5.
Flashing process was a bit strange, because the tool didn't provide me with the same information shown in the guide, but it flashed a couple of things to 100% completeness and after that it kept counting up and showing $pause. Not much later the phone started to boot into MIUI and everything was normal.
Enabled dev options and usb debugging.
Re-flashed latest twrp recovery just to be sure.
And it's all working fine again.
Really, thank you for your help! It's much appreciated!
FlashyDuck said:
Absolutely awesome! We did it!
I'm no expert in all this, so I had to use a guide to flash a fastboot rom with the Mi Flash Tool. I used this guide: https://www.thecustomdroid.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
That was all straight forward untill I came to step 6; flashing the actual rom with the Mi Flash Tool.
The tool just wouldn't recognize my phone when in Fastboot mode. Even after the driver install popup.
- after pressing refresh phone disconnected.
- tried 3 different usb ports (read online that this could be the issue)
- tried 3 different cables...
The third cable (Ugreen cable) worked! Although it only worked on a usb 3.0 port strangely enough.
I used the "clean all" option and flashed the latest MIUI global fastboot rom for the RMN5.
Flashing process was a bit strange, because the tool didn't provide me with the same information shown in the guide, but it flashed a couple of things to 100% completeness and after that it kept counting up and showing $pause. Not much later the phone started to boot into MIUI and everything was normal.
Enabled dev options and usb debugging.
Re-flashed latest twrp recovery just to be sure.
And it's all working fine again.
Really, thank you for your help! It's much appreciated!
Click to expand...
Click to collapse
Glad that it worked out. Sometimes even the most untraditional methods work like usb 3.0 and the third cable.
Still all went good and that's the good news. Enjoy
--double, woops--
zaqm said:
Glad that it worked out. Sometimes even the most untraditional methods work like usb 3.0 and the third cable.
Still all went good and that's the good news. Enjoy
Click to expand...
Click to collapse
Unfortunately, the problem has returned.
The first time flashing Orange Fox Recovery was no problem. I could boot to Recovery. I installed Pixel Experience Plus again. That all worked fine.
Today I wanted to try out ArrowOS. And this is what I did:
- loaded the .zip file on the phone
- turned off the phone
- booted into recovery
- stuck on recovery logo screen...
- after this the phone bootloops to recovery again as before...
In Recovery and Fastboot the phone is still recognized by the PC. But in Recovery I can't do anything.
So in Fastboot mode I tried re-flashing Orange Fox , but same result. Flashing seems successful but can't get past the Recovery logo. I even tried flashing TWRP, but also same result.
I can probably redo all the steps in my previous post, but once I boot to recovery the phone is done for it seems.
Any ideas?
FlashyDuck said:
Unfortunately, the problem has returned.
The first time flashing Orange Fox Recovery was no problem. I could boot to Recovery. I installed Pixel Experience Plus again. That all worked fine.
Today I wanted to try out ArrowOS. And this is what I did:
- loaded the .zip file on the phone
- turned off the phone
- booted into recovery
- stuck on recovery logo screen...
- after this the phone bootloops to recovery again as before...
In Recovery and Fastboot the phone is still recognized by the PC. But in Recovery I can't do anything.
So in Fastboot mode I tried re-flashing Orange Fox , but same result. Flashing seems successful but can't get past the Recovery logo. I even tried flashing TWRP, but also same result.
I can probably redo all the steps in my previous post, but once I boot to recovery the phone is done for it seems.
Any ideas?
Click to expand...
Click to collapse
Hmm, I don't know why is that happening. It's usually the custom recovery's fault in such case except if Pixel rom comes with its own prebuilt recovery that overwrites the one you installed.
I suggest you first to try to boot into system to see if it will work - in fastboot mode type the command fastboot reboot.
If this doesn't work then flash again fastboot rom to get the phone in working condition and after installing twrp FORMAT DATA in twrp Wipe section. Then install rom again.
Good luck, zaqm!
zaqm said:
Hmm, I don't know why is that happening. It's usually the custom recovery's fault in such case except if Pixel rom comes with its own prebuilt recovery that overwrites the one you installed.
I suggest you first to try to boot into system to see if it will work - in fastboot mode type the command fastboot reboot.
If this doesn't work then flash again fastboot rom to get the phone in working condition and after installing twrp FORMAT DATA in twrp Wipe section. Then install rom again.
Good luck, zaqm!
Click to expand...
Click to collapse
It worked!
Don't know why, but it's working. Here's what I did:
- In Fastboot Mode > fastboot reboot > booted to recovery, so no luck there
- Used MiFlash to flash the fastboot rom again (clean all)
- Setup the phone etc. and activated usb debugging
- Flashed TWRP
- Booted to TWRP
- Format Data
- Rebooted to TWRP
- Mounted Storage, uploaded ArrowOS.zip and installed it
- Wiped Dalvik/Cache
- Booted ArrowOS, and success!
Have done several reboots to (and from) system/recovery and it just works again, as it should.
I think the Format Data in TWRP did the trick. I remember in Orange Fox this all was a bit unclear; I'm just not used to Orange Fox, always used TWRP. So my bad for not correctly flashing the rom probably.
Again, thank you very much for your help! Have a great day! And let's hope this is the end of this issue haha.
FlashyDuck said:
It worked!
Don't know why, but it's working. Here's what I did:
- In Fastboot Mode > fastboot reboot > booted to recovery, so no luck there
- Used MiFlash to flash the fastboot rom again (clean all)
- Setup the phone etc. and activated usb debugging
- Flashed TWRP
- Booted to TWRP
- Format Data
- Rebooted to TWRP
- Mounted Storage, uploaded ArrowOS.zip and installed it
- Wiped Dalvik/Cache
- Booted ArrowOS, and success!
Have done several reboots to (and from) system/recovery and it just works again, as it should.
I think the Format Data in TWRP did the trick. I remember in Orange Fox this all was a bit unclear; I'm just not used to Orange Fox, always used TWRP. So my bad for not correctly flashing the rom probably.
Again, thank you very much for your help! Have a great day! And let's hope this is the end of this issue haha.
Click to expand...
Click to collapse
Maybe some glitch of OrangeFox recovery and yeah, let's hope that this issue won't appear anymore.
All the best, zaqm!