[Q] How to Root? - Galaxy S I9000 General

So I've been looking all through the Samsung Galaxy S I9000 threads and can't find ANYTHING on rooting this phone. I've rooted several other phone models, including the S2 and I've never had so much trouble finding info on rooting a phone.
Could someone place a sticky on this?
I'm trying to root this Bell Canada Galaxy S I9000 on ver 2.33 and I can find plenty of instructions AFTER rooting but that doesn't help me if the phone can't even access the system
I just want to root this and install Cynaogen 7 on it. Help, please!
Silvercloak

Very useful thread, thanks a lot ^^.
-=Sent From Tapatalk - Galaxy S=-

OK here is a good starter guide.
The most important thing is getting a rooted kernel that matches your current Android version, wrong version will lead to bootloops and sadness. Once you've got a rooted kernel and CWM recovery you can backup and flash CM7 (twice, trust me).
CR Root thread has a long archive of kernels, should have one that matches your version

There are several methods existing in order to root your phone.
If you just need to root without changing your ROM, flash a kernel via Odin (kernel examples : Semaphore, CF-root, ...)

Why I'm rooting
Thanks everyone for your help.
TBH I'm rooting this for my brother's friend. He unplugged the phone in the middle of an update and now it won't make or recieve calls anymore... Soooo I'm guessing if I install a new ROM on it, it'll fix the whole issue... I could be wrong though, but it's worth a shot.
Silvercloak

He unplugged it during a Kies update? Check if the IMEI matches the sticker on the phone. If the IMEI is corrupted you might be best to send it back, a custom ROM will void any warranty.
If the IMEI is OK then rooting it and flashing a stock ROM might clean it up.
Best of luck

rax22 said:
He unplugged it during a Kies update? Check if the IMEI matches the sticker on the phone. If the IMEI is corrupted you might be best to send it back, a custom ROM will void any warranty.
If the IMEI is OK then rooting it and flashing a stock ROM might clean it up.
Best of luck
Click to expand...
Click to collapse
This is all hearsay from my brother, all he told me was this guy unplugged his phone in the middle of an update. If it was OTA, or Kies, I don't know. I'll check the IMEI, but I know his warranty is up crap creek, he tried to get it fixed under warranty and they wanted to charge him over 600 bucks.
I'm going to assume the IMEI is fine though, as he's getting data just fine without wifi being turned on, and he's connecting to Bell Canada, he's just not getting voice calls in or out.
Silvercloak

Flash a stock rom using g heimdall or Odin and go from there. Putting cm7 over it without calls working might make the issue worse. Flash stock first. Then install clockwork mod kernel, ie hardcores speedmod. Then flash cm7.no need to mess around rooting. U just need cwm.
Drew071
Sent from my Samsung apparently not capable, very capable ICS i9000!

Related

A few basic questions I am still confused about

Hi,
I am tasked with making a Friends Galaxy Apollo ( I5801) usable.
She bought it in Thailand and it is SIMlocked and currently running Eclair (2.1)
1) I first want to SIM Unlock it. I have seen multiple methods for this
This thread has a discussion :
http://forum.xda-developers.com/showthread.php?t=1339705
I will take a look at the youtube video first, but I am concerned that I will lose my IMEI. This seems to happen a lot. How do I back it up? I have seen instructions to backup the /efs folder and others that include a DD command. Which is the most reliable?
2) What is the easiest rooting method? Does SuperOneClick work? Do I even need to root to unlock only?
3) How do I then install a working 2.2? Is there such a thing as an Official 2.2 for the I5801? Otherwise, what is the best way to STABILITY?
4) Other Samsung phones offer packages ODIN or Heimdall ROMs that are pre-rooted in order to do a one operation (sometimes one-click) root/upgrade operation. Is there such a thing for the Apollo?
Thanks.
I tried running a search, and waaay too much confusing crap came back. I have owned several HTC, Mot and Samsung phones and am usually pretty good with this stuff...but I am just plain confused about this phone.
Any help would be appreciated
Caz
2) What is the easiest rooting method? Does SuperOneClick work?
Click to expand...
Click to collapse
SuperOneClick is the works fine for me
For 3) www.sammobile.com/showthread.php?t=12 Scroll down to asuan firmware. Im using dxjpc as it is the latet 2.2 version for asian countries such as Singapore, Malaysia etc other than India. Flash usin odin but do not flash the bootloader as there would be a possibility of a hardbrick.
Sent from my GT-I5801 using XDA App
Caz666 said:
Hi,
I am tasked with making a Friends Galaxy Apollo ( I5801) usable.
She bought it in Thailand and it is SIMlocked and currently running Eclair (2.1)
1) I first want to SIM Unlock it. I have seen multiple methods for this
This thread has a discussion :
http://forum.xda-developers.com/showthread.php?t=1339705
I will take a look at the youtube video first, but I am concerned that I will lose my IMEI. This seems to happen a lot. How do I back it up? I have seen instructions to backup the /efs folder and others that include a DD command. Which is the most reliable?
2) What is the easiest rooting method? Does SuperOneClick work? Do I even need to root to unlock only?
3) How do I then install a working 2.2? Is there such a thing as an Official 2.2 for the I5801? Otherwise, what is the best way to STABILITY?
4) Other Samsung phones offer packages ODIN or Heimdall ROMs that are pre-rooted in order to do a one operation (sometimes one-click) root/upgrade operation. Is there such a thing for the Apollo?
Click to expand...
Click to collapse
1.I backup the /efs folder and also manually copy the files for additional safety.
2.if you are on 2.1, z4root works great. get the apk from here, install and root. thats it. you need to root at least to backup the /efs folder.
3.go to samfirmware.com and search i5800. install any of the latest ROMs.
4.Some "stock" ROMs themselves are pre rooted. Dunno how. Install them if you want. (eg. JPM)
Ok...my phone is now rooted and SIMunlocked. Pretty easy once you get over the fear of corrupting your IMEI data.
Now I have another question:
I REALLY want to make sure I don't brick this phone, but I think I want to upgrade it to
2.2...sooooo:
How can I be sure where the phone is from and therefore which firmware to flash?
I *know* the phone was purchased in Thailand, but I can't find the firmware currently on the phone referenced anywhere for the Apollo.
The firmware baseband is DXJG2 and the build number is DXJH2. A quick google search yields only hits for a "Galaxy Beam" ??
Am I asking for trouble flashing this puppy? My friend probably does not care that much about ECLAIR vs. FROYO...I just think that FROYO is a lot more modern.
I am just afraid that I have a freakish phone in my hands and that it won't react in a "nice" way.
Any pointers?
If you do not flash the bootloader it is not possible to hardbrick the phone. Only a softbrick is possible and a reflash will solve the problem. Android firmwares have been shifted to sammobile.com and samfirmware does not provide them anymore if im not wrong. In froyo you will have a bit more space for appilcations and since your friend in from Thailand(in asia) i suggest u flash an asian firmware. Dxjpc is working find for me
Sent from my GT-I5801 using XDA App
u neednt be afraid of bricking the phone. and it is not necessary that u flash only asian frimwares. look around the forum to see which f/w works best for the majority of people and flash it. before flashing, make sure u remove boot and sbl files from the downloaded f/w. then u have 0% chance of hardbricking the phone.
cheers

[Q] New to note 3 & samsung

hi, i just got my note 3 n9005 international a couple of days ago & now its time to root...you can say i am a little new to samsung because the last device i used was an s3 & that was a long time ago.....
i dont have any warranty so knox isnt that big of a concern unless it may cause some sort of damage to the phone...so far i have read..its only for warranty purposes like the flash counter for s3.
i was wondering if anyone would be kind enough to point me to rooting & everything else i need to do to install custom roms including recovery...
i tried to read through the instructions of root de la vega but i find it too complicated...so i was thinking of doing cf auto root....
thank you
linx1287 said:
hi, i just got my note 3 n9005 international a couple of days ago & now its time to root...you can say i am a little new to samsung because the last device i used was an s3 & that was a long time ago.....
i dont have any warranty so knox isnt that big of a concern unless it may cause some sort of damage to the phone...so far i have read..its only for warranty purposes like the flash counter for s3.
i was wondering if anyone would be kind enough to point me to rooting & everything else i need to do to install custom roms including recovery...
i tried to read through the instructions of root de la vega but i find it too complicated...so i was thinking of doing cf auto root....
thank you
Click to expand...
Click to collapse
Samsung issue a 24month warranty on the Note 3 (maybe country specific?) -
If KNOX isn't an issue for you and you do not mind tripping it, the CF-Auto is the way to go.
RDLV is complicated if you're lazy, but it does preserve KNOX status depending on your bootloader version, put in #*1234# into your dial pad and post the results. We can know if you can use RDLV.
However, if you want to flash a Custom ROM, then you will need a custom recovery, which will trip your KNOX (can't be done without) - on the Android dev section and Orginal Android dev section (in this sub forum) are some Custom ROMs and the instructions on how to do so.
I have used X-Note, Crash and am currently using AllianceROM, but there are a few others.
Just be careful with custom kernels until you're pretty confident cause you can bootloop and ruin your EFS quite easily (it is fixable 99% of the time tho, script is on here also)
EDIT : All you need is here pretty much
thank you for your reply & these are the stats
AP: N9005XXUDMJ6
CP: N9005XXUDMJ4
CSC: N9005EVRDMJ4
also RDLV is way too complicated for me & besides i do plan to install a custom recovery so i think that defeats the point ....since you seem to have tripped knox, there hasnt been any kind of system issue i hope? this whole knox business gave me cold feet when i read about it...but so far as i can see..its just a flash counter.... could you tell me the tools i need to get started with? i already downloaded the usb drivers & odin 3.09..is there anything else i should need?
p.s. i was reading about "before or later MJ7 4" whatever...& i was wondering which of these was it refering to? ap? thank you
Once you trip the knox counter it makes no difference to the phone except not being able to use knox containers, and of course the warranty which you know. -- if you have the drivers and odin. Go grab cf-autoroot, run it thru odin and voila all done, similar for twrp or Cwm which ever you choose as your custom recovery (I use twrp) flash in odin and that's it all set.
Just make sure and I can't stress this enough, that you flash the right ROM for the N9005, and N900 doesn't work. - avoid doing restores with twrp for now also when you do a back up, some issues have arose recently and not sure of they're resolved or not yet.
Have fun man, just read everything about the ROM etc before you flash the odd one has FC's or NFC issues
Sent from my SM-N9005 using XDA Premium 4 mobile app
ok so backing up & restoring with recovery is, for the time being, a no no? yes i will make sure to see if the roms are made for n9005 only....i will probably start off with omega roms as they are the 1st choice i had when i started modding the s3 ....thank you soo much mate for all the info...1 last thing to clear up is i am reading on developers talking about MJ or MK or whatever it is....are they talking about the build number i find in Settings/About??
1 thing i couldnt get a proper answer for...is how does 1 know they have the international variant of the n9005 anyway? normally if a n9005 is under some sort of carrier...the carrier logo would flash when booting up right? because thats what happens on my brother's note 3 n9005...when he boots up his phone..it shows SFR logo before going to the samsung bootanimation.....but on mine there is no such thing...the simple note 3 n9005 text then samsung boot animation & then straight to system...that means mine is the unbranded 1 am i correct?
linx1287 said:
1 thing i couldnt get a proper answer for...is how does 1 know they have the international variant of the n9005 anyway? normally if a n9005 is under some sort of carrier...the carrier logo would flash when booting up right? because thats what happens on my brother's note 3 n9005...when he boots up his phone..it shows SFR logo before going to the samsung bootanimation.....but on mine there is no such thing...the simple note 3 n9005 text then samsung boot animation & then straight to system...that means mine is the unbranded 1 am i correct?
Click to expand...
Click to collapse
Yeah yours is unbranded, only thing that may/will apply to you is region lock (which unless you're leaving the country your purchased your phone in isn't an issue at the start.
Although I see your CSC is EVR (if I recall correctly that is EE UK's firmware on board)
EDIT: Yes MK/ML are build numbers
no i dont have region lock..THAT i checked...so can i go forwards with all the rooting recovery & custom roms? i did find a orange core services apk on my apps manager under ALL tab..... also what original firmware can i roll back to incase anything goes wrong? any specifics?
linx1287 said:
no i dont have region lock..THAT i checked...so can i go forwards with all the rooting recovery & custom roms? i did find a orange core services apk on my apps manager under ALL tab..... also what original firmware can i roll back to incase anything goes wrong? any specifics?
Click to expand...
Click to collapse
Yup can go forwards. EVR (EE aka Orange/T-Mobile) have unlocked phones so yeah you won't have region lock. Which means yours is unbranded but carrier unbranded.
As for firmware, it depends on what region you are using? And what country you are in (you could use BTU (also UK, unbranded but EVR is ok also) - You are **now I say this depending on your country/region** OK on MJ7 or MK2 IF you upgrade since you're using a UK based ROM/CSC your network obviously supports it. However battery life is better on lower than MJ6. So it's your choice really.
Most custom ROMs are MK2 or ML2 atm I think, - Not sure if any upgrade your bootloader to MJ7 (if they do, you can't roll back any lower currently)
i just need a stock firmware so as i have a fallback if anything goes wrong...nothing more really as i plan to stick with custom roms...will this do?
http://samsung-updates.com/details/17028/Galaxy_Note_3_Snapdragon/SM-N9005/EVR/N9005XXUDMJ6.html
i am in Bangladesh so i am pretty confident that there isnt any rom for my region
yea i was wondering about the battery life myself...i dont know what version my brother's note is but his battery lasts noticibly longer than mine does....i was even planning on swapping batteries as i thought it might be a cell related issue
linx1287 said:
i just need a stock firmware so as i have a fallback if anything goes wrong...nothing more really as i plan to stick with custom roms...will this do?
http://samsung-updates.com/details/17028/Galaxy_Note_3_Snapdragon/SM-N9005/EVR/N9005XXUDMJ6.html
i am in Bangladesh so i am pretty confident that there isnt any rom for my region
yea i was wondering about the battery life myself...i dont know what version my brother's note is but his battery lasts noticibly longer than mine does....i was even planning on swapping batteries as i thought it might be a cell related issue
Click to expand...
Click to collapse
As long as your bootloader doesn't go to MJ7 - that firmware is OK, If your bootloader updates ( I think it may with the custom ROM) you can't roll back to MJ6, you can go to MJ7 or MK2 via BTU which will work for you since EVR works.
the latest omega is ML2 so by that measure...i wont be able to roll back to MK2 either & the latest on this thread http://forum.xda-developers.com/showthread.php?t=2459328 is MK2
linx1287 said:
the latest omega is ML2 so by that measure...i wont be able to roll back to MK2 either & the latest on this thread http://forum.xda-developers.com/showthread.php?t=2459328 is MK2
Click to expand...
Click to collapse
You can drop back as far as MJ7 ( I have at least when I've returned to stock due to mess ups) my build is MK2 atm
the bootloader only goes to MJ7 (last I checked, If it has changed then mine still lets me roll to MJ7)
csc seems a very complicated mess...GOD when did the mod friendly samsung go this crazy? the s3 was the most fun thing to mod...now this feels more complicated then Sony's!! :'( since my csc is EVR...is it possible to put BTU? i saw someone post this but didnt get any replies... http://www.usofttech.com/t128991.html
OH CRAP you said this BTU already...sorry my bad.... just trying to absorb all this
1 last query & i think i can start....with my current MJ6 build...can i do the cf auto root? or do i need to be on a lower build? if i can...then i think i will start or should i wait for the MJ7 to finish downloading & root that with cf auto root? & mate...thank you... you helped clear a lot of the confusions stopping me from modding this...now i think i can start things with a bit of confidence...thank you.... MUCH appreciated
linx1287 said:
1 last query & i think i can start....with my current MJ6 build...can i do the cf auto root? or do i need to be on a lower build? if i can...then i think i will start or should i wait for the MJ7 to finish downloading & root that with cf auto root? & mate...thank you... you helped clear a lot of the confusions stopping me from modding this...now i think i can start things with a bit of confidence...thank you.... MUCH appreciated
Click to expand...
Click to collapse
You can CF root straight away, - since you're triggering KNOX anyway it won't affect you. Then on with custom recovery etc, just keep MJ7 as your stock back up on your PC just incase. and IF you run into any issues with EFS (bootloops/no signal/wifi/baseband etc) use THIS It has saved me and quite a few others.
EDIT: And no problem man, glad to help, we all start somewhere with new devices
mate....the odin inside the cf root is 1.85 & the 1 got from google is 3.09 which should i use? & is PDA & AP the same thing because they are diff in the 2 versions of odin
linx1287 said:
mate....the odin inside the cf root is 1.85 & the 1 got from google is 3.09 which should i use? & is PDA & AP the same thing because they are diff in the 2 versions of odin
Click to expand...
Click to collapse
I use 3.07 personally - and flash using PDA -- Use the one with CF root if you're unsure
the phone is rooted ahhh feels like home again ....mate you said earlier that restoring backups on twrp causes system issues....i was wondering if this is true for just twrp or ALL current recoveries in general? which recovery would you suggest? also i was wondering about that script you told me about...the 1 about soft brick.... that fixes corrupt efs due to flashes yes? if so, does that mean it doesnt require my backup of efs?
linx1287 said:
the phone is rooted ahhh feels like home again ....mate you said earlier that restoring backups on twrp causes system issues....i was wondering if this is true for just twrp or ALL current recoveries in general? which recovery would you suggest? also i was wondering about that script you told me about...the 1 about soft brick.... that fixes corrupt efs due to flashes yes? if so, does that mean it doesnt require my backup of efs?
Click to expand...
Click to collapse
TWRP has issues *sometimes* there's a few posts about it around, I personally have had no problems and use TWRP fine, but I mentioned it because what works for one, doesn't always for another.
As for EFS backup, keep it just incase -- IT seems Android can rebuild the EFS again with that fire script. -- It's handy though, gotten a few out of the crapper including myself

Slow Internet (3G/LTE) after 4.4.2 Update

Hello Guys
Well, let me get straight to the point. After my old rom (Revolution HD3) was draining my battery pretty fast, i decided to update to 4.4.2. Well, i downloaded the latest 4.4.2 for switzerland from sammobile.com. I flashed it and it somehow was all laggy and i had fc's the whole time. After some time i was able to use the phone anyway, but it was laggy. And the problem was that my 3G connection was EXTREMELY slow. I got connection time outs the whole time and wasnt able to download anything. Well, i thought it was the rom i flashed trough odin, so i downgraded to 4.2.2, my original rom, and updated trough KIES. The rom wasnt laggy anymore, but the 3g/4g was slow. I tried different Modems and Kernels. Nothing Helped. I then decided im going back to a custom rom but the flash failed. Then i tried another rom and it failed again. So i thought it may was cause i was on 4.4.2 and tried to flash a custom rom that was 4.2.2. I then tried to reflash my stock rom trough odin, and it FAILED. And that's how i bricked my phone. I can still enter Download Mode, but can't enter the recovery anymore. What do i do? I'd like to solve both problems.
Thanks guys
Btw: I've got an I9505
I assume you didn't wipe anything before you flashed stuff? Thats like rule number 1 to do.
You can try flashing a recovery true Odin.
Hej Guys
Um.. Just to let you guys know, it is possible to downgrad to 4.2.2 from 4.4.2. I just did it this morning and had sucess. But the problem with the really slow internet connction still is here, when im on a 4.4.2. And, it is the same with custom roms running 4.4.2. I tried different kernels and modems, nothing helped so far. As soon as i was back to 4.2.2 it had the usual connection speed. I called my provider and also called samsung itself. Obviously, they both told me to bring the phone back for garantuee. But well, as i know it's a software problem and not hardware, i wont do that. So can you guys help me? What should i do next? Actually im back on 4.2.2. Thanks
Edit: Oh, and ofc, i did everything like wiping/factory resetting, wipping preoload etc. It's not my first time flashing.
It's not possible to downgrade from 4.4.2 to 4.2.2! End of..
Sent from my GT-I9505 using xda premium
Are you serious dude? Im running 4.2.2 right now. What is your point?`I didnt even ask about it. I asked about a solution to the problem that i get slow 3G/4G on my I9505 when running 4.4.2. If you want a proof Pic about it running 4.2.2, i can give you one. But i dont really get what your point is.
Hang on hang on hang on, it is common knowledge that you cannot downgrade from official samsung 4.4.2 to official samsung 4.2.2 because in odin you will get failure at aboot.bin because you cannot downgrade bootloader.
How ever what would be really good is instead of just trying to say it then jumping out saying what's your point, we'll my friend the point is, it would be advantageous to everyone in the entire samsung galaxy s4 i9505 community if you can tell everyone how you did it.
My perspective is your doing a bit of flaming.
Pictures really won't prove a whole lot as anyone can do some build.prop edits and show different rom name and version.
Sent from my GT-I9505 using Tapatalk
Well, if it sounded like flame to you, it wasnt. I didnt create this thread to flame others. But i wasnt kidding saying that i downgraded to 4.2.2. Here how i did it:
Was running 4.4.2 (I9505XXUFNB9)
Flashed TWRP recovery.
Flashed custom Rom 4.2.2, which FAILED!
Flashed Official 4.2.2 trough odin, which FAILED!
Flashed TWRP recovery again, since it was somehow damaged from the flash before
Flashed Wanamlite 4.4.2
Flashed Custom Rom 4.2.2
Flashed Official 4.2.2 with succes.
Im not sure what part of those flashes were essential, but i have no reason for liying to you. What would be the perks if i did?
But now again BTT, Did anyone else have that problem of slow interenet connection? Or is it just me? Maybe some ideas?
Regarding slow Internet maybe it's your carrier with issues.
Maybe the downgrade back to 4.2.2 has created issues in its self. Have you checked your baseband matches bootloader and build?
A problem we have is we can't see the version of the 4G modem (non-hols) so that might be also an issue.
When you flashed back did you do a factory reset?
In regards to downgrade do you still have the Knox bootloader?
Sent from my GT-I9505 using Tapatalk
Well, i called my operator and the girl on the phone said that some people already called with the same issue, but its not on their side. It's a problem with the update samsung released. After the downgrade i had my Knox Bootloader and everything worked like it always did.
Yesterday Sammobile released a new ''rom'' for my country. Downloaded it, flashed it and it works great now. I have a bit of a fast battery Drain, but the problem with the slow internet seems to be fixed.
Again: 4.2.2 worked perfectly after downgrade. It had no issue, No FC nothing at all. Maybe i was lucky? No idea, but im happy my 4.4.2 works now
Thanks anyway for your help guys
Edit: Yeah, my bootloader matched both baseband and build.
Joku1981 said:
Mod Edit
Click to expand...
Click to collapse
If you had done your homework, you would know that in almost all cases Samsung repairs it even with Knox set to 0x1. They even publicly stated it in the Netherlands that they will repair your phone even with custom roms.
And you don't know the law in Switserland. Nor do I. So you can't say that in Switserland his rights are voided by flashing.
If Samsung doesn't give you the warranty, then you still have your consumer rights in the European Union (not that Switerland is in it). No flashing, modding or other chances decleine you your rights if it's not related to a hardware failure. In the countries that you and I live in, it will never void your rights if the damage is not related to flashing or modding.
So well, i think that in switzerland they actually WONT repair it if you flash it, but i aint sure about that, since i never had to send it to repair. But anyway, it was only a software problem on their side. They released another version for switzerland and it seemed to have fixed the problem. I have a bit more of a battery drain, but i actually think im just too used to some other custom roms. Anyways, thanks for the help guys

Galaxy S5 chinese clone ROOT problem

Hello. Recently I got Galaxy S5. Then after trying to root it I realized it's a chinese clone which haa complicated my life. I tried to root it and put in a wrong version of Clockworkmod. As a result, I fortunately haven't bricked the phone, but my bootloader is not working anymore. It doesn't load up. Only thing that works is the factory mode. Now the problem is - I want to get the phone to it's stock ROM and firmware, but because there is no way to access bootloader, nor download mode, I can't use Odin to do so. Is there any way I could flash the phone with a stock ROM and make the bootloader work again? The OS works fine, only thing that doesn't work is the bootloader. Thank you.
Samsung Galaxy S5 clone (G900S - South Korean), MT6589. Android version 4.4.2 Kit Kat, Kernel version 3.4.5, rooted.
You need to identify what model you have, obtain the stock firmware for that model and restore that. There are forums that concentrate on the clone models, use Google to find them, and they will go into more detail about your options.
Beware that many things on XDA will brick or worse a clone as the apps and advice here are not intended for a clone which is completely different under the hood.
.
fffft said:
You need to identify what model you have, obtain the stock firmware for that model and restore that. There are forums that concentrate on the clone models, use Google to find them, and they will go into more detail about your options.
Beware that many things on XDA will brick or worse a clone as the apps and advice here are not intended for a clone which is completely different under the hood.
.
Click to expand...
Click to collapse
Thank you for your reply. Well tge stock firmware is secondary for me. The problem is with the corrupt bootloader. I think it tries to load the CWM, but due to it's incompatibility it cannot. Is there any way to replace the bootloader only? Without the working bootloader, I can't do anything to fix it or to flash a custom ROM. I haven't find anything related to it. Or at least not yet.
Tom1597530 said:
Thank you for your reply. Well tge stock firmware is secondary for me. The problem is with the corrupt bootloader. I think it tries to load the CWM, but due to it's incompatibility it cannot. Is there any way to replace the bootloader only? Without the working bootloader, I can't do anything to fix it or to flash a custom ROM. I haven't find anything related to it. Or at least not yet.
Click to expand...
Click to collapse
Try to get your money back bro. If it's a chinese clone s5 God only knows what it's running. It's not a Samsung nor an s5 for that matter so the recovery and Odin won't work.
Sent from my SM-G900W8 using Xparent Cyan Tapatalk 2
Well, everything worked well until I tried to flash it. The reason was corrupt GPS. I found a way to fix the GPS but it required root and somehow I clashed it with incorrect CWM and the problem was born :/
Tom1597530 said:
Well, everything worked well until I tried to flash it. The reason was corrupt GPS. I found a way to fix the GPS but it required root and somehow I clashed it with incorrect CWM and the problem was born :/
Click to expand...
Click to collapse
Dude, get out of this forum or you`ll break your device permanently. You don`t have a Galaxy S5 and thuss neither a Qualcomm 801 cpu fow which these roms are build for. Find a forum somewhere for your device. Good luck
A normal (full) software image would include a bootloader. Separating a bootloader is much less common.
And as several people have already warned you.. quite a lot of the advice, procedures, firmware, et cetera on XDA will further damage your clone. Your clone may look like an S5 but it is very different internally. If you truly want a completely unusable phone, a literal paperweight, then continue.
Find another forum that has firmware and advice on how to program your specific clone.
Start here
.
Was the purchase of this clone made inside or outside of the USA?

How to return to original firmware from CM13

Hello everybody,
I have a Moto x play running CM 13. I followed the process listed somewhere in this forum and successfully installed cm 13.
Bad news is my laptop got stolen at uni. I had installed Motorola drivers and all that stuff in there, so now I'm wondering if I can go through this process without that laptop. I hope I can.
I only have the cellphone and I would like to return it to its original firmware so I can sell it.
Is there a safe way to do this without "bricking" my phone? I'm not very well versed in these processes and managed to install cm13 only because the procedure was very clear. I hope you guys can help me!
The original carrier is Iusacell (Mexico), although the cellphone itself is unlocked and takes any Sim.
thanks in advance!
gabrsmn said:
Hello everybody,
I have a Moto x play running CM 13. I followed the process listed somewhere in this forum and successfully installed cm 13.
Bad news is my laptop got stolen at uni. I had installed Motorola drivers and all that stuff in there, so now I'm wondering if I can go through this process without that laptop. I hope I can.
I only have the cellphone and I would like to return it to its original firmware so I can sell it.
Is there a safe way to do this without "bricking" my phone? I'm not very well versed in these processes and managed to install cm13 only because the procedure was very clear. I hope you guys can help me!
The original carrier is Iusacell (Mexico), although the cellphone itself is unlocked and takes any Sim.
thanks in advance!
Click to expand...
Click to collapse
to flash original firmware without PC you can use Chainfire's Flashfirehttp://forum.xda-developers.com/general/paid-software/flashfire-t3075433, however - it's still kinda experimental, needs some knowlege, and I'm not really sure if it supports our device. Reading through its thread may give you some clues. This will not revert your phone to out-of-the-box condition - that would take relocking your bootloader and PC is needed to do so (warranty will be still voided anyway). So maybe just try flashing some stock ROM in TWRP. The procedure will be the same as flashing CM.
minimale_ldz said:
to flash original firmware without PC you can use Chainfire's Flashfirehttp://forum.xda-developers.com/general/paid-software/flashfire-t3075433, however - it's still kinda experimental, needs some knowlege, and I'm not really sure if it supports our device. Reading through its thread may give you some clues. This will not revert your phone to out-of-the-box condition - that would take relocking your bootloader and PC is needed to do so (warranty will be still voided anyway). So maybe just try flashing some stock ROM in TWRP. The procedure will be the same as flashing CM.
Click to expand...
Click to collapse
I feel more comfortable with the second option. I found this github with MXP ROMs for my country and carrier: https://github.com/motoxplay/stock
I honestly can't remember if I had it at the beginning with Android 5 or 6. What happens if I flash Android 6 and it originally was 5? I suppose I should make a backup "nandroid" first.
BTW, can the bootloader be locked again via a new PC?
gabrsmn said:
I feel more comfortable with the second option. I found this github with MXP ROMs for my country and carrier: https://github.com/motoxplay/stock
I honestly can't remember if I had it at the beginning with Android 5 or 6. What happens if I flash Android 6 and it originally was 5? I suppose I should make a backup "nandroid" first.
BTW, can the bootloader be locked again via a new PC?
Click to expand...
Click to collapse
Flashing newer firmware won't break anything, it's a normal update. Worse thing would be if you tried to flash Lollipop over Marshmallow.
Making backup is always a good idea, do mind however, that flashing full stock firmware means overwriting your TWRP with stock recovery. Also, be aware the files you linked are actually firmware and not TWRP flashable zips.
And yes, you should be able to relock bootloader with original firmware.

Categories

Resources