Database Info

[Q] HELLUP! Firmware upgrade encountered an issue. Please seclect recovery mode in Ki

Firmware Upgrade encountered an issue. Please select recovery mode in Kies & Try again.
I have this problem with my Samsung Galaxy Tab 7.7 wifi
Saw several site and I also use Odin 3 v1.85 but I can nog fix it.
Does anyone has a solution PLEASE??.

Hi,
If u hv made a nand backup... restore it from cwm.
If not, get yr original ROM and reinstall thru odin.
Then reroot and reinstall CWM & install yr prefered ROM/kernel.
Hope it helps.

skycruzer said:
Hi,
If u hv made a nand backup... restore it from cwm.
If not, get yr original ROM and reinstall thru odin.
Then reroot and reinstall CWM & install yr prefered ROM/kernel.
Hope it helps.
Click to expand...
Click to collapse
Hi,
It look like it doesn't get connected to the device.
I need the orgibnal Rom for the device I found a lot on the internet but nothing works though Odin.
Where can I find the orginal Rom.
Regards,
P. Derksen

plsderksen said:
Hi,
It look like it doesn't get connected to the device.
I need the orgibnal Rom for the device I found a lot on the internet but nothing works though Odin.
Where can I find the orginal Rom.
Regards,
P. Derksen
Click to expand...
Click to collapse
Try sammobile...

I have this problem with my Samsung Galaxy Tab 7.7 P6800. I've never tried to flash any custom rom. I was trying to upgrade from HC to ICS official firmware P6800XXLQ2/P6800OXALQ2/P6800XXLPW/P6800XXLQ2. I've tryied several times with odin3 v1.85 and always fail. I've tried again the original HC P6800XXLA4_CSC_TPH and still fail. And always in the end.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6800OXALQ2_P6800XXLQ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> cache.img
<ID:0/006> NAND Write Start!!
<ID:0/006> factoryfs.img
<ID:0/006> hidden.img
<ID:0/006> recovery.img
<ID:0/006> Sbl.bin
<ID:0/006> zImage
<ID:0/006> modem.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've searched along the forum and found no more solutions. Can anybody help me? Are there some more instructions to use in odin, another odin version or another program?
Thanks in advance.
I've solved the problem.
Used a wrong pit. Saw the solution not in Galaxy Tab 7.7 Q&A, Help & Troubleshooting but in general.
So thanks again for the magnific forum.

[Q] N8000 Boot (not OS boot animation) cleared

After using Odin to perform a Nand Erase All on my n8000, the boot screen(which should be Samsung Galaxy Note 10.1 GT-N8000) turns into the Download mode screen. All features are working. How to recover. Thanks.
Add: and is still booting. Only UI change

Boot Logo Modder
Kavin Zhao said:
After using Odin to perform a Nand Erase All on my n8000, the boot screen(which should be Samsung Galaxy Note 10.1 GT-N8000) turns into the Download mode screen. All features are working. How to recover. Thanks.
Add: and is still booting. Only UI change
Click to expand...
Click to collapse
See here: BOOT LOGO MODDER :good:
And you can use your own BOOT LOGO ofcourse:laugh:

tanker32 said:
See here: BOOT LOGO MODDER :good:
And you can use your own BOOT LOGO ofcourse:laugh:
Click to expand...
Click to collapse
Exactly the same problem.
Thanks a lot for that, going to try it. :good:

Well, that worked. But after flashing another picture provided by the second post(on another thread), a even more serious problem came: Device Bricked Anything helps?

Doesn't even power on(turn on the screen) was it bricked or something else?
Help!!!! What shall I do?

Describe your problem in detail, please!
Kavin Zhao said:
Well, that worked. But after flashing another picture provided by the second post(on another thread), a even more serious problem came: Device Bricked Anything helps?
Click to expand...
Click to collapse
You must describe what exactly you did before brick the device.
1. Type of your device
2. Are you used my MOD with new picture before brick your device?
3. Did you exactly proceed step by step like I describe in my thread?
4. Was your picture in good size (1280x800 landscape mode and portrait mode 800x1280 according to type of device) ?
5. Picture must have same name, same type (logo.jpg) as is in my MOD!
6. Check your ZIP, if you have good path and structure as in my MOD exactly!
7. If you don't made a mistake and you've kept my proceed, problem is somewhere else.
Try to go to recovery, download my first type MOD and wipe cache, dalvik cache and install ZIP and don't forget reboot back to RECOVERY
and after then use system reboot !!!!! I'm waiting for your answer. Then we will try something else (according to your problem) :good:
---------- Post added at 11:18 AM ---------- Previous post was at 11:09 AM ----------
Kavin Zhao said:
Doesn't even power on(turn on the screen) was it bricked or something else?
Help!!!! What shall I do?
Click to expand...
Click to collapse
You have my answer above, but I see that even POWER ON doesn't work!
Hold POWER more than 30 sec! Then you try go to recovery... If didn't work, hold POWER+VOLUME DOWN and when you see boot logo release
POWER and then VOLUME DOWN. You should be in DOWNLOAD MODE. And then proceed with ODIN software and stock firmware. But I think
that you made mistake when you try put you picture in my MOD in ZIP file.
User jordimra in BOOT LOGO MODDER THREAD has the same problem see:
The picture attached is made ​​by me, but I think it looks like the original Samsung Galaxy Note 10.1 logo.
Edit 1: Installed "boot-logo-GT-N8000.zip" and went OK. But if I modify the "logo.jpg" inside with my own one, the device gets stuck on black (logo?) screen, and can't get into recovery.
Edit 2: Reason: bad zip structure

Thankyou for your care.
Answers:
1.N8000
2.Yes
3.Yes--perhaps
4.Didn't check that, my picture was exactly the same as The picture attached is made ​​by me, but I think it looks like the original Samsung Galaxy Note 10.1 logo.
Edit 1: Installed "boot-logo-GT-N8000.zip" and went OK. But if I modify the "logo.jpg" inside with my own one, the device gets stuck on black (logo?) screen, and can't get into recovery.
Edit 2: Reason: bad zip structure(attachment)
5.Yes
6.Yes
...and huh? how did I enter download mode just now:laugh:?
Is flashing stockrom the only way?
tick nand erase all?
tested, can only enter download mode

My advice
Kavin Zhao said:
Thankyou for your care.
Answers:
1.N8000
2.Yes
3.Yes--perhaps
4.Didn't check that, my picture was exactly the same as The picture attached is made ​​by me, but I think it looks like the original Samsung Galaxy Note 10.1 logo.
Edit 1: Installed "boot-logo-GT-N8000.zip" and went OK. But if I modify the "logo.jpg" inside with my own one, the device gets stuck on black (logo?) screen, and can't get into recovery.
Edit 2: Reason: bad zip structure(attachment)
5.Yes
6.Yes
...and huh? how did I enter download mode just now:laugh:?
Is flashing stockrom the only way?
tick nand erase all?
tested, can only enter download mode
Click to expand...
Click to collapse
If you can go to download mode only, you don't need flash entire ROM. Forget tick Nand erase all and in Odin just flash boot.img or sboot.img, you can find here a lot of this file. But img must be Android same version as you have! Then flash sboot.img through PDA in Odin, and everything should be back in normal.:good: Just try it and then send me, how successful you've been :highfive: Regards, Peter

I have to reboot in to Ubuntu to get the tar files ready for flashing. Sadly, I found Odin cannot flash in anything(sboot.bin and boot.img) except the stock bundle and as you can see, i flashed the stock bundle. And your advice made me found another perfect thing on Google that I have always been searching for-- Dual boot
But it still cannot boot. I think I have to tick Nand Erase All to erase the trouble-causing boot picture.
Wish you good luck, Peter. Cheers:highfive:
P.S While flashing the bootloder(from the tar I made myself), it shows this:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
and stuck here

Keep going...
Kavin Zhao said:
I have to reboot in to Ubuntu to get the tar files ready for flashing. Sadly, I found Odin cannot flash in anything(sboot.bin and boot.img) except the stock bundle and as you can see, i flashed the stock bundle. And your advice made me found another perfect thing on Google that I have always been searching for-- Dual boot
But it still cannot boot. I think I have to tick Nand Erase All to erase the trouble-causing boot picture.
Wish you good luck, Peter. Cheers:highfive:
P.S While flashing the bootloder(from the tar I made myself), it shows this:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
and stuck here
Click to expand...
Click to collapse
Well, I'm so sorry about to hearing that. But as the poet says: "By seeking and blundering we learn." So O.K. try NAND ERASE ALL and then Flash your device by STOCK firmware with ODIN or KIES. Then let me know, how did you get... Regards :fingers-crossed: and for sure :highfive:

Operation Successful
Device successfully unbricked after Nand Erase All
Thank you Peter. It was not your responsibility to help me, but you did... and thank you again for that.
And after this post's been published, I think I'm not a new member anymore.
P.S
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8000ZSCMD2_N8000OZSCMD2_1149484_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Erase...
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> sboot.bin
<ID:0/006> tz.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

It's my pleasure to help!
Kavin Zhao said:
Device successfully unbricked after Nand Erase All
Thank you Peter. It was not your responsibility to help me, but you did... and thank you again for that.
And after this post's been published, I think I'm not a new member anymore.
P.S
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8000ZSCMD2_N8000OZSCMD2_1149484_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Erase...
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> sboot.bin
<ID:0/006> tz.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
YES! You welcome! :highfive:

It was the picture's problem. I optimized the picture to 1200x800 and it’s OK.
The zip with the optimized picture is below. Should look like the original.

hi
i have the same problem,after flashed this tablet,stuck on bootloop
no access to recovery,i tried many method but no success
i tried:
pit - 4 file - 1 file - all recovery - clear efs & repair again with odin & z3x - nand erase all & ...
but no success
tablet always in bootloop & just can put into download mode
when i turn on tablet,it's take 1 second and reboot and reboot and reboot & ... on Samsung Galaxy Note 10.1

Can't restore note 5 to stock

I am trying to restore my phone to stock because only stock modified rom works with VR, but doesn't play nice with android wear.
So back to stock I go, however when I put it in download mode load up AP with the file, and hit start it says "FAIL!" I have team win installed and that is how I get to download mode. I only had Auto Reboot and F. Reset time selected as well.
Can anyone advise me on what I may be doing wrong?
Here is the log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

Download the stock firmware again the one you're using might be corrupt, also make sure drivers are installed

I have the drivers installed, also tried 2 firmwares, trying one more now.
Was following this guide:
http://www.droidviews.com/restore-t-mobile-galaxy-note-5-sm-n920t-to-stock-5-1-1-lollipop-firmware/

no firmware seems to be working. I also tried a new cable and a few ports. No change.

tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.

Are you using 3.10.7?

I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.

Drachnem said:
tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.
Click to expand...
Click to collapse
How are you entering download mode?
Sent from my SM-N920T using Tapatalk

I've done it by using teamwin, also by holding pwr + home + volume down

guaneet said:
Are you using 3.10.7?
Click to expand...
Click to collapse
tried two...3.10.6, and 3.10.7

audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
You have to pay 10.00 to download the files

Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
Last time I checked you donated if you wanted, not forced to

Drachnem said:
Last time I checked you donated if you wanted, not forced to
Click to expand...
Click to collapse
Donated to try this fix, hope it works...

Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
As I recollect the fee is for the latest PAC, the others are free.

So it got further with the files and the pit file, but it didn't seem to fully work and I want to understand what may be wrong. It said failed in the first box but continued then the next box said pass.
The phone is now booted in setup mode but I wanted to understand what i may run into with this error or if I am fine...
Here is the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_TMB_N920TUVS2COKC_N920TTMB2COKC_CL5966591_QB7480468_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/004> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:1/004> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:1/004> File analysis..
<ID:1/004> SetupConnection..
<ID:0/005> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Set PIT file..
<ID:1/004> DO NOT TURN OFF TARGET!!
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> SingleDownload.
<ID:1/004> sboot.bin
<ID:1/004> NAND Write Start!!
<ID:1/004> param.bin
<ID:1/004> cm.bin
<ID:1/004> boot.img
<ID:1/004> recovery.img
<ID:1/004> system.img
<ID:0/005> Can't open the serial(COM) port.
<ID:1/004> modem.bin
<ID:1/004> cache.img
<ID:1/004> RQT_CLOSE !!
<ID:1/004> RES OK !!
<ID:1/004> Removed!!
<ID:1/004> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)

audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.

Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
I don't often have an answer, but after being the benefactor of the knowledge and kindness of others through the years, I'm glad to help when I can.

Drachnem said:
I've done it by using teamwin, also by holding pwr + home + volume down
Click to expand...
Click to collapse
That's the problem you are using twrp enter download mode by volume up+pwr+home
Sent from my SM-N920T using Tapatalk

Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
Are you able to post the files here (if that doesn't violate an XDA rule)? Trying to get the old ones and they seems to be gone and really don't want to have to pay, but I guess I will if I have to.

Hey Guys,
Having an issue getting one of my Galaxy Note 5 (SM-N920T) back to stock. I am able to flash stock firmware in Odin 3.10.7 but the phone is bricked. When I flash any stock firmware the phone reboots and is stuck at the Note 5 Splash Screen. If i reboot into recovery and try to do the factory wipe it tells me it can't find "E:" and fails. Only way I can get the phone to boot is if I flash a rooted kernel. Then I noticed it says the Baseband is unknown in settings. I was going to try flashing through ADB but it tells me ADB is disabled, same with flashing from external storage. I cant even get it to reboot into bootloader. I am starting to think the phone needs IMEI repair..

Soft Bricked GT-S7582

I am following "[Guide] Know your Device: Galaxy S Duos2 GT-S7582~Root~Odin~CWM~ROM LIST |2014.06.08|" this process to flash my device but its not working
please help
odin log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7582DDUANJ1_S7582ODDANJ1_S7582DDUANI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> BcmCP.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anybody tell me the problem how can i fix it

Flash the latest firmware from Odin ..u can download it from firmwarefile.com

Muscular droid said:
Flash the latest firmware from Odin ..u can download it from firmwarefile.com
Click to expand...
Click to collapse
I have already download the latest firmware from there.
Is there any other solution available for it then please help me out

rename the .tar.md5 file to .tar, open with winrar or anything that can read .tar and tell me if it having sboot.bin in there or not?
also your phone is s7580 or s7582?

​
sandpox said:
rename the .tar.md5 file to .tar, open with winrar or anything that can read .tar and tell me if it having sboot.bin in there or not?
also your phone is s7580 or s7582?
Click to expand...
Click to collapse
no it doesn't contain sboot.bin in there
i have attached the screenshot of the files in there
and my device is s7582

kishorprabhat said:
​
no it doesn't contain sboot.bin in there
i have attached the screenshot of the files in there
and my device is s7582
Click to expand...
Click to collapse
Looks like the last stock ROM which installed on your device is too old and its bootloader doesn't accept sign of new stock ROM, try to download another ROM but lower down in the list on samfirmware

sandpox said:
Looks like the last stock ROM which installed on your device is too old and its bootloader doesn't accept sign of new stock ROM, try to download another ROM but lower down in the list on samfirmware
Click to expand...
Click to collapse
okay trying with oldest one available on samfirmware
wait for my replay because free download service of samfrimware is under maintenance till 28 Nov so unable to download rom

kishorprabhat said:
okay trying with oldest one available on samfirmware
wait for my replay because free download service of samfrimware is under maintenance till 28 Nov so unable to download rom
Click to expand...
Click to collapse
http://updato.com/firmware-archive-select-model?q=gt-s7582

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7582DDUANJ1_S7582ODDANJ1_S7582DDUANI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> BcmCP.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> dt-blob
<ID:0/005> hidden.img
<ID:0/005> param.lfs
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
downloaded rom from the site you provided and it worked
thank you very much

Hello everyone.
I have a big problem i had root on my GT-S7582
On the other day the mobile phone hung up and when I went to call it it arrives the part of for the password and it restarts and it stays like this always and does not let to reset by keys somebody knows how to solve this problem? I've tried several things but it does not work.
Sorry for my english
(I'm from Portugal, Portugal phone)

SérgioVoid said:
Hello everyone.
I have a big problem i had root on my GT-S7582
On the other day the mobile phone hung up and when I went to call it it arrives the part of for the password and it restarts and it stays like this always and does not let to reset by keys somebody knows how to solve this problem? I've tried several things but it does not work.
Sorry for my english
(I'm from Portugal, Portugal phone)
Click to expand...
Click to collapse
You have to reset your phone, to do so turn it off, go to recovery(press power,home , vol up key simultaneously) then use vol key to move up down, select format or factory reset whatever is present there and then apply it.....it will fix your problem

Vishal Shrivastav said:
You have to reset your phone, to do so turn it off, go to recovery(press power,home , vol up key simultaneously) then use vol key to move up down, select format or factory reset whatever is present there and then apply it.....it will fix your problem
Click to expand...
Click to collapse
Hello.
I already did it wrong but when I go to restart it says error in big letters.

SérgioVoid said:
Hello.
I already did it wrong but when I go to restart it says error in big letters.
Click to expand...
Click to collapse
Then download odin and firmware from Google, put i in your computer, turn off your phone go to download mode(press power button,home key and volume down (not up ) key simultaneously)
Open Odin on computer select PIT/AP and locate firmware you just downloaded connect your phone through usb when it show [com 6 ] or something like that then press start, leave it till process complete, it will reboot in between the process, dont panic just wait till it say ok.....turn it on injoy, i hope you didn't installed any custom ROMs like cyanogen 12,13,14 etc. If you did, then you have to factory reset it as i mentioned earlier

Vishal Shrivastav said:
Then download odin and firmware from Google, put i in your computer, turn off your phone go to download mode(press power button,home key and volume down (not up ) key simultaneously)
Open Odin on computer select PIT/AP and locate firmware you just downloaded connect your phone through usb when it show [com 6 ] or something like that then press start, leave it till process complete, it will reboot in between the process, dont panic just wait till it say ok.....turn it on injoy, i hope you didn't installed any custom ROMs like cyanogen 12,13,14 etc. If you did, then you have to factory reset it as i mentioned earlier
Click to expand...
Click to collapse
OK thank you!
How can I find out what my original Firmaware is? And where can I find the PIT I could not find.

SérgioVoid said:
OK thank you!
How can I find out what my original Firmaware is? And where can I find the PIT I could not find.
Click to expand...
Click to collapse
http://www.samprix.com/samsung-galaxy-s-duos-2-gt-s7582-official-firmware-update/ you will find it here, just download the firmware for your contry,

Vishal Shrivastav said:
http://www.samprix.com/samsung-galaxy-s-duos-2-gt-s7582-official-firmware-update/ you will find it here, just download the firmware for your contry,
Click to expand...
Click to collapse
Did not work does not leave the part that says samsung
I do not know what else to do anymore.

Are you on stock ROM
Sent from my Intex Cloud Swift using XDA Labs
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
Muscular droid said:
Are you on stock ROM
Click to expand...
Click to collapse
Try installing TWRP recovery and flash custom ROM !!!!
Sent from my Intex Cloud Swift using XDA Labs

Successful Flashing via Odin but stuck at Samsung Logo and cannot access recovery

Hi,
I'm a new member for this community with a bit of a limited experience in Flashing.
My Samsung Galaxy Tablet 10.1 GT-N8000 was stuck in a boot loop when turning on and even when charging.
I decided to check the xda forums and similar threads regarding my issue to try out some resolution to my problem:
What I have tried so far was:
1. Tried doing the standard hard reset which was Power + Volume +/Up = No response
2. Tried Flashing the Stock ROM I got from sammobile for my region using different versions of Odin( just to check)
The flash goes successful with the following logs in Odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> param.bin
<ID:0/006> recovery.img
<ID:0/006> sboot.bin
<ID:0/006> system.img
<ID:0/006> tz.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
But when it reboots its stuck at the Samsing Galaxy Note 10.1 logo and it stays there for the longest without a hint of turning off.
As per reading previous threads about the same concern, I tried to:
-Access the recovery by pressing Power+Volume up - the screen will display the Samsung logo, then go to a blank screen the just reboots back to the "infinite logo".
-As I was desperate, I already had tried to re-flash the tablet together with a PIT file and the firmware above as well as a combination of the PIT file and just TWRP(openrecovery-twrp-2.6.1.0-p4notewifi) or Philz Touch (philz_touch_6.12.8-i9500.tar), it results to the same blank screen > reboot> infinite logo scenario.
I'd like some humble assistance from established members who had resolved this issue as I am in dire need for having this tablet fixed.
Thanks a bunch and in advance as well

Possible probable wrong PIT file used .Certainly you used wrong model recovery its not I9500 is it .
See multiple identical posts .

JJEgan said:
Possible probable wrong PIT file used .Certainly you used wrong model recovery its not I9500 is it .
See multiple identical posts .
Click to expand...
Click to collapse
Thanks for the reply.
The I9500 that I tried was for recovery file, but since it did not work, I also tried the TWRP as indicated in the post but still it had the same results
*Correction - the recovery file I used for Philz Touch was philz_touch_6.48.4-n8000.tar.md5 as JJEgan stated I used the the wrong model of recovery*
The PIT file that I used was the same one that was on this post : https://forum.xda-developers.com/galaxy-note-10-1/general/n8000-stuck-samsung-logo-t3212923 - Since he reported success in his endeavor to revive same device, I used the same PIT file, but still the same results.
If anyone could still help out, I'll be more than grateful.

thunderhavoc said:
Thanks for the reply.
The I9500 that I tried was for recovery file, but since it did not work, I also tried the TWRP as indicated in the post but still it had the same results
*Correction - the recovery file I used for Philz Touch was philz_touch_6.48.4-n8000.tar.md5 as JJEgan stated I used the the wrong model of recovery*
The PIT file that I used was the same one that was on this post : https://forum.xda-developers.com/galaxy-note-10-1/general/n8000-stuck-samsung-logo-t3212923 - Since he reported success in his endeavor to revive same device, I used the same PIT file, but still the same results.
If anyone could still help out, I'll be more than grateful.
Click to expand...
Click to collapse
Hello, did you ever find a solution? I'm facing a similar problem with my unit.
Thanks.
Sent from my SM-N920C using Tapatalk

I'm facing a similar problem with my unit.

Lack of information does not help.OP is i9500 not Note 10.1.
Read the thread. Search your problem.