Hey all,
I've been trying to get an up-to-date MIUI for the P769 users. @artit used to make one but has ceased development and @ZduneX25 makes one for the P760 but unfortunately, not for the P769 as well.
I have tried several different ways:
Rom porter: using CM 10.1 as the base and using both ZduneX25's miui p760 rom as the port rom
- have also tried this using MIUI's official p760 rom
Artit's MIUI port method for MIUI V5: as seen here: http://forum.xda-developers.com/showthread.php?t=2476760 in post #2
- again, i tried CM10.1 and Artit's p769 version as a base rom and both p760 versions(ZduneX25 and official MIUI as a port rom)
However, I still can't get it to boot fully...
as with Artit's rom, it starts with a backwards LG screen then show's an miui logo with flame/fire and then goes to the MIUI LG optimus on an orange background and never boots past here.
I have unpacked and repacked it properly thanks to a lot of googling and help from XDA members but still can't find out why it won't boot since all of the other roms booted up fine.
I have tried to take logcats through ADB but the device does not connect when trying to boot after installing. It connects via adb before I install but yeah.
Is there anything I can do since it won't boot far enough to be recognized by adb or any other way I can troubleshoot this?
Maybe, I'm not the only P760 user looking to get a decent updated MIUI rom. If I have any luck, I'll for sure pass it along!
edit: I tried installing ZduneX25's p760 rom and it installed correctly but everything was mirrored. Is there a simple fix I can do to just edit the rom(flip the img back) to work with P769?
shockah486 said:
Hey all,
edit: I tried installing ZduneX25's p760 rom and it installed correctly but everything was mirrored. Is there a simple fix I can do to just edit the rom(flip the img back) to work with P769?
Click to expand...
Click to collapse
use ZduneX25's rom as a port rom, then go to my porting Guide, i hope you success porting MIUI for p769
shockah486 said:
edit: I tried installing ZduneX25's p760 rom and it installed correctly but everything was mirrored. Is there a simple fix I can do to just edit the rom(flip the img back) to work with P769?
Click to expand...
Click to collapse
If there's a way to fix mirrored screen of P769 when flash other variants' ROM, it must be very good news because I think we'll have more ROM for P769 (share with P760/P768). Anyone know why the screen is mirrored only with P769? I'm so confuse, maybe because of LG want that?
nhoc_maruko9x said:
If there's a way to fix mirrored screen of P769 when flash other variants' ROM, it must be very good news because I think we'll have more ROM for P769 (share with P760/P768). Anyone know why the screen is mirrored only with P769? I'm so confuse, maybe because of LG want that?
Click to expand...
Click to collapse
I wish I knew the answer but it has probably something to do with the fact our p769 unlocked bootloader is based off of the p760 one. If only it were as easy as editing a few settings fix the backwards screen image!
nasheich said:
use ZduneX25's rom as a port rom, then go to my porting Guide, i hope you success porting MIUI for p769
Click to expand...
Click to collapse
I tried your porting guide with Artit's p69 rom (cm10.1.3 based) and the official miui v5 4.2.XX 10.1.3 patchwork rom for p760 as the port rom. It installed to 100% but upon boot, I ended up with the screen:
DemiGod Crash HAndler : Kernal Panic has been occured
Please do following action:
1)capture this screen
2)get last_kmsg.txt log in /data/dontpanic after rebooting
Internal error: Oops: 817 PREEMPT SMP
CPU: 0 Not tainted (3.0.31-CM+-#1)
PC is at eventpoll_release_life+0x38/0x7c
LR is at __mutex_lock_slowpath+0x248/0x314
pc : c01420d4 lr : c0551f24 par: 200a0013
sp e683df38 iq : 00000090 fp: e79f3188
(eventpoll_release_life+0x38/0x7c) from (fput+0x198/0x1f8)
(fput+0x198/0x1f8) from (flip_close+0x58/0x7c)
(flip_close+0x58/0x7c) from (sys_close+0xa4/0xb8)
kernel panic - not syncing: Fatal exception
Kernel version: Linux version 3.0.31-CM+ antsvx9UBUNTU64) (gcc version 4.7.4 20130603 (prerelease) Linaro GCC 4.7-2013.03-1) #1 SMP PREEMPT Mon Oct 7 13:20:45 EDT 2013
Anybody have any idea what's wrong?
Looks like firmware issue. I had this issue when I forgot to get p760 vendor and etc/firmware folder.
Related
Hi, all,
I recently helped an acquaintance that was having a terrible time with an assert_failed error with Loki while trying to install CM 10.2, so I figured I'd explain the problem and solution.
Backing up to the beginning, this acquaintance recently upgraded to the G2 (a few weeks ago) and wanted to test out KitKat. Here, we discovered that the phone had been updated to VS98012b before he'd received it - but rather than reverting to stock, we decided to use the root solution detailed here (http://wiki.cyanogenmod.org/w/Install_CM_for_d802), but we swapped the Loki flash method to that detailed here (http://forum.xda-developers.com/showthread.php?t=2449670) and used the CWM no-touch image from here (http://forum.xda-developers.com/showthread.php?t=2498941). [For reference, the touch image doesn't flash properly... but the one without touch is still touch-enabled.]
After gaining root and getting CWM up and running, we decided on the Nightly CM 11 build (ro.build.date=Sat Jan 18 08:04:40 PST 2014) and it flashed with the recommended GApps without a hitch.
Fast-forward three days and said acquaintance is having tons of crashing issues and some apps weren't working too well - certainly not far-fetched for a nightly build. We decided to flash him back to CM 10.2. However, after doing a factory reset, wiping the cache again to be sure, then wiping the dalvik cache, and finally running the CM 10.2 stable version available here (http://download.cyanogenmod.org/get/jenkins/49892/cm-10.2.0-vs980.zip, date: 2013-12-02 21:45:13) we ran into the following error during the install:
Code:
script aborted: assert failed: run_program("/tmp/loki.sh") == 0
assert failed: run_program("/tmp/loki.sh") == 0
Neat.
Some digging lead to a Pastebin (http://pastebin.com/uLtw2vG6) with an explanation of the problem and a proposed solution:
Code:
[email protected] : autoprime, thats 9/10 times because old loki_patch
...
[email protected] : if they are stuck in recovery completely because they wiped everything then just remove the assert line you meniotned and flash the rom then flash the zip I just linked
Since I've poked around with ROMs before, I unzipped the CM 10.2 ROM and popped the /cm-10.2.0-vs980/META-INF/com/google/android/updater-script file open to remove the assert line and the deletion line, incidentally. But reflashing the ROM and the linked zip that Shellnutt2 suggested (http://downloads.codefi.re/shelnutt2/freegee/loki_boot.zip, for the curious) didn't actually work for us. Much of the problem, I suppose, had to do with the data and system partitions not being loaded in the loki_boot.zip updater-script.
So a bit of thought lead me to check the CM 11 commits for updates to enable functionality for the VS98012b update - bingo! A conveniently close-to-the-top update (http://review.cyanogenmod.org/#/c/56181/) mentioned that, as Shellnutt2 suggested, loki_flash was updated for this precise reason. Now, I wasn't about the pull the whole CM 10.2 repo and build with the updated loki_flash.c, so I just copied the newest CM 11 nightly's /system/bin/loki_flash, /system/bin/loki_patch, and /system/bin/loki.sh into the CM 10.2 ROM's /system/bin/ and overwrote the old ones (after reverting the updater-script changes, of course). After rezipping, the install worked like a charm!
---
[TLDR]
If you're having
Code:
script aborted: assert failed: run_program("/tmp/loki.sh") == 0
assert failed: run_program("/tmp/loki.sh") == 0
errors,
1) grab the latest CM distribution and copy the loki_flash, loki_patch, and loki.sh files out of /system/bin/ (or from https://www.mediafire.com/?y3ubxgnxzxq89f9, which are from the Tue Jan 21 13:05:13 PST 2014 CM11 Nightly) and
2) paste them over the /system/bin/ equivalents in whatever VS980 ROM you're having problems with,
3) rezip,
4) and clean flash the ROM in recovery.
Presumably, this workaround should work for all VS980 ROMs (tested for CM10.2 and OSE) that haven't updated their loki_patch versions. It probably won't work for any other phone that has loki.sh failed assertions - the GitHub master loki repo (https://github.com/djrbliss/loki/blob/master/loki_flash.c) doesn't say anything like the CM 11 distro, so it's likely a check coded in. But I didn't take the time to look into that on the CM side.
EDIT: This should also work for devices other than the VS980 - I looked up loki_flash.c rather than loki_patch.c (https://github.com/djrbliss/loki/blob/master/loki_patch.c) and incorrectly commented on the situation.
Any phone/software version found in the CyanogenMod 11 Repo listing for loki_patch.c (https://github.com/CyanogenMod/android_device_lge_g2-common/blob/cm-11.0/releasetools/loki_patch.c) file - do a CTRL+F - should be able to apply this workaround to flash a ROM with an out-of-date patcher.
EDIT 2:
This solution should, based on the Loki source used for CM11, work for the following G2 models:
AT&T: D80010d, D80010o (however 10o has a reported failure and no successes)
Verizon: VS98010b, VS98012b
T-Mobile / Canada: D80110c or D803
International: D802b
Sprint: LS980ZV7
KT / LGU: F320K, F320L
SKT: F320S, F320S11c
However, if you're just looking for a CM 10.2 ROM with this fix for the Verizon VS980, I uploaded the zip that I flashed for my acquaintance for convenience: http://www.mediafire.com/download/tmu28ihn3gm2ngw/cm-10.2-vs98012b.zip .
[/TLDR]
---
Hope this helps anyone that's having the same problem - good luck flashing!
Is the Loki patch updated for 12b backward compatible with 11a and so on?
Basically, would one on 11a, be able to flash a ROM with the 12b Loki patch?
Great write up by the way
VS980
If you're looking for a stable AOSP kk ROM try cyanfox. Its cm based. I've been running it for about 3 weeks with paeks kernel and have 0 probs with it. No lag no crashes no lockups no sods. Its been the most stable AOSP ROM I've found.
Sent from chdhsheh fhhdud
I've been having the same problem with the AT&T G2 on 10o. Besides downloading, do you think this will work for any of those roms?
Sent from my LG-D800 using xda app-developers app
Dork6243 said:
Is the Loki patch updated for 12b backward compatible with 11a and so on?
Basically, would one on 11a, be able to flash a ROM with the 12b Loki patch?
Click to expand...
Click to collapse
Skizzy034 said:
I've been having the same problem with the AT&T G2 on 10o. Besides downloading, do you think this will work for any of those roms?
Click to expand...
Click to collapse
The listed carrier/software variants in the current (Wed Jan 22 2014) CM11 G2 repo's loki_patch.c (and the uploaded loki_patch zip file) are:
AT&T: D80010d, D80010o
Verizon: VS98010b, VS98012b
T-Mobile / Canada: D80110c or D803
International: D802b
Sprint: LS980ZV7
KT / LGU: F320K, F320L
SKT: F320S, F320S11c
If you were to compile the current (Wed Jan 22 2014) loki_patch.c from https://github.com/djrbliss/loki/blob/master/loki_patch.c (sorry, can't post links because of new member restrictions) yourself, you'd get an added compatibility with:
DoCoMo: L-01F
On PURELY SPECULATIVE terms, there's a good chance other versions of the software for the different carriers could be supported if you download the Loki source and compile it after adding another entry (format shown below in code tags) for your specific carrier/software version. But I don't know anything about the code and have no reason to look into it, so I can't confirm this. Plus, I don't own a G2 myself and can't test this method anyway.
Code:
{
.vendor = "T-Mobile or Canada",
.device = "LG G2",
.build = "D80110c or D803",
.check_sigs = 0xf813294,
.hdr = 0xf906440,
.lg = 1,
},
feldenthorne said:
The listed carrier/software variants in the current (Wed Jan 22 2014) CM11 G2 repo's loki_patch.c (and the uploaded loki_patch zip file) are:
AT&T: D80010d, D80010o
Verizon: VS98010b, VS98012b
T-Mobile / Canada: D80110c or D803
International: D802b
Sprint: LS980ZV7
KT / LGU: F320K, F320L
SKT: F320S, F320S11c
If you were to compile the current (Wed Jan 22 2014) loki_patch.c from https://github.com/djrbliss/loki/blob/master/loki_patch.c (sorry, can't post links because of new member restrictions) yourself, you'd get an added compatibility with:
DoCoMo: L-01F
On PURELY SPECULATIVE terms, there's a good chance other versions of the software for the different carriers could be supported if you download the Loki source and compile it after adding another entry (format shown below in code tags) for your specific carrier/software version. But I don't know anything about the code and have no reason to look into it, so I can't confirm this. Plus, I don't own a G2 myself and can't test this method anyway.
Code:
{
.vendor = "T-Mobile or Canada",
.device = "LG G2",
.build = "D80110c or D803",
.check_sigs = 0xf813294,
.hdr = 0xf906440,
.lg = 1,
},
Click to expand...
Click to collapse
There is def. a problem with flashing roms on 10o.
Just as an update, Skizzy034's problem was apparently resolved by flashing the previous AT&T D800 firmware. (Presumably 10d.)
Perfect!
Thank you very much!!
I was having this exact error while installing 10.2, and your rom worked perfectly. Thanks!
Yeah buddy!
Thanks for the zip dude. ROM is running perfect. :good:
You have no Idea how much this helps
I thought I was totally screwed haha
Thanks for this! It worked out trying to get PAC-man ROM 4.4.2 for my D803. I just copied the loki files from another ROM.
CM11!
Oh man, I spent tons of time trying to find out what I did, and almost gave up. I switched to CM11 Nightly and it worked like a charm.
Latest CM 11.0 no longer contains loki_patch
The files in mediafire link that you provided didn't work for me, but I used the "loki.sh" and "loki_tools" files from a recent nightly build (cm-11-20141209-NIGHTLY-d800.zip) and it worked fine. loki_patch no longer is provided with cm-11, so I removed it from the cm-10.2 zip and my flash worked without it.
Thanks so much for posting this and helping everyone out with this problem.
Carl
Hi,
i was using Mokee 4.4.4 and since a few weeks I'm using Mokee 5.0.2
It is a rom like CM12 but with some customization, not as many as AOKP but still more than in CM12
It is multilangual and as stable as cm12
It was updated recently : http://www.yirom.com/rom/index/344
did someone already download it ? If yes is it possible to upload it somewhere else like mega ?
Thank you in advance
I'm running the 23/3 version of Mokee 5.02 as of a few hours. So far so good!
Does dual sim works well?
And battery consumption is similar to 4.4.4 RC7?
Did you detected any bugs?
Is it stable enough for a daily device?
Lord_Snake said:
Does dual sim works well?
And battery consumption is similar to 4.4.4 RC7?
Did you detected any bugs?
Is it stable enough for a daily device?
Click to expand...
Click to collapse
I'm using the previous version (1st march) and I used it daily
i don't use 2 sim cards.
I had 1 reboot (not a wished, it was because of a crash) in nearly one month
Lord_Snake said:
Does dual sim works well?
And battery consumption is similar to 4.4.4 RC7?
Did you detected any bugs?
Is it stable enough for a daily device?
Click to expand...
Click to collapse
The previous version dual SIM worked very well. I'll know if the dual SIM will work well for the new version later this week as I will be travelling.
Yes I'm using it for a daily work phone as I rely on it. Thou I have my ultra-stable iPhone 6 as my personal phone/backup :victory:
can someome upload it ?
EDIT: Someone post a mirror in other topic
I used this one : http://www.gamefront.com/files/24894999/MK50.2-nx507j-201503230233-UNOFFICIAL.zip
I think I get more spontaneous reboots with this new version than with the last version. However, it could be due to the memory leak issue all Android Lollipop phones have and isn't fixed until 5.1
Hoping to see Mokee 5.02 upgrade soon to 5.1 and integrate native dual SIM support...
Hello, I like the mokee rom,
If you have the file MK50.2 or more, please post it !
sdchew said:
I think I get more spontaneous reboots with this new version than with the last version. However, it could be due to the memory leak issue all Android Lollipop phones have and isn't fixed until 5.1
Hoping to see Mokee 5.02 upgrade soon to 5.1 and integrate native dual SIM support...
Click to expand...
Click to collapse
This has been confirmed in several posts on some of the Chinese bbs. Apparently, someone has released a temporary fix; although, I haven't tried it yet. I agree, I'm having the same problem. Additionally, it vibrates for everything. I currently have it set to vibrate only on phone and SMS, yet it does for everything and I cannot find out how to make it stop.
pedrud said:
This has been confirmed in several posts on some of the Chinese bbs. Apparently, someone has released a temporary fix; although, I haven't tried it yet. I agree, I'm having the same problem. Additionally, it vibrates for everything. I currently have it set to vibrate only on phone and SMS, yet it does for everything and I cannot find out how to make it stop.
Click to expand...
Click to collapse
I didn't noticed this kind of error
but I admit this is because of my config => my phone does not vibrate and it is my xiaomi MiBand who vibrate for specific notifications
does anybody have a custom recovery that works with android 5.0 on z7 mini.
I have stock 5.0 installed and wanted to flash the newest mokee. but when i want to make a backup through the old mokee cwm, but it always says "cant mount data".I would thing thats because of the changed partitions.
Anyway, is there any (non-chinese) recovery that i can use with stock 5.0?
sancho777 said:
does anybody have a custom recovery that works with android 5.0 on z7 mini.
I have stock 5.0 installed and wanted to flash the newest mokee. but when i want to make a backup through the old mokee cwm, but it always says "cant mount data".I would thing thats because of the changed partitions.
Anyway, is there any (non-chinese) recovery that i can use with stock 5.0?
Click to expand...
Click to collapse
Here in the z7 mini rom thread on post 781 (top) is a link to TWRP 2.8.5.0. However, I don't know if the new mokee works after flashing the nubia version of 5.0 because I don't think (someone can correct me) the mokee uses unified storage yet. Can someone verify this?
Thanks, trying TWRP right now.
So anybody knows if i can flash Mokee 5.02 after flashing Offical 5.0 with the new kind of partitions?
pedrud said:
Here in the z7 mini rom thread on post 781 (top) is a link to TWRP 2.8.5.0. However, I don't know if the new mokee works after flashing the nubia version of 5.0 because I don't think (someone can correct me) the mokee uses unified storage yet. Can someone verify this?
Click to expand...
Click to collapse
sancho777 said:
Thanks, trying TWRP right now.
So anybody knows if i can flash Mokee 5.02 after flashing Offical 5.0 with the new kind of partitions?
Click to expand...
Click to collapse
I did not tried it right now as i'm still discoverng this android 5 by nubia...
i just tried it 1 min and can already say that I may switch to mokee soon (I'll try the nubia rom 1 week I guess..)
the UI feels slow
I don't like the nubia theme
and beside of that, the French translation f(cuoco92 rom) is partial and canadian only (other timezone, other clock format, other keyboard layout...)
nubia's rom seems more unstable than mokee (from the first comments I read on cuoco92 facebook page)
it is also very BIG (double the size...)
If you are afraid of bricking the phone, you can also use the stupid chinese tool to install again kitkat on the phone, then install again mokee
but i guess (not sure !!!! ) that it should be possible to install mokee without doing this pain in the ass trick :/
sancho777 said:
Thanks, trying TWRP right now.
So anybody knows if i can flash Mokee 5.02 after flashing Offical 5.0 with the new kind of partitions?
Click to expand...
Click to collapse
No, you cannot. See this thread on the Nubia forum. CM12 and Mokee are still technically considered 4.4 because they do not use the unified storage. You will most likely brick the phone if you attempt to flash it. You have to first use the Nubia updater to go back to at least 1.82, then you can use CM12 or Mokee.
This is Team Superluminal cyanogenmod 12.1 (5.1.1) port for your Lenovo K910
Check out our website www.teamsuperluminal.org
You can find all files and latest updates from there!
XDA:DevDB Information
TS-Cyanogenmod 12.1, ROM for the Lenovo K900
Contributors
ekkilm, morphicts
Source Code: Not shared yet
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TS-TWRP 2.8.6.
Based On: Cyanogenmod 12.1
Version Information
Status: Beta
Created 2015-04-12
Last Updated 2015-07-16
Just install on my phone. Work just fine on K910L
Hey!
Great step by step manual.
I am just wondering - can we make it a bit simpler and skip unlocking bootloader?
e.g. I can download twrp from google play, from this installed twrp I can choose reboot to recovery and I can see twrp 2.8.1.0
Why can't I just from this point flash CM12.1? May it cause any problems?
Thank you for your reply!
ruphuss said:
Hey!
Great step by step manual.
I am just wondering - can we make it a bit simpler and skip unlocking bootloader?
e.g. I can download twrp from google play, from this installed twrp I can choose reboot to recovery and I can see twrp 2.8.1.0
Why can't I just from this point flash CM12.1? May it cause any problems?
Thank you for your reply!
Click to expand...
Click to collapse
Sorry for lately respond! These instructions are the way we have tested this process and we have stated that it is the most effective way to install everything and be sure everything works as they should. If you have allready unlocked the bootloader, you dosen´t have to do it again, but be sure that it is unlocked. And if you are in 4.2.2., then I recommend to flash 4.4.2 first, for the partition table and then 5.1.
About TWRP, our recovery is compiled from cm12.1 (lollipop) source and we are sure that it is compatible with our rom. Ofcourse you can try any other recovery, but this is the recommended method. And you're doing it at your own risk, as all custom flashes.
Thank you for your support and stay tuned, there is rom update ...B12, enjoy!
-Team Superluminal, ekkilm
Flashable on k900?
Can i flash this ROM on K900?. I got this page as one of the search results under the ROMs tab for K900
tech_savvy_sk said:
Can i flash this ROM on K900?. I got this page as one of the search results under the ROMs tab for K900
Click to expand...
Click to collapse
No... This rom is for K910. There is no undercategory for K910, so that why it is under k900. Sry...
ekkilm said:
No... This rom is for K910. There is no undercategory for K910, so that why it is under k900. Sry...
Click to expand...
Click to collapse
Ok thanks. Even i was wondering why did it come under ROMs tab for k900
AVRCP?
Hey guys,
great work and thumbs up for supporting the K910! I installed the latest build (RC16) just a few hours ago and noticed immediately in the car, that no music metadata is being transmitted to my car radio. Is AVRCP currently not supported? It worked with the official KitKat ROM at least.
Edit: Never mind - I reflashed the whole thing and it works now.
AFAIK AVRCP up to v1.5 is supported, but I don't have equipment to test meta data stuff atm.
Even though you said it's working now, I double checked BT config and there were still some old stuff lying around from CM11
I'll bring BT config up to date in next build.
Saiyajin said:
Hey guys,
great work and thumbs up for supporting the K910! I installed the latest build (RC16) just a few hours ago and noticed immediately in the car, that no music metadata is being transmitted to my car radio. Is AVRCP currently not supported? It worked with the official KitKat ROM at least.
Edit: Never mind - I reflashed the whole thing and it works now.
Click to expand...
Click to collapse
ROM UPDATE
cm-12.1-20150614-UNOFFICIAL-kiton RC17 (see downloads)
MD5: 687823fef854f15b9250cc522e2ab050
Fixed power off charger only mode
Bring WLAN config in line with upstream
Bring BT config in line with upstream
Default LCD density to 440
Enable dual sim by default
Fixed ghost sim icon when switching from dual sim to single sim mode
Sync with CM12.1 source
NOTE: First boot takes longer time, because SC6500 modem FW update (blue led blinks)
NOTE2: Remember factory reset when coming from any other ROM than previous version of TS CM12.1
Enjoy,
Team Superluminal, Morphic
great work !!
thank you for this amazing rom ,
phone model is K910 ,rom 14/6/2015
i followed instructions all and all ok
except in blutooth headset the sound in call is ok in sim1 BUT sim2 no call sound in headset at all , tried using single sim mode sim2 no sound ..
so i know you did hard work and hope it completes
thank you again for your efforts
Ok
long system reboot
NOTE: First boot takes longer time, because SC6500 modem FW update (blue led blinks)
Click to expand...
Click to collapse
hi, i am stuff at the first boot like forever, and there is no blue led blinks.
below is the files that i have used
- gapps-L-4-16-15.zip
- cm-12.1-20150623-1G.zip
- Bootloader_Unlocker 4.4
How to install cm12 on lenovo vibe z k910?
aiha2420 said:
How to install cm12 on lenovo vibe z k910?
Click to expand...
Click to collapse
Check out www.teamsuperluminal.org and there are roms-> cm12.1 see the instructions there.
Hello. This firmware phone Lenovo K900? The firmware has a Russian language?
Hello. This firmware phone Lenovo K900?
The firmware has a Russian language?
HI Can install on my lenovo k910 dual sim or not?
download link
Hey, why i can't find or see dowlosd link? And your site doesnt work
Great I just brick my phone
I was .bat unlook bootloader on my lenovo 4.4.2 from barajlabi (or somethink like this) and then phone restart but dont turn on :/ If i pres power button do nothink, no answer, black screen no light only vibration before meny seconds :/ When i plug on PC in Device Menager, Lenovo HS-USB Diagnostics 9006, fck :/
How can i fix this ??? I try with eMMC Software download but Download mode work for little seconds and turn off :/
Help :/ :crying:
Hello,
I've benn running this ROM for a while but I have problem with loud speaker. I thought, that it's some HW problem with my phone (like stugged some dust in that small holes on the back site of phone) but I cleaned it up few days ago and loud speaker volome is still very very low (like I barely hear when my phone in my pocket ringing in public). But if I make some camera record and uploud it on YouTUBE (or simply play it on my laptop) than sound volume seems to be fine.
Do you have any solution for that? Because I found some solution for CM but for another phones.
Thank you.
Hello dear Community,
i really hope you can help me along. First of all pardon my english... i have not used it for a decade so it is really "rusty"
I bought a Kindle Fire HDX 7 Inch (the Version with Front Facing Camera) second hand. It came with Cyanogenmod 11 and Safestrap on it installed by the previous owner.
Now i figured out that there are CM 12 and CM 13 Versions availuable for this device (thor should be its pseudonym)...
I don't want to brick my device and i have no idea where to really start....
First of all i always read about unlocked bootloaders... if i am correct my tablet at the moment does not have an unlocked bootloader just a sort of "bypass" so that the older Cyanogenmod 11 works? Is that correct?
If so how can i unlock it properly... i already tried the 1 Click unlock method posted in this forum using VirtualBox etc.... which failed with an error code and did not seem to work out well.
What else do i have to do in order to successfully install Cyanogenmod 13 nightlys? Is Safestrap as sort of a recovery based on an older TWRP Version (2.7x is suppose) a proper recovery for installing a rom? Or do i need to change the recovery? What about the rom slot management options in Safestrap i found!?
I hope somebody might help me out with this (i am not totally new to flashing roms) but i just want to be sure to make it in the right way and order... (cyanogenmod wiki is not speaking a word about unlocking the bootloader in terms of how to do it properly).
Lots of Questionmarks over my head.... *sigh*
I hope someone can help me sort this out.
Best regards
Daedra666 said:
Hello dear Community,
i really hope you can help me along. First of all pardon my english... i have not used it for a decade so it is really "rusty"
I bought a Kindle Fire HDX 7 Inch (the Version with Front Facing Camera) second hand. It came with Cyanogenmod 11 and Safestrap on it installed by the previous owner.
Now i figured out that there are CM 12 and CM 13 Versions availuable for this device (thor should be its pseudonym)...
I don't want to brick my device and i have no idea where to really start....
First of all i always read about unlocked bootloaders... if i am correct my tablet at the moment does not have an unlocked bootloader just a sort of "bypass" so that the older Cyanogenmod 11 works? Is that correct?
If so how can i unlock it properly... i already tried the 1 Click unlock method posted in this forum using VirtualBox etc.... which failed with an error code and did not seem to work out well.
What else do i have to do in order to successfully install Cyanogenmod 13 nightlys? Is Safestrap as sort of a recovery based on an older TWRP Version (2.7x is suppose) a proper recovery for installing a rom? Or do i need to change the recovery? What about the rom slot management options in Safestrap i found!?
I hope somebody might help me out with this (i am not totally new to flashing roms) but i just want to be sure to make it in the right way and order... (cyanogenmod wiki is not speaking a word about unlocking the bootloader in terms of how to do it properly).
Lots of Questionmarks over my head.... *sigh*
I hope someone can help me sort this out.
Best regards
Click to expand...
Click to collapse
Quick responses (btw - your english is fine!):
- Safestrap is not a generic recovery and can not be used to flash roms other than those designated as "Safestrap Compatible"
- Unlocking the bootloader is the best (really only) path to newer ROMs including CM 12.1 and CM 13; links to relevant threads below
- If you opt to stick with Safestrap v4 do NOT create or use secondary slots; everything happens in the STOCK slot
Everything you need to know about unlocking the bootloader can be found in these two threads. Read the thread OP (important) and then focus on posts made during the past 30 days. Good luck!
http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
http://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Hi,
I am stuck right at the beginning with the attempt to install LineageOS on my LG G2 mini, because I am not able to get root. My conclusion is that I am failing because my Stock-SW Version seems different from what is captured in this forum mostly.
Device: LG-D620r
Software platform: Android 5.0.2
Software version: V20e-232-03
Build-Number: LRX22G
It's an Austrian, Telering-branded LG G2 mini.
Of course I've tried the path described in here: https://forum.xda-developers.com/g2-mini/development/root-root-g2-mini-lollipop-t3123652 even trying that attached kingroot.apk, which in the end failed with "no methods found", I guess because of this exotic SW-Version.
Next thing would be to load one of the patched bootloaders here https://forum.xda-developers.com/g2-mini/development/bootloader-d620-d618-t3127819, but I would not know which version to pick. But without root I can't proceed anyway(?)
Would be nice if anyone of you has ideas on how to achieve this. Maybe I am just missing something obvious?
For my background: I have installed and troubleshooted LineageOS before on an Moto G (thea) which was of course way easier
downgrade to kitkat, everything will be easier. @psycoy
Hey @psycoy, I just did that and along with some other issues it finally worked. So, a late thank you, it was appreciated!