abc
I haven't personally played around with the unbrick tool at all, so I can't help you on that current condition. But I would like to point out the following (my comments in red text):
Keanu73 said:
It's been a week since I attempted to root my phone.
First thing you should have done after flashing TWRP (before flashing any mods), is to make a backup of the stock ROM. This gives you a stock backup you can easily revert to, if you run into any problems rooting. etc.
I had followed through one of the guides, got up to the point where I had installed the dm-verity patch and SuperSU. I rebooted. It had soft-bricked. Problems with root are usually caused by wrong version TWRP, or wrong version SuperSU (or Magisk is also a good alternative), and wrong version DM-verity may be a problem, as well. Sometimes, the solutions is a simple as flashing the right version (but sometimes you may need to restore the stock ROM first).
So then I went into TWRP and factory reset the device. Of course, that deleted the stock ROM.
There is no "of course" applicable here. Factory reset does not in itself delete the stock ROM. All it does is wipe user data, and cache. If you went into the Advanced TWRP options, that is a different thing. What you should have done is come on here, and seeked advice.
Click to expand...
Click to collapse
redpoint73 said:
I haven't personally played around with the unbrick tool at all, so I can't help you on that current condition. But I would like to point out the following (my comments in red text):
Click to expand...
Click to collapse
Yea... I realised this all too late..
Keanu73 said:
Yea... I realised this all too late..
Click to expand...
Click to collapse
I solved the issue. It seems that my phone WAS a OnePlus 3 and not a 3T.
Related
I've been using TWRP ever since I have rooted mt ONE. Over the last few days its been crashing while trying to install any zips at all.I can do a nandroid restore but nothing else. When I try to install any file it just goes to a black screen and reboots the phone.
Any ideas of what could be causing this and how to repair it also.
Thanks
I've also just replaced TWRP with clockwork mod touch and that is doing the same thing. I am now at a stage where I cannot install anything via the recovery method.
What is my bet options for starting afresh as my phone is unlocked with HTC dev and rooted also.
I'd like to go back to the beginning and start again.
Thanks
potsykate said:
I've also just replaced TWRP with clockwork mod touch and that is doing the same thing. I am now at a stage where I cannot install anything via the recovery method.
What is my bet options for starting afresh as my phone is unlocked with HTC dev and rooted also.
I'd like to go back to the beginning and start again.
Thanks
Click to expand...
Click to collapse
This seems to becoming a more and more recurrent event, though I cannot say for what the correct solution is, check these two threads:
http://forum.xda-developers.com/showthread.php?t=2435499
http://forum.xda-developers.com/showthread.php?t=2423817
one of them had to fix a corrupt partition, the other just reflashed and wiped again and again, and it worked.
If something works out for you do share!!
Thanks for that,I'll redownload my favourite Rom and try again without trying to update the Kernel,everything was fine as I remember before I tried the kernel update.
I'll let you know how I get on in a while.
potsykate said:
Thanks for that,I'll redownload my favourite Rom and try again without trying to update the Kernel,everything was fine as I remember before I tried the kernel update.
I'll let you know how I get on in a while.
Click to expand...
Click to collapse
Though the reasons are still unclear (at least to me ), it seems that flashing a custom kernel while still in recovery immediately after the ROM does work. Of course, make sure you're flashing a compatible kernel to the ROM; the version numbers of the custom kernels do not correspond to the ROM versions, and I've seen some that flashed an incompatible kernel, just because the version numbers looked similar.
Good luck & keep us posted
PS: If you do solve it, please update the main thread title to include [SOLVED]. thanks
Thanks for the two links,after reading them and doing a fresh install off my rom. Wiping cache,delvick and data I seem to be able to install zips again from recovery without the black screen and reboots.
Yep, so far all the zips that failed earlier are now installing.
A BIG THANK YOU :good::good:
potsykate said:
Thanks for the two links,after reading them and doing a fresh install off my rom. Wiping cache,delvick and data I seem to be able to install zips again from recovery without the black screen and reboots.
Yep, so far all the zips that failed earlier are now installing.
A BIG THANK YOU :good::good:
Click to expand...
Click to collapse
Excellent
Edit the main thread title to include [SOLVED] so that others can refer to it :victory:
Hello Folks!
So I've had this weird bug for a few months now (can't remember when it started).
Everytime the keyboard pops up for a writing field, it stays open, even when I exit the field, or the app itself where the process was called. The only way to make it hide again is to press the back button, or to press home twice. This is really really really annoying!!
Anyone else has had this bug? Have you been able to fix this?
FYI: I'm running a stock-based ROM 4.4.2 with XPOSED/Gravitybox installed; I already tried disabling modules; I already did a new clean install; This bug happens with any keyboard (Swype, Swiftkey, Flesky, Google)
Please Help!
Charlie.igg said:
Hello Folks!
So I've had this weird bug for a few months now (can't remember when it started).
Everytime the keyboard pops up for a writing field, it stays open, even when I exit the field, or the app itself where the process was called. The only way to make it hide again is to press the back button, or to press home twice. This is really really really annoying!!
Anyone else has had this bug? Have you been able to fix this?
FYI: I'm running a stock-based ROM 4.4.2 with XPOSED/Gravitybox installed; I already tried disabling modules; I already did a new clean install; This bug happens with any keyboard (Swype, Swiftkey, Flesky, Google)
Please Help!
Click to expand...
Click to collapse
Can you provide more details? You say "stock-based" ROM, so I'm not sure if you are using safestrap or have an unlocked bootloader. Also, you don't mention if you used RSD Lite/manual fastboot method, OR TWRP to do your "clean install".
These additional details will help with troubleshooting....
And no, I'm not experiencing these issues.
samwathegreat said:
Can you provide more details? You say "stock-based" ROM, so I'm not sure if you are using safestrap or have an unlocked bootloader. Also, you don't mention if you used RSD Lite/manual fastboot method, OR TWRP to do your "clean install".
These additional details will help with troubleshooting....
And no, I'm not experiencing these issues.
Click to expand...
Click to collapse
Thanks for the swift reply!
I'm on the KangKat ROM (See here: http://goo.gl/sp1ciz), and my bootloader is unlocked.
When I said clean install, I meant doing a full data/system/dalvik wipe, then flashing ROM via TWRP. Also, in case it matters, I'm on Dalvik and have never tried ART Runtime.
Charlie.igg said:
Thanks for the swift reply!
I'm on the KangKat ROM (See here: http://goo.gl/sp1ciz), and my bootloader is unlocked.
When I said clean install, I meant doing a full data/system/dalvik wipe, then flashing ROM via TWRP. Also, in case it matters, I'm on Dalvik and have never tried ART Runtime.
Click to expand...
Click to collapse
Ok, I do indeed have a suggestion for you.
Please consider doing a 100% complete return to stock by following the instructions in the "Return to 100% stock" thread - located in the General Sub-forum.
Be sure to flash the SAME EXACT (or newer) version that your are currently running (DO NOT Downgrade), and also be sure to use the correct firmware for YOUR variant.
Afterwards, you can flash TWRP back on, and re-install KangKat rom. Additionally, according to the installation instructions for that ROM, you are not supposed to WIPE /system before installing it. So once you have followed the return-to-stock guide, and re-flashed TWRP back on, be sure to install the KangKat rom without first wiping /system.
Links to all of the tools, drivers, and firmware files themselves are located in the Return to stock thread -- everything you need.
Please follow my advice, which will give you a *truely clean install*, and post back as to whether or not it worked for you.
The process is actually pretty quick. If you already have the necessary tools and drivers, it should take you less than 20 minutes to complete the ENTIRE procedure, including re-flashing the KangKat ROM.
Good Luck :good:
Hello, My brother have a XT1053 that he was trying to install CM 12 on it, but accidentally he wiped up his entire phone ( including system ). Now when he turns his phone on it stays on the Bootloader Unlocked screen forever. Im not an android user so i dont have any idea of what to do. my brother does not speak english so he cant search for a solution. Is there anything that could be done to "save" the phone?
Kurinn said:
Hello, My brother have a XT1053 that he was trying to install CM 12 on it, but accidentally he wiped up his entire phone ( including system ). Now when he turns his phone on it stays on the Bootloader Unlocked screen forever. Im not an android user so i dont have any idea of what to do. my brother does not speak english so he cant search for a solution. Is there anything that could be done to "save" the phone?
Click to expand...
Click to collapse
Restore the phone using RSD. Very simple. Simple search will give you the answer. Just a reminder. You should always have a backup before flashing any ROMs. ESPECIALLY stock, that way if something like what you said happens. You can easily recover. Hence the custom recovery Wiping it clean on accident is also difficult. Not sure how one does that. Hope you're using TWRP.
kcuffel said:
Restore the phone using RSD. Very simple. Simple search will give you the answer. Just a reminder. You should always have a backup before flashing any ROMs. ESPECIALLY stock, that way if something like what you said happens. You can easily recover. Hence the custom recovery Wiping it clean on accident is also difficult. Not sure how one does that. Hope you're using TWRP.
Click to expand...
Click to collapse
Ok, i already downloaded RSD but i cant find the stock firmware for the phone. Yes im using TWRP, and you asked how he wiped it up, he was selecting the items to wipe and misclicked on system.
Another Method
Install ClockWorkMod Recovery. (Phil's touch CWM). This has the option to mount storage as USB drive. use this to copy the ROM you want to install in the phone. Then disconnect phone and flash the ROM. :good:
TWRP does not have this option. or atleast i have not been able to find it. I know CWM has it because i screwed up once like this with my old phone, and did this to get back to normal.
Kurinn said:
Ok, i already downloaded RSD but i cant find the stock firmware for the phone. Yes im using TWRP, and you asked how he wiped it up, he was selecting the items to wipe and misclicked on system.
Click to expand...
Click to collapse
Sites with STOCK Moto roms for the X are listed in this thread -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
Or download the correct sbf, extract, flash in bootloader.
I have been experiencing certain issues w my phone and decided to do a factory reset.
Originally i was getting the TWRP loop when my celluar phone provider was trying to push an update.
Well after doing the factory reset, it went into TWRP. I"m not sure why, but that's where I am. I currently do not have an OS installed.I tried downloading a purenexus_shamu-7.1.1-20170215-OFFICIAL rom through some thread that I read, hoping to get a rom installed (excuse my terminology)
The system updated the partition, flashed itself, but still boots into TWRP.
I was at times able to get into the Pure rom? But then it had no apps. not even google play for me to use to download more apps.
Can someone pls provide a step by step of what to do to get me back up and running and disable this TWRP program permanently?
Thank you.
kaiotes said:
I have been experiencing certain issues w my phone and decided to do a factory reset.
Originally i was getting the TWRP loop when my celluar phone provider was trying to push an update.
Well after doing the factory reset, it went into TWRP. I"m not sure why, but that's where I am. I currently do not have an OS installed.I tried downloading a purenexus_shamu-7.1.1-20170215-OFFICIAL rom through some thread that I read, hoping to get a rom installed (excuse my terminology)
The system updated the partition, flashed itself, but still boots into TWRP.
I was at times able to get into the Pure rom? But then it had no apps. not even google play for me to use to download more apps.
Can someone pls provide a step by step of what to do to get me back up and running and disable this TWRP program permanently?
Thank you.
Click to expand...
Click to collapse
Well, the question is:
Honestly... Did you ever read the PureNexus thread?
Check this post for a detailed install (Google apps links in first post):
https://forum.xda-developers.com/showpost.php?p=61653759&postcount=4
If you want to start fresh, just flash a factory image of your choice (I advise the latest)
Follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Backup your datas first...
Don't flash userdata partition if your phone is not a 32GB model...
Also, don't mess with your phone unless you read enough and know what you are doing otherwise you could break it for good...
i was able to install it and get the gapps running
the problem is it didnt fix anything
i still cant really work the dialup unless it is via bluetooth. (am forced to reboot to be able to use the phone during a call)
my front facing camera still does not work.
5.1 said:
Well, the question is:
Honestly... Did you ever read the PureNexus thread?
Check this post for a detailed install (Google apps links in first post):
https://forum.xda-developers.com/showpost.php?p=61653759&postcount=4
If you want to start fresh, just flash a factory image of your choice (I advise the latest)
Follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Backup your datas first...
Don't flash userdata partition if your phone is not a 32GB model...
Also, don't mess with your phone unless you read enough and know what you are doing otherwise you could break it for good...
Click to expand...
Click to collapse
Hi... I'm currently using PureNexus myself and never encountered such problems... I guess you'll have to report your issues in the PureNexus thread with proper logs...
5.1 said:
Hi... I'm currently using PureNexus myself and never encountered such problems... I guess you'll have to report your issues in the PureNexus thread with proper logs...
Click to expand...
Click to collapse
Follow the guide posted above to get it back to stock. There shouldn't be a calling issue on that rom. Must be something janky during the flash process. Just get back your phone e to stock and see if everything works.
kaiotes said:
I have been experiencing certain issues w my phone and decided to do a factory reset.
Originally i was getting the TWRP loop when my celluar phone provider was trying to push an update.
Well after doing the factory reset, it went into TWRP. I"m not sure why, but that's where I am. I currently do not have an OS installed.I tried downloading a purenexus_shamu-7.1.1-20170215-OFFICIAL rom through some thread that I read, hoping to get a rom installed (excuse my terminology)
The system updated the partition, flashed itself, but still boots into TWRP.
I was at times able to get into the Pure rom? But then it had no apps. not even google play for me to use to download more apps.
Can someone pls provide a step by step of what to do to get me back up and running and disable this TWRP program permanently?
Thank you.
Click to expand...
Click to collapse
Ya forgot your gapps...
Please read more... Flash less... Don't be a dummy... It's expensive... And it's supposed to be a phone
Cant flash Super SU or Any rom as it goes into bootloop.
I have been following the procedure quite thoroughly .
Need Help ..
aka70698 said:
Cant flash Super SU or Any rom as it goes into bootloop.
I have been following the procedure quite thoroughly .
Need Help ..
Click to expand...
Click to collapse
So, TWRP is properly installed?
What kind of errors do you receive?
Unleashed by ONEPLUS 3T rooted
no error it just stucks...everything installs without any error
aka70698 said:
no error it just stucks...everything installs without any error
Click to expand...
Click to collapse
Sounds like you forgot to format the data partition between ROM swap, or flashed ROM for wrong Oneplus device.
Agreed, you probably didn't wipe data.
Miracles don't really exist in Android land. It works for everyone else.
Mate, we need more information;
What ROM's have you tried flashing it over?
Anything you've flashed recently?
Have you tried flashing Magisk or another SuperU method?
Have you tried a clean flash, without GAPPS or other bloat, and simply just flashing the package and the ROM?
Have you tried wiping your entire storage and then flashing?
aka70698 said:
Cant flash Super SU or Any rom as it goes into bootloop.
I have been following the procedure quite thoroughly .
Click to expand...
Click to collapse
Posting that you "followed the procedure quite thoroughly" doesn't' tell us anything, if you don't actually describe what you did.
Similar to another response, I'm wondering if you did a clear flash (default wipe in TWRP) before flashing a ROM. For that matter (like another asked) what ROMs did you try specifically. Or what version TWRP or version SuperSU?
Using old versions of TWRP or SuperSU is a really common mistake, and will lead to boot loops, or no boot. Folks will often assume they are using the "right version" and then when you ask for more info, it turn out they are using something totally obsolete, old guide, etc.
Good rule of thumb: when asking for help, provide as much detail as possible. Exact steps taken (step by step, in chronological order), with file names and version numbers. Asking for help, with a post consisting of 2 or 3 sentences, is never going to be enough.