Database Develop

[Q] i9305 doesn't boot anymore after failed update (TWRP)

Hey guys,
i just created this account because i'm really lost right now.
since 3 days i'm trying to flash a new version of cyanogenmod on my phone, but it always failed because of an TWRP error (error status 7).
it wasn't really a problem because i just flashed the working version(cm-11-20131222-Nightly-i9305) back on and everything was alright.
but now i accidentally deleted this version and the cyanogenmod site doesn't list it anymore.
i've been trying to install a new version on the phone with always the same error no matter which version i try.
after i looked it up here, i deleted the assert part in the updater-script. doesn't work either.
so i upgraded the TWRP to the current version via Odin because i read it could help.
and now it only saids:
set_metadata_recursive: some changes failed.
E: Error executing updater binary in zip <PATH>
Error flashing zip <PATH>
and i can only boot into the download or recovery mode now.
i hope anybody can help me with that. i also could offer the recovery.log from TWRP if it would help.

Wrong forum, i9305 has a specific section where you're most likely to receive an answer. Report your own post and ask a moderator to move it.
Usual advice is to flash a full stock rom using odin then start over, check the md5 of any downloads.

[Q] Bricked phone, fastboot but no adb, SD has been wiped,

Hey guys,
Earlier today I tried reverting my phone back to stock which worked fine until i tried installing the OTA update to 4.3 with sense 5.5 which, after the installation was complete, caused my phone to stop booting ( I now just get a black screen). I can still access the bootloader and recovery (I've reinstalled TWRP from my PC) but I can't access adb cause it keeps disconnecting from my PC within seconds of entering recovery. Because my SD card has somehow been wiped it also means that I have no ROMs or backups with which to reinstall an operating system.
I understand that you can flash files such as boot.img and system.img directly to partitions via fastboot but none of the rooms/ backups I have seem to have a system.img, only boot.img and recovery.img. Do i have to do something extra to get the system.img from a zipped ROM or a backup?
What are my options at this point?

RealityClash said:
Hey guys,
Click to expand...
Click to collapse
Please stick to your original thread: http://forum.xda-developers.com/showthread.php?t=2744820
Multi-threading and cross-posting is not viewed upon favourably here
Thanks

Sorry bout that, am I able to delete this thread then?

RealityClash said:
Sorry bout that, am I able to delete this thread then?
Click to expand...
Click to collapse
No only Moderators can do that, just let this one "die" out, and stick to with your other thread, it already has much/most of the information needed. Please remember to be patient, you are already being actively helped, and many of us will chip in when / if we can and have something to add.
(not everybody is online at the same time, and free all the time)
PS: you can always "bump" your other thread (if it get's "buried") after 24 hours.

Help, in need of system image

So I was messing with some kernel stuff when after flashing something I noticed I no longer was connecting to Sprint, It just would say "No Service" I figured that restoring a NAND backup would correct this issue but it hasn't. The issue has been persistent with any rom I tried. Another issue i noticed is that I couldn't connect my phone do a PC and transfer files, I soon came to the realization the reason was that when the system booted the sd card wouldn't mount. If i tried to "cd /sdcard" it would say "no such file or directory" So unsure of what to do I began to start the process of restoring stock with RUU. But unfortunately I couldn't make it through the process. Unfortunately my sdcard got formatted when I Re-unlocked my bootloader, this means I don't have any roms to flash, and when I try to use ADB from TWRP it says there is no device connected.
I really must have screwed something up and it seems to me this won't be a quick fix. to start off I was wondering if anybody could donate a system.img from their cyanogenmod installation just so I can flash via fastboot and get started or could point me in the direction of getting one.
Thanks for the help everyone, I hope I can get my One working again.

CyrodiilSavior said:
So I was messing with some kernel stuff when after flashing something I noticed I no longer was connecting to Sprint, It just would say "No Service" I figured that restoring a NAND backup would correct this issue but it hasn't. The issue has been persistent with any rom I tried. Another issue i noticed is that I couldn't connect my phone do a PC and transfer files, I soon came to the realization the reason was that when the system booted the sd card wouldn't mount. If i tried to "cd /sdcard" it would say "no such file or directory" So unsure of what to do I began to start the process of restoring stock with RUU. But unfortunately I couldn't make it through the process. Unfortunately my sdcard got formatted when I Re-unlocked my bootloader, this means I don't have any roms to flash, and when I try to use ADB from TWRP it says there is no device connected.
I really must have screwed something up and it seems to me this won't be a quick fix. to start off I was wondering if anybody could donate a system.img from their cyanogenmod installation just so I can flash via fastboot and get started or could point me in the direction of getting one.
Thanks for the help everyone, I hope I can get my One working again.
Click to expand...
Click to collapse
First, you need to Relock your bootloader, Unroot, then S-ON your devide , Then flash RUU rom via Command in PC ( fastboot , ADB )
Finaly : if you want Flash a custom Rom , you should unlock bootloader , Root your HTC ONE , Flash recovery and then Flash custom Rom
Hope this can help you , sorry for my bad in english , I'm VietNamese

I attempted to relock unroot RUU etc. via this method, but the process got stuck at Checking Headers.
Is there another way of doing this?

CyrodiilSavior said:
I attempted to relock unroot RUU etc. via this method, but the process got stuck at Checking Headers.
Is there another way of doing this?
Click to expand...
Click to collapse
Make sure you're running it on a Windows 7 PC.

I did use a windows 7 64bit machine yesterday when it got stuck on Checking headers. I also tried on my Ubuntu system using the manual Decrypted method. Upon typing "sudo fastboot flash /system newimage.img" it returned :
Code:
target reported max download size of 1520349184 bytes
Invalid sparse file format at header magi
sending sparse '/system' (1456350 KB)...
FAILED (status read failed (Bad file descriptor))
finished. total time: 33.855s
Any ideas as to why it cant do this?

I'm sorry for not being more descriptive, I have a pretty strong background in linux and android but this issue has really stumped me.

CyrodiilSavior said:
I did use a windows 7 64bit machine yesterday when it got stuck on Checking headers. I also tried on my Ubuntu system using the manual Decrypted method. Upon typing "sudo fastboot flash /system newimage.img" it returned :
Code:
target reported max download size of 1520349184 bytes
Invalid sparse file format at header magi
sending sparse '/system' (1456350 KB)...
FAILED (status read failed (Bad file descriptor))
finished. total time: 33.855s
Any ideas as to why it cant do this?
Click to expand...
Click to collapse
The decrypted version won't work; it's for developer use only (making ROMs etc). Try using a USB-OTG cable in TWRP to flash a ROM.

StormyNight said:
The decrypted version won't work; it's for developer use only (making ROMs etc). Try using a USB-OTG cable in TWRP to flash a ROM.
Click to expand...
Click to collapse
Last night I finally managed to flash a ROM through recovery. I booted into the os and everything works fine aside from the network. I still am unable to connect to the sprint network, It just says "No Service". I've done some research and it seems to me the best/only way to fix this issue is to flash it back to stock. Which I have been unable to succeed in doing.
Let me know what you think my next step would be, either if I should continue trying to go back to stock or to fix the network issue with my current ROM.

CyrodiilSavior said:
Last night I finally managed to flash a ROM through recovery. I booted into the os and everything works fine aside from the network. I still am unable to connect to the sprint network, It just says "No Service". I've done some research and it seems to me the best/only way to fix this issue is to flash it back to stock. Which I have been unable to succeed in doing.
Let me know what you think my next step would be, either if I should continue trying to go back to stock or to fix the network issue with my current ROM.
Click to expand...
Click to collapse
Flash the latest radio/baseband founf HERE

BD619 said:
Flash the latest radio/baseband founf HERE
Click to expand...
Click to collapse
I didn't notice this till now but the sdcard is not mounting. I have the ability to mount it in recovery but when booted into system no luck. I am thinking reflashing a new boot.IMG would correct the issue.

Good news, I did an adb push and flashed the radio and that fixed it, I now can connect to sprint and my Sdcard is now mounting.
Thanks so much to everyone for the help. I really appreciate it!

Nexus 6 bootloop and locked bootloader

Hi guys i have a problem with Nexus 6
the problem is my Nexus 6 is stuck on boot loop and bootloader locked i think the only solution for this is, if google make avaliable individually system ZIP files to transfer using ADB sideload on recovery mode.
I've now open a thread on official Nexus forum
Link: https://productforums.google.com/fo...er-discussions/other-nexus-device/l_GO8k2N1Ho
and I would ask for members of the community here look and comment on this thread for google see that there is more Nexus users who supports this case, THX Anderson.
If anyone at here havê other solution for this problem please tell i would be greatful.

Well, firstly how have you got stuck in a bootloop? If they provide flash able zips, they'll be bypassing their own security.

After OTA bad installation, when i try to start my the device don't start and when i check my bootloader LOG see this message " Invalid boot image header"
I think the kernel partition is corrupted =\

Acfanderson said:
After OTA bad installation, when i try to start my the device don't start and when i check my bootloader LOG see this message " Invalid boot image header"
I think the kernel partition is corrupted =\
Click to expand...
Click to collapse
You'll need to RMA it.
I suppose if they could provide a side load that doesn't touch the data partition, it could be helpful.

Moto Z3 Play stuck at TWRP logo screen

Hello everyone,
I tried to flash TWRP on my Z3 play today and got stuck on the TWRP logo screen. Since I am a noob, i will try to give a detailed describtion of what i have done so far.
I started by going into debuggingn mode and unlocking to bootloader following the guide unlock-bootloader-moto-z3-play from getdroidtips
This worked as far as i can tell. Today I wanted to get TWRP running as this seemed like the next step to take. Again i followed the getdroidtips guide twrp-recovery-moto-z3-play/ which linkes to flash-twrp-recovery-android. Here I didnt install Odin and Android Kies, because these seem to be Samsung-specific? I followed all other steps and arrived at the command line "fastboot flash recovery recovery.img" which didnt work, but gave the error message "invalid partition name recovery". After googling a bit I found that "fastboot boot recovery.img" should boot TWRP and that I could procced from there. At first it looked as if TWRP would actually boot, but then it got stuck in the logo screen and is sitting at that for an hour now.
Did I brick my phone? And can I fix this somehow?
Any help would be greatly appreciated.
Thank you.

Dunsinan said:
Hello everyone,
I tried to flash TWRP on my Z3 play today and got stuck on the TWRP logo screen. Since I am a noob, i will try to give a detailed describtion of what i have done so far.
I started by going into debuggingn mode and unlocking to bootloader following the guide unlock-bootloader-moto-z3-play from getdroidtips
This worked as far as i can tell. Today I wanted to get TWRP running as this seemed like the next step to take. Again i followed the getdroidtips guide twrp-recovery-moto-z3-play/ which linkes to flash-twrp-recovery-android. Here I didnt install Odin and Android Kies, because these seem to be Samsung-specific? I followed all other steps and arrived at the command line "fastboot flash recovery recovery.img" which didnt work, but gave the error message "invalid partition name recovery". After googling a bit I found that "fastboot boot recovery.img" should boot TWRP and that I could procced from there. At first it looked as if TWRP would actually boot, but then it got stuck in the logo screen and is sitting at that for an hour now.
Did I brick my phone? And can I fix this somehow?
Any help would be greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Just like the Google search you used, there's a search here on XDA. Your problem has been addressed many times.
Instead of creating a new Topic/thread, ideally you could've and should've first searched the TWRP Z3 thread. Then asked questions about TWRP in The TWRP thread.

kewlzter said:
Just like the Google search you used, there's a search here on XDA. Your problem has been addressed many times.
Instead of creating a new Topic/thread, ideally you could've and should've first searched the TWRP Z3 thread. Then asked questions about TWRP in The TWRP thread.
Click to expand...
Click to collapse
Oh, I am sorry if this is a duplicate. I searched the forum before and didnt find my problem. I will look again.
Thanks for the quick response

Dunsinan said:
Oh, I am sorry if this is a duplicate. I searched the forum before and didnt find my problem. I will look again.
Thanks for the quick response
Click to expand...
Click to collapse
Did you find the solution?
hint: 3.3.1.0

Okay, I am an idiot.
Thanks to your hint I figured out that I had to use TWRP 3.3.1.0 to not get stuck. This worked, but I accidentaly flashed TWRP to boot instead of recovery.
When i tried to flash to recovery i got: "Invalid partition name recovery"
What can I do now?

Dunsinan said:
Okay, I am an idiot.
Thanks to your hint I figured out that I had to use TWRP 3.3.1.0 to not get stuck. This worked, but I accidentaly flashed TWRP to boot instead of recovery.
When i tried to flash to recovery i got: "Invalid partition name recovery"
What can I do now?
Click to expand...
Click to collapse
That's not an accident, that's a mistake!
I'm sure there are a number of things you can do. But messing with Boot partition is the best way to brick your phone.
have you tried to use LMSA to start over.
or
Boot TWRP, use one of the backups you made. Restoring boot?
or
ADB flash boot, from firmware sideload folder.

I used LMSA to go back to stock android. Now it boots normal again.
Okay, so how do I get TWRP to work? I am hestitant to try on my own again.
Last time i tried to flash twrp to recovery i got a "invalid partition name recovery" error message.

Dunsinan said:
I used LMSA to go back to stock android. Now it boots normal again.
Okay, so how do I get TWRP to work? I am hestitant to try on my own again.
Last time i tried to flash twrp to recovery i got a "invalid partition name recovery" error message.
Click to expand...
Click to collapse
Do you just try things without any research? have you not considered reading the very short thread associated with TWRP and this device?
That's the correct place to both look for your answers, and ask for clarification.