Related
First of all I just bought Global Moto G 2014 (XT1063) from US Amazon and that was KXH21.85-23 (not updatable to Lollipop via shared OTA.)
So I did manage to unlocked the bootloader and flashed KXH21.85-17 and tried to flash the "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US" which supposed to flash the Lollipop.
Unfortunately at first it failed to update me because "Printspooler.apk" mismatch the hash check. After attempt to flash (yes, I ignore the abort message and redo the process, It passed.... I don't know why) and stuck at some "xxx.apk" mismatch the hash again. After redo the process and bypass (for unknown reason that redo bypass the mismatch) I stuck at "velvet.apk" mismatch and this time It won't let me bypass and keep going on update to lollipop.
In my theory, Is it possible that I flash KXH21.85-17 from other country? Yes, any XT1063 (latin american, whereever on earth) supposed to flashable, but maybe the different country has slightly different apk. So that's why I failed the hash check.
Can anyone give me a URL or mirror to USA XT1063 for KXH21.85-17 that confirmed updatable to Lollipop? Since SBF-Dev and MotoFirmware is now down I couldn't find any.
I know what I'm saying is sound ridiculous, but I have no other theory that support my conspiracy anymore.
Hi @bankkung, I was facing similar problems. First you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!
Lamech242 said:
Hi @bankkungFirst you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
Click to expand...
Click to collapse
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
Lamech242 said:
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!
Click to expand...
Click to collapse
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?
bankkung said:
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?
Click to expand...
Click to collapse
Yes once you place the backup on your SD card, flash TWRP, reboot into recovery and go to advanced then go to file manager, then finish following the instructions above. Once you place it in the right place then you restore it. As of the stock recovery issue, it wouldn't make much sense to do that unless you followed the first option, where the stock recovery would actually be needed. But if you find a recovery image then yeah. If you do the second method you won't be able to receive updates nor update it manually unless doing the first method.. But the TWRP backup is the latest lollipop so enjoy!
If you still need help you can just flash TWRP recovery, and download this and flash it. http://forum.xda-developers.com/mot...-stock-rom-t2970427/post57438355#post57438355
Spice Dream Uno android 5.1.1 official OTA link captured!!!
LINK:-
https://android.googleapis.com/pack...-spice-mi498h-LMY47V-from-LMY47O.a818932c.zip
Instructions:-
Make sure u are on Stock 5.1 (LMY47O) & u have stock recovery
Place the ota zip in sdcard
Reboot to stock recovery
select apply update from sdcard
TA_DA!! U have android 5.1.1 running on your phone.
Credits:-
@mukeshpurohit
status 7 error
I am rooted and having stock recovery stock rom but while installing getting status 7 error.What to do?
There is an option in supersu to perform full unroot and then try again ( remember stock LMY47O recovery is required )
ujwal.p said:
There is an option in supersu to perform full unroot and then try again ( remember stock LMY47O recovery is required )
Click to expand...
Click to collapse
try that too but not working
The only thing I can imagine is that system files have been modified... Otherwise it should work..
Sent from my Mi-498 using XDA Forums
Error
Hey
My device is rooted but it is on stock ROM and stock recovery.
I downloaded the flashable zip and placed it on my ext sd card and flashed it using TWRP Recovery.
When flashing, it shows an error E: error excuting updater binary in zip <zip_file_location>
I tried this over three times and it still shows the same error.
Please Help!!
aditya_chachad said:
Hey
My device is rooted but it is on stock ROM and stock recovery.
I downloaded the flashable zip and placed it on my ext sd card and flashed it using TWRP Recovery.
When flashing, it shows an error E: error excuting updater binary in zip <zip_file_location>
I tried this over three times and it still shows the same error.
Please Help!!
Click to expand...
Click to collapse
Hmmm, try after full unroot, if that also doesnt work. There is one more method mentioned by people in the group. ie First flash the stock 5.1(LMY47O) ota and then on top of that flash 5.1.1 OTA, it will work.
How to successfully update to 5.1.1
Hey
Thanks for the suggestion :good: I managed to install 5.1.1 on my device.
My findings:
Before Lollipop, while updating from an OTA update, Google made android only check the system partition details to verify their OTA updates and that the installed version was the correct one.
However, with 5.0 Lolipop they introduced a new method of system checking. For each OTA update, the updater in recovery checked the file in the /system/bin/install-recovery.sh for its legit data. So any rooting or messing with the kernel or any part of the system made changes to it.
If any of the data is wrong or changed, the updater generates an error which most of us are getting. You won't even be able to manually flash the image as the system does not grant access to any recovery to patch the zip.
Even just installing SuperSU will change the data. A full unroot wont work as unrooting dosen't set back the default value for the files!! Only chance is if you have the stock image. without any messing around.
Sadly, I am not a professional developer and I don't know why Google did so?
The method that I used:
I flashed a stock image from another Spice Dream Uno device that my Dad has (that's silly) and restored the original system files.
And VOILA!, my OTA works just fine and I am on 5.1.1 now!
Edit: The updater checks every file in /system folder !! So if u even modify a stock apk, it will give an error.
Please Hit "Thanks" if this information was helpful!
aditya_chachad said:
Hey
Thanks for the suggestion :good: I managed to install 5.1.1 on my device.
My findings:
Before Lollipop, while updating from an OTA update, Google made android only check the system partition details to verify their OTA updates and that the installed version was the correct one.
However, with 5.0 Lolipop they introduced a new method of system checking. For each OTA update, the updater in recovery checked the file in the /system/bin/install-recovery.sh for its legit data. So any rooting or messing with the kernel or any part of the system made changes to it.
If any of the data is wrong or changed, the updater generates an error which most of us are getting. You won't even be able to manually flash the image as the system does not grant access to any recovery to patch the zip.
Even just installing SuperSU will change the data. A full unroot wont work as unrooting dosen't set back the default value for the files!! Only chance is if you have the stock image. without any messing around.
Sadly, I am not a professional developer and I don't know why Google did so?
The method that I used:
I flashed a stock image from another Spice Dream Uno device that my Dad has (that's silly) and restored the original system files.
And VOILA!, my OTA works just fine and I am on 5.1.1 now!
Edit: The updater checks every file in /system folder !! So if u even modify a stock apk, it will give an error.
Please Hit "Thanks" if this information was helpful!
Click to expand...
Click to collapse
Can you give the link for the system file I think I'm gonna try ur step...post the link ASAP.✌✌✌✌✌
& tell me how did you restore the system either using custom recovery or stock.
or
can you backup the current 5.1.1 system and post the Link...✌✌✌✌
SathishKies said:
Can you give the link for the system file I think I'm gonna try ur step...post the link ASAP.
& tell me how did you restore the system either using custom recovery or stock.
or
can you backup the current 5.1.1 system and post the Link...
Click to expand...
Click to collapse
As I mentioned, I had my stock recovery and system image backed up. I used custom recovery to restore my stock system.
For the safer side, I did do a full unroot from SuoerSU, which u can find it in the settings of SuperSU.
One thing I prefer is I never flash a recovery directly to my device.
Whenever I need custom recovery ( I use TWRP btw), I open it by using
Code:
fastboot boot TWRP.img
or whatever your file name is.
I then restored my backup from TWRP. In your case if you didn't backup your system before rooting then try flashing the stock system images from the links below.
After flashing the stock system, your OTA should work just fine.
There are many other threads where u can find the stock images.
Link for 5.1.1 flashable.
http://forum.xda-developers.com/crossdevice-dev/android-one-general/rom-t3120737
Link for Lollipop 5.1 stock image.
http://forum.xda-developers.com/cro...general/lmy47o-stock-rom-android-one-t3076777
If the stock images don't work for you then please tell me. I will backup my system and provide it.
I have yet another workaround way which is a bit complex. I'll post that too if this method didn't help you.
Hit Thanks if this helped you!!:good:
aditya_chachad said:
As I mentioned, I had my stock recovery and system image backed up. I used custom recovery to restore my stock system.
For the safer side, I did do a full unroot from SuoerSU, which u can find it in the settings of SuperSU.
One thing I prefer is I never flash a recovery directly to my device.
Whenever I need custom recovery ( I use TWRP btw), I open it by using
Code:
fastboot boot TWRP.img
or whatever your file name is.
I then restored my backup from TWRP. In your case if you didn't backup your system before rooting then try flashing the stock system images from the links below.
After flashing the stock system, your OTA should work just fine.
There are many other threads where u can find the stock images.
Link for 5.1.1 flashable.
http://forum.xda-developers.com/crossdevice-dev/android-one-general/rom-t3120737
Link for Lollipop 5.1 stock image.
http://forum.xda-developers.com/cro...general/lmy47o-stock-rom-android-one-t3076777
If the stock images don't work for you then please tell me. I will backup my system and provide it.
I have yet another workaround way which is a bit complex. I'll post that too if this method didn't help you.
Hit Thanks if this helped you!!:good:
Click to expand...
Click to collapse
Hey man I tried it but, seriously its going to bootloop. If you provide the system backup of current OS & if its not much of a trouble give it as a recovery restorable file the flashable zip is not workin out for me. I believe that ur posting the 5.1.1 backup plz post it... :fingers-crossed::fingers-crossed:
SathishKies said:
Hey man I tried it but, seriously its going to bootloop. If you provide the system backup of current OS & if its not much of a trouble give it as a recovery restorable file the flashable zip is not workin out for me. I believe that ur posting the 5.1.1 backup plz post it... :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Hey,
Sorry to hear that the previous method didn't work.
Your device is probably going into bootloop because of the remains of your previous system and the dalvik-cache. Try clearing that once.
I am providing you with both the system recoveries below.
Link for Lollipop 5.1 system backup:
https://goo.gl/NkAxwo
Link for Lollipop 5.1.1 system backup:
https://goo.gl/TL6EqU
Link for TWRP custom Recovery for Spice Dream Uno (sprout):
https://dl.twrp.me/sprout/twrp-2.8.6.0-sprout.img
These backups are directly from TWRP Recovery, so I don't know how you will use them.
You can't just copy these folders on your ext sd card and do a restore from TWRP as it won't recognize it as a system backup (as far as I know).
So basically, what I did was, I made a fool out of TWRP!!
You can follow these steps too.
First download the files from the required given links and place it in a new folder.
1. Start your device into TWRP cutom recovery.
2. Keep your device plugged in to a PC. Do not unplug your device until the whole restoration process completes!! And create a system backup of your device using TWRP. DO NOT use compression and DO NOT check md5. Do not reboot the device after the backup!!
3. After a successfull system backup, you will get a folder it your ext sd card mostly in ext_sdcard\TWRP\BACKUPS\Mi498HA14090161\<recovery_name>
4. Locate the folder on a PC and open it. There will be six files in the folder. Replace these files with the backup files that I provided you with in the download.
5. Now go to Restore option in TWRP and you will find the backup that you just created. The backup name will be the same but the system images will be changed as we just replaced the system and boot files.
6. Select the backup and restore.
Reboot your device after a successful backup and you should now have a fresh un-mod system.
You can directly use the 5.1.1 system image, but I suggest, you use the 5.1 system backup and update to 5.1.1 OTA.
And for the bootloop problem, I prefer backing-up the data of my device and do a complete system wipe. Wipe off the data, system partition and cache. This sholud set your device to a untouched state and hopefully there won't be any further problems.
Hit thanks if this helped you!! :good:
aditya_chachad said:
Hey,
Sorry to hear that the previous method didn't work.
Your device is probably going into bootloop because of the remains of your previous system and the dalvik-cache. Try clearing that once.
Click to expand...
Click to collapse
Everything worked as a dime if you backed up stock recovery that came with 5.1.1 post me tat took✌✌✌✌
SathishKies said:
Everything worked as a dime if you backed up stock recovery that came with 5.1.1 post me tat took
Click to expand...
Click to collapse
Feels good to help a fella!! :good: :good: :good:
How to update manually to Lollipop 5.1.1 for release key error and other errors
aditya_chachad said:
Hey
My device is rooted but it is on stock ROM and stock recovery.
I downloaded the flashable zip and placed it on my ext sd card and flashed it using TWRP Recovery.
When flashing, it shows an error E: error excuting updater binary in zip <zip_file_location>
I tried this over three times and it still shows the same error.
Please Help!!
Click to expand...
Click to collapse
Youtube Search for teckspotindia "Android One Release Key Error | Update Lollipop 5.1.1 Error | Micromax Canvas A1 | Dream UNO"
---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------
manojnagendra said:
I am rooted and having stock recovery stock rom but while installing getting status 7 error.What to do?
Click to expand...
Click to collapse
How to update manually to Lollipop 5.1.1 for release key error and other errors
Youtube Search for teckspotindia "Android One Release Key Error | Update Lollipop 5.1.1 Error | Micromax Canvas A1 | Dream UNO"
Hi All,
I see a lot of people asking for stock stuff for the HTC One Mini 2, please find them here:
Stock RUUs - https://forum.xda-developers.com/one-mini-2/general/htc-one-mini-2-official-ruu-t3425930
BOOT IMAGE
Signed Boot Image : boot_signed.img for booting problems (FOR INTERNATIONAL/EUROPEAN DEVICES ONLY)
PROCESS
Enter bootloader and then enter fastboot and type the command :
Code:
fastboot flash boot boot_signed.img
fastboot reboot bootloader
Nandroid Backup for restoring to stock, I have used this, working fine (Can be restored through TWRP): https://www.androidfilehost.com/?fid=24052804347818782 (FOR INTERNAITIONAL/EUROPEAN DEVICES ONLY)
Stock Firmware: https://www.androidfilehost.com/?fid=95784891001615234
Stock Recovery: https://www.androidfilehost.com/?fid=24052804347822267 (Newer)
Stock Recovery: https://www.androidfilehost.com/?fid=95784891001615233
Original Page (German): http://www.handy-faq.de/forum/htc-one-mini-2-firmwaresammlung-ruus-otas-backups-t309020/
LINKS WERE WORKING WHEN I POSTED THEM, DOWNLOAD AT THE EARLIEST AS MAY BE THEY WONT WORK WHEN YOU NEED THEM, SO JUST DOWNLOAD AND KEEP.
STEPS TO RESTORE NANDROID BACKUP THROUGH TWRP:
- REBOOT AND ENTER TWRP, PERFORM A BACKUP (THIS WILL CREATE A TWRP BACK UP FOLDER WITH DEVICE SERIAL NUMBER IN THE SD CARD)
- DOWNLOAD AND EXTRACT THE NANDROID BACK UP FILE
- PLACE THE EXTRACTED FILES IN TO THE TWRP>BACKUP<DEVICE SERIAL NUMBER> FOLDER IN THE SD CARD
- RESTART THE DEVICE AND ENTER TWRP, CHOOSE RESTORE
- LOCATE THE FOLDER COPIED IN THE ROOT OF THE SDCARD
- SWIPE TO RESTORE
- FOR SOME REASON THE NANDROID BACKUP DOES NOT CONTAIN CALCULATOR, FLASH LIGHT WHICH CAN BE DOWNLOADED HERE: http://www.apkmirror.com/apk/htc-corporation/
THANK YOU
I cant install
Bear Grylls said:
I cant install
Click to expand...
Click to collapse
What is the exact problem you are facing when flashing the stock file. PLEASE EXPLAIN FOR BETTER UNDERSTANDNG.
ELSE YOU CAN TRY THE BELOW.
NB: I AM ASSUMING THINGS AND GIVING THIS INFORMATION, I AM NOT RESPONSIBLE FOR WHAT HAPPENS AS I DONT KNOW THE EXACT PROBLEM YOU ARE FACING.
Make sure device is 100% battery.
1st try this:
1-Download this file: [ https://drive.google.com/file/d/0B_1zjuazXSqbQ0p6NWtvRk9OMzA/edit?pli=1 ] and install in Windows (Run as Administrator).
2-Open Command window and type:
Code:
cd c:\adb
3-now on your device use Vol keys to choose and power key to select, and choose FASTBOOT
4-now download the attached file boot_signed.rar (extract the file in C:\adb folder)
5-type in the command window:
Code:
fastboot flash boot boot_signed.img
5-type in the command window:
Code:
fastboot erase cache
6-type in command window:
Code:
fastboot reboot
IF THIS DID NOT WORK, THEN TRY THIS:
Download this [ https://www.androidfilehost.com/?fid=95916177934555508 ] file and rename it to 0P8BIMG.zip and place it into the SD card (MMC Card), restart the device and let it boot into the HBoot menu.
Reboot device from the boot mode, if the device automatically reboot into the boot menu then it will start flashing the file automatically.
Good Luck, let me know how it went.
Try and let me know.
this is excellent, all in one place...
However, please forgive my ignorance in recovery/backup terminology (I hope it is not just me) but I get confused by the use of 'Nandroid' backup, Stock Rom, and .zip and .img files for flashing.
I have successfully used TWRP to flash the NostromoPop ROM, but have not been successful with any other .zip file supposedly a Stock ROM.
I have been hoping that somebody could put a rooted Stock ROM so that I can try it as a way to get around the KitKat blocks on writing to the SD card for some of my autosync apps.
Am I making any sense?
Many thanks if you can help
soundrediscovery said:
this is excellent, all in one place...
However, please forgive my ignorance in recovery/backup terminology (I hope it is not just me) but I get confused by the use of 'Nandroid' backup, Stock Rom, and .zip and .img files for flashing.
I have successfully used TWRP to flash the NostromoPop ROM, but have not been successful with any other .zip file supposedly a Stock ROM.
I have been hoping that somebody could put a rooted Stock ROM so that I can try it as a way to get around the KitKat blocks on writing to the SD card for some of my autosync apps.
Am I making any sense?
Many thanks if you can help
Click to expand...
Click to collapse
Hi,
As I understand you cannot flash a stock ROM with customer Recovery, as far as I know you need stock Recovery to flash a stock ROM, I remember trying stock ROM on TWRP but it failed, could be due to some other reason, I read somewhere it has something to do with file signatures.
As for SD write fix, you need to have root access other than that there is no fix for it, rooting with SuperUser Binary... I myself did want to try it now that I am back on stock but then I am greedy for Marshmallow (if they could fix that Loud Speaker issue) I am all in for Android M, I tried to get in touch with people on the Cyanogen Forums but no luck as I have not yet received verification email, tried so many times, no luck and as it seems there is no Marshmallow development on HTC One Mini 2....
I will wait and see how it goes...
If I am correct you can keep stock ROM and flash SU Binary and get root access and then install https://play.google.com/store/apps/details?id=nextapp.sdfix to get it done with, it ought to work, haven't tried myself...
The recovery image you gave seems a little broken, but the backup worked...thought I recommend a factory reset unless you want the system language to be weird...
hanro50 said:
The recovery image you gave seems a little broken, but the backup worked...thought I recommend a factory reset unless you want the system language to be weird...
Click to expand...
Click to collapse
Which recovery image have you used, I have flashed the newer version successfully, yes the backup worked and has non-English language as default.
The command:
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache
If you could elaborate a "little broken"
I maneged to reflash twrp from android, ok these is what happened, I flash it as a recovery image with twrp, when I reboot into recovery later then it just showed a picture of my phone with a red triangle icon in it, after a while my phone resets...and goes back to booting from the main installed os...
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
The name of the file is M8_MINI_UL_Stock_Recovery_2.19.401.2.img
I don't remember if I taped New or old
hanro50 said:
I maneged to reflash twrp from android, ok these is what happened, I flash it as a recovery image with twrp, when I reboot into recovery later then it just showed a picture of my phone with a red triangle icon in it, after a while my phone resets...and goes back to booting from the main installed os...
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
The name of the file is M8_MINI_UL_Stock_Recovery_2.19.401.2.img
I don't remember if I taped New or old
Click to expand...
Click to collapse
Hi,
I believe you flashed a recovery with another recovery, which I think is not the right way, the right way is to use the command to overwrite TWRP with stock recovery.
hanro50 said:
I maneged to reflash twrp from android, ok these is what happened, I flash it as a recovery image with twrp, when I reboot into recovery later then it just showed a picture of my phone with a red triangle icon in it, after a while my phone resets...and goes back to booting from the main installed os...
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
The name of the file is M8_MINI_UL_Stock_Recovery_2.19.401.2.img
I don't remember if I taped New or old
Click to expand...
Click to collapse
HI,
Just wanted to know if you are having any issues with low audio after restoring Android backup from TWRP, I feel my audio is way too low and cant be heard just if I am outside my room..
I didn't have any audio problems, it could just be you being used to cm's 3rd party BoomSound replacement
---------- Post added at 01:25 PM ---------- Previous post was at 01:21 PM ----------
Well that would exsplain why some elements of the stock recovery remained after I reflashed twrp with a app on my phone, e.g. it fixed the image I get when I hook my device up to power when it is turned off...before that it would just boot me into a unusable twrp homepage
The stock RUU file is corrupt! (tried 5 times now)
Where can I get a A stock flash or a ROM that is NOT ROOTED please?
I tried the 0P8BIMG.zip on SD card method and that did not work either.
Also, I thought the RUU file is meant to be an executable not a zip file. I'm confused...
niblettr said:
The stock RUU file is corrupt! (tried 5 times now)
Where can I get a A stock flash or a ROM that is NOT ROOTED please?
I tried the 0P8BIMG.zip on SD card method and that did not work either.
Also, I thought the RUU file is meant to be an executable not a zip file. I'm confused...
Click to expand...
Click to collapse
I doubt its corrupted, which OS are you running currently ?, when I tried it, it failed due to the installed stock ROM being newer than the one being installed and since I have S-ON I cant downgrade it...
You can Nandroid Restore the stock backup, I have personally tried and it works....
Another way to do it is to have the Nandroid Restore and then use Sunshine to S-OFF (as sunshine only works on stock or near-stock ROMs) and then flash with 0P8BIMG.zip, it should work then, just a thought...
Hi, thanks for these links & info. Just about to give this a go. But, what does boot_signed.img do?
pavsid said:
Hi, thanks for these links & info. Just about to give this a go. But, what does boot_signed.img do?
Click to expand...
Click to collapse
Its a signed boot file, meaning it flashes successfully should the device fail to boot or stuck on boot or in other words if the device does not boot and remains on HTC, this flashing this should solve your problem.
Hi all I have been directed here from another thread as I am looking to place a stock rom on my htc one mini 2 without bloatware, I have unlocked the bootloader and installed TWRP but the stock rom remains the same all I want is to install a rom via TWRP if at all possible. Is the 1gig one ok for that or will i need to completely put the stock recovery back on and the phone is unlocked to all networks if that makes any different
Thank in advance
The Watergod said:
Hi all I have been directed here from another thread as I am looking to place a stock rom on my htc one mini 2 without bloatware, I have unlocked the bootloader and installed TWRP but the stock rom remains the same all I want is to install a rom via TWRP if at all possible. Is the 1gig one ok for that or will i need to completely put the stock recovery back on and the phone is unlocked to all networks if that makes any different
Thank in advance
Click to expand...
Click to collapse
Hi,
Its not possible to flash stock rom via TWRP, plus you need to have S-Off.
The only way to go complete stock is to restore Nandroid Backup and then flash stock recovery.
TryllZ said:
Hi,
Its not possible to flash stock rom via TWRP, plus you need to have S-Off.
The only way to go complete stock is to restore Nandroid Backup and then flash stock recovery.
Click to expand...
Click to collapse
so is this the nandroid back up of a stock rom that I can use with the latest update for use with twrp and when I mean stock rom I mean a rom that has not been majorly altered to class it as a custom rom. I.e still has sense and no additional apps added
Again Thanks in advance
The Watergod said:
so is this the nandroid back up of a stock rom that I can use with the latest update for use with twrp and when I mean stock rom I mean a rom that has not been majorly altered to class it as a custom rom. I.e still has sense and no additional apps added
Again Thanks in advance
Click to expand...
Click to collapse
Hi,
Yes you will have to restore the Nandroid Backup, this backup is completely of a stock ROM, no edition, however it does not have some apps like the Calculator, Flash etc for some reason.
However I found the missing apps from here: http://www.apkmirror.com/apk/htc-corporation/
TryllZ said:
Hi,
Yes you will have to restore the Nandroid Backup, this backup is completely of a stock ROM, no edition, however it does not have some apps like the Calculator, Flash etc for some reason.
However I found the missing apps from here: http://www.apkmirror.com/apk/htc-corporation/
Click to expand...
Click to collapse
Excellent much appreciated for this right, so I need to first copy the nandroid backup to my Phones root and run TWRP and restore using the downloaded nandroid yes?
if yes could I please have the steps to put the stock recovery on with ADB commands as I really don't want to brick my phone (Yes I know you take no resposibilty etc) just happier to have as least the correct file names and adb commands.
And last I just copy the new stock RUU to my phone and install?
You help is as always greatly appreciated as no one seems to be ddoing anything anymore for this phone
Hey folks,
after hours of reading around I have almost no idea left how to update my CM13 (13.0-20151213_nightly-titan) currently installed to a newer version. I tried with TWRP 2.8.6.0 and even 2.8.7.0, but it's all the same: I choose the zip file to install, the filesystem is detected correctly - but the installation just won't continue (usually the detection is followed by "patching the system unconditionally"). TWRP doesn't freeze, but just nothing happens . When I brake up after some time (usually an installation is done very quickly) with pressing the power button, my phone boots in the old version normally.
I tried another TWRP, wiped cache and dalvik, fixed permissions, set root in phone options, tried several CM13 builds... But I'm afraid of wiping data and system as it's a lot of work to get everything right again afterwards :crying:. Do you have any idea why TWRP doesn't want to install the new build?
Thanks a lot!
First always take a nandroid backup before you make any changes.
Even thought TWRP 2.8.7.0 is released, For Moto G 2014(titan)
only 2.8.6.0 is official https://dl.twrp.me/titan/
Try doing a clean installation(Wipe the data & System). That should do the trick.
just for the record the recovery is stopping you from installing a new build
Seems to be an issue with TWRP. You could give a try using CWM PhilZ Touch recovery. I have flashed using this recovery numerous times without any problem.
Thank you two for your replies !
Maddy, I know that 2.8.7.0 is unofficial for titan, but nevertheless it's working (for others). I want to avoid a complete reset, but in the end this could be a solution. But as I reflashed twrp (and tried another version also) I'm really wondering why twrp could be the problem ...
pank, I will take a look on CWM PhilZ, but until now I was really happy with twrp (and of course with its backup function). I hope it's possible to flash CWM using twrp and vice versa .
Unfortunately CWM PhilZ Touch Recovery shows the same behaviour than twrp - installation of new zip file just doesn't work (without any error) . If someone has an idea (except of a full wipe) please give me input !
Update the bootloader to the latest version. Had a similar problem a few months back that resulted in lots of hair tearing This solved it.
http://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007
Great hint - just checked your link already this morning and everything seemed to make sense... But I figured out that bootloader 4883 (newest version) was installed at my phone . Downgrade to 4882 should not be possible, and I'm also afraid of that .
I think I have something to do around Christmas - full wipe and a clean install! Damn...
Try installing this app called "CyanDelta" from playstore. What it does is it downloads the necessary files to upgrade from cm latest build (not the hole file) it's could be around 30 mb only. Totally legit!!... And it would dirty flash after download....
Do let us know how it turns out ?
I already tried CyanDelta, great tool! But as it's just creating a script for TWRP it has the same behavior . Oh, and I discovered that the nightly I'm using is no more available on cyanogenmod's official website ^^.
By now I think I've spend more time on searching for a solution than a full wipe including everything would need :laugh: ...
For me TWRP gives this behaviour only when Downloaded zip has some problem in it.
when it's not downloaded correctly it stuck at patching System
Have you tried latest zip?
also check SHA1 after download, doing that will confirm zip is downloaded correctly
Yes, I've tried the newest zip (several days respectively the newest) and I've checked the SHA value every time . The zip verification of twrp itself also doesn't report an error.
Maybe the reason is that I've used CM 12.1 before and made a "dirty" flash. Full wipe is getting closer to me...
No_Future said:
Yes, I've tried the newest zip (several days respectively the newest) and I've checked the SHA value every time . The zip verification of twrp itself also doesn't report an error.
Maybe the reason is that I've used CM 12.1 before and made a "dirty" flash. Full wipe is getting closer to me...
Click to expand...
Click to collapse
Just to say that I am having the same problem. Does the problem exist with Cyanogen Recovery? Can I replace TWRP with Cyanogen Recovery without touching everything else?
Thanks in advance.
mwalma said:
Just to say that I am having the same problem. Does the problem exist with Cyanogen Recovery? Can I replace TWRP with Cyanogen Recovery without touching everything else?
Thanks in advance.
Click to expand...
Click to collapse
Yes, you can try Cyanogen Recovery
download it and from fastboot
you can either just boot once and try it or flash the recovery replacing TWRP
Code:
fastboot boot recovery.img
Code:
fastboot flash recovery recovery.img
Great, I didn't know that it's possible just to boot once with a special recovery image. I'll try cyanogenmod recovery today !
Great news: With use of Cyanogenmod Recovery I was able to flash the newest build :victory:! I'm looking forward to try one day with TWRP, but for now I'm totally up to date . Thank you all again and have some nice days !
Edit: A full wipe and clean install solved this problem completely . Now the flashing with TWRP works again.
Hi There
Using this rom by Danvdh (6.0.1 MMB29K):
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
1) Is there a difference between the original one from Google to that rom?
2) OP mentioned that there is an updated recovery flashable releases of stock rooted Android.
It mean that it actually like an OTA updates?
3) What is the process if I want to move from rom such as the one mentioned here to a stock by Google and stay rooted?
Thanks!
1. Read the build information in the OP of the thread, it mentions all the differences.
2. It's the full stock FW but recovery flashable instead of fastboot and also rooted.
3. You would need to fastboot stock FW and manually root or flash the recovery flashable stock FW the was mentioned in question no. 2.
1) "100% untouched stock framework" Would actually be and act the same as a real stock from from(Factory Image) developers.google.com?
2) Meaning that when an update will be released I would able to flash it auto' from the recovery?
3) Can you please explain me?
- "fastboot stock FW" ?? Means download the Factory Image from developers.google.com , connect to usd and hit the " flash-all.bat"?
- "recovery flashable stock FW" ?? I know only about the Factory Image that flashed through fasboot...Where can i get the recovery version? (not from Google,right?)
Or I could just use this tutorial?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thanks!
duba500 said:
1) "100% untouched stock framework" Would actually be and act the same as a real stock from from(Factory Image) developers.google.com?
2) Meaning that when an update will be released I would able to flash it auto' from the recovery?
3) Can you please explain me?
- "fastboot stock FW" ?? Means download the Factory Image from developers.google.com , connect to usd and hit the " flash-all.bat"?
- "recovery flashable stock FW" ?? I know only about the Factory Image that flashed through fasboot...Where can i get the recovery version? (not from Google,right?)
Or I could just use this tutorial?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 Read this to get a better idea what to do.
duba500 said:
Hi There
Using this rom by Danvdh (6.0.1 MMB29K):
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
1) Is there a difference between the original one from Google to that rom?
2) OP mentioned that there is an updated recovery flashable releases of stock rooted Android.
It mean that it actually like an OTA updates?
3) What is the process if I want to move from rom such as the one mentioned here to a stock by Google and stay rooted?
Thanks!
Click to expand...
Click to collapse
1)Differences would be that SuperSu is installed, busybox is installed, encryption is disabled in the kernel, important gapps such as google play services and the play store are updated to their newest current version so when you install the rom google services immediately work without needing to wait for a background update, gapps that can be fully functional by just downloading them from google play store (google+, youtube, google drive, etc) were removed from /system likely to save space to make it easier to install mods such as guitardedhero's viper/dolby sound mod, vanilla android's gallery photos app was added in place of google photos app, the little android debugging notification is hidden, and the tethering check was disabled to allow for tethering without a tethering plan.
2) The updated recovery flashable line is referring to the fact that the dev updated the google apps in the rom.
3) If you wanted to go totally stock then you'd need to just flash the boot.img and system.img out of a factory image from google since the rom is very very close to stock a userdata wipe shouldn't be needed and a cache/dalvik wipe may or may not be but as always have a backup in TWRP. Then go into TWRP before booting and install the latest SuperSu (2.65 iirc right now) installing the newest SuperSu's can cause a bootloop or 2 (in the middle of booting the phone will go back to the Google logo and booting again, it will usually do this 1 or 2 times before properly booting). (if you boot to android before going to TWRP it will be replaced since you have an untouched /system after flashing the system.img). And if you allow TWRP to keep /system as read only (it'll popup when you first boot into TWRP asking if you want to do that) then the stock /system will replace TWRP with stock recovery and OTA's will work if you do a total unroot from within the SuperSU app.
Hi,
Regarding (1): Yes I know that.
I meant to the rom itself(not gaspps, supersu, busybox..).
(2) Really? that's all? I thought it kinda of ota to the rom.
(3) Really? that's all(2...)?
If i boot in into twrp => flash the boot.img and system.img from the factory image , I will have a totally stock rom?!
So 4sure just download the factory image and just extract the boot.img and system.img?
Would you mimd to aprove if i got this right?
-> Take the boot.img and system.img from the factory image
=> Boot into TWRP and FLASH the 2 img's *without rebooting at the end*
=> Wipe cache/dalvik.
=> Flash SuperSu 2.65 ***By flashing 2.65 I wont face the 1-2 bootloop's?***
=> Wipe cache/dalvik.
=> Boot into system.
Did I undersyood it right?
Thanks for your advice-tip of the SuperSu version!
P.S:
LG doesnt have a dev site such as Google's have with all the Factory Firmwares?
Can I trust site such as: lgg3root. com/lg-g3-stock-factory-firmware
???
duba500 said:
Hi,
Regarding (1): Yes I know that.
I meant to the rom itself(not gaspps, supersu, busybox..).
(2) Really? that's all? I thought it kinda of ota to the rom.
(3) Really? that's all(2...)?
If i boot in into twrp => flash the boot.img and system.img from the factory image , I will have a totally stock rom?!
So 4sure just download G3 LS990 32GB and extract the boot.img and system.img?
Would you mimd to aprove if i got this right?
-> Take the boot.img and system.img from the factory image
=> Boot into TWRP and FLASH the 2 img's *without rebooting at the end*
=> Wipe cache/dalvik.
=> Flash SuperSu 2.65 ***By flashing 2.65 I wont face the 1-2 bootloop's?***
=> Wipe cache/dalvik.
=> Boot into system.
Did I undersood it right?
Click to expand...
Click to collapse
You have got a fantastic tip in looking here: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Search for fastboot.