Related
I can't boot up, can't get into recovery. I can only get into download mode. No matter what TWRP I flash, it says "Custom Binary(BOOT) Block By FRP Lock" on the Downloading screen.
I tried flashing stock 5.1.1 odin, 5.1.1 bootloader/modem, etc. Can't get past this to get into recovery or boot the device. Any suggestions??
EDIT: Good news! Flashing the stock 5.1.1 odin image worked . (link: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841)
It even preserved my data and everything (I guess b/c I was on the leaked 5.1.1). I'll probably just back up some things and start fresh on the stock software, but I'm just glad to have it working.
whittikins said:
I can't boot up, can't get into recovery. I can only get into download mode. No matter what TWRP I flash, it says "Custom Binary(BOOT) Block By FAP Lock" on the Downloading screen.
I tried flashing stock 5.1.1 odin, 5.1.1 bootloader/modem, etc. Can't get past this to get into recovery or boot the device. Any suggestions??
Click to expand...
Click to collapse
SmartSwitch disaster recovery mode.
whittikins said:
I can't boot up, can't get into recovery. I can only get into download mode. No matter what TWRP I flash, it says "Custom Binary(BOOT) Block By FAP Lock" on the Downloading screen.
I tried flashing stock 5.1.1 odin, 5.1.1 bootloader/modem, etc. Can't get past this to get into recovery or boot the device. Any suggestions??
Click to expand...
Click to collapse
More info, how did you get to this state of brick?
What was flashed, odined or installed.
Files, links. Etc.
Pp.
PanchoPlanet said:
More info, how did you get to this state of brick?
What was flashed, odined or installed.
Files, links. Etc.
Pp.
Click to expand...
Click to collapse
I was running the G925T (edge) leaked 5.1.1 rom ([5.1.1][ROM][TW][OE6] Blck/TW), which worked well for the month that I used it. I had TWRP from that thread installed as well (I think it was 2.8.6.x). Everything was good at this point.
Where I am now:
When I power the device on, it says:
KERNEL IS NOT SEANDROID ENFORCING
Custom binary blocked by FRP Lock.
When I try to enter Recovery, it says:
RECOVERY IS NOT SEANDROID ENFORCING
Custom binary blocked by FRP Lock.
What I did to get here:
SHORT VERSION - flashed latest modem and bootloader for G925T (edge) via Odin.
LONG VERSION
Last night I attempted to flash (via ODIN) the G925T bootloader, modem, and TWRP for this ROM: http://forum.xda-developers.com/gal...-xtrestolite-pure-edition-1-0-beta-1-t3082467
G92xF(D)/T Galaxy S6 Universal Odexed Pure edition ROM
Based on the latest Samsung Stock G925F XXU2BOFJ Lollipop 5.1.1 firmware (Base build date: 20-JUN-2015)
NOTE: I didn't ever get to flash the ROM because the trouble started when trying to flash the bootloader/modem via ODIN.
- Odexed Pure Edition: Odexed & 100% original/Stock files!
Steps followed:
Do exactly step-by-step the following things:
- Unplug your Phone (IMPORTANT!)
- Turn your Phone completely off (This is IMPORTANT)
- Start your Phone in download mode on this way: Press Vol down + Home + Power buttons till the screen turns on, press Vol Up to continue (Only enter download mode on this way, otherwise it won't work!!)[/B]
- Open Odin 3.10.6 on your PC (Make sure you're using this version of Odin, other versions won't work correctly maybe!)
- Click on the 'BL' button, and load in your BOOTLOADER tar.md5 file for your model
- Click on the 'CP' button, and load in your MODEM tar.md5 file for your model
- DON'T TOUCH ANYTHING ELSE (you can brick your phone if you choose other settings in Odin)
- Now Connect your phone to your computer (DO NOT connect your phone before this step, otherwise it won't work!)
- Click on the Start button
- Wait till it finish flashing.
- Your phone reboots automatically after flashing. <--- device never rebooted because ODIN said Failed instead of Successful.
I then tried to flash TWRP 2.8.7.1 (link below) since maybe that had to be flashed before the bootloader/modem, but it failed too.
Links:
Odin 3.10.6
DOWNLOAD - https://www.androidfilehost.com/?fid=95916177934555153
[G925T] Odin Bootloader/Modem Packages:
5.1.1 Bootloader: G925T-UVU2COF6
DOWNLOAD - https://www.androidfilehost.com/?fid=24052804347766210
5.1.1 Modem: G925T-UVU2COF6
DOWNLOAD - https://www.androidfilehost.com/?fid=24052804347766211
You also have to update your TWRP to the latest version (2.8.7.1 or newer) when flashing this.
DOWNLOAD - http://build.twrp.me/twrp/twrp-2.8.7.1-zeroflte.img.tar
Is there a file I can Odin flash to disable FRP Lock? I can't boot up to turn it off.
If not, what are my options from here? Any way to preserve SDCARD or even /Data?
If all else fails, what Odin file should I flash to get back to stock?
EDIT: Regardless of what I try to flash in Odin (recovery, kernel, TWRP, modem), it begins the process but then fails because the phone states "_______ is not SEANDROID enforcing" and states FRP lock is on.
NexVision said:
SmartSwitch disaster recovery mode.
Click to expand...
Click to collapse
SmartSwitch isn't detecting my phone (although Odin does). What mode should it be in? I can get into Download Mode, but that's about it!
Your biggest problem right now is getting past FRP / factory reset protection, the only way to avoid this would have been to turn on bootloader unlock in "developer options"
OEM unlocking.
The security system is protecting your phone from you.
You need to be able to smartswitch back to stock but since your device status was not official, custom after running odin, root or anything else you may have done with root, smartswitch won't recognize your phone.
Without "OEM unlocking" on, the phone will turn on you.
The purpose of this security is to prevent your lost or stolen phone from been modified in any way and activated with another carrier.
Maybe tmobile has a procedure for returning phone back to normal.
Pp.
PanchoPlanet said:
Your biggest problem right now is getting past FRP / factory reset protection, the only way to avoid this would have been to turn on bootloader unlock in "developer options"
OEM unlocking.
The security system is protecting your phone from you.
You need to be able to smartswitch back to stock but since your device status was not official, custom after running odin, root or anything else you may have done with root, smartswitch won't recognize your phone.
Without "OEM unlocking" on, the phone will turn on you.
The purpose of this security is to prevent your lost or stolen phone from been modified in any way and activated with another carrier.
Maybe tmobile has a procedure for returning phone back to normal.
Pp.
Click to expand...
Click to collapse
Guys at the store couldn't do anything unfortunately. I guess it's just a brick now?
EDIT: The leaked 5.1.1 didn't have that option in dev options either. I guess running the leaked 5.1.1 is where I screwed up, even though it worked great while actually using it. I didn't have root, but I had TWRP recovery.
Would flashing the stock image work since it's not a custom one? I'm downloading it now from here: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
I'm guessing it won't work or else you would have suggested it. If anyone has a suggestion, I'm open to it!
It seems like there must be a way to disable FRP with an Odin flash, but maybe not.
whittikins said:
Would flashing the stock image work since it's not a custom one? I'm downloading it now from here: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
I'm guessing it won't work or else you would have suggested it. If anyone has a suggestion, I'm open to it!
It seems like there must be a way to disable FRP with an Odin flash, but maybe not.
Click to expand...
Click to collapse
After looking over article I give it a thumbs up, it may work for you.
Thats the problem with leaked updates or firmware, sometimes devs take shortcuts in order to package it for flashing and security stuff gets left out.
The ota 5.1.1, shows the option to turn on unlock bootloader .
Keep us posted, good luck.
Pp.
Screenshot showing option for bootloader unlock.
Pp.
PanchoPlanet said:
After looking over article I give it a thumbs up, it may work for you.
Thats the problem with leaked updates or firmware, sometimes devs take shortcuts in order to package it for flashing and security stuff gets left out.
The ota 5.1.1, shows the option to turn on unlock bootloader .
Keep us posted, good luck.
Pp.
Click to expand...
Click to collapse
Good news! Flashing the stock 5.1.1 odin image worked .
It even preserved my data and everything (I guess b/c I was on the leaked 5.1.1). I'll probably just back up some things and start fresh on the stock software, but I'm just glad to have it working. Thanks for taking the time to help out!
whittikins said:
Good news! Flashing the stock 5.1.1 odin image worked .
It even preserved my data and everything (I guess b/c I was on the leaked 5.1.1). I'll probably just back up some things and start fresh on the stock software, but I'm just glad to have it working. Thanks for taking the time to help out!
Click to expand...
Click to collapse
Glad to hear, don't forget about the oem unlocking in developer options.
Read carefully before you flash, and setup smartswitch on your pc, do a backup just in case.
Pp.
I had the same issue. I try to download stock firmware, download link just keep loading, doesn't work.
Is there any other links? samobile link doens't work neither. Thanks.
drakegao said:
I bricked my phone as well, same situation, I headed to that page try to download stock firmware, download link just keep loading, doesn't work.
Is there any other links? samobile link doens't work neither. Thanks.
Click to expand...
Click to collapse
Try a different pc, check your WiFi connection, or maybe Starbucks.
Pp.
Just checked link works and download works.
Pp.
PanchoPlanet said:
Just checked link works and download works.
Pp.
Click to expand...
Click to collapse
Thanks for replying, by the way. I got locked when i am still on 5.0.2 and i flash the bootloader and the modem. It was the modem of 5.1.1 didn't go through.
Will it be flashed through the 5.1.1 firmware, if not, any other options can solve the frp locked? Thanks
You need to flash 5.0.2 stock firmware with Odin, then maybe.
You can't flash anything that's 5.1.1 on your phone.
PanchoPlanet said:
You need to flash 5.0.2 stock firmware with Odin, then maybe.
You can't flash anything that's 5.1.1 on your phone.
Click to expand...
Click to collapse
tried, still failed in odin. I think is may be because my bootloader is actually 5.1.1's.
However, I saw above said flash 5.1.1 odin image ? what is that? Thanks.
solve it by flash 5.1.1 tar via odin as above said. thanks.
After updating my bootloader to NE2 using odin, by phone just keeps and booting up to the Samsung Galaxy logo and restarting. The logo appears for a second or so before restarting. I can access download mode, but receive the following:
ODIN MODE
PRODUCT NAME: GT-N7100
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
AP SWREV: A2
RPMB: INVALID RPMB DATA
( the last three lines have appeared, and were not there previously before updating the bootloader). The phone was working fine with stock 4.4.2, before installing the bootloader. I cannot access recovery mode, and have flashed TWRP with odin (reported success in odin), but cannot access the TWRP recovery menu on my phone. I have tried to flash stock 4.4.2 again with odin, I do not receive any errors and receive a success 1 in odin where a blue bar is visible (when flashing) on the screen of my phone. But after the phone restarts, i experience the same bootloop problem. Help would be greatly appreciated.
Open Odin, uncheck everything, flash latest stock ROM from sammobile (https://www.sammobile.com/firmwares/database/GT-N7100/), you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
audit13 said:
Open Odin, uncheck everything, flash latest stock ROM from sammobile, you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
Click to expand...
Click to collapse
Before proceeding, I'd like to ask:
1 - I have a motherboard that I've obtained from China. Would it be ok for me to flash as you've recommended with this motherboard, taking into account the "RPMB: INVALID RPMB DATA" message that appears in download mode ?
2 - Can I install any of the latest firmwares available on sammobile for my galaxy note 2 ?
3 - Would I be able to install TWRP and custom roms after ?
Thanks
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
audit13 said:
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
Click to expand...
Click to collapse
After flashing the N7100XXUFOC2 firmware with all boxes unchecked in odin, i still receive a bootloop, and the phone is not entering recovery :-/. The messages that appear in download mode have remained unchanged.
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
audit13 said:
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
Click to expand...
Click to collapse
Yes it flashes with no errors. When turning the phone on, the samsung galaxy note 2 logo appears for just under a second, and the phone restarts and repeats until i remove the battery. Nothing happens when I try to enter the recovery menu, the same behaviour is observed (phone restarting constantly after showing SGnote2 logo). I have been reading around, and i suspect (just a guess, not sure) that the "RPMB: INVALID RPMB DATA" message that I observe in download mode may have something to do with this.
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
audit13 said:
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
Click to expand...
Click to collapse
Is there anything else that i could try ? I used an app to check the bootloader version when it was working on stock 4.4.2, and it stated that it was at LJ7. After updating the bootloader to NE1, I've experienced this problem. Would it be possible to revert back to the previous bootloader ( and would this help ?). I've flashed custom roms with no problems, beforehand using TWRP.
How did you update the bootloader? Did you update the bootlaoder without updating anything else?
audit13 said:
How did you update the bootloader?
Click to expand...
Click to collapse
I downloaded the NE1 bootloader from a user here who has a list of bootloaders on his profile (user: Androidwizzard), and flashed it using Odin v3.09 with the default boxes checked. I did not update anything else ( just clicked the "BL" field and selected the bootloader, then flashed).
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
audit13 said:
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
Click to expand...
Click to collapse
Yeah. Would it be possible to revert the bootloader back to what it was previously ? Also, is there anything else that you may suggest that i could do ? I'm still not sure what is causing this issue exactly. It seems strange that I can flash all files with no errors using Odin. By flashing a later firmware, is the bootloader automatically updated ? ( if yes, then I'm not sure why the app stated that my bootloader version was at LJ7, given that I've flashed stock 4.4.2 with odin beforehand.)
Do you have a link for the bootloader?
Did the phone work properly before flashing the new NE1 bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
audit13 said:
Do you have a link for the bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
Click to expand...
Click to collapse
I have not tried flashing the latest rom ( I could try, if that may help). I can not provide the direct link to the bootloader, since i will have to produce 10 posts ( new user here lol ). You can find the bootloader by searching google: [bootloader/modem/rom][tw kitkat][4.4.2][pf1 + pc1 + oe1 + od4 + nl1 +], then going to Androidwizzard second post.
The phone was working great before flashing the NE1 bootloader. As mentioned previously, I've flashed the N7100XXUFOC2 firmware resulting in no change.
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
audit13 said:
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
Click to expand...
Click to collapse
I will give it a go right now. Would you be able to guide me to where I could obtain the appropriate pit file for the phone ? The firmwares with PF1 have (orange) carrier. Would this affect things ?
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
audit13 said:
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
Click to expand...
Click to collapse
16 GB model. Alright, I'll try to flash the latest rom.
Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?
flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !
porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does
flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well
Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.
ma2crmam said:
Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.
Click to expand...
Click to collapse
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!
ma2crmam said:
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!
Click to expand...
Click to collapse
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?
ma2crmam said:
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?
Click to expand...
Click to collapse
Glad it helped and yes it is not so expensive regarding the fact that there are all sorts of official firmware (mostly leaked ones) available for a lot of manufacturers.
The CUST reference at the end if the firmware version can be found in settings > about the tablet in the very last line. Mine is in German, So translated this line would state something like adapted/customized version. D001 is definitely Western Europe,this should be fine.
If not familiar how to install it google or search the forum for dload method. It will tell you what to do.
Sent from my HTC U11 using XDA Labs
I've done:
1. Get the correct firmware (version ...B007) and extract the RECOVERY.IMG and UPDATE.APP.
2. Flash the RECOVERY with Fastboot and install the UPDATE with the "dload" in the SD.
3. Reboot in RECOVERY MODE, wipe all and restore factory settings.
4. Then, the tablet was updated via OTA to the ...B008 version.
Then, positive:
1. The OTA works fine.
2. I was abble to install the Nextlix App and the HBO Spain App plays videos. Both didn't work before.
3. If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: SAFE
Then, negative:
1. I can't relock the Bootloader yet. When I try to relock (fastboot oem relock CODE) and the answer was again: FAILED (Remote: root type is risk)
Well, for normal use that's enough, but... THE RELOCK is becoming personal!!!
Hi
I've problem with my sm-g960f. I live in UK, but my phone was bought in Switzerland and because of that I am not receiving any system updates. Samsung support told me to go to Switzerland to check if I'll receive update there, but it is not an option. I've got stuck at android 8.0. Is there any chance that I update it manually to newest one? If it is, please help me with it. Thanks!
I've never did anything with phones soft before, sorry if it is stupid question.
When I was like you I did a lot of research for what i needed to flash the software i wanted and what to do if any thing goes wrong.
First you need to unlock your bootloader and this can take 7 days to confirm and also wipes your data. Once unlocked you need to flash twrp through Odin on your pc also you will need a file to flash to stop a boot loop after flashing twrp. Then you need to download the latest firmware from Sam mobile, this can take hours on the free account. Then use Odin again to flash the firmware android 10. Then you will be updated
danlivesey said:
First you need to unlock your bootloader and this can take 7 days to confirm and also wipes your data. Once unlocked you need to flash twrp through Odin on your pc also you will need a file to flash to stop a boot loop after flashing twrp.
Click to expand...
Click to collapse
You don't need to flash TWRP, for this to work. You can do it normally using stock recovery.
Then you need to download the latest firmware from Sam mobile, this can take hours on the free account. Then use Odin again to flash the firmware android 10. Then you will be updated
Click to expand...
Click to collapse
Start from this step. I highly recommend to download original firmware using the Frija tool (search here in XDA) because there you don't have any limiting download speed. Once downloaded, you can now just go to stock recovery, wipe data, cache and system, and reboot to download mode and flash the downloaded firmware from frija tool.
danlivesey said:
When I was like you I did a lot of research for what i needed to flash the software i wanted and what to do if any thing goes wrong.
First you need to unlock your bootloader and this can take 7 days to confirm and also wipes your data. Once unlocked you need to flash twrp through Odin on your pc also you will need a file to flash to stop a boot loop after flashing twrp. Then you need to download the latest firmware from Sam mobile, this can take hours on the free account. Then use Odin again to flash the firmware android 10. Then you will be updated
Click to expand...
Click to collapse
I've followed your instruction and everything works great! Just instead of downloading from sam mobile I used frija tool. @kyooohei08, @danlivesey Thanks a lot guys!