Database Info

[Q] 2.3.4 update failure leads to whole crash..

Ok, so Was using my nexus s today and I kept getting the notification to perform a system update to the newest version of gingerbread (2.3.4). Prior to pressing update my phone was at 2.3.1 default with 2.5.### ClockworkRecovery and it was rooted. Everything worked on it perfect. So I proceeded to download and install the update, and CWR fails to install the update and I would have to take out the battery to restart the phone. I had been doing this multiple times and I wanted to get it updated. So I go into CWR and try installing it manually:
I look around and try to find the file and I couldn't, I reset user data to see if it would fix it and it didn't, then I go back and start formatting the following folders, /system, /cache, /data and one other but I did not format /boot, so Then (noob me) I restart to phone and of course the rom is gone. I get back to recovery and try to restore from update.zip but the console said the file could not be found, I look up my model and look for a full verison rom and the mount my usb storage and place the rom .zip on the storage and try to install from .zip on sd but it did not work so I end up grabbing this and installing it and now I'm stuck, when I do adb shell it doesn't pick up the phone any more, it can fast boot on the phone but it can't go into recovery and I have no idea what I should do to try to fix this problem.
NOTE: before I ened up installing and replacing the recovery, my /system folder would not mount due to "invalid arguments"
Model is i9020T
I don't have firmware version access
and if there is any other information I can provide please let me know
Update:
I got the device to be recognized by fastboot but not by "adb shell", when I type adb shell no device is found, so I guess my question now is do I need to just flash a new recovery and then try to flash a new rom?
Solution:
1. fastboot your phone, (volume up+lock/power button)
2. place the recovery image you want to install in the "Android SDK"/tools/ folder
3. in your cmd/terminal, while in "Android SDK"/tools/ execute:
Code:
fastboot flash recovery "NAME-OF-RECOVERY.img"
4. once that is installed and it should work, then restart your recovery mode
5.clear all your data/factory reset, including davlik cache
6.mount your sd to your computer so you can place the Rom you want on your phone's sd
7. In recovery choose zip from sdcard to install.
8. It should install, if it gives you problems try another rom, I had problems with rAv 1.2.2, keep restarting every minute. I used "NS-2.3.4-GRJ22-Stock-Deodexed-signed.zip" and it worked.
9. Restart the phone and be patient the phone will start up and you should be set.
Hope this helps someone!

Asus Padfone 2 - softbrick after SKU change + Fix

Hi Guys,
Just thought I'd provide a warning and a fix to a half day ordeal recovering from a soft-brick after wanting to make the switch from TW to WWE.
What made this all go wrong?
I have a Padfone 2 which had the latest TW_A68-10.4.17.15
I have a accidentally turned off adb USB debugging mode
The process:
I unlocked my bootloader using the ASUS official unlocker.
I had then install 2.7.0.1 twrp which didn’t work
Install 2.5.0.0 twrp which did.
Forgot to do a backup which I usually did, but guess I thought that I have done this so many times, nothing would go wrong.
DON’T GET COCKY BACKUP FIRST.
Opted for the easy way out and write to system VIA twrp using zip, which was reported to work.
This installed and didn’t report any error.
After reboot, app.phone and another OS programs crashed constantly and rebooted.
I removed my sim and this stopped the crashed apps, but not the reboots.
I realised I was in a whole world of trouble and it was only at this moment did I realise that I didn’t have USB Debugging turned on. Frantically tried to enable it in between reboots, but failed and was now presented with only a ASUS spinning circle of death, or even better later, only the which ASUS logo before it reached it.
All I had available was fastboot and twrp.
You’d think this was an easy fix, but I didn’t have a usable/original rom on the /data/media a.k.a /sdcard partition.
Note: have a handful of roms including your original rom saved on the phone before trying anything, as this phone has no access to external storage when all goes pear shaped.
I wiped caches, didn’t work.
I then wiped data, which then deleted the only rom I had access to. So I couldn’t even now retry installing from zip.
ADB didn’t work from any recovery including CWM 6.0.4.4
I was at a loss and didn’t know what to do.
The recovery:
Installed twrp 2.6.3.0 was persistent with ADB sideload, even though I didn’t have USB Debugging enabled.
Note: ADB sideload will still work even if you don’t have USB Debugging enabled. It’ll either take a min or two to register on your computer, but if not reboot and reboot again to get it to register.
Sideloaded the wrong firmware file again.
Note: If you are trying to sideload the original firmware, extract the zip “TW_PadFone2_user_10_4_17_15_UpdateLauncher.zip” and sideload the zip hiding within “ASUS” -> “Update” -> “TW_A68-10.4.17.15-0-ota-user.zip”
After another long time trying to get the ADB device to register, finally got a second chance and got back to the original firmware.
Did this deter me from the switch from TW to WWE. HELL NO!!
Enable ADB USB Debugging
Make sure you push the rom WWE to your /sdcard partition
How to do it right.
Load the original recovery attached recovery.stock.img
Reboot into recovery and select "apply update from external storage" and choose the zip file to flash.
This will fail! It's what it's meant to do
At this point the recovery changes the partition table and then restarts.
On reboot we will have a nice "Installation aborted", this because, being changed the partition table, the recovery can not find the file to flash as it the partition containing the data has been reformed losing its contents. So you will need to copy the file again via adb.
Select "wipe data / factory reset"
You need to do a wipe, because it formats the partition where we will send the file. Having just changed, the partition has not a file system and so it must be formatted to save something on it.
Upon rebooting to ADB stopped working under the stock recovery. It registered with my computer but the command to repush the WWE rom to /data/media kept failing.
Rebooted into fastboot and install twrp 2.6.3.0. At this stage as I knew that the partition table had been updated, I sideloaded the WWE rom, which works more reliably when it's originally enabled
Did a Wiped cache for safe measure
Reboot and welcome to another 2GBs of space and WWE firmware.
NOTE: Always flash the inner zip “TW_A68-10.4.17.15-0-ota-user.zip” not the outer zip “TW_PadFone2_user_10_4_17_15_UpdateLauncher.zip”

freak4916 said:
Load the original recovery attached recovery.stock.img
Click to expand...
Click to collapse
Where can I find this?

Stuck on... bootloop after rooting.

I rooted my device about an hour ago with the instructions from https://forum.xda-developers.com/20...o-root-moto-g-2015-android-t3320113?nocache=1.
(I have a Moto G Osprey, not Merlin).
The problem is, after flashing SuperSU 2.63 according to the instructions and wiping the Dalvik cache and cache, I'm stuck on the slowly spinning 'Hand stitched by Peter Crawley screen that you see just before the phone opens up. I think it's not a boot loop because it isn't starting everything from the beginning again and again (I've dealt with boot loops before *shivers*). Is it just rebuilding the cache, or do I have a bigger problem?
I have tried:
1/ Rewiping the Dalvik/Cache
2/ Rewiping the Dalvik/Cache and the Data.
Oh, and btw, I have a pre-SuperSU backup, but I'm not planning to use it if I can avoid it.
Any help from kind strangers would be appreciated.
(Help from unkind ones will be too)

Check if it's installing in systemless mode, also you can try magisk root

mercuryprobe said:
I rooted my device about an hour ago with the instructions from https://forum.xda-developers.com/20...o-root-moto-g-2015-android-t3320113?nocache=1.
(I have a Moto G Osprey, not Merlin).
The problem is, after flashing SuperSU 2.63 according to the instructions and wiping the Dalvik cache and cache, I'm stuck on the slowly spinning 'Hand stitched by Peter Crawley screen that you see just before the phone opens up. I think it's not a boot loop because it isn't starting everything from the beginning again and again (I've dealt with boot loops before *shivers*). Is it just rebuilding the cache, or do I have a bigger problem?
I have tried:
1/ Rewiping the Dalvik/Cache
2/ Rewiping the Dalvik/Cache and the Data.
Oh, and btw, I have a pre-SuperSU backup, but I'm not planning to use it if I can avoid it.
Any help from kind strangers would be appreciated.
(Help from unkind ones will be too)
Click to expand...
Click to collapse
the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
:good:

karankatson said:
the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
:good:
Click to expand...
Click to collapse
Thanks, man. I'd have tried it but in the end I just gave up and restored my backup, and subsequently wiped the caches again and rebooted.
And it worked! Guess the moral is to, as you said, keep a backup.
(P.S.- My subsequent SuperSU installation attempt seemed to work after that. Weird, but hey, I'm not complaining).

Magisk root > bootloop > Stock ROM > success

I have almost finished setting up new Redmi 6.
After rooting, getting TWRP on the phone I have reinstated all apps trough TitaniumBackup. I have reinstated too many apps from TB and at some point I have removed 1 or 2 apps too many that I thought are only from TB...
Inside TB I went into system apps and deleted apps wit: Backup copy [APK + backup]. Before I realised that apps with backup were actually original Xiaomi appswas too late, I had few warnings later and phone rebooted but couldn't boot into system.
This way I got rid of:
com.android.providers.telephony
com.android.phone
I could recreate what I have removed going into old phone and seeing which apps are backed up from system...
Can you help me to get apps back trough TWRP or FASTBOOT?
USB debugging was still on last time
My SD card is formatted as part of internal storage
TWRP File Manager can browse ROOT folder
It is newest ROM for Redmi6, [V10.3.6.0.OCGMIXM_], can someone provide copy of APKs please?
When in TWRP I mount system only, and try to [wipe dalvik] I get messages:
Failed to wipe dalvik
Updating partition details...
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
...done
Unable to mount storage
I almost will not loose any data, but:
if I can I'd like to move missing apps back to /app/data/ OR /system/app/ ? to recover system so it starts
if need be I will flash Xiaomi ROM and start from scratch but will loose many h of hard work on de-bloating etc [I hope that flashing original ROM will be easy since TWRP is working fine]
During TWRP - ADB sideload:
HTML:
adb install com.android.phone.apk
error: device '(null)' not found
- waiting for device -
What can I do???
-------------------------------------------------------------------------------------
Turns out I had to flash original stock
Xiaomi guide is terrible and out of date, so:
there are prerequisites required, like ADB, drivers, that is well explained on Xiaomi site, then...
download original stock for fastboot >>> unpack folder XXX sitting inside 2 archives [it's not zip] >>> download/install and run XiaoMiFlash.exe >>> SELECT button - navigate to unpacked folder XXX >>> attach mobile >>> refresh = device will appear on list >>> FLASH
Read official xiaomi instructions on flashing original ROM just in case something will get updated
Why not any other way?
In TWRP it asked me for a password at the start
I couldn't get /system/ or /data/ mounted, wiped or formatted.
I have seen folks giving advice on how to do it, but often it didn't make sense or it didn't work.
I would be risking bricking new device by other methods & I had no more than 3 pictures to loose on flashing ROM and hours spent on doing up.
Interesting is, there really wasn't even one working advice on how to mount i.e. /system in TWRP when password is missing in booted operating system [like my case, I couldn't find any info on that, all at some point were going to advice to do something that required mounted /system or /data]
But then I just finished whole process of flashing stock ROM; I have set [1. simple password] then [PIN], went to TWRP, tried to use OS password/PIN and it didn't work, it didn't remove encryption .
----------------------------------------------------------------------------------------------------------------------------------------------
Found a solution on how to root the phone after all above.
After another Original stock ROM 10.3.6.0.OCGMIXM flash with XiaoMiFlash.exe, phone will automatically restart and start OS
But... I didn't let it to boot
Once it restarted I have pressed Vol- [button down] and waited for fastboot to load [no need to hold power button]
Installed TWRP 3.0.0.0
Restarted
Hold Vol+ [button up]
TWRP loads
CANCEL if asks for password
----------------------
INSTALL boot.img [when you flash stock ROM it is inside folder, just copy it across]
in MOUNT tick /vendor & /system
use back button to exit MOUNT
INSTALL Magisk 19.3.zip
clean dalvik cache and swipe
I have once again restarted to RECOVERY/TWRP
------------------------
When OS booted I couldn't run/start Magisk APK/aplication. Screen blinked and that's all. Root not working.
download Magisk Manager [7.3.4 in my case] from web & install
I could start application this time & it asked me to install something extra - I have chosen to install it right away
Magisk reboots phone
Now phone was finally rooted
---------------------
I used external USB attached to phone with files so I didn't need to copy files to phone.
This is much more convenient as after restarting to TWRP first time there is nothing on the phone and you would have to sideload.
---------------------------
Below is LibreOffice doc with ADB commands to uninstall bloatware. In the column next to uninstalling commands, are commands to instal same app back [I do not know will this always work since I tried only on few] [some missing - you can create it yourself]
Potentially further down the list there are more necessary apps. Uninstalling them did not cause problems in my set up, but sometimes they might be needed for less important stuff...
https://www.dropbox.com/s/xpfeh4wx1nv5dlf/Bloatware removal + SD as internal.ods?dl=0

Boot Animation Change Issue - Pixel 4a

Hello everyone.
So I've been having some trouble changing my boot animation in my Pixel 4a running Android 12. I have tried every method I possibly can, and nothing seems to work. My device is rooted, and the bootloader unlocked. I have all necessary drivers updated, debugging enabled, etc etc.
I have tried:
Boot Animation apps - Just give error messages
Rebooting the bootloader into recovery to flash the .zip - This option isn't available in my boot recovery
5-6 different file manager apps - all of them won't let me either delete the original bootanimation.zip file or copy/paste the new one I have ready to go
Using a windows based root file manager - same as above
Is htis an Android 12 issue? Since it was released relatively recently I just need to wait for an updated method?
Any help would be appreciated. Thanks.

DKM-Eby said:
Hello everyone.
So I've been having some trouble changing my boot animation in my Pixel 4a running Android 12. I have tried every method I possibly can, and nothing seems to work. My device is rooted, and the bootloader unlocked. I have all necessary drivers updated, debugging enabled, etc etc.
I have tried:
Boot Animation apps - Just give error messages
Rebooting the bootloader into recovery to flash the .zip - This option isn't available in my boot recovery
5-6 different file manager apps - all of them won't let me either delete the original bootanimation.zip file or copy/paste the new one I have ready to go
Using a windows based root file manager - same as above
Is htis an Android 12 issue? Since it was released relatively recently I just need to wait for an updated method?
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Have you also enabled r/w permissions for the system partition?

Droidriven said:
Have you also enabled r/w permissions for the system partition?
Click to expand...
Click to collapse
Every time I try with my root file manager it says "error changing permissions." I'll add a screenshot of what they currently are.
The error on the bottom is after I added the check mark in the Owner row, under the S column. The other ones were already set.

DKM-Eby said:
Every time I try with my root file manager it says "error changing permissions." I'll add a screenshot of what they currently are.
The error on the bottom is after I added the check mark in the Owner row, under the S column. The other ones were already set.
Click to expand...
Click to collapse
Put a check in the box beside "recursive" in the upper part, and tap "apply" then, in the lower part, check the box beside "recursive" then tap "apply".

Droidriven said:
Put a check in the box beside "recursive" in the upper part, and tap "apply" then, in the lower part, check the box beside "recursive" then tap "apply".
Click to expand...
Click to collapse
Still gives error while trying to apply.

DKM-Eby said:
Still gives error while trying to apply.
Click to expand...
Click to collapse
Boot to recovery and choose the option to "wipe cache partition", if you have custom recovery, wipe the cache partition and the dalvik cache partition(DO NOT factory reset). After wiping cache(s), reboot the device and then see if that helps.
Any time you make a change of any kind to the system partition, rebooting to recovery and then wiping the cache partition(s) and then rebooting is usually required in order for the changes to take effect.

Droidriven said:
Boot to recovery and choose the option to "wipe cache partition", if you have custom recovery, wipe the cache partition and the dalvik cache partition(DO NOT factory reset). After wiping cache(s), reboot the device and then see if that helps.
Any time you make a change of any kind to the system partition, rebooting to recovery and then wiping the cache partition(s) and then rebooting is usually required in order for the changes to take effect.
Click to expand...
Click to collapse
There are no options in my recovery mode to wipe the cache for anything. The only thing available in recovery was to factory reset.
I also noticed something in Magisk - I installed the boot animation changer module, and when running it, it says it does not support my sunfish kernel. So I'm wondering if my Pixel 4a is just completely unable to perform this action?

DKM-Eby said:
There are no options in my recovery mode to wipe the cache for anything. The only thing available in recovery was to factory reset.
I also noticed something in Magisk - I installed the boot animation changer module, and when running it, it says it does not support my sunfish kernel. So I'm wondering if my Pixel 4a is just completely unable to perform this action?
Click to expand...
Click to collapse
You don't have a stock recovery if you don't see the option to wipe cache partition. Can you post a screenshot of what your recovery looks like.
If Magisk says it doesn't support your kernel, you need to see if there is a custom kernel available for Pixel 4a that it does support.