Ok so i installed cyanogen mod 9 on my s3 international version because it didn't let me install 10. I did it through rooting the phone then installing rom manager, there i downloaded the rom and installed it, it worked and i was able to start the phone with the new rom, but then i went to bed and it shut down and now its stuck on the boot screen. I've gone into recovery mode and tried everything, and it doesn't connect to my computer, it is unable to be read. Any help with be appreciated
Related
Hi, i have a galaxy tab 10.1 wifi only (GT-P7510)
Recently i rooted my tab and it was all good. I flashed a ICS rom (AOKP_p4wifi_milestone-4) and kernel (2.6.36.4 cynogenmod + pershoot #1) on it also worked just fine.
However i wanted to get rid of the triangle on the bootscreen so i stupidly googled a solution without checking it. Flashed the wrong bootloader and now my tab won't boot into recovery, wont boot in to download, Isn't recognised by ODIN
BUT
It will eventually turn it's self on and otherwise works perfectly fine, i can do everything but boot into recovery download and wont turn it on when i want it to. So i can use it but i'm stuck with an unfinished ICS rom and i can't flash any other roms in the future (Nor make backups). I have also tried to use ROM manager to flash and it just turns its self off and won't boot.
So is there anyway to flash it to get back into recovery/download mode or better yet are you able to flash the device while its on.
P.S connects to computer fine in MTP mode and i can search the internal sd (copy paste etc.)
Also I'm a noob
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
Hi, I have a bricked Galaxy S3 to fix here.
I generally install ROMs for people, so this one guy came by and said he tried changing his GS3 (i9300) to Cyanogen Mod, but it bricked it
I don't know when nor how he did it, the guy doesn't even know what happened because he left it flashing and went somewhere else
According to him, he used odin, doesn't know wich version of CM he installed, he only knew he installed a CM based ROM using Odin and it doesn't work anymore
Here's what i already know and tried
- The Phone won't power for more than 30 seconds on battery
- If I remove the battery and keep it usb, the phone keeps up in Download Mode
- Can't enter any recovery, tried flashing : Stock Recovery, TWRP, CWM and none worked, all of them show up and the phone reboots
- Tried doing the same thing i did on the download mode, but in recovery. It shuts down anyway,
- Tried leaving the phone without battery for a whole day and nothing changed!
Stuck on Oneplus One logo while trying to access recovery
Hi,
First of all please forgive my english, it's not my native language
So, when i try to access recovery mode on my oneplus one, it gets stuck on oneplus logo
I rooted my phone some weeks ago and installed without troubles paranoid android. I wanted to go back
to CyanogenMod so I flashed it, but I forgot to flash gapps. Cyanogen is working fine, but it's kinda useless
without google package.
Problem is, I cannot access the recovery mode anymore, because it gets stuck on the oneplus logo. I tried
to unlock the phone and install twrp again but it has no notable effect. I also waited an hour, it won't pass
the logo.
I can boot on cyanogen and on fastboot, but recovery is what i need...
The cyanogen version a flashed is cm-13.0-20160107-NIGHTLY-bacon nightly. I performed a regular wipe
with twrp and flashed.
Thanks for reading, any help is greatly appreciated.
EDIT : I noticed odd things. The musics I've put before wiping and flashing cyanogen are still on my phone,
which means the wipe did not work ( right ? ). Also, I can't access anymore to the files of my phone while being
on Media Transfer Protocol, but I can see my images if I set Pictures transfer protocol ( USB configuration in developer
settings ).
Hard reset
AkromaSt said:
Hi,
First of all please forgive my english, it's not my native language
So, when i try to access recovery mode on my oneplus one, it gets stuck on oneplus logo
I rooted my phone some weeks ago and installed without troubles paranoid android. I wanted to go back
to CyanogenMod so I flashed it, but I forgot to flash gapps. Cyanogen is working fine, but it's kinda useless
without google package.
Problem is, I cannot access the recovery mode anymore, because it gets stuck on the oneplus logo. I tried
to unlock the phone and install twrp again but it has no notable effect. I also waited an hour, it won't pass
the logo.
I can boot on cyanogen and on fastboot, but recovery is what i need...
The cyanogen version a flashed is cm-13.0-20160107-NIGHTLY-bacon nightly. I performed a regular wipe
with twrp and flashed.
Thanks for reading, any help is greatly appreciated.
EDIT : I noticed odd things. The musics I've put before wiping and flashing cyanogen are still on my phone,
which means the wipe did not work ( right ? ). Also, I can't access anymore to the files of my phone while being
on Media Transfer Protocol, but I can see my images if I set Pictures transfer protocol ( USB configuration in developer
settings ).
Click to expand...
Click to collapse
Try to do a hard reset (Search it in google or youtube)
It worked ! thanks a lot : ) !
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?