Database Info

[Q] Possible bricked Motorola Xoom - Please help!

Hi all, I recently got up the courage to attempt to install 3.1 on my UK Wifi xoom. I started by unlocking the bootloader. All went ok. Next I followed instructions on how to install the ClockworkMod Recovery. Installed it fine but couldn't boot into it.
Then rebooted to find my wifi had an error so i decided to perform a factory reset. The device rebooted into ClockworkMod Recovery and for some reason i played around with the 'Partition SD card' and made a partition... "I think".
It then turned off.. and nothing. I have tried the volume up + power button etc etc...
Any solutions or advice? PLEASE!?!

is it still recognized by PC in ANY way?

lexarjump said:
Hi all, I recently got up the courage to attempt to install 3.1 on my UK Wifi xoom. I started by unlocking the bootloader. All went ok. Next I followed instructions on how to install the ClockworkMod Recovery. Installed it fine but couldn't boot into it.
Then rebooted to find my wifi had an error so i decided to perform a factory reset. The device rebooted into ClockworkMod Recovery and for some reason i played around with the 'Partition SD card' and made a partition... "I think".
It then turned off.. and nothing. I have tried the volume up + power button etc etc...
Any solutions or advice? PLEASE!?!
Click to expand...
Click to collapse
Sorry, but this sounds bad. Really bad.
Do a search through these forums. It appears that trying to partition using CWM ends up bricking the Xoom to the point that sending it to a service center and feigning ignorance is your only recourse.
Search through the forum, I hope I am wrong...but I don't think I am.

Not recognized at all - The only life i get out of it is the charging light.

i try to understand what you actually tried? u inserted a not-working sd in the SD-Slot and tried to partition it with CWM ?

Darn. I have had a quick look. I have a local technician looking at it at this present. But you have a good point. I could just say i hadn't a clue what i was doing.

lexarjump said:
Darn. I have had a quick look. I have a local technician looking at it at this present. But you have a good point. I could just say i hadn't a clue what i was doing.
Click to expand...
Click to collapse
that enlarges the possibility for the brick....
as far is this is know, i cant be of help, hopefully someone else can!
i wish good luck!

RinTinTigger said:
i try to understand what you actually tried? u inserted a not-working sd in the SD-Slot and tried to partition it with CWM ?
Click to expand...
Click to collapse
No i did a factory reset and was presented with clockwork mod recovery and messed around with the partition SD card (There was no SD card in slot) created a partition, pressed reboot and didn't turn back on.

lexarjump said:
No i did a factory reset and was presented with clockwork mod recovery and messed around with the partition SD card (There was no SD card in slot) created a partition, pressed reboot and didn't turn back on.
Click to expand...
Click to collapse
erm....if there was no SD Card in....how could CWM partition a SD card??

I have no idea. It gave me the option to do it. So i tried it basically. Biggest mistake of my life.

lexarjump said:
I have no idea. It gave me the option to do it. So i tried it basically. Biggest mistake of my life.
Click to expand...
Click to collapse
Okay, keep your head up. its no use in argueing, why u did what. i just wanted to understand what u did exactly.
I hope someone can assist u.... sorry for u man

Well there was no fix. I took it back into Curry's/PCWorld and they replaced it. I blamed it on the fact that the battery overheated. No questions asked.
But cheers for all of your advice guys! Much appreciated

lucky u....now NEVER do something you dont know a single FU** about

lexarjump said:
Well there was no fix. I took it back into Curry's/PCWorld and they replaced it. I blamed it on the fact that the battery overheated. No questions asked.
But cheers for all of your advice guys! Much appreciated
Click to expand...
Click to collapse
Good for you, in the future please do those of us that make a living on technology a favor and dont ruin your device and then ask the store you bought it from to take responsibility for your mistake.
Hope you enjoy your replacement Xoom and please do me more careful with it.

[Q] Nexus S 4G won't boot past Google Screen!!

I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??

There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).

Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?

deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.

It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )

deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?

deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.

I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.

deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps

Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.

same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...

nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David

I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.

[Q] Is rebooting Android the same as a P.C.?

I know when you reboot a p.c. you dont lose any setting . I get the feeling that is not the case with Android. Can someone confirm?
Thanks and sorry for the noob question.

shaggyskunk said:
I know when you reboot a p.c. you dont lose any setting . I get the feeling that is not the case with Android. Can someone confirm?
Thanks and sorry for the noob question.
Click to expand...
Click to collapse
wtf?
of course you dont 'lose settings' by rebooting.
what exactly makes you think it would work otherwise?

Pirateghost said:
wtf?
of course you dont 'lose settings' by rebooting.
what exactly makes you think it would work otherwise?
Click to expand...
Click to collapse
Well it seems from stuff that I have read, that a reboot is often compared to a factory reset?
It did not make sense that a reboot would wipe the setting, but I just wanted to be sure.
Thanks!

shaggyskunk said:
Well it seems from stuff that I have read, that a reboot is often compared to a factory reset?
It did not make sense that a reboot would wipe the setting, but I just wanted to be sure.
Thanks!
Click to expand...
Click to collapse
a reboot is not compared to a factory reset.
i dont know what you have been reading, but a factory reset is definitely not equal to rebooting the phone.

+1 all you settings remain intact when u reboot the device. Think about how much of a pita it would be if it did not. No one would buy an android device, and if it could not save you settings data then also your Apps would be lost upon each boot. I have no idea where someone would have claimd this but its so far from the
A factory data/wipe reset does remove all user data

amazing........i loved this question
i may put that in my Sig

silver03wrx said:
+1 all you settings remain intact when u reboot the device. Think about how much of a pita it would be if it did not. No one would buy an android device, and if it could not save you settings data then also your Apps would be lost upon each boot. I have no idea where someone would have claimd this but its so far from the
A factory data/wipe reset does remove all user data
Click to expand...
Click to collapse
Thanks AGAIN Silver! I have had an Android for all of three weeks, but if it were any Win
sys I would be right at home.
I had read on a few sites that a reset would clear all of your personal info and any d/l s/w?
My next step is to root the phone. It's too bad that you can't just boot from a back up if you mess up, and just reinstall the whole O/S...but from what I can tell, you can't just get a virgin copy of the Android O/S.?

Well in this thread it is the virgin copy of our factory firmware. If u ever mess up u can use Odin in this thread to flashing back to stock.... http://forum.xda-developers.com/showthread.php?t=1342348
But also u can make backups that restore every thing before u messed up which will fix ya in most situations. Its called a nandroid backup. Once u root boot into cwm recovery, and click back up restore then select backup. Now anytime u want to go back to how your phone was when u made that back up u just ...boot into cwm click backup restore select restore and choose that restore point..... its just like the system backup/ restore in windows

silver03wrx said:
Well in this thread it is the virgin copy of our factory firmware. If u ever mess up u can use Odin in this thread to flashing back to stock.... http://forum.xda-developers.com/showthread.php?t=1342348
But also u can make backups that restore every thing before u messed up which will fix ya in most situations. Its called a nandroid backup. Once u root boot into cwm recovery, and click back up restore then select backup. Now anytime u want to go back to how your phone was when u made that back up u just ...boot into cwm click backup restore select restore and choose that restore point..... its just like the system backup/ restore in windows
Click to expand...
Click to collapse
THANKS AGAIN!!
Nandroid requires root, right? I guess that's why some are nervous when delving into new territory..like me.

Yeah u need to be rooted and have cwm recovery. You do the nandroid backup/restore in cwm recovery

HELP! Brick Bug!

So long story short, my tab was running stock ICS (rooted, with temp CWM/cwm.zip). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Do I have the Brick Bug?

rumpypumpy said:
So long story short, my tab was running stock ICS (rooted, with temp CWM). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Click to expand...
Click to collapse
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers

gmaster1 said:
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
Click to expand...
Click to collapse
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...

rumpypumpy said:
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
Click to expand...
Click to collapse
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers

gmaster1 said:
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
Click to expand...
Click to collapse
I forgot about download mode. I'll have a go then I'll report back.
Thanks

Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction

rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866

rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
If cwm works then we both know theres hope
Sent from the phone of Gamers

lsherif said:
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
Click to expand...
Click to collapse
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually

rumpypumpy said:
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
Click to expand...
Click to collapse
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers

gmaster1 said:
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
Click to expand...
Click to collapse
:crying:
I was reading the following articles:
http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
http://forum.xda-developers.com/showthread.php?t=1810954
Could this Brick Bug be the source of my problems?
I was running a leaked version of ICS AND I have been using the cwm.zip so there is the possibility

Being unable to flash through either Odin or CWM surely sounds a lot like the brickbug.
If I were you, I'd reboot to download mode, and install a full ROM with repartition + PIT file. If it works, install locerra's CWM (it's one of the few recoveries for our tablet that's confirmed to be brickbug-free), and work as usual. But remember to wipe everything before installing anything through CWM...
If Odin doesn't work, you probably have been hit by the brickbug. However, all is not lost: this guy seems to have found a "fix" for many devices. It involves giving up on all your data and making your onboard storage a couple of GB smaller than it used to be, but it can make your device work again. Read the thread, try to understand it, and (if you can't find another way out) use the PIT file for the GT-6800 provided. If your tab isn't the international WiFi+3G GT-P6800, you may have to ask the guy (hg42) for a PIT tailored to your device.
The other option, in the case of a eMMC-related brick, is to remove all traces of CWM, go to a Samsung store and repair it under warranty, saying "its broke down when I were running that backie upppe thing in kies".

The other option is the better one, as i bricked my note. When i am able to revive it, i am left with 8GB space and it seems real laggy. Change a new motherboard would be better if still cover undr warrantly.
Sent from my GT-P6800 using xda premium

Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks

rumpypumpy said:
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
Click to expand...
Click to collapse
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.

Steve_max said:
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Click to expand...
Click to collapse
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:

rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Thats...a...problem...if it takes longer then 15 mins its bricked...i have been a gt user and devs on other sites told me it was bricked. Maybe there is a solution but...i havnt found one. It should never take too long on one thing in odin.
Sent from the phone of Gamers

rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.

Steve_max said:
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Click to expand...
Click to collapse
The warrenty is not void unless they find proof of tampering with system files. So basicly yeah...everything that guy said. Get it as close to stock as possible and send.
Sent from the phone of Gamers

Right OK, I definately don't want my warrenty void!
So would it be ok if I flashed 'P6800OXALQ1_P6800XXLQ1_HOME.tar.md5' (minus the factoryfs.img) to my tab?
Thanks

PLEASE HELP Nand Erase all, boot loop

My Note Edge N915F volume down stopped working
i wanted to know if it's software so i went to safe mode, but nothing brought it out of safe mode.
so i flashed the latest Firmware but i realized the (( Nand Erase all )) option was on, ( laptop is touch screen )
now the phone is in boot loop. i reflashed the firmware but nothing.
i can't go to Recovery mode because volume doesn't work but i can only go to download mode with on OTG device i bought before.
is there anything i can do to fix it?

anyone can help? i have a dead expensive phone on my hand now.

omid_freesky said:
anyone can help? i have a dead expensive phone on my hand now.
Click to expand...
Click to collapse
try to flash custom recovery, if any available there... wipe data and cache, then you need to install stock rom. so download stock rom for your country first.
Maybe it helps.

omid_freesky said:
anyone can help? i have a dead expensive phone on my hand now.
Click to expand...
Click to collapse
You may need to take back to Samsung...
No-one wants to give advice that can get you deeper into trouble than you already are...
Let this be a lesson, before you hit "start" make sure nothing but reset and f-reset time is ticked... All else can cause serious problems... Hopefully won't be an expensive lesson...

opethianskies said:
try to flash custom recovery, if any available there... wipe data and cache, then you need to install stock rom. so download stock rom for your country first.
Maybe it helps.
Click to expand...
Click to collapse
here is the problem, i can't go to recovery because volume down didn't work, and this is why i end up flashing firmware.
i want to know if there is another way to go to recovery .

ultramag69 said:
You may need to take back to Samsung...
No-one wants to give advice that can get you deeper into trouble than you already are...
Let this be a lesson, before you hit "start" make sure nothing but reset and f-reset time is ticked... All else can cause serious problems... Hopefully won't be an expensive lesson...
Click to expand...
Click to collapse
i can take any advice at this point. i can't take it to samsung because i might be the only one who owns this phone here. the local service said they can do nothing.
i've flashed a million times and this is the first time this happened to me. and Yes it is an expensive lesson, $1,200 expensive

omid_freesky said:
here is the problem, i can't go to recovery because volume down didn't work, and this is why i end up flashing firmware.
i want to know if there is another way to go to recovery .
Click to expand...
Click to collapse
you don't have to go into the recovery, you need to go download mode and flash custom recovery there...
feel sorry for you, custom roms or the roms that are not verified by samsung, are risky as hell. I flashed my Note II million times, but now i'm not interfering with my Note Edge.
may be you had better bring your phone to an authorized service. this doesn't seem to be a software problem.

opethianskies said:
you don't have to go into the recovery, you need to go download mode and flash custom recovery there...
feel sorry for you, custom roms or the roms that are not verified by samsung, are risky as hell. I flashed my Note II million times, but now i'm not interfering with my Note Edge.
may be you had better bring your phone to an authorized service. this doesn't seem to be a software problem.
Click to expand...
Click to collapse
i flashed the custom recovery, nothing changed.
unfortunately we don't have authorized service here.

omid_freesky said:
i flashed the custom recovery, nothing changed.
unfortunately we don't have authorized service here.
Click to expand...
Click to collapse
Have you tried to flash stock rom for your country. Go sammobile and find your stock rom for your country, at least you can open your phone again.

opethianskies said:
Have you tried to flash stock rom for your country. Go sammobile and find your stock rom for your country, at least you can open your phone again.
Click to expand...
Click to collapse
it is the first thing i did, i flashed stock Firmware when the Nand Erase all was accidentally on, and i flashed it again (without Nand) but it didn't fix.

Possibly your phone has gone into bootloop. Release the battery for one minute. Then plug the battery again, Try to flash Rom with an higher Odin version...
However I found a solution in XDA
Quote:
Originally Posted by samersh72 View Post
before flashing param.tar. go into recovery, if it is possible, wipe data and cache, then flash with odin the stock firmware in pda with the pit file in pit window. just check auto reboot, f.reset and re-partition. when it say "pass" remove battery, re-insert it, go to recovery, wipe data and cache reboot.
if it didnt work, unzip attached file and flash "param_I9505.tar" in pda. (without pit file)(dont tick re-partition)
im afraid that ticking "nand erase all" in odin, usually lead to a hard brick!
Duuude! It worked!!!!
Even without flashing param partition. Just the first step:
Quote:
go into recovery (I flashed CWM with Odin), if it is possible, wipe data and cache, then flash with odin the stock firmware in pda with the pit file in pit window. just check auto reboot, f.reset and re-partition. (then it went into bootloop as usual and after a moment Odin said "pass") when it say "pass" remove battery, re-insert it, go to recovery (the recovery at that moment returned to stock), wipe data and cache reboot.
And ta-daaa! It works now. Ahhh! that was close! )))
You should write this instruction for [email protected] like me.
You can't imagine how I'm grateful to you!

opethianskies said:
if it didnt work, unzip attached file and flash "param_I9505.tar" in pda. (without pit file)(dont tick re-partition)
Click to expand...
Click to collapse
The param_I9505.tar this refers to is for the Note 4(international). Are you REALLY sure this won't cause more problems? It's hard enough to fix something when you don't know what's wrong but adding another ingredient into the mix can REALLY make the brown stuff hit the whirlygig...
Also, Op shouldn't have flashed custom recovery, you need to send back to Samsung... Its possible you may have triggered the Knox warranty void. You may have to pay $$$ now to get it fixed....
Fooling around more will make sure you have a $1200 paperweight...

ultramag69 said:
The param_I9505.tar this refers to is for the Note 4(international). Are you REALLY sure this won't cause more problems? It's hard enough to fix something when you don't know what's wrong but adding another ingredient into the mix can REALLY make the brown stuff hit the whirlygig...
Also, Op shouldn't have flashed custom recovery, you need to send back to Samsung... Its possible you may have triggered the Knox warranty void. You may have to pay $$$ now to get it fixed....
Fooling around more will make sure you have a $1200 paperweight...
Click to expand...
Click to collapse
yeah it's solution for note 4 but i assumed that he already knew that... OP must have flashed proper file for his phone... I'M not referring Note 4 here.