Related
This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor
Yes this try to keep this thread open.
Sent From My Evo Killer!
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force
forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.
olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.
Duplicate... Sorry
forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted
Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3
Im trying to install an OC kernel on my NC running CM7.... but its not working. I install it and everything goes correctly, but i cannot surpass the 925 OC on CM7, even though it can go up to 1000ghz and 1100ghz.
Im using update-CM7-dalingrin-OC-sd-042411.zip from dalingrins..
The "official" OC kernel thread is here:
http://forum.xda-developers.com/showthread.php?t=925451
Not sure what to do or how the OC kernels work. He says to use CM7 settings to overclock, but the highest it goes up to is 925, which seems to be stock for that. Let me know if you can helppppp!
Thanks, Bobby
AEBobby912 said:
Im trying to install an OC kernel on my NC running CM7.... but its not working. I install it and everything goes correctly, but i cannot surpass the 925 OC on CM7, even though it can go up to 1000ghz and 1100ghz.
Im using update-CM7-dalingrin-OC-sd-042411.zip from dalingrins..
The "official" OC kernel thread is here:
http://forum.xda-developers.com/showthread.php?t=925451
Not sure what to do or how the OC kernels work. He says to use CM7 settings to overclock, but the highest it goes up to is 925, which seems to be stock for that. Let me know if you can helppppp!
Thanks, Bobby
Click to expand...
Click to collapse
Are you installing the correct kernel for your install? EMMC vs. SD?
Are you installing the kernel itself & not the MD5 file on the kernel page?
What versions of recovery and CM7 are you using?
hockeyfamily737 said:
Are you installing the correct kernel for your install? EMMC vs. SD?
Are you installing the kernel itself & not the MD5 file on the kernel page?
What versions of recovery and CM7 are you using?
Click to expand...
Click to collapse
I installed the SD kernel, and it installed fine....but nothing new showed up.
I installed the EMMC kernel, which was a bad idea...and just didnt load up CM7.
I installed the kernel itself, and put it on the root of the SD card, flashed it, cleared the cache and dalvic, but it still says i have the stock kernel that came with CM7
I have CM7.0.2-encore...im using an 8Gb class 6 SD card.
I also tried kernel manager from the market...and tried installing the kernel that way but it literally reset my device to the stock 1.2 update with no CM7....it was wierd, so wont be doing that ever again. Im restoring everything now so ill be back to where i started. Its OC at 925 now, but cant go up any higher which means im not installing the kernel correctly....ughhhh
AEBobby912 said:
I installed the SD kernel, and it installed fine....but nothing new showed up.
I installed the EMMC kernel, which was a bad idea...and just didnt load up CM7.
I installed the kernel itself, and put it on the root of the SD card, flashed it, cleared the cache and dalvic, but it still says i have the stock kernel that came with CM7
I have CM7.0.2-encore...im using an 8Gb class 6 SD card.
I also tried kernel manager from the market...and tried installing the kernel that way but it literally reset my device to the stock 1.2 update with no CM7....it was wierd, so wont be doing that ever again. Im restoring everything now so ill be back to where i started. Its OC at 925 now, but cant go up any higher which means im not installing the kernel correctly....ughhhh
Click to expand...
Click to collapse
Ok. If you were previously running a recent nightly build you should have also wiped system & data. Also check your version of recovery. Current version of Clockwork Recovery is 3.0.2.8....What version are you using? I had tons of problems with kernels over the weekend using and older version of recovery that I was too lazy to update. I updated it and my troubles went away.
hockeyfamily737 said:
Ok. If you were previously running a recent nightly build you should have also wiped system & data. Also check your version of recovery. Current version of Clockwork Recovery is 3.0.2.8....What version are you using? I had tons of problems with kernels over the weekend using and older version of recovery that I was too lazy to update. I updated it and my troubles went away.
Click to expand...
Click to collapse
Im using CWM version 3.0.0.5....so im guessing that is outdated.....do you know where i can find the link to download the latest version of it??? thanks sooo much. Once i get it ill try to reinstall the zip of the kernel i want and see if it works
AEBobby912 said:
Im using CWM version 3.0.0.5....so im guessing that is outdated.....do you know where i can find the link to download the latest version of it??? thanks sooo much. Once i get it ill try to reinstall the zip of the kernel i want and see if it works
Click to expand...
Click to collapse
That you'll have to search for my friend. My install is to EMMC not SD and I've never really followed those processes. When you find it though, be sure to add it to your thread so that others may find the info as well.
AEBobby912 said:
Im using CWM version 3.0.0.5....so im guessing that is outdated.....do you know where i can find the link to download the latest version of it??? thanks sooo much. Once i get it ill try to reinstall the zip of the kernel i want and see if it works
Click to expand...
Click to collapse
[RECOVERY] Making an updated (3.0.2.8) bootable ClockworkMod SD
http://forum.xda-developers.com/showthread.php?t=987735
Might be useful?
Also, can't you just download and flash latest version using Rom Manager?
having similar issues
I have CM7 7.0.2 installled to emmc, but everytime I try installing overclocking update I just get a blank screen after I reboot. Waited five min and nothing happened. This has happened twice so far. I have a 3.0.2.8 CWM SD and am able to rollback my nandroid after this happens. Not sure I'm doing wrong. I tried install 4/4 emmc update, do I need to install 4/24? Or is there another issue with my install? Do I need to install CWM to recovery? Tried wiping cache and dalvik cache as well before installing. Thanks a lot.
nondescriptus said:
I have CM7 7.0.2 installled to emmc, but everytime I try installing overclocking update I just get a blank screen after I reboot. Waited five min and nothing happened. This has happened twice so far. I have a 3.0.2.8 CWM SD and am able to rollback my nandroid after this happens. Not sure I'm doing wrong. I tried install 4/4 emmc update, do I need to install 4/24? Or is there another issue with my install? Do I need to install CWM to recovery? Tried wiping cache and dalvik cache as well before installing. Thanks a lot.
Click to expand...
Click to collapse
You have a slightly different problem. Is it a blank screen, or do you have an under score "_" in the top right hand corner?
Oops, Meant to say do i need to install CWM to emmc?
nondescriptus said:
Oops, Meant to say do i need to install CWM to emmc?
Click to expand...
Click to collapse
Nondescriptus,
read through this thread and see if it clears things up for you...
http://forum.xda-developers.com/showthread.php?t=1070258
You are the cooo cooolest
angomy said:
[RECOVERY] Making an updated (3.0.2.8) bootable ClockworkMod SD
http://forum.xda-developers.com/showthread.php?t=987735
Might be useful?
Also, can't you just download and flash latest version using Rom Manager?
Click to expand...
Click to collapse
Yeah i had someone post that earlier....i forgot that was there....thats exactly what i needed, and i forgot ROM manager did that....so i did both. Im gonna try that and flash the 4/24 SD kernel and see if thats what i needed. Thankssss buddy!
I get a blank screen after I reboot.
hockeyfamily737 said:
Nondescriptus,
read through this thread and see if it clears things up for you...
http://forum.xda-developers.com/showthread.php?t=1070258
Click to expand...
Click to collapse
Thanks, I read the thread, but to confirm I need to have CWM on emmc in order to overclock and can't flash via CWM SD? Thanks again.
nondescriptus said:
I get a blank screen after I reboot.
Click to expand...
Click to collapse
Ok. Try that link I gave you. It was a walk through I did with someone last night. It is a solid 1st step for your EMMC install.
http://forum.xda-developers.com/showthread.php?t=1070258
***Duhhh*** We just posted at the same time. Ignore this post.
nondescriptus said:
Thanks, I read the thread, but to confirm I need to have CWM on emmc in order to overclock and can't flash via CWM SD? Thanks again.
Click to expand...
Click to collapse
Clockwork on EMMC will make your life much easier for everything. Flashing new roms, backing up, restoring, rebooting to recovery without having to change SD cards, etc...
That being said, I personally keep an sd card imaged with recovery, a rom, and gapps for uhh oh's, when I have to start over.
Follow that thread, first trying to use recovery from EMMC (if you can access it), if you can't access it use a bootable recovery sd (your uh oh card).....Some people say just wipe cache & dalvik, but the current CM7 nightlies and stable builds don't play nice when swapping back and forth.
Still dont know how to install the freakin kernellllll.UGHH>
So i updated my sd card to CMW 3.0.28, which is the newest. I downloaded the 4/24 SD kernel file and put it on the root of my SD. Backed up everything, flashed the kernel, wiped the cache and dalvic, rebooted the phone....and everything works like usual, except i still dont have the kernel apparently. In the Cm7 settings it still only goes up to 925 and in the info about the tablet it has kernel version 2.6.29-omap 1.....which is def not the one i flashed....any help?
P.S. im about to give up
P.P.S......not really lol.
AEBobby912 said:
So i updated my sd card to CMW 3.0.28, which is the newest. I downloaded the 4/24 SD kernel file and put it on the root of my SD. Backed up everything, flashed the kernel, wiped the cache and dalvic, rebooted the phone....and everything works like usual, except i still dont have the kernel apparently. In the Cm7 settings it still only goes up to 925 and in the info about the tablet it has kernel version 2.6.29-omap 1.....which is def not the one i flashed....any help?
P.S. im about to give up
P.P.S......not really lol.
Click to expand...
Click to collapse
Another idea....try downloading the kernel again. Could have been a corrupt download. If you've got everything backed up.....wipe system, data, cache, & dalvik then install your kernel through Clockwork (install .zip). Then make sure you allow enough time for your machine to boot fully, before you try adjusting you CM7 settings. Worst case scenario is that you have to restore your backup.
hockeyfamily737 said:
Another idea....try downloading the kernel again. Could have been a corrupt download. If you've got everything backed up.....wipe system, data, cache, & dalvik then install your kernel through Clockwork (install .zip). Then make sure you allow enough time for your machine to boot fully, before you try adjusting you CM7 settings. Worst case scenario is that you have to restore your backup.
Click to expand...
Click to collapse
OK i will try that and let you know....Thanks!
AEBobby912 said:
OK i will try that and let you know....Thanks!
Click to expand...
Click to collapse
Did U try Kernel Manager app?
I am on stock ICS LPA Rom with GL_NOTECORE Kernel (Safe Kernel). Everything was fine for a week with this combo. Today morning i noticed that the phone was not going in to deep sleep and so tried the old trick (Airplane mode, battery remove restart) and BHOMM my phone is stuck in the Boot. It is not passing the samsung logo.
Tried Delvik and Cache cleaning. Did not do a factory reset even thou its a safe kernel as i dont want to risk anything.
Flashed Stock ICS LPA flash via PC Odin. But noting is happeing. Can anyone help?
Solution Flashed GB and All is Well!
Most of, the best way is to flash a new kernel on this case..... Doing jbroid cleaning script before and then flash another safe kernel, maybe speedmod. This will help in most cases..... For the next time..... I got the same issues one time, after flashing cf Kernel, it was okay.......
That's not a brick or else, just some startup data is crashed, so system can't boot forward on any point.......
Greetz
Sts
Sent from my GT-N7000 using Tapatalk 2
atonal said:
Most of, the best way is to flash a new kernel on this case..... Doing jbroid cleaning script before and then flash another safe kernel, maybe speedmod. This will help in most cases..... For the next time..... I got the same issues one time, after flashing cf Kernel, it was okay.......
That's not a brick or else, just some startup data is crashed, so system can't boot forward on any point.......
Greetz
Sts
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
+1
I had the same issue, I flashed Fronco Kernel (the latest), reboot and my Note started, then I reflashed GL_NOTECORE Krenel.
Good luck.
Djoudi
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
jpeclf said:
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your help but seeing as your phone is an Android phone, I don't think the same process applies. But thanks for the effort, I have this baby up and running now.. I just had to reflash the ROM.. Thanks again :good:
FocusHelp said:
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
Click to expand...
Click to collapse
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Be VERY sure you flash the correct ROM for your phone. If you have a version 1.3, then ONLY flash 1.3 ROMs to it. If you have a version 1.4, then ONLY flash 1.4 ROMs to it. You can find the version number under the battery on the sticker. If you flash the wrong version of ROM to it, you will end up with a brick.
When having problems like this, I would recommend flashing the Stock ROM to it first to set everything back to normal. Then, if that works fine, go to custom ROMs if desired. Stock flashing will replace everything back to new settings, including spl, radio, etc... Some of the custom ROMs are truly worth flashing, FASTER, stable, nice features.
Unokashi01 said:
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Click to expand...
Click to collapse
I know I had 3.05a and reflashed 3.10a Clean Rom.. It works great now... I remember I use to have problems with the 3g but not after reflashing it works great
Here's what I have
-i337
-4.4.2 Rom
-KT Kernel
Here's what happened:
-Last night, battery was down to about 10% when I got home (Long sunday). By the time I put it on the charger it was at 7%, but my charger was faulty prior to this instance (It had to be held in at the right angle to keep a connection, charger issue because the others I have at the office work fine).
-Woke up and the phone was stuck in a bootloop. It was like that all night, Battery Symbol will show up empty, and then go into a bootloop at the animation screen.
-Got to work, started charging it in Recovery, it was the only way to charge it without going through the bootloop.
What I have tried:
-Tried doing a Wipe of Cache/Dalvik - still happened
-Tried Deleting the Batterystats.bin file from Data/System - Still bootlooping
-Tried fixing permissions - Nope
I then created a Nandroid of my current system as I didn't have one made for this rom.
Now I'm at the point where I feel like I may only have two choices:
1.) Wait for it to charge to 100% and try the Batterystats delete again
2.) Reinstall the Nandroid I made, even though it may still contain the corrupted file that's causing the bootloop.
Now I ask, of those two possible steps, would you do one or do you have another solution that I could follow?
Yes, it is urgent because my phone is half of my work here. Thank you for reading!
Try flashing different Kernel. ... it might help with bootlooped
Swyped from MK2 Deadly Venom SS
ted77usa said:
Try flashing different Kernel. ... it might help with bootlooped
Swyped from MK2 Deadly Venom SS
Click to expand...
Click to collapse
Just tried installing another ktweaker kernel I had, still no dice. I can't get my phone to mount the usb from recovery so downloading a new kernel isn't happening.
I'm going to try and restore the nandroid I made, and if that doesn't work I'll just restore an older nandroid from the 4.2 rom I had previously.
Goliath27 said:
Just tried installing another ktweaker kernel I had, still no dice. I can't get my phone to mount the usb from recovery so downloading a new kernel isn't happening.
I'm going to try and restore the nandroid I made, and if that doesn't work I'll just restore an older nandroid from the 4.2 rom I had previously.
Click to expand...
Click to collapse
You can try to put the kernel in a sdcard.
Sent from my GT-I9505G using Tapatalk
Strategikqc said:
You can try to put the kernel in a sdcard.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Working on that now. I can't get TWRP to mount so I can access it through my pc. I'm in the process of updating my drivers again to see if that changes.
Any kernel I should try just in case the one I have reproduces the same issue (as in a different kernel from a different source?)
Goliath27 said:
Working on that now. I can't get TWRP to mount so I can access it through my pc. I'm in the process of updating my drivers again to see if that changes.
Any kernel I should try just in case the one I have reproduces the same issue (as in a different kernel from a different source?)
Click to expand...
Click to collapse
ok I'm back on an old 4.2.2 rom I had a nandroid of. It loaded up just fine.
Now, I have the nandroid of the 4.4 that kept failing. Any way to fix that so I can restore it without having to reinstall it all over again ?
Edit: fixed my problem by flashing the rom again, and then using nandroid manager to restore everything from my bad nandroid.
Now to make a good copy.