Related
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.
Hi, Ive been stuck with this problem for about 3 days now. I have tried EVERYTHING possible and now I'm getting impatient. I've tried every advice on almost every forum or blog. But still cant seem to resolve the issue.
I was running echoe rom 5.1 and tried to flash cm 12 on it through philz recovery. It failed the first time but I was able to access philz. Then I tried to flash stock firmware through Odin and I dont know what happened, it failed and I got an error "Firmware upgrade failed and try recovering through kies...."
I tried kies, my device wasnt able to connect( I tried all the ports and cables I have) and even reinstalled kies just to check. No luck.
Then I killed all the kies processes and tried to flash a stock firmware, this time odin gave an error "PIT partition not found".
I have tried multiple PIT files for i9505 16gb with multiple stock roms on multiple versions of Odin (1.85, 3.07, 3.09, 3.10) some forums asked to tick 're-partition', some said to untick 'auto reboot', Ive tried all of them, still fails.
I can only access download mode on my phone right now, not philz recovery and neither stock android recovery.
my write protection is also enabled, I think this is the core issue, once the protection is disabled, PIT can re partition and flash a stock, and once a stock is flashed, I can flash any recovery and flash any custom ROM through that.
I have been flashing and rooting androids since the last 2 years and never encountered such a problem. Always found some solution online.
I would really appreciate if you guys could help with the problem. Thanks
XDA Visitor said:
Hi, Ive been stuck with this problem for about 3 days now. I have tried EVERYTHING possible and now I'm getting impatient. I've tried every advice on almost every forum or blog. But still cant seem to resolve the issue.
I was running echoe rom 5.1 and tried to flash cm 12 on it through philz recovery. It failed the first time but I was able to access philz. Then I tried to flash stock firmware through Odin and I dont know what happened, it failed and I got an error "Firmware upgrade failed and try recovering through kies...."
I tried kies, my device wasnt able to connect( I tried all the ports and cables I have) and even reinstalled kies just to check. No luck.
Then I killed all the kies processes and tried to flash a stock firmware, this time odin gave an error "PIT partition not found".
I have tried multiple PIT files for i9505 16gb with multiple stock roms on multiple versions of Odin (1.85, 3.07, 3.09, 3.10) some forums asked to tick 're-partition', some said to untick 'auto reboot', Ive tried all of them, still fails.
I can only access download mode on my phone right now, not philz recovery and neither stock android recovery.
my write protection is also enabled, I think this is the core issue, once the protection is disabled, PIT can re partition and flash a stock, and once a stock is flashed, I can flash any recovery and flash any custom ROM through that.
I have been flashing and rooting androids since the last 2 years and never encountered such a problem. Always found some solution online.
I would really appreciate if you guys could help with the problem. Thanks
Click to expand...
Click to collapse
Hello there! Welcome to XDA!
First register an XDA account (so you can ask in the proper forum)
then, please visit the following forum... (see below)
try asking here: (You will have a much better chance of getting help there)
Galaxy S4 Q&A, Help & Troubleshooting
or
Galaxy S4 Main Section
Good Luck!
thanks mate!
Registered and posted here
http://forum.xda-developers.com/galaxy-s4/help/s4-lte-i9505-soft-bricked-t3199387
Thread closed
Hey, I made this account to ask this question I'm pretty desperate,
My phone was acting up (overheating, WiFi didn't work half the time), so I decided to reflash my cyanogenmod rom, me being the idoit that I am I didn't do a backup before formatting my phone, I tried to flash the zip file but twrp kept crashing, so the next logical step was to use ADB sideload to flash the rom, that didn't work as well as I expected either the install kept failing at 88% as I was rebooting the phone for yet another attempt, recovery wouldn't start at all, at that point I was pretty frustrated, so I decided to flash the phone back to stock touchwiz, I downloaded the stock firmware and attempted to flash it with odin, low and behold that didn't work either (auth error), I tried again multiple times with firmware files downloaded from different sites but those didn't work either, I also tried flashing stock PIT files to no avail.
So here I am at 5 am with a bricked phone and 8gb of tar files on my desktop any help at all would be greatly appreciated.
Thanks in advance.
i know this thread is old, but can you get to download mode still?
What's the model and type of phone is this ?
hey all
I did a basic root on my samsung galaxy s6 a few days ago. just installed superSu and gave me root access. after that I installed TWRP which I then used to try and install the xposed framework. From then on my phone is stuck on the samsung screen saying kernel is not seandroid enforcing. I downloaded the stock rom for my phone (sm-g920F on 6.01) and attempted to flash it via odin 3.07 but it always failed after the sboot.
i have searched to try and find a solution but nothing I can find will work. can anyone help?
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
vickstew2000 said:
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
Click to expand...
Click to collapse
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Rosli59564 said:
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Click to expand...
Click to collapse
i had tried several times to connect to smart switch but it would not recognise my phone. after a lot of faffing about I finally managed to get it to do an emergency recovery and all seems well so far. it even restored my imei number so thanks for that suggestion Rosli. much appreciated xx
When u install xposed did u ude the special wanam version of the framework
Would say whipe cashe and wait a little while for stock roms like 40 minutes after first time install
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.