this is how i did it
1. did check for update
2. downloaded update
3, un-rooted with Voodoo OTA Root Keeper
4. installed update
5. when tablet had finished installing and had rebooted - ran Voodoo OTA Root Keeper and restored root
6. all data was kept - no need to reinstall apps or change any settings, desktop also had not changed had the same layout and wallpaper
now I am rooted and have Android 4.03
Raptor124 said:
this is how i did it
1. did check for update
2. downloaded update
3, un-rooted with Voodoo OTA Root Keeper
4. installed update
5. when tablet had finished installing and had rebooted - ran Voodoo OTA Root Keeper and restored root
6. all data was kept - no need to reinstall apps or change any settings, desktop also had not changed had the same layout and wallpaper
now I am rooted and have Android 4.03
Click to expand...
Click to collapse
Can you upload a system dump?
Code:
adb pull /system/
gnufabio said:
Can you upload a system dump?
Code:
adb pull /system/
Click to expand...
Click to collapse
Sure - will take a while as i only have .5mb upload speed
Also worked for me, same exact way I did it.
Raptor124 said:
Sure - will take a while as i only have .5mb upload speed
Click to expand...
Click to collapse
Thanks
Raptor124 said:
Sure - will take a while as i only have .5mb upload speed
Click to expand...
Click to collapse
Instead of pulling, tar it up:
Code:
tar cvfj /sdcard/dump.tar.bz2 /system/
It will save all the permissions and files, and prepare special files (like, symlinks) in a readable format.
Also it will be way smaller!
Raptor124 said:
this is how i did it
1. did check for update
2. downloaded update
3, un-rooted with Voodoo OTA Root Keeper
4. installed update
5. when tablet had finished installing and had rebooted - ran Voodoo OTA Root Keeper and restored root
6. all data was kept - no need to reinstall apps or change any settings, desktop also had not changed had the same layout and wallpaper
now I am rooted and have Android 4.03
Click to expand...
Click to collapse
What tablet version do you have? WW or US?
Turge said:
What tablet version do you have? WW or US?
Click to expand...
Click to collapse
I have The US Version
fonix232 said:
Instead of pulling, tar it up:
Code:
tar cvfj /sdcard/dump.tar.bz2 /system/
It will save all the permissions and files, and prepare special files (like, symlinks) in a readable format.
Also it will be way smaller!
Click to expand...
Click to collapse
where can i get tar - i am getting device not found when i use adb pull
Raptor124 said:
where can i get tar
Click to expand...
Click to collapse
Oh, you got me wrong. Issue that command in adb shell, on the phone itself!
Tar should be built-in within busybox, or if it isn't there, make an ext4 dump:
Code:
mount (this will list the mounted partitions, look for the one what's with /system!)
dd if=/dev/block/mmcblk0p[whatever partition was numbered as /system] of=/sdcard/system.img bs=4096
This one (ran in ADB shell too) will produce an Ext4 image of the system partition, like if you pulled it from nvFlash (or a full blob).
fonix232 said:
Oh, you got me wrong. Issue that command in adb shell, on the phone itself!
Tar should be built-in within busybox, or if it isn't there, make an ext4 dump:
Code:
mount (this will list the mounted partitions, look for the one what's with /system!)
dd if=/dev/block/mmcblk0p[whatever partition was numbered as /system] of=/sdcard/system.img bs=4096
This one (ran in ADB shell too) will produce an Ext4 image of the system partition, like if you pulled it from nvFlash (or a full blob).
Click to expand...
Click to collapse
in progress - using tar - had to install busybox
tried the mount method, could not get it to work either
Raptor124 said:
this is how i did it
1. did check for update
2. downloaded update
3, un-rooted with Voodoo OTA Root Keeper
4. installed update
5. when tablet had finished installing and had rebooted - ran Voodoo OTA Root Keeper and restored root
6. all data was kept - no need to reinstall apps or change any settings, desktop also had not changed had the same layout and wallpaper
now I am rooted and have Android 4.03
Click to expand...
Click to collapse
I followed the same methodology except for #3 where I clicked on Back Up Root in Voodoo OTA Root Keeper. Everything went really smooth including the Camera update. All of my data was intact and I didn't have to reinstall any apps or change any settings. Excited to be rooted and have ICS!
mwbarb said:
I followed the same methodology except for #3 where I clicked on Back Up Root in Voodoo OTA Root Keeper. Everything went really smooth including the Camera update. All of my data was intact and I didn't have to reinstall any apps or change any settings. Excited to be rooted and have ICS!
Click to expand...
Click to collapse
for no 3 i had already had backup up the root after i rooted when i was on .33
Raptor124 said:
in progress - using tar - had to install busybox
tried the mount method, could not get it to work either
Click to expand...
Click to collapse
uploading - will post link when upload is complete - have to go out for a while
Raptor124 said:
uploading - will post link when upload is complete - have to go out for a while
Click to expand...
Click to collapse
link for system dump
http://dl.dropbox.com/u/8589057/dump.tar
Raptor124 said:
link for system dump
http://dl.dropbox.com/u/8589057/dump.tar
Click to expand...
Click to collapse
Thanks!
One question: did you add any Samsung stuff to it? There appears to be some apps added from the Samsung Galaxy Tab builds!
fonix232 said:
Thanks!
One question: did you add any Samsung stuff to it? There appears to be some apps added from the Samsung Galaxy Tab builds!
Click to expand...
Click to collapse
sorry i ment to mention that - yes there is - ignore it, i was trrying to get them to work on the prime but they won't
had the dump done before i could delete them
I see. Could you please tell me what did you exactly add to the ROM? Every file what was going under /system, please! So we can have a clean system
fonix232 said:
I see. Could you please tell me what did you exactly add to the ROM? Every file what was going under /system, please! So we can have a clean system
Click to expand...
Click to collapse
dlna.apk
dlna.odex
divx.apk
divx.odex
fmradio.apk
fmradio.odex
jobmanager.apk
jobmanager.odex
com.sec.android.app.controlpanel.apk
memo.apk
memo.odex
minidiary.apk
minidiary.odex
SamsungApps.apk
SamsungAppsUNA3.apk
signin.apk
signin.odex
Swype.apk
Swype.odex
VoiceSearch.apk
VoiceSearch.odex
VoiceToGo.apk
VoiceToGo.odex
I wanted to extract some files from here, but when I expand the .tar file, I'm just left with a 474MB "dump" file with no extension, etc... how can I see the contents of that file?
And this dump was from the 9.4.2.7-20120106 US build, correct?
Related
I uninstalled the Protips.apk without doing a backup first and now need to restore it so the OTA update completes. I have the file from another Photon but how do I go about getting it installed? I moved it to /system/app/ with Root Explorer but it won't install.
Do I need to push it with adb? If it somehow needs to be re-signed I'm not sure how to sign w/system signatures.
What steps can I use to complete this?
Thanks.
download the cm5 from yays thread in the dev section and then using 7zip (providing you are using windows) take everything out except protips app and flash it through recovery
If it will flash via recovery and work then would there be a reason why I can't push it via adb? The file that was sent to me should still have the original signature attached correct?
I was trying to avoid unlocking the bootloader and having to install custom recovery.
CCallahan said:
If it will flash via recovery and work then would there be a reason why I can't push it via adb? The file that was sent to me should still have the original signature attached correct?
I was trying to avoid unlocking the bootloader and having to install custom recovery.
Click to expand...
Click to collapse
I THINK that you can flash the via bootstrap recovery. If not try pushing with adb and before you reboot typing
Code:
sync
reboot
[email protected] said:
I THINK that you can flash the via bootstrap recovery. If not try pushing with adb and before you reboot typing
Code:
sync
reboot
Click to expand...
Click to collapse
I pushed it but not sure about the sync command. Do I need to use "adb sync /system/app/"? It is asking me for a directory but don't know what I am supposed to be syncing.
**EDIT...NM. I need to know the exact syntax for the adb sync command I need to use. Nothing is working. Also, I do not have permission to run the remount command. Does this mean the system may still be read only?
Thanks.
CCallahan said:
I pushed it but not sure about the sync command. Do I need to use "adb sync /system/app/"? It is asking me for a directory but don't know what I am supposed to be syncing.
**EDIT...NM. I need to know the exact syntax for the adb sync command I need to use. Nothing is working. Also, I do not have permission to run the remount command. Does this mean the system may still be read only?
Thanks.
Click to expand...
Click to collapse
Okay try this.
1st put the protips.apk on your sd card then
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /sdcard/protips.apk /system/app
sync
reboot
this should work
You know do don't actually install the apk. Just drop it in the system/app folder in reboot.
Perhaps I misunderstood your problem.
ptfdmedic said:
You know do don't actually install the apk. Just drop it in the system/app folder in reboot.
Perhaps I misunderstood your problem.
Click to expand...
Click to collapse
Yes. However it seems the Protips.apk I have might not be signed properly because it never installs upon reboot. So I was trying to find a way to make this work.
ptfdmedic said:
You know do don't actually install the apk. Just drop it in the system/app folder in reboot.
Perhaps I misunderstood your problem.
Click to expand...
Click to collapse
won't work because we don't have remount available now.
CCallahan said:
Yes. However it seems the Protips.apk I have might not be signed properly because it never installs upon reboot. So I was trying to find a way to make this work.
Click to expand...
Click to collapse
Did you try what i had suggested above (cp from sdcard mount file system sync reboot)???
[email protected] said:
won't work because we don't have remount available now.
Did you try what i had suggested above (cp from sdcard mount file system sync reboot)???
Click to expand...
Click to collapse
Not yet...had to make some dinner. Going to try it here in a sec.
Thanks.
[email protected] said:
Did you try what i had suggested above (cp from sdcard mount file system sync reboot)???
Click to expand...
Click to collapse
Tried it. All commands went through without issue. After reboot I tried doing the update but when it scans for existing files it still stops at 30%. It is still either not finding Protips.apk or there is something wrong with the file I have. A friend of mine emailed to me in an attachment. Don't know of any other way to get it without knowing how to properly extract an sbf file. Maybe if someone has a TB backup of it and could send to me? Then I could try restoring it. Not sure if something like that would be worth a try.
CCallahan said:
Tried it. All commands went through without issue. After reboot I tried doing the update but when it scans for existing files it still stops at 30%. It is still either not finding Protips.apk or there is something wrong with the file I have. A friend of mine emailed to me in an attachment. Don't know of any other way to get it without knowing how to properly extract an sbf file. Maybe if someone has a TB backup of it and could send to me? Then I could try restoring it. Not sure if something like that would be worth a try.
Click to expand...
Click to collapse
protips is the only thing that you don't have?
I am not sure. this thread has the ota as an sbf. I saw in another thread you were worried about having to reactivate again. The phone will program over the air you won't have an issue at all. I wish I could help you get protips installed correctly but I am still finding my way around moto. I guess that the mount command we used could be wrong. Not sure :/
[email protected] said:
protips is the only thing that you don't have?
I am not sure. this thread has the ota as an sbf. I saw in another thread you were worried about having to reactivate again. The phone will program over the air you won't have an issue at all. I wish I could help you get protips installed correctly but I am still finding my way around moto. I guess that the mount command we used could be wrong. Not sure :/
Click to expand...
Click to collapse
Yes. I deleted Protips.apk after rooting and didn't make a backup. The update errors every time because of that file not being installed it seems. Do you think that leaked OTA would restore the missing apk?
CCallahan said:
Yes. I deleted Protips.apk after rooting and didn't make a backup. The update errors every time because of that file not being installed it seems. Do you think that leaked OTA would restore the missing apk?
Click to expand...
Click to collapse
This leak is the same as the OTA. The only difference between installing this and downloading the OTA is having to reset everything up.
[email protected] said:
This leak is the same as the OTA. The only difference between installing this and downloading the OTA is having to reset everything up.
Click to expand...
Click to collapse
I'm gonna go ahead and try to figure out how to do the leaked one. I pulled the Protips.apk from Juggs file and still doesn't work. Weird that I can't go to it in Root Explorer and just install it.
Anyways, phone has been factory reset anyways so I'm not worried about having to set it all back up.
Thanks for your help.
Did you set the proper permissions for it?
CCallahan said:
Tried it. All commands went through without issue. After reboot I tried doing the update but when it scans for existing files it still stops at 30%. It is still either not finding Protips.apk or there is something wrong with the file I have. A friend of mine emailed to me in an attachment. Don't know of any other way to get it without knowing how to properly extract an sbf file. Maybe if someone has a TB backup of it and could send to me? Then I could try restoring it. Not sure if something like that would be worth a try.
Click to expand...
Click to collapse
Beach_Head said:
Did you set the proper permissions for it?
Click to expand...
Click to collapse
Yes. Still wouldn't work. Only thing I didn't try is modifying the update.zip and flashing just to restore the missing apk.
Did you also return the Protips.odex file?
That's the only other reason why the update wouldn't work...
CCallahan said:
Yes. Still wouldn't work. Only thing I didn't try is modifying the update.zip and flashing just to restore the missing apk.
Click to expand...
Click to collapse
Beach_Head said:
Did you also return the Protips.odex file?
That's the only other reason why the update wouldn't work...
Click to expand...
Click to collapse
I can't believe I didn't think of that
Sent from my MB855 using xda premium
No...I didn't.
Oh well. Too late now.
Thanks for the tip.
[GUIDE-IMPORTANT!] "rescue-backdoor" - regarding bootloop, do it before change in sys
UPDATE: THIS IS OBSOLETE.
USE S.onyTablet.S [ALLinONE] tool
Below guide/tool use as 'description'
-------------------------------------------------------------------------
Hi guys,
We've got now ROOT. We can do a lot of things, which we couldn't do before.
But before you begin to make changes in system files, first you need to know few things.
Few users experienced "bootloop". Its brick state. There is no access to shell, no adb.
Damaged device.
How to avoid that?
Yes, there is a solution. We need to get proper update zip for our device.
We also need to fool device, that it is a newer file, than the firmware in device.
How to, step by step:
Of course, ROOT is required.
To get proper ota-update-zip for your device you have to edit /build.prop:
- easiest way is via "Root Explorer", or directly via "build.prop Editor" (in market, free),
- do not use "File Manager HD" or other filemanager, which doesn't support root operations (thx kryddan),
- always make backup of files, which you are modifying,
- change value of "ro.sony.build.incremental" to lower one to fake firmware version,
- for example on my device newest firmware has: "ro.sony.build.incremental=111201022" - decrease that value,
in my case to 111201021.
Reboot device.
OTA update notification will appear - click on "Download" button.
Wait until download finishes, but don't click "Update"!!!
I repeat - DON'T CLICK UPDATE! It will reflash firmware,
and you will have to make everything from the beginning (inc. root).
Update zip is located in /cache/ota/signed-nbx03_.......zip - make a copy to safe place - external sd and/or in pc.
Leave build.prop modified. IMPORTANT. Don't revert back changes.
To enter RECOVERY-MODE - power off device,
hold vol-down + power button.
When you want to flash your device, Sony Tablet is checking few things:
is update zip proper one - signed one,
is the update zip - for your region - SKU value,
is the update zip is newer one than firmware in device - equal and higher will not update,
only lower - thats what we're faking.
If you will revert back build.prop = update will fail,
if you will try to update with other region update zip = update fail.
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
Remember, that after reflash in recovery, your build.prop will be updated back
to higher value, then to be safe you need to reapply modification!
I have tested that "rescue-backdoor" on my own device,
deleted some system framework file - of course bootloop, without adb access.
Flashed through recovery - voila, device fixed
Of course, everything what you do with your device, you are doing at your own
risk. I'm sure that in 99% cases with "rescue-backdoor" you will fix your device,
always could be that other 0,01% case.
One condition for sure = build.prop file has to be correct.
[OPTIONAL]
You can disable ota update notification - which appears on every reboot.
To do this use "Titanium Backup" app, look for "System Update" app on list,
and use "Freeze" option
Any questions, suggestions - just ask
PS. I'm thining about writing auto-script for that...
br
condi
great guide, thank you
I think an automated-script would be much appreciated
condi said:
Hi guys,
We've got now ROOT. We can do a lot of things, which we couldn't do before.
But before you begin to make changes in system files, first you need to know few things.
Few users experienced "bootloop". Its brick state. There is no access to shell, no adb.
Damaged device.
How to avoid that?
Yes, there is a solution. We need to get proper update zip for our device.
We also need to fool device, that it is a newer file, than the firmware in device.
How to, step by step:
Of course, ROOT is required.
To get proper ota-update-zip for your device you have to edit /build.prop:
- easiest way is via "Root Explorer", or directly via "build.prop Editor" (in market, free),
- always make backup of files, which you are modifying,
- change value of "ro.sony.build.incremental" to lower one to fake firmware version,
- for example on my device newest firmware has: "ro.sony.build.incremental=111201022" - decrease that value,
in my case to 111201021.
Reboot device.
OTA update notification will appear - click on "Download" button.
Wait until download finishes, but don't click "Update"!!!
I repeat - DON'T CLICK UPDATE! It will reflash firmware,
and you will have to make everything from the beginning (inc. root).
Update zip is located in /cache/ota/signed-nbx03_.......zip - make a copy to safe place - external sd and/or in pc.
Leave build.prop modified. IMPORTANT. Don't revert back changes.
When you want to flash your device, Sony Tablet is checking few things:
is update zip proper one - signed one,
is the update zip - for your region - SKU value,
is the update zip is newer one than firmware in device - equal and higher will not update,
only lower - thats what we're faking.
If you will revert back build.prop = update will fail,
if you will try to update with other region update zip = update fail.
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
I have tested that "rescue-backdoor" on my own device,
deleted some system framework file - of course bootloop, without adb access.
Flashed through recovery - voila, device fixed
Of course, everything what you do with your device, you are doing at your own
risk. I'm sure that in 99% cases with "rescue-backdoor" you will fix your device,
always could be that other 0,01% case.
One condition for sure = build.prop file has to be correct.
[OPTIONAL]
You can disable ota update notification - which appears on every reboot.
To do this use "Titanium Backup" app, look for "System Update" app on list,
and use "Freeze" option
Any questions, suggestions - just ask
PS. I'm thining about writing auto-script for that...
br
condi
Click to expand...
Click to collapse
Thanks Condi! Download worked great but under my cache there is nothing. Could the file be located elsewhere?
It should be under '/cache/ota' ... nowhere else ..
Judah001 said:
Thanks Condi! Download worked great but under my cache there is nothing. Could the file be located elsewhere?
Click to expand...
Click to collapse
Be sure that ota has been download, check again /cache/ota.
If still no zip, then run 'adb shell' then:
Code:
su
find -name *signed*
or
Code:
find -name *.zip
If your ota update will be in different location, then please post it.
br
condi
condi said:
Be sure that ota has been download, check again /cache/ota.
If still no zip, then run 'adb shell' then:
Code:
su
find -name *signed*
or
Code:
find -name *.zip
If your ota update will be in different location, then please post it.
br
condi
Click to expand...
Click to collapse
ok I will try once I am home through adb. So far there is nothing under my cache folder. I am using file manager HD but it should pick up a zip file.
Thank you condi... The instructions worked perfectly!!
Judah001 said:
ok I will try once I am home through adb. So far there is nothing under my cache folder. I am using file manager HD but it should pick up a zip file.
Click to expand...
Click to collapse
Just a little tip. I'd suggest you use Root Explorer instead of File Manager HD.
You see, File Manager HD does not show the files in /cache. (mine didn't)
I tried File Manager HD on my tablet and found nothing inside /cache
But with Root Explorer I found three different directories. There among OTA.
kryddan said:
Just a little tip. I'd suggest you use Root Explorer instead of File Manager HD.
You see, File Manager HD does not show the files in /cache. (mine didn't)
I tried File Manager HD on my tablet and found nothing inside /cache
But with Root Explorer I found three different directories. There among OTA.
Click to expand...
Click to collapse
That did the trick. I used the root browser in rom tool box and copied the zip to my sd card. Thank you for the help guys.
Good advice kyddan ... same on my tab with file manager HD.
I work normally with Root Explorer or File Expert.
Both show the folders and files in /cache .. File Manager HD do not.
my ro.sony.build.incremental is 111201038
Do I have to decrease it by 1 to 111201037 ?
EDIT: nevermind. I did so. Worked.
sebarkh said:
my ro.sony.build.incremental is 111201038
Do I have to decrease it by 1 to 111201037 ?
Click to expand...
Click to collapse
Yep, exacty. And then you will get newest ota zip of 111201038 pozdro
hahahahah I just had brick... I'm working on auto-install script for "rescue-backdoor", and accidentally I've pushed empty 0bytes build.prop - after reboot - sony logo, then black screen.... and guess what...
recovery reads incremental value (which doesnt exists..) as "0" zero
so i've got lower value, and reflash done.
after reboot my tab started correctly, but.. after reboot again brick - black screen.
fortunatelly - after few min with black screen i've got adb access.
but for first - i can't get root access.. 'su' not works.
but... '/system/xbin/su' works root lets check - build.prop still empty,
remounted system as rw, pushed correct build.prop - ahhh again working !!
that was good experience hahah.
-------------edit:
i've got auto-install tool ready... need to make one more full test with my device and will publish it.
full automatic !!!!!
This is driving me crazy. why everyone is getting update message when changing the incremental value while my dumass tablet keeps saying that my system is up to date
ase3000 said:
This is driving me crazy. why everyone is getting update message when changing the incremental value while my dumass tablet keeps saying that my system is up to date
Click to expand...
Click to collapse
Just wait for automatic-tool. Its ready, but need to make final tests.
condi said:
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
Click to expand...
Click to collapse
In which way we can enter to recovery??
riccardo91 said:
In which way we can enter to recovery??
Click to expand...
Click to collapse
power off, hold vol-down + power.
All done! It works well! Thanks! Avoiding bootloop it's even a good thing!
riccardo91 said:
All done! It works well! Thanks! Avoiding bootloop it's even a good thing!
Click to expand...
Click to collapse
Great Just remember one thing - after reflash in recovery, your build.prop will be updated to higher value - then to be safe you need to reapply modification!
--- my 100th post !
condi said:
Great Just remember one thing - after reflash in recovery, your build.prop will be updated to higher value - then to be safe you need to reapply modification!
--- my 100th post !
Click to expand...
Click to collapse
I bricked my XTS playuing with build.prop. Shame I didn't see this post before. For future - how can I edit build.prop in a safe way? I changed file permission then I forgot to restore default. After restart brick. Do I need to change permission to edit build.prop then do i NEED to restore proper permission back? I'm still confused with it
There seems to be some anxiety about whether a successful ota update can be accomplished by those who modded their build prop file previously.
Just fyi for those who did the build.prop mod and have their original build.prop backed up but were waiting to attempt update, I will confirm that if you delete the modded build.prop and then rename your backed up build.prop.bak back to build.prop before you reboot then you will be able to take the ota update.
Steps I took:
Way back when I had originally renamed my build.prop to build.prop.bak leaving it in the system folder. I had then copied the modified build.prop file into the system folder and fixed the permissions.
Now, to reverse I did this (not sure if need to do all, but these were my steps:
1. opened root explorer
2. navigated to system folder
3. mount r/w
4. delete build.prop (this was the modded one)
5. renamed build.prop.bak to build.prop
6. confirmed permissions remained as they should
7. confirmed, in file properties, that ownership and group remained as "root"
8. mount r/o
9. exit root explorer
10. reboot
11. reboot again
12. opened voodoo ota rootkeeper
13. delete su backup
14. protect root
15. temp un-root
16 close voodoo ota rootkeeper
17. reboot
18 allow ota .28 update
19. when update finished reboot
20 open voodoo ota rootkeeper
21 restore root
So I suppose if you instead had a build.prop that you knew was the original you could substitute that one for the bak one.
Good luck
Yea best to do like you did and leave original in there for these occasions. 10 through 17 kind of overkill though. Reboot would be needed if you were wanting to apply the build.prop but in this case, simply putting the correct file there satisfies the system integrity requirements. No need to unroot. Just verify su backup with voodoo.
It is still fail if you did modify something else in /system partition. Like me i have removed a few sys apps and failed to upgrade. I had to do it manually.
Fireplug said:
There seems to be some anxiety about whether a successful ota update can be accomplished by those who modded their build prop file previously.
Just fyi for those who did the build.prop mod and have their original build.prop backed up but were waiting to attempt update, I will confirm that if you delete the modded build.prop and then rename your backed up build.prop.bak back to build.prop before you reboot then you will be able to take the ota update.
Steps I took:
Way back when I had originally renamed my build.prop to build.prop.bak leaving it in the system folder. I had then copied the modified build.prop file into the system folder and fixed the permissions.
Now, to reverse I did this (not sure if need to do all, but these were my steps:
1. opened root explorer
2. navigated to system folder
3. mount r/w
4. delete build.prop (this was the modded one)
5. renamed build.prop.bak to build.prop
6. confirmed permissions remained as they should
7. confirmed, in file properties, that ownership and group remained as "root"
8. mount r/o
9. exit root explorer
10. reboot
11. reboot again
12. opened voodoo ota rootkeeper
13. delete su backup
14. protect root
15. temp un-root
16 close voodoo ota rootkeeper
17. reboot
18 allow ota .28 update
19. when update finished reboot
20 open voodoo ota rootkeeper
21 restore root
So I suppose if you instead had a build.prop that you knew was the original you could substitute that one for the bak one.
Good luck
Click to expand...
Click to collapse
PLEASE SOMEONE POST A COPY OF THE ORIGINAL US VERSION BUILD.PROP from the .21 firmware
[email protected] said:
It is still fail if you did modify something else in /system partition. Like me i have removed a few sys apps and failed to upgrade. I had to do it manually.
Click to expand...
Click to collapse
Yep. If you want to take OTA's then you shouldn't remove system apps. If you absolutely can't live with the few manufacturer bloat apps, then you can always freeze them instead of remove them. then you can unfreeze them for an OTA.
flak0 said:
PLEASE SOMEONE POST A COPY OF THE ORIGINAL US VERSION BUILD.PROP from the .21 firmware
Click to expand...
Click to collapse
I would post it up for you but I already updated. You can always pull it out of an official update.zip I would think.
---------- Post added at 07:18 AM ---------- Previous post was at 07:14 AM ----------
check here. You might be able to extract what you need from the system dump.
http://forum.xda-developers.com/showpost.php?p=21065580&postcount=2
b.huss2 said:
Yep. If you want to take OTA's then you shouldn't remove system apps. If you absolutely can't live with the few manufacturer bloat apps, then you can always freeze them instead of remove them. then you can unfreeze them for an OTA.
I would post it up for you but I already updated. You can always pull it out of an official update.zip I would think.
---------- Post added at 07:18 AM ---------- Previous post was at 07:14 AM ----------
check here. You might be able to extract what you need from the system dump.
http://forum.xda-developers.com/showpost.php?p=21065580&postcount=2
Click to expand...
Click to collapse
Thanks but those zips have blob files
Sent from my LG-P999 using xda premium
flak0 said:
Thanks but those zips have blob files
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Can you not extract from blob?
flak0 said:
PLEASE SOMEONE POST A COPY OF THE ORIGINAL US VERSION BUILD.PROP from the .21 firmware
Click to expand...
Click to collapse
Here is a copy of the original US. 21
http://db.tt/SOxNURWA
Sent from my SGH-I777 using xda premium
Just make sure to remove ".bak"
Sent from my SGH-I777 using xda premium
Please, i need the EU version .21 of build.prop.
Thank you.
I followed your instructions and update went smooth
Sent from my Transformer Prime TF201 using XDA
I didn't even have to go to all that trouble.
Browsed to /system and renamed build.prop to build.prop.mod
renamed build.mod.bak to build.mod
verified I had a su backup in Voodoo
installed update
restored root
profitted.
In case you want to do the actually OTA with your phone, and got some errors (dead android), you might want to check:
+ if you are using "CWM Recovery" (then uninstall it as in http://forum.xda-developers.com/showthread.php?t=2095825)
+ if you are using "Remove QSlide Apps from NotificationBar" (http://forum.xda-developers.com/showthread.php?t=2194423)
But don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with (you can try if you want). To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first).
+ still not found the problem, check the few last lines of this file: /system/cache/recovery/last_log
It should say which file mismatches the checksum, and in the case of mine, it is LGSystemUI.apk, which I cannot find anything related searching google. And that's why I make the thread so people can search google and found it here.
chicguy said:
In case you want to do the actually OTA with your phone, and got some errors (dead android), you might want to check:
+ if you are using "CWM Recovery" (then uninstall it as in http://forum.xda-developers.com/showthread.php?t=2095825)
+ if you are using "Remove QSlide Apps from NotificationBar" (http://forum.xda-developers.com/showthread.php?t=2194423)
But don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with (you can try if you want). To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first).
+ still not found the problem, check the few last lines of this file: /system/cache/recovery/last_log
It should say which file mismatches the checksum, and in the case of mine, it is LGSystemUI.apk, which I cannot find anything related searching google. And that's why I make the thread so people can search google and found it here.
Click to expand...
Click to collapse
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
eSZee said:
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
Click to expand...
Click to collapse
If you are rooted then all you need to do is find a nandroid backup of previous jb and flash it. Then you use the trick to force the OTA. If you are not rooted then the only thing I can say is download the kdz, flash it, and wait for the OTA.
there are a few things that manipulate the system: link2sd, overclocking, busybox, custom recovery. . .My thing was the busybox. I totally forgot that I downloaded it and my update didn't work at first. Good Luck
eSZee said:
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
Click to expand...
Click to collapse
Go go page 9 of the forum link below. There is a Dropbox link of a factory rooted version of V20f for the 769 US version to flash if you have access to CWM on your phone.
http://forum.xda-developers.com/showthread.php?t=2359044
Sent from my LG-P769 using Tapatalk 2
TheCoutures said:
Go go page 9 of the forum link below. There is a Dropbox link of a factory rooted version of V20f for the 769 US version to flash if you have access to CWM on your phone.
http://forum.xda-developers.com/showthread.php?t=2359044
Sent from my LG-P769 using Tapatalk 2
Click to expand...
Click to collapse
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Make sure MD5 sum is correct. The other stuff doesn't matter. You are flashing a full backup not an OTA which requires all stock apps.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the thanks button.
eSZee said:
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Click to expand...
Click to collapse
Wait you tried to install it as a zip
You are supposed to extract it and put the nandroid in the CWM backup directory.
sent from my locked rooted P769 v20D
I'm on YouTube (BioDesigner48)
I'm having the same issue, I do not have CWM or QSlide Remove installed, I've uninstalled all Root related apps and still encountering the same issue....
eSZee said:
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Click to expand...
Click to collapse
In my OP, I said "don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with".
In case you still have trouble with the OTA, try to follow what I wrote: "To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first)."
Hope that helps!
For other people with problems, I suggest to use the Recovery Flashable Zip mentioned in one of the reply.
Or, if you are as paranoid as I am (who knows what people might put in those zip file ) (and somewhat technically knowledgeable), "check the few last lines of this file: /system/cache/recovery/last_log" to see what file got error, and try to get the original file from 20D (which should have the matched SHA1 checksum) and replace them.
chicguy said:
In my OP, I said "don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with".
In case you still have trouble with the OTA, try to follow what I wrote: "To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first)."
Hope that helps!
For other people with problems, I suggest to use the Recovery Flashable Zip mentioned in one of the reply.
Or, if you are as paranoid as I am (who knows what people might put in those zip file ) (and somewhat technically knowledgeable), "check the few last lines of this file: /system/cache/recovery/last_log" to see what file got error, and try to get the original file from 20D (which should have the matched SHA1 checksum) and replace them.
Click to expand...
Click to collapse
Get the full P769BKv20f kdz file download here. Please be advised that this is just stock and if you flash this ROM then you WILL LOSE ROOT! But you can download and create a bin file to do the Lelus root method.
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
We need someone then to unroot the phone and update to b170 or at least check how to update to b170
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
ensol52 said:
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
Click to expand...
Click to collapse
Paisley Pirate said:
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
Click to expand...
Click to collapse
divineBliss said:
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
Click to expand...
Click to collapse
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
clsA said:
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Click to expand...
Click to collapse
divineBliss said:
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
Click to expand...
Click to collapse
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
HwOUC/****** (numbers)
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
MT2-User said:
HwOUC/****** (numbers)
Click to expand...
Click to collapse
Thanks seems AT&T likes to put them in the path I described though
I'm pretty sure we can edit the updater script to install this from TWRP if someone captures it
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Paisley Pirate said:
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Click to expand...
Click to collapse
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
When I get it I'll get all that as well.
The ATT update note calls it B160_B170_SMR_100 , I hit continue when I tried to hit "remind me later" - but it redownloaded.
Ghost Commander shows nothing in the /cache - odd - so I don't know where it's actually sticking it. I'm searching for it both under that name above and also as update.zip and anything else I can think of (by date, since it just re-downloaded)
I'll grab and document all the info on what I got where.
File is in /cache/fotapkg/ but is named package_temp.zip
I have it out, xda won't accept the file that large, trying to figure out how to link that file only to my onedrive so you can get it without access to all my other junk (sorry)
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Paisley Pirate said:
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Click to expand...
Click to collapse
ok my phone doesn't see the file as an update ..where was it located ?
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
cust.new
cust.patch
cust.transfer
system.new
system.patch
system.transfer
UPDATE.APP
(drawer) META-INF
(drawer) com
(drawer) android
otacert
(drawer) google
(drawer) android
update-binary
update-script
blacklist.conf
CERT.RSA
CERT.SF
MANIFEST.MF
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Paisley Pirate said:
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Click to expand...
Click to collapse
file opens fine ..where was it located on the phone
clsA said:
file opens fine ..where was it located on the phone
Click to expand...
Click to collapse
as I said earlier - /cache/fotapkg/
Paisley Pirate said:
as I said earlier - /cache/fotapkg/
Click to expand...
Click to collapse
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Any idea how the phone installs this OTA zip file?
Is the updater-script failing because of assert statements for cust and system?
Have you had success patching cust and system using the OTA updater-script/OTA zips for the Huawei Ascend XT before? How did you end up getting the cust and system for your B160 Update zip? Probably from a TWRP of someone's updated B160, which is what we need to do for B170 now, I'm guessing?
Thanks for your efforts on this and answering my questions.
clsA said:
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Click to expand...
Click to collapse