Related
Hello members,i have a problem . I bought a samsung galaxy tab 3 7.0 wifi (SM-T210) last week and i have rooted it + installed cwm and after i flash anything(custom lock screen or custom rom) the tablet gets soft bricked and the rom dont boot anymore,it enters automaticaly in cwm. So how can i fix it?
d0vada said:
Hello members,i have a problem . I bought a samsung galaxy tab 3 7.0 wifi (SM-T210) last week and i have rooted it + installed cwm and after i flash anything(custom lock screen or custom rom) the tablet gets soft bricked and the rom dont boot anymore,it enters automaticaly in cwm. So how can i fix it?
Click to expand...
Click to collapse
Which recovery Version you are flashed on your tab?
And which root.zip you are used?
Flash Stockrom and try it again.
bierma32 said:
Which recovery Version you are flashed on your tab?
And which root.zip you are used?
Flash Stockrom and try it again.
Click to expand...
Click to collapse
Im using the latest TWRP recovery 2.7.0.0 and for root i use a zip called universal root armeabi *smth like that*
I allready flashed the stockrom 3 times and i got the same result. also im using the T210XXANC2 firmware.
In CWM, wipe data and factory reset. Then go to Download mode, use Odin and flash your stock rom. That should do it.
paranoidmarvin42 said:
In CWM, wipe data and factory reset. Then go to Download mode, use Odin and flash your stock rom. That should do it.
Click to expand...
Click to collapse
i have rooted stock rom running with latest twrp but if i flash a custom rom it wont boot anymore, it gets softbricked but i dont know why.
d0vada said:
i have rooted stock rom running with latest twrp but if i flash a custom rom it wont boot anymore, it gets softbricked but i dont know why.
Click to expand...
Click to collapse
What ROM are you trying to flash? You must have missed a step. Make sure you read the instructions carefully before doing anything and use a custom rom for your device. Try again. I'm also new to Android and has softbricked my tab a couple of times now.
Go back to stock. Let your device boot completely. Install recovery again. Reboot again.
To make it easier, how about watching a video so you can see how it's done properly? It helped me a lot. http://forum.xda-developers.com/showthread.php?t=2459817
Good luck.
paranoidmarvin42 said:
What ROM are you trying to flash? You must have missed a step. Make sure you read the instructions carefully before doing anything and use a custom rom for your device. Try again. I'm also new to Android and has softbricked my tab a couple of times now.
Go back to stock. Let your device boot completely. Install recovery again. Reboot again.
To make it easier, how about watching a video so you can see how it's done properly? It helped me a lot. http://forum.xda-developers.com/showthread.php?t=2459817
Good luck.
Click to expand...
Click to collapse
I want to flash seal rom. also, thanks for the links, i will check them later.
d0vada said:
I want to flash seal rom. also, thanks for the links, i will check them later.
Click to expand...
Click to collapse
Plesse,dont use TWRP , i prefere CWM or PhilzTouch,why : alot of user are have postet probs when they used TWRP.
Also i prefere after rooting The Blackhawk Kernel.
bierma32 said:
Plesse,dont use TWRP , i prefere CWM or PhilzTouch,why : alot of user are have postet probs when they used TWRP.
Also i prefere after rooting The Blackhawk Kernel.
Click to expand...
Click to collapse
So i have flashed (again) the stock firmware from sammobile,i rooted it,installed cwm 6.0.4.7 and then i flashed SEAL rom v4 and its not working. Its like something that doesnt let custom rom boot on my tab. Sad part is that i cant provide a logcat because the android wont boot.
EDIT: Do i have to unlock the bootloader?
d0vada said:
So i have flashed (again) the stock firmware from sammobile,i rooted it,installed cwm 6.0.4.7 and then i flashed SEAL rom v4 and its not working. Its like something that doesnt let custom rom boot on my tab. Sad part is that i cant provide a logcat because the android wont boot.
EDIT: Do i have to unlock the bootloader?
Click to expand...
Click to collapse
Last Try,
Have you flashed The Blackhawk Kernel?
If not , Boot Into recovery, make a full wipe, flash seal ,Blackhawk Kernel ,full wipe again and reboot.
If this all not help ,post your prob at The Rom Thread.
bierma32 said:
Last Try,
Have you flashed The Blackhawk Kernel?
If not , Boot Into recovery, make a full wipe, flash seal ,Blackhawk Kernel ,full wipe again and reboot.
If this all not help ,post your prob at The Rom Thread.
Click to expand...
Click to collapse
I allready tried 3 roms(seal, 4.2.2 beta 2 and inspire) and all goes to the same result. Also, after installing the cwm i flash first the blackhawk kernel and android boots normally (stock rom with custom kernel) but custom rom with or without custom kernel wont boot.
I had similar problem try flashing seal v3.
Hello everyone.
Im having this problme that only occurs in custom roms and custom recovery. I started having this problem after i updated my phone to official ColorOS 2.0.
So because i couldn't flash that firmware with TWRP I had to go back to Oppo Recovery. I did that and installed new ColorOS.
I then decided to install DU ROM back on my phone (gotta love stock android feel). I went about by flashing latest TWRP 2.8.0.1 to my phone. Restarded phone back into recovery.
This is when i noticed a horizontal line scrolling from top to bottom. I went back to the OS and it was fine. Rebooted back to recovery and the line was still there. I went ahead and flashed DU to my phone. Once it got done i rebooted and now the problem still occurred in the ROM itself. A restart didn't help it either. Went back to recovery and flashed ColorOS lite and problem wasn't there. But when i go back to recovery the problem still persists.
Anyone have this issue?
Everything was working fine before the Color update.
Try flash color is 1.2.6 and then go to flash twrp & DU
tork987 said:
Try flash color is 1.2.6 and then go to flash twrp & DU
Click to expand...
Click to collapse
Should I flash official or kayula rom?
Should i flash it with official recovery or twrp?
I would flash the official with twrp
I need to do some more investigation, but it seems like KitKat ColorOS 2.x contains a new bootloader that causes graphics issues when running custom firmwares (or probably older ColorOS if you didn't downgrade bootloader in the process, for example if you restored a recovery backup instead of flashing COS 1.2.6)
I'll look into methods for bootloader downgrade that don't involve flashing a complete ColorOS package this weekend. I'm not sure, but IIRC, I think some of the existing baseband packages might be sufficient for the bootloader downgrade.
Entropy512 said:
I need to do some more investigation, but it seems like KitKat ColorOS 2.x contains a new bootloader that causes graphics issues when running custom firmwares (or probably older ColorOS if you didn't downgrade bootloader in the process, for example if you restored a recovery backup instead of flashing COS 1.2.6)
I'll look into methods for bootloader downgrade that don't involve flashing a complete ColorOS package this weekend. I'm not sure, but IIRC, I think some of the existing baseband packages might be sufficient for the bootloader downgrade.
Click to expand...
Click to collapse
I think your right. New color os does have a new bootloader because before the update the boot logo didnt contain the words "powered by android" . With this new one the logo looks different and it states those words at the bottom for a few seconds.
tork987 said:
Try flash color is 1.2.6 and then go to flash twrp & DU
Click to expand...
Click to collapse
thanks. this did the trick!
djabi90 said:
I think your right. New color os does have a new bootloader because before the update the boot logo didnt contain the words "powered by android" . With this new one the logo looks different and it states those words at the bottom for a few seconds.
Click to expand...
Click to collapse
The boot logo and the actual bootloader are separate components.
Not my work but it works now.
How to
Reboot in recovery
Wipe device
Flash Rom and kernel:
Download for rom:
Flash this after:
Reboot
Recommend using twrp 3.0.0.1
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
FingerBlastJ said:
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
Click to expand...
Click to collapse
Kernel fixes hardware issues
and if I'm on note 5 moar rom with patch.... no issue flashing right?
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Blzfrost said:
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Click to expand...
Click to collapse
Just flash Rom and kernel everything will work.
MonkeyAround said:
Just flash Rom and kernel everything will work.
Click to expand...
Click to collapse
Oh I'm setting everything up right now for the flash! I'm so excited. Once I realized you linked to a note 5 Rom most of my questions got answered. My favorite part, the kernel was posted on my bday.
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
FingerBlastJ said:
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
Click to expand...
Click to collapse
Update your TWRP.
https://dl.twrp.me/zenltespr/
yea I tried doing that with Odin and it would freeze mid way. I also tried flashing a twrp update zip file on twrp and that didn't work either.
you think I should flash with flash fire?
bricked my phone by trying to flash newer version of twrp with twrp manager
been trying to flash unbrick tar and pit file to get back up and running but its not working.
any help is much appreciated
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
FingerBlastJ said:
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
Click to expand...
Click to collapse
Have you checked for root with root checker? I have lost root access a few times in the past?
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
FingerBlastJ said:
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
Click to expand...
Click to collapse
Last thing I can think of is when opening TWRP the first time. It asks if you want to make the system 'read only'. Did you select No?
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
FingerBlastJ said:
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
Click to expand...
Click to collapse
Not sure. You can click mount and see what is mounted. I am not sure that will work. I am not sure exactly what you are trying to wipe, but mount the items you are attempting to wipe and make sure the read-only is unchecked.
Try this:
Check to see if oem is checked
Re-root via root tar/odin
twrp 3.0.0.1 from edge files post in general
Backup stock
Wipe
Flash Moar
Don't reboot
Flash skyhigh kernel
Flash xposed(don't have to)
Reboot
Allow it to boot loop a couple time (from sky kernel)
Give 5-10 minutes to boot
I just did it with no issues and I've personally had more luck with 3.0.0.1 than any of the others.
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
FingerBlastJ said:
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
Click to expand...
Click to collapse
Your on Lp bootloader that's your issue.
Download Marshmallow tar from the general post I made for rooting Bpg1.
Flash tar and follow post.
twrp. 3.0.x.x is more for marshmallow. You need to be on 6.0.1 not 5.1.1.
Don't use fireflash on this device.
Fireflash is more for phones with locked bootloaders like Verizon s4 on the of1 update.
Fireflash isn't really up to date with our phone and could easily brick your device.
So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life
I have followed the below link from Oneplus community pages to unroot the mobile completely and install stock OOS
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
but now when I tried to follow the same steps to back to Stock OOS from CM 14.1 with TWRP 3.2.2 after running OEM LOCK command the mobile reboots and stalls at Oneplus logo screen with both the hardware buttons lights on and nothing happens I have tried several times to go to recovery mode manually but the same thng happens...after trying a lot I was forced to again unlock the bootloader and go back to CM 14.1 rom (it went back just after installing the twrp recovery ..which means that Stock recovery was not installed properly I guess)
Kindly help me with a solution to this problem as I want to go back to stock ROM again as Nougat Beta Might be released by this november end....
If u any other way of going back to stock OS fully kindly tell that also..
rahulopg42 said:
I have followed the below link from Oneplus community pages to unroot the mobile completely and install stock OOS
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
but now when I tried to follow the same steps to back to Stock OOS from CM 14.1 with TWRP 3.2.2 after running OEM LOCK command the mobile reboots and stalls at Oneplus logo screen with both the hardware buttons lights on and nothing happens I have tried several times to go to recovery mode manually but the same thng happens...after trying a lot I was forced to again unlock the bootloader and go back to CM 14.1 rom (it went back just after installing the twrp recovery ..which means that Stock recovery was not installed properly I guess)
Kindly help me with a solution to this problem as I want to go back to stock ROM again as Nougat Beta Might be released by this november end....
If u any other way of going back to stock OS fully kindly tell that also..
Click to expand...
Click to collapse
Did you try maybe return to 3.5.5 using the custom TWRP and then follow that guide?
Crash said:
Did you try maybe return to 3.5.5 using the custom TWRP and then follow that guide?
Click to expand...
Click to collapse
ya I just did that only...just that I didnt flash 3.5.5 rather restored it....so now I am on 3.5.5 rooted .....so you are saying to try the tutorial now..okh I will..
but wht to do if I face the same thng again..kiindly say tht as well
rahulopg42 said:
ya I just did that only...just that I didnt flash 3.5.5 rather restored it....so now I am on 3.5.5 rooted .....so you are saying to try the tutorial now..okh I will..
but wht to do if I face the same thng again..kiindly say tht as well
Click to expand...
Click to collapse
Well mate is a matter of test I really don´t have more answers maybe to wait other users to comment :good:,
thnxx man
Ah just seen you restored 3.5.5
Flash the stock 3.5.5 and then you should be good and I know why it's not booting when you restore from a backup you HAVE to also restore the system partition as well which is generally 3008mb in size or it simply will not boot.
I have no idea why this is the case but it's easily fixed by flashing stock 3.5.5 over the top.
daleski75 said:
Ah just seen you restored 3.5.5
Flash the stock 3.5.5 and then you should be good and I know why it's not booting when you restore from a backup you HAVE to also restore the system partition as well which is generally 3008mb in size or it simply will not boot.
I have no idea why this is the case but it's easily fixed by flashing stock 3.5.5 over the top.
Click to expand...
Click to collapse
i just tried to install stock 3.5.5 over freedom os and it said
error 7
Error installing zip file
this package is for "oneplus 3" yours is a " "
i was trying the unlocker guide https://www.youtube.com/watch?v=h5a9XOQceC8
so if you guys have any ideas
btw @daleski75 i get random reboots in the same locations with any 7.1/7.0 roms... thats basicaly why i want to go back to stock
gigeaky said:
i just tried to install stock 3.5.5 over freedom os and it said
error 7
Error installing zip file
this package is for "oneplus 3" yours is a " "
i was trying the unlocker guide
so if you guys have any ideas
btw @daleski75 i get random reboots in the same locations with any 7.1/7.0 roms... thats basicaly why i want to go back to stock
Click to expand...
Click to collapse
Side load it.