Database Info

[EP4D/FP1H/FP5E][MOD][ODIN] Change Boot Splash Image

This is from a whole lot of brainstorming, reading, headaches & lack of sleep. I now understand Odin & Heimdall a whole lot better; & my skills with Samsung Android phones have increased a bit more. I hope that at least one person can benefit from having a modified param.lfs for a custom boot splash.
Let me know if there are any ways that I can improve this post.
Before you begin, this is for the fearless types that know what they're doing or go all out even if they're jumping into a tornado. Your phone may soft-brick if something goes wrong.
Modified Instructions (from kmalinich's thread):
Needed:
Rooted Samsung Droid Charge
Working ADB
Latest Odin3
Hacked param.lfs (attached & mirrored)
New jpeg boot logo size 480x800 (less than 64KB - test to see if larger works)
Steps:
Copy your new splash image (logo.jpg) to your sd card however you'd like.
Remove your SIM card for safe keeping until this process is finished
Start Odin
Enter download mode (reboot to it or disconnect the phone, take out the battery, press the volume down button, plugin the USB cable, wait for the download screen to appear & place the battery back in)
Extract param_mod.tar.md5 from droid_charge_param_mod.zip
Flash hacked param_mod.tar.md5 via Odin3 in the PDA area _*ONLY*_
Reboot into CWM recovery
Mount the system partition from within CWM
Open ADB shell
Enter these commands:
Code:
mount -o remount,rw /dev/block/stl7 /mnt/.lfs
cp /sdcard/logo.jpg /mnt/.lfs/logo.jpg
Reboot and enjoy!
Notes:
I've tested multiple versions of Heimdall with just the modified param.lfs & it fails to upload 99 times out of 100. I recommend Odin3, SamsungPST Lite, or redbend_ua.
The boot splash image only appears for a short while since the Droid Charge kernels have splash images, too. If you'd like the same image for the duration of boot, utilize an app or a guide to change your favorite kernel's splash image.
Mirror:
modded param.lfs - http://db.tt/fjyx4uEf
sample boot splash - http://db.tt/Nj26hmb6
original param.lfs - http://db.tt/HcCZ6O0H
Sources:
Free Your Android - Modifying Samsung Splash Screens (Galaxy S Series + SGS2) <- how I learned to do it
[Mod][ec09] samsung boot splash/image change 7.7.11 - xda-developers <- how I learned about it with the Fascinate
Fixes & verification of FP5E by Tanno of DroidForums

Attempted and soft-bricked phone, I am sure it was my fault, but if you are not comfortable fixing your phone then do not try this mod. That being said it looks sweet and thanks for your effort!

Endless2232 said:
Attempted and soft-bricked phone, I am sure it was my fault, but if you are not comfortable fixing your phone then do not try this mod. That being said it looks sweet and thanks for your effort!
Click to expand...
Click to collapse
Did you happen to select "Re-partition"? That will soft-brick your phone if you're only flashing the param.lfs.

CrimsonKnight13 said:
Did you happen to select "Re-partition"? That will soft-brick your phone if you're only flashing the param.lfs.
Click to expand...
Click to collapse
Nope, not a complete idiot. =) haha. I will try again later and report back.

Endless2232 said:
Nope, not a complete idiot. =) haha. I will try again later and report back.
Click to expand...
Click to collapse
I was hoping for the best. I'll do what I can to help & correct any errors that jack phones up. :fingers-crossed:

This looks great; thanks for doing this! I'll give this a try in a few days once I'm reunited with my laptop (and hence have access to Odin).
Some suggestions:
It would be good to provide the stock param.lfs for people who want to return to the original boot logo. Alternatively, you could provide a CWM zip for people who have the mod installed to revert to the original logo.
It's possible to mount filesystems and perform file operations using the Android recovery, so you could create a CWM zip and just instruct people to drop in their logo image of choice and flash it after applying the base modification through Odin. This would reduce the steps required to just flashing the Odin package and then flashing a CWM zip.
Would it be possible to flash the param.lfs file through CWM? This would simplify things even further.
Anyway, thanks again and I look forward to trying this out!

substanceD said:
This looks great; thanks for doing this! I'll give this a try in a few days once I'm reunited with my laptop (and hence have access to Odin).
Some suggestions:
It would be good to provide the stock param.lfs for people who want to return to the original boot logo. Alternatively, you could provide a CWM zip for people who have the mod installed to revert to the original logo.
It's possible to mount filesystems and perform file operations using the Android recovery, so you could create a CWM zip and just instruct people to drop in their logo image of choice and flash it after applying the base modification through Odin. This would reduce the steps required to just flashing the Odin package and then flashing a CWM zip.
Would it be possible to flash the param.lfs file through CWM? This would simplify things even further.
Anyway, thanks again and I look forward to trying this out!
Click to expand...
Click to collapse
Original param.lfs in tar.md5 format will be posted tonight.
I'm reading mixed news regarding /mnt/.lfs/ file flashing through CWM. Most people are saying its unflashable from CWM but I need to confirm that it can be done.
As far as I know, param.lfs can't be flashed through CWM.
Edit: It appears I can create a CWM zip but I'll need to dig into what others have made to verify that its doing what I need it to do.
http://forum.xda-developers.com/showthread.php?t=1474753

CrimsonKnight13 said:
Original param.lfs in tar.md5 format will be posted tonight.
I'm reading mixed news regarding /mnt/.lfs/ file flashing through CWM. Most people are saying its unflashable from CWM but I need to confirm that it can be done.
As far as I know, param.lfs can't be flashed through CWM.
Edit: It appears I can create a CWM zip but I'll need to dig into what others have made to verify that its doing what I need it to do.
http://forum.xda-developers.com/showthread.php?t=1474753
Click to expand...
Click to collapse
I'm sure others will get to this before I do, but I'll tinker a bit with this as well - at least in reference to exploring what cwm recovery can do.

Works.
Sent from my SCH-I510 using xda premium

dwitherell said:
I'm sure others will get to this before I do, but I'll tinker a bit with this as well - at least in reference to exploring what cwm recovery can do.
Click to expand...
Click to collapse
Any community effort to make this into a smooth working mod is fine with me. I'll do more research myself tonight.
kvswim said:
Works.
Click to expand...
Click to collapse
Great to know.

I attempted to make a usable CWM zip but it fails with a line in the updater-script.
assert(package_extract_file("param.lfs", "/tmp/param.lfs"),write_raw_image("/tmp/param.lfs", "/dev/block/stl7"),delete("/tmp/param.lfs"));
Click to expand...
Click to collapse
It gives the error:
assert failed: write_raw_image("/tmp/param.lfs", "/dev/block/stl7")
<snip> (Status 7)
Click to expand...
Click to collapse
I'm wondering if /dev/block/stl7 is even writable from CWM.
I have attached both zips for anyone's perusal.

CrimsonKnight13 said:
I attempted to make a usable CWM zip but it fails with a line in the updater-script.
It gives the error:
I'm wondering if /dev/block/stl7 is even writable from CWM.
I have attached both zips for anyone's perusal.
Click to expand...
Click to collapse
I've been playing around with things on my end - but it seems you are right. I've had no luck w/ this as well. Tried a few changes but to no avail. Ah well - other than that your original method worked for me

dwitherell said:
I've been playing around with things on my end - but it seems you are right. I've had no luck w/ this as well. Tried a few changes but to no avail. Ah well - other than that your original method worked for me
Click to expand...
Click to collapse
I'm glad that the original method does work & that we both came to the same conclusion. Thanks for looking into it.
Is there a method to split the zImage, change the RLE, & rejoin it into a workable kernel? Making this thread into a boot & kernel splash image mod combo would be nice. I'm coming up empty handed with my searches through Google & XDA. Most modifications are for Sony phones.

Is step #7 something that can be done within the stock recovery or is that a separate ADB command?

nismology said:
Is step #7 something that can be done within the stock recovery or is that a separate ADB command?
Click to expand...
Click to collapse
I don't recommend EVER using stock recovery due to the possibility of complications with custom-built zips.
/system can be mounted via adb shell as well. The step assumes that you know how to do it via cwm or adb. If I need to clarify, I can.

CrimsonKnight13 said:
I don't recommend EVER using stock recovery due to the possibility of complications with custom-built zips.
/system can be mounted via adb shell as well. The step assumes that you know how to do it via cwm or adb. If I need to clarify, I can.
Click to expand...
Click to collapse
I was in the process of attempting the ADB method of this mod and had CWM installed which was overwritten by the modded param file and step 6 says allow it to boot into recovery which turned out to be the stock one. I guess that is what threw me off.
I guess I didn't know I had to re-Odin CWM to remount the system partition. Just for posterity though, what is the command for mounting it via ADB? I have it all setup already. Thanks for your patience!
Edit: I got it to work. I had to let it boot up, enter shell, get superuser permission, then execute the mount command. This was great ADB practice for a newb like myself. Excellent work and it looks great! Thanks for the how-to!
:good:

nismology said:
I was in the process of attempting the ADB method of this mod and had CWM installed which was overwritten by the modded param file and step 6 says allow it to boot into recovery which turned out to be the stock one. I guess that is what threw me off.
I guess I didn't know I had to re-Odin CWM to remount the system partition. Just for posterity though, what is the command for mounting it via ADB? I have it all setup already. Thanks for your patience!
Click to expand...
Click to collapse
It doesn't & won't overwrite CWM. It is merely overwriting the /dev/block/stl7 partition of your phone.
The mount for system varies if you have rfs or ext4.
rfs
mount once: mount -t rfs -o rw /dev/block/stl10 /system
remount: mount -t rfs -o remount,rw /dev/block/stl10 /system
ext4
mount once: mount -t ext4 -o rw /dev/block/stl10 /system
remount: mount -t ext4 -o remount,rw /dev/block/stl10 /system
nismology said:
Edit: I got it to work. I had to let it boot up, enter shell, get superuser permission, then execute the mount command. This was great ADB practice for a newb like myself. Excellent work and it looks great! Thanks for the how-to!
:good:
Click to expand...
Click to collapse
Good to know. I'm glad it worked out for you.
Just doing mount is another good way since it calls up fstab or whatever equivalent it might be on the system.

CrimsonKnight13 said:
It doesn't & won't overwrite CWM. It is merely overwriting the /dev/block/stl7 partition of your phone.
The mount for system varies if you have rfs or ext4.
rfs
mount once: mount -t rfs -o rw /dev/block/stl10 /system
remount: mount -t rfs -o remount,rw /dev/block/stl10 /system
ext4
mount once: mount -t ext4 -o rw /dev/block/stl10 /system
remount: mount -t ext4 -o remount,rw /dev/block/stl10 /system
Good to know. I'm glad it worked out for you.
Just doing mount is another good way since it calls up fstab or whatever equivalent it might be on the system.
Click to expand...
Click to collapse
Thanks for that. I used a slightly different syntax for mounting /system but it seemed to work out anyway.
And by "just doing mount" are you referring to doing it through CWM? That might be a more straight-forward method indeed. I could use the ADB practice though.

And the original source of my confusion was that step #6 says "allow the phone to reboot into recovery". When you flash the modded param and power on the phone, it automatically boots into stock recovery. It might help other people if the step mentions the fact that you must enter into CWM to mount the system partition instead of "allowing" it to boot up normally, which will result in stock recovery after initial boot-up.

nismology said:
And the original source of my confusion was that step #6 says "allow the phone to reboot into recovery". When you flash the modded param and power on the phone, it automatically boots into stock recovery. It might help other people if the step mentions the fact that you must enter into CWM to mount the system partition instead of "allowing" it to boot up normally, which will result in stock recovery after initial boot-up.
Click to expand...
Click to collapse
As I said, it shouldn't be booting into stock recovery when the modded param.lfs is pushed. If you have already flashed a custom kernel, CWM recovery will stay. If you still have a stock kernel, stock recovery will constantly take over.
Additionally, whenever I did it, due to lack of logo.jpg, it would kick me straight into CWM. I'm unsure what your setup on your phone looks like though.
nismology said:
Thanks for that. I used a slightly different syntax for mounting /system but it seemed to work out anyway.
And by "just doing mount" are you referring to doing it through CWM? That might be a more straight-forward method indeed. I could use the ADB practice though.
Click to expand...
Click to collapse
Yes, mounting through CWM is the easiest way.

[HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)

STOP
Follow this guide to the letter. If you don't know what something in ODIN is used for...DON'T CLICK IT.​
Now that that's out of the way, I'd like to apologize to psycopanther for three days worth of trial and error (mostly error), but now I've got a surefire fix for softbricked devices. Kinda ironic how I discovered it though lol.
The Problem: Sometimes when you flash a ROM (TouchWiz or AOSP), there is a risk of the /system and /data partitions not wiping correctly thus leading them to be formatted with R/O permissions rather than R/W. This makes it impossible for the phone to boot up because no data can be written. Not even a typical ODIN flash back to stock or rooted stock will fix this. Using CWM to flash another ROM will yield the same no boot results. Furthermore, the stock recovery will not work and it becomes impossible to perform a factory reset. Sound frustrating? It is.
The Fix: You know how people all over the android forums are told never to tick any of the boxes in ODIN except for Auto Reboot and F. Reset Time? Well this time you will be ticking another box. If you ever run into the problem where your partitions are read-only, but the phone will still boot into Download Mode and recovery, you need to do the following steps:
BUT FIRSTPrerequisites:
ODIN: http://samsung-updates.com/Odin307.zip
Root66.tar: http://www.megashare.com/4384479 -------OR------- (Torrent)
VRALEC bootchain: http://www.androidfilehost.com/?fid=9390034591667978517
VRALF bootchain: http://www.androidfilehost.com/?fid=9390034591667978518
Using both bootchains is probably not necessary, but it's what I did and will do in the future if I ever get another soft brick.
ANDNumber of devices tested on and confirmed working: 40​
Open up ODIN
Select only the following box: F. Reset Time
Flash the VRALEC bootchain in the PDA section and wait for a PASS message
Reset ODIN
Flash the VRALF bootchain in the PDA section and wait for a PASS message
Reset ODINIf you have trouble flashing the bootchains with the method above, try this instead:
1: Flash the first bootchain.
2: Unplug the device while leaving it in "Download Mode".
3: Exit ODIN and then restart it.
4: Plug the device back in while still in "Download Mode".
5: Flash the second bootchain.
6: Repeat steps 2, 3, and 4.
Put the stock.vzw_root66.tar in the PDA section
Select the following boxes: Auto Reboot, F. Reset Time, Nand Erase All
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Start the flash process
Your phone will reboot, but it WILL NOT boot to the homescreen. After you receive a PASS message in ODIN, pull the battery and do the following:​
Reboot into Stock Recovery (hold volume-up, home button, power button simultaneously)
NOTE: You WILL see the following error in recovery so don't freak out:
Code:
E:failed to mount /data (Invalid argument)
E:Can't mount /data/fota/ipth-muc.prop
E:failed to mount /data (Invalid argument)
E:Can't mount /data/fota/ipth-muc.prop
E:failed to mount /data (Invalid argument)
E:Can't mount /data/fota/ipth-muc.prop
Wipe data/factory reset
Wipe cache partition
Reboot
Now your phone will boot up completely with no problems! Congratulations, you just saved yourself $600 and a call to Verizon.
The Question: Will this work on other carriers/devices? Possibly. To those of you on other carriers (AT&T, T-Mobile, Sprint), I am 99.99% positive this will work for you. Just be sure to download a rooted stock ROM in addition to your boot chains that can be flashed in ODIN.
DO NOT USE ROOT66 OR THE LINKED BOOT CHAINS IF YOU ARE ON ANOTHER CARRIER! YOU MUST USE YOUR OWN DEVICE-SPECIFIC FILES!
Thanks
psycopanther - for putting up with me and for figuring out the R/O issue
Invisiblek - for the bootchain files
open1your1eyes0 - for root66
h3llsdr0id - for his method of flashing the bootchains
Donations
Thank you all! - If I forgot you send me a PM
mark-in-dallas
madunix
soopervoo
tserrano35
Ryan Sherman
Kenneth Holt
mike216
kp_martin
If this worked for you please consider a donation. After all, you did just save $600 Donations keep me motivated to putting out new goodies and fixes for the community.​

Bootloader(?) brick
I recently discovered another type of brick by accident and it appeared to be associated with the bootloader. To retrace my steps, I updated to the VRALHD baseband using CWM and immediately after that I restored a backup which caused me to lose the ability to flash ROMs. When loading up another ROM, I always got to the bootanimation, but the bootsound would cut off almost immediately and I would be stuck at a black screen. I was not able to flash ROMs and even unlocking the bootloader again after Odin-ing back to stock didn't work. I was stuck with the stock ROM. The method in the OP doesn't work for this, but the following steps do:
Prerequisites
Root66
PIT file (depending on your model (16gb/32gb)) - (PIT)
Odin
The steps are simple:
Flash Root66 in the PDA slot and the PIT file in the PIT slot
Only tick Auto-reboot, Re-Partition, F. Reset Time
Boot into recovery
Factory reset + wipe dalvik
Reboot
Number of devices tested on and confirmed working: 2​
Your device should boot up normally and you should be able to flash custom ROMs now. If you are still encountering issues, try the method in the OP then re-unlock your bootloader using either AdamOutler's CASUAL or EZ Unlock. Note, if you use EZ Unlock you may continue to get a message saying that the bootloader status is UNKNOWN even after unlocking the bootloader. This was the case for me, but I then did the PIT method as described in this post, factory reset the device, and used TWRP to flash my ROM.
Just an FYI, I now use TWRP so I'm not entirely sure whether there was something specifically wrong with CWM. The partition sizes just got severely messed up.

So what's the ironic story on how you found the fix? Great write up BTW. Hope I never have to use it but keeping this in a safe place.
Sent from my SCH-I535 using xda premium

chefdave12118 said:
So what's the ironic story on how you found the fix? Great write up BTW. Hope I never have to use it but keeping this in a safe place.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Had two S3s, tried to hard brick one to use as a brick test device (it was soft bricked with the error in the OP), but ended up fixing it instead

This should be sticky'd imo

Josolanes said:
This should be sticky'd imo
Click to expand...
Click to collapse
+1
Sent from my SCH-I535 using xda premium

Excellent write up. For some soft-bricks, this might be overkill, but it will alteast get everyone back up and running no matter how severe their issue is. Thank you for the post! I am downloading the files now incase we have some hosting issues in the future. After Goo.im wiped everything a couple times I think it is important to be careful and prepared.

con247 said:
Excellent write up. For some soft-bricks, this might be overkill, but it will alteast get everyone back up and running no matter how severe their issue is. Thank you for the post! I am downloading the files now incase we have some hosting issues in the future. After Goo.im wiped everything a couple times I think it is important to be careful and prepared.
Click to expand...
Click to collapse
Added mirrors for the bootchains just in case.

lol. PROFIT!
---------- Post added at 06:39 PM ---------- Previous post was at 06:31 PM ----------
also, if you have CWM or twrp recovery, and you boot into recovery (before trying any steps above), you can connect your phone with adb and while in recovery (cwm, or twrp) and go into adb shell, and type "mount" .this should show something like this :
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p15 on /data type ext4 (ro,nodev,noatime,nodiratime,user_xattr,barrier=1, data=ordered)
/dev/block/mmcblk0p17 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1, data=ordered)
/dev/block/mmcblk0p14 on /system type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
the /dev/block/mmcblk0p15 is set to RO if you notice. and this will cause constant boot hanging as the /system will try to constantly write to /data in which it will fail. These were our symptoms before trying steps in OP.
MAD PROPS to PureMotive for helping solve this issue. pure genius!

psycopanther said:
lol. PROFIT!
---------- Post added at 06:39 PM ---------- Previous post was at 06:31 PM ----------
also, if you have CWM or twrp recovery, and you boot into recovery (before trying any steps above), you can connect your phone with adb and while in recovery (cwm, or twrp) and go into adb shell, and type "mount" .this should show something like this :
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p15 on /data type ext4 (ro,nodev,noatime,nodiratime,user_xattr,barrier=1, data=ordered)
/dev/block/mmcblk0p17 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1, data=ordered)
/dev/block/mmcblk0p14 on /system type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
the /dev/block/mmcblk0p15 is set to RO if you notice. and this will cause constant boot hanging as the /system will try to constantly write to /data in which it will fail. These were our symptoms before trying steps in OP.
MAD PROPS to PureMotive for helping solve this issue. pure genius!
Click to expand...
Click to collapse
Sorry that I didn't think of this before. The logcat you sent me did show the symptoms of a ro filesystem but it didn't click with me!

not a problem. if it were not for realizing this RO thing, i do not think we would have gotten it all figured out. thank google for allowing adb access so early in the booting process of the phone lol.
however, the next step would be WHY the system is changed to a read only. I did try to just change the RO of /data back to RW in adb unsuccessfully. If a way was figured out to do it through adb with a simple command, then it would be quicker to fix the partition ( possibly just making a recovery flashable script to do it automatically to fix softbricks, but the methods in the OP is the best route for right now. definitely a step in the right direction in making the whole custom flashing alot safer.

Still the man pure, I liked your work on the incredible forums as well. Good stuff man
Sent from my SCH-I535

What section of odin are u flashing the bootchain?

droidstyle said:
What section of odin are u flashing the bootchain?
Click to expand...
Click to collapse
PDA

Going to link this in my guide! Could you add PDA next to flashing bootchains? reason being I believe that folks might try to flash this in bootloader section unless you spell it out for them. Thx

droidstyle said:
Going to link this in my guide! Could you add PDA next to flashing bootchains? reason being I believe that folks might try to flash this in bootloader section unless you spell it out for them. Thx
Click to expand...
Click to collapse
Done and done man

complete (write) operation failed
i was on the second step and i got the fail msg ...what did i do wrong.... i just wanna get my phone back to stock.. i have downloaded the strock firmware rom but everytime i hit the start button nothing happens... please help

bakerboy81 said:
i was on the second step and i got the fail msg ...what did i do wrong.... i just wanna get my phone back to stock.. i have downloaded the strock firmware rom but everytime i hit the start button nothing happens... please help
Click to expand...
Click to collapse
Where you unable to boot? This thread is for fixing write permissions.
Sent from my SCH-I535 using Tapatalk 2

bakerboy81 said:
i was on the second step and i got the fail msg ...what did i do wrong.... i just wanna get my phone back to stock.. i have downloaded the strock firmware rom but everytime i hit the start button nothing happens... please help
Click to expand...
Click to collapse
By second step I'm assuming you are trying to flash the bootchain? Make sure you are flashing the files within the PDA secion of ODIN. If the ODIN still doesn't flash the files, try rebooting Download Mode and/or ODIN and then retry.

psycopanther said:
however, the next step would be WHY the system is changed to a read only. I did try to just change the RO of /data back to RW in adb unsuccessfully. If a way was figured out to do it through adb with a simple command, then it would be quicker to fix the partition ( possibly just making a recovery flashable script to do it automatically to fix softbricks, but the methods in the OP is the best route for right now. definitely a step in the right direction in making the whole custom flashing alot safer.
Click to expand...
Click to collapse
Agree, would be good to know the root cause -- eg. is it a bug having to do with some edge case in CWM recovery or a particular ROM that could fixed?

[Q] Infuse 4g looping even after flashing back to GB2.3.6

Hi guys, I have been pulling my hair out trying to figure out how to bring my infuse back to life, I upgraded to GB 2.3.6 from froyo 2.2.1 a while back. a couple of days ago it just died and could not get back in no matter what (constantly rebooting) so I flashed back to stock with "Heimdall One-click Back-To-Stock UCLB3" and it completes just fine but it does not boot normally. it reboots after the AT&T screen.
I read something about the partition been altered when it was updated to 2.3.6, is that a fact? also I'm not able to use recovery (red recovery) to get it to see the external SD card so I'm really stuck, please help
I would love to be able to update to 4.2.2 any rom.
Thanks a bunch
sorry if I'm posting in the wrong section

Have you tried flashing the heimdall package a second time? Or using heimdall to flash a custom kernel to get red CWM?
Try loading recovery (stock or CWM) and let it sit for a minute (just to see if it reboots by itself there too). You do this by holding power+vol up+vol down then releasing only power when you see the Samsung logo.
Note also that you will only be able to see the internal sd card from recovery and that sd-ext does not refer to the external sd card despite the similarity of the name.
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Have you tried flashing the heimdall package a second time? Or using heimdall to flash a custom kernel to get red CWM?
Try loading recovery (stock or CWM) and let it sit for a minute (just to see if it reboots by itself there too). You do this by holding power+vol up+vol down then releasing only power when you see the Samsung logo.
Note also that you will only be able to see the internal sd card from recovery and that sd-ext does not refer to the external sd card despite the similarity of the name.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
OK, tried to flash the heimdall package again but I had the same result(rebooting att animation even after doing the reset from the 3e recovery menu). let the recovery screen sit (it does not reboot). searched for a custom kernel like you suggested and went to this page (http://forum.xda-developers.com/showthread.php?t=1603220) and was able to flash the kernel but all that did was replace the att animation with "android" but still rebooting. i'm trying to flash with Odin from this page (http://forum.xda-developers.com/showthread.php?p=27123262) and i'll report back.
meanwhile I would like to know how to get access to the internal sd memory to be able to copy things there?
I appreciate you time and effort tying to help.

Your best bet for flashing Odin or heimdall stock packages are found in the super everything thread, 2nd and 3rd options in first section - check my sig for link. The ones with repartitioning may resolve the issues you are having.
After the ROM flash...
Try installing a custom kernel/recovery from either the odin page you linked above, or via heimdall (posts 2 or 3 here):
http://forum.xda-developers.com/showthread.php?p=23118134
Once installed and you reboot, you may see a Samsung or blank screen for about 5 minutes with a robot voice speaking periodically - this is normal, let it finish.
Boot into recovery, it should be red.
If you are still not able to boot into the phone OS, but are able to get red recovery, you can try loading the android sdk and running adb or adbmagic to copy rom install files to your internal sd card (/sdcard)..
Lastly andros11 published a guide on how to get to JB from stock ... If you have red recovery and can get files on your internal sdcard this guide shows how to get the rest of the way to JB.
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Your best bet for flashing Odin or heimdall stock packages are found in the super everything thread, 2nd and 3rd options in first section - check my sig for link. The ones with repartitioning may resolve the issues you are having.
After the ROM flash...
Try installing a custom kernel/recovery from either the odin page you linked above, or via heimdall (posts 2 or 3 here):
http://forum.xda-developers.com/showthread.php?p=23118134
Once installed and you reboot, you may see a Samsung or blank screen for about 5 minutes with a robot voice speaking periodically - this is normal, let it finish.
Boot into recovery, it should be red.
If you are still not able to boot into the phone OS, but are able to get red recovery, you can try loading the android sdk and running adb or adbmagic to copy rom install files to your internal sd card (/sdcard)..
Lastly andros11 published a guide on how to get to JB from stock ... If you have red recovery and can get files on your internal sdcard this guide shows how to get the rest of the way to JB.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
The only rom that seems to stop the loops was "stock root mod3e UCKD5 Odin , but it seems to boot to a black screen,(at least is something) also my recovery has a couple more options like reinstall package and format internal sd card (Samsung recovery utils for BML), any ideas?
Thanks

Can you provide more detail about all the things you have tried so far?
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Can you provide more detail about all the things you have tried so far?
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I have tried Stock_SGH_I997_UCLB3_Repartition-One-Click, SGH-i997-UCKJ4-One-Click, SGH-i997 InfuZen-A16 Kernel One-Click, SGH_I997 Entropy 4_4_2012-One-Click-Heimdall, GTGs_Ultimate_Unbrick, DFT_Summy_Rainbow, not necessarily in that order but the first one I tried was UCLB3_Unbrick_w_root (odin) and then I997UCLB3-GB-bootloaders-only.tar
I know I should have wrote things down but here we are. is there a way to completely start over? or maybe may be do it in steps like partitioning first then flash? i'm also totally lost with all the terms since I don't think I have red recovery at all. I read so many things these past three days.
I really appreciate your help and time and I would understand if this is a lost cause.

Probably not a lost cause. It's tough to brick this phone.
1. Check your drivers.. Use Samsung drivers for Infuse, not Kies. You may need to uninstall both, then install just Infuse drivers. Make sure you are using a high quality and reliable usb cable.
2. Boot recovery, red preferred. Do a factory reset, then format system (available in red recovery)
3. Battery pull, boot into download mode. Try odin or heimdall uclb3 with repartition option. Follow instructions exactly.
4. Boot phone normal.
5. If this works, next step is to flash a custom recovery, convert file system (robot voice, wait), boot phone, copy the roms you need to internal sdcard then follow andros11 guide to continue to jb... (I recommend removing the external sdcard before step 5 to eliminate possibility of using the wrong sd card by accident).
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Probably not a lost cause. It's tough to brick this phone.
1. Check your drivers.. Use Samsung drivers for Infuse, not Kies. You may need to uninstall both, then install just Infuse drivers. Make sure you are using a high quality and reliable usb cable.
2. Boot recovery, red preferred. Do a factory reset, then format system (available in red recovery)
3. Battery pull, boot into download mode. Try odin or heimdall uclb3 with repartition option. Follow instructions exactly.
4. Boot phone normal.
5. If this works, next step is to flash a custom recovery, convert file system (robot voice, wait), boot phone, copy the roms you need to internal sdcard then follow andros11 guide to continue to jb... (I recommend removing the external sdcard before step 5 to eliminate possibility of using the wrong sd card by accident).
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
SO do I need to flash a new rom to be able to boot red recovery?
Thanks

skopedia said:
SO do I need to flash a new rom to be able to boot red recovery?
Thanks
Click to expand...
Click to collapse
Just a custom kernel. On the infuse recovery is included in the kernel.
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Just a custom kernel. On the infuse recovery is included in the kernel.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I just flashed 2012.04.05-ODIN-Entropy_DD-GB-zImage custom kernel on it, is there a trick to be boot to red recovery? I must be doing something wrong.. everything I read is talking about accessing the internal memory to copy to it and install zip from there (remember that I'm not able to do that since I'm not able to boot to rom) please clarify as much as you can.
Thanks

I mentioned that a few posts back... Hold both volume buttons plus power until you see the Samsung logo then release just power. Continue holding volume buttons until recovery loads.
Next steps are as in my previous post, or, with a bit of research on your part attempting to copy rom files via adb, then flashing via red recovery.
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Just a custom kernel. On the infuse recovery is included in the kernel.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
finally after many tries, I was able to get cwm recovery 5.5.0.4 by flashing an ICS kernel (jt1134's kernel) from here . not sure why it worked !
http://forum.xda-developers.com/showpost.php?p=25526654&postcount=3
So could you please advice as to how I can enable usb debugging without normal phone boot so I can copy files on the sd? I downloaded sdk but it will not detect the phone when i'm in recovery mode using the "adb devices" command
if I can copy files to the sd card via command line with adb, what kind of rom can I put and run from there? will I be able to run jb 4.2.2?
Thanks

skopedia said:
finally after many tries, I was able to get cwm recovery 5.5.0.4 by flashing an ICS kernel (jt1134's kernel) from here . not sure why it worked !
http://forum.xda-developers.com/showpost.php?p=25526654&postcount=3
So could you please advice as to how I can enable usb debugging without normal phone boot so I can copy files on the sd? I downloaded sdk but it will not detect the phone when i'm in recovery mode using the "adb devices" command
if I can copy files to the sd card via command line with adb, what kind of rom can I put and run from there? will I be able to run jb 4.2.2?
Thanks
Click to expand...
Click to collapse
You need the Samsung usb driver if you don't have it already (smaller of the two files):
http://www.samsung.com/us/support/owners/product/SGH-I997ZKAATT
(If you installed kies previously, I would recommend uninstalling that and installing only the usb driver)
Once you get adb working, you can follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1667929
to push all the rom packages you need - This will include CM9 plus any of the JB roms you want (follow Andros11's guide once the roms are copied successfully). for first JB rom I recommend going with CM10.1 to ensure the file system conversions are completed correctly - read instructions carefully. In some cases a double flash from CWM may be needed.
Side note - Given the issues you have been having with Heimdall and Odin, it is possible that your USB connection is unreliable. Have you tried different, new, better cables or different USB ports for adb access?

Zen Arcade said:
You need the Samsung usb driver if you don't have it already (smaller of the two files):
http://www.samsung.com/us/support/owners/product/SGH-I997ZKAATT
(If you installed kies previously, I would recommend uninstalling that and installing only the usb driver)
Once you get adb working, you can follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1667929
to push all the rom packages you need - This will include CM9 plus any of the JB roms you want (follow Andros11's guide once the roms are copied successfully). for first JB rom I recommend going with CM10.1 to ensure the file system conversions are completed correctly - read instructions carefully. In some cases a double flash from CWM may be needed.
Side note - Given the issues you have been having with Heimdall and Odin, it is possible that your USB connection is unreliable. Have you tried different, new, better cables or different USB ports for adb access?
Click to expand...
Click to collapse
I never had trouble flashing with odin or heimdall so I know my cable and usb are fine, even though I have tried new PC and usb port and cable before with the same results so I know the issue is with the phone.i haveno keis installed, just USB drivers.
the link you provided call for swm to show unmout system and sdcard, but clicking on them gives me error mounting\system and mounting\sdcard so i'm stuck yet again

skopedia said:
I never had trouble flashing with odin or heimdall so I know my cable and usb are fine, even though I have tried new PC and usb port and cable before with the same results so I know the issue is with the phone.i haveno keis installed, just USB drivers.
the link you provided call for swm to show unmout system and sdcard, but clicking on them gives me error mounting\system and mounting\sdcard so i'm stuck yet again
Click to expand...
Click to collapse
OK - so when you go the the mounts menu, both /system and /sdcard show as unmounted, and when you click on them you get an error? Were you able to get adb working with this recovery? If so, please run "adb shell" then at the prompt run "mount" then mark/paste the output here. That will help confirm whether you have a viable file system on your phone. (If not, that would partially explain why the stock revert packages are not working).

skopedia said:
Hi guys, I have been pulling my hair out trying to figure out how to bring my infuse back to life, I upgraded to GB 2.3.6 from froyo 2.2.1 a while back. a couple of days ago it just died and could not get back in no matter what (constantly rebooting) so I flashed back to stock with "Heimdall One-click Back-To-Stock UCLB3" and it completes just fine but it does not boot normally. it reboots after the AT&T screen.
I read something about the partition been altered when it was updated to 2.3.6, is that a fact? also I'm not able to use recovery (red recovery) to get it to see the external SD card so I'm really stuck, please help
I would love to be able to update to 4.2.2 any rom.
Thanks a bunch
sorry if I'm posting in the wrong section
Click to expand...
Click to collapse
Hey! Check the power button of the infuse i have the ramdomly rebooting problem too i was thinking that i was a rom problem but no the power button of the infuse get dirty from inside and get stock i clean my power button and never have the randomly reboot problem again

Zen Arcade said:
OK - so when you go the the mounts menu, both /system and /sdcard show as unmounted, and when you click on them you get an error? Were you able to get adb working with this recovery? If so, please run "adb shell" then at the prompt run "mount" then mark/paste the output here. That will help confirm whether you have a viable file system on your phone. (If not, that would partially explain why the stock revert packages are not working).
Click to expand...
Click to collapse
Sorry it took so long to respond. I was almost ready to give up, I found this page http://forum.xda-developers.com/showthread.php?t=1767837
where it had a new driver link listed which allowed me to use adb properly on the same pc and usb cable. (before this, it would just say no device attached). I did run the first section on the first post to completion (and flashed froyo refuse_v1.7_cwm.zip)but it still won't boot normally.reboots to recovery screen and it freezes there.)(see photo)
so here are the outputs you requested
/ # mount
mount
rootfs / rootfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=
utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=utf8 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/stl11 /cache rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=
utf8 0 0
/dev/block/stl10 /dbdata rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/ #
I appreciate your help.
I would love to be able to update the to the latest stable rom and also please be specific to what I need to do next.
Thanks

alexischino said:
Hey! Check the power button of the infuse i have the ramdomly rebooting problem too i was thinking that i was a rom problem but no the power button of the infuse get dirty from inside and get stock i clean my power button and never have the randomly reboot problem again
Click to expand...
Click to collapse
I'm afraid my problem was more that just a stuck power button. I have taken the cover off and cleaned what I could but I does not make a deference.
Thanks

skopedia said:
Sorry it took so long to respond. I was almost ready to give up, I found this page http://forum.xda-developers.com/showthread.php?t=1767837
where it had a new driver link listed which allowed me to use adb properly on the same pc and usb cable. (before this, it would just say no device attached). I did run the first section on the first post to completion (and flashed froyo refuse_v1.7_cwm.zip)but it still won't boot normally.reboots to recovery screen and it freezes there.)(see photo)
so here are the outputs you requested
/ # mount
mount
rootfs / rootfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=
utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=utf8 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/stl11 /cache rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=
utf8 0 0
/dev/block/stl10 /dbdata rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/ #
I appreciate your help.
I would love to be able to update the to the latest stable rom and also please be specific to what I need to do next.
Thanks
Click to expand...
Click to collapse
From what you have posted, and from the error messages shown in your picture of recovery after attempting to format the sdcard there are two possibilities:
1 - your internal SD card (which contains /data and /sdcard) is dead
2 - your internal SD card is corrupted
Scenario 1 - try for warranty repair if still covered, or see if a repair shop can help (MobileTechVideos.com gets frequent mentions on XDA as a reasonable option for many infuse4g repairs).
Scenario 2 - if the SD card is corrupted there may be a way back, but it requires advanced steps - using programs such as parted and fdisk to repartition the problem device and reformat the two file systems (/data and /sdcard on the infuse). I'm not aware of a guide specifically for the infuse, but there are some available for the i9000 which might be adaptable. You'll likely need to be running a kernel/recovery combo that includes root/su access to be able to use these tools, plus do some research to determine the correct command syntax. If you are not familiar with linux system-level command line utilities, or the equivalent on windows, it's probably best to skip this option.
Lastly, read through this thread from last year. Similar issues to yours - http://forum.xda-developers.com/showthread.php?t=1581977
One person was able to finally recover by flashing GTG's Odin unbrick package - might be worth a try, perhaps from a different PC if one is available):
thread (instructions) - http://forum.xda-developers.com/showthread.php?t=1116251
mirror (files) - http://d-h.st/7DB
Note that if you are running a newer version of the samsung infuse usb drivers, you may need a newer version of Odin (gtg package references v1.7). I use version 3.07 now, but others report success with 1.85 - here's a link to all Odin versions for download - http://forum.xda-developers.com/showthread.php?t=2189539
Good luck.

[Q] OTA Update for Pantech Discover

I have the Pantech Discover
My phone is rooted because of WiFi issues
It only remembered the first 2 WiFi networks I came across after I bought the phone.
So I did all kinds of stuff to it to fix it. But I apparently screwed something up while fixing it, kind of. lol
Every time my phone restarts I have to go to the WiFi files and change the permissions in order for WiFi to turn on.
Other than that it works like a champ. This however isn't the problem.
I want to start fresh. Factory Rom would be great, but nobody has one.
There is an update to 4.1 jellybean for my phone OTA but It gets an error every time I try to update it.
Is there anything I can do?
ANY suggestions or help would be greatly appreciated
Thanks

TheAtreus said:
I have the Pantech Discover
My phone is rooted because of WiFi issues
It only remembered the first 2 WiFi networks I came across after I bought the phone.
So I did all kinds of stuff to it to fix it. But I apparently screwed something up while fixing it, kind of. lol
Every time my phone restarts I have to go to the WiFi files and change the permissions in order for WiFi to turn on.
Other than that it works like a champ. This however isn't the problem.
I want to start fresh. Factory Rom would be great, but nobody has one.
There is an update to 4.1 jellybean for my phone OTA but It gets an error every time I try to update it.
Is there anything I can do?
ANY suggestions or help would be greatly appreciated
Thanks
Click to expand...
Click to collapse
The update validates that dozens of files in /system including everthing in /system/app is there and unmodified. The user gj23 was kind enough to provide the original ICS /system files here: http://www.mediafire.com/folder/r3n3loxxlrv08/systemext4. I was able to help another user with the same problem get updated and suggest the following procedure.
Do this at your own risk. I do not recommend that you try to replace a file unless you are sure you removed or modified it or it shows up as invalid in the log. This can be tedious but far less tedious and risky than reconstructing the entire /system partition (voice of experience).
NOTE: Download and use the VooDoo OTA Rootkeeper application to temporarily unroot. You can use the app to restore root after the update. If you lose root several users have reported Framaroot 1.6 works with Jellbean, download here: http://forum.xda-developers.com/showthread.php?t=2130276.
Dowload the JB update on the phone and choose to delay the update.
Install an sd card in the phone and using a root explorer copy the update to the external sd card. The update is called gota_package.bin and is in /cache/recovery.
Rename the file you copied to the external sd card to gota_package.zip.
Open the last_log file in the /cache/recovery folder with a text editor, scroll to the bottom, and look for a message indicating which file failed the checksum validation.
Download the valid version of the file that failed from the site I posted above. If there is a file with the same name in the same folder but with a different extension (e.g. myfile.apk & myfile.odex) dowload both.
Using a root explorer copy the file(s) you downloaded to the appropriate directory on your device.
Access recovery mode. To do this shutdown the phone, hold the volume up key and the power key down, when you see "pantech" flash on then off let go of the power button. You should be at the green robot screen, if not try again. From here, hold down power, press up volume, then let go of both. You should see a menu of options if not try again.
Use the volume keys to navigate to the option that allows you to install an update from the external sd card, press power, select gota_package.zip, press power again to run the update.
If the update fails go back to step 4 and repeat the process.
If you know which /system/app files you removed you can download and copy all of them (both apk & odex) at once.
Ask if you have questions.

sandnap said:
The update validates that dozens of files in /system including everthing in /system/app is there and unmodified. The user gj23 was kind enough to provide the original ICS /system files here: http://www.mediafire.com/folder/r3n3loxxlrv08/systemext4. I was able to help another user with the same problem get updated and suggest the following procedure.
Do this at your own risk. I do not recommend that you try to replace a file unless you are sure you removed or modified it or it shows up as invalid in the log. This can be tedious but far less tedious and risky than reconstructing the entire /system partition (voice of experience).
Dowload the JB update on the phone and choose to delay the update.
Install an sd card in the phone and using a root explorer copy the update to the external sd card. The update is called gota_package.bin and is in /cache/recovery.
Rename the file you copied to the external sd card to gota_package.zip.
Open the last_log file in the /cache/recovery folder with a text editor, scroll to the bottom, and look for a message indicating which file failed the checksum validation.
Download the valid version of the file that failed from the site I posted above. If there is a file with the same name in the same folder but with a different extension (e.g. myfile.apk & myfile.odex) dowload both.
Using a root explorer copy the file(s) you downloaded to the appropriate directory on your device.
Access recovery mode. To do this shutdown the phone, hold the volume up key and the power key down, when you see "pantech" flash on then off let go of the power button. You should be at the green robot screen, if not try again. From here, hold down power, press up volume, then let go of both. You should see a menu of options if not try again.
Use the volume keys to navigate to the option that allows you to install an update from the external sd card, press power, select gota_package.zip, press power again to run the update.
If the update fails go back to step 4 and repeat the process.
If you know which /system/app files you removed you can download and copy all of them (both apk & odex) at once.
Ask if you have questions.
Click to expand...
Click to collapse
Can someone provide the gota_package.bin file?

jose makalolot said:
Can someone provide the gota_package.bin file?
Click to expand...
Click to collapse
Uploading gota_package.zip (renamed already), I'll PM you a link in a while.

sandnap said:
Uploading gota_package.zip (renamed already), I'll PM you a link in a while.
Click to expand...
Click to collapse
thank you sir
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4

Wow... Totally lost hope in finding a solution.. I'm not sure which files have been modified due to me allowing apps to try and fix issues with my phone and getting the permissions to "stick" I'll take a look at what you've presented here and try to figure out which files I need to change
Sent from my PantechP9090 using xda app-developers app

attnav.apk first delinquent lol... I removed that soon after rooting.. so no surprise there. Ill let you know how it all goes
Update 1:
currently downloading (slowly) the update file.
While I wait I am checking my phones files with the list of files in the link above.
Ive created a mirror image of the folder structure on my computer where i download all the missing files in the appropriate folders. So far in the apps folder in the "A"s ive deleted 4 files family map.. the stupid driving app attnav and some other att bull..
I knew it would come down to this but wasn't anything I could do without the original files... THANK YOU GUYS sooo much
Update 2:
Final Count in the app folder was 16 missing files... Question. Should I remove the superuser.apk file?

Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.

TheAtreus said:
Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.
Click to expand...
Click to collapse
Well anyone who has this phone and does this... It works GREAT. BTW my root was still in place but superuser temporarily unrooted my phone and had rootkeeper enabled... I just unchecked temp unroot and its back in business...
Still does anyone know how to make the permissions stick... OR could Greg Jennings upload just the wifi files.
I know there are multiple files but all known associated files to the operation of wifi would be great. I was hoping this update would fix the issue but it didnt.

TheAtreus said:
Well anyone who has this phone and does this... It works GREAT. BTW my root was still in place but superuser temporarily unrooted my phone and had rootkeeper enabled... I just unchecked temp unroot and its back in business...
Still does anyone know how to make the permissions stick... OR could Greg Jennings upload just the wifi files.
I know there are multiple files but all known associated files to the operation of wifi would be great. I was hoping this update would fix the issue but it didnt.
Click to expand...
Click to collapse
What exactly do you do to get it working after a reboot? Can you access it with adb? More than likely you just need to mount the partition as read/write before making the changes
---------- Post added at 07:02 AM ---------- Previous post was at 06:50 AM ----------
TheAtreus said:
Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.
Click to expand...
Click to collapse
I updated the tutorial above to address maintaining root or rerooting after the update.

sandnap said:
What exactly do you do to get it working after a reboot? Can you access it with adb? More than likely you just need to mount the partition as read/write before making the changes
---------- Post added at 07:02 AM ---------- Previous post was at 06:50 AM ----------
I updated the tutorial above to address maintaining root or rerooting after the update.
Click to expand...
Click to collapse
I got root back... luckily the superuser app is smarter than me.
When I turn the phone on, it wont even let the wifi turn on for a second... So I go to /data/misc/wifi and change the permission of wpa_supplicant.conf from rw-rw---- to rwxrwxrwx ... but it always reverts back if my phone ever turns off.
There are some other files I do the same way. I am doing this using ES File Explorer. Also that wpa file along with some others have root for the owner and for the group.
Im just tired of having to do that and remembering all the passkeys to all my friends networks because my phone cant.

TheAtreus said:
I got root back... luckily the superuser app is smarter than me.
When I turn the phone on, it wont even let the wifi turn on for a second... So I go to /data/misc/wifi and change the permission of wpa_supplicant.conf from rw-rw---- to rwxrwxrwx ... but it always reverts back if my phone ever turns off.
There are some other files I do the same way. I am doing this using ES File Explorer. Also that wpa file along with some others have root for the owner and for the group.
Im just tired of having to do that and remembering all the passkeys to all my friends networks because my phone cant.
Click to expand...
Click to collapse
If you have adb access to the phone type (hit enter after each line):
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
If you don't have access to adb download the "Android Terminal Emulator" app from the Play Store, open it and type:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
Now, make your permission changes, reboot, and report back. If that doesn't work give me the full path of all files causing the issue and I will write a script that will take care of it.

Alright will do
Sent from my PantechP9090 using xda app-developers app

sandnap said:
If you have adb access to the phone type (hit enter after each line):
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
If you don't have access to adb download the "Android Terminal Emulator" app from the Play Store, open it and type:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
Now, make your permission changes, reboot, and report back. If that doesn't work give me the full path of all files causing the issue and I will write a script that will take care of it.
Click to expand...
Click to collapse
Okay i followed the directions.
I rebooted my phone first
Connected it to my computer after it finished booting
Opened my command prompt
made sure my phone was detected
Ran adb shell (said it was out of date)
Here is a copy of what I did
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p14 /system
[email protected]:/ # mount -o rw,remount /dev/block/mmcblk0p25 /data
mount -o rw,remount /dev/block/mmcblk0p25 /data
[email protected]:/ #
Also here is a list of my mounts after reboot
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,relatime,data=orde
red 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,rel
atime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,relatime,noauto_da
_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatim
e,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000
,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=low
er,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
/dev/block/vold/179:33 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ #
None of what i did before stuck
Here is a list of the files, the status of the files, and what I change on each file.
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O root G root CHANGED TO rwxrwxrwx (i didnt change the owner or group on any of them)
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi CHANGED TO rwxrwxrwx
/data/misc/wifi/wpa_suplicant/wlan0 STAYED AFTER TRYING YOUR FIX it is rwxrwxrwx O wifi G wifi
/dev/network_latency rw-rw---- O root G root CHANGED TO rwxrwxrwx
/dev/network_throughput rw-rw---- O root G root CHANGED TO rwxrwxrwx
/dev/wcnss_wlan rw-rw---- O root G root CHANGED TO rwxrwxrwx
After reboot they all except the one I told you about changed back.
I honestly dont know what files do what for wifi... so I just changed these try and make the networks STICK... All I need to do to get wifi to actually turn on and act right is change that first file and it will turn on and take a network passkey and continue working until phone reboots. then i have to change the permissions again and re-enter the passkey for the networks.

Just read that wifi is controlled by the kernel.. When I rooted my phone (using the guide found here at xda ultimate... ) I believe it had the original ics kernel. Would that help?
Sent from my PantechP9090 using xda app-developers app

If you need any more information just let me know
Sent from my PantechP9090 using xda app-developers app

The permissions and ownership for the same files on my JB discover are:
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O system G wifi
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi
/data/misc/wifi/wpa_suplicant/wlan0 rwxrwx--- O wifi G wifi
/dev/network_latency rw------- O root G root
/dev/network_throughput rw------- O root G root
/dev/wcnss_wlan rw------- O root G root
It looks like the ownership is different for the first file but you have the same ownership and equal or looser permissions on the rest of the files. Try changing the ownership of wpa_supplicant.conf:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /data
chown system:wifi /data/misc/wifi/wpa_supplicant.conf
exit
exit
adb reboot

sandnap said:
The permissions and ownership for the same files on my JB discover are:
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O system G wifi
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi
/data/misc/wifi/wpa_suplicant/wlan0 rwxrwx--- O wifi G wifi
/dev/network_latency rw------- O root G root
/dev/network_throughput rw------- O root G root
/dev/wcnss_wlan rw------- O root G root
It looks like the ownership is different for the first file but you have the same ownership and equal or looser permissions on the rest of the files. Try changing the ownership of wpa_supplicant.conf:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /data
chown system:wifi /data/misc/wifi/wpa_supplicant.conf
exit
exit
adb reboot
Click to expand...
Click to collapse
That worked half way. Now I dont have to change any permissions in order to get wifi to turn on but now I have to enter in the passkey for the network every 3 minutes or so because it wipes it or something
UPDATE
Im the type to just fiddle with stuff till it works.. While this hasn't really fixed my issue it might explain whats going on more to you that know the inner workings of Android linux OS better than i do. After I type the passkey in for my wifi network I wait for it to connect and before it shuts off on me I restart my phone... I tried it with the regular connection I have and after that I was think OH maybe it just needed to restart to fix it so i tested with my 5G connection. I put the passkey in and turned my wifi off and then back on it lost the info for 5G and still had the regular... So I typed it in again and restarted my phone and now both are stored permanently (i assume)

TheAtreus said:
That worked half way. Now I dont have to change any permissions in order to get wifi to turn on but now I have to enter in the passkey for the network every 3 minutes or so because it wipes it or something
UPDATE
Im the type to just fiddle with stuff till it works.. While this hasn't really fixed my issue it might explain whats going on more to you that know the inner workings of Android linux OS better than i do. After I type the passkey in for my wifi network I wait for it to connect and before it shuts off on me I restart my phone... I tried it with the regular connection I have and after that I was think OH maybe it just needed to restart to fix it so i tested with my 5G connection. I put the passkey in and turned my wifi off and then back on it lost the info for 5G and still had the regular... So I typed it in again and restarted my phone and now both are stored permanently (i assume)
Click to expand...
Click to collapse
So it seems to be okay for now? It's strange that it wipes after a few minutes. In Settings > Backup & Reset do you have the "Back up my data" checkbox checked? It's a long shot but I wonder if it's synchronizing with the google server and your settings are being overwritten. If you have this selected you can try unchecking it. Have you tried doing a factory data reset?
On a different topic, have you tried booting to the recovery-evita.img since you updated to Jellybean? I am pretty sure they locked the bootloader with the JB update but wanted to confirm with others.

sandnap said:
So it seems to be okay for now? It's strange that it wipes after a few minutes. In Settings > Backup & Reset do you have the "Back up my data" checkbox checked? It's a long shot but I wonder if it's synchronizing with the google server and your settings are being overwritten. If you have this selected you can try unchecking it. Have you tried doing a factory data reset?
On a different topic, have you tried booting to the recovery-evita.img since you updated to Jellybean? I am pretty sure they locked the bootloader with the JB update but wanted to confirm with others.
Click to expand...
Click to collapse
This is what I got when I tried
C:\Users\Atreus\Downloads>fastboot devices
6603452b fastboot
C:\Users\Atreus\Downloads>fastboot boot recovery-evita.img
downloading 'boot.img'...
OKAY [ 0.640s]
booting...
FAILED (remote: Not Support !!)
finished. total time: 0.656s
C:\Users\Atreus\Downloads>
So it looks like they patched that... If somebody wanted root their phone like our. they would need to revert back to ICS do you know how to do that?

Htc sensation boot went to hell

Hi. This is my first post and I hope I didn't have to post in some other section just for present myself, since I'm doing it now.
Anyway, I tried to flash a new rom since my HTC Sensation (no 4g nor XE) was totally stucked. I even installed the minimum software that I needed, and the result was a phone that could barely make calls.
So I did a backup of all my datas, then proceeded to a factory reset.
After that I followed the procedure on the htcdev website to unlock the bootloader and everything went smooth.
The first problem happened when, following a video explanation of a french guy that didn't say that I needed a wire, I had to improvise with what I could find at a late time in the night, and it was some iron wire insulated with some paper. At first the phone reeboted but not like I needed, and the following tries were totally useless so I used that software called rumrunner that claims to do be able to turn S-OFF without the wire trick.
I don't really know if it worked or not: I have S-OFF but during the process in the cmd there was "WTF: what are you doing" and "process stopped" even if I didn't touch anything.
Anyway, let's assume that I have S-OFF:
I then tried to flash the recovery 4-EXT using a software called like "Sensation_All-In-One_Kit_v3.1". I didn't noticed any significant change, nor the other functions were working properly since everything said "phone not found". So I used cmd and flashed "recovery-clockwork-touch-5.8.0.9-pyramid" and it worked flawlessy.
Then I rooted the phone using the recovery and installing from the sdcard the file "su-2.3.6.3-efgh-signed".
Then I downloaded cm12.1 by ivanich and installed it, but I forgot to do a backup before that and when I turned on the phone, nothing was loading. It was a black screen with the superior bar. The touch was not working, the on/off button the same. So I reopened the recovery, wiped out the data and cache to factory reset, and did again the SU and custom SO install.
Now the phone boots but it's again the factory reset version, not the one that I installed. I see that from all the bloatware still there. Also, its version is wrong. It's android 4.0.3, while there wasn't that version when it was produced.
I need help.
edit: I found out that when I try to install the rom I get only errors saying :
[the first part is missing since I can't scroll up]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: no such device
unmount of /data failed; no such volume
patching system image unconditionally...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
script succeded: result was [0.200000]
Install from sdcard complete.
FINAL EDIT:
I searched in many places for help. I found the man in a IRC chat. Seems that I had to change the recovery app and install twrp. Then it worked flawlessy.

Ciome said:
Hi. This is my first post and I hope I didn't have to post in some other section just for present myself, since I'm doing it now.
Anyway, I tried to flash a new rom since my HTC Sensation (no 4g nor XE) was totally stucked. I even installed the minimum software that I needed, and the result was a phone that could barely make calls.
So I did a backup of all my datas, then proceeded to a factory reset.
After that I followed the procedure on the htcdev website to unlock the bootloader and everything went smooth.
The first problem happened when, following a video explanation of a french guy that didn't say that I needed a wire, I had to improvise with what I could find at a late time in the night, and it was some iron wire insulated with some paper. At first the phone reeboted but not like I needed, and the following tries were totally useless so I used that software called rumrunner that claims to do be able to turn S-OFF without the wire trick.
I don't really know if it worked or not: I have S-OFF but during the process in the cmd there was "WTF: what are you doing" and "process stopped" even if I didn't touch anything.
Anyway, let's assume that I have S-OFF:
I then tried to flash the recovery 4-EXT using a software called like "Sensation_All-In-One_Kit_v3.1". I didn't noticed any significant change, nor the other functions were working properly since everything said "phone not found". So I used cmd and flashed "recovery-clockwork-touch-5.8.0.9-pyramid" and it worked flawlessy.
Then I rooted the phone using the recovery and installing from the sdcard the file "su-2.3.6.3-efgh-signed".
Then I downloaded cm12.1 by ivanich and installed it, but I forgot to do a backup before that and when I turned on the phone, nothing was loading. It was a black screen with the superior bar. The touch was not working, the on/off button the same. So I reopened the recovery, wiped out the data and cache to factory reset, and did again the SU and custom SO install.
Now the phone boots but it's again the factory reset version, not the one that I installed. I see that from all the bloatware still there. Also, its version is wrong. It's android 4.0.3, while there wasn't that version when it was produced.
I need help.
edit: I found out that when I try to install the rom I get only errors saying :
[the first part is missing since I can't scroll up]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: no such device
unmount of /data failed; no such volume
patching system image unconditionally...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
script succeded: result was [0.200000]
Install from sdcard complete.
FINAL EDIT:
I searched in many places for help. I found the man in a IRC chat. Seems that I had to change the recovery app and install twrp. Then it worked flawlessy.
Click to expand...
Click to collapse
you just had a very old version of recovery
i assume that guy gave you the proper twrp because there is a false one which messes up with emmc after using wipe option

rzr86 said:
you just had a very old version of recovery
i assume that guy gave you the proper twrp because there is a false one which messes up with emmc after using wipe option
Click to expand...
Click to collapse
No he just told me to get the last version for my phone.

Ciome said:
No he just told me to get the last version for my phone.
Click to expand...
Click to collapse
actually i am saying the same thing