Search This thread

immortalneo

Senior Member
Jan 25, 2011
4,425
1,931
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:

Rizwan66

Member
Apr 10, 2021
8
0
If you used the installer in the main thread that won't work anymore, use the link provided in the mod edit to install ADB and Fastboot: https://dl.google.com/android/repository/platform-tools-latest-windows.zip (you'll also need drivers to allow your PC to communicate with your phone, just google drivers for <device name>)

Also, again:
"adb devices" is for when your device is on and in Android
"fastboot devices" is for when your device is on and in fastboot mode.
Can you give me ur whtsapp ar instaa to contact plz
 

ithan80

Member
Apr 10, 2021
8
0
If you used the installer in the main thread that won't work anymore, use the link provided in the mod edit to install ADB and Fastboot: https://dl.google.com/android/repository/platform-tools-latest-windows.zip (you'll also need drivers to allow your PC to communicate with your phone, just google drivers for <device name>)

Also, again:
"adb devices" is for when your device is on and in Android
"fastboot devices" is for when your device is on and in fastboot mode.
thank you, i will try it
 

xunholyx

Recognized Contributor
Dec 3, 2012
7,620
5,200
Vancouver
HTC 10
Google Pixel 2 XL
Bro how can i directly contact you i am not undrstnding cuz i am new to oneplus .. and my android version is still 10.0.12
Hi
I don't know what you are talking about here or who you are replying to.
In the future, please use the reply option when replying to someone. That way the person you are replying to will get a notification. Also, someone like me coming across your post can click on what you are replying to and go back to see the conversation and might be able to jump in to help.
 

SubwayChamp

Senior Member
  • Aug 6, 2016
    2,600
    1
    1,189
    Alright, suppose I do find a TWRP for the same chipset (ie mt6761 for my device). What information should I need to obtain from my device in order to port the TWRP to it? I'm asking because all porting guides require a copy of the stock recovery image so is there a way to get the information required from my stock rom?

    Another question is if I manage to build a TWRP image, how do I test to see if it works on my device? Executing "fastboot boot TWRP.img" seems to hang on the transfer ok screen for a few seconds then the device reboots into Android. Tried temp booting a magisk patched boot.img as well but it would always boot into the boot.img currently flashed onto the device.
    You should get this information and files from the boot image, of course you have to know something about decompile and recompile (there are some pretty tool to do so).

    In order to flash anything to some partition you need to unlock bootloader and also critical partitions, a recovery ported this way won´t survive in the boot partition so it has to use atleast a minimal portion of the ramdisk to live in the boot partition, for this you should need a TWRP installer that have to be flashed through TWRP, in the meantime push a copy of the stock boot to your SD card in case you can´t boot to system again.

    As I said you TWRP has to be flashed to the boot partition, if it´s not well ported then you will overwrite it and you can´t boot to system so you´d need to flash again the boot image unless the TWRP base has the ability to do so.
     

    SubwayChamp

    Senior Member
  • Aug 6, 2016
    2,600
    1
    1,189
    i had tried with qcomdload,its the same as i see with lenovo downloader,but always had the same message "cannot open raw file". Probably i do something wrong or i haven't download the correct rom.i download the rom from here :https://firmwarefile.com/lenovo-tab-4-10-plus-tb-x704l . i tried 10 minutes ago it says step : sahara ,status :flashing ,time 1000seconds and still flashing, but i must leave for work.But at the begining again the same message ''cannot open raw file'' .
    This message is clearly referring to an image that can´t be handle by the tool, I have to assume that you atleast unzipped your file (?). Upload some screenshots from the folder inside to see which files contain. In case you don´t know qfil works with EDL mode and the LDT works with fastboot.
     

    ithan80

    Member
    Apr 10, 2021
    8
    0
    This message is clearly referring to an image that can´t be handle by the tool, I have to assume that you atleast unzipped your file (?). Upload some screenshots from the folder inside to see which files contain. In case you don´t know qfil works with EDL mode and the LDT works with fastboot.
    i manage to get it work and after 60 secs the programm closes by itself,it never finishes the flashing. 3 times now.After many efforts with different versions of lenovo downloader i managed to flash it,but unfortunatelly it reboots again.I will try this https://forum.xda-developers.com/t/my-phone-keeps-rebooting-even-after-odin-flash-stock-tar.3409961/ . i mean i will let it to drain battery.
     

    Attachments

    • IMG_20210412_000356.jpg
      IMG_20210412_000356.jpg
      2.7 MB · Views: 10
    Last edited:

    acacacac

    New member
    Apr 11, 2021
    2
    0
    Hi there. Any insights to my issue will be appreciated.

    I've been running LineageOS on a Nextbit Robin for a few years, from 14 to 15 to 16 everything was great. Now in 2021, Lineage 17.1 briefly arrived and now Lineage 18.1.

    My problem is new to 17.1 & 18.1, and did not occur over the past few years in earlier versions of Lineage.

    After downloading and installing a 'nightly' update, the phone will boot loop and I'm unable to get it up & running again. For whatever reason the update won't 'take'.

    I'm definitely no expert but I've tried a few different things and nothing seems to avoid this issue. I've always used TWRP but tried the new Lineage Recovery to see if that might help the issue. I used to use OpenGapps but as there's no Android 11 OpenGapps yet I used NikGapps when setting up Lineage 18.1.

    My 'initial' set up of 17.1 and now 18.1 goes fine - I was running 18.1 for the beginning of April until today when I tried to install the weekly update.

    But in my inexpert way of describing things, something in the Lineage update process seems to have broken for me in the newest versions relative to how routine it was in earlier versions over the past years.

    Any advice? Thank you. What if any new habits do I need to adopt to make sure I'm able to successfully install new updates and not soft brick my phone?
     
    Apr 3, 2021
    12
    1
    I need help as my brain is melting. My blu G90 pro is bootlooped. I saw the noob friendly guide to bootloop recovery, but I can't boot my phone into recovery mode. I can only boot into fastboot mode. ADB won't connect and I am at a loss right now.

    I got bootlooped after following these instructions
    • Copy the boot/recovery image to your device
    • Press the Install button in the Magisk card
    • If you are patching a recovery image, make sure “Recovery Mode” is checked in options.
      In most cases it should already be automatically checked.
    • Choose “Select and Patch a File” in method, and select the stock boot/recovery image
    • The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.
    • Copy the patched image to your PC with ADB:
      adb pull /sdcard/Download/magisk_patched_[random_strings].img
    • Flash the patched boot/recovery image to your device.
      For most devices, reboot into fastboot mode and flash with command:
      fastboot flash boot /path/to/magisk_patched.img or
      fastboot flash recovery /path/to/magisk_patched.img if flashing a recovery image
    • Reboot and voila!
    I don't have a custion recovery as there isn't twrp for blu g90 pro.
     

    SubwayChamp

    Senior Member
  • Aug 6, 2016
    2,600
    1
    1,189
    Hi there. Any insights to my issue will be appreciated.

    I've been running LineageOS on a Nextbit Robin for a few years, from 14 to 15 to 16 everything was great. Now in 2021, Lineage 17.1 briefly arrived and now Lineage 18.1.

    My problem is new to 17.1 & 18.1, and did not occur over the past few years in earlier versions of Lineage.

    After downloading and installing a 'nightly' update, the phone will boot loop and I'm unable to get it up & running again. For whatever reason the update won't 'take'.

    I'm definitely no expert but I've tried a few different things and nothing seems to avoid this issue. I've always used TWRP but tried the new Lineage Recovery to see if that might help the issue. I used to use OpenGapps but as there's no Android 11 OpenGapps yet I used NikGapps when setting up Lineage 18.1.

    My 'initial' set up of 17.1 and now 18.1 goes fine - I was running 18.1 for the beginning of April until today when I tried to install the weekly update.

    But in my inexpert way of describing things, something in the Lineage update process seems to have broken for me in the newest versions relative to how routine it was in earlier versions over the past years.

    Any advice? Thank you. What if any new habits do I need to adopt to make sure I'm able to successfully install new updates and not soft brick my phone?
    I never had a device updating with a single ROM for years but I think that maybe it's time to a fresh install wiping caches, dalvik and maybe formatting data, if available some kind of selected files in a form of firmware (to use it as base) and finally flashing the latest LOS available.

    Regarding the Gapps these are the recommended https://wiki.lineageos.org/gapps.html
     

    SubwayChamp

    Senior Member
  • Aug 6, 2016
    2,600
    1
    1,189
    I need help as my brain is melting. My blu G90 pro is bootlooped. I saw the noob friendly guide to bootloop recovery, but I can't boot my phone into recovery mode. I can only boot into fastboot mode. ADB won't connect and I am at a loss right now.

    I got bootlooped after following these instructions
    • Copy the boot/recovery image to your device
    • Press the Install button in the Magisk card
    • If you are patching a recovery image, make sure “Recovery Mode” is checked in options.
      In most cases it should already be automatically checked.
    • Choose “Select and Patch a File” in method, and select the stock boot/recovery image
    • The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.
    • Copy the patched image to your PC with ADB:
      adb pull /sdcard/Download/magisk_patched_[random_strings].img
    • Flash the patched boot/recovery image to your device.
      For most devices, reboot into fastboot mode and flash with command:
      fastboot flash boot /path/to/magisk_patched.img or
      fastboot flash recovery /path/to/magisk_patched.img if flashing a recovery image
    • Reboot and voila!
    I don't have a custion recovery as there isn't twrp for blu g90 pro.
    Firstly to recover the ability to boot again you can go back to the latest working state by re-flashing the stock image either boot or recovery.

    Most of devices actually use DM-verity, maybe you should try flashing a blank/generic vbmeta image after to flash the patched image.
     

    acacacac

    New member
    Apr 11, 2021
    2
    0
    I never had a device updating with a single ROM for years but I think that maybe it's time to a fresh install wiping caches, dalvik and maybe formatting data, if available some kind of selected files in a form of firmware (to use it as base) and finally flashing the latest LOS available.

    Regarding the Gapps these are the recommended https://wiki.lineageos.org/gapps.html
    Thanks for the reply.

    After the fist 17 update issue there was a complete wipe of the phone and I started over, so whatever issue isn't causing updates to 'take' isn't stemming from that.

    Flashing the latest LOS is straightforward enough and will get me going, but after that I still don't understand why I am having the phone soft brick when trying to update thereafter, which is my issue.
     

    SubwayChamp

    Senior Member
  • Aug 6, 2016
    2,600
    1
    1,189
    Thanks for the reply.

    After the fist 17 update issue there was a complete wipe of the phone and I started over, so whatever issue isn't causing updates to 'take' isn't stemming from that.

    Flashing the latest LOS is straightforward enough and will get me going, but after that I still don't understand why I am having the phone soft brick when trying to update thereafter, which is my issue.
    I'm not sure what you mean with "Flashing the latest LOS is straightforward enough and will get me going" so TWRP will flash it anyway no matter what you did previously but a major upgrade might require a complete wipe, in this case going from LOS17 to LOS18, I mean it's not that it can cause issues only on the normal functioning or instability or battery drain or something more but the flashing process itself can be obstructed in some cases resulting in this.

    As it could be that there is not instruction on how to flash this update doing that will be the most recommendable, also in case you didn't, some times you'd need to disable the zip signature verification.

    Edit: Also some times after to flash the ROM you should reboot for first time to system prior to flash the Gapps, if you didn't this way and plus flashing not authorized Gapps package as it seems is the case one of them or both errors could cause the issue.
     
    Last edited:

    Droidriven

    Senior Member
    Jan 27, 2014
    14,749
    5,137
    NC
    Verizon Samsung Galaxy S III
    HTC Thunderbolt
    I use a Umidigi smartphone which uses a type c cable. The cable that came with it was working fast. It charges from 0% to 100% in 2 hours. But all of a sudden, there was a cut on the cable and the wires touched(I think the term is short-circuited), and I had to discard the cable.

    But ever since then, my phone charge really slow. Even when I switch it off, it takes like 10 hours for it to become full from 0%. I tried over three tested quality cables but it's still the same thing. My charger adapter is not the problem as I used it on other people's phone and it was charging the phones well.

    Also, when my phone is now plugged in and it's off, if I want to switch it on, it might take about 10 seconds before it display anything at all. It even discharges whenever my mobile data and my screen are on when plugged in.

    Moreso, the cords no longer transfer files from computer to my phone anymore. The battery is inbuilt and I can't even open the phone's casing. I don't know what to do again. Pls help.
    Sounds like the short circuited cable caused damage to your phone's charging port/pins. It may be as simple as replacing the USB port component or you may have damaged something deeper.
     

    Droidriven

    Senior Member
    Jan 27, 2014
    14,749
    5,137
    NC
    Verizon Samsung Galaxy S III
    HTC Thunderbolt
    Hello, I have a problem that I have not been able to identify the cause, in my terminal.
    You see, it happens to me that every time I use mobile data from the SIM card or simply by removing the airplane mode.
    What happens is that my device begins to connect and disconnect from the network (including mobile and call data) and then it reconnects again. But it is very annoying!
    If I don't have the airplane mode activated, it does the same with the Wi-Fi connection. It connects and disconnects it. And rarely with Bluetooth.
    The way I get around it is by using the phone in airplane mode all the time. But that means that I cannot make or receive calls and that I cannot spend my data.
    Seems to me that your problem may be related to your device's "rescan interval". What kind of system is your Wifi being provided by? If your Wifi is provided via a satellite dish or via a substandard service provider or network, you may be recieving intermittent internet signal, this would cause random disconnects.

    Also, if your phone's service provider or network is also substandard or if you are in an area with poor signal reception such as in rural areas or low-lying areas, this would cause your phone's cellular to have connection issues.
     

    Droidriven

    Senior Member
    Jan 27, 2014
    14,749
    5,137
    NC
    Verizon Samsung Galaxy S III
    HTC Thunderbolt
    Hello Champ, thanks for finding time to reply.

    I was the one who inputted the unlock code, it was successful since when I inserted a sim of a different carrier, I can confirm network unlock, but cannot change the APN settings (message was "APN Settings Not Available for the Current User". That's why I opted to change the GLB FW to XTC FW, but the same issue occurs. This is where I'm stuck right now
    The only times I have encountered "APN settings are unavailable for this user" is when using a SIM card that has not been activated or has been deactivated.
     
    • Like
    Reactions: SubwayChamp
    Apr 3, 2021
    12
    1
    re-flashing the stock image either
    Firstly to recover the ability to boot again you can go back to the latest working state by re-flashing the stock image either boot or recovery.

    Most of devices actually use DM-verity, maybe you should try flashing a blank/generic vbmeta image after to flash the patched image.
    How would I go about doing this? I can't find any resources, either because of my lack of experience, or there aren't any.
    Please keep in mind I started learning about this stuff a week ago.
     

    TheBeast941

    Member
  • Apr 6, 2021
    11
    0
    You should get this information and files from the boot image, of course you have to know something about decompile and recompile (there are some pretty tool to do so).

    In order to flash anything to some partition you need to unlock bootloader and also critical partitions, a recovery ported this way won´t survive in the boot partition so it has to use atleast a minimal portion of the ramdisk to live in the boot partition, for this you should need a TWRP installer that have to be flashed through TWRP, in the meantime push a copy of the stock boot to your SD card in case you can´t boot to system again.

    As I said you TWRP has to be flashed to the boot partition, if it´s not well ported then you will overwrite it and you can´t boot to system so you´d need to flash again the boot image unless the TWRP base has the ability to do so.
    By treating my boot.img as a recovery.img then flashing the output to my boot partition, i managed to port TWRP to my device! However, when attempting to install Magisk (v22.0) either by flashing a patched boot.img or by flashing a zip through TWRP, Magisk seems to install while overwriting TWRP so that on the next boot there is no TWRP when rebooting to recovery. Is there any workaround to get TWRP and Magisk at the same time? I don't want to go ahead and install v22.1 since it still seems pretty new.
     

    SubwayChamp

    Senior Member
  • Aug 6, 2016
    2,600
    1
    1,189
    How would I go about doing this? I can't find any resources, either because of my lack of experience, or there aren't any.
    Please keep in mind I started learning about this stuff a week ago.
    You didn't mention yet which image you patched and flashed to gain root, either boot or recovery image I guess you got it from your stock firmware, so following with this assumption, you should flash again either the boot or recovery stock (not the patched one) to restore your device to its original state.

    Regarding the second part most of devices after to attempt to root them they need to disable DM verity in order to can boot.

    - Firstly re-flash as indicated previously either the recovery or the boot image.
    - Reboot to system and check if USB debugging and OEM unlock options are still enabled.
    - Send device to fastboot.
    - From here on it should be that you simply patched the wrong image, some devices need the boot and some need the recovery image. If you flashed the other image right now and still you can't boot then..
    - Download this file and place it to the same adb/fastboot folder directory to avoid an unnecessary/erroneous/misspelled/mismatched path https://mega.nz/file/dnAS3AhD#g5PnSg-0UKFvyhZSZ8Em6gKO2Do7avaUepPmsH75-Bg (In case your device doesn't require a signed vbmeta then it'll work).
    - Type in fastboot (with device connected to PC)
    Code:
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    in case this command doesn't work type
    Code:
    fastboot flash vbmeta vbmeta.img
    you have to get a successful message, after that you should flash your patched image (always that is the indicated)
    - Method 2 is editing with a hex editor your boot image and removing/replacing from it for 0 values all the verity flags and then patching it with Magisk to finally flash it.
    - Method 3 is signing your own vbmeta image, I guess that the last 2 methods are as you said by now out of your skill.
     
    • Like
    Reactions: mrrocketdog

    SubwayChamp

    Senior Member
  • Aug 6, 2016
    2,600
    1
    1,189
    By treating my boot.img as a recovery.img then flashing the output to my boot partition, i managed to port TWRP to my device! However, when attempting to install Magisk (v22.0) either by flashing a patched boot.img or by flashing a zip through TWRP, Magisk seems to install while overwriting TWRP so that on the next boot there is no TWRP when rebooting to recovery. Is there any workaround to get TWRP and Magisk at the same time? I don't want to go ahead and install v22.1 since it still seems pretty new.

    Well, this is exactly what I warned previously, your TWRP needs to be fixed in the ramdisk partition to live together so any time you flash something it is not overwritten.

    You should port it from a TWRP that already was made for an A-B device (processor similarities required) the Android Ones edition are an example on how it works and additional search for a TWRP installer , look inside and see which values you should replace for those from your device to make it compatible.

    This is an example of what I'm saying, from my current device https://forum.xda-developers.com/t/..._9-0-for-android-9-10-11-custom-roms.4123287/
     
    • Like
    Reactions: mrrocketdog

    Top Liked Posts

    • 2
      https://github.com/yshalsager/MSM8225-TWRP-Porter
      It is obvious that this tool does not work.
      This tool stopped being updated 4 years ago.

      Well, if you are expecting that a tool do all the job for you that is not how it works, you have to take various guides and compliment the information as a puzzle, I don´t think that a full all-in-one guide exists and taking a look on how a tool performs a thing it may help to a better understanding.
      Even the twrp team was not able to support android10 until 2021.
      This is not accurate I´m using Android 10 since few weeks after the first betas were released at March/19 (always rooted and with TWRP, PBR, OFR, SHR, etc?); unofficial builds were ready 2 years ago and official ones started at the mid of the past year https://www.androidpolice.com/2020/...h-limited-android-10-support-and-other-fixes/ a ported custom recovery will be ever an imperfect thing so far from not only the official builds from source but even from the unofficial, so be happy if at least you can perform minimal tasks with it.
      https://www.dealntech.com/phones-snapdragon-750g-5g-processor/
      I referred to this article.
      https://dl.twrp.me/gauguin/
      As a result, I used this twrp.
      Unfortunately, the touch panel does not work.
      Furthermore, the password input screen does not appear, so I can't compound the data.
      Try with other devices and if the next 2 or 3 attempts this persists then you should need to load the correct modules into your kernel config, identify the exact driver for the touch panel that your device uses (use some app like this https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw&hl=es&gl=US) and find other with same compatibility. All that said assuming that your guide is working.

      I will recommend that you use this recovery as base https://forum.xda-developers.com/t/...efox-recovery-for-xiaomi-mi-10t-lite.4227349/ it has best compatibility with a wide vendor display range.

      Follow your guide and if it is not working then use the Carliv Image kitchen https://carliv.eu/ the method will be near to the other, replacing all the files (images) that you´ll find out of the ramdisk folder (those are the same that are usually in split images), regarding the fstab.qcom that you´re not finding it is in the boot image, you have to unpack it too to get it, the rest remains the same.
      1
      I wanted to look into citadel a bit more before I went to far. ;)
      Ran out of time to do some testing.

      From what I found, it seems citadel might just be a reporting tool for the Titan M chip first introduced in Pixel 3.
      Google Blog - WebSite - Titan M makes Pixel 3 our most secure phone yet Link

      Not sure if it can be used/exploited to actually change anything. :confused:
      Then again, how many exploit security patches do we have every year. 🙃


      Before I updated my 5 to the April build (redfin-ota-rq2a.210405.005 at the time), that was the same error it gave me.
      I am not sure why since I was connected to WiFi and I still have not installed a sim card in my 5.
      I wonder if it would have made a difference updating using the updater instead of downloading and sideloading the recovery OTA. ?
      As noted, I bought the unlocked version directly from Google, so there should have been no issue unlocking the bootloader before updating.


      My Pixel 4a (sunfish) and 5 (redfin) are on stock Google Android 11.
      April 2021 build. I will update them to the May 2021 today or tomorrow.

      I will let you know what I find. :D

      Cheers. :cowboy:
      Going to see if I can locally pick up one of those debugging cables if not see if I can get one ordered overnight or close to it from Amazon or the likes. I'm hoping that because we seem to have full functionality here that this cable May cancel out the device error when trying to reset the ABB locks. What happens after that is anyone's guess and whether or not you can change anything in this little rabbit hole may not matter. What I'm interested in is why the bootloader value when doing a reset on citadel goes back to zero and assuming zero means unlocked we have one unlocked slot to work with when that is defaulted to zero. And given I've somehow been able to change slots from b to a might also work on our advantage. Something I still have yet to figure out how I did. Time to go look for one of those cables.

      EDIT ADD: unfortunately until I can find a way to update with a factory image, I am stuck on Android 12. Verizon does not allow flashing of images on locked devices. However they do allow an OTA if they are signed by Google specifically... Or we find out what keys they use and if they are actually available in the AOSP sourcetree. That's just a wild leap of faith, but I've seen weirder things happen. So until I can hack an OTA or a factory image to flash I am stuck on Android 12 and any updates they give me through Google. Verizon no longer updates this device as far as I know but I very well could be wrong.
      1
      I wanted to look into citadel a bit more before I went to far. ;)
      Ran out of time to do some testing.

      From what I found, it seems citadel might just be a reporting tool for the Titan M chip first introduced in Pixel 3.
      Google Blog - WebSite - Titan M makes Pixel 3 our most secure phone yet Link

      Not sure if it can be used/exploited to actually change anything. :confused:
      Then again, how many exploit security patches do we have every year. 🙃


      Before I updated my 5 to the April build (redfin-ota-rq2a.210405.005 at the time), that was the same error it gave me.
      I am not sure why since I was connected to WiFi and I still have not installed a sim card in my 5.
      I wonder if it would have made a difference updating using the updater instead of downloading and sideloading the recovery OTA. ?
      As noted, I bought the unlocked version directly from Google, so there should have been no issue unlocking the bootloader before updating.


      My Pixel 4a (sunfish) and 5 (redfin) are on stock Google Android 11.
      April 2021 build. I will update them to the May 2021 today or tomorrow.

      I will let you know what I find. :D

      Cheers. :cowboy:
      well heres what little bit I found on what the chromeOS cable is. From Amazon:
      When you attach it to a supporting port, Google devices enable a USB port on SBU which exposes a bunch of endpoints, including UART (accessible with standard serial drivers) for both the embedded controller and Linux consoles, and, depending on the state of your system, a way to flash firmware using the open-source servod software and flashrom.
      1
      I wanted to look into citadel a bit more before I went to far. ;)
      Ran out of time to do some testing.

      From what I found, it seems citadel might just be a reporting tool for the Titan M chip first introduced in Pixel 3.
      Google Blog - WebSite - Titan M makes Pixel 3 our most secure phone yet Link

      Not sure if it can be used/exploited to actually change anything. :confused:
      Then again, how many exploit security patches do we have every year. 🙃


      Before I updated my 5 to the April build (redfin-ota-rq2a.210405.005 at the time), that was the same error it gave me.
      I am not sure why since I was connected to WiFi and I still have not installed a sim card in my 5.
      I wonder if it would have made a difference updating using the updater instead of downloading and sideloading the recovery OTA. ?
      As noted, I bought the unlocked version directly from Google, so there should have been no issue unlocking the bootloader before updating.


      My Pixel 4a (sunfish) and 5 (redfin) are on stock Google Android 11.
      April 2021 build. I will update them to the May 2021 today or tomorrow.

      I will let you know what I find. :D

      Cheers. :cowboy:

      Control of firmware write protect.

      Flashing of the AP and EC firmware.

      EC RW console access.

      Read I2C INA219 current sensors (though most production boards do not have them populated).

      A subset of these features (e.g., UART lines) can be accessed without a cros_sdk chroot.

      Once the SuzyQ is plugged in, three /dev/ttyUSB devices will enumerate:

      1. Cr50 console
      2. CPU/AP console (RW)
      3. EC console (RW)

      I wanted to look into citadel a bit more before I went to far. ;)
      Ran out of time to do some testing.

      From what I found, it seems citadel might just be a reporting tool for the Titan M chip first introduced in Pixel 3.
      Google Blog - WebSite - Titan M makes Pixel 3 our most secure phone yet Link

      Not sure if it can be used/exploited to actually change anything. :confused:
      Then again, how many exploit security patches do we have every year. 🙃


      Before I updated my 5 to the April build (redfin-ota-rq2a.210405.005 at the time), that was the same error it gave me.
      I am not sure why since I was connected to WiFi and I still have not installed a sim card in my 5.
      I wonder if it would have made a difference updating using the updater instead of downloading and sideloading the recovery OTA. ?
      As noted, I bought the unlocked version directly from Google, so there should have been no issue unlocking the bootloader before updating.


      My Pixel 4a (sunfish) and 5 (redfin) are on stock Google Android 11.
      April 2021 build. I will update them to the May 2021 today or tomorrow.

      I will let you know what I find. :D

      Cheers. :cowboy:

      So apparently this debug cable does quite a bit of things. Including to some capacity the ability to read and write. If the device is supported, you have access to Closed Case Debugging and Servod. Some features this cable allows when they are activated in a chroot chromeOS environment using hdctools:

      Control of firmware write protect.

      Flashing of the AP and EC firmware.

      EC RW console access.

      Read I2C INA219 current sensors (though most production boards do not have them populated).

      A subset of these features (e.g., UART lines) can be accessed without a cros_sdk chroot.

      Once the SuzyQ is plugged in, three /dev/ttyUSB devices will enumerate:

      1. Cr50 console
      2. CPU/AP console (RW)
      3. EC console (RW)

      Source: https://chromium.googlesource.com/chromiumos/third_party/hdctools/+/HEAD/docs/ccd.md
      1
      For those of you following my latest to do, I ordered the ChromeOS debugging cable and it arrives Sunday. If anyone is interested in one of their own, you can get them on Amazon, as well as a few other sites that are cheaper, but take longer to receive. Here is a link for your reference: https://www.amazon.com/gp/aw/d/B07XF7V6CW?ref=ppx_pt2_mob_b_prod_image
    • 4
      Bro how can i directly contact you i am not undrstnding cuz i am new to oneplus .. and my android version is still 10.0.12
      Hi
      I don't know what you are talking about here or who you are replying to.
      In the future, please use the reply option when replying to someone. That way the person you are replying to will get a notification. Also, someone like me coming across your post can click on what you are replying to and go back to see the conversation and might be able to jump in to help.
      3
      I'm receiving a Galaxy A52 5G (first Samsung phone since the S2) tomorrow and I would appreciate if someone could point me toward some guides/tools to help get rid of bloatware (I believe the device comes with ONE UI 3.1 be default). I'm interested as well in any ressources to help enhance security/privacy, last few devices were running Lineage OS but I don't want to mess things to much for fear of triggering the Knox feature, at least as long as I got the warranty valid.
      Any attempt to root it or unlock it will trigger the Knox/security features and of course the warranty so if you want to stay in the safe side the most you can do by now to "get rid of" (not totally) is disable them using this method https://www.xda-developers.com/disable-system-app-bloatware-android/ be careful to not disable essential apps, also surprisingly there is a lot of real (that I should call them) bloatware that can be uninstalled too.
      3
      Doesnt that oem unlock option just enable/allow unlocking the bootloader, instead of unlocking right away?

      I tried the oem unlock toggle but i think the bootloader is still locked.

      It seems i cant do much with the phone if the charging port is broken.
      Yes, once the OEM unlock option is enabled you can go to the next level rooting it or installing TWRP at least in the first firmware versions (I had one) but actually the most reliable rooting method is Magisk in my opinion, in the old days worked an app called FlashFire, that could flash the firmware directly onto device but it´s now deprecated. For the many inconvenience that make a broken charging port you should rethink it if you are able to repair it at a certain time.
      3
      I've came across a debloat list labelled samsung (2020) and I was wondering if I could use that as is or should I trim it down.
      I don´t think you can use that list as it is, there are some essential and dependencies to some apps can work well. You only should disable those that can you see and interact with as user and that may consume more resources, in my opinion not those from the core.
      2
      Hi guys i'm new here and i don't know if i am writing my request at the right place. if i am not i am sorry.i have a lenovo tab 4 10 plus (TB-x704L) and i think that i bricked my device.i had the android 10,but i didn't like it and i have decided to put again the stock rom(7.1).i tried with qfil and with the lenovo rescue and smart assistance and i probably did something wrong and now my tablet cannot be recognizable by windows(minimal and fastboot don't find the device),but the most importan is that i can't get to the andoid home screen,always reboots at the set up android stage.i tried with qfil again,some imgs takes them some others not (sahara problem or it doesn't find any port).I tried to search the forum about this,but i didn't find anything.Please someone help me.Luckily the tablet has waranty until august,but i am afraid that they will tell me that it is my fault and they will ask me to pay.Thank you.
      Sorry, I doubt that a device that was shipped with 7.1 reached A10 anyway devices since MM don´t admit downgrades.

      The better would be try to restore the firmware that was the latest upgrade.

      If this is succesfull atleast to flash it but some stuffs won´t work anymore then you should claim your warranty.
    • 373
      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]
      107
      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
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone