Hi
Today after restoring my backup of Android 4.0 i noticed that home button is not working. I was on latest Omni 5.1 so i flashed stock via Odin and then custom kernel and restored my backup. I still can get into recovery and download mode using 3 buttons combo but in cwm home button isn`t working just like after booting into android. When i was on Omni 5.1 i have disabled hardware buttons and enabled navigation bar and didn`t reenabled it before flashing stock if it is important. Now home button is not working no matter if it`s stock ROM, 4.0 or 5.1. Could it be hardware problem even if i can get into download mode and recovery? Or maybe i can fix it some way?
Thanks for reading this and i hope someone is able to help.
@rootingguide did you use the same kernel you used previously to create the nandroid backup? Otherwise when you flashed stock firmware did you use also the repartition and pit512 file?
tetakpatalked from N7100
Related
I installed CM6 stable on my N1 after performing a nand backup. I restored to the original rom today to check something out. Now I can't boot into recovery. I get the exclamation android Guy. I used amonRA. Any suggestions?
i've got the same error and i tried with awrecovery.img instead of recovery-RA-nexus-v1.7.0.img and its working
forum.xda-developers.com/showthread.php?t=636795
I think the stock ROM flashes stock recovery when you reboot. You are actually in stock recovery when you see that screen. Try hitting the volume down and power buttons at the same time. Same exact thing happened to me.
I just decided to skip the stock ROM for that reason.
I bet there is a workaround for it though.
One work around would be to flash recovery using rom manager.
pwig is right, you replaced your recovery with the stock one.
You need to re-root (if the stock isn't rooted - which I believe it isn't, since the only builds that include recovery are completely stock), and after rooting re-flash the recovery with Amon_RA's recovery.
Hi,
After some help please, I am trying to upgrade from android 2.1 to gingerbread.
I have managed to get root access on my Samsung galaxy S i9000. I did this using the 'Galaxy S I9000 One-Click Root.exe' tool.
Then I installed Rom Manager via an .apk install (couldn't find the free version in the market for some reason).
After this I downloaded the busybox installer/updater and updated busybox to the latest version available.
Now I am having problems as when I run rom manager and try to run 'Flash Clockworkmod recovery' it goes through the process and when I reboot into recovery (using rom manager as I can't get into recovery using three button combo) it doesn't have the CWM recovery its just the standard one.
Also if I try to backup current rom (thinking this is a nandroid backup?) it reboots into recovery and just sits there and doesn't do anything.
Can someone please help, tried doing lots of research but am getting very confused as to what to do next.
Thanks in advance.
Boost. Haven't you heard....its the new bump!
Any help would be much appreciated.
Check Ramads stock collection:
http://forum.xda-developers.com/showthread.php?t=1102881
1.) Backup /efs folder
2.) Check that USB driver is working OK when connecting SGS to Windows in download mode
(no? - disconnect, find drivers, download, install)
Yes? :
3.) Flash in download mode using Odin + 512.pit + 2.3.x ROM + Sbl
You must use ROM with Sbl.bin = 2.3.x bootloader when going 2.1 -> 2.3
If no download mode by pressing (vol- home pwr), use XDA search for this fix.
Sent from my GT-I9000
Hi,
Thanks for the response.
I have now managed to successfully fix the three button combo issue so can get into download mode and have backup my efs folder.
Before I flash I would like to do a nandroid backup. I installed rom manager but still can't get CWM to install sucessfully. It says download successful when run from the rom manager option (flash CWM recovery) but when the phone reboots the CWM isn't there is just the stock options. Any ideas as to why this is or how to fix?
Many thanks in advance.
I have sorted my nandroid backup. I didn't realise that once you downloaded the CWM you had to do a manual install from stock recovery using the update.zip. Soon as i did this it was ok.
Now going to flash using odin v1.82 + 512.pit and Gingerbread 2.3.5 europe rom GT_I9000_XFJVA_XXJVT_OXFJV1_Sbl
Will make sure re-partition is checked.
Hopefully all will go well. Will post update after update.
jrdunn78hawk said:
Hi,
After some help please, I am trying to upgrade from android 2.1 to gingerbread.
I have managed to get root access on my Samsung galaxy S i9000. I did this using the 'Galaxy S I9000 One-Click Root.exe' tool.
Then I installed Rom Manager via an .apk install (couldn't find the free version in the market for some reason).
After this I downloaded the busybox installer/updater and updated busybox to the latest version available.
Now I am having problems as when I run rom manager and try to run 'Flash Clockworkmod recovery' it goes through the process and when I reboot into recovery (using rom manager as I can't get into recovery using three button combo) it doesn't have the CWM recovery its just the standard one.
Also if I try to backup current rom (thinking this is a nandroid backup?) it reboots into recovery and just sits there and doesn't do anything.
Can someone please help, tried doing lots of research but am getting very confused as to what to do next.
Thanks in advance.
Click to expand...
Click to collapse
For flashing a stock rom follow this video guide : Stock ROM Flashing
For flashing a custom rom follow any one this video guide: Custom ROM Flashing
HI,
I have now sucessfully upgraded to Gingerbread 2.3.5 europe rom GT_I9000_XFJVA_XXJVT_OXFJV1_Sbl
the problem I'm having now is when someone calls the screen just goes black (it doesn't turn off) and I can't answer the call. Also when the call ends there is no record of it in the missed calls so i can'e even see who it was who was calling.
Please help asap as I cant answer any calls or ring them back to tell them.
Thanks
All ok now. I did a factory reset which has sorted it. Phew! lol
i flashed to 4.2.2 this morning but i didn't like it so i decided to go back to stock jelly bean but i can't !! kies wont connect to my phone it would just keep loading and loading and never actually open the phone itself so i tried downloading the drivers manually but then odin doesn't recognize at all i tried unitsalling kies , updating , reinstalling nothing would ever work ! but y laptop recognizes the device and i can acess the files but other then this nothing
====update=====
i tried flashing with mobile odin and now it is stuck on samsung blue logo just keeps doing the animation over and over so i connected to pc and odin recgonized and flashed the rom again but then it is stuck on a boot loop and i tried wiping cache and factory data reset but wont work
What rom did you flash. Ics or JB. Install Philz kernel and do a wipe data reboot. If still no go then wipe system data cache and preload and reboot into download mode and flash stock rom again.
Rebooting in recovery and clearing cache and dalvik cache may help..
same problem here.
Mayank Chandwani said:
Rebooting in recovery and clearing cache and dalvik cache may help..
Click to expand...
Click to collapse
It didn't here. I went back from XXLT4 (rooted) to XXLT4 (stock non-root) using ODIN, and the problem was gone. Then I flashed PhilZ 4.93.6 kernel, and the problem was back. No connection, neither USB or Wifi. I was on a rooted stock kernel before, but have no idea what the problem was.
So, as soon as I root the firmware, the connectivity is gone.
Update: it's back. I have no idea why, I'm still on XXLT4 + latest PhilZ kernel.
Next problem: Where can I edit the newly added lockscreen shortcuts? Could it be that flashing PhilZ kernel removed that feature from the settings menu? I can't find it... and I've definitely seen it before I rooted.
zazzel said:
It didn't here. I went back from XXLT4 (rooted) to XXLT4 (stock non-root) using ODIN, and the problem was gone. Then I flashed PhilZ 4.93.6 kernel, and the problem was back. No connection, neither USB or Wifi. I was on a rooted stock kernel before, but have no idea what the problem was.
So, as soon as I root the firmware, the connectivity is gone.
Update: it's back. I have no idea why, I'm still on XXLT4 + latest PhilZ kernel.
Next problem: Where can I edit the newly added lockscreen shortcuts? Could it be that flashing PhilZ kernel removed that feature from the settings menu? I can't find it... and I've definitely seen it before I rooted.
Click to expand...
Click to collapse
Why do you want to flash Philz kernel..just root your phone on the stock kernel..JB stock kernel is bug free..
Go to settings--lock screen--swipe and there you have the option to change it on stock lock screen..do you have a custom lock screen??
Mayank Chandwani said:
Why do you want to flash Philz kernel..just root your phone on the stock kernel..JB stock kernel is bug free..
Go to settings--lock screen--swipe and there you have the option to change it on stock lock screen..do you have a custom lock screen??
Click to expand...
Click to collapse
Thanks! I used PhilZ because it came with cwm, built in root and was easily available.
Do you know how to go back to stock kernel without a full install? (and keep cwm and root). Something like a XXLT4 German / DBT kernel in a ZIP zile I can flash from recovery? I simply don't know where to find that.
Mybe SCS information is missing.*#1234# and view SCS code.
My CSC information is currently "N7000OXALT4" and nothing more. I was half expecting "DBT" behind that. Could that really be the problem?
Looks like I should go for a new nandroid backup & CSC reset?
zazzel said:
Thanks! I used PhilZ because it came with cwm, built in root and was easily available.
Do you know how to go back to stock kernel without a full install? (and keep cwm and root). Something like a XXLT4 German / DBT kernel in a ZIP zile I can flash from recovery? I simply don't know where to find that.
Click to expand...
Click to collapse
The stock kernel is the zImage which is included in the stock rom, and can be flashed.
qnt said:
The stock kernel is the zImage which is included in the stock rom, and can be flashed.
Click to expand...
Click to collapse
Thanks, I figured that out in the meantime, packed zImage into another flashable ZIP and signed it. Now I can theoretically flash it using "mobile ODIN" (to keep root) or from CWM. It's still not the perfect solution since I would definitely want CWM. So currently, I keep running PhilZ and wait for a better solution for the lockscreen icon issue.
whats the issue with lock screen? sorry for asking but after reading the thread i got confused.
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
zerkylo said:
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
Click to expand...
Click to collapse
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
kalpetros said:
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
Click to expand...
Click to collapse
Thank you for answering!
I fixed the issue. Tried different usb port along with a different version of CWM (5.5.0.4) which I installed with Odin v4.43. CWM 5.5.0.4 caused a bootloop, but i used it only to install CWM 6.0.4.9 from external_sd, so the bootloop problem was gone. Then flashed CyanogenMod 11 and now works like a charm !
I attached an archive with CWM 5.5.0.4, AriesVE.ops and Odin v4.43, so that anyone having my problem can solve it the way i did. But keep in mind that this version of CWM *may* cause a bootloop, so prior to installing it, you should have a working version of CWM on your external_sd. Use CWM 5.5.0.4 to install the better version of CWM from your external_sd. Also, whatever you do is at your own risk!
hey all, I have flashed many s6's in my day but this one is confusing me. I flashed stock 6.0.1 firmware from sammobile successfully, i get to home screen, turn off, boot into download mode and then try to flash TWRP or CF Auto Root and I get a fail message on the recovery part of the flash.
Any reason for this? It did not fail recovery while flashing stock firmware.
Any help would be appreciated.
Thank you.
so i just flashed my s6 edge. i didn't use the cf-root. I flashed the latest twrp from the twrp site via odin, disable auto-reboot so you can go back to recovery directly (while in download mode, hold down power home and volume down, it should reboot, when screen goes black switch to volume up power up and home) and in twrp i flashed the latest supersu from chainfire flashable zip and i flashed twisted 8 kernel. worked great for me, i'm; on the latest marshmallow update
runsoverfrogs said:
so i just flashed my s6 edge. i didn't use the cf-root. I flashed the latest twrp from the twrp site via odin, disable auto-reboot so you can go back to recovery directly (while in download mode, hold down power home and volume down, it should reboot, when screen goes black switch to volume up power up and home) and in twrp i flashed the latest supersu from chainfire flashable zip and i flashed twisted 8 kernel. worked great for me, i'm; on the latest marshmallow update
Click to expand...
Click to collapse
did you not understand what I was asking? or were you just telling me your cool "i can flash" story?
It fails on flashing teamwin OR auto root. I get a fail on either and both when i try them, yet it lets me flash stock firmware
I'm probably sounding grouchy right now, but I've been fighting with this s6 for hours now and I've tried 3 computers and USB 2.0 and 3.0 ports along with multiple cables....i finally get a reply and it was no help. at all. I cannot flash to do it your way because i cannot flash TWRP without it failing when it starts writing the recovery image.
What version of TWRP are you trying to flash, what version of Odin are you using, what slot are you attempting to flash TWRP with, and what is the error message?