Hi
Rooted my S6, and threw TWRP recovery on, put a "sixperience S7" rom on it, at first it worked flawlessly, but since I didnt make a factory reset i pulled one later, thats when my problems started.
Installs fine, reboots and the initial start and setup goes fine, but when the screen turns off and i wake it up again, the screen looked like a pc screen with no gfx driver, funky colors and very dark - tried two times to make a clean install, same happened
Tried to install stock rom with Odin, failed, tried 3-4 times, fails
Then i went into TWRP and deleted all......but seriously all......coudnt boot into anything then, not even download mode, got the message on the screen that "something went wrong in updating the firmware, try the emergency recovery with Samsung Smart Switch" That of course couldnt connect to the phone, when i finally got it to be recognized by the computer, my phone wasn't supported by the program (because it is rooted i read somewhere)
After an hour with a lot of swearing and crying almost, I tried to connect it to Odin and i got connected, installed a new TWRP and i got it into recovery where i could install a new rom, and the phone booted again
Heres my question, when i put it into download mode (tried to install stock rom with Odin once more) then I cannot boot it again, I have to install TWRP and a new rom before I can get it up and running again, is there any possibility to get a stock rom installed ever again?
Related
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
cugami said:
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
Click to expand...
Click to collapse
GO here : http://forum.xda-developers.com/showthread.php?t=1993044
Hello everyone!
I have a Lenovo a820 with Lambda rom 2.4v.
I'm using it for a couple of weeks now with this last version, and everything was fine, until suddenly it froze for a while, I unplugged the battery and plugged it again, and what I notice was that the phone restored itself to when after I installed the rom (meaning all of the apps were gone).
So I tried going into Google play, installing some apps back, and I get this error -24 telling me its unable to install the app, happened with any app I tried. so after trying a few suggestions from the internet about this error, I decided to format it and install the rom all over again.
I go back to recovery mode with CWM, try to install the lambda rom like I did before, and in the middle of the installation it reboots and gets stuck in the "lenovo" screen like when you boot it. so after waiting for a long time I unplugged and plugged the battery again, went through the procedure again this time it installed it 100% rebooted so it would boot with the mod, and again, it freezes at "lenovo" start screen unable to boot.
went on recovery mode, formatted system, data, emmc, everything... I think that's the issue here. but im not sure.
After that, tried to install again with the same problem.
The problem now is. it won't even start I press the on/off button to start it normally, and I dont even get the "lenovo" screen, I tried going into recovery mode and no luck.
It's like the phone is dead! Although I have another Lenovo A820 and I tried the battery, and its 60% so that's not the battery.
Do you guys know any tricks? or any tools that I could use to get my phone running again?
I would appreciate it very much, any help you can give.
Matt.
MatWho said:
Hello everyone!
I have a Lenovo a820 with Lambda rom 2.4v.
I'm using it for a couple of weeks now with this last version, and everything was fine, until suddenly it froze for a while, I unplugged the battery and plugged it again, and what I notice was that the phone restored itself to when after I installed the rom (meaning all of the apps were gone).
So I tried going into Google play, installing some apps back, and I get this error -24 telling me its unable to install the app, happened with any app I tried. so after trying a few suggestions from the internet about this error, I decided to format it and install the rom all over again.
I go back to recovery mode with CWM, try to install the lambda rom like I did before, and in the middle of the installation it reboots and gets stuck in the "lenovo" screen like when you boot it. so after waiting for a long time I unplugged and plugged the battery again, went through the procedure again this time it installed it 100% rebooted so it would boot with the mod, and again, it freezes at "lenovo" start screen unable to boot.
went on recovery mode, formatted system, data, emmc, everything... I think that's the issue here. but im not sure.
After that, tried to install again with the same problem.
The problem now is. it won't even start I press the on/off button to start it normally, and I dont even get the "lenovo" screen, I tried going into recovery mode and no luck.
It's like the phone is dead! Although I have another Lenovo A820 and I tried the battery, and its 60% so that's not the battery.
Do you guys know any tricks? or any tools that I could use to get my phone running again?
I would appreciate it very much, any help you can give.
Matt.
Click to expand...
Click to collapse
The boot.img must be wrong try rom for your phone.
Sent from my Moto G
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
yoda254 said:
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
Click to expand...
Click to collapse
My guess is that when you rooted with CASUAL, it changed the Samsung device driver on your computer and you need to reinstall the Samsung driver to get the computer to recognize the phone again in download mode.
Underneath step 7 of section 1b on Droidstyle's restore guide, he discusses issue with CASUAL replacing the Samsung driver... and he gives a link to Jeremy Loper's fix... "If odin no longer recognizes your device, most likely Casual killed the driver for odin!! follow this tutorial for restoring the driver: http://www.youtube.com/watch?v=zzghcV8HVVk"
Once the computer recognizes the phone again, you should be able to use ODIN to restore back to 4.1.2 so you can root/unlock again with CASUAL. After you get the phone restored with Odin, I would recommend booting into Stock Recovery and wiping cache/doing factory reset before running Casual again... this would enure you are starting over with a totally clean slate.
If the above doesn't work, then here's a thread where I tried to help someone else who couldn't get their computer to recognize the phone.... maybe some of those ideas will help - http://forum.xda-developers.com/showthread.php?p=55833998
Good luck!!
1 step forward two steps back. I got my pc /odin to recognizes my note 2(changed usb cords). Then tried to odin back to stock 4.1.2. At first odin kept saying (odin not responding) and would ask to close the program,after several attemps i final got it to flash the 4.1.2 file. When i flashed the file and was at the point where it reboots, it would not get past the samsung note 2 logo and continued to flicker and not boot up even when i tried to put it into download mode like it said to in this thread. http://forum.xda-developers.com/showthread.php?t=2024207. When i tried to reflash the file it failed. when i attempted again it just hangs at setupconnection. Tried again and it failed. Btw thanks for the help mattnmag.
Got it working! i simply forgot to place the sch-i605 pit. into the pit section of odin when i flashed the 4.1.2 rom.
Similar problems
I was running AllianceROM 26. My phone had been spontaneously rebooting for a bit recently. Today, it started to spontaneously reboot again, but this time, it never got past the Galaxy Note 2 screen. After pulling the battery, I tried to boot into TWRP. It just hangs on the twrp boot screen for a few minutes but never goes into twrp.
I figured I would try taking it back to stock. So, I used ODIN to try and put 4.1.2 on it and a new PIT file. That appeared to work fine. I got no errors in ODIN. However, I still cannot get this thing to get past these boot screens, either the Galaxy Note 2 one or TWRP when I try that there. I have tried this twice now, once with re-partition checked and another time with re-partition unchecked (saw conflicting instructions on that so I figured I would try it both ways). I still am not getting past the boot screen.
Any help or ideas are appreciated as right now, my phone appears to be bricked and I am out of ideas.
so what was the solution to the teamwin flashing on and off after a factory reset? this is certainly not a solution, having to reflash the phone...
Hello. My name is ford, i have a galaxy grand prime with no current OS on it. this is because i was attempting to install a custom ROM onto said phone and the video i had watched, had me go into twrp, (which i had installed previously) and wipe the internal storage. ( i had used odin to flash onto the phone). I then god a custom rom, lineage os i believe, and attempted to install with twrp, but a good 75 % of the way through, no matter what, the phone would reboot. this happened with multiple roms i had tried, all ending with the same result, with the phone still having no os. i then thought that it might work with cwm instead. so from there, i had installed cwm, also with odin, with twrp still installed. i figured cwm would go ahead and either become the default cstom recovery, or it would just replace twrp altogether, but then after i had rebooted and put in the key combination for the custom recovery, it would still show the text in the top left for twrp, but then the screen goes black. I had turned the phone on and off multiple times with the same result every time. i don't know this is because the phone may be confused as to which recovery to boot into, or some other alternative reason, but it will not boot into anything now, just a black screen. I still know the phone is on, because it is noticeably lit, like it is just displaying a black screen. Now to the reason for my post, (if that wasn't enough), i then just tried installing my roms with odin. and no, there is nothing wrong with the roms, as they are all tar, and are all valid, but whenever i attempt to flash any rom, the little debug will say "file analysis" and then a second later crash. (by crash i mean windows will has it has stopped working). As i have said this has happened with all roms. It doesnt matter what order i do the steps in (plug in phone, then load files; load files, then plug in phone etc...), and i have reinstalled the c++ redistributable to make sure i have all of the dll's, but absolutely nothing is working. and no it is not because of the versions of odin, because i have tried multiple. So honestly im just aggravated now. Am i just stuck with a phone with no os now, or what? Seriously will try anything. PLEASE HELP
I ran into a serious problem and now I do not know how to fix it. It turns out that I wanted to install a rom to my cell phone, since the stock I had was giving problems with the battery indicator, and I tried to calibrate it and even used others also following different steps to calibrate them, but always the same problem; Well, after root I found the problem that I could not install anything from the recovery mode of the cell phone, there was a problem that was disabled and could not from the sd, or internal, or adb or anything. Finally I decided to find an application to install twrp and flash the rom, downloaded flashify and I did.
When I went into recovery to flash the rom the cell phone did not change the logo with the message in a corner that is not the official recovery as always comes out when a custom is installed. And there it stays.
I can not turn it on normally, because each time I turn it on it goes directly to the logo with the message that it is not the original recovery, as if trying to access the recovery.
PS: I can not use odin, it does not recognize the cell phone when it is in odin mode, since all the drivers are installed and the kies, I reinstalled everything 3 times every time I tried it. And I can not enter odin mode, and the home button does not work, I used adb, but since it does not turn on, it does not recognize it either.
alberto1251 said:
I ran into a serious problem and now I do not know how to fix it. It turns out that I wanted to install a rom to my cell phone, since the stock I had was giving problems with the battery indicator, and I tried to calibrate it and even used others also following different steps to calibrate them, but always the same problem; Well, after root I found the problem that I could not install anything from the recovery mode of the cell phone, there was a problem that was disabled and could not from the sd, or internal, or adb or anything. Finally I decided to find an application to install twrp and flash the rom, downloaded flashify and I did.
When I went into recovery to flash the rom the cell phone did not change the logo with the message in a corner that is not the official recovery as always comes out when a custom is installed. And there it stays.
I can not turn it on normally, because each time I turn it on it goes directly to the logo with the message that it is not the original recovery, as if trying to access the recovery.
PS: I can not use odin, it does not recognize the cell phone when it is in odin mode, since all the drivers are installed and the kies, I reinstalled everything 3 times every time I tried it. And I can not enter odin mode, and the home button does not work, I used adb, but since it does not turn on, it does not recognize it either.
Click to expand...
Click to collapse
To enter in to the download mode you can use JIG USB which looks like this :
https://images-na.ssl-images-amazon.com/images/I/41MhETGCbBL.jpg
You can buy that jig USB on E-Bay
or you can use this tool but little Warning !!!
https://app.box.com/s/ktb9rzxde78lujqioh3rbmh6w39gedmm
File was scanned against viruses and it has some , maybe because like that he make your device in download mode.
https://www.virustotal.com/sr/file/...33ff7dceef468c2e8c325d79c7ad43fc8c1/analysis/
Here is video how to use .
https://www.youtube.com/watch?v=2er95HkiJbo
Good Luck
I'll try with the usb jig. Still don't know if buy the resistance and make one or just buy the jig. Then i will see if i can get for odin to detect the phone, using some kind of witchcraft or whatever hahahaha.
Thanks, I will set the thread as solved.
Good Luck