Hi all,
I tried to back up my samsung galaxy ace and when accessing the playstore the device froze and upon a battery pull
started to get stuck on the samsung logo or a continual system reboot without ever making it into android. I tried a long battery pull, rebooted the system and wied the cache partition none of which worked.
I was hoping to get the text messages and contacts off the internal storage so these can be transferred to a new phone.
Since then I have downloaded the SDK kit for google and downloaded the ADB drivers and can access ADB from a command prompt window.
I am hoping to be able to use ADB to use the "pull" command to retrieve files from the internal storage but when using the ADB devices command the phone does not show up so doing anything with ADB is not an option.
When I put the phone in download mode windows recognised it with an exclamation mark. I downloaded Kies and then windows started associating it with a CDC driver (whatever that is) but I cannot force windows to see the ADB driver.
I have tried manually pointing it to the ADB driver stored within the SDK ...folders but it just won't see it.
Further, I downloaded Clockworkmod for the galaxy ace as I hoped that it would give me options to boot into nandroid and get the files that way. It said the upgrade of firmware worked but now unless I force download mode when starting up, the phone goes straight in to the reboot system now, apply update etc menu but then says"E:failed to mount /system (Invalid argument)" twice and that's it.
I do not have usb debug enabled.
So, help needed please all you kind people out there. How I make windows see the ADB drivers or get it to recognise the phone for ADB access or is there any other way I can get these files off, by installing CWM I've only played around with the boot software and not the actual OS so the data should still be there, am I right?
These texts messages are more than important , both they and the contacts are crucial.
This all happened when I was trying to back up the data and now I can't.
I don't need to spare the phone just the data, surely someone somewhere can get at it?
Thanks
mr_stupot said:
Hi all,
I tried to back up my samsung galaxy ace and when accessing the playstore the device froze and upon a battery pull
started to get stuck on the samsung logo or a continual system reboot without ever making it into android. I tried a long battery pull, rebooted the system and wied the cache partition none of which worked.
...
When I put the phone in download mode windows recognised it with an exclamation mark. I downloaded Kies and then windows started associating it with a CDC driver (whatever that is) but I cannot force windows to see the ADB driver.
I have tried manually pointing it to the ADB driver stored within the SDK ...folders but it just won't see it.
Click to expand...
Click to collapse
Sounds similar to what happened to me, although on my LG G4. The phone randomly froze and then from there only would bootloop the LG screen, never making it to the Verizon screen. It turned out that components came loose within the phone which caused the boot to fail, as it was a known G4 issue.
What happened with my phone is that my computer wouldn't recognize it as anything other than my processor, and I could only stay in Download mode for about 1 minute before power off. Recovery mode literally had no effect other than "power off".
Personally, I wasn't worried about my data, so I sent it off to be repaired, but while searching around I found this post (can't post links yet, sorry):
Code:
forum.xda-developers.com/att-g4/general/lg-g4-stuck-bootloop-rma-solution-t3279690/post67131904#post67131904
This may be a way to get the data off, BUT ONLY IF you are suffering from the same issue. I'm sorry to say, but it is probably NOT the same issue, but seeing how no one has responded yet I figured I'd through you a lifeline. It's a possibility.
Best of luck to you though, and sorry I couldn't really answer the question.
Related
Hi all,
Looking for a little advice -- I've got a completely wiped (ie no data on the internal SD card) Galaxy Tab 10.1v that's stuck in a boot loop -- just continually cycles the first 'Galaxy Tab' logo again and again.
I'd ideally like to reset it to the stock Samsung 3.0.1 rom, but I can't get Odin to see the device.
I can happily get onto the Fastboot/Download mode screen, and Fastboot mode works fine (skitzandroid's recovery image from his rooting guide will let me get into basic recovery mode). However, switching to Download mode and checking with ADB for connected devices just yields a blank list -- ADB seemingly cannot find it, although it shows up in Windows Device Manager just fine.
I've confirmed ADB is working by plugging in my SGSII phone -- it's seen instantly.
I'm presuming that as ADB can't see the 10.1v, Odin can't either.
Does anyone have any advice on getting ADB to work?
Thanks!
------------------------------------------------------------------------------------
Scratch the above -- installed Kies and tried a bunch of different USB ports and that eventually fixed Odin's ability to detect the tablet. (It's worth noting that ADB still couldn't see it, however.)
Hope this helps anyone unfortunate enough to come across the same issue; I'm going to go clean the inside of my pants now.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi all,
So, I done effed up. I've been running Elegancia with no problems for a while now, and decided off the cuff to try something new. Long story short, I didn't read properly and ended up flashing an International ROM to my phone by accident. No problem, I think, I'll just ADB sideload Elegancia again.
I boot into TWRP recovery and then find that my computer no longer recognizes my phone. So, I hit restore on TWRP, and restore a backup that I'd made beforehand. After everything finishes restoring, I discover to my dismay that the backup did not include my OS.
Now, when I power up my phone, I can boot only into bootloader. When I try to boot into recovery, the phone is stuck on the TeamWin logo and doesn't move. If I turn on the phone without booting into bootloader, I'm stuck on HTC's logo. My primary goal right now is just
In conclusion, I have no idea what to do with the following problems:
1. When booting into bootloader, my computer no longer recognizes my device, so I have trouble flashing TWRP. Basically, my computer searches for an HTC MTP driver, and then fails to find one/install one. When I try to update the driver manually by downloading a MTP driver and then installing via Device Manager, Windows tells me I'm already using the most up-to-date version.
2. When booting into bootloader and then going to Recovery, my phone will boot into teamwin's logo ... and then not move from there.
I'm aware that I've screwed up pretty bad-- I've done my best to read stuff that's relevant, though. I'd love more help, please! Thanks in advance. Lots of invisible cookies coming your way.
[EDIT: It turns out TWRP was just taking a really, really, really long time to load. That said, my problem now is this:
- When going to Advanced -> ADB Sideload, my computer does not recognize my device when using adb devices.
How can I make sure that this actually works? Thanks again!]
[EDIT #2: Okay, um, I don't know why, but for some reason my computer now lists my device after going into sideload from TWRP. Maybe something to do with a reboot of my computer. If that's true, I feel really stupid. Will update if sideload doesn't work ... I think the cosmic gods are laughing at me. I guess all I had to do was post in xda-developers so that I could publicly embarrass myself before I fix my phone.]
[EDIT #3: Everything works and I'm dumb.]
Okay, so my phone's label is "P700" from "LG", I was flashing my rom with all the sucess to slimroms, but I decided to try a new one and basically I went to recovery options, deleted the /system and /data, what I didn't know is that /data is my sdcard, after doing that I was pretty much stuck in recovery mode, then I clicked on sideload and I was stuck in sideload, trying doing sideload from windows, but adb didn't recognize it, now after restarting my phone and plugging it into windows for 4 hours straight and downloading drivers, my adb finally see's it, once the adb started seeing it - I reboteed my phone into recovery because before it didn't work, anyway I end up with blank screen, and before I had just LG logo, now after putting the battery out and inside - my phone causes every windows system to restart with the error - IRQL_NOT_LESS_OR_EQUAL, maybe some of you experienced this, maybe not, I was wondering if I could somehow format my phone, reinstall kernel, reinstall rom and recovery system from Ubuntu, since adb still recognizes it and I think it won't crash Ubuntu.
i managed to delete twrp and when i did then it shows that the system has been destroyed and after restart it is stuck on
fastboot windows. i tried to connect it with my pc so i could install flash rom but it doesnt show up on pc after connecting to usb.
i dont understand what to do next... helppppppppppppppppppppppppp
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
twistyplain said:
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
Click to expand...
Click to collapse
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
AjTheKiller1 said:
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
Click to expand...
Click to collapse
Have you ever had your phone detected by your pc in fastboot mode? And if you connect it to the pc, does the computer play the hardware detected sound?
You need to rule out a driver issue. I'm not the only other person to get the "system has been destroyed" message and people usually get out of it. I don't know why yours is so problematic.
Had you successfully unlocked bootloader?
The Good old "System has been destroyed" Message. Well, This is terrible This should not happen in the first place. I assume it happened Because you wiped data and then deleted twrp. But If you want help you have to specify how exactly did you " Delete TWRP" What steps did you follow to Delete it. None the less the best bet on getting your device back would be to go to the nearest service center. Pretend you did nothing and maybe they will say you got a bad update.
Hi there! I'm hoping someone on XDA Developers can help me sort out a root gone-wrong.
I did my best to follow the guide on XDA. I have an Umidigi A9 Pro with 6gb ram. I was successfully able to get the android tools on PC and was able to unlock the bootloader. I went to the Umidigi website to get the ROM. I think I *might* have grabbed the wrong one. Once I got this zip from the Umidigi website, I unzipped the folder and copied the boot.img that was in that root folder to the device. I then went into Magisk and patched the img. I then copied the patched img to my PC then use the commands on the XDA guide to flash the image to the device, the flash was successful (I think). However the device is now stuck in a boot loop. The device displays the Umidigi OEM logo and the android logo; underneath it says in small text:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
after 5 seconds the screen goes black and then comes back with the same screen. This happens continuously. I have tried holding the volume down, the power button, and several combinations of volume up, down, and power. Holding all buttons down makes the screen stay black, however while plugged into the PC the PC still makes the device connected and disconnected sounds off and on. Whenever I release the buttons, it goes right back to the loop. Windows PC plays the device connected and disconnected sound on and off. The command prompt is not able to affect the device. When I run "adb devices" it doesn't display the phone so it doesn't seem that windows is detecting the device.
ROM: https://community.umidigi.com/forum.php?mod=viewthread&tid=22236&extra=page=1
https://www.umidigi.com/page-Download.html
I'm hoping for some help on this one
Thank you!
It should be obvious that when being in a bootloop ADB cannot function: On Android side the ADB daemon gets started and after seconds closed, and this over and over again.
In the simplest explanation, a bootloop describes when your phone is stuck in a loop of rebooting. The term "bootloop" is just a more common way of saying "reboot loop."
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Zeidwinder said:
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Click to expand...
Click to collapse
I honestly haven't messed with it since. It was a very cheap extra android phone I had laying around. Once it got messed up I pretty much just put it in a drawer and said "maybe another day"