Related
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Rovah said:
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Click to expand...
Click to collapse
Same problem. anyone?
Vincho said:
Same problem. anyone?
Click to expand...
Click to collapse
Did you read the answer ???
jje
Look online (samfirmware), ask friends or on forums for anyone who has the SGS2 w/ the same carrier in the same country and try to find the firmware version (I9100***** - the stars are letter codes). Then just download that firmware and use Odin to install it.
If you can't find it,you presumably could just flash any stock firmware and it might work (or it might make things worse, try at your own risk)
Rovah said:
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Click to expand...
Click to collapse
The progress bar not moving is a known issue with the CM7 Recovery. All you need to do is wait for it to say that it's finished. There is nothing wrong with your phone and no need to return it. You just cancelled the CM7 install part way through which meant not all required files were installed on the phone, causing it to not boot.
As for it taking longer to boot into android after the odin reflash. That's because it has to build up it's dalvik-cache again. This is completely normal any time you install a new rom. It only happens on first boot of a rom.
So again, no need to return your device and feel free to try CM7 again. Just remember to let it finish even if the progress bar isn't moving.
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Rovah said:
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes, as long as the firmware you're flashing is the same as the stock version that came on the phone. And even if not, you'll get the kies updates for whatever region firmware you did flash onto the phone.
I see. Thanks a lot!
Is there any danger to flashing firmware from a different region than the one youre from?
Sent from my GT-I9100 using XDA App
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
boneyarsebogman said:
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
Click to expand...
Click to collapse
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
es0tericcha0s said:
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
Click to expand...
Click to collapse
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
es0tericcha0s said:
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
Click to expand...
Click to collapse
I've wiped the Caches and Dalvik Cache and can't seem to find "Fix Permissions". I did some searching and it seems this feature was removed from CWM? I'm running v6.0.3.7 of CMW.
When I try to format the system, it says
E:format_volume failed to unmount "/system"
Error formatting /system!
Weird, they did take it out. Koush said it was a placebo. Which normally I would take as law, if it weren't for many times I have ran fix permissions and it caused apps that were force closing to not force close anymore. But whatever, if you wanna try, flash this: http://db.tt/9aWdF8Rp. It'll either help fix something, or do nothing. Won't make it any worse. If it can't mount to format though, it's either or a bug with CWM for your device, or after factory reset, reboot recovery and try again. But you really don't want to wipe /system unless you have a nandroid or another rom on your storage that is accessible.
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
boneyarsebogman said:
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
Click to expand...
Click to collapse
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
es0tericcha0s said:
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
Click to expand...
Click to collapse
Mine is the P2-6011.
Swear if we get this working, never changing anything ever.
Yes, the bootloader is unlocked.
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
es0tericcha0s said:
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
Click to expand...
Click to collapse
If I ever meet you I definitely owe you a drink. Did exactly as you said and everything (from what I can tell) is working.
It's one of the things I love about Android phones - unless you do some serious damage to it physically, for the most part it is fixable.
So, thanks button isn't enough - you saved me giving up and buying a new phone
*Hi Five* Glad all is well!
But yea, I do this for a living. Seriously. Helping people on here is how I stay sharp. lol
getting a gateway 504 error from link to firmware, would love to get this update working as i keep getting a notification on phone saying update available but it wont work
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
Can you post the link of the CM 10.2 rom For huawei P2.
I search for a long long time. but still dosnt found a rom.
Thx
Sorry for digging this up but does someone have the stock ROM of the P2? Im stuck like the fella who started this thread and havent found the stock ROM anywhere.
Thanks for the attention.
Hey everyone,
I have an unrooted Samsung Galaxy S3 GT-i9300 on T-Mobile (UK). I recently updated firmware 4.3 and noticed the battery drained really quickly. After a lot of researching, I found that a factory reset should fix the issue, which it did!
I have since discovered that when in recovery mode, everything seems normal (as in the menu is displayed, including the option "Wipe Cache Partition") the words "No Command" is displayed under the Android robot, with a red exclamation mark. If I choose an option, whether it's Wipe Cache Partition" or "Reboot Now" it seems to do the actions(it shows "Erasing" once "Wipe Cache Partition" has been selected and also reboots the phone) but the word "Error" is displayed under the robot when the action has been done or just before the phone reboots, after selecting "Reboot Now"
Is this normal? Why all of a sudden does it say "No Command" and "Error"?
I haven't tried to root my phone or install any custom roms or try to modify the phone in any way since I got it.
Can anyone out there please let me know why these words have started to appear in recovery mode?
I'd really appreciate it!!
P.S. I searched the forums before posting and although some were similar, they didn't cover my exact problem.
Try downloading the same official firmware and flashing with odin, there is a guide in general forum. Factory reset then try again.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try downloading the same official firmware and flashing with odin, there is a guide in general forum. Factory reset then try again.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply. I found the guide to flashing the phone with Odin and I'm a little worried in case I mess up and brick the phone, I read that if you make a mistake, that can happen.
Just to say, I checked the recovery mode again and it seems to do everything normally, such as wiping the cache(it says so in the log) but it just says "No Command" after each action. The word "Error" only appears the very first time you see the robot, and when you select "Reboot Now" just before it reboots "error" shows up under the robot and then the phone restarts.
So, do you know if this is normal? Or do you think it's something to do with the way the firmware 4.3 works?
I'd just like to know whether it's normal or if there's something wrong behind the scenes in the phones firmware.
Hope you can help and thank you again.
MasterfulNinja said:
Thank you very much for your reply. I found the guide to flashing the phone with Odin and I'm a little worried in case I mess up and brick the phone, I read that if you make a mistake, that can happen.
Just to say, I checked the recovery mode again and it seems to do everything normally, such as wiping the cache(it says so in the log) but it just says "No Command" after each action. The word "Error" only appears the very first time you see the robot, and when you select "Reboot Now" just before it reboots "error" shows up under the robot and then the phone restarts.
So, do you know if this is normal? Or do you think it's something to do with the way the firmware 4.3 works?
I'd just like to know whether it's normal or if there's something wrong behind the scenes in the phones firmware.
Hope you can help and thank you again.
Click to expand...
Click to collapse
Honestly, I'd quite like to see a pic of the errors in recovery. Meanwhile if you don't feel like using Odin (if you stick tight to the tutorials nothing bad will happen) you can try to repair with Kies, you might have installed it anyway. Here is a detailed guide http://forum.xda-developers.com/galaxy-s3/general/guide-how-to-reinstall-stock-firmware-t1978840
If this fails for any reason go ahead and try Odin using this noobproof guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081. That should almost certainly eradicate any errors.
Benko111 said:
Honestly, I'd quite like to see a pic of the errors in recovery. Meanwhile if you don't feel like using Odin (if you stick tight to the tutorials nothing bad will happen) you can try to repair with Kies, you might have installed it anyway. Here is a detailed guide http://forum.xda-developers.com/galaxy-s3/general/guide-how-to-reinstall-stock-firmware-t1978840
If this fails for any reason go ahead and try Odin using this noobproof guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081. That should almost certainly eradicate any errors.
Click to expand...
Click to collapse
Thank you so much for the links! I actually just tried the update via Kies, reinstalling the stock firmware and it took a while and I did everything it said but the messages still show in recovery mode, just like before. So I'm wondering if it's actually supposed to normal to display those words, and maybe that's just that way it is now?
I took some pics of the screen, so you can see what I'm talking about.
Here's the "No Command" message displayed. As you can see, it has wiped the cache partition after I selected it.
https://www.dropbox.com/s/irolo6rp8wh5ibf/Photo 27-04-2014 23 39 34.png
And here's the "Error" message it says just after I've selected "Reboot Now" and before the phone restarts.
https://www.dropbox.com/s/9o0yuopkf3dov76/Photo 27-04-2014 23 40 17.png
Have you seen or heard of this before?
No problem. And no, not in this context. But then again, I haven't had a stock recovery (nor a stock ROM) on my phones for years.
But I do get tons of phones in for repair every week, have not really noticed these 'errors' anywhere.
It seems to execute everything fine.
Would be interesting if you'd flash a TWRP recovery what it says then. You can easily replace it by your stock recovery again.
If everything looks good there then it probably is just the way it is.
Benko111 said:
No problem. And no, not in this context. But then again, I haven't had a stock recovery (nor a stock ROM) on my phones for years.
But I do get tons of phones in for repair every week, have not really noticed these 'errors' anywhere.
It seems to execute everything fine.
Would be interesting if you'd flash a TWRP recovery what it says then. You can easily replace it by your stock recovery again.
If everything looks good there then it probably is just the way it is.
Click to expand...
Click to collapse
That would be interesting, but doing so would require me to root my phone, right?
Oh I see, so it's a quite an unusual thing to happen . . . The fact that it says "Error", yet executes things fine anyway.
I've come to a possible conclusion that it's probably down to that particular version of the stock rom? Maybe people how have updated in the UK, using that version would experience the same? Because, after reinstalling it via Kies, and there being no change regarding those messages in recovery mode, doesn't that point to the firmware being the cause? For example, if I flashed the phone with a custom rom(that didn't have any error messages) surely, those messages wouldn't show up after I'd installed it, right?
Does what I'm saying make sense?
Sorry if I'm going on, I'm not too familiar with the technical side of Anroid systems.
MasterfulNinja said:
That would be interesting, but doing so would require me to root my phone, right?
Oh I see, so it's a quite an unusual thing to happen . . . The fact that it says "Error", yet executes things fine anyway.
I've come to a possible conclusion that it's probably down to that particular version of the stock rom? Maybe people how have updated in the UK, using that version would experience the same? Because, after reinstalling it via Kies, and there being no change regarding those messages in recovery mode, doesn't that point to the firmware being the cause? For example, if I flashed the phone with a custom rom(that didn't have any error messages) surely, those messages wouldn't show up after I'd installed it, right?
Does what I'm saying make sense?
Sorry if I'm going on, I'm not too familiar with the technical side of Anroid systems.
Click to expand...
Click to collapse
No, you don't need root for flashing TWRP via Odin. Use this great and easy guide (if the guide helped you hit the users thanks button):
http://forum.xda-developers.com/galaxy-s3/help/twrp-flashing-tar-t2680354
I'm not sure if this is really the UK-ROM or just a common thing under certain circumstances and I've just never noticed it, but I really doubt it.
If everything is fine with TWRP and also installing ROMs causes no problems I would just accept this as one of the never solved mysteries - which I rarely do normally
we have same issue i already flash custom recovery via odin stil no command when i rebooting into recovery. . did you fix it?
Sooo.... I had the OTA to kitkat, lost my root, decided i wanted it back. Downgraded to 4.3 and rooted, safestrap all of that succesfully. Ran it for about 2-3 weeks, figured i'd go and follow the rest of the directions to get back to kitkat, turns out i messed it up good. I still have the nc5 build but the mk2 baseband and 4.3.
Now, whatever the heck i did, i tried a factory reset then tried to flash a stock 4.3 over it just to really clean it up, turns out, it didnt like that. Now kies will not even recognize the device, and when i tried surge's mk2 restore, it fails. I haven't been able to find a 4.4.2 stock to re-odin and try that. I obviously did search and still am searching at this moment but i must be blind or something.
Now i have a phone that says "firmware failed, please connect to kies and run a repair" or whatever. When i try to odin to the mk2, it says "sw rev. check fail : fused 6 binary 5" which i assume has something to do with the build number/bootloader for kitkat thats still on my phone. Am I screwed or is this recoverable? Thanks peoples.
I really need my phone for work. It's used numerous times to make calls because i'm in a service technician position. I can't go without it for even 1 weekday, if i can't get this figured out by sunday at noon, i will have to bite it and get a new phone. Cannot be phoneless on monday. It would literally cause me to lose my job.
Odin this full wipe http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my OtterX running SlimKat 4.4.3 using Tapatalk
joshuabg said:
Odin this full wipe http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my OtterX running SlimKat 4.4.3 using Tapatalk
Click to expand...
Click to collapse
I've tried it about 4 times now, 1 time it got to about 80% done then failed at write for persdata or something of the sort. The other 3 times it stops within 10 seconds. I'm not sure what else to do. It doesn't seem like there is anything else i can do to be honest. I might be effed.
On try #21, still no go. Ugh
BlueForce64 said:
On try #21, still no go. Ugh
Click to expand...
Click to collapse
Are you trying the same file over and over again? If so, maybe you got a bad download. Did you check the MD5 checksum to see if it matches? Maybe you could try downloading it again.
Sent from my NCC-1701
Yeah i am, but it fails at different points. The same 3 different points though. I'll try to re-dl it and try again. Anything is worth a shot at this point. Otherwise someone can get a free broken s4 if they want lol
Finally achieved success. It took about 40 times but it finally went through. The last 10 were tried with a new dl, i just didnt give up, the one time it worked i made sure i ran odin in administrator. I had an odin going without administrator so i loaded up a new one with it on and right when the 1st one failed i started the second one up and it had the blue progress bar go all the way to the right side of the screen and come back around through the left eventually running into itself, as soon as the progress bar began to overlap the screen it was also saying invalid response for bar length or something in the upper left text until that went down screen and started back on the top. In any case, woohoo it's working! Thanks guys, guess i won't need a new phone yet.
I'm having strange problems with an I9300 I'm trying to fix for friend. Now unfortunately I end up doing things like this not because I know anything about these things, but because I'm I'm slightly more computer literate than the rest of my group of friends, so I'll apologise now if these are stupid questions, I have searched but could find nothing.
Now last night my friend comes to mine with his phone stuck in a boot loop. Now beyond the fact it already had a custom ROM on it I can tell you nothing except he claims he installed AVG and it happened. So I reboot into Windows, start up Kies, and see what I can do. Which so far has been:
1) Try to perform an Upgrade and Initialisation. Jump through the hoops, end up with the message "This device's version cannot be updated."
2) Ok, that didn't work. Hit sammobile to find a stock rom and fire up Odin. Ohh success...
3) Oh noes, too soon. The Samsung chime cuts off early and it's stuck with a pulsating logo.
3) Ok well maybe a downgrade first? Get a 4.1 stock rom and try again. Odin sees no problems again, the chime plays fully. But nope, it's just a longer boot loop.
4) After much head scratching and just trying random stuff I end up finding CM9.1 will boot fully, but the EFS data is screwed. This is the only rom I've found so far that will boot.
So from where I started I'm closer and if the radio worked this would be fine. Now the only suggestion I've heard to get the radio working is flashing a stock rom through Kies but I have no idea how to get Kies to play along. Any ideas?
Thanks.
Your downgrade screwed the efs, flash 4.3 and pray it is still readable.
Your mistake was to not factory reset after the first Odin flash.
123c
boomboomer said:
Your downgrade screwed the efs, flash 4.3 and pray it is still readable.
Your mistake was to not factory reset after the first Odin flash.
Click to expand...
Click to collapse
I did actually try that before flashing 4.3 with Odin and after. Was still stuck in a boot loop... :/
Thanks