Related
ok so i rooted a few weeks ago and downloaded the usual apps. super user titanium back up and clock work mod. tried to flash a rom with clock work mod and got the e:signature verification failure message. found a post for a kernal that made clock work mod actually work so i tried to flash a rom. zSimplyAOKPV5_Dark to be exact. now it sticks on boot screen. i have searched for hours and cannot find a way to fix my problem. its my first rooted android and first attempted rom flash and i botched it right off the rip. please help?
Depending on what you did beforehand, you have some options.
If you have backed everything up previously, just flash back to stock with one of the one-click stock roms in the Development section (they're in a sticky).
If you haven't backed everything up, try holding V+/V-/power until it reboots. If it doesn't take you to recovery, you can try to flash a kernel (most likely one that would match the version of android/rom you were running prior to this flash) and see if it lets you into recovery. You'll have to flash it with either Odin or Heimdall, after rebooting into download mode (power off, hold V+/V-, insert USB).
If that doesn't work, though, the stock flashing would probably be your best and/or only bet.
it wont allow me into recovery though i can get to download mode by pulling the battery and pressing just the volume +- and plugging in the usb. i was trying to flash an ics slim rom. thanks for your very speedy response.
i have now tried to flash a stock rom however it is not working from there even with the stock kernal. now it is hanging on the at&t screen.
ok i got it. seems the kernal i flashed to help cwd work properly was the culprit. now i dont know how im going to flash this ics rom im looking at without it.
phoenixfriend said:
it wont allow me into recovery though i can get to download mode by pulling the battery and pressing just the volume +- and plugging in the usb. i was trying to flash an ics slim rom. thanks for your very speedy response.
i have now tried to flash a stock rom however it is not working from there even with the stock kernal. now it is hanging on the at&t screen.
ok i got it. seems the kernal i flashed to help cwd work properly was the culprit. now i dont know how im going to flash this ics rom im looking at without it.
Click to expand...
Click to collapse
Flash corn kernel if you have stock gingerbread
Sent from my SGH-I897
The utility in my signature can help you flash the Corn Kernel so that you will have CWM.
I have corn kernal and odin 3 on the computer at home. Ill do that tonight. Any suggestions on a good stable rom for a noob? Preferably ics. I hated posting for fear of being flamed as a noob. My wife keeps making fun of me for it so I kinda have to get it done. I want to fix hers also. Its a great little phone it just seem a bit buggy to me. Very laggy. Thanks for all the help.
Sent from my SAMSUNG-SGH-I897 using XDA
Maybe start with a KK4 based rom such as Legend and then move up to ICS after that. I only say that because there is a bug in ICS that could render your internal SD unusable. It's rare, but when it happens you will not be happy.
Still unable to get corn kernal to flash. I've tried a few of your guys fixes but I'm gonna have to get some other updates to my computer first.
Sent from my SAMSUNG-SGH-I897 using XDA
i see that the guys working on the jellybean port for the infuse are using cwm 6.0.0.5 or so -- how can i get this installed on my infuse without installing the new jellybean rom (yet) ?
just want to stick with aokp 40 until jellybean is done, but want to play with the cool new touch recovery too...
Some one would have to compile the recovery into the ics kernel....
Sent from my HTC PH39100 using Tapatalk 2
What's so new about it?...........
May want to read this before pulling the trigger.. http://forum.xda-developers.com/showpost.php?p=29037114&postcount=275
hazard66 said:
i see that the guys working on the jellybean port for the infuse are using cwm 6.0.0.5 or so -- how can i get this installed on my infuse without installing the new jellybean rom (yet) ?
just want to stick with aokp 40 until jellybean is done, but want to play with the cool new touch recovery too...
Click to expand...
Click to collapse
I can personally tell you that cwm 6 is not touch...I used it on my vivid and there was no touch...at least the vivid has no touch...ill flash the vivid cwm 6 again just to be sure...
Even better...can someone who has flashed jb say wether or not the cwm has touch?
EDIT: Cwm 6.0.0.5 does not have touch for the HTC vivid...not sure about the infuse though...for the vivid it works just like the old cwm...use volume to navigate, power to choose
Sent from my HTC PH39100 using Tapatalk 2
whether or not cwm has touch enabled or not does not have to do with its version.
The Jack of Clubs said:
whether or not cwm has touch enabled or not does not have to do with its version.
Click to expand...
Click to collapse
yes, i know that as ive seen others with touch...thats why i said not sure about the infuse, the vivid one is built from official cm source so i don't think CWM 6 naturally supports touch...as in touch is enabled by some sort of add on/code edit-i could be wrong as i didn't build it nor have i looked at the source or anything so this is all based off of my observations of the vivid cwm 6
-jack if you've used the cwm from scotts cm10 build can you let us know if it has touch...i would pm scott but hes busy and knowing whether or not a recovery has touch isn't really necessary.
either way...doesn't effect me, im not a fan of CWM any longer and likely will not use it again for flashing roms
enabling touch isnt that hard to do in cwm. if you used the aroma installer on something like aokp on the infuse, youve used touch in cwm on the infuse. i know however its not enabled in the cwm6 thats with the jb rom. its just not a priority to fix right now. but im sure after getting more things working, itll be added one day.
The Jack of Clubs said:
enabling touch isnt that hard to do in cwm. if you used the aroma installer on something like aokp on the infuse, youve used touch in cwm on the infuse. i know however its not enabled in the cwm6 thats with the jb rom. its just not a priority to fix right now. but im sure after getting more things working, itll be added one day.
Click to expand...
Click to collapse
thanks for the reply, yeah...im sure once everything is as stable as ics some one may look into adding touch, ive used aroma before so i know what your talking about there...im buying an infuse in a few hours so i will be able to actually test things out before i reply
as for aroma...i love it and i hate it...its cool that you get to customize your flash some what...but the size of the download can be so huge! especially if its an aroma built for the vivid...stock vivid is 600mb unzipped...zipped and compressed its 400mb add another few hundred megabytes in there for aroma add ons and your looking at one or two roms per gig lol
mg2195 said:
thanks for the reply, yeah...im sure once everything is as stable as ics some one may look into adding touch, ive used aroma before so i know what your talking about there...im buying an infuse in a few hours so i will be able to actually test things out before i reply
as for aroma...i love it and i hate it...its cool that you get to customize your flash some what...but the size of the download can be so huge! especially if its an aroma built for the vivid...stock vivid is 600mb unzipped...zipped and compressed its 400mb add another few hundred megabytes in there for aroma add ons and your looking at one or two roms per gig lol
Click to expand...
Click to collapse
love the touch CWM for the GNote...
http://forum.xda-developers.com/showthread.php?t=1584576
stock Gnote i downloaded was a one click oding 1gig the virgin stock...
Odexed & Stock Rooted, Zipaligned, Deodexed & CRT 600-700mg
most of the GNote custom ROM 600-650...there is work to use the aroma with the GNote again...for the add-ons....its gonna be a whooper...
So is the new CWM suppose to be touched based???
Sent from my SAMSUNG-SGH-I997 using xda premium
slicingtaco said:
So is the new CWM suppose to be touched based???
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Could be wrong...but just based off only official cm source I don't think its touch based...i think the touched based ones have some sort of modification to the cm source
Sent from my HTC PH39100 using Tapatalk 2
http://www.clockworkmod.com/rommanager <- both touch and nontouch recovery are both by clockworkmod. and again, version means nothing towards it. to get touch working in cwm, you just need to load touchscreen modules. theyre just not in any of the infuse versions yet.
Somehow i have cwm 6 while running ics paranoid android. I didn't do it on purpose
MattSoRaven said:
Somehow i have cwm 6 while running ics paranoid android. I didn't do it on purpose
Click to expand...
Click to collapse
With most non-samsung phones recovery is not built into the kernel(actually HTC are the only phones I know like this), its in its on little partion which means you can change kernels without changing recoveries
For the infuse the recovery seems to have always been tied into the kernel so when you flash a kernel you flash a recovery...
Now by you saying that you still have cwm6, that leads to believe that possibly Scott has somehow removed the recovery from the kernel...if that was the case though you'd think there would be problems with the recovery inside the ics kernel...so I'm thinking somehow your still running he jb kernel which somehow can still run ics??? Lol I'm kinda at a lost...that was just me typing my thoughts/thinking outloud/rambling on about recoveries
Makes me curious tho...
Sent from my HTC PH39100 using Tapatalk 2
I think you're right that the recovery was partitioned somewhere and didn't go away. I was on an ics kernel. I believe this based on the build.prop info saying it was a 6/20 kernel, everything worked fine including Wi-Fi, torch, etc.
I was on JB and used Zen's toolkit to "complete wipe" then used the toolkit to restore to PA.
Edit: I flashed the latest yuma kernel because i needed to change this thing asap. I also just noticed multiple kernels have 6/20 as a date. The yuma kernel is signed differently with an "aaron" in the name that the previous kernel didn't have and is has a 6/30. I would have grabbed a screen shot, but i have ppl coming over soon and need to charge it so i can answer calls.
Well matt...here's what Scott had to say, the recovery is not in the kernel...its in recovery (assuming that means in its a seperate partion) so I guess as soon as you get cwm 6 your stuck with it unless you Odin/heimdal back to stock...
Now you wanna hear something interesting/cool? If the recovery is in its own partion then this opens the door for more types of custom recoveries! I was already planing on building an ics kernel with twrp recovery baked in when I get an infuse to work with...the problem with that though is as soon as you flash a Rom you would lose my kernel/twrp...but if Scott has it in its own partion then as soon as there's a twrp for jb I would be able to compile it and not have to worry about it getting erased from flashes..
Here's a video of twrp in action...http://www.youtube.com/watch?v=D2VlpVKj1eI&feature=youtube_gdata_player twrp is my favorite recovery...its fully touch based recovery and you can also theme the recovery as the UI is built with xml codes...really cool-I have it on my vivid...its also based off cwm source...so its just as stable as cwm
EDIT...i like your profile pic/avatar...nothing like some $5 Hot N' Ready large pizzas lol
Sent from my HTC PH39100 using Tapatalk 2
it isnt in the kernel, it is a partition. you cant boot to something inside of a kernel file, that doesnt make sense. you do however need a kernel capable of running whichever version of recovery you want to use. since fastboot is not on this device and many other samsung devices, there is a sort of failsafe in which recovery is written onto the device during system boot. which is why when you flash from a touchwiz rom to aosp rom, you have to let it boot up and freeze, then go back into recovery and flash again. you can look up partition information in recovery.fstab.
The Jack of Clubs said:
it isnt in the kernel, it is a partition. you cant boot to something inside of a kernel file, that doesnt make sense. you do however need a kernel capable of running whichever version of recovery you want to use. since fastboot is not on this device and many other samsung devices, there is a sort of failsafe in which recovery is written onto the device during system boot. which is why when you flash from a touchwiz rom to aosp rom, you have to let it boot up and freeze, then go back into recovery and flash again. you can look up partition information in recovery.fstab.
Click to expand...
Click to collapse
Actually...recoveries are built into the kernel...why else would you get red cam by flashing entropies gb kernel zimage
And as you can see in the picture (twrp Samsung github) they even state that most Samsung's must have recovery built into kernel..
Now it may be different with aosp Roms...but for normal stock Roms and stuff, i know for a fact that kernels contain the recovery...
Sent from my HTC PH39100 using Tapatalk 2
hrm. maybe its some kind of uimage. dunno, doesnt really apply to the infuse though.
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.
Hello everyone,
Ive seem to run into some trouble, that I cant find a solution too.
I rooted my phone with Gingerbreak V1.20, and flash my recovery with CWM.
I proceeded to add the Nightly Four E rom, than the trouble began.
My colors on the phone display are diffused and distorted, mainly showing the color green and blue.
I read thatI need to flash the stock 2.2 rom again and it would fix it but it didnt.
Can someone help me with this, its quite annoying.
Trytohaxme said:
Hello everyone,
Ive seem to run into some trouble, that I cant find a solution too.
I rooted my phone with Gingerbreak V1.20, and flash my recovery with CWM.
I proceeded to add the Nightly Four E rom, than the trouble began.
My colors on the phone display are diffused and distorted, mainly showing the color green and blue.
I read thatI need to flash the stock 2.2 rom again and it would fix it but it didnt.
Can someone help me with this, its quite annoying.
Click to expand...
Click to collapse
It's a kernel issue. From what you've stated, stock 2.2, your device never got it's official 2.3 update. So, you have an old baseband P505. You should be able to flash ROMs made specificially for the P505 as well as P500 ROMs. Since your device is old baseband, you also have the option to flash P509 ROMs. P509 never got an official GB update so it's always an old baseband device, same with the P506. The catch with P500 ROMs and most P505 ROMs is they are build for new baseband so an additional patch, old baseband, will need to be applied after flashing the ROM. P506 devices use a different touchscreen than the others so you'll have issues installing one of those ROMs.
The old baseband patch is to get your radio, cell signal, working with new baseband ROMs. I hope this wasn't information overload If you used ROM Manager, it's possible that is screwed up the radio too. ROM Manager is not friendly to the Optimus One device family. Android Flash Recovery, link in my signature, is designed for flashing recoveries via fastboot and fastboot mode. You may, especially if color banding is an issue with your recovery, want to reflash your recovery too.
Oh, and have you seen the LG Optimus One FAQ?
I appreciate the reply you've giving, but this is my first time using the Optimus One.
You stated its a kernel issue, how would I go upon fixing a kernel issue?
You also stated I should reflash the recovery, is there a specific recovery I should be using?
Trytohaxme said:
I appreciate the reply you've giving, but this is my first time using the Optimus One.
You stated its a kernel issue, how would I go upon fixing a kernel issue?
You also stated I should reflash the recovery, is there a specific recovery I should be using?
Click to expand...
Click to collapse
For the kernel issue, you can search the forums here to find some that are compatible with your device. The kernel you need will depend on the version of Android you are wanting to install since there isn't a universal kernel for all Android versions. Most of the newer kernels are for ICS( Android 4.0 ) and JB( Android 4.1, 4.2 ). I've never used it but they say Franco has a kernel for GB ( Android 2.3 ). SweetnSour has a kernel for JB and the AndroidArmv6 Team has a new 3.0 kernel for JB.
If you like GB, then you may want to look at this CM7.2 ROM( Direct download ). It is for a P500, so you will need the old baseband patch from post #9 in the LG Optimus One FAQ. I''m using that ROM on my P509 ATM.
As for the recovery, I only suggest reflashing it if you are experiencing color issues with it too. I use CWM 5.0.2.7 Touch, but it will only allow P500 ROMs to be flashed. It's no big deal for me, but for someone new to the game it can be troublesome. CWM 5.0.2.0 is also a good recovery. I don't recommend using ROM Manager to flash anything. If you should decide to reflash your recovery, I would recommend using Android Flash Recovery for Windows( in my signature ) or FlashImage GUI which can be found in the Play Store.
It seems no matter what I do, the color will not correct.
I've tried switching roms, flashing a new kernel and recovery nothing seems to be working..
Trytohaxme said:
It seems no matter what I do, the color will not correct.
I've tried switching roms, flashing a new kernel and recovery nothing seems to be working..
Click to expand...
Click to collapse
Do you still have a backup of your stock ROM? I mean a backup that was made while in recovery mode. If you do you can try booting in to recovery and then try wiping and formatting everything but your sdcard. Then restore the backup you made and reboot the device. Other than that, I hate to say it, but I'm at a loss.
I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Edit - The phone no longer allows me to access CWM it's just a black screen.
Trytohaxme said:
I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Click to expand...
Click to collapse
The kernel is part of the boot image. It's possible that somehow your partitions have been damaged.
---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------
Trytohaxme said:
I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Edit - The phone no longer allows me to access CWM it's just a black screen.
Click to expand...
Click to collapse
Hmm. I'm about convinced there's something wrong with your partition tables. Your data is getting corrupted.
So basically I just ruined the phone?
Trytohaxme said:
So basically I just ruined the phone?
Click to expand...
Click to collapse
Yes and no. If you can find or get a hold of the partition.mbn for your device you can use LGMDP to repair the partitions. The P500 one might work too, I'm not sure tho.
EDIT:
You can also install a recovery and ROM in the same process with LGMDP
shinobisoft said:
Yes and no. If you can find or get a hold of the partition.mbn for your device you can use LGMDP to repair the partitions. The P500 one might work too, I'm not sure tho.
EDIT:
You can also install a recovery and ROM in the same process with LGMDP
Click to expand...
Click to collapse
Yeah, I'm screwed I have no idea how to do that so I'm just gonna have to buy a new phone.. :crying:
Im sorry didn't read too well, bad luck, i didn't read your posts before, i knew how to fix the blue colors on your screen
gabo_lope said:
Im sorry didn't read too well, bad luck i didn't read your posts before i knew how to fix the blue colors on your screen
Click to expand...
Click to collapse
Well how exactly do you fix the screen color than?
Trytohaxme said:
Well how exactly do you fix the screen color than?
Click to expand...
Click to collapse
you only had to flash this on your p505 after the rom https://code.google.com/p/sweetnsour-kernel/downloads/list; one of these
kernel-20130224_1312.zip version4-CFS-P505-P506 for battery life
kernel-20130224_1306.zip version4-BFS-P505-P506 for performance
You have saved my phone my good sir, and I thank you greatly!
Now that I have the correct kernel, can I install different roms now?
Yes, but only ics and jellybean roms , if you use the kernel on gingerbread you will get a lot of troubles...
I just flashed the unofficial CM 10.1, and booted the phone and the color was diffused again.
So I flashed the kernel again and booted the phone, and everything is working perfectly.
Thank you so much!
P.S - CM 10.1 doesn't come with Google Apps or Rom manager, how do I get that back?
To get the google apps you will need to flash a gapps.zip, but first you need to trim the cm 10.1 rom, because
The recommended gapps package is not quite small enough to fit along with the rom in our limited /system partition. The size of the rom can be trimmed by deleting or converting some system apps to user apps, deleting unwanted ringtones and fonts.
Click to expand...
Click to collapse
Also
Take off anything that can be installed from Play, same for gapps.zip!!
Click to expand...
Click to collapse
There is a tool designed for that, is in shinobisoft's signature, oone rom editor, download that tool and in the help docs you will find information about trimming, and what can be removed safely... Here it is http://forum.xda-developers.com/showthread.php?t=1959023
If this the first time you are installing roms, i will recommmend you to stay in ice cream sandwich, because is more stable, and it has a lot better battery life than jellybean...
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.