Hi everyone!
A friend of mine tried to flash/destroy his n7100 (i don't know why!) so He gave it to me to "play" and try to recover it.
I think that He tried to flash a 4.4.2 stock rom taken somewhere, so I have the lastest bootloader
I recovered it with KIES (that installed android 4.3) and the phone (now) boot completely and works at 100%!
BUT
sometimes when I detach it from power cord it immediatelly reboot and remain stuck at the "samsung galaxy note n7100" screen and bootloops.
If I reattach the power cord at the next poweroff/poweron cycle the phone start correctly and works 100%!!
Actually I'm on a full stock with root and TWRP installed, but this reboots happens also on full stock
It's really strange and I don't know how to get rid of this!
Actually the custom flash counter report 9 and the knox warranty void is at 1.
Someone has any idea of to get rid of theese strange reboots?
aleritty said:
Hi everyone!
A friend of mine tried to flash/destroy his n7100 (i don't know why!) so He gave it to me to "play" and try to recover it.
I think that He tried to flash a 4.4.2 stock rom taken somewhere, so I have the lastest bootloader
I recovered it with KIES (that installed android 4.3) and the phone (now) boot completely and works at 100%!
BUT
sometimes when I detach it from power cord it immediatelly reboot and remain stuck at the "samsung galaxy note n7100" screen and bootloops.
If I reattach the power cord at the next poweroff/poweron cycle the phone start correctly and works 100%!!
Actually I'm on a full stock with root and TWRP installed, but this reboots happens also on full stock
It's really strange and I don't know how to get rid of this!
Actually the custom flash counter report 9 and the knox warranty void is at 1.
Someone has any idea of to get rid of theese strange reboots?
Click to expand...
Click to collapse
Reinstall correct bootloader for rrom using Odin.
Mufrad said:
Reinstall correct bootloader for rrom using Odin.
Click to expand...
Click to collapse
The actual bootloader is installed by kies... So which bootloader I have to install?
The only one that odin let me flash without problem is the one with 4.4.2 android from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
every other bootloader I tried give me a flash error and the screen show "incompatible version".
This will solve also the reboot part?
aleritty said:
The actual bootloader is installed by kies... So which bootloader I have to install?
The only one that odin let me flash without problem is the one with 4.4.2 android from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
every other bootloader I tried give me a flash error and the screen show "incompatible version".
This will solve also the reboot part?
Click to expand...
Click to collapse
Flash the bootloader then flash 4.4.2 rom, you can try this rom
forum.xda-developers.com/showthread.php?t=2672758
Should stop the sudden reboots.
Mufrad said:
Flash the bootloader then flash 4.4.2 rom, you can try this rom
forum.xda-developers.com/showthread.php?t=2672758
Should stop the sudden reboots.
Click to expand...
Click to collapse
Hello,
I have the same issues but I fear in my case these are early symptoms of a EEMC brick bug :crying:
I am on TWRP with Omega v24 and latest bootloader (i know because I have wifi, otherwise I would't have)
I got inconsistencies in the file system and today I had a UID mismatch message error at boot
I would like to format all the partitions (data/system/ecc) and flash a Rom via Odin just be sure...
Why are you sure that this rom should avoid reboot errors? Is there anyway to install this ROM or any other ROM via Odin so I can format all the partitions just to be sure?
Thanks!
Mufrad said:
Flash the bootloader then flash 4.4.2 rom, you can try this rom
forum.xda-developers.com/showthread.php?t=2672758
Should stop the sudden reboots.
Click to expand...
Click to collapse
Which bootloader? the latest from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
because I actually have it...
Is there anyway to install this ROM or any other ROM via Odin so I can format all the partitions just to be sure?
Click to expand...
Click to collapse
You can flash with odin and repartition with your pit (or another from xda but be careful with that) your same stock and then flash the indicated rom so you have a clean installation
aleritty said:
Which bootloader? the latest from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
because I actually have it...
You can flash with odin and repartition with your pit (or another from xda but be careful with that) your same stock and then flash the indicated rom so you have a clean installation
Click to expand...
Click to collapse
Sure go ahead and flash that bootloader.
SergioBigred said:
Hello,
I have the same issues but I fear in my case these are early symptoms of a EEMC brick bug :crying:
I am on TWRP with Omega v24 and latest bootloader (i know because I have wifi, otherwise I would't have)
I got inconsistencies in the file system and today I had a UID mismatch message error at boot
I would like to format all the partitions (data/system/ecc) and flash a Rom via Odin just be sure...
Why are you sure that this rom should avoid reboot errors? Is there anyway to install this ROM or any other ROM via Odin so I can format all the partitions just to be sure?
Thanks!
Click to expand...
Click to collapse
Do you have cwm? Then you can full wipe, then again you can format each partition separately, then go to android development thread, rom repository and download and flash stock rom, I suggested that specific rom because without the air command mod it's almost stock, without the Damned Knox.
Mufrad said:
Sure go ahead and flash that bootloader.
Click to expand...
Click to collapse
Ok thanks! I'll let you know how does it work!
Mufrad said:
Sure go ahead and flash that bootloader.
Do you have cwm? Then you can full wipe, then again you can format each partition separately, then go to android development thread, rom repository and download and flash stock rom, I suggested that specific rom because without the air command mod it's almost stock, without the Damned Knox.
Click to expand...
Click to collapse
I have TWRP, so I will do that from there.
Which STock rom do you suggest? I am on 4.3.2, I should use this?
http://forum.xda-developers.com/showthread.php?t=2536423
It seems it has Know anyway...
Should I use a pit file to repartition it?
Thanks!
aleritty said:
Ok thanks! I'll let you know how does it work!
Click to expand...
Click to collapse
Ok, I flashed bootloader (only sboot) from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
then flashed
n7100xxufnb4_unsecure.zip
from TWRP (and wiped everything before flashing of course)
The situation is the same of before, but the phone now doesnt boot completely, just remains at "samsung" logo.
Any idea?
aleritty said:
Ok, I flashed bootloader (only sboot) from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
then flashed
n7100xxufnb4_unsecure.zip
from TWRP (and wiped everything before flashing of course)
The situation is the same of before, but the phone now doesnt boot completely, just remains at "samsung" logo.
Any idea?
Click to expand...
Click to collapse
Flash this bootloader www.mediafire.com/download/b59xde333z6q8pv/BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5
Mufrad said:
Flash this bootloader www.mediafire.com/download/b59xde333z6q8pv/BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5
Click to expand...
Click to collapse
Yes Sir! Flashing!
aleritty said:
Yes Sir! Flashing!
Click to expand...
Click to collapse
Flashed this bootloader, heimdall give me:
Code:
Uploading BOOTLOADER
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOTLOADER upload failed!
Ending session...
and on the phone in red appear: unsupported version.
When I reboot appear
"Firmware upgrade encountered an issue. Please select recovery mode in kies & try again.
i have the same issue my note 2 restarting rapidly after a vibrate in samsung logo and successfully start up only when charger is connected. it happen after i install 4.4.2 leaked and revert to 4.3
Related
I woke up this morning to my phone perpetually rebooting.
I was running a nightly of CM 11.
Now when I try to go into Recovery I get a screen that asks for a password. I have no idea what that password is as I did not set one. I tried wiping data to no avail. I tried flashing a new recovery via Odin this did not work (Odin said successful but the screen on the phone never showed the transfer of the file). No matter what wipe method I use in recovery it just says fail, doesn't work at all and hangs or will say it can't mount. I have searched and searched and tried and tried and I'm stuck. I even tried ADB that didn't work either. Please help!
Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
audit13 said:
Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Click to expand...
Click to collapse
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.
therecker said:
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.
Click to expand...
Click to collapse
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This did not work. When I use ODIN all that is happening is that ODIN says it has succeeded but the little progress bar that usually shows up on the phone when you are in download mode never comes up. I did try this method though and it didn't work.
I restarted the phone in ODIN mode then opened ODIN then connected the USB cable then unchecked the two boxes you mentioned then flashed a new non TWRP recovery then waited for ODIN to say successful then the phone never showed the progress bar so I waited 2 mins until I pulled the battery then I restarted phone directly to recovery and still have the password prompt. Even after hitting cancel I cannot interact with recovery because every option I choose just says fail. I cannot even mount external sd card.
What phone do you have? What was the most recent stock ROM on your phone? Maybe you can flash a stock ROM.
There is a copy of the stock Samsung 3e recovery (which we can't use to flash zips with) I'm curious if maybe it can overwrite what you have going on? On the password screen I wasn't hitting cancel I was simply hitting the back arrow key. I will see if I have a copy of the stock recovery, just maybe you can flash it then flash another recovery after that so you can fix your phone.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have Samsung Galaxy S 3 At&T (d2att) SGH-I747 whichever one of those you want. The most recent stock rom on the phone was when I bought it brand new a few months after it came out. I tried installing a stock rom. I tried this using ODIN and it failed. The issue here is that TWRP somehow encrypted the entire file system so NOTHING at all in recovery works. When I use ODIN mode it never shows on my phone that it is accepting a transfer from the computer. When I tried the stock rom via ODIN method it actually failed in ODIN instead of telling me it succeeded and then just not work. It failed at the point when it says Firmware Update Start...aboot.mbn...NAND Write Start!...Complete(Write) operation failed. I am up for any suggestions but I need them to be detailed instructions because I have tried so many things I need to know what exact steps to follow.
I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.
audit13 said:
I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.
Click to expand...
Click to collapse
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?
therecker said:
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?
Click to expand...
Click to collapse
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?
audit13 said:
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?
Click to expand...
Click to collapse
It was a CM11 Nightly ROM from the very beginning of February. And before that it was a CM10.2 Stable ROM.
Which stock ROM was on your phone before you loaded a custom ROM?
audit13 said:
Which stock ROM was on your phone before you loaded a custom ROM?
Click to expand...
Click to collapse
I have no idea. It was when I first got the phone in November of 2012.
Sounds like your phone may be running a 4.3 bootloader which means your bootloader is locked and cannot be downgraded. This may explain why you are getting errors when trying to flash Odin. There is no stock AT&T 4.3 ROM that can be flashed via Odin.
I have PayPal for which I will use to donate an amount to the person(s) who can help me.
I just recently got a new GS4 becuase of an insurance replacement. I looked at the specs before I flashed TWRP. After failing to install 4.2.2 ROMS, I finally found a 4.3 mk2 stock ROM to install. I have the phone working. But TWRP is not installed. My phone tests positive for ROOT with Rootchecker
Currently I'm getting this message everytime I boot "Kernel is not seandroid enforcing"
I have multiple 4.4.2 and 4.3 ROMs I like to use on my SD card, I'd like to continue from a TWRP backup i've made using that recovery.
Here are my current specs:
Model
SGH-M919
Android Version
4.3
Baseband
M919UVUEMK2
Kernel Version
[email protected] #1
Build Number
JSS15J.M919UVUEMK2
SELinux status
Permissive
Secure boot status
Type: Samsung
The replacement phone was probably already on the MK2 bootloader and modem when you received it. Which means you had Knox pre-installed and tripped it when you rooted the phone. The "kernel is not seandroid enforcing" error message does not affect the functioning of your phone in any way. It's just a part of the Knox bootloader. You can continue to re-install TWRP recovery and flash any ROM you want. Your phone will function as normal. Just don't try reverting to the 4.2.2 MDL baseband/modem because it won't work. There's currently no way to revert to 4.2.2 MDL if you're on MK2 or higher. If you want to get rid of the message just flash the stock kernel in a recovery.
Try to be careful with your replacement phone now since you tripped Knox. It might be harder to get a replacement depending on how T-Mobile is.
No donations are needed for these kinds of things.
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Did I miss a step? All my actions were using odin to flash the twrp recover, and then flash another ROM, or restoring a Previous Back. Should I have flashed a rooted bootloader, or rooted firmware or anything besides those two?
nopotential said:
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Click to expand...
Click to collapse
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
brian117 said:
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
Click to expand...
Click to collapse
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
nopotential said:
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
Click to expand...
Click to collapse
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
brian117 said:
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Chain's Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
Click to expand...
Click to collapse
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
nopotential said:
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
Click to expand...
Click to collapse
Like I said donations are not needed. It does take a while for it to flash through Odin so that's normal.
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
nopotential said:
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
Click to expand...
Click to collapse
If you continue to have WiFi problems, flash this via recovery.
brian117 said:
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
If you continue to have WiFi problems, flash this via recovery.
Click to expand...
Click to collapse
It looks like everything is looking good by following your list. Thank you.
nopotential said:
It looks like everything is looking good by following your list. Thank you.
Click to expand...
Click to collapse
Awesome! Good to hear man. Enjoy KitKat and the newest modem. The new modem has gave a significant reception boost for a lot of people. Hope it's the same for you. And please check your PM.
-Deleted-
guys please help me tried dr ketan rom
and jellykat rom
both reach till boot screen and freeze.
i cant use odin because i need the data inside
any ideas please
OK this is not my phone so I didn't what firmware he was on
Now since no ROM is booting I flashed the new boot loader
And then as instructed i flashed stock recovery but still boot loader didnt complete install
And then flashed twrp again
And now I can't get to recovery
Edit 2 I got the boot loader from Dr.ketan ROM thread
Please anyone help I can't loose the data in the phone please help me
bump
alphatia said:
bump
Click to expand...
Click to collapse
Trying now
still doesnt work i disabled auto boot in odin and when the recovery flashed i tried entering recovery mode but the phone rebooted and got stuck at the samsung screen
alphatia said:
guys please help me tried dr ketan rom
and jellykat rom
both reach till boot screen and freeze.
i cant use odin because i need the data inside
any ideas please
OK this is not my phone so I didn't what firmware he was on
Now since no ROM is booting I flashed the new boot loader
And then as instructed i flashed stock recovery but still boot loader didnt complete install
And then flashed twrp again
And now I can't get to recovery
Edit 2 I got the boot loader from Dr.ketan ROM thread
Please anyone help I can't loose the data in the phone please help me
Click to expand...
Click to collapse
What is your recovery?
You can not come in?
If so, make a backup of what is without creating MD5 checksums then upload the rom again and restore only the data.
Regards
lud3ik said:
What is your recovery?
You can not come in?
If so, make a backup of what is without creating MD5 checksums then upload the rom again and restore only the data.
Regards
Click to expand...
Click to collapse
Here is my problem
My friend gave me his note 2 to fix WiFi it was already rooted
I downloaded slimkat and flashed it it worked good
And WiFi worked but he wanted a touchwiz look
So I downloaded jellykat ROM but didn't read the instructions and flashed with cwm
Got into bootloop then I flashed twrp recovery using Odin and reflashed the ROM but I got the fix root error and I swiped to fix
Then also bootloop ..I downloaded Dr.ketan stock ROM
And flashed philz recovery through twrp recovery and then flashed ROM also backed up efs
The phone also didn't boot stuck at bootscreen
Then I got frustrated and didn't know what to do I flashed the nd3 bl through Odin
And rebooted but nothing changed ..I read in Dr.ketan thread about flashing stock recovery and the bl
So I did all through odin and I rebooted but I had no recovery I tried flashing both twrp and cwm through Odin but also nothing
Now I have no recovery but I have download mode
I can Odin flash stock but I can't loose the data inside I really need the data
i think the problem is with the boot loader since i flashed nd3 bootloader and when device booted it didnt finish
so any ideas???
Why not any 4.4.2 stock firmware through Odin? Seems to be the easiest way to get the device started again.
Androidwizzard said:
Why not any 4.4.2 stock firmware through Odin? Seems to be the easiest way to get the device started again.
Click to expand...
Click to collapse
I need the data the pics an videos
But will this work
http://forum.xda-developers.com/showthread.php?t=2531989
Or this
http://forum.xda-developers.com/showthread.php?t=2230250
Note that I flashed nd3 and the Knox warranty void is 1
alphatia said:
I need the data the pics an videos
But will this work
http://forum.xda-developers.com/showthread.php?t=2531989
Or this
http://forum.xda-developers.com/showthread.php?t=2230250
Note that I flashed nd3 and the Knox warranty void is 1
Click to expand...
Click to collapse
Both won't work.
Download 4.4.2 stock firmware from sammobile and flash with Odin.
Data (if it is still there) won't be touched. Only system partition will be wiped.
Androidwizzard said:
Both won't work.
Download 4.4.2 stock firmware from sammobile and flash with Odin.
Data (if it is still there) won't be touched. Only system partition will be wiped.
Click to expand...
Click to collapse
Okay about the data I never wiped it but Odin might wipe it some say it will some say it won't
And why will these non wipe not work can u inform me please?
alphatia said:
Okay about the data I never wiped it but Odin might wipe it some say it will some say it won't
And why will these non wipe not work can u inform me please?
Click to expand...
Click to collapse
Look, flashing with Odin is like getting an update by Samsung. Users would turn crazy if such an update would wipe their data.
Firmware is always installed in system partition and never somewhere out.
Besides: Photos and vids are mostly saved on external SD. Where are yours?
Androidwizzard said:
Look, flashing with Odin is like getting an update by Samsung. Users would turn crazy if such an update would wipe their data.
Firmware is always installed in system partition and never somewhere out.
Besides: Photos and vids are mostly saved on external SD. Where are yours?
Click to expand...
Click to collapse
mine are saved on internal
so now only thing i can do is flash using odin?
alphatia said:
mine are saved on internal
so now only thing i can do is flash using odin?
Click to expand...
Click to collapse
No, it is not the only thing, but you have messed around such a long time and to finish the suffering I suggest to do.
It is up to you to trust or go on searching for alternatives.
Androidwizzard said:
No, it is not the only thing, but you have messed around such a long time and to finish the suffering I suggest to do.
It is up to you to trust or go on searching for alternatives.
Click to expand...
Click to collapse
Thanks a lot man iI really appreciate it but any other ideas would be much appreciated
alphatia said:
Thanks a lot man iI really appreciate it but any other ideas would be much appreciated
Click to expand...
Click to collapse
Well, two things you might do: Search for the truth about wipe data when using Odin or try to install any custom recovery to be able to flash a custom rom.
Androidwizzard said:
Well, two things you might do: Search for the truth about wipe data when using Odin or try to install any custom recovery to be able to flash a custom rom.
Click to expand...
Click to collapse
and am back cant get any recovery to work
and when searching for odin wipe most people say nothing got wiped
alphatia said:
and am back cant get any recovery to work
and when searching for odin wipe most people say nothing got wiped
Click to expand...
Click to collapse
I KNOW that nothing of your data will be wiped, I have done it three times since 4.4.2 came out on 25.4.2014
First ND3, then NE1 and lately NE2.
This is my last post here. Good luck!
Androidwizzard said:
I KNOW that nothing of your data will be wiped, I have done it three times since 4.4.2 came out on 25.4.2014
First ND3, then NE1 and lately NE2.
This is my last post here. Good luck!
Click to expand...
Click to collapse
ok man wish me luck thanks alot for alot of help
Any other suggestions before I flash 4.4.2 with Odin (currently 4.1.2) ?
Noob here. Been trying to figure this out for a while. I have a Galaxy s3 model number: i747m. Was using the phone watching youtube and all of a sudden it turns off and back on with the "Device memory Damaged" screen. I was willing to lose everything and hit the "reset device" button but every time i press it, nothing happens! I try to go into recovery menu to see if i can wipe data that way but every time I try to go into Recovery, I am met up with the Android laying down with a red triangle and an exclamation point above it. Is it possible to fix this?? I can only get into the download mode. If it helps I believe I was on the latest 4.4 KitKat update and was unlocked and using T-mobile network.
Could you post some screen shots of the error
crazymonkey05 said:
Could you post some screen shots of the error
Click to expand...
Click to collapse
I am unable to because i cant get into the phone itself. I can take pictures from my other phone and post them up. Sorry for the late reply but if you can help me it would be much appreciated!
Well if you can't get in to recovery then I'm not really sure how to recover
Can you get into download mode?
audit13 said:
Can you get into download mode?
Click to expand...
Click to collapse
I actually can! Just dont know what to do after that.
What bootloader is on your phone? I assume it is the KK bootloader since you had stock 4.4.2.
Is your phone from a Canadian carrier?
audit13 said:
What bootloader is on your phone? I assume it is the KK bootloader since you had stock 4.4.2.
Is your phone from a Canadian carrier?
Click to expand...
Click to collapse
Its was and is a Canadian phone. It was on 4.4.2 KK just so boggled on whats the problem?
You could try flashing your phone with the latest firmware from sammobile.com.
audit13 said:
You could try flashing your phone with the latest firmware from sammobile.com.
Click to expand...
Click to collapse
I tried to but everytime the flash begins then it says "FAILED" am i doing something wrong?
What ROM are you trying to flash? Post a screen shot of Odin with the error.
audit13 said:
What ROM are you trying to flash? Post a screen shot of Odin with the error.
Click to expand...
Click to collapse
Here it is. I tried about 3 different files and I get the same thing on all.
It's failing because the program is trying to downgrade or alter the bootloader which is causing the error to appear after trying to write aboot.mbn. Do not attempt anymore flashes using Odin as a failed bootloader download could result in a hard brick.
Try installing a custom recovery such as Philz using Odin, boot into recovery, try wiping everything on the phone and install a custom ROM.
You can try flashing latest Philz from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
audit13 said:
It's failing because the program is trying to downgrade or alter the bootloader which is causing the error to appear after trying to write aboot.mbn. Do not attempt anymore flashes using Odin as a failed bootloader download could result in a hard brick.
Try installing a custom recovery such as Philz using Odin, boot into recovery, try wiping everything on the phone and install a custom ROM.
You can try flashing latest Philz from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Click to expand...
Click to collapse
No luck i get this error message
You need to use the latest tar.md file, not zip.md5.
audit13 said:
You need to use the latest tar.md file, not zip.md5.
Click to expand...
Click to collapse
the flash went through without a problem. The problem is that i cant get into recovery because every time I try i get the android laying down with a red triangle above him with an exclamation mark in it. Is this just a dead phone?
Flash it again but don't check auto reboot. Once you see reset in the status window, disconnect USB cable, pull battery, replace battery, boot into recovery.
audit13 said:
Flash it again but don't check auto reboot. Once you see reset in the status window, disconnect USB cable, pull battery, replace battery, boot into recovery.
Click to expand...
Click to collapse
Same thing :/
When you flash Philz, you see the word "reset" in the status window? Try flashing TWRP in Odin.
audit13 said:
When you flash Philz, you see the word "reset" in the status window? Try flashing TWRP in Odin.
Click to expand...
Click to collapse
Yes it said reset and it went through but still won't go to recovery just the same android exclamation image. Where can I download the TWRP? Do I need a specific one?
Hi
Been trying to install twrp-3.5.2_9-0-starlte.img.tar to my S9.
First i succesfully unlocked bootloader. Then installed twrp through Odin v3.14.1.
Then the phone succesfully boots into twrp recovery. Then i flashed and tried to install no-verity-opt-encrypt.. 6.1 didnt work so i flashed and tried all down to 4.0. Nothing worked. Just got the error 1 all the time.
Then i tried the read somewhere that i could try the multidisabler. Ref this thread: XDA link. This succsefully installed. Then i rebootet through twrp with the option to install twrp app. The phone got stuck in a start up screen for 10 min and took me right back to start.
After again logging in and setting up the phone Nothing seems to have changed. Only that the bootloader is still unlocked.
Am i doing something wrong? Is it suppose to boot up again to stock OS?
Wheelx said:
Hi
Been trying to install twrp-3.5.2_9-0-starlte.img.tar to my S9.
First i succesfully unlocked bootloader. Then installed twrp through Odin v3.14.1.
Then the phone succesfully boots into twrp recovery. Then i flashed and tried to install no-verity-opt-encrypt.. 6.1 didnt work so i flashed and tried all down to 4.0. Nothing worked. Just got the error 1 all the time.
Then i tried the read somewhere that i could try the multidisabler. Ref this thread: XDA link. This succsefully installed. Then i rebootet through twrp with the option to install twrp app. The phone got stuck in a start up screen for 10 min and took me right back to start.
After again logging in and setting up the phone Nothing seems to have changed. Only that the bootloader is still unlocked.
Am i doing something wrong? Is it suppose to boot up again to stock OS?
Click to expand...
Click to collapse
All you've done is installed custom recovery over stock. This by it's self doesn't effect stock system firmware. The only thing is because knox is trip you lose knox related apps functions.
spawnlives said:
All you've done is installed custom recovery over stock. This by it's self doesn't effect stock system firmware. The only thing is because knox is trip you lose knox related apps functions.
Click to expand...
Click to collapse
Hi and thank you.
Knox is trip?
So how do i know that this worked and twrp is succesfully installed?
Wheelx said:
Hi and thank you.
Knox is trip?
So how do i know that this worked and twrp is succesfully installed?
Click to expand...
Click to collapse
Knox is a Samsung thing. Once tripped it stays tripped and there is no cure for it. As said you will loose knox related apps functions like secure folder,samsung pass,Shealth etc.
To enter twrp is the same process as entering download (odin) mode except you use to volume up button ( power/bixby/vol up ) while device is starting up.
spawnlives said:
Knox is a Samsung thing. Once tripped it stays tripped and there is no cure for it. As said you will loose knox related apps functions like secure folder,samsung pass,Shealth etc.
To enter twrp is the same process as entering download (odin) mode except you use to volume up button ( power/bixby/vol up ) while device is starting up.
Click to expand...
Click to collapse
Yeah it says warranty something 1 on download screen.
I tried to shut down phone and start in recovery mode, but i loded into the stock recovery, not twrp. Am i doing something wrong?
Wheelx said:
Yeah it says warranty something 1 on download screen.
I tried to shut down phone and start in recovery mode, but i loded into the stock recovery, not twrp. Am i doing something wrong?
Click to expand...
Click to collapse
Without knowing your exact steps it a bit hard to say.
I would say that the multidisabler zip you tried didn't work. The zip you tried is for the S10 series. It's also a common problem on latest version of android that the no-verity-opt-encrypt.. 6.1 fails. Very basically this zip, after format data stage,
will prevent phone from re-encrpyting itself when booting into the system.
Try using this zip when installing twrp
Edit:
Installing the twrp app i leave up to you. Can be install later by twrp or playstore and not necessary for installing twrp recovery.
spawnlives said:
Without knowing your exact steps it a bit hard to say.
I would say that the multidisabler zip you tried didn't work. The zip you tried is for the S10 series. It's also a common problem on latest version of android that the no-verity-opt-encrypt.. 6.1 fails. Very basically this zip, after format data stage,
will prevent phone from re-encrpyting itself when booting into the system.
Try using this zip when installing twrp
Edit:
Installing the twrp app i leave up to you. Can be install later by twrp or playstore and not necessary for installing twrp recovery.
Click to expand...
Click to collapse
I have the same problem. Im Gonna try it out
EDIT: i got the write error. gonna try flashing stock again
edit2: flashing stock didnt work. gonna try turning off bootloader and turning it back on. if it does not work then im just gonna install normal XEO instead of PLS
EDIT3: yeah didnt work. just gonna install XEO now