The phone originially had v405ua11d firmware. I tried "adb reboot bootloader" but it just rebooted. I tried entering the bootloader using the volume down + plugging in, still just booted into android. I used LGUP to flash v405ua20a and its still doing the same. Every guide for unlocking the bootloader involves entering the bootloader as one of the first steps. I don't understand how everyone's doing this. Any help will be appreciated.
There's no way to unlock the bootloader on our own yet unless you own a european EBW model. Unlocking bootloader option right now is to do it remotely. You'll need to pay for the service though. If you need / want to contact either vlad - @Vlaaaad or vasily - @motogvasyag
---------- Post added at 02:57 AM ---------- Previous post was at 02:57 AM ----------
There's no way to unlock the bootloader on our own yet unless you own a european EBW model. Unlocking bootloader option right now is to do it remotely. You'll need to pay for the service though. If you need / want to contact either vlad - @Vlaaaad or vasily - @motogvasyag
Well worth the price to have this done.
Already got it done and on LOS 17. Thinking of going down to 16 to get some stability.
xPreSiDenT said:
Already got it done and on LOS 17. Thinking of going down to 16 to get some stability.
Click to expand...
Click to collapse
Good idea for now, I've got the LOS 16 link in my GSI guide
Ainz_Ooal_Gown said:
Good idea for now, I've got the LOS 16 link in my GSI guide
Click to expand...
Click to collapse
Is it possible to go back to stock pie but with magisk and twrp? Can I flash the kdz, then flash twrp on slot a via fastboot, then magisk through twrp?
Thanks!
xPreSiDenT said:
Is it possible to go back to stock pie but with magisk and twrp? Can I flash the kdz, then flash twrp on slot a via fastboot, then magisk through twrp?
Thanks!
Click to expand...
Click to collapse
You got 2 slots on the phone. Why not just have both? Slot A for stock & Slot B for LOS. Switch when needed. Kicka$$-ness level +1..
neocyke said:
You got 2 slots on the phone. Why not just have both? Slot A for stock & Slot B for LOS. Switch when needed. Kicka$$-ness level +1..
Click to expand...
Click to collapse
I won't even know how to begin with that. It was recommended to keep LOS on A as far as I could understand. My guess was it had something to do with some partitions on one of the slots being damaged to unlock the bootloader. If I had time I would definitely experiment with this but unfortunately got almost none these days. But if there's a guide out there to do this that would be amazing.
Well, you wanna start by getting yer phone bl unlocked and possibly rooted by either vlad or vasily. That solves half of the equation as you now have one slot with stock. Then you wanna head on over to Sgcmarkus' LOS thread for the other half.. done n done.
Oh yeah.. If it's LOS 16 then it's ainz's GSI thread.
neocyke said:
Well, you wanna start by getting yer phone bl unlocked and possibly rooted by either vlad or vasily. That solves half of the equation as you now have one slot with stock. Then you wanna head on over to Sgcmarkus' LOS thread for the other half.. done n done.
Oh yeah.. If it's LOS 16 then it's ainz's GSI thread.
Click to expand...
Click to collapse
I've gone past all of that.... I have LOS 17 on my phone right now. But I am planning to go back to stock pie for the time being.
xPreSiDenT said:
I've gone past all of that.... I have LOS 17 on my phone right now. But I am planning to go back to stock pie for the time being.
Click to expand...
Click to collapse
That's an interesting point to be at. There isn't a stock twrp zip we can flash AFAIK. Didja try switching slots to see if you still have stock on the other one? It should technically be there.
neocyke said:
That's an interesting point to be at. There isn't a stock twrp zip we can flash AFAIK. Didja try switching slots to see if you still have stock on the other one? It should technically be there.
Click to expand...
Click to collapse
Yes but they would have to use Xsavi's Stock TWRP guide for it to boot with TWRP.
Ainz_Ooal_Gown said:
Yes but they would have to use Xsavi's Stock TWRP guide for it to boot with TWRP.
Click to expand...
Click to collapse
Yes, but he says that's all already done and he's got LOS17. So that technically means he should already have twrp as that's needed for LOS.
So.. It now then a matter of fastboot set active a or b to see what's in the other slot. With any luck it'd be the stock fw, otherwise it'd be twrp booting which then means a stock boot.img needed.
neocyke said:
Yes, but he says that's all already done and he's got LOS17. So that technically means he should already have twrp as that's needed for LOS.
So.. It now then a matter of fastboot set active a or b to see what's in the other slot. With any luck it'd be the stock fw, otherwise it'd be twrp booting which then means a stock boot.img needed.
Click to expand...
Click to collapse
No the TWRP work around for Stock by Xsavi
The TWRP guide is by SGCMarkus...
neocyke said:
That's an interesting point to be at. There isn't a stock twrp zip we can flash AFAIK. Didja try switching slots to see if you still have stock on the other one? It should technically be there.
Click to expand...
Click to collapse
Interesting point. I am gonna try that. But, if it isn't there, it should be possible to have twrp with stock, no? I'm thinking back to the steps after unlocking the bootloader and flashing twrp via fastboot. At that stage, according to Vlads instructions, it should be possible to flash magisk through twrp. Gonna try this now after my titanium backup job completes. Will first check the other slot though.
Edit: Turns out I had LOS on both. LOS 17 on A (which I flashed first), and somehow LOS 16 with RR GSI got flashed on B.
On LOS 17 on A, the phone application keeps crashing, the signal indicator never shows, and the phone just shuts down.
After switching back to B, RR is now stuck on the boot screen. So nothing works anymore.
Gonna flash the kdz now. How much worse can it get?
xPreSiDenT said:
The phone originially had v405ua11d firmware. I tried "adb reboot bootloader" but it just rebooted. I tried entering the bootloader using the volume down + plugging in, still just booted into android. I used LGUP to flash v405ua20a and its still doing the same. Every guide for unlocking the bootloader involves entering the bootloader as one of the first steps. I don't understand how everyone's doing this. Any help will be appreciated.
Click to expand...
Click to collapse
Finaly, how did you do ? I have an HK V40 with no bootloader (both ADB command and plug/vol down boot/reboot on normaly). With LG UP cmd I croos flash tu EU version but still no bootloader.
Related
so here is what happened, i was rooted with an unlocked boot loader running chroma rom. i then tried to unroot my device to return completely back to stock. After the process was done, i formatted and wiped everything then did a reboot. when android started up chroma rom was still on there and i can't access developer settings to unlock my boot loader to flash stock image. so now i am stuck with a locked boot loader and a bootloop device. i have tried adb sideload and got back 2 errors that the footer is wrong and the signature. i don't know what to do now. so Please Help! thank you in advance.
another thing i should add, i only have access to stock recovery
i think this toolkit got a boot loop fix although i have never tried it
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
ChiefEli said:
so here is what happened, i was rooted with an unlocked boot loader running chroma rom. i then tried to unroot my device to return completely back to stock. After the process was done, i formatted and wiped everything then did a reboot. when android started up chroma rom was still on there and i can't access developer settings to unlock my boot loader to flash stock image. so now i am stuck with a locked boot loader and a bootloop device. i have tried adb sideload and got back 2 errors that the footer is wrong and the signature. i don't know what to do now. so Please Help! thank you in advance.
another thing i should add, i only have access to stock recovery
Click to expand...
Click to collapse
do you have twrp recovery, or the stock recovery?
i have stock recovery
linezero said:
i think this toolkit got a boot loop fix although i have never tried it
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
ChiefEli said:
i have stock recovery
Click to expand...
Click to collapse
The only option is try and fastboot format userdata and fastboot format cache.
If they don't work, there is no fix. Nothing a toolkit can do.
yup, @danarama has the right explanation. problem is that with stock recovery it most likey will not work. sorry
simms22 said:
yup, @danarama has the right explanation. problem is that with stock recovery it most likey will not work. sorry
Click to expand...
Click to collapse
damn, well i will try it using the toolkit and let you know how it goes.
ChiefEli said:
damn, well i will try it using the toolkit and let you know how it goes.
Click to expand...
Click to collapse
good luck!
at the very least, it might help you fix the bootloop.
ChiefEli said:
damn, well i will try it using the toolkit and let you know how it goes.
Click to expand...
Click to collapse
Has to have unlocked bootloader for that toolkit option to work.
prdog1 said:
Has to have unlocked bootloader for that toolkit option to work.
Click to expand...
Click to collapse
simms22 said:
Click to expand...
Click to collapse
Here is the option. Direct from Wug's FAQ. "If you device is bootlooping or can’t boot up, use “Flash Stock + Unroot” with the “Soft-Bricked/Bootloop” option and follow the onscreen instructions for manually booting your device into bootloader mode and restoring your device."
Can't use flash stock option without an unlocked bootloader.
prdog1 said:
Here is the option. Direct from Wug's FAQ. "If you device is bootlooping or can’t boot up, use “Flash Stock + Unroot” with the “Soft-Bricked/Bootloop” option and follow the onscreen instructions for manually booting your device into bootloader mode and restoring your device."
Can't use flash stock option without an unlocked bootloader.
Click to expand...
Click to collapse
oh well, another "brick"..
simms22 said:
oh well, another "brick"..
Click to expand...
Click to collapse
Pretty much. I have to concur.
prdog1 said:
Pretty much. I have to concur.
Click to expand...
Click to collapse
its sad really. but this happens so often that i dont feel as bad about it anymore. now thats sad
simms22 said:
its sad really. but this happens so often that i dont feel as bad about it anymore. now thats sad
Click to expand...
Click to collapse
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
byrdcfmma said:
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
Click to expand...
Click to collapse
We don't know but this sucker likes to bootloop. Never relock the device till after it boots and running. Concerning relocking non-stock have seen it bork TWRP and kernel.
byrdcfmma said:
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
Click to expand...
Click to collapse
because many people dont read and educate themselves beforehand.
I don't understand why people are re-locking their boot loader. Unless you are returning the device, what is the purpose of re-locking it? I don't get, in this particular thread, why or how the boot loader got locked?
BladeRunner said:
I don't get, in this particular thread, why or how the boot loader got locked?
Click to expand...
Click to collapse
And that is a key question.
I was trying to get ready to turn in my nexus 6 and so I flashed a stock rom (apparently minus the recovery) and relocked my device. I now have twrp but stock 5.1 installed. twrp boots okay but internal storage is 0mb and it appears unable to format partitions. any ideas on a resolution? very comfortable with fastboot (bootloader loads normally) but can't seem to get anything working otherwise.
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
First flash this file and then Rom. That's right?? Or its other way around
karan khara said:
First flash this file and then Rom. That's right?? Or its other way around
Click to expand...
Click to collapse
If u have dm verity error on boot. Just flash it..
Wouldn't this procedure downgrade some performance on the device?
Giocarro said:
Wouldn't this procedure downgrade some performance on the device?
Click to expand...
Click to collapse
No..
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Nitesh13 said:
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Click to expand...
Click to collapse
Yes u can..
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
cool.boy said:
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
Click to expand...
Click to collapse
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
I have no DM verity error and I have cb9 firmware and rooted
Sent from my OnePlus 3 using XDA Labs
Why would you want to flash old firmware and modem, not made for this ROM, just to get rid of a pointless message?
Especially when there are other methods to fix this so called issue ...
Sent from my OnePlus 3 using Tapatalk
puschkin said:
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
Click to expand...
Click to collapse
Yes..
snippem said:
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
Click to expand...
Click to collapse
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
cesar.mk4 said:
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
Click to expand...
Click to collapse
dlhxr said:
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
Click to expand...
Click to collapse
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
cesar.mk4 said:
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
Click to expand...
Click to collapse
I never had that till now only after flash does not reboot.
In my opinion it is more a twrp incompatibility that will be resolved when N sources are out by oneplus
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
Don't even need to wait, just press the power button to skip it (same applies to first bootloader unlocked message).
Sent from my OnePlus 3 using Tapatalk
it's easily avoidable (but the phone will be decrypted)
after flashing ob9 successfully and booting to system, reboot to TWRP (.28) and wipe convert data to f2fs then wipe it, then wipe internal storage (back up your data to your pc 1st)...and that's it, if you want root, reboot back to TWRP and flash root, then roboot to system, dmverity will be gone, and the phone decrypted,
(this will work if you started with a clean ob9 install like sideloading, and you ended with a full stock ob9)
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Zeuszoos said:
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Click to expand...
Click to collapse
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Zeuszoos said:
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Click to expand...
Click to collapse
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
There is an MM ROM that is Rooted and has TWRP built in, but I don't know if it would Flash over this with Odin or not
I am also considering trying the entire KK T2 ROM again to go down to KK and then Flashing that MM ROM.
It has both Odexed & DeOdexed. If I remember right, DeOdexed is the better choice, right?
Thanks for all your time and help!
Dave
Hi,
You know what's sad, is that if I could somehow Roog it without TWRP, then I could use the way awesome "Flashify" app to try to get TWRP on this phone! <lol>
Dave
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Zeuszoos said:
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Click to expand...
Click to collapse
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
dottyparent said:
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
Click to expand...
Click to collapse
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Zeuszoos said:
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Click to expand...
Click to collapse
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
No, I'm sorry, but you have to give me the answer.
All seriousness aside, I depreciate all your effort.
I can only think of one thing left to try... Go to Sammy's site and get the Lollipop 5.1.1 ROM and see what happens. It can't hurt to try, right?
I'll let ya know what happens and thank you again!
Happy Thanksgiving!
Dave
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Zeuszoos said:
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Click to expand...
Click to collapse
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
ShaDisNX255 said:
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
Click to expand...
Click to collapse
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
That's because I have a n910t not a t3
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
I upgraded from LL. The device was running 5.0.1 and now has 6.0.1
dottyparent said:
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Click to expand...
Click to collapse
Thank you for looking! I found out what it is.
It's "Factory Reset Protection" (FRP)
What it does, is keep someone else from Factory Resseting your phone if they steal it. When they reset it, during setup, they have to type in the last Google Email and Password that the phone used, before they can set up theirs.
After reading that, I remembered having to put my Google Info in at two separate points and seeing it telling me to "Verify", but I was just blowing right through setup, not reading all of the small print. I mean hey, I had no idea that even existed and was just annoyed that I had to type the same thing twice!
It will only be found on phones that already have Lollipop and up on them out of the box and probably not all of them yet. And you don't have to worry about downloadable ROMS, so those who have phones that started with KitKat, or even early versions of Marshmallow 6.0 or 6.0.1 would not have seen this happen to them. Even those who updated to the same version of Mm that my phone has won't, if they started with KK or an older MM and then updated to it.
Again, this is something that your phone would have "Out of the Box" and the phone (not all) would have at least L on it.
Just FYI, it's not just Samsung, either.
Just FYI, I have confirmed this info. It is a fact.
Once I have an easy to do, working fix, hopefully without having to perform a Factory Reset, I will "Create A Thread" and as normal for me, write clear and easy, step by step (not leaving any out) instructions on how to "Unlock FRP" and then come back here and post a link to the thread. Hopefully this week.
This phone will not beat me!!!
TTYL
Dave
Hi guys,
My 32 GB 3GB RAM Moto G5S Plus should arrive tomorrow, and I have a couple questions.
Apparently the bootloader can be easily unlocked and I'm guessing I'll be able to easily get root.
My questions are:
1 - How do I unlock the bootloader
2 - How do I get root
3- What's the best custom ROMS for this device
Thanks!
razers7t8 said:
Hi guys,
My 32 GB 3GB RAM Moto G5S Plus should arrive tomorrow, and I have a couple questions.
Apparently the bootloader can be easily unlocked and I'm guessing I'll be able to easily get root.
My questions are:
1 - How do I unlock the bootloader
2 - How do I get root
3- What's the best custom ROMS for this device
Thanks!
Click to expand...
Click to collapse
1 - read - more than enough info available
2 - c 1
3 - that's up to you to decide
razers7t8 said:
Hi guys,
My 32 GB 3GB RAM Moto G5S Plus should arrive tomorrow, and I have a couple questions.
Apparently the bootloader can be easily unlocked and I'm guessing I'll be able to easily get root.
My questions are:
1 - How do I unlock the bootloader
2 - How do I get root
3- What's the best custom ROMS for this device
Thanks!
Click to expand...
Click to collapse
Follow this link for bootloader unlock, root, & twrp(&thank the OP:good - it's pretty straight forward & won't take too long to accomplish...be sure to follow the instructions closely: https://forum.xda-developers.com/moto-g5s-plus/development/root-moto-g5s-plus-t3673287
And "best" is a subjective thing, but there are some good ROMs out there. Give them all a try I've been on validus 8.0 for weeks now, aex 64 bit is nice, and there are more ROMs floating around on android file host too.
Good luck & hope you like your new g5s :highfive:
Mines coming tomorrow too!
Mine will be here Friday.
Sent from my SGP512 using XDA Premium HD app
I don't know how I'm gonna actually make use of it as a "phone" given that I'm currently using an iPhone 8 Plus, but I'm just happy to have a customizable Android device again. Google Voice for the win!
razers7t8 said:
I don't know how I'm gonna actually make use of it as a "phone" given that I'm currently using an iPhone 8 Plus, but I'm just happy to have a customizable Android device again. Google Voice for the win!
Click to expand...
Click to collapse
Just in time too...iPhone X sales are weak so its about that time for crapple to start throttling their 8's to try and get those X sales up!
startswithPendswithOOH said:
Just in time too...iPhone X sales are weak so its about that time for crapple to start throttling their 8's to try and get those X sales up!
Click to expand...
Click to collapse
Hahaha. Custom ROMS, baby!
startswithPendswithOOH said:
Follow this link for bootloader unlock, root, & twrp(&thank the OP:good - it's pretty straight forward & won't take too long to accomplish...be sure to follow the instructions closely: https://forum.xda-developers.com/moto-g5s-plus/development/root-moto-g5s-plus-t3673287
And "best" is a subjective thing, but there are some good ROMs out there. Give them all a try I've been on validus 8.0 for weeks now, aex 64 bit is nice, and there are more ROMs floating around on android file host too.
Good luck & hope you like your new g5s :highfive:
Click to expand...
Click to collapse
I unlocked the bootloader successfully, but when I get to the second step and try to flash the twrp recovery, I keep getting this message:
I keep getting "writing recovery"...
(bootloader) Image not signed or corrupt
OKAY [0.292s]
finished
I erased my phone and started over and didn't enable fingerprint or a PIN. What's the problem?
razers7t8 said:
I unlocked the bootloader successfully, but when I get to the second step and try to flash the twrp recovery, I keep getting this message:
I keep getting "writing recovery"...
(bootloader) Image not signed or corrupt
OKAY [0.292s]
finished
I erased my phone and started over and didn't enable fingerprint or a PIN. What's the problem?
Click to expand...
Click to collapse
Got everything to work. What's the best ROM, though. I'd prefer to be on 8.0 Oreo.
razers7t8 said:
Got everything to work. What's the best ROM, though. I'd prefer to be on 8.0 Oreo.
Click to expand...
Click to collapse
Validus has been my daily driver since day 1 of owning this phone, aex 64 bit is nice too. Just flash & see what you like best
Also, check android file host...there's a few builds there too.
startswithPendswithOOH said:
Validus has been my daily driver since day 1 of owning this phone, aex 64 bit is nice too. Just flash & see what you like best
Also, check android file host...there's a few builds there too.
Click to expand...
Click to collapse
OK. Thanks. I'm guessing Validos is Oreo 8.0. I'm gonna try it now. Could you provide a link?
razers7t8 said:
OK. Thanks. I'm guessing Validos is Oreo 8.0. I'm gonna try it now. Could you provide a link?
Click to expand...
Click to collapse
ROM: https://androidfilehost.com/?w=files&flid=231006
GZR minimal gapps: https://androidfilehost.com/?w=files&flid=222140 (You can use open gapps too if that's your preference)
GZR validus XDA thread: https://forum.xda-developers.com/mo...icial-8-x-y-ground-zero-roms-validus-t3690386
startswithPendswithOOH said:
ROM: https://androidfilehost.com/?w=files&flid=231006
GZR minimal gapps: https://androidfilehost.com/?w=files&flid=222140 (You can use open gapps too if that's your preference)
GZR validus XDA thread: https://forum.xda-developers.com/mo...icial-8-x-y-ground-zero-roms-validus-t3690386
Click to expand...
Click to collapse
I flashed everything, but when I reboot, it doesn't load an OS. It just reboots to TWRP. Help!
razers7t8 said:
I flashed everything, but when I reboot, it doesn't load an OS. It just reboots to TWRP. Help!
Click to expand...
Click to collapse
While I was still on the stock Moto ROM, the last thing I did was fo a factory reset because I had a PIN/Pattern. So I did a factory reset then it took me back TWRP when it restarted. I flashed the Validus ROM and it flashed successfully, but every time I reboot, it goes straight back to TWRP.
razers7t8 said:
I flashed everything, but when I reboot, it doesn't load an OS. It just reboots to TWRP. Help!
Click to expand...
Click to collapse
Hmm... Which TWRP version did you use? r15 is the latest one(r9 worked for me too)... https://androidfilehost.com/?fid=817906626617952763
Download it & flash it in recovery as an image file.
startswithPendswithOOH said:
Hmm... Which TWRP version did you use? r15 is the latest one(r9 worked for me too)... https://androidfilehost.com/?fid=817906626617952763
Download it & flash it in recovery as an image file.
Click to expand...
Click to collapse
Select partition to Flash Image:
system image
boot
recovery
logo
which one?
razers7t8 said:
Select partition to Flash Image:
system image
boot
recovery
logo
which one?
Click to expand...
Click to collapse
I checked. I initially flashed r15
razers7t8 said:
I checked. I initially flashed r15
Click to expand...
Click to collapse
I got out of the TRWP loop by flashing the stock moto ROM following this guide: https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
Something is wrong with Validus. I would advise against using this custom ROM.
razers7t8 said:
I got out of the TRWP loop by flashing the stock moto ROM following this guide: https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
Something is wrong with Validus. I would advise against using this custom ROM.
Click to expand...
Click to collapse
Uh, nope. Not a thing wrong with Validus. Been running the 12/8 build flawlessly since it came out. It's your 1st day with the phone and you messed something up along the way...not a ROM problem...user problem.
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
razers7t8 said:
I checked. I initially flashed r15
Click to expand...
Click to collapse
Did you skip this step from the bootloader unlock thread after installing TWRP?
"Create a complete backup in this step. Do not do anything without taking backup
Now connect your phone to PC. You will see Moto Z storage. Move TWRP backup to PC from your phone. Also move music, images, video and everything to your PC.
Now go to wipe in TWRP and wipe data.
Now copy Magisk zip from PC to Phone.
Now go to install and select Magisk zip and flash. Now reboot to system."
Also, in the validus/GZR OP it has a zip file you need to flash if you had setup fingerprint on stock...did you try that?
"Note: If you set Fingerprint + Pattern/ Pin on Primary/Stock then you need to flash a Lock Fix file on Primary
Lockfix.zip"
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
florian-m19 said:
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
Click to expand...
Click to collapse
I think yes, but I'm not sure
Was wondering the same thing, does anyone know if the red magic 3 is A only or an A/B device. I'm pretty sure it's A only, but I couldn't find any documentation online.
Its A only i think.
Hum... So Project Treble should work ?
That is interesting !
If I could install Resurrection Remix to this device and provided everything works it would become really almost perfect.
If anyone wants to try... If not I'll do it myself when I have time (in 2 or 3 days)...
Regards.
If the device has treble support, meaning a vendor partition it should work no problem, a/b partitioning is really not required for treble.
I tested treble using fastboot, since twrp had some issues, but it resulted in a bootloop and a corrupted recovery partition. I managed to fix it by following: https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
Twrp gave me a mounting error for
/system_root, which is fixable by setting system to be read-only and then rebooting the recovery and re enableing read/write. Have not had the time to test using twrp and treble yet.
*I posted earlier in the day but managed to fix all the issues I had, so this a better summary :silly:
trepKep said:
I tested treble using fastboot, since twrp had some issues, but it resulted in a bootloop and a corrupted recovery partition. I managed to fix it by following: https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
Twrp gave me a mounting error for
/system_root, which is fixable by setting system to be read-only and then rebooting the recovery and re enableing read/write. Have not had the time to test using twrp and treble yet.
*I posted earlier in the day but managed to fix all the issues I had, so this a better summary :silly:
Click to expand...
Click to collapse
So, this means its not working.. Sad Story.
florian-m19 said:
So, this means its not working.. Sad Story.
Click to expand...
Click to collapse
Well not necessarily, since I flashed the lineageos gsi through fastboot. (That may be the issue) I was having issues with twrp. I will try again today, although the chances are slim.
trepKep said:
Well not necessarily, since I flashed the lineageos gsi through fastboot. (That may be the issue) I was having issues with twrp. I will try again today, although the chances are slim.
Click to expand...
Click to collapse
U should clear user data and cache after installing new system if you have bootloop problem
Make sure its A only GSI
em902566 said:
U should clear user data and cache after installing new system if you have bootloop problem
Make sure its A only GSI
Click to expand...
Click to collapse
I'll keep that in mind
trepKep said:
I'll keep that in mind
Click to expand...
Click to collapse
Hey, did you try it again?
florian-m19 said:
Hey, did you try it again?
Click to expand...
Click to collapse
No, I was busy. But I'm trying right now
Treble Attempt #2
No luck, everything flashed with no errors, but all I get is more than 10 minutes of black screen. I also tried flashing magisk right after the gsi finished, same result.
trepKep said:
Treble Attempt #2
No luck, everything flashed with no errors, but all I get is more than 10 minutes of black screen. I also tried flashing magisk right after the gsi finished, same result.
Click to expand...
Click to collapse
Hmm then we must wait for a custom Rom..
florian-m19 said:
Hmm then we must wait for a custom Rom..
Click to expand...
Click to collapse
Yeah, a one plus 7 pro port would be nice
florian-m19 said:
Hello everyone,
is it possible to Flash a treble Rom with unlocked Bootloader?
Do i need twrp also?
If it is possible i will try to install all Apps from the global rom to the treble Rom.
Greets
Click to expand...
Click to collapse
Word of advice. Do not attempt to flash anything on this cell. You will regret it. I tried to flash TWRP over 6 weeks ago an it's been dead ever since. Even a cellphone repair center guy could not repair it.
You need to leave good enough alone.
People all around the world have been stuck in permanent recovery screens or fastboot screens like me.
It really is a very good cell the way it is ?
Bryceicle1971 said:
Word of advice. Do not attempt to flash anything on this cell. You will regret it. I tried to flash TWRP over 6 weeks ago an it's been dead ever since. Even a cellphone repair center guy could not repair it.
You need to leave good enough alone.
People all around the world have been stuck in permanent recovery screens or fastboot screens like me.
It really is a very good cell the way it is ?
Click to expand...
Click to collapse
Many people have faced the issue and they have recovered their device. Look for all solutions available.
danishajaz said:
Many people have faced the issue and they have recovered their device. Look for all solutions available.
Click to expand...
Click to collapse
I have. 7 weeks an counting an no working cell yet. I bought an Mi9 an no issues with it. Easy to reinstall firmware. The red magic 3 is the most difficult to repair cell I have ever encountered. I wish they had something like miflashpro for it
Treble is working from chinese ROM with twrp make sure image is A/B because this device is A/B