Flashed just as dev thread stated and now I have a paperweight - Galaxy Tab 4 Q&A, Help & Troubleshooting

Rooted my tab 4 prior to trying to install BlissPop for the Galaxy Tab 4. Root checker verified that I was rooted. Installed TeamWin's recovery and followed these steps exactly
*Make sure you are rooted.
*Make sure you have a custom recovery installed. (TWRP is the preferred recovery)
*Download the latest Bliss Rom & the latest GApps package.
*Boot into recovery.
*Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
*Flash Bliss Rom
*Flash Google Apps package (for 5.1!)
*First boot may take up to 10 minutes
Now I am stuck on the Samsung Galaxy Tab 4 sm-t230NU powered by android start up screen. Before I flashed it said that it appeared my phone was not rooted but idk how this could be as I root checked and installed TWRP...I have rooted like 5 devices so far and have no idea why this happened....pretty disappointed right now as I FOLLOWED INSTRUCTIONS TO THE LETTER and now this happened. I can't even get it to boot into anything after using odin to reinstall the bootloader...what's going on...this is so frustrating...:crying::crying:

Are you sure you cannot boot into recovery? (Volume up + Home + Power, then release power as the device reboots) I honestly doubt it's a brick.
If you manage to get into recovery, then boot it into "Downloader" (or whatever the stock recovery calls it), send over a proper recovery like TWRP via Odin on you computer and then restore your backup (you DID make a back-up, right?). And if you don't have a back-up, get the official stock ROM from here, and start again.

terrorine said:
Rooted my tab 4 prior to trying to install BlissPop for the Galaxy Tab 4
. Root checker verified that I was rooted. Installed TeamWin's recovery and followed these steps exactly
*Make sure you are rooted.
*Make sure you have a custom recovery installed. (TWRP is the preferred recovery)
*Download the latest Bliss Rom & the latest GApps package.
*Boot into recovery.
*Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
*Flash Bliss Rom
*Flash Google Apps package (for 5.1!)
*First boot may take up to 10 minutes
Now I
am stuck on the Samsung Galaxy Tab 4 sm-t230NU powered by android start up screen.
Before I flashed it said that it appeared my phone was not rooted but idk how this could be as I root checked and installed TWRP...I have rooted like 5 devices so far and have no idea why this happened....pretty disappointed right now as I FOLLOWED INSTRUCTIONS TO THE LETTER and now this happened. I can't even get it to boot into anything after using odin to reinstall the bootloader...what's going on...this is so frustrating...:crying::crying:
Click to expand...
Click to collapse
Are you sure you used the right version of TWRP, ie the one for the SM-T230/NU? I ask because you mention BlissPop and I'm fairly certain there are no BlissPop builds available for the SM-T230NU. When flashing custom recoveries and ROMs, you have to make sure the model numbers match
Edit: you should've used this TWRP: http://forum.xda-developers.com/tab-4/general/root-galaxy-tab-4-7-t230-t2835264 If you used any other TWRP build, that would be why you ran into problems

Related

Trying to install cyanogenmod to nexus 4, I cannot flash it through TWRP recovery

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

[GUIDE] How to get CM 14.1 working.

Hi,
So I have created this thread just because I can see many people creating new threads as after flashing CM 14.1, their phone doesn't boot up. So for all those who are going to flash CM 14.1 or have already flashed it and can't get it working, this thread is for you.
What you will need:
1. Rooted OnePlus X (Obviously)
2. Custom Recovery (TWRP recommended)
3. Latest CM 14.1 build
4. Arsenic Kernel or BlackReactor Kernel
So this is how you get CM 14.1 working on your OPX (make sure your battery is above 80% just to be sure that nothing will go wrong considering battery's point of view)
Make sure you have backed up everything before performing the following steps as the process will wipe your data completely. (I would recommend to take a Titanium backup of all user apps and then taking a nandroid backup of system and data)
1. Download the required files and place them in your SD Card or internal storage
2. Reboot your device into recovery
3. Go to wipe, and swipe to factory reset (Note! This will completely wipe all the data from your device including app data and SMS! This won't wipe the contacts but just to be safe, have a backup of all your contacts)
4. Go to Wipe again, and go to Advanced wipe, select the following partitions - System, Cache, Dalvik cache. Swipe to wipe (Note! Make sure you have a backup of the System as this will wipe the Operating System from your phone!) Although this step isn't necessary, I like to do it.
5. Go to install, and direct to the location where you have saved the CM 14.1 zip file and the kernel. Select the files, and swipe to flash.
6. If you want anything else in your system, direct to that location, select the zip file, and swipe to flash. (Note! You need not flash the SuperSU zip file as CM offers Root access in developer options)
7. Reboot your system and wait for it to boot.
Viola! Your device is now running official CM 14.1 nightly.
Hope this helps! ?
Downloads:
1. Latest CyanogenMod nightly - found here https://download.cyanogenmod.org/?device=onyx
You can have any version of the nightly as long as it is CM 14.1
2. Arsenic Kernel R32 (or R31) - http://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Open the above thread and follow the guide
OR
Black Reactor kernel v1.0 - http://forum.xda-developers.com/oneplus-x/development/kernel-blackreactor-kernel-oneplus-x-t3460989
-Reserved-
Good Evening, @aamodjoshi23 THX a Lot. You are my Hero. Finally it works.
greetings
If you're facing some Error 7 while trying to flash cm 14.1, you can try updating the bootloader following this
http://forum.xda-developers.com/showpost.php?p=69267239&postcount=2560
I used the Oxygen OS 3.13 full ROM as recommended, edited updater-script (following those instructions)
Immediately after flashing the OOS 3.13 rom, you don't have to reboot.
I immediately flashed twrp 3.0.3 original from https://dl.twrp.me/onyx/
I then rebooted into twrp 3.0.3 (using the reboot button in twrp, then bootloader)
Then I installed (in this order):
cm 14.1 (https://download.cyanogenmod.org/?device=onyx)
arsenic kernel (as recommended above)
opengapps
Not sure if this step is necessary, but I wanted to let twrp patch the rom to not overwrite twrp so I rebooted into twrp again (using reboot --> bootloader in twrp)
Then I used reboot --> system
First boot took a while, but now I have nougat!!
kenel zip every time
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
allons-y said:
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
Click to expand...
Click to collapse
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
aamodjoshi23 said:
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
Click to expand...
Click to collapse
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
shashanksachdeva said:
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
Click to expand...
Click to collapse
First of all we need more info about your current ROM recovery etc.
Fap4k said:
First of all we need more info about your current ROM recovery etc.
Click to expand...
Click to collapse
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
shashanksachdeva said:
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
Click to expand...
Click to collapse
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Fap4k said:
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
This is because you flashed wrong recovery twrp 3.0.3 is for new bootloader and you are on old bootloader..that's why it all happened..so you just need to flash old recovery..then follow given link to upgrade bootloader and recovery.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
I've got a good news and bad news for you.
The bad news is, no one has the older 2.8.x TWRP image files and there are no threads that have the download links for the older version of TWRP. So you're stuck and you have lost your recovery. You have lost everything... Having no recovery means you can't do a lot of things like factory reset, any wipe of a partition, you won't be able to update your system, you won't be able to flash zip files to enhance your experience and many more... I'm sorry my friend...
The good news is, I've got you covered. I had saved the older TWRP so that if anyone one day would need that recovery image, I would be able to help them.
Download the older TWRP from here : https://drive.google.com/file/d/0B2Ms-zaNd3SiTmpxX0UtYUV2R1k/view?usp=drivesdk
Flash it. You should get back your recovery.
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Fap4k said:
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Click to expand...
Click to collapse
using resurrection remix marshmallow 6.0...
Plush suthar said:
using resurrection remix marshmallow 6.0...
Click to expand...
Click to collapse
Did you ever updated bootloader?
If not than update your bootloader and install latest recovery!!
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
By stuck on boot, I didn't know you meant that it showed only the OnePlus logo and not even powered by Android.
In that case, follow this guide to update your bootloader :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917

Cant install LineageOS 14.1 on G2 D802 (TWRP deletes root)

Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS
Quicka said:
Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS
Click to expand...
Click to collapse
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.
Jan Philipp said:
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.
Click to expand...
Click to collapse
i have done it... but after i wiped data,... etc. flashed lineage os and gapps and reboot system, phone screen gets black... and i can only go to download mode to flash again stock rom ive tried it about 5 times
Problem fixed
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec
Quicka said:
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec
Click to expand...
Click to collapse
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?
djsasha78 said:
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?
Click to expand...
Click to collapse
just held the volume up button and then connected with pc. then using lg flash tool to flash lollipop stock rom
1. Root + TWRP : https://www.dropbox.com/s/2shvozzbu29xjfu/LGG2-D802-OneClickRootRecoveryV1.1.zip?dl=0
2. Update TWRP to 3.1 by flashing zip file and then rebooting recovery: http://www.gregtwallace.com/lgg2-projects/twrp/?version=3.1.0-1
3. LineageOS by flashing rom zip file and gapps: https://download.lineageos.org/d802 + http://opengapps.org/ (ARM + Android 7.1)
easiest method to flash lineageOS on LG G2 https://www.youtube.com/watch?v=BoPjGM0nrak (Video tutorial)
Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?
JackSparreau said:
Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?
Click to expand...
Click to collapse
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.
cropsroth said:
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.
Click to expand...
Click to collapse
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks
JackSparreau said:
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks
Click to expand...
Click to collapse
Yes, you don't wipe after flash, but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. Check MD5 of the all files you downloaded with original MD5 to confirm the file didn't get corrupt.
Boot stack flash not needed. Please read the first post thoroughly in lineage thread
"""
Requirements:
Custom recovery (TWRP or any other)
KitKat (KK) bootloader (included in the lg-devs LP bootstack)
KitKat (KK) bootstack minimum; Please read the entire FAQ for important bootstack information. Installation of bootstacks is NOT recommended.
Clean flash if coming from another ROM or CM 13 (no dirty flash, wipe system too check you bootstack(needen bump support)
"""
crophs said:
... but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. ...
Click to expand...
Click to collapse
Hi,
what do you mean by "you swipe the factory reset", I'm not sure what it is, either "give it a clean shot again".
Sorry I'm not very aware of all those processes ^_^, and I'm french so not very aware of some vocabulary words
Thank you

Can't get custom ROM installed

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:

SM-P580 custom rom boot animation loop

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

Categories

Resources