Related
I know there are threads like this out there, but none of them fitted my questions...
Hi,
in this post, seo posted some ported sense 3.0 apps and widgets for Sense 2.1 GB roms.
I tried to install some of them and got MMS to work.
Then tried to get Rosie and widgets, but they wouldn't install directly, so i started playing around with ADB.
i think adb is fully set up, i am able to pull apks from /system/app.
problem is, i am obviously unable to push, install or uninstall system apps via
adb push
adb install
adb uninstall.
this was when i tried remounting (with remount,rw etc.) and was able to "rip off" rosie.apk (i know it worked as it wasn't there anymore later on ) but still was unable to install apps (with the effect i hadn't got a launcher at all.)
latest step was creating a signed update.zip, didn't work, recovery just restarts.
anyone help? someone got experience which may help me? i went through about 10 or 20 guides and am kind of desperate right now as things just dont work
thanks
SummonerOfDeath said:
I know there are threads like this out there, but none of them fitted my questions...
Hi,
in this post, seo posted some ported sense 3.0 apps and widgets for Sense 2.1 GB roms.
I tried to install some of them and got MMS to work.
Then tried to get Rosie and widgets, but they wouldn't install directly, so i started playing around with ADB.
i think adb is fully set up, i am able to pull apks from /system/app.
problem is, i am obviously unable to push, install or uninstall system apps via
adb push
adb install
adb uninstall.
this was when i tried remounting (with remount,rw etc.) and was able to "rip off" rosie.apk (i know it worked as it wasn't there anymore later on ) but still was unable to install apps (with the effect i hadn't got a launcher at all.)
latest step was creating a signed update.zip, didn't work, recovery just restarts.
anyone help? someone got experience which may help me? i went through about 10 or 20 guides and am kind of desperate right now as things just dont work
thanks
Click to expand...
Click to collapse
Pull me a recovery.log when you try installing the zip, and I'll have a look for you.
Sent from my HTC Hero using XDA Premium App
S.O.D. proudly presents.... recovery.log!
Here it is, i attached my own update.zip (rosie-signed.apk), maybe you could have a look at it as i don't know where the fault may be.
greets SOD
I would already be happy if you managed to solve the update.zip issue (would help me with other updates) but the main prob is adb noch really working, seems like some system part is blocking this?
my hero was originally a t-mobile google g2, created goldcard, rooted, custom recovery, new radio and custom rom.
a few details:
device HTC Hero (T-Mobile Google G2, the black one )
rom Salsasense RC2 (at the moment...)
recovery CWM 2.0.5.7 (think so, but im sure i got the latest)
sd 2gb
ooookay, tried to edit existing salsasense, resulting in non-functional rom rebooting into recovery.
JieeHD may you probably cook Rosie.apk and HtcClockWidget3d.apk in SalsaSense RC2 and upload it just for testing? much better would be to give me the keys to do it myself *still learning*
i tried it but the situation above occured^^ maybe some md5 thingy?
greets, SOD
SummonerOfDeath said:
ooookay, tried to edit existing salsasense, resulting in non-functional rom rebooting into recovery.
JieeHD may you probably cook Rosie.apk and HtcClockWidget3d.apk in SalsaSense RC2 and upload it just for testing? much better would be to give me the keys to do it myself *still learning*
i tried it but the situation above occured^^ maybe some md5 thingy?
greets, SOD
Click to expand...
Click to collapse
Fixed your update-script, new line for each command is needed
/facepalm
JieeHD said:
Fixed your update-script, new line for each command is needed
/facepalm
Click to expand...
Click to collapse
not serious no? /facepalm -.-" thanks will try that right now xD will give feedback if my device is still alive afterwards xDD
greets, S.O.D.
How's your progress going?
I messed around with the files 2 from the treat and they won't flash error 0. Tried to fix that with.different binery and gave me error 7. If you can make at least the king lockscreen with weather app working than you are the man
Sent from my HTC Hero using XDA App
stroobach said:
How's your progress going?
I messed around with the files 2 from the treat and they won't flash error 0. Tried to fix that with.different binery and gave me error 7. If you can make at least the king lockscreen with weather app working than you are the man
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
brick after flashing modified rom.
push to /system/app didnt work.
flashing restarts recovery.
jieehd's tip of single lines for every command doesnt work, same as above.
error 0 = apk is not made for your device/rom, wont install.
error 7.. dunno, think its not matching binary or parsing error.
files from my thread? as post above says one is a log and the other is defect^^
i doubt weather will work as its eating HUGE amount of resources. if u want this lockscreen, maybe try salsasense, has got a 3.0 alike lock...
holidays now, wish good luck in coding would be happy if u found a solution
greets, SOD
were can i find HTCG2/hboot/PC10IMG.zip been looking all over for it and its no were to be find
Got some questions.
1. You want WHAT? And what is the purpose?
2. In how far is this related to this topic?
3. If u give us a path to this file, why do u ask where it is? Maybe try dowloAding some random rom (probably some ruu) and do extract & search..
4. Are you really willing to contribute to this topic? I dont see the point of posting this.
5. Obey forum rules. If u have got a question, post it directly in q&a section, not in some random topic or directly explain the connection to the actual topic.
Greets, s.o.d.
agnostic900rr said:
I dunno, no idea
Click to expand...
Click to collapse
what don't you know? may we help you? whats the purpose of all these posts?
i think i'll give it a last try next time wenn i got salsa sense installed and either find a solution instantly or give it up, as noone is willing to support me and i can't do much more with my poor coding skills.
seems like we have to admit that hero's dying and i have to wait for my contract to end so i get a new phone.
greets, s.o.d.
Hello everybody
I need a little help to a friend of mine who mistakenly deleted systemui.apk from the system using root permissions on his Transformer Prime
Now the system doesn't boot up, it gets stuck when reaches the ASUS mark.
So if anyone can show me a way to get back to the stock firmware, that'd be much appreciated. The device is rooted.
I've Searched the forums for a solution but found nothing that directly gives me a solution
Thank you.
if you plug it into the cpu does it come up?
I have a similar problem that I just posted. I renamed my /system/bin folder by accident and I'm stuck on Eee Pad screen too. Been looking and trying data wipe, n reset, nothing so far. Need to know if there is a way to access the file system b/c all I have to do is change the name of a damn folder. Sounds like you just need to copy n paste the missing file too.
This will require setting up your computer - drivers & ADB environment - and pushing some commands to your tablet that way ... I would think. Since we have no unlocked bootloader you can't boot into recovery.
Yeah, you're going to have to adb push the systemui.apk to /system/app
But that's only is you can even get adb to recognize your device while it's in the bootloop.... When I pushed my de-odexed framework folder and rebooted, I got stuck in endless bootloop, and the device wouldn't get to the point where adb would be able to see my device, therefore I couldn't push anything.
Also tired to put the ASUS recovery blob .13 .zip file on my micro sd card (since I couldn't access my main /sdcard on the Prime... that still didn't work... Long story short, Amazon is replacing my Prime, b/c it just stopped working ... now I just have to wait 4-6 weeks until they get new ones in stock (hopefully they get them sooner than that).
So Can any one of you guys get me these two filse from his Transformer prime
systemui.apk
systemui.opex
At least it is worth the try.
Replacing the Tablet is not an option because the guy shipped his tablet to another country it would be very painful to try to send it back to amazon.
Hi everyone, I accidentally my systemui.apk. Is this safe?
Loljk, you should be able to get it working i hope.
Sent from my tablet thing with XDA Premium.
jdeoxys said:
Hi everyone, I accidentally my systemui.apk. Is this safe?
Loljk, you should be able to get it working i hope.
Sent from my tablet thing with XDA Premium.
Click to expand...
Click to collapse
I am sorry i don't quite get what you mean ?
DELETED SymstemUI for ASUS Memopad 8
Hi,
I DELETED SymstemUI for ASUS Memopad 8 but I was able to save a backup in the external MicroSD card of my tab. Is there anyway that I can push this back to the system?
I'm still a noob and I am hoping that there's anyone who can help me.
ok so im running some more tests and decided to take a different path for dual boot (for testing anyway, still gonna give it a go with bmp)... so to make a long story short, how do I edit the .bct file that comes with the nvflash zip??? I can edit the .cfg just fine but when I add my secondary partitions at the end of the line up and before UDB, the g2x doesnt seem to boot, like it just stays at the first lg logo and goes no further. I need access to the file to make it kick over. I think. Anyone have any ideas? Ive not been able to find out how to edit the file.. although I've not looked 110% as I usually do.. This time i'm asking the good folks here at xda to see whats up.
Im not even sure if I've named them right.. but hte way I see it they are all 3 characters in length.. so ive made the secondaries called APS, CAS, & UDS.. that also maybe my issue. but none the less ive attached a screen cap to show they were made and where they fall in the lineup.
Anyone got an idea that will help me?
Ok so then if no one knows.. is it possible to edit this file when compiling a build??? I've not compiled a build yet so Idk... I'm currently clearing room out of win7 to give way for more room on Ubuntu ...
Sent from my LG-P999 using xda premium
Hello there,
I just registered on this forum to hopefully resolve my problem with the Kobo Arc tablet. I apologize if any similar issue regarding this was posted. So basically, my Uncle bought me a Kobo Arc tablet about 2 months ago and I know quite alot of things about it. Due to my stupidity I couldn't play a game I really wanted to and so I edited my build.prop to make my tablet compatible with the game. In build.prop I changed the product model to: "GT-I9100", product brand to: "Samsung" and product manufacture to: "unknown". After this I restarted my device. As I did, the kobo arc logo appeared and then a never ending start-up boot. I restarted my device many times but still couldn't get my device to fully on. I entered recovery mode by holding the up volume and power button together and tried to reset to factory, but my Kobo Arc just still won't go pass the never ending start-up screen. I even tried to connect it to my computer but it doesn't recognize it. I'm assuming it's bricked, is there any possible fix for this? if so I need to know asap.
Someone please help me, it would be so kind, and I'll appreciate it soo much.
Thanks in advance
SmootZ
Please, I'm in urgent need of help. I really want to go on my tablet again..
Any help to get my kobo arc to its original state and working properly again, I would be sooo grateful.
Do you have a nandroid backup? If so, restore it.
Otherwise, do you still have access to your SD card (probably using an adapter and connecting it to your PC)? Try using AROMA FM to edit build.prop to the original values.
If not, I'd suggest installing ADB (GIYF) and using that to edit build.prop.
For the last two solutions, you'll need to use the shell, and use a text editor such as nano, pico or vi (depending on what's available). BTW, how did you edit build.prop?
You can also flash back stock/any ROM. Restoring to factory settings doesn't restore build.prop AFAIK.
EDIT: Just noticed your PC doesn't recognize your phone. That rules out solution #3. Are you sure the required drivers installed on your PC?
Yes, I'm sure. But when I plug my tablet into my PC through my usb cable it makes a noise connoting its connected but it won't appear.
Could you possibly give me instructions on how to do a nandroid back-up or something that will get my device back with the following condition:
-My device not able to be recognized on my computer
EDIT: When I connect my device to my computer it charges, but it won't appear on my computer or anything, if this helps.
It's too late to make a nandroid backup now. Try using AROMA FM.
GermainZ said:
It's too late to make a nandroid backup now. Try using AROMA FM.
Click to expand...
Click to collapse
Could you possible give any instructions, I'm kinda new to this stuff.
SmootZ said:
Could you possible give any instructions, I'm kinda new to this stuff.
Click to expand...
Click to collapse
Click the link I posted.
Read the first few posts in full.
Ask about the specific part you don't understand.
I cannot even access my device apart from putting it in recovery mode since my device gets stuck at the start-up and loops, In addition I don't know how to access my sd card since my computer doesn't recognize my device as I said. Will this be a problem?and can I still do it?How do I access my sd card?
Sorry if this question seems stupid
Is your device still not detected in recovery mode?
To access your SD card directly from your PC you'll need a special reader/adapter.
Nope, it doesn't recognize it even in recovery mode. What is this "special" reader/adapter and where can I get it? Could you provide me a link or something?
Well, I'm out of ideas. Just Google "SD card adapter".
Actually my device does not offer any external memory card slot. Meaning There is no support for MicroSD or SD cards on my Kobo Arc.
What shall I do now?
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
SmootZ said:
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
Click to expand...
Click to collapse
I'm out of ideas you could try yourself. I'd try triple checking the drivers on your PC and see if you can get ADB to work.
Is sending your tablet to repair an option?
EDIT: Can't you update to the latest update using fastboot?
Hey.
First of all, messing with build.prop without backup wasn't the brightest idea in your life, but crap happens, like Forrest Gump used to say.
What is the exact model of your tablet? Kobo Arc? Kobo Arc 10 HD? Maybe Kobo released an update and you can update it directly by fastboot.
If not try to use Linux as it handles ADB much better than Windows, go to system and edit you build.prop back and wipe cache and dalvik cache. You need to have a working ADB to even think about reversing your changes.
Good luck.
Well thanks for the help.
Can I try taking this adb method without my device giving permissions for USB debugging? Since I haven't enabled this in my developer options as far as I know, in addition I cannot really check since my device is bricked but I'm 100% sure it's NOT enabled. Will this stop me from carrying an ADB method?
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...