Good morning friends ...
I am a frequent reader of the forum, however, I had to create my first post.
My problem comes down to a Galaxy S7560m, I do wipes and does not delete anything ... that's right, perfect phone to not lose data ...
the annoying it is that the process android forever when trying to uninstall some applications that must surely be the crux of the issue.
I've tried the uninstall the Safe Mode ... he says uninstalled all cute .. now off and connects it .. who is it? the damn apps.
I need a light ...
already tried everything I know
play new rom, root him, wipes, erase at Odin 3:09, and nothing erases the damned ...
if by chance someone has at least his PIT file because not found it on the internet, already I thought about re-create the partitions it could advance, but not match.
or if someone already took a similar situation and can give me a light ...
I will make it reported below what I tried to explain already do better
* Restoration of manufactures the menu (it says it will clean and bla bla bla, and when you restart enters recovery, oddly)
* New rom in Odin (in configurations says the rom code I installed nothing changes on the unit)
* New rom in odin selecting Nand Erase All (does not erase anything, is locked and error)
* Uninstall apps by safe mode (when you restart to leave safe mode they are there laughing at my face)
* Wipe data / wipe cache (says he gave the successfully wipes however not delete anything)
* Install custom rom (he does not leave, it says that it is not possible to verify the parameters of the image)
* Root it (the processes spend more to turn the unit remains the same
if someone have a light, please light the torch as the only solution remaining in my range would play him here on the third floor, however I think it is easier to damage the head of someone than own device.
grateful
Carlos
Related
Okay so,
I feel like this one's on the medium level of emergency here,
The issue is I flashed my cache, dalvick, factory reset, and (not sure) system to install Simple CM9, everything rolled along nicely except......
After booting into my promising new life, I noticed several issues:
KFU no longer recognized it, though the drivers still read "Android ADB Interface" in my computer
Google Apps would not sync my data, but still allows me to download apps from the play store
The sd Card partition no longer is shown by the OS, but still shows up when connected with usb (i'll be downloading a file manager soon, so this may answer itself to whether or not I can still access it)
TWRP will not boot by means of pressing the power button during initial boot
I understand I could solve my GAPPS sync problem by flashing them, and all my other problems wouldn't matter then. but I still have no means to flash'em.
Any and all help is GREATLY appreciated!
-a lowly noob
P.S. Everything about the ROM is fantastic except for those issues, (which are probably my fault) so many thanks on that end
P.P.S. (I do have a nandroid of my stock os before I wiped so If all else fails I can just go back to that if TWRP can be accessed and start over)
I seen a similar issue earlier and the guy fixed it by reinstalling the twrp
but u can always try going to reboot and select recovery and see if that works
gracci
That's a step in the right direction, thank you
no problem glad I could help
suddenly the GT-I8160P started to crash and reboot to crash again and so on.
details:
- the system metioned to be in reduced functionality due to less storage capacity.
- the phone rebooted after starting some app to analyse the memory usage.
- now the system comes up until a few seconds after the lock screen is displayed.
- I am able to unlock the phone and start an app (for example Contacts) and see all contacts are still there.
- but the time is not enough to do anything useful until the phone crashes again and reboots.
I tried:
- first use odin and flash the stock rom again > no result (phone is still on stock rom (4.1.2))
- odin flash the 4.1.2 stock rom without branding > time to crash is a little longer
I want to recover the contacts and some App data (i.e. Whats-App)
The idea to send a stop command via adb shell would be very good.
But adb doesn't find the device as it boots up. Cause the windows system hasn't the time to properly install the driver MTP-USB-Device before the phone crashes again and hence is disconnected what causes the driver installation to break. ADB can connect to the device when it is in recovery mode. BUt am I able to access the file system in this state?
As I am looking through the net for several hours now and trying several suggestions I was not able to get any progress...
If there is any idea I could try either for accessing the data or stopping the phone from rebooting your help would be very welcome. Thank you in advance
Maybe there is any solution with a configuration which is an initramfs which allows to mount the file system and to be connected anyhow (i.e. adb) but I didn't get any hint to something pointing into a similar direction. At least not without wiping the phone (including the data) in advance...
Does Clockwork Mod could be an option
I found the ClockworkMod.
Could this help to get an Recovery boot ?
Does an installation preserves the actual data on the device ?
How did you solve, please help
The issue is still under long-term investigation...
actual status : the boot loop is caused by a massive error in the filesystem of the data partition of the internal memory.
Without dedicated knowledge of the android / Linux / Unix system / boot process / and command line tools one will have no chance to recover anything.
Hence, the recovery of most user-data is very hard / not possible / not economic ... I still try some ideas with imaging the internal memory. But actually I have no great hope to get the user-data out of the boot-looping device.
Most parts of configuration (either system and apps) data might be able to be recovered.
Finally a factory rest will become necessary to get the functional device back.
After the factory reset there is no reason why the device should not work probably.
Phone M8 Europe, OS 6.12.401.4
problem:
phone is unaccessible - Error: com.android.systemui stopped working
This happens after he (is not sure tho...) had his phone updating. It was not reacting, so he restarted several times. Finaly he got "preparing apps" (not sure about the english term for it, its appears after you update before you) what amde he think there were an update.
Now after you start the phone the message "com.android.systemui stopped working" appears over the lockscreen. The lockscreen is still visible, clock shows and is not frozen also i can see the statusbar, Volume keys are working too. When i click ok on that message the lockscreen disappears, i sometimes get some screen flickering seeing a background picture (my friend does not know this). Touch inputs not accepted or nothing happens, same for volume keys but i can push power and choose to restart, airplane mode, shutdown and touch-choose this. If i understand that problem right, its related to the homescreen, so if i somehow can bypass this the apps and menus and stetting will work fine.
Now there can be 2 reasons for that. First something went wrong while updating and restarting and second a problem with the launcher (Smart Launcher) he installed on the phone because he had trouble accessing the statusbar.
Now i want to access the phone without factory reset because of all the important apps/data stored and not backed up...
I cannot access via adb - no device shown, i think because of usb debugging not enabled.
Delete the cache did not solve it. I cannot clear Dalvik, HTC Recovery does not show that option. Also installing TWRP is not possible because i cant unlock the phone.
When i install a stock rom its the same like factory reset, right?
HTC Sync Manager will not find the device either.
I am out of options, maybe you have some ideas? Is it possible to fix this without losing all the data? Are there other ways to access the phone like plug in a keyboard and use key combination to try to get into a menu?
maerzhase said:
I am out of options, maybe you have some ideas? Is it possible to fix this without losing all the data?
Click to expand...
Click to collapse
Probably not. If the OS is not accessible, and the phone was not previously bootloader unlocked & TWRP, there is no way to retrieve the data.
You can run the RUU, which will probably repair whatever is wrong with the OS. But the RUU will wipe all data on the phone.
Either follow the instructions here, to run the RUU by htc_fastboot: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Or if you have an SD card, it may be easier to rename the RUU zip to 0P6BIMG.zip , put it on the SD card, insert in phone. Then restart to bootloader, and it should auto detect the zip and install it.
---------- Post added at 09:45 AM ---------- Previous post was at 09:40 AM ----------
maerzhase said:
Also installing TWRP is not possible because i cant unlock the phone.
Click to expand...
Click to collapse
Don't know what you mean by "can't unlock the phone"
Does that mean you tried, but were not successful? If so, describe the exact steps you took, commands, and specific outputs, error messages, phone status that resulted, etc.
Probably bootloader unlock is perfectly possible, and you just aren't doing it 100% correct. Although the process to RUU is probably easier. Unless you also want to root, custom ROM, etc.
Also, unlocking the bootloader will wipe all data on the phone.
Thanks for your help redpoint73.
Apparently i did not properly read the "how to unlock/twrp", looks like i dont need to put the phone into usb debugging.... Nevertheless does the disclaimer on htcdev warn me about getting all user data deleted in the process :/
Biggest problem is to get the user data, but all solutions i found to get access to the phone involve clearing it. A factory reset will do the trick and she can use the phone again i guess, since the phone is not exactly bricked...more like softlocked. Everything seems to be running fine but the home/lock-screen. If that wont help i will run that RUU.
I will do some more research maybe i find some other solution to bypass it, if not i will we reset.
Also i dont understand how data can be so important that its a tragedy if its gone, but not important enough to backup. but thats not my problem.
maerzhase said:
Also i dont understand how data can be so important that its a tragedy if its gone, but not important enough to backup.
Click to expand...
Click to collapse
There is no such thing. If the data is important to you (your friend, etc.), back it up. It's that simple.
There is a variety of ways to backup, and a number of tools were preinstalled on the phone. So there was really no reason for your friend to not be backing up.
Searching for ways to retrieve the data after something goes wrong, is not good plan. The likely result is going to be regret. But I guess some folks need to learn the hard way!
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
maerzhase said:
Apparently i did not properly read the "how to unlock/twrp", looks like i dont need to put the phone into usb debugging....
Click to expand...
Click to collapse
You don't need debugging for fastboot commands; you only need it for adb commands. While adb and fastboot are related, there are important differences. Fastboot (not adb) is what is needed to unlock the bootloader or RUU.
You were right, i was not able to save any data. The problem itself was solved with a reset - phone working again, top of the screen still not accessible, prob. broken.
Alright, hello everyone,
I'm having a pretty weird issue here. I've flashed my DUK-L09 and the C432B183 EU Firmware, everything was running fine.
I couldn't make a backup of the /data/ partition though, someone told me to wipe the data to decrypt it, but nothing came good after this.
So I tried to flash back the old recovery image by extracting it, flashing it via fastboot, as I would normally do; enter the factory reset, run it.
Everything is good, it goes up to 100% pretty fast, less than 2 minutes. I then enter the setup wizard the NFC is acting weird. It keeps activating
and deactivating illogically. So, ignoring this issue, I kept up configuring the phone then once I'm logged in Google and sync'd, pops a Huawei ID
logging page really really fast then goes back to the EMUI menu at the beginning of the Setup, in an infinite loop.
Useful information to let you help me better:
- Many firmwares. Currently trying to flash back to B120a and NoCheck from OldDroid and Morph. (Edit: Didn't work)
- Phone unlocked, TWRP accessible.
- Getting a weird "Error 9" when trying to run Update.zip from TWRP.
- Sideload working, but not transferring anything.
- Cannot find any B182 or B130 stock firmware. Everything seems to be gone from Huawei's servers.
- The loading logo isn't Honor anymore but Android, for a reason I can't yet understand.
- Restoring a clean backup (without /data/, since I couldn't back it up) did not fix the problem.
- Trying to update with the 3 buttons do not work, even with the right firmware (C432B183) (Software install failed)
- Factory reset works with the right ROM, but gets me to the setup loop issue.
- The loop occurs when I am supposed to see the Huawei ID setup page. If I do not put any SIM card, or WiFi
I am prompted to choose which way to restore data; if I skip this step, it blinks and doesn't do anything.
- I tried to restore via WiFi (Google's cloud stored data from my account), but it does the same thing as mentioned
earlier. It blinks multiple times rapidly the "Huawei ID" setup page then goes back to the first Setup screen w/o
me being able to do anything about that.
I'll be glad if you knew the answer to this, because I'm all lost right now.
Greetings, Kameyuu.
UP !
After many tries and a LOT of hard work, and spent an entire night (was about to spend the second night on this), I found the culprit and now I know what the issue is, it sounds completely legitimate.
So here are the reason and the solution to this issue:
Actually, my CUST was somehow broken. I never flashed it back because no one told me to flash the CUST.img back. They told me to flash BOOT, SYSTEM, and RECOVERY only.
So, after I downloaded a software called HUAWEI Multi-Tool (From hwmt.ru) I noticed they were also asking for the CUST.img and USERDATA.img (<- this one was apparently optional)
So, trying my luck I flashed it. Did a factory reset, and all, it acted weird and failed, then I tried again and it succeeded. So, with all my hope I booted the phone to the system, started configuring... And it worked !
I was able to set up the phone. For a -yet- unknown reason, some apps look missing and the NFC is still blinking on and off repeatedly and randomly, but I'm investigating that.
If you have any question on the precise steps feel free to send me a PM or ask in the thread directly I'll be glad to sort your issue out.
[EDIT]
Sorry, double post I don't know why my message was posted twice. Feel free to delete this message @moderators
SOLVED - Update below.
Hey guys,
I have an S9 (SM-G960F) which appears to have auto-updated during the night and as a result will now not boot. I am making an assumption it was an update of some sort as when I checked the time on it at 1am it was fine, when I woke around 8.30am the phone was off and when powering it on I ran into the issue. To summarise, I power the device on, get the Samsung loading screen, then the black swipe pattern screen to decrypt the phone, followed by the padlock unlocking loading screen, then the phone reboots. Sometimes however, the device gets past the padlock loading screen and says it is optimising apps, which is then followed by a reboot, briefly says it is installing system update before landing me at the Android Recovery screen.
What I've tried:
- Soft reset
- Booting in safe mode (same result as booting normally)
- Clearing cache partition
- Clearing app data
- Lacking storage booting (the device was quite low on storage last time I checked)
Some other (maybe) useful info:
I haven't updated the phone for months, could be why it did an auto update.
I'm on EE in the UK but IIRC the phone is not locked to EE.
Android Recovery has the following info when I load into it
Code:
samsung/starltexx/starlte
9/PPR1.180610.011/G960FXXU2CSB9
(options to try again, erase app data, power off, view rescue log)
#Reboot Recovery Cause is [system_server:12259 RecoverySystemRescueParty]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
Viewing the rescue log presents me with a stacktrace , the top of which is
Code:
*** FATAL EXCEPTION IN SYSTEM PROCESS: main
java.lang.RuntimeException: Failed to create service com.android.server.job.JobSchedulerService: service constructor threw an exception
(followed by the rest of the stacktrace I can get a picture of if necessary)
My goal here is to recover the photos on the internal storage as they don't appear to be backed up to Google photos, nor Samsung's alternative - which is particularly painful cause I'm the one usually preaching backups.
Is there anyway to recover the OS to retrieve data, or pull the data off the device without wiping it? I'm open to any suggestions on how to do this, the main goal here is saving my photos, hence why I have avoided a factory reset from the Android Recovery menu.
Hope I've been clear enough, but let me know if I need to clarify anything. I would greatly appreciate any suggestions!
Thanks,
Matt
Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt
Which version of Odin did you use?
majormatt said:
Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt
Click to expand...
Click to collapse
I would really appreciate it if you post a YouTube tutorial on how to fix this. Because we are facing the same problem right now but I have no idea what solution you prescribed. Thank you and God bless.