Hey i flashed the CM-13 on my GT-N5100. At first, it worked well. I can even installed GApps package and changed the theme. Then i tried to install SuperSU and it asked to install the SU binary. So i installed it using flash recovery. It succeed, but when i tried to reboot the phone, it stucked on the "marshmallow" animation boot. I have tried to wipe data and cache, but those didn't work. Then i tried to re-install the CM-13 package (using flash recovery ofc) but it just showed an error message. What should i do? I'm planning to downgrade the phone back to Kitkat. Would it do? Or is there any other way? Please help. Thanks!
hyemun01 said:
Then i tried to install SuperSU and it asked to install the SU binary. So i installed it using flash recovery. It succeed, but when i tried to reboot the phone, it stucked on the "marshmallow" animation boot. I have tried to wipe data and cache, but those didn't work.
Click to expand...
Click to collapse
Hi
had the same problem yesterday, i found no other way as to make a complete wipe (including SYSTEM!) in TWRP and then without rebooting install the ZIP again. Than it was resurrected.
But make sure that the ROM Zip is on the external sd card.
The problem is the SuperSU, just use the internal Root function.
Related
Hi everyone
Sorry in case of repost.
I have a P5210 (Samsung Tab 3 Wifi). Once rooted everything was allright until I entered in recovery mode from the Rom Toolbox app.
I'm now stuck in a recovery loop mode and can't get out (CWM v6.0.4.7)
I've tried everything from factory reset / cache and dalvik cache wipe, to "fix" zips and so on. But nothing changes.
I've tried to reinstall CWM by putting a recovery image into a script and flash it through CWM. Seems to be done correctly, but when I reboot, it's still the same CWM (no update)
Eventually, i've tried to install some custom ROMs to start fresh : Every installation crashes at "WRITING SYSTEM PARTITION". I get black screen and a reboot.
And I've tried every custom Rom compatible with P5210.
Can you help me to get back to a clean configuration ?
N.
nicobee75 said:
Hi everyone
Sorry in case of repost.
I have a P5210 (Samsung Tab 3 Wifi). Once rooted everything was allright until I entered in recovery mode from the Rom Toolbox app.
I'm now stuck in a recovery loop mode and can't get out (CWM v6.0.4.7)
I've tried everything from factory reset / cache and dalvik cache wipe, to "fix" zips and so on. But nothing changes.
I've tried to reinstall CWM by putting a recovery image into a script and flash it through CWM. Seems to be done correctly, but when I reboot, it's still the same CWM (no update)
Eventually, i've tried to install some custom ROMs to start fresh : Every installation crashes at "WRITING SYSTEM PARTITION". I get black screen and a reboot.
And I've tried every custom Rom compatible with P5210.
Can you help me to get back to a clean configuration ?
N.
Click to expand...
Click to collapse
Hi
It seems you were on kitkat rom which may have updated your bootloader to kitkat version. The CWM needs to be updated to work well with kitkat. I had similar problem with my SM-T210, and solved the problem after updating CWM as per this post for T210:
http://forum.xda-developers.com/showthread.php?t=2433853
Your tab is different from mine so i think you need a fresh stock rom install using odin, then find an updated CWM for your tab.
Hello, I decided to root my device using Odin. I followed steps from a video and successfully rooted and installed twrp with flashify. When I booted to twrp I did a swipe without backup. I proceeded to install CM11 nightly with the gapps zip. Everything went well during installation and the device rebooted. I saw the cm mod logo upon reboot but I get error setup wizard failed after boot. I cant access the tablet or anything. All I see is the blue CM wallpaper and no apps. Upon further investigation, it turns out I flashed the wrong gapps zip? I tried rebooting to twrp recovery to reflash gapps. But problem is that I cant access twrp recovery only the stock recovery. It gives me limited options...update from adb, update from external, wipe data, wipe cache... Is there anyway to fix this? I installed adb and fastboot but when I install rom using adb sideload, i get signature failures all the time. I tried fastboot but apparently there is only download mode (which i used when rooting with odin). My device isnt recognized with fastboot devices command only adb devices. Can anyone help? I am new to this stuff.
Hi,
I will have your thread moved to your device section.
Good luck!
Try to wipe cache, then flash TWRP again by Odin.
If you can get TWRP up and running, you should be able to do the default wipe (cache, Dalvik, and user data) and flash CM11 and gapps again.
I think I had the same issue with CM11 not booting since I flashed the wrong gapps. But flash the right gapps, and you should be ok.
Hi all,
after I had a full crash while I was trying to update 4.0.0 -> 4.0.1 I now installed all from the scratch.
I now try to get root for it. I installed TWRP (twrp-3.0.2-1.28-oneplus3.img) ... opening it it asks me to bring in a PIN. every PIN I enter is wrong. If I choose cancel I am in. But System is accessable.
Anybody can post a real HowTo for getting root (SuperSU) in OxygenOS 4.0.1
Thanks in advance
After you flash the rom, flash SuperSU immediately. Then reboot to recovery, NOT to system.
If the phone stuck, force reboot by pressing power& vol.- . Reflash recovery, reboot to recovery, reboot to system.
Adb Sideload SuperSu via TWRP
Harish_Kumar said:
Adb Sideload SuperSu via TWRP
Click to expand...
Click to collapse
This worked for me!
@all: does anybody have the Stock Recovery .img for "OxygenOS 4.0.1"?
I always get this "the dm-verfiy ..." message. And after booting I have to type in the unlock PIN ... booting again ... ready to use. I think is is because TWRP
How did you do?
Skickat från min ONEPLUS A3003 via Tapatalk
null0seven said:
After you flash the rom, flash SuperSU immediately. Then reboot to recovery, NOT to system.
If the phone stuck, force reboot by pressing power& vol.- . Reflash recovery, reboot to recovery, reboot to system.
Click to expand...
Click to collapse
can you explain me what the purpose of rebooting into recovery after flashing supersu and not to system?
On some roms, you have to instal SuperSu, before first boot. Or you will not have root.
Some rooms will mess up recovery if youre first boot it's in system & not to recovery. You reboot, to recovery, first, to be shure that you have a working recovery.
This is how I did: upgraded to OOS 4.0.1, flashed the latest TWRP (3.0.3-0), copy & paste SuperSU to internal storage then flashed it through TWRP. Everything works fine.
Now I'm trying to figure out how to decrypt this phone because OOS 4.0.1 converts the Data partition file system to F2FS. I'm a heavy user of MultiROM, that's the reason for decrypting.
I was using 4.0.0 stock with twrp and root. Tried to install the 4.0.2 update but every boot just took me back to recovery. Tried wiping clean, no change. Tried installing stock recovery v2.0, recovery would hang. Tried using new twrp 3.0.3 and I could get back in, but any ROM, stock or not I installed, would not stick.. Even twrp would warn me "no os installed. reboot anyway?" even when I had just installed a ROM. So in the end I flashed OOS 3.2.8 with twrp and then flashed stock recovery. At this point I'm pretty much at factory stock at v3.2.8 with stock recovery v1.0. Now I'm trying to update to 4.0.2 via OTA and for the 3rd time already I have received a installation failed message and rebooted to system. The first time I thought it was because I disconnected VPN after starting the download, so I downloaded a second and a third time. I don't want to resort to sideloading again because I fear I might get the same no OS installed problem I got when I tried to install 4.0.2 in the first place. Does anyone have any insight on what is wrong?
Steps:
1. Install latest Official or Modified TWRP ( 3.0.3/ 3.0.3 version 14 by eng.stk)
2. Enter into recovery. Connect phone to PC and copy downloaded ROM file.
3. Wipe everything in the recovery- Data, System, cache and Dalvic. It will erase everything.
4. Flash ROM zip after completing, don't reboot phone. Reboot to recovery again, and then reboot phone.
If u reboot phone directly after flashing ROM, u will loose TWRP.
Even twrp would warn me "no os installed. reboot anyway?" even when I had just installed a ROM.
Click to expand...
Click to collapse
This is pretty normal for nougat OOS. I've faced it for all 3 ROMs i flashed. Don't worry, your ROM was flashed successfully. You can mount and check the /system partition, you can see your ROM files there.
So here's what worked for me. (considering you are on ext4 /data)
1. Flash latest official twrp recovert ext4 version or use the file system swapper zip if it doesn't decrypt your data in recovery. TWRP has some issues as of now and mounts f2fs as default, so you just need to flash the file system swapper zip in order to swap it to ext4 by default.
2. Wipe /system /cache and dalvik cache.
3. Flash full 4.0.2 ROM zip, should be 1.4 GB in size.
4. Flash TWRP image again just in case.
5. Reboot to recovery, not to system.
6. Flash stable 2.79 Super Su and you are good to go.
Thanks for the tip, however I don't mind losing twrp, I only want to get stock unaltered update and this procedure does not help in this
IonAphis said:
Thanks for the tip, however I don't mind losing twrp, I only want to get stock unaltered update and this procedure does not help in this
Click to expand...
Click to collapse
Have you tried this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
P.S. I think you did, but I'm just asking.
Thanks for the tip, but I fixed it. Ended up flashing v3.2.8 via twrp and installed OTA to 4.0.1 via sideload. Recovery would not boot unless first fully booted into the system. After that sideloaded 4.0.2 via OTA and now back to complete stock.
Thanks guys!
Hi Guys.
im new here. hoping you guys can help me.
i accidentally wipe may system and i dont have any backups.
i try installing (lineage-14.1-20161229-UNOFFICIAL-audahadi-Z00ED)
and (Z00E_MM_13.10.7.1_Optimised_22062016)
any one of them installed success fully Via TWRP
First the (LineAge) then i wipe cache and data. and i try to reboot. but still can't boot:crying:
second one the (Z00E_MM) of course i wipe all first even data and reboot (twrp says no OS installed)
then i flash via flashboot(CMD) TWRP.img and reboot again to enter TWRP
then install boot.img and the ROM (Z00E_MM) and it successed.
and try rebooting it again via TWRP...
But Still Not Booting.:crying::crying:
what did i miss?? please Help me..:crying: