A friend of mine, who used a stock samsung rom (i think it was jvt) with a rooted kernel received an mms which didn't want to display the picture. he clicked a couple of times on it nad then everything began:
- First problem, the phone froze and then it was stuck on boot loop. That was when he called me and asked for help. i adviced him to do a full wipe and try again, no success.
- than i told him to mount his internal sd card, to put a rom on it and flash it. but his pc didn't recognize it.
- i told him to put it on his external sd. I knew, flashing from external sd could cause some problems, but it helped me sometimes. everything went fine. phone booted up, but asked for a pin and displayed something like "encryption failed". So it adviced him to wipe, what didn't help
-the next they i got his phone. First thing i tried was to flash a 3file-stock rom, but it ended with a dbdata errer after installation, so it bootlooped again. Then i tried to install dozens of roms, with repartition, without repartition, a one zip-rom, only the missing dbdata. nothing helped.
- my last attempt was to flash an older froyo rom, which i flashed with pit and repartition. Now recovery and download mode are gone. only thing it does is dislpaying "galaxy s" and turing off again.
long story short: the phone is totally bricked now and i have no idea what to do?
Any ideas?
madphone said:
A friend of mine, who used a stock samsung rom (i think it was jvt) with a rooted kernel received an mms which didn't want to display the picture. he clicked a couple of times on it nad then everything began:
- First problem, the phone froze and then it was stuck on boot loop. That was when he called me and asked for help. i adviced him to do a full wipe and try again, no success.
- than i told him to mount his internal sd card, to put a rom on it and flash it. but his pc didn't recognize it.
- i told him to put it on his external sd. I knew, flashing from external sd could cause some problems, but it helped me sometimes. everything went fine. phone booted up, but asked for a pin and displayed something like "encryption failed". So it adviced him to wipe, what didn't help
-the next they i got his phone. First thing i tried was to flash a 3file-stock rom, but it ended with a dbdata errer after installation, so it bootlooped again. Then i tried to install dozens of roms, with repartition, without repartition, a one zip-rom, only the missing dbdata. nothing helped.
- my last attempt was to flash an older froyo rom, which i flashed with pit and repartition. Now recovery and download mode are gone. only thing it does is dislpaying "galaxy s" and turing off again.
long story short: the phone is totally bricked now and i have no idea what to do?
Any ideas?
Click to expand...
Click to collapse
Its not totally bricked cause it turns on.
Buy a JIG and connect to phone then download will appear
flash stock rom then get warranty if still not working.
thanks, so i hope i'll get the jig soon. what would you flash then?
madphone said:
thanks, so i hope i'll get the jig soon. what would you flash then?
Click to expand...
Click to collapse
i would flash stock using odin. then if that works root, flash custom and etc.
If the flashing fails then just fix it from support or try again with JIG.
If u fully stuff up your phone and it doesn't even turn on, go to samsung
and say it stuffed up while u were updating it and hopefully they will fix it for you!
ok so that's what i'll do. any suggestion which specific ROM i should flash? One file rom or 3 file roms? Gingerbread or froyo? do i have to flash a fresh bootloader?
madphone said:
ok so that's what i'll do. any suggestion which specific ROM i should flash? One file rom or 3 file roms? Gingerbread or froyo? do i have to flash a fresh bootloader?
Click to expand...
Click to collapse
To be honest i'm kinda new with rooting and etc on the SGS, but luckily had heaps of experience on my other android phone.
Well if i was you i would do some research on how to unbrick bricked phones, there should be heaps of vidoes on youtube.
Then i would ask here, then do pray that everything will go well and flash stock rom with ODIN. Well i would prefer GingerBread but it doesn't matter which one.
But if it does stuff up flashing Froyo would be better so you can make the excuse of updating to GingerBread and stuffing up.
Have you tried odin? Does it recognize the phone when you are in download mode? If you cannot go into download mode, find a usb jib for i9000 (cca 10e) and you will get into download mode. Then flash some XXJVU with odin. After that try Slim ICS 3.0 works flawlessly for me!
Sent from my GT-I9000 using XDA
so this is going to get even more weird:
suddenly the phone started on its own and booted, but i was almost not responding and it was russian i think. then i removed the sd and it didn't want to boot anymore. when i reinsert the sd it boots, but only with this specific sd.
so i decided to make myself a jig to get into download mode. that was no problem, so i flashed jvq with odin. everything went fine, no errors anymore right after flashing. the phone restarted but it wasn't responsive like before. so i flashed again, this time without sd card. but now after flashing there ere some erros like "can't mount media...)
result: the phone won't boot up anymore?
something must have linked the sd card to the phone. to you have any idea? maby flashing bootloaders?
i have flashed dbdata cause it was still mentioned as missing in the error report right after flashing. result: completely bricked phone. It stays off, no jig helps anymore...
Read broodplanks guide to unbrick i9001, may work on ur phone. Or try another sd card, unplug the battery, try everything..
Btw what's ur friends phone? I9000 ?
Sent from my S+
Related
So im rooted, clockworked and nandroided. i go into rom manager and attempt to partition the sd, everything looks like it went fine. i get the samsung splash tmo bootup then it goes from the S splash screen to what seems to be a soft brick, just a blank screen and four lit up buttons. i try to boot into clockwork and i get the factory recovery mode. Clockwork is nowhere to be found. my sd card appears to be partitioned it shows a 14.8g card on a 16g, but the sd card still has everything on it, it did not get wiped. i have tried using odin, all that happens there is it runs through the motions, resets the phone back into this soft brick. anyone have similar issues or helpful ideas? i will be slowly bashing my head into the wall waiting for a reply. thanks in advance, any help will be appreciated
Same Problems Here
I came on to post and hopefully find a solution for a very similar problem. I rooted, clockworked, and nandroided my vibrant this morning and it worked fine all day. I got home and realized my phone was locked and didn't respond to the unlock button. I pulled the battery and rebooted and it all seemed fine. 5 minutes later i realized it wasn't responsive and once again pulled the battery and now won't boot past the "S" boot screen and seems to freeze. Now my clockwork restore won't backup and says it can't mount. I've tried a factory reset to no avail. Anytime I attempt a clockwork recovery I get the error
E:Can't mount /dev/block/mmcblk0p2
(file exists)
Can't mount /data/!
Any suggestions or solutions would be greatly appreciated.
I'm having the same issue, any help would be greatly appreciated.
did anyone get any help??
Same thing happened to me. I posted such on the market comment for rom manager. I ended up taking mine back to Best Buy (got another). I'm wanting to install linux on mine. Anyone been able to do that?
I hate to tell you this but you just partitioned the internal memory. If you had actually read the thread on clockwork recovery you would have seen that you cannot currently partition the external sd card with clockwork.
so what do i do??
nickerrides said:
so what do i do??
Click to expand...
Click to collapse
I honestly don't know the answer to that question. I'm kind of a casual flasher of my phones and I've never "bricked" one or had any major problem. I believe it can be fixed by using odin to flash back to stock. I'm pretty sure that you can recovery from it but it may take some work.
I would start by reading the entire clockwork recovery thread in the Android Development section. A few other people have made that mistake and may have a solution posted there. I'm at work posting from my phone or I would go look and try and find it.
Okay, I did some digging in that thread and it appears all you need to do is to use the re-partition option in Odin and then use Odin to flash a stock ROM and you should be all set.
Again, I have not used Odin myself so I don't know how easy/hard that is to do or if it will work at all.
nope i tried the repartition option in odin while flashing the stock rom.
With mine, I had success and got it out of the boot loop by using odin and flashing it back to stock.
The phone seems unbrickable, as
others have mentioned, just get it into download mode and use odin carefully.
Sent from my SGH-T959 using XDA App
wanna be more specific on what exactly you did?
Hey I just seriously screwed my self over bassicly I tried to get miui to boot from the samsung fascinate however when I installed it in cmr it spassed out then powered of then went to the bootloader and I get a red error message saying can't mount data or something so then I tried to reinstall Eco 3 Odin using Odin and it worked it booted but it says I have zero data on my phone and I can't install anything. I also tried the oneclick soft unbricker but it fails saying adb divers are not installed when they are. I'm doing this on my phones browser witch is the only thing that seems to be working right now I also tried a band restore but I got the same data error message.
Have you tried restoring to DL17 and then re-upgrading to 2.2?
And how about a good old odin flash?
In worst case, I would ask imnuts for the full odin package, or use a fascinate full odin package to get you off your feet, then reflash the modem, and recovery, then wipe In recovery cyan cwm... Then flash ec03
Sent from my SCH-I400 using XDA Premium App
wait wait, is this on a Continuum or Fascinate?
Nuckin said:
wait wait, is this on a Continuum or Fascinate?
Click to expand...
Click to collapse
He is on a Continuum, but you can use a fascinate Odin package to reformat partitions if they get messed up, then just reflash recovery and start fresh if you can get in then... That wasn't a really good thing though to suggest to a newcomer necessarily, so thank you for pointing that out
okay heres what happened firts i wanted to see if i could get the miui rom for the samsung fascinate to boot on the continuum there pretty much the same phone minus the ticker and screen size so i went into clockwork mod and wiped everything then went to install zip from sd card and clicked on the miui rom witch was the process we always used on the hero. then after i clicked on it, it started to install then my screen started shacking and my phone turned off. when i turned it back on it when to the bootloader and a red error message poped up saying
e:cant mount /dev/blockstill(invalid argument
and when i go to recovery it says the same thing when i try to wipe/restore nand it says the same thing. so at that point i powered off and went to download mode and reinstalled eco3 odin using pda mode on odin and it worked then it rebooted and i got to the set up screen and i got 2 force closes daily brefeing and something else i went ahead and skipped all that stuff and it loaded fine after that. however now for some reason it says i have zero system memory so i cant install any apps or save data however it does recognize my sd card but i cant install to sd card. so bassicly the phone functions just no internal memory. at this point i honestly dont know what to do everything on the hero was simple and straight forward and we never ran into these kind of problems. ive also tried to restore my nands and reinstall clockwork mod but still no dice. what i need to do now i guess is get the necessary files to go completely stock and see if that helps. and if someone could point me in the direction to those files i would really aprechiate it. oh and i tried the one click unbricker it sayed success but didnt really do anything.
oh and i know trying to install miui was stupid but i was just wanting to see if it would boot lol.
Download the PIT file in the Development forum, as well as the DL17 Odin package from the FAQ of the EC03 post I made. Flash the DL17 in PDA, with the PIT, and re-partition selected. After that, you should be back on DL17, and can do whatever you want from there.
huzzza!!!
thank god that worked thank yall so much i still cant believe that just happened but restoring the stock odin image worked and all is well. so i guess tommorow i can reroot and restore my nand.
once again thank yall for the help.
Ok i was on ICS passion then all of a sudden my phone said something about encryption an that it had failed an only option was to reset phone so i hit reset then it went to recovery mode an green android came up with chest open then error message happened an so i booted in to recovery then i try to go in sd an it would not allow me to so i then tried to odin an flashed then i powered on it gies to vibrant screen then it just shuts off so i then flashed Eugene froyo that does not brick then it takes me to stock recovery an says an i cant click on anything in recovery can only move -- movi_checking done!...
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
Here are instructions i have followed an no luck http://forum.xda-developers.com/showthread.php?t=1043892
Ok I think you got some extra cache or some other piece of data that did not get wiped. either way, do this in this sequence and you should be ok
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Load the JFD rom for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
15. Then, root the phone and you can flash your new Rom.
doing this method will get everything back to normal and the phone will work just like it did right out of the box
It is #7 that is important when it reboots into recovery after froyo that does not brick then pull the battery and go back into download mode and flash the JFD, This will clear everything out and put you back into stock
Good luck
Got it started
I got it booted though a very hard process an now i cant get my sd card to mount it says when i go into anything media related it says "Your phone does not have a SD card inserted" an Externel dont mount either
Which sd card isnt working... internal sd, or external sd?
kf7strng said:
Which sd card isnt working... internal sd, or external sd?
Click to expand...
Click to collapse
Both of them aren't working
Jasonhunterx said:
Both of them aren't working
Click to expand...
Click to collapse
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737
jrafael said:
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737
Click to expand...
Click to collapse
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger
Jasonhunterx said:
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger
Click to expand...
Click to collapse
Hey Jason. I'm in the exact situation you're in. Loaded Passion for about 1 week, got the encryption screen and was forced to reset. Now my SD cards (internal and external) won't load. Have you found a work around for it yet? Cheers Mate.
nope nothing
either of you find a solution? Im having same issue
In the same boat
I am in the same boat. I was using the Euphoria ROM. Yesterday things slowed down on the phone. I rebooted a few times and it crashed. The last couple of times it told me about the encrypted data. That was when I tried to take it back to stock and it won't do anything now other than boot to the vibrant logo and shutdown. Searching for a way to odin a ROM/Kernel that has a CWM recovery so I can go in and manually format the SDcard.
Do what I did, sell it to someone as a wifi hotspot and buy yourself a hercules. You'll never look back
Sent from my SAMSUNG-SGH-T989 using XDA
BUMP
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.
webstas said:
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.
Click to expand...
Click to collapse
Try this one.
http://forum.xda-developers.com/showthread.php?t=1580902
Sent from my Vibrant using Tapatalk 2
Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.
Woodrube said:
Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.
Click to expand...
Click to collapse
no i got up an took a shower then came back it gave me an encryption error then i odin back an more trouble odined a couple more times an now it boot loop an also wont start with eugenes froyo
I know it has been awhile but think back. Were you mounted to your PC at anytime between your last reboot and the Encryption Error? Doesn't have to be right before, the error gets throw on your "next" reboot. And as you know, reboots can happen manually or for something as simple as wrong UV settings.
Looking back in this thread, I saw that you got it to boot up. See if you can do that again and then mount your External via ADB and you should to push the proper commands then. Pretty much your internal is hosed, but me and a few others are working on that too.
Can't get it to boot it makes it to Vibrant screen an shut off an on Eugene"s froyo it gives me a couple of errors an I just can't get it to start anymore it there anyone who has encountered this an got it fixed like I really need this fix I am using a blackberry please save me
YAY
I got it fixed but now im on step 13 of that guide where you have to use ADB an i cant get the phone to show up on my PC what drivers do i need i already have Vibrant drivers but still nothing an the usb works its a samsung USB so can anyone help me with ADB
I am having a similar problem. Was running ICS 4.0.3 w/Euphoria without issue until this morning. Got a couple of errors after a normal recharge. Pulled battery and rebooted, but is stuck in boot loop. Cannot access either recovery or fastboot screen. Vibrant logo flashes and release buttons, but never enters mode. Then cycles to Android screen and would likely stay there until battery died. This is primary phone and need to put back into service quickly. Any assistance will be greatly appreciated. Thanks.
JIM in FLA
Go back to stock 2.1
Sent from my SGH-T959 using XDA
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
jpeclf said:
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your help but seeing as your phone is an Android phone, I don't think the same process applies. But thanks for the effort, I have this baby up and running now.. I just had to reflash the ROM.. Thanks again :good:
FocusHelp said:
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
Click to expand...
Click to collapse
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Be VERY sure you flash the correct ROM for your phone. If you have a version 1.3, then ONLY flash 1.3 ROMs to it. If you have a version 1.4, then ONLY flash 1.4 ROMs to it. You can find the version number under the battery on the sticker. If you flash the wrong version of ROM to it, you will end up with a brick.
When having problems like this, I would recommend flashing the Stock ROM to it first to set everything back to normal. Then, if that works fine, go to custom ROMs if desired. Stock flashing will replace everything back to new settings, including spl, radio, etc... Some of the custom ROMs are truly worth flashing, FASTER, stable, nice features.
Unokashi01 said:
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Click to expand...
Click to collapse
I know I had 3.05a and reflashed 3.10a Clean Rom.. It works great now... I remember I use to have problems with the 3g but not after reflashing it works great
Hey wassup. So yesterday I rooted my phone and tried to install CM13 on it. Took a few tries since the rom I got was corrupted but I got it to work. Then I noticed it was guzzling the battery like lemonade (this EXACT same thing happened on my previous S4 too) so I gave up on it and decided to revert back to the stock rom. Everything went well... NOT. I downloaded the stock firmware (3gigs... zzz) and I flashed it with Odin and the phone restarted. The little android robot from the default unrooted recovery popped up and it had below it this: "Installing system update..." and then out of the blue it said "Erasing" and it's gear started rotating backwards. THEN, when it finished the normal Samsung Galaxy Note 4 logo popped up, went away and then CAME BACK AGAIN FOR LIKE 500 TIMES AND COUNTING. AOSP roms work just fine, it's just that touchwiz ones won't work whatsoever (even tried sixperience, no luck)... What should I do? I already lost my S4 due to this...
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Try to remove battery first.from tsoch recovery wipe data cache and see if it works
dork997 said:
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Click to expand...
Click to collapse
Been there, done that. Nope, still refuses to work :/
bumpity bump bump
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
travis82 said:
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
Click to expand...
Click to collapse
this never happened to me with my old s2 or s4
why is it happening now ?
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Peontikos_Desmos said:
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Click to expand...
Click to collapse
Hi
Same problem
Any ideas !!!
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
senon said:
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
Click to expand...
Click to collapse
ffs i'm not paying another phone's worth in a ****ing motherboard. I tried:
-Flashing the stock bootloader, fails at sboot.img:NAND Write start fail
-Flashing the PIT file, just... wont flash. Successes 0/Fails 0
-Flashing the stock AP file, bootloop
-Flashing the CP and the CSC stock files, serial(com) port cannot be opened.
****ing garbage. For some reason my phone's the only exception to the rule that phones able to boot into download mode are salvageable. It's going in for a repair and if it's more than $50 I'm not rooting again even at gunpoint.
Quick update:
I found a toolkit that has a flash stock boot image option. Had to recover to my cm13 backup to enable usb debugging. Will post results
Nothing of course...
try this step by step,
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Oliva.raiders said:
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Click to expand...
Click to collapse
Well, crap I already sent it in for repairing but if the fuqing robbers decide to change the motherboard instead of doing anything to it and charge me 500$ to do so I'm getting it back and I'm trying this one. Already did but it wouldn't hurt retrying... BTW FOR THE LOVE OF GOD DOES SOMEONE HAVE A TWRP BACKUP FILE ON STOCK TOUCHWIZ? JESUS
radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
Is there absolutely NO workaround?
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
JuanWilliman said:
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
Click to expand...
Click to collapse
Oh that's nothing man. The fuqing scammers told me the whole freaking board had to be replaced...
There's one thing I've noticed though that's PROBABLY gotta be the culprit. Whenever I install a touchwiz rom, the phone boots up fine for once, shows the robot with the "Installing system update" and then it goes off with "Erasing" followed by the bootloop. Could anyone please elaborate on this? I have a feeling this is what's causing this ****fest