About ten days ago I bought my first Kenzo, for my wife, attracted by the hardware specs and the existence of plenty custom ROMs - I'm no fan of vendor-customized ROM. The phone was delivered with unlocked bootloader, so hey, I'm lucky . I did boot from an official TWRP, made a full backup, then I flashed Cofface TWRP, tried Mokee, then Resurrection Remix. Because of the battery bug in RR I came back to Mokee. The bootloader got locked, but I re-unlocked it officially - fortunately I got in the meantime the permissions from Xiaomi. This phone is now the daily driver for my wife.
But playing with it made me wanting also one - I realized that I'm getting old and the big screen was confy. So I ordered also one, but this time the "Prime", which arrived yesterday. I booted it only to an Alka TWRP image to take a complete backup (and I noticed that the official TWRP made backup on the first device from 10 partitions, and Alka backed up 42 partitions from the second. Why?). This is my phone, my toy, and I want to play with it. I intend to test some ROMs, be it Cyanogen-based or not, and I'm not sure about the right way.
1. I don't want to end with a locked bootloader again. Btw, isn't there a way to back up the unlocked bootloader and restore it at a later time?
2. I intend to use Alka-TWRP. Is it suitable for my purpose?
3. I intent, at some time, to test also the official CM13, but not until it grows out of its diapers. Anything to know for switching to non-CM-based ROMs?
Any other thoughts?
(Btw, I do not intent to test any Lollipop ROMS, only Marshmallows)
Anyone, please?
Related
Hello there.
My Prime recently went out of warranty and I decided to root and install a custom rom.
I was and still am a newbie when it comes to flashing roms but i stayed true to the guides and followed every step.
I managed to back it with nvflash so everything is safe from that point of view.
After the androidroot recovery, i switched to twrp 2.6.0(a mistake in my opinion now that i have learned certain thing) and followed the steps to installing the androwook rom 2.31.
I flashed the hairybean bootloader and recovery updater - nothing happened to the twrp version as it should have and i noticed nothing happened to bootloader version (it still was 10.4.2.15). I continued with the guide and managed a successful install of the rom with husbunduah kernel.
That's when the problems began with the constant reboots(at about 1min-1,5 min). I reinstalled the rom with other kernels and it only became worse.
I thought it was because of the bootloader - but after all the wipes and reflashing of the updater - it still wouldn't change.
I downgraded the twrp to 2.3.1 and tried it again, thinking i would see the upgrade on the version of twrp and it would work with the bootloader.
All the images were checked with md5checker and i did all the wipes in the order it was written and when i should've done them.
Please lend me a little hand here as i am unsure if i'm correct in my assumptions and don't know what to do next.
to summarize: the question is - how do i update the bootloader and why didn't it upgrade?
cherokee990 said:
Hello there.
My Prime recently went out of warranty and I decided to root and install a custom rom.
I was and still am a newbie when it comes to flashing roms but i stayed true to the guides and followed every step.
I managed to back it with nvflash so everything is safe from that point of view.
After the androidroot recovery, i switched to twrp 2.6.0(a mistake in my opinion now that i have learned certain thing) and followed the steps to installing the androwook rom 2.31.
I flashed the hairybean bootloader and recovery updater - nothing happened to the twrp version as it should have and i noticed nothing happened to bootloader version (it still was 10.4.2.15). I continued with the guide and managed a successful install of the rom with husbunduah kernel.
That's when the problems began with the constant reboots(at about 1min-1,5 min). I reinstalled the rom with other kernels and it only became worse.
I thought it was because of the bootloader - but after all the wipes and reflashing of the updater - it still wouldn't change.
I downgraded the twrp to 2.3.1 and tried it again, thinking i would see the upgrade on the version of twrp and it would work with the bootloader.
All the images were checked with md5checker and i did all the wipes in the order it was written and when i should've done them.
Please lend me a little hand here as i am unsure if i'm correct in my assumptions and don't know what to do next.
to summarize: the question is - how do i update the bootloader and why didn't it upgrade?
Click to expand...
Click to collapse
Cherokee.. I am pretty busy at the moment working on Android TV boxes but I can see that you have nflash backups so everything should be fine.
I will pm you my Google talk address and add me on there with a message saying who you are, this is a bit too complicated to go through on the forums.
Can't promise you I can help you straight away but I will get around to it in the next day or two.. I'm UK time by the way.
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click "format data" under the "wipe" section this will wipe EVERYTHING so make sure you have the latest twrp then on your computer save a rom. Wipe the phone via twrp and then plug the phone it and wait for either Adb sideload or mtp. Personally I feel that mtp is the best just because you can move anything to your phone. Then just move the rom you want to the root of the sdcard (Every folder will be gone). Then flash it and hope that fixes it but if it dosent you may need to use the lg flash tool (windows) and flash the zv4 files. This will make you back on zv4 meaning restump root reflash twrp. The whole nine yards, just try the twrp thing first and if that dosen't work then do the flash tool. I am not responsible if you listen to me and your device breaks
bucketachicken said:
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click to expand...
Click to collapse
Have you tried this?
http://forum.xda-developers.com/lg-...trying-ota-t2907508/post56061720#post56061720
Thanks, I did get it working. I have no idea how, but my data was all still there, despite wiping several times....but the recovery fix is what worked. I also got that lg flash tool setup so hopefully that will be helpful if I run into future problems. I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again!
I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again![/QUOTE]
Here is a cm12 rom that is almost perfic: http://forum.xda-developers.com/sprint-lg-g3/orig-development/cyanogenmod-12-beta-ls990-t2958197
It's the one I use everyday and I have seen almost no bugs
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
vagfyt said:
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
Click to expand...
Click to collapse
There's an issue with SuperSU when it tries to install in systemless mode.
Flashing it this way seems to do the trick, and has been confirmed by multiple users on this board: http://androiding.how/root-moto-g-2014-marshmallow/
If you're using CM13, there is no need to flash SuperSU. CM13 has its own root pre-installed, you can turn it on in Developer Options.
I have a old HTC which I would like to get back to its somewhat original form.
Problem: Before, a long time ago I have wanted to root my phone however at some point I had TWRP on my phone which some people may have had problems with before. I had a friend in the family to try and fix it as it never got to its main lock screen but the HTC screen when turned on. Other than that, he had removed the OS on the HTC and would like to know how can I reinstall the OS to the HTC and how can I remove the TWRP?
I would really like to use this phone again and the software status is "Modified" if that helps to know.
Hopefully someone can help me with my problem and can also help me make it back to "Official" software status.
TechGIRLGAMER said:
Problem: Before, a long time ago I have wanted to root my phone however at some point I had TWRP on my phone which some people may have had problems with before.
Click to expand...
Click to collapse
Not sure what you are getting at here. TWRP works great, and is the most common, and recommended custom recovery for flashing root, custom ROMs, etc.
Most problems with TWRP and root (at least with this device) are due to user error. Most frequent mistake is using wrong (old) version TWRP and/or old version SuperSU.
TechGIRLGAMER said:
I had a friend in the family to try and fix it as it never got to its main lock screen but the HTC screen when turned on. Other than that, he had removed the OS on the HTC and would like to know how can I reinstall the OS to the HTC and how can I remove the TWRP?
Click to expand...
Click to collapse
Wiping the OS was a mistake. Flashing the proper version TWRP and proper version SuperSU probably would have fixed the problem (and give you a phone with root, like you wanted!). It doesn't really sound like your friend knew what they were doing.
Another mistake, was that you should have made a backup in TWRP of the stock ROM, before trying to root. If you had, you could have just restored that backup to get the phone working. Moral of the story, don't made mods to the phone (like root) or definitely don't wipe the OS, if you have no idea how to restore the OS! You should know how to return to stock, before doing any of these things.
You can return to stock by locking the bootloader with command: fastboot oem lock
Then run the appropriate version RUU (last version was Marshmallow 6.20.502.5) which you can find in my Index thread under "RUUs": https://forum.xda-developers.com/showthread.php?t=2751432
Hi guys hopefully someone can give some guidance on my issue.
I loaded a rom (pixel experience (android 10)) apart from stock for first time since I bought v30 about a year ago. Found it to be somewhat unstable, so went back to stock rom (android 9). Phone now boots to LG logo with startup tune, and just sits there on that screen for at least 1 minute longer than it did previously. Did a a complete wipe between flashes, went back to pixel experience to see if it went back to normal "boot speed", Phone bootup speeds went back to normal on that. Now back on stock again, and it's same thing with long boot time. Phone boots up fine eventually but it is quite painful to deal with now and regretting trying something different with zero payoff.
Any ideas?
Many have found flashing back to Nougat KDZ, then flashing to Pie KDZ (your bootloader will remain unlocked during both flashes), then re-installing TWRP, and re-rooting erases some of the changes you describe. See this post for reinstalling all that stuff, after you flash Nougat, then Pie KDZ.
INSTALL or REINSTALL TWRP on PIE stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285
Can't guarantee it, but going back to Nougat temporarily flushes a lot of stuff out of the system.
Which variant do you have?
GetRekt_ said:
Hi guys hopefully someone can give some guidance on my issue.
I loaded a rom (pixel experience (android 10)) apart from stock for first time since I bought v30 about a year ago. Found it to be somewhat unstable, so went back to stock rom (android 9). Phone now boots to LG logo with startup tune, and just sits there on that screen for at least 1 minute longer than it did previously. Did a a complete wipe between flashes, went back to pixel experience to see if it went back to normal "boot speed", Phone bootup speeds went back to normal on that. Now back on stock again, and it's same thing with long boot time. Phone boots up fine eventually but it is quite painful to deal with now and regretting trying something different with zero payoff.
Any ideas?
Click to expand...
Click to collapse
Yep, exactly this. After many hours yesterday of troubleshooting and trying different stuff, what I did in end was downgrade to first oreo release and OTA'd my way backup, all back to normal now.
Phew, glad it's not something I have to live with.
ChazzMatt said:
Many have found flashing back to Nougat KDZ, then flashing to Pie KDZ (your bootloader will remain unlocked during both flashes), then re-installing TWRP, and re-rooting erases some of the changes you describe. See this post for reinstalling all that stuff, after you flash Nougat, then Pie KDZ.
INSTALL or REINSTALL TWRP on PIE stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285
Can't guarantee it, but going back to Nougat temporarily flushes a lot of stuff out of the system.
Which variant do you have?
Click to expand...
Click to collapse