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.

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

[HELP][Samsung A3] - Broken Screen - Recover Files

Hi,
I've a Samsung A3 with a broken screen and I need to recover some files from it.
The device isn't rooted, have a default recover and ROM.
I'm trying to access via adb, but always shows unauthorized with the command adb devices -l.
Other idea is connect the device trough some cable, is possible with MLH?
Is the A3 compatible with MLH?

The files are accessible, dont worry. You will need TWRP on the device, and ADB configured on the PC/MAC. After that, you can "PULL" the files out of there.
OR JUST USE KIES.
PS, not sure about MHL cables, none worked for me.

PlutoDelic said:
The files are accessible, dont worry. You will need TWRP on the device, and ADB configured on the PC/MAC. After that, you can "PULL" the files out of there.
OR JUST USE KIES.
PS, not sure about MHL cables, none worked for me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/development/recovery-twrp-2-8-7-0-galaxy-a3-sm-t3153682
To install TWRP I had read that the phone must be rooted.
My great dificulty is how I can root and install twrp on the phone without a screen to see each process stage...
Regarding KIES I never connected the phone to the PC, so I need to autorize KIES to acess phone... and with a broken screen I can't do it.
tks

You dont need root for TWRP.

PlutoDelic said:
You dont need root for TWRP.
Click to expand...
Click to collapse
I saw that is mentioned here http://forum.xda-developers.com/andr...a3-sm-t3153682 .
The following procedure dont require root but it's needed a working screen ("Settings > Developer Options > USB Debugging").
http://www.xda-developers.com/how-to-install-twrp/

Use KIES then.

Ok, I'll put this to bed right now for anyone else that happens to read that misinformation posted all over the net.
You DO NOT and never have had required to have root or enable USB debugging to install custom recovery.
Recovery is a mini OS that has absolutely no connection to the main system OS. USB debugging and root are only required for the main OS.
You dont even need an OS installed to use recovery.
Install TWRP with ODIN and then use the tool below. You can do all this without a screen. Odin will tell you what's happening.
http://forum.xda-developers.com/showthread.php?t=2786395
IMPORTANT: You must disable auto reboot in Odin then when Odin says PASS after flashing you must IMMEDIATELY boot to recovery by holding POWER + HOME + VOL DOWN
as soon as you see REMOVED in Odins windows quickly change to POWER + HOME + VOL UP.
This may take you a few tries as the timing is critical.
Note: If your device still boots to the OS and you dont have a security locked screen then you should still be able to use MTP to transfer files. Just plug your usb cable in.
If worse comes to worse and you cannot do the above I will modify the boot.img to give you adb support without needing usb debugging enabled.

???
luciofsl said:
Hi,
I've a Samsung A3 with a broken screen and I need to recover some files from it.
The device isn't rooted, have a default recover and ROM.
I'm trying to access via adb, but always shows unauthorized with the command adb devices -l.
Other idea is connect the device trough some cable, is possible with MLH?
Is the A3 compatible with MLH?
Click to expand...
Click to collapse
Hello guys. I have the same problem as the OP, I have no to little experience in android and anything around it, but I am pretty messed up and i could use some help here :<
I have Galaxy A3 (2016), with broken screen (totally black), stock rom, without usb debugging enabled and a lock pattern in use...
I tried everything I could comprehend from the replys here and many posts around, but I got nothing... I am not even sure that I could get into recovery mode to install TWRP with odin, as it failed (whenever it could pass the the "SetupConnection")...
Is there anything I can do, maybe someone can help me on something i am missing here? :F

Doggy17 said:
Hello guys. I have the same problem as the OP, I have no to little experience in android and anything around it, but I am pretty messed up and i could use some help here :<
I have Galaxy A3 (2016), with broken screen (totally black), stock rom, without usb debugging enabled and a lock pattern in use...
I tried everything I could comprehend from the replys here and many posts around, but I got nothing... I am not even sure that I could get into recovery mode to install TWRP with odin, as it failed (whenever it could pass the the "SetupConnection")...
Is there anything I can do, maybe someone can help me on something i am missing here? :F
Click to expand...
Click to collapse
Ensure you have the Samsung USB drivers installed.
You need to put your device in download mode.
Boot holding power + home + vol down.
Hold for around 5 seconds then after another 5 seconds press volume up.
Run odin then plug the usb cable in. You will see the 'added' message if you are in download mode.

ashyx said:
Ensure you have the Samsung USB drivers installed.
You need to put your device in download mode.
Boot holding power + home + vol down.
Hold for around 5 seconds then after another 5 seconds press volume up.
Run odin then plug the usb cable in. You will see the 'added' message if you are in download mode.
Click to expand...
Click to collapse
Hmm.. I used Odin 3.12 and twrp_3.0.2-1_sm-a310.tar . What seems to be the problem here? Am I using wrong version of something?? :<
{
"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"
}

Doggy17 said:
Hmm.. I used Odin 3.12 and twrp_3.0.2-1_sm-a310.tar . What seems to be the problem here? Am I using wrong version of something?? :<
Click to expand...
Click to collapse
You don't have oem unlock enabled.

ashyx said:
You don't have oem unlock enabled.
Click to expand...
Click to collapse
Is there something I can do though?? Please don't say no!

Doggy17 said:
Is there something I can do though?? Please don't say no!
Click to expand...
Click to collapse
Which firmware was your device running?

ashyx said:
Which firmware was your device running?
Click to expand...
Click to collapse
I am not quite sure. It's got Greek baseband so I believe that this must be it "SM-A310F_20160827_A310FXXU2BPH8_A310FOXX2BPI8_6.0.1".

ashyx said:
Which firmware was your device running?
Click to expand...
Click to collapse
Doggy17 said:
I am not quite sure. It's got Greek baseband so I believe that this must be it "SM-A310F_20160827_A310FXXU2BPH8_A310FOXX2BPI8_6.0.1".
Click to expand...
Click to collapse
Is there a way to determine the firmware by the phone as it is now somehow?

Guys, is there anything that I could possibly do, or should I just forget about it?

luciofsl said:
Other idea is connect the device trough some cable, is possible with MLH?
Is the A3 compatible with MLH?
Click to expand...
Click to collapse
Samsung A3 support OTG, but not compatible with MHL.
So does the screen switch on? Or is it completely black?
If can you see the screen display, buy an OTG cable to plug a mouse into your Samsung, and click on your phone to make a backup.

Evening. I have a relatives Galaxy A5 with a completely blank screen and no touch. USB debugging is OFF. Im not sure what version of Android is on the phone. I have installed Custom recovery as far as I can tell. I cannot get the phone into Recovery mode. I have been trying to get the phone to turn off by having it plugged into the charger and holding Volume- & Power (As the battery is non removable) then Power & Volume+ & Home but its a no go. I tried Kies but its saying the phone is locked and it needs a password but I cant type it in with a blank screen and no touch. Does the A5 2015 have OTG support? Theres some important info on the phone so he really needs it. Help Please

wagoera said:
Maybe you can try Broken Android Data Extraction tool to help you recover files from Samsung A3 with broken screen. It can help you access files and extract them out from a broken screen or dead Samsung mobile phone.
Click to expand...
Click to collapse
It's always best to at least read the previous post before you post.

Apply update from sdcard FAILED : Rooted Crosscall Trekker M1 on BOOTLOOP

Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !

Brazyxs said:
Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !
Click to expand...
Click to collapse
Hello,
Can you capture files included in update.zip?

-Hope- said:
Hello,
Can you capture files included in update.zip?
Click to expand...
Click to collapse
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can

Brazyxs said:
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can
Click to expand...
Click to collapse
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip

-Hope- said:
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip
Click to expand...
Click to collapse
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it

Brazyxs said:
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it
Click to expand...
Click to collapse
Can u provide me with a pic of the tar.gz file (the files inside it)

-Hope- said:
Can u provide me with a pic of the tar.gz file (the files inside it)
Click to expand...
Click to collapse
Here's 4 captures of the tar.gz opened with Winzip
{
"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"
}
View attachment 4279786
View attachment 4279787
View attachment 4279788

Brazyxs said:
Here's 4 captures of the tar.gz opened with Winzip
View attachment 4279785
View attachment 4279786
View attachment 4279787
View attachment 4279788
Click to expand...
Click to collapse
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil

-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
Thank you very much ! I will check about QFIL by myself. For now I'm happy that someone care about my issues
I tell you if there is something new !

-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?

Brazyxs said:
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?
Click to expand...
Click to collapse
Can you try to run it as an admin then choose the right com and try again ?

-Hope- said:
Can you try to run it as an admin then choose the right com and try again ?
Click to expand...
Click to collapse
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?

Brazyxs said:
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?
Click to expand...
Click to collapse
Did you install the qcom drivers

-Hope- said:
Did you install the qcom drivers ?
Click to expand...
Click to collapse
Hi, Here's the list of all the drivers I installed :
Qualcomm_USB_Driver_V1.0
MTK_USB_All_V1.0.8
ADBDriverInstaller
I also installed :
Android-sdk
Java SE Development Kit

After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.

Brazyxs said:
After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.
View attachment 4284734
Click to expand...
Click to collapse
Just reread the post, try to do a factory reset

-Hope- said:
Just reread the post, try to do a factory reset
Click to expand...
Click to collapse
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.

Brazyxs said:
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.
Click to expand...
Click to collapse
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted

-Hope- said:
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted
Click to expand...
Click to collapse
Yes I did said that, adb worked for a time.
I'm not sure to understand what you mean by "the file system" and "push it " with adb
The thing I'm sure of is that I'm rooted :good:
I'll continue my researchs.

Help with invalid IMEI fater rebooting phone?

Hey guys, I'm trying to fix an lg spirit (h440n)
The phone ran out of battery, and later when I charged it and rebooted, I couldn't get any service, and later realized that the IMEI is now invalid and is listen as "unknown" (as well as a couple of other things). Also, for whatever reason the phone takes a much longer time to boot up.
I'd really appreciate if anyone could assist me with restoring the IMEI.
So far I tried doing a factory reset, which didn't help at all (and now for whatever reason the youtube app appears as a generic android icon with the name com.google.android.youtube...etc.)
I do still have the original IMEI cause i saved the box from the phone.
By the way, I'm on android 6.0

kiraqu33n said:
Hey guys, I'm trying to fix an lg spirit (h440n)
The phone ran out of battery, and later when I charged it and rebooted, I couldn't get any service, and later realized that the IMEI is now invalid and is listen as "unknown" (as well as a couple of other things). Also, for whatever reason the phone takes a much longer time to boot up.
I'd really appreciate if anyone could assist me with restoring the IMEI.
So far I tried doing a factory reset, which didn't help at all (and now for whatever reason the youtube app appears as a generic android icon with the name com.google.android.youtube...etc.)
I do still have the original IMEI cause i saved the box from the phone.
By the way, I'm on android 6.0
Click to expand...
Click to collapse
Try to reflash your stock rom with lg flash tool.

mayankjet said:
Try to reflash your stock rom with lg flash tool.
Click to expand...
Click to collapse
Hi,
so I tried doing that, but I keep running into several errors:
1) If I try doing a normal flash using a stock v20b ROM (android 6.0), the flashing software gives me an error saying "Problem with communication between cell phone and PC". It has some instructions on what to do to restart the flashing process, but it still doesn't work for me even if I do them
2) Flashing the v20b ROM with with the CSE flash method, I get an error on the program saying "Required info cannot be found. Contact the system administrator.."
3) Flashing a 10i ROM (android 5) with the CSE method, the flashing process goes to about 9% on the PC, then my phone reboots and for a split second displays an error with all red letters saying "Boot verification Fail!! cause : DIFFERENT_HASH", and after that the phone reboots as normal and the flashing process is once again failed.
I honestly don't understand where the problem is... I hope it's still possible to solve

kiraqu33n said:
Hi,
so I tried doing that, but I keep running into several errors:
1) If I try doing a normal flash using a stock v20b ROM (android 6.0), the flashing software gives me an error saying "Problem with communication between cell phone and PC". It has some instructions on what to do to restart the flashing process, but it still doesn't work for me even if I do them
2) Flashing the v20b ROM with with the CSE flash method, I get an error on the program saying "Required info cannot be found. Contact the system administrator.."
3) Flashing a 10i ROM (android 5) with the CSE method, the flashing process goes to about 9% on the PC, then my phone reboots and for a split second displays an error with all red letters saying "Boot verification Fail!! cause : DIFFERENT_HASH", and after that the phone reboots as normal and the flashing process is once again failed.
I honestly don't understand where the problem is... I hope it's still possible to solve
Click to expand...
Click to collapse
Go to this link
http://techtrickszone.com/2017/12/06/invalid-imei-number-after-flashing-android-phone/
If the above method doesn't work then try to flash lollipop rom with LG UP software as it is possible that the lg support tool could be having trouble flashing the rom.
Also please post a screenshot of the issue.

mayankjet said:
Go to this link
If the above method doesn't work then try to flash lollipop rom with LG UP software as it is possible that the lg support tool could be having trouble flashing the rom.
Also please post a screenshot of the issue.
Click to expand...
Click to collapse
Seems like the method you sent me in the link requires for my LG to be rooted, which I don't think I'll be able to do - none of the one click root methods worked cause android 6.0 seems to have fixed the exploit those programs use, and doing it manually might also be troublesome cause I can't get the download mode to work with the phone.(Like I mentioned, the error "Boot verification Fail!! cause : DIFFERENT_HASH"). Sorry, I'm not able to post an image of the error cause I'm still a new user on the forums...
So I think LGUP might be my only hope at this point, but I can't get it to recognize my phone. It just shows up as an unknown device and I can't proceed with the flashing process

kiraqu33n said:
Hey guys, I'm trying to fix an lg spirit (h440n)
The phone ran out of battery, and later when I charged it and rebooted, I couldn't get any service, and later realized that the IMEI is now invalid and is listen as "unknown" (as well as a couple of other things). Also, for whatever reason the phone takes a much longer time to boot up.
I'd really appreciate if anyone could assist me with restoring the IMEI.
So far I tried doing a factory reset, which didn't help at all (and now for whatever reason the youtube app appears as a generic android icon with the name com.google.android.youtube...etc.)
I do still have the original IMEI cause i saved the box from the phone.
By the way, I'm on android 6.0
Click to expand...
Click to collapse
Go to this link:
https://lg-kdz-firmware.com/check-your-firmware.html
Open your phone from the back and remove the battery, then you will find the IMEI, write it on that site that i put a link to and you can find the right firmware for your phone, download it, download lg drivers (search on google for them) and install them, then try flashing with LG Flash Tool 2014, and make settings to be like this:
Select Type: CDMA,
PhoneMode: CS_EMERGENCY
and flash with CSE Flash.
To go in download mode turn off your phone and hold the volume down button while holding enter the usb cable in to the phone but it should previously be connected to the pc, hold volume down button until you sea a screen that shows you that you are in download mode than start the tool from your pc and flash the firmware.
Hope this helps.

Tin40 said:
Go to this link:
https://lg-kdz-firmware.com/check-your-firmware.html
Open your phone from the back and remove the battery, then you will find the IMEI, write it on that site that i put a link to and you can find the right firmware for your phone, download it, download lg drivers (search on google for them) and install them, then try flashing with LG Flash Tool 2014, and make settings to be like this:
Select Type: CDMA,
PhoneMode: CS_EMERGENCY
and flash with CSE Flash.
To go in download mode turn off your phone and hold the volume down button while holding enter the usb cable in to the phone but it should previously be connected to the pc, hold volume down button until you sea a screen that shows you that you are in download mode than start the tool from your pc and flash the firmware.
Hope this helps.
Click to expand...
Click to collapse
Hi, I can't get my phone into download mode, the phone displays an error: "Boot verification Fail!! cause : DIFFERENT_HASH", and just reboots like normal and the flashing process ends up failing... I guess the download mode on my phone is somehow broken, though I can't find any way to fix it

kiraqu33n said:
Hi, I can't get my phone into download mode, the phone displays an error: "Boot verification Fail!! cause : DIFFERENT_HASH", and just reboots like normal and the flashing process ends up failing... I guess the download mode on my phone is somehow broken, though I can't find any way to fix it
Click to expand...
Click to collapse
To enter download mode phone must be turned off then press and hold vol. Up button then plug in the usb cable. It is not the volume down button.
If Lg Up recognizes your phone as unknown device that's normal as it has happened to me as well. See if you can enter in download mode with keys, if you can't, just keep your phone booted into rom then start flashing lollipop kdz and your phone should automatically boot into download mode.

On my LG Spirit 4G LTE h440n is the volume down button. The volume up is to go into the bootloader.

mayankjet said:
To enter download mode phone must be turned off then press and hold vol. Up button then plug in the usb cable. It is not the volume down button.
If Lg Up recognizes your phone as unknown device that's normal as it has happened to me as well. See if you can enter in download mode with keys, if you can't, just keep your phone booted into rom then start flashing lollipop kdz and your phone should automatically boot into download mode.
Click to expand...
Click to collapse
In LGUP when my phone shows up as "unknown", I can't do the flashing process cause the program just says "You have to select a known model, please."
Edit: here is a screenshot
{
"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"
}
And about download mode, I know how to get into it, and it is indeed volume up+usb, but like I said, when I enter download mode it just displays that error message about boot verification failed, and the phone just reboots as normal. I thought maybe I'm not explaining it well enough so instead I filmed a video: https://www.youtube.com/watch?v=APlsn5gVvzw&feature=youtu.be

kiraqu33n said:
In LGUP when my phone shows up as "unknown", I can't do the flashing process cause the program just says "You have to select a known model, please."
Edit: here is a screenshot
And about download mode, I know how to get into it, and it is indeed volume up+usb, but like I said, when I enter download mode it just displays that error message about boot verification failed, and the phone just reboots as normal. I thought maybe I'm not explaining it well enough so instead I filmed a video:
&feature=youtu.be
Click to expand...
Click to collapse
Take a look at this thread.
https://forum.xda-developers.com/g-flex2/help/lgup-unknown-device-t3403402

mayankjet said:
Take a look at this thread.
https://forum.xda-developers.com/g-flex2/help/lgup-unknown-device-t3403402
Click to expand...
Click to collapse
Tried everything in that thread, but sadly the result is still the same. I also followed a tutorial in this thread https://forum.xda-developers.com/lg-spirit/how-to/how-to-install-marshmallow-lg-spirit-t3490045 but my phone is still not recognized by LGUP. I'm certain I followed the instructions correctly

kiraqu33n said:
Tried everything in that thread, but sadly the result is still the same. I also followed a tutorial in this thread https://forum.xda-developers.com/lg-spirit/how-to/how-to-install-marshmallow-lg-spirit-t3490045 but my phone is still not recognized by LGUP. I'm certain I followed the instructions correctly
Click to expand...
Click to collapse
Sorry then as i can't think of anything else. If your phone is still under warranty period you can always send it to service center.

mayankjet said:
Sorry then as i can't think of anything else. If your phone is still under warranty period you can always send it to service center.
Click to expand...
Click to collapse
Ahh that's too bad. Well, thank you for your help either way! Sadly, the phone isn't covered by warranty anymore..
I think my best bet is to make the download mode work correctly. I guess I will have to keep searching

I have an LG Spirit 4G (H440n) that lost its IMEI a month ago after shutting down because of a drained battery. After turning it on, the SIM card never got read and the IMEI was unknown. Following a lot of hurdles to reflash a .kdz from download mode I managed to flash a MM firmware and the phone rebooted with its IMEI intact. Then, after a while the phone shut down with a drained battery and the same thing happened. I reflashed and fixed it.
After that... Yeah, the phone shut down after a battery drain and now it doesn't have its IMEI again. Is there any way to restore it and keep there for good without reflashing the whole device from download mode? What could be causing? Should I watch out for the battery forever now?

hitmancho said:
I have an LG Spirit 4G (H440n) that lost its IMEI a month ago after shutting down because of a drained battery. After turning it on, the SIM card never got read and the IMEI was unknown. Following a lot of hurdles to reflash a .kdz from download mode I managed to flash a MM firmware and the phone rebooted with its IMEI intact. Then, after a while the phone shut down with a drained battery and the same thing happened. I reflashed and fixed it.
After that... Yeah, the phone shut down after a battery drain and now it doesn't have its IMEI again. Is there any way to restore it and keep there for good without reflashing the whole device from download mode? What could be causing? Should I watch out for the battery forever now?
Click to expand...
Click to collapse
Wow this really is strange. Just to be clear, this phone I was trying to fix was being used by my dad, not me, and he also said the problems started happening after his battery got drained. Unlike you, however, I never managed to even flash a stock ROM to the phone, cause for me the download mode still doesn't work.
Any LG gurus out there know what's going on with these phones?

I can't post links on threads but i found a video, not sure if it helps or if it works but you got nothing to lose, PM me and i'll send you the link.