I've been working on my framework-res.apk lately, but haven't tried pushing it yet. I know (most of) how to do the procedure, but i want to be sure before i try. If i screw up, i'll be without a phone for a few days due to my current internet connection. (No, i don't want to wait )
What i know, is that i should modify the apk with 7-Zip, replace the graphics i intended (mostly statusbar icons). I don't have to sign the apk since i'm pushing it trough adb shell, and my rom (V10e) is already rooted. The commands for pushing it from adb shell are simply as follows:
Code:
adb push framework-res.apk /system/framework
I have the three following questins that google can't seem to answer for me:
1. Should i wipe dalvik cache (or anything else) after i push the framework-res.apk?
2. If the answer to the previous question is yes, then can i wipe dalvik cache without a custom bootloader?
3. Does anybody have any experience with doing this to the V10e rom? According to google, a lot of users seem to have problems with apps force closing after doing this, even though it's only graphics that has been replaced. However, this is on random handsets, not P-970...
hulkhaugen said:
1. Should i wipe dalvik cache (or anything else) after i push the framework-res.apk?
2. If the answer to the previous question is yes, then can i wipe dalvik cache without a custom bootloader?
3. Does anybody have any experience with doing this to the V10e rom? According to google, a lot of users seem to have problems with apps force closing after doing this, even though it's only graphics that has been replaced. However, this is on random handsets, not P-970...
Click to expand...
Click to collapse
1.you don't have to wipe dalvik cache,just reboot
2.
3.to avoid fc,you should backup your original framework-res.apk,if you face fc,just push the original one back.
Well thanks for your reply
I just found out something stupid. I don't have access to WiFi atm, nor 3g, so i downloaded ClockworkMOD.apk and recovery-clockwork-5.0.2.6-p970.img, figured i could install it manually. So i started CWM, and tapped Reboot into recovery...nope, should note have done that, lol. When it started up, i got a huge error label, with LG security error as a subtitle to that. Now my phone won't start. After that message, my phone proceeds to boot, but stops at the LG logo. Tried removing the battery and start it up again, but same thing happens again, LG saying Error, lol in YOUR FACE to me, and gets locked in booting... Well, suppose i'll be without a phone for a few days...
hulkhaugen said:
Well thanks for your reply
I just found out something stupid. I don't have access to WiFi atm, nor 3g, so i downloaded ClockworkMOD.apk and recovery-clockwork-5.0.2.6-p970.img, figured i could install it manually. So i started CWM, and tapped Reboot into recovery...nope, should note have done that, lol. When it started up, i got a huge error label, with LG security error as a subtitle to that. Now my phone won't start. After that message, my phone proceeds to boot, but stops at the LG logo. Tried removing the battery and start it up again, but same thing happens again, LG saying Error, lol in YOUR FACE to me, and gets locked in booting... Well, suppose i'll be without a phone for a few days...
Click to expand...
Click to collapse
Ilko's package contained CWM I believe, installing via command with single click. Do you have a nandroid? Install v20a, chinese one via smartflash (no net connection needed). Install CWM (UPK) then restore nandroid.
Problem is if you don't have them. It's good to save these files for future troubleshooting.
Edit: my bad, sorry. You don't have CWM before. So no nandroid.
Nope, no nandroid. Recently unbricked my phone using LG software. My current internet connection is to slow to start up LGMobile update, lol. I'll be home in about 32 hrs (i hope, i'm far offshore atm). Guess i won't be able to do anything until then. I'll look into the framework-res.apk then, hehe. Merry x-mas
Thread moved
Questions belong here, not in development, until something is actually developed.
Do i need busybox?
Related
This one is pretty straight forward...Especially if you haven't done much modding to your
phone.
If you're stock or close to, you can probably just move the update to the phone sd and use stock recovery to apply update, and you're good to go. If you are already rooted try the OTA RootKeeper app, hopefully it'll work for you. being that it seems to be hit & miss, i'm guessing it didn't work for people that had issues updating, but will work for those whose update goes smooth.
I on the other hand had already rooted and did the GSM hack on mine so I ran into a few issues that I've others have been having too.
Probably the biggest and most common are "system 7" errors. I've realized you get these when the update checks and finds that ICS files have changed, are frozen, gone, etc. and it's a bit harder to diagnose because it keeps changing depending on what's wrong.
For example it had a code then something else and it referrenced my STK.apk file, then I realized when I did the GSM hack I renamed those to Stk.apk.bak & stk.odex.bak as recommended. So I fixed those & tried update again.
Failed this time at build.prop, yep another GSM mod, but I didn't back-up or save orig settings, so I had to find a bionic ICS build.prop and replace it. found it here (will update with link asap).
Tried again, IIRC, this is the time it worked, but only booted to animation loop. This sucked. Tried to use House of Bionic to fix, couldn't get it to work, but ended finding a fix using recovory "AP Fastboot" had to use pc CMD to reinstall preinstall.img & system.img from the HoB ICS FXZ file.
Look HERE. Thanks to ERIC for this, he gives you everything you need. He's also responsible for dead battery workaround I put below.
When you do this, you can't boot phone back up but you can go into stock recovery & re-apply update from sd on your phone. It wipes everything tho, so if you used OTA RootKeeper, it's gone. But you get phone back.
Bottom line...MAKE BACK-ups or save everything you've changed.
If you've heavily modded things on your phone it might be more worth it (easier) to back up & save what you can as far as apps & personal stuff then redo ICS stock, Maybe root & use OTA RootKeeper here, tho I've heard this doesn't always work either (the OTA part), then apply JB update. then re-install / apply what you were able to save / back-up.
So in hindsight I would guess modding anything within the system is what gives you the "system 7" error, and depending on what you did, or maybe someone you bought the phone from already rooted & modded, it can take you all day to fix / replace those files, just do the reflash of the (2) img files & call it a day. This way you can probably avoid the boot loop issue too.
One other thing about the boot loop one...if you wait & wait & wait like I did it KILLS your battery, and you won't be able to use Fastboot.
IF THIS HAPPENS...find an old phone charger or DC plug, like for your computer, clip off the end and line up the positive & negative connections on the battery then push it into the phone so the wires are touching the phone connections too. Be careful what it's putting out tho, I found I had one that the output was 6 (watts i believe) and 300 mah. It worked the trick just fine. you don't want anything to high as you don't want to burn up any circuits. most USB plug phone chargers go around 5 (watts) I believe. just FYI.
Hope this helps someone.
Cheers.
Hi all,
I have been hammering away at this one, and putting it on the back-burner, but now, it is really getting to me. Samsung Galaxy Tab Pro 10.1 SM-T520
It has been rooted with ODIN, and shows no problem, (things seem much easier now, as I have re-jigged lots of my old phones using so many more tools, I am not an expert, but can read and search without too much problems) I was very careful to choose the correct file, CF-Auto-Root-picassowifi-picassowifixx-smt520.zip, I have rechecked this step several times, as most of the instructions I found ODIN device ID:COM box should become yellow, when on newer versions it is blue I think, I wondered if I was going mad,
Root Checker Root access granted, all fine. I have Root access. n.
Installed CWM ,latest recovery for a Pro 10.1 wifi, recovery 6.0.3.1 Titanium backup-ed, all ready to go and Reboot and flash a new ROM.. No joy. .. Installed TWRP , same.
When it re-starts it ,shows the galaxy logo, flashes off, then back on, and then fails. Android dead with a red warning , standard recovery KOT49H.T520XXUANAE, all I can do is the usual options:apply update. The only thing I haven't tried is to just wipe all the data. I have a backup of my apps with Titanium Backup on the SD card,I am not that bothered really about much other data if its a pain. I just want control of my device and to try a new ,cleaner ROM(SMT520_GraveD_V3.0)
This has been bothering me for ages, I have read so many posts so am now getting really frustrated I have bought triangle away app. today although I think I sorted that issue early on anyway , but just in case...
Super SU seemed to have vanished so that is back installed
I think I searched and found the Mount/system issue and looked into an issue that lead me to the .system folder, but it is hidden, so I could not find the file it related to. I dont have the specifics to hand as I checked it out at work. I wondered if it is because I have ES file manager, not ASTRO as it said in some of the posts I found.but sure this is a red herring.
I have tried everything..I have a Mac at home and PC at work, I have tried ADB and can see &restart the device etc... so I am connected, first I got the error that it didn't recognise the sideload command. Read up on ADB , looked at the help etc. sideload isn't there as a command, very confusing. But I think I got there one I figured out paths, as of course they are different on a Mac, and possibly more so as I have 2 drives in it, which often confuses me ..grr.
I can of course get into the bootloader, with ON+VOL -, it tells me so far the system is : Official and Knox Warranty Void: 1 which I think is fine, but a chap at work suspected this, but after lots of threads I gather this is normal..
Sorry if long, just thought I should be as clear as possible. I have not really come across such an awkward issue as this , my HTC One was a breeze:crying:
*edit* Just worked out through trial and error, that to use the sideboot command I had to select send via ADB and now with the path /Desktop/SMT520_GraveD_V3.0.zip I was able to send the file but with the following messgae : E:footer is wrong and E:signature verification failed, twice.. So some progress
Thanks !
Just to say after being up waay too long on this, I discovered there is a newer firmware T520XXUANI1_T520BTUANI1_BTU which I may aswell upgrade to first, but of course I cannot do this OTA now As it recognises the device is 'tampered with' *sigh* so gun and games with Odin for Mac tonight, or JODIN3 , just to get the firmware upgrade(which seems to be a jungle of fake download links). before a Rom without bloatware..
I am also not completely clear why, as from another thread about KNOX, as I am basically running stock , without custom recovery.. According to this thread , but I am getting a bit confused now
http://forum.xda-developers.com/gal...neral/knox-warranty-void1-otas-t2996067/page2
Click to expand...
Click to collapse
however this is another story from the ROM install. Apologies
Well. No replies, but I did eventually solve this. Hopefully this can help someone. I am a tinkerer, but I really nearly gave up on this..But this was a cheap second hand tablet ( my first) and I want to see what it can do before I test drive one on my mother who is having nightmares with every Windows laptop I give her!
Once I got to a PC , I had access to Odin3, although it is not available online (apparently to Mac) I could not get it to work due to Java issues (JOdin3 online - brilliant idea but no joy for me so far)
I had the Rom I wanted ( GraveDigger- SMT520_GraveD_V3.0.zip ), the firmware update (T520XXUAOD2_T520BTUAOB1_BTU.zip(i think)) and the unlock file (CF-Auto-Root-picassowifi-picassowifixx-smt520.zip) , non of which I could install in any way , due to being locked out of using a custom Rom bootloader!
At this point I factory reset and cleared the cache( as that is the only options in the basic bootloader!) I also has ADB on the PC so attempted to install the files this way (after messing about using some software to produce the .tar and .md5 files needed for Odin. I tried everything to get this into proper 'bootloader mode' all from scrach again, including trying the adb oem unlockbootloader command, which I would never get to work as I could not get there!
With Odin, I was also again able to flash the firmware update, eventually, and of course had to unlock again. I was curious if I could now use the OTA update, and could not. At some point, in repeating this process( as I think it hung up several times and needed a hard reboot) I had at this point fully wiped the device as I know that is another reason to have glitches and an unstable ROM later.
I think I then tried to check and although T520XXUAOD2 seems to still be the firmware, at some point I managed to get online ( I think some superuser app which I have had to try several may have notified me that KNOX was reset:laugh:When I go to About>Software update it said I had the latest update! Good news!
At this point I had installed both CWM and TWRP again , and thought I would try TWRP.I had tried CWM and the same problem, like a double flash of the Samsung Logo , so I know it had reset !!
THIS TIME I used TWRP ( I thought of trying CWM touch, but its either paid, or I would have to find and ABD the file over I guess) , I managed to re-apply the Root file, Root checker confirmed this , as it had throughout this ordeal!, although apart from ACCESS GRANTED I dont really know what the rest means..Anyway although picassowifi , was still in Device name on TWRP I chose an earlier recovery version to install.- twp-2.7.0.0-picassowifi.img. When I re-booted, I was able to get the TWRP recover image, and install the ROM, I cannot remember if I re-rooted as I was so elated.
I had a few , freezing moments, reinstalling most of my apps through Titanium Backup, I think I just tried to reinstall everything which of was unnecessary, after a hard reset, all seems fine. I checked and the TWRP recovery seems to have stuck. I am not entirely sure how to check about the firmware , but for now I feel this is progress.
Good Luck if anyone found this any use.
Just to add, when you search this ( and probably many other models) you seem to get so many sites, offering exactly the same unlock information, in exactly the same way, many of the downloads seem to take you to many weird and wonderful places. So I tended to look here for downloads if possible. But I had to join SamMobile (which seems a useful site for the firmware upgrade) and trawl all over and assume similarities between other Samsung devices to fully check I was not being an idiot. But this was very odd and I could not find any posts or other workarounds that I did not try. But this new ROM feels lovely and smooth so far, and I now want to look into this tablet further
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
iFran72 said:
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
Click to expand...
Click to collapse
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
9
Revontheus said:
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
Click to expand...
Click to collapse
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
petterssonjohan said:
9
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
Click to expand...
Click to collapse
If you can enter flash mode, flash the latest firmware and software for your device using flash tool.
What is flash mode? I can get the phone in a mode where the indicator lamp turns blue is it that?
get Flashtool @ https://xperiafirmware.com/flashtool/
it includes Xperiafirm so you can download a stock ROM for your device and build an .ftf file
when you have the ftf file, drag it into the main Flashtool window
follow prompts
Hello all. I Recently attempted rooting my phone, running on 5.0.2, and it seemed to have worked. But then after attempting to use SuperSU to add root permissions to an app, my screen went black, and the only thing visible was the top status bar, which had some animations still running (Like the battery icon filling up or the signal bars changing), but thats it. It wasn't responsive to any of my button presses, and then it shut off. It keeps doing this over and over, and i cant keep the phone on for more than 5 mins maybe 10. How would I fix this? I used this "tutorial". - andromods .com/news-root/lg-g3-g-flex-2-g2-lollipop-one-click.html - (Stupid thing wont let me post links)
I would like to solve this without factory resetting, as I have apps that have data on them that needs to be transferred from one phone to another, and i dont have a second phone to transfer to at the moment.
Thanks in advance.
As far as I know, flashing kdz with LG Flash Tool following the tutorial to "unroot" won't delete your data, but you will lose root, of course. If you don't have custom recovery nor root, there is little else you can do. Do you have adb root (shell)? If yes you can try re-flashing system partition...
lfom said:
As far as I know, flashing kdz with LG Flash Tool following the tutorial to "unroot" won't delete your data, but you will lose root, of course. If you don't have custom recovery nor root, there is little else you can do. Do you have adb root (shell)? If yes you can try re-flashing system partition...
Click to expand...
Click to collapse
I'm very new to this, and probably shouldnt have attempted this without knowing more, so I have no idea what you are asking me. What is ADB root (shell)? I probably dont have it. And I didnt do any sort of custom recovery. But it seems that me messing around with SuperSU (clicking the uninstall root/turning of superuser once or twice) seems to have stopped the crashing all together. Ive been using my phone since and it hasnt crashed. Whether or not that's fixed the real issue, I don't know. And I'm not sure I want to mess with it further. :crying:
I have uninstalled a system app that I shouldn't have (something to do with network conectivity according to the recovery log) and everything was fine until I updated my device. I hadn't restarted it since removing the system app but after tyhe update it will no longer go past the Samsung galaxy logo. I remember doing something similar to either this device or another and I remember that I was abler to get into the system enough to be able to reinstall the neccessary app and fix the problem. However, this time I cannot get into adb at all. adb won't show any devices when in recovery, download mode, or at any of the three stages of the boot screen. I have tried wiping the cache and everything but factory resetting it as I have data that I can't lose. Any help would be appreciated whether getting adb install-existing to work or to pull important files off of the device before a reset. The device runs android 12 not rooted.
(...)
Go back via odin to the original firmware including the correct BIT.
(...)
Flash in Odin using home CSC file, simple
You only need to run ADB in Windows PC terminal or DOS mode in order to Odin flash firmware. No need to run ADB commands in the phone.
Just be sure that you install the "Samsung ADB Driver" into your PC before
you try Odin flashing firmware.
Just be sure you download the proper firmware for your phone.
Good luck, have a great day and have fun!
Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode. From here, the phone goes through the initial setup screens but all data is still intact, just not apps. Concerningly, it doesn't ask for you to enter your password, it just puts you on the homescreen, which seems bad from a privacy perspective as any samsung repair tech can easily cause the phone to boot loop. From here, you can back up anything important and factory reset. There is no way to exit safe mode once you've gotten this far.
I don't remember why odin didn't work, it may have been that I couldn't get the firmware to download as Samsung likes to change that stuff all the time or it may not have reinstalled the system app neccessary.
I should've been more clear in the original post but I have not flashed any unofficial firmware just the U1 firmware to remove carrier bloat, but that was way before this occurred. In case it wasn't clear, the problem happened because through
Code:
adb shell uninstall --user 0 package.name
an important system app was removed (something network related) which caused android to crash when trying to start the service. In short: be careful what you remove when using adb and, for all you forum members: read the whole post instead of jumping to conclusions about the user's mistake and if it isn't clear, ask for more details. Again, thank you to all the helpful comments even if they didn't end up working.
ZenDeveloper said:
Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode.
Click to expand...
Click to collapse
May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.
Thanks
hatoxda said:
May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.
Thanks
Click to expand...
Click to collapse
Sorry for the late reply,
I don't know how many times it needs to reboot to go into safe mode but it seemed like quite a bit maybe 20-30 times possibly like 100. But once it does it'll go through the initial setup screens and let you in without a password. It's very important to backup everything on your device before you mess with any system apps or update especially if you've previously messed with system apps. I however don't use google hence I didn't have a backup of anything and needed to get it off before hand.
It could also be possible that Samsung removed this back door in android 13 and just the act of trying to update it gets rid of it. I don't know I'm just throwing around ideas.
Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be! Firmware upgrades/updates can and do break Samsung's.