Database Info

Huawei Ideos Super FAQ

This is an FAQ for the Huawei Ideos as there have been many questions on how to do the same things. Hopefully this should help. There are other FAQs but this one tries to compile as many as it can into one FAQ.
Feel free to reply to this if there are any questions or if you want me to make any additions. The FAQ won't be complete to begin with but I will add as I get time.
One thing I will say is that I WON'T TAKE RESPONSIBITY IF YOU DAMAGE YOUR PHONE. I AM PROVIDING THE INFORMATION AND WILL TRY TO HELP YOU IF SOMETHING BAD HAPPENS BUT I CAN'T TAKE ANY RESPONSIBILITY
1. How to root the IDEOS
This can be done quite simply by adapting what quail wrote:
There is a couple away you can go about gaining root access with this phone I have tested all 3 ways but only had success with 2 of them.
a) You can download 'z4root' from here (WORKS)
b) Search the XDA forums for 'SuperOneClick' which requires mono to work on Linux. I have read people that have had success with 'SuperOneClick' but that was not the case for me. (HAVEN'T CHECKED)
c) My preferred method: (HAVEN'T CHECKED)
Prerequisite:
knowledge of Linux and Terminal
knowledge of ADB (guide available in forums)
I did all this using Debian (testing) 64bit, Android SDK.
Creating correct permissions to access the phone via USB:
i) create
Code:
/etc/udev/rules.d/51-android.rules
ii) in the file put
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
iii) then
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
iv) restart udev or reboot
Downloading and/or Installing required software:
1) Downloading and installing the android-sdk from: developer.android.com/sdk/index.html
2) Downloading and extracting 'SuperOneClick' (you will only need these 5 files: rageagainstthecage, sqlite3, su, busybox and superuser.apk)
3) Copy rageagainstthecage, sqlite3, su, busybox and superuser.apk into the platform-tools directory of android-sdk. Put phone in debug mode.
4) From a terminal (command line) change to the android/platform-tools directory and carefully do these steps.
Check to see if adb can see your phone properly:
Code:
./adb devices
You should see the serial number of you device, if you see bunch of '?' you have done something wrong.
Now for the fun part rooting the phone: <= no phun intended hehe
Code:
./adb push rageagainstthecage /data/local/tmp/rageagainstthecage
Code:
./adb shell
Code:
cd /data/local/tmp
Code:
chmod 0755 rageagainstthecage
Code:
./rageagainstthecage
5) Now wait until you get kicked out from adb before you do the following:
Code:
./adb shell
If everything worked now you should see a "#" instead of the "$" you saw previously in the adb shell which means you shouldn't get "permission denied" in the following steps:
Code:
mount -o rw,remount /dev/block/mdtblock4 /system
Code:
exit
Code:
./adb push su /system/bin/su
Code:
./adb push busybox /system/bin/busybox
Code:
./adb push sqlite3 /system/bin/sqlite3
Code:
./adb push Superuser.apk /system/app/Superuser.apk
Code:
./adb shell
Code:
cd /system/bin
Code:
chmod 4755 su
Code:
chmod 4755 busybox
Code:
chmod 4755 sqlite3
Code:
./adb reboot
Now you should be able to use apps like 'Cache Cleaner NG', 'Root Explorer', 'SetCPU' etc that require root access to work correctly.
Enjoy​
2. How to flash the Ultrakiller Recovery Image
Now this has been covered many times but there have been a lot of problems with the BSOD on the IDEOS. A few days ago Ultrakiller came up with a solution that works regardless of the LCD type. Now this was distributed as an IMG file so many people were confused so here is a link to one with everything you need included. All I did was remove the amon'ra image and copied the Ultrakiller recovery IMG to the folder and edited the scripts to point to the new file.
After you download the file:
* Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys (Yes, bootloader is just the IDEOS logo) WHILE YOUR DEVICE IS PLUGGED IN
* WINDOWS - double click 'install-recovery-windows.bat'
* MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-mac.sh' followed by './install-recovery-mac.sh'
* LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-linux.sh' followed by './install-recovery-linux.sh'​
See Q3 if you have Windows and the prompt hangs on "Waiting for Device"
3. How to solve problems with drivers on Windows in bootloader mode?
1. Unplug your phone
2. Download and install PDANet from here - at the end of the setup it will tell you to plug in your phone - do that
3. Put the phone into bootloader (See Q2 above)
4. Go to device manager and right click on "Android 1.0" and click "Update drivers"
5. Click "No, not this time" and Next
6. When it asks you where to look for drivers point it to PDANet's install location
7. Hopefully it should find the driver and prompt you to install it - it will take some time
8. You can now access your device in bootloader!​
Thanks to the following people:
Quail for the base of the guide and the ROM I'm using - it's amazing BTW
Ultrakiller for the recovery image
Changelog:
21/01/2010: Initial writeup
22/01/2010: Added Q3 and made some minor changes​

i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...

Hi - the Ultrakiller recovery IMG in the ZIP from the Link above is "Ultrakiller.img.img". Dunno if it didnt work cause of this - sry didnt test, just downloaded new Ultrakillers "UltraJack-Recovery_v4.6.2.img", saved into that folder and changed the .bat to "fastboot-windows.exe flash recovery UltraJack-Recovery_v4.6.2.img" and it worked for me Even superuser.apk didnt work for usb-root but z4root does it perfect and DroidExplorer showing files now .
Thanks so far to all investing their time here
P.S.: the HUAWEI background of Ultrakillers recovery is very delicious

General guide to Flash ROM
Can you please provide a detailed guide for flashing Huawei Ideos. Because it is super guide. So it must contain this topic also.
I want to flash official ROM on following link:
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
Waiting for your response

yrnehukuht said:
i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...
Click to expand...
Click to collapse
Dear have u find out the solution of this problem?? COZ im also suffering from this if u find it then plz tell me [email protected]

I have downloaded a rom from xda-developers wiki from this link
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
then updated my device software by going in to update mode(press vol up + end key + power button) .
This step returned me my original recovery.
But I am not going to recommend it bcoz i am facing problems like my cd drive which is automatically displayed has become inaccessible.
I am having problem to copy files to sd card.
My upgrade mode is not working now.
all these things were working immediately after the above mentioned process but I am now stuck with these things.
I think it is because i have flashed lower version number of rom on phone.
If you want to recover recovery mode only then I have successfully flashed UltraJack-Recovery 5.2.1 from this link
http://forum.xda-developers.com/showthread.php?t=860189&page=24
Inform about your progress

Thanx. Very useful

Hi guys. I am in a lot of trouble with my ideos.
Tried installing a custom ROm using ROM manager and it failed, although the original ROM is still there and its booting up and working perfectly.
However, when i try to boot into recovery, only the lit blackscreen shows.
I have tried everything from running ULTRAjack recovery on windows(which only shows 'waiting for device' on cmd, with the pdanet drivers installed) to ubuntu(which shows 'waiting for device' on Amon-ra recovery and permission denied on ULTRAjack).
Could it be i didnt root the device properly since i used z4 root?
Any more ideas?

900/2100 or 850/1700/1900/2100
Hello, How do I tell which sub-model my U8150 is please? Either HSDPA 900 / 2100 / AWS or HSDPA 850 / 1900 / 2100 / 1700. baseband = 22201003; build no.= U8150V100R001C183B825; IMEC = 355093040562676; IMEC-SV = 39.

Check out your fcc id suffix. I have heard there is a b version and a d version.

hi do flashing many roms affects my ideos mobile?

netskink said:
Check out your fcc id suffix. I have heard there is a b version and a d version.
Click to expand...
Click to collapse
All I got is a U8510-1, no letter... any thoughts?

Unlock u8150
Hello.
i have a T-Mobile Ideos u8150, also known as Comet.
it is locked to T-Mobile and requests a pin code when using another sim card.
is there a way to unlock the phone?
please help me...
thank you.

Enable USB Debugging & One Click Root with Unlock Root Tool

[GUIDE] How to install SDK/ ADB and do a Logcat and some essential guides

Hello everyone at xda !
As a newcomer I was searching for a bit of help getting started with android tools and its development.
So I decided to help out the newcomers a bit more by creating this thread..
I found this to be essential for our HTC Explorer Development Forum
This guide contains :
Post 1:
Info about SDK / ADB and how to install them on linux and windows.
Logcat- How to logcat , types of logcats , meaning
Adb wireless
Post 2:
Clean install
Paritioning sd
Flashing kernel , recovery
Permissions
What is overclocking ?
Recover from OC
md5 checksum
Post 3:
Video tuts and credits.
Info about ADB/SDK :
ADB
What is adb ?
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
SDK
What is android SDK ?
Android software development is the process by which new applications are created for the Android operating system. Applications are usually developed in the Java programming language using the Android Software Development Kit, but other development tools are available. As of October 2012, more than 700,000 applications have been developed for Android, with over 25 billion downloads.The Android platform has also grown to become a favorite among mobile developers.
Want to download and use adb and SDK ( its in one package )?
Visit http://developer.android.com/sdk/index.html
Extract the files of the package you downloaded from the site as whatever you want to but remember it ?
Windows Specific (VISTA)
Keep your path name to which is extracted to
Eg : C:\(*package-name*) [ eg of package name : adt-bundle-windows-x86 ]
Rename the Folder to C:\(*Whatever you want to name it*) [ eg change "adt-bundle-windows-x86" to "android" ]
In order to run adb do the following steps :
Click start
Search for cmd
Right click and * RUN AS ADMINISTRATOR *
type the following commands
Code:
C:\Windows\system32\>cd C:\android*\sdk\platform-tools\ [*click enter*]
C:\android*\sdk\platform-tools>adb
C:\android*\sdk\platform-tools>adb devices
Now you should get a huge code block with all the adb commands
That means adb has been installed correctly.
adb devices gives you the list of attached adb devices and if their permissions are right..
Setting up ADB as a command on Windows 7/ Vista
Assuming you have done the above steps correctly you should have no problem going ahead
Right click on Computer
Click on properties
Go the advanced system settings
Click on the advanced tab
Go to Enviornmental variables in the dialog box
In system variables find the variable " Path ".
Double click on it and in variable value add the following line at the end of it :
Code:
;C:\android\sdk\platform-tools\;
Click on OK etc and save the settings
now Run command prompt
Type adb and your adb commands will be in function..
You can now run adb as a command and dont need to go to the directory every time.
Linux Specific ( Ubuntu )
PS (important) if someone has a 64bit linux then they need to download 32bit libs
for this, before all these steps run this
Code:
sudo apt-get install ia32-libs
You should have an updated JDK for this.. Just in case..
Code:
$ sudo add-apt-repository ppa:sun-java-community-team/sun-java6
$ sudo apt-get update
$ sudo apt-get install sun-java6-jre sun-java6-bin sun-java6-jdk
we need to make a new directory by this command
Code:
mkdir android
then extract by
Code:
tar -zxvf ~/Downloads/android-sdk_r21.0.1-linux.tgz
then move it to the directory we just made
Code:
mv android-sdk-linux ~/android/sdk
the open android sdk manager by
Code:
android/sdk/tools/android
this will open android sdk manager
we need to select just android sdk tools and android sdk platform tools for adb and then select install packages
^^this will download everything required
then we need to set a path to include adb
Code:
gedit .bashrc
and then a file opens and paste this text in that file
Code:
export PATH=${PATH}:~/android/sdk/platform-tools
then we make the above bashrc file executable by this
Code:
chmod a+x .bashrc
then we need to setup device rules and make that file executable
ps sample is the username
Code:
]sudo gedit /etc/udev/rules.d/51-android.rules
and copy and paste this
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
and then make rules executable by:
Code:
sudo chmod a+x /etc/udev/rules.d/*
we need to add full path to adb start server
Type :
Code:
sudo gedit /etc/rc.local
this will open a file
now add this line just above where it is written exit 0
Code:
/home/sample/android/sdk/platform-tools/adb start-server
"sample is username"
after this we dont need to cd to adb directory..we can just type adb devices and the phone will surely show up
Guide for Linux by Gnexus. Thank him Here!
Now we have a blooming xda forum at HTC Pico aka Explorer with :
Cyanogen mod 7
Cyanogenmod 9
Cyanogenmod 10
Cyanogenmod 10.1
Sense 3.5(stock)
Sense 4.0
Which is quite a lot considering our device is considered as
A legacy / low activity device
Click to expand...
Click to collapse
Now with all those ROMs come their respective bugs..
Just saying
" Random reboot "
" I dont know but xyz doesnt work "
" Xyz fces "
Click to expand...
Click to collapse
Gives just another burdening job for a ROM dev of trying to find that same mistake and trying to take a log of it..
At times they are on a different ROM and it becomes difficult for them to flash their old ROMs again..
Sometimes they dont even have the same device !!
So.. Try to ease the job of the dev by bringing whats called a logcat so you can do the following to help them out :
You should have installed adb and fastboot by now
For getting a logcat you should do the following easy steps
Connect phone to pc / laptop ( quite obviously )
Assuming you have rooted your phone you should have required drivers installed ?
To enable ADB mode on your phone go to settings > developer options > Debugging > USB Debugging > ON
1st go to cmd and run as administrator and go to the root of adb
simply type
Code:
C:\android*\sdk\platform-tools>adb logcat
and you get a logcat running on your screen
Want to post a logcat somewhere ?
1] A logcat that can be easily copy pasted and given to someone else :
to do that type :
Code:
adb logcat > cat.txt
*cat is just an example .. it can be Anything logcat.txt, catlog.txt, etc ( let your imagination go wild )
This gives you a logcat at the platform-tools folder .
Now if you get your logcat you can post the logcat somewhere in the dev threads as a whole logcat or you can put specific lines where you want the dev to look at or you know the error is present. There is a character number limitation on a single post on xda for which you can simply upload the .txt file or you can also post it on Pastebin and share the link/url on the thread. This helps a lot .
Alternatively there are apps such as aLogcat or Catlog but installing adb and fastboot is essential as it will not only help you with this but other functions also look further down..
Meanings of symbols in a logcat !
You usually see this at the start of a sentence in logcat .
I/> ===> Information
S/> ===> Silent
D/> ===> Debug
W/> ===> Warning
E/> ===> Error
F/> ===> Fatal
For more information about logcats
Help with solving a logcat from fellow members only for pico ! ​
DMESG (*Useful for devs / beta testers alike*)
Go to your adb directory via terminal / cmd on admin privileges
Type
Code:
adb shell dmesg > dmesgLOG.txt
Terminal emulator :
Code:
dmesg > /sdcard/dmesglog.txt
DMESG is useful for finding out errors / bugs in the hardware aspects caused due to software issues and kernel issues (* eg : deepsleep , bluetooth not working , wifi not working etc . *) which cannot sometimes be easily solved through a simple logcat.
Lastly K-MESG
To help solving with respect to kernels (* Yes it is a kernel not kernal... *)
Kernel issues like a kernel panic and similar. Similar steps to dmesg but the code is
Code:
adb shell cat /proc/last_kmsg > kmsg.txt (*via adb*)
cat /proc/last_kmsg > /sdcard/last_kmsg.txt (*via terminal emulator*)
ADB wirelessly
To use adb via Wi-Fi
Download this wonderful app from the playstore adbWireless
Click on the green button and an IP will come on the app screen. (* eg: 123.456.7.890 *)
On your computer go to your adb directory via terminal / cmd prompt
type
Code:
adb connect 123.456.7.890
Voila! You are using adb wirelessly
Some useful extra stuff !
Adb guide
Note : Please do not quote the entire first post in the replies !

Some other essential guides.
What do you mean by a clean install ?
WARNING ! : Do NOT wipe/format External storage . This will result in the loss of data.
A clean install can be done as follows :
On CWM / Yannou's recovery :
Boot into recovery
Do a factory reset
Go into mounts and storage using volume rockers and power button.
Format /system /boot /cache
Go to advanced : Wipe Dalvik Cache.
On TWRP Recovery :
Go to wipe
Wipe Cache , Dalvik Cache , System SD Ext and then do a factory reset.
Done ! Now flash the required ROM you want to flash!
How to partition SD card ?
Note :
This will result in your SD card being formatted. So always keep a backup of all your files on your computer.
For Stock ROM you need a FAT 32 partition which can be done via computer ONLY.
Via Recovery
Boot into recovery
Go to advanced
Partition SD card (*EXT 2,3,4 etc.*)
Select EXT Size *to whatever you want to preferably 512 mb or more*
Select Swap = 0 mb as Explorer doesnt support swap. ( at least till now )
Partition SD card! (*Will take some time*)
After partitioning is done just remove your SD card (*while your phone is off*) and just insert it back in manually.
Reboot /system (*if you have a ROM installed*)
Connect to PC and check for bad partitions just in case.
Steps 7,8,9 are not mandatory but are a good practice.
Via a computer : ( Windows )
Requirement :
SD Card reader
MiniTool Partition Wizard Home Edition 7.7 .
For further details on this visit this great guide
How to flash custom recoveries / kernels ?
How to flash a custom recovery ?
Via computer
Copy the recovery.img of the custom recovery you are try to flash and paste it in the adb directory ( for windows ==> C:\android\sdk\platform-tools\*paste here* )
Boot your Pico into bootloader (*remove battery and after 3-4 secs press vol. down and power button simeltaneously*)
In bootloader menu connect pc to your phone via usb cable and then there will be a red coloured sign just above the options saying
FASTBOOT USB
Click to expand...
Click to collapse
Now start
Windows Go to platform-tools directory in command prompt and type
Code:
fastboot flash recovery recovery.img
fastboot reboot
Linux Go to the directory of adb and fastboot and type in terminal
Code:
$ ./fastboot flash recovery recovery.img && fastboot reboot
or if path is set directly..
Via phone Terminal Emulator
Take the recovery.img that you want to flash and place it on your sd card ( eg /sdcard/(*here*) )
Begin Terminal emulator app (*Download from playstore*)
Type su (*enter*)
Allow superuser permissions (*enter*)
Note : Now you must get a line beginning with $
Enter
Code:
flash_image recovery sdcard/recovery.img
Still racking your brains over this ? Check out post 3 for video tuts !
For kernels do the same thing except replace replace Recovery.img with Boot.img
Setting permissions
Heard about setting permissions ? Ever wondered what they are ?
On a UNIX based system, every single file and folder stored on the hard drive has a set of permissions associated with it, which says who is allowed to do what with the file. Every file (and folder) also has an "owner" and a "group" associated with it. If you created the file, then you are usually the owner of that file, and your group, or the group associated with the folder you created the file in, will usually be associated with that file.
Click to expand...
Click to collapse
So how to configure them ?
You need a file explorer with Root access
Go to the required folder/app you want to set a permission and long press on it ( in most file explorers )
You will get something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select what is required and close.
Alternative via adb
Same as before from adb directory on cmd propt / terminal
Code:
adb shell
su
chmod 777 /system/app/Notes.apk
INDEX :
r = read w = write x = execute
Reference for chmod
So 777 = rwxrwxrwx 755 = rwxr-xr-x and so on and so forth..
What is overclocking ?
Overclocking is the process of making a computer or component operate faster than the specified clock frequency by the manufacturer by modifying system parameters. One of the most important techniques is running at a higher clock rate (more clock cycles per second; hence the name "overclocking")..
Operating voltages may also be changed (increased), which can increase the speed at which operation remains stable.
Pros : You get much more performance including gaming performance and overall UI performance..
Cons : Overclocking is always risky if something is configured improperly and may also result in permanent damage of your hardware. As long as it is done safely you are good to go.
You may see some increased power consumption.
Extreme overclocking might kill your hardware.
Undervolting :
The process where you provide less voltage to your cpu rather than the stock voltage.
Advantage:
Reduced heat from your device.
Good battery life.
Disadvantage:
Extreme undervolting will make your device unstable and some times even end up with a boot loop.
Recovering from an OC NAND Wipe..
cute_prince said:
Ok guys, here I am posting NAND Recovery Procedure:
Download the following attachment.. Rename flash_erase.txt to flash_erase ( Its actually a binary file )
Copy this file to /system/xbin directory using Root Explorer. Set permission as 755
Make sure Root Access is enabled for both Apps and ADB in Developer settings
Connect phone to PC .. Now open a terminal ( I am using Ubuntu ) and type the following:
Code:
[COLOR="Blue"]adb shell
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
./flash_erase -N /dev/mtd/mtd5 0 0[/COLOR]
Note: when you execute above command you may get an IO error.. Its OK, dont get panic
Now disconnect phone from PC.. Remove battery and reinsert it ..
Goto recovery and:
format /boot
format /system
wipe data / factory reset
Now install your favourite ROM
Once the ROM is booted, goto storage settings.. Everything should be fine now and you should get around 140MB free depending on your ROM
Click to expand...
Click to collapse
What is md5 ? How is it useful?
The MD5 Message-Digest Algorithm is a widely used cryptographic hash function that produces a 128-bit (16-byte) hash value. Specified in RFC 1321, MD5 has been utilized in a wide variety of security applications, and is also commonly used to check data integrity. MD5 was designed by Ron Rivest in 1991 to replace an earlier hash function, MD4. An MD5 hash is typically expressed as a hexadecimal number, 32 digits long.
What does it mean in english ?
For android basically it is used to maintain the uniqueness of a file. It is also used to check wheter the file is the same file that has been uploaded or not .. or wheter the the downloaded file is half downloaded or broken..
You can check the md5 sum of two files. If they match then they are the same file. If they dont .. back to your download screen.
How do I check the md5 sum ?
On windows :
Download this and extract it on your pc..
Just put in the file's location..
Get the md5 sum from the OP
Match them ..
On android
There is an app for it : Android Filve Verifier

Video Tutorial # 1 : How to flash any recovery thru terminal emulator ! By Rishik
Video Tutorial # 2 : How to take a backup of your system! By Rishik
Please thank him for it.. HERE !
Credits : bala_gamer, cute_prince , Genexus , Rishik999, wikipedia , sdk , many tutorials on xda and other forums... and google.

Re: [GUIDE] How to install sdk / adb and do a logcat
Wrong section post in general this isnt any development
Sent from my HTC Explorer A310e using xda premium
---------- Post added at 12:03 PM ---------- Previous post was at 12:01 PM ----------
Mods move this to general!
Sent from my HTC Explorer A310e using xda premium

I knew this was coming .. It is in many development sections even for my old device Sensation. Trust me it is needed in the development section. Mods are free to move it.. Even mentioned it in the first post.. as good as a guide on rooting the pico or even compiling a kernel. Dont you think ?
If you think the people actually read the general section why would the dev thread be full of so much spam ? :silly:

good..nice..
i think this will work on win 7 also??
and give a tut for linux too...if you want i can post one here!!

Adding a lot.. Even video tuts.. if possible..

Video Tutorials
I have recently made a tutor on how to flash recovery.img through terminal emulator
I guess OP needed them?
I hope,he wont mind sharing them
http://www.youtube.com/watch?v=ND9UvfV3G34
Liked it
Please hit the like button on the vedio
Ofc the thanks button also
Disliked?
Nevermind :victory:
Thanks!

Re: [GUIDE] How to install sdk / adb and do a logcat
Can u add guide how to adb via wireless
Sent from my HTC Explorer using xda app-developers app

Re: [GUIDE] How to install sdk / adb and do a logcat
KiranP23 said:
Can u add guide how to adb via wireless
Sent from my HTC Explorer using xda app-developers app
Click to expand...
Click to collapse
Yeah was about to add it soon...
Rishik999 said:
I have recently made a tutor on how to flash recovery.img through terminal emulator
I guess OP needed them?
I hope,he wont mind sharing them
http://www.youtube.com/watch?v=ND9UvfV3G34
Liked it
Please hit the like button on the vedio
Ofc the thanks button also
Disliked?
Nevermind :victory:
Thanks!
Click to expand...
Click to collapse
Adding them bro thanks a lot .. I'll pm you
Sent from my HTC Explorer A310e using xda premium

logcats
Thanks a lot OP for making this noob friendly guide!
This really helped me,in getting logcats ..Where first I use to scratch my brains
Such guide will definitely gonna boost up development ! As there would less of noobish post! :victory:
Please,add as much as u can in these guides! :good:
U can still add on ..How to read logcats?
Anyways,I found it really helpful!

Re: [GUIDE] How to install sdk / adb and do a logcat
Fully Reading logcats and undertanding them in detail
. will need a book on java.. I will add some basics symbols and meanings in a log cat ..
Sent from my HTC Explorer A310e using xda premium

Re: [GUIDE] How to install sdk / adb and do a logcat
akshat.shenoy said:
Fully Reading logcats and undertanding them in detail
. will need a book on java.. I will add some basics symbols and meanings in a log cat ..
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
This will be very helpful if u add meaning of those codes

sometimes after doing the instructions given in your tut for linux adb still returns
HTML:
List of devices
???????????
im on linux mint nadia and this did happen to me
so we need to setup device rules..and because we might use another android phone also its wise to add all the rules, so:
Code:
]sudo gedit /etc/udev/rules.d/51-android.rules
and copy and paste this
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
and then make rules executable by:
Code:
sudo chmod a+x /etc/udev/rules.d/*
and akshat we need to make bashrc also executable..

Re: [GUIDE] How to install sdk / adb and do a logcat
I really don't have linux just added what sprintonfire suggested he gave me a shell of what to do so apart from the linux part I have tried and tested everything else. Free for susuggestions and improvements not only on linux but also for the windows part thanks gnexus your a genius ( what my auto correct typed when I tried typing your name)
Cheers
Sent from my HTC Explorer A310e using xda app-developers app

akshat.shenoy said:
I really don't have linux just added what sprintonfire suggested he gave me a shell of what to do so apart from the linux part I have tried and tested everything else. Free for susuggestions and improvements not only on linux but also for the windows part thanks gnexus your a genius ( what my auto correct typed when I tried typing your name)
Cheers
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
i aint that much of a genius...but thanx bro
check ur pm..
didnt put all that here because it would have crowded the thread..!

Edited first post .
Changed entire Linux guide for installing sdk tools.
Added a small bit of info right at the end.

Reading logcats (basic)
http://forum.xda-developers.com/showthread.php?t=1378491
I guess this can be helpfull for noobs like me xD
This one is perfect
http://developer.android.com/tools/debugging/debugging-log.html
Real S**t xD

akshat you havent given a link from where to download sdk package for linux..
for those who just want adb follow these steps before step 1:
go here
and click on sub category "DOWNLOAD FOR OTHER PLATFORMS"
and under "sdk tools only" download the one for linux!
@akshat include this before step 1 of linux guide!

gnexus said:
akshat you havent given a link from where to download sdk package for linux..
for those who just want adb follow these steps before step 1:
go here
and click on sub category "DOWNLOAD FOR OTHER PLATFORMS"
and under "sdk tools only" download the one for linux!
@akshat include this before step 1 of linux guide!
Click to expand...
Click to collapse
They should understand that at least I guess..
still will include thanks..

Repeated update failure AND HOW TO FIX IT OnePlus 8t

I was in the process of rooting when the update was trying to run. Now I keep getting an install failure and can't seem to get any way to fix it.
Where is this update stored so I can delete it or can I get some advice on how to clear it so I can get it to try again?
I can't find the update for download anywhere :/

Not thing about file/cache. Incremental OTA need unroot frist.

Looking for the full installer package file for
11.0.8.12.KB05AA.​

rezapatel said:
Looking for the full installer package file for
11.0.8.12.KB05AA.​
Click to expand...
Click to collapse
Same let me know if you find it lol

OK good news I got myself sorted!
1. What I did was use "Oxygen OS updater" (can be found on playstore) with advanced mode enabled and downloaded the latest OS (11.0.8.11.)
2. Use local upgrade under settings to install 11.0.8.11 and restart. This will remove root but not user data or settings.
3. Check for and install update 11.0.8.12 under settings and it should install fine no issues.
4. Re root using your chosen method.
5. Done!

Interesting. How did you get the boot file for x.12? Isn't that required for rooting..

rezapatel said:
Interesting. How did you get the boot file for x.12? Isn't that required for rooting..
Click to expand...
Click to collapse
Boot modified recovery with ADB function, dump boot_a or boot_b, Magisk patch.

ULTRAJC said:
Boot modified recovery with ADB function, dump boot_a or boot_b, Magisk patch.
Click to expand...
Click to collapse
What they said

ULTRAJC said:
Boot modified recovery with ADB function, dump boot_a or boot_b, Magisk patch.
Click to expand...
Click to collapse
Any guide for this?

DroidFreak32 said:
Since we don't have TWRP yet for our 8T, having ADB enabled on the stock recovery can be really helpful if you are unlocked and rooted.
For example, removing problematic magisk modules.
I tried to install the EdExposed module and ended with a boot loop. To get back I had to flash the stock boot.img again and reconfigure all my modules again.
Having ADB enabled in OOS recovery will let us delete the problematic module at /data/adb/modules without having to delete the working modules.
Credit goes to @s3axel for the Post in Oneplus 8 forums
Quoting the procedure to create the modified recovery.img :
Installation Procedure:
Pre-patched files for the lazy (upto 11.0.4.5):
To find your model and build:
Code:
adb shell getprop ro.product.model
KB2001
adb shell getprop ro.build.version.ota
OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
KB2000 / KB05?? - Chinese Variant
11.0.1.2 Hydrogen_15.H.16_OTA_0160_all_2010150101_4101
STOCK recovery.img
adb patched recovery
KB2001 / KB05DA - Indian Variant
11.0.1.2 - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
STOCK recovery.img
adb patched recovery
11.0.2.3 - OnePlus8TOxygen_15.I.17_OTA_0170_all_2010240047
STOCK recovery.img
adb patched recovery
11.0.3.4 - OnePlus8TOxygen_15.I.18_OTA_0180_all_2011010208
STOCK recovery.img
adb patched recovery
11.0.4.5 - OnePlus8TOxygen_15.I.19_OTA_0190_all_2011101438_3032f.zip
STOCK recovery.img
adb patched recovery
KB2003 / KB05BA - EU Variant
11.0.1.2 - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
STOCK recovery.img
adb patched recovery
11.0.2.3 - OnePlus8TOxygen_15.E.18_OTA_0180_all_2010240038
STOCK recovery.img
adb patched recovery
11.0.3.4 - OnePlus8TOxygen_15.E.19_OTA_0190_all_2011010157
STOCK recovery.img
adb patched recovery
11.0.4.5 - OnePlus8TOxygen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip
STOCK recovery.img
adb patched recovery
KB2005 / KB05AA - International Variant thanks to @card13
https://drive.google.com/drive/folders/1-i4P8sWPfyqwgYvBsKWAAftQW7m66Z70?usp=sharing
KB2007 / KB05CB - T-Mobile Variant
¯\_(ツ)_/¯
Code:
❯ adb devices
List of devices attached
75317573 recovery
❯ adb shell
# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 3648448 40396 3608052 2% /
tmpfs 3837328 1160 3836168 1% /dev
tmpfs 3837328 0 3837328 0% /mnt
tmpfs 3837328 0 3837328 0% /apex
tmpfs 3837328 4 3837324 1% /linkerconfig
tmpfs 3837328 24 3837304 1% /tmp
/dev/block/sda11 491464 140484 350980 29% /mnt/vendor/op2
/dev/block/sda20 11760 164 11596 2% /metadata
/dev/block/dm-3 1516540 1511956 4584 100% /vendor
/dev/block/sda2 27632 10452 17180 38% /mnt/vendor/persist
/dev/block/dm-7 110397292 6627020 103770272 7% /data
Click to expand...
Click to collapse
Mpolo87 said:
CAVEAT
I've only tested this on my device (KB2005 / KB05AA), but it should be universally helpful as it's using your own boot.img so there's no need to find a matching package for your variant and os version.
CREDIT
The steps were buried across a few threads, I'm posting this so it'll be easier for others to find the information. All credit goes to xb360, FullOfHell, and TheUnkn0wn.
INFO​The basic rundown is:
Use the semi-broken TWRP package to give yourself temporary su access through adb.
Extract the boot.img your phone is currently using to your pc.
Reboot to OxygenOS, copy over the boot.img you just extracted and then use Magisk to patch it.
Copy the boot.img back to your pc and use adb to temporarily boot your phone with it, giving you root access until reboot.
Use your temporary root access to allow Magisk to patch your internal as-yet unmodified boot.img to give you permanent root.
There seems to be some confusion in the thread, I'll try to clear up what's happening and why:
The primary issue at hand is that you can't root your device without already having root privileges, for security reasons. Without a custom recovery like TWRP, there are a few more steps than usual (but mostly simple stuff).​
Because we don't flash anything with this guide, it shouldn't cause any permanent bootloops if you use the wrong boot.img, if you get stuck in one just power cycle your phone. ​
Updating with OTAs should be the same process as the other guides here.​
Because of changes in Android, devices that launched with Android 10 and above will not allow you to modify the system partition, even with root. This is not a fault of this rooting method.​
Prerequisites:
ADB and Fastboot installed.​
An unlocked bootloader and USB debugging enabled.​
________________________________________________________
STEPS:​
1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. On your computer open a terminal/cmd prompt. Set the directory (on your pc) you want to work from, I'm using the desktop:
for Windows, type cd C:\Users\Yourname\Desktop​for Mac, type cd desktop or cd /Users/yourname/Desktop​
Spoiler: How to set up adb and fastboot properly
To usb adb and fastboot commands outside of the folder those programs are located in, you'll need to add their location to the PATH list so your terminal can still find them when it's pointing to a different folder. If you want to skip this step, set the directory to the folder that contains adb instead of the desktop.
3. Next, use the terminal to check which A/B partition is active on your phone:
Code:
fastboot getvar all
a. You'll find it on this line: (bootloader) current-slot:a/b​b. For simplicity I'll be referring to boot_a.img throughout the guide, make sure to use boot_b.img if that's the one marked as active on your device. ​​
4. Download the semi-broken TWRP package to your desktop. We'll be using it to extract a copy of your active boot_a.img. It will give you temporary su access via adb, but there won't be a gui. Only boot from it, DO NOT FLASH IT:
Code:
fastboot boot recovery.img
adb shell
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
exit
adb pull /sdcard/boot_a.img boot_a.img
adb reboot
5. Copy the extracted boot_a.img file to a user accessible area of your phone, like your downloads folder.
6. Install the latest Magisk Canary apk on your phone. Open it and:
a. Select the Install option.​b. Use Select and Patch a File on boot_a.img​
7. Copy the patched magisk_patched_a.img file back to your computer. In terminal, type adb reboot bootloader to get back to fastboot mode.
8. Temporarily boot with the patched image that corresponds to the active partition, DO NOT FLASH IT:
Code:
fastboot boot magisk_patched_a.img
Spoiler: Why we're booting and not flashing.
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
9. By booting with the patched image, you now have temporary root access. To make it permanent open Magisk:
a. Select the Install option.​b. Use Direct Install (Recommended) to root your internal boot.img​
10. Reboot and verify it worked.
Click to expand...
Click to collapse

Are you guys aware of the zip file @osm0sis created that lets you add ADB to the stock recovery? You'll need to be rooted to use it.
[TWRP][3.4.0-14][instantnoodle]Unofficial TWRP for OnePlus 8/8 Pro Unified(Stable)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
It works really well - I've used it on 11.0.8.11 and .12

Thank you sir. I took the plunge and have been rewarded. Appreciate it!

shadowtuy said:
OK good news I got myself sorted!
1. What I did was use "Oxygen OS updater" (can be found on playstore) with advanced mode enabled and downloaded the latest OS (11.0.8.11.)
2. Use local upgrade under settings to install 11.0.8.11 and restart. This will remove root but not user data or settings.
3. Check for and install update 11.0.8.12 under settings and it should install fine no issues.
4. Re root using your chosen method.
5. Done!
Click to expand...
Click to collapse
This looks like a great app but it won't work if you need to downgrade. The current release (11.0.8.12.KB05AA) is so bad (look at OnePlus forums) that OnePlus has even taken it down and is no longer available for download. The current one is the previous one (11.0.8.11.KB05AA). Because I have already installed the "12" release, the OxygenOS System Update will not let me downgrade to the "11" release. It gives a "to avoid booting up failure, downgrading is not allowed" message.
Can I sideload/flash this "11" zip file via ADB and accomplish my goal of downgrading? Or could I change the active slot to the inactive one, reboot and get back to "11" that way?

zzjea said:
This looks like a great app but it won't work if you need to downgrade. The current release (11.0.8.12.KB05AA) is so bad (look at OnePlus forums) that OnePlus has even taken it down and is no longer available for download. The current one is the previous one (11.0.8.11.KB05AA). Because I have already installed the "12" release, the OxygenOS System Update will not let me downgrade to the "11" release. It gives a "to avoid booting up failure, downgrading is not allowed" message.
Can I sideload/flash this "11" zip file via ADB and accomplish my goal of downgrading? Or could I change the active slot to the inactive one, reboot and get back to "11" that way?
Click to expand...
Click to collapse
Well I tried switching slots but the inactive slot was corrupted from earlier. So I do not have an "11" in the other slot.

zzjea said:
Well I tried switching slots but the inactive slot was corrupted from earlier. So I do not have an "11" in the other slot.
Click to expand...
Click to collapse
Since OP 8T OxygenOS does not have a recovery, ADB sideload will not work.

Now that 11.0.8.13 is out and I'm on 11.0.8.12 right now, and so far I haven't come across a full zip for 13 yet. Not sure, if this will work .. but I'm thinking, I will uninstall magisk via the app. Restart to ensure, I'm unrooted and then do an OTA to 13. After the OS has been upgraded, follow the steps to root the boot dump file. Anyone tried this method and if would work? The 2 things I'm worried about are - 1) if I uninstall Magisk via the app, does it fully unroot and allows OTA, 2) will the broken twrp shared above work on the latest OOS x.13?
Thanks!

rezapatel said:
Now that 11.0.8.13 is out and I'm on 11.0.8.12 right now, and so far I haven't come across a full zip for 13 yet. Not sure, if this will work .. but I'm thinking, I will uninstall magisk via the app. Restart to ensure, I'm unrooted and then do an OTA to 13. After the OS has been upgraded, follow the steps to root the boot dump file. Anyone tried this method and if would work? The 2 things I'm worried about are - 1) if I uninstall Magisk via the app, does it fully unroot and allows OTA, 2) will the broken twrp shared above work on the latest OOS x.13?
Thanks!
Click to expand...
Click to collapse
For anyone who's interested. This worked!

Hey little bit of an add in! Keep a backup of your non Rooted boot.img!! It is actually easier to flash the non rooted and update just to reroot again.

[GUIDE] How to fix the touchscreen in TWRP (Moto G 5G)

In this guide a describe how you can easily fix the touchscreen issue in TWRP for Moto G 5G.
Before providing the necessary steps, I would like to express my gratitude to the guys here, especially Andrew Hexen for providing the sources and instructions to build the TWRP for this great device.
Building the TWRP from source might result in a recovery without the touchscreen support. To fix that, you can follow these simple steps.
First, we need to extract the touchscreen drivers from the phone. To do this, you need to boot to TWRP. Connect your phone to your PC, open up the terminal and type:
Bash:
# reboot to bootloader
adb reboot bootloader
# boot to recovery
fastboot boot twrp.img
Wait for the phone to boot to recovery. If your phone uses password/PIN or other forms of protection you might have to decrypt the filesystem before proceeding. You can use OTG mouse to do that.
On your PC, in terminal type:
Bash:
adb pull "/vendor/lib/modules/" <path to where you want the modules folder to be pulled>
This will pull from the phone all the necessary drivers, among those are the drivers for the touchscreen. (Probably you could pull just the touchscreen driver, but to be sure I pulled everything.)
On you PC, use Android Kitchen to unpack the recovey image. I usually use the terminal to go to the Android Kitchen folder and I run:
Bash:
./unpacking.sh <path to your twrp.img>
Then go to ramdisk folder that was created by Android Kitchen
Bash:
cd ramdisk
and manually create the following folder:
Bash:
sudo mkdir -p vendor/lib/modules
Then copy the drivers you previously pulled from your phone to this folder:
Bash:
sudo cp <path to modules folder with drivers>/* vendor/lib/modules/
In the ramdisk folder open the init.rc file. We need to open it as su user. You can use:
Bash:
sudo gedit
and then open the file from the editor.
Find the following lines:
Code:
# Load properties, Android 6.0+, vendor init lives here
on load_persist_props_action
load_persist_props
and add a line after load_persist_props so that you get:
Code:
# Load properties, Android 6.0+, vendor init lives here
on load_persist_props_action
load_persist_props
start load_modules # this is the line you must add
Use Android Kitchen to repack the image:
Bash:
cd .. # to move back to the folder where Android Kitchen is
./repacking.sh
You'll get a file called image-new.img. That's your new recovery with a working touchscreen!
I'm sure there's a better way to do this so feedback is welcome.

I tired your method and completed with a newimage file, and flastboot booted off it. Still had touch problems, files attached. Vendor.zip was placed in ramdisk\vendor\lib\modules. Any ideas?
Thankyou
PS (edit): would anything needed to be added to ramdisk/vendor/manifest.xml?

Lostwon said:
I tired your method and completed with a newimage file, and flastboot booted off it. Still had touch problems, files attached. Vendor.zip was placed in ramdisk\vendor\lib\modules. Any ideas?
Thankyou
Click to expand...
Click to collapse
Lostwon said:
I tired your method and completed with a newimage file, and flastboot booted off it. Still had touch problems, files attached. Vendor.zip was placed in ramdisk\vendor\lib\modules. Any ideas?
Thankyou
PS (edit): would anything needed to be added to ramdisk/vendor/manifest.xml?
Click to expand...
Click to collapse
PPS I am trying this on the Moto G stylus xt2043-4. I just noticed thats not the phone you wrote this for, Im going to pull and umpack my stock recovery and compre that to the Twrp3.4 image and see whats missing .

Oneplus 8T Rooted issues with reboot

I'm on 8T latest OOS 11.0.8.13 and rooted with magisk.
Something I've lately noticed is every time I restart it ends up on a long wait on the initial bootloader unlocked disclaimer and ends up in recovery mode. Removing cache generally reboots back into the OS.
This happens on every restart. Pretty irritating.
Are other rooted users facing the same?

CarvedArt said:
Quick and concise how to for obtaining a Stock Boot Image from your Oneplus 8, 8T or 8 Pro device and patching with Magisk to create a fastboot flashable patched boot.img.
DISCLAIMER:
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked, broken or dead devices. This is a high-level
* how to for users with a basic knowledge of ADB and Fastboot. YOU alone are
* choosing to make these modifications, and you are solely responsible for your
* device's fit for use and wellbeing.
*
* Backup your data!
*
*/
PREREQUISITS:
An unpatched Stock Boot.img running on your device
General knowledge and understanding of ADB and Fastboot
Download latest op8, op8p, or op8t Horizon Kernel img from [e.g., op8p_7.img]:
https://dl.akr-developers.com/?dir=oneplus/horizon_kernel/R/images
Download latest Magisk Canary build from Github [e.g., app-debug.apk]:
https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
DEVICE/PC OPERATIONS:
→ ADB
Enumerate devices
Code:
adb devices
Boot into Fastboot
Code:
reboot bootloader
→ FASTBOOT
Enumerate devices
Code:
fastboot devices
Determine the current slot (A/B), whichever slot you're on should be the "good" img
Code:
fastboot getvar current-slot
Boot with the custom kernel downloaded from Horizon to use root [NOTE: Include the full path of the img if not in the same directory]
e.g., fastboot boot "C:\Users\User\Downloads\op8p_R7.img"​
Code:
fastboot boot xxxxxxx.img
→ ADB
Copy the boot.img from each slot to the root of the device
Code:
adb shell
su
dd if=/dev/block/sde11 of=/sdcard/boot_a.img
dd if=/dev/block/sde35 of=/sdcard/boot_b.img
→ Android Device [NOTE: Some Android 11 devices experience patching issues on the Beta Channel like bootloop] [NOTE: Some users experience issues on Canary like no SIM detected; if so switch to Beta]
Install Magisk app-debug.apk (Canary)
Go to Settings → Update Channel → Canary
Go to Home → Install → Install → Select and Patch A File
Navigate to internal storage and select the stock boot.img [choose the img from whichever slot you're on]
When it’s done patching copy the file, named magisk_patched.img, from the root → Downloads of your device to PC
→ ADB
Code:
reboot bootloader
→ FASTBOOT
Test to ensure it boots before flashing; if not you'll need to patch the other img
Code:
fastboot boot magisk_patched.img
→ Android Device
If the device boots and you have root in the Magisk Manager app, reboot the device into Fastboot then flash the active slot [NOTE: Both slots do not need to be flashed; just the current active slot]
→ FASTBOOT
Flash the patched image file [NOTE: Include the full path of the img if not in the same directory]
e.g., fastboot flash boot_b "C:\Users\User\Downloads\magisk_patched.img"
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
- OR -​
Code:
fastboot flash boot_a magisk_patched.img
fastboot reboot
- OR -​
Code:
fastboot flash boot_b magisk_patched.img
fastboot reboot
ADDITIONAL RESOURSES:
→ FASTBOOT
If you need to set the other slot to be the active slot use:
Code:
fastboot --set-active=a
- OR -​
Code:
fastboot --set-active=b
→ ADB
ADB Magisk Bootloop Fix
Code:
adb shell
magisk --remove-modules
→ OTA Help
Magisk stock boot.img missing fix [NOTE: Android 11 onwards, the /sbin folder might not exist, so Magisk will randomly create a folder under /dev and use it as the base folder]
Rename to: stock_boot_0.img
Compress with gzip = stock_boot_0.img.gz
Copy stock_boot_0.img.gz file to the root of: /data
Edit the config file: /dev/xxxxxxx/.magisk/config → Change SHA1= to 0
Magisk Manager → Uninstall Magisk → Restore Images
→ ADB
Determine the random folder name generated by Magisk on Android 11+
Code:
ls -laR /dev | grep '.magisk/rootdir'
→ ADB
Determine the Boot Image partition location [NOTE: Will list all partitions; look for boot_a and boot_b]
Code:
ls /dev/block/bootdevice/by-name/ -all
Click to expand...
Click to collapse
Root with this method probably because of something wrong with the installation or smth.

Kenora_I said:
Root with this method probably because of something wrong with the installation or smth.
Click to expand...
Click to collapse
Rooted using the same guide.. Use the same after each upgrade (full package).

huh, have you updated the kernel and stuff. There are newer releases.
Might be your problem

Kenora_I said:
huh, have you updated the kernel and stuff. There are newer releases.
Might be your problem
Click to expand...
Click to collapse
Adaway and Ktweaks apps, but both execute after boot.
Systemlesshosts (to run Adaway) and Oneplus phone dialer modules on Magisk.
Checked, no newer version for any mentioned.

Use full update.zip update again, see if it can be fix

ULTRAJC said:
Use full update.zip update again, see if it can be fix
Click to expand...
Click to collapse
Will try.