Related
I own a Galaxy Note 10.1 WiFi N8010, was bought in Germany quite some time ago (so CSC is German),
It came with 4.0.3, which was later updated to 4.0.4 and then to 4.1.1. Currently it is running Jellybean 4.1.1.
I had found the Exynos exploit and used it to root my device. The 4.1.2 update came out so I unrooted my device.
The "Device Status" shows "OFFICIAL".
The device received an OTA package, started installing it, started the count to 100%, and at 28-29 percent, the update stopped, the device rebooted, reported a failure and sent me to KIES.
I have some problems with KIES so I am looking for other solutions.
I thought maybe I'd use Mobile Odin to flash the stock firmware but I found it needed a flashkernel which I do not know how nor want to install right now. I was thinking about using ODIN to flash the firmware, but the size of the firmware scared me. I am used to flash 300MB SBF files on my Motorola Defy but this 1GB firmware is insane! I am afraid my computer will suddenly shut down and I will get a hard brick. Anyway, assuming I got over this fear, I have a couple of questions:
1. Does flashing with ODIN delete the user data?
2. Assuming I want to delete my data (like factory reset) - what options should I choose in ODIN when I flash?
3. Are there any options not including ODIN, KIES or the computer in general?
Hi folks,
I've seen other threads where people report similar but perhaps not quite the same issue I am having with my GT-N8010. For context, I installed 4.4.2 a while ago (February?). This was one of the Omni nightlies, omni-4.4.2-20140210. In preparation for this I had installed twrp-2.6.3.1-n8000. All was well and I much enjoyed kitkat until a few weeks came back from a trip and noticed the device had run out of juice. Connected it to the charger and then...
Symptoms:
* Seems to be stuck displaying the Samsung logo
* Download mode works
* When trying to enter recovery (Power+VOL_UP) it briefly shows the Team Win screen logo and then just reboots
Things I've tried:
* Reinstall twrp, using Odin and download mode; Odin succeeds, the device reboots, same symptoms as before
* Install some other recovery (HighOnAndroidv1CWMRecoveryGTN8000), same result; it is as though NOTHING gets flashed???
* Install stock (4.0.4 or 4.1.2, I don't remember) Samsung ROM; Odin succeeds (it takes a few minutes), device reboots but HECK I'm going insane NOTHING has changed, symptoms as before
Please please can one of you ninja dudes help me out as this is such a precious tablet and hopefully not just a brick now .
Among the things I haven't tried, but heard can do wonders, is to re-partition. So if you happen to have a PIT file from your N8010 then would you mind sharing it through a PM please.
Also am currently downloading the "official" 4.4.2 release for the N8000. I've heard this is NOT for the N8010 but as a last resort, I might flash it??
Many thanks in advance for all the help!
Matt
matt_9010 said:
Hi folks,
I've seen other threads where people report similar but perhaps not quite the same issue I am having with my GT-N8010. For context, I installed 4.4.2 a while ago (February?). This was one of the Omni nightlies, omni-4.4.2-20140210. In preparation for this I had installed twrp-2.6.3.1-n8000. All was well and I much enjoyed kitkat until a few weeks came back from a trip and noticed the device had run out of juice. Connected it to the charger and then...
Symptoms:
* Seems to be stuck displaying the Samsung logo
* Download mode works
* When trying to enter recovery (Power+VOL_UP) it briefly shows the Team Win screen logo and then just reboots
Things I've tried:
* Reinstall twrp, using Odin and download mode; Odin succeeds, the device reboots, same symptoms as before
* Install some other recovery (HighOnAndroidv1CWMRecoveryGTN8000), same result; it is as though NOTHING gets flashed???
* Install stock (4.0.4 or 4.1.2, I don't remember) Samsung ROM; Odin succeeds (it takes a few minutes), device reboots but HECK I'm going insane NOTHING has changed, symptoms as before
Please please can one of you ninja dudes help me out as this is such a precious tablet and hopefully not just a brick now .
Among the things I haven't tried, but heard can do wonders, is to re-partition. So if you happen to have a PIT file from your N8010 then would you mind sharing it through a PM please.
Also am currently downloading the "official" 4.4.2 release for the N8000. I've heard this is NOT for the N8010 but as a last resort, I might flash it??
Many thanks in advance for all the help!
Matt
Click to expand...
Click to collapse
There is a n8010 release of 4.4.2 for your Device. but Do NOT Flash the n8000 rom on it..
I think you should odin the 8010 rom from Sam mobile and you will be ok . If not browse the forum and find a pit file for that device.. also some have reported Issues flashing with latest odin. try i think verson 2.9 ?
erica_renee said:
There is a n8010 release of 4.4.2 for your Device. but Do NOT Flash the n8000 rom on it..
I think you should odin the 8010 rom from Sam mobile and you will be ok . If not browse the forum and find a pit file for that device.. also some have reported Issues flashing with latest odin. try i think verson 2.9 ?
Click to expand...
Click to collapse
Thanks, have just flashed the 8010 4.4.2 stock fw. Symptoms remain. I'd be very grateful for a PIT file as I've waded through the other threads and not too sure about the links to PIT files there. PM, anyone, please please .
I've got the N8010 PIT file from here:
http://forum.xda-developers.com/showthread.php?t=2363703
Sadly, this didn't change a thing. I'm still stuck at the Samsung logo, and still cannot enter recovery mode which still briefly shows the TeamWin logo and then reboots.
This N8010 is just over a year old. Bought in Germany, I wonder whether Samsung would repair under warranty. I guess they won't as it's been fiddled with. I've heard about JTAG repairs but something tells me this isn't going to help as I have a feeling that I just can't flash the darn thing. Eeek, faulty flash memory??
matt_9010 said:
I've got the N8010 PIT file from here:
http://forum.xda-developers.com/showthread.php?t=2363703
Sadly, this didn't change a thing. I'm still stuck at the Samsung logo, and still cannot enter recovery mode which still briefly shows the TeamWin logo and then reboots.
This N8010 is just over a year old. Bought in Germany, I wonder whether Samsung would repair under warranty. I guess they won't as it's been fiddled with. I've heard about JTAG repairs but something tells me this isn't going to help as I have a feeling that I just can't flash the darn thing. Eeek, faulty flash memory??
Click to expand...
Click to collapse
search for this file in the forum: Note10_PIT.zip (dunno0 where was it)
the if u can enter to download mode try to flash one of the latest 4.1.2 stock roms with odin 3.07....
if u succeed write here....:laugh:
karaern said:
search for this file in the forum: Note10_PIT.zip (dunno0 where was it)
the if u can enter to download mode try to flash one of the latest 4.1.2 stock roms with odin 3.07....
if u succeed write here....:laugh:
Click to expand...
Click to collapse
Sadly not. Others have reported that having gone with one of the Omni 4.4.2 builds they cannot get the official 4.4.2 release from Samsung installed, at least not with desktop Odin. They do succeed with mobile Odin but yeah, that's not an option here as I don't get past the Samsung logo and no recovery. This is really frustrating.....
matt_9010 said:
Sadly not. Others have reported that having gone with one of the Omni 4.4.2 builds they cannot get the official 4.4.2 release from Samsung installed, at least not with desktop Odin. They do succeed with mobile Odin but yeah, that's not an option here as I don't get past the Samsung logo and no recovery. This is really frustrating.....
Click to expand...
Click to collapse
Try to reinstall the latest rom u had before installing kk! Exact same version with same recovery.
matt_9010 said:
Hi folks,
I've seen other threads where people report similar but perhaps not quite the same issue I am having with my GT-N8010. For context, I installed 4.4.2 a while ago (February?). This was one of the Omni nightlies, omni-4.4.2-20140210. In preparation for this I had installed twrp-2.6.3.1-n8000. All was well and I much enjoyed kitkat until a few weeks came back from a trip and noticed the device had run out of juice. Connected it to the charger and then...
Symptoms:
* Seems to be stuck displaying the Samsung logo
* Download mode works
* When trying to enter recovery (Power+VOL_UP) it briefly shows the Team Win screen logo and then just reboots
Things I've tried:
* Reinstall twrp, using Odin and download mode; Odin succeeds, the device reboots, same symptoms as before
* Install some other recovery (HighOnAndroidv1CWMRecoveryGTN8000), same result; it is as though NOTHING gets flashed???
* Install stock (4.0.4 or 4.1.2, I don't remember) Samsung ROM; Odin succeeds (it takes a few minutes), device reboots but HECK I'm going insane NOTHING has changed, symptoms as before
Please please can one of you ninja dudes help me out as this is such a precious tablet and hopefully not just a brick now .
Among the things I haven't tried, but heard can do wonders, is to re-partition. So if you happen to have a PIT file from your N8010 then would you mind sharing it through a PM please.
Also am currently downloading the "official" 4.4.2 release for the N8000. I've heard this is NOT for the N8010 but as a last resort, I might flash it??
Many thanks in advance for all the help!
Matt
Click to expand...
Click to collapse
Did you ever find a solution ?
chappatti said:
Did you ever find a solution ?
Click to expand...
Click to collapse
Err well I ended up bringing the tablet to a Samsung service store where it was repaired under warranty, free of charge. Dunno what they did to it but it works and has the latest 4.4.2 firmware on it. Glad I have it back.
I have exactly same problem with N8005!... Can't reinstall twrp or any other recovery with Odin. ( "failed")... Can't enter twrp... Can't boot... I guess my tablet decided to suicide.
Hello
I use a ROM with XT897 CM10.2.1 and SIM MOD CornholioGSM since July 2014, it was working fine.
I flashed the ROM-cm-SNAPSHOT-YOG4PAO23E 12.1-20150901-xt897 (RELEASE) one month ago and the ROM worked well. A week ago, the phone was much slower, I turn off reboot and since it constantly!
I made the following transactions with TWRP:
- Reset factory
- Flash ROM (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897)
- Flash ROM (BlissPop-v4.0.1-xt897-OFFICIAL-20150917-1514)
- Flash recovery (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897-recovery.img)
- Flash TWRP
- Flash ROM (cm 12.1-20151007-SNAPSHOT-YOG4PAO339-xt897)
Always the same, I have the boot logo and the logo of the ROM and the phone reboots.
The ROM (CM12.1) has started once and then restart the phone has rebooted repeatedly.
I tried with or without a SIM card.
I do not understand where does the problem, can you help me?
Well not having the phone in front of me, I don't really quite understand the issue myself - however, I would suggest using RSD Lite and one of the FXZ files to flash everything (including recovery) back to stock.
If you still have issues, there is a bigger problem (likely hardware failure).
Hello
sorry if my explanation was not clear.
I added a photo which shows the two steps in the operation of my phone.
Step 1: Start the phone .
Step 2 : boot ROM CM12
The Step 2 lasts 23 seconds then return to Step 1 and Step 2 and Step 1, Step 2 infinitely .
I hope this is understandable .
I read on the forum that used some RSD Lite but as I had not used for the ROM installation, I did not understand why use .
I'm a new user, i can't post picture, I send link by PM, thanks.
I thought my last post made it clear what purpose RSD Lite and the FXZ files are - they restore the phone to stock completely - ROM, recovery, everything will be reset to when it was stock from the factory (granted it may be a newer image than what shipped on the phone, but you get the point).
Again, as I stated previously, if you still have issues after flashing everything stock your issue is likely not software, but hardware.
I searched the forum about RSD Lite. Now I understand its usefulness.
I used RSD Lite to flash the ROM asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip
My phone had with SPRINT .
The flash went well but unfortunately I still have the same problem :
Step 1: unlocked bootloader screen
Step 2: The red M MOTOROLA
Step 1, Step 2 , .....
Is there another test or I can consider it a hardware problem ?
Hardware problem can come out of the MODSIM ? I use a SIM card in the phone for 16 months.
Nicolas.636 said:
I searched the forum about RSD Lite. Now I understand its usefulness.
I used RSD Lite to flash the ROM asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip
My phone had with SPRINT .
The flash went well but unfortunately I still have the same problem :
Step 1: unlocked bootloader screen
Step 2: The red M MOTOROLA
Step 1, Step 2 , .....
Is there another test or I can consider it a hardware problem ?
Hardware problem can come out of the MODSIM ? I use a SIM card in the phone for 16 months.
Click to expand...
Click to collapse
The hardware issue is likely not related to the SIM modification. As to what exactly has failed, I'm not sure... perhaps the NAND or something else memory related.
Aouch aouch...
Thank you for your help.
I think it remains for me to search for a motherboard for photon Q.
Long life in the forum!
Use "borrowed" TWRP recovery image.
Nicolas.636 said:
Hello
I use a ROM with XT897 CM10.2.1 and SIM MOD CornholioGSM since July 2014, it was working fine.
I flashed the ROM-cm-SNAPSHOT-YOG4PAO23E 12.1-20150901-xt897 (RELEASE) one month ago and the ROM worked well. A week ago, the phone was much slower, I turn off reboot and since it constantly!
I made the following transactions with TWRP:
- Reset factory
- Flash ROM (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897)
- Flash ROM (BlissPop-v4.0.1-xt897-OFFICIAL-20150917-1514)
- Flash recovery (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897-recovery.img)
- Flash TWRP
- Flash ROM (cm 12.1-20151007-SNAPSHOT-YOG4PAO339-xt897)
Always the same, I have the boot logo and the logo of the ROM and the phone reboots.
The ROM (CM12.1) has started once and then restart the phone has rebooted repeatedly.
I tried with or without a SIM card.
I do not understand where does the problem, can you help me?
Click to expand...
Click to collapse
I had a similar incident a few days ago. I have a hard time stopping myself from pushing the limits. Usually I stop when it's broken. I tried RSD Lite, SDB sideload/ flash, zip install from recovery, fastboot(mine's dead), all with no luck.
Any how, If you have CWM, temporarily change to TWRP. If you already have TWRP it's easier.
XDA has a TWRP recovery image in the forum. Put that in your sdcard (I had to paste it from my computer because my xt897 was soft bricked). Flash from TWRP.
Worked fom me. got my phone back after 1 week of flashing everything and then some.
Good luck.
http://forum.xda-developers.com/showthread.php?t=2295643
http://forum.xda-developers.com/showthread.php?t=2295643&page=2
Hello
thank you for this new information.
I tried it and it worked with the ROM [PQ_ICS-Stock] but only with that one!
I tried the ROM [PQ_JB-421] , several Cyanogen ROM but still the same looping boot problem.
I tried several version of TRWP without success .
I do not understand why my Photon Q only works with this ROM [PQ_ICS-Stock] .
Is still a motherboard problem ?
Hello everyone
I'm going crazy !
As I had not managed to solve my problem, I ordered a mainboard on ebay.
Today I realized the SIMMOD on this new board.
when I restarted phone the same startup problems with the ROM SPRINT !
I unlocked the bootloader .
I installed TWRP 2.7.1.2
I installed CM12.1-20151219 - NIGHTLY - XT897
Still the same problem starting loop.
Someone an idea ?
Nicolas.636 said:
Hello everyone
I'm going crazy !
As I had not managed to solve my problem, I ordered a mainboard on ebay.
Today I realized the SIMMOD on this new board.
when I restarted phone the same startup problems with the ROM SPRINT !
I unlocked the bootloader .
I installed TWRP 2.7.1.2
I installed CM12.1-20151219 - NIGHTLY - XT897
Still the same problem starting loop.
Someone an idea ?
Click to expand...
Click to collapse
If you can't RSD Lite, something is up. Either you are not doing the process correctly, or there is something wrong with the device (still).
Perhaps you were always on ICS and never made the official jump to JB? You say you can RSD Lite to an ICS version, just not a JB version? So 4.0.x works but 4.1.x does not?
Again I'm talking stock. If stock doesn't work, I wouldn't even attempt CM. Start with the basics, then work your way towards the aftermarket.
I agree that if the stock rom does not work after the installation with RSD Lite is that it remains something (software) .
The first motherboard I used 12.1 CM for several months it is that the phone supports android 5.1
I agree that it must abort running a stock ROM before flashing a ROM CM. But the ICS ROM STOCK works!
It is possible that I did not do the process correctly .
What surprises me is that the second board had the same problem with the ROM SPRINT !
I will do other tests.
Nicolas.636 said:
What surprises me is that the second board had the same problem with the ROM SPRINT !
Click to expand...
Click to collapse
This is the part that makes me think you are perhaps missing some step in the process somewhere.
Can you RSD Lite to ICS? Not flash it with TWRP. If that is successful, try to RSD Lite to the latest JB again.
I modified the second motherboard ( mod sim card ) and I started the phone with the ROM SPRINT and I got the boot problem repeatedly.
the common point of two motherboards is that they both have a bad ESN .
I will do other tests.
Nicolas.636 said:
I modified the second motherboard ( mod sim card ) and I started the phone with the ROM SPRINT and I got the boot problem repeatedly.
the common point of two motherboards is that they both have a bad ESN .
I will do other tests.
Click to expand...
Click to collapse
Bad ESN shouldn't prevent booting... it would prevent you from activating the device on the Sprint network, but I would imagine you don't care about that...
arrrghhh said:
it would prevent you from activating the device on the Sprint network, but I would imagine you don't care about that...
Click to expand...
Click to collapse
yes
I used RSD Lite 6.1.6 for flashing the ROM [ 2014-03-09 - TSv2 ] but the process has blocked after the flash.
Here is what I did :
1- run RSD Lite
2- Start the phone in FASTBOOT mode.
3- usb phone connection to PC
4- opening of the ROM [ 2014-03-09 - TSv2 ] and "uncompress and start flashing"
5- flash goes well
6- the phone reboots => Logo M red => telephone reboot => Logo M red => again ....
7- RSD Lite waits for the restart ... [ it waits again, LOL ]
8- I turned off the phone and I unplugged.
9- I turned on the phone who start properly, I arrived at the language selection screen .
The ROM is an android version 4.0.4 , I think you know this ROM .
Why the process with RSD Lite has blocked the phone to reboot ?
That's what I did wrong in the process?
I have read many forum post, I tried several methods but only in the ROM 4.0.4 STOCK work. Flashed with RSD lite or restoration of a backup with TWRP.
I have the bootloop problem using RSD Lite 6.2.4 for ROM 4.1.2 CSPIRE or ROM 4.1.2 SPRINT. No error message of RSD lite. No error message of phone.
I've modified the XML file but it changed nothing.
Same problem using TRWP with custom ROM or restoration of a backup ROM4.1.2 JB.
Same problem using OPEN RECOVERY 209 with custom ROM.
Where is the problem ?
I would use CM12 ROM.
Nicolas.636 said:
I have read many forum post, I tried several methods but only in the ROM 4.0.4 STOCK work. Flashed with RSD lite or restoration of a backup with TWRP.
I have the bootloop problem using RSD Lite 6.2.4 for ROM 4.1.2 CSPIRE or ROM 4.1.2 SPRINT. No error message of RSD lite. No error message of phone.
I've modified the XML file but it changed nothing.
Same problem using TRWP with custom ROM or restoration of a backup ROM4.1.2 JB.
Same problem using OPEN RECOVERY 209 with custom ROM.
Where is the problem ?
I would use CM12 ROM.
Click to expand...
Click to collapse
Without having the device in my hands, it's hard to say for sure. The only difference I can see you are doing differently from me is using a newer version of RSD. I doubt that would be an issue, but may want to try other RSD versions.
In the end, I suppose if 4.0.4 works, use that...
Thank you for you help.
I'll buy a other PHOTON Q on EBAY.
I do other test with the new PHOTON Q.
Hello
I received my new q photon.
It is version 4.1.2
I unlocked the bootloader .
I made a backup with TWRP and OPEN_RECOVERY_209 .
I tried an installation of 3 different ROM but I have an error message !
I do not understand where does the problem ?!
Is this a bad version of TWRP or ROM ?
Hi,
The first is to apologize for the language used, and the length of the text. I am from Spain and my level of English is low, so as it was a fairly long post I used Google Translator and I know that makes it very literal translation ...
I write this post to see if anyone can help me or give some idea ... I explain the problem.
I own for some time ago the Tablet, Samsung Galaxy Note 10.1 (2012) . He has always liked to try new ROMs, so far without much trouble, but .... I tempted fate a lot.
At some point, after changing the Recovery and ROM, to test Marshmallow, the WiFi stopped working, which is a problem in a device of this type, you lose a lot of functionality.
I have tried many ROMS, about 10, and none of them work properly. It is true that some seems, makes the attempt, working. But it does not work.
I have also tried different Recoveries (CWRM, TWRP, Stock, HigOnAndroid, ....), and I have not gotten the Tablet WiFi work.
With all these tests, entering DOWNLOAD mode, it indicates that the device model is the Note 10.1 GT-N8000, the model without WiFi. And when you install a ROM, and go to Settings/Info, the system said that the Tablet is the GT-N8000 model.
This has led me to perform multiple tests:
A- Flash several ROMS by Recovey, usually used the TWRP.
B- Change Recovey installed by Odin 3.10
C- The last thing I have tried, is back to the original ROM and Recovery by Odin 3.10
All these attempts, multiple, have thrown me the same result. The WiFi does not work, and continues to indicate that is the model GT-N8000
The questions are:
1 - Is it normal, even the GT-N8013 model DOWNLOAD mode appears as the GT-8000?
2- Is there any way to get back to its original state, GT-N8013, with WiFi?
3- What Recovery would be most appropriate? (I once used the TWRP)
4- What ROM for this Tablet is the most appropriate? (This question is very personal, I've always liked Omega Rom)
What model do you have .
Samsung Galaxy Note (2012) Gt-N8013
peirof said:
Samsung Galaxy Note (2012) Gt-N8013
Click to expand...
Click to collapse
Hi, WiFi isn't working because you probabily stay with a older bootloader but with 6.0. When you flashed the MM rom, your tablet at which version of android was? Maybe i think 4.4.x if WiFi doesn't start. You need to update the bootloader into marshmallow or try look on the thread where you found the rom if there are some modem updates. By the way, if you want to get the stock firmware and install it on your tab, first go in sammobile site and download the firmware ( pay attention to version 4g / without 4g ) and then put your device in download mode->connect to odin-> on "PDA" load the firmware you downloaded -> start -> wait 10/12 mimutes and you will have the tablet as you bought for the first time.
And check if the rom is right for your device( because when kernel is different if the device start it can have some issues like WiFi )
Hope i help you
If i helped you, remember to click the thanks button!
gosha98_ said:
Hi, WiFi isn't working because you probabily stay with a older bootloader but with 6.0. When you flashed the MM rom, your tablet at which version of android was? Maybe i think 4.4.x if WiFi doesn't start. You need to update the bootloader into marshmallow or try look on the thread where you found the rom if there are some modem updates. By the way, if you want to get the stock firmware and install it on your tab, first go in sammobile site and download the firmware ( pay attention to version 4g / without 4g ) and then put your device in download mode->connect to odin-> on "PDA" load the firmware you downloaded -> start -> wait 10/12 mimutes and you will have the tablet as you bought for the first time.
And check if the rom is right for your device( because when kernel is different if the device start it can have some issues like WiFi )
Hope i help you
If i helped you, remember to click the thanks button!
Click to expand...
Click to collapse
Hi,
Thanks, sorry for delay, I can solve the isue with another Rom
Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.
this amount of pain can't be titled
Drow_Warlord said:
Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.
Click to expand...
Click to collapse
Day#4 Fail compilation
I see that this gets no response,but I'll continue this thread just in case I fix this and somebody else gets into same problem themselves.
I mentioned before that I somehow flashed custom ROM over CWM and that helped my phone boot into working state after bootloop error caused by greatest Android software there is on the internet,the legendary "Dr.Fone"
The Custom rom used was "[OFFICIAL][i9500][5.1.x] CyanogenMod 12.1 for Samsung Galaxy S4 [NIGHTLY]" From xda user: Alberto96 (thank you friend).
After several other failed attempts of implementing Stock firmware on this bricked device over the PC,I got to the point where I think that it's literally imposible to make it work since I tried so many ways and patterns of installation with no difference in the outcome results whatsoever.
I took a moment to rethink my strat over this and googled other ways of flashing that firmware without using PC.
Found 2 possible solutions that I'm trying to make use of,first is Odin Mobile and the Other is FlashFire.
Since both require rooted devices,finding way to root bricked S4 wasn't a very pleasant experiance,since flashing SuperSU through CWM recovery didn't work,Odin managed to flash me nice Autoroot from Chainfire over the custom ROM I installed before,I found a problem even there since the I9505 autoroot wouldn't work,the custom firware had changed the phone model to I9507 that I downloaded the Autoroot for,was a confusing issue,but I managed to root it anyways.
Page I used for this purpose was Chainfire Autoroot database(sorry if I'm violating forum rules but I think this could be left here without further discussion about it).
After rebooting the device I downloaded Rootcheck software along with SuperSU and FlashFire which confirmed that it's fully unlocked/rooted.
Now I'm recharging my phone so I can later tonight go ahead and transfer firmware to it's SD card and try to flash it once again with FlashFire,last option I'm thinking of as of now if this wouldn't have any progress is to download Odin mobile and try another flash,I'm running out of ideas on this one.
Sorry for the long posts,but these get no respose so who cares.