• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
Search This thread

immortalneo

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

SubwayChamp

Senior Member
Aug 6, 2016
3,093
2
1,331
"it could be that the capacity was overpassed either for a huge number of tasks or a huge number of devices operating at same time (connected to your PC)" could you elaborate on this?
When you connect to a PC 2 or more devices, or you try to do simultaneously 2 or more tasks; sometimes fastboot couldn't work properly, Of course if you try to do one or both things properly fastboot can work though, just guessing that this can be one of the reasons from the various possibilities. Your previous post needs more info to accurately target to a specific direction.
 

Dudstis

Member
Jul 23, 2021
5
1
When you connect to a PC 2 or more devices, or you try to do simultaneously 2 or more tasks; sometimes fastboot couldn't work properly, Of course if you try to do one or both things properly fastboot can work though, just guessing that this can be one of the reasons from the various possibilities. Your previous post needs more info to accurately target to a specific direction.
What information do I need to post?
 

SubwayChamp

Senior Member
Aug 6, 2016
3,093
2
1,331
What information do I need to post?
Everything that can clarify your own post and what you are trying to do exactly.

For example:
- Which device do you own?
- Which Android version?
- Bootloader is already unlocked?
- How good is your connection through fastboot? Did you update the binaries?
- How did you try to install/flash Magisk, and How ends the attempt to install it?
- Were you able to check it by rebooting to system and checking if Magisk is there?

And just now, the second part:
- Which moment TWRP came into scene here? I mean; Did you install it prior to try Magisk or after?
- Which method did you use to install your TWRP?
- From which screen the message came?
 

Dudstis

Member
Jul 23, 2021
5
1
Everything that can clarify your own post and what you are trying to do exactly.

For example:
- Which device do you own?
- Which Android version?
- Bootloader is already unlocked?
- How good is your connection through fastboot? Did you update the binaries?
- How did you try to install/flash Magisk, and How ends the attempt to install it?
- Were you able to check it by rebooting to system and checking if Magisk is there?

And just now, the second part:
- Which moment TWRP came into scene here? I mean; Did you install it prior to try Magisk or after?
- Which method did you use to install your TWRP?
- From which screen the message came?
- Which device do you own?
- Which Android version? Xiaomi Redmi 9
- Bootloader is already unlocked? Yes
- How good is your connection through fastboot? Did you update the binaries? I updated the binaries I don't know how to measure how good my connection is through fastboot
- How did you try to install/flash Magisk, and How ends the attempt to install it? I start off by flashing twrp as my recovery image then flashing vbmeta once I try to boot recovery by typing "fastboot boot twrp.img" I get the afore mentioned too many links error
- Were you able to check it by rebooting to system and checking if Magisk is there? Don't you need twrp to install magisk

And just now, the second part:
- Which moment TWRP came into scene here? I mean; Did you install it prior to try Magisk or after? When I tried to boot into recovery after flashing twrp.
- Which method did you use to install your TWRP?
- From which screen the message came? The command line.
 

SubwayChamp

Senior Member
Aug 6, 2016
3,093
2
1,331
- Which device do you own?
- Which Android version? Xiaomi Redmi 9
- Bootloader is already unlocked? Yes
- How good is your connection through fastboot? Did you update the binaries? I updated the binaries I don't know how to measure how good my connection is through fastboot
- How did you try to install/flash Magisk, and How ends the attempt to install it? I start off by flashing twrp as my recovery image then flashing vbmeta once I try to boot recovery by typing "fastboot boot twrp.img" I get the afore mentioned too many links error
- Were you able to check it by rebooting to system and checking if Magisk is there? Don't you need twrp to install magisk

And just now, the second part:
- Which moment TWRP came into scene here? I mean; Did you install it prior to try Magisk or after? When I tried to boot into recovery after flashing twrp.
- Which method did you use to install your TWRP?
- From which screen the message came? The command line.
In case Lancelot is your variant, this guide and the zip containing TWRP includes the scripts you need to ease your task https://forum.xda-developers.com/t/twrp-recovery-for-miui-12-a11-lancelot.4300657/, from what I understood you didn't really tried to flash Magisk, but you wanted to and no, you also have other ways to get magisk to work like patching the boot image and after that flashing it either through fastboot or through SPFlash tool.

Check if these are the commands you are typing and that those images are there (in the same folder directory where you are opening the fastboot window):
Firstly, rename your recovery image to recovery.img
and then type as follows:
fastboot flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot recovery.img
If for some reason device refuses to boot to TWRP by command you can do it manually typingfastboot reboot and quickly pressing and keeping pressed the vol. up button
 
  • Like
Reactions: Dudstis

Dudstis

Member
Jul 23, 2021
5
1
In case Lancelot is your variant, this guide and the zip containing TWRP includes the scripts you need to ease your task https://forum.xda-developers.com/t/twrp-recovery-for-miui-12-a11-lancelot.4300657/, from what I understood you didn't really tried to flash Magisk, but you wanted to and no, you also have other ways to get magisk to work like patching the boot image and after that flashing it either through fastboot or through SPFlash tool.

Check if these are the commands you are typing and that those images are there (in the same folder directory where you are opening the fastboot window):
Firstly, rename your recovery image to recovery.img
and then type as follows:
fastboot flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot recovery.img
If for some reason device refuses to boot to TWRP by command you can do it manually typingfastboot reboot and quickly pressing and keeping pressed the vol. up button
Thank you so much without your help I wouldn't of been able to install TWRP and the Magisk root.
 
  • Like
Reactions: SubwayChamp

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,624
5,399
Sydney
Hello,
I have a problem I am trying a mod game apk which consists of a mod menu and when I allow display over other apps it crashes the game. I tried it on other devices it's working fine but on my onplus7pro android version 11 it's crashing. Sorry if I am posting in the wrong thread/forum.


You explicitly say it crashes the game. A logcat of that would be the oblivious starting point.
 

forstar

Member
Jun 28, 2021
13
0
I have tablet with intel atom processor running on android x86 and has one problem the orientation are reversed i.e when the device is in horizontal the display becomes vertical and vice versa. Can anybody help in solving this issue?
 

selife

Member
Jul 22, 2021
6
2
Gentlemen who own the POCO X3 PRO device and have the crDroid 7.8 firmware, a moment of attention!
Please tell me, did the new version(the problem was on 7.6) fix the excessive sensitivity of gestures? I am specifically interested in the function of quickly switching applications(a gesture from below - to the side). The problem occurred when I completely removed the navigation line from the bottom. When trying to switch the language, another application was constantly opened, which was very annoying when using the keyboard, since I was used to using swipe language switching (swiftkey keyboard)
 

mstrnemo

Senior Member
Feb 1, 2021
130
14
@
I apoligize i am an idiot i didnt put it in fastboot mode been a long day....
now it worked.

C:\Users\nnnnn>fastboot getvar all
(bootloader) hw-revision:20001
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4058
(bootloader) version-baseband:1307-7511_47.2.A.11.228
(bootloader) version-bootloader:1306-5035_X_Boot_MSM8998_LA2.0_P_114
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:MSM UFS
(bootloader) partition-type:xblbak:raw
(bootloader) partition-size:xblbak: 0x3F5000
(bootloader) partition-type:xbl:raw
(bootloader) partition-size:xbl: 0x3F5000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x587D76000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x138800000
(bootloader) partition-type:vendor:raw
(bootloader) partition-size:vendor: 0x60000000
(bootloader) partition-type:eek:em:raw
(bootloader) partition-size:eek:em: 0x19000000
(bootloader) partition-type:rdimage:raw
(bootloader) partition-size:rdimage: 0x2000000
(bootloader) partition-type:fsmetadata:raw
(bootloader) partition-size:fsmetadata: 0x101000
(bootloader) partition-type:Qnovo:raw
(bootloader) partition-size:Qnovo: 0x1800000
(bootloader) partition-type:diag:raw
(bootloader) partition-size:diag: 0x2000000
(bootloader) partition-type:appslog:raw
(bootloader) partition-size:appslog: 0x1000000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x17C00000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x1000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x200000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x200000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:FOTAKernel:raw
(bootloader) partition-size:FOTAKernel: 0x4000000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x20A4000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x1000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:bluetooth:raw
(bootloader) partition-size:bluetooth: 0x100000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x6E00000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x180000
(bootloader) partition-type:persist:raw
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:xflkeystorebak:raw
(bootloader) partition-size:xflkeystorebak: 0x20000
(bootloader) partition-type:xflkeystore:raw
(bootloader) partition-size:xflkeystore: 0x20000
(bootloader) partition-type:tzxflbak:raw
(bootloader) partition-size:tzxflbak: 0x80000
(bootloader) partition-type:tzxfl:raw
(bootloader) partition-size:tzxfl: 0x80000
(bootloader) partition-type:tzxflattestbak:raw
(bootloader) partition-size:tzxflattestbak: 0x80000
(bootloader) partition-type:tzxflattest:raw
(bootloader) partition-size:tzxflattest: 0x80000
(bootloader) partition-type:xflbak:raw
(bootloader) partition-size:xflbak: 0x1E00000
(bootloader) partition-type:xfl:raw
(bootloader) partition-size:xfl: 0x1E00000
(bootloader) partition-type:storsecbak:raw
(bootloader) partition-size:storsecbak: 0x20000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x20000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x20000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x80000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x80000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x80000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x80000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x80000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x80000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:ablbak:raw
(bootloader) partition-size:ablbak: 0x180000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x180000
(bootloader) partition-type:pmicbak:raw
(bootloader) partition-size:pmicbak: 0x80000
(bootloader) partition-type:pmic:raw
(bootloader) partition-size:pmic: 0x80000
(bootloader) partition-type:hypbak:raw
(bootloader) partition-size:hypbak: 0x80000
(bootloader) partition-type:hyp:raw
(bootloader) partition-size:hyp: 0x80000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:rpmbak:raw
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:LTALabel:raw
(bootloader) partition-size:LTALabel: 0x1000000
(bootloader) partition-type:TA:raw
(bootloader) partition-size:TA: 0x200000
(bootloader) secure:no
(bootloader) serialno:BH9068FD9E
(bootloader) serial:7f4a60a
(bootloader) product:G8441
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.533s

C:\Users\nnnnn>
@SubwayChamp

Sorry for late reply, i tried it and made sure everything was on however when flashing vbmetafile i stil get this message

C:\Users\nnnnn>fastboot flash vbmeta C:\Users\nnnnn\Desktop\vbmeta.img
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.016s]
writing 'vbmeta'...
FAILED (remote: Flashing is not allowed for partition
)
finished. total time: 0.031s


I then flashed magisk like u mentioned using twrp it said it failed but when i tried to reboot it worked phh aosp gsi rom booted!

Qeustion any idea why i cant flash vbmeta file ? is that a bad sign?

what is the difrence between flashing magisk and vbmeta do they do the same thing? is there no difrence now ? is what i have done oke ? also will flashing magisk to get the gsi to startup work for all gsi?

Personally i would prefer to flash vbmeta i mean why wont it flash???
 

SubwayChamp

Senior Member
Aug 6, 2016
3,093
2
1,331
@

@SubwayChamp

Sorry for late reply, i tried it and made sure everything was on however when flashing vbmetafile i stil get this message

C:\Users\nnnnn>fastboot flash vbmeta C:\Users\nnnnn\Desktop\vbmeta.img
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.016s]
writing 'vbmeta'...
FAILED (remote: Flashing is not allowed for partition
)
finished. total time: 0.031s


I then flashed magisk like u mentioned using twrp it said it failed but when i tried to reboot it worked phh aosp gsi rom booted!

Qeustion any idea why i cant flash vbmeta file ? is that a bad sign?

what is the difrence between flashing magisk and vbmeta do they do the same thing? is there no difrence now ? is what i have done oke ? also will flashing magisk to get the gsi to startup work for all gsi?

Personally i would prefer to flash vbmeta i mean why wont it flash???
There also other known commands that may or may not work onto your device,
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot oem disable_dm_verity
But sometimes the script file that disable the verification boot could be included in the boot itself or in the recovery anyway Magisk has, as I said you before the ability to bypass DM Verity.
It could happen also that you need a signed vbmeta to get it to work, if this is the case there are some tools in GitHub that can patch the vbmeta file from your stock ROM.
Also consider that the whole point to use a vbmeta is that the boot process won't be interrupted, so at this point you had success.
 

ibaj69

New member
Jan 16, 2015
4
0
I hope I am asking in the right place, but here goes!

I have purchased an international S9 SM-G960F. I have been looking for days for a reason it wont work here in the USA. everyone says it should but it dont. So I got devcheck and I found out that it has a snapdragon proccessor and that knox has been tripped, also usb debugging is active. My question is, could this be a phone that has had international firmware flashed on it (since its snapdragon) and if so can I flash it back? Thank you for any information as I have been round and round on this.
 

mstrnemo

Senior Member
Feb 1, 2021
130
14
There also other known commands that may or may not work onto your device,
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot oem disable_dm_verity
But sometimes the script file that disable the verification boot could be included in the boot itself or in the recovery anyway Magisk has, as I said you before the ability to bypass DM Verity.
It could happen also that you need a signed vbmeta to get it to work, if this is the case there are some tools in GitHub that can patch the vbmeta file from your stock ROM.
Also consider that the whole point to use a vbmeta is that the boot process won't be interrupted, so at this point you had success.

I was hoping to learn more about this for future referance.
but that i cant get this vbmeta file to work really bugs me ahhahaha
i supose that if magisk basicly does the same then i geuss ill leave it at that

although i do wonder how do you update a gsi ? does it work the same as a custom rom where u flash over it ? if so then i take it magisk needs to uninstalled before that ?

Anyway i wish there was more out there about all this gsi stuf would make it easier oh and i tried phh treble aosp gsi first worked pretty wel after i tried linage os 18.1 gsi wich i have been using the past day and it works pretty well camera doesnt work and some little glitches here and there and batterie life isnt as good but all in all i am impressed.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Mod edit - translated by https://www.deepl.com/translator:
    Greetings. Help me out here. Need to put Xposed on Meizy m3 note.
    Rooted through settings, security settings have "root" button.
    But can not activate xposed. I have tried different versions, no luck. I am attaching a photo of the error.
    *********************************************************
    Приветствую. Помогите разобраться. Нужно поставить Xposed на Meizy m3 note.
    Сделала рут через настройки, в настройках безопасности есть кнопка "root".
    Но не могу активировать xposed. Пробовала разные версии, не получается никак. Прикрепляю фото ошибки.
    @YanaMur

    As courtesy, I've translated your post above. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Russian posts. Thanks for your cooperation!
    4. Use the English language.

    We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.

    Regards
    Oswald Boelcke
    Senior Moderator
    The forum rules require your posts to be posted in English at the top of your post. You can still post in your native language but the English must be at the top of your post and then below that you can post in your native language.
    @Droidriven Just a very small request. Please only report such posts! This will allow us to immediately add a translation as courtesy to the benefit of all users; and we'll simultaneously make aware about the rules. Tanks very much for your cooperation.
    3
    ....snip...

    In the practice it's impossible to have a Samsung Q ROM for a Samsung device that official support stopped at Nougat, or at least I have never seen that. The most I could see is one and only one major update, of course may I totally wrong but never saw more than one update not supported officially.
    Funny you should chose Samsung for you example, my previous / spare device device is a Samsung S4 from 2013, which had official support stop at Lollipop (ie android 5, 2 before Nougat). There is an unofficial ROM using the blobs from the last official release for a current LineageOS 18.1 (ie R, ie Android 11), so that is the next version of android past Q. There is also talk of people starting builds of android 12 for this device. So it is very possible, but it also goes beyond the issue of manufacturers releasing the full source.

    I used to build ROMs from source for this device and a few other even older devices (and released here on XDA), which were well beyond the last official versions released by the manufacturer (from jelly bean to lollipop I think on another). That is one of the reasons for using/building custom ROMs on older devices. ie to upgrade your android version beyond official manufacturer support. To enable building these ROMs, more than just the Kernel needs to be attained. The example I gave a link for is simply just one case I found in a single web search. If you read the article, it actually talks of samsung releasing their source quickly, which I would assume is the full source of the ROM, but not the source for proprietary hardware drivers.
    2
    Got a Droid Turbo with LineageOS recovery, only seen as offline, even with a 'factory' cord. Data and system were wiped to try to start anew, but the unexpected offline condition prevents any side loading. Any tips on how to remove the offline condition? My apologies if this is the wrong forum.
    It seemed better to answer you in this thread.
    Hi. :)

    I do not have the device and do not know your setup, so generic answer. ;)
    • Some devices have issues with USB ports, best to use a USB 2.0 port.
      Also try a different USB port and/or USB cable.
      If it is a USB-C to USB-C cable, try switching it (End B to computer, End A to device.)​
    • Windows - Make sure you have the correct (additional) drivers installed for the device when is in fastboot mode.
    • linux - Make sure you have access to USB.
      Depending on the linux distro you are running..
      Make sure the device is set in your udev-dev-rules and you (user) are part of the plugdev group.
      adb might be able to connect, that is a different connection than fastboot.​
    • macOS - Normally works out of the box once platform-tools are installed.

    Hope something above helps. 🙃

    Maybe another member (who knows more about the issue you are running into) is willing to help. :D


    Cheers. :cowboy:

    PS.
    For anyone who is looking for the official link. :whistle:
    SDK Platform Tools - developer.android - WebSite - Link
    1
    • Bad news: my paid leave days are up, so I'm only able to try to recover the data in my spare time.
    • Good news: I'm coping. I already bought a Galaxy S21 (let's hope Samsung takes software update QA more seriously). I am keeping the Realme device untouched, installing regular updates, hoping for future fixes (perhaps when Realme releases Realme UI 3.0/Android 12 for this phone, another major update will fix this problem and flashable using stock recovery without triggering a wipe).
    Not sure if this tip appears in that tutorial, usually flashing through SP Flash tool the process takes no more than 10 minutes or so.

    When you bypass the BROM restriction and your device is enabled to operate with the tool, you have to set these values; in Options/General uncheck Check LIB DA match and Storage Life Cycle Check, and in Options/Connetion/Conection Settings enable UART and set Baud rate to 921600, this is to speed up the flashing process to a low level, you have to check this option every time you flash otherwise is constantly set to its original value to 115200, also check in the Format tab the option to Flash all except bootloader.
    Thank you for the suggestion. However, tinkering with these settings cause flashing to fail midway. Maybe it doesn't fail every time, but I'm not in a hurry.

    Isn't the firmware you can flash through SP Flash tool the same you can do it through the Realme Download tool, but with the main difference that in Realme Download tool the file doesn't need to be extracted from the original ofp format?
    My understanding:
    • SP Flash Tool: a backup software (can get data from phone and backs it up like UNIX's dd), shows partitions and could selectively restore it bit by bit.
    • Realme Download Tool: a one-way tool to flash firmware files to the device. Will flash the entire device.
    I suggested to flash using this method in the hope your device can be restored to its original functional state to can after that unlock bootloader and this way you could restore the userdata partition, while your device is with locked bootloader it will refuse to boot with that restored/unauthorized partition due to the integrity check.
    • Good news: the bootloader was successfully unlocked, installed a custom recovery, and got Realme UI 1.0 up and running (rooting unsuccessful). Then restore the userdata partition.
    • Bad news: The device throws all sorts of errors, even in Safe Mode. After some digging, apparently, Realme UI 2.0 introduces an encryption model change. Realme UI 1.0/Android 10 used FDE (you must enter a password before booting Android). Meanwhile, Realme UI 2.0/Android 11 uses FBE (the device boots up completely then asks you for a password. Phone calls, alarms, and even emergency mode work before the device is unlocked). Previously, this was a sign that the device was locked but not encrypted. However, this is the new encryption model in Android 11, and apparently, it's safe. It seems that Android made FBE available on Android 7 and required it on Android 10. Yet somehow, Realme just implemented it on Android 11.
    • Worse news: The encryption algorithm and working mode is also changed from AES-128-CBC-ESSIV to AES-256-XTS.
    • Worst news: Apparently, the encryption key is not stored in userdata partition; hence overwriting partitions like this are possibly dead-end. Restored the device from its full backup.
    • A glimmer of hope: I have been downloading and successfully installing OZIP updates in recovery. Just put the OZIP (must be official) in the SD card, and apparently, a monthly security patch is installed. Will wait for a monthly update to fix this issue (slim chance) or for Realme UI 3.0 to fix it (a good chance, but not quite assuring).
    1
    If you for your own have the knowledge to do it or take it to the repair center where they replaced the battery, if it was the case.

    When there is a bad connection, this kind of issues is expected to happen.
    It was my little diy :D
    I will try doing that after work and tell you how it goes.
    Thanks!
  • 381
    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]
    111
    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