I have very slow internet and only need the latest vendor.img from the MOB30M OTA. Could someone please upload it for me so I don't have to download the whole 1gb OTA?
Thanks
Stylez Ray. said:
I have very slow internet and only need the latest vendor.img from the MOB30M OTA. Could someone please upload it for me so I don't have to download the whole 1gb OTA?
Thanks
Click to expand...
Click to collapse
why would you need a vendor.img? and for which phone?
simms22 said:
why would you need a vendor.img? and for which phone?
Click to expand...
Click to collapse
Well i'm not sure if my plan is correct: I am running Dirty Unicorns for a long time now but also flashed A.R.I.S.E sound systems. I wanted to get rid of the sound system completely, normally a dirty flash of the rom is enough but I just had a look at the /vendor folder and saw some files which were edited by the sound system.
So as I remember flashing the rom zip doesn't touch the /vendor partition and looking in the rom .zip looks like I am right as I only see /system and /boot images
Stylez Ray. said:
Well i'm not sure if my plan is correct: I am running Dirty Unicorns for a long time now but also flashed A.R.I.S.E sound systems. I wanted to get rid of the sound system completely, normally a dirty flash of the rom is enough but I just had a look at the /vendor folder and saw some files which were edited by the sound system.
So as I remember flashing the rom zip doesn't touch the /vendor partition and looking in the rom .zip looks like I am right as I only see /system and /boot images
Click to expand...
Click to collapse
ohh.. i see. i thought you were on a n6p or a n5x, since they need the vendor.img, and we dont. i was going to let you know, but youre on top of it
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
Stylez Ray. said:
Well i'm not sure if my plan is correct: I am running Dirty Unicorns for a long time now but also flashed A.R.I.S.E sound systems. I wanted to get rid of the sound system completely, normally a dirty flash of the rom is enough but I just had a look at the /vendor folder and saw some files which were edited by the sound system.
So as I remember flashing the rom zip doesn't touch the /vendor partition and looking in the rom .zip looks like I am right as I only see /system and /boot images
Click to expand...
Click to collapse
btw, i gave you a thanks for..
Originally Posted by morfic
Just flash over.
Only thing we wipe here is our butts.
Click to expand...
Click to collapse
i dont know why you added it, but it seems as you added it for me
simms22 said:
ohh.. i see. i thought you were on a n6p or a n5x, since they need the vendor.img, and we dont. i was going to let you know, but youre on top of it
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
btw, i gave you a thanks for..
Originally Posted by morfic
Just flash over.
Only thing we wipe here is our butts.
i dont know why you added it, but it seems as you added it for me
Click to expand...
Click to collapse
That's my signature for a long time back in the days of Trinity kernel i read this comment, but whom am I telling this
simms22 said:
ohh.. i see. i thought you were on a n6p or a n5x, since they need the vendor.img, and we dont. i was going to let you know, but youre on top of it
Click to expand...
Click to collapse
Just curious, why do those devices need a vendor.img?
ceo4eva said:
Just curious, why do those devices need a vendor.img?
Click to expand...
Click to collapse
no idea, since i dont have one. and ive not done any imvestigating either. but they do need it.
ceo4eva said:
Just curious, why do those devices need a vendor.img?
Click to expand...
Click to collapse
Its do to the way the OEM did it. One of the biggest complaints from people with the device. It is also thought that google is doing it to make things harder for custom rom users and devs and with some of the recent info about Google It wouldnt surprise me at all.
So I downloaded the whole OTA myself and had a look at it. There's no vendor.img in it...
Makes me wonder, how can I get a clean vendor partition now?!
Stylez Ray. said:
So I downloaded the whole OTA myself and had a look at it. There's no vendor.img in it...
Makes me wonder, how can I get a clean vendor partition now?!
Click to expand...
Click to collapse
The only way will be to completely flash the device with the stock files. It wipes all partitions 2hich should fix things
Stylez Ray. said:
So I downloaded the whole OTA myself and had a look at it. There's no vendor.img in it...
Makes me wonder, how can I get a clean vendor partition now?!
Click to expand...
Click to collapse
just flash a rom, maybe it builds fresh each flash?
ceo4eva said:
Just curious, why do those devices need a vendor.img?
Click to expand...
Click to collapse
simms22 said:
no idea, since i dont have one. and ive not done any imvestigating either. but they do need it.
Click to expand...
Click to collapse
We have a vendor image but it is in /system and symlink from /system/vendor to /vendor.
New Google device that have been released with L or M have now the vendor as a separate partition from system.
Why? I think it's more simple and secure for everybody.
---------- Post added at 05:21 AM ---------- Previous post was at 05:18 AM ----------
Stylez Ray. said:
So I downloaded the whole OTA myself and had a look at it. There's no vendor.img in it...
Makes me wonder, how can I get a clean vendor partition now?!
Click to expand...
Click to collapse
So no normally dirty flash your rom will wipe the vendor in n6 because it is stored in /system/vendor.
If a dirty flash doesn't work. In twrp wipe system partition then flash rom - gapps etc...
If you see a /vendor directory it's just a symlink dir like /etc or /sdcard
Dead-neM said:
We have a vendor image but it is in /system and symlink from /system/vendor to /vendor.
New Google device that have been released with L or M have now the vendor as a separate partition from system.
Why? I think it's more simple and secure for everybody.
---------- Post added at 05:21 AM ---------- Previous post was at 05:18 AM ----------
So no normally dirty flash your rom will wipe the vendor in n6 because it is stored in /system/vendor.
If a dirty flash doesn't work. In twrp wipe system partition then flash rom - gapps etc...
If you see a /vendor directory it's just a symlink dir like /etc or /sdcard
Click to expand...
Click to collapse
That's a very nice explanation, thanks!
Found out the same just as I downloaded the factory image and couldn't even see a vendor. img in there.
Dirty flashing rom does the job
Related
hey guys, where to find multipackage firmware for ace, only found s5830i/c multipack thread. none for this device.
thanks for all ur help.
dzeig said:
hey guys, where to find multipackage firmware for ace, only found s5830i/c multipack thread. none for this device.
thanks for all ur help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=39294309
KPH
thanks alot. btw, is it possible to go back to stock from custom rom (ie cm10.1) using single firmware.
coz, i need to flash multipack fw first (from cusrom) before flashing lastest stock, on mini.
dzeig said:
thanks alot. btw, is it possible to go back to stock from custom rom (ie cm10.1) using single firmware.
coz, i need to flash multipack fw first (from cusrom) before flashing lastest stock, on mini.
Click to expand...
Click to collapse
Be careful the rom I posted was for Galaxy Ace!!!
Yes, It's possible, I don't know in mini ... this is the GT-S5830 Q&A THREAD so...
but the fastest way to go back to stock is doing a backup before to use the custom, and then restoring it when you want to go back via custom RECOVERY, or FALSHING A FRESH STOCK ROM VIA ODIN
...and in Galaxy Ace it's possible to use directly the lastest firmware, "one package fw"
i know, im using ace right now.
the thing is i was failed revert back to stock using one pack firmware (on mini). am bit afraid it happens to ace either. but now it's all clear, thanks for all ur helps.
edit: whoaa, we can backup stock on ace, it s not recommended on mini. thanks again.
dzeig said:
i know, im using ace right now.
the thing is i was failed revert back to stock using one pack firmware (on mini). am bit afraid it happens to ace either. but now it's all clear, thanks for all ur helps.
edit: whoaa, we can backup stock on ace, it s not recommended on mini. thanks again.
Click to expand...
Click to collapse
well, the best way to avoid all kind of troubles is flashing a fresh stock via Odin
I'm using a bareboned stock rom, I deleted all useless apps etc and I chaged the kernel and stock partitions from .rfs to .ext4, so I have a clean backup ready to restore in my SDCARD, so I can flash whatever I want, and then when I get tired I can always return to my clean previous rom and I don't need to use Odin
am a noob so...
1. change the kernel? even for lastest fw?
2. how to change the.rfs partition?
dzeig said:
am a noob so...
1. change the kernel? even for lastest fw?
2. how to change the.rfs partition?
Click to expand...
Click to collapse
well... you can change the kernel, deodex your rom, change .rfs partition format to .ext4 format and add more tweaks, barebone your rom... (not for a noob way) or the easiest way!! you can flash a based stock rom with ALL this changes done e.g. http://forum.xda-developers.com/showthread.php?t=1534804
Viper The Ripper said:
well... you can change the kernel, deodex your rom, change .rfs partition format to .ext4 format and add more tweaks, barebone your rom... (not for a noob way) or the easiest way!! you can flash a based stock rom with ALL this changes done e.g. http://forum.xda-developers.com/showthread.php?t=1534804
Click to expand...
Click to collapse
hey viper, can you tell how to root lastest fw (bvkt6). cuz I tried using root.zip, upd_1.zip, universalgbroot_25 none of it works. thanks.
dzeig said:
hey viper, can you tell how to root lastest fw (bvkt6). cuz I tried using root.zip, upd_1.zip, universalgbroot_25 none of it works. thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2346116
I need to know which apps are included in /system. The problem is that there isn't enough free space in /system in this rom so we could use a script to delete whatever app in this partition that allow us to push su.apk and the binaries
Viper The Ripper said:
http://forum.xda-developers.com/showthread.php?t=2346116
I need to know which apps are included in /system. The problem is that there isn't enough free space in /system in this rom so we could use a script to delete whatever app in this partition that allow us to push su.apk and the binaries
Click to expand...
Click to collapse
i read those threads.
so all i need to do is changing the updater-script, and delete unuseful system apps, right?
man, your so helpful. thanks a lot.
dzeig said:
i read those threads.
so all i need to do is changing the updater-script, and delete unuseful system apps, right?
man, your so helpful. thanks a lot.
Click to expand...
Click to collapse
Yeah, it's because I needed to know about your useless apps m but you can modify the script too
I've posted in the other thread how to add to the script how to mount /system auntomatically
You're welcome dude!
Viper The Ripper said:
Yeah, it's because I needed to know about your useless apps m but you can modify the script too
I've posted in the other thread how to add to the script how to mount /system auntomatically
You're welcome dude!
Click to expand...
Click to collapse
i got my phone rooted. ur magical zip works great. once again thank you.
now, i got 50+ mb free space in /system.
i just tried backingup via cwm, it said error mounting the system, bla, bla...
so, next question is how to backup this rom?
dzeig said:
i got my phone rooted. ur magical zip works great. once again thank you.
now, i got 50+ mb free space in /system.
i just tried backingup via cwm, it said error mounting the system, bla, bla...
so, next question is how to backup this rom?
Click to expand...
Click to collapse
you can try mounting manually /system and then doing the backup
go to mount and system >>> mount /system >>> back >>> backup and restore >>> backup
Viper The Ripper said:
you can try mounting manually /system and then doing the backup
go to mount and system >>> mount /system >>> back >>> backup and restore >>> backup
Click to expand...
Click to collapse
already tried to mount /system manually but no luck: "error mounting the system".
what i have to do?
dzeig said:
already tried to mount /system manually but no luck: "error mounting the system".
what i have to do?
Click to expand...
Click to collapse
mm I guess what is your problem
maybe .rfs format , so try to convert your partitions to .ext4 partition, It would solve your problem
use CF-Root-S5830_ext4-v1.3u3.apk to convert .rfs to .ext4 format
Viper The Ripper said:
mm I guess what is your problem
maybe .rfs format , so try to convert your partitions to .ext4 partition, It would solve your problem
use CF-Root-S5830_ext4-v1.3u3.apk to convert .rfs to .ext4 format
Click to expand...
Click to collapse
is this the correct kernel: CF-Root-S5830-v3.7-b84.zip?
edit: i think i did it right. now ive converted it to .ext4.
ive backed it up too, and it works.
my next question, where is a2sd script located, am bout to change it to int2ext4 (i didnt find it in init.d folder)?
dzeig said:
is this the correct kernel: CF-Root-S5830-v3.7-b84.zip?
edit: i think i did it right. now ive converted it to .ext4.
ive backed it up too, and it works.
my next question, where is a2sd script located, am bout to change it to int2ext4 (i didnt find it in init.d folder)?
Click to expand...
Click to collapse
Wooow I'm glad!! I'm a wiseman xDDD
---------- Post added at 05:07 AM ---------- Previous post was at 05:03 AM ----------
dzeig said:
is this the correct kernel: CF-Root-S5830-v3.7-b84.zip?
edit: i think i did it right. now ive converted it to .ext4.
ive backed it up too, and it works.
cf-root b84 work fine
my next question, where is a2sd script located, am bout to change it to int2ext4 (i didnt find it in init.d folder)?
Click to expand...
Click to collapse
Well you need a custom kernel to get an init.d folder or create it on yourself but the easy way, flash cf-root b84, BE 1.5.1. or whatever kernel you want, and you'll get an init.d folder support, so you'll be able to flash the int2ext script without any kind of problem
Viper The Ripper said:
Wooow I'm glad!! I'm a wiseman xDDD
Click to expand...
Click to collapse
i believe you are, how bout removing a2sd i've mentioned before...
edit: mmm... i found a2sd uninstaller zip, i ll give it a go..
dzeig said:
i believe you are, how bout removing a2sd i've mentioned before...
Click to expand...
Click to collapse
Install a Terminal Emulator app and type this code
Code:
su
a2sd remove
But it is not compulsory to install int2ext script, at least if you didn't flash darktremor script to activate app2sd
---------- Post added at 05:17 AM ---------- Previous post was at 05:14 AM ----------
dzeig said:
i believe you are, how bout removing a2sd i've mentioned before...
edit: mmm... i found a2sd uninstaller zip, i ll give it a go..
Click to expand...
Click to collapse
Well you can try it, of course
I accidentally messed up the root folder(/), which contains system, cache, data, lta-label etc folders
Now how can I make the whole root folder back to the original state?
To solve this, can I flash a firmware by Flashtool with "Exclude Partition" unticked?
Will every folder and file under the root folder come back to the original state?
By the way, can lta-label folder be deleted?
Thank you!
Can you elaborate on messing up the root folder? What exactly is messed up?
DevShaft said:
Can you elaborate on messing up the root folder? What exactly is messed up?
Click to expand...
Click to collapse
I wrongly created and moved some files and folders just under the Android root folder(/)(PS not sdcard root folder)
so now the root folder has been messed up and i want to make the whole root directory go back to factory state.
thanks
....cant you just delete them?
Sent from my PAC-ed LT18i.
Press the thanks button if I helped.
Just reflash using flashtool
flytomars said:
I wrongly created and moved some files and folders just under the Android root folder(/)(PS not sdcard root folder)
so now the root folder has been messed up and i want to make the whole root directory go back to factory state.
thanks
Click to expand...
Click to collapse
Which folders are you referring to exactly?
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
Michealtbh said:
Just reflash using flashtool
Click to expand...
Click to collapse
May not help in this case.
tangosierra_ said:
....cant you just delete them?
Sent from my PAC-ed LT18i.
Press the thanks button if I helped.
Click to expand...
Click to collapse
after a reboot the wrongly created files and folders disappear and i don't know where they have gone
i worry that they still exist but cannot be found
DevShaft said:
Which folders are you referring to exactly?
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
May not help in this case.
Click to expand...
Click to collapse
If flashing a FTF can clear every partition then it will help
DevShaft said:
Which folders are you referring to exactly?
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
May not help in this case.
Click to expand...
Click to collapse
i wrongly copied TitaniumBackup folder just to the root folder
after a reboot it disappeared i don't know where it is
flytomars said:
If flashing a FTF can clear every partition then it will help
Click to expand...
Click to collapse
Flashing a FTF can clear most partitions, but not everything like TA. So no 100% clean slade I'm afraid. However this can solve problems such as yours.
---------- Post added at 05:37 AM ---------- Previous post was at 05:26 AM ----------
flytomars said:
i wrongly copied TitaniumBackup folder just to the root folder
after a reboot it disappeared i don't know where it is
Click to expand...
Click to collapse
I believe / is a ramdisk mounting everything together. This means that on every boot this ramdisk is recreated and all adjustments you made to / before will be gone. So your TB folder is actually nowhere, so nothing for you to worry about. It's like it was before you wrongly copied the folder. No need to flash an ftf, but if it makes you feel good .
DevShaft said:
Flashing a FTF can clear most partitions, but not everything like TA. So no 100% clean slade I'm afraid. However this can solve problems such as yours.
---------- Post added at 05:37 AM ---------- Previous post was at 05:26 AM ----------
I believe / is a ramdisk mounting everything together. This means that on every boot this ramdisk is recreated and all adjustments you made to / before will be gone. So your TB folder is actually nowhere, so nothing for you to worry about. It's like it was before you wrongly copied the folder. No need to flash an ftf, but if it makes you feel good .
Click to expand...
Click to collapse
what you said makes me stop worrying.
Besides TB folder I also wrongly copied some files just under the root folder.
I once worried that after a reboot they will not be deleted and just be hidden and be nowhere to be found so that they will permanently exist in a unknown place on my phone.
Now I know that they can be simply 'killed' by completely flashing a ftf.
So can I get a conclusion:
If the root folder is messed up, for example, saving files and folders under lta-lable folder or under any other folder in the root folder or just under the root folder(/), everything that shouldn't exist will be deleted and everything under the root folder will be back to the factory state by flashing the whole ftf.
Is this right?
Thank you!
DevShaft said:
Flashing a FTF can clear most partitions, but not everything like TA. So no 100% clean slade I'm afraid. However this can solve problems such as yours.
---------- Post added at 05:37 AM ---------- Previous post was at 05:26 AM ----------
I believe / is a ramdisk mounting everything together. This means that on every boot this ramdisk is recreated and all adjustments you made to / before will be gone. So your TB folder is actually nowhere, so nothing for you to worry about. It's like it was before you wrongly copied the folder. No need to flash an ftf, but if it makes you feel good .
Click to expand...
Click to collapse
:good:
flytomars said:
what you said makes me stop worrying.
Besides TB folder I also wrongly copied some files just under the root folder.
I once worried that after a reboot they will not be deleted and just be hidden and be nowhere to be found so that they will permanently exist in a unknown place on my phone.
Now I know that they can be simply 'killed' by completely flashing a ftf.
So can I get a conclusion:
If the root folder is messed up, for example, saving files and folders under lta-lable folder or under any other folder in the root folder or just under the root folder(/), everything that shouldn't exist will be deleted and everything under the root folder will be back to the factory state by flashing the whole ftf.
Is this right?
Thank you!
Click to expand...
Click to collapse
just reflash FTF or if you have custom rom reflash the rom in recovery...
G1_enthusiast said:
just reflash FTF or if you have custom rom reflash the rom in recovery...
Click to expand...
Click to collapse
flashing a custom rom won't format partitions so i think it's better to flash ftf
flytomars said:
flashing a custom rom won't format partitions so i think it's better to flash ftf
Click to expand...
Click to collapse
if you wipe system, data and cache it will...worth a try it takes 5 minute to know if it work..
G1_enthusiast said:
if you wipe system, data and cache it will...worth a try it takes 5 minute to know if it work..
Click to expand...
Click to collapse
i messed up the root folder /
not data, system etc which are under the root folder
flytomars said:
flashing a custom rom won't format partitions so i think it's better to flash ftf
Click to expand...
Click to collapse
Yes, only you don't have to because of the fact you wrote to ram, so nothing is messed up .
---------- Post added at 06:07 PM ---------- Previous post was at 05:57 PM ----------
flytomars said:
So can I get a conclusion:
If the root folder is messed up, for example, saving files and folders under lta-lable folder or under any other folder in the root folder or just under the root folder(/), everything that shouldn't exist will be deleted and everything under the root folder will be back to the factory state by flashing the whole ftf.
Is this right?
Thank you!
Click to expand...
Click to collapse
No, that's not right .
When you write anything to / (not further down!), it will be gone like it never existed. This is because writing to / is actually to RAM. RAM is cleared on reboot.
So conclusion is, you don't have a messed up /, since it is restored after a reboot. This is only the case when you write directly to /. So not necessarily when you write to a folder called /foo or /bar. You don't have to do anything, since there is no mess and all is fine.
A RAM disk is an area in memory which is mounted as disk, as if it is disk space while it actually is RAM space which is cleared when the device reboots or shuts down. When the device boots it recreates this RAM disk and copies the necessary files and folders to it. It also mounts certain partitions under aliases like /system and /data. When the RAM disk is removed from memory - at a shutdown or reboot - it will only clear the files and folders copied to / and the aliases of the partitions mounted, not the content of the partitions themselves. So when you write to /system/ it will not be gone at next boot while something written to / directly will. I hope it makes a bit more sense now .
DevShaft said:
Yes, only you don't have to because of the fact you wrote to ram, so nothing is messed up .
---------- Post added at 06:07 PM ---------- Previous post was at 05:57 PM ----------
No, that's not right .
When you write anything to / (not further down!), it will be gone like it never existed. This is because writing to / is actually to RAM. RAM is cleared on reboot.
So conclusion is, you don't have a messed up /, since it is restored after a reboot. This is only the case when you write directly to /. So not necessarily when you write to a folder called /foo or /bar. You don't have to do anything, since there is no mess and all is fine.
A RAM disk is an area in memory which is mounted as disk, as if it is disk space while it actually is RAM space which is cleared when the device reboots or shuts down. When the device boots it recreates this RAM disk and copies the necessary files and folders to it. It also mounts certain partitions under aliases like /system and /data. When the RAM disk is removed from memory - at a shutdown or reboot - it will only clear the files and folders copied to / and the aliases of the partitions mounted, not the content of the partitions themselves. So when you write to /system/ it will not be gone at next boot while something written to / directly will. I hope it makes a bit more sense now .
Click to expand...
Click to collapse
now i understand
and i did a test.
i created a folder and a file under / whose permissions were set the same as the permission of other files under /
after a reboot the created folder and file disappear
so i think what you said is undoubtly right
but if i write something further down then i have to flash a ftf because flashing a ftf can wipe every partition mounted under /
is this right?
thank you!
Most, not every. Partitions like TA cannot be wiped by flashing a ftf.
Sent from my PAC-ed LT18i.
Press the thanks button if I helped.
flytomars said:
but if i write something further down then i have to flash a ftf because flashing a ftf can wipe every partition mounted under /
is this right?
thank you!
Click to expand...
Click to collapse
As said not every partition, like the TA for instance. However in most cases flashing ftf will do.
Recently @Captain_Throwback made a custom TWRP image. My 626s is very broken. I don't even have a system image. I really need someone to install the recovery and backup their system image and send me a link so i can fix my 626s.
Link to TWRP:https://basketbuild.com/devs/Captain_Throwback/Desire 626s/Recovery/TWRP
Will do this as soon as I get home and I'll post a link for you.
Bad news this TWRP build like my unreleased builds have the same issue the stock kernel disables the digitizer when booted to the Recovery partition. Good News HTC finally released the Kernel Source so we can fix this issue. I probably wont be able to work on this since I am currently now working 55 hours a week for the next two months and have very little free time on my hands
Never mind it works i'm just really tired
Can't backupvup system.IMG cause it won't mount external SD card or otg cable with a flash drive
EDIT: wiped data and internal storage to create enough space on internal sd. will post a link for twrp backup and a system.img as well
Piplup702 said:
Can't backupvup system.IMG cause it won't mount external SD card or otg cable with a flash drive
EDIT: wiped data and internal storage to create enough space on internal sd. will post a link for twrp backup and a system.img as well
Click to expand...
Click to collapse
Thanks - This is what I needed to know. I'm sure I can fix this in the recovery kernel. I'll rebuild it later today. Since I don't have the device, it's a bit . . . challenging.
Piplup702 said:
Can't backupvup system.IMG cause it won't mount external SD card or otg cable with a flash drive
EDIT: wiped data and internal storage to create enough space on internal sd. will post a link for twrp backup and a system.img as well
Click to expand...
Click to collapse
Please try the updated TWRP I posted at the same location as indicated in the OP. External SD *should* be accessible now. If not (or even if it is), if you could do Advanced -> Copy Log to SD and then upload that log for me, I'd greatly appreciate it .
Captain_Throwback said:
Please try the updated TWRP I posted at the same location as indicated in the OP. External SD *should* be accessible now. If not (or even if it is), if you could do Advanced -> Copy Log to SD and then upload that log for me, I'd greatly appreciate it .
Click to expand...
Click to collapse
it mounts external and internal and shows up on pc. the first one didnt. heres my recovery log.
dropbox. com/s/yl45s4y463m6fxp/recovery%5B1%5D.log?dl=0
itz me ry4n said:
it mounts external and internal and shows up on pc. the first one didnt. i did copy log to sd but its just a TWRPS file
Click to expand...
Click to collapse
Yes, I need a copy of the log that copied to SD. Please upload that recovery log.
Captain_Throwback said:
Yes, I need a copy of the log that copied to SD. Please upload that recovery log.
Click to expand...
Click to collapse
i found it. updated my pervious post
https://drive.google.com/folderview?id=0B_T4Zb3ybDQ7OWx3NWV3c28yQkU&usp=sharing
heres a link for twrp backup for the people who bricked. The one named 2015-11-12--02-41-03_LMY47O_release-keys is the regular backup, the other one is a system.img backup
Piplup702 said:
https://drive.google.com/folderview?id=0B_T4Zb3ybDQ7OWx3NWV3c28yQkU&usp=sharing
heres a link for twrp backup for the people who bricked. The one named 2015-11-12--02-41-03_LMY47O_release-keys is the regular backup, the other one is a system.img backup
Click to expand...
Click to collapse
will this work on the metro pcs phone?
itz me ry4n said:
will this work on the metro pcs phone?
Click to expand...
Click to collapse
Yes, it's a backup of my metro pcs desire 626s.
Piplup702 said:
Yes, it's a backup of my metro pcs desire 626s.
Click to expand...
Click to collapse
ok thanks. im flashing it now and will update when it is dont if it worked or not.
---------- Post added at 07:51 PM ---------- Previous post was at 07:23 PM ----------
itz me ry4n said:
ok thanks. im flashing it now and will update when it is dont if it worked or not.
Click to expand...
Click to collapse
its done but doesnt boot. just goes to the bootloader menu. i may need the boot.img file for it. if u could get that for me please.
---------- Post added at 08:01 PM ---------- Previous post was at 07:51 PM ----------
itz me ry4n said:
ok thanks. im flashing it now and will update when it is dont if it worked or not.
---------- Post added at 07:51 PM ---------- Previous post was at 07:23 PM ----------
its done but doesnt boot. just goes to the bootloader menu. i may need the boot.img file for it. if u could get that for me please.
Click to expand...
Click to collapse
yea the boot.img was the problem i found one and flashed it and now the phones is booting and android is starting.
itz me ry4n said:
ok thanks. im flashing it now and will update when it is dont if it worked or not.
---------- Post added at 07:51 PM ---------- Previous post was at 07:23 PM ----------
its done but doesnt boot. just goes to the bootloader menu. i may need the boot.img file for it. if u could get that for me please.
---------- Post added at 08:01 PM ---------- Previous post was at 07:51 PM ----------
yea the boot.img was the problem i found one and flashed it and now the phones is booting and android is starting.
Click to expand...
Click to collapse
There's a boot.IMG in my Google drive
https://drive.google.com/folder/d/0B_T4Zb3ybDQ7dEFJUEZxbzZTOEU/edit
Piplup702 said:
https://drive.google.com/folderview?id=0B_T4Zb3ybDQ7OWx3NWV3c28yQkU&usp=sharing
heres a link for twrp backup for the people who bricked. The one named 2015-11-12--02-41-03_LMY47O_release-keys is the regular backup, the other one is a system.img backup
Click to expand...
Click to collapse
Thank you so much downloading now but 2.5GB takes a little while. Will report back if it works
gingrbred said:
Thank you so much downloading now but 2.5GB takes a little while. Will report back if it works
Click to expand...
Click to collapse
Bad news. When I try to restore in twrp I get this error.
Code:
E:extractTarFork() process ended with ERROR=255
gingrbred said:
Bad news. When I try to restore in twrp I get this error.
Code:
E:extractTarFork() process ended with ERROR=255
Click to expand...
Click to collapse
Need the full log.
Captain_Throwback said:
Need the full log.
Click to expand...
Click to collapse
View attachment 3540274
Here you go
gingrbred said:
View attachment 3540274
Here you go
Click to expand...
Click to collapse
This log won't open for me.
View attachment recovery.log
Captain_Throwback said:
This log won't open for me.
Click to expand...
Click to collapse
this is a log from when i got the restore to work but the phone still wont boot
I have selinux set on permissive and I have busybox installed is it that we can't have it on 6.0.1? Please help
josianjehu said:
I have selinux set on permissive and I have busybox installed is it that we can't have it on 6.0.1? Please help
Click to expand...
Click to collapse
works fine here. where did you install it? its supposed to be in /system/priv-app/. theres a flashable in the viper thread in the themes and apps section.
simms22 said:
works fine here. where did you install it? its supposed to be in /system/priv-app/. theres a flashable in the viper thread in the themes and apps section.
Click to expand...
Click to collapse
Idk what you mean by that sorry I installed the apk and I installed the drivers can you give me a link to the threat you used to install it?
josianjehu said:
Idk what you mean by that sorry I installed the apk and I installed the drivers can you give me a link to the threat you used to install it?
Click to expand...
Click to collapse
that's why it won't work, you can't install it as a normal app, it needs to be a system app. anyways, here you go. needs to be flashed in twrp recovery http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
simms22 said:
that's why it won't work, you can't install it as a normal app, it needs to be a system app. anyways, here you go. needs to be flashed in twrp recovery http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
Click to expand...
Click to collapse
I flashed the stock viper 5.0 zip and nothing appeared afterwards
josianjehu said:
I flashed the stock viper 5.0 zip and nothing appeared afterwards
Click to expand...
Click to collapse
nothing? no app or anything? try flashing again.
simms22 said:
nothing? no app or anything? try flashing again.
Click to expand...
Click to collapse
I tried flashing a different one and still nothing could be twrp? I installed twrp using the nexus root toolkit
josianjehu said:
I tried flashing a different one and still nothing could be twrp? I installed twrp using the nexus root toolkit
Click to expand...
Click to collapse
you can use any root file explorer to stick the apk into /system/priv-app/, then reboot and it'll install itself.
simms22 said:
you can use any root file explorer to stick the apk into /system/priv-app/, then reboot and it'll install itself.
Click to expand...
Click to collapse
Okay this what I'm going to do
1. Extract apk from the stock viper 5.0 to system/priv-apps
2. Go to recovery flash the zip
3. And boom it should appear
Correct me if I'm wrong
josianjehu said:
Okay this what I'm going to do
1. Extract apk from the stock viper 5.0 to system/priv-apps
2. Go to recovery flash the zip
3. And boom it should appear
Correct me if I'm wrong
Click to expand...
Click to collapse
just sticknit into /system/priv-app/ and save it. then just reboot and it will install itself.no flash needed this way.
simms22 said:
just sticknit into /system/priv-app/ and save it. then just reboot and it will install itself.no flash needed this way.
Click to expand...
Click to collapse
Doesn't let me put files in that folder and I did put it in read and write
josianjehu said:
Doesn't let me put files in that folder and I did put it in read and write
Click to expand...
Click to collapse
sounds like you don't have root, or just have partial root.
simms22 said:
sounds like you don't have root, or just have partial root.
Click to expand...
Click to collapse
That's strange cause I am able to use light flow for my notification light which uses root
josianjehu said:
That's strange cause I am able to use light flow for my notification light which uses root
Click to expand...
Click to collapse
then you have partial root. its a normal issue, that happens often enough. to be 100% sure, you can try editing tour build.prop file. if the edits stay after a reboot then you have full root. if they don't stay after a reboot, then you have partial root. which is why viper isn't working. it can also be that your system is full. you can delete whichever apps you don't use from /system/app/, which will give you space. you did say you flashed it but it never appeared. if its full, it can't appear.
simms22 said:
then you have partial root. its a normal issue, that happens often enough. to be 100% sure, you can try editing tour build.prop file. if the edits stay after a reboot then you have full root. if they don't stay after a reboot, then you have partial root. which is why viper isn't working. it can also be that your system is full. you can delete whichever apps you don't use from /system/app/, which will give you space. you did say you flashed it but it never appeared. if its full, it can't appear.
Click to expand...
Click to collapse
When I tried editing the build.prop it said I didn't have enough space even tho I have 20 gb left of storage
josianjehu said:
When I tried editing the build.prop it said I didn't have enough space even tho I have 20 gb left of storage
Click to expand...
Click to collapse
Does installing cm help with all this?
josianjehu said:
When I tried editing the build.prop it said I didn't have enough space even tho I have 20 gb left of storage
Click to expand...
Click to collapse
i know, google did it on purpose. to fix that delete whichever system apps you dont use. and storage has nothing to do with system space. system space iz held in a seperate partition.
---------- Post added at 05:21 PM ---------- Previous post was at 05:19 PM ----------
josianjehu said:
Does installing cm help with all this?
Click to expand...
Click to collapse
no idea. probably not?
simms22 said:
i know, google did it on purpose. to fix that delete whichever system apps you dont use. and storage has nothing to do with system space. system space iz held in a seperate partition.
---------- Post added at 05:21 PM ---------- Previous post was at 05:19 PM ----------
no idea. probably not?
Click to expand...
Click to collapse
Thaaaaaank you soon much knowing about the partitions Google made I did it by uninstalling apps
dont instal on note 5
I have never been able to get this feature in TB work. When I try to flash the update.zip I am met with: 'Failed to map file '/sdcard/update.zip' Error installing zip file '/sdcard/update.zip'
No idea where to start with this one.
Anyone?
This may be a WAG, but worth a try.
https://www.xda-developers.com/psa-...broke-titanium-backup-substratum-heres-a-fix/
Pkt_Lnt said:
This may be a WAG, but worth a try.
https://www.xda-developers.com/psa-...broke-titanium-backup-substratum-heres-a-fix/
Click to expand...
Click to collapse
Thanks, I will check it out.
tjlmbklr said:
I have never been able to get this feature in TB work. When I try to flash the update.zip I am met with: 'Failed to map file '/sdcard/update.zip' Error installing zip file '/sdcard/update.zip'
No idea where to start with this one.
Anyone?
Click to expand...
Click to collapse
That feature hasn't worked since eclair... The script is borked and no one uses it
rignfool said:
That feature hasn't worked since eclair... The script is borked and no one uses it
Click to expand...
Click to collapse
Good to know. Thanks.
I'm making some tests now. It seems TWRP only flashes zips with at least 2GB of space. I'm thinking about divide the backup in two zips of apps and a data zip. i think it will work.
---------- Post added at 11:25 ---------- Previous post was at 11:15 ----------
It's official: it works! Divide your backup in zips with less than 2GB and it will work.