I have installed custom ROMs on several other tablets but the Samsung Tab A has me stumped.
1) started with the most recent Samsung Rom from SamMobile. Used ODEN, skipped all setup steps to the end. opened Developer Mode and set OEM unlock to YES.
2) PWR+VolUp+Hm to stock recovery, Factory reset.
3) Pwr+VolDn+Hm to download mode. Used ODIN to flash TWRP 3.3.1. Rebooted directly back into recovery not system which was TWRP as expected.
4) Rebooted back to download mode and used ODIN to flash Stock ROM again, again no setups and OEM Unlock Yes
5) Went into Download mode. Reflashed TWRP. Rebooted straight into TWRP again
6) Reformatted Data drive YES and validated drive > 0
7) Flashed Magisk with TWRP
8) Reboot into system. Stock ROM works perfectly and Magisk is working fine.
9) Reboot back into recovery and wiped data and cache
10) Flashed 3 different custom roms (1 after following all the steps above) and I cannot get any of them to progress beyond the animation bootloop.
I have read just about all of the references and others have success following a similar approach.
I am probably missing one small step. Please let me know of any ideas.
Thanks as I really want to move up to a Pie Rom
++++++
Ignore - it looks like all custom roms are for the t580 not p580. sorry.
don502 said:
I have installed custom ROMs on several other tablets but the Samsung Tab A has me stumped.
1) started with the most recent Samsung Rom from SamMobile. Used ODEN, skipped all setup steps to the end. opened Developer Mode and set OEM unlock to YES.
2) PWR+VolUp+Hm to stock recovery, Factory reset.
3) Pwr+VolDn+Hm to download mode. Used ODIN to flash TWRP 3.3.1. Rebooted directly back into recovery not system which was TWRP as expected.
4) Rebooted back to download mode and used ODIN to flash Stock ROM again, again no setups and OEM Unlock Yes
5) Went into Download mode. Reflashed TWRP. Rebooted straight into TWRP again
6) Reformatted Data drive YES and validated drive > 0
7) Flashed Magisk with TWRP
8) Reboot into system. Stock ROM works perfectly and Magisk is working fine.
9) Reboot back into recovery and wiped data and cache
10) Flashed 3 different custom roms (1 after following all the steps above) and I cannot get any of them to progress beyond the animation bootloop.
I have read just about all of the references and others have success following a similar approach.
I am probably missing one small step. Please let me know of any ideas.
Thanks as I really want to move up to a Pie Rom
++++++
Ignore - it looks like all custom roms are for the t580 not p580. sorry.
Click to expand...
Click to collapse
Have you had any luck finding a solution to this?
I am also looking for a working custom ROM for the Tab
Related
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje
Hey everyone.
I'm really hoping someone can help me. I just got my Redmi 2 Prime today, and before even properly setting it up I had rooted it. It wasn't long before I decided to try a different ROM. I decided on Resurrection Remix and TWRP recovery, both of which I flashed an ran flawlessly. RR booted up, everything was great.
I then tried flashing SuperSU again, after installing RR. Flashing the .zip file resulted in a boot loop, with no access to recovery, only fastboot.
What I've tried (with no success):
- Re-flashing TWRP (through Fastboot).
- Flashing CWM instead (through Fastboot).
- Flashing stock recovery (through Fastboot).
None of these have proven successful..... Can anyone give any advice on how to get out of this mess? I hardly feel up for having to take my phone into a shop without even having had it for 24 hours.....
TIA!
Fastboot flash Redmi 2 ROM. Download ROM file from MIUI forums and read the instructions there. Go to this link http://en.miui.com/a-234.html
i dont know if this comes at the right time,since fastboot is accesbile ,boot into fastboot, and flash recovery into boot(this may sound foolish but you can do it)
fastboot flash boot recovery_twrp.img
reboot,you will be taken into twrp
you can take a backup here,
now wipe all and flash the ROM.zip
anfd it should all work fine
I had the same problem when I switched from MIUI 8 4.4Kitkat to CM13 6.0
But I was able to solve it without fastboot.
RessurectionRemix and most roms esepecially CM based have "built-in" superSU manager.You just have simply to re-enable it on the developer settings.No need to flash supersu.zip,it would just make things worse.Download Flashify to boot in TWRP manually since flashing different ROMs will temporarily remove the TWRP(doing the button combination wouldn't boot into recovery,instead bootloop like you mentioned).
Then I was able to perform a restore on stock MIUI 8.
You have to download Flashify in order to manually force the phone to boot in recovery mode,since doing to volume up+power wouldn't let you.
I don't know if this is because my TWRP version only supports KitKat....or switching from 4.4-6.0 is a big gap.
Thanks for the responses!
I ended up solving the issue, though there wasn't really an issue to begin with. Turns out the button combination to enter recovery is different than stock (both volume buttons and power), though I did re-flash to the latest version of TWRP.
I'm now running Resurrection Remix without flaws!
But yeah, I realize now that CM based ROMs have a baked-in SU manager, it was foolish of me to flash the file without doing proper reading up beforehand!
So I my A2017G had RR-20170314 with TWRP 3.1.0-0 and AX7 R6 installed. Everything was working fine until today my phone rebooted while it was in my pocket. I didn't change anything before and haven't used it for some time and only noticed this through 2 short vibrations. Since then the phone refused to boot into system, TWRP was still accessible though. Three short blinks by the led directly after the bootloader screen and then the phone shut itself down.
Back in recovery I made a full backup and tried booting with deleting cache etc and installing the latest RR. Nothing worked.
When I went back to stock I was finally able to boot. Flashed TWRP 3.1.0-0 through axon7tool and installed RR again. And again only those 3 led blinks
Used "disemmcwp" to make sure write protection is disabled and noticed that when I rebootet the recovery got replaced by the stock one. Only if I enable write protection through "emmcwpenab" the recovery isn't replaced
Just checked the status of the bootloader and it still says unlocked.
I found two threads with a similiar issue but unfortunately nothing helped:
https://forum.xda-developers.com/axon-7/help/boot-recovery-boot-t3569364
https://forum.xda-developers.com/axon-7/help/3-flashes-reboot-phone-shuts-off-t3574324
Never experienced such a thing before. Any help is really appreciated ?
I'm really out of ideas what to do. And stock isn't really a permament solution
Are you using latest G bootstack? Is the device in dfu, or edl mode (check device manager on pc)?
Be very careful with that G version.
Yes since I was on RR before. Using the stock bootstack nor the one provided in the Los thread makes a difference.
Fortunately I'm not stuck in DFU mode. Booting to stock works, so does edl and twrp. But twrp only without using disemmcwp
I would try using older twrp. I've encountered this before but usually a reboot fixes it. I have not gone to twrp 3.1 yet, i think 3.0.4 was the one before.
lafester said:
I would try using older twrp. I've encountered this before but usually a reboot fixes it. I have not gone to twrp 3.1 yet, i think 3.0.4 was the one before.
Click to expand...
Click to collapse
Tried it with TWRP 3.04-1 and it's the same result.
Reboot diseemcwp -> recovery gets replaced by stock recovery after reboot
Reboot emmcwpenab -> recovery gets not replaced
In both cases I am unable to boot with a modified system or kernel.
Seems like the write protection is screwed up
Cyb3rzombi3 said:
Tried it with TWRP 3.04-1 and it's the same result.
Reboot diseemcwp -> recovery gets replaced by stock recovery after reboot
Reboot emmcwpenab -> recovery gets not replaced
In both cases I am unable to boot with a modified system or kernel.
Seems like the write protection is screwed up
Click to expand...
Click to collapse
If you disable write protection you inadvertently end up tripping dm-verity, which causes the device not to boot (security feature).
The reason you feel that disabling system write protection through TWRP causes TWRP to get overwritten by the stock recovery, could be because of the reboot rather than anything else.
I.e. When you install the stock system and reboot, the system overwrites the recovery partition, installing the stock recovery.
My suggestion:
- Make a backup.
- Wipe dalvik cache, cache, system, and data through recovery (under Wipe-> Advanced Wipe).
- Check that the filesystem of the partitions are ext4 (through the "file system" button under Wipe->Advanced Wipe menu), and change them if necessary.
- Reboot recovery.
- Don't swipe to allow system modifications.
- Install the stock bootstack, stock system (I'm assuming that you are using DrakenFX's image zips), and reboot.
- If it fails to install, just reboot recovery, and try to install once again.
Let me know if this works for you.
Erahgon said:
If you disable write protection you inadvertently end up tripping dm-verity, which causes the device not to boot (security feature).
The reason you feel that disabling system write protection through TWRP causes TWRP to get overwritten by the stock recovery, could be because of the reboot rather than anything else.
I.e. When you install the stock system and reboot, the system overwrites the recovery partition, installing the stock recovery.
My suggestion:
- Make a backup.
- Wipe dalvik cache, cache, system, and data through recovery (under Wipe-> Advanced Wipe).
- Check that the filesystem of the partitions are ext4 (through the "file system" button under Wipe->Advanced Wipe menu), and change them if necessary.
- Reboot recovery.
- Don't swipe to allow system modifications.
- Install the stock bootstack, stock system (I'm assuming that you are using DrakenFX's image zips), and reboot.
- If it fails to install, just reboot recovery, and try to install once again.
Let me know if this works for you.
Click to expand...
Click to collapse
Already did those steps but instead of using DrakenFX's files I used the official stock zip.
Shouldn't make a difference right?
Gonna try it once more...
Edit:
I'm stock now, TWRP installed without allowing system modifications.
Edit2:
Just rebootet and the recovery is gone again. This happened after I dlashed the recovery again after reverting to stock.
Edit3:
So what I tried so far after reverting to stock after each fail:
- flash SuperSU 2.65 -> unable to boot
- flash SuperSU 2.97 -> unable to boot
- flash Magisk 11.6 -> boot successful, Magiks installed and showing root but unable to request root permissions
- flash latest Los -> unable to boot
- flash latest RR -> unable to boot
- flash latest tool to disable dm-verity (from TWRP thread: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/) -> unable to boot
- flash AX7 R1 -> unable to reboot
Did the above steps with allowing system modifications and without.
Same for rebooting with disemmcwp and reformatiing partitions.
Tried using the universal bootloader from Los thread and still wasn't able to boot except using the stock rom.
I'm really out of ideads what I could try next.
Recovery seems to stick for now.
Could it be that the problem is not dm-verity but something else?
When I rooted the device I encountered no problem with that security mechanism. Custom roms and kernels worked as well without ever having to worry abou that.
Finally managed to boot into RR!
Here is what I did:
1. Went back to B10
2. Relocked bootloader
3. Booted into system -> developer settings -> Oem Unlock
4. Unlocked bootloader
5. Flashed recovery through fastboot
6. Booted directly into TWRP (when I did a restart it was overwritten immediately that's why I booted directly into it one the second try)
7. Allowed system modifications inside TWRP and flashed SuperSU 2.65
8. Successfully booted into system and had root
9. Flashed Universal Bootloader and Modem from Los thread
10. Flashed RR + Gapps
I really don't know which step the crucial one was but I hope if someone else manages to get into the same situation as I did those steps will help.
Thank you guys for helping me out
I'm having a very difficult time getting this phone setup. I can get very, very close... but then it starts boot looping into recovery.
So starting at the beginning, here is what I did:
- Booted up phone, make sure it works and connects to wifi (I find out later that it got encrypted, even though I didn't set a PIN).
- Inside the OS on first boot, I install and use the official bootloader unlock APK from Asus.
- Rebooted into the bootloader and fastboot flashed TWRP.
- Rebooted into TWRP and flashed the Oreo modem, current unofficial Carbon OS 6.1, nano gapps, and magisk 16.6.
- Rebooted and the Carbon ROM logo comes up. It works for about 2-3 minutes, then reboots.
- After many attempts to decrypt (and a lot of help from the forum), I successfully restore the phone to "WW_ZE552KL_14.2020.1712.85_M3.10.47.15_Phone-user.raw.zip" with the Asus tool.
- Phone is fixed and booting again to the OS, but I'm back to square one.
Second attempt:
- Thinking I need to flash the raw Oreo ROM (instead of just the Oreo modem), I use the Asus tool to flash "WW_ZE552KL_15.0410.1803.55_M3.10.47.19_Phone-user.raw.zip"
- The phone works fine and is now an Oreo ROM with an Oreo modem
- It's still unlocked, so I rebooted into the bootloader and fastboot flashed TWRP.
- Rebooted into TWRP and flashed the current unofficial Carbon OS 6.1, nano gapps, and magisk 16.6.
- Rebooted and the Carbon ROM logo comes up. It works for about 2-3 minutes, then reboots.
- After the reboot, it goes to TWRP... whether I just let it boot on its own, or press power when it says: Start - Continue to boot >
What am I doing wrong?
You're having a rough go at this one eh.
I know we talked about this before, but did you try a factory reset and wiping cache/dalvik before rebooting?
Yes. As we discussed before, you can't wipe cache from TWRP. So I'd wipe dalvik from TWRP, then reboot to the bootloader to do a "fastboot format cache".
I'm going to try a different ROM later this afternoon. Maybe that will make a difference.
Flapjack said:
I'm going to try a different ROM later this afternoon. Maybe that will make a difference.
Click to expand...
Click to collapse
Hello! I've been able to boot any ROM by:
1. flashing TWRP
2. rebooting to recovery
3. installing the ROM zip
4. rebooting to bootloader
5. fastboot continue
But when I restart the phone, it always boots to recovery(TWRP), so I have to repeat steps 4 and 5 to boot the ROM, which is
Could you try and tell me if it works for you too?
I'm gonna take a moment to read about the boot process in depth, as it seems there is no straightforward solution to this out there.
junglesnake said:
Hello! I've been able to boot any ROM by:
1. flashing TWRP
2. rebooting to recovery
3. installing the ROM zip
4. rebooting to bootloader
5. fastboot continue
But when I restart the phone, it always boots to recovery(TWRP), so I have to repeat steps 4 and 5 to boot the ROM, which is
Could you try and tell me if it works for you too?
I'm gonna take a moment to read about the boot process in depth, as it seems there is no straightforward solution to this out there.
Click to expand...
Click to collapse
1) Flash Oreo RAW (can be downloaded from @Saktis_STi' s unlocking thread.
2) Boot till system
3) Flash TWRP
4) Flash ROM, Magisk, GApps
5) Reboot
The reason why it reboots to TWRP is because of 'encryption' thingy.
BootloaderBoi said:
1) Flash Oreo RAW (can be downloaded from @Saktis_STi' s unlocking thread.
2) Boot till system
3) Flash TWRP
4) Flash ROM, Magisk, GApps
5) Reboot
The reason why it reboots to TWRP is because of 'encryption' thingy.
Click to expand...
Click to collapse
many many thanks! I was able to get Ressurection Remix working by now
your steps were right, and I will detail them better to tell how I made it work for others reading this thread:
1) Flash Oreo RAW
1.1 - @Saktis_STi's thread is a bit outdated. I downloaded the newest firmware from Asus website.
1.2 - I also had to find a recent recovery.img, which I think I got it from here https://forum.xda-developers.com/zenfone-3/how-to/original-recovery-img-boot-img-zenfone-t3572188
1.3 - I used the stock recovery's adb sideload to flash the stock ROM
2) Flash TWRP - all good here
3) Flash ROM, Magisk, GApps
3.1 - I wiped system, data, cache and dalvik.
3.2 - I flashed RR ROM, GApps and Magisk (EDIT 2: install all three before the first custom ROM boot, or GApps won't work)
3.3 - Performed a Factory Reset
4) REBOOTED TO GLORY!
For what it seems, the stock ROM encryption that is performed on the stock's first boot was the enemy.
Now one last thing... In Security -> Encription, my device is NOT encrypted.
Do I run the risk of ruining everything if I encrypt it?
EDIT: No, it didn't break, working fine
junglesnake said:
1) Flash Oreo RAW
1.1 - @Saktis_STi's thread is a bit outdated. I downloaded the newest firmware from Asus website
Click to expand...
Click to collapse
lmao. His RAW firmware version is the latest version though
https://forum.xda-developers.com/zenfone-3/development/updated-unlock-relock-bootloader-t3749456
Anyways, enjoy your phone running on custom ROM :good:
Hi all,
So many years ago I used to do this flashing the custom roms on my old galaxy s4, and it was pretty straight forward.
THis s8 though is giving me real problems.
I'm trying to flash lineage 19 on it but I just can't seem to do it. I have run into error messages, boot loops, apparently deleted the boot sector off after using TWRP which only worked once...
I have googled and googled but I can't find the exact guide for my phone. It's a UK phone.
I have managed to get a samsung rom back on it using Odin, but it's got so T roam option which doesn't do anything..
Please can someone help?
It should work like this:
1. Enable OEM-unlocking in the developer options
2. Download the no-verity-opt-encrypt rom (google it, you will find links) on an SD Card or if you can plug that in your phone on an USB Stick
3. Install twrp using odin ( you was able to do this, right?)
4. Boot into twrp (Do not boot in the os first, go to twrp directly after flashing it)
5. Go to wipe, tap on format data and type "yes" to format your data partition.
6. Flash the no-verity-opt-encrypt zip
7. You can now boot to the system. If you already have the install zip for Lineage, you can also flash this now before booting to the system.
8. Done