EDIT: I encountered numerous problems in installing CM13 on Z5C, but a solution is already written here, and it's better than what I could write (because me no good english
Also the problem as explained below is determined only by a wrong environment, in which I blindly flashed uncompatible SW.
Hello, as in title I cannot get "fastboot flash recovery recovery.img" command to work.
This is what terminal gives me:
C:\adb>fastboot flash recovery TWRP-3.0.0.0-suzuran-v2.img
sending 'recovery' (21760 KB)...
OKAY [ 0.756s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.943s
Click to expand...
Click to collapse
Despite the lack of errors the phone is completely unaffected, there's no way I can enter recovery but flashing with "fastboot flash boot", which is improper and so OS loading is broken (it boots only the recovery).
EDIT: I then discovered that's normal behaviour, and that I wasn't able to boot in recovery normally because I flashed Marshmallow SW on Lollipop
I wasn't able to find a solution on the internet, I hope someone can help me.
Z5C E5823, Win7, adb and fastboot are OK
davidbevi said:
Hello, as in title I cannot get "fastboot flash recovery recovery.img" command to work.
This is what terminal gives me:
I wasn't able to find a solution on the internet, I hope someone can help me.
Z5C E5823, Win7, adb and fastboot are OK
Click to expand...
Click to collapse
There's nothing wrong here? Looks successful to me.
civicsr2cool said:
There's nothing wrong here? Looks successful to me.
Click to expand...
Click to collapse
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
davidbevi said:
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
Click to expand...
Click to collapse
You might want to re-download the TWRP and flash it again. You might be that one in a million person who have a corrupted downloaded file.
davidbevi said:
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
Click to expand...
Click to collapse
Download twrp 3.0.2, you're using the wrong one. Also if you use flash tool you can hotboot the recovery to get into it if you don't have a custom kernel that will allow you to get into recovery.
firdyRAY said:
[...] corrupted downloaded file.
Click to expand...
Click to collapse
I doubt because I tried 3 different packages, and every single one works, just I have to flash it unproperly. I would follow your advice anyway if it wasn't for:
civicsr2cool said:
Download twrp 3.0.2 [...]
Click to expand...
Click to collapse
This is the only thing I found googling, can you please give me a link or more info?
I managed to get TWRP v2.8.7.0 on my phone.
I'd like to write a solution on the original post, so those who have my problem also have my solution, but I have to know better:
1) the TWRP I installed comes from a zip containing boot.img and recovery.img
2) flashing both ("fastboot flash boot boot.img" & "fastboot flash recovery recovery.img") did the job
My guess is that you need a piece of code that IS the recovery and a piece of code that MAKES the recovery ACCESSIBLE. If this is the case I don't get how I was able to boot into recovery when flashed on boot. I am confused!
davidbevi said:
I managed to get TWRP v2.8.7.0 on my phone.
I'd like to write a solution on the original post, so those who have my problem also have my solution, but I have to know better:
1) the TWRP I installed comes from a zip containing boot.img and recovery.img
2) flashing both ("fastboot flash boot boot.img" & "fastboot flash recovery recovery.img") did the job
My guess is that you need a piece of code that IS the recovery and a piece of code that MAKES the recovery ACCESSIBLE. If this is the case I don't get how I was able to boot into recovery when flashed on boot. I am confused!
Click to expand...
Click to collapse
twrp 3.0.2
https://www.androidfilehost.com/?fid=24499762636001943
twrp 3.0 and up is for marshmallow, anything below is lollipop. the boot.img is your kernel, like i said before you need to have a custom kernel to access twrp or hotboot it every time you need it. if you're running marshmallow with a lollipop kernel idk how well that will work out for you in the long run. to understand why you need the boot.img kernel i suggest looking up sony ric.
civicsr2cool said:
twrp 3.0.2
https://www.androidfilehost.com/?fid=24499762636001943
twrp 3.0 and up is for marshmallow, anything below is lollipop. the boot.img is your kernel, like i said before you need to have a custom kernel to access twrp or hotboot it every time you need it. if you're running marshmallow with a lollipop kernel idk how well that will work out for you in the long run. to understand why you need the boot.img kernel i suggest looking up sony ric.
Click to expand...
Click to collapse
Thanks a lot, I was able to determine that my problem was caused by a ROM that is too old for what I was trying.
I was trying to install CM13 following CTXz's guide, but I had no idea I had to start from Marshmallow (and it's not written).
davidbevi said:
Thanks a lot, I was able to determine that my problem was caused by a ROM that is too old for what I was trying.
I was trying to install CM13 following CTXz's guide, but I had no idea I had to start from Marshmallow (and it's not written).
Click to expand...
Click to collapse
its in the thread somewhere towards the middle because i tested lollipop to cm13 and got nowhere fast as well.
edit:it says in op that required firmware is 6.0 fwiw
Related
Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Marcusprit said:
Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Click to expand...
Click to collapse
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
es0tericcha0s said:
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
Click to expand...
Click to collapse
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Marcusprit said:
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Click to expand...
Click to collapse
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
es0tericcha0s said:
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
Click to expand...
Click to collapse
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Marcusprit said:
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Click to expand...
Click to collapse
Your device boots and is already rooted, right? If so, try to flash the updated img files with : https://play.google.com/store/apps/details?id=com.cgollner.flashify
recovery
Thank you I now have recovery
Marcusprit said:
Thank you I now have recovery
Click to expand...
Click to collapse
OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.
I'm trying to flash twrp.I have gone step by step I can't think of anything that I forgot to do, I did everything that was mentioned here and other places even my device is detected in both adb & fastboot.but I can't flash twrp
I tried these:
1-adb devices
returned a serial number
2-rebooted to bootloader using:
adb reboot bootloader
3-fastboot devices
returned device id(I think)
4-fastboot flash recovery.img
returned error
5-fastboot flash recovery recovery.img
returned error either "command not allowed" or "Operation is not permited"
6-Different combinations of above commands plus flashing command
What is flashing .... in fastboot.It doesn't work. It acts like an unknown command. Does anyone know how to use it correctly? Help of fastboot didn't help
(Attached screenshots=CMD:Command Line in Windows,SCL-U31:My phone screen in fastboot mode)
See it for yourself in screenshot please
Thanks in advance!
P.S I read a lot of other threads,I Couldn't Find anything that helped me solving the problem,So,Any further idea?
No luck still
Guys I'm tryings to flash an stupid twrp recovery or at least get back to original recovery(All firmware packages are in UPDATE.app format and I can't flash it since It says "recovery image verification failed) . System needs its original recovery to do factory reset,right?
Tell me where to go!!!
Any luck? At least please tell me where to go!! I even mentioned it in a lot of other related xda threads they simply tell me it's a stupid OFF Topic replay or thread. I might be a junior member in xda but it's been years that I worked with a lot of phones and now I'm pretty experienced. Bad luck of mine I damaged my note 3 and got this stupid Y6. It was hard to root unlocking bootloader and now I can't flash twrp in fastboot or whatever. Wishing there was a proper tool like odin for devices like this so it was easy to flash twrp. Anyway.
HELP ME PLEASE!!
flightover588 said:
Any luck? At least please tell me where to go!! I even mentioned it in a lot of other related xda threads they simply tell me it's a stupid OFF Topic replay or thread. I might be a junior member in xda but it's been years that I worked with a lot of phones and now I'm pretty experienced. Bad luck of mine I damaged my note 3 and got this stupid Y6. It was hard to root unlocking bootloader and now I can't flash twrp in fastboot or whatever. Wishing there was a proper tool like odin for devices like this so it was easy to flash twrp. Anyway.
HELP ME PLEASE!!
Click to expand...
Click to collapse
What error gave you when you tried to do this command "fastboot flash recovery twrp.img"
Be sure to have usb debugging enabled.
Thespartann said:
What error gave you when you tried to do this command "fastboot flash recovery twrp.img"
Be sure to have usb debugging enabled.
Click to expand...
Click to collapse
Of course I did. And also device is being detected in both adb and fastboot.
As I already mentioned I used flash recovery recovery.img(or twrp.img I have two versions of recovery that I can flash)
The error is=remote operation is not allowed or sometimes operation is not permitted(which seems to have same meaning )
flightover588 said:
Of course I did. And also device is being detected in both adb and fastboot.
As I already mentioned I used flash recovery recovery.img(or twrp.img I have two versions of recovery that I can flash)
The error is=remote operation is not allowed or sometimes operation is not permitted(which seems to have same meaning )
Click to expand...
Click to collapse
OK then.
You can root your device with kingroot/kingoroot, it worked in the past for Huawei Y6, after you rooted your device install flashify and press on "Recovery image" after you granted root access to the app.After that click on select file, download this recovery for y6: https://www.androidfilehost.com/?fid=962187416754472815 and flash the recovery with Flashify.
Done!
I am not responsible for Bricked devices!
After you done all of that you can flash an custom ROM and I recommend to root with magisk. Always make an backup when flashing a ROM!
If I helped a Thanks is appreciated
Thespartann said:
OK then.
You can root your device with kingroot/kingoroot, it worked in the past for Huawei Y6, after you rooted your device install flashify and press on "Recovery image" after you granted root access to the app.After that click on select file, download this recovery for y6: https://www.androidfilehost.com/?fid=962187416754472815 and flash the recovery with Flashify.
Done!
I am not responsible for Bricked devices!
After you done all of that you can flash an custom ROM and I recommend to root with magisk. Always make an backup when flashing a ROM!
If I helped a Thanks is appreciated
Click to expand...
Click to collapse
You uploaded a twrp recovery on AFH just for me? Thank you,man!I appreciate your help. I really do! But Believe it or not I already tried flashify,Rashr and flashfire. These three cause same thing,when I reboot to recovery it says "recovery image verification failed"Then quickly goes to fastboot&rescue mode where I can't still flash twrp using flash command. Referring to firstb post
flightover588 said:
You uploaded a twrp recovery on AFH just for me? Thank you,man!I appreciate your help. I really do! But Believe it or not I already tried flashify,Rashr and flashfire. These three cause same thing,when I reboot to recovery it says "recovery image verification failed"Then quickly goes to fastboot&rescue mode where I can't still flash twrp using flash command. Referring to firstb post
Click to expand...
Click to collapse
Not nice to hear that.
What you could try to do is:
Factory reset/Install an update.app made for SCL-U31 from recovery
Enable Usb debugging again
Reinstall usb drivers (HiSuite)
Lock&Unlock your bootloader again
Try to flash TWRP
Im happy if this worked and i am sorry if i wasted your time, sometimes this happens if you don't have HiSuite installed.
You could try this too:
adb reboot bootloader
adb kill-server
fastboot flash recovery recovery.img
fastboot reboot
Attention, install HiSuite to your PC, Connect the Phone to the PC with the cable, make sure You have usb debbuing is enabled and accept any dialogs that show in your home screen(They do not show on lockscreen) wait so HiSuite installs on the phone(An dialog should show up on the PC) and try flashing TWRP again.
Good luck
flightover588 said:
Guys I'm tryings to flash an stupid twrp recovery or at least get back to original recovery(All firmware packages are in UPDATE.app format and I can't flash it since It says "recovery image verification failed) . System needs its original recovery to do factory reset,right?
Click to expand...
Click to collapse
Is your boatloader unlocked?
You can find about by typing
fastboot oem devices-info
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
orthen2112 said:
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
Click to expand...
Click to collapse
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
trax7 said:
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
Click to expand...
Click to collapse
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
orthen2112 said:
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
Click to expand...
Click to collapse
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
trax7 said:
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
Click to expand...
Click to collapse
I have to admit I didn't understand very much in those to sentences.
trax7 said:
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Click to expand...
Click to collapse
Any ideas where else I can look
trax7 said:
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
Click to expand...
Click to collapse
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
orthen2112 said:
I have to admit I didn't understand very much in those to sentences.
Any ideas where else I can look
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
Click to expand...
Click to collapse
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
trax7 said:
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
Click to expand...
Click to collapse
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
orthen2112 said:
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
Click to expand...
Click to collapse
Glad I helped! The mods can close the thread now, I guess.
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
fetchaspade said:
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
Click to expand...
Click to collapse
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
trax7 said:
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
Click to expand...
Click to collapse
Thank you for your answer, sorry I did not notice.
My bootloader was indeed unlocked and I had adb + fastboot (on a linux distribution, never had to fetch specific drivers). In the end I tried to use flashtool to flash the stock Android L rom I had used for the downgrade (to backup the TA with the DRM keys before unlocking bootloader) which worked (I could not flash only the kernel image on boot). Then I tried again to boot on TWRP directly from fastboot mode without flashing anything: same error. I then downloaded a few recent stock Android N roms from xperifirm which flashtool could not unzip for some reason, then I found an Australian image elsewhere, and this time flashtool would accept it. So, back to Android N, I tried to flash TWRP again and it worked at last. I'm now running on the Lineage14.1+microG rom (so much better than stock roms I still can't believe it).
I guess TWRP, including old versions I tried, would not boot along the stock Android L rom that was currently flashed so I had to upgrade beforehand. I hope this will help people in the future.
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
elfae said:
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
Click to expand...
Click to collapse
Ofc that the latest recovery wont work for an Android version it wasn't made for (it would probably work on Marshmallow but Lollipop is too old). A different recovery would work there, the old zxz recovery if i remember correctly.
Also you can fastboot boot the recovery image directly.
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
elfae said:
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
Click to expand...
Click to collapse
You dont *have to* backup TA... It's only to preserve your original keys if you want. All of the custom kernels here emulate them anyway if you dont have the backup and LOS doesn't benefit from them at all.
**XT2041-4**
hey folks,
i have the gpower/g8power (XT2041-4) and i was able to unlock the bootloader and i have been able to do the fastboot commands but it fails when i do the fastboot system, product, vbmeta commands for the crdroid, lineage and havok. i got into twrp and tried installing the zips for those roms but those failed too.
i got to the android OS start screen but the touchscreen is unresponsive. i have looked through a lot of the threads for this device and can't find anything that works.
any help will be much appreciated because this is my daily driver.
edit: title should be XT2041-4
your best option would be to connect an otg cable, ( best is to make sure you can have a double connection, one for mouse , on connected to the pc) then get into the phone with the non-touchscreen booted rom, connect it to LMSA , and extract the boot.img image that comes with the rom LMSA downloads. you should have a working touchscreen with the version LMSA downloads .
Reason you need a double connection: you need to accept the connection to your pc from the phone
you could also browse to the settings --> about this phone and take a look at the exact ROM that is installed, and find that image on lollinet , then extract and boot the boot.img from that rom.
Hey, I'm having the same problem but I found a workaround.
you can either go in fastboot mode and enter
fastboot set_active b
or go in TWRP and change the active slot to B then proceed to boot up the phone.
In my case, it showed warning saying "cannot boot into system......file maybe corrupted" etc etc, just choose "factory reset" on that screen and your phone should boot into slot B with stock ROM.
That way you can have a functional phone while waiting for the developers to figure out the kernel problem
Cheers
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
Chosimise said:
waiting for the developers to figure out the kernel problem
Cheers
Click to expand...
Click to collapse
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
I had a completely different issue with the exact same model. I made a post here asking if anyone had an easy fix, but my guess is that these are just growing pains. Give it a couple months and the roms will likely be much more stable. One of the reasons I bought this phone in the first place is because it usually gets official Lineage OS support at some point. With time, I'm sure things will work great. If you use Windows, going back to stock everything is pretty dead simple with the Lenovo Rescue and Recovery tool, so you can kind of experiment safely if you back everything up.
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
After some tinkering, I actually figured out my problem. There's a big difference between "fastboot mode" (the one you enter by pressing power and vol-) and "Fastbootd" mode.
I did all my flashing in "fastboot mode" and I got no touch screen afterward.
Then there's another hiccup for me (which is why I didn't go in "fastbootd" mode in the first place): When I type in the command in regular "fastboot mode"
Code:
fastboot reboot fastboot
I got an error message saying "reboot fastboot" is not a valid destination or something down those lines.
The problem being, they only added that option in fastboot version r30, so I had to update my ADB and fastboot environment.
And I ran into yet another problem, no matter what I do, the fastboot command is still run with the older version. I guess I messed up the previous installation and the pathing got messy. I ended up using my work laptop for a clean installation of all drivers and it finally solved my problem. I guess I'm saying you need to clean up previous adb and fastboot drivers before using the new ones, especailly if you installed it systemwise.
Anyways, after I booted into "fastbootd" mode and flashed everything with the latest version of fastboot driver, the phone worked flawlessly.
Hope it helps!
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
uglyaf said:
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
Click to expand...
Click to collapse
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Beetle84 said:
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Click to expand...
Click to collapse
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
uglyaf said:
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
Click to expand...
Click to collapse
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Beetle84 said:
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Click to expand...
Click to collapse
ok thanks i did that and got version 1.4.3 it sees my device but when i did the fastboot reboot fastboot i got
fastboot: usage: unknown reboot target fastboot
and nothing happened. does anyone know what that means?
ok yes indeed im a huge idiot. i finally got into fastbootd because i downloaded ADB version R30. THATS the most recent adb version and that did the trick! now i got the fastbootd recovery screen!
regardless, thank you all SOOOOO much for taking the time to respond. much appreciated.
im so excited to get flashing!
peace and love
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
brucedroid031 said:
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
Click to expand...
Click to collapse
good look thank you