i tried rooting my samsung galaxy tab 3 10.1 wifi using cf auto root zip using odin ... i ticked nand erase all and started to root .... then my device suffered bootloop ... i have installed many firmwares from samsung updates but again there is bootloop ..... so someone please help me to recover my tab ... i have cleared cache , done reset but nothing happens .... if someone has full firmware files downloaded from dlgsm.com ...... the please help me by giving me the firmwares ... you can upload it to your mega or other accounts ....... i'd be hopeful .....
Praw zoll said:
i tried rooting my samsung galaxy tab 3 10.1 wifi using cf auto root zip using odin ... i ticked nand erase all and started to root .... then my device suffered bootloop ... i have installed many firmwares from samsung updates but again there is bootloop ..... so someone please help me to recover my tab ... i have cleared cache , done reset but nothing happens .... if someone has full firmware files downloaded from dlgsm.com ...... the please help me by giving me the firmwares ... you can upload it to your mega or other accounts ....... i'd be hopeful .....
Click to expand...
Click to collapse
Why did you tick nand erase all ???
If you installed stock rom with ODIN and it didn't fix your problem, then your NAND (whole EMMC precisely) is probably corrupted. If so, I'm afraid you'll need hardware repair to fix it.
Related
Hi
sorry guys i cant seem sot find help thread so i do apologize if this is a wrong thread.
my samsung gt-8500 wont boot hangs on samsung mobile logo / can go to download mode
so i tried flashing with S8500DXJEA and S8500DXJE8 since im from the Philippines by using multiloader v.5.65
i followed instructions up to the details but still getting
Download Start Ch[0]
Amss 12822.2KB OK[5.1s]
Apps 52428.8KB OK[24.7s]
ERR : Rsrc1 Erase
the reason why im flashing is because after upgrade to bada 1.2 after a few days my phone wont boot stuck on logo samsung mobile.
anyone has idea how to fix this thank you in advance.
same problem!!
Hi,
I installed Bada 2.0 on my Wave 2(S8530) and then when I tried to revert back to 1.2 my phone got bricked and was not even able to go in to download mode.
it was completely off.
I took it to a person who had a Riff Box and he was able to get the phone in Download Mode, but when we tried to install any firmware, it didnt work
I tried installing Europe 2.0 XPKJ, its getting installed completely but the phone freezes at bada logo.
Plz help!!!!!!!!!!!!!!
I took it to a person who had a Riff Box and he was able to get the phone in Download Mode, but when we tried to install any firmware, it didnt work
Click to expand...
Click to collapse
If "he" ... user with RIFF Box has used erase option or tried to write FULLdump of other handset.
Then NV items are erased... like IMEI and so on...
I have done this on my S8500 with using oldest Firmware...
XXJEB if I remember correct... then my handset was alive and I was able to RESTORE NV items...
I have NO idea, how to solve this only with RIFF Box...
Before I have fixed my problem I have tried MANY combinations... See here:
http://forum.xda-developers.com/showpost.php?p=20429368&postcount=42
Few posts later I have solution found for me.
Best Regards
Hi guys resolved the error
try to use complete/full FW that includes boot files and factory
happy reflashing
Hi Guys, for a reason or another my note 8 is stuck on Samsung logo and not starting up , its not rooted and I did a reset to default settings and still same issue.... they told me at the repair center that due to a virus , there are some files missing and they need to buy it or install it from the us server ......so , what is the best thing to do now ??
Try going into custom recovery and doing the factory reset.
If you have no custom recovery, booting into uploader mode and flash the proper from from sammobile or samungis. You will loose everything when you flash the OEM firmware.
Be sure to to use Odin 3.07.
At least you will be able to use your device again.
Thanks for the prompt reply ,i already reset it to factory sett from custom recovery and still the same , can you tell me how to boot it into uploader mode ?
alaasagaa said:
thanks for the prompt reply ,i already reset it to factory sett from custom recovery and still the same , can you tell me how to boot it into uploader mode ?
Click to expand...
Click to collapse
do you mean i should normally root my device ?
Hello fellow community!
On first place i want to excuse myself for my bad English!!
I have soft bricked T-Mobile (USA) Samsung Galaxy S4 and everything i found in the web DIDN'T help me to recover my phone...
Here is my history for what i did to bring this condition of my phone.
I was on Original T-Mobile 4.4.2 Stock ROM working normal without any issues. But 2 or 3 months ago i was curious about installing on my phone CUSTOM " CYANOGENmod" rom 5.x.x NIGHTY edition. At all installing on that custom ROM was without problems and phone for this 2~3 months works flawlessly "normal"... all this time i updates every day this custom theme and I'm understand this is NIGHTY but at the end i was kind tired from this NOT exactly real and fully functioned replica of custom ROM and get decision to restore my ORIGINAL status of the phone and put latest (4.4.4) Stock ROM. 1st i download 4.4.4 ROM "M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5" for my T-Mobile phone. I put in in DOWNLOAD mode. Connect phone to my computer.. and Start ODIN3 v3.10.6 ( didn't install Samsung drivers because i already have installed them !! ). In AP i put latest ROM... checked was ONLY options Auto Reboot and F. Reset Time ... NO Re-Partition was checked or pit file wasn't given !! Jus i hit the SATRT and receive that !...
everything was fine till the end !!! Flashing stops on try to flash hidden.img.ext4 with error and FAIL all process !!!
I CANT understand where is my problem and what i can do to flash my phone normally?
Please community help me to solve this problem..
1 year ago i have almost the same problem but with the same error "firmware upgrade encountered an issue" and remember here on XDA DEVELOPERS i read the guide how to recovery phone after that but TBH i cant find this guide now with all my searching attempts..
Please for HELP!
and Thank you in Advance for your support!!..
Cheers!
Not 100% sure but you needed to do a factory reset before flashing stock firmware.
You can't flash kitkat over lollipop before doing factory reset because they are two different firmwares.
Try doing a factory reset and flashing again, if it fails pull battery, replace battery and go straight into download mode, connect to pc and flash again with odin.
Sometimes the double flash can be successful.
Good luck.
Pp.
thank you for replay!! but I [SOLVED] my problems!!!
iceBringer said:
thank you for replay!! but I [SOLVED] my problems!!!
Click to expand...
Click to collapse
Would be nice if you could share your solution for others that may have the same problem
Hi all !
So two days ago i wanted to update my Sm-t310 to 4.4.2 from the tab itsself, but it wasn't possible, because i had rooted it before. So i tried to remove my root and then something happened and my tab got stuck in firmware upgrade encountered an issue. please select recovery mode in kies & try again charging battery screen.. i looked for solutions with both kies and odin, but they get stuck at 7% while flashing????? Nothing seems to work, i tried it even through the philz recovery mode after wiping cache and deleting cache partition, but it only gets stuck at the boot loop and then when i try to flash it with odin it gets stuck on system.img at about 7%... I really don't know what to do :crying: Please help me, I am desperate !
Hi,
This thread is being moved to your own dedicated forum, where the experts may be able to help you better.
Good luck!
benzomarie said:
Hi all !
So two days ago i wanted to update my Sm-t310 to 4.4.2 from the tab itsself, but it wasn't possible, because i had rooted it before. So i tried to remove my root and then something happened and my tab got stuck in firmware upgrade encountered an issue. please select recovery mode in kies & try again charging battery screen.. i looked for solutions with both kies and odin, but they get stuck at 7% while flashing????? Nothing seems to work, i tried it even through the philz recovery mode after wiping cache and deleting cache partition, but it only gets stuck at the boot loop and then when i try to flash it with odin it gets stuck on system.img at about 7%... I really don't know what to do :crying: Please help me, I am desperate !
Click to expand...
Click to collapse
Since you mentioned that you still have your Philz custom recovery, have you tried flashing a rom. It may or may not work, but it is worth a shot.
My samsung grand dous got suddenly off and I had to flash stocks rom with Odin again but the problem is that every time try to flash it strucks on initialsation or setup connection... I tried with multiple ports and Odin versions.. replace battery also but no sucess .. tried pit file then it shows nand write start .. failed
Help please
pratyaksh tyagi said:
My samsung grand dous got suddenly off and I had to flash stocks rom with Odin again but the problem is that every time try to flash it strucks on initialsation or setup connection... I tried with multiple ports and Odin versions.. replace battery also but no sucess .. tried pit file then it shows nand write start .. failed
Help please
Click to expand...
Click to collapse
SOrry wrong forum..
pratyaksh tyagi said:
SOrry wrong forum..
Click to expand...
Click to collapse
Have you asked in your particular phone's model's forum? That should help since we don't even know what phone you have!!
Thanks for moving the thread ..
someone please help with my issue
pratyaksh tyagi said:
My samsung grand dous got suddenly off and I had to flash stocks rom with Odin again but the problem is that every time try to flash it strucks on initialsation or setup connection... I tried with multiple ports and Odin versions.. replace battery also but no sucess .. tried pit file then it shows nand write start .. failed
Help please
Click to expand...
Click to collapse
When I face this problem, i just check the file which im flashing, sometimes it might have not downloaded properly or you might just be flashing firmware of another mobile. Has always worked for me, hope i helped