I've been trying to install different roms, once I start the process after wiping and everything I get status 7 errors stating this is for trltetmo, this device is trlte. My device ID is N910T. I bought this at a tmobile store, currently on Dynamic Kat. So what can I do to fix this because I don't like DK (battery)?
Odin back to stock.
Then factory reset.
Then reroot using the instructions in the sticky.
Then flash away.
Is there a way to Mobile Odin? I don't have access to a computer within the next month or so
Can it be a partial odin, or does it have to be full odin
Has to be full odin or try downloading on WiFi and different browser and let the phone be till download is done.. Then try.. Once you have issues like that it be at to odin
BAD ASS NOTE 4
It seems its just 5.0+ roms (beanstalk, xenon, cmremix) giving me status error, how do I fix that? I just installed hyper drive from Dynamic Kat.
You need to do a full wipe from the team win recovery.
Related
So I updated the MIUI on my Cappy from whatever I had before to 2.3.30 that is GB 2.3.7 from this location:
http://miuiandroid.com/community/threads/archived-miui-versions-captivate-gb.16558/
I didnt care for it so I downloaded SlimICS. I downloaded the base and the cappy essentials. Put them both on my internal sd. I factory reset, wiped data, cache and system and dalvic, just as i do for every phone i work on. I ran the SlimICS base and now it keeps rebooting and going back into recovery and doing this:
Finding update package...
Opening update package...
Installing update...
Slim ICS
Once Slim ICS pops up, it reboots and does it all over. I can yank the battery and manually go into recovery, but if i try to boot it up normal, it goes back into the loop. I am on CWM 5.0.2.7 also.
So what did i miss?
GB bootloaders most likely missing - flash 'em using Heimdall. And SlimICS doesn't have modem. So. Flash my ROM for a change may be.
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
And you flashed the base and the cappy essentials right? Not just the base
Sent from my SGH-I897 using xda premium
korockinout13 said:
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
Click to expand...
Click to collapse
trying to flash again just put it back in the loop. And I read that that does happen alot going from GB to ICS on the Cappy. But for Slim it didnt work.
Wdustin1 said:
And you flashed the base and the cappy essentials right? Not just the base
Click to expand...
Click to collapse
I never could get that far because it was the base that I started to install and it got bootlooped on, everytime it restarted, it went back into recovery and started to run the base again, and repeated boot loop. I read somewhere that teamhacksung's rom would get me over the GB to ICS bridge. This one here:
http://forum.xda-developers.com/showthread.php?t=1363760
It did the bootloop to, but when i yanked the battery and went back in and installed it a 2nd time, it didnt restart and installed correctly. After that I installed SlimICS. But I dont like it as much as i thought i would and now when i try to reinstall teamhacksung ROM, it errors out during the beggining of the installation. The MD5 is still fine. I dont think it likes the version of CWM recovery that SlimICS installed. I know CWMR went to an older version when i went from teamhacksung to SlimICS.
Flash glitch kernel first. Also, don't use the builds from that thread, it is old. Just flash the latest CM9 nightly
Swyped from my ICS Samsung Captivate
Stuck in A boot loop after flashing paranoid rom to cappy i897
I downloaded all needed files to internal SD just as the (how to upgrade the captivate i897 to Paranoid ROM said to do )
wipe data factory reset,wipe cache,selected install zip zip>package (pa_captivatemtd-1.99-13AUGUST2012.zip, md5sum: cc03bacf0f07a94bf25b482d64b94e63) then it started boot looping / att screen twice then android guy ,, then falling over with exclamation point in the middle of him , let it go considering options of 3 button combo weren't working ,, beside guide said 5-10 min to install then it made it to devil kernel installed gapps >> (gapps-jb-20120726-signed.zip, md5sum: f62cfe4a827202899919fd932d5246d7) now back in the boot loop again>>
i did make a nandroid backup but cant seem to get into cwm recovery or download mode . I did follow that guide to a tee.
any help or suggestions on this i would greatly appreciated if this post in wrong spot sry im new.
Also stuck in bootloop reverting to Gingerbread
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Reply Back.
HG_User said:
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Click to expand...
Click to collapse
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out. ??
---------- Post added at 06:38 PM ---------- Previous post was at 06:27 PM ----------
321321wrick said:
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out.
There also Ginger Bread Boot loaders Needed for it to start up Correctly - i personally don't know that much bout gingerbread rom i didn't like it as much as froyo WiFi issues'' the the stock odin should erase all info on your part thou 'e use Is OCD 1 i897UCJF6>lowercase work every time for me.
cept now because my usb is not able to charge phone or enter download mode or recovery which leaves jig option .
Click to expand...
Click to collapse
HG_User,
U can't go back to GB (or froyo/eclair) from CM, MIUI, ICS, JB, AOSP etc., etc. without using Odin or Heimdall---because of the different partitions used---Stock firmware is bml/rfs and all the AOSP etc etc are mtd/yaffs(2).
And u can only restore a backup when u r back running the base rom where u made the back up.
Use this...Stock i897ucKK4 GB 2.3.5 with or without bootloaders... http://forum.xda-developers.com/showthread.php?p=18370912
This kk4 should get u going. Then u can use Odin to flash Corn Kernel to get a cwm back...:thumbup:
Sent from my SGH-I897 using xda premium
... one step on the way: Back to Eclair
thanks for the advice. Ultimately, I decided I should use Odin 3 1-click to revert back to original (2.1 Eclair) firmware that I found on the first post of thread titled
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
This is a huge step forward because it makes my phone work, but it's also a step back in time to the early Eclair days.
Now my next step is to upgrade back to Gingerbread...
Edit: Thanks to all who pointed me in the right direction. I took the phone back to Eclair then used Samsung KiesMini (twice) to get it back to Gingerbread. After re-rooting and removing the AT&T Bloatware, it works fine again. I might try upgrading again to ICS or JB, but I didn't like Cyanogen 9 at all. Maybe I'm just used to the way AT&T polishes the UI, but Cyanogen didn't appeal at all. Now looking for a relatively polished but lightweight ICS or JB version... Also, it would be nice if when I upgrade it preserves the installed apps and what's on my home screens, but that seems unlikely going from AT&T-branded Gingerbread to an independent ICS or JB.
Hi all, I could really really use some help.
Today I decided to try and flash CM9 RC2 and I seem to have messed up big time.
I startred by rooting, using Dr Ketan's guide. That all went smoothly, and root was working.
I put the CM9 zip file on the SD card, turned off my phone, got back into CWM recovery, and most tutorials recommended, selected full data wipe... this is where something seemed to go wrong. While perfoming the data wipe, it seemed to freeze. I let it sit for a while, hoping it would sort itself out, but it didn't, and then it rebooted itself and went into a boot loop.
I can't get back into recovery mode, but I can get into download mode. So I thought the best thing to do would be to flash a stock firmware using odin.
I downloaded the latest german LRG firmware (which I was on before I started) from Sammobile, connected my phone to odin, selected the MD5 file, and pushed start. Again, this is where I got stuck. It just hangs on Nand write start. I've tried this twice now, and it gets stuck at the same stage (about 90% finished)
I have no idea what to do now and really need help. I'm not a total n00b, or at least I thought I wasn't, but I seem to have gotten in way over my head. What should I do?
Edit: see you tried already...
Sent from my GT-N7000 using xda app-developers app
This is classical case of super brick.
You should not hav to wipe on ics. I think u must be on stock kernel. Every corner you may see warning, wiping and reset on ics can brick device, but its unfortunate you didn't notice it.
Anyway check your flash counter is zero and send it to service.centre to claim ur warranty.
If u running out of warranty, fing.a link for 'how to revice bricked note from my signature. And try it.
Edit : i wud like to know, as you said u went to cwm recovery, so at the time of wiping you wr on which kernel?
Sent from my GT-N7000 using xda premium
purple zebra said:
Hi all, I could really really use some help.
Today I decided to try and flash CM9 RC2 and I seem to have messed up big time.
I startred by rooting, using Dr Ketan's guide. That all went smoothly, and root was working.
I put the CM9 zip file on the SD card, turned off my phone, got back into CWM recovery, and most tutorials recommended, selected full data wipe... this is where something seemed to go wrong. While perfoming the data wipe, it seemed to freeze. I let it sit for a while, hoping it would sort itself out, but it didn't, and then it rebooted itself and went into a boot loop.
I can't get back into recovery mode, but I can get into download mode. So I thought the best thing to do would be to flash a stock firmware using odin.
I downloaded the latest german LRG firmware (which I was on before I started) from Sammobile, connected my phone to odin, selected the MD5 file, and pushed start. Again, this is where I got stuck. It just hangs on Nand write start. I've tried this twice now, and it gets stuck at the same stage (about 90% finished)
I have no idea what to do now and really need help. I'm not a total n00b, or at least I thought I wasn't, but I seem to have gotten in way over my head. What should I do?
Click to expand...
Click to collapse
Hi Bud,
From your predicament, first let me tell you what you have done wrong.... You mentioned you're in LRG Rom already and you wanted to flash CM9 after that.... right?
Well, I guess the process you did was totally wrong. You have to download stock GB N7000(from Dr. Ketan's thread) and using that stock GB Rom, that is the time you can install AbysNote kernel to root and install CWM on your phone. Now after that, download mobile ODIN (from google playstore) and flash the CM9 from there.
THAT's the one you should have done before. Remember, there are no easy way of jumping ROMS especially if your already in ICS... IF YOU WANT TO FLASH TO ANOTHER ICS ROM.
My rule of law would be to downgrade first to STOCK GB and from there, ROOT, install CWM and mobile ODIN and that'll be the time you can flash already to the new ICS ROM of your choice.
So here's what your going to do. Since your still able to boot in download mode, Download any stock GB ROM and flash it using PC ODIN. After that, seee if you can bootup your Note already to STOCK GB ROM. If and If you are able to already, then download a clean kernel preferably Abyss Kernel and flash it with your STOCK GB so that you can gain root and have CWM installed. From there, download Mobile Odin pro and flash the CM9 (that you ultimately want to be installed on your Note)
Hope everything's going to be fine and Good luck bud! :fingers-crossed:
Cheers!
Hello, I know its been several days, but I just wanted to update on the situation.
Thank you SO much to Dr.Ketan for pointing me in the right direction. A combination of these 2 guides (http://forum.xda-developers.com/showthread.php?t=1661590&page=2 http://forum.xda-developers.com/showthread.php?t=1667886) has managed to help me repartition my internal memory and get up and running again. I've got a stock gingerbread rom running, and all seems to be well.
I realise I was very stupid to do a wipe on an ICS kernal. I read about the problem for 1 particular Kernal back in may, and hadn't read the updates since, and so didn't realise it effected EVERY ICS kernal since then. It's my own stupid fault for not re-reading the warnings. Let this be a lesson kiddies, a little bit of knowledge is a dangerous thing.
Again, thank you so much for the help, to all involved, you are an asset to the community!
Hi. I'm new to the forum but not new to android and samsung. I got greedy and impatient and wanted to load the lollipop G900T update on my G900A. I got root with the OA1 update, installed busybox, installed safestrap. Tried to install G900T update, but the phone rejected it. Thought I could be even more adventurous and install cyanogenmod so I went into safestrap and did a system wipe, which is where my problems began.
Here's what I can do:
-go into recovery
-go into download mode
-install files from odin
-see the battery charge animation when the phone is off
Here's what my problem is:
as soon as i start the phone, i get the galaxy s5 logo powered by android along with the giant unlocked lock that says custom (busybox or safestrap i assume). then i see the samsung animation and then it freezes. then i get a black screen with the pulsating blue light at the top of the phone. my guess is that it was soft brick so i tried to find every guide on the internet to reset it and it still comes back to that unlocked lock and freezing animation. as probably few of you have experienced, i began to think the worst - should i sell it for parts? is there a religious ritual? what am i going to do?
Here's what i've tried:
-following these http://forum.xda-developers.com/showthread.php?t=2785363
-flashing stock from sammobile
-doing both along with a nand erase all function
-attempting to install the BL file from the first link (fail)
i know the g900a isn't particularly a developer-friendly device with the locked bootloader and att being att, but please tell me there's hope. i can supply any odin logs you want.
p.s. if it helps, i get the fused 2 binary 1 when i try to flash sammobile stock file. or the bootloader file from the first link.
U can try by starting here.
http://forum.xda-developers.com/showthread.php?p=58621872
The general section had quite few good threads on updating g900a.
ovodennis said:
Hi. I'm new to the forum but not new to android and samsung. I got greedy and impatient and wanted to load the lollipop G900T update on my G900A. I got root with the OA1 update, installed busybox, installed safestrap. Tried to install G900T update, but the phone rejected it. Thought I could be even more adventurous and install cyanogenmod so I went into safestrap and did a system wipe, which is where my problems began.
Here's what I can do:
-go into recovery
-go into download mode
-install files from odin
-see the battery charge animation when the phone is off
Here's what my problem is:
as soon as i start the phone, i get the galaxy s5 logo powered by android along with the giant unlocked lock that says custom (busybox or safestrap i assume). then i see the samsung animation and then it freezes. then i get a black screen with the pulsating blue light at the top of the phone. my guess is that it was soft brick so i tried to find every guide on the internet to reset it and it still comes back to that unlocked lock and freezing animation. as probably few of you have experienced, i began to think the worst - should i sell it for parts? is there a religious ritual? what am i going to do?
Here's what i've tried:
-following these http://forum.xda-developers.com/showthread.php?t=2785363
-flashing stock from sammobile
-doing both along with a nand erase all function
-attempting to install the BL file from the first link (fail)
i know the g900a isn't particularly a developer-friendly device with the locked bootloader and att being att, but please tell me there's hope. i can supply any odin logs you want.
p.s. if it helps, i get the fused 2 binary 1 when i try to flash sammobile stock file. or the bootloader file from the first link.
Click to expand...
Click to collapse
Head over to this link http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120 and download the G900A_Downgrade_to_NCE.tar and flash via odin. Take the 2 ota updates and your phone will be all fixed. THis will delete all of your data though.
Thanks! I posted a similar issue after I downgraded from OA1 to NCE using the stock NCE bundled with 4 files. It is important to use the downgrade, not the 4 file NCE stock.
ovodennis said:
Hi. I'm new to the forum but not new to android and samsung. I got greedy and impatient and wanted to load the lollipop G900T update on my G900A. I got root with the OA1 update, installed busybox, installed safestrap. Tried to install G900T update, but the phone rejected it. Thought I could be even more adventurous and install cyanogenmod so I went into safestrap and did a system wipe, which is where my problems began.
Here's what I can do:
-go into recovery
-go into download mode
-install files from odin
-see the battery charge animation when the phone is off
Here's what my problem is:
as soon as i start the phone, i get the galaxy s5 logo powered by android along with the giant unlocked lock that says custom (busybox or safestrap i assume). then i see the samsung animation and then it freezes. then i get a black screen with the pulsating blue light at the top of the phone. my guess is that it was soft brick so i tried to find every guide on the internet to reset it and it still comes back to that unlocked lock and freezing animation. as probably few of you have experienced, i began to think the worst - should i sell it for parts? is there a religious ritual? what am i going to do?
Here's what i've tried:
-following these http://forum.xda-developers.com/showthread.php?t=2785363
-flashing stock from sammobile
-doing both along with a nand erase all function
-attempting to install the BL file from the first link (fail)
i know the g900a isn't particularly a developer-friendly device with the locked bootloader and att being att, but please tell me there's hope. i can supply any odin logs you want.
p.s. if it helps, i get the fused 2 binary 1 when i try to flash sammobile stock file. or the bootloader file from the first link.
Click to expand...
Click to collapse
A couple more things because of the G900A locked down bootloader you won't be able to flash any Lollipop Roms until ATT drops official update.
You also CANNOT flash any ASOP Roms or custom kernels.
gentlemen!
i followed your advice and flashed the downgrade rar. sat in my chair with a frown as i waited for it to load until i heard the infamous at&t tone, the screen light up, and the 'connect to wifi' screen come up.
blessed! thank you! i promise to be patient and always be grateful to the xda community. many thanks again!
:good:
I was on EKXodus N4 5.1.1 URv5 N5R5 ROM, but then I decided to go back to stock because I experience heavy lag in that ROM.
I had COG2 on my computer, so I booted my phone into download mode, opened Odin, and flashed COG2.
When I tried to turn it on, it was stuck on the T-Mobile logo when I boot on.
At that point, I flashed CF Auto Root and TWRP, and tried to restore my phone(I made a backup)
But something went wrong, it showed it couldn't normal boot, either that, or it's stuck in recovery mode when booting on.
So basically I went back and forth between stock and custom, and constant flashing of root and TWRP.
Now, I finally get it to turn on, but it's on EKXodus N4 5.1.1 URv5 N5R5.
TLTR: My IMEI is unknown, and I couldn't get signal on my phone.
Plz help me T.T
As I understand that version of the rom might have been built with the new baseband (DOK2) so when you tried to install the one you had previously (COG2) it failed, my advice would be to try flashing the new version (N910TUVU2DOK2) and see if it fixes your IMEI issues. Before doing all of this verify the version you need (N910T or N910T3) to prevent any issues.
try with kies 3
Try to use emergency firmware recovery option from kies3
but first make a full wipe on twrp data,cache,dalvik, system and internal storage x3 times, reboot on download mode and then use kies to restore your note, if you was on cog2 restore it, or if you was in dok2 restore dok2.
Pd: sorry for my english
Before MM I was already having issues with my LP install. Lockups, crashes, etc.. I had planned on performing a fresh install of my LP ROM yesterday but was excited to see that MM was released. I was hoping that installing MM over LP would fix the issue that I was experiencing. No dice.
So, is it possible to go into TWRP, perform a factory reset (including erasing Internal Storage) and then booting into Download Mode so I can install MM fresh using Odin? Is there anything that I need to know of or missing before performing this procedure? I can then reinstall TWRP and root afterwards. I just want a fresh install and can't wait two or three days for a Flashable Zip. My system is just too unstable in its current form.
Thanks.
JC
For The Record
This is exactly what I just did. It works perfectly and now my phone is back to operating normally. And with a clean install of 6.0.1 to boot!
Now....time for TWRP and Root........
What is safe to wipe in TWRP? I did an install of MM for the 910T stock rom and unfortunately tried the encryption. I thought it would give me the option to decrypt, but that is not the case.
Wipe
Mister_E105 said:
What is safe to wipe in TWRP? I did an install of MM for the 910T stock rom and unfortunately tried the encryption. I thought it would give me the option to decrypt, but that is not the case.
Click to expand...
Click to collapse
I wiped EVERYTHING in TWRP. Powered off the phone and then booted to Download Mode. From there I pushed out a fresh copy of MM using Odin. It flashes a new stock recovery. After the phone boots up go back into Download Mode and flash TWRP using Odin. Then you can flash Beta SuperSU in TWRP for root.
But.....I wanted to follow up on this post. My Note 4 started experiencing issues last week. I was hoping a fresh OS install would fix things. Unfortunately for me during a power off to go into recovery to flash SuperSU I received the dreaded mmc_read failed error. The phone is nearly two years old and I have never seen the bug on my device. I had thought that I was one of the lucky early purchasers. I was wrong.
The device got worse and worse. To the point that now it rarely boots at all. It just sits at the "Samsung Note 4" screen. I can't even get into TWRP reliably. And the mmc screen is popping up more frequently now as well.
I had no choice but to stop by T-Mobile yesterday and (reluctantly) buy a S7 Edge. I say reluctantly for two reasons. 1. The Note 7 comes out in barely over a month 2. There is no known root for S7 (and Note 7 will probably be the same)
I have 30 days to decide if this phone is for me or not. Not having root is something that I never thought I'd have to live with. Barring some unforeseen circumstance I thought I'd have the Note 4 for a couple more years. And I didn't have the time to look for a used one as I needed a phone immediately.
Fingers crossed they get this thing roooted because it really is a pretty sexy device!
I found that the only way to clear the encryption was to load the stock recovery, it had the power to wipe the partitions and allow a clean install.