Database Users

[Ref][Guide] Galaxy Note N7000 Factory Firmware Restore

This is just like any other guide that tells you how to restore your phone to factory...
Please Note All User Data Will Be Lost
Recommended Battery is Fully Charged..
Requirement:
Odin3 1.85 (Download links Attached)
Window Drivers [32bit] or [64bit]
MicroUSB data cable for phone
Firmware files for mobile phone
Phone Obviously....
GB Firmwares: (if password required its "samfirmware.com")
-N7000DXKK1; N7000DXKJ3; N7000OLBKJ6
-N7000JPKJ4; N7000XXKJ4; N7000OJPKJ3
-N7000JPKK2; N7000XXKK5; N7000OJPKK2
-N7000XXKJ4; N7000XXKJ4; N7000PLSKJ3
-N7000XXKJ1; N7000XXKJ1; N7000OXAKJ1
-N7000XXKJ4; N7000XXKJ4; N7000OXAKJ4
-N7000XXKJ4; N7000XXKJ4; N7000XEOKJ1
-N7000XXKJA; N7000XXKJ4; N7000OXXKJ8
-N7000XXKK9; N7000XXKK5; N7000OXAKK9
-N7000XXKKA; N7000XXKK5; N7000OXXKK5
-N7000ZSKK1; N7000XXKJ6; N7000OZSKK1
ICS Firmware (Official)
N7000XXLPY (Single File Load in PDA)
N7000ZSLPF Build: 15.05.2012
FIRMWARE NAME DECODE
Warning: Don't Do This For Fun... could make your phone a nice paper weight..... use only if NEEDED.... I'm not responsible for any mistakes.... The Risk is YOURS!!!
PIT Info:
Changing PIT file (repartitioning ROM) will not affect mobile phone's speed.
PIT files will repartition the mobile phone's ROM (Read-Only Memory). Changing (repartitioning the ROM area) will modify only the space trade between the /system and /dbdata.
What is CSC?
CSC = Country Sale Code
CSC code depends on the region where the phone was sold.
CSC contains the phone settings (internet, wap, mms...), specific applications which available in certain regions, and operator customizations.
CSC code could be changed by flashing a new firmware (including CSC file) on phone. That will change phone language and settings.
Use *#272*IMEI# code on phone to view the list of the available CSCs, or change CSC. (Changing CSC will erase the phone!)
Lets Get Started..
1. Install Samsung USB drivers (in most cases already installed)..
2. Enter Download mode by pressing Volume down, OK and power buttons at the same time. Phone will start in Download mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Press Volume Up..
4. Connect phone to USB cable. (Windows will install if needed).
5. Run Odin Software
6.If repartition is needed, Press PIT button to select .pit file. (Choose The Correct one for your phone internal memory size 16 or 32 GB)
7. Flash Bootloader If Needed, Enable Phone Bootloader Update then press Bootloader button to select bootloader file (filename: KERNEL_... .md5). (Important: Changing / flashing wrong bootloader could damage the phone!)
8.Press PDA, then select PDA file (filename: CODE_... .md5).
9. Press PHONE, then select PHONE file (filename: MODEM_... .md5)
10.Press CSC, then select CSC file (filename: ...-CSC-... .md5).
11. Verify Odin software recognize phone. When the phone is recognized, ID:COM is highlighted in yellow Note: the number can vary(if not repeat steps 2.)
12.Press Start button to begin flashing procedure.
13. Wait a few minutes flashing procedure to complete, This Can Take Some Time.... Plz Be Patience.....
Once Completed PASS! will appear on the upper left corner, and it will be highlighted in green.
---------------------------------------------------------------------------------------------------
Note: if only one file is in firmware download load in into PDA Section leave the rest empty and off as default

hello cannot download one of your roms

brockyneo said:
hello cannot download one of your roms
Click to expand...
Click to collapse
sorry try again links fixed

antiguangenius said:
sorry try again links fixed
Click to expand...
Click to collapse
thank you why do you think this will work for our bricked devices
also are all the files like bootloader and kernel all with the rom download i really hope this works thank you

brockyneo said:
thank you why do you think this will work for our bricked devices
also are all the files like bootloader and kernel all with the rom download i really hope this works thank you
Click to expand...
Click to collapse
read whole post carefully....

Thanks a lot mate, I've finally recovered my phone

Last resort actions always...pit & bootloader flashing. does the ics update require these?

Avlrln said:
Last resort actions always...pit & bootloader flashing. does the ics update require these?
Click to expand...
Click to collapse
dude this guide is all about factory state... in other words GB

Thank You!!!

not work in my case do same as he mantion
brockyneo said:
thank you why do you think this will work for our bricked devices
also are all the files like bootloader and kernel all with the rom download i really hope this works thank you
Click to expand...
Click to collapse
not work in my case do same as he mantion

.pit file
.PIT file is used for full flashing method, this is only advisable and useful for reverting back to original firmware when previously installed unofficial ROM or to fix softbricked devices like unable to boot normally.

I hope not to be OT in this thread and sorry for my bad english.
I would like to ask a question about the recovery / download mode.
It is necessary that the device is turned off before using the specific combo? (vol. up/down + home + power)
Can I go into recovery mode even when the terminal is already on?
If not, why?
Thanks in advance

posalaquaglia said:
I hope not to be OT in this thread and sorry for my bad english.
I would like to ask a question about the recovery / download mode.
It is necessary that the device is turned off before using the specific combo? (vol. up/down + home + power)
Can I go into recovery mode even when the terminal is already on?
If not, why?
Thanks in advance
Click to expand...
Click to collapse
You need to switch off first, otherwise it will just bootloop rather starting in recovery.

posalaquaglia said:
I hope not to be OT in this thread and sorry for my bad english.
I would like to ask a question about the recovery / download mode.
It is necessary that the device is turned off before using the specific combo? (vol. up/down + home + power)
Can I go into recovery mode even when the terminal is already on?
If not, why?
Thanks in advance
Click to expand...
Click to collapse
Are you asking if you can go into Recovery or Download mode when your phone is on,ie,w/o switching it off?
Yes you can.For recovery mode press up volume+home+power(strangely enough any combo works.power+home+volume but keep them pressed till the phone reboots and you see the Samsung GT-N7000 logo then u can let go.
For Download mode press down volume+home+power(again in any combo)
Hope i answered your question

dr.ketan said:
You need to switch off first, otherwise it will just bootloop rather starting in recovery.
Click to expand...
Click to collapse
I already tried going into recovery mode with the phone turned on without bootloop problem!
I'd like to know if this is a correct procedure or not, because there are people who say they can usually do.
---------- Post added at 08:01 PM ---------- Previous post was at 07:33 PM ----------
zeeshanonlyme said:
Are you asking if you can go into Recovery or Download mode when your phone is on,ie,w/o switching it off?
Yes you can.For recovery mode press up volume+home+power(strangely enough any combo works.power+home+volume but keep them pressed till the phone reboots and you see the Samsung GT-N7000 logo then u can let go.
For Download mode press down volume+home+power(again in any combo)
Hope i answered your question
Click to expand...
Click to collapse
Yes!
Thanks a lot.

Lots of people have bricked their phone while repartitioning and using PIT.
I would say read carefully when you try it.
If I ever get superbricked I'd just kill it with Angelom test kernel or if I want to return to clean state - I'd flash any safe kernel - perform factory reset, format system partition and sd card then flash latest stock firmware available for my region.

doesn't work
it stops by "Hidden"
<ID:0/005> factoryfs.img
<ID:0/005> hidden.img
I let it for 1 hour, but it's not working... Can someone tell me what I'm doing wrong

Galaxy Note GT-N7000 Modem locked
My Galaxy Note GT-N7000 I purchased this Cell phone in europe it was not working as 3 G on Tmobile I flashed modem, after that I was not able use as cell when I try to call getting insert the SIM card. My SIM is there please Help

Hey i managed to use the odin software to load the gb firmware onto my phone but now when i tr to boot up the phone just hangs at the smasung logo. did i do something wrong or do i need to load something else onto the phone using odin?

lolgical said:
Hey i managed to use the odin software to load the gb firmware onto my phone but now when i tr to boot up the phone just hangs at the smasung logo. did i do something wrong or do i need to load something else onto the phone using odin?
Click to expand...
Click to collapse
Reboot into recovery and wipe cache and data.

[Solved] Stuck in Boot Loader

* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files please.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Image of recovery that I can not get to.
Current state of device. can not get anywhere else.
Close up of date.
Picture of odin failing. I tried to flash using the option called PDA by the way.
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
solved - cant find where to set this thread to solved thought.
Any help is greatly appreciated.

Nyreb said:
* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files please.
View attachment 2637629
Image of recovery that I can not get to.
View attachment 2637596
Current state of device. can not get anywhere else.
View attachment 2637598
Close up of date.
View attachment 2637611
Picture of odin failing. I tried to flash using the option called PDA by the way.
View attachment 2637622
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Shoot me a email at [email protected]... We can talk more about your issues there..... Thx lj

Solution
Thanks to lj50036, my nexus now actually works.
Here's what he told me to do:
----------
1.) start here http://forum.xda-developers.com/showthread.php?t=2588979
This will install abd fastboot and the drivers for your tablet just follow instructions.
2.) Now open cmd as admin and type
fastboot
should see commands and options listed
3.) now type
cd /
this will move root to c drive.
4.) plug in tablet, boot into bootloader (holding down power, volume up and down I think) and type
fastboot devices
this output serial number of device and then type of device (Fastboot)
5.) go to https://developers.google.com/android/nexus/images#mantaray or google factory images and find Nexus 10. use what ever version you want. download, unzip and you should see something along the lines of this (the kot49h will be what ever version of the image you used.)
6,) move everything but the 2 .sh files to root of c drive (c:/)
and then in cmd prompt type
dir
this will print out file names, data, and other information of c:/. make sure you see the 3 files you moved from the factory image you unzipped.
7.) if so, make sure tablet is in bootloader still, and type
flash-all.bat in cmd prompt.
--About halfway through it reboots your nexus and because my nexus wont reboot its self, and will only come on when its plugged into wall outlet for a bit, I just did that and plugged in and it worked fine.
-- once the whole process runs, my nexus rebooted into recovery mode, and after a minute rebooted correctly and I was able to start setting up.
----------------
Thank you again to lj50036

@Nyreb
Change the forum name to include (SOLVED)

@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.

spudsmac said:
@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.
Click to expand...
Click to collapse
Shoot me a email.... Sounds like you need some help....

So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!

spudsmac said:
So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!
Click to expand...
Click to collapse
What happen in android some time, and I may be way off in left field here but, it has happened this way on the tf700, tf300, tf201, and the nexus 10... Just what I have help people with is that....
The storage no matter what command you issue in fastboot e.g
Code:
fastboot erase boot
fastboot erase system
fastboot -w
It just will not erase everything, and by doing these commands your really only telling the tab and or phone that you are going to be putting other
data in those partitions, so if you just flash exactly what was already on the tablet it does not like it...
@spudsmac had upgraded to 4.4.2 and was trying to install cm11 when things went wrong
So by us trying to reset the tablet to factory 4.4.2 firmware it would not take it... Just froze at android guy with x
So when, we went one version older on the firmware... Magic happened and he was golden....
Thx Josh

Yoga Tab 2 8" 830f failed update led to soft lock

So I downloaded a 16mb OTA update and let the tablet do its thing without touching it. I waited for the tablet to boot up, but it was stuck in a black screen for about 12 minutes until I decided to turn it off and on. It didn't work, so I went to the recovery to do a factory reset and clear the cache, but it still didn't work. I later went to this Russian forum here from this thread. I downloaded a lollipop rom and proceeded to flash it using Phone Flash Tool Ver. 5.2. It went well until 16% in where it failed. Unfortunately, I don't have a screenshot of this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(image of the files in the rom I downloaded)
After all this happened, I tried to start it up but I got the message "Boot Failed. EFI Hard Drive. Boot Successful - Enter Setup"
And now it won't go into recovery mode, but it does go into fastboot and bios setup.
Since it does go into fastboot, I tried to use a tool from this thread (Temp recovery) to use a temporary cwm recovery to hopefully be able to at least boot into that, but that didn't end up working.
I got another rom from the same Russian site that had differently packaged files but still the same stock lollipop rom.
I tried to just use the recovery from there to manually flash it using fastboot, but it still failed.
I later found this thread with these instructions for this problem.
1. download and extract this file someplace on your pc
2. uninstall your existing Phone Flash Tool and from the drivers folder install both files (Intel Phone Flash Tool and Android Driver accepting defaults) reboot pc when finished
3. place your tab in DNX mode (from power off press and hold both volume keys then press pwr to start, in a few you screen will show "Fastboot starting..." message and hang on that. you must get that message on your tab screen, restart from power off until you have it)
4. start the installed Phone Flash Tool and load flash.xml from the extracted YT2-830L... folder then Start Flashing, it will reboot when done
Click to expand...
Click to collapse
The file he linked in his post (ionioni ) was gone but I still tried to do this with the roms I had. And guess what? It still didn't work. The instructions said to place the tablet in DNX mode (meaning fastboot), which I did do...only when I put it into fastboot, it was set to DNX_OS which came to say "Wrong device state" in Phone Flash Tool.
I've tried what I could, but failed. Anyone have any suggestions?

AgentXGhost said:
So I downloaded a 16mb OTA update and let the tablet do its thing without touching it. I waited for the tablet to boot up, but it was stuck in a black screen for about 12 minutes until I decided to turn it off and on. It didn't work, so I went to the recovery to do a factory reset and clear the cache, but it still didn't work. I later went to this Russian forum here from this thread. I downloaded a lollipop rom and proceeded to flash it using Phone Flash Tool Ver. 5.2. It went well until 16% in where it failed. Unfortunately, I don't have a screenshot of this.
(image of the files in the rom I downloaded)
After all this happened, I tried to start it up but I got the message "Boot Failed. EFI Hard Drive. Boot Successful - Enter Setup"
And now it won't go into recovery mode, but it does go into fastboot and bios setup.
Since it does go into fastboot, I tried to use a tool from this thread (Temp recovery) to use a temporary cwm recovery to hopefully be able to at least boot into that, but that didn't end up working.
I got another rom from the same Russian site that had differently packaged files but still the same stock lollipop rom.
I tried to just use the recovery from there to manually flash it using fastboot, but it still failed.
I later found this thread with these instructions for this problem.
The file he linked in his post (ionioni ) was gone but I still tried to do this with the roms I had. And guess what? It still didn't work. The instructions said to place the tablet in DNX mode (meaning fastboot), which I did do...only when I put it into fastboot, it was set to DNX_OS which came to say "Wrong device state" in Phone Flash Tool.
I've tried what I could, but failed. Anyone have any suggestions?
Click to expand...
Click to collapse
This is the file you need https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view
And this https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Ignore the oops error warning, it's something to do with what G drive can scan.

Holy Sh!t. this just absolutely worked!! I didn't think I could bring this thing back to life, but the files you linked just did it! Really, I don't know how to thank you enough for this.

corasman said:
This is the file you need https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view
And this https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Ignore the oops error warning, it's something to do with what G drive can scan.
Click to expand...
Click to collapse
Hi folks,
had the exact same issue and indeed the 1st link offered (https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view) worked like a charm.
The second link is to download the "Intel platform flash tool lite", but I used my existing version of the Intel Phone Flash Tool (5.2.1-0) which worked fine with the image.
In other words, Corasman, it appears you have saved 2 people's life (or at least tablets) with your solution, so Thanks ! :good:
Regards.

Make that 3 people! Thank you so much corasman - your post has finally fixed my yoga 2 tablet, which I was sure would be going in the bin. Can't overstate how grateful I am - Cheers!

update 830f with 1050f rom?
updating 830f with 1050 rom? does it work?

hello. I have the same problem. I update OTA to lolipop. Since the table is slow, i tried flashing some ROM (which i cannot recall) and the tablet stopped working. Now, I am trying to flash the link you provided and it succeed. However after that i get blank Screen. what Could be wrong. My table is YT2 830LC. Please help

I am typing this all over again after my full report vanished. Do not have the patience of typing all that again. Suffice to say I had a similar situation with the boot failed EFI Hard Drive. Boot Successful - Enter Setup" message on my 830LC.
I had even found the bios restore tool for moving back from lollipop to kitkat but it too would hang. And attempts to flash lollipop would fail immediately with the same message as the OP, wrong device state.
So, in spite of it seeming completely counter-intuitive, I flashed the 1050F rom in the link shared by Corasman. Strange as it may seem, my tablet is now alive and working. No calling function, but it is working and calling itself a 1050F.
Now my research has to shift to whether the 830 LC rom can be flashed now.

i have a same problem with yoga 2 pro 1380f mr corasmancan help me

prabuddhadg said:
I am typing this all over again after my full report vanished. Do not have the patience of typing all that again. Suffice to say I had a similar situation with the boot failed EFI Hard Drive. Boot Successful - Enter Setup" message on my 830LC.
I had even found the bios restore tool for moving back from lollipop to kitkat but it too would hang. And attempts to flash lollipop would fail immediately with the same message as the OP, wrong device state.
So, in spite of it seeming completely counter-intuitive, I flashed the 1050F rom in the link shared by Corasman. Strange as it may seem, my tablet is now alive and working. No calling function, but it is working and calling itself a 1050F.
Now my research has to shift to whether the 830 LC rom can be flashed now.
Click to expand...
Click to collapse
i have same problem with my yoga 830lc this rom not work help me to run my tab agian
---------- Post added at 10:55 AM ---------- Previous post was at 10:47 AM ----------
corasman said:
This is the file you need
And this
Ignore the oops error warning, it's something to do with what G drive can scan.
Click to expand...
Click to collapse
hy sir downlod the rom from google drive but unable to download 2nd link (link not working)
i use latest intel flas tool light but the rom no flash to my device its show errors. plese sir help me to run my tab again

S10+ now stuck on soft brick / download mode / black screen

Hi all,
xda newbe here.
I got my s10+ yesterday so Ive decided to root it and flash with custom ROM - beyondrom v5,0
what has been done in chronological steps
1. phone with stock os / bootloader locked
2. dev mode on
3. bootloader open and grayed out in stock os
4. flashing / isntalling custom recovery - twrp via odin - success
5. flashing custom rom via twrp, used usb dongle with usb key
6. aroma installer pop up as expected - ive untick apps which i dont like
6.1. then in aroma instlaller got asked something like what geo should be allocated / list of countries
6.2. i choose UK unspecified (most likely i messed up here), im located in Slovakia, i think in aroma istaller it was eastern europe option
7. ive clicked next in installer, installation went complete, aroma log saved
8. phone turn off
9. now atempt to enter recovery mode - unsuccessful
10. device immidiately boot into download mode pic no1
10.1. there is error log on the top of display in red -
Recovery: Public key used tp sign data does not match key in chain partitin desctiptor. (5)
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU1AS05, 23234098A
11. not able to turn it off
11.1. after couple of hours device turn off, baterry went empty
12. connect to pc - odin - sammobile latest s10+ soft for Slovakia / TMS as the phone its from tmobile - pics no2 and no3
12.1. success, flashed with stock rom, see pic no4
12.2. device immidiate restart - boot - bang donwload mode with error log in red
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU3ASG8, 24948476R
13. turned off device, bixby + vol down + cable - device on, warning, vol up, download mode with long colorfull log, but there is a red log on the botton (nAsv_TABLE: 5 I EVT 1.1 ) pic no5
Current status -
not able to turn on the phone of course
device can be turn off by instruction on download mode screen
able to enter download mode
odin recognize device
pc recognize device
as i didnt find anything related to this status i created this thread and hopefully someone of you, xda overlords, will help. Im suspicious that even after stock rom flash there is still some gap in geo support and the device ... manufacturer hardware support vs slovakia tcom soft version. Maybe Im bullshitting myself. I dont want to kill device completely.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pls advice, many thanks, your noob bunkerr

Just flash the stock firmware using odin you should be ok.
After that reinstall root..and etc.

Player04 said:
Just flash the stock firmware using odin you should be ok.
After that reinstall root..and etc.[/QUOTE
- as you can read in point 12 Ive already did a stock rom reflash. It doesnt help, or did something wrong? the phone after success in odin turn off, and then force to download mode by it self, no way to turn on phone or entry recovery mode
pls advise, thanks
Click to expand...
Click to collapse

Oh i see you flash the wrong csc file. You have to get the correct firmware country.. for me its BRI csc, so i dl bri stock firmware and flash everything (bl, ap,cp and csc) with odin

bunkrra said:
Hi all,
xda newbe here.
I got my s10+ yesterday so Ive decided to root it and flash with custom ROM - beyondrom v5,0
what has been done in chronological steps
1. phone with stock os / bootloader locked
2. dev mode on
3. bootloader open and grayed out in stock os
4. flashing / isntalling custom recovery - twrp via odin - success
5. flashing custom rom via twrp, used usb dongle with usb key
6. aroma installer pop up as expected - ive untick apps which i dont like
6.1. then in aroma instlaller got asked something like what geo should be allocated / list of countries
6.2. i choose UK unspecified (most likely i messed up here), im located in Slovakia, i think in aroma istaller it was eastern europe option
7. ive clicked next in installer, installation went complete, aroma log saved
8. phone turn off
9. now atempt to enter recovery mode - unsuccessful
10. device immidiately boot into download mode pic no1
10.1. there is error log on the top of display in red -
Recovery: Public key used tp sign data does not match key in chain partitin desctiptor. (5)
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU1AS05, 23234098A
11. not able to turn it off
11.1. after couple of hours device turn off, baterry went empty
12. connect to pc - odin - sammobile latest s10+ soft for Slovakia / TMS as the phone its from tmobile - pics no2 and no3
12.1. success, flashed with stock rom, see pic no4
12.2. device immidiate restart - boot - bang donwload mode with error log in red
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU3ASG8, 24948476R
13. turned off device, bixby + vol down + cable - device on, warning, vol up, download mode with long colorfull log, but there is a red log on the botton (nAsv_TABLE: 5 I EVT 1.1 ) pic no5
Current status -
not able to turn on the phone of course
device can be turn off by instruction on download mode screen
able to enter download mode
odin recognize device
pc recognize device
as i didnt find anything related to this status i created this thread and hopefully someone of you, xda overlords, will help. Im suspicious that even after stock rom flash there is still some gap in geo support and the device ... manufacturer hardware support vs slovakia tcom soft version. Maybe Im bullshitting myself. I dont want to kill device completely.
pls advice, many thanks, your noob bunkerr
Click to expand...
Click to collapse
Flash whole firmware not only ap.

MHA-L09 only works with board software, can't update

Hi people, noob user here
My Mate 9 MHA-L09 stays bricked after i rebrand via HWOTA or update by any method, but i can bring it back to life only with IDT and board software (EMUI 5 - Android 7). Tried differents methods with nougat and oreo firmwares:
HWOTA update from sdcard or windows (brick)
Twrp, then supersu or magisk and update zip (brick)
dload folder with sd card upgrade or 3 button method (brick)
fastboot flash images with Huawei Update extractor (brick)
After that, phone stays bricked, no fastboot, recovery, battery charge, nothing. I plug it to usb and its recognized as huawei com usb (without using testpoint), and then i return to the beginning flashing board software (made that like 20 times by now :crying::crying::crying::crying Pleaseee send some help !!

OK I can help you, it's really easy by the way, did you know which version do you have before the disaster?
Version and cust?

lefkiller said:
OK I can help you, it's really easy by the way, did you know which version do you have before the disaster?
Version and cust?
Click to expand...
Click to collapse
Hi, in fact I had no cust because I sent my phone to a technician and he left it like Build System 8.0.0.x(xxx), I couldn't unlock bootloader with dc unlocker because not supported. So I thought the only way was to downgrade with board software and flash new firmware but now I'm in a loop for like 1 week with this problem.

Do you have access to recovery? Bootloader? It allows you flash something?

lefkiller said:
Do you have access to recovery? Bootloader? It allows you flash something?
Click to expand...
Click to collapse
Yes, I can do everything, but after EMUI update process shows "Finished, device will restart" it doesn't, gets bricked. Then I have to flash board software again to boot my phone

OK, what method are you using to flash?
DC Phoenix or dload?
And what firmware are you trying to flash?
Wen all this happens to you what firmware has you in the phone?
Are trying to install your same region?
Answer me all Tha questions and probably I can give you the way to solve you problem

lefkiller said:
OK, what method are you using to flash?
DC Phoenix or dload?
And what firmware are you trying to flash?
Wen all this happens to you what firmware has you in the phone?
Are trying to install your same region?
Answer me all Tha questions and probably I can give you the way to solve you problem
Click to expand...
Click to collapse
HWOTA update from sdcard or windows (brick)
Twrp, then supersu or magisk and update zip (brick)
dload folder with sd card upgrade or 3 button method (brick)
fastboot flash images with Huawei Update extractor (brick)
Click to expand...
Click to collapse
Tried Nougat and Oreo firmwares, rebrand, same model or L29, AL00 (C636, C432, C605). Maybe its an xloader thing, i don't know

OK, but you are not answering my questions, what is you older version, original oeminfo, etc, needed to have success fixing your phone.
Try this:
1 Flash board firmware (idt)
2 Boot on maintenance system and check in manufacturer menu background USB port, manufacturer mode (*#*#2846579#*#*)
3 on HCU client (paid) unlock your phone if needed and fix numbers if your device has Meid use CDMA fix if not use UMTS (imei, model, vendor, country, etc)
Unmark flash as empty board and the opción for QC
4 now you most have a pretty nice Boot loop, so you need to enter fastboot mode, in fastboot mode disconnect the cable USB and press volume bottoms at the same time you are now in fastboot submeno, just luck for shut down opción
5 flash you stock rom in force mode pressing all de buttons at the same time, using a SD card/dload/UPDATE. APP
the rom most be one newest than the one you have before, that's why I ask to you but you don't answer me
That's it, welcome back to your phone
I'm my case I use the rom MHA-L29C605B375 downloaded from androidhost.ru, lock for one whit only 2 archives.

lefkiller said:
OK, but you are not answering my questions, what is you older version, original oeminfo, etc, needed to have success fixing your phone.
Try this:
1 Flash board firmware (idt)
2 Boot on maintenance system and check in manufacturer menu background USB port, manufacturer mode (*#*#2846579#*#*)
3 on HCU client (paid) unlock your phone if needed and fix numbers if your device has Meid use CDMA fix if not use UMTS (imei, model, vendor, country, etc)
Unmark flash as empty board and the opción for QC
4 now you most have a pretty nice Boot loop, so you need to enter fastboot mode, in fastboot mode disconnect the cable USB and press volume bottoms at the same time you are now in fastboot submeno, just luck for shut down opción
5 flash you stock rom in force mode pressing all de buttons at the same time, using a SD card/dload/UPDATE. APP
the rom most be one newest than the one you have before, that's why I ask to you but you don't answer me
That's it, welcome back to your phone
I'm my case I use the rom MHA-L29C605B375 downloaded from androidhost.ru, lock for one whit only 2 archives.
Click to expand...
Click to collapse
Like I said, my phone was running Oreo (I think) and build was System 8.0.0.0xx, could't use themes, bank apps also didn't work, that's why I tried to downgrade so I could flash new firmware :angel: I have no idea what oeminfo was, I'm sorry . I will give a try to HCU

Oeminfo contains model, vendor, country, etc, if you don't know fixed whit HCU, they have tutorial for that
https://hcu-client.com/huawei-phone-country-vendor-repair/
Just follow that and you will be OK, be sure to flash a proper rom, dload method

lefkiller said:
OK, but you are not answering my questions, what is you older version, original oeminfo, etc, needed to have success fixing your phone.
Try this:
1 Flash board firmware (idt)
2 Boot on maintenance system and check in manufacturer menu background USB port, manufacturer mode (*#*#2846579#*#*)
3 on HCU client (paid) unlock your phone if needed and fix numbers if your device has Meid use CDMA fix if not use UMTS (imei, model, vendor, country, etc)
Unmark flash as empty board and the opción for QC
4 now you most have a pretty nice Boot loop, so you need to enter fastboot mode, in fastboot mode disconnect the cable USB and press volume bottoms at the same time you are now in fastboot submeno, just luck for shut down opción
5 flash you stock rom in force mode pressing all de buttons at the same time, using a SD card/dload/UPDATE. APP
the rom most be one newest than the one you have before, that's why I ask to you but you don't answer me
That's it, welcome back to your phone
I'm my case I use the rom MHA-L29C605B375 downloaded from androidhost.ru, lock for one whit only 2 archives.
Click to expand...
Click to collapse
No success on step 5, I tried to install MHA-L09C605B360 (8.0.0.360) with HWOTA, same problem, device restart then hard brick.
Flashed board software again (100th time), HCU thing, dload update (this time with MHA-L09C605B375 8.0.0.375) with 3 buttons and then "Software Update Failed" at 5%

Can you show me the image of HCU Wen you repair UMTS or CDMA

lefkiller said:
can you show me the image of hcu wen you repair umts or cdma
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

pabl0cv said:
No success on step 5, I tried to install MHA-L09C605B360 (8.0.0.360) with HWOTA, same problem, device restart then hard brick.
Flashed board software again (100th time), HCU thing, dload update (this time with MHA-L09C605B375 8.0.0.375) with 3 buttons and then "Software Update Failed" at 5%
Click to expand...
Click to collapse
This update is the one whit just 2 files?
Download this https://androidhost.ru/SG5

Okay, after hours of trying, reading a lot of threads, I concluded this:
Neither B360, 361, 362, etc., worked, UNTIL B375. How did I realize that? earlier I said something about the xloader partition, I don't know clearly what it means but what I did was extract the XLOADER partition image from UPDATE.APP of every build (with huawei update extractor). Then I flashed with fastboot (fastboot flash xloader xloaderfile.img). Every image I tried FAILED image xloader1 verification error, until I tried with XLOADER.img from B375, it said OKAY. Finally, as I knew that build would work, flashed the whole firmware (3 files), following this GUIDE from mankindtw. Btw I repaired imei, vendor, country with hcu after flashing board software
Now I have a second problem, I can't unlock my sim. If someone could help me here, HCU says Error, not supported
View attachment 5091113

lefkiller said:
OK, but you are not answering my questions, what is you older version, original oeminfo, etc, needed to have success fixing your phone.
Try this:
1 Flash board firmware (idt)
2 Boot on maintenance system and check in manufacturer menu background USB port, manufacturer mode (*#*#2846579#*#*)
3 on HCU client (paid) unlock your phone if needed and fix numbers if your device has Meid use CDMA fix if not use UMTS (imei, model, vendor, country, etc)
Unmark flash as empty board and the opción for QC
4 now you most have a pretty nice Boot loop, so you need to enter fastboot mode, in fastboot mode disconnect the cable USB and press volume bottoms at the same time you are now in fastboot submeno, just luck for shut down opción
5 flash you stock rom in force mode pressing all de buttons at the same time, using a SD card/dload/UPDATE. APP
the rom most be one newest than the one you have before, that's why I ask to you but you don't answer me
That's it, welcome back to your phone
I'm my case I use the rom MHA-L29C605B375 downloaded from androidhost.ru, lock for one whit only 2 archives.
Click to expand...
Click to collapse
Te lo dije en el número 3, primera linea

Te lo dije en el número 3, primera linea
Click to expand...
Click to collapse
You were right, I should have done that before repair with hcu. "Read sim unlock codes" did nothing, only "direct sim unlock" worked for me.
So, finally after more than a week , what I did was:
Flash board software with IDT and testpoint
Repair phone with "Direct sim unlock" in HCU (paid 3 euro)
Repair umts (imei, model, vendor, country) (paid 8 euro, 24h timed license)
Flashed B375 ROM with HWOTA guide
After boot system, unlocked frp and bootloader, then upgraded to Pie build 9.0.1.189 with HWOTA9 guide as I didn't receive any official update from huawei
Now my phone is receiving ota updates :highfive::victory: thank you so much :laugh:

The step with HWOTA was not necessary, with dload it was more than enough, all the updates came to me until reaching 9.1.0.252, after that I have not received anything else, in FF I see that there is up to 9.1.0.275, I have my doubts whether to do it by dload

lefkiller said:
The step with HWOTA was not necessary, with dload it was more than enough, all the updates came to me until reaching 9.1.0.252, after that I have not received anything else, in FF I see that there is up to 9.1.0.275, I have my doubts whether to do it by dload
Click to expand...
Click to collapse
dload update (this time with MHA-L09C605B375 8.0.0.375) with 3 buttons and then "Software Update Failed" at 5%
Click to expand...
Click to collapse
Dload method didn't make it for me, for sure I missed or did something wrong

lefkiller said:
This update is the one whit just 2 files?
Download this https://androidhost.ru/SG5
Click to expand...
Click to collapse
This works nice whit dload method, just 2 files in it
The important thing is that you managed to recover the equipment and now everything is functional