Database Info

serious problem

I followed nearly all the steps in installing cm10.1 build 20130322 but the gapps file was corrupted and i couldn't flash it
so i just went ahead and rebooted the system and guess what?
white screen!
so i went to restore boot from advanced restore and guess what again?
bootloop!
I have just decided to give up on installing custom roms and if the mods wanna delete this thread
No problem!

Bhuyan23 said:
I followed nearly all the steps in installing cm10.1 build 20130322 but the gapps file was corrupted and i couldn't flash it
so i just went ahead and rebooted the system and guess what?
white screen!
so i went to restore boot from advanced restore and guess what again?
bootloop!
I have just decided to give up on installing custom roms and if the mods wanna delete this thread
No problem!
Click to expand...
Click to collapse
You should not use restore boot method in CM ROMs. You may also brick device if you do it, better use some GB ROM if you are getting white screen issue.

Bhuyan23 said:
I followed nearly all the steps in installing cm10.1 build 20130322 but the gapps file was corrupted and i couldn't flash it
so i just went ahead and rebooted the system and guess what?
white screen!
so i went to restore boot from advanced restore and guess what again?
bootloop!
I have just decided to give up on installing custom roms and if the mods wanna delete this thread
No problem!
Click to expand...
Click to collapse
flash an english baseband then flash cm
flash the first rom through odin
and there you go, unbrick

ShadowsDie said:
flash an english baseband then flash cm
flash the first rom through odin
and there you go, unbrick
Click to expand...
Click to collapse
can anybody just explain to me what causes this white screen

Bhuyan23 said:
can anybody just explain to me what causes this white screen
Click to expand...
Click to collapse
Because the GB ROM you had earlier is from a country that has something changed,(i don't know what) it causes problems when you flash any CM
The solution is flashing an English rom there will be no such change and it will work
Do you understand now?
P.S. Such a ROM with this problem are used to be from india firmwares
Do you have an indian firmware?

ShadowsDie said:
Because the GB ROM you had earlier is from a country that has something changed,(i don't know what) it causes problems when you flash any CM
The solution is flashing an English rom there will be no such change and it will work
Do you understand now?
P.S. Such a ROM with this problem are used to be from india firmwares
Do you have an indian firmware?
Click to expand...
Click to collapse
Absolutely! I do have an Indian firmware
by the way I thought it had something to do with the model variant
but when I checked the back of the battery I found this

Can you please provide the sales code for an english rom? for example XEU

Bhuyan23 said:
Absolutely! I do have an Indian firmware
by the way I thought it had something to do with the model variant
but when I checked the back of the battery I found this
Click to expand...
Click to collapse
One suggestion don't provide such kind of pics because it has your IMEI number,
So for privacy issue you have to protect that number.
Bhuyan23 said:
Can you please provide the sales code for an english rom? for example XEU
Click to expand...
Click to collapse
For indian firmware issue then I'm not agree that, its issue by indian firmware.
I always flash custom roms on indian firmware & till now i didn't face any issue like white screen or brick device.
-Lets do this step by step.
Do you have indian firmware ?
(Latest firmware DDMF2 or try any old one)
Flash back it through odin
-Then download CWM v5.5
(You get link from my rom Pure Galaxy v1.0 thread in development section, check last page)
Check the version again
CWM v5.5 not v6 or v5.0
-root your device through CWM
-& now finally go n try to flash cm rom, I hope this time you will never face any white screen issue.

j.posarekar70 said:
One suggestion don't provide such kind of pics because it has your IMEI number,
So for privacy issue you have to protect that number.
For indian firmware issue then I'm not agree that, its issue by indian firmware.
I always flash custom roms on indian firmware & till now i didn't face any issue like white screen or brick device.
-Lets do this step by step.
Do you have indian firmware ?
(Latest firmware DDMF2 or try any old one)
Flash back it through odin
-Then download CWM v5.5
(You get link from my rom Pure Galaxy v1.0 thread in development section, check last page)
Check the version again
CWM v5.5 not v6 or v5.0
-root your device through CWM
-& now finally go n try to flash cm rom, I hope this time you will never face any white screen issue.
Click to expand...
Click to collapse
I just know that people here solved this bug flashing an english ROM.
But maybe you are right, he should try.

Problem with archidroid in samsung galaxy s iii

Hello there! I just flashed ArchiDroid V2.3.4 in my Galaxy S III. When flashing ended I selected reboot now. But my phone only reboots in recovery mode (phiilz touch 4 CWM Base Version: 6.0.3.1). I tried to reboot my phone from the recovery mode but still the same problem. I tried to remove the battery and try again but still the same problem. Can you give me a solution to this cause I don't know what to do... Thanks!

aggokeh said:
Hello there! I just flashed ArchiDroid V2.3.4 in my Galaxy S III. When flashing ended I selected reboot now. But my phone only reboots in recovery mode (phiilz touch 4 CWM Base Version: 6.0.3.1). I tried to reboot my phone from the recovery mode but still the same problem. I tried to remove the battery and try again but still the same problem. Can you give me a solution to this cause I don't know what to do... Thanks!
Click to expand...
Click to collapse
did you do a full flash? i would try flashing the rom again.

Trozzul said:
did you do a full flash? i would try flashing the rom again.
Click to expand...
Click to collapse
yes i think i did a full flash.. i just followed the instruction given.. i flashed the rom again several times but i have the same problem. whenever i open the phone it's the recovery mode and not the casual start.

try flashing custom kernel or stock kernel for ur fon...hope this helps...

aggokeh said:
yes i think i did a full flash.. i just followed the instruction given.. i flashed the rom again several times but i have the same problem. whenever i open the phone it's the recovery mode and not the casual start.
Click to expand...
Click to collapse
maybe try another rom for now to at least get somewhere, is the rom your flashing a 4.4.2 rom?

Trozzul said:
maybe try another rom for now to at least get somewhere, is the rom your flashing a 4.4.2 rom?
Click to expand...
Click to collapse
its 4.4.. i will try to flash a custom rom and see what happens but i don't know if this is rom's fault or PhilZ Touch Recovery's fault

aggokeh said:
its 4.4.. i will try to flash a custom rom and see what happens but i don't know if this is rom's fault or PhilZ Touch Recovery's fault
Click to expand...
Click to collapse
i wanna say its the recovery because i think 4.4 roms are only flashing on CWM 6.0.4.3 i dont know what other recovery's require.

Trozzul said:
i wanna say its the recovery because i think 4.4 roms are only flashing on CWM 6.0.4.3 i dont know what other recovery's require.
Click to expand...
Click to collapse
the CWM version of this particular recovery is 6.0.3.1.. Is this a problem? and if it's recovery's problem what can i do about it? if i flash a stock rom the recovery will not be erased.

.
Trozzul said:
i wanna say its the recovery because i think 4.4 roms are only flashing on CWM 6.0.4.3 i dont know what other recovery's require.
Click to expand...
Click to collapse
and this particular recovery is recommended in the instruction of the ROM

aggokeh said:
and this particular recovery is recommended in the instruction of the ROM
Click to expand...
Click to collapse
hmmm well i dont know what to say to that but thats what i have heard with kit kat roms, i have looked on CWMs website and almost all of the galaxys s3s (discluding the s3 mini and international i think) have 6.0.4.X so i would try the specific one for you on Rom manager when you get a rom Working.

I Just installed HellKat 4.4 on my galaxy S3.
The only way this would work is to get my CWM to 6.0.4 just like Trozzul suggested.
The way I did it is to find ODIN pro/lite (MobileODINLite-v4.00.apk)
Then use that to install the CWM.img.
The HellKat 4.4 would not install with CWM 6.0.1
Hope this helps

Razor0 said:
I Just installed HellKat 4.4 on my galaxy S3.
The only way this would work is to get my CWM to 6.0.4 just like Trozzul suggested.
The way I did it is to find ODIN pro/lite (MobileODINLite-v4.00.apk)
Then use that to install the CWM.img.
The HellKat 4.4 would not install with CWM 6.0.1
Hope this helps
Click to expand...
Click to collapse
can he not just Flash a CWM.img in his recovery? or use rom manager to flash over it?

N8000 Bootloop

i have N8000 stuck on First Screen (Samsung Note 10.1)
i tried to flash 4.1.2 FULL (4 files & pit)
4.4.2
stock recovery
twrp
CWM
all successful but still stuck on Samsung Note 10.1 screen
& i cant enter to recovery
any idea???

There are two ways to fix this problem:
1. You can flash stock firmware via Odin.
2. Flash PhilZ Kernel via Odin and then flash custom ROM from it.

DroidTwe4kz said:
There are two ways to fix this problem:
1. You can flash stock firmware via Odin.
2. Flash PhilZ Kernel via Odin and then flash custom ROM from it.
Click to expand...
Click to collapse
i already flashed alot of stock firmware via odin ... all of them flashed 100% but still have the same problem

justrelax said:
i already flashed alot of stock firmware via odin ... all of them flashed 100% but still have the same problem
Click to expand...
Click to collapse
Try second method then.

DroidTwe4kz said:
Try second method then.
Click to expand...
Click to collapse
do u mean this file (philz_touch_6.00.8-n8000.tar.md5) ???
cuz i cant find kernel

justrelax said:
do u mean this file (philz_touch_6.00.8-n8000.tar.md5) ???
cuz i cant find kernel
Click to expand...
Click to collapse
Yes try that one

DroidTwe4kz said:
Yes try that one
Click to expand...
Click to collapse
same problem ... flashed Successful but still no recovery & stuck on Samsung Note 10.1 Screen

justrelax said:
same problem ... flashed Successful but still no recovery & stuck on Samsung Note 10.1 Screen
Click to expand...
Click to collapse
Weird

i am having the exact same problem except mine makes it to the splash screen. a fix would be awesome.

Help! NO OS installed/Need help flashing stock ROM to soft(?)-bricked S6 SM-G290F

So yesterday i done a pretty stupid thing of restarting my phone after I hid my SU binary using hide my root. This left what i think was a soft-brick as it was stuck on the samsung animation. I then stupidly enough got confused with my TWRP recovery menu and ended up wiping out my OS, leaving only the TWRP recovery on the phone. I then decided to download a 6.1.1 stock rom for my SM-G920F. When i tried flashing however, somehow ODIN froze and i made another stupid mistake of restarting my phone from download mode which resulted in the phone being froze on a screen saying " an error has occurred while updating the device software use the emergency recovery function s6 " cant provide an image as this is my first post, but please google the error message if you wish to see it
So i panicked thinking my phone was dead completely and surrendered, but today i managed to hook it up to TWRP and flashed the recovery. Now when i bootup i can access download mode and it boots straight to recovery. To make matters worse I began trying to download the original rom i recieved when i got the phone, however when i try flashing i get errors such as " SW rev, Check Fail: 'x' binary 'y' device "
(x and y vary for each stock rom i tried flashing.)
I have no way of finding out my firmware, bootloader info or anything. Is there ANY fix to this? I've made a huge mess of everything and I'm now desperate. Please, any advice would be a god-send. Thank you for withstanding this crappy post, I'm kind of a noob at xda.
EDIT 1- So I managed to install a custom ROM and kernal as i could transfer files while in TWRP for some reason but a new problem has showed up. So as of right now I have a custom rom installed which works, but when reboot my phone, TWRP is automatically opened after the initial samsung logo. I usually have to reflash my custom ROM (without wiping any data besides cache and dalvik) and the ROM installer will then reboot into the ROM, however this means when my phone turns off, my recovery is booted up instead of the ROM
I'm sensing some sort of Bootloader problem?

Metro221 said:
Now when i bootup i can access download mode and it boots straight to recovery.
Click to expand...
Click to collapse
First off i dont own an S6 (im still rocking the S4), but i have had some problems over the years but always managed to fix them in the end.
So while in Download mode are you not able to Flash Stock ROM (downloaded from samfirmware) via ODIN (following the instructions on the site)?
In TWRP are you not able to flash a custom ROM (probably with OTG cable if you dont have the ROM stored on the internal memory).
Any issues i have had i have always been able to do at least one of the above methods. If you cant do either or, im not sure what else i would try.
Thanks

Metro221 said:
So yesterday i done a pretty stupid thing of restarting my phone after I hid my SU binary using hide my root. This left what i think was a soft-brick as it was stuck on the samsung animation. I then stupidly enough got confused with my TWRP recovery menu and ended up wiping out my OS, leaving only the TWRP recovery on the phone. I then decided to download a 6.1.1 stock rom for my SM-G920F. When i tried flashing however, somehow ODIN froze and i made another stupid mistake of restarting my phone from download mode which resulted in the phone being froze on a screen saying " an error has occurred while updating the device software use the emergency recovery function s6 " cant provide an image as this is my first post, but please google the error message if you wish to see it
So i panicked thinking my phone was dead completely and surrendered, but today i managed to hook it up to TWRP and flashed the recovery. Now when i bootup i can access download mode and it boots straight to recovery. To make matters worse I began trying to download the original rom i recieved when i got the phone, however when i try flashing i get errors such as " SW rev, Check Fail: 'x' binary 'y' device "
(x and y vary for each stock rom i tried flashing.)
I have no way of finding out my firmware, bootloader info or anything. Is there ANY fix to this? I've made a huge mess of everything and I'm now desperate. Please, any advice would be a god-send. Thank you for withstanding this crappy post, I'm kind of a noob at xda.
Click to expand...
Click to collapse
If you boot in TWRP recovery it can be soved easily.
1)first try do wipe data and internal partition.And then try flashing stock firmware with odin(download proper file basing on ur model)
2)U may download a rom for ur model and flash using twrp.then if u want u can stay with the rom,i u dont u can try to flash again with odin after installing rom
Click :good: for my answer

Rremi said:
If you boot in TWRP recovery it can be soved easily.
1)first try do wipe data and internal partition.And then try flashing stock firmware with odin(download proper file basing on ur model)
2)U may download a rom for ur model and flash using twrp.then if u want u can stay with the rom,i u dont u can try to flash again with odin after installing rom
Click :good: for my answer
Click to expand...
Click to collapse
Yeah i managed to install a custom rom Tyrannus v 28.1, through TWRP, however, now I am experiencing a new problem, when i reboot - my phone boots up into TWRP instead of the ROM, more information in the edit i made in the post. THanks for all the continued help

Rremi said:
If you boot in TWRP recovery it can be soved easily.
1)first try do wipe data and internal partition.And then try flashing stock firmware with odin(download proper file basing on ur model)
2)U may download a rom for ur model and flash using twrp.then if u want u can stay with the rom,i u dont u can try to flash again with odin after installing rom
Click :good: for my answer
Click to expand...
Click to collapse
Waste of a post, but i wanted to say shqiptar, faleminderit. :*

Metro221 said:
Waste of a post, but i wanted to say shqiptar, faleminderit. :*
Click to expand...
Click to collapse
Ska gje.
Nga shqiperia je ?

Rremi said:
Ska gje.
Nga shqiperia je ?
Click to expand...
Click to collapse
Po po nga shqiperia.
But living in London ????

Would Samsung smart switch not help installing the stock rom?
Sent from my SM-G920F using Tapatalk

jr866gooner said:
Would Samsung smart switch not help installing the stock rom?
Click to expand...
Click to collapse
'Device not recognised' fixed it though. Flashed custom ROM with TWRP

Emergency recovery will and should help.

My galaxy s6 is stuck on bootloop nothing works please help.

Hello I am so new to this things, my S6 got stuck on installing system update. I downloaded official firmware and tried installing it with odin, it passed but then again got stuck installing system update. Can someone please help me, I am from El Salvador and I saved so much to buy this phone. When I go into recovery mode I get TWRP but i dont know what to do.

try downloadmode and install rom again wirh odin??

lambik333 said:
try downloadmode and install rom again wirh odin??
Click to expand...
Click to collapse
I did, same thing it gets stuck on installing system update screen

dbuyck1 said:
I did, same thing it gets stuck on installing system update screen
Click to expand...
Click to collapse
sometimes you have to wait for 10 mins......same as custom rom..

lambik333 said:
sometimes you have to wait for 10 mins......same as custom rom..
Click to expand...
Click to collapse
I waited for almost 5 hours nothing happened

dbuyck1 said:
I waited for almost 5 hours nothing happened
Click to expand...
Click to collapse
If you flashed a stock firmware successfully it will not boot into twrp, flashing a stock firmware will install stock recovery, which means the stock firmware did not flash properly. Have you tried smart switch at all? Are you sure you have the correct firmware to flash through odin?

sofir786 said:
If you flashed a stock firmware successfully it will not boot into twrp, flashing a stock firmware will install stock recovery, which means the stock firmware did not flash properly. Have you tried smart switch at all? Are you sure you have the correct firmware to flash through odin?[/QUOTE
Yes I am sorry I didn't explained that. Atfer I tried to install stock ROM it got stuck, then smart switch didn't recognize the device but I manage to do the emergency recovery thing with model number and s/n but same thing it got stuck on the same installing system update screen. After that I installed TWRP via Odin to try to push a custom ROM zip, I did that but when I tried to install it failed.
Click to expand...
Click to collapse

Download Samsung SmartSwitch and from the upper menu select Emergency Recovery Mode, put your phone in Download Mode and connect it to your computer, enter your model number and S/N when asked, and it will download and install latest firmware for your model.
Sorry, i haven't seen that you already tried that.

dbuyck1 said:
sofir786 said:
If you flashed a stock firmware successfully it will not boot into twrp, flashing a stock firmware will install stock recovery, which means the stock firmware did not flash properly. Have you tried smart switch at all? Are you sure you have the correct firmware to flash through odin?[/QUOTE
Yes I am sorry I didn't explained that. Atfer I tried to install stock ROM it got stuck, then smart switch didn't recognize the device but I manage to do the emergency recovery thing with model number and s/n but same thing it got stuck on the same installing system update screen. After that I installed TWRP via Odin to try to push a custom ROM zip, I did that but when I tried to install it failed.
Click to expand...
Click to collapse
That means TWRP works and Fastboot/Download works. What is the actual Galaxy S6 model? Mine is G920F.
What custom ROM did you try?
What version of TWRP are you using? The wrong one can create issues.
Did you wipe the phone trough TWRP first? Twice? Including internal memory?
Sent from my SM-G920F using XDA Labs
Click to expand...
Click to collapse