Can't load recovery after flashing Stock image 5.1.1 - Nexus 6 Q&A, Help & Troubleshooting

Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about 14GB from flashing ROMS and such.Everything seems to have gone smoothly however when I try the oem unlock command I am told that the device is already unlocked.I proceeded to root and then I tried to flash TWRP but I get permission denied.
Also,my Play Store just crashed when I try and type in an app to search for.
The question is-how do I know which factory image is right for my device?
There are a number of 5.1.1 images,I selected the one marked for all carriers except T-Mobile.Could I have selected the wrong image to be causing some of these problems?
Or should I just go ahead and jump up to 6.0.1-there is only 1 image for that release.
I would't think the image mattered that much but something is wrong here.
I got the phone last week from the Amazon sale and I activated it no problem on Verizon and flashed several ROMS no issue.
Advice is much appreciated.

I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.

dahawthorne said:
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
Click to expand...
Click to collapse
Thanks for the detailed response. I was running 5.1 initially because that is what the phone booted with and I like full-featured ROMS like BlissPop. I guess I'll give 6.0.1 a whirl.It just seemed like it was too new to be rock solid. I had as many features on my old S3 running 4.4.2 as I have seen since then if not more actually. I am curious about Google Now On Tap however.
Hopefully this gets me fixed up.Cheers.

chiadrum said:
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about .......
Click to expand...
Click to collapse
It is possible that the issue is caused because you downgraded the bootloader by flashing 5.1.1.
Flash the complete latest stock 6.0.1 images.

Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig. I am guessing that is normal?
The 5.1.1 started working fine after an update all but I still couldn't install TWRP fyi.
Let's see how Marshmallow tastes!

The "does not contain boot.sig and recovery.sig" is standard. I have no idea why it continues to appear version after version, but it has no effect on the installation.

chiadrum said:
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig.
Click to expand...
Click to collapse
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.

NLBeev said:
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
Click to expand...
Click to collapse
Thanks guys.

chiadrum said:
Thanks guys.
Click to expand...
Click to collapse
Ok more strangeness.pPhone is working fine,no issues.However I am unable to unlock bootloader using the fastboot OEM unlock command.
The message is "Not supported command in current status".
Yes,OEM unlock is allowed in Dev Options.I tried turning that off in case the indicator was faulty and then I couldn't even attempt to unlock,immediate failure.
Tried this several times after reboots as well.
Build MMB29K.
Any ideas?

Would it be too simple an answer to say that it's because the phone is already unlocked? You couldn't install a new ROM with a locked bootloader.
I myself have been a bit surprised by the peremptory & derogatory comments of some of the very senior members in these forums when people ask what seem to be questions with obvious answers, and I'm beginning to see their point...
Still, I also recognise that an "easy" question is one that you know the answer to, and I don't want to put people off asking questions. Being knocked back myself several times hasn't stopped me asking.

That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.

chiadrum said:
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
Click to expand...
Click to collapse
Confirmed I am an idiot.Device is unlocked already. Wasn't expecting that.The people way smarter than me who prepared that image took care of it for me.

Not an idiot at all. Like I said, an easy question is one that you know the answer to. Experience counts...
It's not the image that is unlocked - it's the device. Once unlocked, you have to specifically lock it again, but it's neither simple nor a good idea. An unlocked device gives you a far better chance to recover from errors.

Related

A new Start !!

Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not iirc <71.08 shouldn't be flashed onto 71.08 existing BL right or was it 71.10 ?? (idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all. Heard a few CM roms had BL packed into ROMs and the updte to 5.1.x + lower BL caused hardbrick, a.k.a bootloop + noTWRP with Fastboot lockedout ).
So here's my to-do list sorry to post this long but seems like this is start for me....Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & Nexus 6 information....
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - MultiROM working guide on 5.1.1 plus M latest release anyone, will try the official thread tho, any info on whre to start would be awesome !!
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful posts/threads that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!
Ashtrix said:
Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not(idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all). So here's my to-do list sorry to post this here but seems like this is start for me.Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & a few Nexus 6 information, any useful links would do the job.
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - Does MultiROM work on 5.1.1 plus M latest release ?
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful links that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!
Click to expand...
Click to collapse
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use
AlkaliV2 said:
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use
Click to expand...
Click to collapse
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..
Ashtrix said:
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..
Click to expand...
Click to collapse
I'm pretty sure mFastboot is made directly for a Verizon variant, but since the Nexus 6 is unlocked and your Verizon SIM card dictates the network you are on, I would say stick with normal Fastboot for your flashing endeavors. Good luck and read twice, flash once :good:
Edit: Quick side note, love the avatar. Good choice.
Thankyou :highfive:
Just did an OEM unlock and wierdly after that, the bugdroid loading doesn't end at all. Did an factory img flash of 5.1.1 Shamu-LMY48Y and booted in less than a min Lol.
And yes the fastboot is working, wow things are definitely wierd with Shamu (volume normalization, mFastboot previous xperience, bootloader bricks...seems like Qcom fixed that after CM brickbug and no one can help the manual bricking) but I'm ok with all these , just love this device, massive, powerful and sexy looking piece
EDIT :
Well everything's going fine but this bugdroid loading doesn't seem to be fixed at all, after bootup 23Gb was there so I did a format and again stuck, this time around I tried using TWRP to flash (CM12.1)after doing fastboot commands - fastboot format userdata, cache. Now it says unable to flash on so&so data partition, So formatted from the OS and now MTP says generical heirarchial. I don't remember any device with that format...
EDIT 2 : Device won't boot with that bugdroid formatting the Data partition. Needs to be fastboot flashed else stuck there forever again same 23Gb bootissue if I do that & Using fastboot format userdata command it formats into the 64GB - 54Gb available space but with TWRP It fails to flash - the same error, can't flash on data parition. So repeat fastboot and it's a damn cycle. Will try to flash MM if it won't then. I may have to return again...OMG
EDIT 3 : http://forums.androidcentral.com/go...ys-formatting-data-yellow-text-any-ideas.html
http://forum.xda-developers.com/google-nexus-5/help/help-stuck-formatting-data-t2737793
EDIT : Tried MM and after 10 mins formatted succesfully now gotta try a ROM or any, hope its fine !!
Again the GH FS is back with MTP and doesn't flash at all with TWRP. If I go for a re-lock and it it fails to boot with formatting properly...then bam nothing but a bricked Nexus !!
TWRP did the format but the device is messed up, sliptscreen issue..
I'm going to return this, enough of the hassle had me messed up totally :crying:
Seems like 6P seems better than having all these issues. Or wait for the 2016 device...
EDIT : Sorry for the GH format seems like it's normal, but the flashing issue is too wierd..
I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.
scryan said:
I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.
Click to expand...
Click to collapse
I know this issue, just a factory reset fixed this thing on my old N6 that I had for 2 days, but this takes too much of time to format....Just had TWRP do the job and flashed the Temasek but ALAS !! Splitscreen issue.

Downgrade 4.1.3 to 4.1.1 (and beyond)

Hi all,
I am having issues with my Bluetooth and GSM. I am considering trying to downgrade from OOS 4.1.3 to 4.1.1. I am completely stock, not rooted and don't even have TWRP.
Would appreciate some clarification to the following questions:
1) Can I downgrade by just flashing the official full 4.1.1 zip found in OP website?
2) Should I only flash the modem zip? And if so, can I use 4.1.1 modem while having 4.1.3 installed?
3) Since 4.1.1 already has nougat 7.1.1, is 1) also safe for further downgrades, for example, directly to 4.0.4?
Thanks.
Best regards,
Oldiamond
If your bootloader is locked, you can't downgrade (unless you exploit the security vulnerability from a few weeks back).
If your bootloader is unlocked, use TWRP or fastboot to clean flash whatever version of OOS you want.
You should consider flashing the latest open beta release, I think it's already fixed over there plus there are some Extra goodies and its stable as ****
Anova's Origin said:
If your bootloader is locked, you can't downgrade (unless you exploit the security vulnerability from a few weeks back).
If your bootloader is unlocked, use TWRP or fastboot to clean flash whatever version of OOS you want.
Click to expand...
Click to collapse
Pharrax said:
You should consider flashing the latest open beta release, I think it's already fixed over there plus there are some Extra goodies and its stable as ****
Click to expand...
Click to collapse
Thanks to both. I am this close to send it back to RMA, as I did not install anything other than 4.1.3, and didn't even unroot it. I don't know... perhaps by sending it back without ever installing TWRP or unlocking anything would provide more feedback to the manufacturer, other than saying "damn guy, started fiddling with the phone and ROMs, and here's the result".
Regarding the beta, I initially considered avoiding it because i read in the forums about issues such as sometimes alarms not ringing. I figure that my boss wouldn't like that
Going back from BETA to regular version also requires TWRP?
Best regards,
Old
oldiamond said:
Thanks to both. I am this close to send it back to RMA, as I did not install anything other than 4.1.3, and didn't even unroot it. I don't know... perhaps by sending it back without ever installing TWRP or unlocking anything would provide more feedback to the manufacturer, other than saying "damn guy, started fiddling with the phone and ROMs, and here's the result".
Regarding the beta, I initially considered avoiding it because i read in the forums about issues such as sometimes alarms not ringing. I figure that my boss wouldn't like that
Going back from BETA to regular version also requires TWRP?
Best regards,
Old
Click to expand...
Click to collapse
Alarm issues were fixed, also it never happened to me I and I've been on beta a long time i think on the official page there are the steps to switch between stable and beta. I don't think it requires twrp but don't take my word for it.

when i try to flash bluesparks twrp there only a white led no screen

The other problem i have is when i try to flash bluesparks twrp and go to recovery the sceen is blank and only the led glows but i can flash the officaial twrp and flash roms but they come with error 7 and when i flash a oxygen os it gets stuck in updating system image
ak_bagade said:
but i can flash the officaial twrp and flash roms but they come with error 7 and when i flash a oxygen os it gets stuck in updating system image
Click to expand...
Click to collapse
Error 7 often means you are trying to flash an Oreo ROM with an older version TWRP which does not support Oreo.
But we can't tell from the info provided by you. Always give version numbers and other details for TWRP (and blu_spark TWRP) you are having trouble with, as well as the ROMs you are trying.
Also, make sure you are using the right TWRP and ROMs for 3 versus 3T (another reason for Error 7).
redpoint73 said:
Error 7 often means you are trying to flash an Oreo ROM with an older version TWRP which does not support Oreo.
But we can't tell from the info provided by you. Always give version numbers and other details for TWRP (and blu_spark TWRP) you are having trouble with, as well as the ROMs you are trying.
Also, make sure you are using the right TWRP and ROMs for 3 versus 3T (another reason for Error 7).
Click to expand...
Click to collapse
its the latest bluesparks
ak_bagade said:
its the latest bluesparks
Click to expand...
Click to collapse
I said: always give a version number. "latest bluesparks" isn't a version number. I can't count how many times I've seen folks claim they flashed the "latest" recovery. And when prompted for more info, we find out that they aren't even close, sometimes flashing a version TWRP from 2 years ago or older! Not saying this is necessarily your case. But we don't know for certain, if you don't give us precise and accurate info to work with.
You also said you flashed official TWRP. What version number exactly?
You also need to tell us what custom ROMs (and versions) you tried to flash. And what version OOS did you try to flash?
Some friendly advice, try to take more than 5 seconds to type a response to questions we ask you. Provide as much detail as possible, and answer all the quesions. For that matter, when asking for help, posting 2 or 3 (poorly typed) sentences is rarely enough info to go on. Again, provide as much detail and specific info as possible.
this is mostly an outdated firmware issue, Always make sure you have the latest firmware for your device
Firmware 4.5.1/nougat/3T
Firmware 4.5.0/nougat/3
or you can try the Oreo ones
(Stable)
Firmware 5.0.0/Oreo/3T
Firmware 5.0.0/Oreo/3
(Open Beta)
Firmware OB20/Oreo/3T
Firmware OB29/Oreo/3
OP3T firmware thread https://forum.xda-developers.com/oneplus-3t/how-to/firmware-modem-collection-flashable-zips-t3565535
OP3 firmware thread https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
redpoint73 said:
I said: always give a version number. "latest bluesparks" isn't a version number. I can't count how many times I've seen folks claim they flashed the "latest" recovery. And when prompted for more info, we find out that they aren't even close, sometimes flashing a version TWRP from 2 years ago or older! Not saying this is necessarily your case. But we don't know for certain, if you don't give us precise and accurate info to work with.
You also said you flashed official TWRP. What version number exactly?
You also need to tell us what custom ROMs (and versions) you tried to flash. And what version OOS did you try to flash?
Some friendly advice, try to take more than 5 seconds to type a response to questions we ask you. Provide as much detail as possible, and answer all the quesions. For that matter, when asking for help, posting 2 or 3 (poorly typed) sentences is rarely enough info to go on. Again, provide as much detail and specific info as possible.
Click to expand...
Click to collapse
the bluesparks twrp which i flashed is 8.61 op-3t
and the official twrp which works is 3.2.1-0
so when i use the official twrp i have to remove the "assert" from the updater script and flash the rom or else i get the error 7
Something which has come up recently is that my homebutton/fingerprint sensor does not work (its like it doesnt exist) when i flash any rom from android 7-8.1.
So i came to stock by relocked the bootloader by the way like it happens when you hardbrick your device. now im in marshmallow.
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
The other funny thing is that when i called oneplus to help me with flashing the latest software there method helps me to get the bluesparks twrp but since i keep flashing i lose the twrp so thats the only way i can bliuesparks twrp
ak_bagade said:
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
Click to expand...
Click to collapse
Doesn't work like that, the home button, fp sensor "files" are not in TWRP, or managed by FW in any way. All of these are in the /system folder of the ROM that is installed. Which is why they don't work in TWRP.
Have you been on MM since you got this phone? If so, your firmware is heavily outdated, and that's why you end up with the White LED of Death. Try flashing the latest Open Beta over stock recovery. Make sure to unlock your bootloader first. Then flash any variant of TWRP you want, and then see if you still get the White LED of Death.
ak_bagade said:
Something you should know about is that i flash a lot of roms and locked and unlocked the bootloader a countless times and i think this has affected the files which might be related to the homebutton and fingerprint sensor .
Click to expand...
Click to collapse
You shouldn't be locking the bootloader if you are flashing custom recovery and custom ROMs, and you don't need a locked bootloader to flash official updates either. Really, there is no reason to lock the bootloader unless you are worried about security concerns; want a "full stock" conditions, etc. And for most xda users, an unlocked bootloader is going to be the highly preferable condition. Further, locking the bootloader requires be full stock (including stock recovery, not TWRP). And trying to lock the bootloader under any other condition, is asking for trouble.
I agree with the recommendation above, to flash the full zip of the Open Beta or official OOS update, which will put you on a fully "stock" baseline including firmware. Then go from there.
---------- Post added at 09:19 AM ---------- Previous post was at 09:07 AM ----------
ak_bagade said:
The other funny thing is that when i called oneplus to help me with flashing the latest software there method helps me to get the bluesparks twrp but since i keep flashing i lose the twrp so thats the only way i can bliuesparks twrp
Click to expand...
Click to collapse
If flashing the official zips with TWRP (including blu_sparks), you will always lose TWRP (overwritten with stock recovery) if you reboot after flashing the update. You can prevent this by flashing root (SuperSU, Magisk) or a custom kernel before rebooting (after the update).

Zenfone Go Oreo help

Hi someone with an account on 4dpa with 30 posts could please download this rom and share it here? I don't know Russian so it's impossible for me to write 30 posts.
I have a Zenfone Go (Z00VD) and the stock ROM it's terrible (crash in the camera, 1 Gigabyte of app space already full....)
In case you can't, could you provide an alternative ROM with as less bugs as possible?
Thank you
Original Thread 4pda
Translated Google
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
JustAnormalGuy said:
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
Click to expand...
Click to collapse
Hi, not yet, it's not my phone so I'm searching a stable ROM. I saw the nougat thread here but it's not very clear what works and what not, there seems to be a nougat rom on 4dpa which should work well except the videocamera with the stock app, but the Oreo one seems almost bug free although more complex to install. Unfortunately I can't access it.
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
aurismat said:
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
Click to expand...
Click to collapse
Those 2 bugs are not a deal breaker for me, would you mind linking to the ResRemix 5.7.4 rom that you used?
Sure, buut since I can't post links(thanks XDA for 10 post restriction, love ya!), I'll have to send one another way.
PM me your Discord handle(if you have one) or something else. I should be able to send you the link there.
aurismat, and what version of twrp do you use ?
I use TWRP 3.0 by Jemmini. It's been a *long* time since I installed it though, so if you have something different, I'm afraid I won't be of much help unless I'll be able to pull my recovery .img file.
Actually, i use the same version. Problem is most probably my method of root. The common method of rooting for our device didn't include any flashing with sp flash tool. But for my situation, my bootloader is locked even after downgrading. So i did the other method (also found on the forum) in which includes flashing.
Hmm, it *may* be the root method, may be also the locked bootloader.
If I recall right(and this might be THE common way), I used the fastboot method from XDA, and I knew it'd work cause I rooted more phones that way. I remember downgrading the stock ROM down to version 39(i think that one still had the bootloader check in dev options) and then trying to unlock the bootloader and obviously go through flashing the recovery image.
Dunno what might be the issue with your way of flashing, though. AFAIK might be anything from leftover files to bootloader giving the finger.
@aurismat i think the problem might be that i used the "format all + download" option on sp flash tool. Does that affect the phone in any way that deprives my phone from using 6.0 - 7.0 roms? (Besides the "null" imei effect)
@JustAnormalGuy I don't think it should be a problem, because the ROM .zips install their own stuff to the partitions AFAIK, so even if Flashtool wipes everything, it should still be fine. Try doing one of them ROMs(previously said ResRemix worked for me), but remember to wipe the Internal Storage partition if you can.
Oh and remember to take a backup of your current ROM, should it bootloop again at least you won't have to do the hassle of reinstalling everything back(learned that the hard eay haha).
EDIT: was it just Nougat ROMs that you were trying or was it both Nougat and Marshmallow? Not sure what might be the cause, but the ROMs developed under the same kernel from ska-vova in 4PDA worked for me. Just a thought.
well actually i already tried various roms from Marshmallow to Nougat all of which gave me bootloops. I've already followed the steps of installation as written. However, i tried once installing a Marshmallow rom from the facebook group named "ASUS Zenfone Go Indonesia" and it surpisingly worked for me (numerous bugs present however), as well as most of the marshmallow (and only marshamallow roms) on their group.
The thing is I also might think one of the reasons why i get the bootloops in the roms from the 4pda forum is the kernel used in them. (just speculation) Should it be correct to assume that ?
As I recall:
Working rom shows "kernel version > [email protected]"
Not working rom - "kernel version > [email protected]"
Hmm, I'm using [email protected] kernel version 3.18.19.
All the ROMs there seem to be by mosly nik-kst's kernel. ska-vova seems to just build ROMs with the kernel.
Besides, take note from the working ROM - it's also from 4PDA.
Only thing I can speculate is that your device is somewhat different(maybe different hardware, not sure) and hence why it gives you BLs.
Dunno, this case is a tough cookie to be honest - only thing I can recommend at this point is to flash literally EVERYTHING back to stock and try using fastboot method to get recovery and root back.
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
aurismat said:
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
Click to expand...
Click to collapse
Nice! Resurrection Remix is working too well to bother, but who knows in a few months!
That would be great man, thanks !!

[Help] Unable to use custom ROMs on brand new 3T (touch non responsive once woken)

So about 3 weeks ago my 2 year old 3T just stopped working out of nowhere. I debated on whether to upgrade for over a week, but eventually decided to replace it with the same, just to have the familiar ROM, & not to have to learn anything new or mess with anything else, since I'm going through a lot of personal stuff right now. Anyway, I got the phone over a week ago and I've tried everything since then to get it running something beside OOS to no avail. Every single time it goes to sleep in another ROM, once I wake it up, touch is no longer responsive. I can't for the life of me figure out why. I have tried so many different things, in so many different ways. I know it might sound ridiculous but at this point I'm just in tears... I really need a functional phone, and I never would have bought another OP3T if I knew I'd be stuck with OOS....
The process I went through as soon as I got it:
Unfortunately I don't remember the version of OOS that it came with
- Unlock bootloader
- Flash TWRP (twrp-3.0.4-1 due to a thread I came across and was confused by)
- Wipe everything
- Flash recommended firmware for my ROM (posted in the ROM's thread)
- Flash my favorite ROM (Unofficial RR)
- Flash Magisk
- Boot, everything seems fine, screen goes off, turn it back on, unable to use touchscreen anymore.
I then used the unbrick tool, and tried again. Same problem. Used unbrick tool, unlocked bootloader, this time tried to flash this unofficial Lineage . Booted. It went to sleep. Woke up. Touchscreen nonfunctional.
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS. I go through the entire process again, this time flashing TWRP 3.2.1.0, it's the same thing. I've tried going up to open beta and then flashing my roms. I've tried flashing the rom without firmware, without magisk. With gapps. Without gapps. I always format and wipe everything. I also tried this on the off chance it might work.... I have seriously done the process every way imaginable, over twenty times since I got the phone last week.... nothing ever works. I also just tried Cyanogenmod, but it wouldn't flash at all.
I don't know what to do anymore. I just want to have a phone that I don't hate. At this point, I am too tired and I've got too much going on to figure this out on my own anymore. I would be grateful to pay someone at this point just to help me get this working honestly.... so if there's anyone out there who knows how to fix this, please let me know
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Mizart said:
It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess).
Click to expand...
Click to collapse
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
SpaceOctopus said:
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS.
Click to expand...
Click to collapse
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Mizart said:
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Click to expand...
Click to collapse
Brand new from ebay. Sealed in the box.
I did try flashing a more recent version of resurrection remix, but it failed. Any recommendations?
redpoint73 said:
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case. Thank you.
hhp_211 said:
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Click to expand...
Click to collapse
I did try that TWRP eventually. No change. I would probably have switched to pie a while ago, except one small thing. There's an xposed module I'm really attached to, and as far as I'm aware, xposed isn't available on pie? Or at least that's what I've heard/read. It's the xprivacy lua module that lets you control every type of data an app has access to. I think I've tried looking for an alternative and there aren't any, either. :'( You know, sometimes it's just that one small thing... lol
However, I did try to install the most recent version of RR yesterday, and it failed flashing. Don't know why. I'm going to try again after flashing the firmware. Maybe it'll work this time.
Anyway, I'm also going to try what you all have recommended and see what happens. Hopefully something happens. Thank you much for your help
Ok, well, this time it let me install Resurrection Remix latest version. It may not be exactly what I wanted, but it's pretty goddamn close, and it sure as hell isn't OOS! lol
Thanks for your help everyone! I really appreciate it. I do still really wish I knew wtf was happening honestly with it not properly running nougat ROM's, but hey, this works for me. It won't make me want to toss it in a dumpster and set it on fire every time I pick it up. :laugh: :laugh: :laugh:
Maybe I can get someone to figure it out in the future or something, I don't know. I sure wish someone would convert that xprivacy module to work with Magisk though! I'm surprised nobody has even made an alternative or an app or anything like it really.
SpaceOctopus said:
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case.
Click to expand...
Click to collapse
I think the unbrick tool does flash the full OOS. But honestly not 100% sure, as I have never actually had to use the unbrick tool (knock on wood!). Which is one reason I decided to pose that as a question.
In any case, if the unbrick did flash an old OOS, best to replace with newer version (or at least the firmware). Updated firmware typically plays better with the current custom ROMs. And old firmware is often a culprit when random bugs occur after flashing a custom ROM. So again, flashing firmware and/or the full update zip (which also flashes the firmware) is best practice in such cases. And if you are in any doubt about the OOS version or corresponding firmware that was installed, it probably doesn't hurt to flash again.

Categories

Resources