Hello
I have a problem with my Mate. I will try and list the things i did to get to this problem and I hope the information helps solve it.
I wanted to install xposed (first thing I did wrong) so I rooted using King Root (ver 4.8.2) successfully
then unlocked the bootloader using Huawei website
Using Flashy, I flashed TWRP recovery to install xposed (regrets).
After creating back up on TWRP, I tried to flash xposed, didnt work.
I gave up and rebooted phone to android, and i saw i had lost Nav buttons and Notification bar.
Booted back into TWRP and tried to restore my backup. It kept failing at 33% (would post logs but I lost them), I then thought a factory reset would help and it did.
I got the navigation and notification bar, but I soon realised I cannot install apps. I couldn’t install from my SD (apk’s) or from the Play Store.
I can’t install anything on it now. I’ve learnt my lesson not to mess with the inner workings of my device but now I am stuck with EMUI (no Nova or other 3rd party launcher).
Is there any way I can get it back to installing apps as usual? I saw another thread with similar problem (can’t install apps) but I wasn’t sure if I should post there (its old and unattended thread). If I should post this in another thread please point me in the right direction and thank you in advance.
:crying:
I would clear cache and Dalvik cache in recovery then flash back to a stock kitkat recovery, put the correct stock complete kitkat ROM in the dload folder in SD card and do a force update from stock recovery. Once it runs properly again, update to the right ROM you want to run, in the correct order of updates, make sure bootloader is unlocked, root the correct way (not kingroot, use ADB) then seek guidance on what mods work with what ROM. Do not try to root without unlocked bootloader! That ruined it I think.
If you want Xposed, it only partially works in Kitkat, not at all in Lollipop. What do you need with Xposed? I'm running B331 Lollipop now, no Xposed and no real need for it. I do have unlocked bootloader, root and Viper4android and it runs great. I use Smart Launcher Pro but kept Huawei Home (launcher) and theming apps installed so the system is happy but it looks how I want and is good to use.
Thanks for your quick response RobboW, will try that method and let you know if I make any improvement to my situation.
So I have to get a stock KitKat recovery and stock KitKat ROM for that recovery. Do I force an update from TWRP or what? I'll read up on recovering stock Roms and let you know if I make any progress. Thank you for the response though.
Force update with a stock ROM needs to be done from stock recovery. TWRP stops the phone from updating the stock way. The bootloader can stay unlocked if it already is.
It worked exactly like you said. I'm back on Lollipop B324. I can install apps and got the motion control settings back.
Thank you so much RobboW!
You're welcome
OS faults are not so bad if you have access to recovery. It's the ones that make using recovery and ADB difficult that cause the big dramas.
Related
Hey, I' ve got my Oneplus One now with CM12 (20150415 nightly), and rooted months ago with zedomax tutorial (can't post link).
With the tutorial, I unlocked the bootloader, flashed SuperSu binaries, installed TWRP recovery and then flashed CM11.
I've some issues with the root. When I try apps requiring root permissions it says they're not enabled. I've also messed flashing CM12.1 yesterday, because I forgot the 5.1 gapps, and had to go back to CM12. Of course now there are a lot of problems with several apps and processes.
I have backups of everything and I don't mind losing data, and my question is: can I follow an xda tutorial to do all the process again? I mean, even my phone is not stock, can I reunlock the bootloader (to erase everything) and do everything well?
I have also another doubt: do I need to flash SuperSu binaries, or CM is prerooted?
Thank you and sorry for my inexperience (I try to progress )
sdert said:
Hey, I' ve got my Oneplus One now with CM12 (20150415 nightly), and rooted months ago with zedomax tutorial (can't post link).
With the tutorial, I unlocked the bootloader, flashed SuperSu binaries, installed TWRP recovery and then flashed CM11.
I've some issues with the root. When I try apps requiring root permissions it says they're not enabled. I've also messed flashing CM12.1 yesterday, because I forgot the 5.1 gapps, and had to go back to CM12. Of course now there are a lot of problems with several apps and processes.
I have backups of everything and I don't mind losing data, and my question is: can I follow an xda tutorial to do all the process again? I mean, even my phone is not stock, can I reunlock the bootloader (to erase everything) and do everything well?
I have also another doubt: do I need to flash SuperSu binaries, or CM is prerooted?
Thank you and sorry for my inexperience (I try to progress )
Click to expand...
Click to collapse
try to flash the stock images with ADB (there are lots of tutorials on the forum here), it will wipe everything and you can have a clean start, then if you want to update to 5.0.2/5.1.1 just download the firmware update, the rom and Gapps. Most of the rooms as for now have a built in root, but maybe it disabled so you have to enabled it through developer settings.
sdert said:
Hey, I' ve got my Oneplus One now with CM12 (20150415 nightly), and rooted months ago with zedomax tutorial (can't post link).
With the tutorial, I unlocked the bootloader, flashed SuperSu binaries, installed TWRP recovery and then flashed CM11.
I've some issues with the root. When I try apps requiring root permissions it says they're not enabled. I've also messed flashing CM12.1 yesterday, because I forgot the 5.1 gapps, and had to go back to CM12. Of course now there are a lot of problems with several apps and processes.
I have backups of everything and I don't mind losing data, and my question is: can I follow an xda tutorial to do all the process again? I mean, even my phone is not stock, can I reunlock the bootloader (to erase everything) and do everything well?
I have also another doubt: do I need to flash SuperSu binaries, or CM is prerooted?
Thank you and sorry for my inexperience (I try to progress )
Click to expand...
Click to collapse
Hi, please follow the below link...
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
I am caught in a bootloop after attempting to root using the following process.
Using Odin3 v3.10.6, I flashed the following:
n915t-cwm-recovery-6.0.5.1(1128).tar - THIS MAY HAVE BEEN AN ERROR. SHOULD I HAVE USED "openrecovery-twrp-2.8.1.1-trltetmo.img.tar"
I did a full backup to my phone's external SD card from cwm-recovery-6.0.5.1.
I then flashed both the files below without rebooting in between. I did not wipe any cache or data.
Emotion-TW-nightly-r23-RC1-SM-N915T
UPDATE-SuperSU-v2.46
The phone locked when I rebooted and would not move past the first black screen.
I pulled the battery and rebooted to recovery.
I did a restore of my backup that appeared to complete successfully.
I got a message asking to root the phone. I said yes, then rebooted.
Now stuck in a bootloop.
Hoping I can recover from this?
Root only with extra Kernel
When recovery asks to install root at the end, hit no. Thats your issue. You already installed supersu, so you've already got root. Personally I prefer stock kernel, with the latest beta supersu, you can still get root. With Universal init.d app, you can still get init.d support. With a custom build of xposed for Samsung lollipop, you can still get xposed. There's even a special version of viper audio. So yeah all you lose is the overclock ability.
Thank you. I ended up reflashing the firmware and got it working again. I'm still in the same situation, without root. My goal is to install a custom rom but I'm concerned about trying The Root process again. I read that a security patch was done in November for lollipop. Could that have impacted my ability to root and cause me to get into a boot loop? Wondering if there is a more current root method than the one I used.
rootnooby said:
Thank you. I ended up reflashing the firmware and got it working again. I'm still in the same situation, without root. My goal is to install a custom rom but I'm concerned about trying The Root process again. I read that a security patch was done in November for lollipop. Could that have impacted my ability to root and cause me to get into a boot loop? Wondering if there is a more current root method than the one I used.
Click to expand...
Click to collapse
There have been reports that the emotion r23 kernel is finicky, some work soem dont. Try another kernel or older version. That could be toir problem.
Sent from my SM-N915T using Tapatalk
Hi.
Just recently I rooted my Xperia z3 (D6603) and upgraded the KitKat 4.4.4 into 6.0.1 MM through AROMA (found a link on this website).
After trying to install Xposed Framework, I had to flash it through TWRP recovery, but it said that I had the wrong version (arm)
I then downloaded a different version, however now my TWRP won't launch manually or automatically ( through a reboot app).
It will just jump straight into android instead of coming up with the team win logo etc.
I am confused as to why this is happening, do I need to flash the .img of it into my phone again or is there another sure way of fixing my issue.
Any help would be very appreciated . At the moment I cannot install Xposed framework because I have to flash it via recovery and I can't get into it.
Thank you
P.S Everything else works fine, no bootloop or brick
P.S2 Rebooting to recovery through TWRP Manager didn't work either (straight into Android)
If you cant get into recovery by pressing volume down on reboot. ie when they phone turns on there will be a buzz and a green light, press vol down and it should turn purple and then go to TWRP.
If you didn't unlock the bootloader this should help you fix it.
If this doesn't happen ensure you have SuperSU and that it works ie. you're actually still rooted...
If still rooted:
Find RecRoot v4 by Wolfbreak here: http://forum.xda-developers.com/z3/general/wip-sony-android-6-0-mm-t3337357 and use it from your PC to reinstall recovery.
If this fails it means root is broken.
If root is gone you will need to downgrade again and root and update again. Make sure this time you use a pre-rooted zip or at least flash recroot (works in recovery also) straight after you flash the ROM to keep root. If you use a custom ROM they should always include root (just read the XDA page of that ROM and make sure).
If your bootloader is locked (which I'm assuming it is if you downgraded to root and upgraded after) don't mess around flashing any .img files you will likely mess things up. Recoveries on LB have to be installed carefully.
If anyone says they haven't had an issue like this with root they're probably lying. It's all part of the fun ;P
To flash xposed make sure you download the one for MM which is SDK 23. And for the architecture of the Z3 processor you need ARM. This should work fine for you.
(please correct me if I missed something or got something wrong)
Dobsgw said:
If you cant get into recovery by pressing volume down on reboot. ie when they phone turns on there will be a buzz and a green light, press vol down and it should turn purple and then go to TWRP.
If you didn't unlock the bootloader this should help you fix it.
If this doesn't happen ensure you have SuperSU and that it works ie. you're actually still rooted...
If still rooted:
Find RecRoot v4 by Wolfbreak here: http://forum.xda-developers.com/z3/general/wip-sony-android-6-0-mm-t3337357 and use it from your PC to reinstall recovery.
If this fails it means root is broken.
If root is gone you will need to downgrade again and root and update again. Make sure this time you use a pre-rooted zip or at least flash recroot (works in recovery also) straight after you flash the ROM to keep root. If you use a custom ROM they should always include root (just read the XDA page of that ROM and make sure).
If your bootloader is locked (which I'm assuming it is if you downgraded to root and upgraded after) don't mess around flashing any .img files you will likely mess things up. Recoveries on LB have to be installed carefully.
If anyone says they haven't had an issue like this with root they're probably lying. It's all part of the fun ;P
To flash xposed make sure you download the one for MM which is SDK 23. And for the architecture of the Z3 processor you need ARM. This should work fine for you.
(please correct me if I missed something or got something wrong)
Click to expand...
Click to collapse
Problem is that when I downloaded the SDK23 arm, it said wrong format : ARM in red and gave me an error. After that I couldn't go back to twrp no matter what I did.
- I am now back to 6.0.1 MM rooted, going to try installing Xposed again, hopefully this time nothing will go wrong
I will try to keep it short and concise;
Had android 5.0.1 (if I recall correctly), unlocked it, installed twrp and rooted it.
Then used the local update option to get to marshmallo. Then tried to root again using supersu and it wouldn't boot. Tried restoring nandroid backup of 5.0.1 backup but it wont boot either.
I have searched for many hours and tried many different roms etc. I can only get to the boot animation and it just stays there.
I can get into TWRP and bootloader with no issue but have no idea if I can use the dload option if I can not boot into the OS.
Can someone please help me get this back either to the stock rom or a custom marshmallo rom installed?
I will be honest that I don't fully understand what it means when there is a prerequisite of "You must already be on B201 or higher to flash this" such as with the Simply International I have tried to flash. And am not sure what the EMUI version is or how it affects what can be installed.
Thanks for any info.
Hello
1) First of all, go into TWRP recovery, and do a full wipe. Then reboot and wait.
2) If unsucessfull, try out the downgrade file for 702L : http://download-c.huawei.com/download/downloadCenter?downloadId=81363&version=323452&siteCode=tw . It does install with official dload method
3) If it's not enough, you'll have to use ADB to fix your device I guess:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378?
its use on X2:
http://forum.xda-developers.com/showthread.php?p=62829551#post62829551
(and following post)
pick up the file from your last installed (or nandroid restored) ROM to use with huawei update extractor.
==
but try out 1 &2, and come back here before using ADB, to have more precise instructions
Which is the best ROM out there for Xperia L and can someone provide me with the exact A-Z guide on how to flash it?
I have a spare 4.1.2 Xperia L lying around and it hasn't been used for months now. About two years back, I had tried to unlock the bootloader and messed up the phone. Had to take it to a local store to get it fixed and apparently, the bootloader was unlocked (does that mean I succeeded?). I later managed to root the phone with MotoChopper and that was the end of it. Uninstalled all the crappy bloatware and the phone was fast af and I never thought about the need for flashing a custom ROM. Well, I couldn't because I was scared to fail.
Then, in July 2016 or so, Pokemon GO was launched worldwide and I couldn't play it 'cause minimum requirement was KitKat (fml). I had to finally get a new phone to be able to play it. Always wanted to upgrade the Xperia L because I love the phone. It was my first ever Android
mama-bobo said:
Which is the best ROM out there for Xperia L and can someone provide me with the exact A-Z guide on how to flash it?
I have a spare 4.1.2 Xperia L lying around and it hasn't been used for months now. About two years back, I had tried to unlock the bootloader and messed up the phone. Had to take it to a local store to get it fixed and apparently, the bootloader was unlocked (does that mean I succeeded?). I later managed to root the phone with MotoChopper and that was the end of it. Uninstalled all the crappy bloatware and the phone was fast af and I never thought about the need for flashing a custom ROM. Well, I couldn't because I was scared to fail.
Then, in July 2016 or so, Pokemon GO was launched worldwide and I couldn't play it 'cause minimum requirement was KitKat (fml). I had to finally get a new phone to be able to play it. Always wanted to upgrade the Xperia L because I love the phone. It was my first ever Android
Click to expand...
Click to collapse
Update: It seems that the Xperia L I had was already unlocked and rooted and I installed the Official TWRP App now to get into the recovery mode but I still can't find the "Install from SD Card" option. These are the steps that I did:
1. Installed Official TWRP
2. Downloaded image for my device
3. Flashed image (it said successful) and restarted into recovery
These are what I see in the recovery mode:
1. Reboot system now
2. Update adb (something)
3. Wipe system data
4. Wipe cache
5. Fastboot mode
That's pretty much it. Help!
mama-bobo said:
Update: It seems that the Xperia L I had was already unlocked and rooted and I installed the Official TWRP App now to get into the recovery mode but I still can't find the "Install from SD Card" option. These are the steps that I did:
1. Installed Official TWRP
2. Downloaded image for my device
3. Flashed image (it said successful) and restarted into recovery
These are what I see in the recovery mode:
1. Reboot system now
2. Update adb (something)
3. Wipe system data
4. Wipe cache
5. Fastboot mode
That's pretty much it. Help!
Click to expand...
Click to collapse
What you're seeing sounds like the stock Android recovery. The TWRP recoveries from the app and from their website can't work on stock roms.
Assuming you have an access to a computer, download https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320 and pick CWM. Transfer an older ROM that has root built-in (any LP/MM ROM would work) onto your internal storage, enter your recovery, and wipe /system, /data and whatever directories you're told to wipe in the descriptions. Flash the ROM, get the TWRP app if that's what you wanna use, and install the recovery. Reboot, and TWRP should be working this time. Wipe and flash the ROM of your choice.
Regarding the "stable ROM" question, I currently run LineageOS 14.1 and that's pretty stable - there's a little bug with the touchscreen that appeared about two or three weeks ago, but if you flash the "Touchscreen fix" .zip linked in this thread it will work just fine.
I know that my method is a bit roundabout but anyone can do it, even with no experience.
HI
I have same Quastion About #Most Stable Rom For Xperia L ?