Problem on Galaxy Ace S5830C - Android Q&A, Help & Troubleshooting

Hello friends,
I was trying to update the ROM on my Galaxy Ace S5830C and saw what needed to be installed on the mobile ClockWordMod before proceeding with the implementation of the sdcard zip, the problem is that installing CWM the phone just started showing a message, I believe it's something with the partition and folder / system. I ask your help to solve the problem!
Below are the error messages:
Error message as it enters the Recovery menu (still shows the old recovery):
E:failed to mount /system(invalid argument)
E:failed to mount /system(invalid argument)
Click to expand...
Click to collapse
Error message when I try to wipe reset / factory or installing any update via zip:
Formatting /data...
E:format_volume: rfs format failed on /dev/stl11
Formatting /data...
E:format_volume: rfs format failed on /dev/stl10
Data wipe complete.
Click to expand...
Click to collapse
And Wipe cache:
E:format_volume: rfs format failed on /dev/stl10
Click to expand...
Click to collapse
And before I forget, ACKNOWLEDGES THAT THE ONLY ODIN The is the version 1.85, versions superiors do not recognize the phone (not even show the active input COM) making it impossible to install the stock version on mobile. What makes me incapable of any form of recovery of the same. [/ Indent]
When I try to run the ODIN 1.85, in part to it's BcmBoot.img (spends a lot of time and goes nowhere), the following log:
NOTE: The phone is not noticed any difference, the number (count) always remains at zero.
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOT_S5830CVJLB3.tar.md5 is valid.
<OSM> PDA_S5830CVJLB3.tar.md5 is valid.
<OSM> PHONE_S5830CVJLB1.tar.md5 is valid.
<OSM> CSC_S5830CZTALB2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> BcmBoot.img
Click to expand...
Click to collapse
Looking forward to an answer, my sincere requests for help.
Sorry for my bad english, translated by Google Translator.
Regards,
RhĂșlio Victor

Have you rooted?? And make sure the CWM is made for your device itself
USING XDA APP ON SONY XPERIA U st25i

cyanide0007 said:
Have you rooted?? And make sure the CWM is made for your device itself
USING XDA APP ON SONY XPERIA U st25i
Click to expand...
Click to collapse
I don't make ROOT and CWM was not for my phone, I got the model from another Galaxy Ace was thinking the same.

rhulio said:
I don't make ROOT and CWM was not for my phone, I got the model from another Galaxy Ace was thinking the same.
Click to expand...
Click to collapse
Oh then 1st t root your phone then search for the compatible CWM for 5830c
USING XDA APP ON SONY XPERIA U st25i

Related

GT-N7105LTE(International)Service;Stock rooted Firmware Odex/Deodex ROM ODIN 3

Stock Prerooted Firmware Without loss of warranty Odex/Deodex ROM ODIN 3
Galaxy Note II N7105 LTE (International)
Odex/Deodexed
Rooted
Recovery & Kernel - Stock
For flash via PC Odin
No Wipe or Wipe (manual)
No Custom Binary Counter increase
Odex_Root_Stock_GT-N7105-VD2-N7105XXDMB2-1359939146
https://hotfile.com/dl/199104077/83ca755/Odex_Root_Stock_GT-N7105-VD2-N7105XXDMB2-1359939146.zip.html
Deodex_Root_Stock_GT-N7105-VD2-N7105XXDMB2-1359939146
https://hotfile.com/dl/199110023/9adad0e/Deodex_Root_Stock_GT-N7105-VD2-N7105XXDMB2-1359939146.zip.html
_____________________________________________
Odex_Root_Stock_GT-N7105-DTM-N7105XXDMB2-1359939146
https://hotfile.com/dl/199113014/724bb57/Odex_Root_Stock_GT-N7105-DTM-N7105XXDMB2-1359939146.zip.html
Deodex_Root_Stock_GT-N7105-DTM-N7105XXDMB2-1359939146
https://hotfile.com/dl/199125862/4425db8/Deodex_Root_Stock_GT-N7105-DTM-N7105XXDMB2-1359939146.zip.html
______________________________________________
Odex_Root_Stock_N7105XXDMB2_XEF
https://hotfile.com/dl/199524105/d1e9d27/Odex_Root_Stock_N7105XXDMB2_N7105XEFDMB2_N7105XXDLL5_XEF.zip.html
Deodex_Root_Stock_N7105XXDMB2_XEF
https://hotfile.com/dl/199525781/ad0cd30/Deodex_Root_Stock_N7105XXDMB2_N7105XEFDMB2_N7105XXDLL5_XEF.zip.html
______________________________________________
Odex_Root_Stock_N7105-XEF-N7105XXDMB6
https://hotfile.com/dl/200808328/a40e09b/Odex_Root_Stock_N7105-XEF-N7105XXDMB6-1361845002.zip.html
Deodex_Root_Stock_N7105-XEF-N7105XXDMB6
https://hotfile.com/dl/200809818/eb854b5/Deodex_Root_Stock_N7105-XEF-N7105XXDMB6-1361845002.zip.html
_______________________________________________
Odex_Root_Stock_GT-N7105-HUI-N7105XXDMC3
https://hotfile.com/dl/202869008/32c1213/ROS_GT-N7105-HUI-N7105XXDMC3.zip.html
Deodex_Root_Stock_GT-N7105-HUI-N7105XXDMC3
https://hotfile.com/dl/202872253/0d15f20/RDS_GT-N7105-HUI-N7105XXDMC3.zip.html
_______________________________________________
Odex_Root_Stock_N7105-VOD-N7105XXDMC3
https://hotfile.com/dl/205389037/046b8db/ROS_GT-N7105-VOD-N7105XXDMC3.zip.html
Deodex_Root_Stock_N7105-VOD-N7105XXDMC3
https://hotfile.com/dl/205420037/7438a7b/RDS_GT-N7105-VOD-N7105XXDMC3.zip.html
_______________________________________________
Odex_Root_Stock_N7105-SEB-N7105XXDMC3
https://hotfile.com/dl/205432998/73ecd7f/ROS_N7105-SEB-N7105XXDMC3.zip.html
Deodex_Root_Stock_N7105-SEB-N7105XXDMC3
https://hotfile.com/dl/205467427/817fa6f/RDS_N7105-SEB-N7105XXDMC3.zip.html
RDS_XEF-N7105XXDMC3
Download
ROS_XEF-N7105XXDMC3
Download
RDS_SWC-N7105XXDMC3
Download
ROS_SWC-N7105XXDMC3
Download
RDS_VGR-N7105XXDMC3
Download
ROS_VGR-N7105XXDMC3
Download
RDS_VNZ-N7105XXDMC3
Download
ROS_VNZ-N7105XXDMC3
Download
RDS_N7105XXDMB2_N7105EVRDMA2_EVR
Download
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
N7105-Service-Firmware
Warning!!!
Firmware consists of four parts, plus pit
Attention! All user data will be deleted during flash the firmware, including internal sdcard
After flash you will have clean device (factory condition) CSC - XEF default
Can flash with PIT - Included in the firmware (The optional - required if damaged partition PIT)
Composition zip:
> BOOTLOADER
> CSC
> PDA
> MODEM
> ODIN 3.07
> PIT
**************************************************************************************************************************
N7105XXDMB2-XEF-Service-Firmware
https://hotfile.com/dl/200944970/60d425e/N7105XXDMB2-XEF-Service-Firmware.zip.html >>>>> Updated PIT!!
**************************************************************************************************************************
N7105XXDMB6-XEF-Service-Firmware
https://hotfile.com/dl/200952208/2308d74/N7105XXDMB6-XEF-Service-Firmware.zip.html
View attachment 1825019
Special thank & big respect
chainfire
as i9000
bodivas
at cetera...
N7105 LTE
Hey...
i tried you solution but it didnt work...
i can only use custom roms..
can you help??
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> FULL_BOOTLOADER_N7105XXDMB2.tar.md5 is valid.
<OSM> FULL_PDA_N7105XXDMB2.tar.md5 is valid.
<OSM> FULL_MODEM_N7105XXDMB2.tar.md5 is valid.
<OSM> FULL_CSC_N7105XXDMB2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
malaach said:
Hey...
i tried you solution but it didnt work...
i can only use custom roms..
can you help??
Click to expand...
Click to collapse
Or try this View attachment N7105_PIT_File.zip
Updated
Odex_Root_Stock_N7105-XEF-N7105XXDMB6
Deodex_Root_Stock_N7105-XEF-N7105XXDMB6
Updated
N7105XXDMB6-XEF-Service-Firmware
Write what firmware should I do?
DTM? COV?TMH?......
Updated
Odex_Root_Stock_GT-N7105-HUI-N7105XXDMC3
Deodex_Root_Stock_GT-N7105-HUI-N7105XXDMC3
alexyuh said:
Odex_Root_Stock_GT-N7105-HUI-N7105XXDMC3
Deodex_Root_Stock_GT-N7105-HUI-N7105XXDMC3
Click to expand...
Click to collapse
Hi, will this version WIPE my data? Thanks
Merxury said:
Hi, will this version WIPE my data? Thanks
Click to expand...
Click to collapse
No-Wipe
Merxury said:
Hi, will this version WIPE my data? Thanks
Click to expand...
Click to collapse
won't
update
Odex_Root_Stock_N7105-VOD-N7105XXDMC3
Deodex_Root_Stock_N7105-VOD-N7105XXDMC3
Odex_Root_Stock_N7105-SEB-N7105XXDMC3
Deodex_Root_Stock_N7105-SEB-N7105XXDMC3
ZHDMB1
can i switch to XEF coming from a hongkong version stock ROM?
update: can confirm that switching to XEF worked fine for me
reason for changing: there's a bug in SMS messaging in latest 4.1.2 HK version N7105ZZHDMB1 / N7105ZHDMB1 / N7105XXDLL5
UPDATE
RDS_XEF-N7105XXDMC3
Download
ROS_XEF-N7105XXDMC3
Download
RDS_SWC-N7105XXDMC3
ROS_SWC-N7105XXDMC3
Download
RDS_VGR-N7105XXDMC3
Download
ROS_VGR-N7105XXDMC3
Download
RDS_VNZ-N7105XXDMC3
Download
ROS_VNZ-N7105XXDMC3
Download
RDS_ATL-N7105XXDMC3
ROS_ATL-N7105XXDMC3
RDS_H3G-N7105XXDMC3
ROS_H3G-N7105XXDMC3
RDS_OPT-N7105XXDMC3
ROS_OPT-N7105XXDMC3
RDS_N7105XXDMB2_N7105EVRDMA2_EVR
Download
Download....
Abbreviations:
ROS-Odex_Root_Stock
RDS-Deodex_Root_Stock
alexyuh said:
RDS_XEF-N7105XXDMC3
Download
ROS_XEF-N7105XXDMC3
Download
RDS_SWC-N7105XXDMC3
ROS_SWC-N7105XXDMC3
Download
RDS_VGR-N7105XXDMC3
Download
ROS_VGR-N7105XXDMC3
Download
RDS_VNZ-N7105XXDMC3
Download
ROS_VNZ-N7105XXDMC3
Download
RDS_ATL-N7105XXDMC3
ROS_ATL-N7105XXDMC3
RDS_H3G-N7105XXDMC3
ROS_H3G-N7105XXDMC3
RDS_OPT-N7105XXDMC3
ROS_OPT-N7105XXDMC3
Download....
Abbreviations:
ROS-Odex_Root_Stock
RDS-Deodex_Root_Stock
Click to expand...
Click to collapse
Country/Carrier Date Version PDA CSC
Singapore (StarHub) 2013 March 4.1.2 N7105XXDMB3 N7105OLBDMC1
i am having this....can i flash for Deodex?
is "VNZ-N7105XXDMC3" region VNZ = (Vodafone New Zealand) ?
Can I request this one deodexed and rooted please?
N7105XXDMB2_N7105EVRDMA2_EVR
Thanks in advance.
than'k for you'r ROS_XEF-N7105XXDMC3
it's ok
(InsertNameHere) said:
Can I request this one deodexed and rooted please?
N7105XXDMB2_N7105EVRDMA2_EVR
Thanks in advance.
Click to expand...
Click to collapse
RDS_N7105XXDMB2_N7105EVRDMA2_EVR
Download
alexyuh said:
RDS_N7105XXDMB2_N7105EVRDMA2_EVR
Download....
Click to expand...
Click to collapse
Cool, thanks to follow when I get my 8 thanks again tomorrow, gonna flash tonight.
(InsertNameHere) said:
Cool, thanks to follow when I get my 8 thanks again tomorrow, gonna flash tonight.
Click to expand...
Click to collapse
Problems with the Internet 3 times tore off downloading ((Provider our bad Russia))

[Q] assert failed: file_getprop "ro.build.PDA" XXELL4 JKay Deluxe / Stock // ERROR

[Q] assert failed: file_getprop "ro.build.PDA" XXELL4 JKay Deluxe / Stock // ERROR
Hi,
I just flashed Slim Bean ROM to my phone. After this didn't worked I tried to reflash with my former ROM JKay_Deluxe_Custom_Stock for XXELL4
But now I get this error:
Installing update...
detected!
assert failed: file_getprop("/system/build.prop", "ro.build.PDA") == "I9300XXELL4"
E: Error in /sdcard/XXELL4_JKay_Deluxe_Stock_v14_7_3.zip
(Status 7)
Installation aborted.
Please help me I just tried to fix it since 3 hours ...
My Phone:
I9300 Tmobile Germany
CWM v5.5.0.4 :: CF v1.5
G3ntlem4n said:
Hi,
I just flashed Slim Bean ROM to my phone. After this didn't worked I tried to reflash with my former ROM JKay_Deluxe_Custom_Stock for XXELL4
But now I get this error:
Installing update...
detected!
assert failed: file_getprop("/system/build.prop", "ro.build.PDA") == "I9300XXELL4"
E: Error in /sdcard/XXELL4_JKay_Deluxe_Stock_v14_7_3.zip
(Status 7)
Installation aborted.
Please help me I just tried to fix it since 3 hours ...
My Phone:
I9300 Tmobile Germany
CWM v5.5.0.4 :: CF v1.5
Click to expand...
Click to collapse
Restore your Nandroid backup .
or redownload firmware .
jje
JJEgan said:
Restore your Nandroid backup .
or redownload firmware .
jje
Click to expand...
Click to collapse
unfortunately I have no nandroid backup...
i will redownload firmware but its the same firmware I used before :/
you need newer jkay with newer rom, I suggest InsertCoin
JKay is a framework mod, it's not a rom.
after you flashed slim, you should've wiped data as the instructions said.
now, reflash the rom you had before slim or do a factory reset
I am just Downloading I9300XELLA
on sammobile that comes out when I put in my information:
GT-I9300
Germany(T-Mobile)
Is that correct stock rom for me? Cause right now it says XELL4
EDIT:
Just tried to put that firmware on my sgsIII
odin says:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL4_I9300DBTELL1_I9300XXELL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

[Q] Flashing Modem/Bootloader issue

Good aftternoon,
I've been trying to update my bootloader/modem from here
Edgars Latest BOOTLOADER/MODEM Packages
Choosing 900t and downloading it and following the directions for UVU1BNH5 it still shows up as NF6 no matter how many times I flash in the about settings.
I don't see any errors in Odin 3 and it flashes fine. I've pulled the battery before and after multiple times.
Anyone run into this and have a fix?
Alan Shore said:
Good aftternoon,
I've been trying to update my bootloader/modem from here
Edgars Latest BOOTLOADER/MODEM Packages
Choosing 900t and downloading it and following the directions for UVU1BNH5 it still shows up as NF6 no matter how many times I flash in the about settings.
I don't see any errors in Odin 3 and it flashes fine. I've pulled the battery before and after multiple times.
Anyone run into this and have a fix?
Click to expand...
Click to collapse
What shows up as NF6? The build number will always show as NF6, but the modem should be updated.
aooga said:
What shows up as NF6? The build number will always show as NF6, but the modem should be updated.
Click to expand...
Click to collapse
Thanks,
It's the baseband number that's still showing up NF6. So it will always say that but update the modem?
Alan Shore said:
Thanks,
It's the baseband number that's still showing up NF6. So it will always say that but update the modem?
Click to expand...
Click to collapse
Could you just post a screenshot of the about phone screen?
Sent from my SM-G900T using Tapatalk
aooga said:
Could you just post a screenshot of the about phone screen?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Attached... Thank you
Alan Shore said:
Attached... Thank you
Click to expand...
Click to collapse
Yeah it didn't flash. Where did you find Odin? Maybe its an older version.
Sent from my SM-G900T using Tapatalk
aooga said:
Yeah it didn't flash. Where did you find Odin? Maybe its an older version.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Here's a screenshot....
Alan Shore said:
Here's a screenshot....
Click to expand...
Click to collapse
Maybe wait till beanstown releases his version. The thread you posted says to do it multiple times if it doesn't work.
Sent from my SM-G900T using Tapatalk
aooga said:
Maybe wait till beanstown releases his version. The thread you posted says to do it multiple times if it doesn't work.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Alright, I'll wait for beanstown. Tried to do it multiple times, no go.
May be it a bad download. Just flashed mine an hour ago without any problem.
..
fffft said:
Your screen shot just shows you loading the modem file, i.e. before you press "start" to actually try writing it to your phone. We need an Odin log or screen shot after you press the start button to see how Odin handles it.
It's common practice to write a modem or radio file twice as they are fussy. And the bootloader @ Android 4.3 is more restrictive and will sometimes return an auth failure if you flash the modem alone. The workaround if that happens is to first address timing e.g. try a different USB cable and port, disable firewall and malware programs, etc. And if necessary, flash the full stock firmware that contains the desired modem. The latter when Odin simply refuses to flash the modem only.
But first we need to see if Odin is succeeding or not. And your screenshot was taken before the write cycle finished.
Also, confirm that your device is in fact a 900T model, not another variant e.g. 900A, 900F, etc.
.
Click to expand...
Click to collapse
I had similar problems every time I tried to update - I found the best solution for me was to flash the entire TAR - everything - not just firmware and modem but the full tar.
The downside is you have to reroot - and you have to re-flash recovery - but that doesn't take too much time - bottom line, I usually have to flash the full stock tar file once - sometimes twice - but never more than two -
I also found that I had to always use Odin 3.09 - but from the screen shot you posted, it looks like youi have that version of Odin anyway - so maybe try flashing the full stock tar and see if that helps.
Good Luck...
joking said:
May be it a bad download. Just flashed mine an hour ago without any problem.
Click to expand...
Click to collapse
Yea, not sure what it is I gave it a couple days just to settle and tried downloading the bootloader and modem and when I tried mounting them it md5 failed. I used an older download of the same modem and low and behold it flashed successfully first try. Am now BHN5. Still don't understand why it works part of the time. Thanks for all your help
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900T-UVU1BNH5-BOOTLOADER.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900T-UVU1BNH5-MODEM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> SingleDownload.
<ID:0/013> aboot.mbn
<ID:0/013> NAND Write Start!!
<ID:0/013> rpm.mbn
<ID:0/013> sbl1.mbn
<ID:0/013> sdi.mbn
<ID:0/013> tz.mbn
<ID:0/013> modem.bin
<ID:0/013> Transmission Complete..
<ID:0/013> Now Writing.. Please wait about 2 minutes
<ID:0/013> Receive Response from boot-loader
<ID:0/013> NON-HLOS.bin
<ID:0/013> Transmission Complete..
<ID:0/013> Now Writing.. Please wait about 2 minutes
<ID:0/013> Receive Response from boot-loader
<ID:0/013> RQT_CLOSE !!
<ID:0/013> RES OK !!
<ID:0/013> Removed!!
<ID:0/013> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

[Q] NOOB with an Galaxy S4 stuck on OC1 lollipop

Hey there guys.... Please read this first so I don't get flamed for taking a OTA update on a non rooted phone.
Heres the skinny.... My buddy gave me his old Galaxy S4 (Verizon I545). When I got it from him, it had KIt Kat on it. His phone was not hooked up with Verizon, since he just got a S5 and switched to AT&T. So I popped in my Tmobile sim card and away I went I had NO problems what so ever for three days. I wake up, and BAM it's Lollipop.
NOW, when it's on 4G, I can't send sms messages (but I can recieve them). I CAN send however send and recieve MMS messages. Internet, and phone work perfect. I have tried everything (wipe cached partition, reboot, clear data for messaging app, etc...), no luck
MY GOAL: Being that I live on a rural area (about 20 minute drive to get cell service), I have been using my wifi calling on my Tmobile phone (prior to taking the S4). My master plan was to root and flash a rom (like insane Kit kat) that would enable the wifi calling..... BUT it went to Lollipop before I could do so.
Now I cant send SMS, NOR can I flash it either.... OR could I??? Any help would be appreciated guys (and girls)..
NOTE: I have tried KingoRoot, and Towelroot... none supported my phone...
Thanks for your input in advance
fricci4993 said:
Hey there guys.... Please read this first so I don't get flamed for taking a OTA update on a non rooted phone.
Heres the skinny.... My buddy gave me his old Galaxy S4 (Verizon I545). When I got it from him, it had KIt Kat on it. His phone was not hooked up with Verizon, since he just got a S5 and switched to AT&T. So I popped in my Tmobile sim card and away I went I had NO problems what so ever for three days. I wake up, and BAM it's Lollipop.
NOW, when it's on 4G, I can't send sms messages (but I can recieve them). I CAN send however send and recieve MMS messages. Internet, and phone work perfect. I have tried everything (wipe cached partition, reboot, clear data for messaging app, etc...), no luck
MY GOAL: Being that I live on a rural area (about 20 minute drive to get cell service), I have been using my wifi calling on my Tmobile phone (prior to taking the S4). My master plan was to root and flash a rom (like insane Kit kat) that would enable the wifi calling..... BUT it went to Lollipop before I could do so.
Now I cant send SMS, NOR can I flash it either.... OR could I??? Any help would be appreciated guys (and girls)..
NOTE: I have tried KingoRoot, and Towelroot... none supported my phone...
Thanks for your input in advance
Click to expand...
Click to collapse
Never heard of something like this before... I'd think that there is no way back...
i have the same problem. if there is a rollback to kitkat
If the build number ends with OC1, then there is no going back. If it ends with something else... Possibly hope
XxD34THxX said:
If the build number ends with OC1, then there is no going back. If it ends with something else... Possibly hope
Click to expand...
Click to collapse
Can we do something to fix the sms issue?
eliah1 said:
Can we do something to fix the sms issue?
Click to expand...
Click to collapse
Yes 100%.
http://forum.xda-developers.com/gal...w-lollipop-t3099930/post60868269#post60868269
We are on stock rom and can t root the OC1.
Sent from my SAMSUNG-SM-G900AZ using XDA Free mobile app
XxD34THxX said:
Yes 100%.
http://forum.xda-developers.com/gal...w-lollipop-t3099930/post60868269#post60868269
Click to expand...
Click to collapse
That's awesome.... being a noob and you a senior member, I have a noob question, if we have a non rooted OC1, how can we get into the rom to do it? I thought we couldn't root it yet?
OC1 does not have root or ROM availability. Nothing can me nodded on OC1.
Repair your Device to Match T-Mobile!!
So, this is a Bit risky.....!!!!!!!
The reason is Because the device is trying to Connect to a Verizon APN. If you factory restore the Device to the T-Mobile Variant, It will Work Flawlessly!
BACKUP ALL YOUR DATA!!! This will WIPE EVERYTHING!!!!
These files are intended to be used with ODIN ONLY!! If at any time ODIN FAILS, pull battery, re-insert battery, go back to "ODIN Mode" and try again.
Here are the Two files you will need to Repair the Device to Be a T-Mobile Device!
These packages are Direct from Samsung and includes the PIT for partitioning!!
ODIN v.3.10:
https://drive.google.com/file/d/0B4RU_ZH5QUASSWhaMmdiaFJ1Tm8/view?usp=sharing
SGH-M919 Service Files:
https://drive.google.com/file/d/0B4RU_ZH5QUASbk5TMU9rdGtwTlU/view?usp=sharing
Extract the Two (2) Downloaded Zips
Right-Click on the "ODIN v.3.10.exe" and "Run as Administrator" on your Windows PC.
Click on each of the 4 buttons below and browse to find matching file in extracted image folder:
BL = BL_****.tar.md5
AP = AP_****.tar.md5
CP = CP-MODEM-****.tar.md5
CSC = CSC-****.tar.md5
Check the following boxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Put 100% charged device into ODIN Mode, and connect to PC USB with Original Cable.
Check there two boxes in ODIN:
Phone Bootloader Update
Clear EFS Partition
Hit the "Start" button
Once the Device reboots, Wait Ten minutes for Programming to occur.
Perform Two [2] FDR (Factory Data Reset), Just bskip thru the Wizard.
Phone is back to complete stock!!
Just to confirm, and not to doubt you (KaosMaster), have you done this, and can you point me to people who have? I know there is risk involved with any of this, but even a small problem can seem like a huge problem to a cell phone noob like me lol... Honestly, I have a lot of experience logging, and reflashing the ecm computer on my Mistsubishi Evo... Although its not a cell phone, it's the same premise in theory. :laugh: :laugh:
@KaosMaster
Also just to be clear, this will work with a NON rooted phone, that CANT be rooted at this time??
This is the STOCK Method! NO ROOT
fricci4993 said:
@KaosMaster
Also just to be clear, this will work with a NON rooted phone, that CANT be rooted at this time??
Click to expand...
Click to collapse
this will Completely reprogram your device to T-Mobile, yes it has been done before by others if you wanna Google Search!!
Worst case is that ODIN Fails To flash and we have to reload the Verizon Software!
You can reach me on Hangouts if you need any Personal help, being a NOOB!! XD
KaosMaster said:
Click on each of the 4 buttons below and browse to find matching file in extracted image folder:
BL = BL_****.tar.md5
AP = AP_****.tar.md5
CP = CP-MODEM-****.tar.md5
CSC = CSC-****.tar.md5
Check the following boxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Put 100% charged device into ODIN Mode, and connect to PC USB with Original Cable.
Check there two boxes in ODIN:
Phone Bootloader Update
Clear EFS Partition
Hit the "Start" button
Once the Device reboots, Wait Ten minutes for Programming to occur.
Perform Two [2] FDR (Factory Data Reset), Just bskip thru the Wizard.
Phone is back to complete stock!!
Click to expand...
Click to collapse
Every file I try to open with ODIN i'm getting a md5Error! Binary is invalid
here is the message box within ODIN
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> BL_M919UVUFNK2_2437203_REV06_user_low_ship.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> AP_M919UVUFNK2_2437203_REV06_user_low_ship.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CP_M919UVUFNK2_2437203_REV06_user_low_ship.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CSC-TMB_M919TMBFNK2_2437203_REV06_user_low_ship.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> BL_M919UVUFNK2_2437203_REV06_user_low_ship.tar.md5 is invalid.
<OSM> End...
OPPS!! Sorry!! ;/
Please rename the file, and just delete the ".md5" portion, and the files should work! I will re-upload shortly!!
KaosMaster said:
Please rename the file, and just delete the ".md5" portion, and the files should work! I will re-upload shortly!!
Click to expand...
Click to collapse
Removed those md5 file extensions but now heres the next issue i have
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on the ODIN MODE (on phone screen) shows this:
ODIN MODE
PRODUCT NAME : SCH-I545
CURRENT BIANARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: Off
CSB-CONFIG-LSB: 0X30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: Enable
eMAC BURST MODE: Enabled
START (224,1440)
ERASING USERDATA PARTITION
SECURE CHECK FAIL : PIT
So I clicked on the PIT button within the ODIN v3.10 and selected the PIT_JFLTE_USA_TMO.pit file andthis was the result
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dragon1018 said:
Removed those md5 file extensions but now heres the next issue i have
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on the ODIN MODE (on phone screen) shows this:
ODIN MODE
PRODUCT NAME : SCH-I545
CURRENT BIANARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: Off
CSB-CONFIG-LSB: 0X30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: Enable
eMAC BURST MODE: Enabled
START (224,1440)
ERASING USERDATA PARTITION
SECURE CHECK FAIL : PIT
So I clicked on the PIT button within the ODIN v3.10 and selected the PIT_JFLTE_USA_TMO.pit file andthis was the result
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I had the same error on my veriso I5454
Ok. Try no repartition, and skip the pit file
KaosMaster said:
Ok. Try no repartition, and skip the pit file
Click to expand...
Click to collapse
Same thing
Ok. I need to find the lollipop version for tmobile. Give me a few

*** Impossible to access to Recovery mode ***

I am using a Samsung Galaxy Grand 2 smartphone series SM-G7102
The smartphone is rooted and it's already working on a Cyanogen ROM , using ROM of this thread : https://forum.xda-developers.com/galaxy-grand-2/orig-development/dev-preview-lollipop-galaxy-grand2-sm-t2949693
I am having troubles with some functionnalities using my phone, so I decided to install a new ROM (https://forum.xda-developers.com/galaxy-grand-2/orig-development/rom-resurrectionremix-v5-8-0-t3534403)
The problem is : I can never access to recovery mode, have used used : VOL UP+MENU+POWER || VOL DOWN+MENU+POWER
But it always goes to downloading mode
I have tried to install a CWM like included in this thread https://forum.xda-developers.com/showthread.php?t=1837605
It goes well and the phone reboots normally. Here's the Odin log :
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ODINRecovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But when trying to boot into recovery mode, it always goes to download mode
Text included in Download mode :
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SM-G7102
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
UDC START
EDIT
The reason behind this wanted change is because the annoying appearance of these messages :
android.process.acore has stopped
Unfortunately, the process com.google.process.gapps has stopped.
I have disabled "Google Play services" & "Google Play Store" to prevent these messages from appearing again : I used substitutes instead like Yalp & F-droid : I have had a good time with my phone for months, but lately there appeared other annoying problems :
1- I can not activate WiFi !!
2- Whenever I use Camera there's : photos taken are black AND/OR not saved
3- I can never access galery
4- I can only go through the File Manager but I can no longer manipulate files : create directories ..
Any solutions for any of these problems please ??
ahmed_aek said:
I am using a Samsung Galaxy Grand 2 smartphone series SM-G7102
The smartphone is rooted and it's already working on a Cyanogen ROM
I am having troubles with some functionnalities using my phone, so I decided to install a new ROM (https://forum.xda-developers.com/ga...lopment/rom-resurrectionremix-v5-8-0-t3534403)
The problem is : I can never access to recovery mode, have used used : VOL UP+MENU+POWER || VOL DOWN+MENU+POWER
But it always goes to downloading mode
I have tried to install a CWM like included in this thread https://forum.xda-developers.com/showthread.php?t=1837605
It goes well and the phone reboots normally. Here's the Odin log :
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
ODINRecovery.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
recovery.img
NAND Write Start!!
RQT_CLOSE !!
RES OK !!
Removed!!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
But when trying to boot into recovery mode, it always goes to download mode
Text included in Download mode :
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SM-G7102
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
UDC START
Click to expand...
Click to collapse
Try holding vol+, home, and power. Let off of power once the splash image shows up.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Try holding vol+, home, and power. Let off of power once the splash image shows up.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
I DID , but nothing changed
Ha. Sorry, just posting because RealWelder's sig cracked me up - the Kyocera C6745 is what I totally expected this thread to be about when I saw the title, not a Samsung. (I swear it doesn't actually have a recovery, I don't care what the handful of people claiming to be able to boot the C6745 into it say...)
lugnut2099 said:
Ha. Sorry, just posting because RealWelder's sig cracked me up - the Kyocera C6745 is what I totally expected this thread to be about when I saw the title, not a Samsung. (I swear it doesn't actually have a recovery, I don't care what the handful of people claiming to be able to boot the C6745 into it say...)
Click to expand...
Click to collapse
I know this isn't the right place for this, but, the Hydro Air does have recovery... It's just stock though. The only way to get to it is to adb reboot recovery. The lack of root and recovery is why I use it as my daily... I don't know how many times I've soft-bricked my daily and had to be without a phone until I figured it out. Lol.
Sent from my KYOCERA-C6745 using Tapatalk

Categories

Resources