Related
Guys,
I'm in need of help fast.....
Just tried to do the Froyo Upgrade and have hit an almighty problem.
Kies downloaded and went to the next stage 'Upgrade'.
It got about 5% into doing this when the bar stopped moving and the phone switched off.
It's been like this now for over 30mins..... The phone won't power up (it's still connected to the PC).
HELPPPP.
Well you get my sympathy vote! But other then that I think you know yourself what to do. You've been around... Good luck!
Yes..... Bloody Phone, Bloody Kies, Bloody Samsung.
I unplugged the phone in the end and Kies offered to do a Firmware Recovery so I thought why not give it a try.
I went into Download mode, reconnected and Kies started the recovery procedure only for again the bar to stop moving again and it's stopped doing the recovery.
The screen on the phone remained a constant bright Yellow.
I unplugged it again and tried once more... It again stopped about a quarter way into the recovery only this time the screen has turned a constant Green.
Damn.................
The sad thing is that this reminds me so much of my sinclair zx81. 25 years later and we still have to deal with the same problems. Never sure the data gets from point A to point B.
Right.... Now I need to find the address for UK returns.
Don't have my warranty card info with me either so looks like I'll have to Google the returns.... but I'm busy as hell and have an Op to carry out soon.
If anyone comes up with it (or the link) I'll be grateful.
Bugger....
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Geryatrix said:
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Click to expand...
Click to collapse
No problem on the 'techer', any advise or assistance is better than nothing.
Yes, I used the cable supplied by Samsung... Nothing seems to sort this out.
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
sargasso said:
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
Click to expand...
Click to collapse
Well I've tried the Firmware Recovery at least a dozen time, each time it starts and stops at different parts.
I nearly got to three-quarters through when the bloody thing hung again.
No problem with the 3 Botton access and getting the Yellow Android Man on screen.. No problems connecting to Kies but as soon as you try the recovery it stops at some point during the process simply saying "An unexpected error has caused firmware upgrade to fail. Do you want to perform firmware recovery now?"....... and that came up whilst doing the firmware recovery.
Doesn't work to flash with odin either?
xExisioNx said:
Doesn't work to flash with odin either?
Click to expand...
Click to collapse
I don't want to use Odin if possible.
With that many different phones and ROMS available I don't want to end up screwing the phone totally.
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Don't be scared of Odin. It has recovered my phone a million times
Really, the time and effort of getting a replacement when you can fix it in 2mins with odin in your own home... seems crazy.
You can flash a UK firmware if theres one available, or otherwise flash any firmware and update to UK firmware using kies reg hack, as far as i understand.
sargasso said:
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Click to expand...
Click to collapse
Thanks... Need to find out now which is the right PIT to download.
I was on JF3.
God... if only I had more time on my hands.
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
When you flashed did you remove your sim card? I had that same problem with ki es. Removed the sim card and redid the flash and it continued on it's way.
How this helps.
Sent from my GT-I9000M
Well, if you have an account at samfirmware you can use this link http://www.samfirmware.com/WEBPROTECT-i9000.htm.
Make sure before you do anything to check your phone model is the one I linked to. Making a backup of your efs directory is not possible anymore but normally that should be done also. As a precaution I always remove my external sd card and sim card before flashing and - as you know - have the battery loaded to the max.
It might be an idea to skip jf3 and go to JM8 with a 512 pit and repartition on. This because it seems to be the recommended way of doing things at samfirmware as preparation for the flashing of current froyo releases.
I have never had problems with their way of doing things but opinions differ.
[EDIT]
I downloaded their JF3 package to see if there was a pit file included as there is some discussion what PIT file to use 512 vs 513. The package contains no information on that. It does however contain the word LOW in one of the filenames ...
Beards said:
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
Click to expand...
Click to collapse
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Fornowagain said:
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Click to expand...
Click to collapse
Surgery postponed until tonight so I have some free time.....
Okay, I got Odin 1.3 & JPO Firmware.
I loaded the JPO into Odin (in the PDA section).
Next I put the SGS into Download Mode and connected via USB and sure enough the ID:COM came up yellow with COM7 so I hit Start.
The green line went so far across under KERNAL but just as it was about to finish that box the SGS screen changed to a solid Blue screen and nothing further is happening in Odin.
Any advice??
Odd never seen that before, maybe your root problem. Should have rebooted automatically once the progress bar reached the end assuming you had the reboot option selected. Try a manual reboot, hold the power button down until it restarts. My next step would be the repartition and try again, load the PIT file (as PIT). Same flash procedure as before just using the 512 PIT, reset it all and try again.
I have been on this forum for 3 days going through many fixes for this problem.
NONE of them have worked.
I have been able to get into download mode, and the phone is recognized via com3 in odin.
I have re-flashed it with Eugenes no-brick version, then re-flashed it with tons of different stock and non-stock roms. It gets to various stages but does NOT work.
Any ideas or fixes will be a lifesaver!! Thanks in advance!
If you can still get into download mode and Odin recognizes your phone, flash it with these two files, they work:
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
DO NOT check the re-partition checkbox in odin.
why not repartition as long as you put pit file in pit field repartitoin like crazy if you like .
and repartition would be required if you coming from vodoo based kernel or if you ran anyother partiton than rfs .
Thanks for the quick response.
I tried these files again (I have tried them before) both with and without checking the re-partition box.
It boots then says Vibrant Samsung, then crashes. When I turn it back on it again crashes and turns itself off after the initial splash screen.
Any other ideas? It says that I passed in Odin
charge your phone ?
bartek25 said:
charge your phone ?
Click to expand...
Click to collapse
Hahaha ya I wish it was something so simple (maybe it is!) but it isn't that!
download this ! http://forum.xda-developers.com/showthread.php?t=734475
put JFD in to PDA
also downlaod PIT from the same lik i gave you and seriously charge your phone , and when you odin with the files i gave you from the link check rapartition . check phone efs clear and f.reset time and auto reboot .
come back report resoults if not we help more .
also by any chance u didnt play with ROM MANAGER when your wibrant was working and didnt play with repartiton while there right ?
The same crashing loop has happened with the latest advice. I checked Phone efs clear, re-partition, auto-reboot, and f.reset.time.
I used tVhe T959UJFD PDA, and the 512 Pit.
This phone has been plugged in for days I really doubt the battery is dead.
It just is a constant loop of crashing,h whether at te "off battery" logo or the vibrant splash screen.
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
I am starting to think there may be a hardware issue.
To be completely honest, I got this phone from a friend who had bricked it. If I can get it working then I have a galaxy on the cheap.
On the downside I have no idea what he did to brick it, and he is not tech-savvy enough to know himself.
I come from an original G1 and Cliq, so this is a tad different then I am used to.
from my point of view your phone is fried (it happends) or you are not doing something right or someone is more tech savy to help more , did you pull battery out for at least a min and let it sit and try again to boot ...
Ohhh i know whats wrong with the phone ........if your friends gave it to you broken i think good advice is ,download a program that can repartition hard drive from windows like any program that can do format of anydrive from windows i recomend PARAGON PARTITION MANAGER , find your phone while in the program and u need some skills lol for it but find the phone and click delete partiton after you do that click apply 2. after deletion and applaying the actions click on the phones formated drive in the program i recomended you and click submenu wher you will see create partiton click FAT32 apply 3. click again on the disk you created and click format . 4 done , its easy just get to hang of it
Good advice, I will work on this and get back to you later tonight.
Thanks again!
sounds like your friend bricked his phone from ROM MANAGER by creating EXT4 partion in phones memmory not on SD thats why phone cant find a drive to install the system , happend to me by my own mistake but i got it to work so if that help you You have free vibrant so try hard if not u have paper weight toy
if u dont want the phone i buy back from you for 20 bucks so i cant smash it against the wall , always want it to do that
Intim said:
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
Click to expand...
Click to collapse
Just so you know when you get to this point you need to make sure you had ADB set up on your pc and then plug in the phone and do adb reboot and that will boot the phone up, then you can shut it down and go into DL and flash back to stock. if you read the directions from Eugene's no brick it stated you need to do a adb reboot to get it to work, so you can fix it if your getting to the recovery of that flash.
Ok so for the paragon partition manager it does not recognize my phone's harddrive. Unsure how to fix that as it is just a wizard type program.
I have been able to recognize the phone in ADB, although I cannot push any files to the phone (access denied) and have not been able to get SU access either as I am assuming he did not have root when he bricked it.
Any ideas?
you dont need to push any files to the phone with the adb, after you flash the eugene rom and it boots into recovery you just need to load up your adb and type this
adb reboot
thats it, and it should reboot your phone and if it does boot up fine then you can flash back to stock with odin from there.
Did you perchance happen to have installed the Team Whiskey DOW kernel on this phone?
Your symptoms match the symptoms of quite a few others.
http://forum.xda-developers.com/showthread.php?p=11704550&posted=1#post11704550
http://forum.xda-developers.com/showthread.php?p=11680374#post11680374
So, I deleted system when I changed ROM for the first time (always had HTCs so that's how it worked). That went well(!) Then my phone repeatedly refused to boot into recovery, just restarted, but I got lucky one time and it did, so I flashed the ROM I had on there as soon as I could. I knew that was buggy but it worked. Completely forgot about the backup I previously made. So after a few days of trying to get into recovery it finally happened today, then I tried to go back to that restore, but it failed. Then I forgot to backup what I had now, so I'm back to nothing, because CM11 won't flash. Then when I tried to restore the update for a second time, the screen got brighter and brighter and became corrupt, so I just unplugged it. There seems to be no damage, and I'm in TWRP again, but upon mounting to my computer it isn't recognised. So, is there a 4.3 100% STOCK ROM for the i9505 that I could flash in Odin (or any ROM that I could flash in Odin) that could get this phone working again? Unless there's a way to downgrade to 4.2, then I'll take that too.
Edit: I'm in the UK (BTU) and found this tar file: I9505XXUEMK8_I9505BTUEMK5_I9505XXUEMK8_HOME.tar. I believe this should work, as I have the i9505 and I'm in the BTU region, so should I just flash that in Odin?
kylepont said:
So, I deleted system when I changed ROM for the first time (always had HTCs so that's how it worked). That went well(!) Then my phone repeatedly refused to boot into recovery, just restarted, but I got lucky one time and it did, so I flashed the ROM I had on there as soon as I could. I knew that was buggy but it worked. Completely forgot about the backup I previously made. So after a few days of trying to get into recovery it finally happened today, then I tried to go back to that restore, but it failed. Then I forgot to backup what I had now, so I'm back to nothing, because CM11 won't flash. Then when I tried to restore the update for a second time, the screen got brighter and brighter and became corrupt, so I just unplugged it. There seems to be no damage, and I'm in TWRP again, but upon mounting to my computer it isn't recognised. So, is there a 4.3 100% STOCK ROM for the i9505 that I could flash in Odin (or any ROM that I could flash in Odin) that could get this phone working again? Unless there's a way to downgrade to 4.2, then I'll take that too.
Edit: I'm in the UK (BTU) and found this tar file: I9505XXUEMK8_I9505BTUEMK5_I9505XXUEMK8_HOME.tar. I believe this should work, as I have the i9505 and I'm in the BTU region, so should I just flash that in Odin?
Click to expand...
Click to collapse
I'd rather suggest putting a new, clean rom on the phone by copying the rom onto your sdcard (via cardreader if it doesnt mount via usb) and installing it through TWRP on the phone itself instead of through odin.
Or is there some point I am missing why you specifically want to go back to a stock rom? Since a restore is out of the question why not go forward?
Can't answer you on that specific file, sorry.
kajing said:
I'd rather suggest putting a new, clean rom on the phone by copying the rom onto your sdcard (via cardreader if it doesnt mount via usb) and installing it through TWRP on the phone itself instead of through odin.
Or is there some point I am missing why you specifically want to go back to a stock rom? Since a restore is out of the question why not go forward?
Can't answer you on that specific file, sorry.
Click to expand...
Click to collapse
The main reason why I wanted to go back to stock was because virtually nothing worked. Scrolling on recovery was broken, getting into recovery itself was a rarity, the charging screen while the phone was switched off but plugged in didn't work, to name but a few problems. I'm just going to stock to fix all of that, by going back to stock, then I'm going to move forward. Go one step backwards to end up two steps forwards.
Anyway, I just did a #YOLO (help pls), flashed it and the phone appears to work perfectly again, to my relief. *breathes heavily*
Solved I see. U flashed the correct one for ur region
Hi
the story is I had a Hong Kong version galaxy s5 G900F model and i wanted to install googles apps and stuffs on it so i tried to root it and as i was NOOB it got a odin failled message. after that phone vibrated and turned on but there were no picture, while it was trying to boot with the blue light on the top it has the samsung booting sound played only half the way and would stay in booting for ever. still no picture ! no physical damage to the phone its only 6days only.
it boots to download mode. even goes to CWM but still no picture. I have z3x box and I have flashed the phone with 4 files still no luck! no picture
Restored the latest firmware with re partitioning enabled, still no luck! the only thing i have not tried is jTag.
I have even tried two different brandnew screens on the phone still no luck! I have tried custom kernel no luck!
I have a repairer friend he said the display driver may have been erased? is there anything like that? is there any way to fix?
I hope someone here can help me !
shamid202 said:
Hi
the story is I had a Hong Kong version galaxy s5 G900F model and i wanted to install googles apps and stuffs on it so i tried to root it and as i was NOOB it got a odin failled message. after that phone vibrated and turned on but there were no picture, while it was trying to boot with the blue light on the top it has the samsung booting sound played only half the way and would stay in booting for ever. still no picture ! no physical damage to the phone its only 6days only.
it boots to download mode. even goes to CWM but still no picture. I have z3x box and I have flashed the phone with 4 files still no luck! no picture
Restored the latest firmware with re partitioning enabled, still no luck! the only thing i have not tried is jTag.
I have even tried two different brandnew screens on the phone still no luck! I have tried custom kernel no luck!
I have a repairer friend he said the display driver may have been erased? is there anything like that? is there any way to fix?
I hope someone here can help me !
Click to expand...
Click to collapse
Shouldn't have ticked the re-partition box without a PIT file
You'll need the stock firmware from sammobile dot com and ODIN, and the PIT file from here
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file and ROM to ODIN together, boot to download mode on the phone, hit start
It will flash the PIT file, then it will flash the ROM, all being well, it should boot back up normally
*Detection* said:
Shouldn't have ticked the re-partition box without a PIT file
You'll need the stock firmware from sammobile dot com and ODIN, and the PIT file from here
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file and ROM to ODIN together, boot to download mode on the phone, hit start
It will flash the PIT file, then it will flash the ROM, all being well, it should boot back up normally
Click to expand...
Click to collapse
as i already have explained i already have done it with PIT file ! it seems turning on but no picture !
Nowhere in your post did you mention a PIT file
common man im looking to solve the problem. its obvious if i click on re partition i have to use .pit file.
Not at all, you managed to brick it, that tells me you don't really know what you're doing, so fairly likely you could have ticked it without knowing you had to use a PIT file
Anyway, if you've successfully flashed a stock ROM using PIT, and it still has no display, it sounds like a hardware fault, there's not much else you can do software wise other than what you've already done
EFS Partition in tact? I know that contains some fairly important data, including IMEI and radios, not sure if it has anything to do with display, but if you lost that, you can't fix it by reflashing ROMs
How do you know it's in download mode if there is no display?
well it can be detected via odin and samsung tool when i press down the volume down power and home and after that volume up.
as i said its just 6days old and had no issues before i start this process.
anyyone ?!
z3x box ?
You tried flashing it connected directly to a native PC ?
Phone > USB > PC
did everything no luck!
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop
I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..
Rajada said:
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop
Click to expand...
Click to collapse
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
iRoNX said:
I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..
Click to expand...
Click to collapse
How do you know the partition is corrupt? I think i already did a factory reset by repartitioning with the pit file. Corrupt partitions i tried to fix by nand erase in combination with repartitioning... this did not help.
I have the same problem, only problem I got some text with red+blue+yellow color, what I did was flash a stock ROM ( SAME ROM I HAD BEFORE ROOT FAIL) and it worked (like)
rionline said:
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
Click to expand...
Click to collapse
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:
Rajada said:
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:
Click to expand...
Click to collapse
thank you very much. i do not understand your first sentence......btw. i can get into download mode...(just if you meant "can not")
Update: I have virtually flashed every rom > 5.0. No success, no difference. Everytime the odin flash procedure is successful (in all variants, with pit, with nand erase, etc...), but the phone loops everything (normal start, recovery) besides the bootloader.
only new thing i noticed: allthough binary status is official, the device status is and stays custom not matter what i flash.
anyone? anything?
Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?
sunniebeta said:
Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?
Click to expand...
Click to collapse
yes i tried stock recovery already. not sure what caused this. i do remember that i had some problems with 4.8 debloated and then i wanted to flash the hole corresponding stock package as clean base. somewhere in the middle this happenend. i am not quite sure, but maybe, maybe flashed cf-autoroot to this march update. but i am not sure if this was before, after or initially.
however,...what really bothers me, is that there is absolutely no indiciation for an error during the flash process. odin and kies, everything completes just fine, just booting does not work. that's why i fear, that this is just an ugly coincident and the problem is caused by some failing hardware.
maybe and immensly undclocked kernel (odin flashable) could start my phone. because something is still working, when the bootloader and the nand writing is working just fine.
does anybody know how to get a really granpa speedy kernel, or how to make it?
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Used to happen to me all the time. What I used to do was, after flashing the rom, connected it again to odin, flashed the cwm recovery 5-6 times and then used to give it a try. Also ,after trying this, flash the bootloader-modem file and pretty sure your phone will boot(This is optional)
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Greetings from Hamburg ☺
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:
android freek said:
Greetings from Hamburg
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks guys. I tried yesterday some stuff, nothing was working and i finally got it dead as a stone! Nothing was working anymore. However, i took it to the samsung service center. They were irritated, that they can't get it on at all! ... However, i am curious, how they handle it and how much they want for a repair attempt/or replacement.
Just for info. I did all the things you proposed. Nothing worked. I think this was just a coincidental hardware failing. If you flash all the time, there is a chance that you do it, while something is dying!?
i keep you updated! Thanks for now...
Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.
ithehappy said:
Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.
Click to expand...
Click to collapse
So i am back with a fresh note 4 mainboard. they changed it no questions asked, no fee, no problems. i like!