I have an old OP5T that is still on an older version of LOS, so I thought I'd start from scratch and first flash the Lineage Recovery instead of TWRP (an equally old version, but still working at this point).
USB debugging is active and OEM unlock enabled.
However, when I flash the image with
fastboot flash recovery lineage-17.1-20201229-recovery-dumpling.img
I get this output:
Sending 'recovery' (26685 KB) OKAY [ 0.698s]
Writing 'recovery' OKAY [ 0.252s]
Finished. Total time: 0.951s
First thing I found weird is how it took less than a second. Is it supposed to be that fast? It obviously did something:
When I try to boot to recovery now, I only get a black screen and a solid white notification LED (after the boot splash).
Same thing when I use the TWRP image instead: terminal shows it's finished in a second, but recovery wont boot afterward.
fastboot boot leads to the same black screen.
I tried it from two different computers, one with Fedora and the other with Windows; same thing happens on both.
The installed OS still works just fine, it's an old version though (and OTA updates don't work for some other reason).
Anyone have an idea what's wrong? What else could I try to get a working recovery?
Hi Mike
I had this very same issue. Regardless of what recovery (codeworkx, blu_spark, LOS etc.) I tried (I was on TWRP 3.2.x before) it always ended up with the solid white led. Eventually I got at least stock recovery from here working again (I was copying the recovery.img to internal storage, then booting to bootloader and went from there to recovery). This then allowed me to get adb sideload back so I could upgrade my old LOS 15.1 to OOS 10.0.1 (via 5.1.3, then 5.1.4, 5.1.7, 9.0.11 and finally 10.0.1). Once I was on the latest OOS I went back to fastboot bootloader and then flashed recovery with a more recent TWRP image (I took twrp-3.3.1-x_blu_spark_v9.101_treble-op5_op5t.img). Not sure if all those steps are actually required (I think you need at least 5.1.3 and 5.1.4 to get around this treble/vendor partition issue if you are on a version that didn't have the vendor partition yet) but this is how I got to a working TWRP recovery again. Hopefully this is of any help to you.
Cheers
Related
Maybe this is an obvious problem, but I couldn't find a solution neither searching Google nor XDA forums... hence this post here.
I'm trying to flash Android Revolution HD 6.2 Jelly Bean Custom Rom on HTC One X+ 1.17.401.1 using tutorial: how-to-install-android-revolution-hd-6-2-jelly-bean-custom-rom-on-htc-one-x-1-17-401-1 on theandroidrom site.
The prerequisites are:
1. Unlock my device using HTCDev account - which I did (the first line on the boot screen: *** UNLOCKED ***).
2. Install ClockWorkMod Recovery from a downloaded IMG file using fastboot - which doesn't seem to work on my device.
Code:
fastboot flash recovery recovery.img
says everything went OK. But when I reboot my device into recovery mode it just reboots or powers off. When I switch it on again, it just boots into Android (Sense).
I tried both: touch and regular IMG files for HTC One X (GSM) (there is no IMG file dedicated for HTC One X+ as I understand) from clockworkmod site:
1. recovery-clockwork-5.8.4.0-endeavoru.img
2. recovery-clockwork-touch-5.8.4.0-endeavoru.img
In both cases fastboot says everything went ok, but I cannot boot into recovery. Do I make some stupid mistake? (I'm a noob...)
Maybe it's also worth mentioning, that I rooted my device about a week ago using some tutorial on the web - I don't recall the adress anymore. It was on the factory 1.14.401.1 software version then. Root checker said, that the phone has root access. A few days later there was an OTA update to 1.17.401.1 software version, which I installed. Root checker says "no root access" now.
Did I mess something up?
Otherwise the phone works OK. My goal is just to install the Android Revolution ROM, hoping mainly for better battery life (is it reasonable? I already use JuiceDefender on balanced setting...)
Thanks in advance for any help.
Ok, this is weird...
Today I tried to flash the stock revovery for HTC One X+.
Fastboot said all went good, just like before:
Code:
C:\Android>fastboot flash recovery recovery_v.0.3.img
sending 'recovery' (6736 KB)...
OKAY [ 0.989s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.378s]
finished. total time: 1.379s
And now, when I boot into recovery mode, the first line says: "ClockworkMod Recovery v5.8.4.0"
This is the "touch" version as I presume, since menus can be navigated using touches (and volume/power buttons as well).
Someone can explain this to me, please?
Does it mean I can proceed with installing Android Revolution HD 6.2 now? (after proper backup of course)
So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Cortimi said:
So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Click to expand...
Click to collapse
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
someolddude said:
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
Click to expand...
Click to collapse
WiFi model, fastboot and adb are fine, no toolkits.
Cortimi said:
WiFi model, fastboot and adb are fine, no toolkits.
Click to expand...
Click to collapse
Get the toolkit by wugfresh and you should be able to restore it.
someolddude said:
Get the toolkit by wugfresh and you should be able to restore it.
Click to expand...
Click to collapse
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.283s]
finished. total time: 1.412s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 754455404 bytes
error: update package missing system.img
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
Click to expand...
Click to collapse
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Cortimi said:
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Click to expand...
Click to collapse
Same problem with mine, cm11 as well.
I like some of the CM features but ever device Ive flashed and had trouble with it has been when Ive went with "Cyanide Mod"
You figure something out, please let me know and I will do the same.
I've got the LTE but my daughter has the WiFi only and is also unlocked. I can make a bone stock backup of here's which is on 4.4.4 if you want to try and restore it to yours.
Hello,
I need some help, because I can't find any solution on my own.
Short story: I need to go back to stock rom and it doesn't work. I can't flash it via fastboot, and recovery mode doesn't work, because I can't use touch and CWM doesn't work either.
Long story:
This morning I wanted to install a Custom ROM, because I've got problems with RAM and touch lately. I heard that touch might be a software problem, so I thought this could solve it.
After several problems with installing Cyanogenmod, I finally made it, just to find out it doesn't find my sd card, which meant I couldn't load my backuped files onto my phone, which meant it was useless.
When I finally gave up on the sd card problem, I just wanted to go back to stock ROM. I also found out that touch doesn't seem to be a problem caused by software, because it doesn't even work in recovery mode.
So now I can't go back to stock ROM. I downloaded the original version from the Huawei Website.
FIRST WAY: Recovery mode.
I can't make a factory reset, because my touchscreen doesn't allow me to swipe, which is needed in TWRP. CWM doesn't work for me, I've tried it several times, but when I go to recovery mode, I only stay at the "huawei ascend" logo. So TWRP; but this doesn't work because of touch problems.
SECOND WAY: Fastboot.
This should work better. BUT:
for fastboot -w I get this error:
Code:
erasing 'cache'...
FAILED (remote: Command not allowed)
for fastboot erasing cache it's the same.
When I just ignore that and go by fastboot update [file], I get the following:
Code:
sudo fastboot update '/home/laura/Schreibtisch/root/HUAWEI_Y300_firmware%28Y300-0100%2CAndroid%204.1%2CEmotion_UI%2CV100R001C00B189%2CGeneral%20version%29.zip'
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
At the moment I have TWRP installed and no OS, because I can't flash any.
Please help me out! I'm sitting here for eight hours, it's in the evening in Germany and I need my phone.
Thanks!!!
Laura
Hi,
I had the bootloader unlocked on my 6.1 today.
Seemed to go well and guy was ver y professional.
Anyway connected my pc, and through adb rebooted to bootloader.
Phone entered download/fastboot mode.
Was recognised by my pc so I then booted into a temporary twrp - I got the image from the twrp site as compatible with the device.
Up came the twrp opening screen
--and that was that?
Did not go beyond this screen, and phone became completely unresponsive- not even holding power button for a minute helped.
Oh dear.
Fortunately, I left it for a couple of minutes and then held power and volume up for quite a while, and ''whew'' it booted fine, and is back to normal?
ANy ideas what I did wrong?
Many Thanks
pootler
pootler said:
Hi,
I had the bootloader unlocked on my 6.1 today.
Seemed to go well and guy was ver y professional.
Anyway connected my pc, and through adb rebooted to bootloader.
Phone entered download/fastboot mode.
Was recognised by my pc so I then booted into a temporary twrp - I got the image from the twrp site as compatible with the device.
Up came the twrp opening screen
--and that was that?
Did not go beyond this screen, and phone became completely unresponsive- not even holding power button for a minute helped.
Oh dear.
Fortunately, I left it for a couple of minutes and then held power and volume up for quite a while, and ''whew'' it booted fine, and is back to normal?
ANy ideas what I did wrong?
Many Thanks
pootler
Click to expand...
Click to collapse
Ok so quick update
I decided to use a different recovery
I was installing lineages 17, so used their recovery.
Everything worked fine?
HI,
I obtained a nokia 6.1 recently.
I had the bootloader unlocked.
I then went to flash the latest ( official) lineage 17
I did all the usual stuff ( i am not a stranger to installing custom roms ), and then tried to temporarily boot into twrp, in order to flash the lineage zip.
I was using the twrp as recommended on lineage site for this device ( nokia 6.1 TA 1050 )
For some reason, after using fastboot boot twrp.img, ( I renamed the image) the phone just booted back to android one screen.?
I could use power/vol up, to get out and back to existing installation, but nothing else.
I then tried temporarily booting the lineage recovery. ( according to the lineage installation instructions)
This involves using a combination of ''fastboot flash boot'' and hardware keys to get there
This worked fine - and I was able to sideolad the lineage zip.
Problem is, if I want to flash images , and do other stuff the lineage recovery cant, i need twrp ( even temporarily).
After installing lineage 17, I tried again to get into twrp, with the same (non) results.
I was wonderinfg if I was getting confused about slots.
I believed that booting twrp temporarily would boot to the right slot? - maybe not.
I then decided to do fastboot flash boot_a, ( etc, ) and then fastboot flash boot_b, ( etc ) to make sure it would boot off either slot. With hindsight, this was dumb
That got me twrp., but lost me the ability to boot into the lineage installation.
After a bit of a panic, I managed to get back to my lineage install.
I have tried since to temporarily boot twrp ( not to both slots ), and am still getting the same results- it boots to the android one screen, and just sits there.
But - if I try to get to recovery using the hardware buttons, I can get to Lineage recovery - which I find strange, because I thought official lineage packages did not install their recovery by default?
Makes me wonder when I thought I had booted lineage recovery temporarily, that maybe I hadn't, and I just booted into a pre installed recovery using the hardware method.
I am probably doing something stupid ( quite common for me ), can anyone enlighten me ?
Many Thanks
pootler
O.k
So I think I found a method in the thread below this - on the third page
I will chek iif it works
Pootler
pootler said:
O.k
So I think I found a method in the thread below this - on the third page
I will chek iif it works
Pootler
Click to expand...
Click to collapse
Yes - it appears that if you cannot boot into twrp temporarily , then this worked for me!
--at your own risk---
fastboot flash recovery <filename>.img
This will FAIL - but ignore and then right after,
fastboot boot <filename> .img
Voila - boots into TWRP temporarily.
Cheers
pootler
I wanted to ask what firmware you are running because I am having the exact same issue on my Pixel 3. I tried the final method you outlined but no luck. I'm running stock Android 10 build QQ3A.200805.001. I have the google USB driver from the platform sdk tools installed, I have ADB added to my $Path.
fastboot boot C:\twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.251s]
Booting OKAY [ 3.451s]
Finished. Total time: 3.784s
Something strange happens, it looks like the reboot to TWRP screen comes on for an instant before going to the unlocked bootloader warning message. Then it proceeds to boot into the android screen instead of the recovery. No idea why, could it be the ADB drivers?
MigueTK said:
I wanted to ask what firmware you are running because I am having the exact same issue on my Pixel 3. I tried the final method you outlined but no luck. I'm running stock Android 10 build QQ3A.200805.001. I have the google USB driver from the platform sdk tools installed, I have ADB added to my $Path.
fastboot boot C:\twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.251s]
Booting OKAY [ 3.451s]
Finished. Total time: 3.784s
Something strange happens, it looks like the reboot to TWRP screen comes on for an instant before going to the unlocked bootloader warning message. Then it proceeds to boot into the android screen instead of the recovery. No idea why, could it be the ADB drivers?
Click to expand...
Click to collapse
HI,
I am sorry but my knowledge is really limited in this area - I wish you luck
pootler said:
HI,
I am sorry but my knowledge is really limited in this area - I wish you luck
Click to expand...
Click to collapse
Thanks for the reply, I still haven't figured it out and am running a manually patched boot image for magisk without a recovery, fastbootd is "enough". Another weird thing is If I installed a custom Rom certain pixel features would be lost such as the OCR and lens integration into the recents menu, pixel stand standby and wallpapers. I love the features of a custom Rom but the overview copy and paste functions are a must have for me.
Well, I use Raghu Varma's unofficial TWRP. It works like a charm, I've had no issues with it so far. Just be careful to choose the correct one between the build for Android 10 and the one for Android 11 -- I think that got me into trouble once, can't remember clearly.
Hi folks,
I got a problem while flashing lineage OS on my brand new OnePlus 9 Pro (LE2120). I was using the installation guide of DroidWin but instead of using MS Windows I used Ubuntu (according to the installation guide from lineage the PC-OS doesn't matter). Well, everything worked fine so far until Step 5: I flashed the lineage-18.1-20211005-recovery-lemonadep.img and once I did the lineage recovery told me I must apply a factory reset. Than my phone freezed on the first attached screen....
In order to solve this problem I switched to TWRP recovery. From the TWRP recovey I sideloaded the copy-partitions-20210323_1922.zip file . This works, at the end the error 'Unable to find partition for path "/cache" ' occurs. In TWRP I switched to the manu 'wipe > format data > factory reset' and the phone crashed. Now my phone is detected by fastboot, but I cant' reach the recovery. Flashing TWRP again ends up with
Code:
fastboot boot TWRP-3.5.2-lemonadep-Nebrassy.img
downloading 'boot.img'...
OKAY [ 6.379s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 6.382s
so I stay at the last attached screen on my phone and I do not get further. From this screen the recovery doesn't start. Thanks a lot in adavance !
Try fixing the phone with MSMDownloadTool and try it again. After you successfully got it, set up OxygenOS. After that, try installing Lineage again.
Thanks a lot Martinez74,
Red Prez16 said:
Try fixing the phone with MSMDownloadTool and try it again. After you successfully got it, set up OxygenOS. After that, try installing Lineage again.
Click to expand...
Click to collapse
Thanks a lot Red Prez16,
I did it the way you recommended and it works !
hshl1968 said:
Thanks a lot Martinez74,
Thanks a lot Red Prez16,
I did it the way you recommended and it works !
Click to expand...
Click to collapse
Well, I'm glad it worked out! Yeah, it's weird like that. Like you can flash TWRP, but touch won't work until you setup OxygenOS again.