Noob needs major help. TWRP Bootloop Unable to Factory Install - Nexus 6 Q&A, Help & Troubleshooting

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

Related

TWRP 2.6.3.0 constantly crashing (SOLVED)

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:

[HELP!] Weird Keyboard Bug

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:

[Q] HELPPP Accidental internal storage wipe

ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
raynefr said:
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Click to expand...
Click to collapse
Do you still have the memory issue? If so, try running a RUU, and see if that fixes your problem.
If not, just use adb sideload to sideload a ROM. Then wipe everything except internal storage and install the ROM normally.
EDIT: Looks like @BD619 ninja'd me XD
BTW sideload very rarely works when you wipe your sdcard.
BD619 said:
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
Click to expand...
Click to collapse
hey thanks for the reply. i followed the guide and after some effort, everything seemed good, but when i was trying to load 5.03 sense 6 rom, i got to the htc start up, then it defaulted back to the bootloader..i went with the deodex version of the download, should i try the odex? or a different version all together?
and now it doesnt want to boot into recovery mode either! going to try redoing the steps, but i just cant figure out what the problem is
**edit* i cant fix twrp. the title loads, but thats it. endless loop
ok i got it to seemingly work. restoring content now. sat in fron of my pc for 15 hours...not even sure where imat or if i got any closer to rooting..smh..thank you everyone who helped. if anyone comes across this
to get out of the endless cycle of recover/loading screen.. delete your twrp, or whatevs your using. even if you have the latest, just redownload it. worked for me. i guess there is a huge difference between the odex and the deodex.i had figured deodex was a more refined version, but maybe it had more complicated software. in any case, if you are at a point where you dont have a base os, and you make it this far, go with odex, it worked for me. htc is big on back up, so i was more worried about having to scrap my phone then i was regaining data, especially with most of my stuff backed up to google drive. hopefully you guys are careful.
now...about this backup issue i had in the first place. how can i fix the storage issue? i have a 32 gb phone minus partition leaves me with over 24gb..why is it going based off the separate phonememory slot? why cant i change it?

Help flashing CM

I screwed up somehow. Maybe things changed since I last messed around with Android phones. I went into twrp and did a factory reset then installed latest nightly and these gapps ( https://github.com/cgapps/vendor_google/tree/builds/arm > gapps-5.1-arm-2015-07-17-13-29.zip), were they the right gapps? . Now phone won't boot or go into recovery mode so can't go back to my stock nandroid. I'll try going back to stock using wugys toolkit :/
Edit: I used the toolkit to flash stock + unroot option without wiping data but it finished too fast somehow and the options in bootloader were fixed. I booted up phone and now CM booting up. What did I do wrong and how did I fix it? I'm really confused and would appreciate some help.
3bs11 said:
I screwed up somehow. Maybe things changed since I last messed around with Android phones. I went into twrp and did a factory reset then installed latest nightly and these gapps ( https://github.com/cgapps/vendor_google/tree/builds/arm > gapps-5.1-arm-2015-07-17-13-29.zip), were they the right gapps? . Now phone won't boot or go into recovery mode so can't go back to my stock nandroid. I'll try going back to stock using wugys toolkit :/
Edit: I used the toolkit to flash stock + unroot option without wiping data but it finished too fast somehow and the options in bootloader were fixed. I booted up phone and now CM booting up. What did I do wrong and how did I fix it? I'm really confused and would appreciate some help.
Click to expand...
Click to collapse
my guess would be the gapps, mainly because i have never heard of the one you used.
perhaps, try a more notable one, like tk, slim, or banks.
bweN diorD said:
my guess would be the gapps, mainly because i have never heard of the one you used.
perhaps, try a more notable one, like tk, slim, or banks.
Click to expand...
Click to collapse
I'll try that if my current setup fails me but why would gapps mess up the recovery? The buttons in bootloader kinda changed to just small text as well and the text under it which had the device details changed but I didn't make note of the changes.
I got the gapps link from the cm page. I guess it might be outdated but that's kind of their fault for not updating in their OP.
3bs11 said:
I'll try that if my current setup fails me but why would gapps mess up the recovery? The buttons in bootloader kinda changed to just small text as well and the text under it which had the device details changed but I didn't make note of the changes.
I got the gapps link from the cm page. I guess it might be outdated but that's kind of their fault for not updating in their OP.
Click to expand...
Click to collapse
i cant explain it sorry.
gapps is usually the weak link then there are issues.

How to Restore Internal SD DATA without DATA LOSS & FACTORY RESET ?

EDIT
You just have to know, that there are some ways to restore everything
In my Case I had Bootloader unlocked already (ofcourse)
And I just was stuck on the TWRP Part... I never knew that was soo easy, but you just have to do it properly.
I will make an extra Tutorial now, because it will save many people from going insane
Because of this I didn't sleep for 40 Hours now already, because I was deeply shocked and some very very nice Pictures and important Communications would be gone... and much work in Optimization etc. etc.
Yes!
Link will follow here!
Here you go for the Solution!
https://forum.xda-developers.com/galaxy-s10/how-to/proper-to-root-s10-device-twrp-s10-10e-t4015813
_________
Hi,
I just tryed to update from beyond rom 5.2 to 5.8 and so I flashed it...
Then I got a Bootloop, because I didn't updated TWRP before.. so I got into my TWRP and flashed TWRP...
But after that I could not got into TWRP anymore, maybe because I forgot to add multidisabler..
So I flashed stock rom...
However Iam now stuck... I have important Data on the Internal SD and also the backup,
But I only come to the points where it asks me to delete all my data.
Is there any way possible to get the data?
Install TWRP somehow or get to a system?
Please suggest whats possible?
It's an emergency...
Hope you can help me & all who have this problem one day.
Best regards
I can only get to standart recovery, normal firmware & system doesn't boot - Bootloop...
I tryd to flash older firmware (ASH1, ASG8 & newer ASK1), but it doesn't boot system, always ask to factory reset and so on....
really ****ed up...
I hope there is another Way, then directly extract the data from the memory component... wich would be very expensive...
https://www.youtube.com/watch?v=nXDUhhyY2rE
basically the new flashed standart rom erases itself after first start, probably because it detects, that the system was modified before (beyond rom) then it reboots itself and there is no system anymore to boot, then it goes in a kind of pre recovery with the option to reboot, factory reset (including all data!) or reading a log...
DAMN I SHOULD BACKUP EVERYTHING ON PC... ALWAYS!
Still I really want to find a solution and I hope some pro can help on the S10.
No Solution for this.... it seems.
Omg i found the solution and got everything back
yes!!!! Great stuff
||||| said:
Omg i found the solution and got everything back
yes!!!! Great stuff
Click to expand...
Click to collapse
Happy to hear you solved... But after reading your other thread and after all of this excitement i still don't get how you solved the problem.... can you specify it?

Categories

Resources