Just after a bit of advice of possible. Firstly I am fairly new to the a/b slot part of flashing and haven't really managed to fully get my head around installing a backup from twrp or going back to stock rom from a custom ROM. Each time I have tried I have usually end up with an encrypted device in twrp (jumbled letters). Please could somebody explain or point me in the direction of a thread explaining how (I have looked but haven't really found anything). I know that flashing a custom you wipe days and not system as we used to do. Is reverting to stock the same process?
Related
I've been doing research on this for a while, and I decided to sign up and ask about this question. Majority of the topics here dealing with bricking either have solved it because of access to fastboot, or some users have given up and either retired their devices or sent them in to ASUS.
Long story short, I installed Clockwork Recovery Mod and Cyanogen mod with no issues. After a couple of weeks, I decided I wanted to go back to stock. I did some research and found a topic which said I needed TWRP in order to flash back the stock ROM. I installed TWRP, but some things seemed to have gone awry with that install and I no longer have access to the fastboot menu and the tablet keeps booting straight into recovery.
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2). So far, I think I can get it back on track if I could somehow install a new recovery, or start my device from scratch somehow.
Also whenever I transfer to device memory, if I reboot the tablet, everything gets erased and the log is littered with errors about not being able to find and mount /data. From what I've read, it should be solved with a simple format of the file system. However, all of my attempts to use the recovery's built in wiping/formatting tools have ended with no success. If I put in a microSD, that gets wiped as well so in order to load a ROM, I have to push it using adb.
I thought I had fully bricked it, but it seems that since it's accessible through adb, it's still somewhat fixable. I know about backing up everything with nvflash, now, I guess I just didn't do enough research before getting into this. Any ideas, feedback, is appreciated, so far I'm learning a lot about android devices from this experience.
lino4 said:
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2).
Click to expand...
Click to collapse
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
_that said:
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
Yeah I found that thread not too long ago, I pushed the bootloader and was able to load the stock rom and get everything going.
Hi everyone. I'm new to XDA, so I'd like to take the time in advance to tell all of you developers and contributors how much I appreciate what you do. XDA has some of the brightest minds in the world. The information contained here has already saved me (and my Nexus 7) quite a few times.
With that said, I'd like to know more about the ins and outs of flashing ROMs (and kernels) and how to do it properly without losing everything (music, pics, etc). Also, how flash updates to ROMs: do I need to wipe and reload everything with each update, and and can I flash the LATEST update or do I have to go back and flash each and every update in order of their release? If anyone could direct me to the proper thread(s) I'd greatly appreciate it. There's so much info here that its easy to get lost. I truly appreciate any help and/or direction.
phys_of_ex said:
Hi everyone. I'm new to XDA, so I'd like to take the time in advance to tell all of you developers and contributors how much I appreciate what you do. XDA has some of the brightest minds in the world. The information contained here has already saved me (and my Nexus 7) quite a few times.
With that said, I'd like to know more about the ins and outs of flashing ROMs (and kernels) and how to do it properly without losing everything (music, pics, etc). Also, how flash updates to ROMs: do I need to wipe and reload everything with each update, and and can I flash the LATEST update or do I have to go back and flash each and every update in order of their release? If anyone could direct me to the proper thread(s) I'd greatly appreciate it. There's so much info here that its easy to get lost. I truly appreciate any help and/or direction.
Click to expand...
Click to collapse
Hi, I'm glad you're happy with XDA.
I'm not a developer but I can tell you about flashing ROMs.
When flashing the latest version of a ROM/kernel you don't have to flash all previous versions
When flashing a new ROM (E.g CyanogenMod) over your stock/current ROM (That isn't CM) you must perform a data wipe/factory reset and wipe the cache. To save data use Titanium backup to backup all your apps, copy all files available to PC and make a Nandroid backup incase the flash fails.
When flashing an update (E.g Cyanogen M6 over M5) most of the time you don't have to backup all apps etc but most people do incase something goes wrong (which it can), however when flashing a nightly/experimental over a M-build you must wipe data and cache.
When flashing a kernel the same rule applies as flashing a new ROM (Backup, Wipe, Restart)
Hope I could help and good luck exploring ROMs and Kernels
For the last year or so, I was using this rom, and I loved it, but I was curious to try the new KitKat version so I tried updating, and kept getting getting a recursive error when trying to flash the d2lte(supposedly all the S3 roms are unified now?) KitKat version. So after doing this, after /system was cleared, but I couldn't flash back to the backup I had made before hand because I was getting an md5 mismatch.
In response, I used Odin to flash Root66. Phone works, but its seriously lacking in terms of bells and whistles of a custom ROM. It says its rooted, but a lot of root apps would fail the permission test. No prompt was given. I used towelroot and started getting root access, but I still can't update CWM or Superuser binaries. Trying to flash any other ROM leads me to an infinite boot screen, forcing me to flash Root66 again.
I tried this as well, but it seemed to yield the same results.
So, I really would like get off Root66, but I'm at a loss as to how. Anyone have any ideas? I'm sure the answer is staring me in the face in one of those threads I linked, but I'd really appreciate it if someone could (at least try to) point me in the right direction. Apologizing in advance if this question has been asked before.
Thanks.
Hi all,
After unsuccessfully asking for support in the LG G3 forums, I'm going to try it here. Please point me out to another thread, if this is the wrong place to ask those questions.
First of all: I am new to flashing etc, so I'd rather not just try anything without being certain about it. Also, my phone is currently running fine, so rather play safe for now...
LG G3, D855, Dirty Unicorns Rom v10.3, TWRP 3.0.2.0 installed, Viper4Android, nothing else (no different kernel or something)
Issue: I cannot perform any wipe in TWRP, as it "fails to mount \data, \cache, \system". Interestingly, flashify thinks I am on "stock recovery", even after booting into recovery and restarting the device. It also refers to old backups as stock. Only the backup of the 2.7.xx TWRP is labeled as such.
I have done some fair share of googling. Most similar threads I have found were left unanswered. On some other devices, the problem could be solved by installing another recovery. But I did not find a CMW for the LG G3, so this won't work. I thought about just installing TWRP again (via flashify, or maybe install some older version/restore a backup), but I'm not sure whether this could do further harm, with the current state in mind? Other possibility could be reverting back to stock, but that would be a rather tedious approach.
Glad for any help/hint/pointing out to better threads/whatever!!
Thanks a lot!
Patrick
OP re-posted...
http://forum.xda-developers.com/lg-g3/help/twrp-failed-to-mount-data-cache-t3421087
Thread closed.
I know we don't have a complete implementation of recoveries, like twrp/of (I know it's basically the same), yet. But now that we have the kernel source, what is still missing (vendor?)?
Also and kinda of a similar question, what is still missing regarding a "normal" flashing process? Like wipe system, data, dalvik/art, cache, flash rom and not having to have a base stock firmware and needing to format data.
To be honest, I'm a bit confused with this phone. My other phones (admittedly last one's didn't get past Android 9), were so different in that regard.
So I'd really appreciate if someone could take the time to shed some light on this.
Maybe we'll see a stable version of twrp for surya but support for dynamic partitions will not be available soon.
Having to format data everytime you flash a new rom may be solved having the kernel source. I think it has to do with encryption keys. Even if you don't have any password set in the OS, miui still generates keys to encrypt the data and when you wipe only, they get deleted hence, data on the internal nemeory remains encrypted. That's what I think.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Ok, to be honest and judging by the fact that the announcement by Dees_Troy was over a year ago, things look pretty difficult to say the least.
I had my last phone (axon7) for so long that all the new implementations, like dynamic linking and super partition, weren't really on my radar.
Guess I was a little naive in thinking that the kernel source would be of any help in that regard.
This lack of stable time-tested solutions worries me, too.
That's the main reason why I'm still on stock ROM on the Poco and the Axon 7 is still my daily driver.
.
pnin said:
This lack of stable time-tested solutions worries me, too.
That's the main reason why I'm still on stock ROM on the Poco and the Axon 7 is still my daily driver.
.
Click to expand...
Click to collapse
How about EU ROM ?
Thanks for your thread.
I'm asking too.
I went from an old device too (redmi note 4 mido), and i'm a bit lost on flashing process.
Is it possible to :
Install orangefox via fastboot.
Wipe all & format data.
Flash recommend firmware for rom.
Flash custom rom.
Flash gapps.
And boot ?
Any problem with that ? What i'm missing ?
Don't have phone now, I'm waiting for shipping, and will wait for unlock bootloader access. I hope it will more clear and simple when I will discover poco x3.
You can do all those things. What you can't do for example is make a backup and restore your current custom rom.
Oh ok.
Sorry, miss understood your op post.
I was confused because on some custom roms thread, I find strange install instructions, like : dont wipe anything, format data AFTER flash custom roms...
Somes roms requires frimware 12.0.3. What about if phone have a more recent ? Can I downgrade just by flash fw+vendor on recovery before flash rom ?
And some people said they have bricked there devices.
Just to be sure to don't make stupid error on fresh new device, that I can't solve with miflash and fastboot.
Thank you for your reply.
I only clean flash roms, never backup, don't have a lot of apps, and majority have import/export options in-app.
But I hope for you it will be fixed soon.
atifnr said:
How about EU ROM ?
Click to expand...
Click to collapse
As @[armitage] pointed, it doesn't enable nandroid backups that I know of.
.