Ok,
GT-N8000 was on stock Samsung 4.1.2 Rom. Rooted using Chainfire, installed CWM 6.0.3.6 and then flashed a CM11 rom from here on XDA.
Rebooted happily, logged in, set-up the tablet and happily worked for about 24 hours.
Tablet at some point rebooted, got only as far as the first "Samsung Note 10.1" white text on the screen and the tablet refused to do anything else.
Can boot into CWM recovery
Can boot into Odin Mode "Downloading"
When booting into Recovery, I can browse all the options, but when selecting any action, the tablet reboots.
Have tried downloading a fresh stock rom (4.4.2 from Vietnam from Samfirmware), and flashing via ODIN. Odin seems to flash OK, but when the device reboots, straight back into "Samsung Note 10.1" screen.
After that flash, when trying to boot into recovery, it still goes to CWM and not the stock Recovery.
Have tried downloading a new PIT and flashing that when flashing the new stock ROM.
Have tried Googling several items, and here on XDA, but not entirely sure where to try next. Suggestions would be welcome.
cdinoz said:
Ok,
GT-N8000 was on stock Samsung 4.1.2 Rom. Rooted using Chainfire, installed CWM 6.0.3.6 and then flashed a CM11 rom from here on XDA.
Rebooted happily, logged in, set-up the tablet and happily worked for about 24 hours.
Tablet at some point rebooted, got only as far as the first "Samsung Note 10.1" white text on the screen and the tablet refused to do anything else.
Can boot into CWM recovery
Can boot into Odin Mode "Downloading"
When booting into Recovery, I can browse all the options, but when selecting any action, the tablet reboots.
Have tried downloading a fresh stock rom (4.4.2 from Vietnam from Samfirmware), and flashing via ODIN. Odin seems to flash OK, but when the device reboots, straight back into "Samsung Note 10.1" screen.
After that flash, when trying to boot into recovery, it still goes to CWM and not the stock Recovery.
Have tried downloading a new PIT and flashing that when flashing the new stock ROM.
Have tried Googling several items, and here on XDA, but not entirely sure where to try next. Suggestions would be welcome.
Click to expand...
Click to collapse
Have you tried full erase(factory reset) via recovery mate including the internal SD? And remove the external SD just to make sure, then reinstall the stock 4.4.2 firmware. Can I ask why did you install vietnam version when you are in Australia? Where did you get the pit file? Is it for 4.4.2?
filchi756 said:
Have you tried full erase(factory reset) via recovery mate including the internal SD? And remove the external SD just to make sure, then reinstall the stock 4.4.2 firmware. Can I ask why did you install vietnam version when you are in Australia? Where did you get the pit file? Is it for 4.4.2?
Click to expand...
Click to collapse
When in CWM and trying to full reset, the tablet reboots a few seconds after selecting the option. Have removed sim and sd card prior to flashing.
Vietnam was one of three roms I was d/l from Sam mobile. I was trying to grab various roms, but they were getting to 70/75% and then failing. I have also tried flashing now a Singapore rom and a German rom. Cannot find an Aussie stock rom on that site anywhere, or anywhere else for that matter, which will download.
Have successfully flashed other region roms on other Samsung devices, so assumed this model would be no different.
PIT file was a last resort effort, found here....http://forum.xda-developers.com/showthread.php?t=2730188
After flashing any stock rom, the tablet continues to not restart, but still let's me boot into CWM oddly (should flashing a stock rom via Odin reinstall stock Recovery?).
cdinoz said:
When in CWM and trying to full reset, the tablet reboots a few seconds after selecting the option. Have removed sim and sd card prior to flashing.
Vietnam was one of three roms I was d/l from Sam mobile. I was trying to grab various roms, but they were getting to 70/75% and then failing. I have also tried flashing now a Singapore rom and a German rom. Cannot find an Aussie stock rom on that site anywhere, or anywhere else for that matter, which will download.
Have successfully flashed other region roms on other Samsung devices, so assumed this model would be no different.
PIT file was a last resort effort, found here....http://forum.xda-developers.com/showthread.php?t=2730188
After flashing any stock rom, the tablet continues to not restart, but still let's me boot into CWM oddly (should flashing a stock rom via Odin reinstall stock Recovery?).
Click to expand...
Click to collapse
Suppose to be when you install full rom the custom recovery is erased and back to stock recovery. What version of pc Odin are you using? Try ver.1.85 or 3.07 if you haven't yet. And just to be sure have you installed any other 4.4.2 rom prior to stock 4.4.2?And maybe you can try philz recovery for custom recovery.
filchi756 said:
Suppose to be when you install full rom the custom recovery is erased and back to stock recovery. What version of pc Odin are you using? Try ver.1.85 or 3.07 if you haven't yet. And just to be sure have you installed any other 4.4.2 rom prior to stock 4.4.2?And maybe you can try philz recovery for custom recovery.
Click to expand...
Click to collapse
Odin - have tried 1.85, 3.07 and 3.09
Rom - When the tablet was on stock 4.1.2, was rooted following method (2) here: http://forum.xda-developers.com/showthread.php?t=1831152 and had installed CWM 6.0.3.6. After gaining root, copied zip files for this rom http://forum.xda-developers.com/showthread.php?t=2550308 to the externalSD and performed a factory reset, wiped data etc and flashed OminRom 4.4. This booted happily, and worked for about 24 / 36 hours (ish) when it's owner claimed it rebooted at some point, and came back only the the "Samsung Galaxy Note 10.1" white text boot screen, and went no further
Recovery - Since the issue first started, have tried various flavours of re-flashing CWM (both Touch and Non Touch), TWRP mostly from here: https://goo.im/devs/Darkman/Recoverys/ and a Philz Touch recovery sourced from here: http://forum.xda-developers.com/showthread.php?t=2202714
Each time have been flashed using Odin and using the .tar.md5 file types (as the CWM simply crashes and the tablet reboots now when trying to flash a zip via recovery). Have set Odin NOT to auto-reboot, however whilst Odin reported no obvious sign of error, upon reboot to Recovery, went straight to the previous CWM 6.0.3.6 recovery.
And now my head hurts......
Note: I did say in the opening post was a CM11 based rom, but it actually was an AOSP based rom,
cdinoz said:
Odin - have tried 1.85, 3.07 and 3.09
Rom - When the tablet was on stock 4.1.2, was rooted following method (2) here: http://forum.xda-developers.com/showthread.php?t=1831152 and had installed CWM 6.0.3.6. After gaining root, copied zip files for this rom http://forum.xda-developers.com/showthread.php?t=2550308 to the externalSD and performed a factory reset, wiped data etc and flashed OminRom 4.4. This booted happily, and worked for about 24 / 36 hours (ish) when it's owner claimed it rebooted at some point, and came back only the the "Samsung Galaxy Note 10.1" white text boot screen, and went no further
Recovery - Since the issue first started, have tried various flavours of re-flashing CWM (both Touch and Non Touch), TWRP mostly from here: https://goo.im/devs/Darkman/Recoverys/ and a Philz Touch recovery sourced from here: http://forum.xda-developers.com/showthread.php?t=2202714
Each time have been flashed using Odin and using the .tar.md5 file types (as the CWM simply crashes and the tablet reboots now when trying to flash a zip via recovery). Have set Odin NOT to auto-reboot, however whilst Odin reported no obvious sign of error, upon reboot to Recovery, went straight to the previous CWM 6.0.3.6 recovery.
And now my head hurts......
Note: I did say in the opening post was a CM11 based rom, but it actually was an AOSP based rom,
Click to expand...
Click to collapse
So that means you can't even install custom rom?Can I ask what version is written in download mode is it still N8000?
filchi756 said:
So that means you can't even install custom rom?Can I ask what version is written in download mode is it still N8000?
Click to expand...
Click to collapse
Correct. If I try to flash via CWM, the tablet goes thru the motion of flashing the rom (the bit where the developers ascii logo appears) followed by the little blue line telling you the custom rom is installing, and after a few seconds tells you that the flash is complete.
The giveaway is that this entire process takes about 15 seconds - and you just know that the rom has not flashed. The second is that immediately when it completes, the tablet (yes you've guessed what happens next...) just reboots back to the Samsung logo.
But yes, when in download mode, the tablet is definitely reporting as still as a GT-N8000. Its also has some other text (sorry the thing is not in front of me right now) about the binary counter of 3...?
Cheers
cdinoz said:
Correct. If I try to flash via CWM, the tablet goes thru the motion of flashing the rom (the bit where the developers ascii logo appears) followed by the little blue line telling you the custom rom is installing, and after a few seconds tells you that the flash is complete.
The giveaway is that this entire process takes about 15 seconds - and you just know that the rom has not flashed. The second is that immediately when it completes, the tablet (yes you've guessed what happens next...) just reboots back to the Samsung logo.
But yes, when in download mode, the tablet is definitely reporting as still as a GT-N8000. Its also has some other text (sorry the thing is not in front of me right now) about the binary counter of 3...?
Cheers
Click to expand...
Click to collapse
About the binary thats not a problem. So your problem now is error flashing via CWM right? Try Philz recovery mate in custom rom installing. And make sure your custom rom is fully working and tested mate. Try to open the zip in pc if it had any error. And how about installing a custom recovery any luck with it installing too?
filchi756 said:
About the binary thats not a problem. So your problem now is error flashing via CWM right? Try Philz recovery mate in custom rom installing. And make sure your custom rom is fully working and tested mate. Try to open the zip in pc if it had any error. And how about installing a custom recovery any luck with it installing too?
Click to expand...
Click to collapse
But there lies the problem.
I have tried flashing Philz both via Odin and via CWM.
It "appears" to flash in Odin, but when the tablet starts, its still CWM.
When flashing in CWM, it fails to flash. (I'll get you the error message when I'm back in front of the tablet).
So, here is Philz Recovery flashing in CWM, showing a successful flash:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
And after a reboot:
Still in CWM 6.0.3.6 (apologies for the terrible image - using my Tab Lite)
cdinoz said:
So, here is Philz Recovery flashing in CWM, showing a successful flash:
[/IMG]
And after a reboot:
Still in CWM 6.0.3.6 (apologies for the terrible image - using my Tab Lite)
Click to expand...
Click to collapse
lastly mate can you take a picture of you download mode were the binary is written.
cdinoz said:
So, here is Philz Recovery flashing in CWM, showing a successful flash:
[/IMG]
And after a reboot:
Still in CWM 6.0.3.6 (apologies for the terrible image - using my Tab Lite)
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...ot-charge-power-off-efs-t2809821/post54680214
Related
Hi guys!
Yesterday I successfully rooted my NS (it is a European SLCD model with stock 2.3.6 on it) following the newest guide on nexusshacks.com. So I ended up with TWRP recovery.
Then I thought the easiest to install CM is via Rom Manager. Therefore I had to change recovery for CWM. (I flashed the latest one.)
And here comes my question: why am I unable to flash CM?
First I tried it in Rom Manager, after wiping everything and rebooting system nothing happens, except for a big yellow exclamation mark.
Then I downloaded the proper CM myself and I tried to do the whole process manually in recovery menu. After wiping and choosing update from SD card I get a message like the process is aborted.
I also tried with an older CWM and with other ROM.
Any suggestions?
Thanks a lot
Sent from my Nexus S using XDA App
Boot into bootloader, then flash recovery via fastboot.
fastboot flash recovery recovery.img
stock firmware will rewrite your recovery after each boot. flash recovery then flash this right after.
Follow what SEAN SAys..............He is a Master in all these , and he helped me with details to root, flash cwm, make it sticky and flash custom ROMS.
It took me 5 minutes to do all those , and Now I am switching Roms like I switch my underwears every day twice.
I must say, Sean has the best possible way which is like a finger click.
So, last night I was updating my phone to a newer version of Paranoid Android. In the process, I accidentally flashed TWRP over my preexisting flash of CWM and, in both being unfamiliar with TWRP, and an apparent conflict between the flashes, it soft bricked my phone. Most of my day has been spent recovering my phone.
I was able to restore my phone to stock using the excellent guide found here: http://forum.xda-developers.com/showthread.php?t=1840030
Then spent the next couple of hours installing updates, at which point I was eager to reflash my custom roms, etc.
Problem is, I can't get the phone to boot into CWM (or TWRP). Just goes to stock recovery. I've tried flashing the lazy way in ROM Manager, and in Odin (reads PASS), but it always goes to stock recovery. For that matter, in trying to flash with ROM Manager, it reads "an error occurred while trying to flash..."
Ideas?
TheBuzzard said:
So, last night I was updating my phone to a newer version of Paranoid Android. In the process, I accidentally flashed TWRP over my preexisting flash of CWM and, in both being unfamiliar with TWRP, and an apparent conflict between the flashes, it soft bricked my phone. Most of my day has been spent recovering my phone.
I was able to restore my phone to stock using the excellent guide found here: http://forum.xda-developers.com/showthread.php?t=1840030
Then spent the next couple of hours installing updates, at which point I was eager to reflash my custom roms, etc.
Problem is, I can't get the phone to boot into CWM (or TWRP). Just goes to stock recovery. I've tried flashing the lazy way in ROM Manager, and in Odin (reads PASS), but it always goes to stock recovery. For that matter, in trying to flash with ROM Manager, it reads "an error occurred while trying to flash..."
Ideas?
Click to expand...
Click to collapse
Do you want CWM or TWRP? If TWRP, you could just download GooManager from the Play Store and press Menu/Install Open Recovery Script.
For flashing either via Odin, deselect auto reboot in Odin then flash the recovery tar. Once its passed, pull the battery and boot directly into your custom recovery.
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
Do you want CWM or TWRP? If TWRP, you could just download GooManager from the Play Store and press Menu/Install Open Recovery Script.
For flashing either via Odin, deselect auto reboot in Odin then flash the recovery tar. Once its passed, pull the battery and boot directly into your custom recovery.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for the advice, but I got it working.
Tried Odin one more time, and it's booting into CWM properly now. Not sure why it didn't "take" the other 2-3 times that I followed the identical procedure, but it appears that my problems are fixed now.
So I've been play with Android for a few years now and I love it. Got the Samsung Galaxy Note 10.1 in the fall of 2012 and had a custom rom installed not long after. Periodically I check XDA to see if there is a new custom ROM I want to try. Finally there is, OMNIRom. It says I need a recovery image that can handle the new SELinux. After poking around for an easy way to update I findout that the goo.im has a new recovery that it will install. And that's where things go south. I installed the new TWRP v2.6.3.0 via the goo.im and then reboot into the recovery. I go to flash the new ROM and it fails. I try downloading the ROM again and flashing it. It fails again. Okay, shouldn't be a problem... I'll just flash my prior rom. It too fails. Uh-oh.... If I try to boot normally, it just loads directly to the faulty TWRP. If I try to boot to the bootloader so I can use Heimdall to flash over a new recovery, it boots to TWRP....
I found a new recovery in a ZIP format finally and tried to use that, but it fails too.
Any advice? Suggestions? Please help.
Hi all,
I was running the new SaberMod Carbon ROM for a few days and decided I didn't like it so I tried to restore a nandroid back up of what I had been running before (rwilco's mostly stock). The phone wouldn't reboot after restoring the backup, it would start and then go right back to recovery. Then I tried just flashing the rwilco's mostly stock as new instead of from a back up, and that had the same results - said it was complete but when I selected reboot phone it just went back to recovery. So I decided to flash the stock tar in Odin, but that kept failing. Now I can't get into recovery, it says something about an update being interrupted. I can get into download mode, but the stock firmware keeps failing in Odin.
I am guessing here that my problem is that the SaberMod rom is based on 5.1.1 and the stock firmware for the G900P (as well as the other rom and backup I tried) are 5.0.0, and I remember hearing you can't go back to an older firmware version. Does this sound right? and if so how do I get my Galaxy working again?
TIA for all help and suggestions!
daniel3x said:
Flash the TWRP recovery in odin
After that enter in recovery mode and format system, data, cache, dalvik cache, sdcards.
Then put the phone into download mode, and flash with odin the last stock rom (OG1) but make sure you don't have selected the "reboot" option in odin
After you got your phone flashed, take the battery out put it again and enter in recovery mode, choose "wipe data/factory reset"
Then put your phone in download mode and flash again the stock rom (OG1) this time with the "reboot" option selected
After you flashed your phone the first boot takes some minutes (in the yellow screen), just be patient.
After this you should have your phone complety clean and your problem solved.
DOWNLOADS
Odin 3.10.7
Stock Rom OG1
TWRP 2.8.7.0
Click to expand...
Click to collapse
Try this
I have phillz recovery on it right now....can't get into the recovery though since it says a firmware update was interrupted. Would TWRP be better than phillz? and would flashing that get it past the firmware interrupted message?
I tried starting by flashing TWRP but that fails too....any other suggestions?
Can't flash anything in Odin, everything fails. Any other ideas before this thing goes for a swim in the sink?
Hi
This is really frustrating. I own many Samsung devices and never had any issue installing twrp, so I am not a noob when it comes to firing up Odin and flashing the image however I am stuck with this device.
I used couple guides with no success. ;( I cant get rid of the Samsung recovery and replace with TWRP. Odin says success but that is just a lie.
I tried both the lollilop bootloader and the older one then TWP with various versions (3.1x , 2.8.x) No luck.
Can anyone please provide me "working files" with "simple steps" in case I am missing out on some minor details. This is SM-P900 Kitkat 4.4.2 version.
- I flash the bootloader using the BL slot in dl mode
- I reboot to downloader again and and install TWRP
- I type adb revoot recovery
Boom, I am back to frigging Samsung recovery
Hi ,
This is a follow up
The only guide that worked for me is this one. It might be helpful to others.
https://forum.xda-developers.com/ga...guide-install-official-lollipop-p900-t3154362
I had trouble getting TWRP to take at first too. It seems Samsung overwrites the recovery upon rebooting so even though TWRP flashed successfully it just gets overwritten when the system restarts. The simple solution for me was to disable the Reboot option in Odin, install TWRP, manually shut down and then enter Recovery mode. Hope that helps. I came across this suggestion either in the thread linked to above or while googling.
Im installing into properly rooted and I have twrp 2.8.7. I want 3+ TWRP.
I flash with PDA/AP and with "autoreboot" unchecked. I power off and power+home+volUP for recovery.
Tablet enters a "enttering recovery" bootloop which can be only disrupted by going into power+home+volDWN to enter Download, and than I can flash with ODIN 2.8.7.
2.8.7 is the latest I can boot into. WHAT IS WRONG?!!!!!!!!! I lost hope, with flashing 100x
Did you try updating TWRP from inside TWRP?
Sent from my Samsung SM-P900 using XDA Labs
try do a full wipe from stock recovery . after that flash twrp selecting the ap and bl in ODIN twrp3.1....tar booth of them (AP & BL)
no no no i tried everything. but than I found out this post : https://s4.postimg.org/s3pel2ekd/this_guy.png and that solved the day!!
With p900 work perfect, but install hard. With this twrp 3.1 i install lineage 14.1, all works good.