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
Dear all,
Before I started a new thread, I just wanted to tell you that I've been awake for over 14 hours Starting to fix issues with my phone and tried alot of things before resorting to starting a new thread,So Please excuse me for starting one
Here's the long one :
Got a Galaxy S as A Present, after an Iphone 3GS, phone is great .. was a branded vodafone one I think from Germany running Android 2.2.1 I think back then.
As am Egyptian I wanted to the phone to read arabic fonts,So I decided it to flash with the Official Android 2.3.3 Arabic version.
Flashing went perfect, everything is smooth and all is very cool started to love the phone.
I dont have an external SDcard this is the internal one btw.
after a few months, a Friend challenged me that he's blackberry would boot faster than an android.
I was intrigued ! So I turned off my phone, turned it back on (I think this was the first time I do it since I flashed it) the phone kept rebooting !
and after like rebooting 10-12 times ... it finally booted correctly (5-6 minutes)
I said something must be wrong with the Firmware I flashed, but Ignored it as the phone worked perfectly after this.
a few days ago it died on battery, charged it ... reboot loop !
I found a hundred of thousands of guides on how to fix that boot loop !
I was getting errors :
e:failed to mount /sdcard (file already exists)
e:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet.please use ui menu for format and reboot actions
meida files copy failed.
after going into recovery mode and trying to wipe data, these above errors always showed.
So I found a guide that suggests flashing with a 3-file ROM (Phone/Modem/CSC) and re-partition would fix this.
So I flashed with the official 2.3.3 (unmodified) and the errors disappeared, phone works perfectly ! although everything is erased of course.
So after setting it up again I thought that I should test restarting it again..
so I did .... and there it goes .. went on Looping again !!!
I went into recovery mode ... same errors appeared again ...
Re flashed 3 files again ... works fine ... restart = loop !
although one time it looped a few times and it did boot at the end, the SDcard (internal one) can be formatted without errors, never had any writing issues so I dont think its corrupted or anything.
But now I can't let the phone reboot or die on battery without flashing it again .. as if its a TETHERED jb iphone !
any suggestions ?
Please try doing as follows:
1. Flash a Kernel with lag-fix support like Voodoo which I can recommend in this case.
2. After flashing the Kernel the phone should boot and the converting of the partitions from RFS to EXT4 will begin, let it be until the phone reboots to the user interface.
3. Turn the phone off and enter Download-mode and re-flash the device using the firmware of your choice and a different pit file of that that is used on your phone (use 512.pit if it's on 803.pit or 803 if it's on 512), you need to use pit and you need to check re-partition.
4. Do a factory reset from recovery after completing the first boot, you need to let the phone boot all the way to user interface then do a factory reset after turning it off.
I hope that this will fix the issue that you are having, good luck and let us know how it goes.
[Ramad] said:
Please try doing as follows:
1. Flash a Kernel with lag-fix support like Voodoo which I can recommend in this case.
2. After flashing the Kernel the phone should boot and the converting of the partitions from RFS to EXT4 will begin, let it be until the phone reboots to the user interface.
3. Turn the phone off and enter Download-mode and re-flash the device using the firmware of your choice and a different pit file of that that is used on your phone (use 512.pit if it's on 803.pit or 803 if it's on 512), you need to use pit and you need to check re-partition.
4. Do a factory reset from recovery after completing the first boot, you need to let the phone boot all the way to user interface then do a factory reset after turning it off.
I hope that this will fix the issue that you are having, good luck and let us know how it goes.
Click to expand...
Click to collapse
I will try it right away, Thanks a lot for your time.
Well I don't know what to do now!
before flashing the kernel you suggested, the phone died on battery so I had to charge it, opened it .. boot looop .. so I said am going to do the same thing I used to do the past few days .. flash with the official 2.3.3 (3 files flash) and repartition.
Apparetly that doesn't cut it anymore, I tried DarkysRom as well, I still get the same error now :
e:failed to mount /sdcard (file already exists)
e:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet.please use ui menu for format and reboot actions
meida files copy failed.
Can't get past it, and of course the phone keeps on boot looping if I ignored it
Am I beyond repair ?
ok after a few reboots, the phone booted correctly, is there's anything to do after it booted ? its on the 2.3.3 now, should I try to update from sdcard thing ?
You don't have a problem with the SD-Card, the problem is with the Kernel not able to mount partitions /data and /dbdata it's why you get those loops, that can happen if there is errors on these spaces and there journals which are located on these partitions.
My advice regarding flashing a costume Kernel and converting to EXT4 is to format these partitions and wipe all these errors, then flashing back to a firmware using pit and reparation should give you a clean firmware install with no errors.
You can try to turn off the phone and power it up again and see if it boots as it should, if not then some of the partitions still does not mount correctly.
You don't have to worry about the device, flashing and re-flashing it will not break it, it's a very solid phone, just be careful and you will be fine.
Always flash when the device has enough battery power (50%-100%)
Ok I've got the voodoo fix but its for 2.2 not 2.3 .. (Vooodo 5.5 ) there's a beta (Voodoo 6.0) for 2.3
I tried flashing 5.5 this morning to the current rom, it still kept on rebooting but it took along time to do so .. (long time between reboots).
So I thought of getting a rom with voodoo built in .. so I got the DarkySrom Resurrection 10.2 and after flashing .. it still went into constant loops..
I have a few things that I didn't try yet, I will post with updates, thanks again for ur time.
Hi,
I got the N7100 on launch day, and rooted using CWM, leaving my phone with a 'custom' recovery, which is noted on the download boot mode.
Now that triangleaway supports the N7100 I thought I would try and get it less dodgy looking which still rooted.
When I ran triangle away, it warned that a custom bootloader / recovery might leave the counter on 1 even after away'ing the triangle...
So I thought I would use mobile Odin Pro to flash stock rom, injecting SU and mobile odin (as i did many times on my note 1).
This failed (using rom N7100XXALJ1_N7100OXXALJ1_BTU) - it verified the MD5 ok, and rebooted into a screen ive never seen before, containing a large blue Android figure with a lightening bolt on his chest. I personally thought he looked a little unhappy as well...
Anyway, first time this happened, i used desktop odin to do a full flash, which fixed it (but increased my custom counter more since I rerooted with CWM+root).
Second time it happened, i fixed it by just re-flashing CWM.
Anyone else had success with Mobile Odin on the N7100 ??? do you think it was the CWM install that it didnt like ?
Im unsure how to flash just the recovery, and am a bit confused between the relationship between the boot image and the recovery one... i wouldnt have expected the recovery image to affect normal boot, but it does.
George
UPDATE - The blue android is actually the mobile odin pro logo... gonna try again and be a little more patient...
...you....fool
Left it 10 mins, and still stuck on blue android screen... gonna try flashing from sd card rather than internal card in case its that...
luckly reflashing cwm6-root-note2.tar from odin fixes it...
Also tried flashing from external sd, and that also failed.
Does anyone know how Chainfire likes issues to be reported?
thanks
George
You can get answer your some question here
http://forum.xda-developers.com/showthread.php?t=1930418
Is that blue android screen not doing anything at all?
I was the one who tested this app prior to its release (on behalf of chainfire who didn't have the phone at that time), I flashed from internal and external without issue.
What is it your flashing exactly? Your not listing it as a OTA/Update.zip are you?
Try to delete the Mobile Odin file off the root of your sd card and open the app again, it will then re-download the files it needs, try it then.
A few other users have reported the exact same problem, and I am pretty sure it will be related to the problem of Triangle Away not always booting up.
Something fishy is still going on with recoveries, and we're not sure what. I can't replicate the problem on my device - at all - so I can't fix it either.
Maybe it has something to do with bootloader version? It seems some people/firmwares have different bootloaders than others and can cause various problems.
What I find strangest is that the Mobile ODIN logo does show up ... that's just weird. Can you use the attached version of Mobile ODIN (its an older version that does not support the Note2) to create a dump file for your device, so I can compare it with the dump files from working devices? It may offer a clue.
EDIT: Download removed, dump made and received.
Dumping...
Hi Chainfire,
Thank you for the response im impressed by your commitment to making our devices better ...
Im doing a dump now [fnarr fnarr] and will make it available to you as soon as its done.
I presume it will be quite large if it takes 30 mins to upload - shall I pm you or email you the dropbox link where i plan to put it?
LennyUK - im flashing what is supposed to be (and in fact is) the latest official rom - i believe its the original shipped rom + an OTA that the UK got. Not sure if it comes from Samsung or its been hacked together from the OTA + original rom. It was downlaoded from sammobile (as i always did with my note 1). Its a tar file (.md5) containing a bunch o f.img files and modem.bin. Im not convinced the N7100 mobile odin flash kernel was corrupted - i would expect CF does a checksum of some sort... ill await his response to my dump.
ps. Why doesnt XDADevelopers email notification work
cheers
George
Chainfire said:
A few other users have reported the exact same problem, and I am pretty sure it will be related to the problem of Triangle Away not always booting up.
Something fishy is still going on with recoveries, and we're not sure what. I can't replicate the problem on my device - at all - so I can't fix it either.
Maybe it has something to do with bootloader version? It seems some people/firmwares have different bootloaders than others and can cause various problems.
What I find strangest is that the Mobile ODIN logo does show up ... that's just weird. Can you use the attached version of Mobile ODIN (its an older version that does not support the Note2) to create a dump file for your device, so I can compare it with the dump files from working devices? It may offer a clue.
Click to expand...
Click to collapse
Dump
Hi,
Here is the dump ...
thanks
George
EDIT: Dump received and removed, thanks.
had the same problem when trying to flash the exchange hack.
used pc odin to upload CWM and this made my phone boot again
Hi, for the record, i tried triangleaway, and ... it booted into it OK, and ran the procedure to reset the counter...
and its worked... I now get
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
im guessing the custom is due to CWM recovery...
cheers
g
Weirdness. It appears your cache partition is borked (its 10 MB instead of 1.5 GB ?!). This could explain the following problems people have reported:
- Mobile ODIN showing the logo but doing nothing else
- Triangle Away breaking recovery
Try flashing the attached cache file in (desktop!) ODIN, then try Mobile ODIN, Triangle Away, etc again. Problem should be solved then - please do let us know, several people are having this problem.
It's a ZIP file, extract once so you end up with a TAR file, put that in ODIN. If you end up with an IMG file, you extracted twice!
EDIT: Note: after flashing this image you will probably automatically boot into recovery - this is expected, just press power to reboot normally.
Hi,
Thank you... flashed the cache.zip, and it rebooted to the Galaxy Note II screen, then rebooted, over and over again...
so I reflashed the rooter, (cwm6-root-note2.tar) which DOES include flashing the cache, so maybe thats got a broken cache in it ? (the reflash fixed it)
odd...
Ive attached to rooting tar ive been using with the strange (but working...) cache file...
cheers
g
Chainfire said:
Weirdness. It appears your cache partition is borked (its 10 MB instead of 1.5 GB ?!). This could explain the following problems people have reported:
- Mobile ODIN showing the logo but doing nothing else
- Triangle Away breaking recovery
Try flashing the attached cache file in (desktop!) ODIN, then try Mobile ODIN, Triangle Away, etc again. Problem should be solved then - please do let us know, several people are having this problem.
It's a ZIP file, extract once so you end up with a TAR file, put that in ODIN. If you end up with an IMG file, you extracted twice!
EDIT: Note: after flashing this image you will probably automatically boot into recovery - this is expected, just press power to reboot normally.
Click to expand...
Click to collapse
Failed to upload..
at
https://dl.dropbox.com/u/279536/cwm6-root-note2.tar
thanks
g
ripnetuk said:
Hi,
Thank you... flashed the cache.zip, and it rebooted to the Galaxy Note II screen, then rebooted, over and over again...
so I reflashed the rooter, (cwm6-root-note2.tar) which DOES include flashing the cache, so maybe thats got a broken cache in it ? (the reflash fixed it)
odd...
Ive attached to rooting tar ive been using with the strange (but working...) cache file...
cheers
g
Click to expand...
Click to collapse
Yes, I confirm it is definitely the cwm6-root-note2 package that messes up your device. I've checked it out - its the cause for all the problems with Mobile ODIN and Triangle Away. It breaks the cache partition on your phone ( dr.ketan ... )
The reason flashing the fixed cache.tar didn't immediately fix your problems was because you still had a messed up recovery, so you also needed to flash a recovery, which you did now again with the cwm6 package. However, your cache is again broken. So now, *again* apply cachefix, and all should be good, and you should be able to use Mobile ODIN and Triangle Away.
Chainfire said:
Yes, I confirm it is definitely the cwm6-root-note2 package that messes up your device. I've checked it out - its the cause for all the problems with Mobile ODIN and Triangle Away. It breaks the cache partition on your phone ( dr.ketan ... )
The reason flashing the fixed cache.tar didn't immediately fix your problems was because you still had a messed up recovery, so you also needed to flash a recovery, which you did now again with the cwm6 package. However, your cache is again broken. So now, *again* apply cachefix, and all should be good, and you should be able to use Mobile ODIN and Triangle Away.
Click to expand...
Click to collapse
Sorry if it was asked before but will you release cf root with cwm recovery for note2? thx
I have no plans to release anything related to CWM ever again.
Chainfire said:
I have no plans to release anything related to CWM ever again.
Click to expand...
Click to collapse
Damn :/ btw what about your root? which wouldnt have issues with ta and mobile odin
EdgaBimbam said:
Damn :/ btw what about your root? which wouldnt have issues with ta and mobile odin
Click to expand...
Click to collapse
There might be a CWM-less CF-Root coming, indeed.
Hi.
That worked perfectly. I can confirm successful flash via mobile odin once I had fixed recovery and flashed that cache fix.
Many many thanks...
George
That wud be very nice.
Thank you..
Sent from my GT-N7100 using xda premium
Hi,
I've owned all the Galaxies and never had any problems installing ROMs.
Ten days ago I bought an unlocked new GT-I9500 in USA. It's not a knockoff, I've checked the IMEI and I know the device (I've had one for a year back in 2013), there is no chance this phone is not legit (even though it's made in China).
I brought the phone to Argentina, where I live.
When I first turned it on I didn't notice anything out of the ordinary, so I assume it worked fine. The thing is I didn't get to test it thoroughly at that moment because I installed a 5.0.1 stock ROM right away (I think the phone came with 4.4.2).
This 5.0.1 ROM worked horribly, all apps were force closing all over the place (even unopened apps), without me doing anything, I would be just watching the screen and the FC dialogs would just pile up. The phone was unusable because you needed to dismiss several FC dialogs before you could get to the screen below, and by then you got a new FC coming up.
Many times when I rebooted, it would say it was optimizing 3 or 4 apps, and then it would work a bit better, or maybe a bit worse, it was a totally random thing. It also rebooted spontaneously, Play Store would close spontaneously, many apps refused to update giving error codes like "unknown error 960" or something like that.
Things I already tried:
-Reinstalled same ROM 5.0.1 I9500UBUHOE2_I9500UUBHOE2_I9500UBUHOE1_HOME.tar
-Installed different ROM 5.0.1 I9500UBUHOE3_I9500ZTOHOF1_I9500UBUHOE1_HOME.tar
-Did all wipes, before and after
-Reinstalled with PIT and re-partition
-Installed Philz and tried "clean to install a new ROM"
-Reinstalled 5.0.1 ROM
-Again tried "clean to install a new ROM"
-Reinstalled 4.4.2 I9500UBUGNJ1_I9500UUBGNJ1_I9500UBUGNJ1_HOME.tar, which is the version I think the phone originally had installed.
-Of course, in the meantime I lost the IMEI and had to restore it from backup.
After downgrading to 4.4.2 the situation got a little better, but I still get several FCs and spontaneous reboots. On one opportunity I booted into recovery, wiped cache, and when I rebooted it got stuck in the boot logo. I removed the battery, turned it on and it did the same thing. I had to boot into recovery and wipe data/factory reset to get it to boot.
I have two theories:
1) There are some residual files or settings from previous ROMs that I can't seem to get erased, and these are interfering with the new ROMs I install.
2) The phone is defective (memory issue, perhaps?)
Theory 2) seems odd because before installing 5.0.1 for the first time, the phone appeared to work correctly. Granted, I just tried it for a minute or so, but anyway.
Theory 1) seems odd because I did all the wipes, the "clean to install a new ROM" thing, and even re-partition. Can any problematic data survive after all that?
I guess the questions for you guys are:
1) Did this happen to anyone else? Could you solve the problem?
2) Is there a way to erase the phone more deeply?
Thank you.
Ricardo
The PIT file should repartition the phone, meaning it should also wipe it.
Are you sure it is a GT-I9500?
People tend to repair phones with compatible parts from other phones. In this case maybe they used parts from other S4 models (9505, 9506 etc).
Boot into download mode and check the phone model.
GDReaper said:
The PIT file should repartition the phone, meaning it should also wipe it.
Are you sure it is a GT-I9500?
People tend to repair phones with compatible parts from other phones. In this case maybe they used parts from other S4 models (9505, 9506 etc).
Boot into download mode and check the phone model.
Click to expand...
Click to collapse
The phone is brand new, and I've checked all known signs of it possibly being fake. I'm pretty sure it's not fake.
See attached image.
Sound like your storage is corrupted.
If you are out of options then you can try to select nand erase all in Odin. Maybe that could fix it. Make sure to add a .pit file, bootloader, modem, rom and check re-partition before doing that.
rabadanpaz said:
The phone is brand new, and I've checked all known signs of it possibly being fake. I'm pretty sure it's not fake.
See attached image.
Click to expand...
Click to collapse
I believe there's no "brand new" S4 in the market right now.
I haven't used philz but twrp .. and if you also install twrp recovery for i9500 ..then you get option for advance wipe .. check everything in advance wipe ( don't forget to take backups .. contacts ..files etc) then swipe to wipe everything .. then go back to main menu and reboot in download mode .. (you may get warning like no OS installed) then install a new ROM via Odin from PC .. you will get a fresh installed ROM
If you still face any FC .. go back to recovery mode .. choose advance then do fix permission .. hope that helps ..
Lennyz1988 said:
Sound like your storage is corrupted.
If you are out of options then you can try to select nand erase all in Odin. Maybe that could fix it. Make sure to add a .pit file, bootloader, modem, rom and check re-partition before doing that.
Click to expand...
Click to collapse
I've been reading about nand erase. It looks like I just need the ROM and the pit file. Maybe the ROM includes everything else you mention?
rabadanpaz said:
I've been reading about nand erase. It looks like I just need the ROM and the pit file. Maybe the ROM includes everything else you mention?
Click to expand...
Click to collapse
The Samsung official Roms have all integrated, SO, booloader, modem, etc. What lacks is the pit file, you have to get it from other place. I have an I9500 and had those issues when installing 5.0.1 official rom, i believe is not a very stable rom and also drains a LOT of battery. If you can install a custom recovery, try the "[GearCM][i9500][5.1.x] Optimized CyanogenMod 12.1 for Samsung Galaxy S4" rom, the post is in this forum , I'm currently using it and works awesome.
Ok guys, so I tried nand erase and the results are the same. Used both a 5.0.1 and a 4.4.2 ROM. Could this be a memory hardware error? Is there anything more radical that is left for me to try?
rabadanpaz said:
Ok guys, so I tried nand erase and the results are the same. Used both a 5.0.1 and a 4.4.2 ROM. Could this be a memory hardware error? Is there anything more radical that is left for me to try?
Click to expand...
Click to collapse
You can try this:
http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/mod-multirom-v28-t2864469
Then you can boot a rom from your sd card. See if that works ok.
Will try that.
In the meantime, quick question: I've noticed that after nand erase the IMEI is retained. This would mean that nand erase does not erase everything really. Isn't it possible that some information is preserved (like the IMEI), and this is what is causing trouble?
Lennyz1988 said:
You can try this:
http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/mod-multirom-v28-t2864469
Then you can boot a rom from your sd card. See if that works ok.
Click to expand...
Click to collapse
This looks like it only works for GT-I9505, mine is 9500. Any ideas?
rabadanpaz said:
This looks like it only works for GT-I9505, mine is 9500. Any ideas?
Click to expand...
Click to collapse
Oh yeah, sorry my bad.
Did you try a custom rom? Try something like CM.
Lennyz1988 said:
You can try this:
http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/mod-multirom-v28-t2864469
Then you can boot a rom from your sd card. See if that works ok.
Click to expand...
Click to collapse
Found this one: http://forum.xda-developers.com/showthread.php?t=2417600
Do you think it's similar to the one you suggested?
rabadanpaz said:
Found this one: http://forum.xda-developers.com/showthread.php?t=2417600
Do you think it's similar to the one you suggested?
Click to expand...
Click to collapse
No, I checked it and it's less advanced. For example you can't boot from sd card.
Try a custom rom and see if that works for you.
Lennyz1988 said:
No, I checked it and it's less advanced. For example you can't boot from sd card.
Try a custom rom and see if that works for you.
Click to expand...
Click to collapse
Ok, tried CM12.1 and it has exactly the same problems.
I think it's time to change the memory chip or the motherboard, right?
rabadanpaz said:
Ok, tried CM12.1 and it has exactly the same problems.
I think it's time to change the memory chip or the motherboard, right?
Click to expand...
Click to collapse
Yes I think it is. If you want to do it yourself:
https://www.youtube.com/watch?v=qdQs9O539_c
The part you need (EMMC) is not that expensive.