I tried the CM updater, like I have been for the nightlies, except, now I'm stuck and a bootloop and I can't get into recovery. I go from the bootloader and select recovery and it takes me to the same screen that the updater does where it says:
Updating partition details....
Running boot script....
Finished running boot script.
Installing zip file '/sdcard/cmupdater/cm-10-20121110-NIGHTLY-evita.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
This is the screen I get every time I flash nightlies, then I reboot and my phone boots normally, but, now when I do this, it puts me in a bootloop (HTC screen comes up, goes dark, no Cyanogen screen, then reboots to the HTC screen and goes to a dark screen...you get the point)...any thoughts on what I need to do to get my phone to work again?
CM10 Nightlies 20121110
First of all I love CM but Ive been having an issue with it. Ok so I flash the rom everything goes fine as far as that goes but Im having call issue. I can hear the person Im calling but that person cannot hear me. When I put the caller on speaker I cant hear him and that person still cant hear me, then the phone freezes. Im no developer but i have flashed plenty of roms so Im literate to this stuff. Some help or tips would be great as I love CM10 and havent been able to use any CM10 based roms they all do the same. I have an At&t One X unlocked, rooted, unlocked bootloader 1.14...
Rising32 said:
First of all I love CM but Ive been having an issue with it. Ok so I flash the rom everything goes fine as far as that goes but Im having call issue. I can hear the person Im calling but that person cannot hear me. When I put the caller on speaker I cant hear him and that person still cant hear me, then the phone freezes. Im no developer but i have flashed plenty of roms so Im literate to this stuff. Some help or tips would be great as I love CM10 and havent been able to use any CM10 based roms they all do the same. I have an At&t One X unlocked, rooted, unlocked bootloader 1.14...
Click to expand...
Click to collapse
Try flashing the previous boot.img then install the latest nightly. I've seen a few people have problems and that normally fixes it.
If that doesn't fix, re download the latest nightly and flash it. Could be a bad dl
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
I had the same problem just like u. I flashed back to 1109.
Sent from my One X using xda app-developers app
So every time I get a newer version of CM10 do I need to flash the boot.IMG first then flash the ROM or is it OK just to flash the ROM with my existing boot.IMG? I mean does the boot.IMG change? I have been just flashing the zip file without the boot.IMG just keeping the original boot.IMG from one of last months update.
Sent from my One X using xda app-developers app
always flash boot.img with any new build, unless your using a custom kernel
cm10 call issue
Myrder said:
Try flashing the previous boot.img then install the latest nightly. I've seen a few people have problems and that normally fixes it.
If that doesn't fix, re download the latest nightly and flash it. Could be a bad dl
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Click to expand...
Click to collapse
So ur saying flash the previous nightly's boot image??? Thanks if that's the case then I will try it and report back. I've tried several CM10 based Rome they all have the same issue... Is it just my phone??? Is it something in the CM code that needs to be fixed? I mean one Rom is one thing but every one Ive tried so far lol. That's what I get for loving asp lol.
---------- Post added at 02:49 AM ---------- Previous post was at 01:52 AM ----------
Myrder said:
Try flashing the previous boot.img then install the latest nightly. I've seen a few people have problems and that normally fixes it.
If that doesn't fix, re download the latest nightly and flash it. Could be a bad dl
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Click to expand...
Click to collapse
Well I tried ur suggestion and nothing... re-downloaded the lates nighty and used previous boot image, nothing. Wiped cache and reflashed the rom and still nothing.
Related
Hey, I'm new to this forum, if im posting in the wrong section , plz move this. Thanks
I wanted to install a more stable rom on my Evo 3D. The rom I wanted is called TweakedSynergy rom. I go to Rom Manager, then click "install ROM from SD Card". I chose the "Synergy-3CVO_RLS1_08-21-11(NIGHTLY)". Rom Manager askes me to backup ROM + Wipe Data and Cache+ Wipe Dalvik Cache" i chose to wipe data and cache. My phone then reboots into recovery where CM starts to do its magic. but once it opens the file on the SD, Every time it tries to install it , it gives me an abort error like this one...
( view pic )
If any one knows what's causing this...please help me out.
Thanks
Sent from my HTC
what version of CM are you using? i wasnt able to flash my 3d with any new versions, so try reverting back to CM 4.0.1.4. that may prove helpful if you are having the same problem i was. mine wouldnt even boot into recovery. after telling it to flash, it would just reboot normaly without ever getting into CW. you may also want to try TWRP. i have been having better luck with that for the past few days. hope that helps
3rdsurfer said:
what version of CM are you using? i wasnt able to flash my 3d with any new versions, so try reverting back to CM 4.0.1.4. that may prove helpful if you are having the same problem i was. mine wouldnt even boot into recovery. after telling it to flash, it would just reboot normaly without ever getting into CW. you may also want to try TWRP. i have been having better luck with that for the past few days. hope that helps
Click to expand...
Click to collapse
I'm using 5.0.2.0, of CWM. How would I downdrade to 4.0.1.4?, and what is TWRP?
I'm going to try flashing a diferent ron and see if I get the same error. If I do ill might do a hard reset of the device reroot then flash synergy...but that's my last option. Don't really want to take that option.
Sent from my HTC EVO 3D X515m using XDA App
TeamWin Recovery Project, they are on version RC2.01 I think; Although I have been running TWRP RC2.0 since it came out just fine.
What Hboot are you running?
Also if your new, I would suggest sticking to Release/Stable builds until you get the hang of it all; Nightlies can be unstable sometimes (Virus' builds are really nice though, I've been using minimalist as my daily driver for weeks now)
wassti said:
TeamWin Recovery Project, they are on version RC2.01 I think; Although I have been running TWRP RC2.0 since it came out just fine.
What Hboot are you running?
Also if your new, I would suggest sticking to Release/Stable builds until you get the hang of it all; Nightlies can be unstable sometimes (Virus' builds are really nice though, I've been using minimalist as my daily driver for weeks now)
Click to expand...
Click to collapse
I'm using 1.5 hboot. I'm going to try using RC.
Ill get back to you on how it turns out.
Sent from my HTC EVO 3D X515m using XDA App
wassti said:
TeamWin Recovery Project, they are on version RC2.01 I think; Although I have been running TWRP RC2.0 since it came out just fine.
What Hboot are you running?
Also if your new, I would suggest sticking to Release/Stable builds until you get the hang of it all; Nightlies can be unstable sometimes (Virus' builds are really nice though, I've been using minimalist as my daily driver for weeks now)
Click to expand...
Click to collapse
my mistake, im on HBOOT version 4.9. If i need to upgrade how do i do so?
also TeamWin Project ver 2.0 , that is only for the HTC Evo CDMA modle not the GSM model witch i have ...
Hahaha, I laugh at my self for this one.
The roms I was trying to install were not meant for my "model" phone.. CDMA & GSM.
I have a GSM model and not a CDMA, I was trying to install a CDMA on a GSM.
Wow I can't believe I could be that stupid...
Lol. Thanks for all the help.
Sent from my HTC EVO 3D X515m using XDA App
I installed a rom. But wifi doesnt work. Opening. .. waiting...
On sensation, used to be flash boot.img and enable smart flash in 4ext recovery and works wifi. But there's not any 4ext recovery for one s
How can i solve wifi problem after install any rom. .
GT-N7100 cihazımdan Tapatalk 2 ile gönderildi
If it is a sense ROM.. and you have hboot 1.14 or higher.. the WiFi partitions won't work.. no real fix other than downgrading your hboot.. not easy and could brick your phone.. I went non_sense ROM and all is good..
Sent a from Jellyrolled One S
Do not downgrade its not safe many clam it is but if heard stories of ville bricking 2-3 weeks after downgrade.
two things that work to fix my wifi and yes im on hboot 1.14.00.4.
when you flash a new rom first use flash image gui app on your currant rom to flash boot img.
if you cant use flash image gui before flashing rom just fastboot the boot img using a pc then after new rom is up and running use flash image gui.
before flashing new rom wipe everything in recovery 3 times yes 3TIMES this does two things removes all traces of old rom and even thought twrp or cwm tells you it wiped it still might of failed. im noob at this but found all these tricks spending many hours reading and reading and reading and reading well you get what im saying. if anyone with more knowledge then me sees something wrong with what ive said feel free to let me know.
If he is using a sense ROM 4.1.2 or newer WiFi will not work period no matter how or what you use to flash it is a widely known issue for hboot 1.14
Sent a from Jellyrolled One S
PAC-Man ROM works very well for me. The only thing that is missing is wifi calling. But I can live without it. Lots of tweaks!
Sent from my HTC VLE_U using xda app-developers app
Unless you really know what you're doing, I wouldn't go downgrading your hboot. I think its more or less a one way street. But I've had no problems with the 2.15 version that came with the jb ota. I'm alternating between various sense and senseless ROMs (currently using the job Nonsense ROM, which is excellent) and have no WiFi issues. As I said to the Dev, no WiFi would be a deal breaker for me.
Sent from my HTC One S using xda app-developers app
I am on Pacman also great ROM..
Sent a from Jellyrolled One S
vuralemre said:
I installed a rom. But wifi doesnt work. Opening. .. waiting...
On sensation, used to be flash boot.img and enable smart flash in 4ext recovery and works wifi. But there's not any 4ext recovery for one s
How can i solve wifi problem after install any rom. .
GT-N7100 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
You may need to upgrade your phones wifi firmwares to work with some (all?) Sense ROMs. Sense ROM's take their wifi firmware from two partitions (18 & 19). However on higher hboot firmwares these partitions are not writable - like a bad joke flashing them will appear to work but won't.
I'm dreaming up a workaround that just might fix this. Trouble is, I cannot replicate the problem - I downgraded my hboot and flashed them and curse it now it's working! You cannot get yours to work and I cannot break mine Please can you tell me your baseband version. settings -> about -> software information -> more.
Good news is that CM10 based ROMs will work out of the box, wifi and radio firmware is baked in the ROM and installed in the filesystem of the phone - so it's easily changed shoud the need arise.
Sofar the only 4.1.1 sense ROM that is playing nice with hboot 1.14 is Virtuous Ville+ I use it on a Tmo USA One S and its flawless. WiFi works perfect.
Sent from my HTC One S Special Edition using xda app-developers app
You guys should check out my thread http://forum.xda-developers.com/showthread.php?t=2151142 for a WiFi fix:thumbup:
The same problem with me..My hboot version:1.14.0002.I flashed extra WiFi partitions but didnt work WiFi.Pease help me
Sent from my HTC One S using xda app-developers app
Hi,
Try the following link
http://forum.xda-developers.com/showthread.php?t=2151142
I use Viper 2.1 and hboot 1.14.004. But, remember to use stock kernel when you flash your Viper rom.
Thank you
Wifi issue on HBoot 1.14 HTC One S SOLVED
hmgurbuz said:
The same problem with me..My hboot version:1.14.0002.I flashed extra WiFi partitions but didnt work WiFi.Pease help me
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Hi
I flashed the Android Sense Best Stock v.3.0 by BehradGH on my TMOU One S with Hboot 1.14 Rooted S-ON This rom rocks so I didn't want to have to get rid of it to get my wifi back...
I've been bummed out and going nuts reading every post from downgrading/upgrading Hboots... to installing linux and going through the process of locking/unlocking.. blah blah blah... I was freaking out!
UNTIL I came upon this post tonight buried deep in the forums... I am admittedly a semi-noob.. well I know just enough to get myself into trouble... and out again haha ... but the post had a link to a .zip file that you can copy onto your internal storage... boot into cwm recovery and simply flash it from there... reboot... and voila... Instant wifi connection! IT WORKS!!
No repartitioning... no flashing radios or anything else...iit takes 3 minutes!
the page is here:
http://forum.xda-developers.com/show....php?t=2151142
The zip file is called "htc_on-s_wifi_fix.zip"
I was skeptical at first... but willing to try anything at this point to get my wifi working on this awesome rom... so i copied it onto my sd card, rebooted into recovery in CWM, ... flashed the zip file, ...rebooted the phone and voila! Instant "wifi It immediately started searching for ip address" (it never got that far before... just said connection problems) ... 2 seconds later it found my network and connected to my in a flash!
My phone is going crazy downloading updates at lightening speeds!! WOOT!!
My sincere apologies to the poster who actually wrote this little script for not being able to thank and acknowledge him for his work... I had like 10 windows open and i couldn't find it... but he is my new hero!!
it's 6:30am in Boston.. sun is coming up... I've been up for 4 days... 24/7 ... going out of my mind trying to fix this... I'm going to sleep for a few days... with my phone charging with the wifi on right next to my head on the pillow
I recently bought my girlfriend a galaxy s II skyrocket. I own one myself. I updated my phone successfully and easily to jellybean through the official CM10. I am well aware of the different methods to install different custom roms to your phone. I received my girlfriend's phone with stock gingerbread. I proceeded to install the stock ice cream sandwich update to the phone through Odin. It was successful. I also installed ClockWorkMod recovery into her phone, the exact same one I had. I continued to attempt to install the same rom that I had on my phone, to my girlfriends phone, CM10. CWM said it was a successful installation after the careful 3x: Factory reset, Cache, Dalvik Cache. Upon rebooting of the phone however, the phone would fail to successfully turn on. It would stay in boot loop mode forever. One time I even left it for an hour and there it was, the boot screen I so dreadfully began to hate. I gave up on CM10, so i began to look for other prospects of a rom. I discovered slim bean. I installed it into my original phone to test it and found it to be of great quality. After I followed the exact same steps I followed to install slim bean to my original phone, to my girlfriends phone, the same result came about; boot loop. After about 20 tries, seriously, I tried to find yet another prospect of a rom. I also discovered another slimmer version of jelly bean for the Skyrocket. Even after the careful following of the steps, I encountered the same result; boot loop. I am beyond frustrated at this point at the fact that I am holding two phones exactly the same, yet when I attempt to install the rom, it only works on one of them. They are both Samsung Galaxy S II Skyrockets model numbers 1727. Both based off of At&t in the United States. One is white while the other one is black. If it makes any bit of a difference the phone I am having trouble with is white. I need help. I've tried everything with no success. I am trying to update this phone to jellybean but it does not seem to accept it, and I have no idea why
Re: [Q] Stuck on boot loop after several different jb roms
TLDR condense give important details that's it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
TLDR condense give important details that's it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Sorry, I am not yet familiar with all the terms. It seems like jargon to me at times lol. TLDR Condense?
Re: [Q] Stuck on boot loop after several different jb roms
Nobody knows what version of cwm you're on.
Nobody knows where you're dl'ing cm10 from.
Quit wiping 3x you only need to do it once.
Don't write novels.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Tldr means to long didn't read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Nobody knows what version of cwm you're on.
Nobody knows where you're dl'ing cm10 from.
Quit wiping 3x you only need to do it once.
Don't write novels.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Tldr means to long didn't read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I've tried installing Official CM10.1 (from XDA) with boot loop result. I've tried installing unofficial 4.2.2 slimbean (from XDA) with boot loop result. I've tried installing Skyjellybean 4.1.2 update 11.4 (from XDA) with boot loop result, and finally I've tried installing Superlite CM10 JB 4.1.2 v8.0 (from XDA) with boot loop result as well. I am currently on stock Ice cream sandwich installed through Odin (links and all found from XDA)
Agree with mtdew.
Keep it as short as possible and be specific.
Get CM10 (not CM10.1 as it's still unstable) from http://get.cm/?device=skyrocket .
Also try latest CWM http://forum.xda-developers.com/showthread.php?t=1777970 .
lingowistico said:
Agree with mtdew.
Keep it as short as possible and be specific.
Get CM10 (not CM10.1 as it's still unstable) from http://get.cm/?device=skyrocket .
Also try latest CWM http://forum.xda-developers.com/showthread.php?t=1777970 .
Click to expand...
Click to collapse
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
s3rgioru3las said:
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
Click to expand...
Click to collapse
That is good news, i'm glad it worked out for you. Good luck. :good:
Help
s3rgioru3las said:
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
Click to expand...
Click to collapse
I too Have a Bad Recovery . Every time i try to install ANY jellybean rom i get stuck in boot loop . I Tried different recovery's and different rom's and stock jellybean and no success . But any ics or gingerbread installs normally . I have a epic 4g touch galaxy 2 and it's rooted . Any new idea's what it could be or how to fix it ? I feel i'm the only person with this problem since i cant find anyone else with the same situation . Your the closets to my problem
Cisco408ca said:
I too Have a Bad Recovery . Every time i try to install ANY jellybean rom i get stuck in boot loop . I Tried different recovery's and different rom's and stock jellybean and no success . But any ics or gingerbread installs normally . I have a epic 4g touch galaxy 2 and it's rooted . Any new idea's what it could be or how to fix it ? I feel i'm the only person with this problem since i cant find anyone else with the same situation . Your the closets to my problem
Click to expand...
Click to collapse
Use the latest recovery in your forum
Sent from my HTC One using Tapatalk 4
I was testing different roms last week. I must have had one flash bad. The phone would boot as normal but when any apps or menus were opened The phone would lock up. Rarely I would get process.android.blah blah blah has stopped, but usually nothing. When I tried tor reboot to recovery it would boot to odin but not CWM. I finally got it to boot to CWM, guessing just a fluke and loaded a different rom. I have tried 4 or 5 roms now all with the same result. If I reboot to recovery prom the power button I can get to CWM. But if I boot to recovery with the volume/power combo 9 out of 10 times I go to odin. I am guessing the kernel got corrupted by the bad flash since it happens with all roms I tried loadig. I am planning on trying to flash a new kernel. Any suggestions on which one will be the best for JMT rom? Or any ather in put? Thanks.
Which one is JMT ROM? Have never heard or seen that ROM on here. Just making sure, do you have an S Blaze 4g?
njstein said:
Which one is JMT ROM? Have never heard or seen that ROM on here. Just making sure, do you have an S Blaze 4g?
Click to expand...
Click to collapse
Jedi mindtrick, sorry. Yes it is a blaze 4g. I am pretty sure I narrowed it down to the kernel. I reloaded Blue Lightning rom and kernel and everything is running smooth. I would like to get back to using jedi mindtrick from ptmr3 since his roms seem to be the only ones built off of tmobile ICS for the wifi calling. When switching should I flash the rom or kernel first?
Venomous Duck said:
Jedi mindtrick, sorry. Yes it is a blaze 4g. I am pretty sure I narrowed it down to the kernel. I reloaded Blue Lightning rom and kernel and everything is running smooth. I would like to get back to using jedi mindtrick from ptmr3 since his roms seem to be the only ones built off of tmobile ICS for the wifi calling. When switching should I flash the rom or kernel first?
Click to expand...
Click to collapse
ROM first then kernel
---------- Post added at 05:40 PM ---------- Previous post was at 05:28 PM ----------
Venomous Duck said:
I was testing different roms last week. I must have had one flash bad. The phone would boot as normal but when any apps or menus were opened The phone would lock up. Rarely I would get process.android.blah blah blah has stopped, but usually nothing. When I tried tor reboot to recovery it would boot to odin but not CWM. I finally got it to boot to CWM, guessing just a fluke and loaded a different rom. I have tried 4 or 5 roms now all with the same result. If I reboot to recovery prom the power button I can get to CWM. But if I boot to recovery with the volume/power combo 9 out of 10 times I go to odin. I am guessing the kernel got corrupted by the bad flash since it happens with all roms I tried loadig. I am planning on trying to flash a new kernel. Any suggestions on which one will be the best for JMT rom? Or any ather in put? Thanks.
Click to expand...
Click to collapse
What version ROMs and gapps were you flashing, and what version CWM are you using?
Venomous Duck said:
Jedi mindtrick, sorry. Yes it is a blaze 4g. I am pretty sure I narrowed it down to the kernel. I reloaded Blue Lightning rom and kernel and everything is running smooth. I would like to get back to using jedi mindtrick from ptmr3 since his roms seem to be the only ones built off of tmobile ICS for the wifi calling. When switching should I flash the rom or kernel first?
Click to expand...
Click to collapse
Ahh yes. Ha! Sorry able that.
I am currently on beanstalk build 275 (android KK), but when I try to reboot into recovery via the power menu, it doesn't work. I am in no way blaming this on the ROM. Instead I am looking for insight. This problem has existed for me since I installed ICS I believe. If I remember correctly, it was working on gingerbread ROMs just fine. Anyway, what happens is the phone proceeds to reboot, but instead of going to recovery after the samsung screen, it proceeds to the boot animation. I have searched around on xda for solutions for rebooting into recovery via the power menu and it seems that in the ICS days, the only way to fix it on ROMs that had this issue was to flash the SGS kernel if I remember correctly in order to get the right recovery and also regain the ability to get into it via all methods. The only problem is that I know that most newer ROMs use scott's modified kernel if I am not mistaken since there wasn't much development for our phone in terms of kernels after ICS. This means that if I take another ROM's boot.img (which I know contains our recovery), it will not change anything since I am basically installing the same kernel. So my question is would I have to go back to ICS in order to fix the problem there first then proceed to flash JB and KK? Thanks for any help or info you guys can provide :good: I hope I can resolve this soon since I find it convenient not having to power off then doing the three finger salute all the time
P.S.: Already asked in beanstalk Q&A also, but I did not get an answer and also I do not believe this problem is ROM related anyway as I said at the start of my paragraph
sorry misread, wrong answer
---------- Post added at 11:43 AM ---------- Previous post was at 11:23 AM ----------
did you download the ROM Manager app from Google Play and try to boot from there?
if it's not working then
I think I would:
put the 255 build and 275 build and Gapps of your choice into SDcard1
then wipe everything on the phone + format the 4 options in advance + format SDcard0
flash 255 + Gapps as per instruction
flash 275 + Gapps per instruction
---------- Post added at 11:48 AM ---------- Previous post was at 11:43 AM ----------
if that's not even working, then I put use the "SGH_I997 Entropy 4_4_2012-One-Click-Heimdall.jar" way
but lets not think of that much trouble - maybe you don't have the right recovery - my version is v6.0.4.7
Go to Developers Options and click on Advanced Reboot.
Sent from my SM-T310 using xda app-developers app
dparrothead1 said:
Go to Developers Options and click on Advanced Reboot.
Sent from my SM-T310 using xda app-developers app
Click to expand...
Click to collapse
The advanced reboot menu is already enabled, what I'm saying is that when i click reboot to recovery, it simply passes the splash screen and proceeds to boot
up normally...
g-noob said:
did you download the ROM Manager app from Google Play and try to boot from there?
if it's not working then
I think I would:
put the 255 build and 275 build and Gapps of your choice into SDcard1
then wipe everything on the phone + format the 4 options in advance + format SDcard0
flash 255 + Gapps as per instruction
flash 275 + Gapps per instruction
---------- Post added at 11:48 AM ---------- Previous post was at 11:43 AM ----------
if that's not even working, then I put use the "SGH_I997 Entropy 4_4_2012-One-Click-Heimdall.jar" way
but lets not think of that much trouble - maybe you don't have the right recovery - my version is v6.0.4.7
Click to expand...
Click to collapse
I'll try the rom manager part and reflashing the different ROMs when i get time and I'll let you know. I already have 6.0.4.7 by the way.
DE52 said:
I am currently on beanstalk build 275 (android KK), but when I try to reboot into recovery via the power menu, it doesn't work. I am in no way blaming this on the ROM. Instead I am looking for insight. This problem has existed for me since I installed ICS I believe. If I remember correctly, it was working on gingerbread ROMs just fine. Anyway, what happens is the phone proceeds to reboot, but instead of going to recovery after the samsung screen, it proceeds to the boot animation. I have searched around on xda for solutions for rebooting into recovery via the power menu and it seems that in the ICS days, the only way to fix it on ROMs that had this issue was to flash the SGS kernel if I remember correctly in order to get the right recovery and also regain the ability to get into it via all methods. The only problem is that I know that most newer ROMs use scott's modified kernel if I am not mistaken since there wasn't much development for our phone in terms of kernels after ICS. This means that if I take another ROM's boot.img (which I know contains our recovery), it will not change anything since I am basically installing the same kernel. So my question is would I have to go back to ICS in order to fix the problem there first then proceed to flash JB and KK? Thanks for any help or info you guys can provide :good: I hope I can resolve this soon since I find it convenient not having to power off then doing the three finger salute all the time
P.S.: Already asked in beanstalk Q&A also, but I did not get an answer and also I do not believe this problem is ROM related anyway as I said at the start of my paragraph
Click to expand...
Click to collapse
I use goo manager app to boot into recovery, always works and is good to go IMO
Judge Joseph Dredd said:
I use goo manager app to boot into recovery, always works and is good to go IMO
Click to expand...
Click to collapse
Ok so I've tried goo manager and also rom manager and neither worked. All that's left is to reflash the ROMs I guess or flash the heimdall package g-noob was talking about although I'm guessing that is a package made for ICS, so I shouldn't flash it with KK. I'll probably just flash back to stock and come back up to really check when the problem occurs as in which android version it starts in. Thanks for your suggestions though I'll report back later this week (probably on the weekend).
DE52 said:
Ok so I've tried goo manager and also rom manager and neither worked. All that's left is to reflash the ROMs I guess or flash the heimdall package g-noob was talking about although I'm guessing that is a package made for ICS, so I shouldn't flash it with KK. I'll probably just flash back to stock and come back up to really check when the problem occurs as in which android version it starts in. Thanks for your suggestions though I'll report back later this week (probably on the weekend).
Click to expand...
Click to collapse
Try Recovery Tools first. Grab it in playstore thats what I use. Give it a shot
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged
eZdubzitmk4 said:
Try Recovery Tools first. Grab it in playstore thats what I use. Give it a shot
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged
Click to expand...
Click to collapse
I installed it and tried the reboot to recovery option which didn't work either in this app. Thanks for suggestion also
Flashing back has worked so far
I flashed back to GB as I said earlier. So far all ROMs have indeed booted into recovery. I guess on my way up the other times, I hadn't followed instructions in detail since I have not experienced any issues that I used to get so far. Hope it keeps going that way anyway once again thanks to everyone for your help! If I have any problems, I'll let you know (currently on Helly Bean 4.2.2 which I just flashed). The real test will come when I flash JB 4.3 and KK which is where I used to have problems booting from power menu.
EDIT: Ok so basically my problems start occurring on jb 4.3. I noticed that going from 4.2.2 to 4.3, the recovery reports a status 7 error. I already know that means the recovery is "old", but the thing is, it allows you to do an install anyway which I usually do in order for it to convert the file system and install the newer recovery which it does. The only thing though is I guess it doesn't repartition correctly due to that status 7 error. So I guess my question would be how I should proceed to get a 4.3 recovery without flashing a ROM or if there's a way to proceed that I am not aware of? Do you happen to have any links @eZdubzitmk4 or @Judge Joseph Dredd or @g-noob ?
sorry, I can't help you as I encountered error 7 so many times and getting to CWM was just sheer luck on my part
maybe you should try flashing CWM community kernel (I am not sure what it does, but it makes me believe that my infuse is unbreakable
http://forum.xda-developers.com/showthread.php?t=1119598
and I did flash everything twice or more than that to make sure everything stick
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
good luck man,
g-noob said:
sorry, I can't help you as I encountered error 7 so many times and getting to CWM was just sheer luck on my part
maybe you should try flashing CWM community kernel (I am not sure what it does, but it makes me believe that my infuse is unbreakable
http://forum.xda-developers.com/showthread.php?t=1119598
and I did flash everything twice or more than that to make sure everything stick
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
good luck man,
Click to expand...
Click to collapse
Haha thanks, it's not so bad anyway. At least I can get into recovery through the manual way (3 buttons) and at least the ROMs install like you said. I was just checking if there was a way to avoid the status 7 which is caused by incompatible partition layout (which is why you flash twice by the way;the second time it ignores the layout and just proceeds). I'll give the link a try by the way.