Weird recovery of a crashed 8 pro. - OnePlus 8 Pro Guides, News, & Discussion

Popping in to give some feedback as always with my stuff.
Last night while using lucky patcher something must have happened it didn't like because I lost my wallpaper and my call history, at that point I figured she needed a restart. This brought me too a boot that would crash 40 seconds later and boot into whatever it was explaining boot issues
I tried clearing cache in the stock recovery but that didn't help
So I wiped the system settings only
Phone restarted as a fresh phone and is running great! First thing I did was look for and launch majisk, it needed to install some stuff but the damn think came back fully rooted!!!
So if all else fails wipe system in factory recovery.
It saved me a good bit of time unlocking bootloader and all that jazz
Hope it helps someone else when they get to a loop
Merry Christmas all

Smittyzz said:
Popping in to give some feedback as always with my stuff.
Last night while using lucky patcher something must have happened it didn't like because I lost my wallpaper and my call history, at that point I figured she needed a restart. This brought me too a boot that would crash 40 seconds later and boot into whatever it was explaining boot issues
I tried clearing cache in the stock recovery but that didn't help
So I wiped the system settings only
Phone restarted as a fresh phone and is running great! First thing I did was look for and launch majisk, it needed to install some stuff but the damn think came back fully rooted!!!
So if all else fails wipe system in factory recovery.
It saved me a good bit of time unlocking bootloader and all that jazz
Hope it helps someone else when they get to a loop
Merry Christmas all
Click to expand...
Click to collapse
You can do a full Factory Reset and remain rooted. Since the boot.img is patched and flashed to your device. A full reset wont lock your bootloader too.
Only if you use MSM Tool or relock the bootloader manually (and flash a non rooted boot img beforehand) you relock your device.

xtcislove said:
You can do a full Factory Reset and remain rooted. Since the boot.img is patched and flashed to your device. A full reset wont lock your bootloader too.
Only if you use MSM Tool or relock the bootloader manually (and flash a non rooted boot img beforehand) you relock your device.
Click to expand...
Click to collapse
Good to know thank you
Merry Christmas

Related

[Q] Issue with HTC One X after bootloader unlock and recovery flash

Hey Guys,
So I am totally stumped at the moment.
I have used the Hasoon2000 HTC all-in-one and performed the following:
Unlocked the bootloader
flashed the recovery
Installed SuperSU
My phone is rooted and all is good but now everytime i try to open an app that has something to do with i think either the gpu or sound it freexes then restarts.
What should i try?? I have tried to flash stock recovery with no success and wiped the cache and tried full factory reset. All results in the same issue. I ahve even tried to remove the SU in the system/xbin and bin folders.
Should i try flashing with a stock rom?
Any help is much appreciated
scycer said:
Hey Guys,
So I am totally stumped at the moment.
I have used the Hasoon2000 HTC all-in-one and performed the following:
Unlocked the bootloader
flashed the recovery
Installed SuperSU
My phone is rooted and all is good but now everytime i try to open an app that has something to do with i think either the gpu or sound it freexes then restarts.
What should i try?? I have tried to flash stock recovery with no success and wiped the cache and tried full factory reset. All results in the same issue. I ahve even tried to remove the SU in the system/xbin and bin folders.
Should i try flashing with a stock rom?
Any help is much appreciated
Click to expand...
Click to collapse
Which apps are doing it, are they stock or 3rd party??
You will find there are still a lot of apps out there that dont work or arent too clever on ICS, so if its from the market id investigate its ics compatability b4 you do anything.
It has happened to me, PROPMODDER, it loads, but as soon as you try to alter something it all goes wrong.
Failing that, try booting into recovery, wipe the cache, dalvik cache, and finally fix permissions, see if that helps any, if it is stock apps causing the problem and you dont want to use 3rd party apps you could also boot into fastboot, open a cmd prompty changing to your ADB directory were fastboot is and try FASTBOOT ERASE CACHE, this can sometimes help with issues.
Good luck with it, i hope you solve it.
Thanks for the suggestion.
I have tried clearing both caches and fixing permission (clockwork recovery) but it has made no difference. it is any app including stock that cause this issue. Seems to be anything related to the GPU or sound (pretty sure sound).
I have the srock RUU, should i lock the boot loader and install the RUU (1.28)??
as a basic test i just tried Youtube and as soon as the video begins to play it freezes for 10 seconds then restarts
Attempted to install orignial RUU but got an image error unpn installation
I checked my phone which matchs the below file, dont know why it thinks its wrong
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
scycer said:
Attempted to install orignial RUU but got an image error unpn installation
I checked my phone which matchs the below file, dont know why it thinks its wrong
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
Click to expand...
Click to collapse
Did you lock your boot loader before flashing the ruu?
Also, did you read some threads around here so you could understand what you are doing to your phone? I'm asking this because the all in one tool is nice, but it's also dangerous when you don't quite understand how it works
Well no i didnt have the bootloader relocked as it wouldnt load the OS back up, it just kept booting to bootloader. Turns out that was a good thing. Ran RUU and now im back to the beggining lol thanks all for your help. I will do some more reading before I root again
Any recommendations? all i want to do is a simple root to connect a ps3 controller lol
http://forum.xda-developers.com/showthread.php?t=1592355

[Q] Factory Reset Bootloop

Hello, all. I've had this problem for about a year, but I just kind of put the KF away once I got it replaced instead of fixing it.
Last year, I put my KF into a softbrick, factory reset bootloop. On boot, the KF warns:
Your Kindle has detected a problem and must clear App storage. The recovery process will erase some apps and data from your device.
Click to expand...
Click to collapse
The rest is the generic factory reset info. Press power to proceed. This looks like it goes through the process, restarts, and just boots back up into this message. Thus, bootloop. I've tried looking up others with the same problem, but no one has had the same one I mention. I don't have a custom bootloader or TWRP.
As for what caused this, if i can remember correctly I was having trouble with google apps permissions and changed a folder in /system/ to something else. The fire freaked out and I rebooted it. The above has happened ever since. So the only modification is being rooted. I've tried getting access to adb, but it hasn't listed the device. Maybe I installed the drivers wrong or something, but I didn't mess with it for long because I don't like being in Windows if I can help it.
Any help would be greatly appreciated. Not in too big of a hurry, though, as I have a Nexus 7 currently. ^.^
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Thepooch said:
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Click to expand...
Click to collapse
I knew about fastboot, I should have mentioned. I just don't have the money to spend on one currently. What do you mean by attempt to race it to factory reset and reset it?
Just what I said you have just a little time to race to settings and factory reset it before it fc`s and shuts down some people manage to pull it off.

[Q] Loads of Problems (rooted, unrooted, firemwares, flash, stuck on logo screen)

I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
geekery15 said:
I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
Click to expand...
Click to collapse
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
geekery15 said:
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
Click to expand...
Click to collapse
Yep.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
geekery15 said:
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
Click to expand...
Click to collapse
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
geekery15 said:
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
Click to expand...
Click to collapse
The only thing I can suggest is download this to your SD card and flash it in twrp. http://forum.xda-developers.com/showthread.php?p=56345482
The Sims may not work because its uncomptiple with lollipop.
Simply, hit wipe in twrp, hit advanced wipe, and tick system, dalivk and cache. Then go back and install the Cm11 zip and reboot. Hopefully it gets you booting
Sent from my SM-T800 using Tapatalk
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
I understand that. That is why I clicked unroot in supersu and tried the game app, but it still wouldn't work. On my galaxy note 3 I run 5.0 lollipop and my game works fine. My phone isn't rooted and I never decided to root it and then unroot it.
Is an app smart enough to know when a device has been rooted and if are those that hack their actual game on rooted devices uses cloak or xposed or both to by pass their root?
I rather be unrooted for the sake of the game, but how does one find the stock firmware? Or is it not possible at this point?
Sorry for any confusion.
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
geekery15 said:
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
Click to expand...
Click to collapse
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
geekery15 said:
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
Click to expand...
Click to collapse
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
ashyx said:
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
Click to expand...
Click to collapse
I did because I thought it had to be shut down before I powered it on and waited. I realized afterwards that you probably meant to just let it sit for 10 to 15 minutes.
Are you asking me my solution or other peoples solution?
geekery15 said:
Are you asking me my solution or other peoples solution?
Click to expand...
Click to collapse
Your solution.
cant reboot after failed encryption
I was trying to encrypt my galaxy tab s, which is rooted and has lollipop 5.0. Afrer reading encryption failed. I tried to reboot in recovery via twrp. My device doesn't reboot, it just acts like its going thru the motions. Only to return to twrp recovery menu. How do I reboot the system clearing the failed encryptions. I am a noob and any suggestions would be much appreciated.
You will have to go into recovery and wipe the data and cache partition then reboot.
It may take a while to boot up after that.
Well I thought my solution was using IronRom... but i'm not too sure now.
I just got back from work and I went to turn on my tablet and it took me to the same loading screen and then after about 5 minutes it tells me that the system can't respond. It asks me to click "ok" or "wait" ... clicking either just turns my tablet off.
Now the screen has dimmed. It's turning on when it wants and sometimes it'll show me the time in the upper right hand corner, but it won't let me do anything because it's a black screen.
What does all of this mean?
I just noticed if I click the "power button" it just flashes my tablet desktop then goes back to black, but it shows me the battery percentage and the time in the upper right hand corner...
smt 800 stuck in logo
SAMSUNG GALAXY TAB S 10.5 WIFI WHAT IT CAN AND CANT DO
i HAD ROOTED AND INSTALLED LOLLIPOP 5.0 WITH SUPER SU AND TWRP RECOVERY.
I THEN TRIED TO ENCRYPT WHICH FAILED.
MY DEVICE SAID TO REBOOT SYSTEM AND THEN TRY TO ENCRYPT AGAIN. AFTER REBOOTING, MY DEVICE IS STUCK WITH (logo screen)THE SAMSUNG TAB S NAME AT THE TOP OF THE SCREEN AND ANDROID ON THE BOTTOM. I then rerooted with cf auto root thru odin. Odin and my tablet went thru the motions. When everything was complete and device should have initialize, but didn't. This part of the process didn't happen.
I am able to go into DOWNLOAD MODE and can get to manual mode, but I seem to have lost recovery. Here is the info.
android system recovery <3e>
kot49h_t800xxu1af8..
the binary reads: samsung official
system status: custom
Do you have any suggestions.

[Q] LG G4 H811 Stuck in Recovery (TWRP) Loop

I was running the latest version of TWRP and a rooted version of the LG G6 port. Everything was stable and worked fine. So I was ready to give it back to its owner who I had modded it for. I went into the settings menu of the phone and did a standard factory reset to remove my account that was logged in so I could test the phone out before giving it to the owner. well when it finished resetting and rebooted, its been stuck in a boot loop ever since.
Tried just clearing both Dalvik Cache and Cache, to no avail. Tried Reflashing the rom and starting over. Still nothing. Tried flashing a different rom. Still nothing.
So what else can I try? and also if its the only thing I can do, rest it all the way back to stock factory everything. How do I do that on this phone. What program do I need and what files. and whats the steps to complete the process.
Thank you in advance for all help that is given
i factory reset in twrp and turned on developers options after first boot then reflashed twrp i always forget backup lol or delete it or use kdz you flashed before anyway i can help i will if you still need
if you have tried to flash the same custom rom or another is still not working, flashes with the program "lg up", you will need a kdz file,and the corresponding drivers. if with that you can not watch this tutorial before doing anything.
if you have a backup made with twrp, it flashes again.
https://forum.xda-developers.com/g4/help/unbrick-lg-g4-brick-hs-usb-qdloader-t3542785
during this process you will have to disassemble the back of the phone, (plastic) you do not need to remove the motherboard completely from the phone, anyway if you can enter download mode try with lg up tool.
if you need help around here we are.
Well now in the process of trying to fix it. The phone bricked and will no longer turn on at all. Is there anyway to fix this ?
Silicon Knight said:
Well now in the process of trying to fix it. The phone bricked and will no longer turn on at all. Is there anyway to fix this ?
Click to expand...
Click to collapse
Can you get into download mode?
Also, it's possible you have been hit by the bootloop

various issues with google variant

I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.
stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
I agree. I got it used tho which is an issue.
Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.
Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.
Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:
stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.
smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.

Categories

Resources