Develop Bugs

[Q] Help Rooting 2.2.1 - I've tried that edition.

I, for the life of me, being a compute tech since the mid 90's, can't root this mytouch g3 slide. I have android 2.2.1 installed, I know I know, I hate it when people don't RTFM, I have tried the following:
(USB Deugging is on, charge mode only when plugged in, full android SDK kit installed and working. PDAnet drivers installed, I have superoneclick 1.9 computer see the phone fine, Goldcard works perfectly.)
1. I've tried Cyanogenmod's instructions (wiki.cyanogenmod.com/wiki/TMobile_myTouch_Slide:_Full_Update_Guide)
-Nothing happens after 2nd to last command line of step 8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. I have tried this "New way to downgrade from 2.2 to 2.1" (http://forum.xda-developers.com/showthread.php?t=1108316)
-4a. , It does not give me the option to "hit vol up to update"esrpimg" just flashes error no image found error messages:
3/ I have tried ULTRA EASY ROOTER (http://forum.xda-developers.com/showthread.php?t=999121)
same problem as #2's problem, just error messages.
4. And I have tried this: "How-To [Root][NewLinks] The myTouch 3GS if you updated to Offical 2.2.1 and lost root" (http://forum.xda-developers.com/showthread.php?t=1025336)
-Everything goes smooth until I type in this line "chmod 04755 *" which I get a bank carraige return, and I can type to my hearts content, nothing happens, can't exit, etc, have to CRTL + C to get out out of it. similar problem as #1's problem. I have tried again and again and again.
Help.

Make a goldcard and install the img from the bootloader.
Then try again.
sent from my MT3GS running CM7 nightly

thanks for the reply poormanq45. I did make a goldcard, maybe it doesn't like my MicroSD card? Which image do you want me to install from the bootloader? Which instructions should I be following?
Which set of instructions talk about having a swap partition as your 3rd partition on the SD card?
poormanq45 said:
Make a goldcard and install the img from the bootloader.
Then try again.
sent from my MT3GS running CM7 nightly
Click to expand...
Click to collapse

I don't remember which img I used. IIRC there are three different ones. Just try each one until one works.
It's possible that your MicroSD card isn't capable of being a goldcard. I had to try two different ones
sent from my MT3GS running CM7 nightly

My Stock 2.2.1 Process
My warranty replacement came with stock 2.2 and all of the tutorials here and elsewhere fell short. I did notice a lot of the other guides were based on "if you upgraded to 2.2"; that did not completely apply in my situation. I to am an industry professional with 14 years experience and am a stickler for detail. I had the gold card created on a SanDisk 2gb micro sd acquired from Walgreen's. I had followed all the steps in order, but the update on the first reboot never happened, it never asked and selecting the update.zip failed signature verification. I knew S-ON was set (which is the whole problem) but the guides I saw to disable it required you already be rooted (which I wasn't).
This past week I did something different. Using the official HTC MyTouch 3G Slide Froyo installer (not selecting anything just having RUU opened) I copied the folder structure (a crazy GUID looking thing) that was in my %TEMP% directory to another location. I closed out of the installer and went to that copied folder. I moved the existing "rom" file and copied the 2.1 "ESPRIMG" image there and renamed it to rom.zip. I then executed the RUU from that folder. It being an HTC official rom did allow the RUU to complete and the slide was officially downgraded to 2.1. After the reboot I verified the ROM was the older version and went ahead with what I was used to.
After that; some of my previous attempts to root were evident because I already had the "#" prompt in the adb shell. Regardless, I did repeat some of the documented steps (just in case my eyes deceived me) from the exploid method (what I used on my previous phone that was an original build). I originally flashed the CM 7.03 while the goldcard (2gb) sd was still in there. I then installed my 32GB card, then hit a nightly, then hit a few more older CM builds (had issues with sd-ext, couldn't find the original guide i used to set it up - new card as well). I did format boot, data, system, sd-ext, and the cache from the clockworkmod recovery screen before settling on CM 7.1 RC 1
If you find it necessary to create the sd-ext partition, format the fat partition in windows, format the other two in the shell. I do not recommend logging (app sync) on the first rom. Build the sd-ext first; re-rom, before doing all the account/app setup. While the phone is USB debugging mode you can use DriodExplorer to shortcut some things (especially if u have all your apks in a backup folder on your computer). I do not recommend using certain busy-box commands from the DriodExplorer terminal. The output can be out of sync at times. I have a 32gb SD and have about 29.3G on FAT, 896MB on SD-EXT (ext3 file system), and the rest on cache. After that Simple2Ext will allow for you to tell CM7 to use the SD-EXT. I do not use .android secure (the froyo apps2sd) because that causes issues when using the fat partition as disk in windows and you have something like a theme installed. Because of themes, games, and other apps I am now using 62% of the sd-ext partition. And an earlier comment I saw on the thread is right. The partition order is FAT, SD-EXT, CACHE. Where the guide is I don't recall.
Also note: If you are doing ADB commands and notice it often says the process is stale; uninstall the HTC sync (this does not affect the drivers, drivers are installed as a pre-req before HTC Sync is installed).
My only outstanding issue is the radio version might have been affected; it's not showing a version number on my info app. So I need to find a guide on verifying/upgrading the radio (one that does not involve installing the htc froyo rom).

Stuck... help.
First of all, sorry I can't past in links to the images, because I need a minimum of eight posts.
-----
Okay, I have made sure my phone has 25MB free. (it told me I needed this)
I have Turn USB Debugging on.
The phone is set to charge mode only.
The phone is plugged in and drivers installed. PDANet is not running.
I've tried it with a goldcard in it and out of it.
tagr.org/ScreenShot084.jpg
I Downloaded "T-Mobile_myTouch_3G_Slide_Software_Update_2.15.531.3.exe" from here the website, (I can't post the links)
I ran setup, and left it open while I went to the temp folder and copied it all out to another location.
I went to the NEW location and deleted "rom.zip" and replaced it with the 140 MB "ESPRIMG.zip" into that folder and renamed it rom.zip
In the new folder, I ran "ARUWizard.exe", agree, agree, okay, etc.
All goes okay, I get to this screen:
tagr.org/ScreenShot091.jpg
I say next, About two minutes into it, the phone reboots, put the HTC logo on it. Then on the computer, I get to this screen:
tagr.org/ScreenShot089.jpg
The phone is stuck on the "HTC" logo when the USB is plugged in. When USB is unplugged, the screen turns to this:
tagr.org/ScreenShot090.jpg
Stuck meaning, can't reboot, turn off, etc. So I have to pull the battery. When it turns on, all seems okay, it's still at 2.2.1 though.
Thoughts?

What the... why could I post pics my first post, but not my third...new policy?
eckre said:
First of all, sorry I can't past in links to the images, because I need a minimum of eight posts.
Click to expand...
Click to collapse

Okay I've figured it out and wrote up a NEW Guide: http://forum.xda-developers.com/showthread.php?t=1189485
No goldcard is needed, no console typing ADB shell etc. blah blah blah, so easy now.

[Q] Dinc corrupt primary file system *serious software help needed*

to start off with here is the problem list:
1) any rom, ruu, etc loaded will not boot past htc screen and if they do it boot loops 5 seconds into the animation.
2) clockwork reads error, E: /dev/block/xxxxxxxxxxx and cant mount data or cache partitions.
3) when doing a cat of mounts there are only five items instead of the 20 an unrooted stock phone possesses.
so in short i am asking for ideas maybe i have not tried "be creative here" to recover or reinstall "in my opinion the best fix" the whole main file system. just as if it was merely hardware blank from the factory. maybe push over new /dev, /system, /data, /cache etc etc as i believe the file system is corrupted and missing directories.
thanks for your time and thoughts...
*edit* i have been trouble shooting with the brilliant guys over at incredibleforum as well and thus whats lead me to my question here. so the back story, everything i've tried already, findings, and pictures are already posted here (not to violate TOS just for reference):
incredibleforum . com/forum/htc-incredible-rescue-squad/10812-boot-loop-after-exhausting-ever-possible-fix-my-head-experiance-help.html

Have you tried to ruu to stock froyo, and then do a factory reset thru hboot? Also when you say you ruu'd before did you do the PB31IMG.zip ruu or the ruu exe, or did you try both? Also have you at some point gotten the 5 vibes of death while booting?

i have done the ruu's both in hboot pb31img and via the exe while i booted into hboot. and i've never gotten nor heard of the five vibes. but exploring the file system there are directories missing for some reason. so i'm figuring the ruu's and roms aren't installing certain files due to not having a place to put them.

Sounds bad to me. I know they say if it turns on its not bricked, but if an ruu cant write to the partitions you will probably never be able to find a way to either. Hey im not an expert though by any means. Hope some one can help you figure it out.

the ruu cant write to the partitions because they don't seem to exist or the mounts for those directories. thats why i'm interested in finding a way to rewrite the partitions back to factory. there is a way because the phone wasn't built with this file system on it so there is a way to write /dev /system /cache /data etc.. maybe even a way to pull it off a stock phone and write to this one?? i can adb shell and view all of the files so i know its accessible. and hboot and recovery both work and can flash successfully. come on xda don't let me down i know there are some really brilliant and creative minds out there who think this is an easy fix to them.

tophkr said:
the ruu cant write to the partitions because they don't seem to exist or the mounts for those directories. thats why i'm interested in finding a way to rewrite the partitions back to factory. there is a way because the phone wasn't built with this file system on it so there is a way to write /dev /system /cache /data etc.. maybe even a way to pull it off a stock phone and write to this one?? i can adb shell and view all of the files so i know its accessible. and hboot and recovery both work and can flash successfully. come on xda don't let me down i know there are some really brilliant and creative minds out there who think this is an easy fix to them.
Click to expand...
Click to collapse
which hBOOT do you have? have you tried to reinstall the hBOOT?
http://pvillecomp.com/?page_id=4
after you reinstall hBOOT then try to ruu with the .exe

synisterwolf said:
which hBOOT do you have? have you tried to reinstall the hBOOT?
http://pvillecomp.com/?page_id=4
after you reinstall hBOOT then try to ruu with the .exe
Click to expand...
Click to collapse
+1 for reflashing hboot.
An ruu is ment to program the phone as if it were strait off the line never touched. It should create the file structure and partitions if they dont exist. What bothers me about your problem is that flashing roms or dooing ruu's compleet sucessfully without error. If the ruu cant write to these partitions it should stop and give an error, not just continue as if everything is ok. So to me it seems its writing to them fine but then for some reason cant read from them. Same for flashing a rom if it cant mount the partitions it should halt and give an error.

cmlusco said:
+1 for reflashing hboot.
An ruu is ment to program the phone as if it were strait off the line never touched. It should create the file structure and partitions if they dont exist. What bothers me about your problem is that flashing roms or dooing ruu's compleet sucessfully without error. If the ruu cant write to these partitions it should stop and give an error, not just continue as if everything is ok. So to me it seems its writing to them fine but then for some reason cant read from them. Same for flashing a rom if it cant mount the partitions it should halt and give an error.
Click to expand...
Click to collapse
well you have have a partition that has blocked write access so when RUU reads it, it works but when it try's to write it skips it.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i currently have .92 installed but i've gone back as far as .77 due to it being the development copy with full fastboot and adb capabilities. but i will try to reflash hboot .92 and then run ruu from computer while still in hboot.. worth a shot

You could try this. Sounds like your issue. Post 3.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20

tried that and i'm guessing the correct partitions are no longer there because i recieve this:
Error: /dev/block/mmcblk0: unrecognised disk label
and get that with every partition in the mmcblk catagory

ok so i have a question based on a possible cause to this problem.. if the prebious owner had flashed a droid incredible 2 rom insted of a DINC rom.. i know that can cause issues flashing the wrong roms.. how would you go about fixing that?

tophkr said:
ok so i have a question based on a possible cause to this problem.. if the prebious owner had flashed a droid incredible 2 rom insted of a DINC rom.. i know that can cause issues flashing the wrong roms.. how would you go about fixing that?
Click to expand...
Click to collapse
Did you try the link on the last page?
Sent from my sexy assistant. (AMOLED HTC Incredible)

synisterwolf said:
Did you try the link on the last page?
Sent from my sexy assistant. (AMOLED HTC Incredible)
Click to expand...
Click to collapse
the link to using parted to fix the partition format.. yes but those folders do not exist. when i show a list of my mounted partitions cache, data, system and a few others don't show up in the list at all. so because they don't exist anymore i don't know what partitions to remake or what folders need to go in them, which to mount etc.

So when you run the RUU's and PBIMG's they complete successfully without error?
also on a kind of related note, have you looked into booting a rom from your SD card or internal storage? Its not a fix or anything just merely might give you the satisfaction that your phone can boot a rom lol though it might not be by the traditional or standard means

nope i've never looked into how to boot a rom from internal storage. could you supply a link to instructions as this might be a temp fix while i continue to try and fix this.
and yes when i run them they compleate with no errors. only errors appear when looking in recovery.

tophkr said:
nope i've never looked into how to boot a rom from internal storage. could you supply a link to instructions as this might be a temp fix while i continue to try and fix this.
and yes when i run them they compleate with no errors. only errors appear when looking in recovery.
Click to expand...
Click to collapse
I would try a Google or XDA search because I've never tried it myself. Last I remember punk.kaos did it back when I had an Eris and I think more recently conap did it with the Incredible. Sorry I couldn't be of more help :/

i'm going to look into it but i've never heard of it being done except on the hd2 and hd7 using ram loading. but thanks for the ideas

My adventures with my ZenWatch over the weekend

I spent a lot of the weekend trying to root my Zenwatch (on 4.4.2w), or get a custom recovery working. Here's what I have tried and found out so far. They locked it down pretty damn well.
Unlocking bootloader and accessing recovery
Go to Settings -> About -> Press Build Number 7 times -> Swipe right, Developer Options now shows under About.
Theres a few different options including an Asus utility to check sensors and such.
To get into recovery or fastboot, you need to active ADB Debugging, unplug the watch than plug it back in, then run "adb reboot recovery" or "adb reboot fastboot"
To unlock bootloader, you need to push the reset button on the back to select.
In recovery, swipe right to left to show screen, up and down to select, and left to right to select.
My Findings so far
The kernel source and ROM source are not available anywhere.
There is no way that I can find to get root. I even went as far as loading towelroot onto the watch through adb install, but it just hangs and eventually closes.
There is no way I have found to build a custom recovery with CWM or TWRP.
There is no way I have found to dump the boot or recovery partitions.
There is no su binary preinstalled. Attempting to link a su binary has come up null.
dump_image binary is not installed, nor can you get it to install.
Trying to install any packages through stock recovery gives signature error.
Trying to use dd command to dump boot or recovery ends with "permission denied"
Trying to use "fastboot oem saveprt2sd recovery -n recovery.img -a" ends with "invalid page size". Same with trying to dump boot in this fashion.
Trying to boot either the LG G Watch or Samsung Gear Live unsecured boot images comes back with "(remote) dtb not found" (No surprise here, but it was worth a shot)
fstab is root only.
/dev tree is root only.
all init.asus scripts are root only.
You can install packages with "adb install" but all the standard root gaining apps stall or force close. Towelroot seems to try, but locks up after hitting "make it r4in." trying to change the modstring on v3 (with triple tap title) does not provide a field to change.
Kernel command line is root only.
I browsed EVERY file on my watch hoping to find a hole that I could build off of, but alas, I had failed.
Even trying to do "adb backup" results in "Confirm on Device," and closes immediately afterwards, with no confirm.
I believe that unless they release either the kernel source or the full ROM source, we are unable to root or modify any options.
Which really sucks, because the "OK Google" screen is REALLY F****** BRIGHT.
if anyone has success, please share

I thought I'd try installing one of my own apps and see what happened. It installs okay, but it crashes immediately. I'm guessing it's because I'm using something that's not supported, probably sound or Webkit (the app displays an HTML tutorial the first time it's run). I haven't had time yet to run it from the debugger and see what's going wrong.

I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/

dgjenkins said:
I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/
Click to expand...
Click to collapse
To build a custom recovery, you need to pull the existing recovery or boot partition off of the device and pull partition information (fstab, which is not readable by user on this device) and the build.config information (which is also not readable by user), or pull the fstab.anithias and build.config from the running system (which again is not accessible to the standard user account).
Without that information, you can't build a custom recovery. I've been attempt this for almost 2 weeks now, and its locked down pretty well. The G Watch and Gear Live allowed access to the needed files, but Asus did not with the ZenWatch.
If anyone is willing to risk bricking their watch (by getting past the dtb error when trying to boot the LG G Watch or Samsung Live recovery images, which is a long shot in itself) to get the openRecovery/CWM/TWRP to install and work to the point of getting ADB working through recovery mode, I can do the rest to build the recovery.
I just dont want to risk bricking mine quite yet, as the google play store was out of stock the last time I checked to purchase a "testing" watch.

@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip

CSX321 said:
@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip
Click to expand...
Click to collapse
Kernel source code
Sent from my SM-G900P

@z3nful And an ota? Would it be usefull?
OTA LWX48S

I haven't had a chance the last week to work on this with the holiday season going on and having to run my store. When I get a chance to get back to it, I'll let you guys know what I come up with

I started trying to build the kernel yesterday, but I'm not getting far yet. I've been a developer for over 30 years, but most of my Linux/other UNIX experience was over 10 years ago, and I've forgotten a lot.
I've tried a couple of different compiler versions, but I'm pretty quickly running into different issues with either one. I'm not sure what version Asus used, but it's apparently not either of the ones I've tried. Also not entirely sure what configuration to use. I'm using the 8226 configuration now, because there's no 8026 configuration in the source archive. I don't know if that's suitable or not.
All-in-all, I may not be out of my depth, but I'm out of my area of experience, at least. Any tips, @z3nful?
Edit...Is there any useful information in the OTA zip file? It's available. Partition info or a boot image or something?

@z3nful and @CSX321 - Any luck moving forward on this? I'm not a programmer, but I'd be glad to offer any assistance if needed!

btonetbone said:
Any luck moving forward on this?
Click to expand...
Click to collapse
No progress here, I'm afraid. I think I just don't know enough about this environment to do it, without devoting a lot more time to learning.
I've also lost some motivation, because there doesn't really seem to be anything I need root for on the watch. About the only thing I would do if I had it is delete a couple of apps, but since Mini Launcher lets me hide apps, I don't care so much about actually deleting them.

Has anyone had success with adb push? It seems the system is read only and doesn't allow for pushing files. Is root required?

Asus is good at locking down their devices, requiring you to register it with them to get an app to unlock it (you also acknowledge that by downloading the app you are voiding your warranty). I really wouldn't be surprised if they did the same thing with this watch and just haven't released the unlock app yet.
I am kinda disappointed to see this sort of thing from a device licensed by Google. It's like the exact opposite of the Nexus line.

@z3nful Just some helpful links, thought I could help a wear user out (I have the G Watch)
Kernel --> https://android.googlesource.com/kernel/msm/+/android-msm-anthias-3.10-lollipop-wear-release
Also, Gohma ROM for gwatch includes a boot img that auto roots android wear. (http://forum.xda-developers.com/g-watch/development/rom-gohma-2-0-12-15-2014-t2974052) Named rboot.img, I think it might be worth a shot to run "fastboot boot rboot.img" to see if it does anything.

Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.

I tried, no luck.. Gave the same "dtb not found" error.
Here is a thread related to DTB in boot images: XDA Topic 2428117
Attached is the rboot.img if anyone wants to see if they can modify it to pass whatever DTB issue is making it fail, if that's even possible. I will dig a little bit deeper once I get out of the office.
The error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rboot.img, zipped:
View attachment rboot.zip
Ignore my sig, it is several years out of date
Regards,
weasel5i2
Doc Ames said:
Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.
Click to expand...
Click to collapse

New Update Asia (1.62.707.4....) (And a lil help??)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got this update few hours ago....
though not able to flash it(After flashing stock recovery ie.)
any1 mind telling me how i can update?
Thnx in advance

system has been remounted r/w reflash device to re enable ota updates
this is the error i get
http://fotadl.htc.com/secure/OTA_HI...1.61.707.4_release_443364hpmfqulmgf0g5meu.zip
this is the url i got when i took a logcat during downloading the update... though i cant access it
and looking here: http://forum.xda-developers.com/showthread.php?t=1606676
if u take a look at ota urls it is similar eg- http://fotadl.htc.com/OTA_ENDEAVOR_....14.401.27_release_302022scz3ve3d2k8wy15p.zip
but the difference is i cant access the above url but this one works just fine
just curious. I'd really appreciate if some1 could answer

T3snake said:
system has been remounted r/w reflash device to re enable ota updates
this is the error i get
http://fotadl.htc.com/secure/OTA_HI...1.61.707.4_release_443364hpmfqulmgf0g5meu.zip
this is the url i got when i took a logcat during downloading the update... though i cant access it
and looking here: http://forum.xda-developers.com/showthread.php?t=1606676
if u take a look at ota urls it is similar eg- http://fotadl.htc.com/OTA_ENDEAVOR_....14.401.27_release_302022scz3ve3d2k8wy15p.zip
but the difference is i cant access the above url but this one works just fine
just curious. I'd really appreciate if some1 could answer
Click to expand...
Click to collapse
wow, that's some annoying thing. I'm not sure what goes on with this, seems like detects if the system partition was tampered with at some point?!
I guess it was with a restored backup of system partition without any modifications, but probably just the restoration process from a backup results in differences to an original System data partition. I have checked the Taiwan OTA zip (unfortunately I can't build a rom from that), and it contains a system diff block patch, which my guess is that takes unmodified system quite seriously, but I'm not familiar how HTC does this part these last years. I was always using custom ROMs when I unlocked my phone, so I have to admit, I'm not sure when HTC ota process is being blocked by the update binary..
All I can help with is to promise i'll update the CleanSlate when I get my hands on a system image with the new base and get some free time to mess with it...

tbalden said:
wow, that's some annoying thing. I'm not sure what goes on with this, seems like detects if the system partition was tampered with at some point?!
I guess it was with a restored backup of system partition without any modifications, but probably just the restoration process from a backup results in differences to an original System data partition. I have checked the Taiwan OTA zip (unfortunately I can't build a rom from that), and it contains a system diff block patch, which my guess is that takes unmodified system quite seriously, but I'm not familiar how HTC does this part these last years. I was always using custom ROMs when I unlocked my phone, so I have to admit, I'm not sure when HTC ota process is being blocked by the update binary..
All I can help with is to promise i'll update the CleanSlate when I get my hands on a system image with the new base and get some free time to mess with it...
Click to expand...
Click to collapse
Here is update-script on OTA.
Code:
# ---- start making changes here ----
([COLOR="Red"]range_sha1("system", "2,0,1") == "c3b8ad46808545e81168538a78b9af707acedceb") || (range_sha1("system", "2,0,1") == "b69f6ab8e68d0df61090527a1575eb052456f3b3") || abort("system has been remounted R/W; reflash device to reenable OTA updates");[/COLOR]
if range_sha1("system", "..." then
ui_print("Patching system image...");
show_progress(0.900000, 0);
block_image_update("system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
else
(range_sha1("system", ...
abort("system partition has unexpected contents");
endif;
It means it will check the SHA1 code for system partition before applying OTA.
If you initial issue the twrp in here,it will mount system as rw and destroy the SHA1.
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 [B][COLOR="Red"] rw [/COLOR][/B] wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,autoformat
Maybe someone could repack the m9+ recovery here with the new version twrp2.8.7.0,the issue should be resolved.

yvtc75 said:
Here is update-script on OTA.
It means it will check the SHA1 code for system partition before applying OTA.
If you initial issue the twrp in here,it will mount system as rw and destroy the SHA1.
Maybe someone could repack the m9+ recovery here with the new version twrp2.8.7.0,the issue should be resolved.
Click to expand...
Click to collapse
What if we remove that part of the code in updater script...
Btw did u get hands on the ota file its tiring to download it after every unsuccesful flash

T3snake said:
What if we remove that part of the code in updater script...
Btw did u get hands on the ota file its tiring to download it after every unsuccesful flash
Click to expand...
Click to collapse
No,you will reach the "system partition has unexpected contents"
Code:
else
(range_sha1("system", ...
abort("[COLOR="Red"]system partition has unexpected contents[/COLOR]")
The OTA file was laid on /data/data/com.htc.updater/files ,if you have rooted, copy it out to your SDCard.

yvtc75 said:
No,you will reach the "system partition has unexpected contents"
Code:
else
(range_sha1("system", ...
abort("[COLOR="Red"]system partition has unexpected contents[/COLOR]")
The OTA file was laid on /data/data/com.htc.updater/files ,if you have rooted, copy it out to your SDCard.
Click to expand...
Click to collapse
what if i replace abort command with print command?
Will there be an syntax error?
or i remove the part u mentioned too?
btw i unrooted thru supersu app yesterday.... still not updating
ill try to get ota file thru adb pull
EDIT: Adb pull gave 0files pulled 0 files skipped
EDIT2: I took a logcat while updating my device
W/htcCheckinService_CheckinRecoverySystem( 850): !!! REBOOTING TO INSTALL /data/data/com.htc.updater/files/OTA_HIAU_ML_TUHL_L50_SENSE70_MR_hTC_Asia_WWE_1.62.707.4-1.61.707.4_release_443364hpmfqulmgf0g5meu.zip
Click to expand...
Click to collapse
if it helps any1
now ill be rooting my phone again
thnx all for help

i removed all the abort commands and it broke my rom
cant mount system
(Flashed thru twrp)
Very bad idea

How to up date LeEco Le Pro3, no root, no TWRP, 100% Stock

I am a New Pro3 owner, and a old XDA flasher. These days I just want stability and battery life. So given no one is getting OTA updates because the LeEco US office are... well about to close doors? Or at a minimum they are not maintaining the OTA servers as of today (09/06/2017 MM/DD/YEAR). I took it on myself to figure out how to get the updates and how to do them.
What you need:
These three files, nothing else.
5.8.019_sta.zip
5.8.020_sta.zip
5.8.021_sta.zip
Found here.
https://drive.google.com/open?id=0B2EAg2WU3OwpSHRMdEZ0Tks0a3M
It is very simple, but also very finicky.
1. Download 5.8.019_sta.zip, rename to update.zip
2. Place the update.zip on the root directory of your phone storage
3. Go to Settings -> System update (about 3/4 the way down)
4. Top right corner will see three vertical dots, tap the dots and select "local update" (see image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. When you select "local update" if you did everything correct it should say "Update package found bla bla bla". Click continue.
That's it, it will load the file, reboot in to recovery and flash the file.
Then just follow this process for each file 19s->20s-21s. Make sure you remove the last update.zip before you put the new one in place.
Now, here is how it can be "finicky". For some reason using an android file manager to rename the files to "update.zip" corrupts the file in some way... and the update once you get in to the recovery section of the auto update fails. BEST PRACTICE IS TO DOWN LOAD THE FILES TO YOUR PC, THEN RENAME IT ON YOUR PC TO update.zip AND TRANSFER TO YOUR PHONES ROOT STORAGE.
Why? no clue, but you can try it either way... but if you find it failing try ^^

Hi, thanks for sharing the files, nuch appreciated.
For some reason I cannot acces the files today ?

bethe said:
Hi, thanks for sharing the files, nuch appreciated.
For some reason I cannot acces the files today ?
Click to expand...
Click to collapse
https://drive.google.com/drive/folders/0B2EAg2WU3OwpSHRMdEZ0Tks0a3M?usp=sharing
made a new sharable link

Hi and thanks for sharing. If you don't mind could you tell me
what's included in these updates?

dallorsj said:
Hi and thanks for sharing. If you don't mind could you tell me
what's included in these updates?
Click to expand...
Click to collapse
Just google "5.8.019_sta" (for each one)
You should be able to find the change-log somewhere.

Edward,
Works great! Just some notes for everyone else.
1) Make sure phone is set to MTP (Media Transfer Protocol).
2) If you are using Windows and are 'dragging and dropping' onto the device just copy to the phone icon in file explorer, that will put it at / which is where it needs to be.
3) When I did this and used the local update option, it didn't even prompt for 19S, it just moved forward and started the upgrade and rebooted the phone. All it asked me to confirm was right when I selected local update to 'make sure' I wanted to do it. No version check, etc. I was on 18S, btw.

Are you saying you went straight from 18s to 21s? Without the intermediary updates? Are you bootloader locked or unlocked?

Thanks for all of those OTAs. I was restoring my device to stock and every update kept failing when I tried to manually update it. Note: Update will fail if your OTA is not called update.zip.
IT IS CASE SENSITIVE; in other words, it will fail if you name is 'Update.zip'.
Thanks again and this post should be stickied tbh.

If my phone has twrp and on a custom rom could i use the same steps to go back to stock?
Sent from my LEX727 using XDA-Developers Legacy app

Ugh
I could not resist the $199 sale on Amazon despite knowing all the shortcomings. I am starting to regret this decision ... somewhat ... especially since Amazon no longer lets you return phones & can only exchange within 10 days.
Anyhow, I was excited when I got this phone the next day after I ordered it but my 1st frustration was that I could not do any system updates. I read about all the improvements like app drawer & really wanted them but no, it kept saying my system was up to date (still on 18 mind you). Which led me to this thread ... but now my computer will not recognize the Le Pro 3 when I connect it. I tried different USB ports & cords and no luck so far. I also cannot download the above links from my phone so I am kind of stuck @ the moment ...
I do, however, think that I got the work around for the notification issue as they seem to be coming in now, so that's good.
Overall, the phone mostly works so I am not totally mad at this purchase but getting the updates would be nice.
Quick Question: if I try to install Lineage OS, will the phone still have the T-Mobile wifi calling?
Thank you all for this super helpful forum for basic users like me.
UPDATE: Rebooting the phone got my computer to recognize the phone. However, I have followed all the instructions above (downloaded the file, renamed it update.zip, dragged & dropped it right on the phone in explorer, but it still will not find it with the local update.
I downloaded the Cheetah File Manger which shows you the Root Directory, which did not look like where I put mine. So I tried to move it over to the Root Directory but it would not let me paste it there. So close ...................................... calling it a night ...... sigh

i wanted to follow your guidelines but there is no system update in settings in my device. i ve bought it from banggood if that info is useful.

Could you please add check sums for these files.
Thanks in advance!

Try to update my X727 from 5.8.018s to 5.8.019s:
1. Renamed 5.8.019_sta.zip to update.zip and copied it to phone root.
2. From File Manager pressed on update.zip and choose "Upgrade", it has started updating "Upgrading, do not power off the phone".
3. The phone rebooted and entered to Recovery with an error message: "Failed to update! Cause: Installation failed"
4. Presses Back-button and tried again "Update system" and got an error message "Failed to update! Cause: APK not found"
What's wrong?