So a few months back I couldn't wait to get the update and decided to flash the CRAP update , using the built in bootloader from Samsung and the zip file. Then when the new one to fix the issues with crap came along, I didn't get the OTA when it arrived to my region (UK) so I flashed it again, but as you can see, now they got mixed up a bit ... It's been like this for a while but I wanna fix it , anyone has any idea how to fix it ? I don't have a Windows computer atm to use Odin and when I try to use adb my phone isn't recognised anymore by my Mac (which it was before)... Feel like this will be quite messy ?
Related
I tried to flash a 6.1 rom to my shadow, but that was back in the day when my WMD did not work. When I tried to flash it, it got stuck in the bootloader mode. It took me awhile to research how to fix it, but eventually I got the re flash of the orignal t-mobile rom to work. Im wondering if I now that my windows media device software will work, if the flashing will? I'm a bit paranoid as I have no back up t-mobile phone and wonder if 6.1 is even worth it.
Also, the issue came because during the flash it said make sure it is connected to active sync, but I have WMD because I am on Vista.
What do you guys think? Should I be able to upgrade the shadow or should i just leave it alone
Hi guys
Just installed the new keies software and it said the froyo update was out for my handset (galaxy s) it downloads the update really slow (takes about 20 mins) and then then after it reaches 100% the phone disconnects from the PC and the andriod constuction logo appears on the phone, then shortly after i get an error message from kies telling me the upgrade didnt work and that an emergancy repair is needed..
Ive managed to recover the phone back to working order, but is there anyway i can get this update?
p.s phone was unlocked with the tool from these forums when we had it, if that makes a differance
There are many problems with kies while upgrading the firmware. When you get the error - did you read the error? At times it says something about a "rapi.dll" file missing or any other file, just download that file and it should work.
Best alternative is download the firmware from samfirmware (stock) and flash through odin, it hardly takes any time.
If you want your genuine network supplied firmware i would use the Kies Registry Patcher as this allows you to save the downloaded rom in case of problems .
Failing that as advised the stock rom but that is not what came with the phone its generic non network non branded .
http://forum.xda-developers.com/showthread.php?t=835628&highlight=Kies+Registry+Patcher
jje
xero01uk said:
Hi guys
Just installed the new keies software and it said the froyo update was out for my handset (galaxy s) it downloads the update really slow (takes about 20 mins) and then then after it reaches 100% the phone disconnects from the PC and the andriod constuction logo appears on the phone, then shortly after i get an error message from kies telling me the upgrade didnt work and that an emergancy repair is needed..
Ive managed to recover the phone back to working order, but is there anyway i can get this update?
p.s phone was unlocked with the tool from these forums when we had it, if that makes a differance
Click to expand...
Click to collapse
This is not a big deal, just click on emergency when it appears and kies will proceed, it might say that it will download the firmware again or might use the firmware that is already downloaded.
Can somebody point me on kernel for JVQ supporting Voodoo Color? Thanks.
I got the phone last week, network lock on, as I got it on T-Mobile, hooked it up to my pc, with the latest Kies, I had 2.3.3 and got a notification for an official update. It got stuck at 3% and was bricked afterwards (phone to pc connection broken image).
Anyways got it into download mode, flashed official firmware from sammobile forum(samfirmware is down) I9001XXKF8 with XEN SCS and AriesVE.ops Odin 4.43
It got stuck after 7/12 ext4 smth..
Then, decided to try 2.3.5 firmware I9001XXKPJ, as it's a Provider firmware, mind you everywhere I read that you shouldn't flash a network locked phone(exception is a provider firmware), but I did anyways , finished in 6mins.
Phone works great, now I have 2.3.5 with what I think is a huge rom with XX languages, including Macedonian(Balkan countries)
I don't have the slightest idea how I got it unlocked.. somewhere I read the network lock is in the rom in i9001, so you can try this. A local phone shop asked for 30eur, so I'm spending that money on booze tonight
I'll add this link to a post as well as I banged my head around quite a lot, before figuring it out/ how to recovery mode http://forum.xda-developers.com/showpost.php?p=17395735&postcount=19 thanks Riversource
can you please add some details?I did a flash with xxkpj but no luck my phone still locked. thanks...
mindless1 said:
I got the phone last week, network lock on, as I got it on T-Mobile, hooked it up to my pc, with the latest Kies, I had 2.3.3 and got a notification for an official update. It got stuck at 3% and was bricked afterwards (phone to pc connection broken image).
Anyways got it into download mode, flashed official firmware from sammobile forum(samfirmware is down) I9001XXKF8 with XEN SCS and AriesVE.ops Odin 4.43
It got stuck after 7/12 ext4 smth..
Then, decided to try 2.3.5 firmware I9001XXKPJ, as it's a Provider firmware, mind you everywhere I read that you shouldn't flash a network locked phone(exception is a provider firmware), but I did anyways , finished in 6mins.
Phone works great, now I have 2.3.5 with what I think is a huge rom with XX languages, including Macedonian(Balkan countries)
I don't have the slightest idea how I got it unlocked.. somewhere I read the network lock is in the rom in i9001, so you can try this. A local phone shop asked for 30eur, so I'm spending that money on booze tonight
I'll add this link to a post as well as I banged my head around quite a lot, before figuring it out/ how to recovery mode http://forum.xda-developers.com/showpost.php?p=17395735&postcount=19 thanks Riversource
Click to expand...
Click to collapse
and don't use Kies people.. Kies really sucks and bricked my phone
flashing a new rom with odin unlocks your phone as far as I know.. it's so easy for android
durkaya said:
can you please add some details?I did a flash with xxkpj but no luck my phone still locked. thanks...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1345671
or
http://broodplank.net/flashsamsungi9001.php
Hi, I tried but the phone is still locked... can you help giving other detalis?
broodplank1337 said:
and don't use Kies people.. Kies really sucks and bricked my phone
flashing a new rom with odin unlocks your phone as far as I know.. it's so easy for android
http://forum.xda-developers.com/showthread.php?t=1345671
or
http://broodplank.net/flashsamsungi9001.php
Click to expand...
Click to collapse
as far as I know flashing a rom (after flashing any kind of them from samobile and xda) does not remove the sim lock. there should be a different method rather than flashing or buying the code
After reading a lot of posts on i9001 I read there are two kinds of network locks, and I guess I was lucky enough to only have had the ROM based lock.
try different provider firmwares/non provider firmwares.. (although non provider firmwares are not suggested anywhere for locked phones, I haven't encountered anyone with bricked phones doing this)
Check your imei.
If it is 000000... ore not the same like the one under your batterie then your imei file got corrupted.
hi. i have a brand new phone s7 edge sm-935f to be more specific if this helps
got it in june. and now from a few days my phone started to freeze during gaming lets say that is a bigload or something and sometimes even when i wanna browse the gallery or even do simple stuff like calling someone..... i don`t know what happend...
this happend since i did the update on december? doesn`t matter the last big update.... i`m on forums 3 days now.... aand since this happend i knew that people are having problems like this... but still so i did the big damn update... and this happend
and now i`m trying to downgrade my phone... dld the firmware from sammobile? the site that everyone says... don`t know
i don`t know what to tell you more guys. i need some help i can`t do this on my one.
as i understand if i can enter in recoverymode blabla it`s not hard bricked? so that`s a very good thing so this means that this problem can be fixed.
i can load the phone by doing some forced resets.
i did hard factory reset.
i did try to flash stock firmware with odin... and kinda still nothing... after doing this i installed nfs no limits to test the phone and still the phone frooze and bam samsung logo we meet again.
i really don`t know what to do anymore.
does it has an importance if the phone came with " hungary firmware " and i dld the uk version ? maybe this could be the problem the language? don`t know
i need some help please i`m desperate.
thank you very much
p.s sorry for my bad english
edit1: didn`t root my phone didn`t try to install a custom thing on it, i started having this problems like 3-4-5 days ago after i did the last update in december can`t remember it.
edit2: dld the romanian (orange version ) gonna see if this works.... but after odin finished flashing the firmware i had to force restart the phone so it can boot... i quess this doesn`t work, i`m gonna dld the 2 versions of firmware of " hungary " and gonna try with those 2... will update when i`m done. in the meanwhile please tell me how i can fix this faster
edit3: i did manage to play a little bit of nfs no limits with this romanian (orange version ) but it frooze and restarted... i will try to install the hungary firmware and see then.
odin stock firmware, get TWRP, flash a custom rom, problem solved. If that dint solve it, you might have a hardware issued which means you are out of luck, need to send in the phone.
i really don`t want to loose my warranty by installing a costum rom on my phone....
as i know if i do that will **** up my waranty right?
any other suggestions?
You mentioned in initial post you would be trying certain stuff. What's the phone status now?
Try the APB1 of 2016.03.11 from SamMobile
phone status right now is still in the same status... tried to flash the 2 hungarian versions.. nothing.... even if it boots if i try to do something it goes in bootloop again... i`m trying to run an antutu benchmark....
some guy that works in a phone service place told me this: he things because of the update samsung rolled out the phone rams cpu is starting to break... because the update wasn`t tested enough,,,, don`t know what to say anymore. right now i don`t have time for the phone. i replaced it with other phone till next year then i`m gonna try to make it work again.
jonrayne i`m gonna try that firmware next yeah.
thanks
up. i think i have to change my phones motherboard.... because of the new update i think becuz of the bugs maybe it ****ed up my phones components i don`t know. if nothing works i will have to do this change. it will cost me 120-130$.... do you guys know any other option to try and fix my phone? i need to try everything before i will spend this money
Recruter said:
up. i think i have to change my phones motherboard.... because of the new update i think becuz of the bugs maybe it ****ed up my phones components i don`t know.
Click to expand...
Click to collapse
Hah, sitting in exactly the same boat as you after the last FW update, my thread is here:
http://forum.xda-developers.com/s7-edge/help/s7e-suddenly-bootlooping-dying-t3528827
up
any more suggestions?
or do i really have to go and change my mobo?
edit1: is there a way to test any part of the phone ? to see what part of the phone is fckd up? i tried to run an antutu benchamark when the phone worked a little bit but the phone went in bootloop at cpu test and ram test don`t know.
hey guys. i think i might have a fix for this sh1t
found on some forum i don`t know if it`s safe to post smt from another phone android related stuff if it`s safe i will paste here the post on that forum.
i found out that a guy with the same problems just like me and the same problems routine.... installed a nougat beta firmware and his phone worked after that. now i don`t have time to find and search a " valid " nougat beta firmware because i`m not home... can you guys please tell me if this is true or if somebody tried this option to fix this sh1t?
found out that many people have the same problem just like me after doing that update from samsung.
now my question is where can i find an " official " nougat update firmware to download. and try this because i don`t wanna go and pay 120$ to switch the mobo and then have the same problems.
saw a guy saying that there is one on sammobile but i don`t really have time right now to search for it. can smb tell where i can dowload one?
thanks
please smb reply
edit1: sorry for my bad english.
up
tried to update the nougat beta fw but nothing... it gets stuck at " erasing blue screen " think after odin finishes to upload the fw to the phone....
after that i flashed stock fw again... still gets stuck on erasing blue screen... or i get the exclamation mark.... tried to whipe cache etc... nothing
Recruter said:
up
tried to update the nougat beta fw but nothing... it gets stuck at " erasing blue screen " think after odin finishes to upload the fw to the phone....
after that i flashed stock fw again... still gets stuck on erasing blue screen... or i get the exclamation mark.... tried to whipe cache etc... nothing
Click to expand...
Click to collapse
Same problem here! What is your phone status now?
sound like a strategic move by samsung to force u replace motherboard again and again until u decided to give s8 a try. then u realise , **** it. get a cheaper phone with similar spec.
Some background... this phone was bought back in the day when Note 4 was about to be released. I have been the unique owner and I have treated the device with an abnormal amount of care and respect. Updates were about to come up but for my device... the bloody thing was getting said updates way too late (2-3 months later than everybody else such as UK or Poland). I grew tired of waiting so I did it, I force updated my own device using an image from sammobile.com with Android 4.4.2 using ODIN. It worked. The phone updated flawlessly in around 3 minutes it started the boot up sequence but the only difference was that the software inside was for UK not my European region which was Romania.
Fast forward... I rooted the device, did a lot of firmware tests (even after 5.0 came out, I still installed a ton of firmwares on it and they all functioned properly even if I was dealing with Android 6.0 or even 7.0) and the phone generally functioned very very well.
Now my **** up was that I wanted to reformat the phone to a 100% stock image (which I could do with ease at any given moment) and for some strange reason I ticked "Nand Erase All" and the reformat went trough... the software fully installed. My phone booted up and what do you know? I suddenly have 16 GB of storage instead of 32. I panic a little... I try to firmware upgrade a normal stock image for the romanian version of the Note 3. Stock Romanian based software for SM-N9005. Fails mid update 100% of the time me trying it well over 20 times. A bit of research, I end up realizing I ****ed up the phone seriously bad. So one guy saves me with a "repair firmware" which is named: N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware. I manage to flash the whole thing onto the phone and it works... but things are off. Apps are crashing at random, the phone is laggy at times... heck, there's a "android.media has stopped working" popping up every 2-3 minutes or even faster if I use internal storage. I can barely do anything... it also destorys the SD Card. As in, I gotta connect it to a micro SD reader to repair the micro SD from within Windows to be able to copy what's on it or even copy something on it... internal storage is zippy but again, it stops working once this android.media crashes. A few months pass, my girlfriend gives me a chance to repair the phone one hopeful last time. So I said "**** it" and I tried flashing again, the latest RO ROM for the phone. It fails mid way. I try restarting the phone and... it's bricked. It says that the software update failed and I need to connect it to Kies to update. Did just that and I find out Samsung doesn't allow the Note 3 to be emergency software updated anymore.....
I have the repair software, and another 2 different softwares. I have tried so many times to update the device using different cables and ports. Heck, I even installed Windows 7 to see if it works (until one guy told me I can install it trough VMWare and I will get the same exact result as if I were to have Windows 7 directly installed on the PC)... nothing works. My main error message is the one attached as a picture.
I tried every ODin, port and cable I could. I just... don't know what to do anymore. The phone is great but do I really have to buy a secondary display broken phone and transfer the mainboard from that phone to this one to have a "functioning" phone again or are there other options I missed out on?
Thanks for your message! I shall try to respond as soon as possible.
Search Nand Erase .
My guess is you need a service centre with a Rif box .
Sent from my SM-N930F using XDA-Developers Legacy app
I'm not sure but is it possible to flash the phone with a 32 GB pit file?
fogoticus said:
Some background... this phone was bought back in the day when Note 4 was about to be released. I have been the unique owner and I have treated the device with an abnormal amount of care and respect. Updates were about to come up but for my device... the bloody thing was getting said updates way too late (2-3 months later than everybody else such as UK or Poland). I grew tired of waiting so I did it, I force updated my own device using an image from sammobile.com with Android 4.4.2 using ODIN. It worked. The phone updated flawlessly in around 3 minutes it started the boot up sequence but the only difference was that the software inside was for UK not my European region which was Romania.
Fast forward... I rooted the device, did a lot of firmware tests (even after 5.0 came out, I still installed a ton of firmwares on it and they all functioned properly even if I was dealing with Android 6.0 or even 7.0) and the phone generally functioned very very well.
Now my **** up was that I wanted to reformat the phone to a 100% stock image (which I could do with ease at any given moment) and for some strange reason I ticked "Nand Erase All" and the reformat went trough... the software fully installed. My phone booted up and what do you know? I suddenly have 16 GB of storage instead of 32. I panic a little... I try to firmware upgrade a normal stock image for the romanian version of the Note 3. Stock Romanian based software for SM-N9005. Fails mid update 100% of the time me trying it well over 20 times. A bit of research, I end up realizing I ****ed up the phone seriously bad. So one guy saves me with a "repair firmware" which is named: N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware. I manage to flash the whole thing onto the phone and it works... but things are off. Apps are crashing at random, the phone is laggy at times... heck, there's a "android.media has stopped working" popping up every 2-3 minutes or even faster if I use internal storage. I can barely do anything... it also destorys the SD Card. As in, I gotta connect it to a micro SD reader to repair the micro SD from within Windows to be able to copy what's on it or even copy something on it... internal storage is zippy but again, it stops working once this android.media crashes. A few months pass, my girlfriend gives me a chance to repair the phone one hopeful last time. So I said "**** it" and I tried flashing again, the latest RO ROM for the phone. It fails mid way. I try restarting the phone and... it's bricked. It says that the software update failed and I need to connect it to Kies to update. Did just that and I find out Samsung doesn't allow the Note 3 to be emergency software updated anymore.....
I have the repair software, and another 2 different softwares. I have tried so many times to update the device using different cables and ports. Heck, I even installed Windows 7 to see if it works (until one guy told me I can install it trough VMWare and I will get the same exact result as if I were to have Windows 7 directly installed on the PC)... nothing works. My main error message is the one attached as a picture.
I tried every ODin, port and cable I could. I just... don't know what to do anymore. The phone is great but do I really have to buy a secondary display broken phone and transfer the mainboard from that phone to this one to have a "functioning" phone again or are there other options I missed out on?
Thanks for your message! I shall try to respond as soon as possible.
Click to expand...
Click to collapse
20 days later it happens to another guy (me)
help me save me from this mess, please, im desperate
neeharv said:
20 days later it happens to another guy (me)
help me save me from this mess, please, im desperate
Click to expand...
Click to collapse
I have tried myself. You have a chance of actually flashing it if you have the original cable that came with the phone. If not, the service is the only spot that can help.
I went to a shop and using an NS Pro box thr phone flashed problemlessly. Found out about my bad usb cable and here we are. The phone cost me 35 euros but it functions again.
fogoticus said:
I have tried myself. You have a chance of actually flashing it if you have the original cable that came with the phone. If not, the service is the only spot that can help.
I went to a shop and using an NS Pro box thr phone flashed problemlessly. Found out about my bad usb cable and here we are. The phone cost me but it functions again.
Click to expand...
Click to collapse
will this work: https://forum.xda-developers.com/showthread.php?t=2610757
it said it will fix partition corruption (like what happens when you do nand erase all without pit file)
neeharv said:
will this work: https://forum.xda-developers.com/showthread.php?t=2610757
Click to expand...
Click to collapse
Probably. Try it.
Here's the fix, it is the proper way to use "nand erase all" and to fix problems encountered while trying to use it:
https://forum.xda-developers.com/showthread.php?t=2610757
You can find the you the PIT files you need for it
https://www.sammobile.com/forum/showthread.php?t=30482
(make sure you download the one coresponding to the stock firmware just in case)
For other devices just google it.