Related
Please read the whole thread!
I know there have been some posts on this already, but I feel like there isn't a solution, and I just want a straight answer as to what I need to do, because I have no idea!
Hiya guys, sorry about this but I'm seriously new to xda and flashing roms etc.
Back a while ago I decided to root using superuser, I then tried to flash a cm7, and to this day I still don't know what is compatible with what..
Unfortunately for the next few days I don't have access to a pc cable, because one never came with my S5830.
Another quick question, what other recovery mods/roms can I get to use, because I have read some posts that say there are bugs with CWM, and haven't been able to find any others (because I just don't know what to search for apart from recovery roms, and that just gives me OS roms)
I then flashed CWM6.xxxxx to my phone and it seems to be working, I have 2 or 3 SD cards, and every one of them I put in it says:
"E:Can't mount /cache/recovery/ (Can't read, goes off screen)
"E:Can't mount /cache/recovery/ (Can't read, goes off screen)
"E:Can't open /cache/recovery/ (Can't read, goes off screen)
"E:Can't mount /cache/recovery/ (Can't read, goes off screen)
"E:Can't open /cache/recovery/ (Can't read, goes off screen)
When I go to "mounts and storage" on CWM v6, and try to mount any of the /cache,/data,/sdcard,/system,/sd-ext, they all give me the same thing:
"Error mounting /xxxxxx!"
Do I have corrupted SD cards?
I've tried flashing CM9, and it seemed to have worked, got caught in a bootloop, which I then redownloaded and reflashed, then it booted up but:
At startup, I was told the encryption was unsuccessful, and the "Reset Phone" button to fix this, doesn't work at all.
I keep think this is a problem with my SD cards.
I've tried partitioning my SD card to fix this problem, using FAT32 and Ext2 roughly half and half. (I don't know what either of these are but I just tried it anyways)
Do I have to have a specific version of CWM and CM in order to make my Ace work again?
I will be able to get a cable in the next few days, then I will use Odin to try and fix it, but here is the important part:
I don't actually remember what specific version of gingerbread my stock rom was, because I just jumped into flashing, didn't think about anything, yes I know. Stupid move.
I've tried flashing a few different CM version, all of them I wiped data/factory reset AND wiped cache partition AND wiped dalvik.
By the way, when I wipe the dalvik it literally just blips and does nothing, don't know whether that means something?
I have a 4GB SD card and a 2GB sd card, my 4GB is partitioned 3:1. They are both a standard version, I've looked around and have been told to get a "version 6" SD card. No idea why, probably something to do with transfer rate?
I have literally spent about 12 hours searching and flashing/reflashing/wiping, not finding anything really useful as to why this is happening..
I was thinking I need to flash to stock (whichever stock it is!!!:'(, and then start from square one). Another question is, does it matter which version of gingerbread I flash stock to? That's if it decides to actually work.
I really need help guys, could someone please tell me which version of CWM and CM to use, and how to flash through SD card for the moment, as I haven't got a cable yet.
I have looked at threads telling me I should wipe everything FIRST, and I have also seen ones that tell me to wipe AFTER I've installed the ROM. What's the difference?:/
All in all, I'm not very clued up when it comes to this, and I don't know whether this is soft bricked or hard bricked, but I can still access the recovery mode, ramdump mode (whatever that is) and download mode.
If anyone could help me it'd be a godsend.
LOLZ
What is that? 3th Bible's Testament?
...
DON'T USE CWM 6.xxx (it's NOT porn, joke )
You need to use CWM 5.0.2.6 FIXED!!! ROOT + CWM 5.0.2.6 FIXED
Here it is a really good thread to start in Galaxy Ace world, you'll find how to root, install CWM 5.0.2.6 FIXED, how to flash a STOCK OFFICIAL firmware using Odin, how to flash a custom rom....forum.xda-developers.com/showthread.php?t=2313363
Here you'll find Official firmwares
SAMMOBILE
...what else?
OMF! I've the 4th Bible's Testament!!!
---------- Post added at 01:07 AM ---------- Previous post was at 01:06 AM ----------
Correct steps:
1. Flash a fresh stock using Odin (AFTER ISNTALL YOU WILL GET BOOTLOOP >>>BOOT INTO STOCK RECOVERY AND DO DATA/FACTORY RESET AND WIPE CACHE PARTITION THEN REBOOT)
2. Root
3. INSTALL CWM 5.0.2.6. FIXED (then boot into recovery and do a backup, it's recommended )
4. Install a custom rom>>> FOLLOW DEV'S INSTRUCTIONS!!
5. Increasing internal memory>>>Use a custom rom/kernel with init.d support and follow the steps I posted here>>>INT2EXT SCRIPT
LOL my post is driving me round the bend! F*******!!
Viper The Ripper said:
LOLZ
What is that? 3th Bible's Testament?
...
DON'T USE CWM 6.xxx (it's NOT porn, joke )
You need to use CWM 5.0.2.6 FIXED!!! ROOT + CWM 5.0.2.6 FIXED
Here it is a really good thread to start in Galaxy Ace world, you'll find how to root, install CWM 5.0.2.6 FIXED, how to flash a STOCK OFFICIAL firmware using Odin, how to flash a custom rom....forum.xda-developers.com/showthread.php?t=2313363
Here you'll find Official firmwares
SAMMOBILE
...what else?
OMF! I've the 4th Bible's Testament!!!
---------- Post added at 01:07 AM ---------- Previous post was at 01:06 AM ----------
Correct steps:
1. Flash a fresh stock using Odin (AFTER ISNTALL YOU WILL GET BOOTLOOP >>>BOOT INTO STOCK RECOVERY AND DO DATA/FACTORY RESET AND WIPE CACHE PARTITION THEN REBOOT)
2. Root
3. INSTALL CWM 5.0.2.6. FIXED (then boot into recovery and do a backup, it's recommended )
4. Install a custom rom>>> FOLLOW DEV'S INSTRUCTIONS!!
5. Increasing internal memory>>>Use a custom rom/kernel with init.d support and follow the steps I posted here>>>INT2EXT SCRIPT
LOL my post is driving me round the bend! F*******!!
Click to expand...
Click to collapse
Nice post but u should send him the update of cwm this is quite old.
chyco94 said:
Nice post but u should send him the update of cwm this is quite old.
Click to expand...
Click to collapse
USE THIS CWM!!!... if you want to avoid troubles. I know it's quite old but it's fully stable for our device and it's the best!
---------- Post added at 03:45 PM ---------- Previous post was at 03:32 PM ----------
A great slogan could be: Easy, Stable and Safe!, especially for noob members
When he'll learn something more from Galaxy Ace and the Android world then he could do what he want, but for the novice is better to give clear and useful instructions, so I always provide the easiest way
Thanks for getting back to me!
Thank you so much! I'll give everything you said a try. It's actually quite sad how the Galaxy Ace has such pathetic RAM.
*Update*: Finally got a recovery flashed, using ROM Manager from inside a Rooted stock ROM (flashed via Heimdall). What a pain! But hopefully this will clear the way for me to install CM11.
Howdy, folks.
My boss bought an unlocked I8190 off Amazon, and I volunteered to throw CM11 on it. I'm having some odd problems that I can't find documented elsewhere.
I'm able to boot into both Recovery and Download mode with no problem. Stock recovery only, note.
In Download mode, I can flash to my heart's content- including recoveries, roms, you name it. I'm using Heimdall from Linux, rather than ODIN. I don't have access to a Windows system.
I can flash a CM11 rom, and it gets to the CM11 boot screen (i.e., Cid with the arrow spinning around him indefinitely).
What I can't do is seem to get into CWM or TWRP. No matter how many times I flash them to the device (as recovery.img, to Partition Identifier 19, apparently named Kernel2), it always goes back into stock recovery.
Any thoughts? I've tried:
Flashing PARAM_i8190 from http://forum.xda-developers.com/attachment.php?attachmentid=1597045&d=1356657742
Flashing "service rom" components from http://forum.xda-developers.com/showthread.php?t=2157105, i.e., i8190_buttonenable_cwm6.0.2.7.tar
Flashing a pre-rooted ROM (http://forum.xda-developers.com/showthread.php?t=2546043) flashing worked, but using goo.im app to flash recovery still didn't
Various types of wiping (flashing "wipe" images, wiping through stock recovery)
Flashing back to a stock ROM (which I can boot successfully)
Rebooting directly into recovery after flashing (i.e., heimdall --no-reboot, followed by pulling the battery and holding down VolUp+Power+Home, which boots into Stock recovery.)
I'd like to get this fixed in the next couple hours before my boss leaves for the middle east (the purpose for the phone). If not, I should be able to take another crack at it after Christmas, once he's back.
I have exactly similar issues. If anybody found any solution to this please help us out.
Thanks in advance.
did you try this
New release (20131218) of CM11.0 thats the odin version with team win recovery project include
Install guide
GAPPS
did u wait atleast 15 min after flashing cm11
eswarvf said:
did u wait atleast 15 min after flashing cm11
Click to expand...
Click to collapse
Yes, I did. This wouldn't have any impact on being unable to flash a new recovery, however.
pdbogen said:
Yes, I did. This wouldn't have any impact on being unable to flash a new recovery, however.
Click to expand...
Click to collapse
Leave it
U did install from maclaws recovery right and did u wipe/ factory reset
daywalk3r666 said:
did you try this
New release (20131218) of CM11.0 thats the odin version with team win recovery project include
Install guide
GAPPS
Click to expand...
Click to collapse
That's brand new; I haven't tried it yet. I did try the older version of Maclaw's CM11 ODIN w/ TWRP. There's already an even newer one out, as well. I don't know if I'll get a chance to try these before my boss leaves, but if so, I'll give it a shot. If not, I'll likely resume my attempts after the holidays.
eswarvf said:
Leave it
U did install from maclaws recovery right and did u wipe/ factory reset
Click to expand...
Click to collapse
I did not install from Maclaw's recovery, because I am unable to flash a custom recovery to the phone. I did *attempt* to install Maclaw's recovery (as well as the first-party TWRP recovery, as well as CWM Touch). Any attempt to flash any recovery is apparently "ignored" by the device, which reboots into the stock recovery no matter what. This happens even when rebooting to recovery (i.e., 3-button) directly from download mode (i.e., no auto-reboot).
I wiped/factory reset several times, through several different mechanisms, including:
Via stock recovery
Via stock ROM's "factory reset" option
Via flashing "wipe" files using Heimdall
I say Odin (all father) is our best friend stick to it
Meanwhile I will ask developers about this its like very unusual
Post a video so we can know
---------- Post added at 12:41 AM ---------- Previous post was at 12:39 AM ----------
And hell what's ur device info as it sounded unlocked version its like i8190x right
---------- Post added at 12:47 AM ---------- Previous post was at 12:41 AM ----------
First of all use wine ( Linux app for exe) and open Odin from it .
eswarvf said:
I say Odin (all father) is our best friend stick to it
Meanwhile I will ask developers about this its like very unusual
Post a video so we can know
---------- Post added at 12:41 AM ---------- Previous post was at 12:39 AM ----------
And hell what's ur device info as it sounded unlocked version its like i8190x right
---------- Post added at 12:47 AM ---------- Previous post was at 12:41 AM ----------
First of all use wine ( Linux app for exe) and open Odin from it .
Click to expand...
Click to collapse
I confirmed that I'll have some time to hack on the device tomorrow, so I'll make videos of the problem and post them. Do you have a specific test case you'd like to see?
Everything I can find on the phone seems to indicate it's just an i8190; nothing on the phone itself says i8190X, but I dunno. The branding on the box is mostly French and English. The CSC on the phone seems to indicate it's Romanian, so idk on that. If you have a more concrete method of determining this, let me know.
I'll try Odin via Wine. Is this generally known to work? I have a feeling it'll be hard to get it to talk to the phone via USB. I'll bring a Windows laptop from home tomorrow to try native Odin, too. (I only have OS X and Linux at work.)
pdbogen said:
I confirmed that I'll have some time to hack on the device tomorrow, so I'll make videos of the problem and post them. Do you have a specific test case you'd like to see?
Everything I can find on the phone seems to indicate it's just an i8190; nothing on the phone itself says i8190X, but I dunno. The branding on the box is mostly French and English. The CSC on the phone seems to indicate it's Romanian, so idk on that. If you have a more concrete method of determining this, let me know.
I'll try Odin via Wine. Is this generally known to work? I have a feeling it'll be hard to get it to talk to the phone via USB. I'll bring a Windows laptop from home tomorrow to try native Odin, too. (I only have OS X and Linux at work.)
Click to expand...
Click to collapse
OK I8190x is series ( I8190,I8190N,I8190L) like that and nah not a test case I want to see using stock recovery is not recommended on our phone and I didn't had a stock recovery at all so first I just rooted my phone and installed cwm everything just fine coming to your phone installing maclaw cm11 by odin is bad process even though i t comes with prerooted firmware but u have to factory reset before and after I think u skipped one of them flashing cm11 with recovery is good process and it rejects everything because we don't because no one here tried maclaw on a fresh piece
i'm having the same problem as you with my 2nd I8190...
however, i am running win7 and even though ODIN tells me everything is PASS, nothing is booting up. I can't get any recovery/rom to boot up
now i'm just stuck in this endless bootloop, no matter what I flash with ODIN
pdbogen said:
*Update*: Finally got a recovery flashed, using ROM Manager from inside a Rooted stock ROM (flashed via Heimdall). What a pain! But hopefully this will clear the way for me to install CM11.
Howdy, folks.
My boss bought an unlocked I8190 off Amazon, and I volunteered to throw CM11 on it. I'm having some odd problems that I can't find documented elsewhere.
I'm able to boot into both Recovery and Download mode with no problem. Stock recovery only, note.
In Download mode, I can flash to my heart's content- including recoveries, roms, you name it. I'm using Heimdall from Linux, rather than ODIN. I don't have access to a Windows system.
I can flash a CM11 rom, and it gets to the CM11 boot screen (i.e., Cid with the arrow spinning around him indefinitely).
What I can't do is seem to get into CWM or TWRP. No matter how many times I flash them to the device (as recovery.img, to Partition Identifier 19, apparently named Kernel2), it always goes back into stock recovery.
Any thoughts? I've tried:
Flashing PARAM_i8190 from http://forum.xda-developers.com/attachment.php?attachmentid=1597045&d=1356657742
Flashing "service rom" components from http://forum.xda-developers.com/showthread.php?t=2157105, i.e., i8190_buttonenable_cwm6.0.2.7.tar
Flashing a pre-rooted ROM (http://forum.xda-developers.com/showthread.php?t=2546043) flashing worked, but using goo.im app to flash recovery still didn't
Various types of wiping (flashing "wipe" images, wiping through stock recovery)
Flashing back to a stock ROM (which I can boot successfully)
Rebooting directly into recovery after flashing (i.e., heimdall --no-reboot, followed by pulling the battery and holding down VolUp+Power+Home, which boots into Stock recovery.)
I'd like to get this fixed in the next couple hours before my boss leaves for the middle east (the purpose for the phone). If not, I should be able to take another crack at it after Christmas, once he's back.
Click to expand...
Click to collapse
Edit: My problem has been solved, I tried to flash recovery again through odin but still issue was there.. then I download stock firmware from sammobile and then flashed the same through odin... and wolaaa... phone rebooted and issue is fixed now.. thanks @Pheoxy for your guidence...
Hi All,
I am having serious problem with my S3 i9305. I was using Amcha ROM version 2.20 yesterday my battery was dead and phone went powered off while I was sleeping, when I woke up I tried charging it but it turns on and stucked on bool logo I accessed recovery mode and tried to wipe cache and dalvik cache, but the issue is when I select wipe dalvik cache and then phone restarted it self and than stuck again on bootloop.. further when I tried to do factory reset through recovery than phone again restarted and then stuck again on boot logo..
I also tried flashing Amcha 3.0 version by putting it on external SD card and through recovery when I selected flash zip than AROMA started and then suddenly while installing ROM phone again restarted and then as usual stucked on bootloop.
please suggest me the way forward, phone is just working fine.. and then......this issue.. Please help as I am in serious issue...
Partitions might be buggered some how. Use Odin to flash recovery again to make sure and then flash stock ROM before android 4.3.
Do a wipe like you would switching Roms and restore backup if you can or flash whatever.
Pheoxy said:
Partitions might be buggered some how. Use Odin to flash recovery again to make sure and then flash stock ROM before android 4.3.
Do a wipe like you would switching Roms and restore backup if you can or flash whatever.
Click to expand...
Click to collapse
Sir, Thanks for your response!
Right now I am downloading a stock kitkat firmware from this link http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
can I install it through odin, or I 1st try to install recovery only..
Mate install before 4.3 if you don't want annoying Knox boot loader.
---------- Post added at 02:03 AM ---------- Previous post was at 02:02 AM ----------
Yeah do recovery first
Pheoxy said:
Mate install before 4.3 if you don't want annoying Knox boot loader.
---------- Post added at 02:03 AM ---------- Previous post was at 02:02 AM ----------
Yeah do recovery first
Click to expand...
Click to collapse
Thanks sooo much for your reply, recovery flashing didn't worked.. however I just flashed stock firmware from odin and now everything is perfect..
No problem. [emoji1]
Hello,
So my Galaxy S6 is stuck in a boot loop and i've literally tried EVERYTHING already and nothing will solve the problem. Safe mode won't work, clearing the cache partition won't work and USB Debugging was turned off so adb wasn't seeing my device either. I also tried Kies and Smart Switch. I am convinced my phone is soft bricked and I need to recover some very important pictures and files from it. At this point my last hope is to flash the stock ROM via Odin and I saw that some people said that they have successfully done this without losing any of their data. Is this possible? If so how do I go about doing it properly?
Thanks for any help!
Phone is not rooted and 100% stock.
Recovery and Download screens are working.
How did Kies not work for you? I used it about 4 times to restore to like new.
cwhiatt said:
How did Kies not work for you? I used it about 4 times to restore to like new.
Click to expand...
Click to collapse
Because the phone is stuck in a boot loop. Kies won't detect my phone because it never fully boots.
Weird. I completely removed the system on one before reinstalling the system via Kies before sending it back via warranty exchange. I'd suggest trying again. Obviously you will need model and serial #.
cwhiatt said:
Weird. I completely removed the system on one before reinstalling the system via Kies before sending it back via warranty exchange. I'd suggest trying again. Obviously you will need model and serial #.
Click to expand...
Click to collapse
Tried Kies multiple times but it just won't work. Uninstalled and reinstalled drivers, disconnected and reconnected the phone, nothing works. That's why I turned to Odin.
1337Dev said:
Tried Kies multiple times but it just won't work. Uninstalled and reinstalled drivers, disconnected and reconnected the phone, nothing works. That's why I turned to Odin.
Click to expand...
Click to collapse
Since you can get into recovery, if I were you I'd flash Unikernel (latest version is 9.1 I believe) and then flash a custom rom. If you can get it to boot you shouldn't lose data in the sdcard/download.
---------- Post added at 09:48 PM ---------- Previous post was at 09:46 PM ----------
I am running Sick as Hell version X rom and loving it.
cwhiatt said:
Since you can get into recovery, if I were you I'd flash Unikernel (latest version is 9.1 I believe) and then flash a custom rom. If you can get it to boot you shouldn't lose data in the sdcard/download.
---------- Post added at 09:48 PM ---------- Previous post was at 09:46 PM ----------
I am running Sick as Hell version X rom and loving it.
Click to expand...
Click to collapse
Forgot to mention but I am going to have to return this phone to T-mobile for a warranty exchange, that's why I was trying to avoid custom rom's thinking it might become ineligible. Want to be able to recover data and then reset the phone for return
The phone i wiped the system on was returned via warranty with Tmobile (of course I later reinstalled it via Kies). I would install a custom rom to attempt to get the thing up and running. Once you do that then go from there (back to Kies or factory reset...)
cwhiatt said:
The phone i wiped the system on was returned via warranty with Tmobile (of course I later reinstalled it via Kies). I would install a custom rom to attempt to get the thing up and running. Once you do that then go from there (back to Kies or factory reset...)
Click to expand...
Click to collapse
Ok, Thank you! I was worried about the warranty exchange. I will attempt to install a custom rom let's see how it goes.
The purpose of installing the custom rom is to attempt to retrieve your data. If you can boot and then successfully get your data, it would be advisable to remove the custom rom and restore it to factory. Let me know how it goes...
cwhiatt said:
The purpose of installing the custom rom is to attempt to retrieve your data. If you can boot and then successfully get your data, it would be advisable to remove the custom rom and restore it to factory. Let me know how it goes...
Click to expand...
Click to collapse
Hello another User here , I am in a similar situation . I installed some theme [live] from theme store , then it started acting wierdly. Finally a bad combination of Good Lock , System UI and Safe Mode my phone is in a bootloop.
I want to recover my data mostly videos and pictures. What shall I do. I am unrooted , I can access recovery , adb sideload from recovery , I can get into download mode. Will wipe data option save my Pictures?
y2k2r2d2 said:
Hello another User here , I am in a similar situation . I installed some theme [live] from theme store , then it started acting wierdly. Finally a bad combination of Good Lock , System UI and Safe Mode my phone is in a bootloop.
I want to recover my data mostly videos and pictures. What shall I do. I am unrooted , I can access recovery , adb sideload from recovery , I can get into download mode. Will wipe data option save my Pictures?
Click to expand...
Click to collapse
If you've got recovery installed it would be just for that purpose. Restoring your backup (i.e., recovery). I gather you don't have a backup?
What device do you have?
G920F International. The Recovery is not a custom one . It is the default recovery that doesn't have backup mode.
y2k2r2d2 said:
G920F International. The Recovery is not a custom one . It is the default recovery that doesn't have backup mode.
Click to expand...
Click to collapse
Ahh gotcha. Well...if it were me what I'd do is to boot to download mode and flash TWRP custom recovery file using Odin. Once that passes I'd boot into TWRP and do a backup.
You can then reboot into TWRP and try to restore your backup but you'll likely end up in a bootloop again. If that happens...
Then, I'd download a stock recovery (looks like they have your variant here.
I'd then flash the stock recovery using TWRP and then reboot.
If you get stuck in a bootloop again then I would do a factory reset (which doesn't wipe storage which is where your photos etc. are) and then reflash the stock recovery zip file.
I can't say for certain if that'll wipe your photos, etc. or not but I'm not inclined to think it would.
cwhiatt said:
Ahh gotcha. Well...if it were me what I'd do is to boot to download mode and flash TWRP custom recovery file using Odin. Once that passes I'd boot into TWRP and do a backup.
You can then reboot into TWRP and try to restore your backup but you'll likely end up in a bootloop again. If that happens...
Then, I'd download a stock recovery (looks like they have your variant here.
I'd then flash the stock recovery using TWRP and then reboot.
If you get stuck in a bootloop again then I would do a factory reset (which doesn't wipe storage which is where your photos etc. are) and then reflash the stock recovery zip file.
I can't say for certain if that'll wipe your photos, etc. or not but I'm not inclined to think it would.
Click to expand...
Click to collapse
Thanks. It will help in the backup.
Will factory reset/wipedata from stock recovery remove the pictures ?
Can you backup data using OTG/pendrive from TWRP recovery?
y2k2r2d2 said:
Thanks. It will help in the backup.
Will factory reset/wipedata from stock recovery remove the pictures ?
Can you backup data using OTG/pendrive from TWRP recovery?
Click to expand...
Click to collapse
factory reset doesn't erase storage data.
Not sure about otg/pendrive
Sent from my SM-G920T using XDA-Developers mobile app
I didn't flash TWRP as I learned that Samsung Pay will never work not even Stock ROM flash. I instead pulled some vital data files from adb pull on 'the window of around 1 minute' each time it was active during safe mode rebooting and thankfully Google Photos had a backup of my Photos and videos.
I used the wipe data option on stock recovery that wiped everything. The device is like new.
My Note 4 has a weird behavior.
When I flash stock firmware, my Note begins to behave really bad:
1. Constant crashes, any app can crash the OS.
2. Get's stuck in the bootloop
3. Every other time I get a boot error: cannot read emmc.
But when I flash non-stock firmware - Dirty Unicorns, everything is FINE!
I'm on EPJ2 bootloader.
This began a few months ago. I rooted my Note for the first time and used WiFi Hotspot app. Then I unrooted and recieved an OTA update. Everything was OK at first, but then this behavior developed.
I googled for a solution and flashed clean firmware maybe 5 times now, but this behavior persists!
Any help would be greatly appreciated!
AntonJart said:
My Note 4 has a weird behavior.
When I flash stock firmware, my Note begins to behave really bad:
1. Constant crashes, any app can crash the OS.
2. Get's stuck in the bootloop
3. Every other time I get a boot error: cannot read emmc.
But when I flash non-stock firmware - Dirty Unicorns, everything is FINE!
I'm on EPJ2 bootloader.
This began a few months ago. I rooted my Note for the first time and used WiFi Hotspot app. Then I unrooted and recieved an OTA update. Everything was OK at first, but then this behavior developed.
I googled for a solution and flashed clean firmware maybe 5 times now, but this behavior persists!
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Did you wipe/format the internal drive?
sloanster said:
Did you wipe/format the internal drive?
Click to expand...
Click to collapse
Thank you for your reply. Yes, each time I did Factory reset/advanced wipe of date, caches, and system
AntonJart said:
Thank you for your reply. Yes, each time I did Factory reset/advanced wipe of date, caches, and system
Click to expand...
Click to collapse
Yeah, but did you check internal?
According to your reply you did not.
Your internal may have residual conflicting files/info on it.
And don't use backup data, garbage in garbage out...
Build your new rom from scratch.
---------- Post added at 05:38 PM ---------- Previous post was at 05:31 PM ----------
Pease review:
http://forum.xda-developers.com/note-4-tmobile/help/note-4-issues-post-11-06-2016-t3495012
Wipe data within twrp where you have to type yes to erase and make sure it's the right firmware. After you flash pull the battery ( uncheck reboot after flash in Odin) 30sec put the battery back in and reboot to recovery, it should be stock, and factory reset, then reboot back to download mode and flash once more, and you should be good to go. If that doesn't work flash one firmware behind your current one.
AntonJart said:
My Note 4 has a weird behavior.
When I flash stock firmware, my Note begins to behave really bad:
1. Constant crashes, any app can crash the OS.
2. Get's stuck in the bootloop
3. Every other time I get a boot error: cannot read emmc.
But when I flash non-stock firmware - Dirty Unicorns, everything is FINE!
I'm on EPJ2 bootloader.
This began a few months ago. I rooted my Note for the first time and used WiFi Hotspot app. Then I unrooted and recieved an OTA update. Everything was OK at first, but then this behavior developed.
I googled for a solution and flashed clean firmware maybe 5 times now, but this behavior persists!
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Thank you gentlemen! Tried some of these, no luck. I'll read and try more in the morning. As for now, it seems that other folks with EPJ2 are having identical issues, including emmc failures.
sloanster said:
Yeah, but did you check internal?
According to your reply you did not.
Your internal may have residual conflicting files/info on it.
And don't use backup data, garbage in garbage out...
Build your new rom from scratch.
---------- Post added at 05:38 PM ---------- Previous post was at 05:31 PM ----------
Pease review:
http://forum.xda-developers.com/note-4-tmobile/help/note-4-issues-post-11-06-2016-t3495012
Click to expand...
Click to collapse
g1-and-only said:
Wipe data within twrp where you have to type yes to erase and make sure it's the right firmware. After you flash pull the battery ( uncheck reboot after flash in Odin) 30sec put the battery back in and reboot to recovery, it should be stock, and factory reset, then reboot back to download mode and flash once more, and you should be good to go. If that doesn't work flash one firmware behind your current one.
Click to expand...
Click to collapse