Hi,
I just installed the ROM on my tf700 and firstly, a big shoutout to you guys who made this work! breathed new life into a tablet i thought was past its day.
what i did was (in case anyone wants to follow):
1. root via kingo and unlock via asus app v7.( factory reset first with no user ID in order for unlock app v.7 to work. v8 didnt work for me)
2. pushed TWRP img via its google app.
3. boot to bootloader and launch recovery TWRP
4. installed the a. ROM, b. performance tweak and c. GAPPS in one go via TWRP.
5. hard reset as the TWRP reset didnt work for me.
6. zombipop booted fine.
my issues faced is that i understand the first time boot will take some time, but what im facing now is each time i boot
1. it's taking a long time. the startup "waves" screen takes a good 4-5 minutes
2. after the bootup, the first 10 minutes of use is very slow and laggy.
only after that does everything work like a charm. seems strange that it's the same everytime i boot up.
Is this behavior normal? can i fix it?
tried searching the forums but can't seem to find symptoms described similar to above.
thnx in advance.
Related
Hi, everyone, I have a Nexus S and I am new to roms and stuff and by far I was using the latest Cyanogen mod, because the installation was easy. I decided to try this custom rom http://forum.xda-developers.com/showthread.php?t=2410844. And after a lot of reading, I figured that i have to install the latest Clockwork mod, so I did, then transferred the rom .zip file to my storage, rebooted in recovery and installed the zip. Then I rebooted again and all that is happening now is - an android text with highlights moving over it is standing in the center of my screen, but nothing loads... I waited like 30-40 minutes but it just stays there... Can somebody tell me if I was wrong with the instructions somewhere or this can be a problem with my device? Thanks a lot and sorry for posting a new thread about it, since I'm new, I'm not allowed to ask in the Developers Section.
I didn't Wipe/Factory reset. Could this be the problem?
It seems you got stuck in the boot loop itself.!! From next time on when you are about to install a new rom, make sure you do a full factory/data wipe.!!
Now that you are stuck in boot loop, just remove batter, insert it, hold simultaneously your volume up+power buttons. From the menu choose recovery. Then
1.data wipe/factory reset.
2. Wipe cache.
3. mounts and storage --> format system.!!
Now you are good to go. Make a clean install of your new ROM. I guess your device by now should work normally.!!
Sent from my Nexus S
Hit thanks if I helped you.!!
Yes, I already did it, right after I asked, with the factory/reset function (I thought this is the problem, so I did it), everithing is ok now, but thanks for answering!
It's ok for the admins to delete that thread, thanks!
I also have a problem with same ROM.
Every once and a while after making a call or doing anything with Dialer he freezes and after that system just reboots. I've installed last version of CWM, updated SuperSu, installed Pa full version of GAPPS.
Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden
Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app
I know I should, but I didnt. Is it still fixable ?
*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.
Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app
Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden
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
Hi all,
well, to be honnest I already posted my story in the help thread but no answer came so I try with a new thread
We'll see if I'm luckier this way !
a few weeks ago I broke my screen and decided to change it myself.
Everything went fine (even restarted successfully my phone before applying the tape to fix the screen) until I finally tried to restart my phone after the repair is done.
Since then I'm not able to turn on my phone
Holding the power button starts fastboot mode, UP + power doesn't do anything and DOWN + power enters recovery. Weird !
Another weird thing: it only works if I'm not plugged. When I'm plugged nothing ever happens.
I suspected I could have damaged buttons or cables. I have looked carefully but nothing appears to be broken.
Here is what I already did without any result:
- I had access to the original recovery so wiped the cache
- I tried to recover the phone but that did not work so
- I installed twrk using adb (like here)
- and then installed the rom as explained here (I used the last release here, so it should be cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-bacon.zip). It seemed to work but finally no, same situtation
- I tried this but so far not able to get the qualcomm port listed once the phone is on. It may be related to the fact that I have to unplug to boot it but I always got a Android bootloader interface listed.
Any idea someone ?
Thank you very much for your help !
Did you try to "fastboot reboot" while in fastboot mode?
Try flashing a CM14 rom. Mine came with CM12 so I tried flashing back to CM11 and I did flash it successfully through Fastboot but alas it won't boot. The boot logo loads but then I'm introduced to a black screen.. So I flashed back to a (at that time the latest stable) CM12.1 but same result. And I got worried. Then I decided to flash a CM13 rom which was a beta build (at that time newly released Android 6) and it booted into it alright! So I suggest flashing a CM14 and let me know how it does.
The problem seems be much deeper than just a broken screen. It may sometime affect the chipset of the cellphone.
For that we can't do anything.
For now you can try the following things :
1 . Flash the latest Cyanogen Firmware from the same place you have downloaded the snapshot cm13.
2. Flash recovery (TWRP) using adb.
3. Wipe
-System
-Data
-Cache and Dalvik Cache
4. Flash the latest Cyanogen Rom .
5. Boot into recovery.
6. Flash some gapps as per the Android version.( Open Gapps I recommend)
7. Boot back to recovery .
8. Boot into System.
This is the max you can do for now.
You can also check device forums for recovering from a bricked device post.
Go through the post and check if any symptoms matches yours. You'll find the answer right away.
And the last option you can do is going to service center, they will charge you mostly (even if in warranty as you have yourself tampered hardware of the phone.)
Hope it will help. Thanks
Hey folks,
I just have a very weird issue with my Z3 Stock firmware : it was in my pocket and suddenly, started to reboot over and over for no apparent reason. So it was heating and the battery was quickly flat. Since then, I can't use it anymore : it startup correctly and once you can finally use the screen to unlock it, it's already "crashed" and several second later, it reboot (over and over ...).
Tried to recovery with the Sony Companion which worked and I could see change after that flash : there is now a "hello" as if it was fresh new, but no time to select anything and again, crashed and reboot.
I have no idea of why, anyone ?
I think the hardware is now defect, but as it start correctly (and flash to stock worked), I really don't understand.
I've seen a post where someone say that it's (could) be because of the gyroscope ... really ??
Help appreciated,
Thx
Hey, more information.
So I was able to flash stock firmware, android 5 or 6, both reboot loop. Each time, it seems to works (touch screen OK) then there is a text displayed and after that, freeze and reboot.
The Killin message, on android 5 or 6 stock rom :
FACTORY STARTUP SERVICE - Please wait for on-screen POWER OFF button
I've never seen that button on screen, reboot before. Any idea? Possibly due to hardware failure? Looks to works, but is not working, sad.
Thx