I have been flashing roms for at least a year now with no problems. For some reason, recently I can flash some roms fine and some roms only boot loop or boot freeze. I am currently using Bamf SoaB v1.0. when I tried to flash iBolt v0.90 the most I can get is to the MUIU boot screen and it either boot loops or freezes. I can boot OMFG roms and others fine as well and have ran into other roms that boot loop and freeze also. I have even had an issue with recovery boot looping in the middle of trying to load a rom or wipe. I have tried different Recoveries with no luck. I am wiping everything every time I flash. I even returned to stock Ruu with S-on and rerooted and no luck. Does anyone have any ideas?
Did you check the md5 of the file? Maybe it was a bad download
Update to newest CWM and use newest recovery or use 3.0.2.5 that was always a great one for flashing with no issue or boot loops.
If I helped you in any way please use the thank you button.
1) you aren't wiping (probably not the case since you've done this b4)
2) bad/corrupt rom download (check md5 as suggested)
3) recovery borked causing failures (reflash newest recovery)
4) recovery outdated and those roms require an updated version (reflash newest recovery)
5) your phone doesn't like the kernel and/or default clock speeds of the rom you are flashing (use different rom or flash a different kernel immediately after the rom *YMMV*)
.
.
.
15) hardware failure (get new phone) *not really failure, just not living up to potential*
All that is meant by the dots is to indicate that there are a few other things to check before settling on it being a hw problem but I can't think of any right now.
After eliminating the likely causes described above, you may want to check your recovery log immediately after you flash. Export the log to the sd card, then examine the log file from your computer.
I am a frequent rom flasher, and I have had issues with bad nand blocks only being a problem to me with select roms and not others. Little bit of weirdness.
I have not received my thunderbolt yet, so I am only assuming that htc designed the internal and sd memory in your phone in a similar manner to my sexy nexy. Please correct me if I am wrong!
Sent from my Nexus One using xda premium
Thanks for all the help. The issue seemed to be a kernal problem. At least with ibolt it was. Sad thing after all that work and time and losing everything on my SD I ended up not caring much for the rom. lol At least I know what to try if the problem happens on other roms.
Related
Dear all
i have a droid eris with 1.5 firmware i root it and did a backup withe clock work mode
the i tried to install a cyanogenmod custom rom it went fine then when i boot my phone it stuck on the logo screen so i turned it off and went to the recovery mode and i try to do a restore for my backup what i get is the following message
"erasing boot before restore...
restoring boot image...
Error while flashing boot image "
and return me to previous selection
and then i tried to download a custom rom and it goes with the following error
assert failed: write_raw_image("/tmp/boot.img", "boot"
so my phone is stuck in the logo screen can you help me please.
Did you get the rom from xda? Also, you should try to flash different rom's that contain Cyanogen (ex: GSB). I may not know much but hope this helped.
P.S I would incite you to Wipe data/cache before flashing a rom; from my personal perspective, I think when you flash a rom and don't wipe, it piles up; and well the phone may not work as expected(ex: glitches). Good luck
i tried but nothing work i don't know what to do i have a guy who has a box to do reflash is it going to work shall i try it
Find and flash an RUU, then install amon ra recovery. Clockwork rom cause trouble on Eris.
Sent from my Galaxy Nexus using xda premium
I may not very adept in these things, however, there is a rom that restores everything back to OTA 2.1 from my knowledge. I admonish you to use that, I presume that it might fix it. In such a grievous state; that would perhaps be an essential option to you.
Sent from my ERIS using xda premium
Find and flash an RUU, then install amon ra recovery. Clockwork rom cause trouble on Eris.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Good thing you pointed this out, as I am too discordant with the use of ClockworkMod in the Eris; as it has proved to promote some minor complications when running.
Sent from my ERIS using xda premium
I will try it and letnu know
ramses77 said:
I will try it and letnu know
Click to expand...
Click to collapse
One more thing, from what I am aware of; there is an application on the Market that actually installs a custom recovery. It's issued as HTC Eris One Click, look it up, I would admonish you to use it; it works more efficiently on the Eris than ClockwordMod does.
Hope this actually benefits
If his phone won't boot an app won't do any good..
There is an ruu or pb img file with an unlocked boot loader. Or try unrevoked to unlock the boot loader. Then you can fast boot flash your recovery.
Its been a while since I retired my Eris, but I'm sure there are still tutorials out there.
Google search is your friend.
Good luck.
Sent from my Galaxy Nexus using xda premium
As far as I know, an Eris flashed with Clockwork as the default recovery that tries to flash an RUU is a quick method to leaving yourself with a brick.
If the OP can restart in Recovery (hold down VolUp while starting the phone), then I would try a wipe data/factory reset. Also, if you can start in Recovery, flash the Flashback_21 ROM (which restores the stock recovery and stock Eris 2.1 software as of the March 2011 OTA) and then re-root with the 1-click Eris root app in the market. Leaving Clockwork as the default Recovery has tended to be a recipe for disaster.
Flashback is here; the non-radio version should be fine: http://forum.xda-developers.com/showthread.php?t=792026
I will try and hope it works cause all the previous tried did not but thanks to you all anyway
There may be a solution: see this thread: http://forum.xda-developers.com/showthread.php?p=22725909#post22725909
ramses77 said:
Dear all
i have a droid eris with 1.5 firmware i root it and did a backup withe clock work mode
the i tried to install a cyanogenmod custom rom it went fine then when i boot my phone it stuck on the logo screen so i turned it off and went to the recovery mode and i try to do a restore for my backup what i get is the following message
"erasing boot before restore...
restoring boot image...
Error while flashing boot image "
and return me to previous selection
and then i tried to download a custom rom and it goes with the following error
assert failed: write_raw_image("/tmp/boot.img", "boot"
so my phone is stuck in the logo screen can you help me please.
Click to expand...
Click to collapse
The two most likely scenarios that you are encountering are one of these two:
(1) Lack of sufficient good NAND memory pages in the "boot" partition to be able to write the boot image due to a few bad pages. (A small number of bad memory pages can be a normal condition)
(2) An extreme lack of good NAND memory pages in the "boot" partition caused by a mysterious and not well-understood phenomenon when using CWM recovery on Eris handsets.
The first thing I would try is flashing an Eris ROM with relatively smaller boot partition utilization to see if it succeeds. For instance, the "March2011 OTA Reference" ROM - it only needs about 86.3% of the space in the boot partition. If it succeeds, then your issue is likely syndrome (1). If it also fails due to a failure writing the boot partition, then it is somewhat more likely you have syndrome (2). There is a solution available for that problem; but let's first find out where your problem lies.
Here's some examples sizes of the boot images sizes of various ROMs:
Evervolv-Eligo-2.1.0b2: 2,478,080 (94.5% of full)
xtrSENSE5.0.1: 2,265,088 bytes (86.41% of full)
March2011_OTA_ReferenceROM_v1: 2,260,992 (86.25% of full)
As strange as it may seem, it is possible to lose 10% of the space available in the NAND boot partition if only two individual (2048-byte) pages go bad - because pages are lumped together into "eraseblocks" of 64 pages (= 128 kB), and there are only 20 "eraseblocks" in the Eris boot partition. (It turns out that when you lose a single Nand memory basic page of 2048 bytes, you effectively lose the entire eraseblock that it lives in - 128 kB !)
So - while I realize your end goal is not some other ROM - we need to find out what the nature of the problem is, and the fastest way to do that is a test flash. ( You'll have to figure out how to get the ROM onto your SD card - card reader, MS/USB toggle in Amon_RA recovery, or via adb with CWM running on the phone. )
Some of the older Eris ROMs also have small boot partition utiliization - unfortunately nearly all of the early Eris dev ROMs are now missing from the internet due to various sites going offline. If you have an early ROM file lying around, you can unpack it (or inspect it with 7-zip) to find out how big the "boot.img" file is. If it is small enough, feel free to use that as a flash test.
bftb0
Hi,
Issue: After system loads (I get to see launcher/sim unlock screen), couple of seconds later streak reboots. At the same time, leds swich off, than flash and reboot starts.
What I tried (almost all combinations of below points):
restore to factory settings
different roms: DSC v2.3, PCM7-Streak, Mokee OS, Longhorn 2.9.3, some ICS rom
custom recovery images: ClockworkMod 6.0.1.2, StreakMod 0.3.2.8
stock roms with corresponding recovery 366, 360, 369, 406, 407
user QDL tool from streakflash.zip/repairtool.zip do recover to Baseband GAUSB1A130500
booting without sim/SD cards
Things to note:
For flashing I have followed the procedure to wipe data, cache, dalvik, fix permissions, dell factory reset.
In the past I had not issues flashing DSC, PCM7-Streak and other roms.
When booting into service mode? (camera+power button, *#301# code) phone passed all tests (including Internal SD card).
Tests performed with two original dell batteries (one bought 8 months ago, barely used).
Batteries fully charged.
Same issue experienced with custom and stock roms.
The issue started after flashing one of the roms (DSC v2.0 probably).
To be honest I run out of ideas. Please tell me if I missed something?
You didn't say which ROM you were currently running. In any event, it doesn't appear you missed anything. I believe you should try flashing the ROM you're using again. It's possible you got a bad flash, in which case one of the files got corrupted on transfer.
Strephon Alkhalikoi said:
You didn't say which ROM you were currently running. In any event, it doesn't appear you missed anything. I believe you should try flashing the ROM you're using again. It's possible you got a bad flash, in which case one of the files got corrupted on transfer.
Click to expand...
Click to collapse
Thanks for advise.
I have tried starting with with 305 from repairtool.zip working my way up through 360, softbank and Olleh. Stopping at each step and flashing ClockworkMod + DSC. Same applies to any updates to each of mentioned custom roms.
The only thing that I know I could have checked better is the internal SD, just a moment ago found a neat way to get to the Internal SD - http://youtu.be/6w4AbtIGp8A. I might give it a try.
I could use some advice on any options I have for trying to salvage this Rezound. Here is what I know:
The Symptoms:
-Was completely stock and actively used phone
-Charging port began misbehaving. I believe it may be loose/damaged. It will only charge reliably on one particular USB cable (an Amazon Basics, but only one of my dozen or so of those)
-Started randomly rebooting
-Did a factory reset, seemed to help for a while, then it started rebooting again
-It started getting stuck in a bootloop. HTC screen up ~2s -> black ~0.2s -> HTC screen up ~28s -> black ~5s -> repeat. Does this for a variable amount of time, sometimes minutes, sometimes hours before it will actually boot all the way into the OS
-If it does boot, it usually does not last long before it reboots and will typically get stuck again
The Facts:
-I can into bootloader with no issues
-Because I can get into bootloader, I went ahead and unlocked and flashed TWRP 2.6.3.0
-I can get into TWRP and use all of it's functions reliably
-I decided to try wiping data and cache then system several times, flashing a custom ROM (Global_OTA_RED_DESENSED-v1.0) in TWRP and then flashed boot.img with fastboot, but the new ROM has the same issue. In fact I've yet to boot all the way into the ROM
-Does the same thing with the SD card and SIM card removed
My Guesses:
Based on the fact that it is rock solid in the bootloader and in recovery, I thought that it was possibly corruption on system or boot, which is why I tried to install a custom ROM. Now I'm leaning towards bad memory, either where system or boot reside, possibly data or even RAM, perhaps caused by electrical damage from the charge port issues. I just don't understand why I've not seen any sort of read/write errors while doing anything with fastboot or recovery.
At this point I don't know what to do beyond throwing it out. If anyone has any fresh ideas for salvaging this thing, I'd appreciate it.
If not, any ideas for replacing are also appreciated. A new phone isn't really in the budget at the moment, particularly because I desperately want to get away from Verizon (most likely will lose unlimited data if we I start swapping and don't really have $600-$700 to throw around at the moment. I have 4 lines to move and the Rezound line is on contract, so I'm sort of feeling the rock one side and a hard place on the other.
Thanks in advance, folks!
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
acejavelin said:
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
Click to expand...
Click to collapse
Thanks for the suggestion. I had let the phone sit turned off all afternoon to charge and tried this after work. I grabbed Amon Ra from http://forum.xda-developers.com/showthread.php?p=37362226, made sure to wipe boot in excess and installed the ROM you linked. It booted up on the first try unlike the last ROM, and I've been able to load some things on it and delete some bloat for a bit with no reboots. I've even powered off and went back into recovery to do a backup, and had a successful reboot afterwards. I don't know if it was wiping boot that did it, but I hope it holds. I'll keep you posted, and either way, thanks again.
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
"Haus" said:
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
Click to expand...
Click to collapse
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
acejavelin said:
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
Click to expand...
Click to collapse
I'm still on the stock ROM. Unfortunately it quit booting again.
"Haus" said:
I'm still on the stock ROM. Unfortunately it quit booting again.
Click to expand...
Click to collapse
Hmm... Honestly looking like a hardware issue... Sorry bro
Sent from my Nexus 4 using Tapatalk
Ok...so flashing and rooting is not new to me. However I may have found myself in a pickle. I have an S3 that I gave to my wife. She did not like the CM nightly that I had on it. So I downloaded the original stock rom that came with it and flashed it with odin. Everything seemed fine, but on reboot, it loops. Can't get into recovery or download mode. Any Ideas. And yes....I have searched and thus far, I have found nothing that matches my scenario. I was reading somewhere where there was a sticky in the general forum about this stuff, but did not see anything.
Could use some help. I don't mind buying the wife a new phone....may do that anyway. But I have one more daughter that I could give this to if I could get it fixed.
Peace
When you first flashed it with oden, did you flash an insecure kernel (flash recovery)?
If so, do so, then enter recovery and select factory reset & cache clean, so it may boot.
It generally happens when data is left over from a different/incompatible kernel.
http://true-android.blogspot.co.nz/2014/01/install-clockworkmod-recovery-6044-on.html
The first time was with CM and everything was fine. I used it for around a year with CM. I did a few updates from them. Then when i used odin to flash back to original I did NOT flash a kernel separately, if that is what you are asking. The kernel came with the rom. Perhaps I don't follow. At any rate I can't do anything atm because I can't get into recovery or download modes.
augustorm said:
The first time was with CM and everything was fine. I used it for around a year with CM. I did a few updates from them. Then when i used odin to flash back to original I did NOT flash a kernel separately, if that is what you are asking. The kernel came with the rom. Perhaps I don't follow. At any rate I can't do anything atm because I can't get into recovery or download modes.
Click to expand...
Click to collapse
To clarify, cleaning (factory reset & cache) is for the kernel, all roms for this model come with a kernel. But they are different. A CM kernel for 4.4 is not going to downgrade well to a stock 4.3 (example version) kernel, without doing this. The boot loop is a pretty common result of not doing this, happened many times when upgrading (depending on how extensive the update).
So how do I get into tje phone without being able to go into recovery or download modes?
Sent from my SM-N900T using Tapatalk
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
firstrival said:
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
Click to expand...
Click to collapse
Dont try flashing a custom ROM on to the phone. Try flash the stock ROM through the lastest odin with the lastest drivers and let me know how that works out for ya. Unless that wipes the phone ( havent used it in quite some time) then I have no idea man.
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
firstrival said:
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
Click to expand...
Click to collapse
I'm not sure maybe want to ask someone else I'm not as experienced as some people on here. Sorry man goodluck
I hope someone can help you out. I would say your cache partition somehow got renamed but I'm not sure if thats possible and if so how to fix it. Maybe someone with ADB knowledge can help?
Also what TWRP were you trying to install? I've had problems when I tried to flash older versions
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
kireflow90 said:
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
Click to expand...
Click to collapse
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
firstrival said:
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
Click to expand...
Click to collapse
Thanks for the quick reply. Its a shame to hear that it didn't work
How did you come to this? as to me it seems the partions have be modified hence why giving those errors I seen similar errors to when users change cache sizes which tends to brick device or from using incorrect pit files.
You never be able to recover data from flashing Odin may be slim chance by custom Rom thru recovery if was a bkup of original system and not selecting data your old data may conflict causing either bootloop or basically stuck on splash screen.
If you was ever able to best way to pull data from device would be thru adb may have a chance.
This phone belongs to a friend of a friend. They said they brought it to T-Mo because it hung up during boot. The store worked on it for a few minutes, but couldn't get it to boot up either. When I tried to go into recovery, they said the store already went into that screen too. They have since bought a new phone, but would like to get the photos off it if possible. They never had an SD card so it's still on the device.
At the moment, I can just go into download mode. I was hoping to flash a custom recovery so I might possibly be able to ADB from there since it won't load the stock recovery.
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
fulgorevinnie said:
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
Click to expand...
Click to collapse
ok so i read all that you have done which is basically everything i would of suggested to you other then could it be the battery may be faulty just random thought noticed you never mentioned trying kies you may have a chance with it beening detected as i see you can enter download mode so that help with odin also kies also have you tried firmware from here sam mobile here T399 or T399N OH2 lastest for tmo and OH3 for metro.
Try to only flash that thru odin i use 3.07 or 3.09 only difference is the pda button changes to AP .works perfect for me so i suggest it then returning back to stock recovery/firmware if it boots then awesome. then return to TWRP 2.8.4.0 beening lastest for this device also needed for CM12 also my projects for device current and future.
when using odin make sure that only “Auto Reboot” and “F. Reset Time” options are selected.
also just note when going into twrp release buttons as soon as you see logo otherwise it will continue to boot thru well happens to me when daydreaming lol.
also if your seeing this adb get-state returns "unknown" i believe installing kies may install the drivers for detection im not postive on that but im sure it something to do with missing the adb driver for device maybe another dev can confirm this ?
hopefully this may be of some help i keep on thread to see how the outcome goes
Thanks for the reply DJBoxer!
Regarding the battery it's a new one and I can confirm it's not a battery problem considering that the phone can stay in download mode and unplugged from any power source for very long times without turning off/rebooting and it never failed to keep the charge so far. I also tried with the old battery and the phone behaves exactly the same way.
I used 3 different versions of Odin (1.87, 3.07 and 3.09) with only “Auto Reboot” and “F. Reset Time” options selected and every time I got the PASS message even though the phone keeps rebooting after the first reboot once the procedure is terminated.
To clarify one thing : when I said "it shows the TWRP splash screen but it reboots right after and this happened even after I flashed CWM" I meant to point out that it looks odd to see the TWRP splash screen (even for just a few seconds) after I just flashed CWM and that makes me think that I'm really not flashing anything here...
Thank you very much for taking the time of posting the links and I actually didn't try with that latest OH2 version.
I am downloading it right now (it takes a while from sammobile) and I will keep you posted on the outcome.
I will try to flash it via Odin and I'll also try the latest version mentioned on sammobile (Odin3_v3.10.7).
Regarding Kies I wasn't able to have it recognize the phone. I may be missing something but I tried updating drivers and going through all the guided procedures with no luck... If you say it should recognize the phone right away while in download mode then something is amiss.
Could you please confirm that I should also be able to use adb commands with the phone connected via USB in download mode? Cause that doesn't look like the case either...
Thank you again and I'll give updates here about my last attempts.
Sorry for the late reply...
Nothing changed by the way...
I am about to send the phone back to the seller who told me they'll try to fix it. Let's see how it goes.