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.
Related
Hello All;
I have decided to try and male my HP touch pad an Android only touch pad.
I need help though as i am a novice at best.
I am looking for help on the files i will need. Want to install CM 10 recent and CWM.
Do i need a boot loader or will that be in the ROM?
And what other files will i need?
i am assuming i need a ROM, Recovery, and GAPPS. Other than that i am not sure.
Found someone on the WebOS Nation who is willing to help so i dont want to go into this like and idiot, i want to have my ducks in a row.
Any help will be appreciated
thanks
This is a good guide: http://forum.xda-developers.com/showthread.php?t=2147284. As for Android-only, I don't recommend it. WebOS has gotten me out of Android trouble before.
Install Android only
bananagranola said:
This is a good guide: http://forum.xda-developers.com/showthread.php?t=2147284. As for Android-only, I don't recommend it. WebOS has gotten me out of Android trouble before.
Click to expand...
Click to collapse
Good point, Hey let me ask you something.
I like flashing ROMs but I always end up with a mess. Moboot, i dont think updates as grub2 does. So, i have thought the best way to switch ROMs would be treating the ROM as a first install, does that make sense and do you agree?
Or do you know a method to change ROMs that works well for you?
geomonroe said:
Good point, Hey let me ask you something.
I like flashing ROMs but I always end up with a mess. Moboot, i dont think updates as grub2 does. So, i have thought the best way to switch ROMs would be treating the ROM as a first install, does that make sense and do you agree?
Or do you know a method to change ROMs that works well for you?
Click to expand...
Click to collapse
Android doesn't update the way Linux does, it only updates apps; the bootloader isn't going to update neatly from a package manager. At the same time, updating the TP's bootloader (moboot) is usually unnecessary. On the other hand I usually like to keep my recovery (TWRP/CWM) up to date. When I switch ROMs I just wipe and flash from recovery. Never had a problem.
Install Android only
bananagranola said:
Android doesn't update the way Linux does, it only updates apps; the bootloader isn't going to update neatly from a package manager. At the same time, updating the TP's bootloader (moboot) is usually unnecessary. On the other hand I usually like to keep my recovery (TWRP/CWM) up to date. When I switch ROMs I just wipe and flash from recovery. Never had a problem.
Click to expand...
Click to collapse
I wander what i am doing wrong? i had skizoid and wanted to go back to cyanogenmod. followed the rules for flashing a rom and at the bootloader i had an entry still on the list for skiziod and the cyanogen entry, when i clicked the cyan entry i got the eternal loading screen.
geomonroe said:
I wander what i am doing wrong? i had skizoid and wanted to go back to cyanogenmod. followed the rules for flashing a rom and at the bootloader i had an entry still on the list for skiziod and the cyanogen entry, when i clicked the cyan entry i got the eternal loading screen.
Click to expand...
Click to collapse
What rules are you following? Full wipe? Leaving extra stuff in moboot is normal. You can delete the extras if they really bother you.
wipe cache and dalvik and factory reset
geomonroe said:
wipe cache and dalvik and factory reset
Click to expand...
Click to collapse
You should wipe system as well and if the extra uimage is still there you can delete it using a file manager after booting
4catalyst2cI said:
You should wipe system as well and if the extra uimage is still there you can delete it using a file manager after booting
Click to expand...
Click to collapse
As far as I know, most ROM install scripts automatically wipe system for you. Can't hurt to try, though.
Thankfully I have this zip again thanks to sstar posting it the other day. This zip will wipe your ulmage clean. Just flash it as you would a rom, than flash rom and gapps after.
https://copy.com/3F9kE
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! Just had a question, might even be a stupid question, but curiosity is a thing. What exactly happens if you flash wrong gapps for your device? I don't mean Android version, I mean for a different CPU architecture? Like, if I were to flash gapps for arm64 or x86 on my Nexus 6 that is actually arm? Does it just not boot and can be restored easy? Or is that a much more in depth fix? Just curious. Thanks guys!
H4X0R46 said:
Hello! Just had a question, might even be a stupid question, but curiosity is a thing. What exactly happens if you flash wrong gapps for your device? I don't mean Android version, I mean for a different CPU architecture? Like, if I were to flash gapps for arm64 or x86 on my Nexus 6 that is actually arm? Does it just not boot and can be restored easy? Or is that a much more in depth fix? Just curious. Thanks guys!
Click to expand...
Click to collapse
If the gapps package is the incorrect version it should run an installation check of your ROM version and fail to flash. In the event that it doesn't contain this check and the packages are installed, it would be a lot like installing a debian package in an rpm environment--it just won't work. Whether this means getting stuck at the boot screen because it is trying to access apps that aren't there or if it actually boots seeing force closes when you attempt to access the installed packages.
It just depends on whether you clean flashed, dirty flashed, what package you tried to install, what services try to run, etc etc etc.
AlkaliV2 said:
If the gapps package is the incorrect version it should run an installation check of your ROM version and fail to flash. In the event that it doesn't contain this check and the packages are installed, it would be a lot like installing a debian package in an rpm environment--it just won't work. Whether this means getting stuck at the boot screen because it is trying to access apps that aren't there or if it actually boots seeing force closes when you attempt to access the installed packages.
It just depends on whether you clean flashed, dirty flashed, what package you tried to install, what services try to run, etc etc etc.
Click to expand...
Click to collapse
Oh alright! So worst case scenario, just soft brick and can be easily recovered with a nandroid or a fastboot flash? Nothing beyond that?
H4X0R46 said:
Oh alright! So worst case scenario, just soft brick and can be easily recovered with a nandroid or a fastboot flash? Nothing beyond that?
Click to expand...
Click to collapse
It's no worse or better than just flashing ROMs over top of other ROMs because it is only installing files to the system partition. Wiping system undoes any wrongfully flashed Gapps or mods.
AlkaliV2 said:
It's no worse or better than just flashing ROMs over top of other ROMs because it is only installing files to the system partition. Wiping system undoes any wrongfully flashed Gapps or mods.
Click to expand...
Click to collapse
Cool dude thanks! It's these simple little curiosity questions that we over look and never try ourselves just in case it's a huge mistake! haha thanks again!
H4X0R46 said:
Hello! Just had a question, might even be a stupid question, but curiosity is a thing. What exactly happens if you flash wrong gapps for your device? I don't mean Android version, I mean for a different CPU architecture? Like, if I were to flash gapps for arm64 or x86 on my Nexus 6 that is actually arm? Does it just not boot and can be restored easy? Or is that a much more in depth fix? Just curious. Thanks guys!
Click to expand...
Click to collapse
Earth would implode then plummet into the Sun. Twice.
But really nothing worse than what can occur during development. Either bootloop, or endless FCs, that you can't acknowledge as fast as the system is throwing them at you. I've tried all. So you boot to bootloader, flash your system again, then boot to recovery, and flash the good gapps this time.
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
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.