My Lenovo Vibe K5 Plus (3GB RAM) has OTA update problem.
I'm attaching some Screenshots.
Its not rooted or modified in any way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone will reboot normally and show "OTA Update failed".
My question is can I update it to latest build by using Lenovo Update Assistant or should I go in order to avoid bricking?
Can I flash the latest build using "Lenovo Smart Assistant" or QFIL?
Will it create any problem like bricking?
Please help.
Your problem is quite classic, the way to solve it is quite simple, but you'll have to lose your data anyway.
The first way is to check if in your internal storage you have a "/0/carrier" folder. If it's the case, you should flash the file <your_country>.ota.zip (via "apply update from sdcard", if it's not accessible, you should copy this file on your external SD card). It will take some time but then you should download and update your phone
In my latest experience, you can try to use Lenovo tools, but I did not succeed to flash my phone this way (never found the right model)
Personnally, when I want to get back to "updatable stock", I usually do this :
Flash a stock ROM via QFIL, but not the last version (I'm on K5 Plus 2GB, and I flash S042)
Just after success, I reboot to booloader via "Power + Vol -"
Using my PC, I reboot to a TWRP recovery, without flashing it, and without changing the readonly filesystem (via TWRP you can access both internal and external storage) : fastboot boot <path to twrp img file>
Here I flash the /0/carrier/<my_country>.ota.zip
Then I reboot and my ROM is installed, and updatable without the carrier problem
Tell me if you need further explanations.
@adinechin thankyou so much for replying.
I don't need my data because I've already backed up everything.
Can I downgrade to a lower build? For example I have build S051 currently installed, so can I go back to S042 with QFIL without any problems?
Is there any other method which doesn't need TWRP because I'm very much afraid of going custom at this moment, because of my lack of knowledge?
I don't have anything in 0 folder. Its empty even after downloading OTA update.
Apocalypse0 said:
@adinechin thankyou so much for replying.
I don't need my data because I've already backed up everything.
Can I downgrade to a lower build? For example I have build S051 currently installed, so can I go back to S042 with QFIL without any problems?
Is there any other method which doesn't need TWRP because I'm very much afraid of going custom at this moment, because of my lack of knowledge?
Click to expand...
Click to collapse
Did you check if you have your ota.zip file ? If you can find it, you only have to flash it and that's it
Sent from my Lenovo K5 Plus using XDA Labs
adinechin said:
Did you check if you have your ota.zip file ? If you can find it, you only have to flash it and that's it
Sent from my Lenovo K5 Plus using XDA Labs
Click to expand...
Click to collapse
No, that's what the irritation. After downloading OTA completely, I don't get anything in my 0 folder. That folder is completely empty. No OTA.zip or any other files completely empty.
Apocalypse0 said:
No, that's what the irritation. After downloading OTA completely, I don't get anything in my 0 folder. That folder is completely empty. No OTA.zip or any other files completely empty.
Click to expand...
Click to collapse
Ok so you can flash any ROM with QFIL, and if you are not comfortable with TWRP, you can try removing your sdcard after flashing ROM, reboot to recovery and flash the OTA.zip.file.
Be aware that flashing with QFIL will also wipe your internal storage.
Sent from my Lenovo K5 Plus using XDA Labs
@adinechin thank you. I have updated to latest version.
Thankyou so much.
I have few questions.
1. Why we can't flash latest version directly from QFIL?
2. My phone gets shut down automatically if not in use. Is it something hardware related because it was fallen down once and I'm getting this annoying problem even after updating to newer build? Earlier I was thinking it is something software related but now I think its hardware problem. Do you have any idea to share on this?
It gets shut down only after not in use. If I use it for hours it works correctly but as soon I lock the screen it gets switched off and only after removing and reinserting the battery it will on again. No matter how long you press Power button it won't get on. Even recovery combination won't work until I remove and reinsert the battery.
Thanks a ton for helping me.
Apocalypse0 said:
@adinechin thank you. I have updated to latest version.
Thankyou so much.
Click to expand...
Click to collapse
Glad I helped you
Apocalypse0 said:
1. Why we can't flash latest version directly from QFIL?
Click to expand...
Click to collapse
You can, but I personally prefer to update via the phone to be sure all is back to normal stock
Apocalypse0 said:
2. My phone gets shut down automatically if not in use.
Click to expand...
Click to collapse
I have no idea on this subject, but with what you describe, it seems more likely to me that the phone is "stuck" than "off". I know it can happen some times if an app takes much memory, especially when you just installed the ROM, it takes some time to stabilize. Have you tried to wait a little when it was stuck like that and unlock it a bit later ? Another remark, instead of removing battery (which can be very annoying), try holding Power Vol+ and Vol- during around 10 seconds : you should reboot to download mode (black glowing screen like with QFIL), and then do it again, you should reboot your phone.
It was happening even on older build. Yes I waited and tried everything (key combinations) but nothing worked. That's why I feel its a hardware problem because of the fall the device took. No problem if I keep using it, no hanging problems or other things, but as soon I lock the screen it just gets switched off Very irritating.
Anyway, you've helped me a lot and I really appreciate the way you've kept everything simple because these things go really above my head.
Thanks again.
Related
WARNING: From koush' IRC channel it seems this version may be (permanently?) bricking devices.
At the time of this writing only a single working flash has been reported, and several (full?) bricks.
--Chainfire
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
932e5f7a9f09c9bc33b14a527f642933
Initramfs source: http://github.com/koush/i9000-leshak-initramfs/tree/koush
Installation instructions:
Install Odin3 v1.0 (MAKE SURE THIS IS THE VERSION YOU USE)
Start Odin3
Press PDA
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads
Wow!... Looks great!
Wanna try after going back home!
I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?
Koush said:
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
Installation instructions:
Install Odin3
Start Odin3
Press PDU
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads
Click to expand...
Click to collapse
Can I assume this kernel wasn't compiled with ext3/4 support?
achio1115 said:
I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?
Click to expand...
Click to collapse
I'm guessing, but considering this replaces the zImage that mimocan's fix provides anything you have on moved to ext3/ext4 will not be accessible.
To reverse reflash with the mimocan kernel.
Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do
Chainfire said:
Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do
Click to expand...
Click to collapse
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.
damianarnold said:
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.
Click to expand...
Click to collapse
I can confirm that, this mod won't work if you have mimocan's kernel applied.
Does it work if you "unapply" it ? Can you get your phone back functional again ?
cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it
raspdeep said:
cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it
Click to expand...
Click to collapse
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid
damianarnold said:
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid
Click to expand...
Click to collapse
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.
Chainfire said:
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.
Click to expand...
Click to collapse
Every single app. you've installed will need to be reinstalled, it's as if the device is completely cleared of any settings/config.
Basically you need to restore from backup.
If you see this screen
follow these commands while odin3 is opened.
"SIM+SD out, put the battery in. Plug in USB. Hold down both Volume keys, and then push power. Hold it. From the phone > pc screen, hold vol +/- and power, wait til it goes black then returns to that screen. When it goes black the 2nd time release power. " That should put you in download mode so you can install the recovery again.
Then flash this kernel to fix any slowness
http://android.eugenekay.com/Vibrant/LeshakKernel_9_01b9.tar
Eugenekay couldn't link because he only has 4 posts so I'm doing it for him
This might not apply to i9000 users but I posted it just encase.
Also any flashing done in odin formats everything. That is why recovery is needed in order to try and get zip updates. Zip updates wont allow a whole rom flash just modifications.
@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.
so are there gonna be roms in zip ?
or this recovery is gonna handle tars as well?
buddy01 said:
@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.
Click to expand...
Click to collapse
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).
not working on JF7, keeping on rebooting
Chainfire said:
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).
Click to expand...
Click to collapse
fair enough.
hkfriends said:
not working on JF7, keeping on rebooting
Click to expand...
Click to collapse
Does the same thing on JG5...
When I first applied it, it rebooted itself twice in a row and booted fine. It ran for a good few hours... restored apps. from titanium backup. Did a reboot again. (just to be safe.) At that point, it kept rebooting itself... and then I pretty much gave up and flashed the stock JG5. (couldn't head to work w/o a working phone, lol) Anyone got it to work so far?
I bought a tab 3 8.0 recently and which after it got updated through wifi touch was not responding as it should later I restared and it was back to normal. Later after few hours the problem started so I rebooted into recovery to clear the cache it displayed error. The tab works fine sometimes but goes back to touch unresponsiveness when I resume the tab after resumining from sleep mode. Can any please help meand if there are similar problems with tab 3
ansonlarken said:
I bought a tab 3 8.0 recently and which after it got updated through wifi touch was not responding as it should later I restared and it was back to normal. Later after few hours the problem started so I rebooted into recovery to clear the cache it displayed error. The tab works fine sometimes but goes back to touch unresponsiveness when I resume the tab after resumining from sleep mode. Can any please help meand if there are similar problems with tab 3
Click to expand...
Click to collapse
you cannot clear cache from stock recovery.
Only data. (act as reset anyways)
just odin another firmware see if it continues.
Update works most of the time, if you let it sits for around 15 minutes after updating.
Many people got problem after system updates was caused by themselves really.
Rules for updating.
1) let it sits for 15 minutes after update.
2) Do not do manual reboot right after update. (After auto reboot) (Wait for 15 Minutes -- minimal)
3) Do not run/install/download right after update. (Leaving it alone for 15 minutes)
4) make sure nothing is running before tapping system update. (reboot, wait 3 minutes, then press system update) / or clear ram from task manager before tapping system update
*Reasons: update is installed, but it might have to convert/translate certain already existing data. We don't know, but just to avoid data corruption, just leave it alone and do not interrupt the process by doing anything above.
The problem still persist...even after resetting the device through recovery and settings... now when I try to update it says that I have the latest update what do I do. Where do I get another firmware if I wana odin the device. This is really annoying help me please
comscier said:
you cannot clear cache from stock recovery.
Only data. (act as reset anyways)
just odin another firmware see if it continues.
Update works most of the time, if you let it sits for around 15 minutes after updating.
Many people got problem after system updates was caused by themselves really.
Rules for updating.
1) let it sits for 15 minutes after update.
2) Do not do manual reboot right after update. (After auto reboot) (Wait for 15 Minutes -- minimal)
3) Do not run/install/download right after update. (Leaving it alone for 15 minutes)
4) make sure nothing is running before tapping system update. (reboot, wait 3 minutes, then press system update) / or clear ram from task manager before tapping system update
*Reasons: update is installed, but it might have to convert/translate certain already existing data. We don't know, but just to avoid data corruption, just leave it alone and do not interrupt the process by doing anything above.
Click to expand...
Click to collapse
The problem still persist...even after resetting the device through recovery and settings... now when I try to update it says that I have the latest update what do I do. Where do I get another firmware if I wana odin the device. This is really annoying help me please
ansonlarken said:
The problem still persist...even after resetting the device through recovery and settings... now when I try to update it says that I have the latest update what do I do. Where do I get another firmware if I wana odin the device. This is really annoying help me please
Click to expand...
Click to collapse
Samfirmware.com is the place to get firmware.
Sent from my GT-P5210 using XDA Premium HD app
Benzoman said:
Samfirmware.com is the place to get firmware.
Sent from my GT-P5210 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks will check It out
US Firmware
I had trouble finding the US version of the Firmware for the Tab 3 8" until I found this post
http://forum.xda-developers.com/showthread.php?t=2471516
it contains a link to the firmware :good:
ansonlarken said:
I bought a tab 3 8.0 recently and which after it got updated through wifi touch was not responding as it should later I restared and it was back to normal. Later after few hours the problem started so I rebooted into recovery to clear the cache it displayed error. The tab works fine sometimes but goes back to touch unresponsiveness when I resume the tab after resumining from sleep mode. Can any please help meand if there are similar problems with tab 3
Click to expand...
Click to collapse
I'm having the exact same issue that you are, and it is in fact extremely annoying. I'm the one that posted the firmware for our device (linked in the post above this,) and it will not fix our problem.
I've flashed stock rom, modified rom, modified kernel, stock kernel, wiped every single thing possible, and have had absolutely no luck with getting the touch panel (digitizer) working properly again.
It has something to do with the tsp driver being corrupt, or stuck in a constant loop of powering on/off. If you connect to ADB and run "dmesg" you will see over and over again
"[TSP] DVFS On!" and then [TSP] DVFS Off!"
Something to do with "melfas-ts," I think.. As far as I know, it's a Mali chipset, and we need to somehow get the kernel to reinitialize it, or remove it and then reinstall it..
Here's a picture of what I'm talking about:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
foil said:
I'm having the exact same issue that you are, and it is in fact extremely annoying. I'm the one that posted the firmware for our device (linked in the post above this,) and it will not fix our problem.
I've flashed stock rom, modified rom, modified kernel, stock kernel, wiped every single thing possible, and have had absolutely no luck with getting the touch panel (digitizer) working properly again.
It has something to do with the tsp driver being corrupt, or stuck in a constant loop of powering on/off. If you connect to ADB and run "dmesg" you will see over and over again
"[TSP] DVFS On!" and then [TSP] DVFS Off!"
Something to do with "melfas-ts," I think.. As far as I know, it's a Mali chipset, and we need to somehow get the kernel to reinitialize it, or remove it and then reinstall it..
Here's a picture of what I'm talking about:
Click to expand...
Click to collapse
Dude the problem is resolved.... i went to a samsung servicing center told them about the problem, they said it would take atleast 2 days to check it. Finally the tab is working absolutely ok as it should be. Said they had to change the motherboard. Thats all they said as there was a problem linked with it. Why don't you get it checked and i think thats the only solution rather then hampering the device. Good luck. I also tried almost everything.
ansonlarken said:
Dude the problem is resolved.... i went to a samsung servicing center told them about the problem, they said it would take atleast 2 days to check it. Finally the tab is working absolutely ok as it should be. Said they had to change the motherboard. Thats all they said as there was a problem linked with it. Why don't you get it checked and i think thats the only solution rather then hampering the device. Good luck. I also tried almost everything.
Click to expand...
Click to collapse
I appreciate the input, and I have actually already sent it off to a service center this morning. However, I'm a hardware hacker, and know what I'm doing with it - it's the touch panel controller that needs the firmware reflashed onto it. If I could reflash the firmware myself, I would have much rather done that, and also had a fix for everybody else. I need the device too bad for work at the moment, or I wouldn't have even bothered sending it in.
This is only what has worked for me i take no responsibility for anyones phone catching fire after following my guide/advice. Tested myself on a UK D802 16GB on Three Network! Confirmed working on 32GB devices now too!!
This needs formatting to make it easier to read. I will get around to it but here is the basic info needed!
Please READ this entire first post before asking questions that are already answered.
Today i have managed to flash the European Open Kitkat rom and root it and keep TWRP recovery. It worked for me but can't guarantee the same results for you.
Prerequisites. (Skip this if you already have rooted JB rom with custom recovery)
First i downgraded to Jellybean using this guide. I downgraded to "UK Open 16GB D80210B_00.kdz" i'm not sure if that's required though.
Then I rooted it using IORoot.
Then i installed TWRP using Freegee from the Play Store.
From here you are ready to flash or you can start from here if you already have root and recovery on Jellybean.
You need these three files.
1. My modded Stock rom zip.
Mirror 1 | Mirror 2
2. Savoca Modded Boot.img.
3. SuperSU ZIP.
Now to flash! (Take out your simcard first.)
1. Boot into TWRP and flash the modded stock rom DOWNLOAD 1. It will take a while and the screen may turn off during this, just press power button. Ignore the failed error!
2. Now go to main TWRP screen and select Reboot Recovery. (Wouldn't mount system otherwise!)
3. Now go to Mount and make sure System is ticked. (Not sure if required but do it anyway!)
4. Now flash Savoca's modified boot.img DOWNLOAD 2.
5. Again go to Mount and make sure System is selected.
6. Now flash SuperSU ZIP DOWNLOAD 3.
7. Now i wiped data here not sure if it's required as the rom wipes system but do it anyway!
8. Replace sim and reboot and all should be well!
If you have NO MOBILE NETWORK i got this error and that's why i recommended removing sim card. I had to repeatedly toggle wifi on and off, and airplane mode and restarted a few times. Not sure what fixed it but don't panic it DOES work.
Bugs and Fixes!
Audio Hissing/Crackling on Headphones.
This is present on all Kitkat roms currently. Some users don't get it most do. Type of headphones seems to be a factor. The following fix is temporary and will revert after a reboot. So needs to be repeated if your phones reboots for any reason.
Type in phone dial pad 3845#*802# and it will show Hidden Service Menu.
Click on "ELT Test", select "Manual Mode" and select "Test Start".
With headphones plugged in select "Audio Loopback" and than select "Test Start".
Blow gently into the microphone and keep on this test 20 seconds or more.
Once done back out and play music. Enjoy!
No LTE/4G anymore?
It seems to require a change of bands for some to get LTE working. There is a value to edit in build.prop. You can do this manually with a root explorer and setting correct permissions after changing, I've found the easiest way is to download JRummy Build.prop editor from market.
Open the Build Prop Editor app.
Find the value "ro.telephony.default_network" and select it.
Notice the property value will be set to "9". Change this to "11" and let the app reboot phone.
If you still don't have LTE try again but change the value to "13" and let the app reboot phone.
Bluetooth Battery Drain
This is NOT real battery drain so please don't worry about it. It is a falsely reported statistic. I get battery life on a par with 4.2.2. Around 8 hours screen on time which is fantastic! If you have battery drain please try a full wipe, don't restore apps from another rom do it manually. Take a look at your apps.
How is it done?!
The modded zip is stripped down to include only the System, Modem and Cust partitions. These are all that is required for Kitkat to play nice with Savocas modified boot.img. I edited the updater-script to remove the entries for all partitions except those listed above and repacked it up nicely to flash. So it is possible to do this with any future updates too. The Cust partition is necessary in case your partition has old carrier stuff still on there, this flashes a clean Cust partition.
Thanks to:
LenAsh for the flashable zip i modded.
Savoca for the modded Boot.img and modules.
Chainfire for SuperSU.
Jesus for blessing all the little children.
it would be great if you also make one for the 32gb version
anyways, great work, dude!
I'm flashing it right now and looking up your address at the same time in case it won't work ;]
How long should it take to boot ?
superbonto said:
it would be great if you also make one for the 32gb version
anyways, great work, dude!
Click to expand...
Click to collapse
As i've said it seems like there isn't a difference between md5's of 32gb and 16gb versions of Kitkat i just wouldn't want to say test it... But in theory it should work just fine.
paniczklos said:
I'm flashing it right now and looking up your address at the same time in case it won't work ;]
How long should it take to boot ?
Click to expand...
Click to collapse
Let me know how it goes...you know just to give me a running start I assume you're 16GB user? It doesn't take long to boot but if it loops make sure you have wiped data in recovery. It is safe to do factory reset in standard recovery too as i tried it when trying to get my network back on!
ephumuris said:
As i've said it seems like there isn't a difference between md5's of 32gb and 16gb versions of Kitkat i just wouldn't want to say test it... But in theory it should work just fine.
Let me know how it goes...you know just to give me a running start I assume you're 16GB user? It doesn't take long to boot but if it loops make sure you have wiped data in recovery. It is safe to do factory reset in standard recovery too as i tried it when trying to get my network back on!
Click to expand...
Click to collapse
I'm preparing a dead fish to throw it on your doormat ;p
I'm on 12th minute of booting - LG logo and led flashing green-to-blue.
And yes I'm 16GB
How to use the standard recovery ?
Is it repeatedly making the boot sound? Hold power button and volume down until LG logo flashes up, then release power button and press again whilst keeping hold of volume. You should get a white screen. Just press power twice i think that should reset it.
I'm pretty sure it didn't take me 12 minutes to boot
Can you please tell us how to mod the original EUR kdz? I can't download 2 gigabytes now and I already have the kdz file. Is there any guide?
Thanks ephumuris
Hey TC i have a lg g2 16gb that i bought from amazon. I am also on the three network in the uk. I do not get 4g option on my phone. Sorry for OT but i havent met anyone else on here using three and g2. Any help would be appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-D802 using Tapatalk
SPBoss said:
Hey TC i have a lg g2 16gb that i bought from amazon. I am also on the three network in the uk. I do not get 4g option on my phone. Sorry for OT but i havent met anyone else on here using three and g2. Any help would be appreciated. View attachment 2630159
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
What rom are you running? I get the option for gsm/wcdma/lte auto. Although no 4g for me on Three in Hull yet.
badchip said:
Can you please tell us how to mod the original EUR kdz? I can't download 2 gigabytes now and I already have the kdz file. Is there any guide?
Thanks ephumuris
Click to expand...
Click to collapse
I'm guessing there is some sort of tool to extract the KDZ files and then all you need out of that is system.img and modem.bin and cust.bin... Easy to make an update script or i can upload one for you. I've never needed to extract a KDZ though...
ephumuris said:
Is it repeatedly making the boot sound? Hold power button and volume down until LG logo flashes up, then release power button and press again whilst keeping hold of volume. You should get a white screen. Just press power twice i think that should reset it.
I'm pretty sure it didn't take me 12 minutes to boot
Click to expand...
Click to collapse
Doing that boots the TWRP. i've wiped the data like a satan, in every possible way. There's no boot loop - it's just booting and booting and booting. I think I'll have to go back to stock and repeat. Or is there any way to upload files to the phone through recovery (I remeber there was this option in clokcwork recovery ) ?
paniczklos said:
Doing that boots the TWRP. i've wiped the data like a satan, in every possible way. There's no boot loop - it's just booting and booting and booting. I think I'll have to go back to stock and repeat. Or is there any way to upload files to the phone through recovery (I remeber there was this option in clokcwork recovery ) ?
Click to expand...
Click to collapse
I'm not sure if there is an option in TWRP i've certainly not seen it. I find it strange that you are getting stuck at boot screen... Maybe it matter which JB rom you come from?
My original one was 80210B Euro open rom.
"UK Open 16GB D80210B_00.kdz"
ephumuris said:
I'm not sure if there is an option in TWRP i've certainly not seen it. I find it strange that you are getting stuck at boot screen... Maybe it matter which JB rom you come from?
My original one was 80210B Euro open rom.
"UK Open 16GB D80210B_00.kdz"
Click to expand...
Click to collapse
D80210A_00.kdz - it's EUR open + OTA update to E version.
I'm trying do sideload the files through ADB ;/
ephumuris said:
I'm guessing there is some sort of tool to extract the KDZ files and then all you need out of that is system.img and modem.bin and cust.bin... Easy to make an update script or i can upload one for you. I've never needed to extract a KDZ though...
Click to expand...
Click to collapse
Thanks, I found this guide but it doesn't mention the download from Savoca. Should I just follow it (and use the KKROM_template.zip)? Or what do you recommend? I really can't to flash KK with root on my device
paniczklos said:
D80210A_00.kdz - it's EUR open + OTA update to E version.
I'm trying do sideload the files through ADB ;/
Click to expand...
Click to collapse
The starting rom is the only thing i can think of that could make a difference if you followed instructions exactly all the factors are the same besides that!
It would help if anyone else has downloaded it and flashed successfully or unsuccessfully to let us know!
badchip said:
Thanks, I found this guide but it doesn't mention the download from Savoca. Should I just follow it (and use the KKROM_template.zip)? Or what do you recommend? I really can't to flash KK with root on my device
Click to expand...
Click to collapse
That guide will give you a rooted Kitkat rom but no custom recovery. Which is a risky position to be in
Although the tool would be useful in that thread it would allow you to get the system.img, modem.bin and cust.bin you need. I could then provide a blank update zip with just the correct updater-script for you?
ephumuris said:
The starting rom is the only thing i can think of that could make a difference if you followed instructions exactly all the factors are the same besides that!
It would help if anyone else has downloaded it and flashed successfully or unsuccessfully to let us know!
Click to expand...
Click to collapse
I'm downloading the UK open EUR and I'll start over.
ephumuris said:
That guide will give you a rooted Kitkat rom but no custom recovery. Which is a risky position to be in
Although the tool would be useful in that thread it would allow you to get the system.img, modem.bin and cust.bin you need. I could then provide a blank update zip with just the correct updater-script for you?
Click to expand...
Click to collapse
I would very much appreciate that. I have used the tool to extract the kdz and dz. I have the files in screenshot now.
Whats the proper next step?
Thanks for your help
edit: The meta-inf folder is from the KK template provided in that thread, I suppose I don't need that.
Hi!
Firstly thanks for this!
and secondly i have to say that i already flashed to my LG G2 32gb and works like a charm... btw i also did it with another way:
1-Downgrade to 4.2.2.
2-when your in v.4.2.2 root and recovery.
3-i used lastest CWM version from Philz.
4-FLash your Rom.zip
5-reboot to recovery. (Dunno if this is really necessary but just in case i did it too)
6-Flash Savoca Patched
7-Flash Root
8-Reboot
9-ENjoy EUR 20b =)
Thanks!
Great to confirm working on 32gb too. Badchip you might have to wait til later unless you can use that existing meta inf folder. I've just left for work so not at laptop.
Try deleting every file but only keep.
Meta inf folder.
System.IMG
Modem.bin
Custom.bin
Zip those up and flash them. Should work if the update script is right in meta inf folder.
@iall5tar What base jellybean rom did you downgrade to?
And regarding custom recovery it should work with any cwm philz or twrp. I just referenced twrp as that's what I use.
Sent from my LG-D802 using Tapatalk
What you mean about folder meta-inf? im not a expert i just want to give a try and it worked xD
Here is the stock 14.5.A.0.270 (5.0.2) customized AU odexed, pre-rooted, highly debloated and bundled up with PRFCreator
BEFORE and AFTER:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ZIP ARCHIVE INCLUDES:
a) the rom itself (removed bunch of crapware)
b) SuperSU-2.49-BETA
c) Nuts Dual Recovery 2.8.15
d) DRM Function Restoration for UB
STEPS:
1) backup
2) wipe /system, /cache, /dalvik-cache
3) flash the main rom
4) flash google services removal.zip (optional)
5) boot up phone and go through setup
6) flash further debloat (optional)
DOWNLOADS:
Main
Google Services Removal
Further Debloat
Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?
Papanik said:
Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?
Click to expand...
Click to collapse
I'm interested in this as well. Does flashing your rom restore BIONZ processing, making all the steps in the linked thread un-necesarry?
Also, anyway to check if BIONZ is working or not?
Papanik said:
Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?
Click to expand...
Click to collapse
zgomot said:
I'm interested in this as well. Does flashing your rom restore BIONZ processing, making all the steps in the linked thread un-necesarry?
Also, anyway to check if BIONZ is working or not?
Click to expand...
Click to collapse
I'm currently on a locked bootloader so I can't verify if it'll work without having to flash an ftf with TA beforehand. Best thing to do is try it yourself.
If x-reality is working, bionz is working.
I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!
facing problems...
After i do google and further debloat... dun even have app store to install my apps. I also unable to add my google account at Settings > Accounts...
Its great to have a RAM free rom... but what the point of having so much ram when there's nothing else u can do with the phone. I did try installing Google Play Store apk but it just simply crashes...
Please dun be offended as I still feel this ROM is a well done rom, I might just missed out something.
kedirakevo said:
After i do google and further debloat... dun even have app store to install my apps. I also unable to add my google account at Settings > Accounts...
Click to expand...
Click to collapse
The google debloat is only optional. If you don't flash it, you'll get to keep the play store.
I personally don't use the play store and download my apps from apkmirror or evozi
Okay, can share more what does further debloat do? I can do that without google debloat right?
kedirakevo said:
Okay, can share more what does further debloat do?
Click to expand...
Click to collapse
Further debloat removes some of the bloat that I forgot to remove from the main rom itself and also the setup wizards. So make sure to use it only after booting your device and going through the setup.
I can do that without google debloat right?
Click to expand...
Click to collapse
Yes.
I've tried flashing this twice and have ended up softbricking twice. I think the issue may be because of the wiping of system, which I have honestly never had to do before, so I'll try once again, and if it doesn't work I guess I'll just find something else.
EDIT: Yep, nothing I do seems to really be working, probably just getting bad downloads on my end though.
compatible with c6902?
Is this compatible with xperia z1 ,c6902?
Zerousen said:
I've tried flashing this twice and have ended up softbricking twice.
Click to expand...
Click to collapse
Do you have a c6903 and on latest kitkat(.108) or .242?
ravishmahur said:
Is this compatible with xperia z1 ,c6902?
Click to expand...
Click to collapse
Nope.
How to flash Xposed in this rom please? Thanks
Ahki767 said:
Here is the stock 14.5.A.0.270 (5.0.2) customized AU odexed, pre-rooted, highly debloated and bundled up with PRFCreator
edited
Click to expand...
Click to collapse
Flashed without issues coming from CM12.1 (the terrible, terrible photo-quality and some in-call sound issues recently always make me return to stock). I just took care to follow instructions and flash a pre-rooted .2.4.2 rom prior to flashing this.
The rom feels really really smooth, it's lovely so far.
edit: One issue thus far is some incompatibility on the Play Store, for instance Galaxy On Fire - Alliances. I can download it on any rom (CM/stock) except this one. Anyway to fix this?
edit2: Are dpi values changed for the launcher? I've tried a couple of xposed modules but I can't seem to get rid of that empty edge. The grid size is weird... it's like 4x4 but really crowded, with nasty-looking empty margins.
I tried a couple of apps to change dpi values to default, but they wouldn't read current dpi and no new values could be applied. Maybe this is linked to the Play Store incompatibilities.
How must I install it? Always I installed it (from official .242 and .270 too with RockZ1 Kernel) I had many bugs on this ROM, please help me
HELP
dyonissos said:
I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!
Click to expand...
Click to collapse
Please help, I'v also got the same problems. I follow everything, but now my phone can not turn on anymore, can not charge. Everytime I press power button, it only vibrate once, but still off. Please help me.
I do the steps from Kitkat and using latest DUAL RECOVERY TWRP.
Thank you in advance
busukusu said:
Please help, I'v also got the same problems. I follow everything, but now my phone can not turn on anymore, can not charge. Everytime I press power button, it only vibrate once, but still off. Please help me.
I do the steps from Kitkat and using latest DUAL RECOVERY TWRP.
Thank you in advance
Click to expand...
Click to collapse
I fond the solutions for my problems. I test Fastboot at It work. When Power Off, press Volume Up and connect the USB Cable, then I can detect my phone with command: fastboot devices
After that, using Flashtools and install any FTF source with Kitkat 108, then flash it using Flashtools at computer PC. Prepare downloaded FTF files about 1 GB size at the same computer drive, then run Flashtools and then connect Press Volume Down and connect with USB cable, after that Flashtools display will show that my phone detected / connected, and continue with flashing FTF files, the process about 10 minutes less, and after finish flashing, disconnect USB cable, press Power button and YES it work again.
After that I have to install again with TWRP and install any Stock preroot firmware.
dyonissos said:
I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!
Click to expand...
Click to collapse
I had the exact same problem. Ended up going back to my nandroid backup.
I am on locked bootloader. Not sure if that is the problem.
@Ahki767 could you please post md5 of the package? I am trying to make sure my download is not corrupt.
zgomot said:
edit: One issue thus far is some incompatibility on the Play Store, for instance Galaxy On Fire - Alliances. I can download it on any rom (CM/stock) except this one. Anyway to fix this?
edit2: Are dpi values changed for the launcher? I've tried a couple of xposed modules but I can't seem to get rid of that empty edge. The grid size is weird... it's like 4x4 but really crowded, with nasty-looking empty margins.
Click to expand...
Click to collapse
if you're still on this rom, you can change the dpi in /system/build.prop look for lcd_density and change it to 480 (original value). only thing i can think of for incompatibility is maybe an out of date play services
squashbuff said:
@Ahki767 could you please post md5 of the package? I am trying to make sure my download is not corrupt.
Click to expand...
Click to collapse
md5 check: 0406a4743310ee19209cfedcf0c728c9
make sure you're flashing at least from latest kit kat or lollipop
Hi,
I am having a serious problem with my Nexus 5x:
After installing the new AOSPA today, I wiped data, cache and dalvik and then tried to boot the phone (up to that point, everything was ok). Instead of showing the usual "google" logo with the warning about the unlocked bootloader , the screen just shows some colorful static (i'll attach a photo of that).
So, I can't boot the phone. It's recognized in fastboot mode by the computer, but the screen doesn't show anything. Same goes for recovery (TWRP), I can talk to the phone via ADB but the screen remains black.
I've tried everything I can, including reverting the software to stock (see Heisenberg's guide) but without wiping the personal data.
Do you have any idea what I could do to get my phone back except relocking the bootloader and sending it in for repair?
Thanks a lot!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: RMA'd the phone, they had to replace the screen / touch unit (obviously) and the camera (?) for some reason
dbahn25 said:
Hi,
I am having a serious problem with my Nexus 5x:
After installing the new AOSPA today, I wiped data, cache and dalvik and then tried to boot the phone (up to that point, everything was ok). Instead of showing the usual "google" logo with the warning about the unlocked bootloader , the screen just shows some colorful static (i'll attach a photo of that).
So, I can't boot the phone. It's recognized in fastboot mode by the computer, but the screen doesn't show anything. Same goes for recovery (TWRP), I can talk to the phone via ADB but the screen remains black.
I've tried everything I can, including reverting the software to stock (see Heisenberg's guide) but without wiping the personal data.
Do you have any idea what I could do to get my phone back except relocking the bootloader and sending it in for repair?
Thanks a lot!
Click to expand...
Click to collapse
This looks like a display failure unfortunately. I don't know if there's anything more you can do except RMA since you flashed the factory image. Could you post the file name of the AOSPA rom zip that you flashed?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
This looks like a display failure unfortunately. I don't know if there's anything more you can do except RMA since you flashed the factory image. Could you post the file name of the AOSPA rom zip that you flashed?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Oh no :crying: how could that be from just flashing a new rom (+ gapps)? I didn't do anything differently from all the other times I flashed my ROM..... Was it really just bad luck?
I flashed the AOSPA build from 6/6/16 (pa_bullhead-6.0-20160606-signed.zip) with BaNkS gapps (BaNkS_Dynamic_GApps_6.x.x_6-7-16_23_51.zip)
I guess it'd be best to lock the bootloader for the RMA, wouldn't it?
dbahn25 said:
Oh no :crying: how could that be from just flashing a new rom (+ gapps)? I didn't do anything differently from all the other times I flashed my ROM..... Was it really just bad luck?
I flashed the AOSPA build from 6/6/16 (pa_bullhead-6.0-20160606-signed.zip) with BaNkS gapps (BaNkS_Dynamic_GApps_6.x.x_6-7-16_23_51.zip)
I guess it'd be best to lock the bootloader for the RMA, wouldn't it?
Click to expand...
Click to collapse
On the P.A website and Google post it says they highly recommend using open gapps perhaps Ur issue is related to that??? I'm no expert is there anyway u can sideload the ROM and open gapps via adb ???
Sent from my Nexus 5X using XDA-Developers mobile app
dog121 said:
On the P.A website and Google post it says they highly recommend using open gapps perhaps Ur issue is related to that??? I'm no expert is there anyway u can sideload the ROM and open gapps via adb ???
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
No... they say you should use banks instead of open gapps since those might make problems. That's the reason I didn't use the open gapps
I'm not sure about the sideloading though, I've never done that. Do you have a guide for me?
dbahn25 said:
No... they say you should use banks instead of open gapps since those might make problems. That's the reason I didn't use the open gapps
I'm not sure about the sideloading though, I've never done that. Do you have a guide for me?
Click to expand...
Click to collapse
Have a look at this...
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I suggest you get the latest update that just came out via Google updates for Nexus 5x and give that a whirl....
I hadn't realised that P.A changed the gapps yesterday they were using open gapps...
Sent from my Nexus 5X using XDA-Developers mobile app
dog121 said:
Have a look at this...
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I suggest you get the latest update that just came out via Google updates for Nexus 5x and give that a whirl....
I hadn't realised that P.A changed the gapps yesterday they were using open gapps...
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
Alright, thanks! Unfortunately, I've already shipped my phone back to repair / replacement. But I wonder, is there any advantage of using sideload over using fastboot to flash the stock image?
Also I don't think it would've worked since I couldn't have enabled sideload without seeing anything on screen (it was completely black while in recovery).
dbahn25 said:
Also I don't think it would've worked since I couldn't have enabled sideload without seeing anything on screen (it was completely black while in recovery).
Click to expand...
Click to collapse
It can be done, just need to look at screenshots someone else posts of the recovery menu and count.