Related
I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks!
If you ever figuered this out please let me know too, i am having the same issue. I am using a Captive that I just restored with Odin. I unroot it and remove the applock on it. I get the same installation aborted issue. I then tried to install it with ClockWork recovery... that just crashed my phone and I had to reinstall again. So if anyone know what the problem is please chime in.
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
TheEscapist said:
Can't theme the stock rom. It has to be a deodexed rom, which is essentially all of the custom ones. Also, don't flash mods through the stock 2e recovery, you want to do it through CWM.
Click to expand...
Click to collapse
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
ootz0rz said:
Hmm I see, thanks for the info... there was no odex file for that particular file, so I thought I'd be lucky and it was possible :/
And, why should you use CWM to flash instead of the stock recovery?
Click to expand...
Click to collapse
No problem. While on the topic, is that thanks button new, or am i just blind, and missed it all this time?
It's something about signatures, if I remember correctly, though, that may be 3e. I think part of it is that it's just typically done with CWM.
ootz0rz said:
I wanted to apply one of the battery mods to my captivate i896 (running the stock rogers rom), specifically version E.
I tried using the UOT Kitchen website at first but that failed. So then I tried to do it myself, but that also fails. Something seems to be going wrong when I try to apply the update.zip I have and I see no error output to help me trace it. Here's what I've been doing (when I tried it from scratch):
So I downloaded the related zip file from the second post, "scbm_E_grey_number.zip".
I then used "Android Theming and Tweaking" to get the framework file from my phone, and decompile it. I replaced the corresponding .png and .xml files from "scbm_E_grey_number.zip" to the appropriate folders in the decompiled folder from the ATT software. Then using the same software, I compile the framework apk again.
I then use the update.zip creator. I create a "framework" folder in the "placehere" folder for the update creator. Inside the framework folder I placed my new APK. I then ran the update creator to generate a new script, which copies from "framework" to "framework" on SYSTEM. Finally, I have it create the update.zip for me.
Everything is fine up to this point. I place the update.zip on my SD card, boot my phone into recovery, try to flash it...I get the following:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried this a few times with no luck
I'd like to figure this out in the hopes that I can do some mods of my own in the future, so any help would be great Thanks![/QUO
Flash perception
Click to expand...
Click to collapse
dfuse06 said:
Flash perception
Click to expand...
Click to collapse
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
ootz0rz said:
Eh, I'm hesitant to flash a custom rom. I have a rogers captivate and don't want to be stuck with an at&t boot screen (in case I need for repair or whatever) and I don't want to be stuck with poor GPS performance (as mine works VERY VERY well right now).
Click to expand...
Click to collapse
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
TheEscapist said:
AT&T boot screen can be replaced, but you have to do a whole bunch of Odin stuff to get there. Also, that's because we(I'm on rogers as well) have a tweaked modem.bin. You can flash that, or one of the jupiter/JM9 fixes to get similar gps performance. But obviously, it's your choice. You are messing with a quite expensive piece of hardware. However, if you want to apply mods, you need to get a custom rom.
Click to expand...
Click to collapse
I'd love to have a set of concise instructions detailing all that...but everything is all over the place and difficult to find :/ Right now I'm just mostly reading up on things and trying to learn
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
TheEscapist said:
There's instructions in the dev forum. If I wasn't on my phone, I'd grab the link for you. As far as learning, you just have to spend hours and hours on here.
Click to expand...
Click to collapse
Heh I've been trying. It's certainly a bit of a learning curve
Hi.
I'd like to know how to do a full, total and complete restore to a certain firmware.
Firmwares that you can flash with ODIN come in various flavours, most distinguished are firmwares that do not do a factory reset, and others that do.
Furthermore, flashing some firmware by no means does a full restore.
It seemes not to change the CSC code currently set.
Finally I suspect it also may leave other data intact, including for intsance the camara firmware (i know from the galaxy s2 there was a tool that upgraded the camera firmware to fix something).
I want to do a COMLETE reset in which i can be absolutely sure that the state of the phone is identical to that when it shipped.
I ask this because my autofocus does not work anymore, and I see a possibility of this being a software issue. I'm also not alone in this issue, see the thread named "Bad Camera autofocus on Note..".
I already tried restoring to a firmware in which I know I managed to get proper photos, but after reverting to that one photos are still blurry.
I also got a CWM recovery backup from the same firmware on which the camera worked, but installing that one did not fix the problem either.
Can anyone help?
This forum should help you
http://forum.xda-developers.com/showthread.php?t=1424997
---------- Post added at 02:47 AM ---------- Previous post was at 02:46 AM ----------
You want to be sure and flash via odin you use on your desktop. This will wipe everything clean and put a factory firmware on the device.
I know this thread.
I actually did a restore from a rom linked there.
However it does not explain the intricacies of installing a rom, like how CSC code settings work, how complete an installation of a rom is and how it affects the firmware of the camera..
I'm asking about details here, not the general basics on how to flash a rom.
Hello
I own a French Galaxy S for more than a year, it's an unlocked unbranded one bought in Pixmania
Model number is I9000 and PCode is GT-I9000HKYXEF
Installed firmware is 2.3.3 updated officially by Kies one year ago
PDA: I9000XWJVH
PHONE: I9000XXJVO
CSC: I9000XEFJV2
It seems to be the latest version released for my phone in France (CSC XEF)
I have been checking samkiesupdates twitter page often but there hasn't been any update coming out which updates my phone to 2.3.4, 2.3.5 or 2.3.6 while other updates based in CSC OXA and DBT have already received the update (Seems OXA is the Open Europe version)
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
What does rooting do exactly?, I know this is something like on UNIX systems where you need a super user account such as root to access system folders, but I only find threads about how to root the phone, but not what does it do exactly and what does it modify. However it seems, from what I read, that it is possible to return to stock (could Samsung Service Centers detect this modification?)
According to what I read, in case I flashed my phone with a custom ROM I would have to root my phone, why is this exactly needed? Why do stock ROMS seem to not need root at all?
Custom roms seem to already have different bootloaders. Is it possible to revert everything back to stock (including ROM and bootloader) just like if the phone was untouched in a way Samsung Service Centers could detect?
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
The PIT files, I know these are like partition size limits. Is there any advantage of using one or another?
I think this is enough for now. I have been having trouble finding information about these and it seems that all Samsung Galaxy S phones, even if they are the same model, won't receive the same updates for different countries/carriers. I bought an unbranded phone, and I should receive the same updates as other countries like UK do
You could use this guide for rooting your phone:
http://www.theandroidsoul.com/fuguroot-galaxy-s-how-to/
Hello
Thank you, however, there are lots of rooting guides out there and that's not my question exactly. My question is how doesit work internally and what does it do to the phone. Just to clearly know what I am doing to my phone at all.
albertocastillo2001 said:
Hello
Thank you, however, there are lots of rooting guides out there and that's not my question exactly. My question is how doesit work internally and what does it do to the phone. Just to clearly know what I am doing to my phone at all.
Click to expand...
Click to collapse
I'll answer your whole load of questions tonight when I'm back from work.
Sent from my GT-I9000 using xda app-developers app
AlwaysDroid said:
I'll answer your whole load of questions tonight when I'm back from work.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Thank you.
why donn't you upgrade it to 2.3.6
for root use cf root kernel or semaphore kernel
I cant post in this thread for some reason. Ill try later
albertocastillo2001 said:
I am going to split this post in two cause there is alot...
I have been checking samkiesupdates twitter page often but there hasn't been any update coming out which updates my phone to 2.3.4, 2.3.5 or 2.3.6 while other updates based in CSC OXA and DBT have already received the update (Seems OXA is the Open Europe version)
- Being upgraded to 2.3.6 or whatever isnt really that great. A few changes were made, but really not much. Like some sgs devices have 2.3.4, mine came with 2.3.3 and you really cant tell the difference. here is a complete list of the changes if you want.
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
-There is nothing that you can do about your ram issue other than get a new rom or kernel that handles ram better and uses less of it. As for GPS, i know nothing about that sorry.
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
- Folders like your /efs /data and /cache should never be touched. Only the system and kernel files are replaced. It is possible for /efs to go corrupted during a flash, HIGHLY unlikely using Odin though. But once your rooted, do a backup of the folder and keep it in many places.
What does rooting do exactly?, I know this is something like on UNIX systems where you need a super user account such as root to access system folders, but I only find threads about how to root the phone, but not what does it do exactly and what does it modify. However it seems, from what I read, that it is possible to return to stock (could Samsung Service Centers detect this modification?)
-I am to lazy to type how it works so go here. I learned off of that website. As for the other part, You can return to stock and never have samsung notice because we dont have a flash counter.
Click to expand...
Click to collapse
There you go. /Part 1
---------- Post added at 04:15 PM ---------- Previous post was at 04:01 PM ----------
albertocastillo2001 said:
According to what I read, in case I flashed my phone with a custom ROM I would have to root my phone, why is this exactly needed? Why do stock ROMS seem to not need root at all?
-Technically all roms use root. The difference here is that what you are referring to is the user having root acess. And of course Samsung doesnt really want uneducated people messing with the phones software, so it is locked away from the user. But the system still has to use it. But you do not have to have a custom rom rooted, but fact is that almost all are. For example I tried out a new jellybean port early on and it had no root access. The only thing in this case is that you must flash anything via odin instead of CWM.
Custom roms seem to already have different bootloaders. Is it possible to revert everything back to stock (including ROM and bootloader) just like if the phone was untouched in a way Samsung Service Centers could detect?
- I dont know where you heard this, but the bootloaders so not change on flashing a custom rom. Anyway, when you flash back to stock with odin, EVERYTHING goes. It will be 100% stock, not a single trace of you being rooted, having kernel and recoverys installed etc. Totally new.
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
- What sorry? I dont understand
The PIT files, I know these are like partition size limits. Is there any advantage of using one or another?
- Indeed, they tell odin how to partition your device. There is no advantage to either or. Read here.
I think this is enough for now. I have been having trouble finding information about these and it seems that all Samsung Galaxy S phones, even if they are the same model, won't receive the same updates for different countries/carriers. I bought an unbranded phone, and I should receive the same updates as other countries like UK do
- Indeed each country seems to recieve a different version for some reason.
Click to expand...
Click to collapse
Part two. Hope that helped!
Hello
Thank you very much.
I'm at work but I will read it again when I get home. It really helped, the rooting technical guide was pretty clear, and the PIT file information as well.
About the other questions:
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
-There is nothing that you can do about your ram issue other than get a new rom or kernel that handles ram better and uses less of it. As for GPS, i know nothing about that sorry.
Click to expand...
Click to collapse
It's ok, the GPS is driving me nuts
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
- Folders like your /efs /data and /cache should never be touched. Only the system and kernel files are replaced. It is possible for /efs to go corrupted during a flash, HIGHLY unlikely using Odin though. But once your rooted, do a backup of the folder and keep it in many places.
Click to expand...
Click to collapse
That's pretty interesting, I've seen options as Clear EFS in Odin that seem to be pretty dangerous at all since the EFS seems to contain specific phone data such as the IMEI
I understand these are partitions and not just folders. I remember getting into the recovery on my Galaxy S and formatting the cache partition. Does this cause any trouble at all?
/data partitions holds all the settings in the phone (according to the rooting guide formatting this partition causes a factory reset)
I will keep looking info on the forums for this to understand the details of these folders more in detail.
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
- What sorry? I dont understand
Click to expand...
Click to collapse
Well. I am not sure how Kies works but I remember reading that it only tries to apply updates if the PCode matches with the CSC of the ROM
In my case my PCode is GT-I9000HKYXEF and my ROM's CSC is XEF
If I flash the Open Europe 2.3.6 ROM, my CSC will be OXA, and in future updates Kies might report that it cannot update my device as I've read on some forums because my PCode doesn't match the ROM's CSC anymore.
All could be fixed by reinstalling the 2.3.3 XEF ROM image as well tho.
Few more questions
PIT repartitioning, does this only affects /dbdata and /system. Correct? No risk of messing up with /efs (as it seems to be the most critical partition in the device, is it?)
I am taking a look at Cyanogen's MOD 7.2 for Galaxy S
On their install instructions they ask you to download a kernel and clockwork mod recovery and then Heimdall
Where is the kernel stored after installing it? /system?
If so, just reflashing a new ROM (or the stock ROM again would get back to the official kernel, correct?
What's the [Dump] option in Odin? Haven't seen that anywhere
I have to read some more info about the bootloaders first before being able to ask more.
Thanks
albertocastillo2001 said:
That's pretty interesting, I've seen options as Clear EFS in Odin that seem to be pretty dangerous at all since the EFS seems to contain specific phone data such as the IMEI
-I very much so agree, i dont know why you would want to use that. But Odin is the official samsung flash tool, so i bet that samsung uses it in their repair centers for something.
I understand these are partitions and not just folders. I remember getting into the recovery on my Galaxy S and formatting the cache partition. Does this cause any trouble at all?
-Yes they are separate partitions
- This is not bad at all. Usually before i do nandroids in will do a /cache clear to make it smaller. I think it might actually be beneficial to clear it once and a while anyway. Sometimes i just clear it. Your phone will boot fine. Keep in mind that clearing cache does not clear the dalvik cache, as this is kept on /data and has to be cleared from the advanced menu. Also a word of caution, i wouldnt clear the dalvik while your phone is on, everything will force close. So just do it from recovery
/data partitions holds all the settings in the phone (according to the rooting guide formatting this partition causes a factory reset)
I will keep looking info on the forums for this to understand the details of these folders more in detail.
-What more details so you want? and yes whenever you perform a factory reset, the dalvik cache, /cache and /data partitions are cleared. But just wiping /data will be the same, but the cached reminants will still be there, which isnt an issue, its just wasted, thats all.
Well. I am not sure how Kies works but I remember reading that it only tries to apply updates if the PCode matches with the CSC of the ROM
In my case my PCode is GT-I9000HKYXEF and my ROM's CSC is XEF
If I flash the Open Europe 2.3.6 ROM, my CSC will be OXA, and in future updates Kies might report that it cannot update my device as I've read on some forums because my PCode doesn't match the ROM's CSC anymore.
All could be fixed by reinstalling the 2.3.3 XEF ROM image as well tho.
-Ah i get it, and yes you are correct. Even though there will never be another update for your device.
PIT repartitioning, does this only affects /dbdata and /system. Correct? No risk of messing up with /efs (as it seems to be the most critical partition in the device, is it?)
-Yes, i believe that the 10mb is transfered between the two. But when you install cyanogenmod 9, it gets rid of /dbdata. There should NEVER EVER EVER be a risk of messing with /efs. It is a rare occasion for it to go corrupt. Possible though, so do your backups.
- As for being the most important partition, it is hard to say. Your phone will boot with no /efs, it will just lag like hell, have no service or imei. Kinda hard to explain that one to the repair center since nothing touches that partition, ever.
I am taking a look at Cyanogen's MOD 7.2 for Galaxy S
On their install instructions they ask you to download a kernel and clockwork mod recovery and then Heimdall
Where is the kernel stored after installing it? /system?
If so, just reflashing a new ROM (or the stock ROM again would get back to the official kernel, correct?
-I believe that the kernel parts are mainly stores in /sys, although there are pieces in other places as well. (ex: /data/local/devil for devil kernel settings)
-Also, unlike my old galaxy gio, the recovery is packaged with the kernel on galaxy s. So changing the kernel replaces the recovery as well. You cant do it individually.
-Yes, all aftermarket and stock roms come packaged with a kernel. For example, i use devil kernel with my cm9. But when i flash a new version of cm9, it replaces the kernel and i have to flash devil kernel again.
What's the [Dump] option in Odin? Haven't seen that anywhere
-DONT take my word on this, i am not 100 sure. But i think dump, performs a dump of all the partitions to your computer. Not sure, so i dont advise trying it without research.
I have to read some more info about the bootloaders first before being able to ask more.
-Okay, let me know!
Thanks
Click to expand...
Click to collapse
.......
Hello
Thanks again
I guess ROMs like CM9 (this seems to be the one I am interested on) don't mess with PBL like boot.bin or the secondary bootloaders right? Or do they? (Only ClockWork Mod modifies the SBL to install it's own recovery I guess?)
Are all the needed folders on the stock ROMs as well? Like boot.bin, the secondary bootloaders and all the folders such as /dbdata /cache /data /dev /etc /lib /mnt and all these folders that are typical to see on UNIX and Linux installs?
As seen in here: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions it seems they contain the PBL, SBL and folders like /mnt. So I guess they have everything on them ready to go
It's just to know which folders to backup in case it's needed.
Does ticking repartition with a PIT file in Heimdall or Odin repartition the whole device in a way where important files/folders get deleted (/efs for example) or does it just repartition /dbdata and /system without touching anything else on the device?
Does installing ROMs from Odin or Heimdall format the partitions before installing them? Seems CyanogenMod 9 has a script to turn partitions from RFS format to EXT4
What if I wanted to get back to stock, would Odin format them in RFS format as well?
I guess these are all the questions I need to ask to cover all doubts.
Thanks!
albertocastillo2001 said:
I guess ROMs like CM9 (this seems to be the one I am interested on) don't mess with PBL like boot.bin or the secondary bootloaders right? Or do they? (Only ClockWork Mod modifies the SBL to install it's own recovery I guess?)
-Nothing unless otherwise stated messes with the bootloaders on most devices. But our bootloaders are unlocked, meaning the partitions arent signed and the bootloader doesnt check for sigantures, so it doesnt care if we have a custom recovery. When we use the three button combo, all it does is trigger the bootloader to boot into the recovery partition. But since they arent locked (bootloaders) and partitions arent signed the bootloader doesnt care whats there. Itll boot whatever is there. So no mods needed for custom recovery.
********NOTHING MESSES WITH BOOTLOADERS UNLESS OTHERWISE STATED ***********
Are all the needed folders on the stock ROMs as well? Like boot.bin, the secondary bootloaders and all the folders such as /dbdata /cache /data /dev /etc /lib /mnt and all these folders that are typical to see on UNIX and Linux installs?
- Yes everything you need to go **********100000000000000000000000000000000000000000000000000000% back to stock ************ is in there, even bootloaders. The primary bootloader isnt, cause nothing will ever touch it.
As seen in here: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions it seems they contain the PBL, SBL and folders like /mnt. So I guess they have everything on them ready to go
It's just to know which folders to backup in case it's needed.
-The only thing you should backup is /efs
Does ticking repartition with a PIT file in Heimdall or Odin repartition the whole device in a way where important files/folders get deleted (/efs for example) or does it just repartition /dbdata and /system without touching anything else on the device?
-Odin only will repartition /data /cache /dbdata and /system back. Removing things like /datadata in the process.
****************NOTHING EVER EVER EVER MESSES WITH YOUR EFS> EVER****************************
Except unlock attempts
Does installing ROMs from Odin or Heimdall format the partitions before installing them? Seems CyanogenMod 9 has a script to turn partitions from RFS format to EXT4
What if I wanted to get back to stock, would Odin format them in RFS format as well?
-This is a question i wish someone had answered for me when i was new here. Odin wont format the /data and /cache and dbdata(i think?) when flashing back to stock, so if you try to boot, you will bootloop. Only the stock recovery can format to rfs and knows how to handle it, so you must do a factory reset to format the rest of the partitions back to RFS.
Click to expand...
Click to collapse
Hope that helps you out
Hello
Thanks again for your infinite knowledge
I think that's all. Anything else you suggest or something I should read? WIki is pretty good, but I think it's far from complete and more could be added
Samsung stopped genuinely supporting this phone quite a while ago. The burden of updating the device has fallen onto the development community. Given that the I9000 is one of the most popular Android phones, LOTS of development has taken place since then.
The kernel on this device is part of the boot image, on its own partition. Recovery is coupled to that partition.
Rooting a device adds a new binary (su) to the system partition. This file is given permission to run as user 0 (root) and acts as a proxy for other processes to perform privileged actions (deleting system files, mounting partitions, accessing all data, etc).
Most custom ROMs come pre rooted since rooting is quite popular. Titanium Backup is the exemplar for what an application can use root privilege for.
Installing a custom ROM does not require the stock ROM to be rooted, it requires a custom kernel (with a cwm or twrp based recovery).
Most high quality custom ROMs (read CyanogenMod) have scripts to protect the efs partition while flashing.
As long as you can get into download mode on your phone you can always get back to stock firmware. The service centre won't know the difference.
The bootloaders are provided by Samsung, these are not replaced by custom ROMs.
Personally I run a modified build of CM10 and use a radio from the Nexus S (KJ1). I'm very happy with the overall battery life of my phone, signal quality is good in Australia (can't say with certainty for any other part of the world) and performance is quite snappy.
Sent from my Nexus 7 using Tapatalk 2
albertocastillo2001 said:
Hello
Thanks again for your infinite knowledge
I think that's all. Anything else you suggest or something I should read? WIki is pretty good, but I think it's far from complete and more could be added
Click to expand...
Click to collapse
Jus read things that come up in the questions/answers forum. Learn from other peoples mistakes
Sent from my GT-I9000 using xda app-developers app
Thanks all of you
One more question
What is baseband exactly? Is it related to modem/phone firmware?
I see it's never changed or replaced by installing custom ROMs
albertocastillo2001 said:
Thanks all of you
One more question
What is baseband exactly? Is it related to modem/phone firmware?
I see it's never changed or replaced by installing custom ROMs
Click to expand...
Click to collapse
Baseband/modem (samething,)is the little piece of software that talks to the cellphone towers. And because each area uses a different frequency, there are many different ones.
Also good to note that it is not ATS all related to GPS or WiFi.
Sent from my GT-I9000 using xda app-developers app
Hi, I am Noobie & I'm currently using a Samsung Galaxy note, GT-N7000, on gingergbread 2.36, using the ..XXLB1 kernal, I bought the device in spain with a CSC- OXXLB1. * Whilst I absolutely love this device and would like to keep the ROM, I am really tired of un-wanted apps seemingly doing what THEY want, some of these apps appear hazardous to security. With this it's strange to own a "computer" and not have access to all its parts? Consequently I appear forced to "root" this device- and take charge!
After exhaustive reading of the XDA site (for which I am seriously grateful) It seems I have to flash with odinPC a pre-rooted "older GB rom" and then use the newly installed CWMR5 to flash any stock or custom rom after (as long as its chainfire!)- from the external sd card. Accepting this procedure is correct? I still have some questions that hopefully the forum can answer- before I comit to bricklaying! *
1. Is this the only method I can use? Will the device be exactly the same as before, but rooted, after re-upgrading back to the stock XXLB1, from chainfire- despite this rom being "not directly rootable"? *
2. In respect of using the external sdcard to flash from. Does it matter if I flash from sdcard via the usb port, or do I have to use the slot next to the battery? After flashing, does the zimage run from the device ROM, or do I have to keep the sd card installed- does this slow things down? What happens to the original ROM and boot loader? *
3. With CWMR5 it seems I can "wipe" all the caches etc- from recovery. What happens if I use factory reset- does it go back to original and lose everything else? Is it true I can only flash up to 50 times? *
4. Ordinarily I would prefer to flash the device ONLY through a PC based loader (odin/ heidemall). Noting my kernal seems to prohibit this, is it possible to completely erase every thing that comes with stock and re-flash, on a virgin device, any appropriate PDA, Modem, PIT file or boot loader of my chosing- ie be in a position to know exactly what my device is upto and "have Control"- you know, a Linux! *
5. Lastly despite rooting the device, as above, some users appear still to have problems with some apps not staying shut down or problems when deleting them. Such apps include "maps"and "mobile tracker"! Is this simply a case of setting permissions correctly and using a good start up manager, or are such apps so embedded that they can not be removed/ stopped? On my device every time I hit the "home" button a whole host of apps start up, if rooting cannot provide a way to solve this then it would appear almost pointless to root in the first place.
Sorry so many questions, but this is a tricky subject and it would be nice to clarify I am on the right track, if any one can answer any of them I'd really appreciate it. Trying real hard not to FUp!
Many thanks
1. you can just download a stock ICS rom for your country, flash it, root using hydracore kernel, cfroot or any custom kernel, then use triangle away to remove the custom binary counter,,, you can also flash custom roms...
all of these must be done after a lot of reading...
2. i don;t really get the part where you say "or do I have to use the slot next to the battery?".
but with respect to zImage or other files, you can delete them after flashing... the original rom or bootloader is replaced if you flash files that replace them..(i am starting to think that i am not making any sense, lol)
3. using factory reset deletes everything from the phone... that's why, it is often required before flashing custom roms... also, you can flash as much as you want, provided, that you FOLLOW instructions or else you may end up posting a "i-am-bricked topic", which is often accompanied by some whining.. LOL...
other users report that they have 100+ flash counters, which mean they have flashed more than 100 times...
4. i dont get the part where you say that your kernel prohibit you to flash... but you can flash anything, provided that again, you read the instructions..
5. i don't experience any of that, my guess is that you have a branded phone?? i am using an international note and i don't expience that...
to other members, please feel free to correct me i said anything wrong.. just trying to help a fellow here, i know the feeling of having a new phone, it's like living in a different world.
and yeah, thats one hell of a post, many users might find your post too long to read.
and yeah, thats one hell of a post, many users might find your post too long to read.
Click to expand...
Click to collapse
yeah atleast follow paragraph rules.. its really hard to point what exactly u want to achieve..
1: > to root.. best is to be on ICS > download a kernel for ur ICS rom from here > flash it from stock recovery.. u will have root and custom recovery.. no changes to apps or data wat so ever.. no triangle as well
2: > its not adviced.. its better to keep the flashing roms file internal storage or external SD slot besides the battery.. the OTG mite not mount in the recovery. what zImage are u referring to ?
3&4 : > Custom roms can only be flashed from CWM..Odin flashes stock roms.. if u do a factory reset it will delete all userapps and data.. but doesnot delete anything on the internal storage .. has to be done manually
for flashing roms
format /system
format /data
format / cache
wipe dalvik cache
5: > with root u can almost uninstall anything eg Titanium backup. with root u can control the apps that startup when boot, connectity changed, power connected, media mounted.. etc.. using (romtoolbox >autostart manager)/ (autostarts) etc.
Tired. need to rest my fingers
newer GB root
Thanks for replies, sorry about lack of paragraphs- copied & paste as I had a lot of questions and lost format in transition. (51 year old noobie!).
I am using a Samsung Galaxy note, GT-N7000, on gingergbread 2.36, using the ..XXLB1 kernal, I bought the device in spain with a CSC- OXXLB1.
I would like to root the device and keep as close to stock as possible. *
From the XDA site it seems, with my kernal being a newer GB kernal, I cannot use "zurgrush" or any other method for 1st root. It appears I have to flash a pre-rooted "older GB rom", from Chainfire, and then upgrade back to near stock ROM after. *
In respect of questions 1 & 2, and the responces.
I mearly wished to confirm if this was the only option open to me and also to check that after re-flashing chainfires XXLB1 kernal and ROM, that the phone would be as close to stock as possible- but now with root.
Both replies suggested I flash ICS, which I was not looking for (and it seems cwm6 can only be used on an original ICS, and not GB?).
After reading about all the problems with ICS I am happy to keep GB, particularly as this was written for my phone, in future I intend to customise this ROM to my own requirements.
However I am concerned that if I use chainfire/root to initially root my device, this may limit my option in the future?
For Q2. I just wanted to confirm that I could remove the external SD card after flashing, ie, is the new ROM flashed onto the internal SD memory. *
In respect of question 4. I was very surprised to read that Odin can only flash stock ROM's. I believed that Odin could flash any appropriate PDA, Modem, PIT file or boot loader of my choice? I would very much appreciate clarification of this situation as the forum gives the impression it is better to flash via PC, weather rooted or not? Note: All initial roots appear to be via PC? *
Thanks for your patience, I'm happy with answers to Q3 & 5. But dearly need clarification on my initial root options.
PS: The wise monkey watches his mates fall from the tree first. Many thanks. *
yep odin can flash PIT, files boot loaders and (PDA, CSC and PHONE but needs .tar file)
odin can flash custom kernels as well in .tar format.
newer GB problem
Hi, Samsung Galaxy Note, GT-N7000, on gingergbread 2.36, ..XXLB1 kernal, *CSC- OXXLB1 (Spain). I'm trying to root the device+ keep as close to stock if*possible? *
From reading the XDA, with my kernal being a newer GB kernal, I have to flash a pre-rooted "older GB rom", from Chainfire, and then upgrade back to near stock ROM after. *
I've just tried this method (using FACTORYFS.tar, as adviced)- via OdinPc. Unfortunately it did not work. Odin stops at "factoryfs.img", with no increasing status bar- this issue is covered in a Dr Ketan post (No:4- 3rd Jan, 2012).
All of the help from here assumes bricking- or resolution for allready rooted devices! *
Luckily I am not bricked & I am able to shut down the device, via 3 buttons, and the device will boot up as normal stock. After disconnecting USB cable, Odin prompts of a total write failure.
Tryed reloading drives, cables etc, but it just can not load the .img file.
I do not get any counter displayed in top right corner.
Note: The .tar file only had the factoryfs.img inside, the other file was a zimage kernal (after 1st unzip) do I need this? *
One last point is I am flashing from a 2000 laptop, with an older usb version- don't see why this should hurt unless the samsung drivers have issues, note the yellow high light suggests all is well before starting Odin. *
I am really stuck from here, would appreciate any advice as to what I can do now- even if it means I can not have a near stock GB.
Many thanks,
Hi Cheapskate1,
I have been following this thread for a while, because your situation seems very much to resemble mine. I have however hesitated to offer you advice because I am pretty inexperienced myself. I did however root my Note in the same way as you are trying, with much enormously valuable help from XDA members in this forum. And I found it very valuable to have the device rooted. At the moment you seem to be at the same point as I was here. I suggest you have a look at this thread, and try to follow what I did from there.
The first part of the way you can follow from the posts in the thread. In the second part of the process I was helped by an XDA member (Afilopou) who preferred to use PMs to communicate so as not to make the thread unnecessarily long. I have his permission to forward those PMs to anyone I think could be helped by them. I think I can safely say that if your Note will still start normally then you are not bricked. When I was at this stage the problem was the USB connection. So perhaps you could try a different USB port on your PC. The PC-Note USB connection is a tricky business in my (limited) experience with many variables which you may need to troubleshoot before it works.
I'll keep following your progress with interest.
nwer GB rom
syncopath said:
Hi Cheapskate1,
I have been following this thread for a while, because your situation seems very much to resemble mine. I have however hesitated to offer you advice because I am pretty inexperienced myself. I did however root my Note in the same way as you are trying, with much enormously valuable help from XDA members in this forum. And I found it very valuable to have the device rooted. At the moment you seem to be at the same point as I was here. I suggest you have a look at this thread, and try to follow what I did from there.
The first part of the way you can follow from the posts in the thread. In the second part of the process I was helped by an XDA member (Afilopou) who preferred to use PMs to communicate so as not to make the thread unnecessarily long. I have his permission to forward those PMs to anyone I think could be helped by them. I think I can safely say that if your Note will still start normally then you are not bricked. When I was at this stage the problem was the USB connection. So perhaps you could try a different USB port on your PC. The PC-Note USB connection is a tricky business in my (limited) experience with many variables which you may need to troubleshoot before it works.
I'll keep following your progress with interest.
Click to expand...
Click to collapse
Many thanks for your post syncopath,
I downloaded the usb drivers from softpedia and noted the file was a. Bin (binary), and dont,t know what to do with this on a windows machine?
These drivers appear to be a lower version from the ones I got from Dr Ketans tool box, which is 1.5.5.0.
Consequently I'm still stuck on the "factoryfs.img prompt.
It is worth noting my computer is an ME laptop, 2000, and I have currently a hacked version of XP running on it, and I note the compatability settings for the samsung driver application does not cater for this, only older machines inc, NT, but not XP.
The only other thing is my usb is not part of the boot run up, and so it might be any port I use would act like a "front usb instead of a "motherboard usb."
Anyone with any comments appreciated, I will try to find a newer machine to try again, but in the mean time- HELP
Thanks again,
newer GB rom
Hello again, Still do not have root???? *
Changed computer, loaded XP OS, Odin and Samsung drivers- v.1.5.5.0. Re-booted computer & started Odin added factoryfs.tar, before attaching phone, in stock recovery mode. Still had same problem, as "Syncopath" mentioned in previous post. Odin showed as follows, *
Com3 added,
Odin engine,
File analysis,
Set up connection,
Initialization,
Get PIT mapping,
Firmware update started,
Factoryfs.img. *
Essentially only things not changed are, phone/cable, plus computer OS and flash files.
Sincerity "yellow" flash, on ID:Com, is present- assume drivers are working?
Assume since Odin is able to setup firmware update, that all is fine untill Odin tries to flash the chainfire ROM .img file. *
The phones boot graphics are all static, none moving, with text in top left corner-
Odin mode,
Custom ROM- No,
Originial stock ROM- Yes. *
To me all of this implies the phone will not accept any custom ROM.
Which raises the questioning, can I flash a complete stock, say ICS, via OdinPC?
And then use a root method, for ICS, after?? *
I previously asked if the "zimage" file, that came from first un-zip, should be added to the .tar file. In some respects this makes sence as the .tar file only has the ROM image- factoryfs.img file.
Reasonably a modified kernal part would also be needed to circumvent the stock boot process??? Only guessing. *
Quite desperate for some advice now. Otherwise I will have to buy a pot plant- they come with roots pre- installed.
Perhaps all rooted phones should be named after plants??? TTFN.
lol... I would say best is to install stock ics and then root as its very easy and safe
u just need to download philz kernel and flash it from the stock recovery and bam u have root.
*don't wipe while on ics stock kernel
---------- Post added at 05:17 PM ---------- Previous post was at 05:16 PM ----------
if its a. matter of moving to a custom rom. then root on ics
cheapskate1 said:
Many thanks for your post syncopath,
I downloaded the usb drivers from softpedia and noted the file was a. Bin (binary),
Click to expand...
Click to collapse
This is strange. I just re-downloaded from the softpedia link http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml for Samsung drivers, and I get SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe I did select the "Softpedia Secure Download (US) [EXE]" link on the way. An .exe should be self executing on any Windows system.
I have just reloaded it actually as I no longer have the previous version. I see that nominally the drivers are for the Galaxy-S but this worked for me using my Note with Windows XP. I am now retrying it on my old XP laptop.
As things now stand, how do you see your Note's SD-cards in Windows explorer?
cheapskate1 said:
my computer is an ME laptop, 2000
Click to expand...
Click to collapse
Just to be sure: is your computer running Windows ME, Windows 2000, Windows XP or what else? Windows ME and Windows 2000 date from around 1999/2000 so I would recommend not using drivers much more advanced than that.
---------- Post added at 03:21 PM ---------- Previous post was at 02:59 PM ----------
Installed the aforesaid executable. Rebooted and connected my Note to the laptop via USB and after a lot of dithering the 2 SD cards became visible in explorer with drive letters. Did you get that too?
nokiamodeln91 said:
lol... I would say best is to install stock ics and then root as its very easy and safe
u just need to download philz kernel and flash it from the stock recovery and bam u have root.
*don't wipe while on ics stock kernel
---------- Post added at 05:17 PM ---------- Previous post was at 05:16 PM ----------
if its a. matter of moving to a custom rom. then root on ics
Click to expand...
Click to collapse
Many thanks, I ve looked at this, re-your previous, and believed it would only work on an existing ICS???
Really appreciate confirmation I can use this with my stock GB, considering my kernal issue??
Thanks for you time man.
cheapskate1 said:
I can use this with my stock GB, considering my kernal issue??
Thanks for you time man.
Click to expand...
Click to collapse
what do u mean?
u can install philz only on ics
GB rom root
syncopath said:
This is strange. I just re-downloaded from the softpedia link http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml for Samsung drivers, and I get SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe I did select the "Softpedia Secure Download (US) [EXE]" link on the way. An .exe should be self executing on any Windows system.
I have just reloaded it actually as I no longer have the previous version. I see that nominally the drivers are for the Galaxy-S but this worked for me using my Note with Windows XP. I am now retrying it on my old XP laptop.
As things now stand, how do you see your Note's SD-cards in Windows explorer?
Just to be sure: is your computer running Windows ME, Windows 2000, Windows XP or what else? Windows ME and Windows 2000 date from around 1999/2000 so I would recommend not using drivers much more advanced than that.
---------- Post added at 03:21 PM ---------- Previous post was at 02:59 PM ----------
Installed the aforesaid executable. Rebooted and connected my Note to the laptop via USB and after a lot of dithering the 2 SD cards became visible in explorer with drive letters. Did you get that too?
Click to expand...
Click to collapse
I tried the same link and got a .bin, even though the link stated. Exe (US). (No firewall or security centre).
Perhaps my hacked XP is an issue, I did try with internet online, re-Chasimodo?, but no update was saught! So assumed my drivers were ok, also had "yellow" light? And using Dr ketan toolbox drivers, v.1.5.5.0.
Havnt looked through "explorer" whilst flashing. Had looked when I was using kies once, is there any thing can be done here?
Thanks 4 driver advice, perhaps will try loading back to ME and seek driver update.
Presumably if I can use explorer drivers must be ok? Flip side.
One idea is it possible to use my galaxy Tab10 to flash to my note, its the only kit I have that hasnt been "robbed or modified"- not bad 12 yrs outa my old ME laptop- sgot ethernet & everything!. Ah- I've also got a small linux distro that works well- any thoughrs on this being a better way to plash- re- heidemall?
Please wait to reply until my next post. Re- Oops.
GB what next
Hello again, Oops, oops.....oops??? *
Accidently used "volume up/*power & home keys to put in flash mode! *
Normally I have used the volume down*key, which comes up with R2D2 and a "loading...." text displayed+ (top left text)
This relates to all my previous posts. *
This 2nd screen (from using vol/up), shows the "Samsung Galaxy Note, GT-N7000" splash, twice, and then displays the following at-Top left screen (Blue). *
Android system recovery (3e) * Enter: OK key, Select: vol UP/vol Down. Reboot system now. Apply update from sdcard. Wipe data/ factory reset. Wipe cache partion. Test redband fota[FS].
* There is Yellow text, mid screen, which details the boot up of the CSC, code PHE. Presumably this required to provide function for this "Boot/ Recovery" mode??
* My main question is what is the difference between the 2 start up modes- this appears to be a pretty crucial ???? Am I using the right one? * Is this recovery a pure! "Android" or a "Samsung mix"? * I have a stock GB on my external sdcard- yet I cannot access it through this menu?
* After pressing "apply update from SDcard", what is a DCIM instal? What is difference between- SDcard and USB storage (doH- is this the 32 pin power connector)?
* If I pressed the "Wipe data/ factory reset" will this clear the external SD or is it the same as a normal factory reset. * Does "Wipe Cache Partion" clear all partion tables (PIT files)??
* Lastly what is redband "fota". System boots normal, but I have previously added one update to phone? *
Because I,m not sure about all the above I will refrain from testing any further, if the forum could fill in the blanks, twood be jolly helpful. *
Old monkey- perfectly willing to fall outa the tree- but not sure of best route? *
PS: Is "cheapskate hacked off at my use of "cheapskate1"? I am after all notoriously frugal, with 20yrs at sea- I,m a skate! Private messages welcome. *
PPS: Noobie, with many Q? trying hard to limit post length- sorry moderators.
Android recovery 3e is the stock recovery
to flash using odin u need to use vol dwn+power+home
u cannot install a rom using the stock recovery, u need clockwork mod
newr GB rom and ICS
nokiamodeln91 said:
Android recovery 3e is the stock recovery
to flash using odin u need to use vol dwn+power+home
u cannot install a rom using the stock recovery, u need clockwork mod
Click to expand...
Click to collapse
Nice one, what exacktly can be done in stock recovery- can I flash a stock ICS?
Re- your earlier post, Using the link provided by you- Philz/cwm6 and ICS,
About half way down, there is a comparison. Cwm6 v CF-root
And it says can only be used on existing stock ICS,
Please confirm, GB with non-prerootable kernal> to ICS via Philz/Cwm6 or
Flash stock ICS then Philz/Cwm6 to get root?
Can I flash stock via stock recovery, or better still Odin, what version of odin for ICS.
Keep cool
correction
syncopath said:
This is strange. I just re-downloaded from the softpnk http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml for Samsung drivers, and I get SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe I did select the "Softpedia Secure Download (US) [EXE]" link on the way. An .exe should be self executing on any Wind
Must appologise, I originally downloaded the softpedia driver set via the Tab10, wifi, twice, and each time .bin- very strange?
All down loads same. Transfered files via USB ( v.1.5) to my old laptop, originally ME. Now using hacked xp on it.
Also tried hack xp on desk top computer, usb v.20, prob' 10 yrs old? Same results.
Can I Tab10 to my note- it would resolve the hardware issues?
Thanks again.
Click to expand...
Click to collapse
Philz is a stock ICS kernel with emmc erase disabled to make it safe. as its a stock ICS kernel..it will only work with ICS only.
so as u on GB now.. just upgrade to the latest version of ICS,
go to philz thread and download the kernel that corresponds to your rom,
install it from stock recovery
- OTA, and a very few mods can be installed from stock recovery.. and you cannot flash any ROM using 3e recovery
cheapskate1 said:
Can I Tab10 to my note- it would resolve the hardware issues?
Click to expand...
Click to collapse
I suggest you get your desktop sorted first so that you can download the right files to it to install Samsung USB drivers and get your Note recognised. Trying to download files via your Note isn't going to make that easier and you need a properly functioning desktop to run PC Odin.
ive got safestrap installed. created rom slot. tried to load a rom and nothin. it boots to a wiped stock rom. nothin happens. nothin changes
harley1rocker said:
ive got safestrap installed. created rom slot. tried to load a rom and nothin. it boots to a wiped stock rom. nothin happens. nothin changes
Click to expand...
Click to collapse
You need to provide a lot more information if you want some help. What firmware are you on? What version of SafeStrap did you install? What ROM did you try to install? What steroids did you take? Which modules did you flash? Does your stock ROM boot?
Always provide as much information as possible, it will increase your chances of getting help.
Devo7v said:
You need to provide a lot more information if you want some help. What firmware are you on? What version of SafeStrap did you install? What ROM did you try to install? What steroids did you take? Which modules did you flash? Does your stock ROM boot?
Always provide as much information as possible, it will increase your chances of getting help.
Click to expand...
Click to collapse
Let me try, because I think I have the same issue. I'm running 4.4.2, and I used safestrap 3.73 to create a rom slot and install Hyperdrive. I wiped everything it said to before I installed it, and installed the latest masterpatch after and rebooted. When it rebooted, it appears to have gone into my stock ROM. Everything is the same, except my network doesn't work because it says my SIM card isn't inserted. Any ideas?
---------- Post added at 12:33 AM ---------- Previous post was at 12:20 AM ----------
Caboose27 said:
Let me try, because I think I have the same issue. I'm running 4.4.2, and I used safestrap 3.73 to create a rom slot and install Hyperdrive. I wiped everything it said to before I installed it, and installed the latest masterpatch after and rebooted. When it rebooted, it appears to have gone into my stock ROM. Everything is the same, except my network doesn't work because it says my SIM card isn't inserted. Any ideas?
Click to expand...
Click to collapse
And now I tried to wipe it again, and that ROM slot is gone, and I suddenly don't have room to make a new one.
*edit* apparently a wipe this time around reset my entire phone. No idea why. Is there a manual on this program somewhere? I keep getting told to search and I'll find it, but all I've found is about five lines worth of instructions.
Caboose27 said:
Let me try, because I think I have the same issue. I'm running 4.4.2, and I used safestrap 3.73 to create a rom slot and install Hyperdrive. I wiped everything it said to before I installed it, and installed the latest masterpatch after and rebooted. When it rebooted, it appears to have gone into my stock ROM. Everything is the same, except my network doesn't work because it says my SIM card isn't inserted. Any ideas?
---------- Post added at 12:33 AM ---------- Previous post was at 12:20 AM ----------
And now I tried to wipe it again, and that ROM slot is gone, and I suddenly don't have room to make a new one.
*edit* apparently a wipe this time around reset my entire phone. No idea why. Is there a manual on this program somewhere? I keep getting told to search and I'll find it, but all I've found is about five lines worth of instructions.
Click to expand...
Click to collapse
You cannot use ROM slots with SafeStrap 3.73. You have to install ROMs to your stock ROM slot overwriting your stock ROM. So make a backup before you flash anything. The developer of SafeStrap took a new job and had to abandon development before he could fully implement ROM slots on 4.4.2. I know it's difficult to find but the information is there. Thank you for trying to find it before posting.
EDIT: just so you're aware, I'm still on 4.2.2, so I haven't actually had any experience with SafeStrap on 4.4.2. I'm just relaying information I've read. So definitely do some reading before you do anything in case I'm wrong. If you have more questions I'll do my best to answer them, but make sure you fact check me because i wouldn't want to brick your phone.
Devo7v said:
You cannot use ROM slots with SafeStrap 3.73. You have to install ROMs to your stock ROM slot overwriting your stock ROM. So make a backup before you flash anything. The developer of SafeStrap took a new job and had to abandon development before he could fully implement ROM slots on 4.4.2. I know it's difficult to find but the information is there. Thank you for trying to find it before posting.
Click to expand...
Click to collapse
Yeah, if that information is out there, it's pretty deep. Like, Mariana's Trench deep. At least now it'll be up front. So basically, SafeStrap is a custom recovery in itself, bypassing the need for an unlocked bootloader?
Caboose27 said:
Yeah, if that information is out there, it's pretty deep. Like, Mariana's Trench deep. At least now it'll be up front. So basically, SafeStrap is a custom recovery in itself, bypassing the need for an unlocked bootloader?
Click to expand...
Click to collapse
same version of bootstrap. same prob here. and let me get this str8...over write stock rom slot? isnt that suppose to be like the "safe zone"
Caboose27 said:
Yeah, if that information is out there, it's pretty deep. Like, Mariana's Trench deep. At least now it'll be up front. So basically, SafeStrap is a custom recovery in itself, bypassing the need for an unlocked bootloader?
Click to expand...
Click to collapse
SafeStrap does not bypass the bootloader, it loads after the kernel loads so there is no way to install a custom kernel. This means that you can only use ROMs that are compatible with your stock kernel, no AOSP ROMs and no CM. You can only use TouchWiz-based ROMs.
harley1rocker said:
same version of bootstrap. same prob here. and let me get this str8...over write stock rom slot? isnt that suppose to be like the "safe zone"
Click to expand...
Click to collapse
That is the way it was intended to work, but Samsung changed some things in 4.4.2 and the developer didn't have time to reimplement ROM slots before he left.
Devo7v said:
SafeStrap does not bypass the bootloader, it loads after the kernel loads so there is no way to install a custom kernel. This means that you can only use ROMs that are compatible with your stock kernel, no AOSP ROMs and no CM. You can only use TouchWiz-based ROMs.
That is the way it was intended to work, but Samsung changed some things in 4.4.2 and the developer didn't have time to reimplement ROM slots before he left.
Click to expand...
Click to collapse
I got it working. I have the 4.4.2 kernel and the Graviton ROM flashed after using Safestrap to make a backup. After I flashed the rom, I wiped dalvik and cache, flashed the master patch v.2, wiped again, and rebooted. Everything works except the stock camera app, which I'm currently looking for a fix.
master patch link??
Devo7v said:
You cannot use ROM slots with SafeStrap 3.73. You have to install ROMs to your stock ROM slot overwriting your stock ROM. So make a backup before you flash anything. The developer of SafeStrap took a new job and had to abandon development before he could fully implement ROM slots on 4.4.2. I know it's difficult to find but the information is there. Thank you for trying to find it before posting.
EDIT: just so you're aware, I'm still on 4.2.2, so I haven't actually had any experience with SafeStrap on 4.4.2. I'm just relaying information I've read. So definitely do some reading before you do anything in case I'm wrong. If you have more questions I'll do my best to answer them, but make sure you fact check me because i wouldn't want to brick your phone.
Click to expand...
Click to collapse
DONT TRY OVERWRITING YOUR STOCK ROM SLOT WITH HYPERDRIVE ROM. YOU WILL LOSE SAFESTRAP AND IT BREAKS CAMERA WIFI,basiclly your phone wont work. Ive done it ant now have a s4 active paperweight. Ive tried odin and all the tar,pit and rar files you can find. NOTHIN WORKS. Before any1 says take it to bestbuy....i did. Kies and all the merry samsung reps culdnt put it back together. So before flashing anything over your stock rom slot make dam sure your a rocket scientist or at the very least a software engineer for samsung...
harley1rocker said:
DONT TRY OVERWRITING YOUR STOCK ROM SLOT WITH HYPERDRIVE ROM. YOU WILL LOSE SAFESTRAP AND IT BREAKS CAMERA WIFI,basiclly your phone wont work. Ive done it ant now have a s4 active paperweight. Ive tried odin and all the tar,pit and rar files you can find. NOTHIN WORKS. Before any1 says take it to bestbuy....i did. Kies and all the merry samsung reps culdnt put it back together. So before flashing anything over your stock rom slot make dam sure your a rocket scientist or at the very least a software engineer for samsung...
Click to expand...
Click to collapse
You need to flash the modules after flashing the ROM to get everything working again. Make sure you do it before you allow Hyperdrive to boot for the first time.
Also, in order to use Odin you cannot have Kies installed.
Devo7v said:
You need to flash the modules after flashing the ROM to get everything working again. Make sure you do it before you allow Hyperdrive to boot for the first time.
Also, in order to use Odin you cannot have Kies installed.
Click to expand...
Click to collapse
Way past that dude. The phone only allows me to enter into DL mode as of now. I know i was on ne3 htperdrive when this happened. Can you pls post a link for the correct tar file to use in odin? Ive tried most of those files but none worked. Can u post the correct ones for odin? May the software gods be with me....ima gonna need em....thanx dude
harley1rocker said:
Way past that dude. The phone only allows me to enter into DL mode as of now. I know i was on ne3 htperdrive when this happened. Can you pls post a link for the correct tar file to use in odin? Ive tried most of those files but none worked. Can u post the correct ones for odin? May the software gods be with me....ima gonna need em....thanx dude
Click to expand...
Click to collapse
Follow the instructions and you'll be fine. Remember, since you're on NE3 you can only flash NC9 or NE3.
http://forum.xda-developers.com/showthread.php?t=2835481