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
Related
Hi,
I've recently flashed ClockWorkMod Recovery using Odin to my Samsung Galaxy mini S5570 device,
the opertion was succesfull (Odin said PASS), but now when I try to boot into Recovery (pressing Middle button and power button) the device just get stuck in the Samsung screen (the first screen you see when you regulary power on your device).
Will be glad for some help!
*Any Ideas how to fix this problem? or why does it occur?
1) Will HardReset/FactoryReset the phone will uninstall ClockWorkMod Recovery?
2) Do I need to ROOT my device prior to the flashing of ClockWorkMod Recovery with ODIN?
3) Can I remove/uninstall the ClockWorkMod Recovery?
Thanks advanced for your help!
Same issue
Hello,
I've got exactly the same issue and do not find any answer
Thank you for your help!
Etienne
Same here..
Same problem here, It just shows the samsung logo and that's all, I can't finish installing firmware
Stuck with first screen
I am also stuck with the opening screen. Prior being bricked the phone went through the washing machine. Board was cleaned. It still has carrier SIM lock on it. I am digging the forum for imput, but no luck so far.
With USB clable plugged in it shows only a small phone and computer icon with yellow triangle+exclamation mark on the dotted line between them. Cannot load the hard reset menu. The Download menu with big triangle comes up, that showed at least the display is working.
Odin 4.38 was able to flash the Clockworkmod, but no Gingerbread or some other update. The time runs happily but MIBIB will not load, and i must turn everything off.
I have the same issue. Wondering if there is a fix for this. Can boot into download mode but not Clockworkmod Recovery. Stuck at Samsung screen.
Okay well I found a fix!
I was trying to update CWM Recovery via Odin when I still had Froyo installed on the device. Classic rookie error. You need gingerbread to use the latest CWM. All I had to do was install an official samsung gingerbread ROM via Odin and then I was able to re-install CWM sucessfully. Now running CM9 on my Galaxy Mini and everything is great, very snappy (few bugs though)
Hello, I will try to explain how I got myself into my current situation which is kinda helpless and it ends up with the SGS II Logo on screen.
I rooted my phone - no problem
Flashed an Insecure Kernel - no problem
Flashed - CWM - no problem
Then I tryed to put the Ressurecion ICS mode.
Started CWM mode, wiped all data but for some reason soon afterwards my phone
turned off. When I started it again it always ended up at samsung logo screen :/
I can put it in download mode. I tryed to flash roms, with or without pit files.
When I do so I get this screen like terminal with many signs like "failed to load booth catche" etc, unable to mount,etc. Then I get the option to either reboot,to wipe data catche or factory reset. No matter what I choose I always end up at logo screen. Please,I beg of you help me !!
SinisterHatred said:
Hello, I will try to explain how I got myself into my current situation which is kinda helpless and it ends up with the SGS II Logo on screen.
I rooted my phone - no problem
Flashed an Insecure Kernel - no problem
Flashed - CWM - no problem
Then I tryed to put the Ressurecion ICS mode.
Started CWM mode, wiped all data but for some reason soon afterwards my phone
turned off. When I started it again it always ended up at samsung logo screen :/
I can put it in download mode. I tryed to flash roms, with or without pit files.
When I do so I get this screen like terminal with many signs like "failed to load booth catche" etc, unable to mount,etc. Then I get the option to either reboot,to wipe data catche or factory reset. No matter what I choose I always end up at logo screen. Please,I beg of you help me !!
Click to expand...
Click to collapse
Have you tried returning it to stock with a one-click return to stock ? you will lose your root permissions but they are easy to get back lol
I havent tryed it. Isnt it just for nexus too ? And I cant enter my phone so I could just USB debugging :X
SinisterHatred said:
I havent tryed it. Isnt it just for nexus too ? And I cant enter my phone so I could just USB debugging :X
Click to expand...
Click to collapse
yea alot of samsung phones have one click return to stock
you just need to get it into download mode (probably by holding volume down and power at the same time then connecting ur usb i can provide links just PM me
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:
revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.
tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi
Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium
freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.
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
Hi,
Hoping someone can help, it switches on then stays on the screen which say "Samsung Galaxy note 10.1" and will not continue. Have tried to use odin to reload with stock firmware, it seem to complete fine, but that does not resolve the problem. is it completely broken or is there something else i can try.
Thanks
Similar issue here....
I'm having the same problem, I had my GT-N8013 running just fine with Omni ROM, booted into recovery (CWM 6.0.3.6) asked me to fix root, clicked yes tablet rebooted into ROM just fine. Then the following morning I woke up and it was stuck on the Samsung Galaxy Note 10.1 logo. I can still boot into recovery and Download mode but I'm not able to restore it back to stock or install a new Recovery through ODIN or CWM. Everything passes just fine every time but once it reboots its still stuck on the logo. I'm also unable to mount, access or format /data and /sdcard on CWM. I'm starting to suspect the eMMC is corrupt and I'll have to send it back to Samsung.If it comes to that this will be the last Samsung product I'll ever buy again.