• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory
Search This thread

immortalneo

Senior Member
Jan 25, 2011
4,425
1,941
Malappuram, Kerala
There are a lot of people joining XDA on a daily basis, and there are a lot of repetitive questions being asked
which clutter up the Development and 'Q & A' threads. Point them here. Feel free to ask or answer questions.

The idea of this thread is to get users to help other users with their problems/questions. People are usually
ridiculed for asking questions that other people deem stupid even though it may be a legitimate question. This
leads to new users being afraid to ask questions!

Only provide well mannered help towards users in this thread. Please do not spoon feed, but rather point in
the direction where that user can find an answer
and educate himself. If you don't want to answer, at least
point out where to find the answer.



Before posting anything, I strongly advise you to read THIS thread.

Then, have a quick look at the names of threads in Post No. 2, you might find what you need right away.

Third. Even if you do get your question answered, please do come back and read threads in Post No. 2
(coming later as soon as we start getting the guides) to educate yourself. You'll be surprised how much time
and frustration it will save you in the future!



No abuse towards noobs tolerated here! That means:
NO TROLLING
NO NAME CALLING
NO RIDICULING
NO FLAMING


ASK ANY QUESTION HERE! No question is stupid or irrelevant in this thread. You will either get an answer or will get pointed in the right direction.


*A Special Thanks to mark manning for his help in creating this thread*


HALL OF FAME

People who contributed most to this thread and helped countless number of people with their
problems/questions. In no particular order.

Bruce Wayne
post-mortem
SilentStrider
Ghostfreak NB
mayank9856
sgs22012
Zatta
ADDICT.ANK



These people also have the right to use the banner below:
Newbie%20Thread%20Sign.gif


Just add this code to your signature:
HTML:
[URL="http://forum.xda-developers.com/showthread.php?t=2257421"][IMG]https://dl.dropboxusercontent.com/u/41066660/Newbie%20Thread%20Sign.gif[/IMG][/URL]
 
Last edited:

Cubicalspy_

New member
May 18, 2021
2
0
There are many non-popular devices out there from which probably you won't find much, the best bet would be searching devices with some coincidences that already were rooted i.e. looking at the same processor (not needed exact) being SD, MTK, etc., Android version and probably the most important first thing; if device have an unlockable bootloader or there is some method to unlock it.
One-Click methods are not recommendable so you would get more issues trying to fix unexpected results, also there are two more things to consider at this point, those methods stopped to working either at all or properly in android versions superior than MM (from what I know) and the fact that bootloader has to be unlocked to accept some change.

For the rest, if you can get the stock firmware, you should try the Magisk method.
I am now trying to do it first on the xcover 4 I had laying around with magisk.
 

SubwayChamp

Senior Member
Aug 6, 2016
2,787
1
1,265
Phone: Note 20 Ultra (N986)

So I got twrp installed--3.5.2. Everything is running smoothly--up until I need to restore a back up. I get this message:

"cannot restore System -- mounted read only."

I've googled up and down on how to resolve this issue, and almost all of them recommend unticking the read only option in "Mount". That problem is: that option ISN'T there for me.

Does anyone have any insight into this?
Check if you missed something in the process for the first installation, most of times is required to swipe to allow modifications in the first screen and formatting data will get access to more partitions, additional steps actually are required too like flash the vbmeta image but it could be an issue that not all TWRP can do that and as Samsung devices don't have access to fastboot is a stop in the end of the way. Check what role plays here MTP to allow backup/restore success too.
Hi. On a zuk Z2 pro with arrow os 10(full ROM, not gsi) fresh install.
Instagram videos playback are corrupt jagged very noisy and messy.
Any fix ?
It could be an error strictly related with the ROM itself but generally speaking the first time you flash something is always recommendable do it through a fresh install but restoring from a previous backup sometimes we are doing the same cycling error as it were a dirty flash I mean, re-do the process from a clean flash and don't restore nothing specially if it is a major update, for the rest it could be an issue ROM/developer related.
 

hash02

Senior Member
Jul 7, 2016
57
5
Check if you missed something in the process for the first installation, most of times is required to swipe to allow modifications in the first screen and formatting data will get access to more partitions, additional steps actually are required too like flash the vbmeta image but it could be an issue that not all TWRP can do that and as Samsung devices don't have access to fastboot is a stop in the end of the way. Check what role plays here MTP to allow backup/restore success too.

It could be an error strictly related with the ROM itself but generally speaking the first time you flash something is always recommendable do it through a fresh install but restoring from a previous backup sometimes we are doing the same cycling error as it were a dirty flash I mean, re-do the process from a clean flash and don't restore nothing specially if it is a major update, for the rest it could be an issue ROM/developer related.
Previous ROM was pyxisOS. Had it for almost a year. Worked fine up to a few months ago. 2 days ago I wanted to upgrade so I tried several, decided to stay on arrowos. Both android 10. Same problem. Clean flash. Totally clean, wiped all from twrp. Your suggestion didn't help unfortunately.
 

FindingShrek

New member
Apr 6, 2021
4
0
23
Philippines

My 64GB Samsung evo Plus Sd Card reduce to 27GB..

  • I've tried all method to retrieve/format to NTFS​
  • I also try format bto NTFS, unhide partition/show partition using cmd​
  • Tried EasUs Partition Recovery​
And its still only show 27GB....
I It's oringinal I think...
I have proof
I've once get it back to original size but suddenly it come back again at 27GB...
It started when I put it on Nintendo Switch Lite with only capable of reading 32GB SD Card..
 

Attachments

  • IMG_20210412_131436.jpg
    IMG_20210412_131436.jpg
    1 MB · Views: 13
  • P_20180621_222033_LL.jpg
    P_20180621_222033_LL.jpg
    1.1 MB · Views: 11
  • SD CARD 02.png
    SD CARD 02.png
    85.4 KB · Views: 11
  • Screenshot_20190619-184058.jpg
    Screenshot_20190619-184058.jpg
    378.4 KB · Views: 9
  • SD CARD 01.png
    SD CARD 01.png
    81.4 KB · Views: 9
  • SD Card 05.png
    SD Card 05.png
    653.6 KB · Views: 9
  • SD Card 03.png
    SD Card 03.png
    624.7 KB · Views: 8
  • SD Card 04.png
    SD Card 04.png
    630.1 KB · Views: 9
  • SD Card 06.png
    SD Card 06.png
    652.8 KB · Views: 9
  • SD Card 07.png
    SD Card 07.png
    70.1 KB · Views: 10
  • SD CARD.png
    SD CARD.png
    81.7 KB · Views: 12

int_i

New member
May 24, 2021
2
0
I'm having trouble getting the whatsapp keyfile w/o rooting (warranty, so I don't want to root). I've tried backing it up (no longer works - there's an option to prevent a full backup of an app. tried installing an old version from before the android OS allowed it - doesn't work due to a bug. Tried using APK easy to change android manifest - the app recognizes it's been modified and won't let me confirm my phone number to generate the keyfile).

my final idea: in whatsapp web, under the browser's local storage, a variable called WASecretBundle exists, containing the entries encKey and macKey. I could recreate the keyfile from that, probably.
problem: I do not know what the format of the keyfile is actually. So no clue how to translate from the content of WASecretBundle into a keyfile. Tried figuring it out from python scripts taking the file to decode megastore, no success. Couldn't find anything online about the format of the keyfile. Asked around, no one has a rooted phone I can use to figure it out.

Any alternative ways to get my keyfile? or, if someone's going to compare their own keyfile to the whatsapp web to tell me the file format, remember not to post your actual encryption keys. use a placeholder!

thanks in vance!
 

SubwayChamp

Senior Member
Aug 6, 2016
2,787
1
1,265
Previous ROM was pyxisOS. Had it for almost a year. Worked fine up to a few months ago. 2 days ago I wanted to upgrade so I tried several, decided to stay on arrowos. Both android 10. Same problem. Clean flash. Totally clean, wiped all from twrp. Your suggestion didn't help unfortunately.
If it is not an issue related with the ROM then you could flash the stock ROM again as a base or if it is available/provided the firmware zip and from there flash again the custom ROM you are in.
 

MarsBars77

Member
May 24, 2021
7
0
Can Someone help me Please?

I tried to install twrp on my phone(Samsung Galaxy A20s-(A207F/DS) following this tutorial:(https://www.androidaddicts.online/i...n-android-phones-samsung-included-using-odin/).

I entered download mode and on odin it said flash was successful after i tried to reboot my phone i was stuck in bootloop of download mode.Now i'm in a different screen where it says:Secure Check fail:recovery.img.Here's a link to the image:Error Message

How do i fix this and is my phone done for?
 

Arc android

Senior Member
Jan 28, 2021
332
171
India 🇮🇳
Can Someone help me Please?

I tried to install twrp on my phone(Samsung Galaxy A20s-(A207F/DS) following this tutorial:(https://www.androidaddicts.online/i...n-android-phones-samsung-included-using-odin/).

I entered download mode and on odin it said flash was successful after i tried to reboot my phone i was stuck in bootloop of download mode.Now i'm in a different screen where it says:Secure Check fail:recovery.img.Here's a link to the image:Error Message

How do i fix this and is my phone done for?
Seems like there was some kind of restriction to flash anything on your phone. And now I think only Samsung can help you.
 
Can Someone help me Please?

I tried to install twrp on my phone(Samsung Galaxy A20s-(A207F/DS) following this tutorial:(https://www.androidaddicts.online/i...n-android-phones-samsung-included-using-odin/).

I entered download mode and on odin it said flash was successful after i tried to reboot my phone i was stuck in bootloop of download mode.Now i'm in a different screen where it says:Secure Check fail:recovery.img.Here's a link to the image:Error Message

How do i fix this and is my phone done for?
You're going to have to use Odin to flash back your stock ROM. Your recovery is secure and your boot image is secure. Until it is not you cannot flash a custom recovery. Your only option is to flash back to the exact firm where you were on or if it does not exist the newest version of your firmware that does.
 
  • Like
Reactions: Arc android

SubwayChamp

Senior Member
Aug 6, 2016
2,787
1
1,265
Can Someone help me Please?

I tried to install twrp on my phone(Samsung Galaxy A20s-(A207F/DS) following this tutorial:(https://www.androidaddicts.online/i...n-android-phones-samsung-included-using-odin/).

I entered download mode and on odin it said flash was successful after i tried to reboot my phone i was stuck in bootloop of download mode.Now i'm in a different screen where it says:Secure Check fail:recovery.img.Here's a link to the image:Error Message

How do i fix this and is my phone done for?
Just adding more info hoping that for the next you search for safest information. The guide you followed is not suitable for your device, the new A series have a step more in the process to unlock bootloader, prior to switch to download mode and proceed to flash anything you have to boot to a kind of bootloader screen mode when you will have prompted to allow the OEM unlock and you have to complete/confirm it.
Assuming that you didn't messed even worse and flashed it the recovery for S8.
 

Arc android

Senior Member
Jan 28, 2021
332
171
India 🇮🇳
You're going to have to use Odin to flash back your stock ROM. Your recovery is secure and your boot image is secure. Until it is not you cannot flash a custom recovery. Your only option is to flash back to the exact firm where you were on or if it does not exist the newest version of your firmware that does.
But he'll need a custom recovery to wipe the current ROM, won't he ??? You can't flash stock ROM over earlier rom, right ???
 

IceWing_mk1

Member
May 25, 2021
7
1
I'm crossposting this from the Moto G Power thread. Hoping maybe my problem(s) aren't unique to my model of phone and this may get some more eyes on it.

Ok, I'm stumped and I need help.

Last time I rooted a phone, it was our old HTC Thunderbolts... Things have changed significantly since then, or so it would appear.

Trying to fix my wife's phone after a Verizon OTA update seems to have jumped her phone from Android 10 to 11, and in the process nerfed the hotspot (which we need, as we're rural with no landline broadband available)

I'm working on a Moto G Power (sofia XT2041-4), bought late last year off the shelf from Best Buy.

Home PC is a Windows 10 box. I do not have a linux environment available to me.

So, here's where I'm at in the last 48 hours.
  • I have gone in and gotten the unlock key from motorola, and successfully undone the OEM Lock. (I know this is the case because it tells me I'm an idiot and I should lock it, every time it boots up now). This also managed to wipe the phone, which, oops, read to the end of the paragraph BEFORE unlocking and deleting pictures of the grandkids which came in since the last backup.
  • Somehow last night, I managed to get it to be a brick, but used LMSA to unbrick it, but that version is still the OTA updated Android 11, so same problem with the hotspot.
  • I have installed the Android SDK, newest motorola drivers, and also the standalone 'Minimal ADB and Fastboot' on my PC
  • I've managed to get TWRP installed in the recovery portion of the phone.
  • Following this video, I managed to bring TWRP up, wiped the device, then copied the Lineage OS image to the microSD card, as well as Open GApps.
  • When I try to install the LinageOS (17.1), it looks like it's installing, goes through steps 1 and 2, then a slew of error messages in the log.
  • I've got the 4 image files I pulled out of one of the LineageOS zip files (Boot, Product, System, VBMeta) in the 'Minimal ADB and Fastboot' directory.
  • I can run 'fastboot flash boot boot.img' from the 'Minimal ADB and Fastboot' directory and it succeeds.
  • When I try to run Product, System or VBMeta in the same way (cmdline = fastboot flash product product.img), all of them fail the Preflash Validation and it comes back with 'FAILED (remote failure)'
Things I'm not sure about
  • First, I'm pretty sure I'm not in FastbootD. I don't see a big red FASTBOOTD at the top, and according to this thread, means I'm not in it.
  • I think FASTBOOTD should be something I'm interacting with on the Moto G Power, but for the life of me, I can't figure out how to get to it.
I feel like I've got to be CLOSE to getting this thing working, but damned if I can seem to cross the finish line.

Help?

Edit: I'm redownloading the image into LMSA since apparently getting one of four images onto a phone stops it from booting successfully and my trying to use LMSA to get the linageOS onto the phone messed up the zip file.
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,406
5,117
Sydney
But he'll need a custom recovery to wipe the current ROM, won't he ??? You can't flash stock ROM over earlier rom, right ???
On my previous phones (ie not this specific phone), the flashable firmware included total wipes. On my pixel 4a, it also has an option when flashing stock, to wipe. Thats specifically the data, but stock firmware should include a flash of all the partitions (with the optional wipe of data). I thoink the manufacturers sede it as a way to return a damaged device (ie a any and all corrupt partitions) to a working device. When I upgrade a device, I am flashing stock over stock, andon some[previous devices, I have done the same downgrading the firmware.ie using ODIN or fastboot and not a custom recovery. Flashing stock normally overwrites the custom recovery, so you may be in a chicken-egg scenario if that was the case.
 

IceWing_mk1

Member
May 25, 2021
7
1
Ok, so, I've solved SOME of the problems I've run into as I tried to reimage...

Now I've got a Moto G Power (2020) where I believe I have successfully loaded the new images (Resurrection Remix), and yet, when I get to the end of the instructions and try to reboot, I just keep ending up at the bootloader (Fastboot Flash Mode, NOT FastBootD, just the normal one with the green droid opened up for repairs)

I've tried going into the following options:
  1. Start - comes right back to the same screen
  2. Restart Bootloader - Same Screen
  3. Recovery mode, and it says 'No Command'
  4. Power Off - goes down, when I power it up, same screen
  5. Bootloader Logs - says "AP Fastboot Flash Mode (Secure) Fastboot Reason: Reboot mode said to fastboot"
I've also tried this with and without a USB cable attached.

How do I smack this thing and get it out of the endless loop it's stuck in? And WHAT did I do to cause this loop?
 

Arc android

Senior Member
Jan 28, 2021
332
171
India 🇮🇳
On my previous phones (ie not this specific phone), the flashable firmware included total wipes. On my pixel 4a, it also has an option when flashing stock, to wipe. Thats specifically the data, but stock firmware should include a flash of all the partitions (with the optional wipe of data). I thoink the manufacturers sede it as a way to return a damaged device (ie a any and all corrupt partitions) to a working device. When I upgrade a device, I am flashing stock over stock, andon some[previous devices, I have done the same downgrading the firmware.ie using ODIN or fastboot and not a custom recovery. Flashing stock normally overwrites the custom recovery, so you may be in a chicken-egg scenario if that was the case.
If it worked for you, maybe it will for him too😃
 

SubwayChamp

Senior Member
Aug 6, 2016
2,787
1
1,265
Ok, so, I've solved SOME of the problems I've run into as I tried to reimage...

Now I've got a Moto G Power (2020) where I believe I have successfully loaded the new images (Resurrection Remix), and yet, when I get to the end of the instructions and try to reboot, I just keep ending up at the bootloader (Fastboot Flash Mode, NOT FastBootD, just the normal one with the green droid opened up for repairs)

I've tried going into the following options:
  1. Start - comes right back to the same screen
  2. Restart Bootloader - Same Screen
  3. Recovery mode, and it says 'No Command'
  4. Power Off - goes down, when I power it up, same screen
  5. Bootloader Logs - says "AP Fastboot Flash Mode (Secure) Fastboot Reason: Reboot mode said to fastboot"
I've also tried this with and without a USB cable attached.

How do I smack this thing and get it out of the endless loop it's stuck in? And WHAT did I do to cause this loop?
I'm feeling that you are missing just the minimal but most essential part of the whole process and to solve it you should have to start from the scratch, completely but doing every of the steps correctly.
I will just put in clear here some of the steps from the RR ROM thread.

- Flash again the stock ROM for your device through LMSA.
- Reboot to system for first time and check if all is fine with the OEM Unlock option starting from the toggle, USB debugging till the fastboot command to be sure if your bootloader is still unlocked (as I think is required)
- Be sure that your stock recovery is there.
- Reboot to bootloader either manually, through adb commands or through the recovery menu.
- Reboot to fastbootd using
Code:
fastboot reboot fastboot
(don't forget to use the latest SDK platform that contains the fastbootd binaries)
- Flash one by one the boot, system, product and vbmeta images.
- Wipe the userdata partition with fastboot -w (to can reboot)
- Reboot.
 
  • Like
Reactions: Arc android

IceWing_mk1

Member
May 25, 2021
7
1
I'm feeling that you are missing just the minimal but most essential part of the whole process and to solve it you should have to start from the scratch, completely but doing every of the steps correctly.
I will just put in clear here some of the steps from the RR ROM thread.

- Flash again the stock ROM for your device through LMSA.
- Reboot to system for first time and check if all is fine with the OEM Unlock option starting from the toggle, USB debugging till the fastboot command to be sure if your bootloader is still unlocked (as I think is required)
- Be sure that your stock recovery is there.
- Reboot to bootloader either manually, through adb commands or through the recovery menu.
- Reboot to fastbootd using
Code:
fastboot reboot fastboot
(don't forget to use the latest SDK platform that contains the fastbootd binaries)
- Flash one by one the boot, system, product and vbmeta images.
- Wipe the userdata partition with fastboot -w (to can reboot)
- Reboot.
First, thanks @SubwayChamp and @sd_shadow for trying to help.

To be clear, I'm documenting step by step here, a.) to make sure I can replicate what I'm doing b.) you guys can see what I'm doing (and possibly more importantly what I'm NOT doing) and c.) to make sure I'm not missing any steps.
  • rebooted the phone (Moto G Power) manually going into the bootloader, decided wanted to check settings first so then I
  • rebooted to go into the stock image (reset again last night via LMSA) in order to check for developer mode and usb debugging,
  • got the same message on startup that it's unlocked, so I know OEM Unlock is still open
  • went into settings-> about phone, tapped build # seven times to enable developer mode
  • went to settings-> system -> Developer Options, disabled autoupdates, enabled USB debug mode
  • Shutdown the phone , unplugged from USB cable and brought it back up in bootloader mode (via holding Down Volume and Power to start it up (it shows the android open for repairs, and in the text does say "Flashing_unlocked"
  • Plugged in USB cable, connecting phone to PC
  • Selected 'Start Recovery Mode', get the error screen reading 'No Command' with the red icon over the android open for repairs
    • @SubwayChamp - I tested this because you told me to make sure that Stock Recovery mode was there, which it seems like it is not... How do I \ do I need to fix that ?
  • Rebooted phone again, comes up with the restored version that LMSA put on it
  • Unplugged, power down, restart to bootloader, plugged into USB to connect to PC
  • In the directory containing the extracted contents of 'platform-tools_r31.0.2-windows.zip', downloaded from 'https://dl.google.com/android/repository/platform-tools_r31.0.2-windows.zip', I am opening a new CMD window via typing CMD in Windows File Explorer address bar 'C:\WorkingProject\platform-tools'
    • One question here... when you say make sure to use the most up to date SDK, with the most up to date binaries, I THINK the Android Platform Tools is the right one, but I've also downloaded and installed a full Android Studio, which is in a separate directory, and when I look at the root folder there, I don't see the same fastboot binary, which I believe is what I'm launching when I try the 'fastboot reboot fastboot' command. Which is the correct instance to be using?
  • Run the command 'fastboot devices' and get back the phone serial # and 'fastboot'
  • Run 'fastboot reboot fastboot' (which if I understand correctly reboots the phone, using the 'fastboot' binary in the 'platform-tools' directory on the PC)
    • Note: the binary in the local 'platform-tools' directory says 'fastboot', NOT fastbootd and is 1592kb
  • 11.329 seconds later, the command has finished running and I see 'fastbootd' in big red letters on the phone screen
  • Copy the 4 img files (boot, product, system, vbmeta) from the directory where I'm storing the ROMs into the 'platform-tools' directory (I'm trying LineageOS 17.1 this time around)
  • Run command 'fastboot flash boot boot.img' in the previously opened cmd prompt.
    • Sending to boot_a, writing to boot_a.
    • Finished with a total time of 3.461sec.
  • Run command 'fastboot flash system system.img' in the previously opened cmd prompt.
    • Resizes system_a
    • sends 4 chunks of data and writes them
    • Finished with total time of 31.927s
  • Run command 'fastboot flash product product.img' in the previously opened cmd prompt.
    • Resizes product_a
    • sends 2 chunks of data and writes them
    • Finished with total time of 16.467s
  • Run command 'fastboot flash vbmeta vbmeta.img' in the previously opened cmd prompt.
    • sends 1 chunks of data and writes it
    • Finished with total time of 0.066s
  • Run command 'fastboot -w' in the previously opened cmd prompt to wipe the user data .
    • C:\WorkingProject\platform-tools>fastboot -w
      • Comes back with:
      • Erasing 'userdata' OKAY [ 0.513s]
        Erase successful, but not automatically formatting.
        File system type raw not supported.
        Erasing 'metadata' OKAY [ 0.009s]
        Erase successful, but not automatically formatting.
        File system type raw not supported.
        Finished. Total time: 0.539s
  • Just looked at the phone, still shows fastbootd in red at the top.
  • At the suggestion of @sd_shadow I'm adding the following fastboot oem fb_mode_clear
    fastboot reboot
  • Run command 'fastboot oem fb_mode_clear' in the previously opened cmd prompt.
    • FAILED (remote: 'Command not supported in default implementation')
      fastboot: error: Command failed
    • @sd_shadow - any idea why this occurred? Does this go back to I'm running from 'platform-tools' instead of the Android Studio?
  • No change on the phone screen
  • Run command 'fastboot reboot' in the previously opened cmd prompt.
  • phone reboots, warns me I'm unlocked, then right back into the bootloader screen again.
  • Restart Phone with Recovery Mode Option
  • Phone gives me the 'you're unlocked' warning, I push past it, get the no command red warning icon.
  • Unplug phone, reboot it, back to bootloader
So, I'm guessing that probably during the LMSA purge\reset the TWRP instance I had loaded into the recovery slot previously got wiped, and now I need to get the 'default' recovery tool back in there to actually initialize the images I have loaded and get this thing running.

What recovery image should I load? (and I believe it is done via going back into fastbootd on the phone, then running 'fastboot flash recovery >recovery image name<' from the command prompt)

Thanks in advance.

Ice
 

fakewooder

New member
May 24, 2021
4
0
Left an interesting situation in the Q&A, no answers yet. Seems to have gotten buried.

Could someone take a look?

 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I do a lot of shell scripting. Recently i was looking into something on my current device, and I couldn't work out how to do it, so hopefully someone here would know.

    The question is basically, for an updated system app, how do you find the original APK location?

    When a system app gets updated (for example by the playstore), it will get installed to /data/app however, before it gets updated, it may be located in /system/app; and would stilll be there. When It is updated, retrieving its location, it will return the /data/app location, but I cant seem to find how to retrieve its "original" system location.

    To find examples, I can use the following to retrive a list of system apps
    Bash:
    cmd package list packages-s;
    To then find its current install location
    Bash:
    cmd package list packages-f;
    and grep out the specific package I am looking for.

    However, if the system package has been updated, it will only give me the /data/app path.

    Is there anyway (without uninstalling the update) to retrieve the original location?
    if anyone else is interested, I think I found the answer.
    dumpsys package $package_id;
    Gives details of the current install and the original package,
    2
    also may want to delete ur serial #. could be used for bad purposes and is not needed except by you.
    did you just quote his SN# :LOL:
    2
    I wish I could help, but I can't here. I had a S2, a GNex, and an S3. When Sammy announced Knox for the S4, I left. I couldn't be happier. Samsung devices are GREAT for the normal consumer. For people who root, they are a hassle. Being able to just boot to bootloader and use fastboot commands is glorious.

    There are Samsung experts (I am far from one at this point in time) on this thread. Hopefully one of them picks up on your post. Best of luck to you.
    Thanks for getting back to me -- and yeah, Samsung is a pain, and always has been. Unfortunately, they also make the only decent graphics tablets for artists (and I refuse to go to Apple), so for tablets I put up with it. But I've never had this much trouble. Grr!

    For phones, I had a T-Mobile S7 given to me, so I couldn't root it even if I wanted to. Next phone will probably be an LG. I've had both Nexus 4 and 5, both rooted and running (then) CyanogenMod, and loved them!

    SOLVED: I cracked it! For those getting the error "recovery: error validating footer. (6)" the problem is Samsung stupid validating feature called VBMETA that they don't really talk about. It's in the VBMETA partition, and apparently the only recovery that will pass verification is the one installed at the factory. I couldn't even get OEM recoveries to pass. They all gave me the same error.

    So the solution is:

    1) Make sure the recovery you're flashing also has an image called "vbmeta.img". If it doesn't, look elsewhere. (I flashed the recovery that came with my rom, so it had the vemeta.img file in the zip.)
    2) Flash both at the same time. Don't know about Odin, but with heimdall, here's the command: heimdall flash --RECOVERY recovery.img --VBMETA vbmeta.img --no-reboot
    3) Hold down PWR and Vol-dwn, until the device resets. Immediately! hold down Vol-Up & Pwr. The screen will blink a couple of times, then recovery will load.

    Boom!
    2
    Thanks for getting back to me -- and yeah, Samsung is a pain, and always has been. Unfortunately, they also make the only decent graphics tablets for artists (and I refuse to go to Apple), so for tablets I put up with it. But I've never had this much trouble. Grr!

    For phones, I had a T-Mobile S7 given to me, so I couldn't root it even if I wanted to. Next phone will probably be an LG. I've had both Nexus 4 and 5, both rooted and running (then) CyanogenMod, and loved them!

    SOLVED: I cracked it! For those getting the error "recovery: error validating footer. (6)" the problem is Samsung stupid validating feature called VBMETA that they don't really talk about. It's in the VBMETA partition, and apparently the only recovery that will pass verification is the one installed at the factory. I couldn't even get OEM recoveries to pass. They all gave me the same error.

    So the solution is:

    1) Make sure the recovery you're flashing also has an image called "vbmeta.img". If it doesn't, look elsewhere. (I flashed the recovery that came with my rom, so it had the vemeta.img file in the zip.)
    2) Flash both at the same time. Don't know about Odin, but with heimdall, here's the command: heimdall flash --RECOVERY recovery.img --VBMETA vbmeta.img --no-reboot
    3) Hold down PWR and Vol-dwn, until the device resets. Immediately! hold down Vol-Up & Pwr. The screen will blink a couple of times, then recovery will load.

    Boom!
    NICE! Thank you for posting the solution.

    As a side note, rooting the Pixel 5 on Android 12 has an issue with vbmeta as well. After an update, you need to flash the vbmeta.img with disabling verification and verity in fastboot, followed with a "-w" to wipe your phone. In future updates if you sideload the OTA you can boot immediately to bootloader and flash vbmeta with disabling verification and verity without a wipe. If you screw up and boot to system first, you'll have to use "-w" and wipe again
    2
    Hey, GCam suits on what basis. Is it by the Android versions or by the processor basis. Im using Lenovo k10 note which is android 9 and SD 710. I like to install GCam 8 or more.
    It's based on both, this app will help you find the appropriate for your device if there’s available https://play.google.com/store/apps/details?id=com.granturismo.gcamator&hl=es_PY&gl=US
  • 378
    There are a lot of people joining XDA on a daily basis, and there are a lot of repetitive questions being asked
    which clutter up the Development and 'Q & A' threads. Point them here. Feel free to ask or answer questions.

    The idea of this thread is to get users to help other users with their problems/questions. People are usually
    ridiculed for asking questions that other people deem stupid even though it may be a legitimate question. This
    leads to new users being afraid to ask questions!

    Only provide well mannered help towards users in this thread. Please do not spoon feed, but rather point in
    the direction where that user can find an answer
    and educate himself. If you don't want to answer, at least
    point out where to find the answer.



    Before posting anything, I strongly advise you to read THIS thread.

    Then, have a quick look at the names of threads in Post No. 2, you might find what you need right away.

    Third. Even if you do get your question answered, please do come back and read threads in Post No. 2
    (coming later as soon as we start getting the guides) to educate yourself. You'll be surprised how much time
    and frustration it will save you in the future!



    No abuse towards noobs tolerated here! That means:
    NO TROLLING
    NO NAME CALLING
    NO RIDICULING
    NO FLAMING


    ASK ANY QUESTION HERE! No question is stupid or irrelevant in this thread. You will either get an answer or will get pointed in the right direction.


    *A Special Thanks to mark manning for his help in creating this thread*


    HALL OF FAME

    People who contributed most to this thread and helped countless number of people with their
    problems/questions. In no particular order.

    Bruce Wayne
    post-mortem
    SilentStrider
    Ghostfreak NB
    mayank9856
    sgs22012
    Zatta
    ADDICT.ANK



    These people also have the right to use the banner below:
    Newbie%20Thread%20Sign.gif


    Just add this code to your signature:
    HTML:
    [URL="http://forum.xda-developers.com/showthread.php?t=2257421"][IMG]https://dl.dropboxusercontent.com/u/41066660/Newbie%20Thread%20Sign.gif[/IMG][/URL]
    110
    Reserved

    Just a few words of advice on keeping this thread clean of unnecessary clutter:

    1. Before posting a question, it is highly recommended to read this thread.

    2. Click the Thanks button on the posts that helped you, instead of posting "Thanks". This helps other members in finding out the best replies that get buried in the thread.

    3. Do not use this thread to increase your post count! The Off-Topic forum is the place for that.

    4. Do a simple search of this thread before asking to see if your question has been asked previously.

    5. If your question has not received an answer after a few hours, please be patient. Someone will answer you shortly. If you do not get an answer in 24 hours, you may BUMP your post. If you still have no answer after a week, do mention me in your post.

    Thank you for your cooperation!
    26
    Good job mate, hopefully lots of members will find this thread very helpful :cool::good:
    11
    ZTE V970 Brick?

    Hi,

    I've been trying to install Bruno's ROM for this phone (cam with all chinese apps). http://forum.xda-developers.com/showthread.php?t=1856578

    but have a big problem. I tried my best to follow the instructions but, really couldn't work out if I was doing things in the right order.. is there an actual step- by step for this procedure? I know I'm a noob and read this read that I am an idiot etc. etc. but I thought if I used to ROM on that page and the software recommended it would be easy.

    Here's what I did:

    Downloaded all the files as told.

    Tried to 'flash a custom recovery' as here http://bm-smartphone-reviews.blogspot.co.uk/2012/05/mt6575-flashing-tutorial.html

    but it did not mention how to use the ZTE custom recovery file http://d-h.st/Vgt

    I'm also not sure at all that the 'MediaTek drivers' were installed properly. The phone never appeared in the Device manager.

    I opened SP flash tool and followed this: http://bm-smartphone-reviews.blogspot.co.uk/2012/05/mt6575-flashing-tutorial.html

    and selected the 'scatter file' from the unzipped Bruno ROM (took a while to realise had to unzip it to get the file!!!)

    I noticed most of the boxes on the scatter file were unchecked but carried on and ignored a warning message about the phone may not be able to boot (the tutorial said to ignore it).

    I had to click 'download' then plug the phone in and eventually I got the red loading bar. This finished... then nothing else.. no purple bar.. nothing.

    So after waiting a few minutes I unplugged the phone.

    It now appears to be a total brick. What did I do wrong? Why no purple bar? Were the scatter items supposed to be unchecked? What was the 'custom recovery' file for? Because the SP flash prog never asked for it.

    Is there any point in trying it again or is the phone dead?

    Thanks for any help..

    Theo