Some of Our Favorite Features in Android 5.0 Lollipop

Android 5.0 Lollipop is the latest major revision to Google’s mobile operating … more

Sony SmartEyeglass SDK Developer Preview Released

A little over a month ago in Tokyo, Japan, Sony unveiled its new SmartEyeglasstechnology. … more

XDA and Leaseweb: Server Trial/Moto 360 Contest (Winners!)

About a month ago, we held a contest along with XDA’s host, Leaseweb, to … more

Updated Android Lollipop Preview Images – XDA TV

The Android Lollipop Preview Images are now available! That and much more news is … more
Post Reply

Difference between klte and kltespr?

OP ethomas94

21st September 2014, 01:43 AM   |  #11  
OP Member
Florissant
Thanks Meter: 25
 
36 posts
Join Date:Joined: Feb 2011
More
Also, a lot of people were saying that the edited updater-script file would not stay saved and would just revert as soon as you left the editor no matter what. I've got around this by using Gedit (for linux or mac, I don't know about pc) and hitting "save as...", keeping the original name, then simply replacing the original file with the edited one.
21st September 2014, 08:18 PM   |  #12  
Member
Thanks Meter: 21
 
69 posts
Join Date:Joined: Jul 2010
It would be nice if one of these sharp guys would post them already altered.
21st September 2014, 09:41 PM   |  #13  
Senior Member
Flagstaff, az
Thanks Meter: 35
 
328 posts
Join Date:Joined: Feb 2011
Donate to Me
More
Quote:
Originally Posted by ethomas94

I fixed it.

What I was doing wrong was that after I extracted everything from the zip and edited the updater-script file, I would zip the extracted folder with all of the files in it, thus making a zip file, then a folder, then all of the files and stuff inside. That prevented the phone from flashing it, so it gave me the "error" message with no description (probably because it didn't know why it failed).

I was supposed to only zip the files that were in the extracted folder together into one zip, not the entire extracted folder with everything in it.

Im sorry but this is very hard to understand. I still cant get it flashed. Step by step this is what I did.
1.) Extract the zip file.
2.) Locate the updater script file.
3.) Edit script file so mount is the first word in the code.
4.) Save edited script file.
5.) Rezip the entire extracted file.

What am I doing wrong? It will not flash.
21st September 2014, 10:03 PM   |  #14  
OP Member
Florissant
Thanks Meter: 25
 
36 posts
Join Date:Joined: Feb 2011
More
Quote:
Originally Posted by mempho69

It would be nice if one of these sharp guys would post them already altered.

Quote:
Originally Posted by weinerwad3000

Im sorry but this is very hard to understand. I still cant get it flashed. Step by step this is what I did.
1.) Extract the zip file.
2.) Locate the updater script file.
3.) Edit script file so mount is the first word in the code.
4.) Save edited script file.
5.) Rezip the entire extracted file.

What am I doing wrong? It will not flash.

I'm only a new member (well, I was inactive for a long time) so I can't post large files.

Here's what you do.

1. Extract the zip file.
2. Navigate to the updater-script.
3. Edit it so that "mount" is the first thing it says (delete everything before that word).
4. Save it (or replace the file with the new one, which is how I got the save to stick)
5. ZIP ONLY THE FILES INSIDE THE MAIN FOLDER INTO ONE FILE. Don't zip the folder that came about after the extraction, only zip the files inside the folder (meta, img, etc) into one zip. If you zip the folder also, it will create a zip file, then the folder, then the contents. It will confuse the flash, that expects the contents to be directly after the zip layer, and not a zip, then a folder, then the contents; and the flash will fail without reason.
6. After the zip, it's ready.


If that did not work, then try only extracting the updater-script, then editing it, then putting it back in the zip (you may have to replace the original, do it)

The former is how it worked to me. Also, if you are using the 900P (Sprint Variant), get KT Recovery! It worked for me and now I can flash directly from cyanogenmod without editing the updater-script. There is a link in the KLTESPR general forum (It says Cyanogenmod is officially supporting us!). Simply flash it and it will replace the current recovery for your rooted phone as long as it already has a custom recovery. KT Recovery is a modded TWRP, just so you know. It works!

Also, it may not look like there is a folder after the zip if you zip the folder, but it won't flash if you zip the folder. That's why i say only zip the contents (meta, img, etc) into one zip!
Last edited by ethomas94; 21st September 2014 at 10:15 PM. Reason: Forgot words.
The Following User Says Thank You to ethomas94 For This Useful Post: [ View ]
21st September 2014, 10:06 PM   |  #15  
OP Member
Florissant
Thanks Meter: 25
 
36 posts
Join Date:Joined: Feb 2011
More
KT Recovery is a modded TWRP, just so you know. It works!
21st September 2014, 11:21 PM   |  #16  
Senior Member
Flagstaff, az
Thanks Meter: 35
 
328 posts
Join Date:Joined: Feb 2011
Donate to Me
More
Quote:
Originally Posted by ethomas94

I'm only a new member (well, I was inactive for a long time) so I can't post large files.

Here's what you do.

1. Extract the zip file.
2. Navigate to the updater-script.
3. Edit it so that "mount" is the first thing it says (delete everything before that word).
4. Save it (or replace the file with the new one, which is how I got the save to stick)
5. ZIP ONLY THE FILES INSIDE THE MAIN FOLDER INTO ONE FILE. Don't zip the folder that came about after the extraction, only zip the files inside the folder (meta, img, etc) into one zip. If you zip the folder also, it will create a zip file, then the folder, then the contents. It will confuse the flash, that expects the contents to be directly after the zip layer, and not a zip, then a folder, then the contents; and the flash will fail without reason.
6. After the zip, it's ready.


If that did not work, then try only extracting the updater-script, then editing it, then putting it back in the zip (you may have to replace the original, do it)

The former is how it worked to me. Also, if you are using the 900P (Sprint Variant), get KT Recovery! It worked for me and now I can flash directly from cyanogenmod without editing the updater-script. There is a link in the KLTESPR general forum (It says Cyanogenmod is officially supporting us!). Simply flash it and it will replace the current recovery for your rooted phone as long as it already has a custom recovery. KT Recovery is a modded TWRP, just so you know. It works!

Also, it may not look like there is a folder after the zip if you zip the folder, but it won't flash if you zip the folder. That's why i say only zip the contents (meta, img, etc) into one zip!

Thank you. I installed the recovery and the file worked. I tried downloading the recovery a few days ago but I got a 404 error from the link. I couldn't stand the stock os so you helped me out tremendously. Thanks again.
Last edited by weinerwad3000; 22nd September 2014 at 01:39 AM.
23rd September 2014, 07:46 AM   |  #17  
OP Member
Florissant
Thanks Meter: 25
 
36 posts
Join Date:Joined: Feb 2011
More
No problem!

Sent from my SM-G900P using XDA Free mobile app
4th October 2014, 10:07 PM   |  #18  
Senior Member
Marlboro NY
Thanks Meter: 208
 
819 posts
Join Date:Joined: Apr 2012
More
So, now I'm stuck. I was rooted, had plain old cwm installed and was able to flash the nightlies of CM11 to my lil hearts content. Then, for... reasons, I had to Odin back to stock and reroot, reflash recovery. Upon flashing Philz touch using Odin, and trying to flash 10/3 nightly, I start getting the error message I am seeing in this thread. First: I'd like to not have to do the fix shown in here. Is there a version of CWM that I can flash that will bypass all of this unpleasantness? Second, I tried, using Notepad++ to remove this line, ya know, the one that is supposedly the fix for all of this?. I highlight it, and nothing works to get rid of it. I hit cut, delete, kb shortcuts, you name it. Nothing works. So, either fix would be helpful, although my first choice would be just going back to the CWM that worked without all this added aggravation. Thanks in advance guys.
5th October 2014, 02:14 AM   |  #19  
Senior Member
St Louis
Thanks Meter: 212
 
337 posts
Join Date:Joined: Jan 2011
Donate to Me
More
Quote:
Originally Posted by AuGmENTor

So, now I'm stuck. I was rooted, had plain old cwm installed and was able to flash the nightlies of CM11 to my lil hearts content. Then, for... reasons, I had to Odin back to stock and reroot, reflash recovery. Upon flashing Philz touch using Odin, and trying to flash 10/3 nightly, I start getting the error message I am seeing in this thread. First: I'd like to not have to do the fix shown in here. Is there a version of CWM that I can flash that will bypass all of this unpleasantness? Second, I tried, using Notepad++ to remove this line, ya know, the one that is supposedly the fix for all of this?. I highlight it, and nothing works to get rid of it. I hit cut, delete, kb shortcuts, you name it. Nothing works. So, either fix would be helpful, although my first choice would be just going back to the CWM that worked without all this added aggravation. Thanks in advance guys.

May be a little late, but i put up a custom version of TWRP that will allow installing, and updating via their update section in settings. Its in the dev section of sprint gs5 here at xda. Will try to post a link if i remember.

http://forum.xda-developers.com/show...php?p=52260413
Last edited by miked63017; 5th October 2014 at 02:24 AM.
The Following User Says Thank You to miked63017 For This Useful Post: [ View ]
5th October 2014, 02:17 AM   |  #20  
Senior Member
Marlboro NY
Thanks Meter: 208
 
819 posts
Join Date:Joined: Apr 2012
More
Quote:
Originally Posted by miked63017

May be a little late, but i put up a custom version of TWRP that will allow installing, and updating via their update section in settings. Its in the dev section of sprint gs5 here at xda. Will try to post a link if i remember.

I flashed PacMan ROM, which for some reason worked. So for now I'm stable. But I will be looking to go back to my first true love.... Cyanogenmod!

Post Reply Subscribe to Thread
Previous Thread Next Thread