Related
ive been folowing the android 4.0 port for the galaxy s ii and like using the alphas but they arent daily material so i found dualboot(lolboot) on market, followed the directions, using clockworkmod flashed to the ics alpha and saved it (not sure thats exactly the term they used) for secondary, flashed back to cyanogenmod, used the apps second function to install the secondary boot(ics), then i installed the siyah(probably mispelled) kernal it provided, went to try it by pressing the vol up + home + power combo, hung up and the samsung boot image, tried to start it normally and the same thing happened, help, i cant go back to my chinese htc wildfire, how do i get my phone back working?
ps: i can still get into download mode
same problem here .. please help!!!
This is my first time rooting or doing any modifying to my phone. Can someone please help??!
I have installed the CM 10.1, but whenever I reboot, it takes me to the main screen (language screen), but I am unable to do anything. The touch screen and interactive buttons do not work. The only buttons that work are the power and volume buttons. I can only go back to the bootloader and/or twrp, what do I do???!
hmmmm
lbharris2008 said:
This is my first time rooting or doing any modifying to my phone. Can someone please help??!
I have installed the CM 10.1, but whenever I reboot, it takes me to the main screen (language screen), but I am unable to do anything. The touch screen and interactive buttons do not work. The only buttons that work are the power and volume buttons. I can only go back to the bootloader and/or twrp, what do I do???!
Click to expand...
Click to collapse
Not really sure what you mean, but are you s-on? because then you have have to flash the kernel manually.
I know with my HTC One X I have to flash the boot.img manually before installing CM10 otherwise it just won't work.
Download adb / fastboot
Reboot into bootloader
Connect USB
command is "fastboot flash boot boot.img" - obviously the boot.img is the kernel.
reboot and all should be working
Screen nonresponsive
I flashed my HTC EVO 4G LTE to Cyanogen 10.1. Stupid me didn't make a backup. I have the same issue as OP - the phone boots ok, but screen and keys at the bottom of the screen are non-responsive. I tried flashing 10.0, that didn't work. The Cyanogen splash screen hung. Tried going back to RUU (stock) but I have the new bootloader with Jellybean, and that wouldn't work either. I tried manually flashing the kernel from the latest nightly and got no errors. But same issue. The phone loads, but screen doesn't work.
Found my own answer. This is a typical issue with CM10.1 - the screen drivers have changed. For anyone else who stumbles across this with the same issue...
http://forum.xda-developers.com/showthread.php?t=2151727
Quick Question
Hi guys,
I just have a quick question. I'm on MeanBean 3.09. Its great, but I'm getting the urge to switch roms. I loved cm 10.1, but I missed the voice mail function- which i found an apk to a modded voice mail. I was also having the problem of not getting certain notifications. Facebook, Messenger, and other social apps weren't showing notifications, I would have to manually check. This was a major inconvenience. I was wondering if that has been resolved? Or is there a fix for it?
Thanks,
Nick M.
wwjoshdew....You Tube. He'll know!
Ok, a long story here.
My son dropped his Samsung Ace2x s-7560m phone. The screen cracked. I bought a replacement screen through a reputable seller on ebay.
After installing the screen, the s7560 starts, but freezes on the Samsung screen, then boots over. This goes on and on.
I rooted the phone and flashed a 7562 stock rom to the device. The only difference between the two devices is that the 7562 is a dous phone.
The flash went well, and after rebooting, the phone boots up. It starts out as a 7560, then the screen flickers and becomes the 7562 duos.
The phone boots up. I can surf online using wifi, and the screen reacts as it should for the whole screen.
Now, when I try to call out the call does connect, but I can't end the call. The phones network does not work at all.
I have tried to enter into the recovery and can , but only by using adb. The key combos don't work. I can get the phone to boot into download mode.
The bootloader still shows as a 7560, and the software shows as a s a 7562. I think what is happening is the seller from ebay has sold me the duos screen instead of the 7560. He has refunded the money, and told me to keep the screen, so now it has become a bit of a challenge that I will defeat.
I am wanting to get the phone working. I have found a rom called kyleopen, but all the download links are removed or not working. I can put other files like cwm into the download file. When I try and access the sd card, I get an error that it can't mount it.
So..
Is there a custom rom that works on both the 7560 and the 7562 that can be installed using odin?
or:
Is there a way to flash the bootloader to be a 7562 model?
Is there a way to correct the screen issue..whereas I can still use a 7560 rom, and the screen will be detected.
As stated, I am trying to run the 7560 with a 7562's screen. I am guessing the digitizer is a bit different from device to device, and that the 7560 is just not recognizing the screen as being there. I have tried to flash the stock 7560 rom back onto the phone, but get the same issue..won't boot past the samsung screen.
Is there a file to alter to get the 7560 to accept the screen as the right one? I know the screen does work with the phone, and think the network issues I am having is because the duos feature of the rom flashed to the device.
Anybody have any ideas?
freakybaby said:
Anybody have any ideas?
Click to expand...
Click to collapse
Maybe too late.
In a call, usually if you can´t finish the call is because the proximity sensor is not working and didn´t detect that you separate the phone from your face, or when you disassembly and reassembly the phone you forgot the plastic mount of the infrared detector.
Did you get the two lines working? I mean, both phones are exactly same board and rest of the spares, but s7562 uses two sim cards, in a s7560 flashed with s7562 firmware are both sim cards works?
WBR
freakybaby said:
Ok, a long story here.
My son dropped his Samsung Ace2x s-7560m phone. The screen cracked. I bought a replacement screen through a reputable seller on ebay.
After installing the screen, the s7560 starts, but freezes on the Samsung screen, then boots over. This goes on and on.
I rooted the phone and flashed a 7562 stock rom to the device. The only difference between the two devices is that the 7562 is a dous phone.
The flash went well, and after rebooting, the phone boots up. It starts out as a 7560, then the screen flickers and becomes the 7562 duos.
The phone boots up. I can surf online using wifi, and the screen reacts as it should for the whole screen.
Now, when I try to call out the call does connect, but I can't end the call. The phones network does not work at all.
I have tried to enter into the recovery and can , but only by using adb. The key combos don't work. I can get the phone to boot into download mode.
The bootloader still shows as a 7560, and the software shows as a s a 7562. I think what is happening is the seller from ebay has sold me the duos screen instead of the 7560. He has refunded the money, and told me to keep the screen, so now it has become a bit of a challenge that I will defeat.
I am wanting to get the phone working. I have found a rom called kyleopen, but all the download links are removed or not working. I can put other files like cwm into the download file. When I try and access the sd card, I get an error that it can't mount it.
So..
Is there a custom rom that works on both the 7560 and the 7562 that can be installed using odin?
or:
Is there a way to flash the bootloader to be a 7562 model?
Is there a way to correct the screen issue..whereas I can still use a 7560 rom, and the screen will be detected.
As stated, I am trying to run the 7560 with a 7562's screen. I am guessing the digitizer is a bit different from device to device, and that the 7560 is just not recognizing the screen as being there. I have tried to flash the stock 7560 rom back onto the phone, but get the same issue..won't boot past the samsung screen.
Is there a file to alter to get the 7560 to accept the screen as the right one? I know the screen does work with the phone, and think the network issues I am having is because the duos feature of the rom flashed to the device.
Click to expand...
Click to collapse
try this install firmware for s7560 then flash cwm recovery and after that boot into recovery wipe data/factory reset then go to advanced menu in recovery and then wipe dalvick cache . reboot phone. now it should boot with no problem
sadman2 said:
try this install firmware for s7560 then flash cwm recovery and after that boot into recovery wipe data/factory reset then go to advanced menu in recovery and then wipe dalvick cache . reboot phone. now it should boot with no problem
Click to expand...
Click to collapse
So I have reflashed with the 7560 rom. I am back to a boot loop. I can't get to recovery..I was only able to do that in ADB, but can't boot up for adb right now.
ANy other ideas..or ways I can get into recovery. I can get the download screen using the buttons, but not the recovery.
Means reflashed the rom using a stock firmware and ODIN?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
freakybaby said:
So I have reflashed with the 7560 rom. I am back to a boot loop. I can't get to recovery..I was only able to do that in ADB, but can't boot up for adb right now.
ANy other ideas..or ways I can get into recovery. I can get the download screen using the buttons, but not the recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=45767157#post45767157
here have all the faq for this phone and the links. download daverq18 root pack and follow the instructions. then you should succesfully boot into cwm recovery
i upgraded my note N8000 via odin mobile pro with success and everything was smooth and the root was not intact
I tried to flash a theme via mobile odin but was not success, but note was still ok
then 2 days later I tried to enter the recovery mode , i found the note stuck on samsung boot screen and dose not reboot, I can enter download mode but can not enter recovery mode to reflash even the stock rom
what to do?
should i reflash the CWM as 1st time? then reflash the root if i found it is gone?
or i have to reflash the stock rom first via odin desk top since i can not reboot the note? problem is the stock rom is on the note and do not have it on PC
the note now is on Samsung boot screen, how to turn it off since note can not remove the battery?
EDIT 1::good:
Flashed a stock recovery via odin desk top, and rebooted
Note is back alive , no wipes, every thing still there, root still here
Rebooted once again with success
rebooted into recovery (stock since I lost my CWM) with success
EDIT 2
Flashed CWM and my note is back for my modifications
:fingers-crossed:
Stock Recovery File?
thermax04 said:
i upgraded my note N8000 via odin mobile pro with success and everything was smooth and the root was not intact
I tried to flash a theme via mobile odin but was not success, but note was still ok
then 2 days later I tried to enter the recovery mode , i found the note stuck on samsung boot screen and dose not reboot, I can enter download mode but can not enter recovery mode to reflash even the stock rom
what to do?
should i reflash the CWM as 1st time? then reflash the root if i found it is gone?
or i have to reflash the stock rom first via odin desk top since i can not reboot the note? problem is the stock rom is on the note and do not have it on PC
the note now is on Samsung boot screen, how to turn it off since note can not remove the battery?
EDIT 1::good:
Flashed a stock recovery via odin desk top, and rebooted
Note is back alive , no wipes, every thing still there, root still here
Rebooted once again with success
rebooted into recovery (stock since I lost my CWM) with success
EDIT 2
Flashed CWM and my note is back for my modifications
:fingers-crossed:
Click to expand...
Click to collapse
Do you have a link to where you found the stock recovery rom/image? And how did you flash it? I am having a similar problem right now.
kyleschepis said:
Do you have a link to where you found the stock recovery rom/image? And how did you flash it? I am having a similar problem right now.
Click to expand...
Click to collapse
do u mean the stock rom? I got it from samobile.com
or u mean u want the stock recovery?
try this
http://mirror21.downloadandroidrom....e10.1/recovery/N8000_StockRecovery.tar?token=
Will reflashing the tablet to stock, delete all of my files off of it? Is there a way to retrieve the files through download mode somehow?
kyleschepis said:
Will reflashing the tablet to stock, delete all of my files off of it? Is there a way to retrieve the files through download mode somehow?
Click to expand...
Click to collapse
in my post i wrote that reflashing the stock rom did not wipe (delete) any thing, u will find all your stuff undeleted
thermax04 said:
in my post i wrote that reflashing the stock rom did not wipe (delete) any thing, u will find all your stuff undeleted
Click to expand...
Click to collapse
It says you flashed a stock recovery. Is it the same case for a stock ROM?
kyleschepis said:
It says you flashed a stock recovery. Is it the same case for a stock ROM?
Click to expand...
Click to collapse
sorry, my mistake, flashing the stock rom will not delete your stuff, just be sure to flash the same rom or higher, not lower one
So, I tried flashing the stock recovery and that did not work. And then I tried flashing the stock rom (multiple times with different roms) and that did not work either. My tablet is still stuck on the screen that says "Samsung Galaxy Note 10.1". Do you have any other suggestions?
can u write some details about what was before and reason for problem, to think together about a solution
thermax04 said:
can u write some details about what was before and reason for problem, to think together about a solution
Click to expand...
Click to collapse
My Note 10.1 N8013 was rooted, had TWRP, and Cyanogenmod 10.2 Nightly on it. I hadn't touched it in two days and went to turn it on. It wouldn't turn on, so I assumed it was dead. I charge it overnight and try to turn it on in the morning, but it just goes into a boot loop. The tablet says "Samsung Galaxy Note 10.1" and stays that way until it dies. If I boot into recovery mode, the Teamwin (TWRP) title screen pops up and then immediately disappears. The tablet then shows the battery loading icon if it is plugged in. The icon shows up, then disappears and the shows up again and repeats this a few times. I could only boot into download mode successfully.
I have tried flashing different stock roms and recoveries through odin, including the one that you have linked on here. None of them have worked. I have also tried repartitioning the tablet, which passed on Odin, but did not solve the problem.
Other forums say that I should do a factory reset or wipe the data, but I do not know how to do this without being able to boot into recovery or the OS itself.
Thanks
P.S. I also brought it to Best Buy to see if the Samsung guy could reflash the stock rom, but his rom did not work either. They are all passing on Odin, so it isn't an error in that case.
I read that a lot of people got problems with Cyano roms. I did not like it and never used it, sorry can not help you
thermax04 said:
I read that a lot of people got problems with Cyano roms. I did not like it and never used it, sorry can not help you
Click to expand...
Click to collapse
Could it be because of the Cyanogen rom? I didn't update recently... I probably updated it a week before it died. Would you happen to know how to do a factory reset / wipe the data from the tablet, if I can't get into recovery mode or the OS?
I don't think that there is any other way, sorry about that.
try to put your problem in the Cyano rom thread, may others had the same and solved it
Ok thank you
Let me know if you get it fixed
Hi kyleschepis,
Let me know if you find a solution. I have a very similar issue . . . the difference is, I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started about 5 days ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But 5 days ago, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I am able to get into the Odin download mode but cannot get into recovery mode no matter what I do/
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. But the power + volume up combination does not get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for 5 days now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
robb-x said:
Hi kyleschepis,
Let me know if you find a solution. I have a very similar issue . . . the difference is, I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started about 5 days ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But 5 days ago, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I am able to get into the Odin download mode but cannot get into recovery mode no matter what I do/
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. But the power + volume up combination does not get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for 5 days now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
Click to expand...
Click to collapse
Did you try removing the sd card and reboot again ?
DId you fix your tablet
kyleschepis said:
Ok thank you
Click to expand...
Click to collapse
Hi Kysleschepis,
Were you able to fix the problem with your phone.
I have exact same problem....my Gt-n8000 tablet is stuck on "Samsung Galaxy Note 10.1" logo. And i cant access the recovery mode.
Let me know if you found a solution to this problem.
Thanks.
same here but didn't work
i have same problem with my Note 10.1 N8000 stuck in bootloop problem but i didn't do anything like upgrading or install new app ... its stuck by him self and i tried the following and all not working :
1, Hard Reset with software menu (not working)"only if the device is working".
2, Hard Reset with Dial secret code key(not working) "only if the device is working".
3, Hard Reset with Hardware Key Button(Factory recovery screen not working).
4, installing recovery philz_touch_6.07.9-n8000.tar with Odin (passed installed successfully but still not working).
5, installing recovery openrecovery-twrp-2.4.1.0-p4notewifi_3 with Odin (passed installed successfully but still not working).
6, installing recovery CF-Auto-Root-p4noterf-p4noterfxx-gtn8000.tar with Odin (passed installed successfully but still not working).
7, installing recovery twrp-2.6.3.1-n8000.tar with Odin (passed installed successfully but still not working).
8, installing recovery Samsung_N8000_Hard_Reset_File_JB in "CSC" field with Odin (passed installed successfully but still not working).
9, installing "N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar" full new Android OS with Odin (passed installed successfully but still not working).
Finlay there is No Samsung Service Center in my country, i need to send it by mail to nearest country have Samsung Service Center and will cost me a lot .. what i have to do
Weeshi said:
i have same problem with my Note 10.1 N8000 stuck in bootloop problem but i didn't do anything like upgrading or install new app ... its stuck by him self and i tried the following and all not working :
1, Hard Reset with software menu (not working)"only if the device is working".
2, Hard Reset with Dial secret code key(not working) "only if the device is working".
3, Hard Reset with Hardware Key Button(Factory recovery screen not working).
4, installing recovery philz_touch_6.07.9-n8000.tar with Odin (passed installed successfully but still not working).
5, installing recovery openrecovery-twrp-2.4.1.0-p4notewifi_3 with Odin (passed installed successfully but still not working).
6, installing recovery CF-Auto-Root-p4noterf-p4noterfxx-gtn8000.tar with Odin (passed installed successfully but still not working).
7, installing recovery twrp-2.6.3.1-n8000.tar with Odin (passed installed successfully but still not working).
8, installing recovery Samsung_N8000_Hard_Reset_File_JB in "CSC" field with Odin (passed installed successfully but still not working).
9, installing "N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar" full new Android OS with Odin (passed installed successfully but still not working).
Finlay there is No Samsung Service Center in my country, i need to send it by mail to nearest country have Samsung Service Center and will cost me a lot .. what i have to do
Click to expand...
Click to collapse
I have the same problem. I was just playing a game when it suddenly turned off and went to the boot screen. Also tried installing N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar.md5 (success but also didn't work). Still stuck at the "Samsung Galaxy Note 10.1" screen.
Also can't access recovery, or do a wipe before installing firmware (I think USB debugging isn't turned on).
Did you find any solutions yet?
Thanks.
el_roi said:
I have the same problem. I was just playing a game when it suddenly turned off and went to the boot screen. Also tried installing N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar.md5 (success but also didn't work). Still stuck at the "Samsung Galaxy Note 10.1" screen.
Also can't access recovery, or do a wipe before installing firmware (I think USB debugging isn't turned on).
Did you find any solutions yet?
Thanks.
Click to expand...
Click to collapse
Sorry till now no solutions ... If you have warranty on the device go to the samsung maintenance center i think its wrong factory made
Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode
migimantas said:
Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode
Click to expand...
Click to collapse
I have found that my emmc has the insane chip bug. The phone boots normally with cyanogen mode 11 but then it goes to sleep mode or I press the power button the screen goes black and the phone restarts. I have tried siyah kernel to try dual boot but then I flash siyah I cant get into recovery.
I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...
twinsen.net said:
I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...
Click to expand...
Click to collapse
I have already tried this but with the stock rom phone boots but at the section where I have to chose language I jus freezes stops working
So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.
twinsen.net said:
So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.
Click to expand...
Click to collapse
Take it straight away to the official service centre