I rooted my phone a few days ago and tried installing Nitrogen OS. and my device was encrypted so i had to wipe all the user data and still it asked for encryption.
so i tried installing OOS 5.0.5 which gave the Error 7. saying the ROM isn't for OP3T.
then I saw a tutorial on YouTube about bypassing the security on a ROM and did it and the the ROM got installed.
after yesterday's update, when i tried flashing the entire ROM again, I'm facing the same problem. can somebody help me with this?
EDIT: My phone shows the model as A3003. isn't it supposed to show A3100 or something?
Eeshan Bhave said:
I rooted my phone a few days ago and tried installing Nitrogen OS. and my device was encrypted so i had to wipe all the user data and still it asked for encryption.
so i tried installing OOS 5.0.5 which gave the Error 7. saying the ROM isn't for OP3T.
then I saw a tutorial on YouTube about bypassing the security on a ROM and did it and the the ROM got installed.
after yesterday's update, when i tried flashing the entire ROM again, I'm facing the same problem. can somebody help me with this?
EDIT: My phone shows the model as A3003. isn't it supposed to show A3100 or something?
Click to expand...
Click to collapse
how did you format your data? just wipe?
Went into TWRP, erased all data, formatted the partition too. My major issue is why does it give "error 7 rom is for phone OnePlus 3t and you're not using 3t".
I do have a 3t and i think there might be some problem with kernal. Only i don't know how to fix that
Eeshan Bhave said:
Went into TWRP, erased all data, formatted the partition too. My major issue is why does it give "error 7 rom is for phone OnePlus 3t and you're not using 3t".
I do have a 3t and i think there might be some problem with kernal. Only i don't know how to fix that
Click to expand...
Click to collapse
Are you using the latest TWRP (3.2.3)? If not, try using it.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Are you using the latest TWRP (3.2.3)? If not, try using it.
Click to expand...
Click to collapse
I am using 3.1.1 Blue Sparks
Eeshan Bhave said:
I am using 3.1.1 Blue Sparks
Click to expand...
Click to collapse
Update to the latest version of twrp. You can download it using the TWRP app or by browsing to twrp.me
That should do the trick with the error saying the rom is not for your phone.
Incanity said:
Update to the latest version of twrp. You can download it using the TWRP app or by browsing to twrp.me
That should do the trick with the error saying the rom is not for your phone.
Click to expand...
Click to collapse
Thanks a lot that actually worked. I thought there was some problem with the kernal. Now i can freely flash Pie. Any suggestions on which ROM is best right now?
Eeshan Bhave said:
Thanks a lot that actually worked. I thought there was some problem with the kernal. Now i can freely flash Pie. Any suggestions on which ROM is best right now?
Click to expand...
Click to collapse
Good to hear!
Would'nt know which ROM is best right now, I stick with stock OOS with Magisk.
Eeshan Bhave said:
Any suggestions on which ROM is best right now?
Click to expand...
Click to collapse
There is an entire thread about ROM suggestions: https://forum.xda-developers.com/oneplus-3t/help/best-stable-8-1-custom-rom-oneplus-3t-t3788189
There is not such thing as "best ROM". It depends on your individual requirements, usage patterns, and preferences. It's an individual choice.
Eeshan Bhave said:
I am using 3.1.1 Blue Sparks
Click to expand...
Click to collapse
I am using the same twrp and never had such errors even with latest 5.0.6
Strange
Sent from my ONEPLUS A3003 using Tapatalk
Related
Hi all. Just got htc one. Managed to unlock bootloader and install CWM recovery and flashed Android Revolution HD 4.0 Google Edition but having some problems. First was it had no keyboard but i managed to select one. Now when i press Messenging it just flashes up with not responding and wont load it. Also every now and then it keeps rebooting? HELP please as i cant really do anything. I just installed rom without wiping anything so has that caused it? thanks.
dj-basher said:
I just installed rom without wiping anything so has that caused it? thanks.
Click to expand...
Click to collapse
I'm going to say yes.
When dirty flashing, if there are bugs present, always full wipe and reflash prior to posting any kind of error report.
Sent from my HTC One using XDA Premium 4 mobile app
Got a problem here... Wanted to ota to 4.4 in my rooted, s-off on stock rom.
Flashed stock recovery and downloaded the Ota but it turns to red triangle as its installing.
My question is would this be happening due to having Xposed framework and having Flashed some zips for ad blocking and such? Any feedback is much appreciated!
Also, if that is the issue, would flashing an old backup work if that was prior to using Xposed and such?
Please help! Thanks!
irtrueno said:
Also, if that is the issue, would flashing an old backup work if that was prior to using Xposed and such?
Please help! Thanks!
Click to expand...
Click to collapse
In order to take the ota you have to be on a stock rom
Sent from my HTCONE using Tapatalk
luigi311 said:
In order to take the ota you have to be on a stock rom
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
yes I am on stock rom. Would having xposed cause issues? Or anything that edits the system?
irtrueno said:
yes I am on stock rom. Would having xposed cause issues? Or anything that edits the system?
Click to expand...
Click to collapse
Maybe. The ota might check what's in the system partitions such as apps and such and if there's anything that usually isn't there when the phone is stock it might not update. I asked on the Verizon forum if it's possible to update after deleting some system apps and they said no but I've never tried it.
Sent from my HTCONE using Tapatalk
luigi311 said:
Maybe. The ota might check what's in the system partitions such as apps and such and if there's anything that usually isn't there when the phone is stock it might not update. I asked on the Verizon forum if it's possible to update after deleting some system apps and they said no but I've never tried it.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I eventually was able to update. I restored a backup I did before root, right after unlocking bootloader.
also, I used an old stock recovery. I found the most recent stock recovery and used that and it worked. so still unsure what exactly caused my problems but using the latest stock recovery and using unmodified stock rooted rom worked.
thanks for the response though, much appreciated. definitely soft bricked my phone few times before getting it done. phew...
Hey guys I have a Moto bought Nexus 6, running on T-Mobile network Sim card and all. Currently the 6 is on 5.0.1 and has been asking me to bump up to 5.1. My phone is stock and rooted. As we all know I can't use the OTA as a result.
I'm here bugging you all because I know there are different builds for the Nexus 6, and they seem carrier specific. So I went and hunted down an M build which supposedly is for Tmo, as we have some specific tweaking.
I downloaded the LMY47M build and I am currently on the LRX22C 5.0.1 build. What I would like to know is it okay for me to go into TWRP and flash the download? Like the way a person would flash a nightly of CM? Is it the same process? If not what do I gotta do?
(On a bus ride so would be nice to have it update while I'm still riding)
Sent from my Nexus 6 using XDA Free mobile app
If the "download" is an OTA, it cannot be flashed from a custom recovery. ...and it will still fail because you're rooted.
Nope I downloaded online and it's sitting in a download folder now
Sent from my Nexus 6 using XDA Free mobile app
dynamo147 said:
Nope I downloaded online and it's sitting in a download folder now
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Let me rephrase, if the file you have downloaded is the same file you would get as an ota, then what i said before.
Very likely it's the same but I can't say for sure.,. So where does that leave me in terms of options?
Sent from my Nexus 6 using XDA Free mobile app
dynamo147 said:
Very likely it's the same but I can't say for sure.,. So where does that leave me in terms of options?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know much about this "M" build and what version it is supposed to flash from. What I do know is there is no full factory image available.
Of everything else is stock on your phone (Including radio) I think the best action would be:
- download the factory image for the version you are on now.
- extract it and fastboot flash the stock recovery and system.img
- do NOT lock your bootloader
Then you should be able to accept the ota or side load it from stock recovery.
Mmm will try this when I get home thanks! Will be back to update Folks!
Also, will flashing the stock image and recovery wipe any of my data?
Sent from my Nexus 6 using XDA Free mobile app
dynamo147 said:
Mmm will try this when I get home thanks! Will be back to update Folks!
Also, will flashing the stock image and recovery wipe any of my data?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Not if you extract it an flash only the system.img
Its flashing the userdata image that wipes data
Yes. I would like to know how to do this also. Is there a difference in flashing the D or E version of 5.1 and then flashing a custom ROM that is built from T-Mobile's update?
Or is there carrier specifics in the different Factory Images?
downloading the img right now, when i get back I will make a little step by step for anyone else curious
dynamo147 said:
downloading the img right now, when i get back I will make a little step by step for anyone else curious
Click to expand...
Click to collapse
Its only 3 steps and I already Gave them earlier in the thread
BossJ said:
Yes. I would like to know how to do this also. Is there a difference in flashing the D or E version of 5.1 and then flashing a custom ROM that is built from T-Mobile's update?
Or is there carrier specifics in the different Factory Images?
Click to expand...
Click to collapse
In my mind in its the radio. you want the radio that comes with the T Mobile version. (if you are on t-mobile obviously) what you flash on top of it for system doesn't matter as long as it supports the radio and is version 5 .1. And as long as what you're flashing doesn't include the radio you are good to go.
So for me as long as I keep the E radio for Verizon I can flash D through M it kind of doesn't matter.
Sent from my Google N6 on VZ
rootSU said:
Its only 3 steps and I already Gave them earlier in the thread
Click to expand...
Click to collapse
Thanks for your replies here. I'm in the same boat as the OP, and have one follow-up question to this thread, if you or anyone could answer --
After doing the steps you mentioned previously -- specifically sideloading/accepting the OTA update, will the bootloader remain unlocked? I'd like to re-root afterwards and keep the user data, though I was under the impression it would actually re-lock the bootloader.
Thanks for any info!
vormund said:
Thanks for your replies here. I'm in the same boat as the OP, and have one follow-up question to this thread, if you or anyone could answer --
After doing the steps you mentioned previously -- specifically sideloading/accepting the OTA update, will the bootloader remain unlocked? I'd like to re-root afterwards and keep the user data, though I was under the impression it would actually re-lock the bootloader.
Thanks for any info!
Click to expand...
Click to collapse
Yes, your bootloader will remain unlocked.
dynamo147 said:
Hey guys I have a Moto bought Nexus 6, running on T-Mobile network Sim card and all. Currently the 6 is on 5.0.1 and has been asking me to bump up to 5.1. My phone is stock and rooted. As we all know I can't use the OTA as a result.
Click to expand...
Click to collapse
Did you ever get this going? I know I procrastinated a bit due to the "unknowns", but finally made it happen (bug off, TMo "5.1 Available" notification!). I ran into a lot of oddities between my phone and computer (running Windows 7) like the phone being an unrecognized device when working with adb sideloads... I ultimately opened the Device Manager and forced the composite ADB driver through for each instance. For me, the rough flow was, starting out with stock but unlocked and rooted,
* flashed stock LRX22C system and recovery images
* used adb to sideload the T-Mobile LMY47M official update
* flashed TWRP
* used adb to sideload SuperSU
* and of course, cleared the dalvik/cache and rebooted
All data in-tact, and my LEDs are still functional (the LEDs are actually the key reason I have it rooted right now... it's insanely stupid that Google blocks these built-in LEDs from being used by those that want them!).
Anyways, if you run into any of those issues, happy to help!
Evolution_Freak said:
Yes, your bootloader will remain unlocked.
Click to expand...
Click to collapse
Thank you...exactly what I needed to know!
Ah yeah I did actually, and I like you, had problems getting the phone recognized with the ADB, also windows 7, which prevented me from slide loading like I wanted to, but nevertheless got all the updates pushed through thnx though!
Sent from my Nexus 6 using XDA Free mobile app
For some reason TWRP is not working after the lollipop update. Is anybody else having this problem? If there is a fix someone let me know. I can't flash anything with twrp not working.
Sent from my SM-N910T using XDA Free mobile app
TechGuy334 said:
For some reason TWRP is not working after the lollipop update. Is anybody else having this problem? If there is a fix someone let me know. I can't flash anything with twrp not working.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Did you reflash twrp? You gotta reroot and reflash twrp
absinthesummer said:
Did you reflash twrp? You gotta reroot and reflash twrp
Click to expand...
Click to collapse
I reflashed it 3 times with not luck. I'll try to re-root and see what happens.
Sent from my SM-N910T using XDA Free mobile app
TechGuy334 said:
I reflashed it 3 times with not luck. I'll try to re-root and see what happens.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Yeah cf auto root that sucker in Odin and then flash recovery.
absinthesummer said:
Yeah cf auto root that sucker in Odin and then flash recovery.
Click to expand...
Click to collapse
I tried that with no luck. I even reflashed stock lollipop and it still isn't working. This is crazy.
Sent from my SM-N900T using XDA Free mobile app
TechGuy334 said:
I tried that with no luck. I even reflashed stock lollipop and it still isn't working. This is crazy.
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
Wow that's strange. Is stock recovery working at all? I think I'd try to enter it and do a reset from it and then maybe retry root & recovery. Never seen it reject recovery like that :/
absinthesummer said:
Wow that's strange. Is stock recovery working at all? I think I'd try to enter it and do a reset from it and then maybe retry root & recovery. Never seen it reject recovery like that :/
Click to expand...
Click to collapse
Me either. This is the first time this has ever happened to me.
Sent from my SM-N900T using XDA Free mobile app
absinthesummer said:
Wow that's strange. Is stock recovery working at all? I think I'd try to enter it and do a reset from it and then maybe retry root & recovery. Never seen it reject recovery like that :/
Click to expand...
Click to collapse
TechGuy334 said:
Me either. This is the first time this has ever happened to me.
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
I haven't done LOLLIPOP yet, downloading it now...
but if you used cf autoroot, it puts and old recovery so you won't enter recovery after using it...
are you using twrp 2860....
I always do this.. for a new version update..
I enter twrp and wipe 3 or 4 time, system, data, cache, and dalvik cache, then within twrp I reboot into download mode.
odin v3.09 and do new firmware, after it reboots and enters recovery and does it thing. I pull out the battery then
odin twrp ... after reboot, I pull out battery and enter recovery and flash SU...
mdiaz33685 said:
I haven't done LOLLIPOP yet, downloading it now...
but if you used cf autoroot, it puts and old recovery so you won't enter recovery after using it...
are you using twrp 2860....
I always do this.. for a new version update..
I enter twrp and wipe 3 or 4 time, system, data, cache, and dalvik cache, then within twrp I reboot into download mode.
odin v3.09 and do new firmware, after it reboots and enters recovery and does it thing. I pull out the battery then
odin twrp ... after reboot, I pull out battery and enter recovery and flash SU...
Click to expand...
Click to collapse
That's why I said reflash recovery after rerooting. Either way I hope he gets it sorted. He never did say if stock recovery was working for him or not :/
can someone post the link to the newest twrp i can't find it on twrp site for some odd reason.
I think the link is in their xda thread
http://forum.xda-developers.com/not...-utility-twrp-2-8-1-0-teamwin-t2915588/page32
TechGuy334 said:
Me either. This is the first time this has ever happened to me.
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
Actually, come to think of it. I do remember having an issue on note 3 once. It was my bosses phone and I rooted it for him and flashed recovery. But recovery wouldn't boot no matter what I did.
What it was- I had chosen a version of twrp I had known to be stable rather than the latest, but it wasn't compatible with that firmware. I ended up flashing the latest and it worked fine. Twrp moved to a new site which should be linked in the thread another poster posted. With the new lollipop firmware you probably need the absolute latest recovery. Good luck with it!
absinthesummer said:
That's why I said reflash recovery after rerooting. Either way I hope he gets it sorted. He never did say if stock recovery was working for him or not :/
Click to expand...
Click to collapse
I got it fixed but I used older version of twrp. Twrp version 2.8.6.0 wasn't working for me after the lollipop update at all. I tried everything guys and nothing worked but an older version. Thanks for the help guys
Sent from my SM-N910T using XDA Free mobile app
TechGuy334 said:
I got it fixed but I used older version of twrp. Twrp version 2.8.6.0 wasn't working for me after the lollipop update at all. I tried everything guys and nothing worked but an older version. Thanks for the help guys
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Excellent news! Glad you're up and running
nofroyo said:
can someone post the link to the newest twrp i can't find it on twrp site for some odd reason.
Click to expand...
Click to collapse
http://dl.twrp.me/trltetmo/
TechGuy334 said:
I got it fixed but I used older version of twrp. Twrp version 2.8.6.0 wasn't working for me after the lollipop update at all. I tried everything guys and nothing worked but an older version. Thanks for the help guys
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
running into same thing.. I just tried twrp 2850 and I cant install no previous roms, or backups from before this lollipop... only restore is the new updated lollipop from the firmware.
edit - which version of twrp did u use....
mdiaz33685 said:
running into same thing.. I just tried twrp 2850 and I cant install no previous roms, or backups from before this lollipop... only restore is the new updated lollipop from the firmware.
edit - which version of twrp did u use....
Click to expand...
Click to collapse
I used version 2.8.4.0
Sent from my SM-N910T using XDA Free mobile app
TechGuy334 said:
I used version 2.8.4.0
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Best one so far. The 2 following I saw nothing that made me want update it.
BAD ASS NOTE 4
BACARDILIMON said:
Best one so far. The 2 following I saw nothing that made me want update it.
BAD ASS NOTE 4
Click to expand...
Click to collapse
I totally agree.. looks like tmobile patched the hack we do for unlimited tethering, that I used from @jovy23 tutorials... If I delete the tetherprovison.apk the tethering app doesn't work. and with this new Lollipop for some reason the wifitether and FoxFi app aren't working.
I'm just playing with it a bit. but we can always downgrade the bootloader with the actual firmware so that NK4 will work again.
waiting to see if someone else finds a way through this. I might just go back to v4.4.4 Kitkat..
I guess that was the delay with the T-Mobile Note 4 update to lollipop.
Well from what I seen is tmobile like all isp knows what you been doing online. So if they see ya been downloading at sites and ur data is not moving they gonna lock you out lol. The days of free tether are coming to a halt.
BAD ASS NOTE 4
Had my OnePlus 3T working fine with Stock ROM, wanted to try Nougat on OP3T. Adb Sideloaded the file "OnePlus3Oxygen_16_OTA_018_all_1612281257_d8107904d7734248.zip" (Open Beta 10 for OnePlus 3) on to my OnePlus 3T via OnePlus Recovery. The installation completed successfully via Stock Recovery, but on selecting reboot, the phone is completely dead. No response to power cycle or even dash charging.
Is it a hard brick, and is there any way to come out of this?
SathyaWP said:
Had my OnePlus 3T working fine with Stock ROM, wanted to try Nougat on OP3T. Adb Sideloaded the file "OnePlus3Oxygen_16_OTA_018_all_1612281257_d8107904d7734248.zip" (Open Beta 10 for OnePlus 3) on to my OnePlus 3T via OnePlus Recovery. The installation completed successfully via Stock Recovery, but on selecting reboot, the phone is completely dead. No response to power cycle or even dash charging.
Is it a hard brick, and is there any way to come out of this?
Click to expand...
Click to collapse
I accidently flashed the op3 firmware/modem and this brought me back.
Try this http://forum.xda-developers.com/showthread.php?t=3515306
Sent from my unknown using Tapatalk
tdamocles said:
Try this http://forum.xda-developers.com/sho...postimg.org/ssp33fvrp/Screenshot_73.png[/img]
Click to expand...
Click to collapse
Good, now try it. It'll take you back to the original firmware. It will erase everything.
Sent from my unknown using Tapatalk
tdamocles said:
Good, now try it. It'll take you back to the original firmware. It will erase everything.
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
It worked! Thanks! :good::good:
SathyaWP said:
It worked! Thanks! :good::good:
Click to expand...
Click to collapse
Awesome!
Sent from my unknown using Tapatalk
tdamocles said:
I accidently flashed the op3 firmware/modem and this brought me back.
Try this http://forum.xda-developers.com/showthread.php?t=3515306
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
which modem/ROM have you installed on Oneplus 3T and did system allowed u to install OP3 ROM on OP3T ?
Can you give me the link
tdamocles said:
I accidently flashed the op3 firmware/modem and this brought me back.
Try this http://forum.xda-developers.com/showthread.php?t=3515306
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
Heya, I've ran into the same issue. Any idea how you flashed the OP3T firmware without getting the CheckHwId failed error?