I tried to root my wifi Note 10.1(wifi) using TWRP and the SuperSU flashable zip, but when wiping cache and Dalvik the tablet shut down. Now when I try to boot the device it only plays part of the boot sound and gets stuck on the "Samsung" logo. I've tried searching for ODIN flashable stock firmware, but with Hotfile being down(sammobile's file host) and the rest requiring a paid subscription to their site, I'm screwed.
I've tried using Kies' emergency recovery option, but it won't recognize the device as needing recovered. When I try to search for updates through Kies it tells me the model name is invalid(P600, SMP600, SM-P6000ZKYXAR, Galaxy Note 10.1 2014).
I can still boot into download mode and TWRP.(I REALLY should have made a backup first.)
All I need is the stock US(XAR) firmware, preferably ODIN flashable. I'm not sure if I trust TWRP to flash it just yet considering it crashed wiping dalvik, but if it's my only option I'm willing to try it.
I have seen somewhere that TWRP is a bit temperamental on our devices with wiping cache, and you sometimes have to do it twice, have you tried it the 2nd time ?? Use the advanced menu, wipe cache and reboot.
Edit
http://forum.xda-developers.com/showthread.php?p=47379905&highlight=cache#post47379905
i did this
::
jpearn said:
I have seen somewhere that TWRP is a bit temperamental on our devices with wiping cache, and you sometimes have to do it twice, have you tried it the 2nd time ?? Use the advanced menu, wipe cache and reboot.
Edit
http://forum.xda-developers.com/showthread.php?p=47379905&highlight=cache#post47379905
Click to expand...
Click to collapse
It took a long time to finish, but it successfully wiped the cache the second time and booted successfully! Thanks for the link by the way.
Related
Hi guys and gals,
I'm kind of new to this, so this issue may be trivial for most. I have successfully rooted to tab pro 10.1, have flashed TWRP, and have loaded custom ROM zips on my external SD. My problem is that when I try to flash most rooms, it ends up saying failed. The one that does actually show successful(ProPlusV1), will allow me to boot but then shows processes force stopping, and then sends me into a boot loop.
Is there something i'm doing wrong or missing. I searched the forums(maybe not as well as most), and was not able to find anyone with the same issue.
Any help is appreciated!!
Camron
Did you do an advanced wipe before you installed the roms? Advanced = wipe system, data, cache, dalvik cache. Then factory reset. This is my standard mode and I don't have problems. Which rom in particular are you trying to install?
Did you try wiping everything except external sd in TWRP? I tried that rom for my 12.2 and ended up with the Samsung logo followed by a black screen and ended up restoring my backup. It's still a test version for the 10.1 and 12.2 so I wasn't expecting much. Maybe try this one: http://forum.xda-developers.com/showthread.php?t=2776206
based on the stock rom that comes with US tablets. The last time I tried downloading, it kept failing at about 75%. I think I'll try again tonight.
---------- Post added at 11:39 PM ---------- Previous post was at 11:27 PM ----------
k8108 said:
Did you do an advanced wipe before you installed the roms? Advanced = wipe system, data, cache, dalvik cache. Then factory reset. This is my standard mode and I don't have problems. Which rom in particular are you trying to install?
Click to expand...
Click to collapse
Just saw your post after submitting mine. What is the factory reset doing after wiping everything? I'm still fairly new to this.
I have a very similar problem, though I don't consider myself new to flashing.
I did advanced wipe (system, dalvik, cache, and data), though TWRP was complaining about being unable to mount /cache. I also had to select "use rm -rf instead of formatting", because formatting didn't work (recovery would reboot). Then I tried flashing the ROM linked (the GigaWatts Pro), but it would not boot (gets stuck on black screen after boot logo).
Since I had a backup of the stock ROM, I figured this wouldn't be a problem. But now TWRP can't mount /system and therefore I can't restore my backup - it just says "failed".
Deusdies said:
I have a very similar problem, though I don't consider myself new to flashing.
I did advanced wipe (system, dalvik, cache, and data), though TWRP was complaining about being unable to mount /cache. I also had to select "use rm -rf instead of formatting", because formatting didn't work (recovery would reboot). Then I tried flashing the ROM linked (the GigaWatts Pro), but it would not boot (gets stuck on black screen after boot logo).
Since I had a backup of the stock ROM, I figured this wouldn't be a problem. But now TWRP can't mount /system and therefore I can't restore my backup - it just says "failed".
Click to expand...
Click to collapse
Try a factory reset? I'm not sure what it does after you've already wiped everything. I've soft bricked my tablet in a similar fashion with the same symptoms as you except TWRP wouldn't even load after a couple mounting failures. Here's what worked for me. I downloaded the stock firmware for my tablet from here: http://www.sammobile.com/firmwares/
Enter your model # where it says "search device here..." and download for your region. If you're in the US you'll want Cellular south. Extract the .tar.md5 file then run Odin 3.09 as admin and install using the AP button. If using Odin 3.07 use the PDA button. I'm pretty sure I had to re root and reinstall TWRP after that. I was then able to restore my backup. I've soft bricked my tablet a few times playing with custom roms. Hope this helps.
I'm fairly new to this, so if I've made any mistakes, someone please chime in b4 Deusdies reads this.
thanks for this. you should also mention the unbelievably long download time of over 2 hours if you're not a premium member of sammobile.
I had the same problem.
Mount data partition in recovery, and flash the zip from Internal SD.
Sent from my SM-T520 using Tapatalk
I've looked around a bit and can't quite find someone that has had my specific situation.
I have a AT&T S3 SGH-I747 that is rooted running stock 4.1.1 with CWM 6.0.4.7. I have updated the modem and bootloader (Baseband - I747UCUEMJB and Build # JRO03L.I747UCDLK3).
I have tried to flash custom and stock ROMS with CWM but get stuck on the glowing Samsung logo. I have tried to follow the instructions listed here but I cannot flash the stock ROM with ODEN.
I am not sure as to what to attempt next. I first want to be able to update to 4.3/4.4.2 and then try custom builds.
I have all my apps and data backed up with MyBackup and a Nandroid backup as well.
Thank you.
Are you wiping the cache, davilk, and data before of after flashing the ROM?
I wipe/format before the flash. I factory reset, clear cache, clear davilk, format data, and format system then flash the ROM. I've tried several combinations of clearing/formatting. The flash always goes well and then I reboot. The boot goes and then just sits at the Samsung logo (It does make the AT&T sound during this time)
Hubbins said:
I wipe/format before the flash. I factory reset, clear cache, clear davilk, format data, and format system then flash the ROM. I've tried several combinations of clearing/formatting. The flash always goes well and then I reboot. The boot goes and then just sits at the Samsung logo (It does make the AT&T sound during this time)
Click to expand...
Click to collapse
Try to factory reset once the flash is done if it doesn't boot after 5-10min.
Thanks. I'll give it a shot and we'll see how it goes.
Unfortunately that tip did not appear to help. I still got stuck on the glowing Samsung logo.
I was final able to flash 4.3 using the method here using odin.
I flashed a rom and then this problem started happening since. My phone tries to go to the samsung boot animation screen but never goes through it, it vibrates and then reboot, i tried installing stock rom, etc, i can now go to recovery and download mode.
You might need a jtag
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
errusdan said:
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
Click to expand...
Click to collapse
I Can install firmware through download mode.!""
Me too, i tried installing stock firmware and all that. Even i am able to use the aroma filemanager from recovery, to see all my files, and when i delete system, preload, data, cache, etc i can see that in fact the device deletes them correctly.
Sorry I miss understand, you can go in download and recovery, my bad.
Have you tried factory reset, Flash original firmware, factory reset, let it boot
What was your original firmware which file(s) did you use?
When the thing you said happened i went on the store and Luckly they replaced my phone. Your phone probably ruined thats what happens when you play with it:cyclops:
Yeah i know that there are risks when you install another roms and such. I've read that it can corrupt your internal sd card, maybe that is what happened to me? because i tried installing different firmwares, kernels, recoveries, wipe data, wipe cache, wipe dalvik cache, wipe system, wipe preload, etc, even i tried installing boot animations, and it stucks at the boot animation screen samsung galaxy, it tries to load but then it vibrates and restart like a loop.
I am now with the russian 4.4.2 rom, and yes i know that i cannot downgrade because of the bootloader version. But i tried installing modified roms with zip (like cm 11) in recovery, and it installs correctly without errors, the problem is with the bootloop.
I have tried the roms below:
Pac-rom
LiquidSmooth
CyanogenMod 12.1
CyanogenMod 11
And the result is it always gets stuck at boot where the boot animation continues infinitely. I have gave it about 30 minutes to boot.
With LiquidSmooth I was able to run logcat, but CM12.1 I am not able to.
I have tried resetting system, data, caches in twrp and using the reset for new rom in philz.
I have tried flashing with both TWRP and Philz.
I am using the latest Philz and TWRP.
The only thing that has worked for me is samsung stock ROM, but I do not like the stock ROM.
Are there SPH-L900 phones you have to do something different?
Is there a way to get boot logs from CM12?
Am I doing something wrong?
See attachment from LiquidSmooth.
After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.
GRMrGecko said:
After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.
Click to expand...
Click to collapse
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks
Raziel10000 said:
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks
Click to expand...
Click to collapse
Followed this guide from some post I found after reading for 8 hours, LOL. Don't remember who it is from... It's for the Cyanide ROM but worked perfect for CM12.1 latest nightly with the latest GAPPs
1.) revert everything to stock
Using Odin3 v3.09 I first flashed this: L900VPUCNE2_L900SPTCNE2_SPR.zip
2.) Reboot and verify it's not bricked, then use ODIN to flash Philz philz_touch_6.15.4-l900.tar.md5
3.) Reboot into Philz recovery and follow these steps exactly
1. Mounts and Storage
Format / system
Format / cache
Format / data
Format / data and /data /media (/sdcard)
(note this isn't the EXTERNAL sdcard, on to which I had loaded the ROM, Shift and gapps)
2. Power Options > reboot recovery
3. Wipe cache partition
4. Advanced > Wipe dalvik cache
5. Wipe data / factory reset > Wipe data / factory reset
6. Wipe data / factory reset > clean and install new ROM
At one point Philz asked me if I wanted to root and I said yes.
3.) Flash (from the external sdcard) the ROM (Tablet style ROM found in OP "5.0.2-RC-7.1-tablet"), Then flash Shift (Shift-LP-4.3 other versions DID NOT WORK), then flash gapps (GApps-5.0.2-20150315-signed NO OTHER VERSION WOULD FLASH, got Error 20 every time) Here's the
After everything was flashed I rebooted and got stuck at boot animation AGAIN, so I rebooted into recovery and wiped cache. Just cache, not dalvik or user data, rebooted, and it worked.
Installed Netflix from appstore, when I logged in to netflix it asked me to update google play services (I've seen it do this on other devices as well). Updated google play services and went back to Netflix, chose a random show and tapped on it, stuck at "loading" screen. Rebooted phone, tried netflix again and it works.
This was a tough one! But it's working now and I've saved all these files in one place incase it bricks again. Now to install the Note 3/4 style faux-stitched-leather back cover I got off Amazon.
Thanks all!
Hi, phones been running great until yesterday when it started telling me the disk space was nearly full(via es filee xplorer). It then turned off a few times and i turned it on again. The phone would shut off if I tried to do anything like launch the camera app. It now bootloops when i try to turn it on.
I have tried wiping dalvic cache, factory reset, recover from a recovery point i made when i installed the cm13 rom and reinstalling the custom rom like I did the first time using twrp.
The phone did once go into a boot animation of the old boot screen(02 animation), another time it started the miui boot logo but went back to the normal samsung galaxy note 2 boot loop where its stuck at now.
Any suggestions on how i could get it running again? Thanks!
Note2mk said:
Hi, phones been running great until yesterday when it started telling me the disk space was nearly full(via es filee xplorer). It then turned off a few times and i turned it on again. The phone would shut off if I tried to do anything like launch the camera app. It now bootloops when i try to turn it on.
I have tried wiping dalvic cache, factory reset, recover from a recovery point i made when i installed the cm13 rom and reinstalling the custom rom like I did the first time using twrp.
The phone did once go into a boot animation of the old boot screen(02 animation), another time it started the miui boot logo but went back to the normal samsung galaxy note 2 boot loop where its stuck at now.
Any suggestions on how i could get it running again? Thanks!
Click to expand...
Click to collapse
Tried putting stock rom back on but still bootlooping. When i go into android system recovery it says twice
E:failed to mount /efs (Invalid argument)
Search for efs.tar file on the internet for n7100, flash it via Odin then wipe data, cache and davlik cache.
Skull97 said:
Search for efs.tar file on the internet for n7100, flash it via Odin then wipe data, cache and davlik cache.
Click to expand...
Click to collapse
Thanks. Any instructions /tutorials on how to flash an efs file?
Is it the same procedure as flashing a stock ROM using Odin?
Note2mk said:
Thanks. Any instructions /tutorials on how to flash an efs file?
Is it the same procedure as flashing a stock ROM using Odin?
Click to expand...
Click to collapse
It should use the same procedure as flash stock ROM. I'm not sure because the last time I did it was some years ago.
I have found another way, it's a bit hard, but safer
http://www.selftechgenius.com/how-t...nvalid-argument-in-all-samsung-galaxy-phones/
Skull97 said:
It should use the same procedure as flash stock ROM. I'm not sure because the last time I did it was some years ago.
I have found another way, it's a bit hard, but safer
http://www.selftechgenius.com/how-t...nvalid-argument-in-all-samsung-galaxy-phones/
Click to expand...
Click to collapse
Gave it a read. Phones not entering recovery mode anymore so not sure I can proceed. Maybe try flashing stock ROM again.