Database Users

Fail flash, what to do?

Hello!
I was about to unroot and get back to stock with my A500 so I flashed a stock ROM via CWM to get a ota-update. Before i had a custom ICS ROM installed and now I installed a HC stock ROM. The problem is that i forgot to go through the wipe menu in CWM before the flash and now when I start up my tablet I first see the ACER logo as usual, then a android text-logo which the tablet is stuck at. I've waited 20 minutes and is still shows the same thing. The logo has an animation which i still can see. I've tried to restart the tablet and get into CWM again without succes.
I have read diffrent threads for several hours but I can't find my problem. What should I do? :crying:

what does the android text say?

Hi dibb_nz.
It is the bootanimation from what I gather (Video; http://s1142.photobucket.com/albums/n602/JdgM3NT4L/?action=view&current=AndroidBootanimation.mp4). I am trying to help someone get a tab up that is doing the same thing as well. The weird part is that recovery is good, bootloader passed (V8), wiped data/cache/system. Tried three ICS roms so far, and every one is stuck at the bootanimation. About to go bonkers trying to figure it out. The only thing that I can think of to try next is changing CWM from Thors to TWRP or something...
To Webspirit, your problem will most likely get fixed by using blackthund3rs APX Tool. Google it and then goto the forum where it is. There's plenty of support for getting that going and you shouldn't have any problems. If you do holler. Alot of us have had to use that tool and can help. I am hopeful that yours will be as simple as downloading and installing recovery back and flashing a nice rom.

Yeah i agree with the guy above me, your going to have to flash something from apx
Sent from my A501 using xda app-developers app

JdgM3NT4L said:
Hi dibb_nz.
It is the bootanimation from what I gather (Video; http://s1142.photobucket.com/albums/n602/JdgM3NT4L/?action=view&current=AndroidBootanimation.mp4). I am trying to help someone get a tab up that is doing the same thing as well. The weird part is that recovery is good, bootloader passed (V8), wiped data/cache/system. Tried three ICS roms so far, and every one is stuck at the bootanimation. About to go bonkers trying to figure it out. The only thing that I can think of to try next is changing CWM from Thors to TWRP or something...
To Webspirit, your problem will most likely get fixed by using blackthund3rs APX Tool. Google it and then goto the forum where it is. There's plenty of support for getting that going and you shouldn't have any problems. If you do holler. Alot of us have had to use that tool and can help. I am hopeful that yours will be as simple as downloading and installing recovery back and flashing a nice rom.
Click to expand...
Click to collapse
hi J...ok thats cool re boot anim...i asked becoz like u i been trying to help a couple of others who can't use any of the flash tools or roll back to HC...i only just got myself fixed after being stuck in apx, no recovery, and boot screen saying in red text "reboot device" thought he may have had similar issue....
J...have u used nvflash or apxflash to roll back - theres a few folks getting stuck with it...its loading the HC apx driver which aint working with the ics bl so then yr tab gets stuck in apx!!!
I started a new thread hoping someone can help us all out be great to hear yr thoughts on this....its driving me up the wall
sorry didnt mean to hijack the thread

LG G2 (Secure booting error) can boot into TWRP. How do i fix this?

(I CAN GET INTO TWRP AND DOWNLOAD MODE) T-Mobile D801 (This was my previous phone that i had rooted before) My dads LG G2 was having issues with the touchscreen on CM so i decided to flash the stock ROM but i guess i might have skipped a few steps and after flashing i got :boot certification verify, secure booting error! and cause: boot certification verify. after that i tried flashing a backup but i got the same thing. My friend told me to wipe all the files so i did and that's what point i am on now. I can still boot into recovery but have no idea what to do further, i tried to following one of the guides on here (forgot link sorryz) but once i got to one of the steps where i plug my phone in my PC would recognize it as a bunch of drives (tried this on a different PC as well) WILL REALLY APPRECIATE THE HELP GUYS!

Gandek said:
(I CAN GET INTO TWRP AND DOWNLOAD MODE) T-Mobile D801 (This was my previous phone that i had rooted before) My dads LG G2 was having issues with the touchscreen on CM so i decided to flash the stock ROM but i guess i might have skipped a few steps and after flashing i got :boot certification verify, secure booting error! and cause: boot certification verify. after that i tried flashing a backup but i got the same thing. My friend told me to wipe all the files so i did and that's what point i am on now. I can still boot into recovery but have no idea what to do further, i tried to following one of the guides on here (forgot link sorryz) but once i got to one of the steps where i plug my phone in my PC would recognize it as a bunch of drives (tried this on a different PC as well) WILL REALLY APPRECIATE THE HELP GUYS!
Click to expand...
Click to collapse
if you can enter download mode then just flash stock friemware. using TOT or KDZ. thatll fix it. the boot error is when you mess with the bootloader. like you instal wrong bootloader for rom..
try it again.. i had same all i did was go back to stock.

i cant flash anything though since any PC will recognize my phone as a bunch of drives so i cant get the stock firmware

Gandek said:
(I CAN GET INTO TWRP AND DOWNLOAD MODE) T-Mobile D801 (This was my previous phone that i had rooted before) My dads LG G2 was having issues with the touchscreen on CM so i decided to flash the stock ROM but i guess i might have skipped a few steps and after flashing i got :boot certification verify, secure booting error! and cause: boot certification verify. after that i tried flashing a backup but i got the same thing. My friend told me to wipe all the files so i did and that's what point i am on now. I can still boot into recovery but have no idea what to do further, i tried to following one of the guides on here (forgot link sorryz) but once i got to one of the steps where i plug my phone in my PC would recognize it as a bunch of drives (tried this on a different PC as well) WILL REALLY APPRECIATE THE HELP GUYS!
Click to expand...
Click to collapse
you can flash again right rom for your model.(first confirm its not refurbished) or install bootloader changer through twrp(zip can be found on forum throug search). flash zip witb the help of OTG cable and usb drive. if you need help email me.. aslam. jarh @ gmail. com

Gandek said:
i cant flash anything though since any PC will recognize my phone as a bunch of drives so i cant get the stock firmware
Click to expand...
Click to collapse
Had the exact same issue, I believe it's caused by corrupting the internal memory (multiple causes for this).
Don't freak just follow http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 (there's a video guide at the bottom, but it's pretty straight forward).
After that follow http://forum.xda-developers.com/show....php?t=2432476 to get it back to stock and work from there.

[Q] Bricked Nexus 4

Hello Guys,
yesterday I restarted my Nexus 4, running the cm-13.0-20160520-NIGHTLY-mako. It stuck at the bootlogo, so I tried to reflash it in the twrp 2.8.7.0 recovery. But I got the error message "E:/ unable to mount /cache".
After that I was trying to solve this issue by wiping the cache, but I got the same error message -> The phone wasn't booting
From now on I did several things to solve my problem. I don't know the exact order.
- I've downloaded the Nexus Root Toolkit from WugFresh -> Tried to use the Flash Stock + Unroot Option with Soft-Bricked/Bootloop status enabled -> I choosed the 5.1.1 Factory Image -> In the cmd window, I get in every point the same error message "Falied (remote: flash write failure) -> I get the same message when I'm trying to manually flash each part of the factory image via fastboot
- Within the Toolkit I also tried to format cache, system and Userdata, but afther this I get the same error when trying to do the step before
- I think also used the Fastboot Flash options, but I'm not sure.
- After that I attempted to flash the cm13.zip via adb-sideload in TWRP. Here is a part from the error message I get:
"(...) could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume (...)
E: Error executing updater binary in zip 'sideload/package.zip'
E: Unable to mount '/data'
- In TWRP the Internal Storage is shown with 0mb
- Currently only the bootloader is working fine and I also can get a fastboot and adb connection to the phone
-> Loading the recovery is only possible by booting a recovery image in fastboot
Can somebody tell me if it is possible to restore my Nexus 4 and how to do it?
Thank you in advance :fingers-crossed:
PS: I hope I mentioned all the important points. If some information is missing, feel free to ask me.

Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?

audit13 said:
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Thank you for your answer.
I tried to flash the newest cm13 in TWRP and with adb Sideload. I get the same error.
Also the 4.2 Stock rom doesn't work. Same problem as with the 5.1.1 factory image.
I also switched the cable and the USB ports, but it leads to the same error messages.

Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.

From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.

audit13 said:
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
Click to expand...
Click to collapse
I get the same error message as always: Falied (remote: flash write failure)
nerotNS said:
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
Click to expand...
Click to collapse
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:

Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.

audit13 said:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
Click to expand...
Click to collapse
Unfortunately yes. After locking the bootloader via fastboot, the bootloader is marked as unlocked after rebooting.
Do I have to change the mainboard?

This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.

audit13 said:
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
Click to expand...
Click to collapse
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.

tobi.king said:
I get the same error message as always: Falied (remote: flash write failure)
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Click to expand...
Click to collapse
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
tobi.king said:
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
Click to expand...
Click to collapse
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.

nerotNS said:
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
Click to expand...
Click to collapse
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.

tobi.king said:
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
Click to expand...
Click to collapse
Awesome, glad to be of service

Cant flash an OS - "failed to mount partition '/vendor' (invalid argument)"

Hello!
Now, I know this problem is in other threads. But the only reason why I'm posting a new one is if either that thread had died or the solution wasn't applicable to me (it didn't/doesn't work).
So! What happens is when I try to flash a file to the system or vendor I get this error.
Code:
failed to mount partition '/vendor' (invalid argument)
I've tried in TWRP and the bootloader fixes. And now, I currently have no OS.
What I've tried is as follows:
Flashing just the vendor (bootloader/TWRP) - ends with the vendor error.
Flashing .zip ROMs (bootloader/TWRP) - ends with the vendor error.
Trying the usual return to stock procedure - ends with the vendor error.
Repairing partition in TWRP - Says operation completed but the error is still persistent.
Basically. Nothing works because the Vendor partition is unmountable.
What should I do? I have no idea what a fix could be.

Alright, so i've tried some things. I guess I've fixed it but I got a new problem. In the end what fixed it was wiping every parition and rebooting TWRP and then flashing a system image then vendor image. When i say image i mean a manual .img flash instead of a .zip file.
The problem now it that because every was wiped, i no longer have a recovery. When i boot into recovery i get "No command". So now im stuck with stock android 8.1 and a unlocked bootloader that won't do anything. Every time i try and flash a partition i get
Code:
FAILED (data write failure (Too many links))
or
Code:
FAILED (command write failed (No error))
Any tips on getting a recovery installed so i can return to my custom ROM ways.
Thanks for any help in advance.

Nexus Radical said:
Alright, so i've tried some things. I guess I've fixed it but I got a new problem. In the end what fixed it was wiping every parition and rebooting TWRP and then flashing a system image then vendor image. When i say image i mean a manual .img flash instead of a .zip file.
The problem now it that because every was wiped, i no longer have a recovery. When i boot into recovery i get "No command". So now im stuck with stock android 8.1 and a unlocked bootloader that won't do anything. Every time i try and flash a partition i get
or
Any tips on getting a recovery installed so i can return to my custom ROM ways.
Thanks for any help in advance.
Click to expand...
Click to collapse
Try using Nexus root toolkit, I used that today to fix recovery,

jimbomodder said:
Try using Nexus root toolkit, I used that today to fix recovery,
Click to expand...
Click to collapse
Done some research and it seems to be a cable issue of all things with this errors. I bought a new one that should arrive by amazon tomorrow. Will see if that fixes it.
As the nexus toolkit ive been using that a lot. With that i don't even get an error but it never works.

Nexus Radical said:
Done some research and it seems to be a cable issue of all things with this errors. I bought a new one that should arrive by amazon tomorrow. Will see if that fixes it.
As the nexus toolkit ive been using that a lot. With that i don't even get an error but it never works.
Click to expand...
Click to collapse
That's something I have loads of, all seem to connect ok but least you should have it fixed soon.

jimbomodder said:
That's something I have loads of, all seem to connect ok but least you should have it fixed soon.
Click to expand...
Click to collapse
Yeah well, it seemed the cable wasn't the issue. I wouldn't of thought it was myself but yeah. Seems my initial thoughts were right as the cable didn't fix anything. Same errors, same problem. So all my research has lead to nothing. So how can I fix this? I'm out of solutions. I need xposed at least on my phone to be usefull since I can't disable the screen off during calls.

Nexus Radical said:
Yeah well, it seemed the cable wasn't the issue. I wouldn't of thought it was myself but yeah. Seems my initial thoughts were right as the cable didn't fix anything. Same errors, same problem. So all my research has lead to nothing. So how can I fix this? I'm out of solutions. I need xposed at least on my phone to be usefull since I can't disable the screen off during calls.
Click to expand...
Click to collapse
Have you tried wugfresh Nexus tool kit?

Just thought I'd let you know that I have fully restored stock and locked my bootloader, and if I boot recovery I get " no command" too. Seems latest recovery image does f*@k all.

jimbomodder said:
Have you tried wugfresh Nexus tool kit?
Click to expand...
Click to collapse
No, I haven't. BUT!!! I have fixed it...
So the issue that I was having is that I bought a replacement charging board (the PCB for the USB dock.) I replaced it because I had a faulty microphone on it but the USB port was fine. Putting in the old one fixed all the issues I was having. Its meant to be an OEM part so I didn't figure it would be the problem but it was *sigh*... So I take it where I got it from Replacement Base wasn't legit? Ah well, at least my problem is fixed and if anyone gets the same problems they might find this thread.
Thanks for your support thought dude! It was nice to have someone to ask.

Nexus Radical said:
No, I haven't. BUT!!! I have fixed it...
So the issue that I was having is that I bought a replacement charging board (the PCB for the USB dock.) I replaced it because I had a faulty microphone on it but the USB port was fine. Putting in the old one fixed all the issues I was having. Its meant to be an OEM part so I didn't figure it would be the problem but it was *sigh*... So I take it where I got it from Replacement Base wasn't legit? Ah well, at least my problem is fixed and if anyone gets the same problems they might find this thread.
Thanks for your support thought dude! It was nice to have someone to ask.
Click to expand...
Click to collapse
O crap, I got 2 "oem" replacement cameras for my 6p from them and both blurry and don't save pictures,. Glad you fixed it yet.

Deleted Bootloader on LeEco S3 X626

A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.

can you at least get the phone to fastboot mode?

microMXL said:
can you at least get the phone to fastboot mode?
Click to expand...
Click to collapse
No I cannot, The screen is completely black and nothing comes on at all if I hold down the power button.

well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.

microMXL said:
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
Click to expand...
Click to collapse
I have already looked through that thread, and i have done everything up to the flashing process, and then I get a STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) Error. I looked it up but the only option I haven't tried to solve the issue is to remove the battery, which i cannot do currently because to remove the battery you need a heat gun to remove the screen to get to the rest of the phone. I think I've given up all hope on fixing this phone and may just begin saving for a new one.

Sgt.Collywobbles said:
A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
Click to expand...
Click to collapse
Help, pls I got the exact same problem... Pls any solution to it... I have been at it for a month now no solution, help

same problem. after twrp flash x626 not boot