Related
Okay so Im not that new with rooting androids or with using custom roms, so I'm not that much of a noob. The other day I decided since CM9 was in official nightlies I would give it a try. So I backed up my rom which was stock and rooted and I installed CM9 all through CWM recovery. Once in CM9 i notice the tablet wont connect to my phones tethering which is the only way I can get internet on it so I deciced to go back to my backup. But now on my backup the Wifi wont even turn on, anyideas why?
Hello,
I got exactly the same problem. I have installed CWM 5.5.0.4 and I tried CM9 nightly and return to Nandroid BackUp. Then no more wifi..
I tried to flash differents versions of stock kernels, but it was impossible to flash it : "Installation aborded"..
I used fastboot to install a new recovery : TWRP, but same problem : impossible to flash any kernels..
Does someone has the same problem? Or any idea to solve it?
Thank a lot !
Crystalyse
I also had another question...
is there any rom that will connect to Android tethering (ad-hoc)?
I was able to connect on stock rom rooted with cwm recovery but now every rom I tried so far wont connect to it.
Is there a way to work around this issue
I'm having similar problems, check this out:
http://forum.xda-developers.com/showthread.php?t=1438297
Going to try when I get home but other users are reporting this working for them.
KB Smoka said:
I'm having similar problems, check this out:
http://forum.xda-developers.com/showthread.php?t=1438297
Going to try when I get home but other users are reporting this working for them.
Click to expand...
Click to collapse
+1 That's the fix (WPA_Spullicant2) that worked for me. My TF300 just kept saying "Saved" when trying to connect to ad-hoc. Replaced the WPA_Supplicant2 file and all is working well.
It's a known issue with wifi not working on stock rooted nandroid backups. If you go back to stock, you will need to follow the step in this post from Xplod.
http://forum.xda-developers.com/showpost.php?p=26435786&postcount=2
meatrocket said:
+1 That's the fix (WPA_Spullicant2) that worked for me. My TF300 just kept saying "Saved" when trying to connect to ad-hoc. Replaced the WPA_Supplicant2 file and all is working well.
Click to expand...
Click to collapse
Sent from my ASUS Transformer Pad TF300T using XDA
Worked perfect....Thanks again for this.
Inc2.CM7.Condemned.Wireless.Tether.2.0.7
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.
As the title says: P5110 keeps rebooting during boot - right after animation stops (before word SAMUNGS starts glowing).
Tablet is rooted and there is CWM 5.5.0.4 installed. Was just fine for almost half a year and all of a sudden this...
I have tried
- wipe data/factory reset
- wipe cache partition
- advanced : wipe Dalvik Cache (whatever that might be?)
I also tried all the "mounts and storage" options and noticed on thing: i can mount all storage mounts (/system, /cache, /data, /efs, /preload, /sdcard) but one - namely /emmc. Does it mean that emmc is broken? What is emmc? Is it important?
I am considering unrooting it and removing CWM. But not sure whether it's even possible and don't dare to try!
Can you tell me anything that might help me debrick this tablet?
Do you have nandroid backup(one that you make with cwm)? If yes go to backup and restore in cwm and hit restore....if not try to reflash rom via cwm or flash stock rom via odin in dowload mode.
emmc is.... http://www.simmtester.com/page/news/showpubnews.asp?num=181
Starojitski said:
As the title says: P5110 keeps rebooting during boot - right after animation stops (before word SAMUNGS starts glowing).
Tablet is rooted and there is CWM 5.5.0.4 installed. Was just fine for almost half a year and all of a sudden this...
I have tried
- wipe data/factory reset
- wipe cache partition
- advanced : wipe Dalvik Cache (whatever that might be?)
I also tried all the "mounts and storage" options and noticed on thing: i can mount all storage mounts (/system, /cache, /data, /efs, /preload, /sdcard) but one - namely /emmc. Does it mean that emmc is broken? What is emmc? Is it important?
I am considering unrooting it and removing CWM. But not sure whether it's even possible and don't dare to try!
Can you tell me anything that might help me debrick this tablet?
Click to expand...
Click to collapse
If you have nandroid backup.. Just restore it.. Or else download a stock firmware and flash it via odin.. gud luck:good:
flash another rom !!
mythi said:
flash another rom !!
Click to expand...
Click to collapse
Sorry to jump on this thread but might be a similar steps the OP has to take.
What if he flashes a new Rom and it still is locked in a strange boot up?
I posted a thread earlier today but either no one has an answer or my thread title was just crappy.
Mine did exactly what his is doing now (just boots the samsung logo and hangs) and now it just boots into recovery everytime you start it.
Flashing an original stock rom didnt fix it.
Flash via Odin any stock ROM then root it and flash whatever you like.
This kind of brick may occur easily if you have flashed uncompatible kernel or tried to restore nandroid backup of another ROM or made by uncompatible CWM recovery version.
Sent from my GT-P5110 using XDA Premium HD app
Solved?
dartd27 said:
Sorry to jump on this thread but might be a similar steps the OP has to take.
What if he flashes a new Rom and it still is locked in a strange boot up?
I posted a thread earlier today but either no one has an answer or my thread title was just crappy.
Mine did exactly what his is doing now (just boots the samsung logo and hangs) and now it just boots into recovery everytime you start it.
Flashing an original stock rom didnt fix it.
Click to expand...
Click to collapse
Normally, it should actually work absolutely fine if you flash a stock ROM via Odin.
Nobody knows what did cause your problems and what did you flash as last. Also, different OS versions use sometimes different partitions. Even CWM recovery is not compatible through all versions, it uses different formatting.
So this way should work to restore stock ROM on your device:
find and download Odin that fits your device (earlier versions are not neccessarily worse ones)
find and download PIT file for your device
find stock ROM for your device consisting 3-files (for PDA, Phone, CSC).... ROMs are usually zipped, so you will get 3 data after extracting
The PIT file will do re-partitions for the case that your formerly installed ROM used different partitions whch are not compatible with the stock ROM.
After that you will have again unrooted stock ROM. So just be careful afterwards whatever you flash and before you do it, make sure that whatever you flash always fits your device (no matter is it whole ROM, kernel or just upgrade).
tetakpatak said:
Normally, it should actually work absolutely fine if you flash a stock ROM via Odin.
Nobody knows what did cause your problems and what did you flash as last. Also, different OS versions use sometimes different partitions. Even CWM recovery is not compatible through all versions, it uses different formatting.
So this way should work to restore stock ROM on your device:
find and download Odin that fits your device (earlier versions are not neccessarily worse ones)
find and download PIT file for your device
find stock ROM for your device consisting 3-files (for PDA, Phone, CSC).... ROMs are usually zipped, so you will get 3 data after extracting
The PIT file will do re-partitions for the case that your formerly installed ROM used different partitions whch are not compatible with the stock ROM.
After that you will have again unrooted stock ROM. So just be careful afterwards whatever you flash and before you do it, make sure that whatever you flash always fits your device (no matter is it whole ROM, kernel or just upgrade).
Click to expand...
Click to collapse
Thank you for the reply. I had posted a link in here that linked to my thread that explained what i had done and used but it didnt show up for some reason? Anyway I used the below roms(in bold). An update was available for JB and we own two tablets both the P5113 and bought at the same time. One tablet updated fine but the other one would download the package but then would keep failing to install it. So i did a factory reset on the device and then that's when the fun began and it started booting strange.
So I first tried flashing the official JB rom using ODin 3.04.
P5113UECLK7 (4.1.1) - Cellular south November 2012 (Official)
and it still did the same thing so then i tried flashing it back to ICS which is the rom that was on there i think. (It was ICS but not sure if that was the exact version number?)
P5113UEBLI1 (4.0.4) - Singapore September 2012 (Official)
Im sure the roms are going on there fine as if im not mistaken ICS has a blue battery charge icon and JB a gold one. I noticed that it went from blue to gold when i first loaded the 4.1.1 on there and then back to blue when i put ICS back on there.
I cant seem to find a PIT file for the P5113. Only for the P5100. Would that work?
I tried it anyway and it didnt work
dartd27 said:
I cant seem to find a PIT file for the P5113. Only for the P5100. Would that work?
Click to expand...
Click to collapse
If I was you, I wouldn't flash it before I am 100% sure it fits the p5113. I own the p5110 and they are indeed very similar, but who knows.... Take care of your Tab, mate.
BTW: why not CM10.1 stable? It works awesome, full wipe/factory reset, install zip through recovery, install recent gapps for CM10.1 (4.2.2) and after boot install Apex launcher and enjoy life
Sent from my amazing i9000 running CM10.1 by pawitp
tetakpatak said:
If I was you, I wouldn't flash it before I am 100% sure it fits the p5113. I own the p5110 and they are indeed very similar, but who knows.... Take care of your Tab, mate.
BTW: why not CM10.1 stable? It works awesome, full wipe/factory reset, install zip through recovery, install recent gapps for CM10.1 (4.2.2) and after boot install Apex launcher and enjoy life
Sent from my amazing i9000 running CM10.1 by pawitp
Click to expand...
Click to collapse
I hear you Its a paper weight right now though so thought id rather try as nothing else is doing the trick.
The tablets are my kids so i preferred to just give them an official stock version. I got put off using custom roms when i used paranoid android on my samsung galaxy 2 and it was real buggy. I just need my devices to work for the basics. I now run stock jelly bean on my GS2 but even that has crappy battery life, lucky for it to make it till 4pm and still be on and thats with moderate use. Couple of phone calls and a few text messages and a tiny bit or browsing. I know what is causing it though as it only starts to lose battery when im not on wi fi. It at least doesnt freeze and stop receiving phone calls altogether like PA did though. I used to miss a ton of work calls because the phone had actually frozen.
I love Apex though. I have Apex pro on my GS2 and its much better then the standard launcher. My daughter has the GS3 and it still does not rotate on the home and app screens which i find annoying.
dartd27 said:
I got put off using custom roms when i used paranoid android on my samsung galaxy 2 and it was real buggy. I just need my devices to work for the basics.
Click to expand...
Click to collapse
I've got your point, mate. :good:
Same with me: I need all the functions to work. The CM10.1 does it really, but my p5110 is wifi-only device so I'm not sure if CM10.1 is same good for your p5113. CM10.2 seems to be smooth and fast, but many apps aren't yet updated for 4.3 so I will wait a while before I flash it again.
I have cm10.1 on my p5113...it runs amazing...the p5113 owners most of the time have to flash the p5110 version because there is nothing different with the tabs besides the ir port..
Sent from my GT-P5110 using xda app-developers app
help me
hello guys,
i have the same problem with my p3100
in my case i cannot connect my tablet to my laptop and it is always looping
i already install the driver, odin, and kies
i already root my tablet
can anyone help me please??
obeye said:
hello guys,
i have the same problem with my p3100
in my case i cannot connect my tablet to my laptop and it is always looping
i already install the driver, odin, and kies
i already root my tablet
can anyone help me please??
Click to expand...
Click to collapse
Can you describe it bit more precised, mate? Don't panic, so far it doesn't sound so bad....
tetakpatak said:
Can you describe it bit more precised, mate? Don't panic, so far it doesn't sound so bad....
Click to expand...
Click to collapse
okay, thanks mate
the problem is my tab always looping whenever I turn it off
I already try wipe at CMW mode,
but it is always restart and nothing happen and its still looping
I already try install the OS, but its aborted
i trying to flash it with Odin, but my laptop cannot read my tab
its been 3 day my tab cannot turn on
obeye said:
okay, thanks mate
the problem is my tab always looping whenever I turn it off
I already try wipe at CMW mode,
but it is always restart and nothing happen and its still looping
I already try install the OS, but its aborted
i trying to flash it with Odin, but my laptop cannot read my tab
its been 3 day my tab cannot turn on
Click to expand...
Click to collapse
Can you reach the download mode? (press 2 buttons at same time: volume down and power button)
OK, yes- you need same Odin version as Tabs 51xx, this is link for Odin 3.07:
http://hotfile.com/dl/161620048/6c6d559/Odin3_v3.07.rar.html
Try pressing the buttons with the charger plugged in, as well as plugged out, that is little trick with the p51xx Tabs
tetakpatak said:
Can you reach the download mode? (press 2 buttons at same time: volume down and power button)
OK, yes- you need same Odin version as Tabs 51xx, this is link for Odin 3.07:
Try pressing the buttons with the charger plugged in, as well as plugged out, that is little trick with the p51xx Tabs
Click to expand...
Click to collapse
Thanks mate!
already done!!
its work!
thank you so much!!
obeye said:
Thanks mate!
I already install ROM JB on my tab
but its still looping in samsung logo,
i read that i should install CWM, but when i install it, it says that "verification failed"
what should i do??
Click to expand...
Click to collapse
Great, I am glad to hear it did charger cable trick help?
Just to make sure: you must be sure to flash a stock ROM first (not JB based custom ROM), after it you will have revived Tab without root. After that normal proceeding: root it, install CWM recovery or custom kernel that fits your ROM (or even whole custom ROM) which already features the CWM recovery.
The stock recovery (3e) checks the signature so of course you can't flash any custom zips. CWM recovery has an option "toggle signature verification" where one can disable signature check. Then you can flash whatever you want, just take care that all you ever flash must be absolutely compatible for your device.
---------- Post added at 03:45 PM ---------- Previous post was at 03:21 PM ----------
obeye said:
Thanks mate!
I already install ROM JB on my tab
but its still looping in samsung logo,
i read that i should install CWM, but when i install it, it says that "verification failed"
what should i do??
Click to expand...
Click to collapse
One more thing mate, look at this video which I've posted on YouTube last January:
http://www.youtube.com/watch?v=0NXBN9Z63TY
It describes how to get rid of the signature verification problem. For the reason that quite many people don't understand english well, I have made a speechless video added by step by step description in the text (video description) so people can just copy the text and paste it into their translators.
If one ROM that you have flashed bootloops on the logo just try another ROM. It happens sometimes. Important is that you should always before flashing another ROM make full wipe: (data/factory reset/cache/dalvik) in your recovery mode.
Did you do it?
Please let me know if you were successful, it should work now! Good luck :fingers-crossed:
It works!
Thanks everyone for your feedback!!!
and my apologies for late response.
I followed the advise to (re)flash stock rom and it worked!
After that i rooted it again, installed another recovery and now have the latest stock rom working perfectly.
For those who get the same problem and the tabled keeps rebooting - just plug it into recharger and keep the on/off button until it turns off. Then you can fully charge it before you attempt to flash rom.
Once again, thanks a lot!
PS. now i am considering installing CM10.1
Starojitski said:
Thanks everyone for your feedback!!!
and my apologies for late response.
I followed the advise to (re)flash stock rom and it worked!
PS. now i am considering installing CM10.1
Click to expand...
Click to collapse
Great! Congratulations
Yes, install CM10.1.1 with gapps for 4.2.2 it works great, all the functions. Just mind that you can not restore nandroid backups made with other kernel, (sometimes also not if done with older CWM recovery version) and also apps backups made by Titanium backups in older systems aren't good idea to restore once you upgrade to CM10x
If you want to return for any reason to your old (current) ROM, do the same procedure like by unbricking
Hi guys, I'm fckland and I'm relatively new here since I never write but I always come here when I need something
This time I come here with a doubt. I got the motorola xt1032 and it's awesome, I have unlocked the bootloader and rooted it and installed CWM to flash some ROM's, but they didn't worked and bricked my phone, so I had to install google play edition by fastboot (following this guide: http://forum.xda-developers.com/showthread.php?t=2542219 ) and now when I hit "install zip from sdcard" it says: e:\ can't mount sdcard
I want to access that option to install the faux kernel to test it but i can't. What can I do to fix it? I have searched and I didn't find nothin specific for the motorola moto G.
While I was writing this, I installed the TWRP and it worked! I had access to the internal memory without any issue!
BUT I HAD AN ISSUE
I installed the faux kernel with the OC to 1.6GHz and it bricked the OS (google play edition) (stuck at bootanimation), I installed the other version, the non OC and it bricked too and I had to do the tutorial once again since i didn't do a backup
And my second question is... Why this moto g doesn't accept most ROM's and kernels? I have tried with ROM: Carbon, AOSP, MOKEE and none worked and Kernels: faux version u and m and none worked, all of them bricked my phone.
If you need details of the version of my phone or something please ask for it and I'll upload it.
Thank you very much.
Nobody? I need to know at least why I can't install ROM's without having lots of issues.
Post details.
Please post details of which recovery you are using to flash ROMs, which kernel you are on and lastly which ROM works fine and which doesn't.
I, personally think you might had been on philz recovery and issue is not only which /sdcard but with /data.
Post the required info and I'll get back to you.
Problem solved!
I don't know what the problem was, but I think that I wasn't formating well after installing ROM's.
I have installed CM11 minutes ago and it works really nice (with wifi, I didn't try 3G yet) but I have a stock kernell and I would love to install faux or pink kernell, how do I have to do exactly to install one of them? And what can I do if i get bootloop?
Thank you!
Stick with the original kernel.
fckland said:
Problem solved!
I don't know what the problem was, but I think that I wasn't formating well after installing ROM's.
I have installed CM11 minutes ago and it works really nice (with wifi, I didn't try 3G yet) but I have a stock kernell and I would love to install faux or pink kernell, how do I have to do exactly to install one of them? And what can I do if i get bootloop?
Thank you!
Click to expand...
Click to collapse
It's nice that your problem is resolved. And for the kernel as far as I know faux and pink support only stock ROM, no support for CM11 yet. You can search the thread for any other kernel but I would recommend to stick to default kernel now. Moto G is still under huge development, have patience. Soon we'll have a lot of them.
Regarding bootloops, take care that before installing any Rom you format /system along with wipe cache and data. Mount them again and then flash the rom.If any other help needed then post it.
P.S. No need to say Thanks press Thank you instead.
fckland said:
Problem solved!
I don't know what the problem was, but I think that I wasn't formating well after installing ROM's.
I have installed CM11 minutes ago and it works really nice (with wifi, I didn't try 3G yet) but I have a stock kernell and I would love to install faux or pink kernell, how do I have to do exactly to install one of them? And what can I do if i get bootloop?
Thank you!
Click to expand...
Click to collapse
i had also same problem with my moto g...
just u guide me how u solve this problem....?
im unable to instal stock, CWM, and TWRP recovery mode on it... Except philz_touch_6.41.6-moto_falcon..
plz help me
vardhanram said:
i had also same problem with my moto g...
just u guide me how u solve this problem....?
im unable to instal stock, CWM, and TWRP recovery mode on it... Except philz_touch_6.41.6-moto_falcon..
plz help me
Click to expand...
Click to collapse
Why you can't?
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.