Develop Bugs

Updated Bootloader: Bootloop, cannot access recovery, can access download mode !

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.

SM-J200GU/DS Stock firmware?

Hello,
While trying to root my J200GU I accidently wiped the OS. Now I am left with the TWRP recovery mode and access to Download mode.
I have been trying to flash a stock firmware to my phone using different methods without success:
1- Used Odin tool but it fails when it begins to write the rom
2- ADB sideload - Gives me an error saying the rom is missing the META INF
3- TWRP Install - I tried different zipped roms and all of them give me error saying cannot detect MD5, although the file is there inside.
I am very confused I dont know what is wrong. I am not sure if the roms I use are good but since I already tried multiples I might be doing somethin else wrong.
Can anyone help me out. Does anyone has a stock rom that actually works? or a method?
Thanks.
V.

download the official samsung firmware at sammobile then flash it through odin.

Problems with Safety Net

After the last OTA update, my Moto G5 started to boot with the following warning:
"
Your device has failed verification and may not work properly.
To learn more visit:
motorolacom/unlockbootloader
ID: N/A
Your device will boot in 5 seconds
"
It also started to restart randomly.
I did some research on the web and found out that this warning appears when someone unlocks/roots the device.
The problem is that I aver never unlocked the bootloader or rooted the device.
When I boot to fastboot it says "OEM Locked" and the app DevCheck says that I am not rooted.
It seems to me that the update corrupted something and now some piece of software flags my device as unlocked.
Besides the irritating screen, some apps are not working properly or cannot be downloaded from the store.
I tried to reset to factory settings and wipe caches. Problem still happens.
I'd like to know if you guys know a solution for this problem.
I saw on another post that this problem was happening on some Verizon Moto Zs and they provided a software to reinstall the rom
Unfortunately, Motorola has not released a software to do the same to unlocked devices.
My ROM version is: NPPS25.137-33-6 (yeah, there is an "S" that I don't find in the roms available here)
The baseband is: M8937_8000.122.02.45R
(CEDRIC_BRAZILDSDS_CUST)
I was thinking in loading the rom into internal memory, reboot in recovery mode and flash the rom using the option "Install package from zip".
Do you know if it would work without an unlocked bootloader. Is it safe?
Thank you for the help,

Don't know if you can flash the boot logo without an unlocked bootloader but if you can here it is
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files (Google to learn howto install Android sdk) & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
If you can't then you have no option but to wait for Motorola to fix it if you really haven't modded your phone

TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
https://community.verizonwireless.com/thread/921991

hoferbr said:
TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
/QUOTE]
I have the same problem as you. Could you fix it?
Thank you,
Luciano
Click to expand...
Click to collapse

You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.

p8tgames said:
You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.
Click to expand...
Click to collapse
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!

hoferbr said:
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!
Click to expand...
Click to collapse
you can flash what ever you want in fastboot -
However - In terms of firmware, if you are trying to flash incorrect firmware then the verification check will fail and it will not flash
Just don't flash a new bootloader if you are worried about it - its not needed unless you are upgrading an android version and that version has an updated bootloader

So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?

hoferbr said:
So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?
Click to expand...
Click to collapse
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot

TheFixItMan said:
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot
Click to expand...
Click to collapse
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.

jdonadel said:
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.
Click to expand...
Click to collapse
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version

TheFixItMan said:
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version
Click to expand...
Click to collapse
Yeah, I see that, but looking into the stock rom .zip file I cannot find the correct ID that matches to my. But since I posted the reply, I´ve downloaded from a mirror in lolinet, and correct flash my phone.

Global OTA 9.5.4.0 + TWRP = fail

My phone has unlocked bootloader, TWRP, and is rooted with magisk. Got the OTA for (global) 9.5.4.0 last night - it downloads/de-crypts ok, reboots into TWRP, and then fails to flash. I also tried to flash manually via TWRP by locating the downloaded file, still fails. During the night, it rebooted itself (to try again I suppose), and my alarm didn't go off.
So here I am, late in work, wasting more "work time" to ask you for a possible solution :angel:

Go back to original miui recovery then you can update your miui successfully. After update,reflash twrp and magisk.

jimandy60 said:
Go back to original miui recovery then you can update your miui successfully. After update,reflash twrp and magisk.
Click to expand...
Click to collapse
Sounds easy, but I don't know how to do that. Could you point me in the right direction?

you can't flash an OTA with TWRP

Flash recovery img with fastboot
Code:
fastboot flash recovery recovery.img
then boot your phone
settings->about phone->system update->update
it will get in origin miui recovery and update system automatically
after update finished,reflash twrp and magisk

Thank you very much @jimandy60
With all the respect though, I would prefer downloading the file from a popular location. Is there any way to find this hosted somewhere else, maybe by Xiaomi?

ang3l said:
Thank you very much @jimandy60
With all the respect though, I would prefer downloading the file from a popular location. Is there any way to find this hosted somewhere else, maybe by Xiaomi?
Click to expand...
Click to collapse
maybe try this site?
en.miui.com

Hello!
I got the same problem but instead to come here and ask for help I tried to solve myself. I downloaded the lastest TWRP version and the device was not going into recovering mode. Then I installed again the previous one without results. I downloaded the TWRP app from Play Store and trying to solve I made wipe data, cache and I am not sure but I think also choose wipe system. Now my phone is stuck on the fastboot screen. Does not start. Using ADB I installed back the stck recovery but the problem remains. Somebody can help me please?

reflash the full rom?
download&unzip full rom package,get in fastboot mode and run flash_all.bat

Check out my guide here:
https://forum.xda-developers.com/mi-mix-2/how-to/guide-mi-mix-2-unroot-restore-recovery-t3770690
It has all the steps and files you will need to go from rooted stock MIUI Nougat to rooted stock MIUI Oreo applying the OTA update

colorado_al said:
Check out my guide here:
https://forum.xda-developers.com/mi-mix-2/how-to/guide-mi-mix-2-unroot-restore-recovery-t3770690
It has all the steps and files you will need to go from rooted stock MIUI Nougat to rooted stock MIUI Oreo applying the OTA update
Click to expand...
Click to collapse
Thanks, I'll take a look.

Pie root, twrp fail, odin fail and Emergency Recovery Function

Hi, community
I tried to root my SM G-9600 but it all went wrong. First i went on twrp, it worked, but wiped my entire data. Then i tried make a factory reset o installation with odin and the latest firmware for my device, but it failed and showed this message labeled in red color: "sw rev check fail device 4 binary 3 error". then i found in this and other forums that it was because i used not the latest firmware. I downloaded the latest one, tried once to flash it via ODIN, and it failed again. Then when it restarted this message was shown : " An error has occurred while updating the devide software. Use the Emergency recovery function in the Smart Switch PC software. I donwloaded the smart switch, installed it, plugged my devide, but it shown that my device was "Unsupported". IDK what to do by now, so i need help from anyone on this forum. PLS
Greeting from Peru.

i had the same problem
(before processing to the next step try to redownload the firmware, i think i was using an old firmware and this is why i got this error)
i am assuming that you can not boot on twrp recovery
that's not a problem , you need to install twrp via odin and boot directly to it....
format the data and connect to your laptop (if it does recognize the phone but there is no storage dont worry, just reboot again to recovery (there is an option on reboot tab))
since you already tripped the knox just flash a custom rom, boot and set it up, and then try to flash stock image via odin as normal.
and sorry for my bad english.

Cant install a custom rom
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)

dimitrispas22 said:
i had the same problem
(before processing to the next step try to redownload the firmware, i think i was using an old firmware and this is why i got this error)
i am assuming that you can not boot on twrp recovery
that's not a problem , you need to install twrp via odin and boot directly to it....
format the data and connect to your laptop (if it does recognize the phone but there is no storage dont worry, just reboot again to recovery (there is an option on reboot tab))
since you already tripped the knox just flash a custom rom, boot and set it up, and then try to flash stock image via odin as normal.
and sorry for my bad english.
Click to expand...
Click to collapse
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)

Stevie1997 said:
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)
Click to expand...
Click to collapse
do you want to install a custom rom or revert back to stock?

For custom ROM I suggest Soldiers ROM here's the link to the thread. https://forum.xda-developers.com/ga...g96xf-fd-n-stock-rom-soldier9312-1-0-t3771346 . You can more information about it on the thread. Been using the moment I rooted my phone.

Xspidera said:
For custom ROM I suggest Soldiers ROM here's the link to the thread. https://forum.xda-developers.com/ga...g96xf-fd-n-stock-rom-soldier9312-1-0-t3771346 . You can more information about it on the thread. Been using the moment I rooted my phone.
Click to expand...
Click to collapse
i think he is out of lack it looks like he doesn't know exactly his model snapdragon samsung devices are different from our g960f exynos version and it may brick his device
i think hes only option is to flash the stock firmware and yea just that....