My daughters phone, had older version of alliance rom, updated to build 26, ran fine for a few hours, now hangs at the first boot screen. when I enter tw recovery, it asked for a password. on the log(only thing i can see, cant get to main screen) i get many errors, unable to find partition size for... boot,recovery,modem,data. also unable to mount efs,cache,system,cache, cache.
ive tried odin back to stock, with and without pit files, never seen or heard anything about this before. any ideas where to start? thanks
odin will complete with success, but wont reboot, stuck at black note 2 screeen
I've tried about everything I could find on reverting back to stock, have one more stock image to try, downloading now, thank God I have fast service, only about 15 gigs so far today.
Related
I recently rooted my phone and everything was fine. This morning I installed a debloated rom http://forum.xda-developers.com/showthread.php?t=2296109 and It seemed to work but after I rebooted the phone just sits at a screen that says
Samsung
an unlocked icon
Custom
I can still get into Odin and TWRP but nothing I do seems to solve my problem. I have verified the MD5 of the image as well as trying to install a backup I made prior to flashing but the restore fails.
Does anyone know what I can do?
I should add that TWRP asks for a password when I load it but I never explicitly set one and also it seems to have trouble with the partition table.
Update: Solved maybe? I got this phone to boot but I am not sure what happened. I flashed a rom from TWRP several times and finally one took ... still would like info from someone who actually knows what is going on as I am not sure this wont happen again
Update: So it seems that every time I something happens and the drive or loader gets encrypted and it no longer boots. the "solution" is to do a full wipe then install a rom. This happens every time i reboot and I would really like a solution to this.
Last night I softbricked installing a rom. The device was being very weird and would not boot correctly. The device started showing the big GALAXY S4 splash screen instead of the usuall plain SAMSUNG sometimes says custom unlock sometimes not depending on the rom/kernal being used. Now even with Kernals that used to say SAMSUNG custom all it says is the big only GALAXY S4 splash screen. The device seems to take alot longer to get past this screen as well. Any suggestions on this??
Recovery would flash roms and device would boot once but would not boot after reset. SO F-it just Odin back to stock, root, recovery, done.
everything is working now except I still have the GALAXY S4 splash scren instead of the SAMSUNG and takes forever to boot/load past splash screen.
Is this stored in the kernal? Ive tired different kernals and all have stayed the same. I have completly ODIN back to stock wiped any and everything on this device.
QUESTION Summary::: Whats up with this splash screen VS the other one, why cant i get it to go back to the way it was before even after ODIN stock img, and why does it take longer to load and 1/2 the time not load at all.
Is there a BIOS that is not wiped... I think I broke it.
EDIT: Just sat on the SAMSUNG GALAXY S4 for 20 minutes before starting after fresh rom install... what a pain.
mrlaigle said:
Last night I softbricked installing a rom. The device was being very weird and would not boot correctly. The device started showing the big GALAXY S4 splash screen instead of the usuall plain SAMSUNG sometimes says custom unlock sometimes not depending on the rom/kernal being used. Now even with Kernals that used to say SAMSUNG custom all it says is the big only GALAXY S4 splash screen. The device seems to take alot longer to get past this screen as well. Any suggestions on this??
Recovery would flash roms and device would boot once but would not boot after reset. SO F-it just Odin back to stock, root, recovery, done.
everything is working now except I still have the GALAXY S4 splash scren instead of the SAMSUNG and takes forever to boot/load past splash screen.
Is this stored in the kernal? Ive tired different kernals and all have stayed the same. I have completly ODIN back to stock wiped any and everything on this device.
QUESTION Summary::: Whats up with this splash screen VS the other one, why cant i get it to go back to the way it was before even after ODIN stock img, and why does it take longer to load and 1/2 the time not load at all.
Is there a BIOS that is not wiped... I think I broke it.
EDIT: Just sat on the SAMSUNG GALAXY S4 for 20 minutes before starting after fresh rom install... what a pain.
Click to expand...
Click to collapse
yes the boot.img is held in the kernel....flash back to stock and reroot your device dont take any chances...hopefully you have some backups on an external sd card....this happened to me as well and i could only get to download mode so i flashed back to stock and rerooted my device everything is peachy....dont dont dont take any chances with this phone the security measures in this phone are insane and if you keep messing around with having the device "sometimes boot with custom samsung screen and sometimes not" there is something wrong with the partition....youre best bet is to flash stock and reroot....if you have a backup on an external sd card then youre set otherwise start over or you will have a $700 paper weight....let me know if you have any questions reverting back to stock or anything else good luck dude
Yeah I restored started from Odin stock last night. I thought that would take out anything that I flashed that caused the issue. But it didn't fix it.
I odin'ed back installed root recovery and still having issues where it will not boot after 2 or 3 resets. Hangs on thats galaxy s4 splash screen for more than 30 and never boots.
I would think that when it was odin'ed it would have over written the boot IMG and any thing else it might be but its not.
Sent from my SCH-I545 using Tapatalk 2
mrlaigle said:
Yeah I restored started from Odin stock last night. I thought that would take out anything that I flashed that caused the issue. But it didn't fix it.
I odin'ed back installed root recovery and still having issues where it will not boot after 2 or 3 resets. Hangs on thats galaxy s4 splash screen for more than 30 and never boots.
I would think that when it was odin'ed it would have over written the boot IMG and any thing else it might be but its not.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
when you did odin back to stock did you do a factory reset...NOT FROM RECOVERY....from settings>>backup and restore>>factory data reset? ......theres a couple of things to look for here....Odin back to stock and boot in the STOCK recovery....try wiping the cache and dalvik partitions...if they fail then the partitions are corrupted....boot normally and go to settings>>backup and restore>>factory data reset....try that...if that doesnt work then try a factory reset from the stock recovery...if all of that STILL doesnt work then the partitions are corrupted I would ask for a replacement device
Hi all, my Prime is stuck at the Asus splash screen out of nowhere! I looked through these q & a, googled, and tried a few simple options before i posted this.I was not trying to flash a new rom or anything like that. I actually hadn't used it for a few days because i'm moving, i charged it up, used it for a few hours, came back later to use it, and the browser froze. No big deal, it does that once every day or two. I hold the power button to restart it and now it just stays at the flash screen. I haven't tried to flash anything in so long i forgot for a bit how to access recovery or what exact rom im using. I can access recovery(twrp 2.2.2.1) and fastboot, i remember unlocking without a problem, and doing the nvflash backup on ics before i believe i flashed a stock jb rom(which i think i'm still on.) I was able to copy my pictures to an external sd card through twrp , and after that i tried to restore a backup, and wiping data and cache but still stuck at the splash screen. Any help would be greatly appreciated, right now im going to look through and see if i can find the stock jb rom, or lookup fastboot guides or something. Thanks for any help!
I flashed this rom and got it up and running. I love this forum! w00t http://forum.xda-developers.com/showthread.php?t=1927494
Hey all,
First, I just wanted to say that I have searched high and low for a solution to this already without much success, so I'm coming to you guys in sheer desperation; normally these forums and/or Google turn up the answer pretty quickly, but for once I am thoroughly stumped, so I'm coming to you sages for help.
tl;dr: After failing to unlock the bootloader through Odin (failure at sboot.bin), I re-installed a previously-working stock VRALJB ROM through Odin only to be met with a frozen Samsung boot logo and an inability to enter into recovery mode. I can get the phone into download mode, but that's it. Leaving the phone on for hours has given me no results, just the Samsung logo.
Background
Before I did anything last night that caused this current situation, the phone was running an unlocked/rooted (but otherwise stock) VRALJB ROM since I purchased it second-hand back in 2013. Actually, the bootloader may not have been unlocked as I had assumed, because what started all of this was me deciding it was time for a newer, better-optimized ROM. It was certainly rooted, as I had no issues running and granting root privileges to CWM and flashing the recovery loader. This was something I have done a dozen times for other people's phones (ah, hubris), so when everything appeared to be in order for me to boot into CWM's recovery mode, I did so, but was immediately greeted with Verizon's wonderfully-annoying Yellow Triangle-o-Death. I guess that's what I get for assuming the bootloader was unlocked.
I wasn't too worried; I had already backed up everything prior to attempting this, and I had Odin and my stock ROM ready to go should anything happen. So, I did exactly that: booted into download mode, connected the phone to Odin, and installed the stock VRALJB ROM. After about 6 minutes, the phone restarted and booted into a fresh, new stock version of Jelly Bean. There were no issues with the install, and the phone was working just as it should.
Where the problem started
So, now that I knew that the bootloader had never in fact been unlocked, I began searching down the process needed to unlock it so that I could then install a custom ROM. I began following the steps found on galaxynote2root.com's page for the SCH-I605, including downloading the "GalaxyNote2UnlockVerizon" archive will all the necessary tools (CASUAL, SuckItVerizon, etc).
**NOTE**: I know, now, that there were other, better options that existed and that I should have taken that path instead, but as it had been about a year since I had attempted any kind of flashing on my phone, I was rusty on the most current best-practices for unlocking the bootloader, and just went with the first tutorial I found that matched my phone model/firmware.
I loaded up Odin, included the option to re-partition with the included .pit file, placed the BootloaderBaseline2.tar.md5 file in the Bootloader section, and hit start. Everything was going great until Odin reached the infamous sboot.bin part of the bootloader; it failed at that moment, giving me the usual error message:
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
"Okay, no biggie," I thought to myself. I must have done something wrong, or maybe the bootloader baseline file was corrupt.
Assuming I had just soft-bricked my phone, I went ahead and reset Odin, loaded up the sch-i605-16gb.pit file, the stock VRALBJ ROM I had just successfully installed 20 minutes earlier, told Odin to erase everything, and hit start.
Odin had no problem re-installing the ROM. It went through the entire process again in about 7 minutes, and I was happy to see the Samsung logo pop up at the end. Only problem was, though, that the Samsung logo stayed there.
"Damn it," I thought. So, I let it sit for a while, thinking that maybe something was happening in the background, but after 10 minutes, the logo was still there. Obviously, something had gone wrong in the install, so I decided I would boot into recovery mode, clear the cache, and to a factory restore now that the ROM was "successfully" installed.
Except I can't get into recovery mode. When I do the usual Volume Up-Home Button-Power Button combo, the Samsung logo appears as it should, but stops right there; it will not enter recovery mode.
Okay, so I can't fix it that way. I'll just go ahead and re-install the ROM through Odin again. After all, I had just used this exact same .md5 ROM file only an hour earlier and the phone booted fully and I had zero issues; so, I knew that the ROM file itself wasn't corrupted.
So I tried re-installing the ROM again through Odin, but got the same result: Samsung logo, with no ability to enter recovery. I tried again and again, and even went and downloaded another copy of the stock VRALBJ ROM in the hopes that maybe something was wrong with the one I was using.
Nope. Same results.
So now my phone is bricked, and I'm at a loss as to how to get it back. I have yet to try newer ROMs, only because I don't want to update to a newer stock version and lose the ability to unlock the bootloader; after all, the entire point behind last night's excursion into madness was so that I could load a custom ROM.
That said, if installing a newer stock ROM from Samsung/Verizon is the only way of fixing this, I will do it, but I was hoping there was another way that may allow me to stay on the VRALBJ ROM as a stepping-stone to another custom ROM.
I appreciate any help I can get, and I apologize for the wall of text, but I know how important background information is when trying to diagnose and fix these kind of problems, so I assumed you guys wouldn't mind
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.