Did i brick my phone? - Nexus 5 Q&A, Help & Troubleshooting

Hello, i recently installed the new official lollipop 5.0 android, however it was working like crap so i decided to change with custom firmware.
Heres what i did.
Unlock bootloader
install custom recovery
root with super SU
install custom rom.
It worked, and android started up, however, i cant connect to cellular network anymore, i waited like 10 minute to detect it but it wont, then i tried a different rom, didnt help. Did i bricked my phone? Is there anything to do?
Im with Virgin canada
Thanks

Can you access the bootloader? If yes, then you did not brick it. You probably didn't completely wipe the stock ROM before you flashed the custom one. Also, not a good idea to flash SuperSU before flashing your ROM.

Everything is working has usual, except i cant connect to LTE anymore. I flashed TWRP instead of Clockwork recovery, ill try again with this one...

From where you are now with TWRP installed:
1. In TWRP, go to "Wipe" then go into the advanced wipe options and wipe every partition except the internal storage.
2. Flash ROM.
3. Flash Gapps if needed.

Google "APN"

theesotericone said:
Google "APN"
Click to expand...
Click to collapse
From what ive seen, i have to set it up myself?
Also i currently has no ROM installed, and none in my SD card, i tried sideload but it failed, is there a way to transfert the ROM to my memory card in TWRP? If i have to click USB-OTG for it, then nothing happen when i do.

insistents said:
From what ive seen, i have to set it up myself?
Also i currently has no ROM installed, and none in my SD card, i tried sideload but it failed, is there a way to transfert the ROM to my memory card in TWRP? If i have to click USB-OTG for it, then nothing happen when i do.
Click to expand...
Click to collapse
Push the ROM zip file to your phone from within TWRP, don't sideload it. You shouldn't even need to do that though. TWRP now supports MTP so your internal storage should appear when you connect the phone to the PC when you're in TWRP.

So you went from having possible APN issues to completely wiping your device? Slow down before you actually do brick it. Read the stickies. All the info you need is already here.

Brushstroke said:
Push the ROM zip file to your phone from within TWRP, don't sideload it. You shouldn't even need to do that though. TWRP now supports MTP so your internal storage should appear when you connect the phone to the PC when you're in TWRP.
Click to expand...
Click to collapse
-snip
Had to turn off MTP

theesotericone said:
So you went from having possible APN issues to completely wiping your device? Slow down before you actually do brick it. Read the stickies. All the info you need is already here.
Click to expand...
Click to collapse
I followed the stickies, im not sure what i could have missed.

insistents said:
I tried "adb push rom.zip /sdcard/"
but it say
error: device not found
Click to expand...
Click to collapse
Nevermind.

insistents said:
Hello, i recently installed the new official lollipop 5.0 android, however it was working like crap so i decided to change with custom firmware.
Heres what i did.
Unlock bootloader
install custom recovery
root with super SU
install custom rom.
It worked, and android started up, however, i cant connect to cellular network anymore, i waited like 10 minute to detect it but it wont, then i tried a different rom, didnt help. Did i bricked my phone? Is there anything to do?
Im with Virgin canada
Thanks
Click to expand...
Click to collapse
Try wiping your cache in TWRP.

Brushstroke said:
My bad. TWRP, as far as I can tell, only allows sideloading as far as ADB commands are concerned. Can you not mount the SD using the Mount option in TWRP?
Click to expand...
Click to collapse
I managed to push files by disabling MTP
However, im still waiting on that colour dot loading screen...

insistents said:
I managed to push files by disabling MTP
However, im still waiting on that colour dot loading screen...
Click to expand...
Click to collapse
Which screen are you referring to?

Brushstroke said:
Which screen are you referring to?
Click to expand...
Click to collapse
Boot screen, where there are flying colour dot.
By the way, i only have managed to enter TWRP recovery once, for all the other time, there only was the Teamwin picture, then it reboot to android each times...

insistents said:
Boot screen, where there are flying colour dot.
By the way, i have to do "fastboot flash recovery recovery.img" each time if i want to acess TWRP
Otherwise it wont work, when i go to recovery mode, i can see the TeamWin picture appear for a few second, then the phone reboot to android.
Click to expand...
Click to collapse
Well, did you flash a ROM or factory image? Earlier you said there was no ROM installed.
And about that TWRP issue...not too sure. That could be the recovery_from_boot.p file restoring the stock recovery. Are you seeing an android with a red exclamation point?

Brushstroke said:
Well, did you flash a ROM or factory image? Earlier you said there was no ROM installed.
And about that TWRP issue...not too sure. That could be the recovery_from_boot.p file restoring the stock recovery. Are you seeing an android with a red exclamation point?
Click to expand...
Click to collapse
There was none earlier untill i managed to push a rom in the memory card, but now the Rom just wont start, its stuck in the boot screen so i will try a different ROM.
Nope no red exclamation point, when i choose recovery mode, the Google boot screen appear, then the Teamwin logo appear for a few second, then screen goes black and then google logo is back, and finnaly android boot up...

Ah well i think i fixed the recovery, i used an older version and now its starting properly.

insistents said:
There was none earlier untill i managed to push a rom in the memory card, but now the Rom just wont start, its stuck in the boot screen so i will try a different ROM.
Nope no red exclamation point, when i choose recovery mode, the Google boot screen appear, then the Teamwin logo appear for a few second, then screen goes black and then google logo is back, and finnaly android boot up...
Click to expand...
Click to collapse
Which ROM is this? And since you've already wiped the SD card once and the ROM won't boot, why not just flash the factory image so you'll have a clean slate to start with?

Factory image = Official firmware?

Related

no os issue

so my bro rebooted out of recovery (twrp) after wiping system and not flashing anything and now im stuck on splash screen. im screwed aren't I. edit: I can still boot into recovery... not sure if that will help! also I currently have no backups or rom to flash on the device ;( anyway to get adb sideload to work!? I use and it says device not found
Stryker1297 said:
so my bro rebooted out of recovery (twrp) after wiping system and not flashing anything and now im stuck on splash screen. im screwed aren't I. edit: I can still boot into recovery... not sure if that will help! also I currently have no backups or rom to flash on the device ;( anyway to get adb sideload to work!? I use and it says device not found
Click to expand...
Click to collapse
nvm I used my pc's device manager to work adb
I did something stupid like this yesterday. If you have a recent enough TWRP, you can use the Advanced-> sideload app option with adb to download a rom to where you can install it using twrp.
Stryker1297 said:
so my bro rebooted out of recovery (twrp) after wiping system and not flashing anything and now im stuck on splash screen. im screwed aren't I. edit: I can still boot into recovery... not sure if that will help! also I currently have no backups or rom to flash on the device ;( anyway to get adb sideload to work!? I use and it says device not found
Click to expand...
Click to collapse
All you have to do is put the rom zip on your micro sd card, then TURN OFF your device. Now boot into twrp then select install by browse to the micro sdcard to select the rom zip file.
buhohitr said:
All you have to do is put the rom zip on your micro sd card, then TURN OFF your device. Now boot into twrp then select install by browse to the micro sdcard to select the rom zip file.
Click to expand...
Click to collapse
I had a very similar 'No OS' problem and I wasn't sure if I would be able to reboot into recovery but thank you for answering my question!

Phone Won't Turn On; Soft Keys Flashing When Buttons Are Pressed

Hi all,
So, last night I successfully rooted and unlocked my One X on AT&T. Today, I tried putting a ROM on it. I flashed the boot.img first, then tried to install the ROM (Jelly Bean Sense). It failed for some reason, so I wiped and rebooted my phone.
Instead of going back to the stock ROM, the phone now will not turn on, is not recognized on both laptops I tried, and does not recognize even being charged. The only thing that happens is when I press down the power button, all of the soft keys illuminate and flash until I stop holding it. I've managed to get into the bootloader screen once, but the phone reset itself before I could do anything.
The only screen I can get to with the Vol Down+Power combo is the HTC Screen, but it's the one that shows before my custom recovery, with some warning from HTC in red letters at the bottom.
At this point, I just want a phone that works. This is a lot more complex [for me] than rooting and flashing a ROM to the Inspire I had for some reason. I fly out for vacation in two days for a few weeks, so I'd like to be able to avoid having to send this thing back to HTC or AT&T if possible.
ANY help is greatly appreciated.
If it's easier, feel free to Skype chat me.
Thanks!
Im confused.. it won't come on, but you can get to recovery? If you can manually boot into twrp you'll be fine.. may I ask which Rom you flashed? Did you flash the boot.img first? Or after you flashed Rom? Alot of guys will say flash boot.img first.. I don't have that funky hboot but I have to do my cousins alot and his will only boot correctly if I flash Rom first, then boot into bootloader and fastboot the boot.img.
Try that and let me know how it goes
Also... Let go of all the buttons when you see the white screen lol. That means you found bootloader
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Im confused.. it won't come on, but you can get to recovery? If you can manually boot into twrp you'll be fine.. may I ask which Rom you flashed? Did you flash the boot.img first? Or after you flashed Rom? Alot of guys will say flash boot.img first.. I don't have that funky hboot but I have to do my cousins alot and his will only boot correctly if I flash Rom first, then boot into bootloader and fastboot the boot.img.
Try that and let me know how it goes
Also... Let go of all the buttons when you see the white screen lol. That means you found bootloader
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I can get it to boot into the Bootloader screen and the TWRP now just fine, but that's as far as it will go. The internal SD will not mount with TWRP either now.
Here's the ROM I tried to flash: http://forum.xda-developers.com/showthread.php?t=2055490
I put it on my SD card, then extracted the boot.img to the folder I have my dab/fastboot files in, then flashed the boot.img, then tried to flash the ROM.
If I can get it working again, I'll try to do it in reverse order next time and see if that works. Still trying to find a way to get a ROM on here with my Mac, and to make my SD card work again. Everything on it is backed up so it's ok if I need to wipe it.
If you can get to bootloader, you're not bricked. It's just a matter of flashing the right stuff in the right order.
It could be that your sdcard is corrupted. Factory reset from bootloader will do it, but fixing it just a matter of formatting it again. Can you mount it on your computer? What happens when you plug into your PC?
Your sdcard is corrupt. No big deal but you'll lose everything. Plug it in into computer and locate the storage and try to find a way to format it. Sorry, I have no clue with a mac I swore off apple products :thumbup:
Anyway, you seem to know the ropes for the most part. If you can format, drag Rom onto SD. Wipe everything in twrp. Cache, dalvick, factory reset, system. Flash Rom.. immediately boot into bootloader and fastboot the boot.img. choose reboot from bootloader. Good luck!
Sent from my HTC One XL using Tapatalk 2
Yep, I also suggest doing a factory reset from the bootloader ( which will erase your internal storage) but at least you'll be able to mount your SD card, put a ROM on it and flash it. I would highly recommended you to flash viper 3.0.0, you don't need to flash the boot.img and its pretty much stock JB with some tweaks.
Sent from my HTC One XL using Tapatalk 2
I am having this same problem (minus the custom screen).
My phone will boot into TWRP and all, but it won't mount (PC says the disk needs to be formatted before it can be used). When I go to reboot or anything from TWRP, it tells me there is no OS installed and am I sure.
Can anyone help?
That's good news!
I tried doing a factory reset from bootloader, but nothing happened. Maybe because the SD card won't mount?
I only have a Mac, with no PC in sight. It doesn't show up at all on here. Fastboot USB, or when I mount it as USB in TWRP. It does however show up as a device in recovery in terminal. But nothing on the desktop. Apple+Android do not mix well!
I'm ok with losing my data, what I'm not OK with is having to use this pink Razr while my nice phone is broken :'(
Thanks for all the help so far!
I do a factory reset from bootloader, it takes me into TWRP. Now is the only time it will even remotely show up on my laptop, and even then it's only via terminal when I do adb devices. Since it can't mount for some reason, is there a way to reformat via Terminal, and maybe even push the ROM to my phone from there? That's something I'm not familiar with.
elijahpr said:
I do a factory reset from bootloader, it takes me into TWRP. Now is the only time it will even remotely show up on my laptop, and even then it's only via terminal when I do adb devices. Since it can't mount for some reason, is there a way to reformat via Terminal, and maybe even push the ROM to my phone from there? That's something I'm not familiar with.
Click to expand...
Click to collapse
Format your sd..drag Rom..wipe..flash..enjoy
omario8484 said:
Format your sd..drag Rom..wipe..flash..enjoy
Click to expand...
Click to collapse
I can't format because it doesn't show up on my computer, and doing so in bootloader takes me to TWRP.
emylibef said:
I am having this same problem (minus the custom screen).
My phone will boot into TWRP and all, but it won't mount (PC says the disk needs to be formatted before it can be used). When I go to reboot or anything from TWRP, it tells me there is no OS installed and am I sure.
Can anyone help?
Click to expand...
Click to collapse
Hey dude, I followed their advice (dug out my XP machine) and now my SD card is re-formatted.
Get into the bootloader screen, hit factory reset. (When I did this on mine, it took me right to TWRP)
From there, I mounted as USB and it showed up as needing to be reformatted on my XP machine. Took a few minutes to do on this dinosaur, but it worked, cause everything is gone!
Right now I'm in the process of zipping up the Viper XL ROM (thanks for the recommendation barondebxl, it looks awesome!), which I'll put onto my SD card and wipe/flash from there. (on my Mac now).
Hopefully it works!
I'm unable to flash ROMs for some reason. It doesn't give an error, just says that it failed. Any ideas?
elijahpr said:
Get into the bootloader screen, hit factory reset.
Click to expand...
Click to collapse
No no no. This is what is corrupting your sdcard. Only do a factory reset in TWRP or once booted up. Start over and format again. Then copy over your rom.
When you and a few others mentioned doing it, what were you referring to?
I've tried three different ROMs now, and each fails without saying why in TWRP.
Problem solved! Got the stock RUU back on there and it works perfectly. Just re-rooted and unlocked again. Round two..

Cannot Flash anything!

Alright, so, my tablet decided to one day just cease stop working. The recovery for some reason can't flash anything now, is used to be able to flash a backup, but not anymore. It used to be able to boot past the animation, but not anymore. I cannot flash a ROM from recovery because it says that the file is bad (and please, don't tell me to check to see if the md5's are correct, they are, I've triple checked.) I've flashed CWM recovery and TWRP recovery, and TWRP cannot fix permissions, but CWM recovery can, but neither can flash a single ROM. I've tried sideloading a rom but i get this error from the CMD window
Code:
* failed to write data 'protocol fault (no status)' *
. I'm at my wits end here. The bootloader is perfectly fine, it works 100% but I can't flash a single thing from recovery. I've flashed non-corrupted recoveries, and still I cannot flash a thing.
You have flashed the latest TWRP via fastboot and it still wont flash roms? Also, what bootloader are you on?
Sent from my ASUS Transformer Pad TF700T Infinity using Tapatalk HD
Rom: CleanRom 3.4.4
Phultara said:
Alright, so, my tablet decided to one day just cease stop working. The recovery for some reason can't flash anything now, it used to be able to flash a backup, but not anymore. It used to be able to boot past the animation, but not anymore. I cannot flash a ROM from recovery because it says that the file is bad (and please, don't tell me to check to see if the md5's are correct, they are, I've triple checked.) I've flashed CWM recovery and TWRP recovery, and TWRP cannot fix permissions, but CWM recovery can, but neither can flash a single ROM. I've tried sideloading a rom but i get this error from the CMD window
Code:
* failed to write data 'protocol fault (no status)' *
. I'm at my wits end here. The bootloader is perfectly fine, it works 100% but I can't flash a single thing from recovery. I've flashed non-corrupted recoveries, and still I cannot flash a thing.
Click to expand...
Click to collapse
What tablet do you have?
From where did you download which recovery for which Asus tablet.
Sounds like the recovery version doesn't match the device.
Thats OK said:
What tablet do you have?
From where did you download which recovery for which Asus tablet.
Sounds like the recovery version doesn't match the device.
Click to expand...
Click to collapse
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Phultara said:
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Click to expand...
Click to collapse
Have you ever unlocked the bootloader? (If not: do so by searching on Asus' site for the Unlock Bootloader Tool v7) It's a simple apk which you install and then check and let it unlock.
Only then, you can start flashing!
If you already have unlocked, maybe you sent it in (?) Or flashed an official Asus rom (?), you might want to unlock it again.
Let us know if any of these answers above helped
Phultara said:
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Click to expand...
Click to collapse
If you have the 4 icons that indicates JB.
Sounds like the custom recovery is not installed if your on the RCK icon and press the up volume rocker and nothing happens.
adelancker said:
Have you ever unlocked the bootloader? (If not: do so by searching on Asus' site for the Unlock Bootloader Tool v7) It's a simple apk which you install and then check and let it unlock.
Only then, you can start flashing!
If you already have unlocked, maybe you sent it in (?) Or flashed an official Asus rom (?), you might want to unlock it again.
Let us know if any of these answers above helped
Click to expand...
Click to collapse
Unlocking it would require an OS to be installed, but none is installed because I was wiping to install a different ROM. I have unlocked it. In response to the boot loader, yes, it has 4 icons. So I guess it is the JB boot loader. When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Phultara said:
When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Click to expand...
Click to collapse
Can you get adb shell access to your recovery?
Which ZIP are you actually trying to flash? What is the exact error message from the recovery? Try running md5sum (inside the adb shell) on the file you want to flash. Check the output of "mount". Check if /cache/recovery/log contains interesting info.
Phultara said:
Unlocking it would require an OS to be installed, but none is installed because I was wiping to install a different ROM. I have unlocked it. In response to the boot loader, yes, it has 4 icons. So I guess it is the JB boot loader. When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Click to expand...
Click to collapse
AH sorry!
I only read the title and replied lol
Does adb do anything?
Or is adb not working either?
adelancker said:
AH sorry!
I only read the title and replied lol
Does adb do anything?
Or is adb not working either?
Click to expand...
Click to collapse
How would I go about connecting through ADB?
Phultara said:
How would I go about connecting through ADB?
Click to expand...
Click to collapse
* Connect your tablet to a computer with proper drivers and adb installed.
* Boot tablet to recovery.
* On computer, type "adb shell".
_that said:
* Connect your tablet to a computer with proper drivers and adb installed.
* Boot tablet to recovery.
* On computer, type "adb shell".
Click to expand...
Click to collapse
Alright, I'll have to try that when I get home in about 3-4 hours. I'll get back to you on that. Also, I noticed last night that when I was on fast boot, it would stay stuck as waiting for device on the cmd window. I'm not sure if it was my computer that didn't detect it or a new symptom. O hope its just a fluke!
Alright, here's the log from my recovery.
Phultara said:
Alright, here's the log from my recovery.
Click to expand...
Click to collapse
OK, I assumed that you're not using data2sd. 1. Make sure your microsdcard is good (reformat and recopy your backup or rom if needed),2. Boot into twrp and wipe cache, dalvik cache, factory reset, wipe system, wipe internal then finally the most important part, FORMAT SDCARD. Now reflash a new rom or try to restore from backup. I would try step#2 first. Good luck.
EDIT: format sdcard instead of wipe sdcard.
buhohitr said:
OK, I assumed that you're not using data2sd. 1. Make sure your microsdcard is good (reformat and recopy your backup or rom if needed),2. Boot into twrp and wipe cache, dalvik cache, factory reset, wipe system, wipe internal then finally the most important part, FORMAT SDCARD. Now reflash a new rom or try to restore from backup. I would try step#2 first. Good luck.
EDIT: format sdcard instead of wipe sdcard.
Click to expand...
Click to collapse
That did it!!! Thank you!!!! Looks like it was the SD that was the root of the issue! Thanks!!

[Q] Screen stuck when try to reboot

Hi,
Im trying to root my HTC ONE S. I followed all the steps that suggested in the forums, but when I reboot the phone in the final step, it got stuck in the 'HTC quietly brilliant' screen. I left it there for 20 min or so, it didn't change. I am able to go to the recovery mode but I don't know what to do. I did a factory reset attempting to go back to the original software but it didn't work either. Any ideas what can I do? Im in real trouble if Im not able to use my phone anymore.
Thanks in advance,
Angel
100315595 said:
Hi,
Im trying to root my HTC ONE S. I followed all the steps that suggested in the forums, but when I reboot the phone in the final step, it got stuck in the 'HTC quietly brilliant' screen. I left it there for 20 min or so, it didn't change. I am able to go to the recovery mode but I don't know what to do. I did a factory reset attempting to go back to the original software but it didn't work either. Any ideas what can I do? Im in real trouble if Im not able to use my phone anymore.
Thanks in advance,
Angel
Click to expand...
Click to collapse
Well if you are installing a custom ROM then there is no need to root before hand, you just need a custom recovery installed. The custom ROM will have root access enabled.
If you are asking how to just be rooted on a stock rom, then I would just google how to do it like you would. But I assume you install custom recovery, download a supersu.zip and install via recovery.
tivofool said:
Well if you are installing a custom ROM then there is no need to root before hand, you just need a custom recovery installed. The custom ROM will have root access enabled.
If you are asking how to just be rooted on a stock rom, then I would just google how to do it like you would. But I assume you install custom recovery, download a supersu.zip and install via recovery.
Click to expand...
Click to collapse
Hi, thank you for the reply
Well, I have no access to the sd card, it says it's not mounted. I can't copy any files to the phone, therefore I can't reinstall it from the phone. Sorry for my ignorance, but I don't know what to do next.
Thanks,
Angel
100315595 said:
Hi, thank you for the reply
Well, I have no access to the sd card, it says it's not mounted. I can't copy any files to the phone, therefore I can't reinstall it from the phone. Sorry for my ignorance, but I don't know what to do next.
Thanks,
Angel
Click to expand...
Click to collapse
seems to be a common that the sdcard can become corrupted.
If that is the case, having the stock recovery on and then booting the phone into bootloader and selecting "clear storage" fixes the issue.
Then you need to flash custom recovery again, and mount usb storage.
For the S4 Ville version of this phone and not the S3 VilleC2
stock recovery
https://dl.dropboxusercontent.com/u/84212943/ville_recovery_signed.img
tivofool said:
seems to be a common that the sdcard can become corrupted.
If that is the case, having the stock recovery on and then booting the phone into bootloader and selecting "clear storage" fixes the issue.
Then you need to flash custom recovery again, and mount usb storage.
For the S4 Ville version of this phone and not the S3 VilleC2
stock recovery
Hi,
I tried to do what you told me, but now I can´t even go into the recovery mode. I can only access the bootloader; anytime I select recovery mode it shows this (image below), after a few minutes it reboots and stays with the white screen ´HTE quietly brilliant´. I can´t copy any files either because the computer doesn´t read the sd card. Any ideas?
Thank you for your time.
Angel
Click to expand...
Click to collapse
100315595 said:
tivofool said:
seems to be a common that the sdcard can become corrupted.
If that is the case, having the stock recovery on and then booting the phone into bootloader and selecting "clear storage" fixes the issue.
Then you need to flash custom recovery again, and mount usb storage.
For the S4 Ville version of this phone and not the S3 VilleC2
stock recovery
Hi,
I tried to do what you told me, but now I can´t even go into the recovery mode. I can only access the bootloader; anytime I select recovery mode it shows this (image below), after a few minutes it reboots and stays with the white screen ´HTE quietly brilliant´. I can´t copy any files either because the computer doesn´t read the sd card. Any ideas?
Thank you for your time.
Angel
Click to expand...
Click to collapse
That is good, that is the stock recovery, basically saying you don't have access to it.
But you don't need to go into recovery, it is there just to fix the issue when you enter the bootloader and pick "clear storage"
So get back to the bootloader and clear storage. Then you will need to flash the recovery of your choice, CWM or TWRP. You should now be able to access usb storage. (unless you are using the special TWRP in the Maximus thread meant for hboot 2.16, then it just doesn't work)
Click to expand...
Click to collapse
Yes, it worked. Thank you.
But, which ROM should I install now? I tried with the SU, but the screen was stuck again. Do I need the phone in S-off mode? how do I do that? I saw that many ROM's need this.
Thank you again for your help, very appreciated
Angel
100315595 said:
Yes, it worked. Thank you.
But, which ROM should I install now? I tried with the SU, but the screen was stuck again. Do I need the phone in S-off mode? how do I do that? I saw that many ROM's need this.
Thank you again for your help, very appreciated
Angel
Click to expand...
Click to collapse
You are welcome.
You only need S-Off if the rom says 2.16 HBoot required.
So there are a lot of different ones to try. As long as your Hboot is 2.15, if not then you need to upgrade your firmware to that. You see your HBoot in the bootloader screen.
So ya, most of the roms are ok with S-on, you just have to remember to:
fastboot flash boot boot.img
So on your pc download the rom, unzip it you will see the boot.img move that to fastboot folder and fastboot flash it.
Then you can move the ROM.zip to your phone and install via recovery.
Don't forget to wipe caches before rebooting. (when installing, if that particular rom opens up Aroma installer and one of the options is to wipe, do that but don't wipe again when back to recovery)
The sense based roms are generally more stable and like stock.
The CyanogenMod may have a few little bugs.
Just browse around and see which one you like.
It all worked out pretty well.
I'm trying with the MagioRom, seems to be very stable!
Thank you for your help, you literally saved my HTC!
:good:

URGENT Google Pixel struck in bootloops, can't access recovery mode!

Ok so never mind i got into teamwin TWRP phew. But Alpha2 but isn't it suggested that you don't recover using twrp? I don't know what to DO.
silvernirvash said:
Ok so never mind i got into teamwin TWRP phew. But Alpha2 but isn't it suggested that you don't recover using twrp? I don't know what to DO.
Click to expand...
Click to collapse
Download TWRP RC1 and flash it with TWRP alpha. Then download PN and follow the flashing instructions OR use your PC to flash back to stock and start over.
Edit: if you've made a backup using TWRP alpha, you can try to restore it using TWRP alpha.
k.s.deviate said:
Download TWRP RC2 and flash it with TWRP alpha. Then download PN and follow the flashing instructions OR use your PC to flash back to stock and start over.
Edit: if you've made a backup using TWRP alpha, you can try to restore it using TWRP alpha.
Click to expand...
Click to collapse
I don't have ADB or USB debugging enabled on my device. I can't DO anything. And i go and mount my storage onto my PC it just shows a **** ton of folders with random letters and numbers. i can't copy any files onto the device nor will minimal ADB and fastboot work when i type adb devices to detect the device. i don't know what to do!
silvernirvash said:
I don't have ADB or USB debugging enabled on my device. I can't DO anything. And i go and mount my storage onto my PC it just shows a **** ton of folders with random letters and numbers. i can't copy any files onto the device nor will minimal ADB and fastboot work when i type adb devices to detect the device. i don't know what to do!
Click to expand...
Click to collapse
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?
k.s.deviate said:
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?
Click to expand...
Click to collapse
stock rooted with substratum installed. i had a substratum theme that worked for the most part perfectly fine but then i found orange kittens and the colored kittens addon to change the color to something i wanted people told me it would work just fine on the pixel 7.1 and when it rebooted BAM bootloop. i didn't have adb or usb debugging enabled when i did it and i wasn't thinking because i've done this kinda stuff in the past so i thought i'd be fine. but i guess i wans't.
k.s.deviate said:
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?
Click to expand...
Click to collapse
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?
also what is PN? i'm confused by that one.
silvernirvash said:
stock rooted with substratum installed. i had a substratum theme that worked for the most part perfectly fine but then i found orange kittens and the colored kittens addon to change the color to something i wanted people told me it would work just fine on the pixel 7.1 and when it rebooted BAM bootloop. i didn't have adb or usb debugging enabled when i did it and i wasn't thinking because i've done this kinda stuff in the past so i thought i'd be fine. but i guess i wans't.
Click to expand...
Click to collapse
ok, bootloop form theme. After TWRP has successfully decrypted, this might take a few reboots.. Go to sd card, you will see a folder named Substratum, in there are two zip files, flash the SubstratumRescue_Legacy.zip then reboot.
IF that does not work, go back into TWRP and go to mount - system. back out and go to advanced - file manager navigate to /system/vendor/overlay and delete the entire folder. Ive done that only once on the Pixel, you might have to go to /system/system/vendor/overlay and delete the folder then reboot.
silvernirvash said:
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?
Click to expand...
Click to collapse
That is interesting, my first experience with the Pixel I had bought it close to when Best Buy was closing (they were offering the $10.00/month promotion) and the device had not finished updating. However, the person checking me out let me go before it had completely finished and said it "will finish the updates shortly and be usable". Well, i guess in his haste to get blackout drunk and attempt lame pick up lines, he did something wrong. After the update finished, The phone was stuck in a constant boot loop. My first experience with my beloved Pixel was a nightmare. Of course, I had it replaced with a new one in the store the next day, but it was very strange. I had not even got into the OS at all and it was stuck in this strange bootloop.
Glad your situation worked out, when I saw the title to this post my heart sunk a little bit because I certainly know the look.
silvernirvash said:
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?
Click to expand...
Click to collapse
No, just read my post and see if that works.
k.s.deviate said:
ok, bootloop form theme. After TWRP has successfully decrypted, this might take a few reboots.. Go to sd card, you will see a folder named Substratum, in there are two zip files, flash the SubstratumRescue_Legacy.zip then reboot.
IF that does not work, go back into TWRP and go to mount - system. back out and go to advanced - file manager navigate to /system/vendor/overlay and delete the entire folder. Ive done that only once on the Pixel, you might have to go to /system/system/vendor/overlay and delete the folder then reboot.
Click to expand...
Click to collapse
ZOMG it rebooted! i already did a restore so i have to set up my phone again in terms of apps and stuff but that's fine. but now it keeps saying android.process.acore keeps stopping. i'm assuming it has to do with the substratum theme and i guess that means i should just delete that folder huh?
silvernirvash said:
ZOMG it rebooted! i already did a restore so i have to set up my phone again in terms of apps and stuff but that's fine. but now it keeps saying android.process.acore keeps stopping. i'm assuming it has to do with the substratum theme and i guess that means i should just delete that folder huh?
Click to expand...
Click to collapse
How did you restore? I've never seen that process stop before.
It might be best to (since you have to set up your apps again) flash a factory image and start over.
---------- Post added at 05:02 AM ---------- Previous post was at 04:56 AM ----------
And if your going to be playing with themes.. PN is the way to go. PN is Pure Nexus rom. Follow the instructions word for word and you won't have any troubles. It is as stable as stock with some extra goodness baked in.
k.s.deviate said:
How did you restore? I've never seen that process stop before.
It might be best to (since you have to set up your apps again) flash a factory image and start over.
Click to expand...
Click to collapse
oh i did a quick cache and data wipe. it's what you're supposed to do when flashing new or updated roms in the first place. at the top right of TWRP it says wipe. i thought that would restore it back to default settings including substratum theme application but it seems all it did was set me back to stock settings with apps uninstalled lol. gotta set up my device again sadly. but now like i said now i keep getting this stupid android.process..acore keeps crashing error.
and i restored using the legacy zip you told me to use in the substratum folder using the install option at the top left.
Just hit the thanks button. ?
and by recovering i lost root....great....now i need to reroot.....damn it all =w=;;
k.s.deviate said:
Just hit the thanks button.
Click to expand...
Click to collapse
oh hey can i download and flash the latest version of android 7.1.1 manually using TWRP with out losing TWPR or my locked bootloader? just curious. i'm about to go back and reroot but i know updating to 7.1.1 = losing root and requiring me to root again after the fact which is why i'm holding off for NOW until i get an answer.
silvernirvash said:
oh hey can i download and flash the latest version of android 7.1.1 manually using TWRP with out losing TWPR or my locked bootloader? just curious. i'm about to go back and reroot but i know updating to 7.1.1 = losing root and requiring me to root again after the fact which is why i'm holding off for NOW until i get an answer.
Click to expand...
Click to collapse
No you can't flash factory images using TWRP, I would however highly suggest flashing the factory image to stop that crashing process.
k.s.deviate said:
No you can't flash factory images using TWRP, I would however highly suggest flashing the factory image to stop that crashing process.
Click to expand...
Click to collapse
so i gotta flash using minimal adb and fastboot huh? :/ damn lol. wouldn't that in turn remove TWRP tho? or am i mistaken on that one?
silvernirvash said:
so i gotta flash using minimal adb and fastboot huh? :/ damn lol. wouldn't that in turn remove TWRP tho? or am i mistaken on that one?
Click to expand...
Click to collapse
It would remove TWRP, but after the flash-all.bat is done.. set up your phone. Reboot to bootloader, fastboot boot TWRP install TWRP via zip and flash super su.
Then going forward to update every month, download the newest factory image, right click on the flash-all.bat click edit, scroll over and remove the -w. Then boot into bootloader and run the flash-all.bat, when it's done your still in bootloader, fastboot boot TWRP, flash TWRP zip and flash super su. Reboot.
k.s.deviate said:
It would remove TWRP, but after the flash-all.bat is done.. set up your phone. Reboot to bootloader, fastboot boot TWRP install TWRP via zip and flash super su.
Then going forward to update every month, download the newest factory image, right click on the flash-all.bat click edit, scroll over and remove the -w. Then boot into bootloader and run the flash-all.bat, when it's done your still in bootloader, fastboot boot TWRP, flash TWRP zip and flash super su. Reboot.
Click to expand...
Click to collapse
this would in fact wipe my phone every time i do it tho right? like EVERYTHING including music and photos and stuff right?

Categories

Resources