okay i tried a lot and searched a lot too but could not find solution to this one hope i am posting in right place
I got almost bricked tablet
i had twrp 2.8.x.x with cm12 running
i tried to factory reset from OS.
it went to reboot
AND only thing now i can see is TEAMWIN welcome page to recovery nothing else and it flashes every 4-5 seconds
cant connect it to fast boot
shows the devices in list of adb devices but takes no action
tries reboot using adb into recovery bootloader ALL but no effect
and somehow while trying different commands i was able to push new recovery and OS files to sdcard folder
also i m not able to start adb shell too
does anyone has any idea how to make this thing running again????
TIA
Related
Hi all,
hope this is the right place to ask this... I've been playing around with various custom ROMs on my Vodafone 845, and I was able to restore back to my previously working setup, but then I loaded the latest official ROM (again)
Now when I am in AmonRa recovery mode I can connect via adb, but it disconnects after about 2 seconds.
I have no problems staying connected to adb when the phone is fully booted, but the reason I need it in recovery mode is to restore my working settings.
I can't understand why it's behaving differently suddenly. I can run a single command in or through "adb shell" then it just disconnects.
I can't use the nandroid restore option in the recovery menu for some reason, it always says to use nandroid-mobile.sh through adb (which has worked well for me in the past)
I have re-flashed the AmonRa image several times in case. No change.
Please help!
Thanks
Jon
Ahh, found it! I had rebooted my machine and it restarted Android-Sync which kept interrupting it.
I killed the AS process before, so it wasn't a problem, and killing it now allowed me to get into adb and restore my system.
Yippee!!
My wife was using her phone (completely stock, no mods whatsoever) and it started shutting down processes (contacts, calendar, etc). She held the power button down to manually shutdown and then rebooted shortly after. The next day, it started to do it again, so she did the same thing only this time it stuck on the "M" logo screen. When she brought it home, I held the power & vol down buttons in for 2 minutes and the phone began to reboot but still stuck on the "M" logo screen.
I began searching vigorously online for a solution and have tried everything. **NOTE** - I am completely unsure what version of software the phone was running before this happened. The first thing I tried was RSD Lite with the JB Stock file from Team US Cellular. The flashing fails during certain lines of the .XML file. I took suggestions from other users to delete the lines it fails on and let the file continue the flash. Once it reboots, it is still stuck on the "M" logo screen. I then tried all the other stock firmware files I could and the same result each time.
Next, I tried using ADB and Fastboot tools. My PC recognizes the phone when plugged in and running command "adb devices" shows the phone listed, but whenever I try to run a pull or other command, I get error:closed. I've tried all the solutions of making sure ADB files are updated, running the list of commands to get the daemon connection reset, etc. I can't push/pull anything using adb. I tried using mFastboot with no luck either.
I tried the above steps over and over for 3 days straight, hoping I missed something simple. My final option was to boot into Recovery Mode and run Wipe Data/Factory Reset. When I select that option, about 3 lines of command begin to run and the phone reboots and goes back to being stuck on the "M" logo screen. The command lines and reboot literally happen within 2 seconds. That tells me Factory Reset is corrupted, but I'm not 100% at this point.
Does anyone have any insight on if there is anything I can do at this point? It wouldn't be such a big deal to lose the phone, but we have pics/videos of our 2 year old that we never got backed up at home or in the cloud and they're very important to us. Unfortunately, the phone did not have and SD card. I'm honestly out of ideas at this point and have never felt so defeated.
Thanks in advance.
mwc104 said:
My wife was using her phone (completely stock, no mods whatsoever) and it started shutting down processes (contacts, calendar, etc). She held the power button down to manually shutdown and then rebooted shortly after. The next day, it started to do it again, so she did the same thing only this time it stuck on the "M" logo screen. When she brought it home, I held the power & vol down buttons in for 2 minutes and the phone began to reboot but still stuck on the "M" logo screen.
I began searching vigorously online for a solution and have tried everything. **NOTE** - I am completely unsure what version of software the phone was running before this happened. The first thing I tried was RSD Lite with the JB Stock file from Team US Cellular. The flashing fails during certain lines of the .XML file. I took suggestions from other users to delete the lines it fails on and let the file continue the flash. Once it reboots, it is still stuck on the "M" logo screen. I then tried all the other stock firmware files I could and the same result each time.
Next, I tried using ADB and Fastboot tools. My PC recognizes the phone when plugged in and running command "adb devices" shows the phone listed, but whenever I try to run a pull or other command, I get error:closed. I've tried all the solutions of making sure ADB files are updated, running the list of commands to get the daemon connection reset, etc. I can't push/pull anything using adb. I tried using mFastboot with no luck either.
I tried the above steps over and over for 3 days straight, hoping I missed something simple. My final option was to boot into Recovery Mode and run Wipe Data/Factory Reset. When I select that option, about 3 lines of command begin to run and the phone reboots and goes back to being stuck on the "M" logo screen. The command lines and reboot literally happen within 2 seconds. That tells me Factory Reset is corrupted, but I'm not 100% at this point.
Does anyone have any insight on if there is anything I can do at this point? It wouldn't be such a big deal to lose the phone, but we have pics/videos of our 2 year old that we never got backed up at home or in the cloud and they're very important to us. Unfortunately, the phone did not have and SD card. I'm honestly out of ideas at this point and have never felt so defeated.
Thanks in advance.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. Please consider asking your question here:
Android Q&A, Help & Troubleshooting
You'll find expert advice there. Good luck!
Hello, i've bought this Samsung SM-T210 like 3 years ago, i rooted it as soon as i got it and after a year or so i decided to go back to factory settings cos of too many trash files anyway as far as i can remember i've select the wipe data or somethin and it got stuck on "Boot Loop" thingy only samsung logo comes up over and over again till i turn it off so i have tried every single solution that i can find on google and forums best i could do was getting it out of boot loop, now it just directly boots into TWRP and i can not do anything over there can't install any roms nothing whenever i try to install somethin it just gives me bunch of errors with cant find cache, data etc . i saw people had same problem and they got solutions by installing a new os, rom whatever it's called, i know how to follow the instructions but those solutions about my problem didn't help at all, now after a year i've decided to fix it again do u guys have any other solutions about this ? i'm waiting for it the charge up gonna list the errors i get on each section of twrp. :crying: :crying: :crying:
When i press (power+home) i'm only getting a text on bottom left corner says POWER UPLOAD REASON: POWER KEY H/W REVISION : 0.3
(vlm down+power+home) only gets me to the black screen nothing comes up
(vlm up+power+home) TWRP interface
power key by itself does nothing anymore.
----
******i had access to download mode via adb by using "adb reboot download"
i tried to install my firmware using odin and surprisingly it started to work again and im sure i've tried this billions of time.***********
semavi said:
Hello, i've bought this Samsung SM-T210 like 3 years ago, i rooted it as soon as i got it and after a year or so i decided to go back to factory settings cos of too many trash files anyway as far as i can remember i've select the wipe data or somethin and it got stuck on "Boot Loop" thingy only samsung logo comes up over and over again till i turn it off so i have tried every single solution that i can find on google and forums best i could do was getting it out of boot loop, now it just directly boots into TWRP and i can not do anything over there can't install any roms nothing whenever i try to install somethin it just gives me bunch of errors with cant find cache, data etc . i saw people had same problem and they got solutions by installing a new os, rom whatever it's called, i know how to follow the instructions but those solutions about my problem didn't help at all, now after a year i've decided to fix it again do u guys have any other solutions about this ? i'm waiting for it the charge up gonna list the errors i get on each section of twrp. :crying: :crying: :crying:
When i press (power+home) i'm only getting a text on bottom left corner says POWER UPLOAD REASON: POWER KEY H/W REVISION : 0.3
(vlm down+power+home) only gets me to the black screen nothing comes up
(vlm up+power+home) TWRP interface
power key by itself does nothing anymore.
----
i had access to download mode via adb by using "adb reboot download"
i tried to install my firmware using odin and surprisingly it started to work again and im sure i've tried this billions of time.
Click to expand...
Click to collapse
I don't understand.
You're saying that you successfully flashed it with your firmware and it started working. Does this mean you don't have an issue now? Or is there still a problem?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
yea i couldnt even open up the download mode it was saying RUN RDX TOOL but i just ignored whatever it says and tried to install it with odin till it succeeds after a few tries it just completed the installation and simply started to running.
EDIT: title is incorrect, model is actually S2109A-F
Hi, I'm pretty novice but have searched a solid 2 days about this topic on this device.
The lenovo a2109a-f I recently got (I know, its like 4-5 years old, but for 40$, not a bad 9+" tablet) was in fine working order, but did have some bloatware. Feeling ballsy, I attempted a root, and now it boot loops, meaning it will constantly reboot and show the animated splash screen, and play the synthetic chime sound. Each loop lasts about 1-2 minutes.
Since I can still access the fastboot and the boot recovery I've tried the following:
1) attempt the install of a new rom (original ICS or JB for this device) from a micro SD card inserted into the slot
- no go, it says it mounts the sd card, but wont read from it
2) attempt factor reset (cache, factory reset etc)
- no change and same root file still shows up in the tablet "/sdcard/"
3) Rerun the flash recovery process
- Tablet seems to accept linux (from windows) commands via cmd (fastboot -i <address/commands go here>), but no change for the boot loop
4) attempted other recovery images in fastboot mode
- thought I actually damaged it more. Since it stopped boot looping but wouldn't even boot to recovery at all. I then flashed the original recovery ("CWM_S2109.img") and was able to get the bootloader back and the bootlooping behavior again.
My question for you all, is there something I need to do via the fastboot method to clear the cache of the bootloader, or the memory of the device and install the bootloader that way and hope it accepts a basic OEM rom? Again, I'm no programmer, but am able to follow instructions and would love to be able to fix my 40$ mistake here sometime. Thanks in advance for all your help. I've used a lot of your tips and resources here over the years and have learned a lot from your skills and experience.
Hi,
Since yesterday, my phone suddenly went into a bootloop (I wasn't even using it, but it suddenly started vibrating every half a minute or so). I'm able to get into fastboot mode, but from there if I try to boot into TWRP, it just shows the splash screen for a bit, and then crashes and reboots again. I should say that this is my brother's old phone he gave to me, so I'm not exactly sure what he's done to it, and I'm also not particularly familiar with Android stuff myself.
Is there anything I could try to retrieve data from the device? I've managed to run a different recovery img (included in here: https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_One/), which allowed me to use ADB from my MacBook, and from there I tried to use the adb backup command, but this just gives me "Now unlock your device and confirm the backup operation..." without actually showing anything on the phone.
And even if I can't recover anything, is there anything I could try to bring the device back into a working state?
since your fastboot is working, you can try downloading the bacon roottoolkit and restore stock rom, before doing that install all the drivers like it mentions in the app. https://androidfilehost.com/?fid=95916177934555863;
Let me know if this works