Related
So I attempted to install Cyanogen mod on my phone, and when I rebooted my phone all I get is this screen....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it bricked ?
try to get into recovery
Sent from my GT-I8150 using Tapatalk
Do full wipe via Cwm, and then try to reflash CM9
Sent from my GT-I8150 using xda premium
I'm sorry, I'm a total noob with this, I did a reflash but same thing
Agust1337 said:
I'm sorry, I'm a total noob with this, I did a reflash but same thing
Click to expand...
Click to collapse
Yeah try make full wipe then reflash.
Sent from my GT-I8150 using xda premium
First go into Recovery. Then select the option "wipe data/factory reset" and go down until yes then press the home button once and reboot your phone
Sent from my GT-I8150 using Tapatalk
I did a full wipe and I still get that screen
Did you refer to this prior to flashing http://forum.xda-developers.com/showthread.php?t=1576874 ?
Sent from my GT-I8150 using xda premium
I used that mod yes
Well I didnt flash cm9 my self. My suggestion post your problem here
http://forum.xda-developers.com/showthread.php?t=1598056 and browse the thread as well as there might someone out there with same encounter as yours.
Sent from my GT-I8150 using xda premium
Try to do this bro
1. get into CWM recovery
2. Wipe data/factory reset
3. Wipe Cache partition
4. go to Advance/Wipe Dalvik Cache/Wipe Battery Stats
5. go to Mount/Storage/Format System/Format Cache/Format data
make sure u do it twice, i did the full wipe when i flashing MIUI v4 Alpha 4 Rom by AliDSD, and no problem at all
Uhm, I dont have CWM Recovery, it says Android System Recovery <3e> :s
Agust1337 said:
Uhm, I dont have CWM Recovery, it says Android System Recovery <3e> :s
Click to expand...
Click to collapse
so, u flash cm9 with stock recovery ??
u have to go to this thread here
Thats soft bricked, happened to me just a few days ago..
i suggest that if you can't make their suggestions work then flash a stock firmware again, here http://forum.xda-developers.com/showthread.php?t=1467128..
then root your phone, http://forum.xda-developers.com/showthread.php?t=1317394
after you root, tick the usb debugging mode to enable it,
then get CWM from here http://forum.xda-developers.com/showthread.php?t=1446593, and from here http://forum.xda-developers.com/showthread.php?t=1576874 it says that you should wipe all first before/after you flash a new rom..
Hello kemaro30,
I can't seem to get it into USB Debugging Mode, I think it's because I can't even get into the OS.
Plus, I suck at reading guides :/
Agust1337 said:
Hello kemaro30,
I can't seem to get it into USB Debugging Mode, I think it's because I can't even get into the OS.
Plus, I suck at reading guides :/
Click to expand...
Click to collapse
Settings>applications>development>usb debugging.
Sent from my GT-I8150 using xda premium
Hi man...
You do this on other phone??
http://forum.xda-developers.com/showthread.php?p=25422300
1. Did you follow the instructions in the CM9 Dev thread?
2. Did you first flash CWM5, it is the first item in the instructions in that thread.
3. If not, you can still flash CWM5, either by ODIN or adb.
4. You will have to read the instructions as to how, they are all in the forum.
5. No-one else can do it for you, you have the phone, just don't skip any essential steps.
6. I know you think your phone is bricked, but it does not seem so from your description.
7. Not sure how you got the CM9 splash screen by flashing through stock recovery?? Maybe you can explain how exactly you are flashing CM9??
Sent from my GT-I8150 using Tapatalk
Well I cant get into my phone. It only loops through the boot over and over again.
I did exactly the steps, but I did not use cwm5. Maybe thats why its doing it...
Agust1337 said:
Well I cant get into my phone. It only loops through the boot over and over again.
I did exactly the steps, but I did not use cwm5. Maybe thats why its doing it...
Click to expand...
Click to collapse
well, that's the problem... if you want to install CM9, you should install CWM recovery first...
this is what you should do to resolve it:
1. turn on your phone into download mode
2. connect your phone to your PC, then flash CWM recovery through ODIN
3. after finished flashing CWM recovery, turn off your phone, then turn on your phone into recovery mode to enter CWM recovery
4. full wipe your phone in CWM recovery (wipe data, cache, dalvik cache)
5. flash CM9 in CWM recovery
next time, if you want flash ROMs into your phone, make sure you follow every instructions and DO NOT EVER SKIP single step of the detailed instructions...
Sent from my GT-I8150 using xda premium
Agust1337 said:
Hello kemaro30,
I can't seem to get it into USB Debugging Mode, I think it's because I can't even get into the OS.
Plus, I suck at reading guides :/
Click to expand...
Click to collapse
yes you can't ofcourse, you must flash a rom first then after that when you get into debugging mode. the guide on flashing is on the link i provided, just go to download mode and if you can got to download mode everything would be fine as they said, DO NOT SKIP any steps, all links are provided from my first post from flashing, rooting, installing CWM and flashing the CM9 rom. hope this helps.
Hi all!!
Just before Christmas, my Rooted One X decided it had a OTA update it wanted to do, and tried to install said update.
But once it turned off to reboot, it no longer boots!
It just stays on the HTC Splash screen till the battery dies
I can get it to the Bootloader, but that's about it, on the boot loader This is what it looks like (im unsure if the top messages are normal or not!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I try to go to recovery, it just shows a pic of Android and a loading bar for a second or two, then reboots and loops on the HTC screen again, and the exact same thing when I try to 'Factory Reset'
Also, it will NOT power off, you can hold the power button, and it will do off, but instantly will try and boot back up
Any help would be greatly appreciated, Even if it means going back to a stock rom.
If you need any more info, please feel free to ask and ill try my best to answer.
Cheers
Keith
I had similar problems, I reflashed cwm and erased cache through fast boot erase cache, at least twice.
This finally allowed me to boot into recovery and reflashed another rom (with the proper boot.img flashed of course).
It's very important that you erase cache
Sent from my EndeavorU using Tapatalk 2
drivenby said:
I had similar problems, I reflashed cwm and erased cache through fast boot erase cache, at least twice.
This finally allowed me to boot into recovery and reflashed another rom (with the proper boot.img flashed of course).
It's very important that you erase cache
Sent from my EndeavorU using Tapatalk 2
Click to expand...
Click to collapse
Hi, any chance you could talk me through what I need to do??
Im a noob with these phones, im use to my old school HTC Hero were flashing roms was a little bit simpler lmao
Never put a rom on this at all yet, so I have no idea about boot.img's etc...
Im currently downloading the Android SDK etc as im guessing this will be needed...
:EDIT:
Ok, I managed to do what you said, but still cant boot into recovery :s
I flashed CWM and cleared the cashe but still nothing, damnnnn
Have you tried "fastboot erase cache" before going to recovery ? Maybe it helps
Sent from my HTC One X using Tapatalk 2
vaykossil said:
Have you tried "fastboot erase cache" before going to recovery ? Maybe it helps
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I dont seem to have this option matey! :/
:EDIT:
Never mind matey, I get what you ment and I have tried it not with zero success :s
I have reflashed the CWM and erased the cashe using fastboot, but still nothing
Try fastboot boot (nameofcwm).img
Sent from my faster than SGS3 HOX.
XxVcVxX said:
Try fastboot boot (nameofcwm).img
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
Thanks alot matey!!
This worked and I managed to recover from one of my backups
Glad it worked, there's a thanks button :hint:
Sent from my faster than SGS3 HOX.
XxVcVxX said:
Glad it worked, there's a thanks button :hint:
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
ohhhh yeah, there you go matey
Bit skeptical about the update it keeps telling me about now! haha
I recoverd back to my old 4.0.4 version of android, but SuperSU no longer works so im guessing its unrooted some how?
Now its telling me there is an update to 4.1.1 (Saftware update 3.14.401.27) ....
Lets see if its bricks again! lmao
:EDIT:
ooookayyyy, that didnt want to install at all... hmmmm It downloaded, then went to recovery to install and just errors out, something about internal storage or something... will get the proper message in a min or so!
Anyone reccommend a good Rom to flash? haha
Also, how do I go about flashing the boot.img that im guessing will be needed with a rom?
Keefo said:
ohhhh yeah, there you go matey
Bit skeptical about the update it keeps telling me about now! haha
I recoverd back to my old 4.0.4 version of android, but SuperSU no longer works so im guessing its unrooted some how?
Now its telling me there is an update to 4.1.1 (Saftware update 3.14.401.27) ....
Lets see if its bricks again! lmao
:EDIT:
ooookayyyy, that didnt want to install at all... hmmmm It downloaded, then went to recovery to install and just errors out, something about internal storage or something... will get the proper message in a min or so!
Anyone reccommend a good Rom to flash? haha
Also, how do I go about flashing the boot.img that im guessing will be needed with a rom?
Click to expand...
Click to collapse
You need stock recovery to update via OTA, or you could relock the phone and run an RUU of the newest version.
Sent from my HTC One X using xda app-developers app
mibikin said:
You need stock recovery to update via OTA, or you could relock the phone and run an RUU of the newest version.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Ahhhh cheers, makes sense really haha
Im looking at installing the Android Revolution HD 18.0 Rom, but im a little confused on what im needing to do to get it all working correctly..
As I said above, im use to just sticking a single zip on the SD and installing back on my old HTC Hero haha
Also, is there any way of mounting the SD card without having to boot the phone up?...
I know you cant do it in the Clockwork recovery sadly!! :s
You can do it in CWM or TWRP. Just click mounts and storage and then mount USB storage. I think what you should do is run an RUU and then unlock boot loader and flash ARHD 18 like any other ROM.
Sent from my Transformer Pad TF300T using xda app-developers app
mibikin said:
You can do it in CWM or TWRP. Just click mounts and storage and then mount USB storage. I think what you should do is run an RUU and then unlock boot loader and flash ARHD 18 like any other ROM.
Sent from my Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Iv tried that, but it does not work, and I have read in another thread that this didn't work on CWM? Maybe im wrong and my phone has another fault! haha
I just get and error saying E:Unable to open ums lunfile (no such file or directory)
The open ums lumfile error is because of an older custom recovery you must update to a newer recovery ....try this one
http://db.tt/Krlm4dPs
:thumbup:
But i cant find in the thread that you updated the hboot already ?
Otherwise you can use this ruu
http://www.htcruu.com/securekey.php...Radio_5.1204.162.29_release_302015_signed.exe
Relock the bootloader with fastboot command
Fastboot oem lock
And then run the ruu with admin rights !
It will give you the latest hboot and stock JB software
Edit : its best to get to the point, are you on the stock rom, stock kernel,custom recovery
Flash this recovery back
http://db.tt/U5CK4noo
Put the phone fastboot usb mode and copy the file to the fastboot folder (rename it to recovery.img)
Then the fastboot command
Fastboot erase cache
Fastboot flash recovery recovery.img
Fastboot erase cache
Reboot the phone and do the software update again.
Try flashing back stock recovery, if it still doesn't install then try the ruu.
Sent from my faster than SGS3 HOX.
I know this is a common problem but my Galaxy Note 2 is stuck on the boot screen and keeps restarting like a loop . I would do a factory reset but I don't have a custom recovery and I can't even get pass the boot logo .
Is there any way to factory reset it without custom recovery ? Or solve this problem any other way ? Thanks in advance , cheers
You can factory reset from stock recovery also ....
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Epix4G said:
You can factory reset from stock recovery also ....
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Oh yeah , I forgot to mention , I don't know why , when I boot into recovery , it doesn't have the Wipe Data and Wipe cache etc options . It only has factory tests .
fireboylolz said:
Oh yeah , I forgot to mention , I don't know why , when I boot into recovery , it doesn't have the Wipe Data and Wipe cache etc options . It only has factory tests .
Click to expand...
Click to collapse
I would not recommend this but it worked for me after I had the same issue after a bad flash.
Prerequisite is a backup image made by TWRP.
To fix used GNTK to have ODIN load an insecure image with TWRP. Still boot looped. Entered TWRP and Wiped everything (did not leave or reboot.) loaded the backup stock image made with TWRP initially from SD.
darksoul21 said:
I would not recommend this but it worked for me after I had the same issue after a bad flash.
Prerequisite is a backup image made by TWRP.
To fix used GNTK to have ODIN load an insecure image with TWRP. Still boot looped. Entered TWRP and Wiped everything (did not leave or reboot.) loaded the backup stock image made with TWRP initially from SD.
Click to expand...
Click to collapse
Urmm , can I get a step by step guide ? I'm kind of lost .
Apologies for missing/mangled links; I'm not allowed to post any.
Download one of garwynn's ma7 Odin packages here:
sxtpdevelopers.com/showthread.php?t=154
I'd suggest the one labeled "Rooted - KEEPS user data" if you do not have a backup.
Use the one labeled "Rooted- ERASES user data" if you do, or if you don't care about your memory/data.
Here's the procedure:
On the phone: Turn it off (remove the battery if you need to).
Hold volume down, the big button on front, and the power button (stick the battery back in if it's out)
The phone will immediately say "Warning!! A custom OS will melt your phone, eat your dog, etc etc".
Let go of all the buttons and then press Volume up.
The "ODIN MODE" screen will come up (it has a big green picture of the Android guy and says "ODIN MODE" at the top left).
Unplug the phone if it's connected to anything.
Put the .exe file you downloaded above on a Windows PC. Connect the phone to the Windows machine with a good USB cable (even new ones can be bad; cheap cables made for battery charging don't always have all the wires that a USB cable should).
On the Windows PC, go to samsung.com/us/support/owners/product/SPH-L900#
Hit "Manuals & Downloads, then the "Software" sub-tab, and click "Download File EXE". (The only file available for download is the USB driver.)
Install the USB driver.
Connect the phone, and make sure the PC doesn't complain that it doesn't have a driver for the device. Disconnect the phone.
Launch the .exe you downloaded from garwynn's recovery ROM post.
Connect the phone. You should get a message like, "<ID:0/009> Added!!" in the Odin window.
Push "Start".
Poof, a stock or near-stock MA7 phone, with or without a user data wipe, depending which version you downloaded.
Stuck in bootloop of some sort
Hi Guys. I am in serious problems. My note 2 kept on going off as much as 5-9 times a day. I decided to flash a new stock ROM. I did this three with three different stock ROM times with similar problem of switching off. On the last time however, my phone went on a bootloop. It keeps on showing "Samsung Galaxy Note 2 N7100" then the android robot(like the one which appears when the phone is doing a factory reset or update, then back to "Samsung Galaxy Note 2 N7100"....
1. I have tried restoring the phone with ODIN unsuccessfully.
2. Kies does not work at all(in fact Kies does not even connect to the phone. When i try using Emergency Firmware Recovery it states "Please enter recovery code from previous PC.." I had previously taken it to the Samsung service center here but i am not sure if Kies is a recovery process they tried using.
3. The Samsung Service Center here in Kenya cannot restore it either.
4. I cannot access the recovery menu at all: the phone only boot loops when i press the recovery combo.
5. I can only access the download mode which i have tried flashing different stock ROM unsuccesfully.
6. Currently the phone bootloops and has even refused to communcate with the computer(not recognised-maybe something related to the USB drivers)
Anyway, i love this phone greatly and i have heavily invested in it. I would not love to lose it. I heard of people losing IMEI because of ROM flashes- might this be something that affected me?
PLEASE HELP!
kennethwendo said:
Hi Guys. I am in serious problems. My note 2 kept on going off as much as 5-9 times a day. I decided to flash a new stock ROM. I did this three with three different stock ROM times with similar problem of switching off. On the last time however, my phone went on a bootloop. It keeps on showing "Samsung Galaxy Note 2 N7100" then the android robot(like the one which appears when the phone is doing a factory reset or update, then back to "Samsung Galaxy Note 2 N7100"....
1. I have tried restoring the phone with ODIN unsuccessfully.
2. Kies does not work at all(in fact Kies does not even connect to the phone. When i try using Emergency Firmware Recovery it states "Please enter recovery code from previous PC.." I had previously taken it to the Samsung service center here but i am not sure if Kies is a recovery process they tried using.
3. The Samsung Service Center here in Kenya cannot restore it either.
4. I cannot access the recovery menu at all: the phone only boot loops when i press the recovery combo.
5. I can only access the download mode which i have tried flashing different stock ROM unsuccesfully.
6. Currently the phone bootloops and has even refused to communcate with the computer(not recognised-maybe something related to the USB drivers)
Anyway, i love this phone greatly and i have heavily invested in it. I would not love to lose it. I heard of people losing IMEI because of ROM flashes- might this be something that affected me?
PLEASE HELP!
Click to expand...
Click to collapse
Just experienced the same issues while switching from the a custom rom back to stock LJ1. Stuck at the samsung screen. Took me back to my Original Epic. Downloaded the LJ1 kernel, reflashed custom recovery, flashed it, cleared dalvik, rebooted and bam! up and running. Keep getting an error about Chameleon has stopped that I am working on fixing but it is up and running so I am pleased.
kuroyoma said:
Just experienced the same issues while switching from the a custom rom back to stock LJ1. Stuck at the samsung screen. Took me back to my Original Epic. Downloaded the LJ1 kernel, reflashed custom recovery, flashed it, cleared dalvik, rebooted and bam! up and running. Keep getting an error about Chameleon has stopped that I am working on fixing but it is up and running so I am pleased.
Click to expand...
Click to collapse
It happened because you tried to flash backwards. With JB you can only flash forward.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Team Nocturnal Like A Boss :flipoff2:
-Galaxy Note II Lab Rats 2.1 Edition Goodness Theme- "Mine"
-Galaxy S2 Goodness Edition- "Wifes"
Elw00d said:
It happened because you tried to flash backwards. With JB you can only flash forward.
-Team Nocturnal Like A Boss :flipoff2:
-Galaxy Note II Lab Rats 2.1 Edition Goodness Theme- "Mine"
-Galaxy S2 Goodness Edition- "Wifes"
Click to expand...
Click to collapse
I had JB v15 and had to flash this file because I was stuck on the flash screen, after I flashed this file, it loads the phone, but it will not allow me to use the touchscreen and keeps rebooting..I need to chk debugging mode and also see what version I have now after flashing this file...pls HELP!!!!
I can't use my phone..
fechina said:
I had JB v15 and had to flash this file because I was stuck on the flash screen, after I flashed this file, it loads the phone, but it will not allow me to use the touchscreen and keeps rebooting..I need to chk debugging mode and also see what version I have now after flashing this file...pls HELP!!!!
I can't use my phone..
Click to expand...
Click to collapse
I stuck with my phone too.
I was partition my sd card and copying somes apps there and then it crashes and reboots.
Stucked in boot loop.
Already wipe data/ factory reset.
Flash stock via odin and cwm via odin.
Format sdcard in recovery (excepts /data)
Still is on boot loop
Dalvik?
Sent from the little guy
Hello to all guys I desperately need your help, this morning I installed it on my notes 2, application Swapper 2, damn I say, because I restarted the phone and it is in an infinite bootloop, I tried the same thing any firmware I can not solve the problem, i also tried the Help and Rescue Deep Clean but nothing to do, the rescue does not recognize me the files that I put on odin I tried 5 times the result is always FAIL. What can I do? 1000 Thanks to all. I posted in the other thread of aid, they told me to post it here.
P.S Sorry for my Englesh i'm italian
luca260786 said:
Hello to all guys I desperately need your help, this morning I installed it on my notes 2, application Swapper 2, damn I say, because I restarted the phone and it is in an infinite bootloop, I tried the same thing any firmware I can not solve the problem, i also tried the Help and Rescue Deep Clean but nothing to do, the rescue does not recognize me the files that I put on odin I tried 5 times the result is always FAIL. What can I do? 1000 Thanks to all. I posted in the other thread of aid, they told me to post it here.
P.S Sorry for my Englesh i'm italian
Click to expand...
Click to collapse
Can you get to your custom recovery? Vol up+home+power, keep holding till Samsung Galaxy Note 2 pops up and it goes to recovery. Which recovery are you using? What ROM are you on? These need to be known to help you
Android...A New Digital Revolution Of Incredible Developers...
ianmb said:
Can you get to your custom recovery? Vol up+home+power, keep holding till Samsung Galaxy Note 2 pops up and it goes to recovery. Which recovery are you using? What ROM are you on? These need to be known to help you
Android...A New Digital Revolution Of Incredible Developers...
Click to expand...
Click to collapse
Yes I can install the TWRP Recovery, and I have the Samsung Stock Rom. I can go in download mode. In the stock recovery I have 2 errors: E: Failed to mount / efs (invalid argument) and Faied mount / sdcard No such file.
Sorry for my Englesh I'm Italian
Question
Did you save a stock backup so you can reinstall if something happens.
luca260786 said:
Yes I can install the TWRP Recovery, and I have the Samsung Stock Rom. I can go in download mode. In the stock recovery I have 2 errors: E: Failed to mount / efs (invalid argument) and Faied mount / sdcard No such file.
Sorry for my Englesh I'm Italian
Click to expand...
Click to collapse
If you are rooted you need to use TWRP and not stock recovery. You cannot flash a different ROM on stock recovery.
Android...A New Digital Revolution Of Incredible Developers...
ianmb said:
If you are rooted you need to use TWRP and not stock recovery. You cannot flash a different ROM on stock recovery.
Android...A New Digital Revolution Of Incredible Developers...
Click to expand...
Click to collapse
Yes i can also install the root, but then the galaxy will not start is always the same in writing samsung and does not go ahead I also flashed 13 times than the stock firmware and not a single one all the stops to boot. I do not know how to fix it.
luca260786 said:
Yes i can also install the root, but then the galaxy will not start is always the same in writing samsung and does not go ahead I also flashed 13 times than the stock firmware and not a single one all the stops to boot. I do not know how to fix it.
Click to expand...
Click to collapse
Was it a stock ROOTED rom? And all this was from installing an app? What did you wipe in TWRP? Did you try Advanced Wipe in TWRP...Cache/Dalvik/Data/System? Then try a rooted rom made for your phone.
Android...A New Digital Revolution Of Incredible Developers...
ianmb said:
Was it a stock ROOTED rom? And all this was from installing an app? What did you wipe in TWRP? Did you try Advanced Wipe in TWRP...Cache/Dalvik/Data/System? Then try a rooted rom made for your phone.
Android...A New Digital Revolution Of Incredible Developers...
Click to expand...
Click to collapse
I have already done all this that you have written, I have not solved the problem. When I installed Swapper 2 I had a custom rom rooted.
Hey guys,
My girlfriends S4 mini has bricked. I've tried flashing a totally stock firmware via odin to recover it. This doesn't seem to help at all, it still gets stuck at the splash screen. I've tried flashing TWRP via odin too but that fails as well, AFAIK drivers are installed correctly, odin detects the device, it wouldn't do so if drivers weren't install correctly surely? The only mode I can get it into is download mode, if I try to reboot into recovery mode it'll say 'booting recovery' for 5 seconds or so then reboot and get stuck at the splash screen again.
Any help is appreciated, I'm a samsung noob, thanks.
What recovery was on it prior to having this problem?
I read that someone was having a slight problem like you (twrp recovery), and they flashed PhilZ tar using Odin, in order to boot back into recovery.
You could try a older version of PhilZ foie your device might help...
Look here>> http://goo.gl/2xlUCO
And have you tried using the kies emergency firmware recovery? That saved a device I flashed with a stock firmware, and then the phone wouldn't boot, soft brick.
Ran the kies emergency firmware, it downloaded what was needed, then flashed it on the phone. Takes about 20-30 mins.
Keep in mind if you do try that method, no need to put the phone into download mode. Kies will recognize the phone when you connect it thru usb. And it will do the rest.
Hope this can help you fix the phone.
Bajanman said:
What recovery was on it prior to having this problem?
I read that someone was having a slight problem like you (twrp recovery), and they flashed PhilZ tar using Odin, in order to boot back into recovery.
You could try a older version of PhilZ foie your device might help...
Look here>> http://goo.gl/2xlUCO
And have you tried using the kies emergency firmware recovery? That saved a device I flashed with a stock firmware, and then the phone wouldn't boot, soft brick.
Ran the kies emergency firmware, it downloaded what was needed, then flashed it on the phone. Takes about 20-30 mins.
Keep in mind if you do try that method, no need to put the phone into download mode. Kies will recognize the phone when you connect it thru usb. And it will do the rest.
Hope this can help you fix the phone.
Click to expand...
Click to collapse
Thanks, I'll be sure to try that a bit later when I get back later.
It was 100% stock when the issue occurred, no root, no custom recovery, knox is still 0x0
matt4321 said:
Thanks, I'll be sure to try that a bit later when I get back later.
It was 100% stock when the issue occurred, no root, no custom recovery, knox is still 0x0
Click to expand...
Click to collapse
Wow then yes that is kinda crazy then being fully stock set-up.
Then you'll want to try the kies emergency firmware fix.
Lmk how it works out for you.
I'll keep an eye on this thread for your feedback.
matt4321 said:
Hey guys,
My girlfriends S4 mini has bricked. I've tried flashing a totally stock firmware via odin to recover it. This doesn't seem to help at all, it still gets stuck at the splash screen. I've tried flashing TWRP via odin too but that fails as well, AFAIK drivers are installed correctly, odin detects the device, it wouldn't do so if drivers weren't install correctly surely? The only mode I can get it into is download mode, if I try to reboot into recovery mode it'll say 'booting recovery' for 5 seconds or so then reboot and get stuck at the splash screen again.
Any help is appreciated, I'm a samsung noob, thanks.
Click to expand...
Click to collapse
Try doing @Bajanman said
If it doesnt work then try a new firmware which isnt for your carrier or maybe a different country. This is because samsung has this long lasting tradition of some of its firmware being corrupted/not booting. Screw you samsung moment when you realize that the firmware you have cooked/themed on is bullcrap
Thanks @SkywalkerZ and @Bajanman for your help,
the current situation is that I've tried the kies recovery method, but when doing tools > emergency recovery mode, it asks for a recovery code which I dont have,
If I try tools > firmware upgrade and initialization, it asks for the model name ( GT-I9195 ) and the seriel number, which I also enter. But it then says 'GT-I9195 does not support initializing'.
I'm currently downloading a new firmware of sammobile which I can try flash through odin right?
matt4321 said:
Thanks @SkywalkerZ and @Bajanman for your help,
the current situation is that I've tried the kies recovery method, but when doing tools > emergency recovery mode, it asks for a recovery code which I dont have,
If I try tools > firmware upgrade and initialization, it asks for the model name ( GT-I9195 ) and the seriel number, which I also enter. But it then says 'GT-I9195 does not support initializing'.
I'm currently downloading a new firmware of sammobile which I can try flash through odin right?
Click to expand...
Click to collapse
Yeah, odin
let us know
SkywalkerZ said:
Yeah, odin
let us know
Click to expand...
Click to collapse
So I tried that, unfortunatly the same issue occured, when the flash is done, it trys to reboot into recovery, fails, then reboots to the splash screen, reboots, then back to the splash screen and so on until I remove the battery
matt4321 said:
So I tried that, unfortunatly the same issue occured, when the flash is done, it trys to reboot into recovery, fails, then reboots to the splash screen, reboots, then back to the splash screen and so on until I remove the battery
Click to expand...
Click to collapse
Can I ask what recovery is installed? And have you tried flashing a different custom recovery thru Odin? To see if it will help boot the phone..
Someone else was going thru the same as you, and that help get them back in order.
Bajanman said:
Can I ask what recovery is installed? And have you tried flashing a different custom recovery thru Odin? To see if it will help boot the phone..
Someone else was going thru the same as you, and that help get them back in order.
Click to expand...
Click to collapse
Yeah I've tried flashing a custom recovery, nothing seems to stick, it's so strange.
Everything is 100% stock and knox is still 0x0, I'm running out of ideas. Might have to send it off.
It's frustrating though because I can get it into download mode, but the flashing doesn't seem to work
matt4321 said:
Yeah I've tried flashing a custom recovery, nothing seems to stick, it's so strange.
Everything is 100% stock and knox is still 0x0, I'm running out of ideas. Might have to send it off.
It's frustrating though because I can get it into download mode, but the flashing doesn't seem to work
Click to expand...
Click to collapse
I can understand the frustration you're going thru trust me.
I know you know what you're doing, but the person who said they fixed a soft brick, flashed a really old version of PhilZ to get it back. Then flash a custom Rom to get the phone up and running.
But I know you've tried Odin back to stock and nothing is working for you. What's the crazies part is that the phone was completely stock. And it's still broke...
If I see/find any thing that may help you I'll post it here ok.
Bajanman said:
I can understand the frustration you're going thru trust me.
I know you know what you're doing, but the person who said they fixed a soft brick, flashed a really old version of PhilZ to get it back. Then flash a custom Rom to get the phone up and running.
But I know you've tried Odin back to stock and nothing is working for you. What's the crazies part is that the phone was completely stock. And it's still broke...
If I see/find any thing that may help you I'll post it here ok.
Click to expand...
Click to collapse
Appreciate the help mate!
So I tried an old Philz recovery, that didn't stick either. I'm wondering what is really happening since if I flash a custom recovery then knox should void right? but anytime I flash TWRP or Philz, then head back to download mode it still says knowx 0x0.
What drivers did you install on your PC, do you have a link? I'm starting to think maybe that is the issue, but surely odin would refuse to flash at all if no samsung drivers were installed...?
matt4321 said:
Appreciate the help mate!
So I tried an old Philz recovery, that didn't stick either. I'm wondering what is really happening since if I flash a custom recovery then knox should void right? but anytime I flash TWRP or Philz, then head back to download mode it still says knowx 0x0.
What drivers did you install on your PC, do you have a link? I'm starting to think maybe that is the issue, but surely odin would refuse to flash at all if no samsung drivers were installed...?
Click to expand...
Click to collapse
Sorry i lost touch with this thread and busy with studies
The only drivers that are needed are the ones that will be installed with KIES
Nothing else is needed
This is really weird of how it doesnt want to boot up even after flashing stock firmware via odin
Just a quick check, ..what options did you choose in odin ?
SkywalkerZ said:
Sorry i lost touch with this thread and busy with studies
The only drivers that are needed are the ones that will be installed with KIES
Nothing else is needed
This is really weird of how it doesnt want to boot up even after flashing stock firmware via odin
Just a quick check, ..what options did you choose in odin ?
Click to expand...
Click to collapse
These are the options, see the photo.
I've tried trying a few different options. Is this how it should look?
I'm a full on Samsung noob
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
matt4321 said:
These are the options, see the photo.
I've tried trying a few different options. Is this how it should look?
I'm a full on Samsung noob
Click to expand...
Click to collapse
Hi, re-partition should be not ticked!, download firmware from sammobile, select it only as AP.
N0Ntoxic said:
Hi, re-partition should be not ticked!, download firmware from sammobile, select it only as AP.
Click to expand...
Click to collapse
Cheers for the reply, so I've tried that before, saw the instructions in another thread, I'll give it another try though and untick re-partition
May I ask which firmware exactly are you trying to flash?
From your pictures youre trying Bml4 i think its a jb with Knox , if the phone has a kk it will fail install
Why are you trying to flash with repartition and pit file?
Did you messed somehow with the partition table?
What is exactly the the phone got bricked, normal usage overheat, water damage, dropped if you have no signs damage if it's under Warranty and knox 0x0 Send it to service.
matt4321 said:
These are the options, see the photo.
I've tried trying a few different options. Is this how it should look?
I'm a full on Samsung noob
Click to expand...
Click to collapse
yeah, as another user said
Re partition shouldn't be ticked
Now hopefully this does the trick
and also, if your phone came with 4.4.2, flash 4.4.2
dont downgrade. to 4.2.2
Try this:
Flash a custom recovery
wipe internal sd
Flash stock firmware and try booting up
Hopefully that will fix it
hey guys,
i dun think thr is a similar thread regard my issue, here is a picture of what i get when i stuck at login screen for very long, decide to flash stock rom using ODIN and i did.
After which it boots to system recover and this is what it shows.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
helpppppppppppp
Identical to mine, gave up on it, sds
Sent from my SM-N910G using Tapatalk
Does it go to this after the flash with Odin or whenever you go into recovery
Sent from my Moto G using Tapatalk
ramien said:
hey guys,
i dun think thr is a similar thread regard my issue, here is a picture of what i get when i stuck at login screen for very long, decide to flash stock rom using ODIN and i did.
After which it boots to system recover and this is
helpppppppppppp
Click to expand...
Click to collapse
looks like partition table corrupted. reflash stock rom with CORRECT pit file may help (DO IT AT YOUR OWN RISK)
For me, I couldn't flash with Odin no matter what I tried, can't remember the error but essentially odin couldn't even begin the process.
I have flashed 100s of times previously with Odin too, so it really is kaput once this sds happens.
Yes, this is symptom of corrupted partition table, or at least it means the partition table is not as needed by stock Samsung firmware. Most (all?) 3rd party recoveries cause this; they are ok with custom rom but cause problems with stock (other great symptom is you can make nand backup of stock but it will be unusable after restore).
Solution is to again use odin, this time with pit file and stock image. I have done this a few times, no problems.
tonymy01 said:
For me, I couldn't flash with Odin no matter what I tried, can't remember the error but essentially odin couldn't even begin the process.
I have flashed 100s of times previously with Odin too, so it really is kaput once this sds happens.
Click to expand...
Click to collapse
try another usb port, those on the rear are preferred usually. if it fails, connect to another pc
I tried two computers, with SDS Odin will not be able to flash no matter what you try(trust me,I tried multiple different pit,f/w downloads).
Sent from my SM-N910G using Tapatalk
tonymy01 said:
I tried two computers, with SDS Odin will not be able to flash no matter what you try(trust me,I tried multiple different pit,f/w downloads).
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
looks like u have to find a way to access the phone via adb and repartition yourself
ykkfive said:
looks like u have to find a way to access the phone via adb and repartition yourself
Click to expand...
Click to collapse
Stock recovery gives nearly no options in adb shell, and thanks too not being able to mount anything, is next to useless. Research about SDS, once a phone is in this state due to SDS, it is not recoverable.
Sent from my SM-N910G using Tapatalk
ykkfive said:
try another usb port, those on the rear are preferred usually. if it fails, connect to another pc
Click to expand...
Click to collapse
yeah for me it took ages to figure out it was usb ports.
wait for odin to detect. start. fails. new usb port. same thing. back to the old one. try usb3.0. try 2.0. try 1.0 etc. was a nightmare
also make sure u install drivers for usb
Do you used 1.9 extra space partition ? See here http://forum.xda-developers.com/showthread.php?t=2773758
In that case, try to load the stock pit via Odin.
yeah it can go to odin still, but after flashing stock roms, its still the same, when it goes to recovery, it shows all that. =( someone help pls?
so which PIT file to be used? there is so many out there =\
ramien said:
so which PIT file to be used? there is so many out there =\
Click to expand...
Click to collapse
I've attached a zipped pit for 16GB GT-N7105. I've used it, it's fine.
btw, after trying out different recoveries I found that the only one that has worked reliably on my GT-N7105 is twrp-2.8.7.0-t0lte.img.tar (version number is probably unimportant, that just happens to be the latest). It has to be installed using odin. Both cyanogen and cwm recovery images (such as cm-12.1-20151024-NIGHTLY-t0lte-recovery.img or recovery-clockwork-touch-6.0.4.1-t0lte.img) have left me with partition table problems which became apparent on trying to return to stock samsung.....which is why I needed the pit file and why I know it's good.
TWRP has been excellent and also let me root stock samsung in a simple way (normal supersu.zip or even just from the prompt in the recovery) instead of needing CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip.
Anyway I hope the pit is suitable (you do have a 16GB device?) and that you get it all fixed.
i tried to use ODIN, PIT with the twrp file, it fail.
helppppppppppppppppppp
It is SDS, there is no software recovery at this point,I have tried everything.
Sent from my SM-N910G using Tapatalk
julian67 said:
I've attached a zipped pit for 16GB GT-N7105. I've used it, it's fine.
btw, after trying out different recoveries I found that the only one that has worked reliably on my GT-N7105 is twrp-2.8.7.0-t0lte.img.tar (version number is probably unimportant, that just happens to be the latest). It has to be installed using odin. Both cyanogen and cwm recovery images (such as cm-12.1-20151024-NIGHTLY-t0lte-recovery.img or recovery-clockwork-touch-6.0.4.1-t0lte.img) have left me with partition table problems which became apparent on trying to return to stock samsung.....which is why I needed the pit file and why I know it's good.
TWRP has been excellent and also let me root stock samsung in a simple way (normal supersu.zip or even just from the prompt in the recovery) instead of needing CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip.
Anyway I hope the pit is suitable (you do have a 16GB device?) and that you get it all fixed.
Click to expand...
Click to collapse
tonymy01 said:
It is SDS, there is no software recovery at this point,I have tried everything.
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
SDS is stuck SDS can load to home page, mine is not SDS. i still can go ODIN and go recovery page, just that when i factory reset, it shows errors.
any new solutions guys? Devs? i love you, please help me..
ramien said:
i tried to use ODIN, PIT with the twrp file, it fail.
Click to expand...
Click to collapse
1st thing: don't use pit with twrp or other recovery. Pit is for use with ROM image, typically stock ROM.
Ignore the guy who keeps injecting "SDS" every other reply. It is just noise.
So be calm and start over.
Plan A:
Make sure your phone has at least 75% battery, if possible.
Start Odin.
Put your phone in Download Mode and connect to Odin in the usual way.
Check the Re-Partition box and select your pit file.
Check the PDA box and select your Original Samsung Firmware. NOT your TWRP recovery image.
Odin will take a minute to check the PDA image. When that is done then press Start and be patient. Very patient. Do not disconnect your phone before completion. When Odin shows "Pass" in green box then you can disconnect.
Power down the phone. It won't boot yet.
Boot to Recovery (Volume Up+Home+Power buttons)
Choose "wipe data/factory reset" and proceed.
Next Choose "wipe cache partition" and proceed (actually I am sure that "factory reset" includes "wipe cache" but anyway, no harm in doing it twice).
Now "reboot system now".
Be patient. Very, very patient. It could even take 15 minutes to start the first time.
If the above doesn't help then it's time for.....
Plan B!
Plan B is the same except you are going to be brave.
Back to Odin:
Check the Re-Partition box and select your pit file.
Also select "Nand Erase All"
Check PDA and load Samsung firmware
Proceed as described in Plan A complete with rebooting to recovery and performing factory reset and so on.
I have done this myself. It worked. Ignore the people who have some religious-type terror of checking re-partition and nand erase boxes. This situation is what those boxes are for.
Once the NAND flash is dead from SDS, it really depends on which part of the flash is no longer readable or writable as to the symptoms. But you can keep trying, you never know..
Sent from my SM-N910G using Tapatalk