Hi All,
I attempted to flash my I747 to the latest 4.3 ROMs (I first flashed to I747UCUEMJB modem and bootloader) from 4.2.2 ROM. However, no matter which 4.3 ROM I use, I am always asked to enter PIN or password used to encrypt memory after the new ROM boots up. Some ROMs will show "Unfortunately the UI has stopped working", but others will simply ask me to enter PIN or password over and over and over. It does not matter what I enter, it just won't work.
Does anyone else experience this issue?
I think this is caused by my company email requiring encryption on my phone in my 4.2.2 ROM. However, I thought factory reset and data wipe will erase all encryption, or not?
Can anyone help me? Seems the only way to unbrick my phone is to use ODIN to flash stock 4.3 ROM. However, there is no 4.3 stock firmware to download... Only custom ROMs out there.
Are you doing a wipe of the cache, data, Dalvik, and system before installing a new ROM? Try a KK ROM instead of a 4.3 ROM.
audit13 said:
Are you doing a wipe of the cache, data, Dalvik, and system before installing a new ROM? Try a KK ROM instead of a 4.3 ROM.
Click to expand...
Click to collapse
Yes I wipe cache, data, system, dalvik all of them before each flash.
Can you please point me to "KK ROM"? What exactly is a KK ROM? I have tried many 4.3 ROMS, and all of them will bring me back to the "Enter your PIN or password" screen on the initial boot.
Try something like Validus release version 4.3. It is based on 4.4.2 KTOH.
I also recommend using the latest CWM. I had problems using TWRP.
Related
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Firewalker1980 said:
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Click to expand...
Click to collapse
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
ahmadallica said:
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
Click to expand...
Click to collapse
Hey thx for your suggestions!
I always flash a "new" rom that way though. But an update of the same rom, I "dirty" flash, which should be fine according to everyone.
No matter what Rom/Kernel I use, I still frequently have to pull the battery out.
It's never from locking up within Android. It just freezes/loops on the Google bootlogo.
I once wiped everything, even the storage space, and it helped for a little while, but did not make it go away for good.
Could it be related to certain apps ? Maybe PGM or Seeder or smth ?
All input welcome
---------------------------------------------------------------
Phone: Samsung Galaxy Nexus Maguro
Rom: AOSPA 2.99 latest
Kernel: AK Purity v20
Recovery: TWRP 2.3.3.0
Hey Everyone,
I have been trying to upgrade my phone from 4.2.2 to 4.3, TWRP 2.6
My settings for 4.2.2 are as follows: TASK650 7.20b, Stock Kernel, LK3 Modem and corresponding boot loader , TWRP 2.6
I decided to give PAC-Man 4.3 nightlies a try following these steps. Factory reset 2x, format data, update modem to MG2 and corresponding bootloader. Now the first time the ROM loads there is no problem, brings up the G-mail account information and everything is works. Rebooting the phone however causes it to freeze on the Kernel Splash, and does not allow for the ROM to boot.
Attempts to fix: factory reset, format data, wipe cache and dalvik as well as internal storage. Followed the process for installing the ROM, still intial works but reboot fails and same thing happens.
To get my phone working again, I have ODINed back to LK3 modem and bootlaoder, and restored my latest 4.2.2 backup.
What can I do to upgrade to 4,3? OR is it that my phone cant handle the new update? Anyone else in a similar situation?
General info ...
Update from:
Bootloader: (???same as modem???)
Modem: I747UCDMG2 (http://forum.xda-developers.com/showthread.php?t=1831898)
ROM: CM 10.2 (http://download.cyanogenmod.org/?device=d2att)
GAPPS: 20130813 (http://wiki.cyanogenmod.org/w/Gapps)
TO
Bootloader: I747UCUEMJB (http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23)
Modem: I747UCUEMJB (http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23)
ROM: CM 11 nightlies (http://download.cyanogenmod.org/?device=d2att)
GAPPS: 20131119 (http://wiki.cyanogenmod.org/w/Gapps)
Does this setup look alright? Will it work?
Any danger of incompatibities/brick?
Any need for I747UCUEMJB kernel? Or, is it included/superseeded by CM 11? (http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18)
Thanks!
You can flash any ROM you want after upgrading your boot loader. Just do not try to downgrade your boot loader to anything below 4.3 as it will result in a hard brick.
Can't Flash anything
I was on stock 4.3 and i decided to upgrade to the [ROM][9.15.14] LikeWise Galaxy S5 | TouchWiz 4.4.2 | NE4 | Version 4.1.
It didn't work. It gets stuck on the s5 samsung logo boot. I decided to return to 4.3 but it doesn't work it gives the status 7 error.
Files i have
1. d2att_I747UCUEMJB_modem.zip
2. I747UCUEMJB_bootloader.............. I am not able to flash this
3. att-LikeWise-v4.1-NE4-9-15-14
4. update43
Status 7 errors can happen with an outdated bootloader.
I highly recommend Philz Touch which can be flashed in Odin or from your existing custom recovery.
audit13 said:
Status 7 errors can happen with an outdated bootloader.
I highly recommend Philz Touch which can be flashed in Odin or from your existing custom recovery.
Click to expand...
Click to collapse
yea i used philz_touch_6.07.9. I also tried flashing I747UCUEMJB_bootloader because i suspected that i couldn't revert to 4.3 because of an outdated bootloader, but that didn't work either.
I will really love that S5 ROM but now i can't even flash anything.
I can view my recovery and download mode.
I suggest downloading a CM11 for a d2lte and flash it in recovery. Before flashing, I recommend that you wipe cache, dalvik, data, and system. After flashing, wipe cache, data, and dalvik again just to be sure everything has been cleared, then boot the phone.
audit13 said:
I suggest downloading a CM11 for a d2lte and flash it in recovery. Before flashing, I recommend that you wipe cache, dalvik, data, and system. After flashing, wipe cache, data, and dalvik again just to be sure everything has been cleared, then boot the phone.
Click to expand...
Click to collapse
Please how do i even know if my s3 at&t is d2att or d2lte?
Slemgen07 said:
Please how do i even know if my s3 at&t is d2att or d2lte?
Click to expand...
Click to collapse
Hey!!! I've installed the CM11 d2lte and it's running perfectly.
Quick one, i'm still interested in installing the likewise S5 ROM. Now that i'm on the CM11, how do i go about it?
Thanks for your assistance, it was highly helpful.
Make sure you have the latest custom recovery on your phone. Copy the custom ROM to your phone, boot into recovery and create a nandroid backup of your current ROM. Once the backup is complete, wipe cache, dalvik, and flash the custom ROM.
Make note of any errors messages you get when flashing the new ROM.
audit13 said:
Make sure you have the latest custom recovery on your phone. Copy the custom ROM to your phone, boot into recovery and create a nandroid backup of your current ROM. Once the backup is complete, wipe cache, dalvik, and flash the custom ROM.
Make note of any errors messages you get when flashing the new ROM.
Click to expand...
Click to collapse
The mistake i was making was that i didn't mount the system after i flashed the Likewise ROM. The moment i did it, it booted correctly. Almost everything is working perfectly fine. If i try to change the lockscreen wallpaper and it brings out the Gallery, wallpaper and err... some other option, when i select the wallpapers for the lockscreen the settings crashes.
You guys are just awesome. Thanks!
Hi,
For about a few days, I can't flash any touchwiz based rom, even the ones I could flash without any problem before. After I flash any touchwiz rom, my phone goes into a bootloop cycle. Though I can boot into recovery and download mode with key combinations. I don't know when this happened for the first time but as far as I can remember, it would be after I flashed some 4.4 AOSP rom (could be Omnirom, I'm not sure though)
What I did to recover from boot loop:
- Wipe cache, wipe dalvik cache and reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, wipe data/media, reboot, no joy.
- Pulled out the battery between these steps too.
At first, I thought something was wrong about the aroma installer itself because the phone was getting frozen during aroma installer setup screen, then I came up that it was caused due to my older CWM version, so I updated the recovery and it didn't freze again during installation.
And by the way, I've lost my efs partition during these processes, thankfully I've had a nandroid backup from a couple of months before.
Now I'm stuck with AOSP roms and the only way I can use a touchwiz rom is to flash the stock rom via odin. But I want to use the new leaked version based Note3 featured roms.
I've seen similar topics at S4 section but I couldn't be sure if I can do the exact steps for an N7100 international device.
I'm pretty familiar with linux system and I can use adb so I can provide any kind of information you need to diagnose this issue. Thanks in advance. Best regards.
HOW I SOLVED THIS PROBLEM
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Guys, I really need some help.. Any idea about what might the problem be?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful:http://d-h.st/fWr
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
akp.ajinkya said:
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful..
Click to expand...
Click to collapse
Thanks for the reply. I flashed this superwipe script, then flashed DN3 rom but still I got stuck at Samsung Galaxy Note II screen boot loop. I really don't understand this. What am I missing? What would happen if I wipe the entire internal memory block, I mean the whole things, even the root partition too.. I'm thinking that maybe there's some file inside the root partition that prevents me to flash touchwiz roms or perhaps something wrong about touchwiz based roms' bootloaders.. I'm truely pissed..
(InsertNameHere) said:
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
Click to expand...
Click to collapse
Have you read my first message? I remember that I've mentioned I've done already what you ask me to do.. Believe me I wouldn't shoot a new thread if I could've solved my problem with such easy steps. I've already done so many wipes, including internal SD and whatsoever.. I'm really confused and NEED help. Thanks anyway..
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Im having the same problem but after flashing kernels (e.i. saber & perseus).
Im currently running on Tigra rom. Is this a compatibility issue or im just missing something here too?
I came across flashing bootimg but this thread http://forum.xda-developers.com/showthread.php?t=1752270
is for One S, im not sure if will work on Note 2 & haven't tried it yet.
Any suggestions? help pls...
akp.ajinkya said:
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Click to expand...
Click to collapse
Well, the problem is gone.
What I did was the things you said.
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Happy to help you bro
I'm having some issues flashing any ROM. TWRP will not wipe data, or internal SD
For some reason, when I go to wipe data and factory reset, TWRP will say it was successful, but nothing ever gets wiped. It will only wipe system if I choose to. I've gotten a ROM to flash but when it boots up, all of the old apps and user data are still there and it makes everything crash. I've gotten into settings to do a reset, it reboots into recovery, runs the script, and still nothing wipes.
What I have tried:
Old TWRP, newest TWRP
CWM (seems to wipe but it won't get past the note 2 screen after flashing anything)
Wiping with CWM, flashing TWRP, then flashing a ROM (still loops after the note 2 screen)
Is there a terminal command I can use in TWRP to manually wipe things?
Thanks for any help I can get, I've flashed so many phones I can't remember but I've never had this issue
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
audit13 said:
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
Click to expand...
Click to collapse
Well when it bootloops t the Note 2 screen, I have to flash a ROM with Odin to get it working again. I've flashed a stock ROM with Odin, flashed TWRP with Odin, tried the wipes and it never wipes anything... I'm lost...
Isn't there a format function in TWRP that is seperate from the factory reset or advanced wipes? I was also trying to find a terminal command to type in the terminal in TWRP... I'm a little stumped...
I'm sorry, I read that too fast... That may actually work, wipe it in the stock recovery, and just don't let it boot into the system before flashing other stuff... I'm gonna try that out... Thanks man, I'll post back about it...
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
audit13 said:
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
Click to expand...
Click to collapse
The stock ROM I used is I317-ODIN-UCUCNJ1-Stock without the booloader packaged in, I'm still on the old bootloader. It's 4.4.2
The ROMS I've tried to flash was
Cyanide (Error 7, says incompatible data, please wipe the phone)
Resurrection Remix (Error 7, says incompatible data, please wipe the phone)
Latest CM10 Nightly
I got CM10 and Resurrection Remix to flash a couple times, but the phone boots and all the old apps and data, including the AT&T ones are still there, and the system keeps crashing. Then I change the recovery to CWM because it seems to wipe, change back to TWRP, flash the ROM and gapps again, but it bootloops at the Note 2 screen.
Should I try the 4.1.1 ROM and CWM? Whenever I'm going from a stock TW to non-TW I like to format everything, data, cache, system, and internal SD, but of course TWRP won't wipe the data or the internal SD.
It's probably because the bootloader and modem are too old for the roms. Recent roms will need updated bootloaders.
Ok, I had some more time to mess around with this today and figured it out. I feel kind of dumb but oh well, I got it.
TWRP was already loaded on, so I went to messing with it again. The 'Swipe to factory reset' was not wiping the data, and there was the 'Format Data' button right there in front of me. I did the factory reset, format data, rebooted recovery, wiped dalvik, cache, and system, then flashed the ROM and everything booted up just fine.
Thanks for all of the help!