Related
Hi
I am trying to install the Jellybean 4.1.1 ROM on my rooted Nexus S.
The history of my attempts so far are here: Rooted Nexus S OTA Upgrade to 4.1 http://forum.xda-developers.com/showthread.php?t=1833420
I have downloaded the "image-soju-jro03e.zip" form the Android open source website, and used the Nexus Root Toolkit to install it.
This failed, and I attempted to install the image using ROM Manager.
This also failed, and produced a lengthy Recovery Log.
I have read through it and it seems to be telling me that certain files or folders are missing from the download.
e.g can't open /dev/tty0: No such file or directory
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
can't find /sd-ext in /etc/fstab
Is that what this means?
How can I correct it?
The full log is here: https://docs.google.com/document/d/1HWeYsXPnppQbgoloz72RH81E8a479LBmvYXIlzYPETo/edit
S
Help with recovery log
Hello?
Can anyone help me to understand this recovery log?
Should I direct my question to the "ROM Manager" people?
I have tried without success to install JB 4.1.1 from the Google Android Images page, and I think it must because something is missing from the file structure of my current ROM.
Am I on the right track?
M S
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
new hope
nightsky87 said:
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
Click to expand...
Click to collapse
Hello nightsky ( is that like, "nice guy",?) thanks for taking a look.
My phone is a Nexus S i9020, no suffix.
It is running Andriod 4.0.4 ICS. It is "rooted" and "unlocked".
I have Clockwork Mod v.6.0.1.0. Superuser v.3.1.3. and ROM Manager v.5.0.2.0.
I have tried over and over again without success to upgrade to JB 4.1.1 and I am getting sick and tired of this stupid game.
I would be happy to just stick with ICS 4.0.4, but every week, the phone tells me that an "update is available", and I have to dismiss the message every time I look at the phone! When I tried to apply the update It used to crash, requiring a battery-pull reset. Now I have CWM it takes over and says "failed to verify file signature", "install untrusted package?"
If I press on and install, it fails and the android is on its back with a red triangle on its belly.
If you look at the posts I have linked to, I have been on a steep learning curve regarding ROM flashing, and I understand the basic idea, its just that when I follow the instructions given on the forum, It doesn't happen that way for me and I suspect that there is something wrong with the file structure on my phone. That is why I have posted the link to my recovery log.
If you can help, please reply.
I have had a look at the "Random Phantasmogoria" site that you recommend, is it offering anything different than the Google developers site https://developers.google.com/android/nexus/images that I have downlooaded my image from?
MS
another version!
PS I have just had a look at the Google Dev. site and there appears to be a new version of 4.1.1 called JRO03L.
My next attempt, I'll try that.
MS
goodnight
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
jus to add on the post above. the instruction to install the factory images are on the same page where you downloaded the image in question.
and there is something to be wary of : flashing the factory image will WIPE the phone CLEAN (except what's on the usb storage o/c).
albundy2010 said:
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
Click to expand...
Click to collapse
Smashing buttons and hoping something works?
That's not very nice, or fair!
If you take the trouble to read my post, and the linked previous posts, you will see that I am trying my best to follow the instructions given on this forum, where I hoped to find knowledgeable professionals who contribute their valuable time free of charge to help noobs like me.
So far I have followed the instructions, only to get something other than the result described. This is why I am asking for your help to understand the recovery log, so that I can work out for myself what went wrong, and what I should change next time to get it right.
At this point in the journey I am still unsure about backup. I have "backed up" using the nexus root tool kit, which is a Nandroid back up, and I have "backed up" using ROM manager, but Titanium Back-Up does not recognise the backups and wants me to "back up" some more. After all this is over will I be able to clear out all the dross that my phone memory is accruing? Is there any point backing up Apps like "Google Earth" when I can easily download them from the Play Store after I have my new OS? etc... etc...
Anyway, I am going to try again, this time with the new JRO03L image, and this time I shall do it Command Line style instead of the "one click crap", as you recommend, my friend. I'll let you know how I get on.
MS
There is now a super thread over here with this root information and some more recoveries. I plan on expanding as more things are developed for the Rugby Pro.
I have added other hacks to this thread below the root download links. Enjoy.
The below guide outlines how to gain root on the Samsung Galaxy Rugby Pro (SGH-I547 ATT / Bell (Yes, Canada works!) / commanche). Please read through the full guide before attempting to root your device.
You will need ODIN v3.04 in order to gain root on the Rugby Pro (comanche), I will not post a link due to the nature of the package. Google has plenty of links for it.
BIG thanks to utkanos for all the help and making this a reality
Install instructions -- goldenlederhosen has provided some further information and detail about the below procedure here
Please read his post as well as the instructions before attempting this procedure
Install drivers from link below
Download necessary packages (clockwork recovery, root update) from the links below
Copy root update to your devices sdcard(s) -- Copy to both if external SD card is present
Charge phone to at least 80%
Power off the phone
Unplug from USB / Charger
Boot into download mode (Home + Volume Down + Power)
When asked if you want to continue, press Volume Up to enter download mode
Plugin phone and
Launch ODIN
Check the checkbox next to "PDA"
Click the PDA button
Select the comanche_cwr_6015_utkanos.tar.md5 file
Make sure only "Auto Reboot" and "F. Reset Time" are selected
Click start
Your phone will reboot one the flash is complete
You now have Clockwork Recovery, continue with the steps to get root
Power off your phone
Unplug from USB / Charger
Boot into Clockwork Recovery (Home + Volume Up + Power -- Release when Samsung logo appears)
Select "Install zip from sd card"
Select "Choose zip from sd card"
Navigate to zip
Select zip
Confirm
Reboot
You should now have root
I am not responsible for anything bad that comes to your device when using the information posted in this thread. Everything here is dangerous, may cause a brick, will void a warranty and has the potential to just plain wreak havoc. Do not complain you followed my instructions and met with a dead device. Consider yourself warned
I've tested to the best of my ability, but I am one person with one device, I cannot catch all potential failure modes. If you find a problem and a fix, or have information that should be added let me know and I will update the necessary information.
Download Links
Head over to the super thread here (link) for links.
CWR Touch / ODIN
Courtesy of childrenofthehorn there is a now a Clockwork Recovery Touch and ODIN images for the ATT varient. The thread is: http://forum.xda-developers.com/showthread.php?t=1990519
Rootz Wiki Forum
childrenofthehorn has gotten a dedicated forum setup over at Rootz Wiki. Check it out: http://rootzwiki.com/forum/556-galax...o-development/
Works like a charm!
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.
dweide9 said:
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.
Click to expand...
Click to collapse
Thank you much for the donation
Would you be willing to pull an image of the stock boot partition (dd if=/dev/block/mmcblk0p7) and PM me a link?
Also: check the OP, I've added some info on how to get tethering (after rooting) without the need for a dedicated ATT tethering plan.
re: post-root stuff
>Would you be willing to pull an image of the stock boot partition (dd >if=/dev/block/mmcblk0p7) and PM me a link?
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
>Also: check the OP, I've added some info on how to get tethering (after rooting) without >the need for a dedicated ATT tethering plan.
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?
dweide9 said:
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
Click to expand...
Click to collapse
You can copy the contents of boot by:
Install a terminal emulator from the market
Launch terminal
su
Accept request for root
dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/mmcblk0p7_boot.img
Transfer mmcblk0p7_boot.img to your favorite cloud storage provider
Share link
If you run into trouble or have any questions let me know.
dweide9 said:
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?
Click to expand...
Click to collapse
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Sent from my SAMSUNG-SGH-I547 using Tapatalk 2
boot partition image
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
So what fun stuff can you do with this file & how would my image be any different then yours? Or is it another issue, like uploading being restricted because you're a developer?
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.
kemonine96 said:
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Click to expand...
Click to collapse
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.
dweide9 said:
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
Click to expand...
Click to collapse
Thanks for the file. I just finished pulling it.
dweide9 said:
So what fun stuff can you do with this file
Click to expand...
Click to collapse
I plan on using a stock boot image so I can put together an ODIN image that will flash the phone back to a stock state. If you root your phone or have a custom recovery / system / boot OTA updates will generally fail to apply. The best way to get an OTA update applied is to rollback to stock and install the OTA.
dweide9 said:
how would my image be any different then yours?
Or is it another issue, like uploading being restricted because you're a developer?
Click to expand...
Click to collapse
The boot partition should be the same across devices unless you make modifications.
I had to blindly update the boot partition on my device to get root, so I do not have an un-changed copy of it. In order to get an OTA update applied and to work with some Cyanogen / Clockwork Recovery stuff I will need a clean boot partition image.
dweide9 said:
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.
Click to expand...
Click to collapse
I worked with a few people to get help putting together an ODIN image that allowed me to get custom recovery and the clockwork recovery update.zip. There is no general guide on the steps necessary.
If you are interested in diving into the custom rom / recovery stuff I will be doing some work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully working on a Cyanogenmod 10 (JellyBean) port in the future. I am working on some items for the Rugby Smart (apache) at present, as soon as that stuff is taken care of I'll be focusing more on the Rugby Pro (commanche). If you are interested in taking a shot at updating the clockwork recovery for the commanche let me know and I can maybe point you in a few directions to get you going.
stuff
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.
dweide9 said:
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
Click to expand...
Click to collapse
I pulled that package as well. Unfortunately it is only the GPL components they are required to release, not the full ROM sources. It does contain the kernel sources which will be very helpful down the line.
dweide9 said:
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Click to expand...
Click to collapse
There is a lot of testing work and guess/check for the ROM building stuff. I was thinking of setting up an IRC channel on FreeNode for discussing work on the device. Would you be interested / willing to move some of the interactive discussion over there once I have a channel setup?
dweide9 said:
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.
Click to expand...
Click to collapse
Keep me in the loop. I tend to only tether for the purpose of my tablet when I'm not near a WiFi AP. I wanted to point it out just in case, better to have it working before it's necessary.
Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.
IRC channel on FreeNode is setup: #rugby-pro-dev for those that are interested.
Motorhead1991 said:
Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.
Click to expand...
Click to collapse
I think we should be covered at the moment. The first priority will likely be getting a recovery nailed down and 100% before working on a customized kernel. I'm hoping to get recovery nailed sooner than later so we can do things like nandroid and similar before starting in on CM10 or another ROM.
I am also working on the Rugby Smart (apache) CM9/3.0 Kernel/CM10 stuff as well so my time with the Pro is limited at the moment. Hopefully the Smart stuff moves quickly so I can loop back around to the Pro quickly.
>I pulled that package as well. Unfortunately it is only the GPL components they are >required to release, not the full ROM sources.
Ah, learn something new every day.
>I was thinking of setting up an IRC channel on FreeNode for discussing work on the >device. Would you be interested / willing to move some of the interactive discussion >over there once I have a channel setup?
Sure, I already monitor #opennic on freenode, so I can just open another channel.
kemonine96 said:
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.
Click to expand...
Click to collapse
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."
MCKINLEC said:
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."
Click to expand...
Click to collapse
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?
kemonine96 said:
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?
Click to expand...
Click to collapse
Thanks, but I made a backup copy, Think the issue could be because it was deleted instead of frozen?
ETA, help, donation etc
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
@kemonine96 et.al.:
When do you think a beta CM port will be ready?
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....
goldenlederhosen said:
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
Click to expand...
Click to collapse
You are not alone in that sentiment. I won't run a device I know won't receive a CyanogenMod port. The good news is as long as there is root, CyanogenMod can be made to work.
goldenlederhosen said:
When do you think a beta CM port will be ready?
Click to expand...
Click to collapse
"Soon". Myself and a couple others are working on a set of changes for the Rugby Smart (predecessor to the Pro) and once they are further along I will be looking into starting the CyanogenMod port for the Pro.
goldenlederhosen said:
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Click to expand...
Click to collapse
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
goldenlederhosen said:
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....
Click to expand...
Click to collapse
As much as I may appreciate a donation, please hold off as I cannot commit to working on CyanogenMod for the Pro in a paid capacity I am comfortable with. I am working 50-60 hour work weeks at my day job so my free time is severely limited. I have every intention on bringing CyanogenMod to the Pro but it is a free time problem more than anything else.
Foreign anglopu
kemonine96 said:
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
Click to expand...
Click to collapse
Okay, will do.
Below you will find instructions how to root this device.
The following procedure has been tested up to firmware J120AUCU2APJ2
KNOX should remain 0x0
However you undertake this at your own risk.
Issues:
Wifi passwords not remembered (fix below)
Stock Flashlight app not working.
Model number may be missing from build.prop (fix below)
Instructions
1. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_J120A_PG1
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Download the ENG_BOOT_J120A_PG1.tar to your PC and add it to AP / PDA in ODIN.
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
2. Install and run Kingroot:
http://www.apkmirror.com/apk/kingro...-release/kingroot-5-0-5-android-apk-download/
You may need to run Kingroot several times to gain successful root.
3. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
Alternative (free) method to replace Kingroot:
Follow Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Don't flash the boot partition with Flashfire, uncheck.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware. Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
4. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
5. To fix “Unauthorized actions have been detected”
disable 'security log agent'
6. Model number missing fix:
http://www.techgainer.com/change-fake-android-device-model-number-and-brand-name/
Enjoy your rooted device
To recover from a soft brick flash the firmware below.
https://firmwarefile.com/samsung-sm-j120a
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Still no TWRP, though, right?
fbueller said:
Still no TWRP, though, right?
Click to expand...
Click to collapse
Not possible I'm afraid.
ashyx said:
Not possible I'm afraid.
Click to expand...
Click to collapse
As ashyx mentioned in a previous post, Flashfire works. Loaded Xposed for Samsung via the Wa?? version.
spicybeansandricey, to clarify, Wanam is a modified version of Xposed for Samsung phones. Google is my friend, Google is your friend and Google is our friend. If you Googled it, you will find links to the same/similar packages linked by ashyx to get Xposed on Samsung phones. Since I was skimming the articles and successfully installed on a 4" screen, I wasn't sure about the name but only remembered the first 2 letters. In fact, the tutorial I followed was different from ashyx's post and gave no credit to XDA.
As an addendum, Flashfire works great and was able to back up EFS files. I just chose to backup EVERYTHING since I don't know what I will need later. My 128GB sd card cost more than the phone! LOL As for my vacation reading list and Google, I still have to read up on new superuser and root that can survive OTAs and root detection.
shirleys143 said:
Flashfire works. Loaded Xposed for Samsung via the Wa?? version.
Click to expand...
Click to collapse
Yeh flash fire is pretty much the next best thing to custom recovery with a few little tricks of its own.
Anyone have a list of garbage that can be safely removed? Even after stripping some of the obvious stuff there's over 4Gb of system stuff.
Can I remove the Samsung stuff like Galaxy Apps and such? I don't want to remove anything that will make it unstable so that I can still reset it back to fresh and begin over, but without the bloat ware of that makes sense?
ViralThread said:
Anyone have a list of garbage that can be safely removed? Even after stripping some of the obvious stuff there's over 4Gb of system stuff.
Can I remove the Samsung stuff like Galaxy Apps and such? I don't want to remove anything that will make it unstable so that I can still reset it back to fresh and begin over, but without the bloat ware of that makes sense?
Click to expand...
Click to collapse
No matter how much you remove from system the size will never change, it's rather a pointless exercise. All you're doing is creating unused space.
ashyx said:
Yeh flash fire is pretty much the next best thing to custom recovery with a few little tricks of its own.
Click to expand...
Click to collapse
SO i tried to flash xposed via flashfire and got the old "system software not authorized by at&t has been found on your phone..." brick.
How to get xposed on there without bricking?
ashyx said:
No matter how much you remove from system the size will never change, it's rather a pointless exercise. All you're doing is creating unused space.
Click to expand...
Click to collapse
So what's the point of rooting? The primary reason was to remove the bloat and recover some usable space on the device. Out of 8GB there's less than 3gb of usable storage on it rendering it mostly useless for anything but a media player or emulator box loading crap off the SDCard.
What a waste.
ViralThread said:
So what's the point of rooting? The primary reason was to remove the bloat and recover some usable space on the device. Out of 8GB there's less than 3gb of usable storage on it rendering it mostly useless for anything but a media player or emulator box loading crap off the SDCard.
What a waste.
Click to expand...
Click to collapse
Rooting is about more than debloating. It's about having control over your device.
Why don't you use adoptable storage if you need more space?
You can always move user apps to system to take up the space you've created. There are plenty of apps that can do this such as system app remover. That way not only do you utilise that space but you also free up storage space.
spicybeansandricey said:
SO i tried to flash xposed via flashfire and got the old "system software not authorized by at&t has been found on your phone..." brick.
How to get xposed on there without bricking?
Click to expand...
Click to collapse
How do you class a message, which is easily removed, as a brick?
ashyx said:
Rooting is about more than debloating. It's about having control over your device.
Why don't you use adoptable storage if you need more space?
You can always move user apps to system to take up the space you've created. There are plenty of apps that can do this such as system app remover. That way not only do you utilise that space but you also free up storage space.
Click to expand...
Click to collapse
Adoptable storage is useless. Most of the apps will not see it and refuse to install data there, making it impossible to install anything large on the device or more than a few small apps/games.
I hadn't considered moving installed apps to system space I will give system app removed a glance. Thx
ashyx said:
How do you class a message, which is easily removed, as a brick?
Click to expand...
Click to collapse
i just asked how to install xposed on there, who cares about what i feel is a brick or not. a brick, soft or hard is still a brick.
is there a way to get xposed on the j120a without custom recovery? i tried flashfire, maybe my setting were incorrect? do you have a method?
thanks in advance.
spicybeansandricey said:
i just asked how to install xposed on there, who cares about what i feel is a brick or not. a brick, soft or hard is still a brick.
is there a way to get xposed on the j120a without custom recovery? i tried flashfire, maybe my setting were incorrect? do you have a method?
thanks in advance.
Click to expand...
Click to collapse
Yes there is, but due to your attitude sort yourself out. I honestly don't know why I bother sometimes with this forum.
ashyx said:
Yes there is, but due to your attitude sort yourself out. I honestly don't know why I bother sometimes with this forum.
Click to expand...
Click to collapse
thats kind of harsh considering i just asked for instructions on how to get xposed on my phone. instead of helping you wanted to put me down for not using the word "brick" in a manner thats acceptable to you.
im sorry that we dont agree on semantics. i really have no "attitude" and how one can attribute an attitude to text on a website is debatable at best.
I have no ill-will, malice, or attitude, i had a general question that i was asking about and was looking to someone who looked like they had the answer for it. Normally, i "sort" these things out myself, but i went against my better judgement and asked here...(hence my 2 reply post history.)
if you can help me, i would gladly reward you for your time, via bitcoin, etc; I honestly have no issue other than i dont have the time to sit and look into this stuff like i use to 4-5 years ago. I promise you, i have no sort of attitude. this is just a forum FFS, and above all else, im not an 'ingrate.' i am always appreciative for any help that i receive.
If you could find the will to help me i would greatly appreciate it, otherwise lets not part ways with any ill-will, that's the last thing that i would ever want to happen.
thanks again for your time.
Ok so here's what my experience with system app remover was, and I hope I wasn't sounding rude or unappreciative, Immsimply trying to work towards a certain endpoint solution if possible.
System app remover did not permit me to relocate user apps into system space, in fact it won't let me move any apps as it claims "sdcard share the same disk with os", both in "move to phone" and in "move to sdcard" options.
Is there any reliable way to install apps directly to the external SDCard? Maybe install them to internal storage and then manually move them and symlink them? That wouldn't work for large apps but might allow installation of more smaller apps?
Essentially what you've stated means even the system is on its own "partition" right? So as I remove stuff that's stored in the /system folder, it's freeing space but not space my Android can access for the purpose of installation ?
Is that a proper summary of my situation?
Thanks in advance
spicybeansandricey said:
thats kind of harsh considering i just asked for instructions on how to get xposed on my phone. instead of helping you wanted to put me down for not using the word "brick" in a manner thats acceptable to you.
im sorry that we dont agree on semantics. i really have no "attitude" and how one can attribute an attitude to text on a website is debatable at best.
I have no ill-will, malice, or attitude, i had a general question that i was asking about and was looking to someone who looked like they had the answer for it. Normally, i "sort" these things out myself, but i went against my better judgement and asked here...(hence my 2 reply post history.)
if you can help me, i would gladly reward you for your time, via bitcoin, etc; I honestly have no issue other than i dont have the time to sit and look into this stuff like i use to 4-5 years ago. I promise you, i have no sort of attitude. this is just a forum FFS, and above all else, im not an 'ingrate.' i am always appreciative for any help that i receive.
If you could find the will to help me i would greatly appreciate it, otherwise lets not part ways with any ill-will, that's the last thing that i would ever want to happen.
thanks again for your time.
Click to expand...
Click to collapse
OK, let's start again. Maybe I mistook your response, it just seemed a little snipey. To get help in the right direction, proper details of what the actual issue is goes a long way to obtaining the solution. Stating a message caused a brick isn't anything I've ever come across before which is why I asked the question? However it seems further to that post you actually meant Xposed caused the brick after you saw that message and rebooted.
So going back to what I previously stated about correct details, here we are 3 unnecessary posts later.
Moving on...to install Xposed you need to ensure you use the wanam build of Xposed.
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
.
ashyx said:
OK, let's start again. Maybe I mistook your response, it just seemed a little snipey. To get help in the right direction, proper details of what the actual issue is goes a long way to obtaining the solution. Stating a message caused a brick isn't anything I've ever come across before which is why I asked the question? However it seems further to that post you actually meant Xposed caused the brick after you saw that message and rebooted.
So going back to what I previously stated about correct details, here we are 3 unnecessary posts later.
Moving on...to install Xposed you need to ensure you use the wanam build of Xposed.
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
.
Click to expand...
Click to collapse
thank you so much!! that was what the "wa???" was in the first few post of this thread that i didnt understand. i sincerely was not trying to come off as pompous, snipey etc; so thank you for helping me. I run a vbulletin forum myself so im no stranger to miscommunication.
I appreciate your help, honestly and sincerely. ill give this a try and be back, my sincerest thanks again.
ViralThread said:
Ok so here's what my experience with system app remover was, and I hope I wasn't sounding rude or unappreciative, Immsimply trying to work towards a certain endpoint solution if possible.
System app remover did not permit me to relocate user apps into system space, in fact it won't let me move any apps as it claims "sdcard share the same disk with os", both in "move to phone" and in "move to sdcard" options.
Is there any reliable way to install apps directly to the external SDCard? Maybe install them to internal storage and then manually move them and symlink them? That wouldn't work for large apps but might allow installation of more smaller apps?
Essentially what you've stated means even the system is on its own "partition" right? So as I remove stuff that's stored in the /system folder, it's freeing space but not space my Android can access for the purpose of installation ?
Is that a proper summary of my situation?
Thanks in advance
Click to expand...
Click to collapse
Whoops, my bad. That's was the wrong app to suggest. I actually meant this one that DOES move user apps to system. You can see the mistake with the similar names!
https://www.google.co.uk/url?sa=t&s...CBowAA&usg=AFQjCNFe58rupOZgD6hS3UfXr-2rkHxsyQ[/url]
By the way I suggest this busybox:
https://www.google.co.uk/url?sa=t&s...CB8wAg&usg=AFQjCNGS1LQ2kB8PZ4Y--lzVTOG1SKQWvA
ashyx said:
Whoops, my bad. That's was the wrong app to suggest. I actually meant this one that DOES move user apps to system. You can see the mistake with the similar names!
https://www.google.co.uk/url?sa=t&s...CBowAA&usg=AFQjCNFe58rupOZgD6hS3UfXr-2rkHxsyQ[/url]
By the way I suggest this busybox:
https://www.google.co.uk/url?sa=t&s...CB8wAg&usg=AFQjCNGS1LQ2kB8PZ4Y--lzVTOG1SKQWvA
Click to expand...
Click to collapse
Thanks for the quick response.
I installed /system/app/remover and it seemed to offer a solution. However upon moving few apps to system with the app, it's merely removing them. So more tweaking needed.
Will keep update on progress.
Thanks again
---------- Post added at 03:53 PM ---------- Previous post was at 03:29 PM ----------
Is it safe to remove all of the Samsung stuff? Will that break the reset ability?
Hi,
Since a few days I'm unable to see any data in my phone via gallery or file manager or any application, and I'm unable to save any data to internal storage. (example: I'm able to use whatsapp for texting, but I can't receive/send any audio/picture and I can't access the old ones).
And I keep getting this error message:"com.android.providers.media.MediaApplication keeps stopping."
I don't know if that's what causing it or if that's just a consequence of not being able to access internal storage.
I can still see all the used storage from settings though.
Phone has unlocked bootloader, but no root/custom rom/recovery.
I saw other Oneplus users started getting the same error these days... (I have a Oneplus 6, but others have different models like Oneplus Nord).
Someone resolved by wiping system and they were able to retrieve storage content and functionality, but they lost apps data, I'm trying to find another way since I have an unlocked bootloader.
A user on stackoverflow suggested I should clean the com.android.providers.media.MediaApplication app data to regenerate the database, but I couldn't figure out how to do it
I tried cleaning media and media.module packages (not media.MediaApplication) from adb but no luck even if successful.
I tried removing "com.android.providers.media" (not media.MediaApplication, I couldn't find that one) folder from data/data with twrp file manager but no luck...
Is there a way to specifically clean "com.android.providers.media.MediaApplication"?
If anyone has any other suggestion on things to try, post it here please.
Have you modified any system settings recently? Or might be just some unorganized drivers.
Conect pc and make bakup your stuff...
Then on settings make Factory Reset...
Zxalilh said:
Have you modified any system settings recently? Or might be just some unorganized drivers.
Click to expand...
Click to collapse
Not at all... I never did any modding, and I saw it happened to people that were completely stock as well
Mord0rr said:
Conect pc and make bakup your stuff...
Then on settings make Factory Reset...
Click to expand...
Click to collapse
I wanted to try to avoid that route...
0xCuter said:
Not at all... I never did any modding, and I saw it happened to people that were completely stock as well
Click to expand...
Click to collapse
Maybe it's just a common error, you could search it up on youtube but I guess you will have to backup and reset your device
Zxalilh said:
Maybe it's just a common error, you could search it up on youtube but I guess you will have to backup and reset your device
Click to expand...
Click to collapse
I already looked everywhere but there is not much about it other than other users that are having the same issue
0xCuter said:
I already looked everywhere but there is not much about it other than other users that are having the same issue
Click to expand...
Click to collapse
Try this?
Zxalilh said:
Try this?
Click to expand...
Click to collapse
Already tried... didn't work unfortunately
You need to flash a fila called "SdcardFixPermissions-singed" and will be work again
anhenrique said:
You need to flash a fila called "SdcardFixPermissions-singed" and will be work again
Click to expand...
Click to collapse
Did you have the same problem or is it just speculation? I don't to want to break more stuff...
0xCuter said:
Did you have the same problem or is it just speculation? I don't to want to break more stuff...
Click to expand...
Click to collapse
I had the same problem, and this is how I solved it. But it's your own risk.
anhenrique said:
I had the same problem, and this is how I solved it. But it's your own risk.
Click to expand...
Click to collapse
Sorry, I see your message only now... Do you remember when did you have this problem? And was it this exact message on a Oneplus 6?
I have the problem of not being able to save anything in the storage or having a broken zip, always after using msmtool 10.3.5, I saw it in a post here about this file and it solved.
[SCRIPT/FIX] Internal sdcard permissions (/data/media/)
This should be applicable to any ROM on devices which share internal storage for applications and the internal "sdcard" (Note II, SGS3, probably others). Symptoms may include inability to take screenshots and other failures, and will usually show...
forum.xda-developers.com
the file was developed by a senior member and recognized @osm0sis
Hi, first of all, thank you for reading me.
I think i messed up big time.
I had Havoc OS 4.1 installed since more than a year and it was kinda messy e.g. the sim card card wasnt recognized anymore so wasnt able to make calls because i played to much in the settings.
Having some stupid but incredibly addictive games on this smartphone i decided to keep it like this and since i'm a complete n00bs and being afraid of security risk of rooting my device i never rooted it.
Big mistake.
So, recently, one games needed an update (like they all do at least once a week) and since i'm anti-google/f***book (no comment please) i nvever saved my progress in the cloud and "that" game required absolutely an update.
I installed the update from an alternative apk source and , (applause if you want and laugh), it screwed up the game.
Now the nightmare begin.
Since the device isnt rooted i made a backup of /data partition. Gone crazy and before i might explode in an uncontrollable fury and madness i used LMSA to rescue the phone. And myself, lol.
Now i have stock android and i am googled to the bone. My butt hurts. My head too.
THE (first) simple question is : how can i restore this backup because i have the error 255?
Notes and observations; logically i would say because the device is back with stock rom and doesnt have the same os/rom installed and/or the partition and whatever is not the same wich may explain the error 255.
SECOND QUESTION: can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
I know i have to give as much information possible but i dont what else to give. If you need logs, or everything else just say it nicely and i will give it to you with immense pleasure.
Oh yeah, model : XT2113-2 5g Kiev RETCA 128gb a/b type and maybe was crypted before because twrp asked me the password to make backup or else.
Thank you in advance and i really hope somebody would help, if not i just loosed 1.5 years of stupid gaming because i messed up like an idiot. (A lesson well learned, the hard way...)
Thank you so much for not answering this simple question.
Kerplunk83 said:
Thank you so much for not answering this simple question.
Click to expand...
Click to collapse
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
Finally a sign of life from someone here.
Thank you sd_shadow
sd_shadow said:
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
Click to expand...
Click to collapse
These precious brief and concise 2 lines of a simple answer is immensely welcomed.
Wich point me to reply that to my knowledge i interpret it as a security chip with big chances that its in relation to the knox technology.
It also point me to ask WHY, if i cant back up because of that, why/how is it possible to install a custom rom or gsi (sorry i still dont make the difference because i dont understand it) on this very protected smartphone?
That must explain why i had problems trying to root it and fail each time.
Finally i think that i should use another device for android gaming since i dont want to depend on f***book and google.
Thanks again sd_shadow. Even if it was a very simple answer it enlightens me alot.
Note: sorry for my bad english.
Kerplunk83 said:
how can i restore this backup because i have the error 255?
Click to expand...
Click to collapse
This error code means that at some point your backup of /data could not be extracted further. But for more detailed infos you must provide a recovery.log which will be generated when doing a backup of e.g. /boot.
>>> Please DO NOT copy+paste it here!! <<<Rename it (recovery.log > recovery.log.txt) to be able to upload it within "Attach files".
Kerplunk83 said:
can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
Click to expand...
Click to collapse
Yes, use Titanium Backup (TB). Although it's very outdated it still features a restore of single apps out of a TWRP backup. Here's how you do it:
1. IMPORTANT: TB will only search for TWRP backup files on internal storage!! Use the default path created by TWRP, e.g.: /sdcard/TWRP/BACKUPS/ZY322V8K28/2023-04-08--06-53-20/
2. Install and open Titanium Backup.
3. In the upper right corner tap
MENU > scroll down to "Extract from Nandroid backup" > choose your backup folder
##############
Notes:
- Usually a TWRP backup of /data consists of several parts (data.ext4.win000, ~win001, ~win002 etc). TB requires all of them (or at least those ones with the /data/data/ path inside).
- If you are facing this error message:
Could not find any data in this TWRP backup
then your TWRP backup is compressed with gzip. To decompress it you must rename the file
data.ext4.win001 > data.ext4.win001.gz
and extract it with any archiver tool, e.g.:
- ZArchiver (Android)
- 7zip (Windows)
- Problems finding any TWRP backup data with Titanium Backup? Then please check your path!! (see above section)
Good luck!!
Thank you very much WoKoschekk i'll do it as soon i'll have the time for since i'm working today.
Thank you so much again, i'll keep you posted with logs and such.
I'm sorry i didnt gave news since, i'm not doing very well.
there's those 2 question i still have in my head;
1-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Ultimately, how can i be rooted if there's a chip preventing me to do so?
I'll keep you posted when i'll be of better health, thank you.
Kerplunk83 said:
-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
Click to expand...
Click to collapse
TWRP backup = *.tar archive
TB unpacks the needed app's data and nothing else. You must be rooted to have access on /data for restoring your apps. But for the backup process it doesn't matter if you were rooted. Root is part of your boot.img.
Kerplunk83 said:
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Click to expand...
Click to collapse
TB is for free. But a paid version unlocks additional features (not related to the TWRP restoring feature).
And yes... root is mandatory for TB. As I said before you must have r/w access on /data/*.
Kerplunk83 said:
if there's a chip preventing me to do so?
Click to expand...
Click to collapse
Which chip?? You already have root access via TWRP. Magisk is only needed in system and just a patched boot.img (custom kernel).
Get well soon!
WoKoschekk thank you for this insanely fast reply.
All those answers and infos have now a gigantic value for me, if only i knew that before.
To describe a bit more my situation i slept only few hours since 5 days, vomiting, heavy coughs and fever.
I'm sure i'm not supposed to but i will anyway, i engage myself and promise to reward you (in particular) and others for the help you're bringing me. It wont be much but very important to me.
I'll go try to get (again) some rest. Just before i go, why was there a mention about my device;
"
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
"
I dont ask you (WoKoschekk) or other to explain in the most explicit and endless details of what is exactly this "chip" and all the history that goes with it cause i dont want to be a pain but just why it was mentionned. Only, why?, it has ben mentionned.
I cant wait to get better since i finally see possibilities to get back those files.
Have a nice week-end and thanks again.
@Kerplunk83 To reveal the mystery behind "the chip": Motorola released two variants (Snapdragon/Mediatek CPU) of this model. Since the CPU largely determines the system structure, building a functional TWRP for both of them is very challenging. It seems that TWRP for the SD's variant got some bugs while the MT's variant runs more smooth. Due to this fact the error 255 is caused by something that you weren't be able to fix.
Regarding your problem: To restore an app and its specific app data you need the proper permissions to write in /data/data and /data/app. For this permissions you either need TWRP or Magisk installed. TWRP seems to be unable to write in that specific directory. On the other hand you don't want to install Magisk. I'm sorry but with this setup your problem can't be fixed.
Just out of curiosity, could you provide me a recovery.log showing error 255 during the restore process?
Please DO NOT copy/paste the whole log and post it here!! Instead of this you should rename the file (recovery.log => recovery.txt) because a file called *.log isn't allowed for upload. But a *.txt file is.
Options to create a recovery.log:
1. adb pull /tmp/recovery.log
=> copies a recovery.log into your ADB/fastboot folder
2. Do a backup of sth. like "boot" because the backup process will create a recovery.log by default
3. TWRP mainscreen > advanced > create log (kernel log isn't needed here)
=> log is stored on the default storage (internal or external) that you have choosen for backups etc.