samsung gt-s7390 problem - Samsung Galaxy Fresh/Trend Questions & Answers

hi everyone
for start days ago my phone reboot sometimes alone and when it turn one it work normaly
but to day it turn of and it didn't start . it doesn't stop rebooting
(the hard reset doen't work)
so i took a look in forums they said that's a bootloop prob
i download the official firmware of my phone samsung gt-s7390 and install it with odin with out prob
but when it donne the phone reboot and i got a msg wrot in italy said " crittografia non eseguita " * translate in ENG - performed encryption - *
and a botton when you tap phone reboot ...... the msg again etc....
plz help
what is this prob and where it come from ( the coz )
thx alot

Same here. I'm trying to factory reset it but it won't let me, somehow. Next I think I need to try a custom ROM. But it's actually really hard to find a root for it via ODIN, since the device won't keep on for long enough to perform a root via softwares.

Ummm that's odd.
Same thing happened to me while ago, solved it by flashing the stock firmware.
Did u check the build version of your phone? It has to match the OS
If you stillhave access to download mode then try flashing a custom recovery and clearing Dalvik Cache, if that doesn't work then try flashing one of the cm11 roms

All i know... If you can get the only ROM i Ever found for gt-s7390 and Flash IT in Recovery (if you can) or try to use Odin... BUT DON'T FORGET TO WIPE ALL: DATA, CACHE, DALVIK AND SYSTEM PARTITIONS... I am using cm11 ( best i could find ) and TWRP (team Win Recovery project) or Just Factory reset? Idk i haven't got into a Situationeel like that...
Cheers and good luck :fingers-crossed:
-Dylan

Related

Device soft brick after flashing rom

Hello all hope you will be able to help me.
Device : Nexus S I 9020
So basicly iam kinda new to whole this world of "android" former Iphone user.
last mounth i got my nexus S wich is my first android phone.
As soon as i got it i started to read guids and etc.
Root the device and ofc the nexy step was trying Rom`s.
but then a problem , every time i try to flash a rom i get status 7 error.
tryed every possible combination of restore / wipe etc...
nothing helped , so i came back to the stock one (backup i made before i started)
after a while i discovered the app Rom mananger , wich install rom update recovery etc...
so i updated my recovery and installed CM7 using it.
used it for a while and went back to the stock.
after cople of days tryed to install MIUI using rom manger every thing went clear and after the intall device reboot it self and then stuck on the Google logo with the lock in the botom of the screen.
and nothing helped since then restore , factory reset/restore / wipe`s etc.
as last resort i tryed Odin and it worked like a charm got my device back and runing.
today i tryed to install a new rom AOASP(i think , or some thing like that) in the first time from the recovery (several times) with every possible wipe.
all the time status 7 error , then went to rom mananger and again same thing.
stuck on the google logo.
now iam gonna use Odin again hope it will work this time too.
Any idea how to resolve it , or why this is happen ?
and how can i resolve the status 7 error and what does it mean ?
Thank you all.
(sorry for this been so long , wanted to give as much details as possible)
Contact this guy. Looks like the same problem. If you can't get it going, I can also fix it so just PM me...
http://forum.xda-developers.com/showthread.php?t=1091789
doesnt seem to be the same problem like i had.
Any way at this point i was able to restore my phone using Odin , and then restore it into my stock backup (including all my data and etc...)
but the problem remain the same.
cant install any rom (status 7 error).
and when i try to install any rom using Rom mananger iam stuck on the google logo after the reboot.
so what can i do ?
Problem solved by using Odin ro restore it and after that flash Nanbackup and finally updating the CWM recovery.
If any one get the problem try this
Btw SuperAOSP is GREAT !!!!
gl all.

Another Newbie with a slight problem.

I tried to flash from darky's rom back to I9000UGJK3.tar
Using Odin i selected the s1_odin_20100512.pit then pda for I9000UGJK3.tar
Things went well with Odin but when the phone trys to boot the splash screen just flashes endlessly.
Im guessing i pooched something along the way.
Download mode works but not sure how to get this stock rom back on.
Any suggestion would be appreciated
sarcasm-inc said:
Using Odin i selected the s1_odin_20100512.pit then pda for I9000UGJK3.tar
Click to expand...
Click to collapse
You shouldn't use a pit or re-partition for a 1 file firmware.
I know i messed up,
Anyhow i just flashed I9000XXJPU, selected re-partition, and selected
PDA,MODEM,CSC.
Everthing worked then, when the phone rebooted, it says cannot mount sd card, use UI something. Then it just flashes the logo screen like before.
Update: reflashed with I9000UGL2 and the phone works now.
Now if i could only figure out what my original firmware was, Kies does not work now
To go back to stock:
1) Back up things u love
2) Make factory reset. Any reset options you can get
3) Wipe
4) Download firmware from samfirmaware.com
5) Patch with all 4 files
6) Factory reset, wipe, clear cache
Done
Well i followed the instruction from this page:
If you had enough or want to send it back in for warranty and want to go back to a STOCK ROM, this video shows how to go back to a 2.2.1 default ROM which in this case is JPY based - Made by AndroidGalaxyS:
http://forum.xda-developers.com/showthread.php?t=1009197
The problem now is I cannot remember what firmware i had. My phone is not coming up as a bell phone and the code to reinstall the provider apps will not work.
I think im screwed, have a feeling there gonna know i was messing with my phone if i try to bring it back, which is what i want to do. I have a extended warranty from Future shop, and supposedly they will not honour it for any software related problems.
Also now when my phone boots i keep getting a gallery force close. The phone is like a semi functional brick right now.
Not sure if the firmware is region specific in Canada as well but i got my phone in BC?
Usual Darky f9999 my phone repair kit .
Boot to restore wipe Dalvik cache followed by factory reset and wipe .
Boot to download mode flash stock rom with pit relevant to that rom and repartition checked .
Once working you can upgrade as you want .
jje
Sarcasm, just do as stated above. Find the default canadian firmware. If you can make make ur phone upgrade/update with kies, without messing with kies itself you r home.
Sent from my GT-I9000 using XDA App
Usual Darky f9999 my phone repair kit .
Boot to restore wipe Dalvik cache followed by factory reset and wipe .
Im not to sure how to do that. Is that in the recovery mode?
Update:
I used titanium backup to wipe davlik cache. re flashed with Firmware: I9000MUGKC1 found here:
http://forum.xda-developers.com/showthread.php?t=1022445
Still no luck Kies says this device version cannot be updated.
I tried this code to get the stock bell apps but it does not work. nothing happens when you finish with # then if i press the dial button it just says USSID code rejected.
*#272*353285040815508#

[Q] process com.android.phone has stopped - KitKat 4.4

Hello Guys
I have a greek Note 3, I had recently Android 4.3 with root and Omega Rom.
After a few days the Poland KitKat update came out, I installed it ( with all routine procedures, like format data/system, cleand cache/factory reset etc etc )
Now I have a problem: after phone startup, the following message appears:
"unfortunately the process com.android.phone has stopped"
untill i press "ok", the phone won't take signal or work right. After I press it, it work well :/
What can I do? is a known bug? I've tried everything (like format cache of telephone.apk and contacts.apk), but nothing worked.
Thank U
PS now i've noticed that I got no sound plug in/out when in charge.
PPS sorry for my bad eng
mirkonapoli said:
Hello Guys
I have a greek Note 3, I had recently Android 4.3 with root and Omega Rom.
After a few days the Poland KitKat update came out, I installed it ( with all routine procedures, like format data/system, cleand cache/factory reset etc etc )
Now I have a problem: after phone startup, the following message appears:
"unfortunately the process com.android.phone has stopped"
untill i press "ok", the phone won't take signal or work right. After I press it, it work well :/
What can I do? is a known bug? I've tried everything (like format cache of telephone.apk and contacts.apk), but nothing worked.
Thank U
PS now i've noticed that I got no sound plug in/out when in charge.
PPS sorry for my bad eng
Click to expand...
Click to collapse
Flash THIS
EDIT: Explanation: you warped your EFS folder flashing custom ROMs, it happens sometimes,so don't be too alarmed.
Hi!
Thx for your help, I flashed the zip but the fix dind't work :/
I don't think is a problem with the EFS partition ( I never touch it ).
Now i'm trying to flash one more time the Poland KitKat, then I'll root and flash that Zip.... hoping that is this the right way.
mirkonapoli said:
Hi!
Thx for your help, I flashed the zip but the fix dind't work :/
I don't think is a problem with the EFS partition ( I never touch it ).
Now i'm trying to flash one more time the Poland KitKat, then I'll root and flash that Zip.... hoping that is this the right way.
Click to expand...
Click to collapse
Hi,
Please, keep us informed of any solutions you might have found. I'm having a similar problem with a UK Note 3 - processes stop like there's no tomorrw, constant framework reboots - practically on any of the custom KitKat ROMs as well as the stock ones. Tried flashing with different Odin versions and using differrent stock firmwares - Polish, Dutch, etc. - same thing.
The EFS fix did not work for me - the thing is, you don't have to have touched the EFS partition to warp it. But in my case this didn't work.
So, please, let us know if you find any solution
Nick.
You need to format your entire system, custom recovery find /format system delete all and flash a custom ROM see if it fixes. Grab a pit file just in case you need to repartition also!
Sent from my SM-N9005 using XDA Premium 4 mobile app

[Q] My Note III is bricked??

Hi guys, I am new here, I am now finding help anywhere about my Note III recent problem...
My note III is SM-N9005 Malaysia version, I did root it with CF Auto Root and I had been using it without problems until yesterday morning,
This is my case :
I realized my alarm was written "Clock has been not responding" and I lost my network service, then I tried to restart my phone,
Since I restart, it became worst, my phone went into boot loop and sometimes freeze on the "Samsung Galaxy Note 3" screen,
But in a few times of reboot, it will be able to boot into homescreen, but still no service for the network, and everything processes work extremely slow, even freezing and crashing!
What I tried to do to fix it :
-I went to the Samsung service center, and the technician said that my warranty is voided (Ofcourse I knew it), and he told me that this problem is due to software problem instead of hardware.
-I did flash my kernel with stock kernel again which was downloaded from Sammobile, but it did not fix my problem,
-And I tried to hard reset and factory reset of my phone, it did not help too,
-I am also tried to clear cache and dalvik cache and reboot the device, it didn't seems working...
I have already done what I could but I still yet to fix my phone, what should I do now, any experts can guild me?? T^T
Thank you
KelvinEclipse said:
Hi guys, I am new here, I am now finding help anywhere about my Note III recent problem...
My note III is SM-N9005 Malaysia version, I did root it with CF Auto Root and I had been using it without problems until yesterday morning,
This is my case :
I realized my alarm was written "Clock has been not responding" and I lost my network service, then I tried to restart my phone,
Since I restart, it became worst, my phone went into boot loop and sometimes freeze on the "Samsung Galaxy Note 3" screen,
But in a few times of reboot, it will be able to boot into homescreen, but still no service for the network, and everything processes work extremely slow, even freezing and crashing!
What I tried to do to fix it :
-I went to the Samsung service center, and the technician said that my warranty is voided (Ofcourse I knew it), and he told me that this problem is due to software problem instead of hardware.
-I did flash my kernel with stock kernel again which was downloaded from Sammobile, but it did not fix my problem,
-And I tried to hard reset and factory reset of my phone, it did not help too,
-I am also tried to clear cache and dalvik cache and reboot the device, it didn't seems working...
I have already done what I could but I still yet to fix my phone, what should I do now, any experts can guild me?? T^T
Thank you
Click to expand...
Click to collapse
have you done a EFS backup? it helps if you run into problems like this....
check here...http://forum.xda-developers.com/showthread.php?t=2298104
this works on note 8 though
welard said:
have you done a EFS backup? it helps if you run into problems like this....
check here...http://forum.xda-developers.com/showthread.php?t=2298104
this works on note 8 though
Click to expand...
Click to collapse
I didn't really know about EFS while I root my phone, I just knew it recently due to my current issue, so I didn't backup it....
Is there any other solution??? Or could I recover my EFS eventhough I didn't do a backup??
BTW, thx for reply~
KelvinEclipse said:
I didn't really know about EFS while I root my phone, I just knew it recently due to my current issue, so I didn't backup it....
Is there any other solution??? Or could I recover my EFS eventhough I didn't do a backup??
BTW, thx for reply~
Click to expand...
Click to collapse
check your internal card or sd card for a folder called Backups or something similar, if your running a custom rom normally EFS is automatically stored there if your custom rom does do EFS backup automatically at install....if not do a search on the forum for EFS RECOVERY or re-flash your rom it may help or may not, but im sure it wont though...
also read though the link i sent you there maybe some think there that may help you
you can try to do install new firmware with odin 3:09 kitkate see how it behaves ....
ANDROIDXFOREVER said:
you can try to do install new firmware with odin 3:09 kitkate see how it behaves ....
Click to expand...
Click to collapse
Its not bricked if its still working. Have you tried turning on your phone without a sim card / sd card inserted?
also try *#06# to see if your imei number is presant..
try flashing stock rom
in the same boat hope u get it sorted, i just flashed the omega v14 onto my note and its stuck on the first screen
yulaw5110 said:
in the same boat hope u get it sorted, i just flashed the omega v14 onto my note and its stuck on the first screen
Click to expand...
Click to collapse
Reboot into recovery and wipe cache partition and then scroll to advanced and wipe dalvik cache, then reboot your phone
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thanks guys for the replies
-I went for a search for the backup folder in either of the storage mentioned by I didn't see a file called "backup"... I think I deleted it since the factory reset I've done yesterday, I went to many forums hat talk about EFS, and it wont help my problem cos all of them are talk about "Backup/recover", where I didn't backup my EFS earlier...
-I tried for the IMEI code, that's the reason I know about EFS, it shows "null/null", and most the information are showing unknown, such as baseband version, IMEISV, IP Address, Bluetooth Address.
-My current situation is whatever I flash into my phone, it just wont help, the problem didn't improvise at all...
Thanks..
KelvinEclipse said:
Thanks guys for the replies
-I went for a search for the backup folder in either of the storage mentioned by I didn't see a file called "backup"... I think I deleted it since the factory reset I've done yesterday, I went to many forums hat talk about EFS, and it wont help my problem cos all of them are talk about "Backup/recover", where I didn't backup my EFS earlier...
-I tried for the IMEI code, that's the reason I know about EFS, it shows "null/null", and most the information are showing unknown, such as baseband version, IMEISV, IP Address, Bluetooth Address.
-My current situation is whatever I flash into my phone, it just wont help, the problem didn't improvise at all...
Thanks..
Click to expand...
Click to collapse
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
doodydood said:
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
Click to expand...
Click to collapse
Thanks for the reply
I have tried the odin method and it didn't work...
Now I am trying for the kies emergency recovery method, and I will reply if there are any improvements...
Hi guys, I think have some new clues to determine my problem now
I flashed a custom recovery into my phone this morning,
and I realise that my /system, /efs and /firmware-modem is unmounted,
I tried to mount them, it was successful, but when I reboot the device, the problem still there,
Boot loop, no IMEI, no Baseband Version, Lag Processes,
and I went back to recovery again, I realised they have been unmounted again...
Any idea what is the problem guys??
Thx
doodydood said:
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
Click to expand...
Click to collapse
Hi there,
I have tried the kies emergency recovery method, but it was unsuccessful,
My note 3 was connected to the kies, but when I run Emergency Firmware Recovery,
My device was instantly disconnected with kies
And I have also tried the Firmware Upgrade and Initialisation,
The Kies showed me that my device is not supported with initialisation...
Anything I should do??
Thx
speedyjay said:
Reboot into recovery and wipe cache partition and then scroll to advanced and wipe dalvik cache, then reboot your phone
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i actually found a different kernal in the omega thread and that seemed to sort it, thanks tho

Help urgently !

today I tried to install CyanogenMod 12.1 on my Samsung note 3 SM-N900 (4.4.2) from this project
http://forum.xda-developers.com/gala...od-12-t2999486
and it mentioned in 1 of the comments that i have to get lollipop bootloader so i could flash the CM Mod ... so i flashed the bootloader and i tried to boot my device . It kept viewing many errors of many apps that stopped working and behind it is a black screen ... i tried resetting the mobile to its factory setting ( first time flashing ROMS so i was a bit afraid ) and it works totally fine . even when i restart the device but when i enter the recovery menu and click reboot from there the whole bunch of errors comes back .. so my question is what did i do ? what exactly is a boot loader ? could i continue on with my device like this without getting near the recovery menu ? or will it lead to an error in the near future ?
yoyo3999 said:
today I tried to install CyanogenMod 12.1 on my Samsung note 3 SM-N900 (4.4.2) from this project
http://forum.xda-developers.com/gala...od-12-t2999486
and it mentioned in 1 of the comments that i have to get lollipop bootloader so i could flash the CM Mod ... so i flashed the bootloader and i tried to boot my device . It kept viewing many errors of many apps that stopped working and behind it is a black screen ... i tried resetting the mobile to its factory setting ( first time flashing ROMS so i was a bit afraid ) and it works totally fine . even when i restart the device but when i enter the recovery menu and click reboot from there the whole bunch of errors comes back .. so my question is what did i do ? what exactly is a boot loader ? could i continue on with my device like this without getting near the recovery menu ? or will it lead to an error in the near future ?
Click to expand...
Click to collapse
You should have read before doing this.
It means flash the lollipop version first or update to lollipop if available.
Your url doesn't work for me.
Then flash twrp. In twrp flash cm12.1 and a recommended gapps.
You need to get logcat and post it to that thread so the developer can helo you. But first you need to do your part and at least get through the flashing process.
I wouldn't ignore any system errors.

Categories

Resources