Database Users

Help! I screwed up :(

Hey guys... friend of mine asked me to put in a custom ROM to his Hero, tires of waiting for HTC to release a 2.1/2.2 for us here in SE Asia.
The phone had already been rooted, but I could not manage to put in a recovery partition, even trying with the GoldCard method.
So, I dug around and found recommendations to try Droid Explorer, which I did, very nice program!
What I did was to use the "update custom ROM" function to put in the ChocolateEclair ROM
Everything seemed to run fine, phone rebooted, showed the new boot animation, then went to a green screen for a few minutes, but this is normal as per the ROM's details page.
But, since then, it's rebooted, it does the boot animation (hand-drawn droid), over and over again, can't get past that. I can get into bootloader and stock recovery screens, though. I'm thinking I should try to wipe the device again, but I cannot select this option in the recovery, it says to press alt-w but that's a bit hard without a keyboard!
I also tried to connect with adb shell (when in recovery mode) but it tells me it cannot find the shell.
So... have I bricked this poor phone? Right now I am downloading the latest RUU I can find, and hope it will work, but if anyone has any experience and advice to share it will be greatly appreciated!

Hey mate... You should have posted in ChocolateEclair topic. Can a mod merge the topics?
To answer you... This does not mean the phone is bricked. Are you sure you don't have a custom recovery image?(boot with home+power) Please paste me your logcat(adb logcat) and I'll tell you what causes the reboot, there's nothing to worry about.

Hey RaduG,
Thanks for getting back so quick! I posted a general thread as I thought it would not be a problem specific to your mod but rather my method or lack thereof
Now the problem is... I can't run logcat either.:
- exec '/system/bin/sh' failed: No such file or directory (2) -
when I go to the recovery image I am quite sure it is the stock one (3D exclamation mark with a phone next to it, then loads the reboot/apply update.zip/wipe data menu. There's also a warning "E: can't open /cache/recovery/command" in yellow at the bottom.

How you try to run logcat? "adb logcat"?

Apparently you can reinstall a recovery using that Droid Explorer?.... I'd try that for AmonRa1.6.2 if Radug cant help you once you have supplied a logcat.
Then load into the recovery, do your wipes, and flash again.

..... And please post in GENERAL or QnA next time.

are you able load into armon recovery console?
if yes try wipe everything & reflash others custom rom then wipe again & reflash ChocolateEclair 1.0.1. i also face the same problem just now when i'm at work *playing with roms secretly* ^^"
i load in success without seeing the green screen now =)
& best not to use the ExtremeKernel as not all phone can support as stated on the dev post =)

ddotpatel said:
Apparently you can reinstall a recovery using that Droid Explorer?.... I'd try that for AmonRa1.6.2 if Radug cant help you once you have supplied a logcat.
Then load into the recovery, do your wipes, and flash again.
Click to expand...
Click to collapse
he is unable to do this atm, as he is stuck at the boot screen...so unable to load previous ROM...
ADB stuff should be the way

Most likely his hero cant be overclocked to 69x mhz. So flash the low kernel.

jarski12345 said:
Most likely his hero cant be overclocked to 69x mhz. So flash the low kernel.
Click to expand...
Click to collapse
I'm quite sure this is the case... but I am so far unable to put in any other ROM. When i get into the stock recovery console, I can select the "apply update.zip" option, but pressing the trackball does nothing, same with the factory wipe option. Are there any other button combinations for these? It says Alt+S and Alt+W for these options, but without a physical keyboard, how to do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Droid Explorer does let me update a new ROM, but... nothing happens on the phone.
As for trying to put in a new recovery through Droid Explorer, it can only do so by pulling the file for the SDcard... which is not detected when the phone is in recovery mode
I tried to run a recent HTC RUU, but it does not detect the phone...
Last option seems to be working from ADB, yes... But half the commands I try end up with the error "- exec '/system/bin/sh' failed: No such file or directory (2) -"
So, are there any ADB commands I could try, to wipe the device?

Urgent Request

Hi , i have motorola defy , and i have flashed many roms without any defect , but today , i've flashed CM10 with its Gapps , but the mobile be always show 100% battery , so i thought that will resolved after rebooting the mobile ,, but when i reboot the mobile , it doesn't work unless i put it on charge .
when i put it on charge it start but stop in booting showing battery icon question mark in it !!! and when i remove tho charge wire to put it in the computer to flash another rom it turned off !! please i need your help
this exactly as icon i have !!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

That's a defy?? Looks nothing at all like any defy I've seen.
Anyway, you probably should read this:
http://forum.xda-developers.com/showthread.php?t=2016041
And follow these instructions, if they apply:
http://forum.xda-developers.com/showthread.php?t=2011990

I had the same problem. Resolved it in "mcgiver mode"...search for it around there are instructions..
Sent from my MB525 using xda app-developers app

thanks
Antiga Prime said:
That's a defy?? Looks nothing at all like any defy I've seen.
Anyway, you probably should read this:
http://forum.xda-developers.com/showthread.php?t=2016041
And follow these instructions, if they apply:
http://forum.xda-developers.com/showthread.php?t=2011990
Click to expand...
Click to collapse
thank you for replaying ,, actually i have tried battery fix and the problem is resolved ,, thanks a lot for you , but i faced another problem which is when i try to flash any rom , this message appear :
bootmenu recovery v5.0.6
E:can't mount / cash / recovery / command
E:can't mount / cash / recovery / log
E:can't mount / cash / recovery / log
E:can't mount / cash / recovery / last log
E:can't mount / cash / recovery / last log
do you have any idea ?

What base stock rom are you using? And what model Defy is that, anyway?
Secondly, are you trying to flash a ROM with Clockworkmod? I'm just asking because I've always known CWM's recovery to say something like "ClockworkMod Recovery (version number)", and not "bootmenu recovery" (which seems like the stock recovery), which, if that is the case, are you renaming the ROM file to "update.zip" and flashing it through stock?
The procedure you are using to flash would help (and a pic of the recovery too)
EDIT: Is your phone actually booting up??? I just recalled that sometimes when I used the stock recovery with my Defy I would get error messages like that, but my phone worked normally.

Nexus 4 - wiped internal storage & pc wont recognize phone so stuck in recovery mode

Nexus 4 - wiped internal storage & pc wont recognize phone so stuck in recovery mode
before i start, i would like to say that my last experience with android phone, rooting and other stuff related to android was last october 2013. please bear with me
i posted this exact texts below before before i gave up on my nexus 4. now after 2 years, im ready to get frustated again. so here it is
----------
my problem started after i updated to oct 7 cm10.3 nightly. my pc and my mbp cant read my nexus storage.
searched for this problem and found some few n4 users that experienced this but my main problem is there is no android device listed on my device manager.
i checked for all possible solutions:
- uninstall driver on device manager and reconnect the phone to install the driver automatically (but theres no android device listed)
- changed the storage settings as to connect to mtp
- restore factory settings and wipe data
- tried different data cables
- changed my rom from cm to pa
- restart phone
- push adb but device not found (but my pc doesnt recognize my phone)
- turned on/off usb debugging (still cant read)
then out of frustration, i wiped my storage data completely
so now, i cant flash any roms, no files found on system
i cant push adb because my pc cant find my phone even in recovery and device manager, even in USBDeview
but the unit is till charging
i sent it to lg and they said the board was the problem and the replacement was expensive so i gave up and bought another phone
----------
google released pixel and i began to miss my n4 so tried to recover it
the condition is the same 2 years ago. placed it in storage after got frustrated
so anyone has an idea?

If the phone is recognized in fastboot mode, flash TWRP, boot into TRWP, mount storage, copy a custom ROM to the phone, and flash from TWRP.
As an alternative, you can flash a stock Google ROM if fastboot commands are working.

Hey!
Maybe it's just a minor "hardware problem". Did you check if there is any lint between the micro usb connector-plate and the back (see attachment)? Mine caught dirt and lint over time. With a thin but sturdy piece of plastic I could remove the dirt again, and suddenly all my cables started to work again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

thank you audit13 and smeee_again for your replies. ill look into both of it!

Phone should be recognized in Bootloader mode anyway, try different drivers, then fastboot flash stock and re-root
Optionally, boot into recovery, connect cable and go to mount options then mount usb storage, put any ROM in storage and flash it, the trick is it shouldn't require specific drivers as storage via recovery shouldn't use MTP but generic USB connection (like pendrive) as far as I know.

If you don't want to root and install a custom recovery just download and fastboot the Fake Nexus ROM which will give you a stock experience really easily and also it will be Nougat . Check out the thread for how to install it, it's really easy.

Bootloop Android 10: enablefilecrypto_failed boot issue after recent update

I got an OTA security update few days back. The update was done successfully. Then I ran out of charge and the phone switched off during usage. When I charged and tried turning back it on, the phone got stuck in the android one screen and it rebooted. It again got stuck in the android one screen and the following message opens up in android recovery mode.
Code:
Android Recovery
Nokia/Dragon_00WW/DRG_sprout
10/QKQ1.190828.002/00ww_4_10D
user/release-keys
Use volume up/down and power.
Code:
Cannot load Android system. Your data may be corrupt.
If you continue to get this message, you may need to perform
a factory data reset and erase all user data stored on this device.
Then it shows options to select either Try again or do Factory data reset
The following code is shown at the bottom
Code:
Supported API: 3
Boot Reason: enablefilecrypto_failed
I found a similar issue in Nokia 7.1 after January update. The phone does not boot up. Is there a way to solve this issue?
I have some important data in my phone. Is there a way to recover them before resetting the phone?
Note: The phone is in stock condition with only usb debugging on.

Change slot, boot the device make sure there's enough storage available and then apply update.

same probelm , it return to recovery mode , any help

On these phones. If phone stuck on Android One screen.
And when doing factory reset from recovery, if device stuck at wiping data.
Then it is a dead EMMC.

Same problem, can anyone help?

today i tried to flash OSt service tool this type problem facing device... than find [15:15:42::203][03964] [FB]: [Recv] FAILError flashing partition : Write Protected this error.... thats mean motherboard damage.
Sent from my TA-1054 using Tapatalk

D-Mi said:
Change slot, boot the device make sure there's enough storage available and then apply update.
Click to expand...
Click to collapse
Tried it and no improvement. Could you explain in detail so that I'll check whether proceeded correctly or will try again.
Is there any way in which I can recover the data even before the problem being solved?

Jenish_SweetRascal said:
Tried it and no improvement. Could you explain in detail so that I'll check whether proceeded correctly or will try again.
Is there any way in which I can recover the data even before the problem being solved?
Click to expand...
Click to collapse
At this point there's no way to recover your data, and the guide to change the current active slot you can find in the below link
https://www.google.com/amp/s/www.te...-stuck-on-download-mode-after-ota-update/amp/
The issue mentioned might not be similar but the solution you're looking for could be it I had a similar problem with a 7.1 that can't boot after a security patch update and everytime the update will download and after restart the phone will throw error and ask to factory reset I couldn't test this method on that phone as the person had set it up for work after a reset and willing to hold till he can visit a service center. And he said he didn't have much storage at the time of update so it got corrupted somehow

I tried the method I mentioned by changing the slot, my current slot is b and update is supposed to install on a, a is corrupt or something as soon I changed active to a the device will bootloop in android one screen and go to failed page and ask for reset after which it will boot on slot b, also tried to install the Feb SP manually which installed fine via adb but again after reboot it will act same, so the only way is to visit a service center or better pay it directly for a bootloader Unlock service to avoid any future software problems

?
juwelrana091 said:
On these phones. If phone stuck on Android One screen.
And when doing factory reset from recovery, if device stuck at wiping data.
Then it is a dead EMMC.
Click to expand...
Click to collapse
R u sure bro....ost is detecting my phone though

emmc damaged device also detect fastboot... when u try to flash through ost tool u will get those error. check ost tool log data... if it say write protected than u should be sure emmc damaged
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my TA-1054 using Tapatalk

Same issue I was facing but is fixed
So what did I do?
Downloaded stock ROM and installed using OST LA.
Then the update was installing but failed. [I was trying from last 1-2 months but getting same enablefilecryto_failed message but finally I solved it]
I downloaded OTA from website of same update and installed via ADB.
After installin OTA, It said it needs to "Format data" upon reboot.
I formated and mobile now has "Stock ROM".

SM-J510MN/DS with two problems: "E: failed to open" and "Device or resource busy".

I have a problem with the device: SM-J510MN/DS. It came to me with the problem. I don't know what was done before.
I installed as per the common guidelines and the problem persists with the messages:
"E: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory"
"E: ensure_path_unmounted failed to unmount /efs (Device or resource busy)"
If I restart, it stops on the screen with the "Samsung" logo in an eternal loop.
Tried Android 6.0.1 and 7.1.1.
I used Odin 3.12; 3.13 and 3.14.
I used TWRP 3.0.2 and 3.5.2.
Tried with FRP HiJacker too.
All forms without success so far.
Ps.: I looked for this in other forums for some weeks, but no get answer yet anyway...
Grateful if anyone can give me a hand!

gersonvagner said:
E: failed to open /dev/block/bootdevice/by-name/misc: No such file or directory"
"E: ensure_path_unmounted failed to unmount /efs (Device or resource busy)"
Click to expand...
Click to collapse
Where does this happen?

LR7875 said:
Where does this happen?
Click to expand...
Click to collapse
Hi. I am not a professional, so sorry, but when I try the "download area" for reinstall the original rom, all go fine. But it dont get in the main screem anyway and go to a "infinit loop" at the Samsung logo. This two messagens apear at the bottom in the "factory reset" menu.

gersonvagner said:
Hi. I am not a professional, so sorry, but when I try the "download area" for reinstall the original rom, all go fine. But it dont get in the main screem anyway and go to a "infinit loop" at the Samsung logo. This two messagens apear at the bottom in the "factory reset" menu.
Click to expand...
Click to collapse
So the phone just died on the Samsung logo and those words appears there?
Send me the words that appears on the download mode screen, that may help.

Here, is this menu on the bottom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

First install 'TWRP' software, this will allow you to install a custom system.
[RECOVERY][TWRP][J510][AROMA] 3.1.1-0 for J5**2016 [UPDATED MTP-OK!]
TWRP 3.1.1-0 for Samsung Galaxy J5 2016 with Aroma support by Lemlis ------------------------------------------------- J510FN--OK! J510GN--OK! J510MN--OK! J510H--OK! J510F--OK! ------------------------------------------------- Description...
forum.xda-developers.com
Disable auto reboot at odin options.

LR7875 said:
First install 'TWRP' software, this will allow you to install a custom system.
[RECOVERY][TWRP][J510][AROMA] 3.1.1-0 for J5**2016 [UPDATED MTP-OK!]
TWRP 3.1.1-0 for Samsung Galaxy J5 2016 with Aroma support by Lemlis ------------------------------------------------- J510FN--OK! J510GN--OK! J510MN--OK! J510H--OK! J510F--OK! ------------------------------------------------- Description...
forum.xda-developers.com
Disable auto reboot at odin options.
Click to expand...
Click to collapse
I tried with "I used TWRP 3.0.2 and 3.5.2.", as I say. But the same problem persists. Some especifc version can you tell me?

Well, I will try the post, and I will back to tell.

Immediately power off and press volume up +home+power after Odin success flashing.

LR7875 said:
Immediately power off and press volume up +home+power after Odin success flashing.
Click to expand...
Click to collapse
No work yet...

By the way , you tried flashing stock ROM, Odin says success, and the phone died in the boot screen?

LR7875 said:
By the way , you tried flashing stock ROM, Odin says success, and the phone died in the boot screen?
Click to expand...
Click to collapse
Sorry... I dont know if I understand what you mean...
First of all, sorry about my english, its not my first language, but I am trying! Sorry if I am sounds rude...
And Im not a professional, just trying to recover my wife celphone! haha
But Im think that the problem is the FRP... and I am stuck here...
I tryed to instal the original rom with Odin and I try the TWRP, but when I reboot, stuck in a eternal loop on the logo Samsung and the problems with the E: partition persist...
I tryed the post that you indicated, but it doesn't even finish successfully, as in the print.
Install rom is successfully!
But stuck in Samsung logo and, when Im going to recovey menu, the same problem with E: partition persist...
What Im forgoten?!?!?!

Seems like your bootloader is locked so you cannot flash TWRP.
What shows up on Samsung logo?

LR7875 said:
Seems like your bootloader is locked so you cannot flash TWRP.
What shows up on Samsung logo?
Click to expand...
Click to collapse
Nothing more, just the logo in a infinity loop.

Try enabling repartition in odin options while flashing stock ROM

LR7875 said:
Try enabling repartition in odin options while flashing stock ROM
Click to expand...
Click to collapse
I don't know, this is a bit dangerous, especially for inexperienced ones like me. I've read several articles about this option and it's not just click and be happy...

So, I tried this tutorial bellow after many more readings and the problem remains the same even after I tried it through Odin successfully.
https://technastic.com/odin-nand-erase-samsung/
If someone have any other idea...

did u get solution of this problem

gersonvagner said:
So, I tried this tutorial bellow after many more readings and the problem remains the same even after I tried it through Odin successfully.
https://technastic.com/odin-nand-erase-samsung/
If someone have any other idea...
Click to expand...
Click to collapse
did u get solution of this problem?

dafvad said:
did u get solution of this problem?
Click to expand...
Click to collapse
Not yet...
Its very sad, cause the celphone is relative new, but it stayed in the desk... dead.