Database Develop

[Q] Unofficial CM11 Problem

Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East

EastPatel said:
Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East
Click to expand...
Click to collapse
Are you on the correct bootloader 10.26.1.18 as is required?

EastPatel said:
Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East
Click to expand...
Click to collapse
I've not heard of this ocurring (my own tab has been running for a while now; no issues of this sort).
Are you on the latest ROM build (01/29)? Have you flashed the appropriate gapps?
Are you on the latest boot loader?
Any apps installed which could cause issue?
If it happens when plugged in to USB, is isb OK on your PC/Mac?
Have you used titanium backup to restore system level stuff from a non compatible build?
Do this,
Go back to stock (latest release from asus) and observe for an hour or two. Any issues? If not then flash ROM + gapps and wipe. Don't sign in and don't restore apps. Any issues? Then sign in and restore. Any issues? And so on and so forth until.you find the break point.

Thank you for your prompt responses as always and apologies for not replying sooner.
SDbags I am installing CM11 over your own excellent 4.3+ stock rooted v2 ROM which I believe involved updating my boot loader. I am unsure how to confirm the version I am on but booting into recovery shows the following
Android Macallan-user BL released by ww_epad-10.26.1.7-20131108.
Pershoot once the new CM11 was first flashed the TF701 would freeze during the setup steps well before any 3rd party apps could be installed. After a number of attempts I manage to get through set up and the system becomes a lttle more stable but then freezes after a few more minutes. I can conform that the correct gapps has been flashed using the link on the associated thread and no additional apps except the ones included on the ROM have been flashed. The system freezes without being plugged into the PC via USB and as mentioned before I am coming from sdbags stock rooted 4.3 ROM and have not used titanium back up at all.
A couple of additional point
1) I have tried to reflash sdbags ROM again but it now gets stuck on a bootloop.
2) I noticed that my install of CM11 is not able to access either an SD card placed in the dock or MicroSD placed in the tab despite the system recognising when they are inserted or removed on the task bar.
3) Because the system freezes so quickly it tabvery difficult to transfer a new ROM downloaded to my PC over to the TF701 because the moment it freezes the PC can't communicate with the tab.
Apologies if this reply is a little onerous - any help would be greatly appreciated and thank you both again for your prompt response to my.request for help.
Kind regards,
East

Hold down Volume Down and Power and read the bootloader version from the top left.

EastPatel said:
Thank you for your prompt responses as always and apologies for not replying sooner.
SDbags I am installing CM11 over your own excellent 4.3+ stock rooted v2 ROM which I believe involved updating my boot loader. I am unsure how to confirm the version I am on but booting into recovery shows the following
Android Macallan-user BL released by ww_epad-10.26.1.7-20131108.
Click to expand...
Click to collapse
That's the wrong BL to be on. I don't believe sdbags' ROM updates BL. You must do it via Asus's update.
Go back to stock recovery and follow asus's procedure to update yourself to their latest 10.26.1.18 (4.3) build.

Dear SD Bags & Pershoot,
Apologies for not responding to your feedback sooner - Its been a busy week at work.
I will follow your advise and update the bootloader via the ASUS website and try to reinstall the rom again over the weekend or early next week and I will update this thread with the results. Once again apologies for not following the instructions more carefully.
Many thanks & kind regards,
East

Hi felIas.
I have updated the bootloader as I should have done initially which appears to have sent me back to stock unrooted 4.3. Please could you confirm that all I need to do now is install the recovery image and then flash CM11 and GApps? Does the rom file work the same way as SDbags rom where it also roots the phone as part of the installation or do I need to somehow root first?
Having said all this I am considering leaving the system as stock until a work around for sky go on rooted 4.4.2 devices is found!
Many thanks again for your guidance and patience.
East

EastPatel said:
Hi felIas.
I have updated the bootloader as I should have done initially which appears to have sent me back to stock unrooted 4.3. Please could you confirm that all I need to do now is install the recovery image and then flash CM11 and GApps? Does the rom file work the same way as SDbags rom where it also roots the phone as part of the installation or do I need to somehow root first?
Having said all this I am considering leaving the system as stock until a work around for sky go on rooted 4.4.2 devices is found!
Many thanks again for your guidance and patience.
East
Click to expand...
Click to collapse
I have a work around for Sky Go on rooted devices You didn't ask.
PM Please.

Hey there I was wondering if anyone else is experiencing my problem. I updated to CM11 on my TF701 and while the dock and keyboard works some of the keys are dead i.e. Settings button, toggle wifi, toggle bluetooth, screenshot, disable trackpad, and auto brightness. Is there any way to fix this? I have tried editing the qwerty files and installing the asus keyboard apk, but neither worked. The APK did not install and editing the qwerty.kl file quite literally did nothing. Also curious if there is a way to get an external mouse to behave the way it did on JB left click is a standard touch and right click is back?

Jrockstar867 said:
Hey there I was wondering if anyone else is experiencing my problem. I updated to CM11 on my TF701 and while the dock and keyboard works some of the keys are dead i.e. Settings button, toggle wifi, toggle bluetooth, screenshot, disable trackpad, and auto brightness. Is there any way to fix this? I have tried editing the qwerty files and installing the asus keyboard apk, but neither worked. The APK did not install and editing the qwerty.kl file quite literally did nothing. Also curious if there is a way to get an external mouse to behave the way it did on JB left click is a standard touch and right click is back?
Click to expand...
Click to collapse
Kernel needs recompiling with fixes in it - not a huge job but something I have on my todo list - won't be for a while though.

Is there a thread I can subscribe to to get the latest news??
Sent from my Transformer TF701

[Q] Unlock Bootloader B609 + recovery

Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated

JellyFox said:
Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated
Click to expand...
Click to collapse
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!

arthios said:
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!
Click to expand...
Click to collapse
RootGenius was the first thing i tried. It went up to 66% then i got an error but that was a fully Chinese version.
I just tried it again with the one i found by using Google and it goes up to 72%, then tells me that the root has failed.
Which version did you use?

This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers

ibeqa said:
This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers
Click to expand...
Click to collapse
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.

JellyFox said:
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.

arthios said:
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.
Click to expand...
Click to collapse
I disabled my firewall and antivirus and gave RootGenius another try. Normally it goes up to 71% and gives me the error. Now it went to 71%, rebooted and then it gave me the error. The weird part is that right before i get the error, it says the installation is complete.
Moved on to Vroot (which is called Iroot now apparently) . It took a while longer but it wasn't able to do it either.

JellyFox said:
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.

update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208

Z!L0G80 said:
update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208
Click to expand...
Click to collapse
I still didn't get the OTA for B615 yet but thank you for the recovery.
ibeqa said:
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.
Click to expand...
Click to collapse
You were right! (not that i every doubted you). I found the problem i had: For some reason, i couldn't boot in bootloader trough my phone BUT i was able to do it with 'adb reboot bootloader'. After making some idiotic mistakes and having to re-flash the stock ROM, I finally was able to install My-RoM v3.3, its rooted, i have Xposed so i am happy
So thank everyone for the help!

[Q] Phone rooted but stuck on bootloop

Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.

cowboyv said:
Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
Click to expand...
Click to collapse
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.

Revontheus said:
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Click to expand...
Click to collapse
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?

cowboyv said:
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
Click to expand...
Click to collapse
You can always download GAPPS manually, and flash it via Recovery if you think the Google Play Services that comes with your FW is bugged

XT1097/1095 Hybrid CANT FLASH STOCK ROM

Hi, first off I want to introduce myself since I have been lurking in the forums for some time now but never posted anything. (I am not a developer).
My name is Nicolas, and currently I own a Moto X 2014. (XT1097)
I bought it recently, with lollipop out of the box, and updated via OTA to MM, since I wanted to check what was available to flash I unlocked the bootloader and flashed TWRP to then get root.
All up to this point it was all normal. I proceed to flash CyanPop 4.8 via TWRP, again all normal.
The problem begun when i wanted to flash a MM Stock ROM back, flashed via TWRP and as soon I hit reboot it gets stuck in the M logo with the white backgroud and bootloops there.
I reflashed Stock ROM XT1097, still bootloops, flashed Stock ROM Lite XT1097, still bootloops, flashed Stock rom XT1095, bootloops.
I ended up returning to CyanPop 4.8, (btw, I say its a hybrid in the title because as soon I installed CyanPop, the setup screen told me it was a XT1095)
and cant get out.
I know its kind of messy, but if anyone could bring light to what is going on, I would be extremely grateful, or if anyone knows what to search for to point me in the right direction, also i would be extremely grateful.
Anyway, thanks for all the work you guys do, and for this awesome forum :good::good::good::fingers-crossed:

"set_metadata_recursive: some changes failed"

Okay.
So I have a Note 5 N920G. I'm 99% sure this is what the phone I have is, I bought this phone from Amazon India, pretty sure when I looked it up way back when, this was the one.
First ROM I ever installed was a Dr. Ketan Rom , Lollipop V8. I don't ever remember installing a BL/Modem for the same way back then.
Later I moved on to a Sick as Hell V3 Rom and I managed to get that installed just fine without getting a BL/Modem for the same as well.
**TODAY**
I have now tried to install the latest version of Dr Ketan's ROM N10 for my Note 5. It mentioned to install/upgrade the BL/Modem so I chose the one that is required for me phone, viz. the N920G BL/Modem.
Proceed to install. Rom installs just fine.
Proceed to reset/reboot. Get NOTHING. Stuck on an infinite loading screen.
Reboot phone, still nothing.
Get frustrated try to move to another ROM for the same phone in the same sub forum.
This one also has a Kernel and a CSC something that needs to be installed in order to try and boot this ROM. Proceed with everything and in order, no luck still....
NOW, even when I try to install the other ROMs, including Dr Ketan Roms or my previous Sick as Hell Rom that I was using earlier I am facing the error labelled :-
"set_metadata_recursive: some changes failed"
I just upgraded from TWRP 3.0.0.2 to the latest 3.1.1.X version that's out right now between these two installs (previous installation worked out just fine from what I can remember.)
I ALSO installed a new kernel since I was trying to install another rom when this one failed, and that rom required a kernel to be installed :-
https://forum.xda-developers.com/note5/development/7-0-khongloi-nougat-rom-aod-edge-t3580620
Now since flashing this kernel (I assume that is what is giving me all these issues) NO ROM is installing without giving me the error above of set metadata.
A quick google search says that I should update my recovery to the latest... But it IS! I upgraded to the current latest 3.1.1.X that I am supposed to have, that I found from their website.
I am so beyond frustrated at this point in time. Can someone please help me figure this out?
Honestly I am so ****ing done right now, I would Paypal you my appreciation if you can get me to install a new ROM after getting out of this mess.