So I got a htc mytouch 4g And it has that phone icon with a triangle and exclamtion mark. I dont know anything about this phone since I have a att captivate From what I read is that if you have recovery you might be able to do it.
Also when I plug in the usb I go into recover and I Get a fasboot screen and other sorts of menus i have put a pd15img.zip in my external sd card and it loads installs It I guess but still boots into the same Icon.
from what I also read is that you can fix this by loading a stock rom pushing into your sdcard via adb but make sure is name update.zip but when I do that I get Invalid Operation.
when in recovery I have this message E:cant't open /cache/recovery/command also phone boots right into that icon.
{
"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"
}
I assume this is a soft brick since I get into recover and the other fasboot menu when I plug in USB any help is appreciated
This is my first time with a phone like this so I'm doing what I would normaly do with a captivate ish
I answered in your other thread here. However, now that you've posted a screenshot, I see that the phone isn't even rooted. I have no idea how you get into a custom recovery without root.
I connect usb while the phoneis off and then press volume up + power and that appears.
chibixzero said:
I connect usb while the phoneis off and then press volume up + power and that appears.
Click to expand...
Click to collapse
Yeah, see where it says "S-ON"? That means the phone isn't rooted. You need to perm root and it install CWM recovery, but with those cache errors you're getting, I'm not sure there's any point since those usually indicate a failed eMMC.
Guess my options are
1. call t-mobile and tell them what happen maybe they will replace it but I didnt buy it with contract I'm att and was going to ask my friend to get me unlock code, But idk if its possible I drop it and theres a crack on the phone
2. sell it for parts...
>.< money down the drain I guess fuggin phone
You're booting into stock recovery by default, that's the "triange". That might happen if you have a VolumeDown key/trackpad stuck.
The error in the recovery is natural - stock recovery expects a command when booted into, but finds nothing.
Check that you're indeed installing a correct PD15IMG that contains a complete system image, and if you are and it still doesn't help - try to shake the phone on the side / upside down, to try and release the possibly stuck buttons. If it doesn't help - the phone needs warranty repair. T-Mobile or HTC directly, your choice. To send it to HTC, you pay the shipping. But in any case it's under warranty, unless it has water damage or something.
download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe
atifsh said:
download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe
Click to expand...
Click to collapse
That appears to be the Gingerbread leak from the Canadian HTC Panache, but you might want to describe to the OP what exactly it is. Most people won't blindly flash something to their phone without a little info first. Also, could that be flashed to a non-rooted device?
yes thats the official RUU of panache which is glacier inside.
yes u can flash as its RUU.exe u dont need root.
u can even comeback to official mytouch RUU.zip using this exe later if wanted.
because its exe it will reflash everything boot, recovery, splash, radio every thing, thus fixing any problem thats not hardware.
atifsh said:
download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe
Click to expand...
Click to collapse
i used this as noted but I get this error
Customer ID error (131) I read on these forums is has something todo with a goldcard?
Edit-
I manage to load a stock rom into a External sd card. it updated it everything pass exept step 8 it skip it and the said finish updateing press power to reboot. Rebooted but the whole (second) mytouch splash was going for a long time. I try to use the RUU.exe and it wont boot into bootloatder just boots and stays on the splash screen.
this is what I get now and is stuck on That screen updating radio
Damn.
That would be the first completely stock Mytouch4G in the forum that has a failed eMMC chip.
Yes, it's bricked, you need to exchange it.
But it's also a good proof that gfree has nothing to do with failed eMMC, extra write cycles of flashing ROMs most probably just speed up the destruction process.
you got one large scratch on screen, how good have you kept your phone? have you droped it badly once or twice?
when you used the RUU.exe when did u get that error, does it go upto where it showed you the rom version?
if u got there than you can try one more time but this time with official mytouch RUU.zip. i'll tell you how to do that, later if u got upto that part.
edit nevermind my post cameback above this
If it shows "Fail-PU" in bootloader - then the eMMC isn't functional anymore. No flashing will help him in this case, only warranty repair.
hmm too bad, feel sorry for him
Related
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?
I went and bricked my SGS again and thought great.. time to exchange again right? Wrong.
My Bell SGS is one of those cute ones that has no download mode. I thought all hope was lost. It wasn't.
It's simple, adb reboot recovery works fine. But trying to adb is a pain in the ass. Easy solution.
1) Get the one click root/unroot tool: http://forum.xda-developers.com/showthread.php?t=742403
2) Use the tool--any setting is fine, all we're using this for is getting into recovery mode. I clicked unroot 2.1.
3) Surprise! The tool can communicate with the phone just fine even though the phone is failing to boot. You're now in recovery mode.
4) Wipe the data and the cache on the device, and you're good as new. No flashing of update.zip required.
I guess that:
adb reboot recovery
would also work then?
Mithent said:
I guess that:
adb reboot recovery
would also work then?
Click to expand...
Click to collapse
You know, I have no idea. I'm assuming so since that's what I believe his software calls upon, but I've never actually tried it.
define your "bricked"
did you get this screen of
pc-!-phone ?
because in that screen, the phone is not recognized by windows when you plug in the USB cable
so ADB doesn't work when it's the phone is not listening to the PC
Mithent said:
I guess that:
adb reboot recovery
would also work then?
Click to expand...
Click to collapse
AllGamer said:
define your "bricked"
did you get this screen of
pc-!-phone ?
because in that screen, the phone is not recognized by windows when you plug in the USB cable
so ADB doesn't work when it's the phone is not listening to the PC
Click to expand...
Click to collapse
No, I did not get that screen. For me, it just blacked out and locked on bootup.
scouzer said:
No, I did not get that screen. For me, it just blacked out and locked on bootup.
Click to expand...
Click to collapse
then that is not bricked
that is just a software error
when you are truly bricked the phone will not do anything but show you only that screen
AllGamer said:
then that is not bricked
that is just a software error
when you are truly bricked the phone will not do anything but show you only that screen
Click to expand...
Click to collapse
Well I did not know this, and I doubt many people here do either. So I think it's helpful.
picture here
{
"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"
}
* adding it to wiki
Hope I never see that screen then, so if you see that is it game over....no chance of recovery?
galaxysman said:
Hope I never see that screen then, so if you see that is it game over....no chance of recovery?
Click to expand...
Click to collapse
If your phone is 3 button disabled, no chance of recovery. If you have 3 button recovery enabled, it's no big deal.
Cant you just send it into Samsung to recover it if its under warentee??
Cant you just send it into Samsung to recover it if its under warranty??
d3a said:
Cant you just send it into Samsung to recover it if its under warentee??
Click to expand...
Click to collapse
yes you can
actually i did that to mine the one that had the 3 buttons disabled
the new one i picked up have the 3 buttons working properly
Can the 3 button be enabled through a potential future software update?
Or is it something thats so hard-coded in, that it cannot he ever fixed
Ziostilon said:
Can the 3 button be enabled through a potential future software update?
Or is it something thats so hard-coded in, that it cannot he ever fixed
Click to expand...
Click to collapse
it's called a SPL, it might be possible to be fixed if some developers figures out how to copy a good SPL over the defective SPL, but at the moment there is no fix
When i press "3 button" i go to downloading mod, how to get in recovery ? Except from rom manager...
micri said:
When i press "3 button" i go to downloading mod, how to get in recovery ? Except from rom manager...
Click to expand...
Click to collapse
same 3 button, but use volume up instead of down
see the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/Vibrant_GT-I9000M
Someone please help
I was trying to run the DTJG4 with the 512 PITT through ODIN when it failed.
I tried again and it didnt flash, so I tried rebooting the phone.
Now I get nothing... just a black screen.
Plug in the power, nothing, plug in the USB, nothing.
Battery removed several times and tried powering up just with power and battery, and trying 3 button combo that didnt work before, but still nothing.
Any ideas?
Thanks
AllGamer said:
picture here
* adding it to wiki
Click to expand...
Click to collapse
I had I9000M do this, 3 button mode was not working and had to return it. It happened during a kies update, luckly, 20 minutes after I had bought it. So I went to a different store and got my current phone. This phone is the best one of the three I've owned. Either 3 button mode just works, and the g-sensor calibration is much closer to being dead on. So there are good ones out there.
I've had 3 total. Here's a breakdown.
1. Purchased august 6th. First phone sold in the store. Download and Recovery modes worked 25% of the time. G-sensor calibration was horrible. Also could not be unlocked.
2. August 21st. Could not get the phone into either mode with button presses. Phone unlocked, but bricked via kies update. Never got to test the g-sensor. Last phone in same store as first purchase.
3. August 21st. Near perfect phone. 100% sucess gettung into download or recovery modes. Unlocked easily, and G-sensor is just slightly off. No need for calibration, unless using as leveling device. Purchased at a store that got initial stock on august 8th.
So, there ARE good phones out there. But the majority by the sounds of it are less than good. Which is unforunate.
As a former samsung owner as well, this is dissapointing. The original galaxy i7500L is still officially running android 1.5 in canada. I just hope and pray samsung doesn't drop this device from their dev cycles. And better yet.. Can fix all these problems with an update somehow...
Sent from my GT-I9000M using XDA App
So, only that specific screen counts as a brick?
On mine the 3 button combo doesn't work (I can only get to some weird "upload mode"), and the phone is stuck on the "Samsung Galaxy S GT-I9000" screen when I boot it up.
Does that mean I should still be able to use ADB with it? The PC seems to recognize the phone (as "SAMSUNG USB Composite Device"), as well as Odin, but ADB doesn't.
I have just upgraded to FROYO through KIES after 3 HOURS of waiting.
But my is stuck at boot screen & vibrates..
i had tried the recovery but no use.
please help me...
Take the battery out, try recovery mode again.
Or you didnt uninstall your lagfix before updating.. If so, do a factory reset in the recovery console.
i did that by VOLUME UP + HOME + POWER.
it went into recovery mode i did every thing NO USE.
did wipe all data, factory, format sd card. Still no use.
i heard about hard reset VOLUME DOWN + (press & release) POWER
then clear storage.
BUT HARD RESET is not working for me..
Donald Nice said:
Or you didnt uninstall your lagfix before updating.. If so, do a factory reset in the recovery console.
Click to expand...
Click to collapse
i haven't installed any lagfix
If you are able to enter to download mode then try reflashing via odin it should work.
dalepraneeth said:
I have just upgraded to FROYO through KIES after 3 HOURS of waiting.
But my is stuck at boot screen & vibrates..
i had tried the recovery but no use.
please help me...
Click to expand...
Click to collapse
i had the same problem and just Vol Up+Home+Power then did a factory reset and then it started up normally.
i had the root & lagg fix when i updated to Android 2.2 Optus
Mr.Hunk said:
If you are able to enter to download mode then try reflashing via odin it should work.
Click to expand...
Click to collapse
how much time would it take through ODIN for flashing???
I got the same issue here. And my SGS can not boot into download mode by hold 3 buttons.
Anyone knows what's the option for me now?
Thanks
Hi
I had the same issue it vibrated and didn't boot up. Remove SD Card, go to recovery via VOL UP + HOME + POWER button when you see boot screen releae all buttons. You are in recovery mode. Vol up down and select wipe data/ factory reset, confirm and your device shall boot.
My SGS booted after this and Yes I had OCLF lagfix installed, device rooted which I didn't remove prior to update. Now its fine again.
Now i tried to flash it through ODIN.
It was taking a long time so i stopped
it is displaying this
{
"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"
}
[/URL] Uploaded with ImageShack.us[/IMG]
now please help me
dalepraneeth said:
Now i tried to flash it through ODIN.
It was taking a long time so i stopped
it is displaying this
[/URL] Uploaded with ImageShack.us[/IMG]
now please help me
Click to expand...
Click to collapse
From this screen you sholud be able to enter in downloadmode. And, but I'm not sure, from this screen Kies should be able to recover the phone too...
Any way:
Always is a solution.... Search here, on forum, about JIG method to unbrick Galaxy S. You have to made a 301kohms rezistor and connect it on 2 pins from a usb cable. You'll see more pictures, it's easy to made it...
This JIG rezistor will always put the phone in download mode. From here you can reflash with Odin any rom you want.
But, if Odin stopped, there are 2 possibilities: you don't have the phones drivers installed corectly, or (and most important) you don't close Kies from Task Manager before launch Odin. If Kies is runing will take the comm port busy and Odin can't use it to comunicate with the phone.
Always close all Kies applications before flashing with Odin. It's very important.
Good luck.
dentimarius said:
From this screen you sholud be able to enter in downloadmode. And, but I'm not sure, from this screen Kies should be able to recover the phone too...
Click to expand...
Click to collapse
I did not find that recovery.....
does that have to work if KIES pops some recovery of os????
please tell me a way to flash back to
original DDJG4 india firmware...
and is it possible to upgrade to FROYO using KIES after flashing???
have you tried adb search youtube for a tutorial. you can reboot/recovery or download and much much more.
MAKE SURE YOU ARE IN DEBUGGING MODE WITH ADB. and i take out the sim card and ext sd card.
you use commands like c:\androidsdk\tools\adb reboot download
c:\androidsdk\tools\adb reboot recovery
c:\androidsdk\tools\adb reboot
also try apk 3.0 this lets you install apk's via your pc right to your phone, search for z4root apk on this site and use adb to reboot into recovery to apply update.zip
hope this helps, i also have no 3 button combo
dalepraneeth said:
Now i tried to flash it through ODIN.
It was taking a long time so i stopped
it is displaying this
[/URL] Uploaded with ImageShack.us[/IMG]
now please help me
Click to expand...
Click to collapse
Not sure why you would purposly stop Odin while it was running. All you are doing is creating a worse and worse situation for yourself by doing things like that.
It seems to me that you do not know enough about flashing, etc to even be concidering doing so, so... I reccomend that after you finally get your device up and running again that you ONLY flash through Kies and dont do anything else as you will likely end up with one issue after the other...
yiannisthegreek said:
Not sure why you would purposly stop Odin while it was running. All you are doing is creating a worse and worse situation for yourself by doing things like that.
It seems to me that you do not know enough about flashing, etc to even be concidering doing so, so... I reccomend that after you finally get your device up and running again that you ONLY flash through Kies and dont do anything else as you will likely end up with one issue after the other...
Click to expand...
Click to collapse
personally it amazes me when i read some of the horror stories on this site, i find it very couragous that anyone would attempt this without proper research, .
some of the complex hacks i am seeing just aren't needed, yet people risk bricking their phones. Anyway good luck to all who venture in to flashing, you dont learn if you dont try and without mistakes we would not learn as much so thankyou i know no what not to do hi.
I got into the download mode finally by the hairdryer method and load the original optus jg4 rom into the phone, then upgrade to froyo again.
Now everything works fine.
jamyi said:
I got into the download mode finally by the hairdryer method and load the original optus jg4 rom into the phone, then upgrade to froyo again.
Now everything works fine.
Click to expand...
Click to collapse
I searched about the hairdryer method but I don't find anything. Can you help me with a link please?
jamyi said:
I got into the download mode finally by the hairdryer method and load the original optus jg4 rom into the phone, then upgrade to froyo again.
Now everything works fine.
Click to expand...
Click to collapse
I searched about the hairdryer method but I don't find anything. Can you help me with a link please?
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".
Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
{
"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"
}
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help
arksoother said:
Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help
Click to expand...
Click to collapse
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54
rahimali said:
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54
Click to expand...
Click to collapse
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.
arksoother said:
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.
Click to expand...
Click to collapse
Can you not even boot into bootloader/fastboot or TWRP/recovery?
You should be able to boot to recovery by following the steps shown here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/recovery-mode/
You could also try and boot into safe mode and try and use the magisk manager to uninstall magisk - howto here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/safe-mode/
okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?
arksoother said:
okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?
Click to expand...
Click to collapse
somebody else apparently had the same experience although on a different LG device -> https://forum.xda-developers.com/lg-spirit/help/help-fastboot-error-loading-keystore-t3430163
So it seems that fastboot commands may have been disabled which means you can't interact with the device in fastboot mode whatever you do.
If nothing else works, you could try and re-flash stock ROM if you can manage to get into download mode.
Best of luck!