[Q] [HELP] Boot loop - cant mount efs [partly solved] - Galaxy Note II Q&A, Help & Troubleshooting

Hi guys,
first ill try to explain how I got where I am right now.
Sometimes my Phone gets so low in power it just shuts down, after plugging in the power it will show a charge icon for a few seconds and it will automatically try to boot again, once finally booted it shuts down again due to the lack of power.
What I normally do to fix this is go into recovery or download mode because this uses far less power and so I can charge it to like 5 or 10 percent and boot normally.
This time after charging it to 5 or 10 percent it wont boot at all and it's looping. I allready reinstalled my current Rom (Omega V29) but still no normal boot. After a full whipe and installing V30 I still cannot get beyond the boot animation.
what I tried:
- Reinstalling the same Rom I'm using for months.
- Full Whipe
- Install V30 ROM
- removing Sim and SD card
- Now trying to go back to stock using Odin.. also not working..
Is there anyone out there who has any ideas left for me to try? :'(
thanks in advance!
one more thing! If I get this phone running again I would be very happy if someone could show me a method to disable the autoboot. I remember my previous phones could just charge without automatically trying to boot the device.
>> I found out that after installing the ND3 bootloader it will not autoboot, so that's one step in the right [email protected]

One important information missing:
What's your current firmware, especially bootloader.
Then: what firmware have you tried to flash thru Odin?
What recovery/version do you work with?

current firmware:
Omega v29 (27/05/2014):
Based on firmware XXUFNE1 Android 4.4.2 (Date: 06/05/2014)
current bootloader:
MJ5
Firmware I tried flashing to solve the problem:
Omega v30 (19/09/2014) Based on firmware XXUFNG4 Android 4.4.2 (Date: 30/07/2014) USING RECOVERY
DN3_v5.5_N7100_2nd_september.zip USING ODIN
Latest stock rom USING ODIN
bootloader I tried flashing to solve the problem:
N7100_KK_ND3_BL.tar.md5
Recovery I'm using:
TWRP latest
Recovery I tried:
CWM latest
also the error "E: Unable to mount '/efs' " displays when i try to factory reset using TWRP

I found out that somehow my efs was corrupt. Unfortunately I did not have a backup.
I did however found a working efs backup on the internet which I flashed using Odin. Now the Phone boots and I have a IMEI number that is not correct. So last step is to fix the IMEI number and I should be back in business.

Related

[Q] Note II stuck at Samsung Logo durring boot

I am trying to fix a Samsung Note 2 (Model No. SGH-i317) that refuses to boot.
When you push power, the white Samsung logo appears and just stays there until you pop the battery and remove USB power.
It will not go into the recovery menu after pushing Power+VolUp+Home.
It will however go into download mode after pushing Power+VolDn+Home. Once in download mode I tried to update the kernel to no avail. I also tried to install CWM thinking that maybe installing a new recovery over an old stock one that was corrupted somehow might help. Both approaches did nothing.
The device was originally running stock Samsung; I never attempted to load another ROM until this problem hit. So the phone was just as it was from the factory two years ago when this problem recently hit and I have been trying to fix it. After trying to flash the aforementioned things, the counter on the download screen (i.e. Odin), now shows the number of different times I have tried to update the recovery or the kernel, which is currently at four or five.
So, some aspects of the phone are working but clearly not enough for me to even get it to recovery, let alone boot. Any advice? Many thanks in advance.
roll-back said:
I am trying to fix a Samsung Note 2 (Model No. SGH-i317) that refuses to boot.
When you push power, the white Samsung logo appears and just stays there until you pop the battery and remove USB power.
It will not go into the recovery menu after pushing Power+VolUp+Home.
It will however go into download mode after pushing Power+VolDn+Home. Once in download mode I tried to update the kernel to no avail. I also tried to install CWM thinking that maybe installing a new recovery over an old stock one that was corrupted somehow might help. Both approaches did nothing.
The device was originally running stock Samsung; I never attempted to load another ROM until this problem hit. So the phone was just as it was from the factory two years ago when this problem recently hit and I have been trying to fix it. After trying to flash the aforementioned things, the counter on the download screen (i.e. Odin), now shows the number of different times I have tried to update the recovery or the kernel, which is currently at four or five.
So, some aspects of the phone are working but clearly not enough for me to even get it to recovery, let alone boot. Any advice? Many thanks in advance.
Click to expand...
Click to collapse
Try to odin the stock firmware then before it boots up boot into recovery and wipe dalvik and cache then boot it up.
Flashing Kernel did not help
cnote74 said:
Try to odin the stock firmware then before it boots up boot into recovery and wipe dalvik and cache then boot it up.
Click to expand...
Click to collapse
I run Linux and don't really have access to a Windows box and have been using heimdall to flash things. When you said
"Try to odin the stock firmware"
Click to expand...
Click to collapse
is that the same as trying to loading a kernel image and then going to recovery before it fully boots? If so, I tried that with the following command using the image I downloaded from sammobile.com. This is the command that I ran:
Code:
heimdall flash --kernel KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 --verbose
That resulted in the same as when I tried to flash a new CWM recovery. It doesn't allow me to access the recovery, it just boots and shows the white Samsung logo and hangs there till you pop the battery & remove the USB cable.
If what you are suggesting is something different than the flash that I did with the image from sammobile.com, please let me know. This is my first attempt to fix something like this. Many many thanks.

problems

Hi,
Hi I was given an s3 sprint. It doesn't get past the sprint screen, but when plugged in it goes all the way until played with then it'll reboot. It does however go into download and recovery mode which leads me to believe its a software problem. The phone is not rooted/ fully stock. Could someone walk me through rooting, installing custom recovery and ROM via Odin? Also there seems to be no water damage. Per download mode:: binary-samsung official
System satus-official
Qualcomm secure boot enable
Warranty-0
Bootloader ap swaev-2
PS I already tried Odin but failed at aboot mbn. Now upon booting it reads ... firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?
Pleas ask in here instead. Also first get the phone working by either flashing it using kies 2.6, or by using odin and flashing this image. Be sure to unzip it first.

Bootloops After ODIN back to Stock Firmware

Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
kswa1987 said:
Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
Click to expand...
Click to collapse
You probably need to do a factory reset
In the future you should make a full backup before installing a rom
kswa1987 said:
Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
Click to expand...
Click to collapse
AHH!! Sorry to have made this post... here's what I did to get it actually boot:
reflahed the stock firmware through odin again, tried to reboot, it failed, obviously. rebooted to recovery, factory reset in recovery, power down option in recovery, then turned the phone on again and it magically worked!
hopefully this post will help someone who encountered the same issue
eousphoros said:
You probably need to do a factory reset
In the future you should make a full backup before installing a rom
Click to expand...
Click to collapse
thank you so much for the quick reply, I ended up figuring out the solution while you were typing. sorry to pull you away from other tasks. I have several backups saved to my PC but thank you for the reminder!! :laugh::laugh:
kswa1987 said:
AHH!! Sorry to have made this post... here's what I did to get it actually boot:
reflahed the stock firmware through odin again, tried to reboot, it failed, obviously. rebooted to recovery, factory reset in recovery, power down option in recovery, then turned the phone on again and it magically worked!
hopefully this post will help someone who encountered the same issue
Click to expand...
Click to collapse
I had the same excat same thing happen when flashing this via Odin. I didnt need to Odin stock twice though . I just booted stock recovery and did a factory reset. After that I went ahead an powered down and rebooted . All good now
How long did you have to wait in the stock recovery to get past the "installing system update" screen? Mine just sits there and I'm unable to view other options in recovery.
EDIT for noobs (like me): wait 30 seconds on the "installing system update" screen.
I'm still stuck in boot loop
Im in the same exact situation , but I'm still stuck in boot loop. I followed your restore instructions and nothing. Please help.
Creel711 said:
Im in the same exact situation , but I'm still stuck in boot loop. I followed your restore instructions and nothing. Please help.
Click to expand...
Click to collapse
Looks here, may apply to your case. http://forum.xda-developers.com/showthread.php?p=63226466
Pp.
I initially used odin to flash OI1 update, after a rom I was using caused problems and I got bootloop. It changed bootloader value to b:3 and I'm unable to downgrade now so I used smart switch which didn't recognize device so used emergency recovery and still bootloop. I have factory reset and wipe cache multiple times along with adb side load and individual flashes of bootloader, modem, kernel, flashed custom kernel and twrp to access fix permissions and to mount partitions with advanced wipe etc and still wont boot past logo. Also during one fix attempt phone said can't mount system.. Idk I'm not understanding where the problem is .everything says successful but I'm still in bootloop. Please help. I've spent hours everyday for the past week searching & trying different things that seem might help so open to any suggestions.
Problem with Samsung Galaxy S4 Mini GT-I9195
Hi everyone
I'm new to the whole ROM flashing and using Odin. I had a bootloop problem and recovery mode showed all the options but has a green android man laying down with red icon above him and No Command below the android man. Tried the factory wipe and cache wipe but it gives some red writing with the word failed in the coding and the word error under the android man. Tried to flash a stock ROM from sammobile using Odin. Odin gives a pass but the same problems persist. Can someone please help?
any solution, i have this problem to? only bootloop, nothing else. Updatet bootloader with 4up
kswa1987 said:
Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
Click to expand...
Click to collapse
had the same issue ... did a factory wipe...(had lineage os 14 installed with gapps 7.1.1) flashed stock rom using odin(success) . stuck in bootloop(samsung logo fades in and out) pleaase help (sm-g900H)
Very usefull post, same issue, solved trough recovery->wipedata/factoryreset. Thanks!!!!
my s6 was freezing and restarting again and again, I reinstalled the firmware for odin and then it didn't encounter any problem for a whole day but now i have the same problem again - freezing and restarting
any help would be appreciated
I am already done with factory reset and wiping cache partition but still nothing turnout to be helpful
Hi Please help me.
I did everything that mentioned but no succes at all. Any new suggestion?
Btw my phone passing ODIN and stuck in "installing system updates then erasing"
hello
i need downgred g925t frome androide 7 to 6 or 5.1.1
can anyone help me
im flashed phone whit dis frimwer from anroide 7 G925TUVS6FRC1_G925TTMB6FRC1_TMB
im dawnloaded this frimwer 4Files-G925TTMB3EPD1-6.0.1-By-NoLoGiG but not work or not flashed have error

LG G4 boot loop into TWRP

Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
If you can reach download mode you could try reflashing back to stock then starting again.....Hope you get yours fixed - Sorry to say this but mine did a very similar thing only 24 hours before you posted!!! Only mine was on stock FW and was in use at the time - I've now had to swap it as valuebasket who sold me the phone have ceased trading. If yours is a UK model you may be able to get it replaced under warranty - believe that LG guarantee their phones for 2 years and a ruling by the European court said that flashing a custom rom doesn't invalidate any warranties.
I have the same exact issue, I also flashed the latest CM14 nightly and cannot get the device to boot any rom.
I have even tried flashing stock rom but I get the same problem.
From what I have read, the bootloop issue happens once the device boots but I don't seem to be getting that far.
Any ideas?
Ran into the same problem 3 days ago. This is the first time I have encountered a non-revertible issue in 3 years as a cyanogenmod user. This changes my opinion on how safe it is to make use of a custom ROM. I tried to wipe everything, reinstall TWRP, change TWRP with another recovery, reinstall a safe NAND backup of mine.....nothing.....it went into boot loop. Before I read this post, I was convinced my phone encountered the infamous G4 bootloop problem.....now I see there are other examples, so it shouldn't be the case. Long story short, I had to check my device in at the LG assistance, with 25 days as time forecast.
The guilty nightly was 20161205.
I have never seen anything like this...
This has solved it for me - I installed LG Bridge and flashed the factory firmware using the tool. Now it seems I'm back on stock but at least it's working.
got mine working. I had to install LGUP and flash stock ROM. Once flashed I installed CM14 and I am back up and running again.
I tried LGUP but it could not recognize the device while this was looping.....a bad experience......
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. I did a cyanogenmod update from within cyanogenmod, which just booted into twrp, then I manually installed the update zip that cyanogenmod had downloaded, then it always boots into twrp. I wonder if initiating the update from within cyanogenmod was the cause. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Well. Mine got stuck in bootloop for the second time today. What is going on? In between the two bootloops I had one good update with CM. Using TWRP 3.0.2.1. Steps to reproduce failure: updating CM from within CM, it autoreboots into TWRP and after that nothing happends, no autoinstall. Then after a manual install of the new CM the bootloop starts.
Resolve the problem:
* Install LGUP 8994 DLL Ver 0 0 3 23, Install LGUP Install Ver 1 14, get the latest KDZ
* Get the phone into download mode with usb cable and after that in firmware update mode
* Startup LGUP and choose refurbish and select the kdz file.
* After that you can boot into your stock LG firmware again, reinstall TWRP an CM. If you want so.
Read that it is advised to manual update cm from within TWRP. TWRP will get an update in the future to solve this bootloop problem.
iankelling said:
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. After a cyanogenmod update, it always boots into twrp. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Click to expand...
Click to collapse
I second that. Same issue and neither LG Up nor LG Bridge will recognize my device. Looking in device manager there are no serial interfaces. Do I need a special driver that provides a com port for a phone in recovery or fastboot mode?
---Edith 2016-12-12: Found a solution for my issue:
The phone has to be in _download_ mode, not in recovery or fastboot. After realizing that I have to boot the phone in a different manner, it will be recognized by LG UP.
Here is how to boot the pone in download-mode:
- Power off your LG device.
- Press and hold Volume Up button.
- Connect your device to PC with a USB cable while holding the Volume Up button.
- You’ll boot into download mode with “Firmware Update” written on top of the screen.
Now everything is fine again.
croclacrimae said:
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
Click to expand...
Click to collapse
I was able to get out of that by also wiping by-name/misc. Don't do that, though, because then your wifi mac address will get messed up and you'll spend all day looking for a permanent fix for that.
I suggest reflashing a stock KDZ using LGUP, as others have said. You can get the usb drivers from LG Bridge.
I will release a fix for that soon. Check the twrp thread for updates on this.
Hi
I also have this problem
I installed cm-14.1-20161201-NIGHTLY-h815 successfully and was running it for almost 2 weeks without issues, today I updated to cm-14.1-20161213-NIGHTLY-h815 from cmupdater and I have been ending up in recovery every time I rebooted.
I tried flashing the latest cm recovery and reflashing the rom, with full wipes but no luck.
Full steps of recovering would be appreciated (for example, there are comments about flashing the latest stock rom, but a link to this rom would be helpful)
Thanks
Good news regarding this:
http://forum.xda-developers.com/showpost.php?p=70082901&postcount=213
The above will fix TWRP bootloop issues as well and I also released a first h811 version which should allow installing CM etc as it should.
Keep in mind that this is a BETA and not an official TWRP release.
Please report back in the above thread!
.
Does your twrp beta really fix the boot loop even it is already happening. What do I have to wipe? I have not managed to get out of the boot loop despite intalling it.
Is using using LG Up to flash to the stock rom really the only option?
Edited 2017-01-25 2:45 pm:
Well, sometimes you just have to be patient. Powered down the phone and when th H815 restarted CM did boot. Great. :good:
Hey, I just want to share a small detail, possibly a fluke that helped me overcome the bootloop.
So...I started with a fresh, stock H815, I don't quite remember the firmware version..it was something like version "20g"..
OK, I looked up several guides and tried to get the newest stable versions of each tool. I went through with the official bootloader unlock, then moved on to rooting: Kingroot didn't work for me so I went on installing twrp in fastboot mode so I could afterwards install supersu and root.
I got there eventually but first I was stuck in bootloop - kept ending up in twrp interface. I found the 2 dd commands but those didn't work for me as the msm_sdcc folder did not exist, but instead there was a "f9824900.sdhci". Tried to overwrite this one ...but as others have stated as well, it didn't work.
At that point, I had nothing to lose, I was starting to accept that I had soft-bricked my precious G4 so..I went on installing the DU 10.6 7.1.1 rom and the stock gapps, wiped dalvik, rebooted and held my breath...not literally
About 12 minutes later, after an endless red, spinning logo, my shiny ping pong paddle showed me a different screen, a fresh start welcome screen .
Almost 24h / 10-12 reboots (twrp included) / 70+ apps installed and removed later, the new OS holds around 2G ram average, a bit better battery life, smoother transitions, flawless navigation, flush streaming over both 3G/LTE & 2.4/5 G wifi.
FYI the reboots were intended, wanted to see consistency in boots - we're in the green . Now testing long term stability with moderate/high usage.
There is 1 aspect I noticed, there are a couple of contexts when the interface burps (several menus, various situations, never in apps) and resets back to homescreen...but I think that's more of a launcher topic than an OS one.
Other than that, so far I'm happy with the mod.
Hope my experience helps others that might be in the same spot I was or at lest boosts their confidence to try out a decent idea they might be pondering.

Weird n7100 bootloop

Hi i was helping my friend to update his firmware. after doing so the phone is now stuck in a weird bootloop. i had seen my fair share of bootloops but this seems weirder than others. the n7100 logo would loop very quickly (sorta like flash) and keeps doing so. can't enter recovery mode at all, only download mode. plug it to odin and whatever i can throw at it i just got nand write start fail, be it twrp, multiple versions of stock rom. im at the end of my wits, so what should i try next? thank you for any input
What is the Odin error when trying to flash the latest stock ROM from sammobile.com? Tried different USB cables and USB ports?
I kinda have/had the same problem.
N7100 logo would bootloop quiet fast (doesn't get to the point where it should load the rom).
Can't enter recovery bc of that.
Only thing that works is download mode.
After trying to flash newest stock rom (4.4.2) it failed once (I think my cable gets too old...)
Next try it worked without a problem.
Problem persists.
Next step was flashing an older repair firmware (4.1.2) but it failed (I think bc of the 4.4.2 bootloader? IDK)
Then I tried to flash the newest stock again but with the pit file. Flashed without a problem but the problem was still there.
Last step I made was to flash the newest stock with the pit file and nand erase + update bootloader.
Tried it 2 times but it failed.
Now I'm stuck on the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Download mode got a red message also: "RPMB: INVALID RPMB DATA"
I don't know what to do now. Please help.
PS: It was a "new" motherboard from aliexpess, it had a chinese version of the stock 4.1.2 if I remember right and was already rooted when I installed it. I wanted to flash the newest 4.4.2 for the new modem and stuff and then upgrade to lineage. :/

Categories

Resources