Hey guys. I'm trying to figure out what's going wrong with my Transformer. I'm not experienced with Android development/ROM's so please bare with me.
Rooted my first Android device about a month ago. Made a stupid mistake placing the ROM I was planning to use on the external SD card & didn't backup the install I wiped. Recovered with an official Asus ROM & after about two hours fiddling around I managed to root & load my first ROM (Revolver, whoot!). Very pleased with myself!
Have been using the Revolver ROM for a month without any problems. No deep sleep etc, everything worked perfectly. Using the latest version of Clockworkmod, also no issues so far. Strange thing is that since last monday everytime I (re)boot the device it loads CWM instead of the Android OS. I can get back into Android bij holding volume down during boot & choose to cold boot. Not a big issue but very annoying & can't seem to find the fix.
Searched Google & XDA for a solution. Updated Revolver to 1.3.1 beta, also found the repack by Koush for CWM. Tried fixing permissions, clearing cache, clearing dalvik, wiping & starting over, etc. Everything I tried so far does not fix the CWM-loop I seem to be stuck in.
Would really appreciate some help, I'm probably looking in the wrong direction here. Thanks in advance.
Found something
Finally got out of the CWM loop, found a solution here: http://forum.xda-developers.com/showthread.php?t=1622814&page=2
Strange thing is that after I flashed it with the fix CWM changed to the touch mod I recently installed but never seemed to work. If I understand correctly the fix only deleted the first few lines in the config where the boot in recovery flag should be.
Afterwards I factory wiped the unit & flashed it with a clean ROM. Currently re-installing my apps. I do not have a good feeling on this, tablet seems sluggish last couple of days & I can hear a soft click when the unit reboots. Same sort of click a laptop hdd would make.
Think it's dying on me...
Hi All,
I've searched across forum to find also similar cases, but no results so far.
I have a N4 with TWRP and CM (previously running 10.1.2)
Today I decided to install the new 10.2.
Installation went fine but after the restart I've noticed some strange behaviour with some applications (missing from phone, but installed for my play store account)
I've decided to reboot again the phone, and since that time I'm stuck with the black start up Google screen (the one with the lock at the bottom).
Entered recovery mode, I've wiped Dalvik, Cache and System, but no results, rebooting is always stuck on Google screen (I've also left it there for 15+ minutes, no changes)
I've tried to install a previous ROM (zip available on phone storage) but no result even in this case.
Any help or suggestion would be much appreciated, even a link pointing to similar case happened in the past.
Let me know if any further detail may be needed to better understand the situation
Thanks!
mh a wipe/factory reset should be working...
Try pushing a different rom with ADB to your device, then flash it.
Sent from my Nexus 4 with Tapatalk 4
This is usually happening when you don't flash something right. I'd go back, flash it all again with wiping everything and flashing it by the right order and stuff. If it doesn't work, as written above, flash other ROM through ADB or something similar.
Besides, you could always restore your nandroid backup, and if you don't have one, learn from your mistake
Good luck
Sent from my Nexus 4 using xda app-developers app
To be honest, I've already tried to revert back to previous CM and even to the factory image from Google, but it always hang on the google screen.
I've not yet Format/completely wiped the phone, and that's my last option.
Once I'm done with the manual backup I'm doing via adb shell, I will try again to flash a new ROM, and see what happen.
Definitely I'm learning from my mistakes
hello world!
i've been using my gt-i9300 since one year now. back then i've rooted it right away with an already rooted firmware or stock firmware.
can't remember anymore. the file was: I9300XXDLIH_I9300EPLDLJ1_I9300XXDLID_HOME.tar.md5
i hadn't had any problems. even had cwm and stuff on it.
a few days ago i've flashed this firmware onto my cellphone: I9300XXUGMK6_I9300DBTGMK2_I9300XXUGMK6_HOME.tar.md5
and after testing if all went ok i've figured out that some apps had trouble opening itself.
i've then flashed chainfire's CF-Auto-Root-m0-m0xx-gti9300.tar.md but still the problem remained.
firefox, dropbox, drweb light and a few others had problems running. so i've uninstalled firefox and drweb, reinstalled them
and the ran again.
then i thought "whynot copy the files from internal storage to the external" .. ive tried that and copied the stuff back into
the phone and the apps ran again.
so my question now is, what have i done wrong or why were there right problems or what is it that the apps
get fixed after copying them from and to the internal cellphone storage?
besides that, cf's superuser hasn't been flashed directly. i had to install it.
done the firmware/cf flash/install procedure twice and both times i had to install the stuff manually.
it's rooted now and the trick with copying the apps fixes the halting problem. but what is the real problem?
and another question i have "insane chip? YES" .. i thought samsung fixed this bug?
cheers!
'My Nexus 10 started to randomly reboot several times a day after the Kitkat update and because it is outside the warranty period I cannot get it replaced.'
It reboots no matter what is running and sometimes it reboots immediately after a power up but never enters a reboot loop.
I've tried a factory reset and running it in safe mode but that didn't stop it.
I've not been able to replicate the reboot fault until yesterday when I ran the BBC iplayer and downloaded a 1-hour Horozon video of about 650Mb and when I tried to play it I got a reboot and that happened consistantly.
I tried a complete power down and reboot then tried to play the downloaded video but it always rebooted.
I tried deleting and re-saving the video incase it was corrupt but it still rebooted.
I tried deleting the video and streaming it and I could watch it that way without any reboot.
I've tried downloading three 1-hour Horizon videos of about the same size and only one plays without rebooting.
A check of running apps shows just the keyboard and a couple of system apps but I still get the reboot when I try to play the saved video.
I thought about removing apps one at a time to see if that would solve it but I've basically got the same apps I had before the Kitkat update.
I wondered if I could undo the Kitkat update and flash the previous rom to see if that would solve it for Kitkat was not a big improvement.
I've never used a custom rom and not run anyting other than stock software.
I would be most grateful for any suggestions on how to fix this rebooting problem and whether going to an earlier version of Android is feasable and how would I do it.
PS. There is a BBC iplayer option to download videos using less resolution and when I choose that option the Horizon file size falls to 344Mb which is about half the size of the original and it solves the reboot problem when playing the saved video.
So it would seem that the BBC iplayer reboot problem is related to file size.
It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app
gc84245 said:
It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).
Gaugerer said:
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).
Click to expand...
Click to collapse
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796
gc84245 said:
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
Thanks for the guide link.
Unfortunately, my laptop is running Windows 8.1 and it is difficult to install the USB driver and Android Development Kit needed to flash previous Android versions, so I've given up until I can find the way to do it.
PS. I've found a way of installing the ADB and Fastboot drivers on my Windows 8.1 laptop and here is a link:
http://forum.xda-developers.com/showthread.php?t=2588979
So I'm back on track to solve my random reboots using an earlier version of Android.
I noticed the iPlayer hard crash thing too. I can play downloads, but as soon as I pause it and attempt to restart, or just slide the progress bar to move to a different part of the video, the tablet hangs then reboots. It's completely reproducible, and doesn't happen on any of my other devices.
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!
I've found a easy way to downgrade to 4.3 and would be grateful for any opinion on how safe it is and if anyone has tried it.
http://forum.cyanogenmod.com/topic/83985-nexus-factory-images-to-revert-to-stock/
AleT said:
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!
Click to expand...
Click to collapse
Arghh...this thing is a POS. I haven't used it in 2 months. Today I fired up chrome for some browsing. It hard locked within 5 minutes. I left it for an hour plus with the screen on and still locked up. Just frustrated. Worst Android device I've owned.
Sent from my XT1053 using Tapatalk
Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.
Koopa777 said:
Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.
Click to expand...
Click to collapse
I still get random re-boots in `safe mode` which is supposed to only allow apps installed with the system to run which leaves a bad 4.4.2 which could be checked by a re-flash of the factory image or faulty hardware.
I was planning to downgrade to 4.3 to see if that solved the re-boots but I might try a re-flash of 4.4.2 first to see if that works..
I'm not very confident about flashing and I've had the additional problem of working on windows 8.1 on my laptop.
I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk
rxnelson said:
I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
The memory leak was fixed but apparently, it's reappeared for me with the latest kitkat update. Quite frustrating, you'd think Google would be on top of these things. What's the point of fast updates if you're waiting months on end for a fix. If I don't powerdown my tablet when I'm finished using it I can guarantee a reboot during use. In the last 24hrs, it has rebooted on me twice while using Chrome. Quite irritating to be honest
It seems from previous posts that re-flashing 4.4.2 does not solve the reboots and I've not found a way to downgrade to 4.3 on Windows 8.1 to see if that works.
So I've tried another factory reset, but this time I've not allowed any non-Google apps to be installed other than the Photon browser which I need for flash Websites and the Re-boot logger app to record any reboots.
I'm using my Note 3 for the rest of my apps as that is still on 4.3 and doesn't have the reboot problem, but that might change after the KitKat upgrade.
I was getting at least 2 or 3 reboots a day so I should soon know if running 4.4.2 after a factory reset with just two 3rd party apps solves the problem and if so then that will suggest a rougue app. which I can reveal by re-installing the apps piecemeal.
I've just had another random reboot so I've done another factory reset but not signed in to Google so there have been no downloads and the only program I've run is Settings to increase the screen timeout to 30 - minutes.
If I still get random reboots then it is nothing to do with 3rd party apps or updates for I've not downloaded any.
That just leaves the hardware or the original 4.4.2 assuming the factory reset returns to that.
I didn't experience any reboots when not signed into google after a factory reset so I signed in and restored my tablet using Google backup.
I soon started to get reboots again, but I noticed that since the KitKat upgrade a website I use very often was sometimes automatically loading the Play store to try and get me to use their much inferier app. It doesn't happen on my Note 3 which is still on 4.3.
If I tried to close the Play store app to get back to the browser by swiping it away then it crashes and keeps trying to load over and over. If I hit the home button the Play store automatically re-appears still loading over and over, but after swiping it away several times it goes away or stops with an error message asking me to report the crash which I did and the browser is closed.
In order to fix this I disabled the Play store app so that it did not appear in my list of apps.and the website instead of loading the Play store app re-directed the browser to the Play store website which was better for I was still in the browser.
Since I stopped this particular website loading the Play store by removing it, I've just had one re-boot instead of several and my tablet is no longer overheating. I am a heavy user and have my tablet on many hours a day, so one re-boot is acceptable to me.
I've downloaded a Play store apk which I can install if needed but always remove it before using the website which tries to automatically load it.
It is a nuisance and I wish I'd stayed with 4.3, but I can live with the occaisional re-boot that might not be noticed if I only used my tablet lightly.
I'm annoyed that a website can automatically load the Playstore without me requesting it and that KitKat allows it.
I hope my experience helps others who are getting several re-boots a day.
PS
I did a factory reset then removed the Play store app before using the problem website so that it never loaded it in case that was needed.
Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.
Koopa777 said:
Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.
Click to expand...
Click to collapse
Now that I'm just getting one reboot a day and my tablet is running cooler I can live with that and I don't mind re-installing the Play store when needed for continuous updates can be a nuisance.
I finally managed to downgrade to 4.3 and I'm hoping that will solve all the problems I had with 4.4.2
But all seems well at the moment.
I'm not being booted from websites to the Play store, I can use the BBC iPlayer to download and run 1-hour videos and flash player works better.
Google has downloaded 4.4.2 (KitKat) but I'm not going to install it.
Guys,
I'm not even sure where to start with what I'm seeing, but maybe you can help me.
I have had Timur's ROM on my N7 2012 for a couple years. It's been crashing randomly, even though I have few things installed on it, and a good power supply. I took it out of my car and put it on an iPad 2 amp supply, and it still crashed a bunch so I knew I needed to wipe and reinstall. I also wanted to go from 4.2.2 to 5+, which I know takes away a lot of the good features I need (like power on/deep sleep).
I booted into TWRP and wiped my tablet, which appeared to softbrick it (I think I have the usage right from searching). I downloaded the Pure Nexus 6.0.1, CM13, and already had Autodroid ROMs to use. I tried to install Pure through ADB sideload, and got it installed. When I finished and tried to reboot, it said I had no OS. When I rebooted, I got the boot animation, and nothing else.
Long story short, I tried Autodroid and CM13, and using CM13 I got it back going. Unfortunately, every time I try to flash another ROM over it, it will no longer go past the boot screen. With CM13, it boots properly, but doesn't like the gapps pico I tried to install (error message when booted, keeps returning to the same pop up error).
I'm quite sure there's something I'm missing, but I don't know what it is.
Thanks!
Eric
Ok, before anyone goes nuclear on me, I think I better understand what happened. When I got ANYTHING to work, I stopped doing anything. As I understand, it wasn't functioning...it was just in a temporary mode of some sort.
After not being able to get it to work properly, I used this: http://forum.xda-developers.com/showthread.php?t=1781250 to try and restore the system. I followed all the directions, except for using the 5.1.1 version of the ROM, and used the corresponding file name for the zip file used.
After doing so, the bootloader won't go to TWRP, but goes to the pic as seen below. I did reboot the tablet, and after waiting quite a while, the tablet came on, but I don't understand what that picture means.
Thanks!
Eric
Ok...I realized that I lost root. I'm fixing it now. I had read before, but didn't understand what I saw.
Thanks,
Eric