Related
Ok, I want to leave a message on here for future noobs like me with a Galaxy S
i9000 but it might work for others too.
My issue when flashing custom roms is that I have not been able to access my galaxy from my computer via usb since literally day 1 (when it did work once).
I spent a week trying to connect to Kies on multiple computers (vista and Windows 7). Tried via Android SDK, even tried hiemdall. I almost tried in ubuntu also but I never did get that working as I really don't know linux well enough. I've now given up...
So then I saw that you can do flashing all on the phone with the clockwork mod. With clockwork, my first rom flashed, well, like clockwork! But then I had some issues with lag and hang ups and reception and I decided to switch to another rom (seearms jl2 based rom - good stuff so far).
However this rom install went sideways... It said that it had installed ok but on reboot it stalled on the Galaxy I9000 screen and froze. Luckily I could still use the 3 button recovery to boot to clockworks but the hitch was that I HAD NO OTHER ROM to flash back to.
I had done a backup through clockworks but when I tried to restore it said the systems.img file was missing so it skipped it and the end result was the same freeze.
Normally everone says to reflash at this point with odin but that was not an option for me. So this is where I got lucky. The SeeARMs rom included Steam recovery module (though I thought it was the stock 3 button recovery menu for a while - I was panicking a little). I highly recommend seeing if you can get steam because it allows access to the External SD card for flashing which can be a lifesaver. Ahh, finally I could get the old rom on that, reflash it and go one with my life. My theory being that at least the issues would be aligned with the this rom and it worked.
So the lessons I learned:
1) Always have your new rom and your old rom on the interanal SD card in case of issues.
2) check your nandroid backup - even try testing it? - they don't always work perfectly with every device.
3)I highly recommend finding out if Steam or similar will work if you cannot access the USB connection and load things on when things go wrong.
Some tips I saw that also worked for me
1) flash a new kernel before you flash a new whole rom.
2) if things go sideways, try redownloading or retransferring the file to make sure there were no errors.
I did both and then reflashed (with my old rom Voodoo Doctor, SeeArms Rom and Darky's 8.1 rom on the card just to have options) and all was good!
PS: the steam recovery knocked off the first letter of the file when executing for some reason so I had to make 2 copy's of each rom I wanted access to ie Darkysrom.zip and arkysrom.zip just look for that error when you are doing this.
Good post - hopefully it'll help someone out who's stuck.
Hopefully
I'd like to stick some of that in on the thread for your rom but I need put another 7 half relevent messages out there before I am worthy... I understand the rule but I'd rather only post where it is meaningful...
GF
Greetings all.
Firstly, thanks for such a great repository of info. I have successfully managed to root my phone using Chainfire's method. I'm supremely happy to have even accomplished that.
I'm not a tech noob, but I'm quite new to Androids.
The feeling of frustration at trying to learn new terms and make sense out of all this information is HUGE. I have seen various "noob" entitled threads, as well as threads (Like ChainFire's) that make it somewhat easier. However, there seems to be so many threads to look through, and different info/terms that at this point trying to add a battery percentage mod to the status bar (which I'm sure is an easy easy thing to some of you) has become quite the gargantuan task for me.
---to that topic i'm having trouble understanding what it means when people say "flash using CWM". I understand "flash" (i think) and i know what CWM is, but have no idea what steps to take to "flash the necessary apk" files.
Do i use CWM? I've seen mention of using a root explorer or just adding the files overtop.
Then I've read "backup first". Yes, i know i want to do that. I have Titanium Backup on my device. And I've backed it up> but then i read that i should be using Nandroid. Where the hell do i get that? lolz. I mean I've searched for it and found threads, but from HTC section. Is it even compatible? No D/L links...
arrrrgggggg!!!
I did find some resources from Villain rom. So at least I found some term definitions.
Speaking of Roms...
If I have KF3 on my phone, and i wanted to put Villain Rom v.2 on it, would i need to install KF2? Or is it recommended to put on KG1? Am I flashing that like I flashed the kernels when rooting (via odin)?
------------------------------------
Well if you made it through that - thanks. My head feels like it's going to explode. Too much info, too fast. I feel like I've had a ton of info my brain really doesn't comprehend. What was that movie...Johnny Mnemonic?
I wish we had a Rooting Rom'ing Guide for Noobs. One that explained what terms meant along with the instructions. Maybe a screenshot or two.
benivolent said:
Greetings all.
Firstly, thanks for such a great repository of info. I have successfully managed to root my phone using Chainfire's method. I'm supremely happy to have even accomplished that.
I'm not a tech noob, but I'm quite new to Androids.
The feeling of frustration at trying to learn new terms and make sense out of all this information is HUGE. I have seen various "noob" entitled threads, as well as threads (Like ChainFire's) that make it somewhat easier. However, there seems to be so many threads to look through, and different info/terms that at this point trying to add a battery percentage mod to the status bar (which I'm sure is an easy easy thing to some of you) has become quite the gargantuan task for me.
---to that topic i'm having trouble understanding what it means when people say "flash using CWM". I understand "flash" (i think) and i know what CWM is, but have no idea what steps to take to "flash the necessary apk" files.
Do i use CWM? I've seen mention of using a root explorer or just adding the files overtop. CWM comes with Chain Fires Rooted Kernel. If you have rooted your phone using Chaninfiire Kernel you should have an app called CWM. you need to put the apk in your internal storage using PC, then open CWM, theer is an option to install apk. select that and browse to the file.. all done
Then I've read "backup first". Yes, i know i want to do that. I have Titanium Backup on my device. And I've backed it up> but then i read that i should be using Nandroid. Where the hell do i get that? lolz. I mean I've searched for it and found threads, but from HTC section. Is it even compatible? No D/L links...
it means backing up ur phone using CWM.. open CWM and theer is a backup option select that or just boot to recovery power off then Power+home key+ volume Up) and select backup from there
arrrrgggggg!!!
I did find some resources from Villain rom. So at least I found some term definitions.
Speaking of Roms...
If I have KF3 on my phone, and i wanted to put Villain Rom v.2 on it, would i need to install KF2? Or is it recommended to put on KG1? Am I flashing that like I flashed the kernels when rooting (via odin)?
no ur not required to put KF2 first. flash the villain rom using CWM (install zip from sd card)
------------------------------------
Well if you made it through that - thanks. My head feels like it's going to explode. Too much info, too fast. I feel like I've had a ton of info my brain really doesn't comprehend. What was that movie...Johnny Mnemonic?
I wish we had a Rooting Rom'ing Guide for Noobs. One that explained what terms meant along with the instructions. Maybe a screenshot or two.
Click to expand...
Click to collapse
hope that helps
Thanks indeed!
I did have a problem with the CWM, I did pretty much exactly as you mentioned - prior to me making this thread - and I used cwm to browse to the location with the apk on my sd card. installed... nothing happened.
re: cwm and back up - again, did as you had mentioned, but when i go into cwm and press "backup" it give me option to name the file, and then resets into recovery mode (i think - as i've used the buttons method to get to the same screen) but there is no "back up" option listed. also there is some csc error message. see picture.
re: villain rom. so to confirm, I do not have to change from kf3 to another kernel to install VR2.0?
Have to agree, especially for people coming form the world of Ilockedinsideaboxfullofnothingtochangeordophone
What are the benefits of flashing a custom rom?
PM sent.
Sent from my GT-I9100 using XDA Premium App
benivolent said:
Thanks indeed!
I did have a problem with the CWM, I did pretty much exactly as you mentioned - prior to me making this thread - and I used cwm to browse to the location with the apk on my sd card. installed... nothing happened.
re: cwm and back up - again, did as you had mentioned, but when i go into cwm and press "backup" it give me option to name the file, and then resets into recovery mode (i think - as i've used the buttons method to get to the same screen) but there is no "back up" option listed. also there is some csc error message. see picture.
re: villain rom. so to confirm, I do not have to change from kf3 to another kernel to install VR2.0?
Click to expand...
Click to collapse
according to that pic..u dont have cwm installed properly.. that recovery screen is from the default recovery which comes from the phone..ur not flashing your rooted kernel properly.. ur recovery screen should be orange in colour and it will be stated there clockwork mod recovery
and you can safely ignore that csc error..
THUDUK said:
Have to agree, especially for people coming form the world of Ilockedinsideaboxfullofnothingtochangeordophone
What are the benefits of flashing a custom rom?
Click to expand...
Click to collapse
You mean like my Blackberry? heh. for sure.
I'm hoping with the Custom Rom it's got less bloatware, better battery life.
xinfinityoO said:
according to that pic..u dont have cwm installed properly.. that recovery screen is from the default recovery which comes from the phone..ur not flashing your rooted kernel properly.. ur recovery screen should be orange in colour and it will be stated there clockwork mod recovery
and you can safely ignore that csc error..
Click to expand...
Click to collapse
I never installed cwm as a separate action. Only used the "cwm" that came with chainfire's stuff. I've seen the orange colour you speak of in an faq I've found, but I'm not sure how to remedy this....
I am using the system as described for flashing kernels in Chainfire's thread.
1. debug mode on phone
2. phone into download mode (three buttons)
3. start Odin
4. plug phone into usb
5. browse to zip/tar file of unsecured
6. phone reboots
7. root phone
8. install secured kernel to sd card
9. use cwm to flash that kernel. (which did so successfully i believe)
Is there another step I should have done to install CWM? will reflashing the kernel via odin fix this?
thanks!
benivolent said:
I never installed cwm as a separate action. Only used the "cwm" that came with chainfire's stuff. I've seen the orange colour you speak of in an faq I've found, but I'm not sure how to remedy this....
I am using the system as described for flashing kernels in Chainfire's thread.
1. debug mode on phone
2. phone into download mode (three buttons)
3. start Odin
4. plug phone into usb
5. browse to zip/tar file of unsecured
6. phone reboots
7. root phone
8. install secured kernel to sd card
9. use cwm to flash that kernel. (which did so successfully i believe)
Is there another step I should have done to install CWM? will reflashing the kernel via odin fix this?
thanks!
Click to expand...
Click to collapse
ur puting the kernel in the PDA section ?? and it is the chainfire kernel ur flashing using ODIN??
boot to download mode
CF kernel >> PDA (Odin)
Flash
Reboot
You get yellow triangle
to remove triangle use a usb jig..its the best option ..u can get it from ebay for less then 10 bux
or
transfer zimage file from the CF kernel.tar file (extract) to internal storage
boot to download mode
stock kernel >> PDA (ODIN)
flash
reboot
open up CWM application(should be in your apps)
choose flash kernel
browse to the zimage file from earlier (from cf kernel)
all done
your step 8 looks wrong.. secured kernel would mean stock..u will not flash the stock kernel (secured)
benivolent said:
You mean like my Blackberry? heh. for sure.
I'm hoping with the Custom Rom it's got less bloatware, better battery life.
Click to expand...
Click to collapse
Not unless bloatware has been removed . Read the rom posts in dev section .
Villain lite rom would be one with less bloatware or use the remove bloatware script same section .
Battery life is more than just the rom much is down to user apps installed .
Villian full rom thread has some useful battery info over the last ten or so pages .
jje
xinfinityoO said:
ur puting the kernel in the PDA section ?? and it is the chainfire kernel ur flashing using ODIN??
Yes, browsing to the CF kernel in pda section of odin
boot to download mode
CF kernel >> PDA (Odin)yup
Flashyup
Rebootyup
You get yellow triangleyup
to remove triangle use a usb jig..its the best option ..u can get it from ebay for less then 10 bux don't have a jig... yet
or
transfer zimage file from the CF kernel.tar file (extract) to internal storage
boot to download modemight do this then
stock kernel >> PDA (ODIN)
flash
reboot
open up CWM application(should be in your apps)
choose flash kernel
browse to the zimage file from earlier (from cf kernel)
all done
your step 8 looks wrong.. secured kernel would mean stock..u will not flash the stock kernel (secured)I did flash the secured version of the kernel back onto it after rooting it. That might have been the issue. I just reflashed CF kernel and had the CWM work differently for the back up. still not orange, but at least it actually backed it up!!! yaaaahooooo!
Click to expand...
Click to collapse
initially i had rooted with the one click method, and then still didn't have root so changed and did the chainfire method. but still put a stock kernel on after flashing and getting root with super one click. I think I didn't realize that the CF kernel means I get root without having to use superone click. and still put a stock kernel back on afterwards.
JJEgan said:
Not unless bloatware has been removed . Read the rom posts in dev section .
Villain lite rom would be one with less bloatware or use the remove bloatware script same section .
Battery life is more than just the rom much is down to user apps installed .
Villian full rom thread has some useful battery info over the last ten or so pages .
jje
Click to expand...
Click to collapse
Ok, fantastic. Thanks I'll have a look at that. I may not have gotten to the end yet with all 700+ pages hehe
And thanks to all who've responded to my issues. Much appreciated.
Here's the reflashed CF kernel CWM doing the back up... this about right?
benivolent said:
And thanks to all who've responded to my issues. Much appreciated.
Here's the reflashed CF kernel CWM doing the back up... this about right?
Click to expand...
Click to collapse
yes
get a jig ..will save u a lot of work.. since i think u made an error while trying to remove the triangle
xinfinityoO said:
yes
get a jig ..will save u a lot of work.. since i think u made an error while trying to remove the triangle
Click to expand...
Click to collapse
I purchased one from somewhere in the UK (off ebay), just waiting for it to arrive.
So now I've gotten my CWM working and i've backed up my phone with titanium and cwm (no need for nand i guess?) Can i safely try to add the mods for the battery %?
benivolent said:
I purchased one from somewhere in the UK (off ebay), just waiting for it to arrive.
So now I've gotten my CWM working and i've backed up my phone with titanium and cwm (no need for nand i guess?) Can i safely try to add the mods for the battery %?
Click to expand...
Click to collapse
as far as i think..backup using cwm is nand backup..unless i am wrong
once you have cwm backup u can play around with mods
thanks again for your help.
Hey guys,
Right now I'm on a custom GPe rom (i9505G). I need to get back to Touchwiz.
You're probably wondering ... why...? Well, last night I bought a Fitbit Flex, and it's supported by GS4 (wireless syncing), http://www.fitbit.com/devices. Could it be because I'm on a custom rom?
Any feedback is appreciated.
Thanks,
gameriot
Yes, it doesn't work because you're on a custom Rom. Fitbit doesn't support it. You can flash the stock firmware in Odin.
Those fitbit's only work on stock or stock-based roms. There's some good ones in the Android Development section. Cheers
jd1639 said:
Yes, it doesn't work because you're on a custom Rom. Fitbit doesn't support it. You can flash the stock firmware in Odin.
Click to expand...
Click to collapse
I have a Mac, so I can't get Odin.
xBeerdroiDx said:
Those fitbit's only work on stock or stock-based roms. There's some good ones in the Android Development section. Cheers
Click to expand...
Click to collapse
I'll check it out. Could you link it?
gameriot said:
I have a Mac, so I can't get Odin.
I'll check it out. Could you link it?
Click to expand...
Click to collapse
Best Touchwiz-based ROM, in my opinion, right here:
http://forum.xda-developers.com/showthread.php?t=2313469
gameriot said:
I have a Mac, so I can't get Odin. I'll check it out. Could you link it?
Click to expand...
Click to collapse
#1. The TW rom that I find best for me is Shostock2.1 It's already very mature, stable and zero issues.
Here's the link if you want another option:
http://forum.xda-developers.com/showthread.php?t=2305752
#2. As to the Mac and no Odin thing. . . . I use a Mac (a couple of them, actually) and found that Heimdal can be made to work, but some folks feel it is not as user friendly/easy to use as Odin. (Btw, you should not need a custom driver to use Heimdal -its a mac and should see your phone w/o driver issues!)
I have used it, but maybe it's just my experience, there have been sometimes when you have everything set up correctly, Heimdal still seems to choke, or just not complete the task (or see the tar file that you want to use!).
Anyway, the newer versions seem better, please check out the current version of Heimdal and the Heimdal front end package?
Here is a Heimdal link in case you want to check: http://www.glassechidna.com.au/products/heimdall/.
The site should have instructions on how to get your file -the stock image or rom image that you want to load and make sure it's the right one and also that its in a form Heimdal can use. . .
Also, here is another very good, informative thread of someone's experience restoring his i337 using Heimdal! It might be helpful (and it is just a few posts down from yours
http://forum.xda-developers.com/show....php?t=2374441
#3. But even on a MAC you CAN use Odin! Odin generally works well and if Heimdal seems to complicated or you can't get it working, then you could open your options up significantly if you can either:
(1) use bootcamp and boot into a windows OS, or
(2) use Parallels/VM Ware Fusion and use windows in a virtual window.
Bootcamp is 100% windows running on your mac and is rock-solid, while the VM machine approach also is mature and pretty good, if occasionally temperamental...
If you can do this, then you can use Odin and work on phone with all the tools that most folks here have and use to good effect.
Good Luck!
markbc01 said:
#1. The TW rom that I find best for me is Shostock2.1 It's already very mature, stable and zero issues.
Here's the link if you want another option:
http://forum.xda-developers.com/showthread.php?t=2305752
#2. As to the Mac and no Odin thing. . . . I use a Mac (a couple of them, actually) and found that Heimdal can be made to work, but some folks feel it is not as user friendly/easy to use as Odin. (Btw, you should not need a custom driver to use Heimdal -its a mac and should see your phone w/o driver issues!)
I have used it, but maybe it's just my experience, there have been sometimes when you have everything set up correctly, Heimdal still seems to choke, or just not complete the task (or see the tar file that you want to use!).
Anyway, the newer versions seem better, please check out the current version of Heimdal and the Heimdal front end package?
Here is a Heimdal link in case you want to check: http://www.glassechidna.com.au/products/heimdall/.
The site should have instructions on how to get your file -the stock image or rom image that you want to load and make sure it's the right one and also that its in a form Heimdal can use. . .
Also, here is another very good, informative thread of someone's experience restoring his i337 using Heimdal! It might be helpful (and it is just a few posts down from yours
http://forum.xda-developers.com/show....php?t=2374441
#3. But even on a MAC you CAN use Odin! Odin generally works well and if Heimdal seems to complicated or you can't get it working, then you could open your options up significantly if you can either:
(1) use bootcamp and boot into a windows OS, or
(2) use Parallels/VM Ware Fusion and use windows in a virtual window.
Bootcamp is 100% windows running on your mac and is rock-solid, while the VM machine approach also is mature and pretty good, if occasionally temperamental...
If you can do this, then you can use Odin and work on phone with all the tools that most folks here have and use to good effect.
Good Luck!
Click to expand...
Click to collapse
I already tried hiemdall. It kept coming up with error whatever I did. Also my TWRP keeps failing when I'm trying to flash. I'm trying goomanager.
Sent from my GT-I9505G using Tapatalk 4
gameriot said:
I already tried hiemdall. It kept coming up with error whatever I did. Also my TWRP keeps failing when I'm trying to flash. I'm trying goomanager.
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
OK, I have been there! If Heimdall does not work, then:
a) find a windows machine for a while or
b) use your machine with bootcamp (if you're on a MBP) or
c) use your machine but install/open a virtual desktop (Parallels or VMware Fusion) to get a windows or linux environment.
Please BE CAREFUL when using goomanager (or Rom Manager, for that matter). These apps are useful, but they also are prone to suddenly creating havoc on the phone - usually when least expected . I have used both -but only very carefully and for limited functions. (I recently used GM to update my TWRP to the latest (I think 2.6?) -no issue --so try that at least!)
But for loading roms, initially loading recoveries or the like it is better to use the "manual" processes that we have available here.
Good Luck!
markbc01 said:
OK, I have been there! If Heimdall does not work, then:
a) find a windows machine for a while or
b) use your machine with bootcamp (if you're on a MBP) or
c) use your machine but install/open a virtual desktop (Parallels or VMware Fusion) to get a windows or linux environment.
Please BE CAREFUL when using goomanager (or Rom Manager, for that matter). These apps are useful, but they also are prone to suddenly creating havoc on the phone - usually when least expected . I have used both -but only very carefully and for limited functions. (I recently used GM to update my TWRP to the latest (I think 2.6?) -no issue --so try that at least!)
But for loading roms, initially loading recoveries or the like it is better to use the "manual" processes that we have available here.
Good Luck!
Click to expand...
Click to collapse
Thanks for the help. I got Touchwiz on my phone and got the sync to work but I just hate Touchwiz and went back by restoring my nandroid. Can't wait till they get Bluetooth 4.0 on custom roms, then it'll work.
Sent from my GT-I9505G using Tapatalk 4
Great..and if you still need a TW Rom, you still can switch launchers to Nova or something like that...
Then you hardly see the Samsung footprint...yet have the TW needed for the device..
Sent from my SAMSUNG-SGH-I337 using XDA Premium HD app
Hi All,
I just got an SPH-i337 yesterday and attempted to Root + Install Mod.
I ended up rooting and installing Safestrap (TWRP 2.6.x.x). Upon first use I backed up my current OS to a removable SD card using the utility in TWRP. I then, because I was not clear on how to download install CM which was what I was going to, installed ROM Manager and selected CM without setting up a ROM slot. I think this is where I went wrong.
Upon reboot, I was unable to access the Stock ROM and had no options to go to CM. When I attempted to perform a restore from my backup on SD it failed as well and keeps going to the Android recovery screen (not TWRP).
I'm now just trying to go back to stock and have tried using both Heimdall and Odin to no avail. Odin at least provides an error message:
SW REV. CHECK FAIL: Fused:4, Binary:1. What does this mean? That I'm attempting to use an image (.tar.md5 file) which is not current? Is there a way that I can still recover my phone?
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
revolut10n said:
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
Click to expand...
Click to collapse
Look for the mk2 tar files. And do a lot of reading. You went wrong in a number of different areas
revolut10n said:
Hi All,
I just got an SPH-i337 yesterday and attempted to Root + Install Mod.
I ended up rooting and installing Safestrap (TWRP 2.6.x.x). Upon first use I backed up my current OS to a removable SD card using the utility in TWRP. I then, because I was not clear on how to download install CM which was what I was going to, installed ROM Manager and selected CM without setting up a ROM slot. I think this is where I went wrong.
Upon reboot, I was unable to access the Stock ROM and had no options to go to CM. When I attempted to perform a restore from my backup on SD it failed as well and keeps going to the Android recovery screen (not TWRP).
I'm now just trying to go back to stock and have tried using both Heimdall and Odin to no avail. Odin at least provides an error message:
SW REV. CHECK FAIL: Fused:4, Binary:1. What does this mean? That I'm attempting to use an image (.tar.md5 file) which is not current? Is there a way that I can still recover my phone?
Click to expand...
Click to collapse
revolut10n said:
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
Click to expand...
Click to collapse
Safestrap only works with other TW ROMS, so your first issue was trying to use CM. Second, it's not official TWRP and is not even installed to the recovery partition so using ROM Manager was your second issue. Trying to boot into recovery normally will take you to stock recovery since it isn't installed in the recovery partition, there should be a splash screen that comes up after the Samsung Galaxy S4 screen asking to either press for recovery or continue. If that works, you can use the backup from there. If it's gone, you have to use ODIN. The reason you get that SW REV. CHECK FAIL is because you're trying to flash an older firmware than you have. Depending on if you were on 4.2.2 or 4.3 you will either need the MF3 or MK2 .tar.md5 respectively.
jd1639 said:
Look for the mk2 tar files. And do a lot of reading. You went wrong in a number of different areas
Click to expand...
Click to collapse
Thanks for pointing me to those files. I'm sure I did go wrong in a few places as I felt that I was largely just winging it.. There's a TON of information out there. Is there anything specific that I was more wrong than the rest?
revolut10n said:
Thanks for pointing me to those files. I'm sure I did go wrong in a few places as I felt that I was largely just winging it.. There's a TON of information out there. Is there anything specific that I was more wrong than the rest?
Click to expand...
Click to collapse
Deadly sin said it all. Cm and rom manager. Here are the files you need http://forum.xda-developers.com/showthread.php?p=49687770
Thanks everyone. Hell of an introduction to Android, I have to say considering I just got off the WinPhone bandwagon yesterday (been using it for ~7 years).
revolut10n said:
Thanks everyone. Hell of an introduction to Android, I have to say considering I just got off the WinPhone bandwagon yesterday (been using it for ~7 years).
Click to expand...
Click to collapse
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
jd1639 said:
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
Click to expand...
Click to collapse
Now you tell me - after I've been trying to do this for 12+ hours. Many thanks though - it looks like the MK2 AiO files are working.
jd1639 said:
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
Click to expand...
Click to collapse
Unfortunately, it seems that I can't use the method listed directly on that page on account of running the MK2 baseband. If I'm going to go forward it looks like I'll have to use SafeStrap and unofficial TWRM + TW mods for the time being.
Of course, if something about what I'm saying is wrong, I'd be glad to hear it.
revolut10n said:
Unfortunately, it seems that I can't use the method listed directly on that page on account of running the MK2 baseband. If I'm going to go forward it looks like I'll have to use SafeStrap and unofficial TWRM + TW mods for the time being.
Of course, if something about what I'm saying is wrong, I'd be glad to hear it.
Click to expand...
Click to collapse
Check my last Post #50 it should get u an idea and where to find related link. Also check that MK2 INDEX & ROM LIST ....:good:
I can't seem to figure out how to downgrade back to a stock ROM after installing this:
lineage-14.1-20170331-UNOFFICIAL-trltetmo.zip (can't post link yet)
I believe it's the Nougat 7.1.1
I want to downgrade to 6.0.1 or 5.1.1
One message I see is "Recovery is not Seandroid Enforcing". Seems like all fixes suggest reinstalling stock ROM, which I'm trying to do, but can't.
Phone is a Samsung Note 4 SM-N910W8 (Rogers)
What's your steps to downgrade to 6.0.1? Did you download Rogers ROM and ODIN it(google is your best friend)?
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
If ODIN starts and stops immediately, you have a different problem. Did you install the Samsung Android USB driver properly. Anyway, you have a software issue, fix it first. I suggest you watch a few related video on youtube.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse
Currently no response.
In the freezer... I'm waiting.
Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
SUREFACE said:
It Sounds that You have a "FULL BRICK" !
The Only way, that REALY can Help is a "USB-JIG".
And Hope, that this One Brings Your Device back in Download-Mode!
You can Build Your Own One, see here : https://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707
Or Buy One! See Here: https://www.amazon.de/Download-Repair-Stecker-Samsung-Galaxy/dp/B004VN5ZYS
And You need a REPAIR ROM ! Take A Look here for Your Variant : https://mega.nz/#F!Ax0gxSzZ!Qq_eJWX678bQHBhn7BHNDQ
Hope that this will Work!
Click to expand...
Click to collapse
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0
Is your phone booting up and functioning? If it is, why are you talking about debrick? I'm assuming that you're "new" to all this. I suggest you read up(especially the stickies) and be comfortable before you go further.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse
ziggy1971 said:
Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0
Click to expand...
Click to collapse
No, it doesn't boot up at all now.
I know I initially said "I" installed the custom ROM, I didn't, I bought it that way. The previous owner won't do anything to help. The only thing he did was provide a link to the ROM he had installed, nothing more, not even the tutorial related to it, I found that on my own (wait, he's made it more than clear how incompetent/ignorant I am as a person).
I've been searching and reading for 3 days straight now. Getting to the point again where I accept defeat, assume the money lost.
Moving on... I've rooted other phones before without issues.
I follow a tutorial on how to downgrade to a stock ROM.
http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
Odin stops with various errors.
I could still boot device into TWRP-3.1.0
Reflashed LineageOS 14.1 ROM from SD to get it working again.
LineageOS 14.1 ROM would boot up, run for almost a minute and a half and shut down.
Pull battery, reboot into LineageOS 14.1 ROM, same thing.
Run Odin, connect device to computer, try to flash stock ROM, error again (different one). Somehow, it says "There is no PIT partition"
I followed this tutorial: https://forum.xda-developers.com/no...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
Odin says FAIL.
Now, it does NOTHING.
I follow this tutorial: Debrick here: https://forum.xda-developers.com/not...k-img-t3488114
Yes, the whole freezer thing overnight.
I have the latest USB drivers installed.
When I connected to the PC, an error popped up saying "...drivers not installed properly..." so I let Windows Update install the correct drivers.
I can connect to the PC now, press the power button for more than 10 seconds, eventually a popup message says "USB Device Not Recognized by Windows"
I've tried the following stock ROMs, 4.4.4, 5.1.1. I finally managed to download 6.0.1, but haven't been able to try it.
All I can say is that if you can boot into TWRP(I assumed you install the N910T version), then your phone is not bricked. All these "debricking" you're doing is potentially harming than fixing.
You assume the risk, when you buy 2nd hand. But based on what you're saying, it sounds like it may also have hardware issues(I don't think software will fix). Was it working when you got it? If you can return it, I suggest you do.
Another pc or windows version may work
A more trustworthy guide on using ODIN:
http://forums.androidcentral.com/am...w-flash-stock-rom-via-odin-new-interface.html
mnopy said:
Another pc or windows version may work
Click to expand...
Click to collapse
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?
ziggy1971 said:
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?
Click to expand...
Click to collapse
QualcommDrv
this is the Qualcomm Drivers(x86 and x64, choose your system's version and install) .
Without that your pc will not recognize your phone.
Uninstall everything related to samsung from your pc.
Kies, smart link, usb drivers. Use revo-unistaller for this to be sure nothing have left behind.
Go to control panel>system>device manager and remove anything that is related to your phone . If prompt delete drivers associated with that, say yes. Reboot your pc
Have saved QualcommDrv, samsung usb drivers and Odin. These are the tools you are going to need and must have.
after uninstall everything, unzip and install QualcommDrv.
Take off your battery, press power buton for 10 sec . Connect the phone to pc (without battery)
QualcommDrv will install the correct drivers for your phone. After that If in devices and printers it is recognized as Qualcomm 8084 .... its ok to proceed . if not , check again drivers and their installation
If windows says device drivers are not correctly installed and prompt to download and install, stop and cancel it.
IT will replace the QualcommDrv and you will not be able to see your phone correctly.
You need to keep QualcommDrv installed. When this is done and you are sure its correct and working, unplug your phone and install Samsung usb drivers. Reboot pc
unzip odin in desktop (or where ever its easy to access).
with your phone freezed and battery charged try to go to download mode. If succeed, connect to pc and with odin try to flash stock rom. If not ......
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
That what you need to have correct and working in order to START. THIS IS ONLY THE FIRST STEP
YOU HAVE TO UNDERSTAND
this is a hardware failure of the motherboard and will never will be completely fixed. These steps will only help you resurrect your phone and maybe give you the chance to be able to use it again.
It has nothing to do with software that failed to install. It was just the result and not the real problem, which is a diffect motherboard like thousand others. Sadly this is a common problem with Note 4 that happened to many users.
I have the same problem and I also bought it second hand knowing its problematic but not how much.
After that I realized the problem and the solutions to it. Every one of us is having a slightly different behavior of the phone.
I, for example cannt use the phone without the ext sdcard with unbrick image in it. When I take it out phone, will not start, reboot , do nothing.With the card in it its working almost perfect.
So have patience and read and search to know what you are dealing with.
Good luck
I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?
ziggy1971 said:
I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?
Click to expand...
Click to collapse
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.
dicksteele said:
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.
Click to expand...
Click to collapse
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.
ziggy1971 said:
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.
Click to expand...
Click to collapse
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613
dicksteele said:
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613
Click to expand...
Click to collapse
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.
ziggy1971 said:
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.
Click to expand...
Click to collapse
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step
logosA said:
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step
Click to expand...
Click to collapse
Those are good.
Some more are here
https://forum.xda-developers.com/general/xda-university
https://forum.xda-developers.com/chef-central/android
https://forum.xda-developers.com/showthread.php?t=1272270
https://forum.xda-developers.com/showthread.php?t=2069130
https://forum.xda-developers.com/showpost.php?p=5626301&postcount=4
https://forum.xda-developers.com/showthread.php?t=1590192
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
There are essentially two ways to do what you want.
Use the unpack tool above, extract the system.img from a Stock ROM
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
I get my stock ROMs from here
http://updato.com/firmware-archive-select-model?q=n910c&rpp=15&order=date&dir=desc
Remove the bloatware or apps you don't want.
Use the app same app that you used to extract the system.img to repack it.
Use the https://forum.xda-developers.com/chef-central/android/tool-afaneh-tar-kitchen-t3603649
to build a tar and flash with ODIN.
Second option use a kitchen. I'm testing the one below today to see if it works.
https://forum.xda-developers.com/ch...0-0-deluxe-kitchen-graphic-interface-t3579100
SuperR works great. But you need a Linux environment to run it.
I use virtualbox on my Win10 machine. I use premade images from here
http://www.osboxes.org/virtualbox-images/
Personally I use the Ultimate Edition.
Or use cygwin. I gave you plenty of links to learn how that works. It's a pain that's why I use virtualbox.