[Q] strange boot bugs - Galaxy Note II Q&A, Help & Troubleshooting

i have n7100 . running stock deodexed nd3 4.4.2
running twrp 2.7.2
but had the prob since 2.7.0
the problem is when i try to restart from my rom to recovery sometimes like 50 % of the time i have one of 2 bugs either a
firmware upgrade error bla bla bla ..
or strange download mode screen with no info on the top left side (which doesn't work with odin ..i have tried )
restarting the phone from the first case always fix it and everything is back to normal
the second one is tricky sometimes just a simple reboot fix it and sometimes i need to enter normal download mode and install the recovery again which then the phone boot's to it and from then to system
any ideas what's the cause of this ??
and had this problem over a variety of roms and twrp and philz recoveries but i mainly use twrp

77 view without a single reply !!!!!!!!!!

Related

Samsung Logo Keeps Flashing, wont boot HELP

Never thought I'd be the one to create a thread like this..
After I flashed the OKV4 ROM, strange things started to happen (this was after a full wipe). Apps kept force closing, etc. Later that day, when I picked up my phone, I saw the samsung logo flashing over and over. Making me unable to enter recovery.
Download mode still worked though and I proceeded to flash a stock firmware via ODIN. This did not help. Oh, and the Odin flash succeeded, without rebooting my phone though...
So, I'm still stuck with my phone which can't seem to get out of this strange loop.
HELP :C
I remember reading somewhere here that if you have flashed a diff FW now and then a possibility the last recent kernel is still in the system folder etc....this is maybe the cause of the bootloop.
Since you had confirmed going to download mode is possible..this may work logically... Why not do the following :
Get your phone rooted via Recovery (there is a thread here by The-E)..Once done flash arco68's CWM Recovery....Boot to recovery n do this :
Factory Format....Wipe n Clear including Delvik...Then go to Mount n Storage wipe every single folder...System...Data...Etc (this will wipe every single data left behind but I assure you the CWM will not be wiped) once done reboot n put the device into DL mode and use Odin to flash back to the stock FW.
From this moment the recovery will be replaced by stock version and the stock FW will be restored....once it boot up..Walla as I had done this over two times :
Best of Luck !!
Sent from my GT-I8150 using xda premium
I think you misunderstood me :/
This isn't the ordinary bootloop where the boot animation plays. It resets literally 2 seconds after starting. This makes me unable to enter the recovery at all. Thanks for the effort tho.
Tl;dr:I can not enter recovery mode.
treUse said:
I think you misunderstood me :/
This isn't the ordinary bootloop where the boot animation plays. It resets literally 2 seconds after starting. This makes me unable to enter the recovery at all. Thanks for the effort tho.
Tl;dr:I can not enter recovery mode.
Click to expand...
Click to collapse
Hi Bro...
I already discuss it in this Tread couple a days a go
You not alone bro
I ask The-E to mention all Wonder user to get safety flashing
Until this time we didn't get way to fix it yet

[Q] WildFire S A510b CWM recovery problem

hi friend's
i have a problem with this model of WFS A510b....
i tri'ed many recovery by many method's...
while i flash a castum recovery on WFS A510b,the LCD is going black and show nothing...but the phone is alive and it has current by the voltage source...the current is normal and it shows that the phone is working correctly...by pressing up and down and the power,current will change...and the phone can boot and works well...the problem is just at the recovery menu...
when i flash stock recovery it will shows the recovery and every thing is ok...
*******
when i downgrade the phone with 2.3.3 firmware...it shows nothing and the phone is alive again....phone boots but show nothing at all at every menu's ...by flashing 2.3.5 rom again the phone will work good without problem ...
*******
i think this is because of the base of the castum recovery's that exist now for WFS...is there any recovery that based on 2.3.5 roms?!!!
any idea?!!!
any solution?!!
yes i have this problem too

[Q] [HELP] Boot loop - cant mount efs [partly solved]

Hi guys,
first ill try to explain how I got where I am right now.
Sometimes my Phone gets so low in power it just shuts down, after plugging in the power it will show a charge icon for a few seconds and it will automatically try to boot again, once finally booted it shuts down again due to the lack of power.
What I normally do to fix this is go into recovery or download mode because this uses far less power and so I can charge it to like 5 or 10 percent and boot normally.
This time after charging it to 5 or 10 percent it wont boot at all and it's looping. I allready reinstalled my current Rom (Omega V29) but still no normal boot. After a full whipe and installing V30 I still cannot get beyond the boot animation.
what I tried:
- Reinstalling the same Rom I'm using for months.
- Full Whipe
- Install V30 ROM
- removing Sim and SD card
- Now trying to go back to stock using Odin.. also not working..
Is there anyone out there who has any ideas left for me to try? :'(
thanks in advance!
one more thing! If I get this phone running again I would be very happy if someone could show me a method to disable the autoboot. I remember my previous phones could just charge without automatically trying to boot the device.
>> I found out that after installing the ND3 bootloader it will not autoboot, so that's one step in the right [email protected]
One important information missing:
What's your current firmware, especially bootloader.
Then: what firmware have you tried to flash thru Odin?
What recovery/version do you work with?
current firmware:
Omega v29 (27/05/2014):
Based on firmware XXUFNE1 Android 4.4.2 (Date: 06/05/2014)
current bootloader:
MJ5
Firmware I tried flashing to solve the problem:
Omega v30 (19/09/2014) Based on firmware XXUFNG4 Android 4.4.2 (Date: 30/07/2014) USING RECOVERY
DN3_v5.5_N7100_2nd_september.zip USING ODIN
Latest stock rom USING ODIN
bootloader I tried flashing to solve the problem:
N7100_KK_ND3_BL.tar.md5
Recovery I'm using:
TWRP latest
Recovery I tried:
CWM latest
also the error "E: Unable to mount '/efs' " displays when i try to factory reset using TWRP
I found out that somehow my efs was corrupt. Unfortunately I did not have a backup.
I did however found a working efs backup on the internet which I flashed using Odin. Now the Phone boots and I have a IMEI number that is not correct. So last step is to fix the IMEI number and I should be back in business.

[Q] Issues after OTA

Have a bit of a problem here. I gave my parents my SGS3 and i know i had a root on it and was running stock. Im pretty sure that before giving it to them i ran an OTA lost root then re rooted. This most recent OTA has left the phone in a boot loop. Since it has been so long i have no idea what version it was running. Ive done some reading here and thought the solution would be to go back to 4.1.1 but i few posts warned that it could hard brick the phone if it was upgraded to 4.3... Anyway to tell what i have on there. I can get to download mode. Unable to get recovery open. ...Any help would be helpful. Thank you
Boot into download mode. Do you see anything on the screen about warranty bit?
Yes set to 1 now... it was zero earlier before I tried to fix my issues via kies.
Now I don't get boot loop any more but it just asks to be hooked back to kies to fix issue which it doesn't
Sent from my SAMSUNG-SGH-I337 using XDA
You tried to fix/update with kies? Are you getting an error message about a firmware problem?
The fact that you have a line in download mode about warranty means you have at least a 4.3 bootloader; therefore, you cannot flash back to 4.1.1.
I suggest you flash Philz Touch for the d2lte and flash CM11 to at least get your phone booted so you can confirm the bootloader and modem on your phone.
Yes I tried kies... It starts to download it but then fails and does not give me an "emergency recovery code" so i can not continue.
when turning on the phone no it loads up a screen that shows the ODIN info at the top like in download mode but in the center of the screen it says " Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." Of course no luck there.
Ok so i at least have 4.3 bootloader... one check off the list...thank you
I will flash Philz touch and then CM11 ... I should be able to use ODIN ?
Going to use Philz touch philz_touch_6.48.4-d2lte.zip ...
Use Odin 3.07 to flash Philz Touch but make sure you download and flash the tar.md5 version, not the zip version.
I had 3.09 and got philz on .... trying to find a usable CM11 I have Att as my carrier.. was going to use one of the stable releases cm-10.2.1-d2att.zip ... used a micro sd to load on the rom ... but after i attempted to install the i got installation aborted ( Status 7)
http://download.cyanogenmod.org/?device=d2lte
"all I can really do, is stay out of my own way and let the will of heaven be done"
Ok so i got cm-11-20141209-NIGHTLY-d2lte.zip loaded.....
I would like to get this back to stock as or as close as possible ( touchwiz and all) this was my mothers phone 60+ years old ...she doesnt like change
thanks for the help so far what info do we need
Android version 4.4.4
Baseband I747UCUFNJ1
Kernel
3.4.104-cyanogenmod-g38a4e52
[email protected] #1
dont know if this one youre looking for but this should take you to stock 4.4.2. (read read read - have a backup - go slow and ask questions if not sure).
http://forum.xda-developers.com/showthread.php?t=2788357
"all I can really do, is stay out of my own way and let the will of heaven be done"
Thank you ... i will probaly need to down load the stock Odex or stock deodex?? i do not need
Stock Kernel, insecure, init.d, sdcard R/W, selinux permissive ? thanks
How can i tell what boot loader version i have ?
download samsung info app from play store. or if have terminal emulator app on phone type in : su (enter = to grant superuser priv.)
type in : getprop ro.bootloader (enter = this will tell bootloader version).
first option is easiest/less chance (0%) for error/mistype.
"all I can really do, is stay out of my own way and let the will of heaven be done"
ok ...downloaded it but I dont see where it says what version example 4.3 or 4.4.2
Im attempting to load the ROM you recommended.
http://forum.xda-developers.com/showthread.php?t=2788357
Prerequisites include a minimum of a 4.3 bootloader and modem.
If you are not on the official 4.4.2 bootloaders and modem then you will need to flash ktoonsez kernel. http://forum.xda-developers.com/show....php?t=1756776
Directions:
1. Factory data reset
2. Flash ROM
3. If your still on 4.3 bootloader flash ktoonsez kernel immediately after the rom.
4. Let phone boot up, go through start up etc...
5. Open SuperSU, Let it disable Knox. If it gets stuck, press the home button and reboot the phone and try it again. It will work the 2nd time.
6. Nothing else to see here.
Got that ROM installed finally but the WiFi will not turn on
***Never mind reloaded the kernel and 2nd time and worked.

M9 in bootloop, TWRP stopped working

Hello all, my M9 has been crazy since some days. I have a lot of different problems and haven't been able to see what the common issue is, so I will list everything I know:
1. European M9 unlocked, baseband 01.01_U11440792_97.00.51203G_F, OS-3.35.401.32
2. Had official Android 6.0 and couldn't update OTA to Nougat (update crashing after 25%) so I tried rooting and flashing a custom ROM (RR-N-v5.8.0-20170106-himaul-Unofficial). Worked without problems for 3 months and 2 days ago my phone restarted and didn't boot to the rom anymore (I see the HTC logo with white background and red letters, after 10 seconds or so I see the logo of my rom but it freezes and restarts again, over and over again).
3. Tried flashing the same version stock rom with RUU method (renaming it to 0PJAIMG.zip and place it in sd card) and this failed because of a problem with the zip signature.
4. Tried another custom rom (ViperOneM9_6.1.0) and the same situation (I see the rom logo but freezes and restarts again)
5. After flashing the 2nd rom, my TWRP stopped working (I see the logo of TWRP and freezes, restart)
6. I tried using fastboot commands to boot to recovery and nothing happens, tried flashing different TWRP versions and still freezes.
So at the moment the working modes are only download and bootloader.
Any ideas of where the problem is?
I'm pretty used to flashing custom roms but never had such problems before, so my knowledge doesn't go that far. Also if you need logs, please give me some instructions on how to get them. Thanks

Categories

Resources