Hi guys.I am new to forum so i didn't know where to open this thread.Also i have checked internet for a solution but never seen a dumb thing like this before in my life.So even google search engine couldn't help me about that.
One of my friend has purchased a device from dubai.it is an original device of i9505 with snapdragon 600 processor.I am personally using an i9500 octa version btw.my friend told me to check his device after he had problems with gsm service+wifi for 3g doesn't connect(or connect and drops fast) so i went to check his device.i have used some system info tools and benchmark softwares to identify the device is ok.but NO IT WAS NOT OK.all of the system info tools says that the device is i9500 but it has snapdragon processor.some idiot somehow managed to write i9500 rom to i9505 and it is working with problems.i have checked camera both ok frontal and rear.and other device properties working good as well.i should expect that it should even fail to boot but somehow working with great deal of no phone service+3g problem(phone service sometimes work i really don't know how it works or how it fails).
So i decided to make things right.Which is put the right original galaxy s4 i9505 rom to that device.i have checked sammobile and found germany version of kitkat.
general info : device is rooted.it says it has Wanamlite rom 4.2.2.
My Try list:
1)downloaded odin 3.09 and followed the instructions.(used the official rom given from sammobile.)and put the mobile to download mode(i couldn't do it with volume down+home+power button cos it is not working)but i thought i was lucky cos that custom rom had an option when i push the power button/restart/ it says there is a download menu so i choose that to put the device to download mod.after that i was hoping odin will do the job.but it FAILED DUE TO WRITE PROTECTION ENABLED on device.
2)i tried to setup cwm recovery to device(which i figured out later it was already on device but i didn't know it was there).downloaded rom manager from playstore.and i thought it would work.rom managers says i had 2 recovery programs or rom managers on the phone 1 is cwm and other is teamwin recovery.also rom manager asks me to update or upgrade cwm but it does't recognise the device cos it is i9505 with i9500 rom and rom manager couldn't identify the device as it should be.so cwm update doesn't work.also i couldn't get to the user interface of cwm which is already on the device no matter what i do.also i know old version of cwm will not make it happen for what i need to do if i was able to get in the user interface as well.i think teamwin is blocking cwm.
so on rom manager i decided to use the team win cos there is no other option for me there which puts the phone after a restart to recovery mod,the user interface works ok there but teamwin also FAILED TO WRITE THE ROM(i think it is an old version too)i couldn't say the exact version of cwm cos the device is not with me and i forget the version but team win i asked to my friend just yet and he said TWRP 2.6.00 is on it.
3)CWM i can't even get to user interface,i really don't know how to with team win there.So yeah i couldn't even give a try.
4)I am stuck.and i don't know what to do.
general user profile about me: i have a general understanding of computers,but i haven't written any rom to galaxy s4 before yet i found myself in a situation i can't handle.someone screwed up an i9505 with a i9500 rom.
ANY HELP FROM ANYONE will be very appriciated.
i have managed to upgrade tw recovery with flashify to final version but in odin still write protection is enabled in the download mod.so odin again failed.btw after upgrading tw with flashify i lost my ability to get into operating system.i just have tw recovery on the screen atm.
the rom file i tried is this one I9505XXUFNB8_I9505VFGFNB3_I9505XXUFNB8_HOME.tar.md5 which i have downloaded from sammobile.
I9505XXUFNB8_I9505VFGFNB3_VOD.zip vodafone version it says for uk.
now i have a screen of tw recovery when the device opens.strange thing is i have 2 versions of tw recovery installed at the same time.when i press volume up+home+power tw version 2.6.00 loads.
or when i open the device with only power button tw recovery 2.7 loads.no operating system yet.
i tried I9505XXUFNB8_I9505VFGFNB3_VOD.zip with tw. it gave me an error of md5 not found and failed.
what now?
anybody around there to help?
another note : i don't know if it is important or not but it says the product name is sghi337.checked google it says at-t network.is this a useful information or what to identify the problem?
all i want is any rom to make the device work again with fully functioning.
after having twrp 2.7 i tried some roms had md5 error,so after a search i wanted to try wanamlite rom wanamlite-xxufnbe-v2-4-android-kitkat-4-4-2-xposed.after installing wanamlite rom it has asked me to reboot.so i did reboot it.it had adam kernel 2.1 version.
i was expecting the device will reboot but thanks to at&t for making odin useless + making twrp useless as well.it had a message on the screen and it was written ''samsung custom'' with a locker logo open.i thought i have to wait for the first boot and be patient and after waiting about half an hour still nothing.(on the left up of the screen written red : kernel)i checked more than maybe hundreds of threads to find an answer about at&t sghi337 galaxy s4 and some ppl say i have to change the kernel.and some say i have to change it to at&t kernel i searched again for an at&t kernel i found a file name KT-SGS4-TW-JB-ATT-06-06-2013.zip.then i gave a try to that.but suddenly i realized i have lost the ability of booting to twrp 2.7.all i have left with is twrp 2.6.00 when i press volume up+home.still lucky to have it.i used that kernel reboot and got a message on the screen ''system software not authorized by at&t''.then i started searching again ppl say about loki doki.downloaded the file and flashed it on at&t kernel this time it showed samsung logo appeared and the boot sound which you know all of us familiar with and samsung led was blue.the led was like it is a pounding heart coming on and off.this should be the first load of the rom i thought again and waited and got no result.it didn't load again.failed failed and failed many times.
i also tried this file named MDOB-KERNEL2STOCK-LIB.zip.flashed it no result again.failed.this result was another strange thing.it was showing samsung custom logo boot it with sound and then turn the device off after 10 seconds.and repeats the process.reboots sounds and reboots again and again.
questions :
1) do i have a bootloader locked device?since i can't use odin to flash anything.(odin version 3.09) and if i have what can i do to fix it?
2)since i only have twrp 2.6.00 how can i upgrade it to 2.7 back with twrp.i mean twrp update using twrp.
3)with twrp 2.6.00 i used wanamlite rom kitkat version.and it says it has flashed it.but can it flash roms succesfully enough like 4.4.2?if it says it flashed everything is ok? or it misses some important features to make the rom work.what is the maximum capability of twrp 2.6.00.Do i have to try roms like 4.2.2?
4)about kernels with at&t i337 galaxy s4 what can i do?what should be the reason preventing the rom load successfully?if i have access to twrp does it mean i don't have to mess with bootloader cos i have already passed that step and got an interface for loading roms?i mean everything is ok with bootloader if i have twrp installed user interface? and after flashing a rom do i have to use the specific kernel coming with the rom or can i use any kernel for the device like stock kernels(doen't allow me to load) with loki doki or some kernels with loki doki?
i am so helpless,please enlighten me with your knowledge.any moderators or any developers can answer me?or help me?
stuck in the middle of nowhere.please help.
Getting some progress at the end!!!
Since twrp 2.6.00 is the only option i have,or i can say ''was the only option i had'' i knew i had to get an android user interface for upgrading my recovery.after a bit more search i found slimroms for android version 4.2.2 just to make the device run,and it is already loki patched.so yeah that rom flashed as lightspeed and loaded extremely fast!that worked!!! i have downloaded aptoide market since it was lacking google apps.and downloaded flashify to upgrade the version of twrp to 2.7.01.from now on i believe i can find my way to whichever kitkat rom that is loki patched would work with this recovery support.
THANKS TO SLIMROMS for making downloadable and flashable small sized roms and tnx for the guy whoever found the loki way to make it possible.Also great thanks to TWRP team!!!
PLEASE NOTE THAT : Why did i write this after no reply or no help or no messages to this thread?Because i have figured out my way reading,trying and hard pushing after failing a lot but i found my way with xda developers threads out there even no one ever replied for help.I mean thanks anyway :cyclops:
When in doubt, flash to stock ROM and proceed from there.
you mean to tell me u cant enter download mode? ask someone to press the 3 buttons together to enter it and flash the firmware specified for that S4.
Related
Hi all. Tried my first root + custom rom installation and i messed up the device..
i had the newest KIES firmware update (phone XXBMA5) and (XXBMA6) and i rooted the device with odin (3.07). That went OK.
Then i installed the CWM recovery with odin and that was OK too.
Then i downloaded the latest Omega Rom (i missread that it supports N8020) and followed the installation instructions to the point where it started installing Omega V2.0 from SDCARD and then it asked me to select device from a list that included only (N8000,N8010,N8013)..
So the situation now is that i have working odin, working CWM and backup of the EFS (img+tar) but no working recovery. i live in Finland and the device is Sonera locked i think, so the stock roms (international) do not work i guess.
KIES has a backup of my Note but i can't even get to a point where KIES discovers the device.
So basically i think i need a working ROM for my model (Note 10.1 4G N8020), or can i recover the original samsung software somehow ?
Any advices ?
Removed
Just a thought, but can't you reflash CWM or the stock recovery?
If you didn't install the rom why do you need to re-install anything. Just powering down and powering up should have left you as was....
Alajarvi84 said:
working CWM .......... but no working recovery.
Click to expand...
Click to collapse
Maybe i'm missing something but isn't CWM your custom recovery?
It doesn't sound like you've actually installed any rom yet.The Omega installer doesn't actually install anything until a few steps after the one you mentioned about the model type.
I'm with ultramag69 on this one. You should still be on a stock rom unless you already wiped your original rom.
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
What is truly amazing is that i did not brick the device tough..
switch from cwm to stock
Alajarvi84 said:
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
Click to expand...
Click to collapse
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
jjndimp said:
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
Click to expand...
Click to collapse
I was not easy, i just tried the download mode over and over again with KIES open in windows and somehow it finally did find my device and offered a emergency restore. That is it, and the device was restored to default "original state".
OMG.... one would think after nearly having bricked your device you would either A) stop messing around with it or, B) read and learn more about what you're wanting to achieve and THEN maybe trying something with the ABSOLUTE certainty that a backup to restore is available to you in case of any mishap!
Moral of story :
Don't do anything until you are absolutely sure you have read EVERYTHING about what you are going to do.
For others wanting to mess with their devices, take heed! You may not be as lucky as OP (or troller) whichever is applicable.
There comes a certain point, that when crossed one does not care what happens to the device at hand. After fighting with my n8020 for several days in a row i couldn't care less, and like said before i dont have the level of enhusiasm like i had when i was younger. Of course i know now what went wrong.. But seriously, these are just overpriced toys, so it's not a matter of life and death.
Sent from my GT-N8020 using XDA Premium HD app
Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.
As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Fleacore210 said:
As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Click to expand...
Click to collapse
Go to sammobile and flash the latest stock firmware for your device .
Newyork! said:
Go to sammobile and flash the latest stock firmware for your device .
Click to expand...
Click to collapse
Well after a short research I found a ROM called Resurrection Remix, loaded with 5.0.2 (or Lollipop) however now everything is force closing and I barely got my laptop to see it as MTP again after installing a new Binary (glad that did that trick for that) but I cant get it to boot into CWM Recovery bc I cant access the app the only thing it will let me do right now is change the Binary.
How can I fix this issue?
Edit: Okay so I got that solved with doing a factory reset twice, booted in CWM, loaded up the GApps. Now just wondering if there is away to make it not seen with phone options like the dialer or msgs as its jus a plan old tablet, doesnt take a sim card and has no carrier. I do have the source code but I am not tweaking that til I get a better understanding of it.
After a lot of research and tries (amazingly without bricking) I am now running an even newer version of a CM 13 Marshmellow
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.