Hello guys, i have been reading the forums for a long time now and it's finally time i registered to ask you about a problem of mine.
I purchased a TF300T around two months ago and it was already unlocked from the previous owner. I went straight ahead and installed TWRP and CM 12.1 (nightlies) on it. Everything was working fine, i could update to newer versions of the nightlies (only problem was that if i updated them through the system the downloaded update was giving me an error).
For some days now the tablet had been really slow and so i thought i would factory reset it in order to empty it and be like new. I went into settings>backup and restore>factory reset (if i remember correctly). It restarted my tablet and tried to boot into recovery. I see the teamwin logo but nothing happens and every 20-30 seconds the screen just blinks for a brief second. I also tried to use adb reboot bootloader but nothing was happening. I can't get into the bootloader neither this way or by pressing the buttons on the tablet.
Do you think i have probably bricked it somehow? What would you reccomend me to do in order to fix it? If there's any more info you want I'd be glad to answer.
Thanks for your time everyone!
Edit:
After a lot of searching i finally was able to restore my tablet and it now works fine. I used these guides to fix it and i'm linking to those in case anyone in the future finds this post.
http://forum.xda-developers.com/showthread.php?t=2528976
http://forum.xda-developers.com/showthread.php?t=2403674
Related
I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Orical said:
I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Click to expand...
Click to collapse
If you boot into recovery or hard reset by holding the power button. It will always ask to send crash report
OK cool so it's normal, thanks for the information.
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
m_hawkmoon said:
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
Click to expand...
Click to collapse
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Theonew said:
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Click to expand...
Click to collapse
The phone rebooted automatically. Did not give me the chance to do anything beforehand.
As you said the phone was soft bricked so when i got home that day i just fixed it. No problem. However I am really really into getting to find out how a 1 day old back up can get corrupted.
I've been working on this for nearly three days. My pad has been having issues for a while. Really laggy and slow. Finally couldn't take it anymore. I've restored to factory a number of times and while it helped briefly the lag always returned within a few days. Since I rooted (with Motochopper) and unlocked my pad the improvement is very, very noticeable. Faster than it was out of the box. I've been trying to install Cyanogen, but from the start I've been getting stuck at "booting recovery kernel image" whenever I try and boot into recovery. CWM can't get into it either. I tried TWRP instead but apparently their website is down because I can't access it via CWM or a web browser. I rolled the rom back to the last 4.1 and thought I'd bricked it. Kept getting stuck at spinning wheel on every restart. Wiped data and it restarted fine.
I'm convinced that it's the kernel issue, but after extensive searches I can't find a way to overwrite it without having access to "recovery". Yes, I'm noobish. I haven't cracked anything since my original Razr many a moon ago.
Any help would be greatly appreciated cuz im about to lose my marbles
Thanks!
Hi everyone!
Yesterday my GT-3100 got stuck on bootloop. Around two years ago, I got tired of seeing the Jellybean look so I gave custom ROMs a try. Even though I was incredibly scared of bricking my device, I went through with it anyway and flashed CyanogenMod 12 and made sure to make a backup of the stock version. Ever since then I've used the upgraded Lollipop 5.0.2 version. Occasionally it would get stuck on bootloop and it would get fixed on erasing the cache partition. Just yesterday the bootloop started again and even after trying everything, nothing's working.
I have CWM Recovery v6.0.2.7 installed, which I installed 1.5 years ago. I have tried factory resetting and after it rebooted I realized that nothing was even erased. My backup seemed to have disappeared as well since CWM can't find it even though it takes up almost 8Gbs of storage. After restarting, the home screen appears for about 30 seconds before restarting again in a continuous cycle.
I'm a noob when it comes to these things so any help (in simplified language) helps.
Thank you so much! :laugh:
Its probably a broken emmc. That means you need to replace the motherboard.
I installed Lineage on my Moto G7 Power a few days ago, and after rebooting it yesterday, it's stuck in bootloop (the Lineage starting animation is displaying), i have left it for 4 hours with nothing changing. can reboot it by holding the power button and I am able to get into recovery. USB debugging still works aswell.
I installed the newest nightly Lineage build for ocean (19.1), along with MindTheGapps and TWRP.
This has happened again, 2 days ago. I tried dirty flashing the same lineage version and nothing happened. I ended up completely restoring my phone using the official tool motorola provides.
then, after reinstalling lineage and twrp this time (so i would have access to my data if it were to happen again), and setting everthing up again, it just happened again yesterday.
things I've tried:
- clearing the cache using twrp
- letting it boot for hours on end
- repairing the file system with twrp (idek what that does, but I had hopes)
I would really like to just find a solution to this, as I very much enjoyed using Lineage (when it was working), but reinstalling everything every 2 days is not an option. this **** is driving me insane, i haven't been able to find a decently answered forum post on this anywhere.
so yeah, i would be eternally grateful for any help I can get.
thank you <3
Hello,
Did you ever find a solution to this? I am unable to boot into LineageOS as well, the boot just hangs. Posted on this thread: https://forum.xda-developers.com/t/official-lineageos-19-1-for-the-moto-g7-g7-power.4436929/page-7
greenmatrix said:
Hello,
Did you ever find a solution to this? I am unable to boot into LineageOS as well, the boot just hangs. Posted on this thread: https://forum.xda-developers.com/t/official-lineageos-19-1-for-the-moto-g7-g7-power.4436929/page-7
Click to expand...
Click to collapse
no, I'm sorry, I have nothing. I gave up after the fourth time of wiping everything and am back to using the motorola rom. a real shame
good luck tho and if you find something that works, do let me know please!!
Bummer. I will let you know if I figure it out.
Got it working, see https://forum.xda-developers.com/t/...or-the-moto-g7-g7-power.4436929/post-87342621