100% working TWRP recovery.. my first port but everything works amazing
Thank You Sir!
Edit - Flashed and works good so far; boots anyway; ill test more and repost in awhile
Flashed it to device and it works use gravity box to get advance power menu but everything is working just need to get read write in it would be nice any ideas been trying
svoc said:
Flashed it to device and it works use gravity box to get advance power menu but everything is working just need to get read write in it would be nice any ideas been trying
Click to expand...
Click to collapse
Is this the only missing feature, R/W capabilities for all device partitions or only for a few of them?
I'm assuming you are referring to a permanent setting to allow R/W permissions for /system and not an all encompassing problem of this TWRP image lacking that? In other words, nandroid backups are working?
No rw anywhere not even in Android or twrp but everything else works of this twrp it can be flashed to the device too
No but there's a thread in here with an app called super repack and you'll actually have to hook it up to a computer for this one but it works and it unpacks and repacks your super partition on the Android just follow the directions.. and I have an updated recovery file because the old one the fastboot didn't work
My system product and vendor is RW capable now.. so don't tell me it can't be done
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
That is the link to the super repack thread
tbirdguy said:
Thank You Sir!
Edit - Flashed and works good so far; boots anyway; ill test more and repost in awhile
Click to expand...
Click to collapse
You might want to download the updated image I uploaded.. the fast boot works on this one.. it's hell learning how to get fast boot and MTP to work when you are teaching yourself
svoc said:
Flashed it to device and it works use gravity box to get advance power menu but everything is working just need to get read write in it would be nice any ideas been trying
Click to expand...
Click to collapse
mario0318 said:
Is this the only missing feature, R/W capabilities for all device partitions or only for a few of them?
I'm assuming you are referring to a permanent setting to allow R/W permissions for /system and not an all encompassing problem of this TWRP image lacking that? In other words, nandroid backups are working?
Click to expand...
Click to collapse
svoc said:
No rw anywhere not even in Android or twrp but everything else works of this twrp it can be flashed to the device too
Click to expand...
Click to collapse
svoc said:
Flashed it to device and it works use gravity box to get advance power menu but everything is working just need to get read write in it would be nice any ideas been trying
Click to expand...
Click to collapse
Look at the time on the picture if you think I'm lying
Ok I can get it to work but my device will not boot after words but it has rw in twrp and if I just do product I loose all settings and your new twrp adb is not working and if you try to bring a back up over 4gb it fails
Can you tell me what steps you took to get it done I have tried over 10 times having to reflash each time
are you able to share the source so I can attempt to build this for g10/capri?
Hi bro, thanks for your help porting TWRP, I've flashed the recovery succesfully but the touchscreen doesn't work, so I can't type anything on the screen.
I used this code to flash the recovery on fastboot mode:
Code:
fastboot flash recovery_a MotoGuamnaFixed2.img
fastboot flash recovery_b MotoGuamnaFixed2.img
fastboot reboot recovery
When the recovery starts, I get stuck on the password screen.
rogjr1986 said:
100% working TWRP recovery.. my first port but everything works amazing
Click to expand...
Click to collapse
how do i install it
All right so you download your recovery hook your phone up to the computer in fastboot mode and open up your command prompt on your computer you should have ADB and fastboot installed type into the command prompts fastboot flash recovery name.img
Do I need to unlock bootloader?
I am getting
target reported max download size of 798511104 bytes
sending 'recovery_a' (35428 KB)...
OKAY [ 0.836s]
writing 'recovery_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.922s
Related
hello I used the Revolutionary to achieve s-off and install clockwork recovery, then my phone booted up and update the prl and hands free and such. now when i boot into the bootloader if i select recovery it goes to the HTC logo screen and does nothing and if i even just try to power on my device same screen HTC logo only thing i can do is volume down and power to access bootloader
spinx1337 said:
hello I used the Revolutionary to achieve s-off and install clockwork recovery, then my phone booted up and update the prl and hands free and such. now when i boot into the bootloader if i select recovery it goes to the HTC logo screen and does nothing and if i even just try to power on my device same screen HTC logo only thing i can do is volume down and power to access bootloader
Click to expand...
Click to collapse
recovery didnt flash, you arent bricked. just flash team win project recovery
Definitely not bricked, you probably just scared a whole bunch of people.
Follow this i had the same issue http://forum.xda-developers.com/showthread.php?t=1192245
when i open the fastboot.exe the adb shell windows (dos) opens and closes extremly fast no idea what it said
some people need to learn the definition of Bricked.
Bricked= exactly that the phone is now good for. a brick. (A.K.A: paperweight, doorstop, etc.) lol
yeah, just do what the others of told you, you'll get it squared away.
smokin1337 said:
Follow this i had the same issue http://forum.xda-developers.com/showthread.php?t=1192245
Click to expand...
Click to collapse
i followed instructions and flashed the recovery thru fastboot usb in the bootloader but still nothing
http://imageshack.us/photo/my-images/52/18712672.jpg/
spinx1337 said:
i followed instructions and flashed the recovery thru fastboot usb in the bootloader but still nothing
http://imageshack.us/photo/my-images/52/18712672.jpg/
Click to expand...
Click to collapse
Take out flash_image and replace with just "flash" <---No Quotes!
did you download fastboot from htc site? do you have sdk downloaded? i had same issue. cwm didnt take. i flashed teamwins no issues at all.
HSadler93 said:
Take out flash_image and replace with just "flash" <---No Quotes!
Click to expand...
Click to collapse
if i do that i get
unknown partition 'recovery-twrp-shooter-1.0.0.img'
error: cannot determine image filename for 'recovery-twrp-shooter-1.0.0.img'
spinx1337 said:
if i do that i get
unknown partition 'recovery-twrp-shooter-1.0.0.img'
error: cannot determine image filename for 'recovery-twrp-shooter-1.0.0.img'
Click to expand...
Click to collapse
Is your file called "recovery-twrp-shooter-1.0.0.img"? Also is it in the same folder as ADB/Fastboot?
okay finally got the image to flash start to send once on writing image fails remote partition does not exist
had to type
fastboot flash image recovery-twrp-shooter-1.0.0.img in the cmd prompt
HSadler93 said:
Is your file called "recovery-twrp-shooter-1.0.0.img"? Also is it in the same folder as ADB/Fastboot?
Click to expand...
Click to collapse
yes same directory
spinx1337 said:
okay finally got the image to flash start to send once on writing image fails remote partition does not exist
had to type
fastboot flash image recovery-twrp-shooter-1.0.0.img in the cmd prompt
Click to expand...
Click to collapse
It is
fastboot flash recovery recovery-twrp-shooter-1.0.0.img
that you need to type in cmd. You have to tell it where to flash (in this case the recovery partition).
Let me know if that works for you.
thanks for your help now i have recovery working my phone still wont boot up ill have to find a factory rom on the web
Your welcome. Glad I could help!
There is a rom in the development section. Not sure if it works though. You could run the RUU and then redo everything now that you know exactly how.
Have you tried a factory reset from the bootloader after getting the recovery to work?
just did a factory reset thru TWRP and its stuck on the HTC logo screen trying to boot up same issue as earlier Im not sure why my phone will not boot up. seems like only thing i can do is access the bootloader
How long do you wait before you decide it wont boot?
10-15 minutes should i wait longer?
Nah, that should be good. http://forum.xdadevelopers.com/showthread.phpt=1092957&highlight=ruu
Do this then the whole process over.
As the title states here are the 4.4.4 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system
MD5HASH: 49aa7777a1c60fc6742f12c2a31f1cdf
Size: 481 MB
Type: disk dump (compressed 7z)
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it... It was the other guy... I swear.... Flash at your own risk
DooMLoRD said:
As the title states here are the 4.4.4 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system [UPLOADING]
MD5HASH: 49aa7777a1c60fc6742f12c2a31f1cdf
Size: 481 MB
Type: disk dump (compressed 7z)
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it... It was the other guy... I swear.... Flash at your own risk
Click to expand...
Click to collapse
Hi DOOMLORD!
All users are waiting UPLOADING dump GPE 4.4.4 System!
P.S. Kernel now ported
scrubber said:
Hi DOOMLORD!
All users are waiting UPLOADING dump GPE 4.4.4 System!
P.S. Kernel now ported
Click to expand...
Click to collapse
stupid asymmetric ADSL speeds... get 4 MBPS download and only 256KBPS upload :crying::crying:
restarted uploaded twice yesterday...
will try again today
DooMLoRD said:
stupid asymmetric ADSL speeds... get 4 MBPS download and only 256KBPS upload :crying::crying:
restarted uploaded twice yesterday...
will try again today
Click to expand...
Click to collapse
Ok. Will arrange topic
scrubber said:
Ok. Will arrange topic
Click to expand...
Click to collapse
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
DooMLoRD said:
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
Click to expand...
Click to collapse
No problem, any source and can parts
DooMLoRD said:
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
Click to expand...
Click to collapse
We can wait
joluke said:
We can wait
Click to expand...
Click to collapse
scrubber said:
No problem, any source and can parts
Click to expand...
Click to collapse
done
https://mega.co.nz/#!4RNx0Jaa!trTgJIXt8bB9R8LW6z3IVejSRV0MfqNvviD769UUsDo
@DooMLoRD
Have you seen a XZU GPe get stuck and be unable to flash the boot partition? I get this every time I attempt to flash it.
Code:
[[email protected] 4.4.4 Stock Rooted]# fastboot flash boot boot_4.4.4.img
sending 'boot' (20480 KB)...
OKAY [ 2.462s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 2.466s
Now before we all start screaming bad download, here's the list of things that I've tried...
I've tried multiple boot images from various sources, validating md5 sums accordingly. I even tried the restoration procedure from your thread about restoring to stock.
I've tried to erase the partition using fastboot (which doesn't return an error) but I still can't flash after that.
I've tried using a different OS with fresh drivers. I normally run on a Fedora 20 box but I've tried on Windows 7 using Flashtool as well.
I've tried to wipe & clear cache. (Didn't think this would help, but what the hell?)
Anyway, I'm out of ideas. Any thoughts would be greatly appreciated.
And thank you for all of your hard work on the Xperia line. I've appreciated all of the posts in this forum, the system images and tutorials, as well as the custom recoveries!
Update : flashing boot.img from CM11 works fine. Clearly I'm missing something about how to flash the boot partition on this device. Apparently not all boot.img files are created equal...
Update 2 : I can flash the Advanced Stock Kernel with Dual Recovery without issue, so I'm going to flash my way back to 4.4.3 and go from there.
Fixed! : In the end, it was because I was using an ELF image and fastboot didn't like flashing it for some reason. I reverted my phone back to 4.4.3 using the stock system.img and FOTAKernel.img, then used the Advanced Stock Kernel with Dual Recovery, since they were all flashable via fastboot. Once the system was up, I used adb to push the 4.4.3 stock boot.img to the device and the did an adb shell, su'ed to root, and dd'it onto the boot device. Rebooted, OTA'ed it to 4.4.4. Done.
What a night. This is what I get for starting this project late...
Has anyone with a broken camera tried flashing this image?
Does the camera work in 4.4.4 after the flash?
Sorry for the newbie question, but what is the proper way to flash these files?
This is what I tried:
fastboot flash system <system.img>
fastboot flash boot <boot.img>
fastboot flash FOTAKernel <FOTAKernel.img>
I got an error for the boot.img (same error as ekrunch), but system and FOTAKernel successfully flash.
This is my first Sony device, so not too familiar with flashing this type of phone.
Thanks,
Matt
pudgewack said:
Sorry for the newbie question, but what is the proper way to flash these files?
This is what I tried:
fastboot flash system <system.img>
fastboot flash boot <boot.img>
fastboot flash FOTAKernel <FOTAKernel.img>
I got an error for the boot.img (same error as ekrunch), but system and FOTAKernel successfully flash.
This is my first Sony device, so not too familiar with flashing this type of phone.
Thanks,
Matt
Click to expand...
Click to collapse
Forgive the long post, I'm sure some of this is repetitive, just trying to be complete for those who don't.
Sounds like you have the same exact problem as mine. Something about restoring an ELF image to the boot partition via Fastboot isn't working. Weird.
Alright, get ready to have some fun!
Get your device working again. I recommend using the 4.4.3 system.img/FOTAKernel.img and DooMLord's Advanced Stock Kernel with Dual Recovery. Worked like a charm for me. Get the 4.4.3 images from here and the kernel from here. Use "fastboot flash" accordingly for these 3 images. Note: The reason I use the custom kernel is b/c the 4.4.3 boot.img didn't flash correctly either.
Now you're running on 4.4.3 again, rooted. If you wiped data, don't bother signing in to your Google account, we're going to wipe again.
Now on to 4.4.4...
Okay so what we're going to do now is flash the boot.img for 4.4.4 on your running 4.4.3. Once you do this, the device probably won't boot Android again without some flashing in the boot loader, so brace yourself. :laugh:
First up, push the boot image to your device. You can do that with an ADB push, or ES File Explorer's handy FTP server, or just download the image with the phone. I used the 4.4.4 images from here. Get the boot-4.4.4.img on your device somehow and leave the system-4.4.4.img and FOTAKernel-4.4.4.img on your PC.
Code:
## [I](Not sure if you need the full path, I didn't push it this way)[/I]
adb push boot-4.4.4.img /storage/sdcard0/Download
Get a shell going
Code:
adb shell
Now that you're in the shell on your device, change to the right directory on the device, and copy the ELF image to the raw device using DD. (Everybody get your UNIX party hat out, we're going old school...)
Code:
su -
cd /storage/sdcard0/Download
dd if=boot4.4.4.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Alright, you have a 4.4.4 boot image. Now get back to the boot loader.
Code:
adb reboot-bootloader
And now it's time to get those 4.4.4 images onto the system. I'd highly recommend a good wipe of data/cache while you're at it. ("fastboot -w" will do this for you.)
Code:
fastboot flash FOTAKernel FOTAKernel-4.4.4.img
fastboot flash system system-4.4.4.img
That should do it. Reboot, lock on to your Google account, then fire up the developer's menu and crank up ART, then enjoy your device on 4.4.4. (BTW, this still didn't fix my camera. :crying: )
Good luck everyone! Hope this helps someone out. And would somebody please chime in with the simple command that I'm missing that fixes this problem and avoids all of this foolery?
ekrunch said:
Forgive the long post
Click to expand...
Click to collapse
Nice, well explained post.
ekrunch said:
@DooMLoRD
Have you seen a XZU GPe get stuck and be unable to flash the boot partition? I get this every time I attempt to flash it.
Code:
[[email protected] 4.4.4 Stock Rooted]# fastboot flash boot boot_4.4.4.img
sending 'boot' (20480 KB)...
OKAY [ 2.462s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 2.466s
Now before we all start screaming bad download, here's the list of things that I've tried...
I've tried multiple boot images from various sources, validating md5 sums accordingly. I even tried the restoration procedure from your thread about restoring to stock.
I've tried to erase the partition using fastboot (which doesn't return an error) but I still can't flash after that.
I've tried using a different OS with fresh drivers. I normally run on a Fedora 20 box but I've tried on Windows 7 using Flashtool as well.
I've tried to wipe & clear cache. (Didn't think this would help, but what the hell?)
Anyway, I'm out of ideas. Any thoughts would be greatly appreciated.
And thank you for all of your hard work on the Xperia line. I've appreciated all of the posts in this forum, the system images and tutorials, as well as the custom recoveries!
Update : flashing boot.img from CM11 works fine. Clearly I'm missing something about how to flash the boot partition on this device. Apparently not all boot.img files are created equal...
Update 2 : I can flash the Advanced Stock Kernel with Dual Recovery without issue, so I'm going to flash my way back to 4.4.3 and go from there.
Fixed! : In the end, it was because I was using an ELF image and fastboot didn't like flashing it for some reason. I reverted my phone back to 4.4.3 using the stock system.img and FOTAKernel.img, then used the Advanced Stock Kernel with Dual Recovery, since they were all flashable via fastboot. Once the system was up, I used adb to push the 4.4.3 stock boot.img to the device and the did an adb shell, su'ed to root, and dd'it onto the boot device. Rebooted, OTA'ed it to 4.4.4. Done.
What a night. This is what I get for starting this project late...
Click to expand...
Click to collapse
you should read the "TYPE" mentioned in the OP
you cant flash ELF images using fastboot on newer s1 bootloaders
ddslee said:
Has anyone with a broken camera tried flashing this image?
Does the camera work in 4.4.4 after the flash?
Click to expand...
Click to collapse
my camera was working fine (could take pics in 4.4.3)...
after flashing to 4.4.4 i can no longer "take pics" using the camera app... though the camera preview is coming...
ekrunch said:
Forgive the long post, I'm sure some of this is repetitive, just trying to be complete for those who don't.
Sounds like you have the same exact problem as mine. Something about restoring an ELF image to the boot partition via Fastboot isn't working. Weird.
Alright, get ready to have some fun!
Get your device working again. I recommend using the 4.4.3 system.img/FOTAKernel.img and DooMLord's Advanced Stock Kernel with Dual Recovery. Worked like a charm for me. Get the 4.4.3 images from here and the kernel from here. Use "fastboot flash" accordingly for these 3 images. Note: The reason I use the custom kernel is b/c the 4.4.3 boot.img didn't flash correctly either.
Now you're running on 4.4.3 again, rooted. If you wiped data, don't bother signing in to your Google account, we're going to wipe again.
Now on to 4.4.4...
Okay so what we're going to do now is flash the boot.img for 4.4.4 on your running 4.4.3. Once you do this, the device probably won't boot Android again without some flashing in the boot loader, so brace yourself. :laugh:
First up, push the boot image to your device. You can do that with an ADB push, or ES File Explorer's handy FTP server, or just download the image with the phone. I used the 4.4.4 images from here. Get the boot-4.4.4.img on your device somehow and leave the system-4.4.4.img and FOTAKernel-4.4.4.img on your PC.
Code:
## [I](Not sure if you need the full path, I didn't push it this way)[/I]
adb push boot-4.4.4.img /storage/sdcard0/Download
Get a shell going
Code:
adb shell
Now that you're in the shell on your device, change to the right directory on the device, and copy the ELF image to the raw device using DD. (Everybody get your UNIX party hat out, we're going old school...)
Code:
su -
cd /storage/sdcard0/Download
dd if=boot4.4.4.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Alright, you have a 4.4.4 boot image. Now get back to the boot loader.
Code:
adb reboot-bootloader
And now it's time to get those 4.4.4 images onto the system. I'd highly recommend a good wipe of data/cache while you're at it. ("fastboot -w" will do this for you.)
Code:
fastboot flash FOTAKernel FOTAKernel-4.4.4.img
fastboot flash system system-4.4.4.img
That should do it. Reboot, lock on to your Google account, then fire up the developer's menu and crank up ART, then enjoy your device on 4.4.4. (BTW, this still didn't fix my camera. :crying: )
Good luck everyone! Hope this helps someone out. And would somebody please chime in with the simple command that I'm missing that fixes this problem and avoids all of this foolery?
Click to expand...
Click to collapse
thanks for creating it i was lazy to write all this
DooMLoRD said:
....
my camera was working fine (could take pics in 4.4.3)...
after flashing to 4.4.4 i can no longer "take pics" using the camera app... though the camera preview is coming...
...
Click to expand...
Click to collapse
Preview comes out ok as the hardware does initialize. The issue is, from what I have seen and other who may have corroborated this, is the AF on the camera. You see, photosphere actually works well, just not the regular camera. Someone else mentioned that apps using infinity focus work as well.
My guess is that something in 4.4.3 and 4.4.4 (maybe in the kernel?) is looking for the missing DRM keys from devices with unlocked BL. Several people have already stated that they have no issues with their cameras, with the only difference being the locked bootloader in their devices. Considering that Sony had done something similar with the Z1 last year, I would not be surprised if it was the case here as well. Not sure why this would be the case for a GPE unit as it has no proprietary software (other than X-Reality)...
As I said, nothing but a guess albeit it does make sense (to me anyways).
Finally!!
Finally got my GPE to update using ekrunches excellent post..it took a little fiddling, (WIPE!! REALLY!!) but everything else went quite smoothly. I did find that fastboot -w didn't format partitions on cache and data and ended up in stock recovery to do a full wipe, after which things worked perfectly. Before that it was bootlooping on me. Didn't fix the camera though. I may leave this sucker mostly stock until someone fixes the camera...and on that note-I unlocked my bootloader immediately on getting the phone, before any updates ran. I've been considering the idea that if you unlocked before 4.4.2, that might be what's messing the camera up. I don't have any evidence for this though, it's just a guess.
DooMLoRD said:
you should read the "TYPE" mentioned in the OP
you cant flash ELF images using fastboot on newer s1 bootloaders
Click to expand...
Click to collapse
hahahaha I did. But it's the same for the boot and FOTAKernel images. What kept throwing me was one working while the other didn't but they were both the same type of file. How nice of Sony to do this... *cough cough*
DooMLoRD said:
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Click to expand...
Click to collapse
So is there a better way to flash that boot image or is this it?
DooMLoRD said:
thanks for creating it i was lazy to write all this
Click to expand...
Click to collapse
You're quite welcome. Thank you for all of the dumps, kernels, write ups, etc. It is much appreciated. I've been leeching information from this forum for years with no contribution other than some donations so I'm glad to help out. I was beating my head up against the wall when I wrote that first post as it was driving me crazy that I couldn't flash that boot image. I've been spoiled by Nexus devices.
Do i need to flash BootKernel and FOTAKernel as well or will simply flashing the system image work ?
Pallavgarg10 said:
Do i need to flash BootKernel and FOTAKernel as well or will simply flashing the system image work ?
Click to expand...
Click to collapse
Depends what you are trying to achieve?
Fully update your new GPe ZU?
From 4.4.2 to 4.4.4?
Already rooted or not, if not I would just flash the OTAs
I just want to update to 4.4.4 with as little modification as possible
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
Hi All,
I've been crawling the web the past few days to find a solution to my problem and unfortunately I didn't...
I have a Asus Zenfone 3 Max ZC520TL MT6737M, I never did a custom OS installation before and didn't know anything about how phone works except the Linux kernel
After 2 or 3 weeks playing with custom rom and recovery, softbrick, fastboot and adb I finally successfully intalled a custom OS, I wanted lineageOS but only found an Himax image working properly (with bluetooth., etc) for my phone and TWRP as custom recovery.
I setted my parameters for all my applications and after inserting my SIM card the network was not working, I tried a factory reset from the phone and then I got stuck in twrp however the way I booted, I tried flashing the os again, the recovery again wiping/formatting data, I was still stuck in TWRP
Then I executed :
fastboot format:ext4 cache
fastboot format:ext4 boot
And now I can't boot nor in twrp nor in fastboot, I can't access the bootloader using power and volume up, and my phone bootloop
Is there a way to get to fastboot to reinstall the recovery and then from here the os or is my phone hardbricked with no future, ready for trash?
Thank you
rominail said:
then I executed :
fastboot format:ext4 boot
Click to expand...
Click to collapse
You completely destroyed phone's boot-loader, what is comparable to a computer's BIOS.
What do you expect? IMO phone is case for the e-waste.
rominail said:
Hi All,
I've been crawling the web the past few days to find a solution to my problem and unfortunately I didn't...
I have a Asus Zenfone 3 Max ZC520TL MT6737M, I never did a custom OS installation before and didn't know anything about how phone works except the Linux kernel
After 2 or 3 weeks playing with custom rom and recovery, softbrick, fastboot and adb I finally successfully intalled a custom OS, I wanted lineageOS but only found an Himax image working properly (with bluetooth., etc) for my phone and TWRP as custom recovery.
I setted my parameters for all my applications and after inserting my SIM card the network was not working, I tried a factory reset from the phone and then I got stuck in twrp however the way I booted, I tried flashing the os again, the recovery again wiping/formatting data, I was still stuck in TWRP
Then I executed :
fastboot format:ext4 cache
fastboot format:ext4 boot
And now I can't boot nor in twrp nor in fastboot, I can't access the bootloader using power and volume up, and my phone bootloop
Is there a way to get to fastboot to reinstall the recovery and then from here the os or is my phone hardbricked with no future, ready for trash?
Thank you
Click to expand...
Click to collapse
You NEVER format your boot partition as ext4 it's a raw boot.img which holds the kernel and ramdisk. You should really do research and follow instructions alittle better than that.. unfortunately I don't think your device can be saved and if you flashed aboot or sbl1/2/3 then your SOL
Thanks
Thank you for your answers!
I don't know why I did that (sometimes I have crazy bad ideas), I didn't see that on internet
rominail said:
Thank you for your answers!
I don't know why I did that (sometimes I have crazy bad ideas), I didn't see that on internet
Click to expand...
Click to collapse
That's okay! Please so make sure you do some research if your new to the custom OS scene.. it's always good to learn new things
maybe you can flash again like from the factory by using the default flashing and ROM tools.
BryanHafidz said:
maybe you can flash again like from the factory by using the default flashing and ROM tools.
Click to expand...
Click to collapse
If your in a Qualcomm chipset and you have an EDL programmer that works for your device I have custom tools in my cloud storage to create an EDL firmware if you don't ready have one. If your on MTK then there is Sugar MTK or SP flash tool that can work. If your an another one you may be out of luck as it seems nobody has been able to restore those chipsets
EDIT: I do have a whole zip file of programmers and one that I use for my LG Zone 2 (msm8x10.mbn)
TheExploitedOne said:
You NEVER format your boot partition as ext4 it's a raw boot.img which holds the kernel and ramdisk. You should really do research and follow instructions alittle better than that.. unfortunately I don't think your device can be saved and if you flashed aboot or sbl1/2/3 then your SOL
Click to expand...
Click to collapse
we have the same problem but I didn't do like you.
I entered these commands
*fastboot flash recovery boot.img (I'm stupid lol)
*fastboot flash boot boot.img
*fastboot reboot*
mahirab23 said:
we have the same problem but I didn't do like you.
I entered these commands
*fastboot flash recovery boot.img (I'm stupid lol)
*fastboot flash boot boot.img
*fastboot reboot*
Click to expand...
Click to collapse
What seems to be going on after the flash?
TheExploitedOne said:
What seems to be going on after the flash?
Click to expand...
Click to collapse
the biggest problem is i have reset the phone and i am stuck with this message: "to start android enter your password". I entered the correct password but another message appears with a reset phone option.
Since the recovery.img file is no longer in the system, the phone keeps making this loop.
mahirab23 said:
the biggest problem is i have reset the phone and i am stuck with this message: "to start android enter your password". I entered the correct password but another message appears with a reset phone option.
Since the recovery.img file is no longer in the system, the phone keeps making this loop.
Click to expand...
Click to collapse
If you can get into fastboot run the following:
fastboot erase recovery
fastboot erase userdata
fastboot format:ext4 userdata
Then reflash your recovery
TheExploitedOne said:
If you can get into fastboot run the following:
fastboot erase recovery
fastboot erase userdata
fastboot format:ext4 userdata
Then reflash your recovery
Click to expand...
Click to collapse
I can't get into fastboot.
another solution?????
mahirab23 said:
I can't get into fastboot.
another solution?????
Click to expand...
Click to collapse
Can you access EDL mode?
TheExploitedOne said:
Can you access EDL mode?
Click to expand...
Click to collapse
thank you for your attention and suggestions.
I haven't tried this method yet.
I'm not good with EDL mode
Can SP tools and MiracleBox help me?
mahirab23 said:
thank you for your attention and suggestions.
I haven't tried this method yet.
I'm not good with EDL mode
Can SP tools and MiracleBox help me?
Click to expand...
Click to collapse
MiracleBox and QPST yes
TheExploitedOne said:
MiracleBox and QPST yes
Click to expand...
Click to collapse
good !!!: o: o
can you develop the method with Miracle Box and QPST ? please!!!
mahirab23 said:
good !!!: o: o
can you develop the method with Miracle Box and QPST ? please!!!
Click to expand...
Click to collapse
I have the tools needed in my cloud I can make into a zip file. You'll need to also do some research on your part but I can also write a readme file too so you have a basic understanding. Just give me a few to get the link
EDIT:
Here you go this has all you'll need for flashing your device in EDL as well as create the firmware if needed
https://mega.nz/file/rc8CVIiB#qnM3_ZzrvCJtp_M7Y9ZftZqDtGgWeN0tqFrLlT30pws
TheExploitedOne said:
MiracleBox and QPST yes
Click to expand...
Click to collapse
thank you
I finally managed to reset the phone thanks to SoftwareDownload
thank you really. you are really kind and available:bien::bien::bien:
mahirab23 said:
thank you
I finally managed to reset the phone thanks to SoftwareDownload
thank you really. you are really kind and available:bien::bien::bien:
Click to expand...
Click to collapse
Absolutely good sir! I'm glad that I can help
TheExploitedOne said:
If your in a Qualcomm chipset and you have an EDL programmer that works for your device I have custom tools in my cloud storage to create an EDL firmware if you don't ready have one. If your on MTK then there is Sugar MTK or SP flash tool that can work. If your an another one you may be out of luck as it seems nobody has been able to restore those chipsets
EDIT: I do have a whole zip file of programmers and one that I use for my LG Zone 2 (msm8x10.mbn)
Click to expand...
Click to collapse
Thank you for your help, unfortunately it's a mediatek
**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