Help!
I'm trying out a series of ROMs and now am faced with a puzzle. After wiping CM13 (system and all), I'm trying to flash an @amaces AOSP Marshmallow build, but TWRP is giving me grief saying it can't flash an older OS over a newer one.
It says the previous CM13 OS was dated 2017 (I don't think so....) while the one I am trying to flash is dated 2016 (yes, the @amaces ROM was posted in 2016).
So...I thought I had truly wiped the system. How can it know anything about a "previous" ROM?
Edit: Ugh. So I think this is because the CM12 and CM13 ROMs changed the partition table? Or they changed something and I need to get back to stock. Unfortunately my stock backup is gone (8gb). I've looked at all the various restores and they rely on files that no longer exist or are behind so many layers of pop-ups and -unders that it doesn't seem safe to wait and hope the download will eventually start. Succulent has a series of flashable zips to "restore" a tablet to stock, but if there has been a partition change, will his zips fix that?! I have the nooktablet_1_4_3_update.zip, but have no idea if that is even useful. It certainly can't be flashed with CWM or TWRP.
Edit-Edit: OK, I learned something(s). Apparently the issue was the version of TWRP I was using. I tried an older version and I was able to flash one of @amaces ROMs, but I also did manage to take the tablet back to stock using nooktablet_1_4_3_update.zip. It turns out that you can't flash that successfully with TWRP--at least not the versions I had. But I did have CWM 6.0.5.1 from succulent as altboot on my SD card. That was able to flash the zip and restore to stock. Good to know since everything else is gone. And, yes this time I also made a CWM stock backup and put it somewhere safe
Related
Some months ago I was flashing nightly and non stable zip. If you loose AOSP keyboard, Ok. At some point, after IOKP 4.3.1. flash, not beanstalk or even hellkat which I could not install, ALL ROM FAILED, all gapps idem.I only had a backup of IOKP and it isntall. TWRP 2.6.4.0 .img flashed by Odin 1.85 saved me once.
This time I felt unstability over several processes and only gave one order, reboot recovery. It all blaked, samsung in an out
Tried .tar of phielz touch, CMW. TWRP above refered showed itself but whem I thought the backup was over, it seems the OS was missing...
Now after flashing The new version of TWRP for t0lte I got nothing.
I know nothing of programming, code or whatsoever.
If somebody could give some suggestions that can help...:crying:
Hi there, i'm writing this in hopes of someone reading it who give me some pointers.
i was running for the last years on CM 10.2.1 but i thought it was time for an update. update to CM 11.2 worked but my installed apps were making some weird troubles so i decided to do a factory reset and there my trouble started.
i flashed to boot.img in fastboot, cleared cache with fastboot cmd
format \system, \data, \cache and of course dalvik
flashed rom CM 11.2 (from official cyanogenmod site) via recovery sideload
rebooted and as my thread title says was stuck on CM boot sequence
i tried different CM roms, but always the same result. system wont end the bootup.
i even suspected a problem with CMW v6.0.4.8 and flashed TWRP from the CM 12.1 thread here in the forum.
so in short i can flash boot.img, recovery, different roms but in the end can't get it to work.
i would really appreciate some hints what i could do differently or maybe were i go wrong.
if you need more info i'm happy to supply them to you.
Thanks in advance.
solved by installing a TWRP backup and boot.img what i found on a german android site.
i was also able after that to install CM 12.1 unofficial and its running now. but i'm totally stumped what caused this weird problem to begin with. doesn't really matter now, i'm relieved it worked in the end.
Hello there I have a couple questions regarding to the red honor boot logo and also on how to update from a stock rom with TWRP and root ( also a couple of system modifications ) to the new B331 update.
So heres the rundown, when I first got my honor 5x I did not spend too much time on the stock rom I went ahead and rooted my phone and installed TWRP then made a backup of my stock rom (B151) no modifications other than SuperSU being installed. After that I went ahead and installed CM13 nightlies and updated mostly everyday up until the build July-18-16. I had adoptable storage enabled with my 32GB SD card and I totally forgot to disable the adoptable option before I reverted to my stock backup so when I went onto TWRP and tried to restore my backup I always got an error where it said something along the lines " error; could not find system" but instead of it backing out it continued to restore and bricked my phone. I had a somewhat clever idea to flash any build of CM13 I had on my computer and guess what it booted then I disabled the adoptable storage and booted back onto TWRP restored my backup and everything was fine until it booted and I noticed the honor boot logo had a red "h". I found that weird since I have restored my backup previously and that never happened. Anyone knows what it could mean and how to fix it?
My second question is how should I go about updating to B331? Should I download the stock recovery B151 ( since that is what shipped with my phone and is what my backup is) then revert to my near stock backup, flash stock recovery and unroot then update through cslA's B331 instructions? Or should I somehow fix the red honor boot logo then go ahead with what I stated above or is this all done differently? I am not a newbie at these kind of things I just moved onto more important things in life and simply want to update my phone. My needs for flashing new roms daily are over and I just simply like huawei's UI as it just "works" for me. Thanks to anyone who responds anything is appreciated as I can't seem to get my old skills working again. Haha:laugh:
Fibgerprint aint working right? U cant go back to stock with just a normal twrp backup. Install an update.app through dload for your region and then apply the twrp backup.. Make sure you are on B151 Recovery!
Demian3112 said:
Fibgerprint aint working right? U cant go back to stock with just a normal twrp backup. Install an update.app through dload for your region and then apply the twrp backup.. Make sure you are on B151 Recovery!
Click to expand...
Click to collapse
No, my fingerprint is working... I just wanted to go back to stock ROM with root and that's what I got just now I have a red honor bootlogo. Now I want to update to marshmallow but I have a fear that even if I follow the steps onto reverting to stock I may brick it because of the red bootlogo.
So what you are saying is I should download my B151 recovery and firmware to revert to stock then update and from there I should root and install TWRP?
Hello i wanted to Flash Lineage Os on my s2 but ran into some problems. I came from omnirom with twrp 2.7.1.0 installed.
So the flash process hung itself up i tried again and it didnt work.
Well i suppose the bootloader is unlocked cause i flashed omnirom right.
Since i already deleted omnirom i cant check now with the dialpad.
So I thought about updating twrp but since its not after 2.8.4 i cant flash .img files.
I would prefer to flash it without heimdall cause i have only strangely configured computers available.
So I tried to flash twrp 3.0. 4 or something like this which I found as a zip file the installation runs just fine says it was successful but after rebooting to recovery it is 2.7 again.
I dont necessarily want to update twrp if i can flash lineage but i guess i have to?
Are there any recommendations for a lost soul.
All the best
Sorry for the false place for this maybe someone can move it to the right spaxe thx
Swarion said:
Hello i wanted to Flash Lineage Os on my s2 but ran into some problems. I came from omnirom with twrp 2.7.1.0 installed.
So the flash process hung itself up i tried again and it didnt work.
Well i suppose the bootloader is unlocked cause i flashed omnirom right.
Since i already deleted omnirom i cant check now with the dialpad.
So I thought about updating twrp but since its not after 2.8.4 i cant flash .img files.
I would prefer to flash it without heimdall cause i have only strangely configured computers available.
So I tried to flash twrp 3.0. 4 or something like this which I found as a zip file the installation runs just fine says it was successful but after rebooting to recovery it is 2.7 again.
I dont necessarily want to update twrp if i can flash lineage but i guess i have to?
Are there any recommendations for a lost soul.
All the best
Sorry for the false place for this maybe someone can move it to the right spaxe thx
Click to expand...
Click to collapse
Please follow one of the guides available, like this one, or the one in my signature.
You have to be aware that twrp 3 requires kernel isorec support, so you must have a kernel that supports isorec, and also you must have a 1GB system partition to be able to install any nogut or mm rom.
thank you so much managed to find this guide before you answered.
anyway thanks so much my s2 is running lineage smoothly and now we saved some piece of electronics of garbage to early the planet and me are thanking you so much for every one having the same problem as me go with philz touch recovery and then flash the twrp you want from there
all the best
Hi there,
Not sure what happened - I'm using my Tab S3 (SM-T820) for ages in the same (stable) configuration - rooted Stock, no changes/installations for months.
This morning it was in Odin/Download mode and I cannot boot into system.
I can get into recovery (TWRP), but I cannot boot into system from there either, it always returns to Odin (tried wiping Cache/Dalvik, didn't help).
For now my only idea is to let it completely discharge, charge again and give it another try.
No buttons appear to be stuck.
Any ideas or suggestions, eg sth I could check in TWRP to see what's going on?
(hopefully nothing wrong with the system partition).
Note - I'm only familiar with the typical TWRP functions needed to install custom firmware, haven't used it for much else. Obviously would prefer not to destroy my (stable) setup and spent a full day re-installing everything
Thanks a lot for your help everyone!
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
bmwdroid said:
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - yes, I will try that once the complete discharge is finished.
Reflashing stock - could cause this any troubles as it's already unlocked/rooted?
Or is there a chance dirty flashing the Tweaked Stock ROM could work, too?
Tablet was still on the original Stock it came with, but rooted with magisk and manually debloated...
Thanks again!
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
bmwdroid said:
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
Click to expand...
Click to collapse
Hi there and thanks again -
Took me a while to try everything but finally it's working again.
Complete battery drain didn't help, but dirty flashing did - once I got the correct version.
Basically made a nandroid backup, then flashed the tweaked rom over my existing one, starting with newer versions down to older ones.
So, flash, reboot - didn't work, restore nandroid (all), flash slightly older rom....
Till it started booting with v2.0 (probably matching my existing rom close enough).
Had to reflash Magisk as the 2.0 Rom included didn't match my Magisk Manager, but now my Tab S3 is working again!