Related
I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please
ImjuzCY said:
I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please
Click to expand...
Click to collapse
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358
jj14 said:
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358
Click to expand...
Click to collapse
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be
ImjuzCY said:
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be
Click to expand...
Click to collapse
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this
jj14 said:
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this
Click to expand...
Click to collapse
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now
I tried everything and still get wrong build fingerprint when trying to flash the 5.0
ImjuzCY said:
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now
Click to expand...
Click to collapse
Hello!
Really want to flash the OTA without a total wipe.
First flashed it from TWRP 2.8.1.0 and got the wrong build finger print says I have Flo:4.3/JSS15Q/779366 and it expects KTU84P/1227136
Then using WugFresh 1.9.4 flashed stock recovery so I could sideload then encountered the whole adb disappearing in recovery - eventually solved that and finally managed to adb sideload saw my screen saying it was installing the update using the stock recovery - YAY! It was short lived as the stock recovery screen told me the exact same thing that TWRP had told me.
I looked at my build.prop and it says my ro.build.fingerprint=google/razor/flo:4.4.4/KTU84P/1227136. user/release-keys
Can someone enlighten me? I've wasted so much time on this I would love some keen insight - PLEASE!!
Thanks for any and all help!
Edbogue
Google changed the way OTAs work in 5.0. You will usually not be able to flash a OTA if your OS is modified. Means no custom recovery or root. You will have to flash your tab back to stock kitkat.
Before it would patch individual file blocks, now it patches the whole system partition as a blob. Read more http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
Workaround that helped me upgrade
Following the steps below seems to have done the trick for me. My issue was that Android 5.0 updates the system partition all in one go now, rather than each file separately. Following those steps will unroot your device but will allow you to install the OTA updates.
So follow these steps to refresh your current Android version (e.g 4.4.4) then use OTA or adb sideload to update to, for example, 5.0.
This will not wipe user data or the cache.
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
I would post my source, but as I only just joined to say what helped me, I'm not allowed to post links I'll just say Google "flashing-a-stock-android-image-without-wiping-user-data" and (as of 19/11/2014) it's the top result.
Please continue here: http://forum.xda-developers.com/nexus-4/help/android-5-0-0-to-5-0-1-update-t2972371#post57515317
Finally finally!!! A fix!
Raingram said:
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
.
Click to expand...
Click to collapse
Thank you Raingram! This worked perfectly!
INSTALL OFFICIAL CM12 TO YU YUREKA
Yu Yureka has got the official Cyanogenmod 12S sealed and signed by Google which is being rolled out today! Few users has already got the update and we have captured the OTA link , that means now we don't have to wait for the OTA update. We can also install them manually and can enjoy the sweeter taste of Lollipop.
As it is officially confirmed, you may check the forum
_____________________________________________________________________________
Requirements :-
1.) Data Plan to download approx 680 mb OTA file.
2.) Charged Yu Yureka device.
3.) Stock recovery, download here
4.) Rashr to flash stock recovery.
5.) Backup all your data.
6.) Patience, it will require 30 min to install the update
Steps to Install the OTA update :-
1.) Flash the stock recovery first from Rashr or Flashify.
2.) Download the OTA zip file and place it in your storage.
3.) Power off your device, Now press Volume Up + Volume Down + Power button simultaneously.
4.) Cyanogenmod Official Recovery will be opened.
5.) Select 2nd option i.e. Apply Update
6.) Select the storage, you have copied the OTA zip file
7.) Select the OTA Zip file, and open it, it will start to install the update.
8.) Wait for the completing installation, you have to reboot it manually .
9.) First bootup will take time, so keep patience.
10.) Voila You have successfully updated your Yu Yureka to CM12S.
NOTE: We are not responsible to any damage to your device. Do at your own risk!
data's
my data's are deleted or not.
during this update ?
Yes, it will
Panneer Selvam said:
my data's are deleted or not.
during this update ?
Click to expand...
Click to collapse
Your Phone storage will be formatted! And your Internal Storage will not, but make the backup of that too
Hit Thanks if help
You havn't send the link of the files, Can you send the link of how to download those recovery too, if i does that, it mean by phone will be rooted na, Sorry i am new bee i don't know much about rooting
JoelXD said:
You havn't send the link of the files, Can you send the link of how to download those recovery too, if i does that, it mean by phone will be rooted na, Sorry i am new bee i don't know much about rooting
Click to expand...
Click to collapse
DONT worry YOU can flash the above file by stock recovery also,
if you dont understand anything revert me back.
D_Rising_Pheonix said:
DONT worry YOU can flash the above file by stock recovery also,
if you dont understand anything revert me back.
Click to expand...
Click to collapse
Hmmm i did and it got installed successfully, but when my factory restore it from new cm12, its again doing all that from begining, but only difference this time, its installing 122 app, and before it was 156 app. Is it normall, Will it take so long to factory reset in Lolipop ??
Will it solve the problem if i would have rooted my device, i just on the recovery mode of Yureka, by pressing volume key and power button , than apply update and update the ROM. and now everytime i factory reset, its doing the whole process again again.
Android is Upgrading ...
Please help
Thanks in Advance !
I'm on custom ROM crdroid and cwm recovery,
So I just need to flash stock recovery and then flash the ota?
On Custom Rom Can i flash this...
I am on custom rom, should i flash in official recovery and flash the update? or what should i do??
Is upgrading to cm12 worth it?
Link to download stock 64-bit cyanogen recovery for CM12.0-YNG1TASOWO
Please provide me Link to download stock 64-bit cyanogen recovery for CM12.0-YNG1TASOWO.Please also tell me how to flash it.l,Currently I m using CWM/TWRP recovery.
I am on cm12s official update not able to install music app of Sony walkman of z3. After installing and on play it says can't play the song. Help
Any one rooted after updating to CM12 (Official)
I have updated my so far i have noticed some lags & network issues
PLS share your problems
THX
vipimg said:
Any one rooted after updating to CM12 (Official)
I have updated my so far i have noticed some lags & network issues
PLS share your problems
THX
Click to expand...
Click to collapse
If you wanna root it....Just install a custom Recovery & flash SuperSu.zip
hrishi21007 said:
If you wanna root it....Just install a custom Recovery & flash SuperSu.zip
Click to expand...
Click to collapse
I am just asking if its the same procedure as CM11 ....?(Dont wat to brick it)
Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ??
Mine's bricked.
rahulsingh616 said:
Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ����
Click to expand...
Click to collapse
i also update to lollipop, unlocked the bootloader and flashed 64bit twrp but my phone is bricked. can u please help?
thanks in advance.
aakarshak said:
i also update to lollipop, unlocked the bootloader and flashed 64bit twrp but my phone is bricked. can u please help?
thanks in advance.
Click to expand...
Click to collapse
This is what I was trying to say i was not sure about it i didnt do it yet just waiting for a solid one
Mr aakarshak
May i ask if your phone now in boot loop ...? or something else
vipimg said:
Mr aakarshak
May i ask if your phone now in boot loop ...? or something else
Click to expand...
Click to collapse
I jst flashed the cwm recovery and its working fine
Yes i was about to tell u to flash CWM recovery
aakarshak said:
I jst flashed the cwm recovery and its working fine
Click to expand...
Click to collapse
which one... is it 64 bit or the old one ????
rahulsingh616 said:
Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ����
Click to expand...
Click to collapse
i am also trying to flash the same thru fastboot but every time i am booting to recovery it shown cynogen's recovery.
update cm recovery is already unchecked in Dev option.?
any help
Rooted my phone, bricked it, and now went back to default Lollypop
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
After flashing dont start ua phone
Go to recovery mode directly!
abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
What is the proper procedure to install the fast boot version as I am facing issues after installing the OTA and probably they can be resolved with the fastboot option. Kindly help.
I hv updated my yureka yesterday manually to cm12 and device is running very smoothly..bt I faced an issue while charging the phone..it was taking around 4hrs of time and phn heating a lot .. I was thinking to revert back to kitkat which was also working f9 for me without any heating issue bt I came to know it is not passible to go back.. I was bit tensed regarding heating issue bt suddenly I see my lumia 520 charger and I charged yureka with that charger and u won't believe charging speed is increased and phn was nt heating up at all.. I don't knw what is issue with charning in lollipop bt nw I am very relaxed ...
original 12S zip links
abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
Can u post links to original CM12S zip u mentioned above...?
vipimg said:
I am just asking if its the same procedure as CM11 ....?(Dont wat to brick it)
Click to expand...
Click to collapse
I bricked mine... So i dont recommend rooting after upgrading to cm 12
kailashnj said:
What is the proper procedure to install the fast boot version as I am facing issues after installing the OTA and probably they can be resolved with the fastboot option. Kindly help.
Click to expand...
Click to collapse
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.
abeyhere said:
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.
Click to expand...
Click to collapse
Are you sure this worked for you,cause basically you are just saying that you did the normal rooting procedure that we did when we had kitkat,just that you used a 64 bit recovery this time
Stock recovery for CM 12
abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
Can you tell you you flashed the cm12 recovery ???
i cannot find it inside the cm12 update zip file.
abeyhere said:
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.
Click to expand...
Click to collapse
I did install the rom from the fastboot method still it did not work. I am fed up of the CM12 rom.
My Huawei p6 is stuck at Huawei Ascend Logo screen or in TWRP menu.
Here is the history :
-From the stock Firmware, its been updated to B132 > B512 > B708
-TWRP installed and rooted.
-SD card partitioned and used Link2sd.
- Phone was working quite OKEY.
What Happened :
- I was fumbling with the phone, and accidently I used TWRP Advanced wipe (data, dalvik cache, system)
Now whats happening :
- Phone stuck at Huawei Ascend Logo screen
- If i press vol+ + vol - +power buttons, it goes to TWRP menu.
- in the TWRP menu, it shows NO OS INSTALLED at various places.
What I tried :
- I put the B708 zip file to SD card and tried flashing from TWRP.
md5 file not found, failed installing zip. FAILED.
- I tried B512 zip file too. same result.
Now the phone is always ON, in the Huawei Ascend Logo screen.
Note :
- I am not an expert user.
- The phone is not getting detected in windows.
How shall I get back to the B708 OS or atleast the stock firmware ?
ozshire said:
My Huawei p6 is stuck at Huawei Ascend Logo screen or in TWRP menu.
Here is the history :
-From the stock Firmware, its been updated to B132 > B512 > B708
-TWRP installed and rooted.
-SD card partitioned and used Link2sd.
- Phone was working quite OKEY.
What Happened :
- I was fumbling with the phone, and accidently I used TWRP Advanced wipe (data, dalvik cache, system)
Now whats happening :
- Phone stuck at Huawei Ascend Logo screen
- If i press vol+ + vol - +power buttons, it goes to TWRP menu.
- in the TWRP menu, it shows NO OS INSTALLED at various places.
What I tried :
- I put the B708 zip file to SD card and tried flashing from TWRP.
md5 file not found, failed installing zip. FAILED.
- I tried B512 zip file too. same result.
Now the phone is always ON, in the Huawei Ascend Logo screen.
Note :
- I am not an expert user.
- The phone is not getting detected in windows.
How shall I get back to the B708 OS or atleast the stock firmware ?
Click to expand...
Click to collapse
Are the files that you putting on sd card official update files or custom ones? Twrp csn only flash custom ones for the official you need stock recovery.
Sent from my SM-G850F
tileeq said:
Are the files that you putting on sd card official update files or custom ones? Twrp csn only flash custom ones for the official you need stock recovery.
Sent from my SM-G850F
Click to expand...
Click to collapse
Thanks for the support Tileeq.
The ROM file is
" B708_Repack_NeoArnet.V3". The one I used to update to kitkat 4.4.2, got from the XDA forum itself.
http://forum.xda-developers.com/ascend-p6/general/ascend-p6-b708-emui-3-0-international-t2991646
ozshire said:
Thanks for the support Tileeq.
The ROM file is
" B708_Repack_NeoArnet.V3". The one I used to update to kitkat 4.4.2, got from the XDA forum itself.
http://forum.xda-developers.com/ascend-p6/general/ascend-p6-b708-emui-3-0-international-t2991646
Click to expand...
Click to collapse
You cannot use TWRP to flash neoarnet's rom. It is an update.app file, so you need to flash the stock recovery onto your device, and then create a dload folder in the root of your SD card, and place the update.app file into the dload folder.
Do a local update using the Updater application.
miz_pimp said:
You cannot use TWRP to flash neoarnet's rom. It is an update.app file, so you need to flash the stock recovery onto your device, and then create a dload folder in the root of your SD card, and place the update.app file into the dload folder.
Do a local update using the Updater application.
Click to expand...
Click to collapse
Okey, That was quite an useful Info.
But How do I go back to Stock recovery ?
Updater Application is within the stock recovery I guess.. ?
ozshire said:
Okey, That was quite an useful Info.
But How do I go back to Stock recovery ?
Updater Application is within the stock recovery I guess.. ?
Click to expand...
Click to collapse
No, the updater app is on your home screen.
It might be called System Update, or similar, if you're not on Emui 3.0.
How did you install TWRP? The process is the same, except you need the stock recovery. I can't give a detailed description now, but there are many guides explaining the process.
i got the same problem, my phone ran out of battery and then put it to charge and got stuck on the android logo, i cant install any rom, it was updated to kk with emui 3.0, i put the dload folder on the sd card root and when i try to open it it only appears ../, and if i put the boot.img on the sd card root it tries to install the os but tells me e: signature verification failed and stop installing
miz_pimp said:
No, the updater app is on your home screen.
It might be called System Update, or similar, if you're not on Emui 3.0.
How did you install TWRP? The process is the same, except you need the stock recovery. I can't give a detailed description now, but there are many guides explaining the process.
Click to expand...
Click to collapse
I think I missed to tell you that, it seems the phone got no OS now. Its not going further the Huawei Ascend Logo screen at Startup. Then how shall i run the updater ? I am confused.
Or are you telling me that I should install the STOCK RECOVERY just like I did TWRP ?
Wont it be easier if I find a TWRP compatible ROM ZIP (kk, emui 3.0 ) ?
ozshire said:
I think I missed to tell you that, it seems the phone got no OS now. Its not going further the Huawei Ascend Logo screen at Startup. Then how shall i run the updater ? I am confused.
Or are you telling me that I should install the STOCK RECOVERY just like I did TWRP ?
Wont it be easier if I find a TWRP compatible ROM ZIP (kk, emui 3.0 ) ?
Click to expand...
Click to collapse
Yep, you did. And yes, I meant that you can install the stock recovery the same way you installed TWRP (using fastboot commands).
I just assumed since you already had that firmware, that you'd want to update to that, but yes, it will be easier to just install a ROM that that you can flash through TWRP.
Let me know how it goes.
miz_pimp said:
Yep, you did. And yes, I meant that you can install the stock recovery the same way you installed TWRP (using fastboot commands).
I just assumed since you already had that firmware, that you'd want to update to that, but yes, it will be easier to just install a ROM that that you can flash through TWRP.
Let me know how it goes.
Click to expand...
Click to collapse
I flashed emui_3.0_b709_by_oxalis_p6-u06_v04.zip this time. ( it was b708 before in the phone)
Using TWRP and the rom zip file.
It was a success.
But now there is no network !!!!! No sim inserted !!!
What happened ???
I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
hotmatua.parulian said:
I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
Click to expand...
Click to collapse
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
ShadySquirrel said:
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
Click to expand...
Click to collapse
Thank you very much Shady.. Please be kindly to review steps that i should execute when flashing to Carbon Lollipop with regards to my current state (rooted 4.4.2. stock Kitkat):
Prerequisite:
- LG Flash Tool 2014 installed in PC
- LG United Mobile Driver (i use v3.11.3) installed in PC
- Stock firmware E98810e_00.kdz (Indonesia Jellybean) -- Jellybean stock base is required to cater modem/wakelock issue
- Stock firmware E98820c_00.kdz (Indonesia Kitkat)
- ROM Manager (for current state backup/restore)
- Freegee (to cater LG security issue after success flash)
- Towelroot (to root device after success flash)
- TWRP (for recovery tool after success flash)
- Downloaded ZeKrnl 1.7 Build 11/28 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975
- Downloaded ZeKrnl 1.6 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page4 (to cater camera issue after flashed to Carbon)
1. Flash CWM via ROM Manager
2 Execute Backup Current ROM to sd card via ROM Manager and save copy to PC
3. Backup manual for files, apks, contacts to sd card and save copy to PC
4. Copy ZeKrnl 1.7 zip & ZeKrnl 1.6 zip to sd card
5. Turn off phone, plug usb cable to phone
6. Press & hold Volume keys (Up + Down) then plug the other end of usb into PC to until download mode showned
7. Run LG Flash Tool with administrator privilege
8. Flash E98810e firmware into the device till success
(After Success Flash to Andro 4.1.2 JB):
9. Install towelroot and root the device
10. Install freegee to cater LG security issue
11. Install latest TWRP
12. Reboot into recovery mode
13. wipe system, data, cache, dalvik cache
14. flash ZeKrnl 1.7
--Camera issue
debug.composition. type=dyn --> debug.composition. type=gpu using build prop editor and/or flash ZeKrnl 1.6 kernell
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page8
--Deep Sleep issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page10
-- SD Card issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page12
-- Kernel parameter tuning sampel
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page14
Btw looks like you are the only person that still active in this thread...really appreciate it...thank you very much
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
So you are saying i just flash the rom as is without any further change?Noted shady...i will inform you the result
ShadySquirrel said:
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
Click to expand...
Click to collapse
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
hotmatua.parulian said:
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
Click to expand...
Click to collapse
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
ShadySquirrel said:
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
Click to expand...
Click to collapse
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
hotmatua.parulian said:
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
Click to expand...
Click to collapse
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
g0at1 said:
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
Click to expand...
Click to collapse
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Quiet interesting this device...salut to programmers of this device...
hotmatua.parulian said:
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Click to expand...
Click to collapse
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
hotmatua.parulian said:
Quiet interesting this device...salut to programmers of this device...
Click to expand...
Click to collapse
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
ShadySquirrel said:
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
Click to expand...
Click to collapse
:good::good::good::good: salut to you...the true programmer..never quit..yes im agree with you...i had played with nexus 1,2,3 before but never found something like this...
OK then, i will try g0at1 suggestion, hopefully it works... Like you said its only JB, root, freegee, newer twrp, backup, flash custom
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
hotmatua.parulian said:
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
Click to expand...
Click to collapse
You forgot to wipe system, data and caches.
ShadySquirrel said:
You forgot to wipe system, data and caches.
Click to expand...
Click to collapse
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
hotmatua.parulian said:
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
Click to expand...
Click to collapse
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
g0at1 said:
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
Click to expand...
Click to collapse
Finally carbon installed successfully after I repeat the step very carefully including your reminder bout wiping...
Thank you very much, I will consult any bugs I found..
Half Day 1 issue:
- Scrambled screen layout each time booting
- Camera unstable/crash, also with apps camera mx and open camera
- i think batt is draining faster than kitkat stock
- i feel internet via wifi is slower than kitkat stock
- phone call, other person cant hear my voice
Just flashed SlimLP..Gosh its so slim and smooth...thank you very much...there issue bout the camera and scrambled screen each time I reboot the system, which camera apps I should use?