Hello guys, I have this weird A3000-H problem.
So the tablet boots normally, it loads in one particular state every time, like it's booting an image. After a while or if you try to do something, running a program, uninstalling, changing settings it's starts the cascade of pretty much "every has stopped working" and it's like that until you restart it and it's all over the same again.
So far I've tried everything I could scour from the internet, XDA forums included.
• I've tried to flash new stock rom 4.2.2, then I tried the 4.4.2 from Hesham.
If I use an older, version 3 SP Flash Tools it gives me this error at the end:
imgur com a5oKTLw.png
If I use version 5+ of SP Flash Tools it gives me an "OK" download or upgrade, but when I disconnect and turn on the tablet it's in it's same previous state, it didn't change anything.
• I tried full format - it did absolutely nothing despite SPFT giving me the okay
SPFT memory test returns this error : .imgur com / jbSUwV5.png
• I tried writing memories - nothing changes despite getting on OK message.
• I tried to fastboot CWM - I can't make the tablet to enter the mode, it just restarts and boots in it's previous state.
• I've tried to connect it to PC and delete folders manually, despite windows saying the folders are deleted and not showing them anymore, as soon as I reconnect the tablet again they show up as they were. It's like the on board memory is locked to writing anything on it.
• Of course I tried manually resetting to factory settings, uninstalling software from the tablet and so on, but that just makes the errors of "stopped working" to pop and restart to same condition.
I would appreciate any help at this point, I'm about to give up on it.
P.S.: I can't post whole links yet so I had to improvise a bit.
Related
Hello guys.
I have an LG L5 (E610) that is having a very strange behavior.
It started by throwing a lot of ANR with different applications (Google Play Store, Play Services, Facebook, and others).
So, seeing this, I decided to do a factory reset. After reboot, what is my surprise that I see everything as I had before. All the applications, all the data, everything.
With this, I tried almost everything at the moment. And by saying that, I mean:
- Tried to follow the key combination for the recovery, it goes to recovery, I see the Android and some progress bar moving, but after the reboot, the system remains with no change;
- When on the system, I uninstall applications, they seem to be uninstalled, but after a reboot all the applications are back.
- Tried to root the phone with more than one process, no success. I cannot install any application. Not via play store, not via adb install, there is no way;
- Tried to flash a recovery img, to try to clean cache partition from there, no luck. From Fastboot it says everything went well, but when I reboot, everything is the same;
- In fastboot, I tried to erase cache and userdate partitions, no luck. When I try, i have a message saying "FAILED (status read failed (Too many links))". This happens with all the partitions. I even tried to erase the system partition, and I have the same response. Strange thing is that after this error, the phone reboots and goes directly to the system;
- Tried with KDZ images and tools to install different versions, I receive errors during the deployment and at the end the phone reboots. Again, the same system is installed as before. No changes.
As of now, I was trying to understand if there is any problem with the internal flash system. Maybe it is corrupted and is causing all these issues.
The thing is, as the phone is not rooted, I cannot launch a e2fsck to the maybe faulty mmcblk0pXX
The phone has a stock ROM based on Android 4.0.3 (build IML74K / LG-E610-V10e-JUN-30-2012)
I am out of ideas, I've looked around here at XDA, Google and I have no other ideas to try.
Does anyone have another suggestion?
Is there something else I can do to try to make the phone live again?
Any help someone can provide will be very much appreciated..
Now this is what I call a coincidence.
About 2 years ago, a friend of mine asked me for help with her E610. Almost all actions were giving us ANRs. Whatever you do, i.e. unsinstall, install, change, delete... after reboot/reset were all there, even notifications! Tried KDZ updater, and, while the update was OK without signs of errors or so, after reboot - nothing, everything was like before. After trying to find a solutions by hundreds of ways, with adb and fastboot commands (all partitions&folders were locked, no read, no write, and you can't see any file, tried root to no avail), L5 got bricked. She already got a new phone and this LG was laying there without any use.
Three days ago I decided to try again, with no hope tbh No screen, no vibration, nothing, apparently dead. But, I could install Qualcomm drivers and my Windows can see it in download mode. I think that the only way is to flash the phone with LGFlashTool and using COM port. I already extracted *.dz from *.kdz but I need the dll for FlashTool. Found 2 or 3 webs with this dll, but you need a 100 bucks subscription :crying: If anyone can upload that dll I'd be very happy to try to flash this phone I'm really big n00b in this, just a plain phone user, nothing more, so don't blame me if I said something wrong
Many thanks in advance.
same problem
Hello! Same problem...
My L5 is making me crazy... It has CyanogenMod 10 nighlty. A friend of mine was using it and he tried to install the GAPPS after he did a factory reset. I have no idea what guide he used but it got soft bricked... It's constantly showing a "stopped working" message and after a while reboots by itself.
I tried to do a factory reset but it always returns to the same point, same apps installed, everything like the reset never happened. I even used CWM to reset it and it allways goes back to the same recovery point.
After a while I decided to flash a stock room but here's the problem: I can't get into emergency mode.
After reading ALL post about it I found that there's at least three ways of entering EM, (1) down VOL and plug in usb cable without battery; (2) down+up VOL and plug in usb; (3) down+up VOL + power botton.
Conclusions:
(1) - gives me a screen full of code like a command line
(2) - White screen
(3) - White screen
I've read ALL the unbrinking post on the internet, including xda, and none of them helped.
The KDZ Updater never recognizes the phone. I installed all the drivers but everytime I plug in the phone it installes the same LGE MTP drive...
Can anyone help, please?!
How to enter Emergency mode? How to flash another rom?
I have tried searching, nothing has recovered it yet. In attempt to do this https://forum.xda-developers.com/showpost.php?p=72501544&postcount=25
I got to step 11, but didn't check fc well, and didn't have TWRP installed! Any hope?
I get a Battery ? on battery out. It makes a device driver connection and loads drivers, but doesn't seem to get into download or recovery. No connection on ADB, or Fastboot with my drivers that I've tried. The LGMobile Support Tool gives a battery or download error, and I've used another Leon to check it's 100% charged. I made the backups as stated in the howto above, but can't connect to do a restore. I've got pretty far with the disconnect after 5 seconds to bypass the battery check, but still nothing flashed. I may have tried more options to flash and nothing has worked, please ask to check if I've tried it already. My main reason for this attempt was to free up size for apps, and to utilize the SD card memory more effectively. I have not seen a menu or screen image except what I've mentioned.
Hi all,
:crying: - Looking for a way to get my Mi Note 2 back to life!
This device has never been unlocked or ROMed before (although it has been re-flashed successfully via Xiaomi's own pushed updates).
It is running MIUI 10.0.something (cannot access menus to verify exact).
The problem
----------------
I did a standard factory reset on the phone.
Once restarted, it takes you through the normal setup screens such as 'language', 'region', 'wifi network' after which I am given the option to select "copy your data from an old phone" or "set up as new", no matter which I select, my phone goes to the next screen which shows "Checking for updates". Here it stays - endlessly...
What have I tried?
----------------------
I have tried a different wifi network but it does the same.
I have also tried selecting "copy your data" instead of "set up as new" but it does the same.
Thoughts
------------
I thought I would try to install a new stock ROM to see if that would fix the issue. However, in order to unlock with the Mi bootloader unlock tool (and then use their flashing tool), apparently to do this, I need to enable something under developer options - clearly impossible when I cannot get to any android menus.
The phone *can* be re-started into the fastboot screen but does this help me at all?
On the MIUI website I noticed the following in the tips and tutorials forum: How to install a MIUI update without unlocking the bootloader: https://en.miui.com/thread-3852597-1-1.html
The above got me slightly excited before I realised that I have no way to place a ROM into the ‘downloaded_rom’ folder in the internal storage of my device (as the article instructs). Note that the reason for this (on my phone at least) is that although a Windows explorer window does open when I connect the phone to my laptop, it is empty (i.e. you cannot see any files/folders in it). BTW - I know what causes that specific issue as that bug was present in the device ages ago - basically, the phone seems to default to be in USB charge mode and in order to see the folders in Windows Explorer, you have to go into developer options and manually change the USB mode and then change it back to MTP mode. Once that is done, you can see the files/folder structures. However, I cannot get to any developer options as I cannot get to Settings at all.
What can I do?
------------------
So my burning question is this: How can I re-ROM this theoretically 'working' device, given the above constraints?
Is there any way to do anything while the phone is in the fastboot mode perhaps?
Is there some method maybe used to recover a bricked device that I could employ here?
Thank you for any help offered!
Cheers!
Hi all. If anyone could help me out I"d greatly appreciate your time and any advice.
So I got this tablet from my brother, working and all, but Google FRP was on it and he couldn't remember the credentials from when he first set it up. "No worries," I proclaimed like some advanced Android tech, lol, "I'll get it running" First thing, I downloaded the "stock.img" firmware from the only other ONN tablet page. Then SPFLASH tools. Then I plugged in the tablet; holy crap theres instant connection (this is better than ODIN haha). I immediately click the Download tab, load the scatter file, the stock directory, etc and hit "Download" after only a couple of minutes, SUCCESS.
So it reboots.
Oh, wait wait, I did nothing to format the tablet and so I'm just back at FRP.
Back to fastboot.
Open SPFlash Tools and goto format, formal all except bootloader, Start. Now though, as I'm waiting, I look over and my niece is pressing buttons on it, nothing seemed to have happened tho on my PC except I noticed moments before, likely when my niece started pressing buttons out of my view, that the little red bar that normally shows progress turned completely red and filled from 0 to 100 in a split second. I left the device and PC alone, only to get a notification after just a couple of minutes reading:
"ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] ENABLE DRAM FAILED!
[HINT]:
Please check your load which matches to your target which is to be downloaded"
**I'm noticing that my PC, for whatever reason, is bouncing between seeing the device as USB Serial COM5 and "MK6***" So when the device bounces is when the connection seems to be losing. I'd be happy to share my output for format if this makes sense to anyone.
The only thing is, I cannot get any screen whatsoever to show up on this tablet. I've tried holding down power, power+vol down, power+vol up+vol down, for up to 30 seconds and yet nothing comes up. It's almost like I don't have a bootloader or anything anymore as the device just kind of seems stuck. Even if I try using the DOWNLOAD tab, I still get the message as above. If I try to do READBACK I get a slightly different message. The READBACK will start and the red bar doesn't fill up instantly but after a couple of minutes I get:
"ERROR : S_COM_PORT_OPEN_FAIL (1013)
[COM] FAILED TO OPEN COM PORT
[HINT]:
1.retry a new COM port (tried switching to another USB with no success);
2.retry a new cable;
3.retry a new device;
4.restart the computer and try again.
Am I missing drivers? I communicate with my MOTO on this laptop just fine because of the google usb_driver, but maybe I'm missing a driver? Or maybe the device is bricked in just a tiny instant of someone tapping a button?
Any help would be much appreciate. Thanks a lot!
I think I have an unsolved problem. I know it doesn't exist, but it's very hard to find it.
I know it's not the Plus, but the Model is the Moto C XT1754 (NAMATH) Android 7.0 Nogaut - NRD90M.060
And there is no specific topic for it, but they are very similar and I thought I could post it here.
It's a very complicated problem, so I'll explain in detail what happened and why I had to come here to solve it.
(translated)
- STARTING:
I installed a TWRP through the app, without unlocking the Bootloader.
Whenever I turned it on, at boot still, the message appeared:
'red state
Your device has failed verification and may not work properly
Your device will boot in 5 seconds'
But it called normally.
I installed 'Magisk Manager 24.2' by zip and app afterwards.
I activated 'Zygisk' and in DenyList I activated/hidden from Google Play Services completely. All.
I restarted the smartphone and Sitema started having numerous errors. Most of the apps that I opened, closed with error, and other apps in the background too, mainly Google Play Services.
I tried to solve this but I couldn't because the smartphone was unusable.
I decided to format by TWRP.
But when I tried to restart the device, I always entered TWRP and continued that message in Boot ('Red State Your Device...')
I decided to reinstall Stockrom from Moto C XT1754.
When I tried to install Stockrom through flash_tool, I couldn't.
It always gives error.
'BROM ERROR : S_BROM_CMD_STARTCMD_FAIL (0x7D5)
[BROM] Can not pass bootrom start command! Possibly target power up too early.
[HINT}:'
or this one is the most common:
'BROM ERROR : ?? (0x1)
[HINT];'
I even tried installing a Custom Rom via Sdcard , 'Viper-namath-20171206-Coral-v3.1.1-UNOFFICIAL' with the GAPPs, etc.
I can install the ROM. (but the GAPPS gives an error at the end of the installation) 'open_gapps-arm64-7.1-micro-20220215'
But I think this case is because it is not installing the Custom ROM correctly. (Because of the Locked Bootloader? Maybe... I'm kind of a layman on the subject)
Because when I restart the device after installation it goes back to TWRP.
I can't get into Fastboot mode with the command by the buttons on the device, only by TWRP when I access 'Reboot>Bootloader'.
Reboot and go to fastboot (Black screen, down there written '=> FASTBOOT mode...'
I've already tried to recover/rescue the device by Motorola/Lenovo's 'Rescue and Smart Assistant'. But when I try to rescue it (with it connected to TWRP) it asks to accept the message to enable USB debugging.
But I don't have access to this window through TWRP.
Here comes the big question, why I am not able to solve my problem:
I think my 'USB Debugging' was off/disabled before I erased everything (formatted).
I'll try Stockrom's Flash through TWRP to see if it solves the problem, but I don't think it will.
I think the problem may be with the 'USB Cable' as well. He's old. I tested with a non-original USB cable that I had to see and I can't either, the errors persisted.
I plan on getting another original to test as well.
Just an observation.
My device is being recognized as 'USB MTP Device' (under 'Portable Devices')
If anyone can save me, I'd really appreciate it!
Thanks in advance for all the help! Every opinion matters!
And when I give the command 'ADB Devices' my device appears 'unauthorized'
'ZW3223CGWK unauthorized'