Hello.
I have a problem with my S4 i9500. I've successfully rooted it and flashed custom recovery. But I'd also like to install custom rom on it, and there is where problem begins. Every time I flash rom and reboot it stucks at boot logo. I've tried it with Philz and TWRP recoveries and three different kitkat AOSP based roms. But the situation looks the same every time, despite waiting over 15-30 minutes the system doesn't boot properly, it stucks at boot logo. Creating backups and restoring stock rooted rom works flawlessly however with both recoveries.
I've also tired twice to install rom without doing factory reset before and then it goes trough boot logo, however stucks at "android is being actualised" window or something like that.
I hoped to get rid of ugly and slow touchwiz from my phone as fast as possible, but with no succes so far. What am I doing wrong?
Sorry for possible mistakes, english is not my first language.
mintor said:
Hello.
I have a problem with my S4 i9500. I've successfully rooted it and flashed custom recovery. But I'd also like to install custom rom on it, and there is where problem begins. Every time I flash rom and reboot it stucks at boot logo. I've tried it with Philz and TWRP recoveries and three different kitkat AOSP based roms. But the situation looks the same every time, despite waiting over 15-30 minutes the system doesn't boot properly, it stucks at boot logo. Creating backups and restoring stock rooted rom works flawlessly however with both recoveries.
I've also tired twice to install rom without doing factory reset before and then it goes trough boot logo, however stucks at "android is being actualised" window or something like that.
I hoped to get rid of ugly and slow touchwiz from my phone as fast as possible, but with no succes so far. What am I doing wrong?
Sorry for possible mistakes, english is not my first language.
Click to expand...
Click to collapse
It should just work.
- Is your bootloader up to date?
- Running latest modem?
- Try not to flash it from your external sd but from your internal.
- Use something like Airdroid to transer the files from your laptop to your phone. I find it more reliable then cabled.
- Redownload the rom again.
- Use TWRP recovery. The rest is outdated.
- Make sure to properly wipe in the recovery. Maybe even wipe your internal storage (/data).
That's what comes to mind.
Lennyz1988 said:
It should just work.
- Is your bootloader up to date?
- Running latest modem?
- Try not to flash it from your external sd but from your internal.
- Use something like Airdroid to transer the files from your laptop to your phone. I find it more reliable then cabled.
- Redownload the rom again.
- Use TWRP recovery. The rest is outdated.
- Make sure to properly wipe in the recovery. Maybe even wipe your internal storage (/data).
That's what comes to mind.
Click to expand...
Click to collapse
How do I check bootloader version and update it if necesarry?
I tried flashing both from internal and external memory, with te same result (no success).
Also, I didn't transfer roms form PC, I downloaded them directly to my phone. I did it the same way with my older phones and never had an issue like this.
mintor said:
How do I check bootloader version and update it if necesarry?
I tried flashing both from internal and external memory, with te same result (no success).
Also, I didn't transfer roms form PC, I downloaded them directly to my phone. I did it the same way with my older phones and never had an issue like this.
Click to expand...
Click to collapse
As silly as it sounds, try to download them on your pc and then transfer them.
Lennyz1988 said:
As silly as it sounds, try to download them on your pc and then transfer them.
Click to expand...
Click to collapse
I was unable to get airdroid working correctly. I'm not sure if it wasn't because of SD restrictions on Kitkat. Maybe this causes my problem as well? I also realized that many file related operations like renaming a folder, deleting files and even downloading it is unsuccessful unless I use stock samsung app. I've transferred the rom later via USB cable and flashed, but the problem still occurs.
mintor said:
I was unable to get airdroid working correctly. I'm not sure if it wasn't because of SD restrictions on Kitkat. Maybe this causes my problem as well? I also realized that many file related operations like renaming a folder, deleting files and even downloading it is unsuccessful unless I use stock samsung app. I've transferred the rom later via USB cable and flashed, but the problem still occurs.
Click to expand...
Click to collapse
What roms are you trying to flash?
Lennyz1988 said:
What roms are you trying to flash?
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s4/i9500-develop/rom-t2913193
http://forum.xda-developers.com/showthread.php?t=2688387
and CM11 found outside XDA, I cannot find link.
I also tried to flash CM10.2 and 10.1, but both recoveries refused to even flash it.
I found out that the problem is I cannot flash kernel. I tried to flash few of them, but nothing changed in About device/Kernel Version. I also have SE for Android status "Enforcing".
mintor said:
I found out that the problem is I cannot flash kernel. I tried to flash few of them, but nothing changed in About device/Kernel Version. I also have SE for Android status "Enforcing".
Click to expand...
Click to collapse
What does it say your model is when you are in download mode?
Lennyz1988 said:
What does it say your model is when you are in download mode?
Click to expand...
Click to collapse
Do you mean "Product name"? It's SHV-E300K
It's Korean model. I'm not sure if GT-I9500 ROMs will work correctly on SHV-E300K (if it's booting), due to too many differences between International and Korean version.
Sent from my ASUS_Z00AD
mintor said:
Do you mean "Product name"? It's SHV-E300K
Click to expand...
Click to collapse
Then why did you say you have an i9500? You have a SHV-E300K which is a completely different model.
Lennyz1988 said:
Then why did you say you have an i9500? You have a SHV-E300K which is a completely different model.
Click to expand...
Click to collapse
Because in About device/Model number it shows I9500. Sorry, I didn't know the info from download mode is more important. Why would it show different things anyway?
mintor said:
Because in About device/Model number it shows I9500. Sorry, I didn't know the info from download mode is more important. Why would it show different things anyway?
Click to expand...
Click to collapse
Because you can change it manually, but you cannot change the model in in download mode.
forum.xda-developers.com/showthread.php?t=2284543&page=101
Use that thread for reference.
Related
I really screwed this one up guys. I was trying to upgrade to the new 4.3 TW based roms and accidentally installed all the knox stuff and all that, but I'm not really worried about the warranty.
What I am worried about though is that now, no matter what I try I get stuck in a boot loop. I have formatted my external SD card, reinstalled official CWM recovery, wiped everything more often than I can count and tried TW based roms, official ROM, AOSP based ROMs and nothing works. In most cases this is what happens after install:
1. The boot animation comes up
2. It actually boots
3. Then immediately force shutdowns
4. Boot loop
I have tried everything. I even tried just going back to stock ROM but I got an error in heimdall.
ERROR: Failed to open file "system.img.ext4"
Click to expand...
Click to collapse
Does anybody have any solutions for me. I feel like i've done every tutorial on the internet for 2 days now and I just don't know what to do!
Pesvardur said:
I really screwed this one up guys. I was trying to upgrade to the new 4.3 TW based roms and accidentally installed all the knox stuff and all that, but I'm not really worried about the warranty.
What I am worried about though is that now, no matter what I try I get stuck in a boot loop. I have forformattedmatted my external SD card, reinstalled official CWM recovery, wiped everything more often than I can count and tried TW based roms, official ROM, AOSP based ROMs and nothing works. In most cases this is what happens after install:
1. The boot animation comes up
2. It actually boots
3. Then immediately force shutdowns
4. Boot loop
I have tried everything. I even tried just going back to stock ROM but I got an error in heimdall.
Does anybody have any solutions for me. I feel like i've done every tutorial on the internet for 2 days now and I just don't know what to do!
Click to expand...
Click to collapse
Ok Bro I had same problem.
Facts: if your stock is 4.2 that's why you can't flash - 4.3 forbids downgrade. Try this http://forum.xda-developers.com/showthread.php?t=2250824 and find XXUEMJ7 - you should be able to flash it. Did it today - writing from phone
socah said:
Ok Bro I had same problem.
Facts: if your stock is 4.2 that's why you can't flash - 4.3 forbids downgrade. Try this http://forum.xda-developers.com/showthread.php?t=2250824 and find XXUEMJ7 - you should be able to flash it. Did it today - writing from phone
Click to expand...
Click to collapse
Ah, thing is I'm on Linux now and can't use ODIN . But are you saying my problem is that I'm trying to flash 4.3 roms, that I have to have 4.2.2 roms? Or vice versa? Also, I must have ****ed up even further because now I can't even print-pit in heimdall.
EDIT: Well anyway, I get home in about 3 hours and then I'll have a windows machine. I'll try it then. Will update when that's done.
Pesvardur said:
Ah, thing is I'm on Linux now and can't use ODIN . But are you saying my problem is that I'm trying to flash 4.3 roms, that I have to have 4.2.2 roms? Or vice versa? Also, I must have ****ed up even further because now I can't even print-pit in heimdall.
EDIT: Well anyway, I get home in about 3 hours and then I'll have a windows machine. I'll try it then. Will update when that's done.
Click to expand...
Click to collapse
I was saying that you probably tried flash 4.2 rom on 4.3 rom you have on phone - which is impossible due to Knox lock that will not allow to downgrade. Just download 4.3 rom and flash it, heimdall could do the job too.
socah said:
I was saying that you probably tried flash 4.2 rom on 4.3 rom you have on phone - which is impossible due to Knox lock that will not allow to downgrade. Just download 4.3 rom and flash it, heimdall could do the job too.
Click to expand...
Click to collapse
Ah but I've been trying exclusively to install 4.3 roms. But I haven't yet tried it on Odin.
socah said:
I was saying that you probably tried flash 4.2 rom on 4.3 rom you have on phone - which is impossible due to Knox lock that will not allow to downgrade. Just download 4.3 rom and flash it, heimdall could do the job too.
Click to expand...
Click to collapse
Well, thanks guy. Flashing the stock rom worked perfectly FROM ODIN. For some reason it just would not work on my Linux machine using Heimdall. But I feel like I tried this yesterday... although that was at like 3:30 am so I might have hallucinated it.
Anyway, you are a god and I hope for all the luck in the world to you.
Just a quick update: I found out the reason I was stuck in the boot animation and it crashing was in fact because the battery is faulty. I thought it was because flashing the ROMS wasn't working, but it was because the battery was shutting down at random intervals no matter what the charge
Sent from my GT-I9505 using Tapatalk
I found the development thread, downloaded and flashed the p700 version instead of the p705 like I should have and now clockwork won't let me flash the correct version...
Is there a way to correct my mistake? I wouldn't normally care as it seems to work fine, but it's very annoying that the phone won't get out of Edge mode and I have perfect 3G nearby.
Thanks in advance!
-Dave
2BNDatte said:
I found the development thread, downloaded and flashed the p700 version instead of the p705 like I should have and now clockwork won't let me flash the correct version...
Is there a way to correct my mistake? I wouldn't normally care as it seems to work fine, but it's very annoying that the phone won't get out of Edge mode and I have perfect 3G nearby.
Thanks in advance!
-Dave
Click to expand...
Click to collapse
Why won't it let you flash the correct version? Just put the ROM on your external SD, boot into CWM and flash the correct ROM. If that's not possible, I suggest you flash your country's firmware via KDZ and then root your phone, unlock your boot loader again and flash the correct ROM (this is the long way).
You should flash again CWM with CWM app. It'll probably overwrite your current recovery which probably kept in memory your device as a P705 or an other thing.
Sent from my Nexus 7
TahaX said:
Why won't it let you flash the correct version?
Click to expand...
Click to collapse
I don't know, that's the question I was asking you.
TahaX said:
Just put the ROM on your external SD, boot into CWM and flash the correct ROM.
Click to expand...
Click to collapse
Yes, I am aware of how to flash a ROM, that's how I got into this situation. CWM keeps telling me the correct ROM is for a p705 and it says I have a p700, which is not true. It is clearly a p705!
TahaX said:
If that's not possible, I suggest you flash your country's firmware via KDZ and then root your phone, unlock your boot loader again and flash the correct ROM (this is the long way).
Click to expand...
Click to collapse
I really don't want to do that if I don't have to.
azvlean said:
You should flash again CWM with CWM app.
Click to expand...
Click to collapse
Are you are saying that I should re-flash CWM? How would that change things?
You flashed a ROM that changed your phone to a P700, theoretically speaking. There is no way to revert, unless, and this is a theory and not a possible solution, if you find a different P705 ROM and try to flash that. Maybe CWM will let you flash that P705 ROM even though it thinks that your phone is a P700. If this doesn't work, I don't think there's a different way to change your phone back to a P705 rather than flashing the original firmware through KDZ.
TahaX said:
You flashed a ROM that changed your phone to a P700, theoretically speaking. There is no way to revert, unless, and this is a theory and not a possible solution, if you find a different P705 ROM and try to flash that. Maybe CWM will let you flash that P705 ROM even though it thinks that your phone is a P700. If this doesn't work, I don't think there's a different way to change your phone back to a P705 rather than flashing the original firmware through KDZ.
Click to expand...
Click to collapse
Okay, I suppose I didn't make it clear. I already tried to flash the p705 ROM and CWM won't let me.
I am confused as to why CWM won't let me change ROMs considering that I haven't changed the recovery, only the ROM. Why would a ROM not let me change to another ROM? Maybe I have the incorrect CWM version?
2BNDatte said:
Okay, I suppose I didn't make it clear. I already tried to flash the p705 ROM and CWM won't let me.
I am confused as to why CWM won't let me change ROMs considering that I haven't changed the recovery, only the ROM. Why would a ROM not let me change to another ROM? Maybe I have the incorrect CWM version?
Click to expand...
Click to collapse
Yeah, I guess it's just CWM trying to protect P700 users from flashing the wrong version, but not the other way around. Weird. Anyways, I suggest you give it a go with TWRP Recovery. They might allow you to flash a P705 ROM.
2BNDatte said:
Okay, I suppose I didn't make it clear. I already tried to flash the p705 ROM and CWM won't let me.
I am confused as to why CWM won't let me change ROMs considering that I haven't changed the recovery, only the ROM. Why would a ROM not let me change to another ROM? Maybe I have the incorrect CWM version?
Click to expand...
Click to collapse
Actually, CWM considers your phone is a P700. But, if you flash a second time CWM with CWM app available on the Play Store, your recovery will be overwrited with a new recovery who " knows " you own a LG P-705. So, your problem will probably be solved. Or you can also flash TWRP.
Sent from my Nexus 7
Okay... I'm doing the whole thing over again, this really sucks because I spent hours getting it the way I like it, too. UGH.
2BNDatte said:
Okay... I'm doing the whole thing over again, this really sucks because I spent hours getting it the way I like it, too. UGH.
Click to expand...
Click to collapse
That's the beauty of being able to develop your phone to your own liking my friend!
Now KDZ says it can't find the phone... what gives?
2BNDatte said:
Now KDZ says it can't find the phone... what gives?
Click to expand...
Click to collapse
Did you install your drivers? Did you install LG PC Suite? Was your phone in emergency mode? Did you select "EMERGENCY" from the drop down list? Try to double check all of these things.
TahaX said:
Did you install your drivers? Did you install LG PC Suite? Was your phone in emergency mode? Did you select "EMERGENCY" from the drop down list? Try to double check all of these things.
Click to expand...
Click to collapse
I don't know how to get into emergency mode... But yes, I have all the drivers. The PC suite won't connect for some reason, it won't me to download a driver, but the device isn't listed through any of the carriers it lists.
2BNDatte said:
I don't know how to get into emergency mode... But yes, I have all the drivers. The PC suite won't connect for some reason, it won't me to download a driver, but the device isn't listed through any of the carriers it lists.
Click to expand...
Click to collapse
Connect your phone to your computer via an USB cable, remove your battery, wait until the LG logo goes away and then hold the power button and volume up button until you see the yellow emergency screen and immediately release all buttons.
The emergency mode only stays on for a second then the phone goes into regular boot...
2BNDatte said:
The emergency mode only stays on for a second then the phone goes into regular boot...
Click to expand...
Click to collapse
Hold the buttons a bit shorter. It's all about timing.
Okay, i wasn't releasing the buttons fast enough, nevermind, its doing it's thing now, will update...
The problem looks to be the original firmware I had, I still get the same issue now. I need p705 specific firmware to start with...
A little history on the phone, my friend gave it to me because she couldn't remember the pin to open the phone, so I had to flash it to use it. My bad, I guess i didn't know where to get the v20 file to start with. Do you know where I can get a p705 specific version?
Bad post, sorry!
For the record, our phone is the same as the 700. Only they had nfc while we don't. So it's ok to flashed it but the downside is you don't have deepsleep. The battery will drained because of nfc. So relax, you don't need to go over the kdz flashing as long as you can go to cwm. So questions:
1. what Rom did you flashed?
2. If you hate the kdz flashing, then just go to cwm and flashed the correct one. But before that, you need to delete the first line of the updater script in order for it to continue.
3. Or you just stay with the Rom, and delete all nfc related files and flash 705 kernel. For nfc remover, just go to apps and themes section and look for nfc remover by caliban as reference.
sent from my p705g - v20f jellybean extreme w/ stock kernel
So I'm really into Android developing, I'm always flashing and installing etc, but I got a problem now.
Phone information
LG G2 D802
Rooted
TWRP Recovery 2.7.0.0
Was running 4.4.2, found a kdz file on the internet and flashed it (no regular update from my phone)
What happenedI actually did something stupid, I received an application update from the LG Download Center (or whatever it's called) on my phone and clicked on it. I was planning on flashing Android 4.4.2 again because my firmware was not stable, and I thought this update could help me.
But no, after it finished downloading, I automatically booted into recovery.
What I didSo I tried to reboot and enter my OS, but unfortunately, I was stuck in recovery.
I did everything I could, wiping (Dalvik) cache, factory reset, flashed a new rom, restored Nandroid backup, but no, every time I booted, I got back into recovery again.
I only saw 1 option left, booting into download mode and flashing a new firmware.
I found the Netherlands 16GB kdz file for Android 4.4.2 (because I had a French one first), the one I was looking for.
Looked all over the internet, and all guides pointed me to this guide.
Tried it, but I got multiple errors, one of them was that my phone was not connected while I was at 15% of the flash process.
What happenedAfter that first flashing process, I booted up, but got a Security Error. After the Security Error was showing for 5 seconds, my phone shut down. This is happening every time I try to boot up.
I couldn't access my recovery anymore, nothing. Edit: I can access my recovery right now, and I tried this, but when I boot up I get the Security Error again.
The big problem right now is the Security Error! How do I bypass that?
So can someone please help me out!
Several phones/tablets of mine bricked and I always found a way to get out of it, but not this time, unfortunately...
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
XxZombiePikachu said:
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
Yes, I actually have. Didn't mention it, but after I did that I booted and got an LG logo and below it was a text that said 'Security Error' After like 5 seconds the security error goes away and my phone shuts down. I can only enter download mode right now.
I'll edit my first post with this info.
Thanks for the help though!
Edit: I find a way to access my recovery again because at first I couldn't but I figured out that the code in the thread you linked was a bit different than the code I entered at first.
So I used the code you gave me, but now I get the Security Error again!
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
evilruck said:
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
Click to expand...
Click to collapse
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Ibrahim9999 said:
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Click to expand...
Click to collapse
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
evilruck said:
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
Click to expand...
Click to collapse
Thanks man! I'm probably going to save money because of you, awesome!
Ibrahim9999 said:
Thanks man! I'm probably going to save money because of you, awesome!
Click to expand...
Click to collapse
I hope so!
Let me know if you fix the thing :laugh:
evilruck said:
I hope so!
Let me know if you fix the thing :laugh:
Click to expand...
Click to collapse
I just managed to fix it! Thank you so much man!
Can someone help me plz I got flashily got CWM instead of the TWRP and got and lg update it updated and now it's stuck in recovery mode it won't go into download mode it only goes to recovery mode and my computer won't recognize my phone so if any one knows how to fix it can you plz help me out
my pc don't recognize the lg g2 in download mode!
i installed the drivers and the USB is connected but the pc don;t even say that the device is connected . and nothing in device manager at all
Perhaps you might consider sending it in to lg if you still have warranty. But I'd you don't, there are services on eBay/ Craigslist that can help you.
Sent from my LG-D800 using XDA Free mobile app
This used to be easy.
After 8 hours yesterday I think I managed to root the phone. CWM/TWRP will not install. At all, under any method. Rom manager, goo manager, I now get this stupid message that says that "an application attempted to access something unauthorized and has been blocked" over and over.
Just trying to flash CM11 rom. Guess I need to learn how to sideload or something? I physically can't get my phone to recovery mode other than the stock Android, which does not have the "flash zip from sdcard" option.
For the love of god help me. My phone stopped working around 2 pm yesterday and I seriously can't believe I'm about to be going into day 2 of this, so rather than drive myself crazy i'm going to wait for help
bump please help should be simple
Hi,
Please, don't panic! Panic is your worst enemy . First, give a good read here: http://forum.xda-developers.com/showthread.php?t=2419762. Then try again . It's very likely Knox is blocking your TWRP/CWM installation, that's why you receive this message.
All the best,
~Lord
XxLordxX said:
Hi,
Please, don't panic! Panic is your worst enemy . First, give a good read here: http://forum.xda-developers.com/showthread.php?t=2419762. Then try again . It's very likely Knox is blocking your TWRP/CWM installation, that's why you receive this message.
All the best,
~Lord
Click to expand...
Click to collapse
thanks
knox is disabled
root is gained
su is installed
rom manager and goo manager installed
when i downloaded the CM rom from goo manager and try to install it, the phone restarts in download mode and just sits there...
Damani311 said:
thanks
knox is disabled
root is gained
su is installed
rom manager and goo manager installed
when i downloaded the CM rom from goo manager and try to install it, the phone restarts in download mode and just sits there...
Click to expand...
Click to collapse
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord
XxLordxX said:
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord
Click to expand...
Click to collapse
tried flashing four different CWM tars, all are failing.
XxLordxX said:
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord
Click to expand...
Click to collapse
tried flashing four different CWM tars, all are failing.
also trying to flash TWRP
its just all failing on the install
Hi,
Please post your installation issue on the Galaxy S4 Help Thread there might be someone better than me to help you there. Also are you sure you're flashing the right files and using the right method? Did you try another USB Cable? Did you try another Odin version? It all can contribute to the fail.
~Lord
XxLordxX said:
Hi,
Please post your installation issue on the Galaxy S4 Help Thread there might be someone better than me to help you there. Also are you sure you're flashing the right files and using the right method? Did you try another USB Cable? Did you try another Odin version? It all can contribute to the fail.
~Lord
Click to expand...
Click to collapse
its the official samsung cable. and yes i tried others
tried other versions of odin as well
and different versions of both twrp and cwm
its crazy i tells ya xD
If it fails to flash true Odin, then you are doing something wrong.
- Different pc
- Reinstall drivers
- Different cable
- Different usb port
- Make sure kies is not running in the background
What are you running? Windows 8? Try a windows 7 pc.
Post the details of the error you are getting.
Also when the flash goes succesfull, but you still don't have a custom recovery, then uncheck auto-reboot.
can someone please link me to a guaranteed working version of a flashable recovery for odin ?
I know its a lot to ask but I've actually gone through almost that entire list you listed
tried diff cables
no kies runnning
on windows 7
drivers been installed twice
maybe i should try the other port, but in case that doesnt work can anyone just link me? sorry i've just never had this much problems with this, must be b/c of the new security knox update or w/e in oct of last year. Last June I did all this in about 15 minutes....
I had the same trouble with the knox crap yesterday, the only way I could get it rooted and/or with custom recovery was to use the Cyanogen windows installer, then when CM booted I then rebooted into recovery and installed a different rom from there. :good:
dwarfer66 said:
I had the same trouble with the knox crap yesterday, the only way I could get it rooted and/or with custom recovery was to use the Cyanogen windows installer, then when CM booted I then rebooted into recovery and installed a different rom from there. :good:
Click to expand...
Click to collapse
that's crazy
so where do i find this windows installer? i'm just trying to put CM on there so I suppose this would work
Hi i know youve already said said its officail cable but im saying try another different s4 cable. Because when i was installing recovery or anything it wouldnt let me (i thought i had original white s4 cable) but then i got my dads cable (hes gt s4) and it worked instantly. These fake cables are at large and its very very difficult to tell if its original.
Also like previous guy said using a different computer/laptop also helps i know because ive flashed my phones since day 1.
GL and plz let me know if u managed to fix it another way as its always good to try new options when others fail.
189cutter said:
Hi i know youve already said said its officail cable but im saying try another different s4 cable. Because when i was installing recovery or anything it wouldnt let me (i thought i had original white s4 cable) but then i got my dads cable (hes gt s4) and it worked instantly. These fake cables are at large and its very very difficult to tell if its original.
Also like previous guy said using a different computer/laptop also helps i know because ive flashed my phones since day 1.
GL and plz let me know if u managed to fix it another way as its always good to try new options when others fail.
Click to expand...
Click to collapse
alright it'd be awesome if someone can post a link to the files the work, for sure.
CM windows installer
CWM odin tar file
TWRP odin tar file
Damani311 said:
alright it'd be awesome if someone can post a link to the files the work, for sure.
CM windows installer
CWM odin tar file
TWRP odin tar file
Click to expand...
Click to collapse
http://www.cyanogenmod.org/ then click the start button and follow the instructions.
It will get you to download the installer (or http://dist01.slc.cyngn.com/CMInstaller.msi?t=1403660099360) the click it to run, It may download an update for itself, then it will download recovery, operating system, gapps, then start to install everything. About 300mb altogether.
That way you don't need the tar files, just search on this sight for flashable from recovery for the recovery files you want. (I use the touch versions myself).
dwarfer66 said:
http://www.cyanogenmod.org/ then click the start button and follow the instructions.
It will get you to download the installer (or http://dist01.slc.cyngn.com/CMInstaller.msi?t=1403660099360) the click it to run, It may download an update for itself, then it will download recovery, operating system, gapps, then start to install everything. About 300mb altogether.
That way you don't need the tar files, just search on this sight for flashable from recovery for the recovery files you want. (I use the touch versions myself).
Click to expand...
Click to collapse
thanks, but naturally this would be too easy
says: "not supported on your device"
a freaking S4 AT&T! what the ****?
From what I've read AT&T have locked bootloaders. Glad I have an unlocked Australian version!
Yeah so if anyone can still find a way to help me that'd be awesome. Wasted two days already and rather not be stuck with stock
Damani311 said:
Yeah so if anyone can still find a way to help me that'd be awesome. Wasted two days already and rather not be stuck with stock
Click to expand...
Click to collapse
So do you have an AT&T phone? If you do, you are in the wrong section of the forum.
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.